WO2011103761A1

WO2011103761A1 - Data packet transmission method and access device

Info

Publication number: WO2011103761A1
Application number: PCT/CN2010/080057
Authority: WO
Inventors: 张世伟; 符涛
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-02-26
Filing date: 2010-12-21
Publication date: 2011-09-01
Also published as: CN102170389B; CN102170389A

Abstract

The present invention provides a data packet transmission method and an access device. The method is realized based on an identity identifier and locator separation network, and includes the following steps: a source access device Access Service Node (ASN) receives an Access Identifier (AID) data packet, wherein the source and destination addresses in the packet header of the AID data packet are source and destination AIDs respectively; the source ASN replaces the source and destination AIDs in the packet header of the AID data packet with the source and destination Routing Identifiers (RIDs) to generate an RID data packet, and adds a packet extension header in the RID data packet to be transmitted to a terminal, wherein the packet extension header includes the source and destination AIDs; the source ASN transmits the generated RID data packet to a destination ASN; and the destination ASN receives the RID data packet transmitted by the source ASN, and forwards the RID data packet if it carries the packet extension header, or processes directly the RID data packet if it does not carry the packet extension header. With the invention, it can be realized that the ASN processes the data packet correctly.

Description

Data message transmission method and access device

Technical field

The present invention relates to the field of mobile communications, and in particular, to a data message transmission method and an access device.

Background technique

The IP address in the Transmission Control Protocol/Internet Protocol (TCP/IP), which is widely used in the Internet, has a dual function, which serves as the location identifier of the network interface of the network layer host in the network topology. The identity of the host network interface that is the transport layer. The TCP/IP protocol was not designed at the beginning of the host. However, as host mobility becomes more prevalent, the semantic overload defects of such IP addresses are becoming increasingly apparent. For example, when the IP address of the host changes, not only the route changes, but also the identity of the communication terminal host changes. This causes the routing load to become heavier and heavy, and the change of the host identity causes the application and connection to be interrupted.

The purpose of identification and location separation is to solve the problem of semantic overload and serious load and security of IP addresses, and to separate the dual functions of IP addresses to achieve dynamic redistribution of mobility, multiple townships, and IP addresses. Support for mitigating routing load and mutual visits between different network areas in the next generation Internet.

In order to solve the above problems, various architectures of identity and location separation networks have been proposed.

An identity identification and location separation network architecture is shown in FIG. 1. The identity identification and location separation network architecture includes an Access Service Node (ASN), a User Equipment (UE), and an Identity Location. Identification & Location Register (ILR), etc. The access service node is responsible for implementing the access of the user terminal, and is responsible for charging and switching functions; the ILR is responsible for the location registration and identity of the user, and each user terminal has a unique identity identifier, that is, access Identification (AID).

In Figure 1, the access service nodes ASN1 and ASN2 are respectively used to access the user terminals UE1 and UE2, and ASN1 and ASN2 respectively have routing identifiers RID1 and RID2, and UE1 and UE2 respectively store The only access identifiers are AID1 and AID2.

For convenience of description, the identity and location separation network is simply referred to as SILSN (Subscriber Identifier & Locator Separation Network).

In the SILSN network, when the network is mixed with the existing network, the ASN also assumes the functions of the common ISILSN network node and needs to process some traditional IP packets at the same time. When the ASN processes the traditional IP packets (as shown in Table 1 below), there is no The special flag allows the ASN to distinguish which packets are sent to the ASN itself, and which packets are sent to the mobile users under the ASN, causing the ASN to be confused when processing the data packets (the terminal, the message format received by the user). Also the format in Table 4). Table 1 sends the message content to the ASN itself.

IPV6 packet header

The most typical example is: When the network administrator needs to manage the core network nodes such as ASN and router, the administrator will send the traditional IP data packet destined for the ASN. That is, the ASN will receive two types of packets. : One type is to be forwarded to the end user, one has to deal with it by itself, and the existing processing methods can not clearly distinguish and process the two types of messages. Therefore, a new packet processing method must be given to enable ASN to distinguish between processing. Two types of messages.

Summary of the invention

It is an object of the present invention to provide a data message transmission method and an access device for implementing correct processing of data packets by an access device in an identity identification and location separation network.

To solve the above technical problem, the present invention provides a data message transmission method, which is implemented based on an identity identification and a location separation network, and includes:

