CN108322400B

CN108322400B - Message processing method, system and routing equipment

Info

Publication number: CN108322400B
Application number: CN201711387698.7A
Authority: CN
Inventors: 叶宇煦; 查敏
Original assignee: Huawei Technologies Co Ltd
Current assignee: XFusion Digital Technologies Co Ltd
Priority date: 2012-06-05
Filing date: 2012-06-05
Publication date: 2021-06-08
Anticipated expiration: 2032-06-05
Also published as: WO2013181991A1; CN103457856B; CN103457856A; CN108322400A

Abstract

The application provides a message processing method, a message processing system and routing equipment. The terminal communicates with the destination device through the first routing device via the IPv6 network and through the second routing device, and all IPv4 messages initiated by the terminal need to be sent to the destination device via the first routing device and the second routing device, so that a star-shaped communication mode is implemented in an application scenario of the MAP technology, and the management capability of the second routing device, that is, the network-side device, on user communication traffic can be improved.

Description

Message processing method, system and routing equipment

The application is a divisional application of an application with the application date of 2012, 6 and 5, the application number of 201210183101.8 and the invention name of 'message processing method, system and routing equipment' submitted to the intellectual property office of China.

Technical Field

The present application relates to communications technologies, and in particular, to a method, a system, and a routing device for processing a packet.

Background

The large-scale application of Internet technology has greatly increased the demand for Internet Protocol (IP) addresses. The IP version 6(IPv6) is a new generation network protocol, adopts a 128-bit address format, has huge address space, and can thoroughly solve the problem of insufficient IP version 4(IPv4) addresses. But in the smooth migration process from the internet to the IPv6, the IPv4 service still needs to maintain continuity. The Mapping of Address and Port (MAP) is a transition technology from IPv4 to IPv6, and mainly aims at an application scenario where an access network adopts pure IPv6, and main network elements of technology application include a Border Relay Router (Border Router, BR) located between an IPv6 network and an IPv4 network and a Customer Edge Router (CE) located at a Border of a Customer network. The CE obtains an IPv4 address of the CE according to an IPv6 prefix allocated to the CE and a Basic Mapping Rule (BMR) issued by a Dynamic Host configuration Protocol (for IPv6, DHCPv6) server supporting IPv6, where the IPv4 address may be shared (not shared) or shared. When the IPv4 address of the CE is a shared address, a Port-Set Identifier (PSID) of the CE may be further obtained. The CEs using the same Mapping Rule may form a MAP domain, and the CEs in the same MAP domain may directly communicate with their respective IPv4 addresses and IPv6 addresses by using their Mapping rules, where the Mapping rules may include BMR, Forwarding Mapping Rule (FMR), and Default Mapping Rule (DMR) that provides IPv6 addresses or prefixes of BRs.

However, direct communication between CEs makes it impossible for the network side device to perform management operations on these user communication traffic, such as: flow control, statistics, etc., resulting in a reduction of the management capability of the network side device.

Disclosure of Invention

The application provides a message processing method, a message processing system and routing equipment in multiple aspects, and is used for improving the management capacity of network side equipment on user communication flow.

One aspect of the present application provides a method for processing a packet, including:

a first routing device receives an IPv4 message, wherein the IPv4 message contains a destination IPv4 address;

the first routing equipment encapsulates or translates the IPv4 message into an IPv6 message by using an IPv6 address or prefix of the second routing equipment and sends the IPv6 message to the second routing equipment, so that the second routing equipment updates a source IPv4 address carried by the IPv6 message according to a first BMR and a source IPv6 address of the IPv6 message, matches routing information corresponding to the target IPv4 address by using the first BMR, and forwards the content of the IPv4 message according to the routing information.

Another aspect of the present application provides a method for processing a packet, including:

the second routing equipment receives an IPv6 message sent by the first routing equipment, wherein the IPv6 message is obtained by packaging or translating the IPv4 message by using an IPv6 address or prefix of the second routing equipment after the first routing equipment receives the IPv4 message, and the IPv4 message contains a target IPv4 address;

the second routing equipment updates a source IPv4 address carried by the IPv6 message according to the first BMR and the source IPv6 address of the IPv6 message, and matches routing information corresponding to the target IPv4 address by using the first BMR;

and the second routing equipment forwards the content of the IPv4 message according to the routing information.

In another aspect of the present application, there is provided a routing device, including:

the first receiver is used for receiving an IPv4 message, wherein the IPv4 message contains a destination IPv4 address;

the processor is used for packaging or translating the IPv4 message into an IPv6 message by utilizing the IPv6 address or prefix of the second routing equipment;

a sender, configured to send the IPv6 packet to the second routing device, so that the second routing device updates a source IPv4 address carried in the IPv6 packet according to the first BMR and the source IPv6 address of the IPv6 packet, matches, by using the first BMR, routing information corresponding to the destination IPv4 address, and forwards the content of the IPv4 packet according to the routing information.

a receiver, configured to receive an IPv6 packet sent by a first routing device, where the IPv6 packet is obtained by encapsulating or translating an IPv4 packet by using an IPv6 address or prefix of the routing device after the first routing device receives the IPv4 packet, and the IPv4 packet includes a destination IPv4 address;

the processor is used for updating a source IPv4 address carried by the IPv6 message according to the first BMR and the source IPv6 address of the IPv6 message, and matching routing information corresponding to the target IPv4 address by using the first BMR;

and the sender is used for forwarding the content of the IPv4 message according to the routing information.

In another aspect of the present application, a message processing system is provided, which includes the routing device in the above two aspects.

According to the technical scheme, the terminal communicates with the destination device through the first routing device via the IPv6 network and through the second routing device, and all IPv4 messages initiated by the terminal need to be sent to the destination device through the first routing device and the second routing device, so that a star-shaped communication mode is realized in an application scene of an MAP technology, and the management capability of the second routing device, namely network side device, on user communication traffic can be improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below. It should be apparent that the drawings in the following description are examples of the present application and that other drawings may be derived by those skilled in the art without inventive exercise.

