WO2011069399A1

WO2011069399A1 - Address mapping method and access service node

Info

Publication number: WO2011069399A1
Application number: PCT/CN2010/078568
Authority: WO
Inventors: 孙翼舟; 王标; 江华
Original assignee: 中兴通讯股份有限公司
Priority date: 2009-12-09
Filing date: 2010-11-09
Publication date: 2011-06-16
Also published as: CN102098349A

Abstract

The present invention discloses an address mapping method and an Access Service Node (ASN), which are implemented based on an identity and location separation network, wherein the ASN is provided with a commonly used address mapping table including a mapping relationship between commonly used identity identifiers and location identifiers. The method includes: the ASN receives a data message including a target identity identifier; the ASN queries the commonly used address mapping table according to the target identity identifier in the data message; if the target location identifier corresponding to the target identity identifier is found in the commonly used address mapping table, then the ASN forwards the data message according to the target location identifier; if the target location identifier corresponding to the target identity identifier is not found in the commonly used address mapping table, then the ASN interacts with a mapping server to forward the data message. The present invention can reduce data traffic between the ASN and the mapping server, and improve the efficiency of data message processing.

Description

Address mapping method and access service node

Technical field

The present invention relates to the field of communications technologies, and in particular, to an address mapping method and an access service node.

Background technique

Research on the next generation of information network architecture is one of the hottest topics at present. At present, most of the research accepted the view that: In the future, the network will use the Internet as the unified bearer network. The Internet has maintained rapid development since its birth. It has become the most successful and most vital communication network. Its flexible and scalable, efficient packet switching, and powerful functions of the terminal are in line with the design needs of the new generation network. It will be the main reference blueprint for next-generation network design.

However, the structure of the Internet is far from optimal. There are many major design problems. The typical problem is the dual attribute of the IP address, that is, the IP address represents both the user identity and the network topology of the user. , that is, the dual attribute of the IP address. The Internet was invented in the 1970s. It is difficult to predict that there will be a large number of mobile terminals and multiple township terminals in the world today. Therefore, the Internet protocol stack at that time was mainly designed for terminals connected in a "fixed" manner. In the current network environment, since the terminal basically does not move from one location to another, the transmitted address is the received address, and the path is reversible, so the IP address with dual attributes of identity and location can work very well. There is no conflict between the identity attribute of the IP address and the location attribute.

The IP address also represents the identity and location that exactly met the network needs of the time. From the perspective of the network environment at the time, this design scheme is simple and effective, simplifying the hierarchy of the protocol stack. But there is no doubt that there is an internal contradiction between the identity attribute of the IP address and the location attribute. The identity attribute of an IP address requires that any two IP addresses be equal. Although the IP address can be assigned according to the organization, there is no necessary relationship between consecutively encoded IP addresses, or at least there is no necessary relationship in the topology. The location attribute of the IP address requires that the IP address be assigned based on the network topology (rather than the organization). The IP addresses in the same subnet should be in a contiguous IP address block so that the network topology can be made. The IP address prefix is aggregated, thereby reducing the entries of the routing table of the router device and ensuring the scalability of the routing system.

In general, the inherent contradiction between the dual attributes of IP addresses will lead to the following main problems: 1. Routing scalability issues. There is a basic assumption about the scalability of Internet routing systems:

"The address is assigned according to the topology, or the topology is deployed according to the address, and the two must choose one."

The identity attribute of an IP address requires that the IP address be assigned based on the organization to which the terminal belongs (rather than the network topology), and this allocation must be stable and cannot be changed frequently; the location attribute of the IP address requires the IP address to be based on the network. The topology is allocated to ensure the scalability of the routing system. In this way, the two attributes of the IP address create conflicts, which eventually leads to the scalability problem of the Internet routing system.

2. Mobility issues. The identity attribute of the IP address requires that the IP address should not change as the location of the terminal changes. This ensures that the communication bound to the identity is not interrupted, and that the terminal can still use its identity after the terminal is moved. The communication link is established; the location attribute of the IP address requires the IP address to change as the terminal location changes, so that the IP address can be aggregated in the new network topology, otherwise the network must reserve a separate route for the mobile terminal. Information, which causes a sharp increase in routing table entries.

