Hierarchical Identifier Addressing Method

Abstract

A hierarchical identifier addressing method, the method comprising: step 1) receiving a request message including an identifier of a requesting network entity; step 2) analyzing the identifier in an edge router of a control domain to obtain an address; if the address obtained by the analysis is a final destination address, terminating the process; otherwise, the address obtained by the analysis is a border router address of the administrative domain where the network entity resides, and thus entering step 3); step 3) in the border router of the administrative domain matching the identifier of the entity in this administrative domain with a controller storing a mapping relationship related to the identifier, if a matching controller is found, performing identifier analysis and addressing in the matching controller, and returning to step 2); otherwise, executing step 4); step 4) in the administrative domain border router determining an intermediate border router corresponding to the identifier, and in the intermediate border router obtaining the border router of the administrative domain related to the identifier by an index, and executing step 3).

Description

[Technical Field]

[0001] [CROSS-REFERENCE TO RELATED APPLICATIONS] This application claims priority to Chinese Patent Application No. 2020113263621, filed on November 24, 2020, entitled "Hierarchical Structure Identifier Addressing Method," and Chinese Patent Application No. 2021105002713, filed on May 8, 2021, the entire contents of which are incorporated herein by reference. The present invention relates to the field of network technology and communication technology, and more particularly to a hierarchical identifier addressing method. [Background technology]

[0002] With the development of new technologies and applications such as the Internet of Things (IoT), mobile access, distributed information processing, and massive streaming media, the performance of computer networks based on the current TCP / IP architecture is already approaching its limits. The conflict between the enormous demand for information content services and network bandwidth bottlenecks is becoming increasingly severe. Network bottlenecks caused by IP network structures have become a major factor hindering the development of the current network application layer. The existing Internet TCP / IP system architecture has many problems in areas such as scalability, mobility, multihoming, and traffic engineering. The IP addresses currently used by the Internet have the dual meaning of locator information and identifier information, which confuses the functional boundary between locator and identifier, resulting in semantic overload of IP addresses. This naming mechanism is also a significant constraint on the development of network technology.

[0003] In response to these issues, academics and various standardization organizations are intensifying research into new future Internet architectures. At the beginning of this century, Information-Centric Networking (ICN) was proposed, focusing on the Internet's primary needs. It is an information / content-centric network system architecture that establishes a non-interfering relationship between information and locators. This technology improves the network's information storage capabilities and enhances content retrieval, mobility support, and content-oriented security mechanisms. Representative ICN series standards include NDN, DONA, NetInf, and PURSUIT. In 2009, the International Internet Engineering Task Force (IETF) launched the Locator / ID Separation Protocol (LISP) Working Group, which proposed separating identifiers and addresses to solve routing system problems. In 2018, the European Telecommunications Standards Institute (ETSI) published "NGP 004: Evolved Architecture for Mobility Using Identity-Oriented Networks," which supports traditional mobility based on the concept of name and address separation. The new network architecture based on the idea of ​​separating identifiers and addresses has already provided a new perspective for solving the problems of traditional TCP / IP networks. After the separation of locators and identifiers, the current research focus is on how to design a routing mechanism that utilizes the uniqueness and persistence characteristics of identifiers to meet the needs of future Internet development.

[0004] Identifier-based routing methods can be divided into two types: direct routing based on identifiers, and methods that perform analysis and addressing based on identifiers and then perform routing based on addresses. The direct routing based on identifiers directly maps the identifiers of objects to routes, i.e., integrates the analysis path of locators and identifiers with the return path of routing information, and representative examples include CCN / NDN. The address-based routing based on identifiers first maps the identifiers to addresses using a name resolution system, and then uses address-based routing, and representative examples include DONA and MobilityFirst.

[0005] The first type of method does not need to rely on resolution services and network addresses and routes forwarding entirely based on identifiers, but has poor compatibility with existing network devices and network architectures, and has problems with scalability and routing convergence efficiency due to the large number of identifier routing tables. The second type of method has good compatibility with existing network devices and network architectures, and its underlying mechanism is still address-based routing. However, it needs to rely on an external resolution mapping system, which affects the security and efficiency of the system in the routing process. Summary of the Invention [Problem to be solved by the invention]