Fig. 1 is a schematic flow chart of a message processing method according to an embodiment of the present application;

FIG. 2 is a diagram illustrating an application scenario of the MAP technique employed in the embodiment corresponding to FIG. 1;

FIG. 3 is a diagram illustrating a mapping relationship of a second BMR according to the embodiment of FIG. 1;

FIG. 4 is a diagram illustrating a mapping relationship of the first BMR in the embodiment corresponding to FIG. 1;

FIG. 5 is a diagram illustrating another mapping relationship of the first BMR in the embodiment corresponding to FIG. 1;

FIG. 6 is a diagram illustrating another mapping relationship of the second BMR in the embodiment corresponding to FIG. 1;

FIG. 7 is a diagram illustrating another mapping relationship of the second BMR in the embodiment corresponding to FIG. 1;

fig. 8 is a schematic flowchart of a message processing method according to another embodiment of the present application;

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

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

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

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

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

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The technical scheme of the application can be applied to an application scene adopting the MAP technology (see draft-mdt-softwire-mapping-address-and-port-03). The first routing device may be a Customer Edge Router (CE), a Customer Premise Equipment (CPE), or a Customer Gateway device (identified Gateway) located at a boundary of a subscriber network; the second routing device may be a Border Relay Router (BR) or a Port-Range Router (PRR) located between the IPv6 network and the IPv4 network.

Fig. 1 is a schematic flowchart of a message processing method according to an embodiment of the present application, and fig. 2 is a schematic view of an application scenario of a MAP technique adopted in the embodiment corresponding to fig. 1, as shown in fig. 1 and fig. 2.

101. And the first routing equipment receives an IPv4 message, wherein the IPv4 message contains a destination IPv4 address.

102. The first routing equipment encapsulates or translates the IPv4 message into an IPv6 message by using an IPv6 address or prefix of the second routing equipment and sends the IPv6 message to the second routing equipment, so that the second routing equipment updates a source IPv4 address carried by the IPv6 message according to a first BMR and a source IPv6 address of the IPv6 message, matches routing information corresponding to the target IPv4 address by using the first BMR, and forwards the content of the IPv4 message according to the routing information.

Specifically, the first routing device may specifically implement, through two functional modules, encapsulation or Translation of the IPv4 packet into an IPv6 packet, that is, Network Address Translation (NAT) 44 and MAP. In the NAT44 module, the private network IPv4 address and port in the received IPv4 message are converted into a public network IPv4 address; in the MAP module, the IPv4 message processed by the NAT44 module is encapsulated or translated into an IPv6 message.

It can be understood that, the first routing device may also specifically implement, through one functional module, encapsulation or translation of the IPv4 message into an IPv6 message, which is not limited in this embodiment.

The IPv6 message may specifically carry a source IPv4 address (i.e., a public network IPv4 address) in two ways: one way is that for the encapsulation condition, the packet header of the IPv4 packet is used for carrying; the other way is that for the translation condition, the translation condition is carried by a field in an Interface identifier (Interface ID) of a source IPv6 address of the IPv6 message.

In this embodiment, the terminal communicates with the destination device through the IPv6 network via the first routing device and through the second routing device, and all IPv4 messages initiated by the terminal need to be sent to the destination device through the first routing device and the second routing device, so that a star communication mode is implemented in an application scenario of the MAP technology, and the management capability of the second routing device, that is, the network side device, on user communication traffic can be improved.

Optionally, in an optional implementation manner of this embodiment, in a scenario where different first routing devices share a public network IPv4 address, before 102, the first routing device receives a PSID of the first routing device and an IPv6 address or prefix of the second routing device, which are issued by a Dynamic Host configuration Protocol (Dynamic Host configuration Protocol for IPv6, DHCPv6) server that supports IPv6, and does not issue a BMR, so that the first routing device cannot obtain the public network IPv4 address of the first routing device according to the BMR. Correspondingly, in 102, since the first routing device cannot use the BMR to match the routing information corresponding to the destination IPv4 address, the first routing device may use the IPv6 address or prefix of the second routing device to encapsulate or translate the IPv4 packet into an IPv6 packet, and send the IPv6 packet to the second routing device. In addition, since the first routing device cannot obtain the public network IPv4 address, the source IPv4 address carried by the IPv6 packet sent by the first routing device may be a specific IPv4 address, for example: 192.0.0.2, or all 0's, or all 1's, etc. used to identify B4 in the IANA application registration for specific unicast IPv4 addresses, or similar DS-lite technologies.

Take the first routing device as the CE located at the boundary of the user network and the second routing device as the BR located between the IPv6 network and the IPv4 network as an example. The DHCPv6 server includes the DMR for accessing the BR and the PSID of the CE in the parameters downloaded to the CE. The DMR comprises the IPv6 address or prefix of the BR. And the CE utilizes the DMR to package or translate the received IPv4 message into an IPv6 message and send the message to the BR. Since the complete BMR, i.e. the first BMR, is retained in BR, as shown in fig. 4. Therefore, the BR can obtain the public network IPv4 address of the CE according to the first BMR and the source IPv6 address of the IPv6 message from the CE, and update the source IPv4 address carried by the IPv6 message by using the public network IPv4 address; then, the BR may match routing information corresponding to the destination IPv4 address by using the first BMR, and forward the content of the IPv4 packet according to the routing information. For example: if the destination IPv4 address carried in the IPv6 message received by the BR can be matched with the rule IPv4 prefix in the first BMR of a certain MAP domain in the BR, it indicates that the BR will perform backhaul processing on the content of the IPv4 message by using an IPv6 message in a certain MAP domain where the destination device is located, that is, the content of the IPv4 message is sent to another CE through the BR; if the target IPv4 address carried by the IPv6 message received by the BR cannot be matched with the rule IPv4 prefix in the first BMR of any MAP domain in the BR, the BR forwards the content of the IPv4 message carried by the IPv6 message to an IPv4 public network.

