IPv6 single stack evolution method, apparatus and device

Abstract

The application relates to an IPv6 single-stack evolution method, wherein an exit-layer IPv4 / IPv6 translation device is arranged at the exit of a core network, an access-layer IPv4 / IPv6 translation device is arranged at the entrance of the core network, and the core network only has IPv6 flow; the method comprises the following steps: the access-layer IPv4 / IPv6 translation device receives a transmission message sent by a terminal device, and transmits IPv6 flow to the core network; the transmission message is analyzed to determine whether IPv4 Internet or IPv6 Internet is accessed; when the terminal accesses IPv4 Internet, the terminal accesses IPv4 Internet after being translated by the exit-layer IPv4 / IPv6 translation device; and when the terminal accesses IPv6 Internet, the terminal directly accesses IPv6 Internet through the core network. The application can expand the core device according to the scale of the terminal and flow, can access various types of user terminals, can monitor IPv6 flow and terminals in real time to improve exit IPv6 flow, does not need to modify any configuration of the existing network, and does not need to make any prior configuration of the access-layer translation device.

Description

Technical Field

[0001] This application relates to the field of computer network technology, and in particular to a method, apparatus and device for IPv6 single-stack evolution. Background Technology

[0002] The evolution of the Internet towards IPv6 single-stack is an internationally recognized trend. However, due to the incompatibility between the IPv6 protocol and IPv4, IPv4 / IPv6 translation technology is needed to enable IPv6 single-stack networks to communicate with the IPv4 Internet. In scenarios involving large-scale IPv6 single-stack network deployments, the following requirements need to be met:

[0003] 1) Scalability: It can be operated on a large scale, and the core equipment can be expanded according to the scale of terminals and traffic.

[0004] 2) Terminal compatibility: It should be able to access various types of user terminals and be compatible with various operating systems and applications.

[0005] 3) Manageability: IPv6 traffic and terminals can be monitored in real time, and IPv4 traffic and IPv6 traffic can be scheduled based on the current situation and policies (IPv4 traffic can be scheduled as IPv6 traffic or IPv6 traffic can be scheduled as IPv4 traffic on demand). While ensuring user experience, IPv6 traffic can be increased as much as possible to promote the transition to IPv6.

[0006] To address the aforementioned issues, RFC 6146 defines one stateful translation method for IPv6 clients accessing IPv4 servers. However, this method has the following problems:

[0007] 1) The statefulness of core devices prevents the solution from scaling to a large scale. NAT64 as defined in RFC6146 requires saving and tracking the connection state of each connection, which consumes a lot of computing and storage resources. When multiple devices are stacked and deployed, a large amount of horizontal traffic is also required for state synchronization, making it difficult to run stably with a large number of users.

[0008] 2) Inability to connect to all types of user terminals. While some operating systems support access to IPv6 single-stack networks, allowing applications with embedded IPv4 addresses to still run through underlying translation capabilities (RFC6877), such as Android, iOS, and macOS, others (e.g., Windows) lack this capability. When these operating systems connect to an IPv6 single-stack network, applications with embedded IPv4 addresses will experience functionalities. Furthermore, some IoT terminals, dumb terminals (such as printers), or older operating systems (such as Windows XP in its default configuration) only support IPv4 and cannot connect to an IPv6 single-stack environment.

[0009] 3) Although the user network uses a single IPv6 stack, when accessing internet resources, IPv6 traffic from the user terminal is either translated into IPv4 traffic to access IPv4 resources, or it accesses IPv6 resources without translation. DNS64 (RFC6147) is usually used in conjunction with RFC6146, but DNS64 does not have a clear mechanism to perform policy-based scheduling of the ratio of IPv4 traffic to IPv6 traffic to effectively improve IPv6 traffic.

[0010] Other technologies can solve some of the problems mentioned above, but no technology can meet all the requirements. Examples are listed below:

[0011] 1) Stateless translation technologies can solve the scalability problem of core devices, including SIIT (Stateless IP / ICMP Translation) (RFC7915, replacing the original versions RFC2765 and RFC6145) and MAP-T (RFC7599). SIIT technology has specific requirements for the address format of the user end, needing to conform to the address format of RFC6052, and cannot be used alone in scenarios using SLAAC to automatically allocate IPv6 addresses. MAP-T technology, on the other hand, involves installing a MAP-CPE at the user end, working in conjunction with the core stateless MAP-BR, but its application is limited: it can only be used in home broadband scenarios and is difficult to apply to enterprise / campus networks. Furthermore, both SIIT and MAP-T technologies use common DNS technology, which cannot perform policy-based scheduling of IPv4 and IPv6 traffic to improve IPv6 traffic performance.

