CN106792657B

CN106792657B - A kind of network identity method and device for supporting identity and position to decouple

Info

Publication number: CN106792657B
Application number: CN201710003651.XA
Authority: CN
Inventors: 陈山枝; 胡博; 邢琳; 王颖
Original assignee: China Academy of Telecommunications Technology CATT
Current assignee: China Academy of Telecommunications Technology CATT; Datang Mobile Communications Equipment Co Ltd
Priority date: 2017-01-03
Filing date: 2017-01-03
Publication date: 2019-09-17
Anticipated expiration: 2037-01-03
Also published as: CN106792657A

Abstract

This application discloses a kind of network identity method and devices for supporting identity and position to decouple.This method comprises: receiving network insertion request；Network node identity is specified when networking, the network node according to network insertion request for request access distributes station location marker；MA is introduced, MA maintenance identity map table carrys out the map information of buffer network node identities mark and station location marker, and is responsible for the conversion of identity and station location marker in data transmission procedure；Introduce DMS, one side DMS maintains mapping table in domain, cached the title of network node, the identity of node, the address of the local anchor point of node, node be currently accessed anchor point address and node before access the list of anchor point address, another aspect DMS maintains mapping table between domain, the number of the DMS in local domain, reduces the time delay in data transmission procedure where node can be inquired by mapping table between domain.By MA and DMS, identity map resolving is realized, guarantee the continuity communicated in moving process.

Description

Network identification method and device supporting identity and position decoupling

Technical Field

The present application relates to the field of communications technologies, and in particular, to a network identification method and apparatus supporting identity and location decoupling.

Background

With the development of the mobile internet, the characteristics of the traditional internet still exist in the communication process of the existing mobile network, namely, the IP address is used as the identity identifier of the node to be bound with the high-level session, and is also used as the position identifier of the node to perform routing and forwarding of the data packet, and the dual semantics are realized.

In order to solve the ambiguity problem of the IP address, the industry provides the idea of separating the identity from the position, and separates the identity identifier and the position identifier of the node, thereby ensuring the independence of an upper layer protocol and supporting the flexibility of a network layer protocol.

After the identity is separated from the position, the communication process is realized by depending on an identifier mapping analysis mechanism to complete the mapping and analysis between the identity identifier and the position identifier.

Disclosure of Invention

The embodiment of the application also provides a network identification method and device supporting identity and position decoupling.

The embodiment of the application provides a network identification method supporting identity and location decoupling, which is applied to a communication system comprising a DMS and an MA, and comprises the following steps: receiving a network access request sent by a first network node by the MA; the MA judges whether the MA is a home MA of a first network node, wherein if the identity of the first network node is in the address range of the MA, the MA is the home MA of the first network node, otherwise, the MA is not the home MA of the first network node; if the MA is not the home MA of the first network node, performing the following operations:

sending a position request message to a DMS of a local management domain; receiving a location response message returned by the DMS according to the location request message, wherein the location response message carries a location identifier distributed by a location identifier pool for the first network node; and maintaining an identification mapping entry of the first network node according to the received position response message, wherein the identification mapping entry of the first network node comprises the identity identification and the position identification of the first network node.

The embodiment of the application provides a network identification method supporting identity and location decoupling, which is applied to a communication system comprising a DMS and an MA, and comprises the following steps: the method comprises the steps that a DMS receives a position request message sent by a first MA of a local management domain, wherein the first MA is a visiting MA of a first network node, and the position request message is sent by the first MA according to a request of the first network node for accessing the visiting MA; the DMS executes the following operations according to the position request message:

requesting a location identifier pool to allocate a location identifier for a first network node; maintaining an intradomain mapping entry for a first network node, the intradomain mapping entry for the first network node for storing: the method comprises the steps that the identity of a first network node, the address of a home MA of the first network node, the address of a MA currently accessed by the first network node and the address list of the MA previously accessed by the first network node are preset; sending a location response message carrying a location identifier of a first network node to the first MA to trigger the first MA to maintain an identifier mapping entry of the first network node, wherein the identifier mapping entry of the first network node comprises an identity identifier and a location identifier of the first network node; and sending a location updating notification message to the MA accessed last time by the first network node and the home MA, wherein the location updating notification message is used for indicating that the identification mapping item of the first network node is updated.

An embodiment of the present application provides a mobility anchor device, which is applied to a communication system including a DMS and an MA, where the MA includes: the first interface module is used for receiving a network access request sent by a first network node; a processing module, configured to determine whether the mobile anchor MA is a home MA of a first network node, and if not, instruct a second interface module to request to acquire a location identifier of the first network node and instruct a mapping table maintenance module to maintain an identifier mapping entry in an identifier mapping table, where if the identity identifier of the first network node is within an address range of the MA, the MA is the home MA of the first network node, and otherwise, the MA is not the home MA of the first network node; the second interface module is used for sending a position request message to a DMS of a local management domain; receiving a location response message returned by the DMS according to the location request message, wherein the location response message carries a location identifier distributed by a location identifier pool for the first network node; and the mapping table maintenance module is used for maintaining the identifier mapping entries of the first network node according to the received position response message, wherein the identifier mapping entries of the first network node comprise the identity identifiers and the position identifiers of the first network node.

An embodiment of the present application provides a domain mapping server, which is applied to a communication system including a DMS and an MA, where the DMS includes: a receiving module, configured to receive a location request message sent by a first MA of a local management domain, where the first MA is a visited MA of a first network node, and the location request message is sent by the first MA according to a request for accessing the visited MA by the first network node; the identifier distribution module is used for requesting the location identifier pool to distribute the location identifier for the first network node according to the location request message; a mapping table maintaining module, configured to maintain, according to the location request message, an intra-domain mapping entry of the first network node, where the intra-domain mapping entry of the first network node is used to store: the method comprises the steps that the identity of a first network node, the address of a home MA of the first network node, the address of a MA currently accessed by the first network node and the address list of the MA previously accessed by the first network node are preset; a sending module, configured to send a location response message carrying a location identifier of a first network node to the first MA, so as to trigger the first MA to maintain an identifier mapping entry of the first network node, where the identifier mapping entry of the first network node includes an identity identifier and a location identifier of the first network node; and sending a location update notification message to the last access MA and the home MA of the first network node, wherein the location update notification message is used for indicating to update the identification mapping entry of the first network node.

An embodiment of the present application provides a communication device, including: a network interface, a processor, and a memory; the memory to store computer program instructions; the processor, coupled to the memory, is configured to read the computer program instructions stored in the memory and execute the method of the MA in the above embodiments.

Another communication device provided in an embodiment of the present application includes: a network interface, a processor, and a memory; the memory to store computer program instructions; the processor, coupled to the memory, is configured to read the computer program instructions stored by the memory and execute the method of the DMS in the above embodiments.

Drawings

FIG. 1 is a schematic diagram of a network architecture suitable for use in embodiments of the present application;

fig. 2 is a schematic diagram of data transmission flow after MN1 accesses a home network in this embodiment;

fig. 3 is a schematic diagram of a network access flow when MN1 switches from MA1 to MA2 in this embodiment of the present application;

fig. 4A and 4B are schematic diagrams illustrating a data transmission flow when the MN1 accesses the MA2 according to an embodiment of the present application, respectively;

fig. 5 is a flowchart illustrating a handover of MN1 from MA2 back to home network MA1 in the embodiment of the present application;

fig. 6 is a schematic diagram of a network access flow when MN1 switches from MA2 to MA3 in this embodiment of the present application;

fig. 7A and fig. 7B are schematic diagrams illustrating a data transmission flow when MN1 accesses MA3 in this embodiment of the present application, respectively;

fig. 8 is a network access flow diagram of MN1 switching from MA3 to MA4 in the embodiment of the present application;

fig. 9A and 9B are schematic diagrams illustrating a data transmission flow when MN1 accesses MA4 in this embodiment of the present application, respectively;

fig. 10A and 10B are schematic diagrams illustrating a data transmission flow when MN1 accesses MA4 according to an embodiment of the present application, respectively;

fig. 11 is a schematic structural diagram of a domain mapping server according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of a mobility anchor device according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of a communication device according to another embodiment of the present application;

fig. 14 is a schematic structural diagram of a communication device according to another embodiment of the present application.

Detailed Description

The embodiment of the invention provides a network identifier mapping scheme and a data transmission scheme for supporting identity and position decoupling of a network layer based on the requirement of identity and position decoupling of the network layer. The network identification may include identity identification and location identification, and may be in the form of an IPv6 address. The identity mark is appointed for the network node by a home network to which the network node belongs, and is bound with the high-level session as the identity mark of the network node; the location identity is assigned by the visited network of the network node for routing and forwarding of data.

In the embodiment of the present application, the full-network mapping entries are distributed and stored in a Domain Mapping Server (DMS), and a Mobility Anchor (MA) caches and updates the identifier mapping entries of the network node identifiers and the location identifiers in the Domain, and is responsible for performing conversion between the identifiers and the location identifiers for encapsulation of data packets in a data transmission process. The embodiment of the application can realize the identifier mapping analysis process, efficiently complete the updating synchronization and the mapping analysis of the identity identifier and the position identifier, and effectively support the service continuity in the moving process. The analysis and mapping process provided by the embodiment of the application is transparent to the network node, and has good compatibility with the IPv6 protocol and the IPv6 address.

The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

In the embodiment of the present application, a DMS and a MA are deployed in a network architecture. The number of DMS and the number of MA may be determined according to the size of the network size. For ease of management, the network may be domain partitioned, i.e. may be partitioned into a plurality of domains, with at least one DMS and at least one MA deployed in each domain. The partitioning of the domains may be based on geographic location or network topology, etc. An MA within one domain communicates with a DMS within that domain, and DMS of different domains may communicate with each other. Typically, one DMS and a plurality of MAs may be deployed within one domain. Further, in order to improve reliability, a plurality of DMS may also be deployed in one domain, and the DMS deployed in one domain may cooperate in a load sharing manner or in a main-standby manner.