The terminal communicates with the destination device through the IPv6 network via the CE and the BR, and all IPv4 messages initiated by the terminal need to be sent to the destination device via the CE and the BR, so that a star communication mode is realized in an application scene of an MAP technology, and the management capability of the BR on user communication traffic can be improved.

Optionally, in an optional implementation manner of this embodiment, in a scenario where different first routing devices share a public network IPv4 address, before 102, the first routing device receives an incomplete BMR (i.e., a second BMR) and a DMR issued by a Dynamic Host configuration Protocol (DHCPv 6) server, that is, the server does not issue a complete BMR (i.e., a first BMR), so that the first routing device cannot obtain the public network IPv4 address of the first routing device according to the second BMR. The second BMR provides only length information of the PSID. Optionally, the second BMR may further include a first Embedded Address (EA) bit length (EA bits), where the first EA bit length is used to indicate a length of a PSID in an IPv6 prefix allocated to the first routing device. The DMR is configured to access a second routing device, where the DMR includes an IPv6 address of the second routing device or an IPv6 prefix thereof. That is, before 102, the first routing device cannot match the routing information corresponding to the destination IPv4 address by using the second BMR. Correspondingly, in 102, since the first routing device cannot utilize an incomplete BMR (i.e., a second BMR), match the routing information corresponding to the destination IPv4 address, the first routing device encapsulates or translates the IPv4 packet into an IPv6 packet by using a DMR, and sends the IPv6 packet to the second routing device. In addition, since the first routing device cannot obtain the public network IPv4 address of the first routing device, the source IPv4 address carried by the IPv6 packet sent by the first routing device may be a specific IPv4 address, for example: 192.0.0.2 for B4, either all 0's or all 1's, etc., is applied for registration by the Internet Assigned Number Authority (IANA) for a specific unicast IPv4 address, or similar lightweight stack lite (DS-lite) technology.

Wherein the IPv6 prefix of the first routing device is assigned to the first routing device by an operator, such as: the DHCPv6 server delegates the IPv6 Prefix to the first routing device in a Prefix Delegation (DHCPv6 Prefix deletion, DHCPv6-PD) manner, or the IPv6 Prefix allocated to the first routing device by an operator Edge Router (Provider Edge Router) in a Stateless Address Auto-Configuration (SLAAC) manner.

Take the first routing device as the CE located at the boundary of the user network and the second routing device as the BR located between the IPv6 network and the IPv4 network as an example. The DHCPv6 server issues a DMR for accessing the BR and an incomplete BMR, that is, a second BMR, in a parameter issued to the CE, as shown in fig. 3, where the second BMR may further include a first EA bit length, and the first EA bit length is used to indicate a length of a PSID in an IPv6 prefix allocated to the CE. And the CE utilizes the DMR to package or translate the received IPv4 message into an IPv6 message and send the message to the BR. Since the complete BMR, i.e. the first BMR, is retained in BR, as shown in fig. 4. Therefore, the BR can obtain the public network IPv4 address of the CE according to the first BMR and the source IPv6 address of the IPv6 message from the CE, and update the source IPv4 address carried by the IPv6 message by using the public network IPv4 address; then, the BR may match routing information corresponding to the destination IPv4 address by using the first BMR, and forward the content of the IPv4 packet according to the routing information. For example: if the destination IPv4 address carried in the IPv6 message received by the BR can be matched with the rule IPv4 prefix in the first BMR of a certain MAP domain in the BR, it indicates that the BR will perform backhaul processing on the content of the IPv4 message by using an IPv6 message in a certain MAP domain where the destination device is located, that is, the content of the IPv4 message is sent to another CE through the BR; if the target IPv4 address carried by the IPv6 message received by the BR cannot be matched with the rule IPv4 prefix in the first BMR of any MAP domain in the BR, the BR forwards the content of the IPv4 message carried by the IPv6 message to an IPv4 public network.

Optionally, in an optional implementation manner of this embodiment, in a scenario that different first routing devices do not share a public network IPv4 address, before 102, the first routing device may further receive the DMR only issued by the DHCPv6 server, that is, the server only issues the DMR, and does not issue the BMR, so that the first routing device cannot obtain a public network IPv4 prefix or address of the first routing device according to the BMR. The DMR is configured to access a second routing device, where the DMR includes an IPv6 address of the second routing device or an IPv6 prefix thereof. Correspondingly, in 102, since the first routing device cannot use the BMR to match the routing information corresponding to the destination IPv4 address, the first routing device may use the DMR to encapsulate or translate the IPv4 packet into an IPv6 packet, and send the IPv6 packet to the second routing device. In addition, since the first routing device cannot obtain the public network IPv4 address, the source IPv4 address carried by the IPv6 packet sent by the first routing device may be a specific IPv4 address, for example: 192.0.0.2 for identification B4, either all 0's or all 1's, etc., in the specific unicast IPv4 address registered by the IANA application, or similar DS-lite technology.