[0012] 2) RFC 8925 defines a method for ensuring compatibility with IPv6-only terminals in a single-stack IPv6 network: An IPv6-only preferred option is issued via DHCPv4. IPv6-only terminals, upon seeing this option, will not obtain an IPv4 address from the DHCPv4 provider. Other terminals that do not support IPv6, or IPv4 terminals that do not recognize this option, will obtain an IPv4 address via DHCPv4. This method allows access for various types of user terminals. However, it does not address other requirements, including scalability and policy-based IPv4 / IPv6 traffic scheduling to improve IPv6 traffic flow.

[0013] In summary, the existing technologies each have the following problems:

[0014] RFC6146-NAT64: The stateful nature of the core leads to poor scalability; it cannot access various types of user terminals; it cannot perform policy-based IPv4 / IPv6 traffic scheduling, thus failing to effectively improve IPv6 traffic performance.

[0015] RFC7915-SIIT: This has specific requirements for the address format of the user terminal, requiring it to conform to the address format of RFC6052. It cannot be used alone in scenarios where SLAAC automatically assigns IPv6 addresses (use cases are limited).

[0016] RFC7599-MAP-T: Limited application scenarios: It can only be used in home broadband scenarios and is difficult to apply to enterprise / campus network scenarios.

[0017] RFC8925: A single technology that can address the needs of accessing various user terminals; other requirements are not covered. Summary of the Invention

[0018] This application provides a method for IPv6 single-stack evolution, characterized in that an egress layer IPv4 / IPv6 translation device is deployed at the core network egress, an access layer IPv4 / IPv6 translation device is deployed at the core network ingress, and the core network only has IPv6 traffic;

[0019] The method includes:

[0020] The access layer IPv4 / IPv6 translation device receives transmission packets sent by terminal devices and transmits IPv6 traffic to the core network;

[0021] The transmitted message is analyzed to determine whether it is accessing the IPv4 Internet or the IPv6 Internet;

[0022] When the terminal is accessing the IPv4 Internet, it accesses the IPv4 Internet after being translated by the exit layer IPv4 / IPv6 translation device.

[0023] When the terminal is accessing the IPv6 Internet, it accesses the IPv6 Internet directly through the core network.

[0024] Optionally, the access layer IPv4 / IPv6 translation device receives transmission packets sent by the terminal device and transmits IPv6 traffic to the core network, including:

[0025] The transmission messages sent by the terminal device are sensed by the access layer IPv4 / IPv6 translation device during transmission, and all the traffic of the transmission messages is translated into IPv6 traffic and sent to the core network.

[0026] Optionally, the IPv6 single-stack evolution method is characterized in that:

[0027] The access layer IPv4 / IPv6 translation device is compatible with all types of terminal devices and has no requirements on the user terminal address format, thus translating accessed resources, whether IPv4 or IPv6, into IPv6 traffic.

[0028] Optionally, the terminal type to be acquired includes:

[0029] The terminal types are divided into three categories: IPv6 single-stack terminal, IPv4 terminal, and IPv4 / IPv6 dual-stack terminal.

[0030] Based on the type of message sent from the IPv4 / IPv6 address received by the terminal device, and by determining whether the IPv6 address is obtained, whether RFC6877 is supported, and whether the IPv6-Only Preferred Option is recognized, the terminal type is obtained.

[0031] If the terminal obtains an IPv6 address and supports RFC6877, then the terminal type is an IPv6 single-stack terminal.

[0032] If the terminal cannot obtain an IPv6 address and does not recognize the IPv6-Only Preferred Option, then the terminal type is an IPv4 terminal.

[0033] If the terminal obtains both IPv6 and IPv4 addresses and does not support RFC6877, then the terminal type is an IPv4 / IPv6 dual-stack terminal.

[0034] Optionally, the transmitted message is analyzed to determine whether it is accessing the IPv4 Internet or the IPv6 Internet, including:

[0035] The terminal device sends transmission messages configured with IPv4 / IPv6 translation rules, which set translation processes based on accessing the IPv4 and IPv6 Internet respectively;

[0036] Traffic accessing the IPv6 Internet is sent directly to the IPv6 Internet exit point;

[0037] Traffic accessing the IPv4 Internet is routed to the egress layer IPv4 / IPv6 translation device, translated into IPv4, and then accessed to the IPv4 Internet.

[0038] Optionally, the step of configuring IPv4 / IPv6 translation rules based on the obtained terminal address, and setting up translation processes for IPv6 single-stack terminals, IPv4 terminals, and IPv4 / IPv6 dual-stack terminals respectively, includes:

[0039] The IPv6 single-stack terminal, IPv4 terminal, and IPv4 / IPv6 dual-stack terminal are configured with different operating modes for the data path components depending on whether they are accessing the IPv6 Internet or the IPv4 Internet.

[0040] The data path consists of, in sequence, an access layer IPv4 / IPv6 translation device, a core network, an egress layer IPv4 / IPv6 translation device, and access to the Internet.

[0041] Optionally, the IPv6 single-stack evolution method is characterized in that:

[0042] The main components of this solution are: an IPv4 / IPv6 translation device at the egress layer, an IPv4 / IPv6 translation device at the access layer, and an IPv6 single-stack development monitoring and management center.

[0043] Deploy export layer IPv4 / IPv6 translation equipment at the exit point, deploy access layer IPv4 / IPv6 translation equipment in the terminal access network in a transparent Layer 2 deployment manner, and deploy IPv6 single-stack development monitoring and management center in the data center or network-accessible location.

[0044] The access layer IPv4 / IPv6 translation device counts the number of detected terminal types and collects time-series data on traffic volume for each scenario, then reports this data to the IPv6 single-stack development monitoring and management center.

[0045] This application also provides an IPv6 single-stack evolution device, characterized in that the device comprises:

[0046] The access layer translation module is used to receive the original transmission packets sent by the terminal, analyze the destination address type of the packet, determine the access target, and output IPv6 traffic to the core network in a unified manner.

[0047] The core network routing module is used for pure IPv6 traffic forwarding, does not handle any IPv4 routing or translation logic, and selects the path based on the IPv6 destination address;

[0048] The export layer translation module is used to receive IPv6 traffic from the core network, convert IPv6 packets back to IPv4 format, and forward them to the IPv4 Internet.

[0049] Optionally, the IPv6 single-stack evolution device is characterized in that:

[0050] The access layer translation module converts IPv4 packets into IPv6 format for IPv4 Internet requests and directly transmits native IPv6 packets for IPv6 Internet requests.

[0051] The core network routing module routes IPv6 traffic accessing the IPv4 Internet to the egress layer translation module, and directly routes IPv6 traffic accessing the IPv6 Internet to the IPv6 Internet.

[0052] The export layer translation module performs IPv6 to IPv4 conversion through a reverse translation engine.

[0053] This application also provides an electronic device, characterized in that it is used to implement any of the described IPv6 single-stack evolution methods, comprising:

[0054] The first gateway device is deployed near the terminal side at the core network entrance. It is used to convert IPv4 packets initiated by the terminal into IPv6 format and directly transmit native IPv6 packets initiated by the terminal.

[0055] The second gateway device is deployed on the side of the core network exit close to the Internet. It is used to translate IPv6 traffic from the core network that accesses the IPv4 Internet into IPv4 traffic, access the IPv4 Internet, and pass through native IPv6 traffic to the IPv6 Internet.

[0056] The beneficial effects of this application are as follows: core equipment can be arbitrarily expanded according to the scale of terminals and traffic without any horizontal connection status synchronization; through the deployment of access layer translation equipment, various types of user terminals can be accessed, and it is compatible with various operating systems and applications; IPv6 traffic and terminals can be monitored in real time, which can maximize the outbound IPv6 traffic and promote the IPv6 transition; the deployment of access layer translation equipment is a Layer 2 deployment, which does not require any modification to the existing network configuration, and the access layer translation equipment does not need to be pre-configured. Translation rules can be automatically configured after going online, simplifying the difficulty of operation and maintenance. Attached Figure Description

[0057] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the accompanying drawings required in the description of the embodiments or the prior art are briefly introduced below. Obviously, the accompanying drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0058] Figure 1 This application discloses a flowchart illustrating an IPv6 single-stack evolution method.

[0059] Figure 2 This diagram illustrates the main connection relationships of an IPv6 single-stack evolution method disclosed in this application.

[0060] Figure 3 This application discloses an IPv6 single-stack terminal data path diagram of an IPv6 single-stack evolution method.

[0061] Figure 4 This application discloses a method for IPv6 single-stack evolution, which includes an IPv4 single-stack terminal data path diagram.

[0062] Figure 5 This paper illustrates the IPv4 / IPv6 dual-stack terminal data path diagram of an IPv6 single-stack evolution method disclosed in this application. Detailed Implementation

[0063] Various exemplary embodiments, features, and aspects of this application will now be described in detail with reference to the accompanying drawings. The same reference numerals in the drawings denote elements that have the same or similar functions. Although various aspects of the embodiments are shown in the drawings, they are not necessarily drawn to scale unless specifically indicated otherwise.

[0064] The terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0065] The term “exemplary” as used herein means “serving as an example, embodiment, or illustration.” Any embodiment illustrated herein as “exemplary” is not necessarily to be construed as superior to or better than other embodiments.

[0066] Furthermore, to better illustrate this application, numerous specific details are provided in the following detailed embodiments. Those skilled in the art should understand that this application can be implemented without certain specific details. In some instances, methods, means, components, and circuits well-known to those skilled in the art have not been described in detail in order to highlight the main points of this application.

[0067] This application presents a method for IPv6 single-stack evolution. In scenarios involving large-scale IPv6 single-stack network applications, this method deploys stateless IPv4 / IPv6 translation devices at the network core. By completely eliminating connection state, it allows for arbitrary expansion of core devices based on terminal and traffic volume. Furthermore, the presence of access layer translation devices enables access to various types of client terminals and compatibility with various operating systems and applications. Through real-time monitoring of IPv6 traffic and terminals, and policy-based scheduling of IPv4 and IPv6 traffic, it maximizes IPv6 traffic while ensuring user experience, thus facilitating the IPv6 transition.

[0068] like Figure 1 The diagram shown is a flowchart of an IPv6 single-stack evolution method according to an embodiment of this application, which specifically includes the following:

[0069] S100, the access layer IPv4 / IPv6 translation device receives the transmission message sent by the terminal device and transmits IPv6 traffic to the core network;

[0070] Specifically, regardless of the type of terminal from which the transmission message originates, and regardless of whether the accessed resource is IPv4 or IPv6, the access layer IPv4 / IPv6 translation device translates it into IPv6 and sends it to the core network.

[0071] S200, Analyze the transmitted message to determine whether it is accessing the IPv4 Internet or the IPv6 Internet;

[0072] Specifically, after the access layer IPv4 / IPv6 translation device and the egress layer IPv4 / IPv6 translation device perceive the terminal address in S100, they automatically configure IPv4 / IPv6 translation rules and use different translation rules according to the different Internet accesses of different terminals.

[0073] S300, when the terminal is accessing the IPv4 Internet, it accesses the IPv4 Internet after being translated by the egress layer IPv4 / IPv6 translation device;

[0074] Specifically, traffic accessing the IPv4 Internet will be routed to the egress layer IPv4 / IPv6 translation device, translated into IPv4, and then accessed to the IPv4 Internet.

[0075] S400, when the terminal is accessing the IPv6 Internet, it directly accesses the IPv6 Internet through the core network.

[0076] Specifically, traffic accessing the IPv6 Internet will be sent directly to the IPv6 Internet exit point.

[0077] In summary, by deploying access layer IPv4 / IPv6 translation devices and egress layer IPv4 / IPv6 translation devices, terminal types can be automatically detected, and IPv6 single-stack addresses can be allocated to terminals whenever possible. This also ensures that terminals that do not support IPv6 single-stack or even IPv6 can obtain addresses normally. Appropriate data access paths are provided for various terminals accessing IPv4 or IPv6 resources, and traffic is converted to IPv6 in the core network, increasing IPv6 traffic per user unit. Policy-based scheduling of IPv4 and IPv6 traffic maximizes egress IPv6 traffic.

[0078] like Figure 2 As shown, the main connection diagram of an IPv6 single-stack evolution method of this application includes the following:

[0079] This solution mainly consists of three parts: access layer IPv4 / IPv6 translation equipment, egress layer IPv4 / IPv6 translation equipment, and IPv6 single-stack development monitoring and management center.

[0080] The aforementioned egress layer IPv4 / IPv6 translation device is a fully stateless IPv4 / IPv6 translation device compliant with RFC 7915. It is deployed at the boundary between the core network egress and the Internet and can be deployed side-by-side or in series. Because it is a fully stateless IPv4 / IPv6 translation device, multiple units can be horizontally expanded arbitrarily without any horizontal connection state synchronization.

[0081] The access layer IPv4 / IPv6 translation device is deployed in the terminal access network in a transparent Layer 2 deployment manner, installed in the existing access network (all components of the existing access network, including gateways, DHCP, authentication, etc., do not require configuration modification). The access layer IPv4 / IPv6 translation device allocates only IPv6 addresses to terminals as much as possible and is compatible with all types of terminal devices; it has no requirements on the address format of the user end and can adapt to various usage scenarios; by integrating intelligent DNS software, it can schedule IPv4 and IPv6 traffic based on policies, maximizing IPv6 traffic while ensuring user experience. Regardless of the terminal type or whether the accessed resource is IPv4 or IPv6, the access layer IPv4 / IPv6 translation device will translate it into IPv6 traffic and send it to the core network. Therefore, only IPv6 traffic is transmitted to the core network, increasing the proportion of IPv6 traffic in the user's core network.

[0082] The IPv6 single-stack development monitoring and management center is deployed in a data center or a network-accessible location. By acquiring IPv6 terminal and IPv6 traffic information from each IPv4 / IPv6 translation device deployed at the egress layer and each IPv4 / IPv6 translation device at the access layer of the user unit, it monitors the development of IPv6 single-stack traffic and terminal ratios across the entire user unit's network, facilitating a smooth transition of the user network to IPv6 single-stack.

[0083] Specifically, during the transmission of packets using both IPv6 and IPv4 addresses, the access layer IPv4 / IPv6 translation device detects the packets and adds the IPv6-Only Preferred Option defined in RFC8925 to the packets transmitted using IPv4 addresses. The method of determining the terminal type and address based on the type of packets received by the terminal is used to determine the terminal type by acquiring the IPv6 address, supporting RFC6877, and recognizing the IPv6-Only Preferred Option.