[0006] In view of the problems in existing identifier routing algorithms, the present invention provides a hierarchical identifier addressing method, in which network domains are hierarchically organized based on management domains and control domains, a controller stores the mapping relationship between the identifiers and addresses of entities in the control domain, and the border routers of the management domain store the matching relationship between the identifiers of entities in the management domain and the control domain, and the association relationship between the identifiers and the associated border routers, thereby realizing hierarchical storage, and using a hierarchical analysis method within and between domains to realize dynamic analysis and addressing of identifiers in the message transmission process, thereby effectively solving the problems of scalability and query efficiency caused by the large number of identifier-address mapping tables. [Means for solving the problem]

[0007] To solve the above problem, the present invention provides a hierarchical identifier addressing method, in an architecture where identifiers and addresses are separated, each network entity in the network is uniquely identified by an identifier that is not related to a network address, the whole network is composed of multiple administrative domains, and the administrative domain may be divided into multiple control domains, and there is one controller in each control domain, and the network nodes that carry out identifier resolution and routing include, but are not limited to, edge routers of the control domains and border routers of the administrative domains. The controller stores the mapping relationship between the identifiers and addresses of entities in the control domains, and the administrative domain border routers store the matching relationship between the identifiers of entities in the administrative domains and the control domains, and the association relationship between the identifiers and the associated border routers, and the method includes: 1) receiving a request message including an identifier of a requesting network entity; The edge router of the control domain analyzes the identifier to obtain an address, and if the address obtained by analysis is the final destination address, the process ends. If not, the address obtained by analysis is the border router address of the administrative domain in which the network entity exists, so the process goes to step 3). Step 2). Step 3) in which a border router of the administrative domain matches the identifier of an entity in this administrative domain with a controller that stores a mapping relationship related to the identifier, and if a matching controller is found, the matching controller analyzes and addresses the identifier and returns to step 2), otherwise, executes step 4); Step 4) includes, but is not limited to, determining an intermediate border router corresponding to the identifier in the border router of the administrative domain, and obtaining the border router of the administrative domain associated with the identifier by an index in the intermediate border router, and performing step 3).

[0008] As an improvement of the above method, the network entities include, but are not limited to, hosts, data, and services, and the identifier generation methods include, but are not limited to, flat naming, hierarchical naming, and multi-semantic naming.

[0009] In an improvement to the above method, the controller (1) storing and maintaining a mapping relationship between identifiers and addresses of entities within the control domain; (2) Provides a function for registering and deleting mapping relationships between identifiers and addresses of entities within the control domain; (3) exchanging information with an administrative domain boundary router in the administrative domain to which it belongs in order to determine a matching relationship between the identifier and a controller; (4) Upon receiving a message sent from the router, check whether the destination address in the message is a valid address; (5) For messages where the destination address is an invalid address, an identifier analysis can be performed; (6) for messages in which the destination address is a valid address, the identifier can be reparsed based on a specific trigger mechanism; (7) analyzing all identifiers, and if the controller stores a mapping relationship associated with the identifiers, the address obtained by the analysis is the final destination address; otherwise, the address obtained by the analysis is a pre-configured destination address, including but not limited to a border router address and a default forwarding address; (8) This is to realize the function that the controller includes the address obtained by analysis in the outgoing flow table, and the router can write or update the destination address field in the message based on the outgoing flow table.

[0010] In an improvement of the above method, the entity in the control domain is a network entity having a unique identifier, including but not limited to a network device, a service, and data. If the entity is a network device, the device is first connected to the network by this control domain; if the entity is data, a service, etc., the network device where the entity resides is first connected to the network by this control domain, i.e., the first control domain through which a message sent by the device where the entity resides enters the network is called the control domain where the entity resides.

[0011] As an improvement to the above method, if the destination address field in the message is null or the filled in address is a predetermined address, the destination address in the message is an invalid address; otherwise, the destination address in the message is a valid address, and the predetermined address is an address selected from reserved addresses in the address space, which is a non-routable address and includes reserved addresses in the IP network.

[0012] As an improvement to the above method, the specific trigger mechanism can trigger a re-analysis and addressing of the identifier, including but not limited to the inclusion of a trigger flag bit in the message.

[0013] As an improvement to the above method, the edge router of the control domain refers to the first router through which a message is passed when transferring the message within the control domain, and is located on the periphery of the control domain, and the edge router of the control domain is: (1) When receiving a message that the destination address field is an invalid address, the edge router can report and forward the message to the controller to which it belongs and request the controller to originate and forward the flow table; (2) For messages in which the destination address field is an invalid address, the controller may write or update the destination address field in the message based on the flow table it originates, and the updated destination address may include, but is not limited to, the final destination address and the border router address of the corresponding administrative domain; (3) For a message whose destination address field is a valid address, the message can be reported and forwarded to the controller to which it belongs based on a specific trigger mechanism, and the controller can be requested to originate and forward the flow table; (4) for a message in which the destination address field is a valid address, the controller can update the destination address field in the message based on the flow table sent by the controller; (5) It is intended to realize the function of routing and forwarding based on the flow table sent by the controller.

[0014] As an improvement to the above method, the administrative domain boundary router refers to a device for transferring messages between administrative domains and is a type of boundary device, and the administrative domain boundary router is: (1) having one index that uniquely represents the border router; (2) storing and maintaining the mapping relationship between the index and address of all border routers; (3) storing and maintaining a matching relationship between the identifiers of entities in the management domain and the control domain; (4) using a predetermined method to map the identifier of a network entity to the index of one or more border routers, where these mapped border routers are called intermediate border routers for that entity identifier, and where the predetermined method includes, but is not limited to, table lookup and function mapping; (5) Requests an intermediate border router to register or delete the association between the identifier and the border router; (6) storing and maintaining an association between the identifier and an associated border router; (7) In response to a request to register or delete an identifier, a matching relationship between the identifier and the control domain can be added or deleted; (8) Adding or deleting an association between an identifier and a border router in response to a request to register or delete an identifier; (9) analyzing the identifier and updating a destination address field of the message based on the analysis result, where the addresses obtained by the analysis include, but are not limited to, a controller address, an edge router address, and a border router address; (10) If the received message is from a network device within the administrative domain to which it belongs, it first matches the identifier within the administrative domain with the control domain, and if the match is not successful, it performs mapping of an intermediate border router.

[0015] As an improvement to the above method, in the matching relationship between the identifier of an entity within the administrative domain and a control domain, the mapping relationship between the identifier and address of the network entity corresponding to the identifier is stored and maintained in the controller of the control domain, but the matching relationship between the identifier and the control domain is stored and maintained in the border router of the administrative domain to which the network entity belongs.

[0016] As an improvement of the above method, the association relationship between the identifier and the relevant border router refers to a mapping relationship between the entity identifier and the border router address that registers the relationship.

[0017] As an improvement to the above method, the method further comprises a step of registering an identifier, specifically: The entity registers a mapping relationship between an identifier and an address in a controller of a control domain to which the entity belongs; The controller stores a mapping relationship between the identifier and the address of the entity; extending (sending) the registration request to the border router of the administrative domain to which the entity belongs; The border router stores a matching relationship between the mapping relationship and the control domain; a border router mapping a network entity identifier to an index of an intermediate border router; extending the registration request to an intermediate border router to which the identifier is mapped; The intermediate border router stores an association relationship between the identifier and the associated border router.

[0018] As an improvement to the above method, step 2) specifically comprises: Step 201) When the destination address field in the received message is an invalid address or is related to a specific trigger mechanism, the edge router reports and forwards the message to the controller to which it belongs, and requests that the controller send and forward a flow table; After receiving the message, the controller analyzes the identifier (step 202); The controller transmits a flow table including the address information obtained by the analysis (step 203); The edge router writes or updates the message destination address field based on the originated flow table (step 204).

[0019] As an improvement to the above method, step 3) specifically comprises: A border router receives the message and matches the control domain within the administrative domain (step 301); If a matching control domain exists, the matching controller analyzes and addresses the identifiers and executes step 201), and if the match is not successful, the intermediate border routers between the management domains are mapped and addressed and executes step 4), step 302).