3. A number of township issues. Many townships usually refer to terminals or networks that access the Internet through multiple Internet Service Provider (ISP) networks. The advantages of multiple township technologies include increasing network reliability, supporting traffic load balancing across multiple ISPs, and increasing overall available bandwidth. However, the inherent contradiction between the dual attributes of IP addresses makes it difficult to implement multiple township technologies. The identity attribute of an IP address requires that a plurality of township terminals always display the same identity to other terminals, regardless of whether the multiple township terminals access the Internet through several ISPs; and the location attribute of the IP address requires that multiple township terminals are different. The ISP network uses different IP addresses to communicate, so that the IP address of the terminal can be aggregated in the topology of the ISP network.

4. Security and location privacy issues. Since the IP address includes both the identity information and the location information of the terminal, both the communication peer and the malicious eavesdropper can obtain the identity information and the topology location information of the terminal according to the IP address of the terminal. In general, since the establishment of the traditional Internet architecture, the technical environment and user groups of the Internet have undergone earth-shaking changes, and the Internet needs to be innovated. The dual attribute problem of IP address is one of the fundamental reasons that plague the Internet to continue to develop. Separating the identity attribute and location attribute of the IP address is a good way to solve the problems faced by the Internet. The new network will be designed based on this idea and propose an identity letter. Separate the network structure of interest and location information to solve some serious drawbacks of the existing Internet. In order to solve the problem of identity and location, the industry has carried out a lot of research and exploration. The basic idea of all identity and location separation schemes is to separate the identity and location dual attributes originally bound to the IP address. Some schemes use the Uniform Resource Locator (URL, URL is a method for identifying the address of web pages and other resources on the Internet) or the qualified domain name (Fully Qualified Domain Name). , FQDN for short) as the identity of the terminal, such as IP Next Layer (IPNL, which belongs to the NAT extension architecture), TRIAD (upgradable configuration of NAT-based Internet architecture, A Scalable Deployable NAT-based Internet) Some schemes introduce a new namespace as an identity. For example, the Host Identity Protocol (HIP) adds a host identifier to the network layer with the IP address as the identifier. Some schemes classify the IP address. IP is used as the identity, and part of the IP is used as the location identifier, such as the Locator/ID Separation Protocol (LISP); the patent application CN 1801764, published on July 12, 2006, Location Separation Internet Access Method" proposes a solution to use I The P address is used as the location identifier of the host, and the host identifier is introduced as an identity to solve the problem of identity and location separation.

The above proposals and solutions propose a solution for identity and location separation under the existing network architecture from some parts of the problem. Location and identity separation are the core technologies of future data communication networks, especially mobile data communication networks.

The above solution, regardless of which identifier is used to represent the terminal identity information and which identifier is used to represent the terminal location information, must establish a mapping relationship between the identity identifier and the location identifier for use by the network device for addressing. The mapping relationship is stored in the mapping server, and the access service node receives the data packet sent from the terminal. If the destination identity of the data packet is unknown, the identity location mapping table of the mapping server needs to be queried, and the identity identifier is found according to the destination identity identifier. Destination location identifier, encapsulates the data packet and sends it to the corresponding network. For the access service node, in order to forward the data packet, it needs to interact with the mapping server to obtain the destination location identifier or forward the data packet by the mapping server, which will undoubtedly increase the access between the access service node and the mapping server. Data traffic, which in turn affects the processing speed of the network. Summary of the invention

The technical problem to be solved by the present invention is to provide an address mapping method and an access service node, so as to reduce data traffic between the access service node and the mapping server, and improve data packet processing efficiency.

To solve the above technical problem, the present invention provides an address mapping method, where the method is implemented based on an identity location separation network, and the access service node is provided with a common address mapping table, where the common address mapping table includes common identity identifiers and Mapping relationship of location identifiers; the method includes:

The access service node receives a data packet, where the data packet includes a destination identity identifier; the access service node queries the common address mapping table according to the destination identity identifier in the data packet;

If the destination location identifier corresponding to the destination identity identifier is queried in the common address mapping table, the access service node forwards the data packet according to the destination location identifier; The destination location identifier corresponding to the destination identity is not found in the table, and the access service node interacts with the mapping server to forward data packets.

Preferably, the method further includes: configuring the common address mapping table by the system, or periodically updating the common address mapping table according to a broadcast of the mapping server.

Preferably, after the step of the access service node receiving the data packet, before the step of the access service node querying the common address mapping table according to the destination identity identifier in the data packet, the method further includes: Querying the address mapping table learned in the local cache, if the destination location identifier corresponding to the destination identity identifier is not found, performing the access service node according to the destination identity identifier in the data packet The steps of the address mapping table.

Preferably, before the step of performing the data packet forwarding by the access service node and the mapping server, the method further includes: querying the address mapping table learned in the local cache, if the destination corresponding to the destination identity identifier is not found And performing the step of performing the data packet forwarding by the access service node and the mapping server.

Preferably, the step of the access service node interacting with the mapping server to forward data packets includes:

The access service node forwards the packet to the mapping server of the mapping forwarding plane; the mapping server queries the address mapping table to obtain the destination location identifier corresponding to the destination identity identifier, and then the root Decoding and forwarding the data packet according to the destination location identifier; or

The access service node requests the mapping server to obtain a destination location identifier corresponding to the destination identity identifier; after the mapping server queries the address mapping table, returns the queried destination location to the access service node. The access service node implements encapsulation and forwarding of data packets according to the obtained destination location identifier.

To solve the above technical problem, the present invention further provides an access service node, where the access service node is located in an identity location separation network, and includes:

a packet receiving module, configured to receive a data packet, where the data packet includes a destination identity identifier;

a commonly used address mapping table, which is configured to save a mapping relationship between a commonly used identity identifier and a location identifier; a location identifier obtaining module that is connected to the packet receiving module and the common address mapping table, and is configured to: according to the data The destination identity identifier in the packet is used to query the common address mapping table to obtain a destination location identifier corresponding to the destination identity identifier, or obtain a destination location identifier corresponding to the destination identity identifier from the mapping server;

And a packet forwarding module, configured to be connected to the location identifier obtaining module, and configured to forward the data packet according to the destination location identifier corresponding to the destination identity identifier in the received data packet.

Preferably, the common address mapping table is configured by a system

Preferably, the access service node further includes a mapping relationship maintenance module that is connected to the common address mapping table, where the mapping relationship maintenance module is configured to update the common address mapping according to an address mapping relationship broadcast by the mapping server. table.

Preferably, the access service node further includes a mapping relationship cache module connected to the location identifier obtaining module, where

The mapping relationship cache module is configured to: learn and cache a mapping relationship between the destination location identifier obtained by the location identifier obtaining module from the mapping server and the corresponding destination identity identifier, and learn and cache the identity identifier of the source end in the data packet. a mapping relationship with a location identifier;

The location identifier obtaining module is further configured to: query the mapping relationship cache module to obtain a destination location identifier corresponding to the destination identity identifier. To solve the above technical problem, the present invention further provides another access service node, where the access service node is located in an identity location separation network, and includes:

a commonly used address mapping table, which is configured to save a mapping relationship between a commonly used identity identifier and a location identifier; a local location identifier query module, which is connected to the packet receiving module and the common address mapping table, and configured to be based on the data The destination identity in the message queries the commonly used address mapping table;

And a packet forwarding module, configured to connect to the local location identifier query module, and configured to forward the data packet according to the query result of the local location identifier query module.

Preferably, the >3⁄4 text forwarding module is configured to: if the query result of the local location identifier query module is that the destination location identifier corresponding to the destination identity identifier is obtained, implementing the Encapsulating and forwarding the data packet; if the query result of the local location identifier query module is that the destination location identifier corresponding to the destination identifier is not obtained, forwarding the data packet to the mapping server.

Preferably, the access service node further includes a mapping relationship maintenance module connected to the common address mapping table, wherein the mapping relationship maintenance module is configured to update the common address mapping table according to an address mapping relationship broadcast by the mapping server.

Preferably, the access service node further includes a mapping relationship cache module connected to the local location identifier query module, where

The mapping relationship cache module is configured to: learn and cache a mapping relationship between the identity identifier of the source end and the location identifier in the data packet;

The local location identifier query module is further configured to: query the mapping relationship cache module to obtain a destination location identifier corresponding to the destination identity identifier.

The address mapping method and the access service node of the present invention configure a common address mapping table. After receiving the data packet sent by the terminal, if the destination identity of the data packet can be found in the table, the access service node can locally The destination location identifier of the packet is found without having to map the server query, thereby reducing data traffic between the access service node and the mapping server. BRIEF abstract

1 is a schematic diagram of a network topology of an identity location separation architecture according to the present invention;

2 is a schematic flow chart of an address mapping method of the present invention;

3 is a schematic flowchart of a specific implementation manner of an address mapping method according to the present invention;

4 is a schematic structural diagram of an implementation manner of an access service node according to the present invention;

FIG. 5 is a schematic structural diagram of still another embodiment of an access service node according to the present invention.

Preferred embodiment of the invention

The address mapping method of the present invention and the main idea of the access service node are: establishing a common address mapping table in the access service node of the identity location separation network, and querying the common address mapping table when forwarding the packet, when not queried Then, according to the normal destination location identification acquisition method.

The identifier of the present invention refers to an identifier for identifying the identity information of the terminal, and is not limited to the URL of the application layer, FQDN, IPNL, TRIAD (A Scalable Deployable NAT-based Internet Architecture) or IP address. The location identifier refers to an identifier for identifying routing information of the terminal, which is also not limited to an IP address.

The commonly used address mapping table in the present invention stores mapping relationships between identity identifiers and location identifiers that are commonly used, public, or infrequently changed, such as the identity location mapping relationship of some portal websites.

There are various network-based identity location separation architectures (hereinafter referred to as the architecture), and one of the architectures will be described below in conjunction with FIG. As shown in Figure 1, the network is divided into an access layer and a core layer, and each user in the network is assigned a unique identity AID, which remains unchanged during the mobile process; there are two types of identifiers in the network. Type: Identity AID and Location ID RID, where the identity AID can only be used at the access layer, and the location ID RID can only be used at the core layer.

The topology of this architecture is shown in Figure 1. Under this framework, the network is divided into an access network 110 and a backbone network 120. The access network 110 is located at the edge of the backbone network 120 and is responsible for access of all terminals. The backbone network 120 is responsible for routing of terminals accessed through different access networks 110. The access service node 130 is located at a demarcation point of the backbone network 120 and the access network 110, interfaces with the access network 110, and interfaces with the backbone network 120. The access network 110 and the backbone network 120 do not overlap in the topology relationship. Communication between user terminals The letter only needs to be carried out using the identity of the peer. The access service node 130 provides access services for the terminal, maintains user connections, and forwards user data.

The backbone network of the architecture is divided into two planes: a mapping forwarding plane 121 and a generalized forwarding plane 122.

The main function of the generalized forwarding plane 122 is to select and forward data packets according to the location identifier RID in the data packet. The data routing and forwarding behavior in the generalized forwarding plane 122 is consistent with the Legecy IP network.

The main function of the mapping forwarding plane is to save the mapping information of the mobile node's identity location, process the registration process of the mobile node, process the location query process of the communication peer, and route and forward the data packet with the identity identifier AID as the destination address.

The main network elements and functional entities of this architecture include:

Access Service Node (ASN) 130: The ASN 130 maintains the connection relationship between the terminal and the network, assigns the RID to the terminal, processes the handover process, processes the registration process, processes the accounting/authentication process, and maintains/queries the communication. The AID-RID mapping relationship of the peer end, and encapsulation, routing, and forwarding to the data message sent by the terminal or the terminal.

In the architecture network of FIG. 1, if the ASN 130 receives the data packet sent by the terminal (MN), it queries the AID-RID mapping table in the local cache according to the AIDc of the destination address communication end (CN) in the data packet. The corresponding AIDc-RIDc mapping entry is found, and the RIDc is encapsulated in the packet header as the destination address, and the RIDm corresponding to the MN source address AIDm is encapsulated in the packet header and forwarded to the generalized forwarding plane 122; The corresponding AIDc-RIDc mapping entry is not found, and the data packet is tunnel encapsulated and then forwarded to the mapping forwarding plane 121, and the flow of querying the AIDc-RIDc mapping relationship is sent to the mapping forwarding plane 121.

When receiving the data packet sent by the network to the terminal, the ASN 130 decapsulates the data packet, strips the RID encapsulation of the data packet header, and retains the AID as a data packet header to be sent to the terminal.

