CN115567444B - Controller routing address searching and calling method and system - Google Patents
Controller routing address searching and calling method and system Download PDFInfo
- Publication number
- CN115567444B CN115567444B CN202211165009.9A CN202211165009A CN115567444B CN 115567444 B CN115567444 B CN 115567444B CN 202211165009 A CN202211165009 A CN 202211165009A CN 115567444 B CN115567444 B CN 115567444B
- Authority
- CN
- China
- Prior art keywords
- node
- controller
- path
- tree
- searching
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000003780 insertion Methods 0.000 claims 2
- 230000037431 insertion Effects 0.000 claims 2
- 238000011161 development Methods 0.000 abstract description 6
- 230000008569 process Effects 0.000 abstract description 5
- 238000004891 communication Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 230000003416 augmentation Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
Abstract
The application discloses a controller routing address lookup calling method and system. Firstly, obtaining information of each controller in a target client app, and determining different root nodes according to service types of each controller; generating a routing tree based on the path prefixes in the controllers corresponding to the root nodes and the service types; each controller in the service type corresponds to a leaf node, and the leaf node comprises a path, a controller name, the service type and a node depth; and acquiring information of the target controller to be called, and traversing the prefix tree in the generated routing tree according to the path of the target controller to obtain a searching and calling result of the target controller. The invention can improve the development efficiency of each module of the client app and the safety in the development process.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and a system for searching and calling a controller routing address.
Background
With the current trend of huge business, various modules are developed on client apps, each module can be understood as a new system, controllers in each module are more and more, because teams of the development of the modules are different, mutual calling is a necessary thing, the number of controllers can reach tens of thousands, and how to efficiently manage, control and call the controllers is an important thing.
However, in the face of increasing control, existing companies often call controllers using names that are controlled, for example, by specification, but communication costs are relatively high in the event that a new person is engaged, and naming controllers can lead to significant accidents on-line in the event that a new person is not fully aware.
Disclosure of Invention
Based on this, the embodiment of the application provides a controller routing address searching and calling method and system, which can improve the development efficiency of each module of the client app and improve the safety in the development process.
In a first aspect, a method for calling a controller to route address lookup is provided, the method comprising:
acquiring information of each controller in the target client app, and determining different root nodes according to the service types of each controller; wherein, different root nodes access through a routing single instance;
generating a routing tree based on the path prefixes in the controllers corresponding to the root nodes and the service types; each controller in the service type corresponds to a leaf node, and the leaf node comprises a path, a controller name, the service type and a node depth;
and acquiring information of the target controller to be called, and traversing the prefix tree in the generated routing tree according to the path of the target controller to obtain a searching and calling result of the target controller.
Optionally, performing prefix tree traversal in the generated routing tree according to the path of the target controller, including:
searching a target root node in a routing list according to the path of the target controller;
searching the child nodes of the next level until the searching and calling result of the target controller is obtained when the searching and calling result of the target controller does not exist in the current level based on the child nodes of the target root node.
Optionally, generating a routing tree based on each root node and the path prefix in the controller corresponding to each service type, further includes:
and matching the paths of the remaining controllers with the existing prefix tree, and finding the positions of the leaf nodes generated by the remaining controllers in the routing tree.
Optionally, determining different root nodes according to the service types to which each controller belongs includes:
calling an addRouter method of the routing singleton, finding a corresponding root node according to the name of the service type, judging whether the root node exists or not, and if not, creating.
Optionally, performing prefix tree traversal in the generated routing tree according to the path of the target controller, including:
searching a common prefix of a path with the target controller in the routing tree;
and updating the unspecified child node of the current node to continue searching when the common prefix of the current leaf node and the path of the target controller is updated.
In a second aspect, a controller routing address lookup call system is provided, the system comprising:
the acquisition module is used for acquiring information of each controller in the target client app and determining different root nodes according to the service types of each controller; wherein, different root nodes access through a routing single instance;
the generating module is used for generating a routing tree based on each root node and the path prefix in the controller corresponding to each service type; each controller in the service type corresponds to a leaf node, and the leaf node comprises a path, a controller name, the service type and a node depth;
and the searching module is used for acquiring the information of the target controller to be called, and traversing the prefix tree in the generated routing tree according to the path of the target controller to obtain a searching and calling result of the target controller.
Optionally, performing prefix tree traversal in the generated routing tree according to the path of the target controller in the lookup module includes:
searching a target root node in a routing list according to the path of the target controller;
searching the child nodes of the next level until the searching and calling result of the target controller is obtained when the searching and calling result of the target controller does not exist in the current level based on the child nodes of the target root node.
Optionally, the generating module generates a routing tree based on each root node and the path prefix in the controller corresponding to each service type, and further includes:
and matching the paths of the remaining controllers with the existing prefix tree, and finding the positions of the leaf nodes generated by the remaining controllers in the routing tree.
Optionally, the determining, in the obtaining module, different root nodes according to service types to which each controller belongs includes:
calling an addRouter system of the routing singleton, finding a corresponding root node according to the name of the service type, judging whether the root node exists or not, and if not, creating.
Optionally, performing prefix tree traversal in the generated routing tree according to the path of the target controller in the lookup module includes:
searching a common prefix of a path with the target controller in the routing tree;
and updating the unspecified child node of the current node to continue searching when the common prefix of the current leaf node and the path of the target controller is updated.
In the technical scheme provided by the embodiment of the application, the information of each controller in the target client app is firstly obtained, and different root nodes are determined according to the service types of each controller; generating a routing tree based on the path prefixes in the controllers corresponding to the root nodes and the service types; each controller in the service type corresponds to a leaf node, and the leaf node comprises a path, a controller name, the service type and a node depth; and acquiring information of the target controller to be called, and traversing the prefix tree in the generated routing tree according to the path of the target controller to obtain a searching and calling result of the target controller. It can be seen that the beneficial effects of the invention are:
(1) Different businesses are isolated in the program, so that the possibility that one app is developed by different business departments and finally put on shelf is combined.
(2) Tens of thousands of controllers invoke time milliseconds.
(3) And the plugging target of the authority check and control logic at any time is realized.
(4) The communication efficiency of each department is improved, and the workload of the test department is greatly reduced.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below. It will be apparent to those skilled in the art from this disclosure that the drawings described below are merely exemplary and that other embodiments may be derived from the drawings provided without undue effort.
FIG. 1 is a flowchart of a controller routing address lookup call method provided in an embodiment of the present application;
fig. 2 is a schematic structural diagram of a root node according to an embodiment of the present application;
FIG. 3 is a flowchart of searching an inserted node in a routing tree according to an embodiment of the present application;
fig. 4 is a block diagram of a controller routing address lookup call system according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.
In the description of the present invention, the terms "comprises," "comprising," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements but may include other steps or elements not expressly listed but inherent to such process, method, article, or apparatus or steps or elements added based on further optimization of the inventive concept.
The method aims at isolating each module through different module root (root) nodes, reducing development and communication costs of each module, reducing workload of testers and improving stability of future edition; meanwhile, the size of the storage controller on the data structure is reduced, the speed of searching the controller is improved, and the searching time O (n) is improved to O (log 2 n) compared with the previous searching time; in addition, from the state of the single-instance controller, a verification method can be added at will, and the problem that the client app cannot add middleware is solved.
Specifically, please refer to fig. 1, which illustrates a flowchart of a controller routing address lookup calling method according to an embodiment of the present application, the method may include the following steps:
step 101, obtaining information of each controller in the target client app, and determining different root nodes according to the service types of each controller.
Wherein, different root nodes access through a routing singleton.
In the embodiment of the present application, step 101 specifically includes:
(1) A node structure is defined, and this application mainly includes a routing list (routing), a root node (root), and a child node (node).
(1) Routing single case: and a plurality of root controllers are globally held in a life cycle and are put in a memory, so that the speed of creating and accessing each node is improved.
(2) The root node (root) is divided into a common controller, a tabbar controller, a basic tool class, a network class, a statistical class and a webpage class according to different overall services.
(3) The child node (node) contains the current path, own child node, the name (type array) of the controller (method), the number of routes passing through the child node, the type of the node, and the complete path of the current node.
As in fig. 2, a schematic diagram of the structure in a root node is given.
Step 102, generating a routing tree based on the path prefixes in the controllers corresponding to the root nodes and the service types.
Each controller in the service type corresponds to a leaf node, and the leaf node comprises a path (path), a controller name, the service type and a node depth.
And matching the paths of the remaining controllers with the existing prefix tree, and finding the positions of the leaf nodes generated by the remaining controllers in the routing tree.
In the embodiment of the present application, step 102 specifically includes:
(2) A routing tree is generated.
(1) The App starts the entry man function to start constructing the routing tree, judges whether the tree is constructed locally or not, and if so, directly reads the memory.
(2) And generating an absolute path, calling an addRouter method of the single-instance object, finding a corresponding root node according to the name of the module, judging whether the root node exists or not, and creating if the root node does not exist.
(3) The child node is found according to the root node (root), and then the addRouter of the child node is called to add the path to the appropriate node of the tree.
In an alternative embodiment of the present application, step 102 further includes:
(3) Adding child node-method of joining child node again at child node.
(1) And matching according to the path and the existing prefix tree, and finding the positions of child nodes to be inserted in the rest paths.
(2) The node is inserted at this location, and if the tree is empty, the process of adding the first path becomes simply inserting the node.
Step 103, obtaining information of the target controller to be called, and traversing the prefix tree in the generated routing tree according to the path of the target controller to obtain a searching and calling result of the target controller.
In the embodiment of the application, a target root node is found in a routing single instance according to a path of a target controller; searching the child nodes of the next level until the searching and calling result of the target controller is obtained when the searching and calling result of the target controller does not exist in the current level based on the child nodes of the target root node.
In the embodiment of the present application, step 103 specifically includes:
(4) The inserted node is looked up.
When the root node is not an empty node, a prefix tree needs to be searched, a node with an empty path is found, the rest paths which are not matched with the existing tree are inserted, and then the method name is typed in finally so as to be used for calling a method related to searching in future.
Meanwhile, as shown in fig. 3, a flowchart for searching the inserted node in the routing tree provided in the embodiment of the present application is provided.
(5) Method for calling correlation through route
(1) And using a single example of the system to find the root of the corresponding module.
(2) The working root finds out the corresponding child node, then starts to traverse the prefix tree according to the path until a related method is found, if no related path exists in the child node, prints log, and establishes a default controller.
(5) Route augmentation middleware
(1) The relevant nodes are found by the path.
(2) Then, when the handleChain adding method of the node is called, the relevant father node is searched from a single instance, the controller chain of the father node is called, and then the relevant method is searched layer by layer until finally.
In summary, the idea of the prefix tree is introduced, but the prefix tree is not completely used, and the same path is placed on the path of the node, so that the storage space is saved and the searching efficiency is improved. Different root nodes are constructed through different service modules, so that each department can maintain own frames conveniently, and unnecessary communication is reduced. The method chain is added, so that a user-defined method can be added at any place more efficiently, and the situation that chained calling cannot be achieved before is broken through. And carrying out multi-layer cache on the constructed tree, so that the time cost of construction is reduced, and the starting rate of the app is improved.
As shown in fig. 4, the embodiment of the application further provides a controller routing address lookup calling system. The system comprises:
the obtaining module 401 is configured to obtain information of each controller in the target client app, and determine different root nodes according to a service type to which each controller belongs; wherein, different root nodes access through a routing single instance;
a generating module 402, configured to generate a routing tree based on each root node and a path prefix in the controller corresponding to each service type; each controller in the service type corresponds to a leaf node, and the leaf node comprises a path, a controller name, the service type and a node depth;
the searching module 403 is configured to obtain information of the target controller to be invoked, and perform prefix tree traversal in the generated routing tree according to the path of the target controller, so as to obtain a searching and invoking result of the target controller.
In an optional embodiment of the present application, the searching module 403 performs prefix tree traversal in the generated routing tree according to the path of the target controller, including searching for the target root node in the routing singleton according to the path of the target controller; searching the child nodes of the next level until the searching and calling result of the target controller is obtained when the searching and calling result of the target controller does not exist in the current level based on the child nodes of the target root node.
In an optional embodiment of the present application, the generating module 402 generates a routing tree based on each root node and the path prefix in the controller corresponding to each service type, and further includes matching the paths of the remaining controllers with the existing prefix tree, and finding the positions of the leaf nodes generated by the remaining controllers in the routing tree.
In an optional embodiment of the present application, the obtaining module 401 determines different root nodes according to the service types to which each controller belongs, including invoking an addRouter system of a routing case, finding a corresponding root node according to a name of the service type, determining whether the root node exists, and creating if not.
In an alternative embodiment of the present application, the searching module 403 performs prefix tree traversal in the generated routing tree according to the path of the target controller, including searching the routing tree for the common prefix of the path of the target controller; and updating the unspecified child node of the current node to continue searching when the common prefix of the current leaf node and the path of the target controller is updated.
The controller routing address lookup and call system provided in the embodiments of the present application is used to implement the above-mentioned controller routing address lookup and call method, and the specific limitation of the controller routing address lookup and call system can be referred to the limitation of the controller routing address lookup and call method hereinabove, which is not repeated herein. The various parts of the controller routing address lookup call system described above may be implemented in whole or in part by software, hardware, and combinations thereof. The above modules may be embedded in hardware or independent of a processor in the device, or may be stored in software in a memory in the device, so that the processor may call and execute operations corresponding to the above modules.
The technical features of the above-described embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above-described embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The above examples only represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the claims. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application is to be determined by the claims appended hereto.
Claims (4)
1. A controller routing address lookup call method, the method comprising:
acquiring information of each controller in the target client app, and determining different root nodes according to the service types of each controller; wherein, different root nodes access through a routing single instance;
generating a routing tree based on the path prefixes in the controllers corresponding to the root nodes and the service types; each controller in the service type corresponds to a leaf node, and the leaf node comprises a path, a controller name, the service type and a node depth;
acquiring target controller information to be called, and performing prefix tree traversal in the generated routing tree according to the path of the target controller to obtain a searching and calling result of the target controller;
the steps of obtaining the information of each controller in the target client app, and determining different root nodes according to the service types of each controller comprise: acquiring information of each controller in the target client app, and determining different root nodes according to the service types of each controller; different root nodes access through a routing single instance, and specifically comprise a defined node structure body which mainly comprises the routing single instance, the root nodes and the child nodes; the routing list has a plurality of large root controllers globally in a life cycle and is placed in a memory, so that the speed of creating and accessing each node is improved; the root node is divided into a common controller, a tabbar controller, a basic tool class, a network class, a statistics class and a webpage class according to the difference of the whole business; the child nodes comprise current paths, own child nodes and names of controllers, the number of routes passing through the child nodes, the types of the nodes and the complete paths of the current nodes;
generating a routing tree based on the path prefixes in the controllers corresponding to the root nodes and the service types, wherein each controller in the service types corresponds to a leaf node, and the leaf node comprises a path, a controller name, a service type and a node depth; according to the matching between the paths of the remaining controllers and the existing prefix tree, the position of the leaf node generated by the remaining controllers in the routing tree is found, which specifically comprises: generating a routing tree, starting an entry man function by an App to construct the routing tree, judging whether the tree is constructed locally or not, and if so, directly reading the memory; generating an absolute path, then calling an addRouter method of the single-instance object, finding a corresponding root node according to the name of the module, judging whether the root node exists or not, and if not, creating; finding a child node according to the root node, then calling an addRouter of the child node, and adding a path to the nodes of the tree; adding a child node, namely adding the child node again in the child node, specifically matching the child node according to the path and the existing prefix tree, and finding the positions of the child nodes, which need to be inserted, of the rest paths; inserting the first path into the node at the position, and if the tree is empty, adding the first path into the node only;
acquiring target controller information to be called, performing prefix tree traversal in the generated routing tree according to the path of the target controller, and acquiring a searching and calling result of the target controller comprises searching a target root node in a routing single instance according to the path of the target controller; searching the child nodes of the next level until the searching and calling result of the target controller is obtained when the searching and calling result of the target controller does not exist in the current level based on the child nodes of the target root node; the method specifically comprises the steps of searching an insertion node, searching a prefix tree when a root node is not an empty node, finding a node with an empty path, inserting the rest paths which are not matched with the existing tree, and finally typing in a method name for future call of a method related to searching.
2. The method of claim 1, wherein traversing the prefix tree in the generated routing tree based on the path of the target controller comprises:
searching a common prefix of a path with the target controller in the routing tree;
and updating the unspecified child node of the current node to continue searching when the common prefix of the current leaf node and the path of the target controller is updated.
3. A controller routing address lookup call system, the system comprising:
the acquisition module is used for acquiring information of each controller in the target client app and determining different root nodes according to the service types of each controller; wherein, different root nodes access through a routing single instance;
the generating module is used for generating a routing tree based on each root node and the path prefix in the controller corresponding to each service type; each controller in the service type corresponds to a leaf node, and the leaf node comprises a path, a controller name, the service type and a node depth;
the searching module is used for acquiring information of the target controller to be called, and performing prefix tree traversal in the generated routing tree according to the path of the target controller to obtain a searching and calling result of the target controller;
the acquisition module comprises: acquiring information of each controller in the target client app, and determining different root nodes according to the service types of each controller; different root nodes access through a routing single instance, and specifically comprise a defined node structure body which mainly comprises the routing single instance, the root nodes and the child nodes; the routing list has a plurality of large root controllers globally in a life cycle and is placed in a memory, so that the speed of creating and accessing each node is improved; the root node is divided into a common controller, a tabbar controller, a basic tool class, a network class, a statistics class and a webpage class according to the difference of the whole business; the child nodes comprise current paths, own child nodes and names of controllers, the number of routes passing through the child nodes, the types of the nodes and the complete paths of the current nodes;
in the generation module, each controller in the service type corresponds to a leaf node, and the leaf node comprises a path, a controller name, the service type and a node depth; according to the matching between the paths of the remaining controllers and the existing prefix tree, the position of the leaf node generated by the remaining controllers in the routing tree is found, which specifically comprises: generating a routing tree, starting an entry man function by an App to construct the routing tree, judging whether the tree is constructed locally or not, and if so, directly reading the memory; generating an absolute path, then calling an addRouter method of the single-instance object, finding a corresponding root node according to the name of the module, judging whether the root node exists or not, and if not, creating; finding a child node according to the root node, then calling an addRouter of the child node, and adding a path to the nodes of the tree; adding a child node, namely adding the child node again in the child node, specifically matching the child node according to the path and the existing prefix tree, and finding the positions of the child nodes, which need to be inserted, of the rest paths; inserting the first path into the node at the position, and if the tree is empty, adding the first path into the node only;
the searching module comprises searching a target root node in the routing single instance according to the path of the target controller; searching the child nodes of the next level until the searching and calling result of the target controller is obtained when the searching and calling result of the target controller does not exist in the current level based on the child nodes of the target root node; the method specifically comprises the steps of searching an insertion node, searching a prefix tree when a root node is not an empty node, finding a node with an empty path, inserting the rest paths which are not matched with the existing tree, and finally typing in a method name for future call of a method related to searching.
4. The system of claim 3, wherein the performing prefix tree traversal in the generated routing tree according to the path of the target controller in the lookup module comprises:
searching a common prefix of a path with the target controller in the routing tree;
and updating the unspecified child node of the current node to continue searching when the common prefix of the current leaf node and the path of the target controller is updated.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211165009.9A CN115567444B (en) | 2022-09-23 | 2022-09-23 | Controller routing address searching and calling method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211165009.9A CN115567444B (en) | 2022-09-23 | 2022-09-23 | Controller routing address searching and calling method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115567444A CN115567444A (en) | 2023-01-03 |
| CN115567444B true CN115567444B (en) | 2024-02-27 |
Family
ID=84741548
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211165009.9A Active CN115567444B (en) | 2022-09-23 | 2022-09-23 | Controller routing address searching and calling method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115567444B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6266706B1 (en) * | 1997-09-15 | 2001-07-24 | Effnet Group Ab | Fast routing lookup system using complete prefix tree, bit vector, and pointers in a routing table for determining where to route IP datagrams |
| WO2013078644A1 (en) * | 2011-11-30 | 2013-06-06 | 华为技术有限公司 | Route prefix storage method and device and route address searching method and device |
| CN105491094A (en) * | 2014-09-24 | 2016-04-13 | 腾讯科技（深圳）有限公司 | HTTP request handling method and device |
| CN108134739A (en) * | 2016-12-01 | 2018-06-08 | 深圳市中兴微电子技术有限公司 | A kind of method for searching route and device based on index trie |
| CN110290117A (en) * | 2019-06-06 | 2019-09-27 | 新华三信息安全技术有限公司 | A kind of method and device of Match IP Address |
| CN112667636A (en) * | 2020-12-30 | 2021-04-16 | 杭州趣链科技有限公司 | Index establishing method, device and storage medium |
| CN112887212A (en) * | 2021-02-25 | 2021-06-01 | 清华大学 | High-speed route searching method and device based on variable stride width trie tree |
| CN114900546A (en) * | 2022-07-08 | 2022-08-12 | 支付宝(杭州)信息技术有限公司 | Data processing method, device and equipment and readable storage medium |
| CN115086221A (en) * | 2022-07-27 | 2022-09-20 | 新华三半导体技术有限公司 | Message processing method, device, forwarding equipment and storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7581204B2 (en) * | 2004-06-01 | 2009-08-25 | Sap Ag | Dynamic contexts |
| CN111553669B (en) * | 2020-04-28 | 2021-09-10 | 腾讯科技（深圳）有限公司 | Transaction routing method, device and computer readable storage medium |
-
2022
- 2022-09-23 CN CN202211165009.9A patent/CN115567444B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6266706B1 (en) * | 1997-09-15 | 2001-07-24 | Effnet Group Ab | Fast routing lookup system using complete prefix tree, bit vector, and pointers in a routing table for determining where to route IP datagrams |
| WO2013078644A1 (en) * | 2011-11-30 | 2013-06-06 | 华为技术有限公司 | Route prefix storage method and device and route address searching method and device |
| CN103404092A (en) * | 2011-11-30 | 2013-11-20 | 华为技术有限公司 | Route prefix storage method and device and route address searching method and device |
| CN105491094A (en) * | 2014-09-24 | 2016-04-13 | 腾讯科技（深圳）有限公司 | HTTP request handling method and device |
| CN108134739A (en) * | 2016-12-01 | 2018-06-08 | 深圳市中兴微电子技术有限公司 | A kind of method for searching route and device based on index trie |
| CN110290117A (en) * | 2019-06-06 | 2019-09-27 | 新华三信息安全技术有限公司 | A kind of method and device of Match IP Address |
| CN112667636A (en) * | 2020-12-30 | 2021-04-16 | 杭州趣链科技有限公司 | Index establishing method, device and storage medium |
| CN112887212A (en) * | 2021-02-25 | 2021-06-01 | 清华大学 | High-speed route searching method and device based on variable stride width trie tree |
| CN114900546A (en) * | 2022-07-08 | 2022-08-12 | 支付宝(杭州)信息技术有限公司 | Data processing method, device and equipment and readable storage medium |
| CN115086221A (en) * | 2022-07-27 | 2022-09-20 | 新华三半导体技术有限公司 | Message processing method, device, forwarding equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115567444A (en) | 2023-01-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10324909B2 (en) | Omega names: name generation and derivation utilizing nested three or more attributes | |
| US10073876B2 (en) | Bloom filter index for device discovery | |
| US9483508B1 (en) | Omega names: name generation and derivation | |
| CN111488143A (en) | Automatic code generation device and method based on Springboot2 | |
| CN106547646B (en) | Data backup and recovery method and data backup and recovery device | |
| US11934674B2 (en) | Method, electronic device, and computer program product for storing and accessing data across multiple servers utilizing metadata of a distributed hash table | |
| US20120078970A1 (en) | Performance of Hash Tables | |
| CN112559635B (en) | Service processing method, device, equipment and medium for Ethernet alliance chain node | |
| CN113704790A (en) | Abnormal log information summarizing method and computer equipment | |
| US11409724B2 (en) | Hashed balanced tree data structure | |
| CN111124872A (en) | Branch detection method and device based on difference code analysis and storage medium | |
| US11768759B2 (en) | Method and system for automated testing of web service APIs | |
| CN112269839B (en) | Data storage method and device in blockchain, electronic equipment and storage medium | |
| CN111339055B (en) | Big data cluster capacity expansion method and device | |
| CN115567444B (en) | Controller routing address searching and calling method and system | |
| CN110263104A (en) | JSON character string processing method and device | |
| CN112860412B (en) | Service data processing method and device, electronic equipment and storage medium | |
| CN115203746A (en) | Data account access authorization method and device | |
| CN115221559A (en) | Data account access authorization method and device | |
| CN112395339B (en) | Intersystem data admission verification method, device, computer equipment and storage medium | |
| CN112579591B (en) | Data verification method, device, electronic equipment and computer readable storage medium | |
| US10735539B1 (en) | Publish/subscribe system broker | |
| CN109918147B (en) | Expansion method and device for drive under OpenStack and electronic equipment | |
| CN113254399A (en) | Log query method and device, electronic equipment and medium | |
| CN113992664A (en) | Cluster communication method, related device and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |