[go: up one dir, main page]

WO2011029343A1 - 身份位置分离网络的名址映射系统及数据传输方法 - Google Patents

身份位置分离网络的名址映射系统及数据传输方法 Download PDF

Info

Publication number
WO2011029343A1
WO2011029343A1 PCT/CN2010/074941 CN2010074941W WO2011029343A1 WO 2011029343 A1 WO2011029343 A1 WO 2011029343A1 CN 2010074941 W CN2010074941 W CN 2010074941W WO 2011029343 A1 WO2011029343 A1 WO 2011029343A1
Authority
WO
WIPO (PCT)
Prior art keywords
mapping
domain
destination
node
plane
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.)
Ceased
Application number
PCT/CN2010/074941
Other languages
English (en)
French (fr)
Inventor
汪军
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Publication of WO2011029343A1 publication Critical patent/WO2011029343A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/54—Store-and-forward switching systems 
    • H04L12/56—Packet switching systems
    • 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
    • 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/02—Topology update or discovery
    • H04L45/04—Interdomain routing, e.g. hierarchical routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping

Definitions

  • the present invention relates to an identity location separation technique, and more particularly to a name mapping system and a data transmission method for an identity location separation network.
  • the Internet Engineering Task Force has proposed a technology of identity and location separation in recent years, separating identity locations.
  • the LISP protocol proposed by the Locator and Identifier Separation Protocol (LISP) is used as an example.
  • the Endpoint IDentifier (EID) of the terminal does not participate in the routing of the IP core network.
  • the backbone router can only see the interface of the border access router.
  • a routing address (Routing LOCator, RLOC) and a border router can access a large number of terminals, and separately set a mapping plane to store the correspondence between the terminal identity EID and the router RLOC.
  • the packet destined for the terminal first needs to find its corresponding border router RLOC in the mapping plane, and then routes to the access router where the destination terminal is located according to the RLOC.
  • the schematic diagram is shown in Figure 1.
  • the ITR (Ingress Tunnel Router) and the ETR (Egress Tunnel Router) represent the ingress tunnel router and the egress tunnel router.
  • LISP can greatly reduce the routing table capacity of the IP backbone router, but it leaves the complexity in the mapping plane.
  • the mapping plane stores all the EID-RLOC correspondences.
  • ALT is the abbreviation of Alternative Topology.
  • the mapping plane can use the normal IP hop-by-hop routing method to finally route to the destination access.
  • the router but in the mobile network, this assumption does not hold, so it is not suitable for solving the identity location separation network problem of mobile terminal access. Luo Hongbin of Beijing Jiaotong University and others published "A DHT-based Identifier-to-locator Mapping Approach for a Scalable Internet" on the IEEE website.
  • a DHT-based identity location mapping method for scalable Internet proposes a Distributed Addressing Network (CAN) distributed hash table.
  • DHT Distributed Addressing Network
  • the problem to be solved by the present invention is to provide a name mapping system and a data transmission method for an identity location separation network to improve routing efficiency.
  • the present invention provides a name mapping system for an identity location separation network, the system comprising a domain mapping server and one or more domain mapping planes connected to the domain mapping server, where:
  • the domain mapping plane is configured to: save the local domain routing table and the local mapping table, and receive the packet sent by the access service node or other domain mapping plane, where the packet carries the destination identity identifier;
  • the routing table determines that the destination identity does not belong to the domain mapping plane, and sends a domain query request to the domain mapping server; receiving the destination domain mapping plane information returned by the domain mapping server, and sending a packet to the destination domain mapping plane; And sending, according to the destination route identifier corresponding to the destination identifier in the local mapping table, a packet to the destination access service node corresponding to the destination route identifier;
  • the domain mapping server is configured to: save an identity identifier and a mapping plane relationship table, receive a domain query request of the domain mapping plane, the query request includes a destination identity identifier; and query the identity identifier and the mapping plane according to the domain query request
  • the relational table acquires the target domain mapping plane information and returns to the domain mapping plane.
  • the domain mapping plane is composed of at least one mapping node, and the mapping node includes a transceiver module, a local routing table module, a node determining module, an inter-domain routing module, a local mapping table module, and an address query module.
  • the transceiver module is configured to: receive a message sent by the access service node or another mapping node, and send a message to the access service node or another mapping node;
  • the local routing table module is configured to: save the local routing table, where the local routing table includes a correspondence between the local identity identifier and the local mapping node;
  • the node determining module is connected to the transceiver module and the local routing table module, and is configured to: query the local routing table, determine whether the destination identity belongs to the domain, and determine the destination identity in the domain Corresponding mapping node, the destination identity identifier does not belong to the local domain, and the inter-domain routing module is notified; when the determined mapping node is another mapping node in the local domain, the notification transceiver module forwards the packet to the determined mapping node; Notifying the address query module when the mapping node is the current mapping node;
  • the inter-domain routing module is configured to: send a domain query request to the domain mapping server, where the destination identity identifier is carried; receive the destination domain mapping plane information sent by the domain mapping server, and notify the transceiver module to Decoding the destination mapping plane to forward the packet;
  • the local mapping table module is configured to: save a local mapping table, where the local mapping table includes a mapping relationship between the local identity identifier and the routing identifier;
  • the address querying module is connected to the local mapping table module, and is configured to: query the local mapping table according to the destination identity to obtain a destination routing identifier, and notify the sending and receiving module to access the destination routing identifier.
  • the service node sends a message.
  • the system further includes an access service node that is connected to the domain mapping plane of the domain in which the domain is located.
  • the address query module is further configured to: after obtaining the destination route identifier, notify the transceiver module to send the access service node corresponding to the source route identifier Mapping relationship between the destination identity identifier and the destination route identifier;
  • the transceiver module is further configured to: send the mapping relationship to an access service node corresponding to the source routing identifier;
  • the access service node is further configured to: cache the mapping relationship, and after receiving the packet sent by the terminal, query the mapping relationship of the cache first, and then forward the packet to the domain when the corresponding mapping relationship is not found.
  • the mapping node of the mapping plane is further configured to: cache the mapping relationship, and after receiving the packet sent by the terminal, query the mapping relationship of the cache first, and then forward the packet to the domain when the corresponding mapping relationship is not found.
  • the destination area mapping plane information is a mapping node address list of the destination domain mapping plane; the inter-domain routing module is configured to notify the transceiver module to forward the packet to the destination domain mapping plane in the following manner: according to the mapping
  • the node address list selects one or more mapping nodes of the destination domain mapping plane, and notifies the transceiver module to forward the packet to the selected mapping node.
  • the access service node is a mapping node that is configured to forward the packet to the mapping plane of the domain in the following manner: Configure at least one mapping node of the domain, and when multiple mapping nodes are configured, use round robin or random
  • the selected mode selects a mapping node from the configured mapping nodes, and sends a message to the selected mapping node.
  • the mapping node further includes an identity maintenance module that is connected to the local mapping table module.
  • the transceiver module is further configured to: receive a registration or deregistration request sent by the access service node, where the identity identifier to be registered or deregistered is carried a mapping relationship between the routing identifiers; the node determining module is further configured to: query the local routing table according to the registration or deregistration request of the access service node to determine a corresponding mapping node, and if the determined mapping node is a current mapping node, Then, the identity identifier maintenance module is notified; the identity identifier maintenance module is configured to: register or deregister a mapping relationship between the corresponding identity identifier and the route identifier in the local mapping table.
  • the present invention also provides an identity location separation network data transmission method, which is implemented based on a name mapping system, the system includes a domain mapping server, and one or more domains connected to the domain mapping server. a mapping plane, and an access service node connected to the domain mapping plane of the domain, the method includes: the packet carrying the destination identity identifier;
  • the source domain mapping plane determines whether the destination identity identifier belongs to the local domain, and if yes, performs step E, and if not, sends a domain query request to the domain mapping server, where the destination identity identifier of the packet is carried;
  • the domain mapping server queries the correspondence between the identity identifier and the domain mapping plane, and returns the destination domain mapping plane information to the source domain mapping plane.
  • the source domain mapping plane forwards the packet to the destination domain mapping plane according to the destination domain mapping plane information
  • the destination area mapping plane searches for the identity of the identity identifier and the route identifier, obtains the destination route identifier, and sends the packet to the destination access service node corresponding to the destination route identifier.
  • the domain mapping plane includes at least one mapping node
  • the step E includes: after the mapping node of the destination domain mapping plane receives the packet and determines that the destination terminal is the domain terminal, first queries the local routing table. Determining the destination mapping node where the destination route identifier is located, and if it is the current mapping node, querying the mapping between the local identity identifier and the route identifier, obtaining the destination route identifier, and sending the packet to the destination access service node, otherwise The message is forwarded to the determined mapping node.
  • the method further includes: after obtaining the destination route identifier, the destination mapping node of the destination area mapping plane sends the mapping relationship between the destination identity identifier and the destination route identifier to the source access service node; the source access service node The mapping relationship is saved in a local mapping table;
  • the method further includes: after receiving the packet sent by the terminal, the source access service node first queries the local mapping table according to the destination identity, and if the destination route identifier is found, directly The packet is forwarded to the corresponding destination access service node. If the destination route identifier is not found, go to step A.
  • the target domain mapping plane information in step C is a mapping node address list of the destination domain mapping plane.
  • Step D includes: the mapping node of the source domain mapping plane selects one of the destination domain mapping planes according to the mapping node address list. A plurality of mapping nodes to which the 4 transcripts are forwarded.
  • the system and method of the present invention by dividing the domain mapping plane and adding the domain mapping server, can implement the relationship query of the cross-domain identity to the domain mapping plane through the domain mapping server, obtain the entry address of the mapping plane of the destination domain, and then cross-domain The message is delivered to the destination domain mapping plane to finally complete the communication.
  • a single-hop DHT (Distributed Hash Table) technology is used in the domain mapping plane to construct a high-performance distributed database storage name (ie, identity) address (ie, route identification) mapping relationship, thereby realizing a hop in the domain mapping plane.
  • the fast query of the mapping relationship is completed, and the routing efficiency is improved.
  • the domain mapping plane is divided according to the carrier, that is, each carrier forms an independent mapping plane, and a unified domain mapping server is set, thereby providing a high network suitable for multiple operators.
  • Performance identity location mapping plane BRIEF abstract
  • FIG. 1 is a schematic structural diagram of an existing identity location separation network
  • FIG. 2 is a system block diagram of an identity location separation network according to the present invention.
  • 3 is a flowchart of a mapping relationship registration of an application example of the present invention
  • 4 is a flowchart of implementing IP communication in a domain mapping plane of an application example 2 of the present invention
  • FIG. 5 is a flowchart of implementing IP communication by using the three-span mapping plane of the application example of the present invention.
  • the main idea of the system and method of the present invention is to divide the domain mapping plane and add a domain mapping server, so that the domain mapping server can implement the relationship query of the cross-domain identity to the domain mapping plane, and obtain the entry address of the mapping plane of the destination domain, and then The cross-domain message is delivered to the destination domain mapping plane to finally complete the communication.
  • a single-hop DHT (Distributed Hash Table) technology is used in the domain mapping plane to construct a high-performance distributed database storage name (ie, identity) address (ie, route identification) mapping relationship, thereby realizing a hop in the domain mapping plane.
  • the fast query of the mapping relationship is completed, and the routing efficiency is improved.
  • the system includes an ASN (Access Service Node) 101, an operator IP core network 102, a domain mapping plane 103, and a domain mapping server 105, where the domain mapping The plane is composed of at least one mapping node 104.
  • ASN Access Service Node
  • An ASN can access multiple terminals, each terminal has a specific identity, and the terminal communicates with other terminals through the ASN.
  • the function of the ASN includes: a mapping relationship sent by the cache mapping plane, and receiving a packet sent by the terminal. Then, the mapping relationship of the cache is first queried. If the corresponding mapping relationship is not found, the packet is forwarded to the mapping node of the mapping plane of the domain.
  • Each ASN is configured with at least one mapping node of the domain, and if the access service node is configured with multiple mapping nodes, the access service node selects a mapping node from the configured mapping nodes by using round robin or random selection. And send a message to the selected mapping node.
  • the domain mapping plane, the local domain routing table, and the local mapping table are configured to: receive a packet sent by the access service node or another domain mapping plane, where the packet carries the destination identity identifier; And is further configured to send, according to the local routing table, the domain identity query to the domain mapping server when the destination identity does not belong to the domain mapping plane, and is further configured to receive the destination domain returned by the domain mapping server. Mapping the plane information, sending a message to the destination area mapping plane; and sending a packet to the destination access service node corresponding to the destination route identifier according to the destination route identifier corresponding to the identity identifier of the local mapping table;
  • the domain mapping plane can be divided according to the geographical location or the operator. In Figure 2, the operator maps the domain mapping plane.
  • Each carrier's mapping plane uses a single-hop DHT structure to store only the carrier (ie, this Domain) responsible mapping between the terminal identity and the route identifier. There is no need to exchange data between the mapping planes of different carriers.
  • the inter-operator communication needs to query the domain mapping server to obtain the carrier domain corresponding to the destination identity and its interworking.
  • the mapping plane maps the node list, making interoperability between operators simpler.
  • the local routing table is generated and queried by using the DHT algorithm.
  • the local routing table stores the correspondence between the segmentation of the identity hash value and the mapping node in the domain mapping plane.
  • the reason for using the DHT algorithm is Because the original identity is assigned by the operator segment by segment, it is unevenly distributed in the whole space, so it is not easy to distribute the data to the mapping plane mapping node evenly. This problem can be solved by using the DHT algorithm.
  • the current hash algorithm generally uses MD5 or SHA1, and the hash output is 128bit or 160bit.
  • the following simplified simplification uses 16bit or 0 65535 hash value to interpret the single-hop DHT algorithm: If the identity hash value is 16bit The mapping node of the domain mapping plane is also assigned a 16-bit logical node ID. Generally speaking, the number of nodes in the system is much smaller than the number of identity data entries. If a node stores 100 identity data, there are 10,000 in the system. For identity data, the node only needs 100. The mapping node where the identity data is located is determined by the relationship between the hash value of the identity identifier and the node ID.
  • the identity identifier is stored in the node ID greater than or equal to the identity hash value and most recently On the mapping node, for example, there are 4 mapping nodes in the domain mapping plane, and the node IDs are 0, 10000, 30000, 40000 respectively. If the hash values of the given identity are 3000 and 16000 respectively, the data should be stored separately. On the mapping node with node IDs 10000 and 30000.
  • the local routing table of each mapping node stores the ID information of all mapping nodes in the local domain, so it is determined whether the data is stored in the local domain according to the hash value of the destination identity identifier. And the mapping node stored in this domain.
  • the storage relationship is selected according to the method in which the absolute value of the difference between the identity hash value and the node ID is the smallest.
  • the mapping plane is constructed by DHT single-hop technology.
  • the intra-domain addressing only needs one hop, and the performance is greatly improved compared with the CAN algorithm.
  • the storage location of the correspondence between the identity identifier and the route identifier in the DHT algorithm is determined according to the DHT algorithm, and is independent of The topology of the underlying IP network does not need to limit the user's EID It can only be fixed to a certain ASN access, so it can well support the mobility of the terminal.
  • the domain mapping server stores an identity identification and mapping plane relationship table.
  • the domain mapping server includes: a domain query request for receiving a domain mapping plane, where the query request includes a destination identity identifier;
  • the domain query request query identity and the mapping plane relationship table obtain the destination domain mapping plane information and return to the domain mapping plane.
  • the data transmission process implemented by the above system based on the above system includes the following steps: the message carries the destination identity identifier;
  • Each ASN is configured with at least one mapping node of the domain, and if the access service node is configured with multiple mapping nodes, the access service node selects a mapping node from the configured mapping node by using a round robin manner, and selects The mapping node sends a message.
  • the source domain mapping plane determines whether the destination identity identifier belongs to the local domain, and if yes, performs step E, otherwise sends a domain query request to the domain mapping server, where the destination identity of the packet is carried;
  • the domain mapping server queries the correspondence between the identity identifier and the domain mapping plane, and returns the destination domain mapping plane information to the source domain mapping plane.
  • the source domain mapping plane forwards the packet to the destination domain mapping plane according to the destination domain mapping plane information.
  • the destination domain mapping plane information is a mapping node address list of the destination domain mapping plane.
  • the mapping node of the source domain mapping plane selects one or more mapping nodes of the destination mapping plane according to the mapping node address list, and forwards the packet to the mapping node.
  • the destination domain mapping plane searches the identity identifier and the route identifier mapping relationship, obtains the destination route identifier, and sends the packet to the destination access service node.
  • the mapping node of the destination mapping plane receives the packet and determines that the destination terminal is the domain terminal, first queries the local routing table, and determines the destination mapping node where the destination routing identifier is located. The node then queries the local identity and the route identifier to obtain the destination route identifier, and sends the packet to the destination access service node. Otherwise, the packet is forwarded to the determined mapping node.
  • step E after the destination mapping node of the destination mapping plane obtains the destination route identifier, Transmitting the mapping relationship between the destination identity identifier and the destination route identifier to the source access service node; the source access service node saves the mapping relationship in a local mapping table; before step A, the source access service node receives After the packet is sent to the terminal, the local mapping table is queried according to the destination identity. If the destination route identifier is found, the packet is directly forwarded to the corresponding destination access service node. Destination route ID, and then go to step A.
  • FIG. 3 shows the process of registering with the domain mapping plane when the UE is attached to the network, including the following steps: Step 301: The UE registers with the ASN, and the registration process uses an existing process; for example, the ASN is a 3GPP network access gateway. Then it uses the 3GPP packet domain user attachment process;
  • Step 302 When the ASN processes the UE network attach request, the ASN initiates a registration request Map_Register to the mapping plane, where the request carries the identity identifier of the UE and its own route identifier.
  • each ASN can configure mapping node addresses of multiple mapping planes, which can be used to issue requests to multiple mapping nodes in a round-robin manner to achieve load balancing.
  • Step 303 The mapping node 1 queries the local routing table () according to the identity identifier of the UE, and learns that the identity identifier should be stored on the mapping node 2, so it sends a DHT storage request to the mapping node 2, requesting to store the identity identifier of the UE. Correspondence relationship between route identifiers of ASNs;
  • the local routing table actually stores information about all mapping nodes of the local mapping plane.
  • the node ID length is assumed to be 16 bits (typically 128 bits or more in the actual network), as follows:
  • 0x8200 node ID Is the minimum node ID greater than or equal to the value, so the identity data is stored on the mapping node corresponding to the 0x8200 node ID.
  • Step 304 After receiving the mapping relationship storage request, the mapping node 2 locally stores the correspondence between the identity identifier of the UE and the route identifier of the ASN.
  • mapping node 2 it is possible for the mapping node 2 to back up the data to one or more other nodes according to the backup policy of the DHT algorithm.
  • Step 305 The mapping node 2 returns a DHT storage response message to the mapping node 1.
  • Step 206 The mapping node 1 returns a Map_Register response message to the ASN, which is completed in this embodiment.
  • FIG. 4 shows an embodiment of implementing IP communication in a domain mapping plane, including the following steps: Step 401: UE11 sends an IP packet whose destination address is the identity identifier EID21 of the UE 21; Step 402, ASN1 receives the packet. After the EID21 record is not found in the local identity-route ID mapping cache table, the packet is encapsulated and sent to the mapping node 1 of the mapping plane, and the encapsulated outer address is the IP address of the mapping node 1;
  • a static configuration mode may be adopted, for example, multiple mapping nodes are configured on the ASN, and the ASN selects between multiple mapping nodes for each request sent to the mapping plane by using a load balancing method such as round robin. ;
  • Step 403 After receiving the packet, the mapping node 1 determines that the EID21 is the domain user according to the local routing table, and then searches the local routing table with the EID21 as a key, and learns that the data is stored in the mapping node 2;
  • Step 404 the mapping node 1 forwards the packet to the mapping node 2 according to the query result
  • Step 405 The mapping node 2 reads the local mapping table to learn the RLOC21 corresponding to the EID21 (the routing identifier of the ASN2), and changes the external encapsulation target address of the received IP document to RLOC21.
  • Steps 406-407 the mapping node 2 notifies the ASN1 of the corresponding relationship of the EID21-RLOC21, and the ASN1 stores it in its own local cache, so that the subsequent IP packets sent to the EID21 can be directly local. Matching to the record, no need to forward through the mapping plane;
  • Step 408 the mapping node 2 sends the changed packet address to the ASN2 corresponding to the RLOC21;
  • Step 406 and step 408 are in no particular order.
  • Step 409 After receiving the packet, the ASN2 removes the external encapsulation header, and sends the packet to the UE21 to complete the end-to-end delivery.
  • Step 410 The UE11 sends a certificate whose destination address is EID21.
  • Step 411 After receiving the packet, the ASN1 obtains the route identifier RLOC21 corresponding to the EID21 in the local cache query, and encapsulates the packet, the encapsulation target address is RLOC21, and the source address is the RLOC11 of the ASN;
  • Step 412 The ASN1 sends the packet encapsulated in the previous step to the ASN2 directly, and does not need to go through the mapping plane.
  • Step 413 After receiving the packet sent by the ASN1, the ASN2 removes the external encapsulation header and forwards the packet to the UE21.
  • FIG. 5 illustrates a process for implementing IP communication across a carrier domain mapping plane through a domain mapping server, including the following steps:
  • Step 501 The UE11 sends an IP packet whose destination address is the terminal identifier EID21 of the UE21.
  • the ASN1 does not find the record of the EID21 in the local identity-route identifier mapping cache table.
  • the packet is encapsulated and sent to the mapping node 11 of the mapping plane of the domain (operator A), and the outer address of the encapsulated packet is the IP address of the mapping node 11;
  • a static configuration mode may be adopted, for example, multiple mapping nodes are configured on the ASN, and the ASN selects between multiple mapping nodes for each request sent to the mapping plane by using a load balancing method such as round robin. .
  • Step 503 After receiving the packet, the mapping node 11 determines that the EID21 is a domain user according to the local routing table, and then uses the EID21 as a key to search for a domain query request to the domain mapping server.
  • Step 504 The domain mapping server queries the identity identifier and the domain mapping plane correspondence table to return to the mapping node 11 the mapping plane mapping node address list of the operator B corresponding to the EID 21; in the present invention, the domain mapping server does not need to store the specificity of each identity identifier. The information only needs to store the identity segment information, that is, the correspondence between the storage identity segment and the domain mapping plane entry address list.
  • Step 505 The mapping node 11 selects a mapping node 21 according to the mapping node address list returned in the previous step, and forwards the initial IP address to the mapping node 21;
  • Step 506 after receiving the message, the mapping node 21 of the operator B determines that the target identity identifier EID21 is the domain user, queries the local domain routing table, and knows that the data is stored in the mapping node 22;
  • Step 507 the mapping node 21 forwards the packet to the mapping node 22 according to the result of the previous query
  • Step 508 The mapping node 22 reads the local EID-RLOC mapping table to learn the RLOC21 corresponding to the EID21 (the routing identifier of the ASN2), and changes the external encapsulation target address of the received IP address to RLOC21.
  • Steps 509-510 the mapping node 22 notifies the ASN1 of the corresponding relationship of the EID21-RLOC21, and the ASN1 stores it in its own local cache, so that the subsequent IP packets sent to the EID21 can be directly matched to the record locally, without further Forwarding through the mapping plane;
  • Step 511 the mapping node 22 sends the changed packet address to the ASN2 corresponding to the RLOC 21;
  • Step 509 and step 511 are in no particular order.
  • Step 512 After receiving the packet, the ASN2 removes the external encapsulation header, and sends the packet to the UE21 to complete the end-to-end delivery.
  • Step 513 The UE11 sends a certificate with the destination address being EID21.
  • Step 514 After receiving the packet, the ASN1 obtains the route identifier RLOC21 corresponding to the EID21 in the local cache query, and encapsulates the packet, the encapsulation target address is RLOC21, and the source address is the RLOC11 of the ASN;
  • Step 515 The ASN1 sends the packet encapsulated in the previous step to the ASN2 directly, and does not need to go through the mapping plane.
  • Step 516 After receiving the packet sent by ASN1, ASN2 removes the external encapsulation header and reports The file is forwarded to the UE21.
  • mapping node in the domain mapping plane:
  • Each mapping node of the domain mapping plane includes:
  • a transceiver module configured to receive a packet sent by the access service node or another mapping node, and send a packet to the access service node or another mapping node; And sending the mapping relationship; receiving the registration or deregistration request sent by the access service node, where the mapping between the identity identifier and the route identifier to be registered or deregistered is carried; the local routing table module is configured to save the domain The routing table, the local routing table includes the correspondence between the local identity identifier and the local mapping node;
  • the DHT route maintenance module is configured to collect the mapping node information in the mapping plane of the local domain, generate the local routing table, process the joining and exiting events of the node, and ensure the accuracy of the routing table.
  • a node determining module configured to be connected to the transceiver module and the local routing table module, configured to query the local routing table, determine whether the destination identity belongs to the local domain, and determine the mapping node corresponding to the destination identity in the domain, When the destination identity identifier does not belong to the local domain, the inter-domain routing module is notified; when the determined mapping node is another mapping node in the local domain, the notification transceiver module forwards the packet to the determined mapping node; when the determined mapping node is the current mapping node And notifying the address query module; and further configured to query the local domain routing table to determine a corresponding mapping node according to the registration or deregistration request of the access service node, and if the determined mapping node is a current mapping node, notify the Identity maintenance module,
  • An inter-domain routing module configured to send a domain query request to the domain mapping server, where the destination identity identifier is carried, and the destination domain mapping plane information sent by the domain mapping server is received, and the transceiver module is notified to
  • the destination domain mapping plane forwards the packet; specifically, the destination domain mapping plane information is a mapping node address list of the destination domain mapping plane; and the inter-domain routing module selects the destination domain mapping plane according to the mapping node address list.
  • the one or more mapping nodes notify the transceiver module to forward the message to the mapping node of the selected destination domain mapping plane.
  • a local mapping table module for saving a local mapping table, the local mapping table including a local identity identifier Mapping relationship with route identifiers;
  • An address querying module configured to connect to the local mapping table module, to query the local mapping table according to the destination identity to obtain a destination routing identifier, and to notify the sending and receiving module to access the destination routing identifier
  • the service node sends a message; the address query module obtains the destination route identifier, and is further configured to notify the transceiver module to send a mapping relationship between the destination identity identifier and the destination route identifier to the access service node corresponding to the source route identifier.
  • the identity maintenance module is connected to the local mapping table module, and is configured to register or unregister the mapping between the corresponding identity and the route identifier in the local mapping table.
  • the system and method of the present invention by dividing the domain mapping plane and adding the domain mapping server, can implement the relationship query of the cross-domain identity to the domain mapping plane through the domain mapping server, obtain the entry address of the mapping plane of the destination domain, and then cross-domain The message is delivered to the destination domain mapping plane to finally complete the communication.
  • a single-hop DHT (Distributed Hash Table) technology is used in the domain mapping plane to construct a high-performance distributed database storage name (ie, identity) address (ie, route identification) mapping relationship, thereby realizing a hop in the domain mapping plane.
  • the fast query of the mapping relationship is completed, and the routing efficiency is improved.
  • the domain mapping plane is divided according to the carrier, that is, each carrier forms an independent mapping plane, and a unified domain mapping server is set, thereby providing a high network suitable for multiple operators. Performance identity location mapping plane.
  • the access service node ASN responsible for the terminal access is responsible for replacing the terminal's address/address binding relationship with the distributed database.
  • the ASN receives the destination address of the packet sent by the terminal (ie, the destination terminal). When there is no record in the local cache, it sends the message to the domain mapping plane for forwarding.
  • the domain mapping plane routes the message to the destination terminal through the address mapping relationship of the destination terminal it stores; when the ASN is locally cached The mapping between the identity of the destination terminal and the destination route identifier is recorded.
  • the ASN forwards the packet directly to the destination ASN without forwarding through the domain mapping plane.
  • the system and method of the present invention by dividing the domain mapping plane and adding the domain mapping server, can implement the relationship query of the cross-domain identity to the domain mapping plane through the domain mapping server, obtain the entry address of the mapping plane of the destination domain, and then cross-domain The message is delivered to the destination domain mapping plane to finally complete the communication.
  • the single-hop DHT technology is used to construct a high-performance distributed database storage name (ie, identity) address (ie, route identification) mapping relationship, so that a fast query of the one-hop completion mapping relationship in the domain mapping plane can be implemented. Improve routing efficiency.
  • the domain mapping plane is divided according to the carrier, that is, each carrier forms an independent mapping plane, and a unified domain mapping server is set, thereby providing a high network suitable for multiple operators. Performance identity location mapping plane.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明系统和方法，通过划分域映射平面及增设域映射服务器，从而可通过域映射服务器实现跨域的身份标识到域映射平面的关系查询，获得目的域映射平面的入口地址，再将跨域报文递交给目的域映射平面最终完成通信。在域映射平面内采用单跳DHT技术构建高性能的分布式数据库存储名(即身份标识)址(即路由标识)映射关系，从而可以实现域映射平面内一跳完成映射关系的快速查询，提高了路由效率。当多个运营商域组网时，根据运营商划分域映射平面，即，每个运营商组成独立的映射平面，并设置统一的域映射服务器，从而可提供适用于多运营商组网的高性能身份位置映射平面。