Common Router (Core for short): Routes and forwards data packets with the source address/destination address in the RID format. The function of this general purpose router is no different from that of the prior art routers.

Identity Location Register/Packet Transfer Function (referred to as ILR), maintains/saves the AID-RID mapping relationship of users in the network of this architecture, so it is also called mapping server. Implement the registration function and process the location query process of the communication peer. The Broke ILR is mainly used to signal the signaling between transit ILRs when there is no direct relationship between the ILR and the home ILR.

Packet Forwarding Function (PTF): After receiving the data packet sent by the ASN 130, the mapping forwarding plane 121 routes and forwards the PTF according to the destination AID in the mapping forwarding plane. After the PTF node in the mapping forwarding plane 121 finds the mapping relationship of the destination AID-RID, it encapsulates the corresponding RID information in the data packet header and forwards it to the generalized forwarding plane 122, which is routed by the generalized forwarding plane 122 and forwarded to the communication peer. .

Certification Center: The Certification Center is responsible for recording the user attributes of the network, including user categories, authentication information, and user service levels, and generating user security information for authentication, integrity protection, and encryption. Access control and authorization. The certificate authority supports two-way authentication between the terminal and the network.

In an identity-based location separation architecture, the identity AID of the end user remains the same. Location ID The RID indicates the location of the ASN where the current terminal is located. When the terminal user accesses the network, the authentication center authenticates the authenticity of the identity, and the mapping server saves the AID-RID mapping relationship of each node. The access network partially distinguishes the different nodes from the identity identifier AID. The generalized switching plane uses RID to route data packets. To establish an end-to-end communication process, the identity identifier AID is used to find the corresponding user location identifier RID.

The technical solution of the present invention will be described in more detail below with reference to the accompanying drawings and embodiments.

The address mapping method of the present invention is implemented based on an identity location separation network. The access service node is provided with a common address mapping table, which includes a mapping relationship between a common identity identifier and a location identifier.

The common AID-RID mapping table of the access service node is written from the configuration file when the access service node is powered on, and needs to be updated during the operation of the access service node. The update manner is as follows:

The mapping server periodically broadcasts a common AID-RID mapping table to all access service nodes in the network, and the access service node updates its common AID-RID mapping table after receiving it.

In the AID-RID mapping table of the buffer of the access service node, if some entries are used frequently, they can be added to the common AID-RID mapping table of the access service node.

As shown in FIG. 2, the address mapping method of the present invention includes:

201: The access service node receives a data packet, where the destination identity identifier is included; 202: The access service node queries the common address mapping table according to the destination identity identifier in the data packet.

203: If the corresponding destination location identifier is queried in the common address mapping table, the access service node forwards the data packet according to the destination location identifier; otherwise, the data packet is forwarded by the mapping server.

Step 203 is: if the destination location identifier corresponding to the destination identity identifier is queried in the common address mapping table, the access service node forwards the data packet according to the destination location identifier; The destination location identifier corresponding to the destination identifier is not queried in the common address mapping table, and the access service node interacts with the mapping server to forward data packets.

Generally, the access service node has the function of buffering the learning address mapping table. In the end-to-end communication process, the local identity AID needs to be carried as a source address in the data packet to the communication peer. The access service node of the communication peer can obtain the mapping relationship between the identity identifier and the location identifier of the source end from the source address carried in the data packet, and can also obtain the mapping relationship between the identity identifier and the location identifier of the destination end according to the feedback of the mapping server. Called address learning, the learned AID-RID mapping relationship is maintained in the local buffer of the peer access service node.

Before interacting with the mapping server, query the common address mapping table and the cache address mapping table to reduce the interaction between the access service node and the mapping server. The following two sequences can be used:

1. Before accessing the common address mapping table, the access service node first queries the address mapping table learned in the local cache. If the destination location identifier is not found, the common address mapping table is queried.

2. If the access service node does not query the corresponding destination location identifier in the common address mapping table, first query the address mapping table learned in the local cache, and if the destination location identifier is not found, then The mapping server obtains the destination location identifier.

The access service node interacts with the mapping server to perform packet forwarding. The following two implementation modes are implemented: Method 1, based on the architecture shown in Figure 1, the access service node forwards the packet to the mapping server of the mapping forwarding plane, and then The mapping server queries the AID-RID mapping table to obtain the destination RID, and the mapping server implements packet encapsulation and forwarding of the packet.