[0084] The access layer IPv4 / IPv6 translation device detects passing IPv4 address delivery messages (DHCPv4) and IPv6 address delivery messages (SLAAC or DHCPv6). If it's a DHCPv4 reply message, it adds an IPv6-Only Preferred Option as defined in RFC8925 and sends it to the terminal. In this way, if the terminal supports IPv6 single-stack (i.e., the operating system supports RFC6877), it will see the IPv6-Only Preferred Option, abandon IPv4 address configuration, and directly become an IPv6 single-stack terminal. However, if the terminal does not support IPv6 single-stack, it will not recognize the IPv6-Only Preferred Option and will still recognize the DHCPv4 reply and configure the IPv4 address.

[0085] Specifically, for different types of terminals, there are three cases: if the terminal obtains an IPv6 address and supports RFC6877, then the terminal type is an IPv6 single-stack terminal; if the terminal cannot obtain an IPv6 address and does not recognize the IPv6-OnlyPreferred Option, then the terminal type is an IPv4 terminal; if the terminal obtains an IPv6 address but does not support RFC6877, then the terminal type is an IPv4 / IPv6 dual-stack terminal.

[0086] Furthermore, the IPv4 and IPv6 addresses obtained by the aforementioned terminals are the addresses originally assigned by the user organization's DHCP or gateway, and the access layer IPv4 / IPv6 translation device does not modify them in any way. Similarly, the DNS addresses obtained by the aforementioned terminals are also the addresses originally assigned by the user organization's DHCP or gateway, and the access layer IPv4 / IPv6 translation device does not modify them in any way.

[0087] Specifically, the IPv4 / IPv6 translation rules are configured based on the obtained terminal address, and translation processes are set up for IPv6 single-stack terminals, IPv4 terminals, and IPv4 / IPv6 dual-stack terminals respectively. The traffic sent by each type of terminal becomes IPv6 traffic after passing through the access layer. Traffic that accesses the IPv6 Internet is sent directly to the IPv6 Internet egress, while traffic that accesses the IPv4 Internet is routed to the egress layer IPv4 / IPv6 translation device, translated into IPv4, and then accessed to the IPv4 Internet.

[0088] Specifically, for IPv6 single-stack terminals, IPv4 terminals, and IPv4 / IPv6 dual-stack terminals, the operation mode of the data path components for each scenario is set according to whether the access is to the IPv6 Internet or the IPv4 Internet; the data path is, in order, the access layer IPv4 / IPv6 translation device, the core network, the egress layer IPv4 / IPv6 translation device, and the Internet access.

[0089] like Figure 3 The diagram shown is a data path diagram for a single-stack IPv6 terminal, including the following:

[0090] Scenario 1: When an IPv6 single-stack terminal accesses the IPv6 Internet, the access layer IPv4 / IPv6 translation device does not perform any operation and sends the data directly to the IPv6 Internet through the core network. The traffic does not need to pass through the egress layer IPv4 / IPv6 translation device.

[0091] Scenario 2: When an IPv6 single-stack terminal accesses the IPv4 Internet, the access layer IPv4 / IPv6 translation device translates the source address of the IPv6 packet sent by the IPv6 single-stack terminal into an address in RFC6052 format. After the translated IPv6 packet is routed to the egress layer IPv4 / IPv6 translation device, it undergoes completely stateless IPv4 / IPv6 translation and is then converted into an IPv4 packet and sent to the IPv4 Internet.

[0092] The component controlling whether resource domain name access uses the data path from Scenario 1 to Scenario 2 is as follows: The access layer IPv4 / IPv6 translation device integrates an intelligent DNS64 component. This component senses the DNS requests sent by the terminal and queries the global DNS infrastructure for the IPv4 and IPv6 addresses corresponding to the resource domain name to be accessed. If the resource only has an IPv6 address, DNS64 returns the original IPv6 address of the resource and directly uses the data path of Scenario 1, sending access traffic through the IPv6 Internet exit. If the resource only has an IPv4 address, DNS64 returns an IPv6 address synthesized from the resource's IPv4 address according to RFC6147 and directly uses the data path of Scenario 2, sending access traffic through the IPv4 Internet exit. If the resource has both IPv4 and IPv6 addresses (currently the most common type of resource), the intelligent DNS64 component can decide whether to return the original IPv6 address or synthesize an IPv6 address based on the administrator's customized policy, thereby realizing traffic scheduling based on the customized policy at the IPv4 / IPv6 exit.

[0093] Furthermore, since the terminal supports IPv6 single-stack, the operating system has embedded a 464XLAT component compliant with RFC6877. When the application accesses the embedded IPv4 address link, since it is an address link, it will not trigger a DNS lookup operation and will directly send an IPv4 access packet. This IPv4 access request will first be routed to the 464XLAT component by default. The 464XLAT component translates it into an IPv6 packet and sends it out. The rest of the process is exactly the same as in scenario 2.

[0094] like Figure 4 The diagram shown is a data path diagram for a single-stack IPv4 terminal, including the following:

[0095] Scenario 3: When an IPv4 single-stack terminal accesses the IPv6 Internet, the access layer IPv4 / IPv6 translation device translates the accessed IPv4 packets into IPv6 packets and sends them to the IPv6 Internet through the core network. The traffic does not need to pass through the egress layer IPv4 / IPv6 translation device.

[0096] Scenario 4: When an IPv4 single-stack terminal accesses the IPv4 Internet, the access layer IPv4 / IPv6 translation device translates the sent IPv4 packets into IPv6. After the translated IPv6 packets are routed to the egress layer IPv4 / IPv6 translation device, they undergo completely stateless IPv4 / IPv6 translation and are then sent as IPv4 packets to the IPv4 Internet.

[0097] Among them, the component that controls whether the data path goes through scenario 3 or scenario 4: The access layer IPv4 / IPv6 translation device integrates an intelligent DNS46 component (defined by "Traffic Scheduling Method for IPv4 Terminal Access to IPv4 / IPv6 Networks", CN114745353A). This component will sense the DNS requests issued by the terminal and query the global DNS infrastructure on behalf of the terminal for the IPv4 address and IPv6 address corresponding to the resource domain name to be accessed. If the resource only has an IPv4 address, DNS46 returns the original IPv4 address of the resource and directly uses the data path of Scenario 4 to send access traffic through the IPv4 Internet exit. If the resource only has an IPv6 address, DNS46 returns the IPv4 address translated from the IPv6 address of the resource and directly uses the data path of Scenario 3 to send access traffic through the IPv6 Internet exit. If the resource has both IPv4 and IPv6 addresses (currently the most common type of resource), the intelligent DNS46 component can decide whether to return the original IPv4 address or the translated IPv4 address based on the administrator's custom policy, thereby realizing traffic scheduling based on the custom policy at the IPv4 / IPv6 exit.

[0098] Furthermore, for embedded IPv4 address links, IPv4 packets are sent directly without querying DNS, directly following scenario 4.

[0099] like Figure 5 The diagram shown is a data path diagram for an IPv4 / IPv6 dual-stack terminal, including the following:

[0100] Scenario 5: When an IPv4 / IPv6 dual-stack terminal accesses the IPv6 Internet, it sends an IPv6 access packet. The access layer IPv4 / IPv6 translation device does not perform any operation and sends the packet directly to the IPv6 Internet through the core network. The traffic does not need to pass through the egress layer IPv4 / IPv6 translation device.

[0101] Scenario 6: When a dual-stack IPv4 / IPv6 terminal accesses the IPv4 Internet, the access layer IPv4 / IPv6 translation device translates the source address of the IPv6 packet sent by the single-stack IPv6 terminal into an address in RFC6052 format. After the translated IPv6 packet is routed to the egress layer IPv4 / IPv6 translation device, it undergoes a completely stateless IPv4 / IPv6 translation and is then converted into an IPv4 packet before being sent to the IPv4 Internet.

[0102] Among them, the component that controls whether the data path for accessing resource domain names goes through scenario 5 or scenario 6 is the intelligent DNS64 component integrated in the access layer IPv4 / IPv6 translation device. It can decide whether to return the original IPv6 address or synthesize the IPv6 address based on the administrator's customized policy.

[0103] Furthermore, for IPv4 address links embedded in the application, the IPv4 access request is first translated into an IPv6 packet at the access layer IPv4 / IPv6 translation device. After the translated IPv6 packet is routed to the egress layer IPv4 / IPv6 translation device, it undergoes completely stateless IPv4 / IPv6 translation and is then sent as an IPv4 packet to the IPv4 Internet. This process is exactly the same as that in Scenario 4.

[0104] Specifically, the step of statistically analyzing the DNS request domain names of the terminal based on the IPv4 / IPv6 translation device is implemented through the IPv6 transition technology component in the access layer IPv4 / IPv6 translation device; the step of performing access quality measurement is to evaluate the latency, packet loss, and bandwidth parameters of IPv4 and IPv6 Internet egress access.

[0105] The intelligent DNS64 and intelligent DNS46 components in the access layer IPv4 / IPv6 translation equipment perform domain name statistics on DNS requests from terminals and report them to the IPv6 Single-Stack Development Monitoring and Management Center. The IPv6 Single-Stack Development Monitoring and Management Center then aggregates the resource domain names accessed by each access network and conducts regular access quality measurements on these domain names, including parameters such as latency, packet loss, and bandwidth for access via IPv4 and IPv6 internet egress points, and evaluates their access quality.

[0106] Furthermore, based on the measurement results, administrators can formulate strategies to schedule IPv4 and IPv6 traffic, maximizing IPv6 traffic while ensuring a good user experience, thus facilitating the IPv6 transition.

[0107] If the IPv4 access quality of a resource is lower than the IPv6 access quality, then the DNS46 and DNS64 policies are recommended to be configured to access from the IPv6 Internet exit.

[0108] If the IPv4 access quality of a resource is comparable to that of IPv6 access, then the DNS46 and DNS64 policies are recommended to be configured so that requests to access that domain name are made from the IPv6 Internet exit.

[0109] If the IPv4 access quality of a resource is significantly better than the IPv6 access quality, for the sake of user experience, it is recommended that DNS46 and DNS64 policies be configured so that requests to access that domain name are made through the IPv4 Internet exit.

[0110] As mentioned above, administrators can flexibly select IPv4 / IPv6 traffic scheduling strategies based on the actual egress situation. After selecting a scheduling strategy, the strategy can be distributed to the access layer IPv4 / IPv6 translation device on the IPv6 single-stack development monitoring and management center.

[0111] Specifically, access layer IPv4 / IPv6 translation devices statistically analyze the number of detected terminal types (IPv6 single-stack, dual-stack, and IPv4 terminals), and collect time-series data on traffic volume for each of the six scenarios. This data is then reported to the IPv6 Single-Stack Development Monitoring and Management Center. After aggregating the data from all access layer IPv4 / IPv6 translation devices, the IPv6 Single-Stack Development Monitoring and Management Center can calculate the percentage of IPv6 single-stack terminals and traffic across the entire user organization's network. These statistical results can guide user organizations in taking further steps to improve IPv6 traffic and continuously promote the IPv6 transition.

[0112] An IPv6 single-stack evolution device used in the above steps is characterized in that the device comprises:

[0113] The access layer translation module is used to receive the original transmission packets sent by the terminal, analyze the destination address type of the packet, determine the access target, and output IPv6 traffic to the core network in a unified manner.

[0114] The core network routing module is used for pure IPv6 traffic forwarding, does not handle any IPv4 routing or translation logic, and selects the path based on the IPv6 destination address;

[0115] The export layer translation module is used to receive IPv6 traffic from the core network, convert IPv6 packets back to IPv4 format, and forward them to the IPv4 Internet.

[0116] The IPv6 single-stack evolution device is characterized in that:

[0117] The access layer translation module converts IPv4 packets into IPv6 format for IPv4 Internet requests and directly transmits native IPv6 packets for IPv6 Internet requests.

[0118] The core network routing module routes IPv6 traffic accessing the IPv4 Internet to the egress layer translation module, and directly routes IPv6 traffic accessing the IPv6 Internet to the IPv6 Internet.

[0119] The export layer translation module performs IPv6 to IPv4 conversion through a reverse translation engine.

[0120] An electronic device used in the above steps is characterized in that, for implementing any of the described IPv6 single-stack evolution methods, it includes:

[0121] The first gateway device is deployed near the terminal side at the core network entrance. It is used to convert IPv4 packets initiated by the terminal into IPv6 format and directly transmit native IPv6 packets initiated by the terminal.

[0122] The second gateway device is deployed on the side of the core network exit close to the Internet. It is used to translate IPv6 traffic from the core network that accesses the IPv4 Internet into IPv4 traffic, access the IPv4 Internet, and pass through native IPv6 traffic to the IPv6 Internet.

[0123] In summary, this invention provides an IPv6 single-stack evolution method and apparatus, applicable to scenarios of large-scale IPv6 single-stack network applications, and can achieve the following technical effects:

[0124] 1) Scalability: The network core is deployed with a fully stateless IPv4 / IPv6 translation device compliant with RFC7915. Because it does not maintain connection state at all, it consumes very few resources, thus enabling large-scale operation. The core device can be arbitrarily expanded according to the scale of terminals and traffic without any horizontal connection state synchronization.

[0125] 2) Terminal compatibility: Through the deployment of access layer translation equipment, various types of user terminals can be accessed, and it is compatible with various operating systems and applications.

[0126] 3) Manageability: IPv6 traffic and terminals can be monitored in real time, and IPv4 and IPv6 traffic can be scheduled based on the current situation and policies (IPv4 traffic can be scheduled to IPv6 traffic on demand, or IPv6 traffic can be scheduled to IPv4 traffic on demand). While ensuring user experience, it can maximize outbound IPv6 traffic and promote the IPv6 transition.

[0127] 4) The deployment of the access layer translation device is a Layer 2 deployment, which does not require any modification to the existing network configuration. The access layer translation device also does not require any pre-configuration and can automatically configure translation rules after going online, simplifying the operation and maintenance difficulty.

[0128] The various embodiments of this application have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles, practical application, or improvement of the technology in the market, or to enable others skilled in the art to understand the embodiments disclosed herein.

Claims

1. A method for IPv6 single stack evolution, the method comprising: An exit layer IPv4 / IPv6 translation device is deployed at the exit of a core network, an access layer IPv4 / IPv6 translation device is deployed at the entrance of the core network, and the core network only has IPv6 traffic; The method comprises: The access layer IPv4 / IPv6 translation device receives a transmission message sent by a terminal device and transmits IPv6 traffic to the core network; The transmission message is analyzed to determine whether IPv4 Internet or IPv6 Internet is accessed; When the terminal accesses IPv4 Internet, IPv4 Internet is accessed after translation by the exit layer IPv4 / IPv6 translation device; When the terminal accesses IPv6 Internet, IPv6 Internet is directly accessed through the core network; The access layer IPv4 / IPv6 translation device receives a transmission message sent by a terminal device and transmits IPv6 traffic to the core network, comprising: The transmission message sent by the terminal device is perceived by the access layer IPv4 / IPv6 translation device during transmission, and the traffic of the transmission message is all translated into IPv6 traffic and sent to the core network.