Fig. 1 exemplarily shows a typical network architecture in the embodiment of the present application, which only shows DMS and MA within 3 domains. As shown in the figure, DMS1, DMS2, and DMS3 are domain mapping servers of each domain, MA1, MA2, and MA3 are mobility anchor points in the domain where DMS1 is located, MA4 is a mobility anchor point in the domain where DMS2 is located, and MA-CN is a mobility anchor point in the domain where DMS3 is located. The MA may communicate with a DMS within the home domain. In the domain where the DMS1 is located, the MA1, MA2, and MA3 are located in different access networks, respectively, as shown in the figure, for a network Node, such as a Mobile Node (MN) 1, an access network where the MA1 is located is a home network of the MN1, and access networks where the MA2 and the MA3 are located are visited networks of the MN 1.

The MA function is deployed at the access routing layer, closer to the MN. The MA expands the function of the access router, can maintain mapping entries (referred to as identification mapping entries in the embodiment of the application) between the identity identifiers and the location identifiers of the related network nodes in the data transmission process, and encapsulates the outer layer of the data packet between the identity identifiers and the location identifiers according to the identification mapping entries to convert, so that the identification decoupling process is transparent to the network nodes. The MA may also perform mobility-related signaling instead of the network node (e.g., MN), making the mobility management procedure transparent to the network node. For example, when the MN moves to an access network, the MA of the network sends an address request signaling instead of the MN, and the last MA accessed by the MN and the home MA receive the mapping update signaling of the DMS, so that the MA currently accessed by the MN and the last MA accessed by the MN and the home MA maintain an identification mapping entry between the identity and the location of the MN, so as to convert the identity encapsulated by the packet header into the location identity during data transmission, and the like. In deployment, optionally, the location identity assigned to the MN is maintained by the MA and need not be sent to the MN.

The MA maintains the maintained identification mapping entries may employ a data structure identifying a mapping table, as shown in table 1, which may be configured on the MA. The identification mapping entry of a network node includes an identity of the network node and a location identification of the network node, and further may also include a name or an ID of the network node (the ID of the network node may be information capable of identifying the network node, such as a network node number). Taking the network node as an MN as an example, an identifier mapping entry of an MN includes an identity identifier of the MN and a location identifier of the MN.

Table 1: data structure maintained by MA for identifying mapping table

Node name	Node identity	Node location identification

When the MN accesses the home network, the MA of the home network creates an identification mapping item of the MN in an identification mapping table; when the MN performs network switching (such as switching from a home network to a visited network, or switching from a visited network to a home network, or switching between different visited networks), the MN's identification mapping entry is updated.

The DMS is mainly used to provide an identification query service for the MA in the domain. To this end, the DMS maintains domain-mapping entries of the network nodes, where the domain-mapping entry of a network node includes an identity of the network node and information (such as an address of a MA) of the MA accessed by the network node, and further may include a name or an ID of the network node. Specifically, the intra-domain mapping entry of a network node may include the identity of the network node, the address of the home MA of the network node, the address of the MA currently accessed by the network node, and the address of the MA last accessed by the network node. The mapping entries of the network nodes may be stored as data structures of an intra-domain mapping table as shown in table 2. The intradomain map may be configured on the DMS.

Table 2: data structure of intradomain mapping table maintained by DMS

When a network node accesses a home network, a DMS assigns an identity for the network node and creates an intra-domain mapping entry of the network node in an intra-domain mapping table; when the MN performs network handover (for example, handover from a home network to a visited network, or handover from a visited network to a home network, or handover between different visited networks), the DMS initiates a request to allocate a location identifier to the network node to a network identifier pool (vLoc pool), and updates an intra-domain mapping entry of the network node in the intra-domain mapping table, and indicates that the last MA accessed by the network node and the home MA of the network node update an identifier mapping entry of the network node in the identifier mapping table.

Further, the DMS may also maintain an inter-domain mapping table, which may be configured on the DMS. The stored content of the DMS inter-domain mapping table may mainly include [ DMS-ID, a region belonging to the identity of the DMS domain ], so that querying the inter-domain mapping table according to the identity of the network node can determine the DMS storing the identity, i.e. the home DMS of the network node can be found.

The identity in the embodiment of the invention can be uniquely specified when the network node accesses the network, and is not reused, and the network node has the unique identity in the whole network; in the home network, the location identity of the network node is the same as the identity. When the network node moves to the visited network, a location identity is assigned by the visited network based on the pool of network identities. The location identity of a network node varies with changes in the network access point, and the location identity of a network node may be globally routable.

As mentioned above, the identity of the network node may be pre-specified, i.e. the identity may be pre-specified for the network node, e.g. identification information for uniquely identifying the network node may be pre-bound with an identity. Taking the network node as a mobile phone as an example, when the mobile phone performs network access registration of an operator, when a Subscriber Identity Module (SIM) card is issued, an identity (IPv6 address form) can be pre-allocated, and the identity is bound with the SIM card number (the SIM card number is used for uniquely identifying the SIM card). Taking the network node as a fixed telephone as an example, when the fixed telephone performs the operator network entry registration and issues a fixed telephone number, an identity (in the form of an IPv6 address) can be pre-assigned and bound with the telephone number. When a network node accesses a home network, the DMS sends an identity assigned to the network node. Compared with the method for distributing the identity identification based on the network identification pool, the embodiment of the invention can ensure the stability of the identity identification of the network node.

In order to distinguish the type of the network identifier (i.e. the identity identifier or the location identifier), in the embodiment of the present invention, a network identifier type information field may be set in the network identifier, and the network identifier is the identity identifier or the location identifier according to different values of the information field.

Taking the network identifier as an IPv6 address form as an example, the length of the IPv6 address is 128 bits, where:

the 'access address prefix' occupies n bits and is allocated by a superior Regional Internet registration structure (RIR) RIR or an Internet Provider (ISP for short);

the routing prefix address block occupies m bits, and operators can reasonably encode and record the routing prefix address block with the m bits according to self deployment planning and load conditions;

"interface identifier" is used to identify a specific interface within the network, occupying 64 bits;

the "subscriber subnet" is an identifier of the subnet within the site, occupying the remaining number of bits.

In some embodiments of the present application, a network type identifier information field is set in an m-bit "routing prefix address block", and the information field may occupy continuous or discontinuous T bits (T is an integer greater than or equal to 0). And identifying the IPv6 address as an identity identifier or a position identifier according to different values of the information field. Table 3 shows a network identification format.

Table 3: network identification format

Further, 2 of the network identification information field^TThe value is divided into at least a first part and a second part, the value of the first part is used as the indication of the identity identifier, and the value of the second part is used as the indication of the network identifier. The number of the first part and the number of the second part can be set according to a set proportion. The operator can determine how many values are used for indicating the identity identifier and how many values are used for indicating the location identifier in the values of the information field according to the self load conditions (such as the number of the mobile nodes and the number of the fixed nodes).

Taking T ═ 2 as an example, the "network identification type" information field with 2 bits length has 4 values (binary form): 00,01,10,11. In some commercial areas, the number of mobile nodes is large relative to that of fixed nodes, and the consumed location identifiers are large relative to the identity identifiers, in this case, the address with the value of 00 in the information domain can be used as the identity identifier, and the addresses with the values of 01,10 and 11 in the information domain can be used as the location identifiers; in a residential area, there are relatively many fixed nodes, and in this case, addresses with values of 00,01, and 10 of the information field may be used as the identity, and an address with value of 11 of the information field may be used as the location. The specific allocation may be as shown in table 4.

Table 4: "network identification type" information domain value distribution

As an example, as shown in table 5, the network identification in the form of an IPv6 address includes the following information fields:

an 'access address prefix' information field with the length of 24 bits, which is used for bearing the access address prefix distributed to the operator;

an 'addressing identifier' information field with the length of 9 bits is used for bearing access province identification, access type identification and the like and is defined by an operator; wherein, the access type can include: fixed network dynamic access, fixed network static access, mobile access, public service operation platform access and the like;

the information field of 8-bit length 'region and county coding' is used for bearing region and county coding;

the network identification type information field with the length of 2 bits is used for distinguishing the identity identification and the position identification through different values; furthermore, some values can be reserved and are not used for distinguishing the identity identifier and the position identifier, so that the ratio of the identity identifier and the position identifier can be adjusted or expanded and distributed by using the reserved values according to the actual requirements of the deployment condition of an operator;

a 21-bit-length 'user subnet' information field for carrying a subnet space identifier;

a 64-bit length "interface identification" information field for carrying an interface identifier.

The "addressing identifier" information field, "county coding" information field, and "network identification type" information field constitute a "routing prefix address block" in the IPv6 address.

Table 5: network identification format

It should be noted that the above structure of the network identifier is only an example, and the length and the position of the "network identifier type" information field are not limited to the description of this example.

In the data transmission process, the MA converts the destination identifier of the data packet and forwards the data packet according to the identifier mapping table, and triggers the DMS to notify the position identifier of the destination network node of the data packet in the current access network to the MA currently accessed by the source network node of the data packet, so that the MA currently accessed by the source network node uses the position identifier of the destination network node in the current access network to repackage the data packet and send the repackaged data packet.

In order to more clearly understand the above embodiments of the present application, an access procedure and a data transmission procedure of a network node are described below by taking the architecture shown in fig. 1 as an example. It should be understood that the implementation principles of the network node access procedure and the data transmission procedure described below may also be applied to other similar network architectures.