In the second manner, the access service node requests the mapping server to obtain the RID corresponding to the destination AID, and after the mapping server queries the AID-RID mapping table, returns the destination RID to the access service node, and then connects The ingress service node implements packet encapsulation and forwarding.

Specific embodiment 1

The following is a description of the specific implementation manner of the present invention by using the following two steps:

Step 301: The access service node receives the data packet sent by the terminal user M, where the identity identifier AIDm of the user M and the identity identifier AIDn of the peer user N are included;

Step 302: The access service node searches the AID-RID mapping table in the buffer. If there is an AIDn entry, the destination location identifier RIDn is used as the destination address of the data packet, and the data packet is sent. Otherwise, Go to step 303;

Step 303: The access service node searches for a common AID-RID mapping table. If there is an AIDn entry, the destination location identifier RIDn is used as the destination address of the data packet, and the data packet is sent, otherwise step 304 is performed;

Step 304: The access service node searches for the AID-RID mapping table of the mapping server, and then uses the found destination location identifier RIDn as the destination address of the data packet, and sends the data packet.

Correspondingly, if the access mode 1 is used, if the access service node finds the corresponding AIDn-RIDn mapping entry in the common address mapping table or the local cache, the RIDn is encapsulated in the packet header as the destination address, and the M source address is used. The RIDm corresponding to the AIDm is encapsulated in the packet header and forwarded to the generalized forwarding plane. Otherwise, the data packet is tunnel encapsulated and then forwarded to the mapping server of the mapping forwarding plane. The mapping between the forwarding plane and the AIDn-RIDn is mapped. Then, the corresponding RIDn information is encapsulated in the data packet header and forwarded to the generalized forwarding plane, which is routed by the generalized forwarding plane and forwarded to the communication peer.

Specific embodiment 2

To implement the method for forwarding the packet between the access service node and the mapping server, the present invention provides an access service node, where the access service node is located in an identity location separation network. As shown in FIG. 4, the access service node includes:

The message receiving module 410 is configured to receive a data packet, where the destination identifier is included, and the location identifier obtaining module 420 is connected to the packet receiving module 410, according to the The destination identity identifier in the data packet queries the common address mapping table 440 or obtains the destination location identifier corresponding to the destination identity identifier from the mapping server, and notifies the packet forwarding module 430;

The message forwarding module 430 is connected to the location identifier obtaining module 420, and configured to forward the data packet according to the destination location identifier corresponding to the destination identity identifier in the received data packet.

The common address mapping table 440 is connected to the location identifier obtaining module 420 for storing a common address mapping relationship.

The common address mapping table 440 is configured by the system.

The mapping relationship maintenance module 450 is connected to the common address mapping table 440, and is configured to update the common address mapping table 440 according to a common address mapping relationship broadcast by the mapping server.

The mapping relationship cache module 460 is connected to the location identifier obtaining module 420, and is configured to learn and cache the mapping relationship between the destination location identifier obtained by the location identifier obtaining module 420 and the corresponding destination identity identifier, and learn and cache the datagram. a mapping relationship between the identity identifier and the location identifier of the source end; the location identifier obtaining module 420 queries the mapping relationship cache module 460 and the common address mapping table 440 before obtaining the destination location identifier from the mapping server, When the corresponding destination location identifier is not queried, it is obtained from the mapping server.

Embodiment 3

In order to implement the packet forwarding method, the access service node is located in the identity location separation network shown in FIG. 1 . As shown in FIG. 5, the access service node includes:

The message receiving module 510 is configured to receive a data packet, where the destination identity identifier is included, and the local location identifier querying module 520 is connected to the packet receiving module 510, and configured to perform the query according to the destination identity identifier in the data packet. The address mapping table 540 is commonly used, and the message forwarding module 530 is notified;

The message forwarding module 530 is connected to the local location identifier query module 520, and configured to forward the data file according to the query result of the local location identifier query module 520. Specifically, the method may be: when the destination location identifier is obtained, the data packet is forwarded according to the destination location identifier, and the data packet is forwarded to the mapping server; The result of the query is that the destination location identifier corresponding to the destination identity is obtained, then the root And performing the encapsulation and forwarding of the data according to the destination location identifier; if the query result of the local location identifier query module is that the destination location identifier corresponding to the destination identifier is not obtained, the datagram is Forward to the mapping server;