[0020] As an improvement to the above method, step 4) specifically comprises: Mapping identifiers to indices of intermediate border routers at a border router of an administrative domain, step 401); forwarding the message to an intermediate border router, step 402); In the intermediate border router, obtaining the border router associated with the identifier (step 403); and forwarding the message to the relevant border router to perform matching and addressing of control domains within this administrative domain to perform step 301).

[0021] As an improvement to the above method, the method further comprises a step of erasing the identifier, specifically: The entity deletes the mapping relationship between the identifier and the address from the controller of the control domain to which the entity belongs; The controller deletes the mapping relationship between the identifier and the address of the entity; extending the deletion request to a border router of the administrative domain to which the entity belongs; The border router deletes the matching relationship between the mapping relationship and the control domain; a border router mapping a network entity identifier to an index of an intermediate border router; extending the deletion request to the intermediate border router to which the identifier is mapped; The intermediate border router deletes the association relationship between the identifier and the associated border router. [Effects of the Invention]

[0022] The advantages of the present invention are as follows:

[0023] The method of the present invention hierarchizes network domains based on management domains and control domains, and the controller stores the mapping relationship between the identifiers and addresses of entities in the control domain. The border routers of the management domain store the matching relationship between the identifiers of entities in the management domain and the control domain, and the association relationship between the identifiers and the associated border routers, thereby realizing hierarchical storage. A hierarchical analysis method is used within and between domains to realize dynamic analysis and addressing of identifiers during message transmission, effectively solving the problems of scalability and query efficiency caused by the large number of identifier-address mapping tables. [Brief explanation of the drawings]

[0024] [Figure 1] FIG. 1 is a schematic diagram of the network structure. [Figure 2]FIG. 2 is a flowchart of registering an identifier according to the present invention. [Figure 3] FIG. 3 is a specific flowchart of registering an identifier according to the present invention. [Figure 4] FIG. 4 is a schematic diagram of a network process for registering a mapping relationship between EID1 and IP1 on the server side according to the present invention. [Figure 5] FIG. 5 is a flowchart of the process for deleting an identifier according to the present invention. [Figure 6] FIG. 6 is a specific flowchart of deleting an identifier according to the present invention. [Figure 7] FIG. 7 is a schematic diagram of a network process for deleting the mapping relationship between EID1 and IP1 on the server side according to the present invention. [Figure 8] FIG. 8 is a flowchart of the identifier parsing and routing according to the present invention. [Figure 9] FIG. 9 is a schematic diagram of a user 1 requesting a network analysis and routing process for identifier EID1. [Figure 10] FIG. 10 is a schematic diagram of a user 2 requesting a network analysis and routing process for identifier EID1. [Figure 11] FIG. 11 is a schematic diagram of a user 3 requesting a network analysis and routing process for identifier EID1. [Figure 12] FIG. 12 is a flowchart for registering an identifier according to the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0025] In order to make the objectives, technical solutions and advantages of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.

[0026] The identifier refers to a globally unique identifier that can represent a network entity and is not related to a network address, including, but not limited to, a data identifier. The network address refers to address information at which the network entity exists that can be routed through the network, including, but not limited to, information such as an IP address. In the described embodiment, the content identifier is represented by an EID (Entity ID) as an example, and the network address is represented by an IP address. A video content "Movie" is located on the server side, with an identifier EID1 and a server-side network address IP1. The server side publishes the video content by registering a mapping relationship between EID1 and IP1 on the network, and users obtain the video content using the identifier EID1. When the server side no longer provides the video content, it deletes the mapping relationship between EID1 and IP1 on the network.

[0027] In the described embodiment, all controllers in the network need to maintain a single EID-IP mapping table. Furthermore, for fast matching between identifiers and control domains, BGP routers maintain a Bloom filter for each controller in the autonomous domain to which they belong. Furthermore, to support the deletion function, this embodiment uses a counting Bloom filter. Based on the hash function and nearest neighbor distance principle, identifiers can be mapped to border router indices. Figure 1 is a schematic diagram of a network structure according to the present invention.

[0028] 2 and 3 are flowcharts for registering an identifier, and FIG. 4 is a schematic diagram of a network process for registering a mapping relationship between EID1 and IP1 on the server side.