Description

身份位置分离网络的名址映射系统及数据传输方法
技术领域
本发明涉及身份位置分离技术， 尤其是一种身份位置分离网络的名址映 射系统及数据传输方法。
背景技术
为了解决互联网核心路由器路由表容量快速膨胀以及互联网协议 ( IP ) 地址二义性的问题， 互联网工程任务组 (Internet Engineering Task Force , IETF) 近年来提出了身份与位置分离的技术， 以身份位置分离协议 (Locator and Identifier Separation Protocol, LISP)工作组提出的 LISP协议为例，其终端的身 份标识（ Endpoint IDentifier, EID)不参与 IP核心网的路由，骨干路由器只能看 到边界接入路由器的接口路由地址 (Routing LOCator, RLOC), 而一个边界路 由器可以接入大量的终端， 单独设置一个映射平面存储终端身份 EID和路由 器 RLOC的对应关系。 发往终端的报文首先需要在映射平面中查找到其对应 的边界路由器 RLOC, 然后根据 RLOC路由到目的终端所在接入路由器。 其 示意图见图 1 , 其中 ITR(Ingress Tunnel Router)、 ETR(Egress Tunnel Router)分 别表示入口隧道路由器、 出口隧道路由器， 是收发两端接入路由器的逻辑名 称。
LISP可以大大缩减 IP骨干网路由器的路由表容量，但是其将复杂性留在 了映射平面， 映射平面所要存储所有的 EID-RLOC的对应关系， 在 IETF的 LISP+ALT(ALT是 Alternative Topology的缩写， 表示一种可选拓朴方案)方案 中其假定终端是不可移动的， 每个终端固定属于某个接入路由器， 因此在映 射平面可以釆用普通 IP逐跳路由方式最终路由到目的接入路由器，但在移动 网中这一假设并不成立， 因此其不适合解决移动终端接入的身份位置分离网 络问题。 北京交通大学罗洪斌 (音译)等在 IEEE 网站上公开 "A DHT-based Identifier-to-locator Mapping Approach for a Scalable Internet" (译文： 一种用于 可扩展互联网的基于 DHT技术的身份位置映射方法)的文章提出了一种釆用 内容寻址网络 (Content Addressable Network , CAN) 分布式哈希表 ( Distributed Hash Table , DHT )算法来构建映射平面的方法， 但是由于 CAN 算法的平均查找跳数为 (d/4) x dl/2(CAN釆用笛卡尔多维空间模型， d为维 度)， 在其维度 d=lnN (N为映射平面节点的数量)时性能最佳， 当映射平面的 节点数量为 1万时， 在 CAN技术构造的映射平面查找数据平均要经过 7跳， 引入时延在 1秒以上， 性能过低， 而且其没有解决多运营商组网的问题。
发明内容
本发明要解决的问题是提供一种身份位置分离网络的名址映射系统和数 据传输方法， 以提高路由效率。
为解决以上技术问题， 本发明提供的一种身份位置分离网络的名址映射 系统， 该系统包括域映射服务器以及与所述域映射服务器连接的一个或多个 域映射平面， 其中：
所述域映射平面设置为： 保存本域路由表以及本地映射表， 用于接收接 入业务节点或其它域映射平面发送的报文， 所述报文中携带目的身份标识； 根据所述本域路由表判断所述目的身份标识不属于所述域映射平面时向域映 射服务器发送域查询请求； 接收所述域映射服务器返回的目的域映射平面信 息， 向所述目的域映射平面发送报文； 以及根据所述本地映射表中目的身份 标识对应的目的路由标识， 向所述目的路由标识对应的目的接入业务节点发 送报文；
所述域映射服务器设置为： 保存身份标识与映射平面关系表， 接收域映 射平面的域查询请求， 所述查询请求中包括目的身份标识； 以及根据所述域 查询请求查询身份标识与映射平面的关系表获取目的域映射平面信息并返回 给所述域映射平面。
所述域映射平面由至少 1个映射节点构成，所述映射节点包括收发模块、 本域路由表模块、 节点确定模块、 域间路由模块、 本地映射表模块以及地址 查询模块；
所述收发模块设置为： 接收所述接入业务节点或其他映射节点发送的报 文， 以及向所述接入业务节点或其他映射节点发送 文； 所述本域路由表模块设置为： 保存本域路由表， 所述本域路由表包括本 域身份标识与本域映射节点的对应关系；
所述节点确定模块与所述收发模块及所述本域路由表模块连接， 其设置 为： 查询所述本域路由表， 确定目的身份标识是否属于本域以及确定所述目 的身份标识在本域对应的映射节点， 所述目的身份标识不属于本域时通知域 间路由模块； 确定的映射节点是本域其他映射节点时， 通知收发模块将报文 转发给所述确定的映射节点； 确定的映射节点为当前映射节点时， 通知所述 地址查询模块；
所述域间路由模块设置为： 向所述域映射服务器发送域查询请求， 其中 携带所述目的身份标识；接收所述域映射服务器发送的目的域映射平面信息， 以及通知所述收发模块向所述目的域映射平面转发报文；
所述本地映射表模块设置为： 保存本地映射表， 所述本地映射表包括本 地身份标识与路由标识的映射关系；
所述地址查询模块与所述本地映射表模块连接， 其设置为： 根据所述目 的身份标识查询所述本地映射表获得目的路由标识， 通知所述收发模块向所 述目的路由标识对应的接入业务节点发送报文。
所述系统还包括与所在域的域映射平面连接的接入业务节点， 所述地址 查询模块还设置为： 获得目的路由标识后， 通知所述收发模块向源路由标识 对应的接入业务节点发送目的身份标识与目的路由标识的映射关系；
所述收发模块还设置为： 向源路由标识对应的接入业务节点发送所述映 射关系；
所述接入业务节点还设置为： 緩存所述映射关系， 接收到终端发送的报 文后， 先查询緩存的映射关系， 未查到对应的映射关系时再将所述报文转发 给所在域映射平面的映射节点。
所述目的域映射平面信息是目的域映射平面的映射节点地址列表； 所述 域间路由模块是设置为以如下方式通知所述收发模块向所述目的域映射平面 转发报文： 根据所述映射节点地址列表选择所述目的域映射平面的一个或多 个映射节点， 通知所述收发模块向选择的映射节点转发报文。 所述接入业务节点是设置为以如下方式将所述报文转发给所在域映射平 面的映射节点： 配置至少一个所在域的映射节点， 当配置多个映射节点时， 釆用轮选或随机选取的方式从配置的映射节点中选择映射节点， 并向选择的 映射节点发送报文。
所述映射节点还包括与本地映射表模块连接的身份标识维护模块； 所述 收发模块还设置为： 接收所述接入业务节点发送的注册或注销请求， 其中携 带要注册或注销的身份标识与路由标识的映射关系； 所述节点确定模块还设 置为： 根据所述接入业务节点的注册或注销请求查询所述本域路由表确定对 应的映射节点， 若确定的映射节点是当前映射节点， 则通知所述身份标识维 护模块； 所述身份标识维护模块设置为： 在所述本地映射表注册或注销对应 的身份标识与路由标识的映射关系。
为解决上述技术问题， 本发明还提供了一种身份位置分离网络数据传输 方法， 该方法基于名址映射系统实现， 该系统包括域映射服务器、 与所述域 映射服务器连接的一个或多个域映射平面， 以及与所在域的域映射平面连接 的接入业务节点， 该方法包括： 所述报文中携带目的身份标识；
B、 所述源域映射平面判断所述目的身份标识是否属于本域， 若是， 则执 行步骤 E, 若不是， 则向所述域映射服务器发送域查询请求， 其中携带报文 目的身份标识；
C、所述域映射服务器查询身份标识与域映射平面对应关系，向所述源域 映射平面返回目的域映射平面信息；
D、 所述源域映射平面根据所述目的域映射平面信息向目的域映射平面 转发所述报文；
E、所述目的域映射平面查询身份标识与路由标识映射关系，获得目的路 由标识， 向所述目的路由标识对应的目的接入业务节点发送所述报文。
所述域映射平面包括至少一个映射节点， 步骤 E包括： 所述目的域映射 平面的映射节点收到报文且判断目的终端为本域终端后，先查询本域路由表， 确定所述目的路由标识所在的目的映射节点， 若为当前映射节点， 则查询本 地身份标识与路由标识映射关系， 获得目的路由标识， 向所述目的接入业务 节点所述报文， 否则将所述报文转发给确定的映射节点。
所述方法还包括： 所述目的域映射平面的目的映射节点获得目的路由标 识后，将目的身份标识与目的路由标识的映射关系发送所述源接入业务节点； 所述源接入业务节点将所述映射关系保存在本地映射表；
步骤 A之前， 所述方法还包括： 所述源接入业务节点接收到终端发送的 报文后， 先根据目的身份标识查询本地映射表， 若查到所述目的路由标识， 则直接将所述报文转发给对应的目的接入业务节点， 若没有查到所述目的路 由标识， 再执行步骤 A。
步骤 C 中的目的域映射平面信息是目的域映射平面的映射节点地址列 表； 步骤 D包括： 所述源域映射平面的映射节点根据所述映射节点地址列表 选择所述目的域映射平面的一个或多个映射节点， 向其转发所述 4艮文。
本发明系统和方法， 通过划分域映射平面及增设域映射服务器， 从而可 通过域映射服务器实现跨域的身份标识到域映射平面的关系查询， 获得目的 域映射平面的入口地址，再将跨域报文递交给目的域映射平面最终完成通信。 在域映射平面内釆用单跳 DHT (分布式哈希表）技术构建高性能的分布式数 据库存储名（即身份标识)址 (即路由标识)映射关系， 从而可以实现域映射平面 内一跳完成映射关系的快速查询， 提高了路由效率。 当多个运营商域组网时， 根据运营商划分域映射平面， 即， 每个运营商组成独立的映射平面， 并设置 统一的域映射服务器， 从而可提供适用于多运营商组网的高性能身份位置映 射平面。 附图概述
图 1为现有身份位置分离网络的架构示意图；
图 2为本发明身份位置分离网络的系统框图；
图 3为本发明应用实例一映射关系注册的流程图； 图 4为本发明应用实例二域映射平面内实现 IP通信的流程图；
图 5为本发明应用实例三跨域映射平面实现 IP通信的流程图。
本发明的较佳实施方式
本发明系统和方法的主要思想是通过划分域映射平面及增设域映射服务 器，从而可通过域映射服务器实现跨域的身份标识到域映射平面的关系查询， 获得目的域映射平面的入口地址， 再将跨域报文递交给目的域映射平面最终 完成通信。 在域映射平面内釆用单跳 DHT (分布式哈希表）技术构建高性能 的分布式数据库存储名（即身份标识)址 (即路由标识)映射关系， 从而可以实现 域映射平面内一跳完成映射关系的快速查询， 提高了路由效率。
图 2为本发明身份位置分离网络的名址映射系统的结构示意图， 该系统 包括 ASN (接入业务节点） 101 , 运营商 IP核心网 102, 域映射平面 103和域映 射服务器 105, 其中域映射平面由至少 1个映射节点 104构成。
一个 ASN可以接入多个终端， 每个终端具有特定的身份标识， 终端通过 ASN与其他终端进行通信， ASN的功能具体包括： 緩存域映射平面下发的映 射关系， 接收到终端发送的报文后， 先查询緩存的映射关系， 未查到对应的 映射关系时再将报文转发给所在域映射平面的映射节点。
每个 ASN配置至少一个所在域的映射节点 ,若所述接入业务节点配置多 个映射节点， 所述接入业务节点釆用轮选或随机选取等方式从配置的映射节 点中选择映射节点， 并向选择的映射节点发送报文。
所述域映射平面， 保存本域路由表以及本地映射表， 域映射平面的功能 包括： 用于接收接入业务节点或其它域映射平面发送的报文， 所述报文中携 带目的身份标识； 还用于根据所述本域路由表判断所述目的身份标识不属于 所述域映射平面时向域映射服务器发送所述域查询请求； 还用于接收所述域 映射服务器返回的所述目的域映射平面信息， 向所述目的域映射平面发送报 文； 以及根据所述本地映射表目的身份标识对应的目的路由标识， 向所述目 的路由标识对应的目的接入业务节点发送报文； 域映射平面可以根据地域位置或运营商来划分， 图 2中， 是以运营商来 划分域映射平面的，每个运营商的映射平面釆用单跳 DHT构造， 只存储本运 营商 （即本域） 负责的终端身份标识和路由标识的映射关系， 不同运营商的 映射平面之间无需交互数据， 跨运营商通信时需要通过查询域映射服务器来 获得目的身份标识对应的运营商域及其互通的映射平面映射节点列表， 使得 运营商之间的互通较为简单。
本发明中， 本域路由表釆用 DHT算法生成及查询， 本域路由表中存储的 是身份标识哈希值的分段与域映射平面内映射节点的对应关系，釆用 DHT算 法的原因是因为原始身份标识由运营商逐段进行分配， 在整个空间中分布不 均匀， 故不容易均匀地分布存储到映射平面映射节点上， 釆用 DHT算法后可 以解决这一问题。目前的哈希算法一般釆用 MD5或 SHA1 ,哈希输出为 128bit 或 160bit的数值， 以下简化釆用 16bit即 0 65535的哈希值来解释单跳 DHT 算法： 若身份标识哈希值是 16bit那么域映射平面的映射节点也要分配一个 16bit的逻辑节点 ID,—般来说系统中的节点数量远远小于身份标识数据条目 数， 若一个节点存储 100个身份标识数据， 系统中共有 1万个身份标识数据， 则节点只需要 100个。 身份标识数据所在的映射节点就是由身份标识的哈希 值和节点 ID之间的关系决定的， 例如， 可以釆用如下简单的规则： 身份标识 存储在节点 ID大于等于身份标识哈希值且最近的映射节点上，比如域映射平 面中有 4个映射节点， 节点 ID分别为 0、 10000、 30000、 40000, 若给定身 份标识的哈希值分别为 3000、 16000, 则其数据就应该分别存储在节点 ID为 10000、 30000的映射节点上。 为了实现本发明所说的单跳 DHT, 每个映射节 点的本域路由表均存储本域所有映射节点的 ID信息，故可根据目的身份标识 的哈希值确定其数据是否存储在本域， 以及存储在本域的映射节点。
当然也可以釆用其他规则来确定存储关系， 例如根据身份标识哈希值与 节点 ID的差值的绝对值最小的方法选择存储关系。
映射平面釆用 DHT单跳技术构建， 其域内寻址只需一跳， 性能较 CAN 算法大大提高，同时 DHT算法中身份标识与路由标识对应关系的存储位置是 依据 DHT算法确定的，不依赖于底层 IP网络的拓朴，不需要限制用户的 EID 只能固定在某一个 ASN接入， 因此可很好地支持终端的移动性。 所述域映射服务器， 保存有身份标识与映射平面关系表， 域映射服务器 的功能包括： 用于接收域映射平面的域查询请求， 所述查询请求中包括目的 身份标识； 还用于根据所述域查询请求查询身份标识与映射平面的关系表获 取目的域映射平面信息并返回给所述域映射平面。
本发明基于以上系统实现的数据传输过程包括以下步骤： 所述报文中携带目的身份标识；
每个 ASN配置至少一个所在域的映射节点 ,若所述接入业务节点配置多 个映射节点， 所述接入业务节点釆用轮选的方式从配置的映射节点中选择映 射节点， 并向选择的映射节点发送报文。
B、 所述源域映射平面判断所述目的身份标识是否属于本域， 若是， 则执 行步骤 E, 否则向所述域映射服务器发送域查询请求， 其中携带报文目的身 份标识；
C、所述域映射服务器查询身份标识与域映射平面对应关系，向所述源域 映射平面返回目的域映射平面信息；
D、 所述源域映射平面根据所述目的域映射平面信息向目的域映射平面 转发所述报文； 具体地， 目的域映射平面信息是目的域映射平面的映射节点 地址列表； 步骤 D中， 所述源域映射平面的映射节点根据所述映射节点地址 列表选择目的域映射平面的一个或多个映射节点， 向其转发所述报文。
E、所述目的域映射平面查询身份标识与路由标识映射关系，获得目的路 由标识， 向目的接入业务节点发送所述报文。
步骤 E中， 所述目的域映射平面的映射节点收到报文且判断目的终端为 本域终端后， 先查询本域路由表， 确定所述目的路由标识所在的目的映射节 点， 若为本映射节点， 则查询本地身份标识与路由标识映射关系， 获得目的 路由标识， 向所述目的接入业务节点所述报文， 否则将所述报文转发给确定 的映射节点。
步骤 E中， 所述目的域映射平面的目的映射节点获得目的路由标识后， 将目的身份标识与目的路由标识的映射关系发送所述源接入业务节点； 所述 源接入业务节点将所述映射关系保存在本地映射表； 步骤 A之前， 所述源接 入业务节点接收到终端发送的报文后，先根据目的身份标识查询本地映射表， 若查到所述目的路由标识， 则直接将所述报文转发给对应的目的接入业务节 点， 若没有查到所述目的路由标识， 再执行步骤 A。
下面结合附图和具体应用实例对本发明作进一步详细描述。
应用实例一
图 3示出了 UE附着到网络时向域映射平面注册的流程， 包括以下步骤： 步骤 301 , UE向 ASN进行注册， 该注册流程釆用现有流程； 比如 ASN 是一个 3GPP网络接入网关， 则其釆用 3GPP分组域用户附着流程；
步骤 302, 当 ASN处理完 UE网络附着请求时， 其向映射平面发起一个 注册请求 Map— Register, 该请求携带 UE的身份标识和自身的路由标识；
一般来说每个 ASN可以配置多个映射平面的映射节点地址，其可以釆用 轮选的方式向多个映射节点发出请求以达到负载均衡的目的。
步骤 303 , 映射节点 1根据 UE的身份标识查询本域路由表 ()， 获知该身 份标识应该存储在映射节点 2之上， 故其向映射节点 2发出 DHT存储请求， 请求存储 UE的身份标识和 ASN的路由标识的对应关系；
当釆用单跳 DHT, 本域路由表实际上存储的是本域映射平面所有映射节 点的信息， 为简化起见， 假定节点 ID长度为 16bit (实际网络中一般为 128bit 或以上）， 示意如下:
Figure imgf000011_0001
给定一个身份标识，查找本域路由表前首先将其哈希获得一个 16bit的身 份标识哈希值， 假定为 0x3012, 在以上本域路由表示例中， 0x8200节点 ID 是大于等于该值的最小节点 ID, 故该身份标识数据存储在 0x8200节点 ID对 应的映射节点上。
步骤 304, 映射节点 2收到映射关系存储请求后， 在本地存储 UE的身份 标识和 ASN的路由标识的对应关系；
在本步骤中， 映射节点 2有可能根据 DHT算法的备份策略， 向 1个或多 个其它节点备份该条数据。
步骤 305 , 映射节点 2向映射节点 1返回 DHT存储响应消息。
步骤 206 , 映射节点 1向 ASN返回 Map— Register响应消息 , 本实施例完 成。
应用实例二
图 4示出了在域映射平面内实现 IP通信的实施例流程， 包括以下步骤： 步骤 401 , UE11发送一个 IP报文，其目的地址为 UE21的身份标识 EID21； 步骤 402, ASN1 收到报文后， 在本地身份标识-路由标识映射緩存表中 未查到 EID21的记录， 将该报文封装后发给映射平面的映射节点 1 , 其封装 外层地址为映射节点 1的 IP地址；
关于映射节点的选择， 可以釆用静态配置方式， 比如在 ASN上配置多个 映射节点， ASN对于每个发往映射平面的请求釆用轮选等负载均衡方法在多 个映射节点之间进行选择；
步骤 403 , 映射节点 1收到报文后， 根据本域路由表判断该 EID21为本 域用户， 然后再以 EID21作为关键字查找本域路由表， 获知其数据存储在映 射节点 2;
步骤 404, 映射节点 1根据查询结果， 将报文转发给映射节点 2;
步骤 405 ,映射节点 2读取本地映射表获知 EID21对应的 RLOC21(ASN2 的路由标识）， 将收到的 IP 文的外部封装目标地址改为 RLOC21；
步骤 406-407 ,映射节点 2将 EID21-RLOC21的对应关系通知 ASN1 , ASN1 将其存储在自己的本地緩存中，以便后续发往 EID21的 IP报文可以在本地直 接匹配到该条记录， 无需再通过映射平面进行转发；
步骤 408, 映射节点 2将更改过封装地址的 文发往 RLOC21 对应的 ASN2;
步骤 406和步骤 408不分先后顺序。
步骤 409, ASN2收到报文后， 移除外部封装头部， 将报文发给 UE21 , 完成一次 ^艮文端到端的递交；
步骤 410, UE11又发出一个目的地址为 EID21的才艮文；
步骤 411 , ASN1收到报文后，在本地緩存查询获得 EID21对应的路由标 识 RLOC21 , 将^艮文进行封装， 封装目标地址为 RLOC21 , 源地址为本 ASN 的 RLOC11 ;
步骤 412, ASN1将上一步封装的报文直接发给 ASN2, 无需再经过映射 平面；
步骤 413 , ASN2收到 ASN1发过来的报文后， 移除外部封装头部， 将报 文转发给 UE21。
应用实例二
图 5示出了一种通过域映射服务器实现跨越运营商域映射平面进行 IP通 信的流程， 包括以下步骤：
步骤 501 , UE11发送一个 IP报文，其目的地址为 UE21的终端标识 EID21； 步骤 502, ASN1 收到报文后， 在本地身份标识-路由标识映射緩存表中 未查到 EID21 的记录， 将该报文封装后发给本域 (运营商 A)映射平面的映射 节点 11 , 其封装报文外层地址为映射节点 11的 IP地址；
关于映射节点的选择， 可以釆用静态配置方式， 比如在 ASN上配置多个 映射节点， ASN对于每个发往映射平面的请求釆用轮选等负载均衡方法在多 个映射节点之间进行选择。
步骤 503 , 映射节点 11收到报文后， 根据本域路由表判断该 EID21为它 域用户， 然后再以 EID21作为关键字查找向域映射服务器发出域查询请求； 步骤 504, 域映射服务器查询身份标识与域映射平面对应关系表向映射 节点 11返回 EID21对应的运营商 B的映射平面映射节点地址列表； 在本发 明中域映射服务器不必存储每个身份标识的具体信息， 而仅需存储身份标识 段信息， 即存储身份标识段和域映射平面入口地址列表的对应关系。
步骤 505, 映射节点 11根据上一步返回的映射节点地址列表， 选择一个 映射节点 21 , 向其转发初始的 IP ·^艮文；
步骤 506,运营商 B的映射节点 21收到报文后，判断目标身份标识 EID21 为本域用户， 查询本域路由表， 获知其数据存储在映射节点 22;
步骤 507, 映射节点 21根据上一步查询的结果， 将报文转发给映射节点 22;
步骤 508,映射节点 22读取本地的 EID-RLOC映射表获知 EID21对应的 RLOC21(ASN2 的路由标识）， 将收到的 IP · ^艮文的外部封装目标地址改为 RLOC21 ;
步骤 509-510, 映射节点 22将 EID21-RLOC21的对应关系通知 ASN1 , ASN1将其存储在自己的本地緩存中， 以便后续发往 EID21的 IP报文可以在 本地直接匹配到该条记录， 无需再通过映射平面进行转发；
步骤 511 , 映射节点 22将更改过封装地址的 文发往 RLOC21对应的 ASN2;
步骤 509和步骤 511不分先后顺序。
步骤 512, ASN2收到报文后， 移除外部封装头部， 将报文发给 UE21 , 完成一次 ^艮文端到端的递交；
步骤 513 , UE11又发出一个目的地址为 EID21的才艮文；
步骤 514, ASN1收到报文后，在本地緩存查询获得 EID21对应的路由标 识 RLOC21 , 将^艮文进行封装， 封装目标地址为 RLOC21 , 源地址为本 ASN 的 RLOC11 ;
步骤 515, ASN1将上一步封装的报文直接发给 ASN2, 无需再经过映射 平面。
步骤 516, ASN2收到 ASN1发过来的报文后， 移除外部封装头部， 将报 文转发给 UE21。
为实现以上方法， 以下对域映射平面内的映射节点的功能模块进行具体 说明：
域映射平面的每个映射节点包括：
收发模块， 用于接收所述接入业务节点或其他映射节点发送的报文， 以 及向所述接入业务节点或其他映射节点发送报文； 还用于向源路由标识对应 的接入业务节点发送所述映射关系； 还用于接收所述接入业务节点发送的注 册或注销请求， 其中携带要注册或注销的身份标识与路由标识的映射关系； 本域路由表模块， 用于保存本域路由表， 本域路由表包括本域身份标识 与本域映射节点的对应关系；
DHT路由维护模块， 用于收集本域映射平面内映射节点信息， 生成上述 本域路由表； 处理节点的加入、 退出事件， 保证路由表的准确性；
节点确定模块， 与收发模块及本域路由表模块连接， 用于查询所述本域 路由表， 确定目的身份标识是否属于本域以及确定所述目的身份标识在本域 对应的映射节点， 所述目的身份标识不属于本域时通知域间路由模块； 确定 的映射节点是本域其他映射节点时， 通知收发模块将报文转发给所述确定的 映射节点； 确定的映射节点为当前映射节点时， 通知所述地址查询模块； 还 用于根据所述接入业务节点的注册或注销请求查询所述本域路由表确定对应 的映射节点， 若确定的映射节点是当前映射节点， 则通知所述身份标识维护 模块，
域间路由模块， 用于向所述域映射服务器发送域查询请求， 其中携带所 述目的身份标识；还用于接收所述域映射服务器发送的目的域映射平面信息， 以及通知所述收发模块向所述目的域映射平面转发报文； 具体地， 所述目的 域映射平面信息是目的域映射平面的映射节点地址列表； 所述域间路由模块 根据所述映射节点地址列表选择目的域映射平面的一个或多个映射节点， 通 知所述收发模块向选择的目的域映射平面的映射节点转发报文。
本地映射表模块， 用于保存本地映射表， 本地映射表包括本地身份标识 与路由标识的映射关系；
地址查询模块， 与所述本地映射表模块连接， 用于根据所述目的身份标 识查询所述本地映射表获得目的路由标识， 还用于通知所述收发模块向所述 目的路由标识对应的接入业务节点发送报文； 地址查询模块获得目的路由标 识后， 还用于通知所述收发模块向源路由标识对应的接入业务节点发送目的 身份标识与目的路由标识的映射关系；
身份标识维护模块， 与本地映射表模块连接， 用于在本地映射表注册或 注销对应的身份标识与路由标识的映射关系。
本发明系统和方法， 通过划分域映射平面及增设域映射服务器， 从而可 通过域映射服务器实现跨域的身份标识到域映射平面的关系查询， 获得目的 域映射平面的入口地址，再将跨域报文递交给目的域映射平面最终完成通信。 在域映射平面内釆用单跳 DHT (分布式哈希表）技术构建高性能的分布式数 据库存储名（即身份标识)址 (即路由标识)映射关系， 从而可以实现域映射平面 内一跳完成映射关系的快速查询， 提高了路由效率。 当多个运营商域组网时， 根据运营商划分域映射平面， 即， 每个运营商组成独立的映射平面， 并设置 统一的域映射服务器， 从而可提供适用于多运营商组网的高性能身份位置映 射平面。
在此基础上， 负责终端接入的接入业务节点 ASN负责代替终端向此分布 式数据库注册 /注销终端名址绑定关系； 当 ASN收到终端发过来的报文其目 的地址 (即目的终端的身份标识)在本地緩存中没有记录时，其将报文发给域映 射平面负责转发， 域映射平面通过其存储的目的终端的名址映射关系将报文 路由到目的终端； 当 ASN本地緩存中记录有目的终端的身份标识和目的路由 标识的映射关系，该 ASN将报文直接转发给目的 ASN, 而无需通过域映射平 面进行转发。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序 来指令相关硬件完成， 所述程序可以存储于计算机可读存储介质中， 如只读 存储器、 磁盘或光盘等。 可选地， 上述实施例的全部或部分步骤也可以使用 一个或多个集成电路来实现。 相应地， 上述实施例中的各模块 /单元可以釆用 硬件的形式实现， 也可以釆用软件功能模块的形式实现。 本发明不限制于任 何特定形式的硬件和软件的结合。
工业实用性
本发明系统和方法， 通过划分域映射平面及增设域映射服务器， 从而可 通过域映射服务器实现跨域的身份标识到域映射平面的关系查询， 获得目的 域映射平面的入口地址，再将跨域报文递交给目的域映射平面最终完成通信。 在域映射平面内釆用单跳 DHT技术构建高性能的分布式数据库存储名（即身 份标识)址（即路由标识)映射关系， 从而可以实现域映射平面内一跳完成映射 关系的快速查询， 提高了路由效率。 当多个运营商域组网时， 根据运营商划 分域映射平面， 即， 每个运营商组成独立的映射平面， 并设置统一的域映射 服务器， 从而可提供适用于多运营商组网的高性能身份位置映射平面。

Claims

权 利 要 求 书
1、一种身份位置分离网络的名址映射系统， 该系统包括域映射服务器以 及与所述域映射服务器连接的一个或多个域映射平面；
所述域映射平面设置为： 保存本域路由表以及本地映射表， 接收接入业 务节点或其它域映射平面发送的报文， 所述报文中携带目的身份标识； 根据 所述本域路由表判断所述目的身份标识不属于所述域映射平面时向所述域映 射服务器发送域查询请求； 接收所述域映射服务器返回的目的域映射平面信 息， 向所述目的域映射平面发送报文； 以及根据所述本地映射表中目的身份 标识对应的目的路由标识， 向所述目的路由标识对应的目的接入业务节点发 送报文；
所述域映射服务器设置为： 保存身份标识与映射平面关系表， 接收域映 射平面的域查询请求， 所述查询请求中包括目的身份标识； 以及根据所述域 查询请求查询身份标识与映射平面的关系表获取目的域映射平面信息并返回 给所述域映射平面。
2、 如权利要求 1所述的名址映射系统， 其中， 所述域映射平面由至少 1 个映射节点构成， 所述映射节点包括收发模块、 本域路由表模块、 节点确定 模块、 域间路由模块、 本地映射表模块以及地址查询模块；
所述收发模块设置为： 接收所述接入业务节点或其他映射节点发送的报 文， 以及向所述接入业务节点或其他映射节点发送 文；
所述本域路由表模块设置为： 保存本域路由表， 所述本域路由表包括本 域身份标识与本域映射节点的对应关系；
所述节点确定模块与所述收发模块及所述本域路由表模块连接， 所述节 点确定模块设置为： 查询所述本域路由表， 确定目的身份标识是否属于本域 以及确定所述目的身份标识在本域对应的映射节点， 所述目的身份标识不属 于本域时通知域间路由模块； 确定的映射节点是本域其他映射节点时， 通知 收发模块将报文转发给所述确定的映射节点； 确定的映射节点为当前映射节 点时， 通知所述地址查询模块； 所述域间路由模块设置为： 向所述域映射服务器发送域查询请求， 其中 携带所述目的身份标识；接收所述域映射服务器发送的目的域映射平面信息， 以及通知所述收发模块向所述目的域映射平面转发报文；
所述本地映射表模块设置为： 保存本地映射表， 所述本地映射表包括本 地身份标识与路由标识的映射关系；
所述地址查询模块与所述本地映射表模块连接， 所述地址查询模块设置 为： 根据所述目的身份标识查询所述本地映射表获得目的路由标识， 通知所 述收发模块向所述目的路由标识对应的接入业务节点发送报文。
3、如权利要求 2所述的名址映射系统， 所述系统还包括与所在域的域映 射平面连接的接入业务节点， 所述地址查询模块还设置为： 获得目的路由标 识后， 通知所述收发模块向源路由标识对应的接入业务节点发送目的身份标 识与目的路由标识的映射关系；
所述收发模块还设置为： 向源路由标识对应的接入业务节点发送所述映 射关系；
所述接入业务节点设置为： 緩存所述映射关系， 接收到终端发送的报文 后， 先查询緩存的映射关系， 未查到对应的映射关系时再将所述报文转发给 所在域映射平面的映射节点。
4、 如权利要求 2所述的名址映射系统， 其中， 所述目的域映射平面信息 是目的域映射平面的映射节点地址列表； 所述域间路由模块是设置为以如下 方式通知所述收发模块向所述目的域映射平面转发报文： 根据所述映射节点 地址列表选择所述目的域映射平面的一个或多个映射节点， 通知所述收发模 块向选择的映射节点转发报文。
5、 如权利要求 1所述的名址映射系统， 其中， 所述接入业务节点是设置 所在域的映射节点， 当配置多个映射节点时， 釆用轮选或随机选取的方式从 配置的映射节点中选择映射节点， 并向选择的映射节点发送报文。
6、 如权利要求 2所述的名址映射系统， 其中， 所述映射节点还包括与本 地映射表模块连接的身份标识维护模块；
所述收发模块还设置为：接收所述接入业务节点发送的注册或注销请求， 其中携带要注册或注销的身份标识与路由标识的映射关系；
所述节点确定模块还设置为： 根据所述接入业务节点的注册或注销请求 查询所述本域路由表确定对应的映射节点， 若确定的映射节点是当前映射节 点， 则通知所述身份标识维护模块；
所述身份标识维护模块设置为： 在所述本地映射表注册或注销对应的身 份标识与路由标识的映射关系。
7、 一种身份位置分离网络数据传输方法， 其特征在于， 该方法基于名址 映射系统实现， 该系统包括域映射服务器、 与所述域映射服务器连接的一个 或多个域映射平面， 以及与所在域的域映射平面连接的接入业务节点， 该方 法包括： 所述报文中携带目的身份标识；
B、 所述源域映射平面判断所述目的身份标识是否属于本域， 若是， 则执 行步骤 E, 若不是， 则向所述域映射服务器发送域查询请求， 其中携带报文 目的身份标识；
C、所述域映射服务器查询身份标识与域映射平面对应关系，向所述源域 映射平面返回目的域映射平面信息；
D、 所述源域映射平面根据所述目的域映射平面信息向目的域映射平面 转发所述报文；
E、所述目的域映射平面查询身份标识与路由标识映射关系，获得目的路 由标识， 向所述目的路由标识对应的目的接入业务节点发送所述报文。
8、 如权利要求 7所述的方法， 其中， 所述域映射平面包括至少一个映射 节点， 步骤 E包括： 所述目的域映射平面的映射节点收到报文且判断目的终 端为本域终端后， 先查询本域路由表， 确定所述目的路由标识所在的目的映 射节点， 若为当前映射节点， 则查询本地身份标识与路由标识映射关系， 获 得目的路由标识， 向所述目的接入业务节点所述报文， 否则将所述报文转发 给确定的映射节点。
9、 如权利要求 7所述的方法， 所述方法还包括： 所述目的域映射平面的 目的映射节点获得目的路由标识后， 将目的身份标识与目的路由标识的映射 关系发送所述源接入业务节点； 所述源接入业务节点将所述映射关系保存在 本地映射表；
步骤 A之前， 所述方法还包括： 所述源接入业务节点接收到终端发送的 报文后， 先根据目的身份标识查询本地映射表， 若查到所述目的路由标识， 则直接将所述报文转发给对应的目的接入业务节点， 若没有查到所述目的路 由标识， 再执行步骤 A。
10、 如权利要求 7所述的方法， 其中， 步骤 C中的目的域映射平面信息 是目的域映射平面的映射节点地址列表； 步骤 D包括： 所述源域映射平面的 映射节点根据所述映射节点地址列表选择所述目的域映射平面的一个或多个 映射节点， 向其转发所述 文。
PCT/CN2010/074941 2009-09-14 2010-07-02 身份位置分离网络的名址映射系统及数据传输方法 Ceased WO2011029343A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910176424.2 2009-09-14
CN200910176424.2A CN101656765B (zh) 2009-09-14 2009-09-14 身份位置分离网络的名址映射系统及数据传输方法

Publications (1)

Publication Number Publication Date
WO2011029343A1 true WO2011029343A1 (zh) 2011-03-17

Family

ID=41710850

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/074941 Ceased WO2011029343A1 (zh) 2009-09-14 2010-07-02 身份位置分离网络的名址映射系统及数据传输方法

Country Status (2)

Country Link
CN (1) CN101656765B (zh)
WO (1) WO2011029343A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102170369A (zh) * 2011-04-19 2011-08-31 北京交通大学 一种一体化网络中映射服务器的dht部署方法
CN104506459A (zh) * 2014-12-10 2015-04-08 北京交通大学 智慧协同网络中的数据包传输方法、装置和系统
CN112788702A (zh) * 2021-01-07 2021-05-11 西安电子科技大学 一种用于卫星物联网移动终端的映射表项缓存更新方法
CN113312347A (zh) * 2020-11-24 2021-08-27 芜湖达成储运有限公司 库存管理系统及方法
CN117728927A (zh) * 2024-02-18 2024-03-19 南京风启科技有限公司 一种基于域标识的变长报文处理时延探测方法

Families Citing this family (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102014043B (zh) 2009-09-08 2013-12-04 中兴通讯股份有限公司 名址映射系统、数据传输方法及名址映射维护方法
CN101656765B (zh) * 2009-09-14 2013-01-16 中兴通讯股份有限公司 身份位置分离网络的名址映射系统及数据传输方法
CN102045266A (zh) * 2009-10-10 2011-05-04 中兴通讯股份有限公司 一种支持数据报文主动推送能力的实现方法及系统
CN102209012A (zh) * 2010-03-29 2011-10-05 中兴通讯股份有限公司 一种终端实现连接建立的方法及系统
CN102209011A (zh) * 2010-03-29 2011-10-05 中兴通讯股份有限公司 多穴终端建立连接的方法和系统
CN102215160B (zh) * 2010-04-07 2016-01-20 中兴通讯股份有限公司 数据通信系统及方法
CN102215161B (zh) * 2010-04-07 2015-06-03 中兴通讯股份有限公司 网间数据通讯系统及方法
CN102238059B (zh) * 2010-04-20 2015-05-13 中兴通讯股份有限公司 数据报文处理方法、系统及接入服务节点
CN102238058B (zh) * 2010-04-20 2015-05-13 中兴通讯股份有限公司 数据报文处理方法、入口隧道路由器及系统
CN101873265B (zh) * 2010-06-09 2012-10-03 北京交通大学 用于标识分离映射网络的数据分析装置及其方法
WO2012088849A1 (zh) * 2010-12-27 2012-07-05 中兴通讯股份有限公司 一种连接信息获取方法和系统
CN102547908B (zh) * 2010-12-28 2015-08-12 中兴通讯股份有限公司 表维护方法、系统和接入网关路由器
CN102625285B (zh) * 2011-02-01 2017-04-26 中兴通讯股份有限公司 一种获取终端的身份标识的方法及系统
CN103069917B (zh) * 2011-02-25 2015-08-19 华为技术有限公司 用于建立数据路径、设备和通信系统的方法
CN102685712B (zh) * 2011-03-09 2016-08-03 中兴通讯股份有限公司 一种身份位置分离网络中的映射服务器及其实现方法
WO2012122709A1 (zh) * 2011-03-16 2012-09-20 中兴通讯股份有限公司 身份位置分离网络与互联网的互通方法及互通网络
CN102938885A (zh) * 2011-08-16 2013-02-20 中兴通讯股份有限公司 身份位置分离与传统网络互联互通方法、ilr和asr
CN102957756B (zh) * 2011-08-23 2017-10-17 中兴通讯股份有限公司 数据报文的处理方法及接入服务路由器
CN103200102B (zh) * 2012-01-09 2018-02-13 中兴通讯股份有限公司 一种业务路由方法、装置和系统
CN103841027B (zh) * 2012-11-26 2018-08-14 中兴通讯股份有限公司 哈希映射平面的映射信息注册和查找方法、设备及系统
CN102970230B (zh) * 2012-12-07 2015-06-10 中国联合网络通信集团有限公司 数据报文转发方法及路由器
CN103491129B (zh) 2013-07-05 2017-07-14 华为技术有限公司 一种业务节点配置方法、业务节点池注册器及系统
CN104184663B (zh) * 2014-07-17 2018-02-06 北京交通大学 基于软件定义网络和一体化标识网络的通信方法和装置
CN105591998B (zh) * 2014-10-21 2019-01-08 新华三技术有限公司 抑制周期性注册通信端点标识eid的方法和设备
CN105592174A (zh) * 2014-10-24 2016-05-18 中兴通讯股份有限公司 一种身份位置分离网络映射平面管理方法和映射平面
CN106101296B (zh) * 2016-05-31 2021-04-09 新华三技术有限公司 分配地址的方法、装置和传输报文的方法、装置
CN107786444B (zh) * 2016-08-31 2020-04-07 中国电信股份有限公司 消息传输方法和控制器
CN108337173B (zh) * 2018-03-23 2020-09-01 中国电子科技集团公司第五十四研究所 基于本地缓存和结构化p2p的分布式名址映射系统及方法
CN109347979B (zh) * 2018-11-22 2021-03-12 中国联合网络通信集团有限公司 一种查询方法和服务器
CN113014489B (zh) * 2020-12-31 2022-02-22 腾讯科技（深圳）有限公司 数据转发方法及装置、服务器、存储介质
CN114785544B (zh) * 2022-03-12 2024-07-02 海南电网有限责任公司 一种提升网络系统中管理面系统安全接入业务面系统的方法
CN118368341A (zh) * 2023-01-17 2024-07-19 腾讯科技（深圳）有限公司 一种基于分层链网络的数据处理方法、装置、设备及介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008140113A1 (ja) * 2007-05-16 2008-11-20 National Institute Of Information And Communications Technology ノード識別子と位置指示子とを用いたパケットの通信方法
CN101483600A (zh) * 2009-02-19 2009-07-15 北京交通大学 实现一体化网络归属域信息扩散的方法
CN101656765A (zh) * 2009-09-14 2010-02-24 中兴通讯股份有限公司 身份位置分离网络的名址映射系统及数据传输方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100365997C (zh) * 2005-08-26 2008-01-30 南京邮电大学 用于在对等网络中采用分布式哈希表的资源定位方法
CN101459698B (zh) * 2007-12-14 2012-11-14 中国人民解放军信息工程大学 域内和域间的网络互连方法及其系统
CN101489307B (zh) * 2008-01-14 2011-05-04 展讯通信（上海）有限公司 一种基于用户标识映射的增强型fach接入方法与系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008140113A1 (ja) * 2007-05-16 2008-11-20 National Institute Of Information And Communications Technology ノード識別子と位置指示子とを用いたパケットの通信方法
CN101483600A (zh) * 2009-02-19 2009-07-15 北京交通大学 实现一体化网络归属域信息扩散的方法
CN101656765A (zh) * 2009-09-14 2010-02-24 中兴通讯股份有限公司 身份位置分离网络的名址映射系统及数据传输方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
FARINACCI, D. ET AL., LOCATOR/ID SEPARATION PROTOCOL (LISP), 2 March 2009 (2009-03-02) *

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102170369A (zh) * 2011-04-19 2011-08-31 北京交通大学 一种一体化网络中映射服务器的dht部署方法
CN104506459A (zh) * 2014-12-10 2015-04-08 北京交通大学 智慧协同网络中的数据包传输方法、装置和系统
CN104506459B (zh) * 2014-12-10 2017-11-21 北京交通大学 智慧协同网络中的数据包传输方法、装置和系统
CN113312347A (zh) * 2020-11-24 2021-08-27 芜湖达成储运有限公司 库存管理系统及方法
CN112788702A (zh) * 2021-01-07 2021-05-11 西安电子科技大学 一种用于卫星物联网移动终端的映射表项缓存更新方法
CN112788702B (zh) * 2021-01-07 2022-07-22 西安电子科技大学 一种用于卫星物联网移动终端的映射表项缓存更新方法
CN117728927A (zh) * 2024-02-18 2024-03-19 南京风启科技有限公司 一种基于域标识的变长报文处理时延探测方法
CN117728927B (zh) * 2024-02-18 2024-05-10 南京风启科技有限公司 一种基于域标识的变长报文处理时延探测方法

Also Published As

Publication number Publication date
CN101656765B (zh) 2013-01-16
CN101656765A (zh) 2010-02-24

Similar Documents

Publication Publication Date Title
WO2011029343A1 (zh) 身份位置分离网络的名址映射系统及数据传输方法
CN102014043B (zh) 名址映射系统、数据传输方法及名址映射维护方法
CN102215160B (zh) 数据通信系统及方法
EP2721787B1 (en) Principal-identity-domain based naming scheme for information centric networks
US9130887B2 (en) Hash-based forwarding of packets with hierarchically structured variable-length identifiers over ethernet
CN101394333B (zh) 转发报文的方法、装置以及网络系统
EP2928118B1 (en) System and method for dynamic name configuration in content-centric networks
US20080107114A1 (en) Method and apparatus for forwarding service in a data communication device
CN105553711A (zh) 实现陆、海、空、天网络一体化的网络体系架构及方法
US9391896B2 (en) System and method for packet forwarding using a conjunctive normal form strategy in a content-centric network
US9401864B2 (en) Express header for packets with hierarchically structured variable-length identifiers
WO2013023465A1 (zh) 身份位置分离与传统网络互联互通方法、ilr和asr
CN102215161B (zh) 网间数据通讯系统及方法
CN102546372B (zh) 一种提高映射路由表使用效率的方法及系统
CN103973572B (zh) 转发报文的方法、装置以及网络系统
CN103209131A (zh) 地址查询、报文发送方法、信息登记服务器及交换路由器
CN103841027B (zh) 哈希映射平面的映射信息注册和查找方法、设备及系统
WO2013053293A1 (zh) 一种标识网与传统网络互联互通的方法、asr及isr
CN102572720B (zh) 一种提高映射路由表使用效率的方法及系统
CN119449704A (zh) 算力路由方法、装置、路由节点、节点和客户端设备
Abid et al. SANA: a service-aware naming architecture for future Internet
CN105592174A (zh) 一种身份位置分离网络映射平面管理方法和映射平面
CN102572720A (zh) 一种提高映射路由表使用效率的方法及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10814945

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10814945

Country of ref document: EP

Kind code of ref document: A1