The common address mapping table 540 is connected to the local location identifier query module 520 for saving a common address mapping relationship.

The mapping relationship maintenance module 550 is connected to the common address mapping table 540, and is configured to update the common address mapping table 540 according to a common address mapping relationship broadcast by the mapping server.

The mapping relationship cache module 560 is connected to the local location identifier query module 520, and is configured to learn and cache the mapping relationship between the identity identifier and the location identifier of the source end in the data packet. The local location identifier query module 520 notifies the forwarding Before forwarding the data packet, the module 530 queries the mapping relationship cache module 560 and the common address mapping table 540 to notify the packet forwarding module 530 to forward the data packet when the corresponding destination location identifier is not queried.

The address mapping method and the access service node of the present invention configure a common address mapping table. After receiving the data packet sent by the terminal, if the destination identity of the data packet can be found in the table, the access service node can locally The destination location identifier of the packet is found without having to map the server query, thereby reducing data traffic between the access service node and the mapping server.

Industrial applicability

The address mapping method and the access service node of the present invention configure a common address mapping table, and after the access service node receives the data packet sent by the terminal, if the destination identity of the data packet can be found in this table, it is locally The destination location identifier of the packet can be found without having to map the server query, thereby reducing the data traffic between the access service node and the mapping server.

Claims

Claim

An address mapping method, wherein the method is implemented based on an identity location separation network, and the access service node is provided with a common address mapping table, where the common address mapping table includes mappings of commonly used identity identifiers and location identifiers. Relationship; the method includes:

2. The method of claim 1, further comprising: configuring the common address mapping table by the system, or periodically updating the common address mapping table according to a broadcast of the mapping server.

The method according to claim 1, wherein after the step of receiving the data packet by the access service node, the access service node queries the commonly used one according to the destination identity identifier in the data packet. Before the steps of the address mapping table, it also includes:

Querying the address mapping table learned in the local cache, if the destination location identifier corresponding to the destination identity identifier is not found, performing the access service node according to the destination identity identifier in the data packet The steps of the address mapping table.

The method of claim 1, wherein before the step of the access service node and the mapping server interacting with the data packet, the method further includes:

Querying the address mapping table learned in the local cache, if the destination location identifier corresponding to the destination identifier is not found, performing the step of the access service node interacting with the mapping server to forward the data packet.

The method according to any one of claims 1 to 4, wherein the step of the access service node interacting with the mapping server to forward the data packet comprises:

6. An access service node, located in an identity location separation network, and comprising:

7. The access service node according to claim 6, wherein the common address mapping table is configured by a system.

The access service node of claim 6, further comprising a mapping relationship maintenance module connected to the common address mapping table, wherein the mapping relationship maintenance module is configured to update according to an address mapping relationship broadcast by the mapping server. The common address mapping table.

The access service node of claim 6, further comprising a mapping relationship cache module connected to the location identifier obtaining module, where

The location identifier obtaining module is further configured to: query the mapping relationship cache module to obtain a destination location identifier corresponding to the destination identity identifier.

An access service node, which is located in an identity location separation network, and includes: a message receiving module, configured to receive a data packet, where the data packet includes a destination identity identifier;

The access service node according to claim 10, wherein the packet forwarding module is set to:

If the query result of the local location identifier query module is that the destination location identifier corresponding to the destination identifier is obtained, the packet forwarding of the data packet is implemented according to the destination location identifier; if the local location identifier is queried If the query result of the module is that the destination location identifier corresponding to the destination identifier is not obtained, the data packet is forwarded to the mapping server.

The access service node according to claim 10 or 11, further comprising a mapping relationship maintenance module connected to the common address mapping table, wherein the mapping relationship maintenance module is configured to update according to an address mapping relationship broadcast by the mapping server. The common address mapping table.

The access service node according to claim 10 or 11, further comprising a mapping relationship cache module connected to the local location identifier query module, where

The mapping relationship cache module is configured to learn and cache a mapping relationship between the identity identifier of the source end and the location identifier in the data packet;

The local location identifier query module is further configured to query the mapping relationship cache module to obtain a destination location identifier corresponding to the destination identity identifier.