[0029] The identifier registration process is Step S1101: the server side sends a registration request for the EID1-IP1 mapping relationship to the controller C1; Step S1102, in which the controller C1 inserts this mapping relationship into a local mapping table; Step S1103: the controller C1 extends the registration information to the border routers BGP1 and BGP2; Step S1104: the border routers BGP1 and BGP2 insert the EID1-IP1 mapping relationship into the storage space of the Bloom filter corresponding to the controller C1 held by each of them; Step S1105: mapping EID1 to an index of an intermediate border router by a hash function; Step S1106: Extend the registration information to the intermediate border router BGP4; Step S1107: inserting the association relationship between EID1 and BGP1 and BGP2 into the intermediate border router BGP4, and terminating the registration process.

[0030] 5 and 6 are flowcharts for deleting an identifier, and FIG. 7 is a schematic diagram of a network process for deleting the mapping relationship between EID1 and IP1 on the server side.

[0031] The identifier deletion process is Step S1201: the server side sends a request to delete the EID1-IP1 mapping relationship to the controller C1; Step S1202, in which the controller C1 deletes this mapping relationship from its local mapping table; Step S1203: the controller C1 extends the deletion information to the border routers BGP1 and BGP2; Step S1204: the border routers BGP1 and BGP2 delete the EID1-IP1 mapping relationship from the storage space of the Bloom filter corresponding to the controller C1 held by each of them; Step S1205: mapping EID1 to an index of an intermediate border router by a hash function; Step S1206: Extend the deletion information to the intermediate border router BGP4; Step S1207: in the intermediate border router BGP4, the association relationship between EID1 and BGP1 and BGP2 is deleted, and the deletion process is terminated.

[0032] Figure 8 is a flowchart of addressing based on an identifier. Figure 9 is a schematic diagram of an addressing process in which a network entity corresponding to an identifier EID1 is requested by a user 1.

[0033] The addressing process by which a network entity corresponding to identifier EID1 is requested by user 1 is Step S1301, when requested by User 1, includes a requested identifier EID1 in the message; After receiving the message, the edge router ER4 checks whether the destination address field is an invalid address. If it is an invalid address, it reports and forwards the message to the controller C1 and executes step S1402; if it is a valid address, it directly forwards the message according to the flow table, step S1401; After receiving the message, the controller C1 analyzes the identifier to obtain the address IP1, step S1402; Step S1403: the controller C1 includes the address IP1 obtained by the analysis in the outgoing flow table; Step S1404: Edge router ER4 updates the destination address field in the message to IP1, and ends the addressing process.

[0034] FIG. 10 is a schematic diagram of an addressing process in which a network entity corresponding to identifier EID1 is requested by user 2. The addressing process by which the network entity corresponding to the identifier EID1 is requested by user 2 is Step S1301, when requested by User 2, including the requested identifier EID1 in the message; After receiving the message, the edge router ER4 checks whether the destination address field is an invalid address. If it is an invalid address, it reports and forwards the message to the controller C2 and executes step S1402; if it is a valid address, it directly forwards the message according to the flow table, step S1401; Step S1402: After receiving the message, the controller C2 analyzes the identifier. Since the controller C2 does not find an entry related to EID1, the address of the border router BGP1 is set as the analyzed address. Step S1403: the controller C2 includes the BGP1 address obtained by the analysis in the outgoing flow table; Step S1404: the edge router ER2 updates the destination address field in the message to the address of BGP1 and forwards the message to the border router BGP1; Step S1501: in the border router BGP1, a fast query and matching of EID1 is performed on the Bloom filters corresponding to the controllers C1, C2, and C3, respectively, and an edge router ER5 of the control domain in which C1 is found to contain an identifier related to EID1 is selected; Step S1502: updating the destination address field in the message to the address of ER5 and forwarding the message to ER5; In the control domain where the controller C1 exists, the following steps S1401 to S1404 are executed again. Specifically, After receiving the message, the edge router ER5 checks whether the destination address field is an invalid address. If it is an invalid address, it reports and forwards the message to the controller C1 and executes step S1402; if it is a valid address, it directly forwards the message according to the flow table, step S1401; After receiving the message, the controller C1 analyzes the identifier to obtain the address IP1, step S1402; Step S1403: the controller C1 includes the address IP1 obtained by the analysis in the outgoing flow table; Edge router ER5 updates the destination address field in the message to IP1 and ends the addressing process, and step S1404 is executed again.