The first access device receives and parses the first data packet, where the source and destination addresses in the header of the first data packet are the source and the destination access identifier (AID);

B. The first access device replaces the source and destination addresses in the packet header of the first data packet with The source and destination end route identifiers (RIDs) generate a second data packet, and add a packet extension header to the second data packet sent to the terminal, where the packet extension header includes the source and destination end AIDs, Transmitting, by the second access device, the second data packet;

The second access device receives the second data packet, and determines whether the second data packet carries a packet extension header. If the packet is carried, step D is performed, if not, step E is performed;

D. The second access device replaces the source and destination addresses in the packet header of the second data packet with the source and destination AIDs in the packet extension header, and deletes the packet extension header to be restored. Transmitting, by the first data packet, the first data packet to the terminal pointed to by the destination AID;

E. The second access device processes the second data packet.

Preferably, in step C, after the second access device receives the second data packet, it determines that the destination RID points to the second access device before determining whether to carry the packet extension header.

Preferably, in step C, after the second access device receives the second data packet, it is first determined whether the destination RID points to the second access device; if it is determined that the destination RID points to the second interface After the device is in the device, it is determined whether the packet extension header is carried. If the destination RID does not point to the second access device, the access device pointed to by the destination RID directly forwards the second data packet.

Preferably, the extension header is an IPV6 packet extension header.

Preferably, the IPV6 text extension header is a destination option header, and the first two digits of the Option Type of the Destination Options header are 00 or 01, to indicate that the destination node does not recognize the header. The option type normally processes the remainder of the data message carrying the destination option header except the option type or discards the data message.

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

The data packet receiving module is configured to: receive the AID data packet and the RID data packet, where the source and destination addresses in the packet header of the AID data packet are the source and destination end access identifiers of the AID data packet (AID), the source and destination addresses in the header of the RID data packet are the source and destination RID of the RID data packet;

The data packet parsing module is configured to: parse the data packet received by the data packet receiving module, and notify the data packet conversion module to the AID data if the parsed data packet is an AID data packet The packet is converted. If the parsed data packet is a RID data packet, and the destination RID of the RID data packet points to the current access device, and the RID data packet does not carry the packet extension header, the datagram is notified. The text processing module processes the RID data packet;

The data packet conversion module is configured to: replace the source and destination addresses in the header of the AID data packet with the source and destination routing identifiers (RIDs) to generate the RID data packet, and send the RID to the terminal. A packet extension header is added to the data packet, where the packet extension header includes the source and destination AIDs, and the data packet sending module is notified to forward the generated RID data packet.

The data packet recovery module is configured to: replace the source and destination addresses in the header of the RID data packet with the source and destination AIDs in the packet extension header, and delete the AID data of the packet extension header to be restored. Transmitting, and notifying the data packet sending module to forward the restored AID data packet to the terminal pointed to by the destination AID;

a data packet processing module, configured to process the RID data packet of the packet extension header to the current access device, and not to carry the packet extension header;

A data packet sending module is configured to route and forward the AID data packet and the RID data packet. Preferably, the data packet parsing module is further configured to: if the data packet received by the data packet receiving module is a RID data packet of the other end device, the notification data packet sending module points to the destination RID The other access devices forward the RID data message.

Preferably, the extension header is an IPV6 packet extension header.

To solve the above technical problem, the present invention further provides another data packet transmission method, which is implemented based on an identity identifier and a location separation network, and includes:

The source access device (ASN) receives the AID data packet, where the source and destination addresses in the packet header are the source and destination access identifiers (AIDs);

The source ASN converts the AID data packet into a RID data packet, and replaces the source and destination access identifiers (AIDs) with the source and destination (RID), and adds the RID data packet to the terminal. a packet extension header, where the packet extension header includes the source and destination AIDs; and the source ASN sends the generated RID data packet to the destination ASN;

The destination end ASN receives the R1D data packet, and forwards the R1D data packet carrying the packet extension header, and directly processes the RID data packet that does not carry the packet extension header.

Preferably, before forwarding the RID data packet, the destination ASN replaces the source and destination RIDs of the RID data packet with the source and destination AIDs, and deletes the packet extension header to obtain the restored AID data packet, and then Forwarding the AID data packet to the terminal pointed to by the destination AID.

Preferably, the extension header is an IPV6 packet extension header.