Take the first routing device as the CE located at the boundary of the user network and the second routing device as the BR located between the IPv6 network and the IPv4 network as an example. The DHCPv6 server issues only the DMR for accessing the BR, but not the BMR, among the parameters issued to the CE. And the CE utilizes the DMR to package or translate the received IPv4 message into an IPv6 message and send the message to the BR. Since the complete BMR, i.e. the first BMR, is retained in BR, as shown in fig. 5. Therefore, the BR can obtain the public network IPv4 prefix or address of the CE according to the first BMR and the source IPv6 address of the IPv6 packet from the CE. If the BR obtains the public network IPv4 prefix of the CE, the BR may fixedly select an address in the network segment indicated by the public network IPv4 prefix according to a preset rule, for example, an available first address of the network segment, as the public network IPv4 address of the CE. Then, the BR can update the source IPv4 address carried by the IPv6 message by using the obtained public network IPv4 address of the CE; then, the BR may match, by using the first BMR, the routing information corresponding to the destination IPv4 address carried in the IPv6 packet, and forward the content of the IPv4 packet according to the routing information. For example: if the destination IPv4 address carried by the IPv6 message received by the BR can be matched with the rule IPv4 prefix in the first BMR of a certain MAP domain in the BR, it indicates that the BR will perform backhaul processing on the content of the IPv4 message by using an IPv6 message in a certain MAP domain to which the BR belongs by the destination device, that is, the content of the IPv4 message is sent to another CE through the BR; if the target IPv4 address carried by the IPv6 message received by the BR cannot be matched with the rule IPv4 prefix in the first BMR of any MAP domain in the BR, the BR forwards the content of the IPv4 message carried by the IPv6 message to an IPv4 public network.

Optionally, in an optional implementation manner of this embodiment, in a scenario where different first routing devices share a public network IPv4 address, before 102, the first routing device receives a BMR (i.e., a second BMR) and a DMR that are issued by a DHCPv6 server and are not completely correct, that is, the server does not issue the BMR (i.e., the first BMR) that is completely correct, so that the first routing device cannot obtain the public network IPv4 address of the first routing device according to the second BMR. Optionally, the second BMR may further include a specific regular IPv4 prefix (e.g., 10.10.10.10/{ length of regular IPv4 prefix }, or all 0 or all 1, etc.) and a second EA bit length, where the second EA bit length is used to indicate a sum of a length of an IPv4 suffix and a PSID in the IPv6 prefix allocated to the first routing device, and the IPv4 suffix is a remaining portion of the IPv4 address of the first routing device after removing a corresponding length of the regular IPv4 prefix. The DMR is configured to access a second routing device, where the DMR includes an IPv6 address of the second routing device or an IPv6 prefix thereof. That is, before 102, the first routing device cannot match the routing information corresponding to the destination IPv4 address by using the second BMR. Correspondingly, in 102, since the first routing device cannot match the routing information corresponding to the destination IPv4 address by using an incomplete correct BMR (i.e., a second BMR), the first routing device may use a DMR to encapsulate or translate the IPv4 packet into an IPv6 packet and send the IPv6 packet to the second routing device. In addition, since the first routing device cannot obtain the public network IPv4 address of the first routing device by using an incompletely correct BMR (i.e., a second BMR), the source IPv4 address carried by the IPv6 message sent by the first routing device may be an IPv4 address using the prefix of the specific regular IPv 4.

Take the first routing device as the CE located at the boundary of the user network and the second routing device as the BR located between the IPv6 network and the IPv4 network as an example. The DHCPv6 server issues a DMR for accessing the BR and a BMR that is not completely correct, i.e. a second BMR, in the parameters issued to the CE, as shown in fig. 6, where the second BMR may further include a specific regular IPv4 prefix and a second EA bit length, and the second EA bit length is used to indicate the sum of the lengths of the PSID and the IPv4 suffix in the IPv6 prefix allocated to the CE. And the CE utilizes the DMR to package or translate the received IPv4 message into an IPv6 message and send the message to the BR. Since the completely correct BMR, i.e. the first BMR, is retained in the BR, as shown in fig. 4. Therefore, the BR can obtain the public network IPv4 address of the CE according to the first BMR and the source IPv6 address of the IPv6 message from the CE, and the public network IPv4 address updates the source IPv4 address carried by the IPv6 message; then, the BR may match, by using the first BMR, the routing information corresponding to the destination IPv4 address carried in the IPv6 packet, and forward the content of the IPv4 packet according to the routing information. If the destination IPv4 address carried by the IPv6 message received by the BR can be matched with the rule IPv4 prefix in the first BMR of a certain MAP domain in the BR, it indicates that the BR will perform backhaul processing on the content of the IPv4 message by using an IPv6 message in a certain MAP domain to which the BR belongs by the destination device, that is, the content of the IPv4 message is sent to another CE through the BR; if the target IPv4 address carried by the IPv6 message received by the BR cannot be matched with the rule IPv4 prefix in the first BMR of any MAP domain in the BR, the BR forwards the content of the IPv4 message carried by the IPv6 message to an IPv4 public network.

Optionally, in an optional implementation manner of this embodiment, in a scenario that different first routing devices do not share a public network IPv4 address, before 102, the first routing device receives a BMR (i.e., a second BMR) and a DMR that are delivered by a DHCPv6 server and are not completely correct, that is, the server does not deliver the completely correct BMR (i.e., the first BMR), so that the first routing device cannot obtain a public network IPv4 prefix or address of the first routing device according to the second BMR. Optionally, the second BMR may further include a specific regular IPv4 prefix (e.g., 10.10.10.10/{ length of the regular IPv4 prefix, or all 0 or all 1, etc.) and a third EA bit length, where the third EA bit length is used to indicate the length of the IPv4 suffix in the IPv6 prefix allocated to the first routing device, and the IPv4 suffix is the remaining part of the IPv4 prefix or the address of the first routing device after removing the corresponding length of the regular IPv4 prefix. The DMR is configured to access a second routing device, where the DMR includes an IPv6 address of the second routing device or an IPv6 prefix thereof. That is, before 102, the first routing device cannot match the routing information corresponding to the destination IPv4 address by using the second BMR. Correspondingly, in 102, since the first routing device cannot use an incomplete correct BMR (i.e., the second BMR), match the routing information corresponding to the destination IPv4 address, the first routing device uses the DMR to encapsulate or translate the IPv4 packet into an IPv6 packet, and send the IPv6 packet to the second routing device. In addition, since the first routing device cannot obtain the public network IPv4 prefix or address of the first routing device by using an incomplete BMR (i.e., a second BMR), the source IPv4 address carried in the IPv6 message sent by the first routing device may be an IPv4 address using the specific regular IPv4 prefix.

Take the first routing device as the CE located at the boundary of the user network and the second routing device as the BR located between the IPv6 network and the IPv4 network as an example. The DHCPv6 server issues a DMR for accessing the BR and a BMR that is not completely correct, i.e. a second BMR, in the parameters issued to the CE, as shown in fig. 7, where the second BMR may further include a specific regular IPv4 prefix and a third EA bit length, and the third EA bit length is used to indicate the length of the IPv4 suffix in the IPv6 prefix allocated to the CE. And the CE utilizes the DMR to package or translate the received IPv4 message into an IPv6 message and send the message to the BR. Since the completely correct BMR, i.e. the first BMR, is retained in the BR, as shown in fig. 5. Therefore, the BR can obtain the public network IPv4 address of the CE according to the first BMR and the source IPv6 address of the IPv6 packet from the CE. Then, the BR can update the source IPv4 address carried by the IPv6 message by using the obtained public network IPv4 address of the CE; then, the BR may match, by using the first BMR, the routing information corresponding to the destination IPv4 address carried in the IPv6 packet, and forward the content of the IPv4 packet according to the routing information. If the destination IPv4 address carried by the IPv6 message received by the BR can be matched with the rule IPv4 prefix in the first BMR of a certain MAP domain in the BR, it indicates that the BR will perform backhaul processing on the content of the IPv4 message by using an IPv6 message in a certain MAP domain to which the BR belongs by the destination device, that is, the content of the IPv4 message is sent to another CE through the BR; if the target IPv4 address carried by the IPv6 message received by the BR cannot be matched with the rule IPv4 prefix in the first BMR of any MAP domain in the BR, the BR forwards the content of the IPv4 message carried by the IPv6 message to an IPv4 public network.

Fig. 8 is a schematic flowchart of a message processing method according to another embodiment of the present application, as shown in fig. 8.

801. The second routing equipment receives an IPv6 message sent by the first routing equipment, the IPv6 message is obtained by packaging or translating the IPv4 message by using an IPv6 address or prefix of the second routing equipment after the first routing equipment receives the IPv4 message, and the IPv4 message contains a target IPv4 address.

802. And the second routing equipment updates the source IPv4 address carried by the IPv6 message according to the first BMR and the source IPv6 address of the IPv6 message, and matches routing information corresponding to the target IPv4 address by using the first BMR.

803. And the second routing equipment forwards the content of the IPv4 message according to the routing information.

Optionally, in an optional implementation manner of this embodiment, in a scenario where different first routing devices share a public network IPv4 address, before 801, the first routing device receives the PSID of the first routing device and the IPv6 address or prefix of the second routing device, which are issued by the DHCPv6 server, and does not issue the BMR, so that the first routing device cannot obtain the public network IPv4 prefix or address of the first routing device according to the BMR. Correspondingly, in 102, since the first routing device cannot use the BMR to match the routing information corresponding to the destination IPv4 address, the first routing device may use the IPv6 address or prefix of the second routing device to encapsulate or translate the IPv4 packet into an IPv6 packet, and send the IPv6 packet to the second routing device. In addition, since the first routing device cannot obtain the public network IPv4 address, the source IPv4 address carried by the IPv6 packet sent by the first routing device may be a specific IPv4 address, for example: 192.0.0.2 for identification B4, either all 0's or all 1's, etc., in the specific unicast IPv4 address registered by the IANA application, or similar DS-lite technology.

Take the first routing device as the CE located at the boundary of the user network and the second routing device as the BR located between the IPv6 network and the IPv4 network as an example. The DHCPv6 server issues a DMR for accessing a BR and a PSID of a CE in parameters issued to the CE. The DMR comprises the IPv6 address or prefix of the BR. And the CE utilizes the DMR to package or translate the received IPv4 message into an IPv6 message and send the message to the BR. Since the complete BMR, i.e. the first BMR, is retained in BR, as shown in fig. 4. Therefore, the BR can obtain the public network IPv4 address of the CE according to the first BMR and the source IPv6 address of the IPv6 message from the CE, and update the source IPv4 address carried by the IPv6 message by using the public network IPv4 address; then, the BR may match routing information corresponding to the destination IPv4 address by using the first BMR, and forward the content of the IPv4 packet according to the routing information. For example: if the destination IPv4 address carried in the IPv6 message received by the BR can be matched with the rule IPv4 prefix in the first BMR of a certain MAP domain in the BR, it indicates that the BR will perform backhaul processing on the content of the IPv4 message by using an IPv6 message in a certain MAP domain where the destination device is located, that is, the content of the IPv4 message is sent to another CE through the BR; if the target IPv4 address carried by the IPv6 message received by the BR cannot be matched with the rule IPv4 prefix in the first BMR of any MAP domain in the BR, the BR forwards the content of the IPv4 message carried by the IPv6 message to an IPv4 public network.

Optionally, in an optional implementation manner of this embodiment, in a scenario where different first routing devices share a public network IPv4 address, before 801, the first routing device receives an incomplete BMR (that is, a second BMR) and a DMR that are issued by a DHCPv6 server, that is, the server does not issue a complete BMR (that is, a first BMR), so that the first routing device cannot obtain the public network IPv4 address of the first routing device according to the second BMR. Optionally, the second BMR may further include a first EA (Embedded Address) bit length (EA bits), where the first EA bit length is used to indicate a length of a PSID in an IPv6 prefix allocated to the first routing device. The DMR is configured to access a second routing device, where the DMR includes an IPv6 address of the second routing device or an IPv6 prefix thereof. That is, before 801, the first routing device cannot match the routing information corresponding to the destination IPv4 address by using the second BMR. Correspondingly, because the first routing device cannot utilize an incomplete BMR (i.e., a second BMR) to match the routing information corresponding to the destination IPv4 address, the first routing device will utilize a DMR to encapsulate or translate the IPv4 packet into an IPv6 packet and send the IPv6 packet to the second routing device. In addition, since the first routing device cannot obtain the public network IPv4 address of the first routing device, the source IPv4 address carried by the IPv6 packet sent by the first routing device may be a specific IPv4 address, for example: 192.0.0.2 for identification B4, either all 0's or all 1's, etc., in the specific unicast IPv4 address registered by the IANA application, or similar DS-lite technology.

Wherein the IPv6 prefix of the first routing device is assigned to the first routing device by an operator, such as: the DHCPv6 server delegates the IPv6 Prefix to the first routing device by means of a Prefix Delegation (DHCPv6 Prefix deletion, DHCPv6-PD) in DHCPv6, or the Stateless Address Auto-Configuration (SLAAC) server assigns the IPv6 Prefix to the first routing device by means of SLAAC.

Optionally, in an optional implementation manner of this embodiment, in a scenario that different first routing devices do not share a public network IPv4 address, before 801, the first routing device may further receive the DMR only issued by the DHCPv6 server, that is, the server only issues the DMR, and does not issue the BMR, so that the first routing device cannot obtain a public network IPv4 prefix or address of the first routing device according to the BMR. The DMR is configured to access a second routing device, where the DMR includes an IPv6 address of the second routing device or an IPv6 prefix thereof. Correspondingly, because the first routing device cannot use the BMR to match the routing information corresponding to the destination IPv4 address, the first routing device may use the DMR to encapsulate or translate the IPv4 packet into an IPv6 packet, and send the IPv6 packet to the second routing device. In addition, since the first routing device cannot obtain the public network IPv4 address, the source IPv4 address carried by the IPv6 packet sent by the first routing device may be a specific IPv4 address, for example: 192.0.0.2 for identification B4, either all 0's or all 1's, etc., in the specific unicast IPv4 address registered by the IANA application, or similar DS-lite technology.

Optionally, in an optional implementation manner of this embodiment, in a scenario where different first routing devices share a public network IPv4 address, before 801, the first routing device receives a BMR (i.e., a second BMR) and a DMR that are issued by a DHCPv6 server and are not completely correct, that is, the server does not issue the BMR (i.e., the first BMR) that is completely correct, so that the first routing device cannot obtain the public network IPv4 address of the first routing device according to the second BMR. Optionally, the second BMR may further include a specific regular IPv4 prefix (e.g., 10.10.10.10/{ length of regular IPv4 prefix }, or all 0 or all 1, etc.) and a second EA bit length, where the second EA bit length is used to indicate a sum of a length of an IPv4 suffix and a PSID in the IPv6 prefix allocated to the first routing device, and the IPv4 suffix is a remaining portion of the IPv4 address of the first routing device after removing a corresponding length of the regular IPv4 prefix. The DMR is configured to access a second routing device, where the DMR includes an IPv6 address of the second routing device or an IPv6 prefix thereof. That is, before 801, the first routing device cannot match the routing information corresponding to the destination IPv4 address by using the second BMR. Correspondingly, because the first routing device cannot match the routing information corresponding to the destination IPv4 address by using an incompletely correct BMR (i.e., a second BMR), the first routing device may use a DMR to encapsulate or translate the IPv4 packet into an IPv6 packet and send the IPv6 packet to the second routing device. In addition, since the first routing device cannot obtain the public network IPv4 address of the first routing device by using an incomplete BMR (i.e., a second BMR), the source IPv4 address carried by the IPv6 packet sent by the first routing device may be an IPv4 address using the prefix of the specific regular IPv 4.

Optionally, in an optional implementation manner of this embodiment, in a scenario that different first routing devices do not share a public network IPv4 address, before 801, the first routing device receives a BMR (i.e., a second BMR) and a DMR that are sent by a DHCPv6 server and are not completely correct, that is, the server does not send the BMR (i.e., the first BMR) that is completely correct, so that the first routing device cannot obtain a public network IPv4 prefix or address of the first routing device according to the second BMR. Optionally, the second BMR may further include a specific regular IPv4 prefix (e.g., 10.10.10.10/{ length of the regular IPv4 prefix, or all 0 or all 1, etc.) and a third EA bit length, where the third EA bit length is used to indicate the length of the IPv4 suffix in the IPv6 prefix allocated to the first routing device, and the IPv4 suffix is the remaining part of the IPv4 prefix or the address of the first routing device after removing the corresponding length of the regular IPv4 prefix. The DMR is configured to access a second routing device, where the DMR includes an IPv6 address of the second routing device or an IPv6 prefix thereof. That is, before 801, the first routing device cannot match the routing information corresponding to the destination IPv4 address by using the second BMR. Correspondingly, the first routing device cannot match the routing information corresponding to the destination IPv4 address by using an incomplete correct BMR (i.e., a second BMR), and the first routing device encapsulates or translates the IPv4 packet into an IPv6 packet by using a DMR and sends the IPv6 packet to the second routing device. In addition, since the first routing device cannot obtain the public network IPv4 prefix or address of the first routing device by using an incompletely correct BMR (i.e., a second BMR), the source IPv4 address carried by the IPv6 message sent by the first routing device may be an IPv4 address using the specific regular IPv4 prefix.

It should be noted that: while, for purposes of simplicity of explanation, the foregoing method embodiments have been described as a series of acts or combination of acts, it will be appreciated by those skilled in the art that the present application is not limited by the order of acts or acts described, as some steps may occur in other orders or concurrently with other steps in accordance with the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.

In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

Fig. 9 is a schematic structural diagram of a routing device according to another embodiment of the present application, and as shown in fig. 9, the routing device according to this embodiment may include a first receiver 91, a processor 92, and a transmitter 93. The first receiver 91 is configured to receive an IPv4 message, where the IPv4 message includes a destination IPv4 address; the processor 92 is configured to encapsulate or translate the IPv4 packet into an IPv6 packet by using an IPv6 address or prefix of the second routing device; the sender 93 is configured to send the IPv6 packet to the second routing device, so that the second routing device updates the source IPv4 address carried in the IPv6 packet according to the first BMR and the source IPv6 address of the IPv6 packet, matches, by using the first BMR, routing information corresponding to the destination IPv4 address, and forwards the content of the IPv4 packet according to the routing information.

It will be appreciated that the first receiver 91 is located at a user side Local Area Network (LAN) interface of the routing device.

Optionally, in an optional implementation manner of this embodiment, in a scenario where different first routing devices do not share a public network IPv4 address, as shown in fig. 10, the routing device provided in this embodiment may further include a second receiver 1001, configured to receive the DMR only issued by the DHCPv6 server. It is understood that the second receiver 1001 is located at a user side Wide Area Network (WAN) interface of the routing device. For a detailed description, reference may be made to relevant contents in the embodiment corresponding to fig. 1, and details are not described here.

Optionally, in an optional implementation manner of this embodiment, as shown in fig. 11, the routing device provided in this embodiment may further include a third receiver 1101, and further include a third receiver, configured to receive the PSID of the first routing device and the IPv6 address or prefix of the second routing device, which are sent by the DHCPv6 server. For a detailed description, reference may be made to relevant contents in the embodiment corresponding to fig. 1, and details are not described here.

Optionally, in an optional implementation manner of this embodiment, as shown in fig. 12, the routing device provided in this embodiment may further include a fourth receiver 1201, configured to receive the second BMR and the DMR sent by the DHCPv6 server; the processor cannot match out the routing information corresponding to the destination IPv4 address by using the second BMR. It will be appreciated that the fourth receiver 1201 is located at the user side WAN interface of the routing device. For a detailed description, reference may be made to relevant contents in the embodiment corresponding to fig. 1, and details are not described here.

For example: in a scenario where different first routing devices share a public network IPv4 address, the second BMR received by the fourth receiver 1201 may include a first EA bit length indicating the length of the PSID in the IPv6 prefix assigned to the routing device. For a detailed description, reference may be made to relevant contents in the embodiment corresponding to fig. 1, and details are not described here.

For another example: in a scenario where different first routing devices share a public network IPv4 address, the second BMR received by the fourth receiver 1201 may include a specific regular IPv4 prefix and a second EA bit length, where the second EA bit length is used to indicate a sum of a length of a PSID and an IPv4 suffix in an IPv6 prefix assigned to the routing device, and the IPv4 suffix is a remaining part of the IPv4 address of the routing device after removing a corresponding length of the regular IPv4 prefix. For a detailed description, reference may be made to relevant contents in the embodiment corresponding to fig. 1, and details are not described here.

For another example: in a scenario where different first routing devices do not share a public network IPv4 address, the second BMR received by the fourth receiver 1201 may include a specific regular IPv4 prefix and a third EA bit length, where the third EA bit length is used to indicate a length of an IPv4 suffix in an IPv6 prefix assigned to the routing device, and the IPv4 suffix is the IPv4 address of the routing device or a remaining part of the prefix excluding a corresponding length of the regular IPv4 prefix. For a detailed description, reference may be made to relevant contents in the embodiment corresponding to fig. 1, and details are not described here.

In this embodiment, the terminal communicates with the destination device through the IPv6 network via the routing device and through the second routing device, and all IPv4 messages initiated by the terminal need to be sent to the destination device through the routing device and the second routing device, so that a star communication mode is implemented in an application scenario of the MAP technology, and the management capability of the second routing device, that is, the network side device, on user communication traffic can be improved.

Fig. 13 is a schematic structural diagram of a routing device according to another embodiment of the present application, and as shown in fig. 13, the routing device according to this embodiment may include a receiver 1301, a processor 1302, and a transmitter 1303. The receiver 1301 is configured to receive an IPv6 message sent by a first routing device, where the IPv6 message is obtained by encapsulating or translating the IPv4 message by using an IPv6 address or prefix of the routing device after the first routing device receives the IPv4 message, and the IPv4 message includes a destination IPv4 address; the processor 1302 is configured to update a source IPv4 address carried in the IPv6 packet according to the first BMR and the source IPv6 address of the IPv6 packet, and match, by using the first BMR, routing information corresponding to the destination IPv4 address; the sender 1303 is configured to forward the content of the IPv4 packet according to the routing information. For a detailed description, reference may be made to relevant contents in the embodiment corresponding to fig. 8, which are not described herein again.

In this embodiment, the terminal communicates with the destination device through the first routing device via the IPv6 network and through the routing device, and all IPv4 messages initiated by the terminal need to be sent to the destination device through the first routing device and the routing device, so that a star communication mode is implemented in an application scenario of an MAP technology, and the management capability of the routing device, that is, the network side device, on user communication traffic can be improved.

An embodiment of the present application further provides a packet processing system, including the routing device provided in any embodiment corresponding to fig. 9 to 12 and the routing device provided in the embodiment corresponding to fig. 13.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims

1. A message processing method is characterized by comprising the following steps:

a first routing device receives an internet protocol version 4IPv4 message, wherein the IPv4 message contains a destination IPv4 address;

the first routing equipment encapsulates or translates the IPv4 message into an IPv6 message by using an Internet protocol version 6IPv6 address or prefix of the second routing equipment and sends the IPv6 message to the second routing equipment, so that the second routing equipment updates a source IPv4 address carried by the IPv6 message according to a first basic mapping rule BMR and a source IPv6 address of the IPv6 message, matches routing information corresponding to the target IPv4 address by using the first BMR, and forwards the content of the IPv4 message according to the routing information;

before the first routing device encapsulates or translates the IPv4 message into an IPv6 message and sends the IPv6 message to the second routing device by using the internet protocol version 6IPv6 address or prefix of the second routing device, the first routing device does not receive the BMR that is issued by the DHCPv6 server and can be used for matching the BMR of the routing information corresponding to the destination IPv4 address, and the first routing device receives the default mapping rule DMR that is issued by the DHCPv6 server.

2. The method of claim 1, wherein the first routing device encapsulates or translates the IPv4 packet into an IPv6 packet using an internet protocol version 6IPv6 address or prefix of the second routing device, and sending the IPv4 packet to the second routing device, the method comprising:

and the first routing equipment encapsulates or translates the IPv4 message into an IPv6 message by using the DMR and sends the IPv6 message to the second routing equipment.

3. The method as claimed in claim 1, wherein before the first routing device encapsulates or translates the IPv4 packet into an IPv6 packet using an internet protocol version 6IPv6 address or prefix of the second routing device, the method further comprises:

the first routing device receives a port set identifier PSID of the first routing device sent by the DHCPv6 server.

4. A message processing method is characterized by comprising the following steps:

the second routing equipment receives an internet protocol version 6IPv6 message sent by the first routing equipment, wherein the IPv6 message is obtained by packaging or translating the IPv4 message by using an IPv6 address or prefix of the second routing equipment after the first routing equipment receives an internet protocol version 4IPv4 message, and the IPv4 message contains a target IPv4 address; before the first routing device encapsulates or translates the IPv4 message into an IPv6 message and sends the IPv6 message to the second routing device by using the IPv6 address or prefix of the second routing device, the first routing device does not receive a basic mapping rule BMR that is issued by a dynamic host configuration protocol DHCPv6 server and can be used for matching routing information corresponding to the destination IPv4 address, and the first routing device receives a default mapping rule DMR that is issued by the DHCPv6 server;

the second routing equipment updates the source IPv4 address carried by the IPv6 message according to a first basic mapping rule BMR and the source IPv6 address of the IPv6 message, and matches routing information corresponding to the target IPv4 address by utilizing the first BMR;

5. The method of claim 4, wherein the first routing device encapsulates or translates the IPv4 packet into an IPv6 packet to be sent to the second routing device using the IPv6 address or prefix of the second routing device, and wherein the method comprises:

6. The method as claimed in claim 4, wherein before the first routing device encapsulates or translates the IPv4 packet into an IPv6 packet by using the IPv6 address or prefix of the second routing device, the method further comprises:

7. A routing device, the routing device being a first routing device, the first routing device comprising:

a first receiver, configured to receive an internet protocol version 4IPv4 message, where the IPv4 message includes a destination IPv4 address;

the processor is used for packaging or translating the IPv4 message into an IPv6 message by utilizing an Internet protocol version 6IPv6 address or prefix of the second routing equipment;

a sender, configured to send the IPv6 packet to the second routing device, so that the second routing device updates a source IPv4 address carried in the IPv6 packet according to a first basic mapping rule BMR and a source IPv6 address of the IPv6 packet, matches, by using the first BMR, routing information corresponding to the destination IPv4 address, and forwards content of the IPv4 packet according to the routing information;

before the processor encapsulates or translates the IPv4 message into an IPv6 message by using an internet protocol version 6IPv6 address or prefix of the second routing device, the first receiver does not receive a BMR issued by a dynamic host configuration protocol DHCPv6 server and can be used for matching out routing information corresponding to the destination IPv4 address, and the first routing device receives a default mapping rule DMR issued by the DHCPv6 server.

8. The routing device of claim 7, wherein the processor is further configured to encapsulate or translate the IPv4 message into an IPv6 message for sending to the second routing device using the DMR.

9. The routing device according to claim 7, wherein the first routing device further comprises a third receiver, configured to receive a port set identifier PSID of the first routing device sent by the DHCPv6 server.

10. A routing device, the routing device being a second routing device, the second routing device comprising:

a receiver, configured to receive an internet protocol version 6IPv6 message sent by a first routing device, after the IPv6 message is received by the first routing device as an internet protocol version 4IPv4 message, encapsulating or translating the IPv4 packet with or into an IPv6 address of the second routing device or an IPv6 prefix of the second routing device, the IPv4 message includes a destination IPv4 address, and before the first routing device encapsulates or translates the IPv4 message into an IPv6 message and sends the IPv6 message to the second routing device by using the IPv6 address or prefix of the second routing device, the first routing equipment does not receive the basic mapping rule BMR which is issued by the dynamic host configuration protocol DHCPv6 server and can be used for matching the routing information corresponding to the destination IPv4 address, the first routing device receives a default mapping rule DMR issued by the DHCPv6 server;

the processor is used for updating the source IPv4 address carried by the IPv6 message according to a first basic mapping rule BMR and the source IPv6 address of the IPv6 message, and matching routing information corresponding to the target IPv4 address by using the first BMR;

11. The routing device of claim 10, wherein the first routing device encapsulates or translates the IPv4 packet into an IPv6 packet using an IPv6 address or prefix of the second routing device, and sends the IPv6 packet to the second routing device, the method comprising:

12. The routing device of claim 10, wherein before the first routing device encapsulates or translates the IPv4 packet into an IPv6 packet by using the IPv6 address or prefix of the second routing device, the method further comprises:

13. A message processing system comprising a routing device according to any of claims 7-9 and a routing device according to any of claims 10-12.