[0035] FIG. 11 is a schematic diagram of an addressing process in which a network entity corresponding to identifier EID1 is requested by user 3. The addressing process by which the network entity corresponding to the identifier EID1 is requested by user 3 is Step S1301, when requested by User 3, including the requested identifier EID1 in the message; After receiving the message, the edge router ER3 checks whether the destination address field is an invalid address. If it is an invalid address, it reports and forwards the message to the controller C4 and executes step S1402; if it is a valid address, it directly forwards the message according to the flow table, step S1401; Step S1402: After receiving the message, the controller C4 analyzes the identifier. Since the controller C4 does not find an entry related to EID1, the address of the border router BGP3 is set as the analyzed address. Step S1403: the controller C4 includes the BGP3 address obtained by the analysis in the outgoing flow table; Step S1404: the edge router ER3 updates the destination address field in the message to a BGP3 address and forwards the message to the border router BGP3; Step S1501: In the border router BGP3, a fast query and matching of EID1 is performed against the Bloom filter corresponding to the controller C4, and it is found that C4 does not contain an identifier related to EID1, and step S1601 is executed; Step S1601: in the border router BGP3, EID1 is mapped to an index of an intermediate border router by a hash function; Step S1602: updating the destination address field in the message to the address of the intermediate border router BGP4 corresponding to the index, and forwarding the message to the border router BGP4; In the intermediate border router BGP4, a fast query of EID1 is made to the Bloom filter corresponding to each border router to determine the associated border router as BGP1, step S1603; Step S1604, in which the relevant border router updates the destination address field in the message to the address of BGP1, and forwards the message to BGP1, thereby executing step (1501).

[0036] In the autonomous domain AS1, the following steps S1501 to S1502 are executed again. Specifically, Step S1501: in the border router BGP1, a fast query and matching of EID1 is performed on the Bloom filters corresponding to the controllers C1, C2, and C3, respectively, and it is found that C1 contains an identifier related to EID1, and an edge router ER5 of a control domain in which one C1 exists is selected; The destination address field in the message is updated to the address of ER5, and the message is forwarded to ER5, and step S1502 is executed again. In the control domain where the controller C1 exists, the following steps S1401 to S1404 are executed again. Specifically, After receiving the message, the edge router ER5 checks whether the destination address field is an invalid address. If it is an invalid address, it reports and forwards the message to the controller C1 and executes step S1402; if it is a valid address, it directly forwards the message according to the flow table, step S1401; After receiving the message, the controller C1 analyzes the identifier to obtain the address IP1, step S1402; Step S1403: the controller C1 includes the address IP1 obtained by the analysis in the outgoing flow table; Edge router ER5 updates the destination address field in the message to IP1 and ends the addressing process, and step S1404 is executed again.

[0037] A flowchart of identifier-based addressing according to the present invention is shown in Figure 12. Finally, it should be noted that the above embodiments are merely for illustrating the technical solution of the present invention, and are not intended to be limiting. Although the present invention has been described in detail with reference to the embodiments, it is understood by those skilled in the art that any modifications or equivalent substitutions made to the technical solution of the utility model of the present invention shall not depart from the spirit and scope of the technical solution of the present invention, and all of them should be included in the scope of the claims of the present invention.

[0038] Finally, it should be noted that the above examples are merely for illustrating the technical solutions of the present invention, and are not intended to be limiting. Although the present invention has been described in detail with reference to the examples, those skilled in the art will understand that any modifications or equivalent replacements made to the technical solutions of the present invention will not depart from the spirit and scope of the technical solutions of the present invention, and all of them should be included in the scope of the claims of the present invention.

Claims