To solve the above technical problem, the present invention further provides another access device, where the access device (ASN) is located in the identity identification and the location separation network, and includes:

The data packet receiving module is configured to: receive the AID data packet when the ASN is the source ASN, and receive the RID data packet, where the AID data packet is the packet when the ASN is the destination ASN. The source and destination addresses in the header are the source and destination access identifiers (AIDs) of the AID data packet, and the source and destination addresses in the header of the RID data packet are the source and destination of the RID data packet. RID;

The data packet parsing module is configured to: parse the data packet received by the data packet receiving module, and if the parsed data packet is an AID data packet, or the parsed data packet is an RID data packet and carries the packet extension The first packet is sent to the data packet forwarding module to forward the parsed data packet. If the parsed data packet is a RID data packet and does not carry the packet extension header, the data packet processing module is notified to the RID datagram. Processing

The data packet forwarding module is configured to: when the ASN is used as the source ASN, replace the source and destination addresses in the header of the AI data packet with the source and destination routing identifiers (RIDs) to generate the RID datagram. And adding a packet extension header to the RID data packet sent to the terminal, where the packet extension header includes the source and destination AIDs, and forwards the destination ASN to the destination end RID. And the RID data packet is forwarded to the terminal in the ASN when the ASN is used as the destination ASN;

The data packet processing module is configured to process the RID data packet that the destination end RID points to the current access device and does not carry the packet extension header.

Preferably, the data packet forwarding module is further configured to first source and destination the RID data packet.

The RID is replaced with the source and destination AIDs, and the AID data packet obtained by the packet extension header is deleted, and the restored AID data packet is forwarded to the terminal pointed to by the destination AID.

Preferably, the extension header is an IPV6 packet extension header.

Preferably, the IPV6 text extension header is a destination option header, and the first two digits of the Option Type of the Destination Options header are 00 or 01, indicating that the destination node does not recognize the option. The type of the data message carrying the destination option header is normally processed except for the option type or the data message is discarded.

In the data packet transmission method and the access device of the present invention, the source access device (ASN) converts the AID data packet that needs to be sent to the terminal, including the replacement source and the destination access identifier (AID) as the source and destination. The route identifier (RID) is added to the packet extension header. The destination end ASN forwards or directly processes the received data packet according to whether the packet extension header is included, so as to implement the correct processing of the data packet by the ASN.

BRIEF abstract

Figure 1 is a system architecture diagram of the SILSN network;

Figure 2 is a schematic diagram of data packet processing by the SILSN network;

3 is a schematic flowchart of a data packet transmission method according to the present invention;

4 is a schematic flowchart of a data packet transmission method according to the present invention;

5 is a schematic structural diagram of a module of an access device according to the present invention;

FIG. 6 is a schematic structural diagram of another module of an access device according to the present invention.

Preferred embodiment of the invention The manner in which the data message is transmitted from the source ASN to the destination ASN is a major problem to be solved by the present invention. The main idea of the data packet transmission method and the access device of the present invention is that the source access device (ASN) converts the AID data packet that needs to be sent to the terminal, including the replacement source and the destination access identifier (AID). For the source and destination route identifiers (RIDs) and the extension headers, the destination ASN forwards or directly processes the received data packets according to whether the packet extension header is included, so that the ASN can correctly process the data packets. As shown in FIG. 3, the data packet transmission method of the present invention includes the following steps:

Step 301: The source access device (ASN) receives the AID data packet, where the source and destination addresses in the packet header are the source and the destination access identifier (AID).

Step 302: The source ASN converts the AID data packet that needs to be sent to the terminal into an RID data packet, including the replacement source and destination access identifier (AID) as the source and destination RID, and sends the RID data packet to the terminal. Add a message extension header;

Step 303: The destination end ASN receives the RID data packet, and forwards the RID data packet carrying the packet extension header, and directly processes the RID data packet that does not carry the packet extension header.

Destination ASN refers to the ASN pointed to by the destination RID of the data packet. The data packet whose source and destination address are AID is called the AID data packet or the first data packet, and the data packet whose source and destination address are RID is called RID data packet or second data packet.

The extension header includes the source and destination terminal identifier information, and is preferably the source and destination AIDs. Before the destination ASN forwards the RID data packet, the RID data packet is converted into the AID data packet, including The source and destination RIDs are replaced with the source and destination AIDs, and the packet extension header is deleted, and then the destination AID is directed to the terminal to forward the AID data packet.

In the present invention, when the packet of ASN1 to ASN2 is transmitted by IPV6, for the data packet addressed to the end user, ASN1 does not use another method of encapsulating an IP header, and the destination address and source address in the IP header are used. Replace the destination AID and the source AID with the destination RID and the source RID, respectively, and then add an extension header to the IP header, and attach the destination AID and the source AID to the extension header of the IPV6 message, such as the destination address extension option. The packet sent by the ASN1 to the end user under the ASN2 carries the extended packet header, as shown in the following Table 2: Table 2 shows the data transmission method used by the present invention.

New IPV6 packet header IPV6 packet extension header

The packet sent by ASN1 and sent to ASN2 itself can use the regular IPV6 packet, that is, it does not carry the extended packet header.

After the IPV6 extension header method is adopted, the destination end ASN only needs to check whether the data packet has the corresponding extended packet header. If there is an extended packet header, it is sent to the lower terminal, and if not, it is sent to the core such as the destination ASN. The network node enables the core network node to correctly distinguish and process the packets sent to the core network node itself and the packets sent to the terminal user.

The following describes the extension header of the existing IPV6 data packet:

The IPV6 header shown in Table 3 is defined in the IPV6 protocol (RFC2460) to carry additional Internet information:

table 3

Version priority

Flow Label

(Version) (Prio. )

Next packet header hop limit

Payload Length

(Next Header) (Hop Limit) Source Address (Source Address )

Destination Address

RFC2460 proposes to add an IPV6 extension header between the header of the IPV6 and the header of the upper layer. RFC2460 defines six types of extended packet headers, which are Hop-by-Hop Options header, Routing header, Fragment header, Authentication header, and ESP. Encapsulating Security Payload header, Destination Options header. RFC2460 defines a protocol number for each extension header, such as a hop-by-hop option header of 0 and a destination option header of 60. When an Internet application needs to use the IPV6 message extension header to deliver information, simply set the next header in Table 5 to the corresponding protocol number. For example, if you need to pass data in the message using the destination option header, you only need to set the next header in Table 5 (Next Header) to 60.

The various IPV6 extension headers can coexist in a certain order, as shown in Table 4. Immediately after the IPV6 header is the routing header, then the destination option header, and finally the TCP packet header.

Table 4

Among the six extension headers defined in IPV6, the destination option header is used to carry information that is only checked by the destination node. The message format of the destination option header is as shown in Table 5 below:

The Next Header indicates the next protocol header type, and Hdr Ext Len indicates the length of the destination option extension header, in units of 8 bytes, excluding the first byte.

In RFC2460, the options are further composed of Option Type, Opt Data Len, and option data. The first three bits of the option type are specified, and the first and second bits specify the action taken by the node that processes the IPV6 data message without knowing the tag:

00 - Skip this option to continue processing the message header

01 - Discard this article. 10 - Discard this 4 text, send ICMP (Internet Control Message Protocol,

ICMP)

11 - Discard this message, send ICMP when it is not a multicast address

In addition, RFC2460 has the following three bits for the Option Type: 1 if the option data affects the route, and 0 if it does not.

For the 8-bit Option Type, except for the first three digits above, only 5 digits are optional, that is, there are actually only 32 numbering spaces. Currently, the RFC has specified a destination option for the mobile IP protocol, called the home address. The Home Address option, whose value defines 0xC9, has a lower 5 bits of 00111 and occupies the sequence number 9.

The option length is in bytes and describes the actual length of the option data. The embodiment of the method is generally set to 12.

Since the destination option header is used to carry information that is only checked by the destination node, and the indication information in the extension header of the present invention is used only by the destination ASN, the present invention preferably uses the destination option header to expand.

The following describes a specific method for carrying the user source address information by using the destination option header of the IPV6. Table 6 shows:

Table 6

Next packet header Header extension length Option type Option data length

(Next Header) (Hdr Ext Len) (Option type) ( Opt Data Len) Source address identifier (128 bits) Destination address identifier (128 bits) In the table, the next header (Next Header) and the header extension length (Hdr Ext Len ) has the same meaning as above, and is not described here. The following describes the new or newly defined destination extension header options of the present invention: 1, option type (Option Type):

The option type in the destination option header has a total of 8 bits:

For the upper 2 bits, the present invention does not make special provisions, and can be set by the node processing device according to the situation. For example, when the security level is relatively high, such as the public security network, this option can be set to 01, that is, if this is handled The node of the data packet does not recognize this data format and discards the entire packet. For a general type of node, it can be set to 00, so that even if the node does not recognize this option, the entire data packet can be processed normally, thereby improving system compatibility and maximizing the use of the original device. For the third bit, In the invention, the intermediate node will process this option, and the option data will affect the route, so it is set to 1;

For the lower 5 digits, you can select any one of the 31 serial numbers other than the serial number option 00111 to expand. For example, the lower 5 digits use 11000 for expansion.

The invention 01111000, that is, 0X98, represents that when the destination node does not recognize this option, the rest of the data message is still processed normally.

2, source address identification

The source address identifier here refers to the source address identifier of the end user that sends the data packet, that is, the user ID AID1 of UE1. When using IPV6 transmission, the source address identifier also uses 128 bits.

3, destination address identification

The destination address identifier here refers to the source address identifier of the terminal user that receives the data packet, that is, the user identifier AID2 of UE2. When using IPV6 transmission, the destination address identifier also uses 128 bits.

The following is a preferred implementation of the data packet transmission method of the present invention. The packet extension header includes a best implementation manner of the source and destination AIDs, and the method includes:

The first access device receives and parses the first data packet, where the source and destination addresses in the packet header are the source and the destination access identifier (AID);

B. The first access device replaces the source and destination addresses in the packet header with the source and destination routes. The identifier (RID) generates a second data packet, and adds a packet extension header to the second data packet sent to the terminal, where the packet extension header includes the source and destination AIDs, and the second access device Forwarding the second data packet;

The second access device receives the second data packet, and determines whether the second data packet carries a packet extension header. If the packet is carried, step D is performed, and if not, step E is performed;

In the step C, after the second access device receives the second data packet, it is determined that the destination RID is directed to the second access device before the packet extension header is carried.

In step C, after the second access device receives the second data packet, it is determined whether the destination RID points to the second access device, and if the destination RID is pointed to the second access device, Then, it is determined whether the packet extension header is carried. If the destination RID does not point to the second access device, the access device pointed to by the destination RID directly forwards the second data packet.

D. The second access device replaces the source and destination addresses in the packet header of the second data packet with the source and destination AIDs in the packet extension header, and deletes the packet extension header to be restored to the first a data packet, forwarding the first data packet to a terminal pointed to by the destination AID;

E. The second access device processes the second data packet.

FIG. 4 is a schematic diagram of data transmission by using the method. After the data packet sent by the user is converted by ASN1 and ASN2 twice, it is finally sent to UE2. The data packet can be correctly sent to UE2 regardless of where UE2 roams. . As shown in Figure 3, the following steps are included:

Step 401: The user terminal UE1 sends an end-to-end data packet with the data format of the IPV6 to the ASN1. The destination address is the user identifier AID2 of the UE2, and the source address is the user address AID1 of the UE1. Table 7 Examples of the data packet sent by the UE1 Version priority

Flow Label

(Version) ( Prio. )

Next packet header hop limit

Payload Length

=TCP (Hop Limit ) Source Address =AID1

Destination address = AID2 TCP packet In the above table, the data packet sent by user UE1 is a TCP packet, where the source address is AID1 and the destination address is AID2.

Step 402: The ASN1 queries whether the location of the AID2 is stored. If not, the location of the AID2 is requested from the ILR.

Step 403, the ILR returns the location information RID2 of the access server where the user is located to the ASN1;

Step 404: ASN1 replaces the source address and the destination addresses AID1 and AID2 in the IPV6 data packet with RID1 and RID2, respectively, and adds the destination extension option corresponding to the IPV6 extension header. Step 405: ASN1 sends the converted data packet. To ASN2;

Table 8 Examples of data packets sent by ASN1

Version priority

Flow Label

(Version) ( Prio. )

Next packet header hop limit

Payload Length

= Destination Option (Hop Limit) Source Address (Source Address) = RID1

Destination Address = RID2 Next Header Header Extension Length Option Type = Destination Option Data Length = TCP (Hdr Ext Len) Option (Opt Data Len) Source Address Identifier (128 bits) = AID1 Destination Address Identification (128 bit) = AID2