In the embodiment of the application, because the identity of the MN is specified, an identity mapping item can be configured for the MN in the identity mapping table of the MA in advance, and the identity mapping item can be updated subsequently according to the access condition of the MN; the domain mapping entry can also be configured for the MN in the domain mapping table of the DMS in advance, and the domain mapping entry is updated subsequently according to the access condition of the MN. The identity identifier of the MN is the same as the location identifier in the identifier mapping table of the MA in advance in configuring the identifier mapping entries for the MN, and in the intradomain mapping entries in the intradomain mapping table of the DMS in advance in configuring the intradomain mapping entries for the MN.

Taking MN1 as an example, table 6 shows an identification mapping entry of MN1 in an identification mapping table on home MA (MA1) of MN1 in advance, and table 7 shows an intra-domain mapping entry of MN1 in an intra-domain mapping table on DMS1 to which home MA of MN1 belongs in advance.

Table 6: identification mapping table of MA1

In table 6, Name-MN1 is the node Name of MN1, HID-MN1 is the id of MN1, the id and location of MN1 are the same, and the id of MN1 has the function of location identification.

Table 7: intradomain map of DMS1

In table 7, Name-MN1 is the node Name of MN1, HID-MN1 is the identity of MN1, the addresses of the home MA and the current access MA of MN1 are both IP-MA1, and the address list of the MA accessed before MN1 is empty.

When MN1 initially accesses home MA1, MN1 sends an access request message to MA 1. After receiving the access request message, the MA1 determines whether it is the home MA of the MN1, and if so, may further determine whether the identity and the location identity of the MN1 in the query identity mapping table are the same. In this example, since MN1 is the first access home MA, the identity and location identity of MN1 in the identity mapping table on MA1 are the same, in which case MA1 may not perform any further processing. In this step, the MA1 may determine whether the MA1 is the home MA of the MN according to the identity of the MN. Specifically, if the MN's identity is within the address range of MA1 (e.g., within the network segment where MA1 is located), then MA1 may be determined to be the home MA of the MN.

Referring to fig. 2, a schematic flowchart of sending data to an MN in a home network according to an embodiment of the present application is provided. Although the process is described by taking the example of MN1 accessing the home network, the access process can be applied to data transmission process of other network structures or other types of network nodes. As shown, the process may include the following steps:

step 201: the CN1 sends a packet to the MA-CN currently accessed by the CN1, the format of which is shown in table 8.

Table 8: data packet format sent by CN1

HID-CN1

HID-MN1

Data

The source identifier of the Data packet is the identifier HID-CN1 of CN (CN represents the opposite communication end), the destination identifier of the Data packet is the identifier HID-MN1 of MN1, and Data is the payload of the Data packet.

Step 202: after receiving the data packet, the MA-CN routes the data packet to the home MA1 of the MN1 according to the destination address HID-MN1 of the data packet.

Step 203: after receiving the data packet, the MA1 queries the identifier mapping table according to the destination identifier HID-MN1 of the data packet to obtain an identifier mapping entry < Name-MN1, HID-MN1, and HID-MN1> of MN1, and since the identity identifier and the location identifier in the identifier mapping entry are the same, the MA1 determines that MN1 is currently located in the home network, and therefore sends the data packet to MN 1.

Referring to fig. 3, a flowchart of switching an MN from a home network to a visited network is provided in the embodiment of the present application. Although fig. 3 describes the access of MN1 to the visited network as an example, the access procedure can be applied to the access procedure of other network architectures or other types of network nodes to the visited network.

When MN1 accesses home network through MA1, it is switched to visiting network by home network and accesses visiting network through MA 2. MA1, MA2 and DMS1 belong to the same domain. As shown, the process may include the following steps:

step 301: MN1 sends an access request message to MA2 requesting access to the visited network. The access request message carries the identity HID-MN1 of MN 1.

Step 302: after receiving the access Request message, MA2 determines that MA2 is not the home network of MN1, and therefore sends a Location Request message (Location Request message) to DMS1 in the local management domain to Request that MN1 be allocated with a Location identifier in the visited network. The Location Request message contains the identity of MN1, HID-MN 1.

Step 303: after receiving the Location Request message, DMS1 allocates a Location identifier in the visited network to MN1, and DMS1 returns a Location Response message (Location Response message) to MA2, where the Location identifier vLoc-MA2-MN1 in the visited network allocated to MN1 is carried. Further, DMS1 updates the in-domain mapping entries of MN 1.

In this step, after receiving the Location Request message, the DMS1 sends the Location Request message, which carries the identity of MN1, to a network identity pool (vLoc pool) to Request to allocate a network identity to MN 1; the vLoc pool selects an unused IPv6 address from the identification pool to allocate a location identification vLoc-MA2-MN1 for MN1, and sends the location identification vLoc-MA2-MN1 allocated for MN1 to MA2 through a location response message. The vLoc pool is a service module for location identity allocation and management, and may belong to two entities with the DMS, or may be deployed on the same entity.

DMS1 updates the mapping entries associated with MN1 in the intra-domain mapping table to: < Name-MN1, HID-MN1, IP-MA1, IP-MA2, IP-MA1 >. The address of the home MA of MN1 is IP-MA1, the address of the MA accessed by MN1 currently is IP-MA2, and the address of the MA accessed by MN1 last time is IP-MA 1. The updated intra-domain mapping table may be as shown in table 9.

Table 9: intradomain map of DMS1

Step 304: after receiving the Location Response message, the MA2 updates the identifier mapping entry of MN1 according to the Location identifier of MN1 carried therein, and may further return a Location Update Acknowledgement message to the DMS 1. The updated identification mapping entry of MN1 is: < Name-MN1, HID-MN1, vLoc-MA2-MN1 >. The updated identification mapping table may be as shown in table 10.

Table 10: identification mapping table of MA2

Step 305: DMS1 sends a Location update notification message to the home MA of MN1 and the last MA accessed, where the Location update notification message carries the identity of MN1, HID-MN1, and Location identity of MN1 in MA2, vLoc-MA2-MN1, so that the home MA of MN1 and the last MA accessed update the identity mapping entry of MN 1.

In this scenario, since the home MA of MN1 and the last MA are both MA1, DMS1 only needs to send Location Update Notification message to MA 1. If the home MA of the MN is different from the MA accessed last time, a Location Update Notification message needs to be sent to the home MA of the MN and the MA accessed last time respectively so as to inform the home MA of the MN and the MA accessed last time to Update the identification mapping table respectively.

Step 306: after receiving the Location Update Notification message, the MA1 updates the identifier mapping entry of MN1 according to the Location identifier of MN1 carried therein, and may further return a Location Update acknowledgement message to the DMS 1. The updated identification mapping entry of MN1 is: < Name-MN1, HID-MN1, vLoc-MA2-MN1 >. The updated identification mapping table may be as shown in table 12.

Table 11: identification mapping table of MA1

In the above flow, there is no strict timing requirement for some steps, for example, the order of step 304 and step 305 may be exchanged.

Referring to fig. 4A and 4B, a schematic flow chart of sending data to an MN located in a visited network according to an embodiment of the present application is provided. Although the flow is described by taking MN1 as an example, the access flow can be applied to data transmission processes of other network structures or other types of network nodes. As shown, the process may include the following steps:

step 401: the CN1 sends a packet to the MA-CN currently accessed by CN1, the format of which is shown in table 12.

Table 12: data packet format sent by CN1

HID-CN1

HID-MN1

Data

The source identifier of the Data packet is the identifier of the CN HID-CN1, the destination identifier of the Data packet is the identifier of MN1, HID-MN1, and Data is the payload of the Data packet.

Step 402: after receiving the data packet, the MA-CN routes the data packet to the home MA1 of the MN1 according to the destination address HID-MN1 of the data packet.

Step 403 a: after receiving the data packet, the MA1 queries the identifier mapping table according to the destination identifier HID-MN1 of the data packet, to obtain an identifier mapping entry < Name-MN1, HID-MN1, vLoc-MA2-MN1> of MN1, and since the identity identifier and the location identifier in the identifier mapping entry are different, the MA1 determines that MN1 has moved out of the home network, and therefore sends a notifiationrequest message to the DMS1, where the identity identifier HID-MN1 and the location identifier vLoc-MA2-MN1 of MN1 are carried, and the identity identifier HID-CN1 of CN1, thereby triggering the DMS to notify the access mobility anchor MA-CN of CN1 of the location identifier of MN1 in the currently accessed network.

Step 404 a: after receiving the Notification Request message sent by the MA1, the DMS1 queries the intra-domain mapping table according to the id of the CN1 carried in the message, i.e., the HID-CN 1. Because the intra-domain mapping table of DMS1 does not have the intra-domain mapping entry of CN1, DMS1 queries the inter-domain mapping table according to HID-CN1, and obtains home network DMS3 of CN 1; DMS1 sends a Notification Request message to DMS3, which may carry the identity of CN1, HID-CN1, and the identity of MN1, HID-MN1 and location identity vLoc-MA2-MN1 in the currently accessed network.

Further, upon receiving the Notification Request message sent by DMS1, DMS3 may return a Notification Response message to DMS1 (step 404 b). Further, upon receiving the Notification request message sent by MA1, DMS1 may return a Notification Response message to MA1 (step 403 b).

Step 405 a: after receiving the Notification Request message sent by the DMS1, the DMS3 queries the intra-domain mapping table according to the id of the CN1 carried in the message, to obtain intra-domain mapping entries < Name-CN1, HID-CN1, IP-MA-CN1, and IP-MA-CN 1- > of the CN1, where the address of the home MA of the CN1 and the address of the currently accessed MA are both IP-MA-CN 1; and the DMS3 sends a Location Update Notification message to the MA-CN currently accessed by the CN1 according to the inquired address of the MA-CN currently accessed by the CN1 in the mapping entry of the CN1, wherein the Location Update Notification message can carry the identity of the MN1, namely HID-MN1 and the Location identity of MN1, namely vLoc-MA2-MN 1.

Further, the MA-CN, upon receiving the Location Update Notification message sent by the DMS3, may return a Location Update Acknowledgement message to the DMS3 (step 405 b).

Step 406: after receiving the Location Update Notification message sent by DMS3, the MA-CN replaces the destination address of the packet with the HID-MN1 as the destination address of MN1 in the currently accessed network with the Location identifier vLoc-MA2-MN1 according to the Location identifier vLoc-MA2-MN1 of MN1 carried in the message, and sends the packet with the destination identifier updated.

Further, after receiving the Location Update Notification message sent by the DMS3, the MA-CN may cache the mapping relationship between the identity HID-MN1 of the MN1 and the Location identity vLoc-MA2-MN 1.

Step 407: the data packet is routed to MA2, after receiving the data packet, MA2 queries the identifier mapping table according to the destination identifier of the data packet, namely vLoc-MA2-MN1, obtains the corresponding identity identifier HID-MN1, updates the destination identifier of the data packet by using the queried HID-MN1, and forwards the updated data packet to MN 1.

It should be noted that, after receiving the Location Update Notification message sent by the DMS3, the MA-CN caches the mapping relationship between the id HID-MN1 of the MN1 and the Location id vLoc-MA2-MN1, so that after receiving the data packet sent to the MN1 again by the subsequent MA-CN (the structure of the data packet is shown in table 12), the MA-CN may query the mapping relationship between the id HID-MN1 of the MN1 and the Location id vLoc-MA2-MN1 according to the destination id of the data packet, replace the destination id of the data packet with the queried Location id vLoc-MA2-MN1, and send an updated data packet, which may be directly routed to the MA2 and sent to the MN1 by the MA2 (i.e., the step shown by the dotted line in fig. 4B may be omitted).

It should be further noted that, when the MA currently accessed by the source network node and the target network node of the packet belong to the same domain, after receiving a Notification Request message sent by the MA accessed by the receiver node (i.e., the target network node of the packet), the DMS in the domain may query an intra-domain mapping entry of the sender node according to the identity of the sender node (i.e., the source network node of the packet) carried in the message, so that according to the MA currently accessed by the sender node indicated in the entry, the Location identifier of the receiver node carried in the Notification Request message is sent to the MA currently accessed by the sender node through a Location Update Notification message, so that the MA forwards the packet to the receiver node according to the Location identifier.

Referring to fig. 5, when MN1 is handed over from visited network MA2 back to home network MA1, the process may include the steps of:

step 501: MN1 sends an access request message to MA 1. The access request message carries the identity HID-MN1 of MN 1.

Step 502: after receiving the access request message, the MA1 determines that MA1 is the home network of MN1, further queries the identity and location identity of MN1 in the identity mapping table, and indicates that MN1 is switched from the visited network to the home network because the queried identity and location identity of MN1 are different. The MA1 updates the identifier mapping entry of MN1, and in the updated identifier mapping entry of MN1, the identity and location identifier of MN1 are the same.

The MA1 sends a Location Update Notification message (Location Update Notification message) to the DMS1 of the local management domain to instruct the DMS1 to Update the intra-domain map entry. The Location Update Notification message contains the identity of MN1, HID-MN 1.

Step 503: after receiving the Location Update Notification message, DMS1 updates the intra-domain mapping entry of MN1, where the updated intra-domain mapping table may be as shown in table 13:

table 13: intradomain map of DMS1

DMS1 sends a Location Update Notification message to MA2 that MN1 previously accessed to indicate that the identity map entry of MN1 is updated.

After receiving the Location Update Notification message, the MA2 updates the identifier mapping entry of MN1, and may further return a Location Update Acknowledgement message to the DMS 1. In the updated identification mapping entry of the MN1, the identity identification and the position identification of the MN1 are the same.

Referring to fig. 6, a flow diagram for MN1 moving from a currently accessing MA2 to MA3 is shown. As shown, the process may include the following steps:

step 601: MN1 sends an access request message to MA3 requesting access to the visited network. The access request message carries the identity HID-MN1 of MN 1.

Step 602: after receiving the access Request message, MA3 determines that MA3 is not the home network of MN1, and therefore sends a Location Request message to DMS1 in the local management domain to Request to allocate a Location identifier in the visited network for MN 1. The Location Request message contains the identity of MN1, HID-MN 1.

Step 603: DMS1 receives Location Request message, allocates Location identification in visiting network for MN1, DMS1 returns Location Response message to MA3, where Location identification in visiting network allocated for MN1 is carried, i.e. vLoc-MA3-MN 1. Further, DMS1 updates the in-domain mapping entries of MN 1.

In this step, after receiving the Location Request message, the DMS1 sends the Location Request message, which carries the identity of MN1, to a network identity pool (vLoc pool) to Request to allocate a network identity to MN 1; the vLoc pool selects an unused IPv6 address from the identification pool to allocate a location identification vLoc-MA3-MN1 for MN1, and sends the location identification vLoc-MA3-MN1 allocated for MN1 to MA3 through a location response message.

DMS1 updates the mapping entries associated with MN1 in the intra-domain mapping table to: < Name-MN1, HID-MN1, IP-MA1, IP-MA3, IP-MA2 >. Wherein, the address of the home MA of MN1 is IP-MA1, the address of the MA currently accessed by MN1 is IP-MA3, the address of the MA accessed before MN1 can include the address IP-MA2 of the last accessed MA2, and can further include the address IP-MA1 of the previously accessed MA 1. The updated intra-domain mapping table may be as shown in table 14.

Table 14: intradomain map of DMS1

Step 604: after receiving the Location Response message, MA3 updates the identifier mapping entry of MN1 according to the Location identifier of MN1 carried therein, and may further return a Location Update Acknowledgement message (Location Update confirm message) to DMS 1. The updated identification mapping entry of MN1 is: < Name-MN1, HID-MN1, vLoc-MA3-MN1 >. The updated identification mapping table may be as shown in table 15.

Table 15: identification mapping table of MA3

Step 605: DMS1 sends Location update notification messages to home MA1 of MN1 and last accessed MA2, respectively, where the Location update notification messages carry the identity of MN1, HID-MN1, and Location identity of MN1 in MA3, vLoc-MA3-MN1, so that home MA1 of MN1 and last accessed MA2 update the identity mapping entry of MN 1.

Step 606: after receiving the Location Update Notification message, MA1 and MA2 Update the identifier mapping entry of MN1 according to the Location identifier of MN1 carried therein, and may further return a Location Update acknowledgement message to DMS 1. The updated identification mapping entry of MN1 is: < Name-MN1, HID-MN1, vLoc-MA3-MN1 >. The updated identification mapping table may be as shown in table 16.

Table 16: identification mapping tables for MA1 and MA2

In the above flow, there is no strict timing requirement for some steps, for example, the order of step 604 and step 605 may be exchanged.

Referring to fig. 7A and fig. 7B, a schematic flow chart of sending data to an MN located in a visited network according to an embodiment of the present application is provided. Although the flow is described by taking MN1 as an example, the access flow can be applied to data transmission processes of other network structures or other types of network nodes. As shown, after the MN1 switches from MA2 to MA3, the data transmission process may include the following steps:

step 701: the CN1 sends a packet to the MA-CN currently accessed by CN1, the format of which is shown in table 17.

Table 17: data packet format sent by CN1

HID-CN1

HID-MN1

Data

Step 702: after receiving the data packet, the MA-CN queries the position identifier of the MN1 cached before according to the destination address HID-MN1 of the data packet, replaces the destination identifier of the data packet with the vLoc-MA2-MN1 by using the queried position identifier vLoc-MA2-MN1, and routes the data packet to the MA2 accessed last time by the MN 1.

Step 703 a: the MA2 receives the packet and then buffers it and waits for a period of time (which may be set). When receiving the Location Update notification message sent by DMS1 to MA2 within the period of time (which carries the identity HID-MN1 and the Location identity vLoc-MA3-MN1 of MN1), MA2 updates the identity mapping entry of MN1 according to the message, and sends a notification Request message (notification Request message) to DMS1, where the notification Request message carries the identity HID-MN1 and the Location identity vLoc-MA3-MN1 of MN1, and the identity HID-CN1 of CN1, thereby triggering DMS to notify the access mobility anchor MA-CN of CN1 of the Location identity of MN1 in the currently accessed network.

Step 704 a: after receiving the Notification Request message sent by the MA2, the DMS1 queries the intra-domain mapping table according to the id of the CN1 carried in the message, i.e., the HID-CN 1. Because the intra-domain mapping table of DMS1 does not have the intra-domain mapping entry of CN1, DMS1 queries the inter-domain mapping table according to HID-CN1, and obtains the local management domain DMS3 of CN 1; DMS1 sends a Notification Request message to DMS3, which may carry the identity of CN1, HID-CN1, and the identity of MN1, HID-MN1 and location identity vLoc-MA3-MN1 in the currently accessed network.

Further, upon receiving the Notification Request message sent by DMS1, DMS3 may return a Notification Response message to DMS1 (step 704 b). Further, upon receiving the Notification request message sent by MA1, DMS1 may return a Notification Response message to MA1 (step 703 b).

Step 705 a: after receiving the Notification Request message sent by the DMS1, the DMS3 queries the intra-domain mapping table according to the id of the CN1 carried in the message, to obtain intra-domain mapping entries < Name-CN1, HID-CN1, IP-MA-CN1, and IP-MA-CN 1- > of the CN1, where the address of the home MA of the CN1 and the address of the currently accessed MA are both IP-MA-CN 1; and the DMS3 sends a Location Update Notification message to the MA-CN currently accessed by the CN1 according to the inquired address of the MA-CN currently accessed by the CN1 in the mapping entry of the CN1, wherein the Location Update Notification message can carry the identity of the MN1, namely HID-MN1 and the Location identity of MN1, namely vLoc-MA3-MN 1.

Further, the MA-CN, upon receiving the Location Update Notification message sent by the DMS3, may return a Location Update Acknowledgement message to the DMS3 (step 705 b).

Step 706: after receiving the Location Update Notification message sent by DMS3, the MA-CN replaces the destination address of the packet with the HID-MN1 as the destination address of MN1 in the currently accessed network with the Location identifier vLoc-MA3-MN1 according to the Location identifier vLoc-MA3-MN1 of MN1 carried in the message, and sends the packet with the destination identifier updated.

Further, after receiving the Location Update Notification message sent by the DMS3, the MA-CN may cache the mapping relationship between the identity HID-MN1 of the MN1 and the Location identity vLoc-MA3-MN 1.

Step 707: the data packet is routed to MA3, after receiving the data packet, MA3 queries the identifier mapping table according to the destination identifier of the data packet, namely vLoc-MA3-MN1, obtains the corresponding identity identifier HID-MN1, updates the destination identifier of the data packet by using the queried HID-MN1, and forwards the updated data packet to MN 1.

It should be noted that, since the MA-CN caches the mapping relationship between the id HID-MN1 and the location id vLoc-MA3-MN1 of the MN1, after the subsequent MA-CN receives the data packet addressed to the MN1 again (the structure of the data packet is shown in table 17), the mapping relationship between the id HID-MN1 and the location id vLoc-MA3-MN1 of the MN1 may be queried according to the target id of the data packet, the queried location id vLoc-MA3-MN1 is used to replace the target id of the data packet, and an updated data packet is sent, and the data packet may be directly routed to the MA3 and sent to the MN1 by the MA3 (that is, the step shown by the dotted line in fig. 7B may be omitted).

It should be further noted that, when the MA currently accessed by the source network node and the MA currently accessed by the target network node of the data packet belong to the same domain, after receiving the Notification Request message sent by the MA accessed by the sending node, the DMS may query the intra-domain mapping entry of the sending node according to the identity of the sending node carried in the message, so as to send the location identifier of the receiving node carried in the Notification Request message to the MA currently accessed by the sending node according to the MA currently accessed by the sending node indicated in the entry.

Referring to fig. 8, a schematic diagram of a network access process when an MN moves across domains is provided in the embodiment of the present application. Although fig. 8 is described by taking MN1 as an example, the access procedure can be applied to the procedure of accessing the visited network by other network architectures or other types of network nodes.

When MN1 moves from the access network where MA3 resides to the access network where MA4 resides, the visited network is accessed through MA 4. MA3 belongs to a different domain than MA 4. As shown, the process may include the following steps:

step 801: MN1 sends an access request message to MA4 requesting access to the visited network. The access request message carries the identity HID-MN1 of MN 1.

Step 802: after receiving the access Request message, MA4 determines that MA4 is not the home network of MN1, and therefore sends a Location Request message to DMS2 in the local management domain to Request to allocate a Location identifier in the visited network for MN 1. The Location Request message contains the identity of MN1, HID-MN 1.

Step 803: DMS2 receives Location Request message, allocates Location identification in visiting network for MN1, DMS2 returns Location Response message to MA4, where Location identification in visiting network allocated for MN1 is carried, i.e. vLoc-MA4-MN 1. Further, DMS2 creates an in-domain mapping entry for MN 1.

In this step, after receiving the Location Request message, the DMS2 sends the Location Request message, which carries the identity of MN1, to a network identity pool (vLoc pool) to Request to allocate a network identity to MN 1; the vLoc pool selects an unused IPv6 address from the identification pool to allocate a location identification vLoc-MA4-MN1 for MN1, and sends the location identification vLoc-MA4-MN1 allocated for MN1 to MA4 through a location response message.

DMS2 creates a map bar associated with MN1, the intra-domain map table at this time being shown in table 18. The address of home MA1 of MN1 is null.

Table 18: intradomain map of DMS2

Step 804: after receiving Location Response message, MA4 creates an identifier mapping entry of MN1 according to the Location identifier of MN1 carried therein, and may further return Location Update Acknowledgement message to DMS 2. The identification mapping table at this time can be as shown in table 19.

Table 19: identification mapping table of MA4

Step 805: since the mapping entry of the intra-domain mapping table of DMS2 for MN1 does not contain the home MA of MN1 and the MA accessed last time (because MN1 does not belong to the domain where DMS2 is located), DMS2 queries the inter-domain mapping table according to the identity of MN1, obtains the address of home DMS1 of MN1, and sends a Location Update Notification message to DMS1, where the identity of MN1 is carried, HID-MN1, the Location identity of MN1 in MA4, vLoc-MA4-MN1, and the address IP-MA4 of MA4 are carried.

Step 806: after receiving the Location Update Notification message sent by DMS2, DMS1 updates the intra-domain mapping entry of MN1 in the intra-domain mapping table according to the message (as shown in table 20); the DMS1 notifies the home MA1 of MN1 and the MA3 that MN1 accessed last time to Update the identifier mapping table of MN1 through a Location Update Notification message, which may include the identity HID-MN1 and Location identifier vLoc-MA4-MN1 of MN 1. Further, DMS1 returns a Location Update Acknowledgement message to DMS 2.

Table 20: intradomain map of DMS1

Step 807: after receiving the Location Update Notification message, MA1 and MA3 Update the identifier mapping entry of MN1 according to the Location identifier of MN1 carried therein, and may further return a Location Update acknowledgement message to DMS 1. The updated identification mapping entry of MN1 is: < Name-MN1, HID-MN1, vLoc-MA4-MN1 >. The updated identification mapping table may be as shown in table 21. The identity mapping entries for MN1 on MA2 may remain unchanged.

Table 21: identification mapping tables for MA1 and MA3

In the above flow, some steps have no strict timing requirements.

Referring to fig. 9A and 9B, a schematic flow chart of sending data to an MN located in a visited network according to an embodiment of the present application is provided. Although the flow is described by taking MN1 as an example, the access flow can be applied to data transmission processes of other network structures or other types of network nodes. As shown, after the MN1 switches from MA3 to MA4, the data transmission process may include the following steps:

step 901: the CN1 sends a packet to the MA-CN currently accessed by CN1, the format of which is shown in table 22.

Table 22: data packet format sent by CN1

HID-CN1

HID-MN1

Data

Step 902: after receiving the data packet, the MA-CN queries the previously cached location identifier of MN1 according to the destination address HID-MN1 of the data packet (see step 706 in fig. 7A and 7B), replaces the destination identifier of the data packet with vLoc-MA3-MN1 by vLoc-MA3-MN1 by using the queried location identifier, and routes the data packet to the last accessed MA3 of MN 1.

Step 903 a: the MA3 receives the packet and then buffers it and waits for a period of time (which may be set). When receiving the Location Update notification message sent by DMS1 to MA3 within the period of time (which carries the identity HID-MN1 and the Location identity vLoc-MA4-MN1 of MN1), MA3 updates the identity mapping entry of MN1 according to the message, and sends a notification Request message (notification Request message) to DMS1, where the notification Request message carries the identity HID-MN1 and the Location identity vLoc-MA4-MN1 of MN1, and the identity HID-CN1 of CN1, thereby triggering DMS to notify the access mobility anchor MA-CN of CN1 of the Location identity of MN1 in the currently accessed network.

Step 904 a: after receiving the Notification Request message sent by the MA3, the DMS1 queries the intra-domain mapping table according to the id of the CN1 carried in the message, i.e., the HID-CN 1. Because the intra-domain mapping table of DMS1 does not have the intra-domain mapping entry of CN1, DMS1 queries the inter-domain mapping table according to HID-CN1, and obtains the local management domain DMS3 of CN 1; DMS1 sends a Notification Request message to DMS3, which may carry the identity of CN1, HID-CN1, and the identity of MN1, HID-MN1 and location identity vLoc-MA4-MN1 in the currently accessed network.

Further, upon receiving the Notification Request message sent by MA3, DMS1 may return a Notification Response message to MA3 (step 903 b). Further, upon receiving the Notification request message sent by DMS1, DMS3 may return a Notification Response message to DMS1 (step 904 b).

Step 905 a: after receiving the Notification Request message sent by the DMS1, the DMS3 queries the intra-domain mapping table according to the id of the CN1 carried in the message, to obtain intra-domain mapping entries < Name-CN1, HID-CN1, IP-MA-CN1, and IP-MA-CN 1- > of the CN1, where the address of the home MA of the CN1 and the address of the currently accessed MA are both IP-MA-CN 1; and the DMS3 sends a Location Update Notification message to the MA-CN currently accessed by the CN1 according to the inquired address of the MA-CN currently accessed by the CN1 in the mapping entry of the CN1, wherein the Location Update Notification message can carry the identity of the MN1, namely HID-MN1 and the Location identity of MN1, namely vLoc-MA4-MN 1.

Further, the MA-CN, upon receiving the Location Update Notification message sent by the DMS3, may return a Location Update Acknowledgement message to the DMS3 (step 905 b).

Step 906: after receiving the Location Update Notification message sent by DMS3, the MA-CN replaces the destination address of the packet with the HID-MN1 as the destination address of MN1 in the currently accessed network with the Location identifier vLoc-MA4-MN1 according to the Location identifier vLoc-MA4-MN1 of MN1 carried in the message, and sends the packet with the destination identifier updated.

Further, after receiving the Location Update Notification message sent by the DMS3, the MA-CN may cache the mapping relationship between the identity HID-MN1 of the MN1 and the Location identity vLoc-MA4-MN 1.

Step 907: the data packet is routed to MA4, after receiving the data packet, MA4 queries the identifier mapping table according to the destination identifier of the data packet, namely vLoc-MA4-MN1, obtains the corresponding identity identifier HID-MN1, updates the destination identifier of the data packet by using the queried HID-MN1, and forwards the updated data packet to MN 1.

It should be noted that, since the MA-CN caches the mapping relationship between the id HID-MN1 and the location id vLoc-MA4-MN1 of the MN1, after the subsequent MA-CN receives the data packet addressed to the MN1 again (the structure of the data packet is shown in table 22), the MA-CN may query the mapping relationship between the id HID-MN1 and the location id vLoc-MA4-MN1 of the MN1 according to the destination id of the data packet, replace the destination id of the data packet with the queried location id vLoc-MA4-MN1, and send an updated data packet, which may be directly routed to the MA4 and sent to the MN1 by the MA4 (i.e., the step shown by the dotted line in fig. 9B may be omitted).

Referring to fig. 10A and 10B, in case MN1 is currently accessing MA4 and the location identity of target network node MN1 is not cached in the MA-CN, the flow of data sent by the CN to MN1 is similar to the flow shown in fig. 7A and 7B. As shown in fig. 10A and 10B, the process may include the following steps:

step 1001: the CN1 sends a data packet to the MA-CN to which the CN1 is currently accessed, the source identifier of the data packet is the identity of the CN, namely HID-CN1, and the destination identifier of the data packet is the identity of the MN1, namely HID-MN 1.

Step 1002: after the MA-CN receives the data packet, because the MA-CN does not cache the mapping relation information of the identity and the position identity of the MN1, the MA-CN routes the data packet to a home MA1 of the MN1 according to the destination address HID-MN1 of the data packet.

Step 1003 a: after receiving the data packet, MA1 queries the identifier mapping table according to the destination identifier HID-MN1 of the data packet, to obtain an identifier mapping entry < Name-MN1, HID-MN1, vLoc-MA4-MN1> of MN1, and since the identifier and the location identifier in the identifier mapping entry are different, MA1 determines that MN1 has moved out of the home network, and therefore sends a Notification Request message to DMS1, where the Notification Request message carries the identifier HID-MN1 of MN1, the location identifier vLoc-MA4-MN1, and the identifier HID-CN1 of CN1, thereby triggering DMS to notify the location identifier of MN1 in the currently accessed network to the access mobility anchor MA-CN 1.

Step 1004 a: after receiving the Notification Request message sent by the MA1, the DMS1 queries the intra-domain mapping table according to the id of the CN1 carried in the message, i.e., the HID-CN 1. Because the intra-domain mapping table of DMS1 does not have the intra-domain mapping entry of CN1, DMS1 queries the inter-domain mapping table according to HID-CN1, and obtains home network DMS3 of CN 1; DMS1 sends a Notification Request message to DMS3, which may carry the identity of CN1, HID-CN1, and the identity of MN1, HID-MN1 and location identity vLoc-MA4-MN1 in the currently accessed network.

Further, upon receiving the Notification Request message sent by DMS1, DMS3 may return a Notification Response message to DMS1 (step 1004 b). Further, upon receiving the Notification request message sent by MA1, DMS1 may return a Notification Response message to MA1 (step 1003 b).

Step 1005 a: after receiving the Notification Request message sent by the DMS1, the DMS3 queries the intra-domain mapping table according to the id of the CN1 carried in the message, to obtain intra-domain mapping entries < Name-CN1, HID-CN1, IP-MA-CN1, and IP-MA-CN 1- > of the CN1, where the address of the home MA of the CN1 and the address of the currently accessed MA are both IP-MA-CN 1; and the DMS3 sends a Location Update Notification message to the MA-CN currently accessed by the CN1 according to the inquired address of the MA-CN currently accessed by the CN1 in the mapping entry of the CN1, wherein the Location Update Notification message can carry the identity of the MN1, namely HID-MN1 and the Location identity of MN1, namely vLoc-MA4-MN 1.

Further, the MA-CN, upon receiving the Location Update Notification message sent by the DMS3, may return a Location Update Acknowledgement message to the DMS3 (step 1005 b).

Step 1006: after receiving the Location Update Notification message sent by DMS3, the MA-CN replaces the destination address of the packet with the HID-MN1 as the destination address of MN1 in the currently accessed network with the Location identifier vLoc-MA4-MN1 according to the Location identifier vLoc-MA4-MN1 of MN1 carried in the message, and sends the packet with the destination identifier updated.

Step 1007: the data packet is routed to MA4, after receiving the data packet, MA4 queries the identifier mapping table according to the destination identifier of the data packet, namely vLoc-MA4-MN1, obtains the corresponding identity identifier HID-MN1, updates the destination identifier of the data packet by using the queried HID-MN1, and forwards the updated data packet to MN 1.

It should be noted that, after receiving the Location Update Notification message sent by the DMS3, the MA-CN caches the mapping relationship between the identity HID-MN1 of the MN1 and the Location identity vLoc-MA4-MN1, so that after receiving the data packet sent to the MN1, the subsequent MA-CN may query the mapping relationship between the identity HID-MN1 of the MN1 and the Location identity vLoc-MA4-MN1 according to the target identity of the data packet, replace the target identity of the data packet with the queried Location identity vLoc-MA4-MN1, and send an updated data packet, where the data packet may be directly routed to the MA4 and sent to the MN1 by the MA4 (that is, the step shown by the dotted line in fig. 10B may be omitted).

It can be seen that although the MN is switched over through multiple network switches, in the switching process, the DMS only requests the MA accessed by the MN last time and the home MA to update the identifier mapping entry of the MN based on the intra-domain mapping table, so that the packet can be routed and forwarded according to the identifier mapping table of the MA involved in the switching process.

The above flow is described by taking the MN and CN as an example, and based on the above principle, the communication process between different network nodes in the network can be implemented by referring to the above flow.

As can be seen from the above description, the DMS may create an intra-domain mapping entry for the network node according to the identity identifier assigned to the MN, where the created intra-domain mapping entry is used to store a mapping relationship between the identity identifier of the network node and a mobility anchor point to which the network node is currently accessed; the mobile anchor point can also request the domain mapping server to allocate a location identifier for the network node accessing the visited network, and create an intra-domain mapping entry of the network node, where the created intra-domain mapping entry is used to store the mapping relationship between the identity identifier of the network node, the mobile anchor point currently accessed by the network node, and the mobile anchor point previously accessed by the network node. Therefore, based on the domain mapping server and the mobile anchor point in the embodiment of the application, the mapping relation of the network identifiers can be maintained, and the guarantee is provided for the routing of the data packets in the data transmission process.

Based on the same technical concept, the embodiment of the present application further provides an MA device, which can implement the process provided by the above-described embodiment of the present application.

Referring to fig. 11, a schematic structural diagram of an MA device provided in an embodiment of the present application is shown. The MA device is applied to a communication system including a DMS and a MA, and the MA may include: a first interface module 1101, a processing module 1102, a second interface module 1103, and a mapping table maintaining module 1104, wherein:

a first interface module 1101, configured to receive a network access request sent by a first network node;

a processing module 1102, configured to determine whether the local mobility anchor MA is a home MA of a first network node, and if not, instruct the second interface module 1103 to request to acquire a location identifier of the first network node and instruct the mapping table maintenance module 1104 to maintain an identifier mapping entry in the identifier mapping table; if the identity of the first network node is in the address range of the MA, the MA is a home MA of the first network node, otherwise, the MA is not the home MA of the first network node;

a second interface module 1103, configured to send a location request message to a DMS of the local management domain; receiving a location response message returned by the DMS according to the location request message, wherein the location response message carries a location identifier distributed by a location identifier pool for the first network node;

a mapping table maintaining module 1104, configured to maintain an identifier mapping entry of the first network node according to the received location response message, where the identifier mapping entry of the first network node includes an identity identifier and a location identifier of the first network node.

Optionally, the processing module 1102 is further configured to: if the MA is judged to be the home MA of the first network node, determining whether the identity identifier and the position identifier of the first network node are the same according to the identifier mapping entry of the first network node; if the difference is positive, determining that the first network node is switched from the other network to the home network, instructing the mapping table maintenance module 1104 to update the location identifier in the identifier mapping entry of the first network node to be the same as the identity identifier, and instructing the second interface module 1103 to send a location update notification message to the DMS of the local management domain to instruct the DMS to update the intra-domain mapping entry of the first network node; and if the first network node is the same as the home network node, determining that the first network node accesses the home network for the first time.

Optionally, the second interface module 1103 is further configured to: receiving a location update notification message sent by a DMS of a local management domain, wherein the location update notification comprises an identity identifier and a location identifier of a second network node; the second network node does not access the MA currently, the MA is the last MA accessed by the second network node or the home MA of the second network node, and the location update notification message is sent by the DMS to the last MA and the home MA accessed by the second network node after the location identifier pool allocates the location identifier to the second network node requesting to access the visited network. The mapping table maintenance module 1104 is further configured to: and updating the identifier mapping item of the second network node according to the position updating notification message.

Optionally, the location request sent by the MA includes an identity of the first network node.

Optionally, the identity includes a network identifier type information field, and a value of the information field indicates that the network identifier type is the identity; the location identifier comprises a network identifier type information field, and the value of the information field indicates that the network identifier type is the location identifier. The network identification type information field is positioned in a routing prefix address block of the network identification.

Optionally, the network identifier type information field is a T-bit information field, where T is greater than or equal toAn integer of 0; 2 of the network identification information field^TThe value is divided into at least a first part and a second part, the value of the first part is used as the indication of the identity identifier, and the value of the second part is used as the indication of the network identifier.

Optionally, the number of values of the first part and the number of values of the second part are set according to a set ratio.

Based on the same technical concept, the embodiment of the present application further provides a DMS, and the DMS in this area can implement the process provided by the above embodiment of the present application.