1. A hierarchical identifier addressing method, comprising: In an architecture in which identifiers and addresses are separated, each network entity in the network is uniquely identified by an identifier not related to a network address, the entire network is composed of multiple administrative domains, the administrative domains include at least one control domain, each control domain has one controller, the network nodes carrying the identifier resolution and routing include edge routers of the control domain and border routers of the administrative domain, the controllers store mapping relationships between identifiers and addresses of entities in the control domain, and the administrative domain border routers store matching relationships between identifiers of entities in the administrative domain and control domains and association relationships between identifiers and associated border routers, Step 1) an edge router of a control domain receives a message sent from a sender, the message including a request destination network entity identifier (EID) in a message header; In the edge router of the control domain, the identifier is analyzed to obtain an address. If the address obtained by the analysis is the final destination address, the process is terminated. If not, the address obtained by the analysis is the border router address of the management domain in which the network entity exists, so the process goes to step 3). In step 2), specifically, Step 201) when an edge router receives a message and the destination address field is an invalid address or is related to a specific trigger mechanism, the edge router reports and forwards the message to the controller to which the edge router belongs, and requests the controller to send and forward a flow table; After receiving the message, the controller extracts an identifier from the message header and performs an identifier analysis (step 202); The controller transmits a flow table including the address information obtained by the analysis, step 203); Step 2) includes: the edge router writing or updating the message destination address field based on the originated flow table; and step 204). In a border router of the management domain, matching is performed between the identifier of an entity in the management domain and a controller in which a mapping relationship related to the identifier is stored, and if a matching controller is found, the matching controller performs analysis and addressing of the identifier and returns to step 2); otherwise, executes step 4); step 3), specifically, Step 301) after a border router receives a message, extracts an identifier from the message header, and matches and obtains a control domain corresponding to the identifier in the management domain; Step 3) includes: if a matching control domain exists, change the destination address of the message to the edge router address of the control domain and forward the message to the edge router, and execute step 201); if the matching is not successful, execute step 4); and step 302). Step 4) in an administrative domain border router, determining an intermediate border router corresponding to the identifier, and obtaining an administrative domain border router related to the identifier by an index in the intermediate border router to execute step 3), specifically comprising: Step 401), in a border router of an administrative domain, extracting an identifier from the message header and mapping the identifier to an index of an intermediate border router, the index being an identifier for uniquely identifying said intermediate border router; forwarding the message to an intermediate border router, step 402); The intermediate border router extracts the identifier from the message header and obtains the border router associated with the identifier, step 403); Step 4) includes forwarding the message to the relevant border router to perform matching and addressing of the control domain within this administrative domain to perform step 301); A hierarchical identifier addressing method comprising:

2. 2. The hierarchical identifier addressing method of claim 1, wherein the network entities include hosts, data and services, and the identifier generation methods include a flat naming method, a hierarchical naming method and a multi-semantic naming method.

3. The controller: (1) storing and maintaining a mapping relationship between identifiers and addresses of entities within a control domain; (2) providing a function for registering and deleting a mapping relationship between identifiers and addresses of entities in a control domain; (3) exchanging information with an administrative domain boundary router in the administrative domain to which it belongs in order to determine a matching relationship between the identifier and a controller; (4) upon receiving a message sent by a router, checking whether the destination address in the message is a valid address; (5) For messages where the destination address is an invalid address, an identifier analysis can be performed; (6) for messages in which the destination address is a valid address, re-analysis of the identifier can be performed based on a specific trigger mechanism; (7) Analyze all identifiers, and if the controller stores a mapping relationship associated with the identifier, the address obtained by the analysis is a final destination address; otherwise, the address obtained by the analysis is a pre-configured destination address, including a border router address and a default forwarding address; (8) The hierarchical identifier addressing method according to claim 1, characterized in that the method is for implementing the function that the controller includes the address obtained by analysis in the outgoing flow table, and the router can write or update the destination address field in the message based on the outgoing flow table.

4. The hierarchical identifier addressing method according to claim 3, characterized in that the entities in the control domain are network entities having unique identifiers, including network devices, services and data, and if the entity is a network device, the device is first connected to the network by this control domain, and if the entity is data or a service, etc., the network device in which the entity resides is first connected to the network by this control domain, i.e., the first control domain through which a message sent by the device in which the entity resides enters the network and passes is called the control domain in which the entity resides.

5. 4. The hierarchical identifier addressing method of claim 3, wherein if the destination address field in the message is null or the written address is a predetermined address, the destination address in the message is an invalid address, and otherwise the destination address in the message is a valid address, and the predetermined address is an address selected from reserved addresses in the address space, is a non-routing address, and includes reserved addresses in the IP network.