2. The IPv6 single stack evolution method of claim 1, wherein: The access layer IPv4 / IPv6 translation device is compatible with all types of terminal devices and has no requirements on user end address formats, and implements translation of IPv4 or IPv6 accessed resources into IPv6 traffic.

3. The IPv6 single stack evolution method of claim 2, wherein, The terminal types include: The terminal types are divided into three cases, namely IPv6 single stack terminal, IPv4 terminal and IPv4 / IPv6 dual stack terminal; According to the IPv4 / IPv6 address message type issued by the terminal device, the terminal type is obtained according to the acquired IPv6 address, support for RFC6877 and recognition of IPv6-Only Preferred Option; If the terminal acquires an IPv6 address and supports RFC6877, the terminal type is an IPv6 single stack terminal; If the terminal cannot acquire an IPv6 address and does not recognize IPv6-Only Preferred Option, the terminal type is an IPv4 terminal; If the terminal acquires an IPv6 address and an IPv4 address and does not support RFC6877, the terminal type is an IPv4 / IPv6 dual stack terminal.

4. The IPv6 single stack evolution method of claim 1, wherein, The transmission message is analyzed to determine whether IPv4 Internet or IPv6 Internet is accessed, comprising: The transmission message sent by the terminal device is configured with an IPv4 / IPv6 translation rule, and the translation rule sets a translation process based on access to IPv4 and IPv6 Internet respectively; Traffic accessing IPv6 Internet is directly sent to an IPv6 Internet exit; Traffic accessing IPv4 Internet is routed to an exit layer IPv4 / IPv6 translation device and accesses IPv4 Internet after translation into IPv4.

5. The IPv6 single stack evolution method of claim 4, wherein, The transmission message sent by the terminal device is configured with IPv4 / IPv6 translation rules, the translation rules set translation processes based on accessing IPv4 and IPv6 Internet respectively, and the translation rules comprise: The IPv6 single-stack terminal, the IPv4 terminal and the IPv4 / IPv6 dual-stack terminal set the running modes of the scene data path components according to accessing IPv6 Internet or IPv4 Internet; The data path is in turn the access layer IPv4 / IPv6 translation device, the core network, the export layer IPv4 / IPv6 translation device and the accessed Internet. 6.The IPv6 single-stack evolution method of claim 1, wherein: The main part of the scheme comprises an export layer IPv4 / IPv6 translation device, an access layer IPv4 / IPv6 translation device and an IPv6 single-stack development monitoring and management center; The export layer IPv4 / IPv6 translation device is deployed at the export, the access layer IPv4 / IPv6 translation device is deployed in a two-layer transparent manner at the terminal access network, and the IPv6 single-stack development monitoring and management center is deployed at a data center or a network reachable position; The access layer IPv4 / IPv6 translation device counts the number of sensed terminal types, counts the time sequence data of the traffic size of each scene, and reports to the IPv6 single-stack development monitoring and management center.

7. An IPv6 single stack evolution apparatus, characterized by, The device comprises: An access layer translation module configured to receive original transmission messages sent by terminals, analyze the destination address types of the messages, judge the access targets, and uniformly output IPv6 traffic to the core network; A core network routing module configured to forward pure IPv6 traffic, not to process any IPv4 routing or translation logic, and to select a path according to an IPv6 destination address; An export layer translation module configured to receive IPv6 traffic sent by the core network, reversely convert the IPv6 messages into IPv4 format, and forward the IPv4 format to the IPv4 Internet. 8.The IPv6 single-stack evolution device of claim 7, wherein: The access layer translation module converts IPv4 messages into IPv6 format for IPv4 Internet requests, and directly transmits original IPv6 messages for IPv6 Internet requests; The core network routing module routes IPv6 traffic accessing the IPv4 Internet to the export layer translation module, and directly routes IPv6 traffic accessing the IPv6 Internet to the IPv6 Internet; The export layer translation module performs IPv6 to IPv4 conversion through a reverse translation engine.

9. An electronic device, comprising: The IPv6 single-stack evolution method of any one of claims 1 to 6 comprises: A first gateway device deployed near the terminal side at the entrance of the core network, configured to convert IPv4 messages initiated by terminals into IPv6 format, and directly transmit original IPv6 messages initiated by terminals; A second gateway device deployed near the Internet side at the exit of the core network, configured to translate IPv6 traffic accessing the IPv4 Internet transmitted by the core network into IPv4 traffic, access the IPv4 Internet, and transmit original IPv6 traffic to the IPv6 Internet.

Images