TCP packet

ASN1 queries the location of AID2 to the ILR, changes the destination address to RID2, and changes the source address to RID1. At the same time, in order to facilitate ASN2 to send the message to AID2, the source user ID and destination user IDs AID1 and AID2 are also placed in the data. Packets are carried. The carrying method is to add an IPV6 packet extension header option. The option type is destination option. AID1 and AID2 are carried in the options.

Step 406: The ASN2 determines that the RID2 is directed to itself and the data packet carries the extension header, and replaces the source address and the destination addresses RID1 and RID2 in the data packet with AID1 and AID2, respectively, and deletes the destination extension option corresponding to the IPV6 extension header.

Step 407: The ASN2 sends the converted data packet to the UE2.

Table 9 Examples of data packets sent by ASN2 Version priority

Flow Label

(Version) ( Prio. )

Next packet header hop limit

Payload Length

=TCP (Hop Limit ) Source Address =AID1

Destination Address = AID2

When the data packet is sent to the ASN2, the ASN2 checks whether the data packet carries the corresponding destination option. If it is carried, the source address AID1 and the destination address AID2 are extracted, and then the source of the IPV6^艮文The address RID1 and the destination address RID2 are changed to the addresses AID1 and AID2 of the terminal respectively, and then the destination option added by ASN1 is deleted, and the converted data message is sent to UE2.

The method of using the IPV6 text extension header to carry the source user identifier and the destination identifier, and distinguishing the packet sent to the terminal user and the packet sent to the core network node, so that the SILSN network has practicality.

To achieve the above method, the present invention further provides an access device, where the access device is located in an identity identifier and a location separation network, as shown in FIG. 5, including:

The data packet receiving module is configured to receive the AID data packet and the RID data packet, wherein the source and destination addresses in the packet header of the AID data packet are the source, the destination access identifier (AID), and the RID datagram. The source and destination addresses in the header of the text are the source and destination RIDs;

The data packet parsing module is configured to: parse the data packet received by the data packet receiving module, and if the data packet is an AID data packet, notify the data packet conversion module to perform conversion; if the data packet is a RID datagram The destination RID points to the current access device, and the data packet carries the packet extension header, and then the data packet recovery module is notified to restore; if the data packet is a RID data packet, and the destination RID points to the current access The device does not carry the packet extension header. According to the message processing module for processing;

The data packet conversion module is configured to: replace the source and destination addresses in the packet header with the source and destination routing identifiers (RIDs) to generate RID data packets, and add the packets in the data packets sent to the terminal. An extension header, where the packet extension header includes the source and destination AIDs, and the data packet sending module is notified to forward the RID data packet;

The data packet recovery module is configured to: replace the source and destination addresses in the header of the RID data packet with the source and destination AIDs in the packet extension header, and delete the packet extension header to be restored to the AID datagram. And notifying the data packet sending module to forward the restored AID data packet to the terminal pointed to by the destination end AID;

A data packet sending module is configured to route and forward the AID data packet and the RID data packet. Further, the data packet parsing module is further configured to: if the data packet received by the data packet receiving module is a RID data packet of the other end device, the notification data packet sending module points to the destination RID The other access devices forward the RID data message.

Further, the packet extension header is an IP V6 packet extension header.

The IPV6艮艮 extended header is a destination option header, and the first two digits of the Option Type of the Destination Options header are 00 or 01, indicating that the destination node does not recognize the option type. The data packet carrying the destination option header is normally processed except for the option type or the data packet is discarded.

The present invention further provides another access device, where the access device (ASN) is located in an identity identification and a location separation network. As shown in FIG. 6, the access device includes:

The data packet receiving module is configured to: when the ASN is used as the source ASN, receive the AID data packet; when the ASN is the destination ASN, receive the RID data packet, where the source in the packet header of the AID data packet The destination address is the source and the destination access identifier (AID), and the source and destination addresses in the header of the RID data packet are the source and destination RID.

The data packet parsing module is configured to: parse the data packet received by the data packet receiving module, and if the data packet is an AID data packet, or the data packet is an RID data packet, and the packet extension is carried The header notifies the data packet forwarding module to forward; if the data packet is a RID data packet, and the packet does not carry the packet extension header, the data packet processing module is notified to perform processing;

The data packet forwarding module is configured to: when the ASN is used as the source ASN, replace the source and destination addresses in the header of the AID data packet with the source and destination routing identifiers (RIDs) to generate RID data packets. And adding a packet extension header to the RID data packet sent to the terminal, where the packet extension header includes the source and destination AIDs, and forwards the RID data packet to the destination end ASN pointed to by the destination end RID; When the ASN is used as the destination ASN, the RID data packet received by the data packet receiving module is forwarded to the terminal in the ASN;

Further, the data packet forwarding module converts the RID data packet into an AID data packet, and replaces the source and destination RIDs with the source and destination AIDs before forwarding the RID data packet to the terminal in the ASN. The message extension header is deleted, and the AID data packet is forwarded to the destination AID to the terminal.

Further, the packet extension header is an IP V6 packet extension header.

Further, the IPV6艮艮 extended header is a destination option header, and the first two digits of the Option Type of the Destination Options header are 00 or 01, to indicate that the destination node is not When the type of the option is recognized, the data packet carrying the destination option header is normally processed except for the option type or the data packet is discarded.

Industrial applicability

Compared with the prior art, in the data packet transmission method and the access device of the present invention, the source access device converts the AID data packet that needs to be sent to the terminal, and the destination end ASN includes the header extension according to whether the packet is extended. The received data packet is forwarded or directly processed to implement correct processing of the data packet by the ASN.

Claims

Claim

A method for transmitting a data packet, wherein the method is implemented based on an identity identifier and a location separation network, the method comprising:

A. The first access device receives and parses the first data packet, where the source and destination addresses in the packet header of the first data packet are the source and destination end access identifiers AID;

The first access device generates the second data packet by sending the source and destination addresses in the packet header of the first data packet to the source and destination routing identifiers RID, respectively, and sends the second data packet. Adding a packet extension header to the second data packet of the terminal, where the packet extension header includes the source and destination AIDs, and the first access device forwards the generated second packet to the second access device. The second access device receives the second data packet sent by the first access device, and determines whether the received second data packet carries the packet extension header. If the packet is carried, step D is performed. If not, perform step E;

D. The second access device replaces the source and destination addresses in the packet header of the received second data packet with the source and destination AIDs in the packet extension header, and deletes the packet extension header. Obtaining the restored first data packet, and forwarding the restored first data packet to the terminal pointed to by the destination end AID;

E. The second access device processes the received second data packet.

The method of claim 1, before the step of determining whether the received second data packet carries the packet extension header, the method further comprising: determining, by the second access device, that the destination end RID points to the Second access device.

The method of claim 1, further comprising: after receiving the second data packet sent by the first access device, determining, by the second access device, whether the destination RID points to the second access If it is determined that the destination RID does not point to the second access device, if it is determined that the destination RID points to the second access device, The access device pointed by the destination RID directly forwards the received second data packet.

4. The method according to claim 1, wherein the packet extension header is an IP V6 message extension header.

5. The method according to claim 4, wherein the IP V6 message extension header is a destination option header, and the first two bits of the option type of the destination option header are 00 or 01 to indicate that the destination node is When the option type is not known, the remaining part of the data message carrying the destination option header except the option type is normally processed or the data message carrying the destination option header is discarded.

An access device, where the access device is located in an identity identifier and a location separation network, where the access device includes:

a data packet receiving module, configured to receive an access identifier AID data packet and a routing identifier RID data packet, where the source and destination addresses in the header of the AID data packet are respectively the AID data Source and destination AID, the source and destination addresses in the header of the RID data are respectively the source and destination RID of the RID data;

The data packet parsing module is configured to: parse the data packet received by the data packet receiving module, and if the parsed data packet is an AID data packet, notify the data packet conversion module to convert the AID data packet; If the parsed data packet is a RID data packet that does not carry the packet extension header, and the destination RID of the RID data packet points to the current access device, the data packet processing module is notified to perform the RID data packet. deal with;

The data packet conversion module is configured to: replace the source and destination addresses in the header of the AID data packet with the source and destination RIDs to generate the RID data packet, and send the RID data packet to the terminal. Adding a message extension header, the packet extension header includes a source and a destination AID of the RID data packet, and notifying the data packet sending module to forward the generated RID data packet;

The data packet recovery module is configured to: replace the source and destination addresses in the header of the RID data packet carrying the packet extension header with the source and destination AIDs in the "3⁄4 text extension header", and delete the data packet recovery module. The packet extension header obtains the restored AID data packet, and the data packet sending module is notified to forward the restored AID data packet to the terminal pointed to by the destination AID;