6. 4. The method of claim 3, wherein the specific trigger mechanism includes a trigger flag bit being included in a message that can trigger identifier re-analysis and addressing.

7. The edge router of the control domain refers to the first router through which a message passes when transferring the message within the control domain, and is located on the periphery of the control domain. The edge router of the control domain is: (1) upon receiving a message that the destination address field is an invalid address, the edge router may report and forward the message to the controller to which it belongs, and request the controller to originate and forward the flow table; (2) for a message in which the destination address field is an invalid address, the controller can write or update the destination address field in the message based on the flow table sent by the controller, and the updated destination address includes a final destination address and / or a border router address of the corresponding administrative domain; (3) for a message whose destination address field is a valid address, it can report and forward the message to the controller to which it belongs based on a specific trigger mechanism, and request the controller to send and forward the flow table; (4) for a message in which the destination address field is a valid address, the destination address field in the message can be updated based on the flow table sent by the controller; (5) A hierarchical structure identifier addressing method according to claim 5, characterized in that the method is for realizing a function of routing and transferring based on a flow table sent by a controller.

8. The administrative domain boundary router refers to a device for transferring messages between administrative domains, and is a type of boundary device. The administrative domain boundary router is: (1) having one index that uniquely represents the border router; (2) storing and maintaining a mapping relationship between the indexes and addresses of all border routers; (3) storing and maintaining a matching relationship between identifiers of entities in the management domain and control domains; (4) using a predefined method to map the identifier of a network entity to an index of one or more border routers, these border routers being called intermediate border routers for that entity identifier, the predefined method including a table lookup and a function mapping; (5) Requesting an intermediate border router to register or delete the association between the identifier and the border router; (6) storing and maintaining an association between the identifier and an associated border router; (7) A matching relationship between an identifier and a control domain can be added or deleted in response to a request to register or delete an identifier; (8) Adding or deleting an association between an identifier and a border router in response to a request to register or delete an identifier; (9) analyzing the identifier and updating a destination address field of the message based on the analysis result, where the addresses obtained by the analysis include a controller address, an edge router address, and a border router address; (10) The hierarchical identifier addressing method according to claim 7, characterized in that if a received message is from a network device within the management domain to which the message belongs, the method first matches the identifier within the management domain with the control domain, and if the matching is unsuccessful, performs mapping of an intermediate border router.

9. A hierarchical identifier addressing method as described in claim 5, characterized in that in the matching relationship between the identifier of an entity in the management domain and a control domain, a mapping relationship between the identifier and address of a network entity corresponding to the identifier is stored and maintained in a controller of the control domain, while the matching relationship between the identifier and the control domain is stored and maintained in a border router of the management domain to which the network entity belongs.

10. The method for addressing identifiers with a hierarchical structure according to claim 8, characterized in that the association relationship between the identifier and the relevant border router refers to a mapping relationship between an entity identifier and a border router address that registers the relationship.

11. The method further includes a step of registering an identifier, specifically, The entity registers a mapping relationship between the identifier and the address in a controller of a corresponding control domain; The controller stores a mapping relationship between the identifier and the address of the entity; extending the registration request to a border router of the administrative domain to which the entity belongs; The border router stores a matching relationship between the mapping relationship and the control domain; a border router mapping a network entity identifier to an intermediate border router index; extending the registration request to an intermediate border router to which the identifier is mapped; 2. The method of claim 1, further comprising: an intermediate border router storing an association relationship between the identifier and an associated border router.

12. The method further includes a step of deleting the identifier, specifically, The entity deletes a mapping relationship between an identifier and an address from a controller of a control domain to which the entity belongs; and The controller deletes a mapping relationship between the identifier and the address of the entity; extending the deletion request to a border router of the administrative domain to which the entity belongs; the border router deletes the matching relationship between the mapping relationship and the control domain; a border router mapping a network entity's identifier to an intermediate border router's index; extending the deletion request to an intermediate border router to which the identifier is mapped; 12. The method of claim 11, further comprising: an intermediate border router deleting the association relationship between the identifier and the relevant border router.

Images