Referring to fig. 12, a schematic structural diagram of a DMS is provided in an embodiment of the present application. The DMS is applied to a communication system comprising domains DMS and MA, the DMS comprising: a receiving module 1201, an identifier allocating module 1202, a mapping table maintaining module 1203, and a sending module 1204, where:

a receiving module 1201, configured to receive a location request message sent by a first MA of a local management domain, where the first MA is a visited MA of a first network node, and the location request message is sent by the first MA according to a request for accessing the visited MA by the first network node;

an identifier allocating module 1202, configured to request, according to the location request message, a location identifier pool to allocate a location identifier for the first network node;

a mapping table maintaining module 1203, configured to maintain, according to the location request message, an intra-domain mapping entry of the first network node, where the intra-domain mapping entry of the first network node is used to store: the method comprises the steps that the identity of a first network node, the address of a home MA of the first network node, the address of a MA currently accessed by the first network node and the address list of the MA previously accessed by the first network node are preset;

a sending module 1204, configured to send a location response message carrying a location identifier of a first network node to the first MA, so as to trigger the first MA to maintain an identifier mapping entry of the first network node, where the identifier mapping entry of the first network node includes an identity identifier and a location identifier of the first network node; and sending a location update notification message to the last access MA and the home MA of the first network node, wherein the location update notification message is used for indicating to update the identification mapping entry of the first network node.

Optionally, the mapping table maintaining module 1203 is specifically configured to: if the DMS is the DMS of the local management domain of the first network node, updating the intra-domain mapping entry of the first network node; or if the DMS is not a DMS of a local management domain of the first network node, updating an intra-domain mapping entry of the first network node if the intra-domain mapping entry already exists, and otherwise creating the intra-domain mapping entry of the first network node, where an address of a home MA of the first network node and an address of a previously-accessed MA in the intra-domain mapping entry of the first network node are null.

Optionally, the sending module 1204 is specifically configured to: if the DMS is the DMS of the local management domain of the first network node, acquiring the addresses of the last-accessed MA and the home MA of the first network node according to the intra-domain mapping entry of the first network node, and sending a location update notification message to the last-accessed MA and the home MA of the first network node according to the acquired addresses; or, if the DMS is not the DMS of the first network node local management domain, obtaining the DMS of the first network node local management domain by querying the inter-domain mapping table, and sending a location update notification message to the DMS of the first network node local management domain, so that the DMS of the first network node local management domain sends a location update notification message to the last MA and the home MA accessed to the first network node; the inter-domain mapping table includes identifiers of the DMS and ranges of network node identities belonging to the DMS.

Optionally, the receiving module 1201 is further configured to: receiving a location update notification message sent by a second MA, wherein the second MA is a home MA of the first network node, and the location update notification message is sent by the second MA according to a request of the first network node for accessing the home MA. The identification mapping table maintenance module 1203 is further configured to: and updating the intra-domain mapping entry of the first network node according to the location updating notification message, wherein the identity identifier and the location identifier of the first network node in the updated intra-domain mapping entry of the first network node are the same. The sending module 1204 is further configured to: and sending a location update notification message to the last access MA of the first network node and a second MA serving as a home MA according to the location update notification message, wherein the location update notification message is used for indicating to update the identifier mapping entry of the first network node.

Optionally, the location request sent by the MA includes an identity of the first network node. Optionally, the location update notification message sent by the DMS includes the identity and the location identifier of the first network node.

Optionally, the network identifier type information field is a T-bit information field, where T is an integer greater than or equal to 0; 2 of the network identification information field^TThe value is divided into at least a first part and a second part, the value of the first part is used as the indication of the identity identifier, and the value of the second part is used as the indication of the network identifier.

Based on the same technical concept, the embodiment of the present application further provides a communication device, where the communication device may implement the flow of the MA in the foregoing embodiment of the present application. See, a schematic structural diagram of a communication device provided in an embodiment of the present application. The communication device may include: a processor 1301, a memory 1302, a network interface 1303, and a bus interface.

The processor 1301 is responsible for managing a bus architecture and general processing, the memory 1302 may store data used by the processor 1301 in performing operations, and the network interface 1303 may be used for transceiving information.

The bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 1301, and various circuits, represented by memory 1302, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The processor 1301 is responsible for managing the bus architecture and general processing, and the memory 1302 may store data used by the processor 1301 in performing operations.

Network interface 1303 may include a receiver to provide a wireless interface for the communication device to communicate with one or more networks and/or any suitable device. Network interface 1303 may include any suitable hardware and/or firmware. The network interface 1303 may include multiple antennas to provide a multiple-input multiple-output wireless interface. In one embodiment, network interface 1303 may include a network adapter, a wireless network adapter, a telephone modem, and/or a wireless modem.

The processes disclosed in the embodiments of the present invention may be implemented in the processor 1301 or implemented by the processor 1301. In implementation, the steps of the signal processing flow may be implemented by integrated logic circuits of hardware or instructions in the form of software in the processor 1301. The processor 1301 may be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof that may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present invention. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 1302, and the processor 1301 reads the information in the memory 1302, and completes the steps of the signal sampling rate conversion process in combination with the hardware thereof.

Based on the same technical concept, the embodiment of the present application further provides a communication device, and the communication device may implement the process of the DMS in the above embodiment of the present application. Referring to fig. 14, a schematic structural diagram of a communication device provided in the embodiment of the present application is shown. The communication device may include: a processor 1401, a memory 1402, a network interface 1403, and a bus interface.

The processor 1401 is responsible for managing a bus architecture and general processing, the memory 1402 may store data used by the processor 1401 in performing operations, and the network interface 1403 is used for information transmission and reception.

The bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 1401, and various circuits, represented by memory 1402, linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The processor 1401 is responsible for managing the bus architecture and general processing, and the memory 1402 may store data used by the processor 1401 in performing operations.

Network interface 1403 may include a receiver to provide a wireless interface for the communication device to communicate with one or more networks and/or any suitable device. Network interface 1403 may include any suitable hardware and/or firmware. Network interface 1403 may include multiple antennas to provide a multiple-input multiple-output wireless interface. In one embodiment, network interface 1403 may include a network adapter, a wireless network adapter, a telephone modem, and/or a wireless modem.

The processes disclosed by the embodiments of the present invention may be applied to the processor 1401, or implemented by the processor 1401. In implementation, the steps of the signal processing flow may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 1401. The processor 1401 may be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, and may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present invention. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 1402, and the processor 1401 reads the information in the memory 1402, and completes the steps of the signal sampling rate conversion process in combination with the hardware thereof.

To sum up, the embodiment of the present application provides an identifier mapping scheme based on a domain mapping server and a mobile anchor point, which can meet the requirements of a mapping mechanism on extensibility and low latency, and can meet the requirements of fast mapping and updating to meet the development requirements of the current internet architecture.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A network identification method supporting identity and location decoupling, applied to a communication system including a domain mapping server DMS and a mobility anchor MA, the method comprising:

receiving a network access request sent by a first network node by the MA;

the MA judges whether the MA is a home MA of a first network node; if the identity of the first network node is in the address range of the MA, the MA is a home MA of the first network node, otherwise, the MA is not the home MA of the first network node;

if the MA is not the home MA of the first network node, performing the following operations:

sending a position request message to a DMS of a local management domain;

receiving a location response message returned by the DMS according to the location request message, wherein the location response message carries a location identifier distributed by a location identifier pool for the first network node;

maintaining an identifier mapping entry of the first network node according to the received position response message, wherein the identifier mapping entry of the first network node comprises an identity identifier and a position identifier of the first network node;

if the MA judges that the MA is the home MA of the first network node, the method further comprises the following steps:

the MA determines whether the identity identifier and the position identifier of the first network node are the same according to the identifier mapping item of the first network node;

if the difference is positive, the first network node is determined to be switched from other networks to the home network, the identifier mapping entry of the first network node is updated, and a location updating notification message is sent to a DMS (distributed management system) of a local management domain to indicate the DMS to update the intra-domain mapping entry of the first network node;

and if the first network node is the same as the home network node, determining that the first network node accesses the home network for the first time.

2. The method of claim 1, further comprising:

receiving, by the MA, a location update notification message sent by a DMS of a local management domain, where the location update notification message includes an identity and a location identifier of a second network node; the second network node does not access the MA currently, the MA is the last MA accessed by the second network node or the home MA of the second network node, and the location update notification message is sent to the last MA accessed by the second network node and the home MA by the DMS after the location identifier pool allocates the location identifier to the second network node requesting to access the visited network;

and the MA updates the identification mapping item of the second network node according to the position updating notification message.

3. A method according to any one of claims 1 to 2, wherein the location request sent by the MA includes the identity of the first network node.

4. The method according to any one of claims 1 to 2, wherein the identity includes a network identifier type information field, and a value of the information field indicates that the network identifier type is the identity; the position mark comprises a network mark type information field, and the value of the information field indicates that the network mark type is the position mark;

the network identification type information field is positioned in a routing prefix address block of the network identification.

5. The method of claim 4, wherein the network identification type information field is a T bit information field, T being an integer greater than or equal to 0;

2 of the network identification information field^TThe value is divided into at least a first part and a second part, the value of the first part is used as the indication of the identity identifier, and the value of the second part is used as the indication of the network identifier.

6. The method of claim 5, wherein the number of values of the first portion and the number of values of the second portion are set in a set ratio.

7. The method of claim 4, wherein the identity and the location identity are both IPv6 addresses.

8. A network identification method supporting identity and location decoupling, applied to a communication system including a domain mapping server DMS and a mobility anchor MA, the method comprising:

the method comprises the steps that a DMS receives a position request message sent by a first MA of a local management domain, wherein the first MA is a visiting MA of a first network node, and the position request message is sent by the first MA according to a request of the first network node for accessing the visiting MA;

the DMS executes the following operations according to the position request message:

requesting a location identifier pool to allocate a location identifier for a first network node;