A data packet sending module is configured to route and forward the AID data packet and the RID data packet.

The access device according to claim 6, wherein the data packet parsing module further sets If the data packet received by the parsed data packet receiving module is a RID data packet of the access device other than the current device, the data packet sending module is notified to the other access device. The device forwards the parsed RID data packet.

The access device according to claim 6, wherein the packet extension header is an IP V6 packet extension header.

The access device according to claim 8, wherein the IP V6 message extension header is a destination option header, and the first two bits of the option type of the destination option header are 00 or 01, to indicate that When the destination node does not recognize the option type, the data packet carrying the destination option header is normally processed except for the option type or the data packet carrying the destination option header is discarded.

A data packet transmission method, characterized in that the method is implemented based on an identity identifier and a location separation network, and the method includes:

The source access device ASN receives the access identifier AID data packet, and the source and destination addresses in the header of the AID data packet are the source and destination AID respectively;

The source ASN replaces the source and destination AIDs in the header of the AID data packet with the source and destination routing identifiers RID to generate RID data packets and send RID data packets to the terminal. Adding a message extension header, where the packet extension header includes the source and destination end AIDs;

The source ASN sends the generated RID data packet to the destination ASN;

The destination end ASN receives the RID data packet sent by the source ASN, and forwards the RID data packet carrying the packet extension header, and directly processes the RID data packet that does not carry the packet extension header.

The method of claim 10, wherein the step of forwarding the RID data packet carrying the packet extension header comprises: first, in the header of the RID data packet carrying the packet extension header The source and destination RIDs are replaced with the source and destination AIDs, and the AID data packet is deleted from the packet extension header, and then the restored AID data packet is forwarded to the terminal pointed by the destination AID.

The method according to claim 10, wherein the packet extension header is an IP V6 message extension. Exhibition head.

13. The method according to claim 12, wherein the IPV6 message extension header is a destination option header, and the first two bits of the option type of the destination option header are 00 or 01, to indicate that when the destination node is not When the type of the option is recognized, the remaining part of the data message carrying the destination option header except the option type is normally processed or the data message carrying the destination option header is discarded.

An access device, where the access device ASN is located in an identity identifier and a location separation network, and includes:

The data packet receiving module is configured to: receive the access identifier AID data packet when the ASN is the source ASN; and receive the route identifier RID data packet when the ASN is the destination ASN, where the The source and destination addresses in the header of the AID data packet are the source and destination AID of the AID data packet, and the source and destination addresses in the header of the RID data packet are respectively the RID data. Source and destination RID of the text;

The data packet parsing module is configured to: parse the data packet received by the data packet receiving module, when the parsed data packet is an AID data packet, or when the parsed data packet is an RID data packet, and the When the RID data packet carries the packet extension header, the notification data packet forwarding module forwards the parsed data packet; the parsed data packet is a RID data packet, and the RID data packet does not carry the packet extension. In the header, the data packet processing module is notified to process the RID data packet. The data packet forwarding module is configured to: when the ASN is used as the source ASN, by using the AID data packet in the packet header. The source and destination addresses are replaced with the source and destination RIDs to generate RID data packets, and the packet extension header is added to the RID data packet sent to the terminal, where the packet extension header includes the source and destination ends. The AID forwards the generated RID data packet to the destination ASN pointed to by the destination RID; and, when the ASN is the destination ASN, sends the RID data packet to the terminal. Forwarding terminal under the ASN;

The access device according to claim 14, wherein the data packet forwarding module is configured to forward the RID data packet sent to the terminal to the terminal under the ASN by: The source and destination RIDs of the RID data packet sent to the terminal are replaced with the source and destination AIDs respectively, and the AID data packet obtained by the packet extension header is deleted, and then the terminal pointed to the destination AID is redirected. Forwarding the restored AID data message.

The access device according to claim 14, wherein the packet extension header is an IPV6 message extension header.

The access device according to claim 16, wherein the IPV6 message extension header is a destination option header, and the first two digits of the option type of the destination option header are 00 or 01, to indicate that the destination is When the node does not recognize the option type, the data packet carrying the destination option header is normally processed except for the option type or the data packet carrying the destination option header is discarded.