maintaining an intradomain mapping entry for a first network node, the intradomain mapping entry for the first network node for storing: the method comprises the steps that the identity of a first network node, the address of a home MA of the first network node, the address of a MA currently accessed by the first network node and the address list of the MA previously accessed by the first network node are preset;

sending a location response message carrying a location identifier of a first network node to the first MA to trigger the first MA to maintain an identifier mapping entry of the first network node, wherein the identifier mapping entry of the first network node comprises an identity identifier and a location identifier of the first network node;

and sending a location updating notification message to the MA accessed last time by the first network node and the home MA, wherein the location updating notification message is used for indicating that the identification mapping item of the first network node is updated.

9. The method of claim 8, wherein maintaining the intradomain mapping entry for the first network node comprises:

if the DMS is the DMS of the local management domain of the first network node, updating the intra-domain mapping entry of the first network node; or,

if the DMS is not the DMS of the local management domain of the first network node, updating the intra-domain mapping entry of the first network node if the intra-domain mapping entry of the first network node already exists, otherwise, creating the intra-domain mapping entry of the first network node, wherein the address of the home MA of the first network node and the address of the previously accessed MA in the intra-domain mapping entry of the first network node are null.

10. The method of claim 8, wherein sending a location update notification message to the last accessed MA and home MA of the first network node comprises:

if the DMS is the DMS of the local management domain of the first network node, the DMS obtains the addresses of the last access MA and the last access home MA of the first network node according to the intra-domain mapping entry of the first network node, and sends a location update notification message to the last access MA and the last access home MA of the first network node according to the obtained addresses; or,

if the DMS is not the DMS of the local management domain of the first network node, the DMS acquires the DMS of the local management domain of the first network node by inquiring an inter-domain mapping table and sends a location update notification message to the DMS of the local management domain of the first network node, so that the DMS of the local management domain of the first network node sends the location update notification message to the last accessed MA and the home MA of the first network node; the inter-domain mapping table includes identifiers of the DMS and ranges of network node identities belonging to the DMS.

11. The method of claim 8, further comprising:

the DMS receives a location update notification message sent by a second MA, wherein the second MA is a home MA of the first network node, and the location update notification message is sent by the second MA according to a request of the first network node for accessing the home MA;

the DMS executes the following operations according to the position updating notification message:

updating an intra-domain mapping entry of the first network node, wherein the identity identifier and the position identifier of the first network node are the same in the updated intra-domain mapping entry of the first network node;

and sending a location updating notification message to the MA which is accessed last by the first network node and a second MA which is a home MA, wherein the location updating notification message is used for indicating that the identification mapping item of the first network node is updated.

12. A method according to any one of claims 8 to 11, wherein the location request sent by the MA includes the identity of the first network node.

13. The method according to any of claims 8 to 11, wherein the location update notification message sent by the DMS includes the identity and the location identity of the first network node.

14. The method according to any one of claims 8 to 11, wherein the identity includes a network identifier type information field, and a value of the information field indicates that the network identifier type is the identity; the position mark comprises a network mark type information field, and the value of the information field indicates that the network mark type is the position mark;

15. The method of claim 14, wherein the network identification type information field is a T-bit information field, T being an integer greater than or equal to 0;

16. The method of claim 15, wherein the number of values of the first portion and the number of values of the second portion are set in a set ratio.

17. The method of claim 14, wherein the identity and the location identity are both IPv6 addresses.

18. A mobility anchor device applied to a communication system including a domain mapping server DMS and a mobility anchor MA, the MA comprising:

the first interface module is used for receiving a network access request sent by a first network node;

the processing module is used for judging whether the mobile anchor point MA is a hometown MA of the first network node, and if not, indicating the second interface module to request to acquire the position identifier of the first network node and indicating the mapping table maintenance module to maintain the identifier mapping item in the identifier mapping table; if the identity of the first network node is in the address range of the MA, the MA is a home MA of the first network node, otherwise, the MA is not the home MA of the first network node;

the second interface module is used for sending a position request message to a DMS of a local management domain; receiving a location response message returned by the DMS according to the location request message, wherein the location response message carries a location identifier distributed by a location identifier pool for the first network node;

a mapping table maintenance module, configured to maintain an identifier mapping entry of the first network node according to the received location response message, where the identifier mapping entry of the first network node includes an identity identifier and a location identifier of the first network node;

the processing module is further configured to:

if the MA is judged to be the home MA of the first network node, determining whether the identity identifier and the position identifier of the first network node are the same according to the identifier mapping entry of the first network node;

if the first network node is determined to be switched from the other network to the home network, the mapping table maintenance module is instructed to update the position identifier in the identifier mapping entry of the first network node to be the same as the identity identifier, and the second interface module is instructed to send a position update notification message to a DMS (distributed management system) of a local management domain so as to instruct the DMS to update the intra-domain mapping entry of the first network node;

19. The mobility anchor device of claim 18,

the second interface module is further configured to: receiving a location update notification message sent by a DMS of a local management domain, wherein the location update notification message comprises an identity identifier and a location identifier of a second network node; the second network node does not access the MA currently, the MA is the last MA accessed by the second network node or the home MA of the second network node, and the location update notification message is sent to the last MA accessed by the second network node and the home MA by the DMS after the location identifier pool allocates the location identifier to the second network node requesting to access the visited network;

the mapping table maintenance module is further configured to: and updating the identifier mapping item of the second network node according to the position updating notification message.

20. The mobility anchor device of any of claims 18 to 19, wherein the location request sent by the MA includes an identity of the first network node.

21. The mobility anchor device of any one of claims 18 to 19, wherein the identity identifier includes a network identifier type information field, and a value of the information field indicates that the network identifier type is the identity identifier; the position mark comprises a network mark type information field, and the value of the information field indicates that the network mark type is the position mark;

22. The mobility anchor device of claim 21, wherein the network identification type information field is a T-bit information field, T being an integer greater than or equal to 0;

23. The mobility anchor device of claim 22, wherein the number of values of the first portion and the number of values of the second portion are set in a predetermined ratio.

24. A domain mapping server applied to a communication system including a domain mapping server DMS and a mobility anchor MA, the DMS comprising:

a receiving module, configured to receive a location request message sent by a first MA of a local management domain, where the first MA is a visited MA of a first network node, and the location request message is sent by the first MA according to a request for accessing the visited MA by the first network node;

the identifier distribution module is used for requesting the location identifier pool to distribute the location identifier for the first network node according to the location request message;

a mapping table maintaining module, configured to maintain, according to the location request message, an intra-domain mapping entry of the first network node, where the intra-domain mapping entry of the first network node is used to store: the method comprises the steps that the identity of a first network node, the address of a home MA of the first network node, the address of a MA currently accessed by the first network node and the address list of the MA previously accessed by the first network node are preset;

a sending module, configured to send a location response message carrying a location identifier of a first network node to the first MA, so as to trigger the first MA to maintain an identifier mapping entry of the first network node, where the identifier mapping entry of the first network node includes an identity identifier and a location identifier of the first network node; and sending a location update notification message to the last access MA and the home MA of the first network node, wherein the location update notification message is used for indicating to update the identification mapping entry of the first network node.

25. The domain mapping server of claim 24, wherein the mapping table maintenance module is specifically configured to:

26. The domain-mapping server of claim 24, wherein the sending module is specifically configured to:

if the DMS is the DMS of the local management domain of the first network node, acquiring the addresses of the last-accessed MA and the home MA of the first network node according to the intra-domain mapping entry of the first network node, and sending a location update notification message to the last-accessed MA and the home MA of the first network node according to the acquired addresses; or,

if the DMS is not the DMS of the local management domain of the first network node, acquiring the DMS of the local management domain of the first network node by inquiring the inter-domain mapping table, and sending a location update notification message to the DMS of the local management domain of the first network node, so that the DMS of the local management domain of the first network node sends the location update notification message to the last accessed MA and the hometown MA of the first network node; the inter-domain mapping table includes identifiers of the DMS and ranges of network node identities belonging to the DMS.

27. The domain mapping server of claim 24,

the receiving module is further configured to: receiving a location update notification message sent by a second MA, wherein the second MA is a home MA of a first network node, and the location update notification message is sent by the second MA according to a request of the first network node for accessing the home MA;

the identifier mapping table maintaining module is further configured to: updating the intra-domain mapping entry of the first network node according to the location updating notification message, wherein the identity identifier and the location identifier of the first network node are the same in the updated intra-domain mapping entry of the first network node;

the sending module is further configured to: and sending a location update notification message to the last access MA of the first network node and a second MA serving as a home MA according to the location update notification message, wherein the location update notification message is used for indicating to update the identifier mapping entry of the first network node.

28. The domain mapping server according to any of claims 24 to 27, wherein the location request sent by the MA includes an identity of the first network node.

29. The domain mapping server according to any of claims 24 to 27, wherein the location update notification message sent by the DMS includes the identity and the location identity of the first network node.

30. The domain mapping server according to any of claims 24 to 27, wherein the identity includes a network identifier type information field, and a value of the information field indicates that the network identifier type is the identity; the position mark comprises a network mark type information field, and the value of the information field indicates that the network mark type is the position mark;

31. The domain mapping server according to claim 30, wherein the network identification type information field is a T bit information field, T being an integer greater than or equal to 0;

32. The domain mapping server of claim 31, wherein the number of values of the first portion and the number of values of the second portion are set according to a set ratio.

33. A communication device, comprising: a network interface, a processor, and a memory;

the memory to store computer program instructions;

the processor, coupled to the memory, to read the computer program instructions stored by the memory and perform the steps of any of claims 1 to 7.

34. A communication device, comprising: a network interface, a processor, and a memory;

the memory to store computer program instructions;

the processor, coupled to the memory, to read the computer program instructions stored by the memory and perform the steps of any of claims 8 to 17.