IPv6 network access methods, devices, and storage media

Abstract

Embodiments of the present application provide an IPv6 network access method, device and storage medium, wherein in the method, in a case where a first IPv6 address corresponding to a first domain name is of a first type, a user-side device only needs to maintain a stateless correspondence table item according to a first IPv4 address corresponding to the first domain name, and does not need to maintain a complex stateful NAT46 session table, thereby saving resources of the user-side device. In addition, the first IPv4 address in the stateless correspondence table item is an existing IPv4 address corresponding to the first domain name, and does not need to occupy an IPv4 address in an address pool of the user-side device, thereby reducing consumption of IPv4 addresses. In addition, the embodiments of the present application provide a real IPv4 address corresponding to the first domain name to a first terminal, which is beneficial to subsequent service access of the first terminal through the real IPv4 address.

Description

Technical Field

[0001] This application relates to the field of data communication technology, specifically to an IPv6 network access method, device, and storage medium. Background Technology

[0002] In recent years, with the continuous advancement of IPv6 transformation and the constant evolution of new IPv6 technologies, global IPv6 traffic has increased significantly, especially in China's networks. As the proportion of IPv6 traffic continues to rise, IPv6 single-stack technology is also constantly evolving.

[0003] In the evolution of IPv6 into a single-stack architecture, Network Address Translation (NAT) has become increasingly important. NAT64 translates IPv6 addresses to IPv4 addresses, while NAT46 translates IPv4 addresses to IPv6 addresses. In some scenarios, both the network and service servers have been upgraded to IPv6 single-stack, but some end-user devices, such as home wireless routers, may not support IPv6, potentially resulting in home devices being assigned only private IPv4 addresses. In such cases, Customer Premise Equipment (CPE), such as a home gateway, is needed to perform NAT46 translation to enable access to the IPv6 network and services.

[0004] In some NAT46 scenarios, the CPE needs to use the IPv4 addresses in the locally configured IP address pool for address translation, which consumes IPv4 addresses. In addition, it is necessary to maintain complex stateful NAT46 session entries, which wastes CPE resources. Summary of the Invention

[0005] At least one embodiment of this application provides an IPv6 network access method, device, and storage medium to reduce the consumption of IPv4 addresses caused by network address translation and save CPE resources.

[0006] To solve the above-mentioned technical problems, this application is implemented as follows:

[0007] In a first aspect, embodiments of this application provide an IPv6 network access method, applied to a user-side device, comprising:

[0008] Receive a first request message sent by a first terminal, the first request message being used to request the IPv4 address corresponding to the first domain name;

[0009] Send a second request message to the domain name resolution server. The second request message is used to request the IPv6 address corresponding to the first domain name.

[0010] The system receives a first response message sent by the domain name resolution server. The first response message includes a first IPv6 address corresponding to the first domain name and the type of the first IPv6 address. The type of the first IPv6 address includes: a first type jointly represented by the first IPv6 address prefix of the network address translation gateway and the first IPv4 address corresponding to the first domain name; and a second type represented by the independent IPv6 address corresponding to the first domain name.

[0011] If the first IPv6 address is of the first type, a stateless correspondence table entry between the first IPv6 address prefix and the first IPv4 address is generated, and the first IPv4 address corresponding to the first domain name is sent to the first terminal.

[0012] Optionally, the above methods also include:

[0013] Receive a first access request, the destination address of the first access request being the first IPv4 address;

[0014] The first access request is subjected to a first address translation process, and the processed first access request is sent, wherein the first address translation process includes:

[0015] Based on the stateless mapping entry, the destination address of the first access request is converted into a first IPv6 address jointly represented by the first IPv6 address prefix and the first IPv4 address.

[0016] Optionally, the source address of the first access request is a second IPv4 address, and the first address translation process further includes:

[0017] The source address of the first access request is converted into a second IPv6 address represented by the second IPv6 address prefix of the user-side device and the second IPv4 address.

[0018] Optionally, the above methods also include:

[0019] If the first IPv6 address is of the second type, a stateful correspondence entry between the third IPv4 address and the first IPv6 address is generated based on the third IPv4 address in the IPv4 address pool, and the third IPv4 address corresponding to the first domain name is sent to the first terminal.

[0020] Optionally, the above methods also include:

[0021] Receive a second access request, the destination address of which is the third IPv4 address;

[0022] The second access request is subjected to a second address translation process, and the processed second access request is sent, wherein the second address translation process includes:

[0023] Based on the stateful mapping table entry, the destination address of the second access request is converted to the first IPv6 address corresponding to the third IPv4 address.

[0024] Optionally, the source address of the second access request is a second IPv4 address, and the second address translation process further includes:

[0025] The source address of the second access request is converted into a second IPv6 address represented by the second IPv6 address prefix of the user-side device and the second IPv4 address.

[0026] Optionally, the first response message is a DNS response message based on the Domain Name Resolution Extension (EDNS) protocol, and the type of the first IPv6 address is carried in a reserved field in the OPT resource record of the DNS response message, or in a reserved field in the header portion of the DNS response message.

[0027] Secondly, embodiments of this application provide an IPv6 network access method applied to a domain name resolution server, including:

[0028] Receive a request message sent by the user-side device, the request message being used to request the IPv6 address corresponding to the first domain name;

[0029] Send a response message to the user-side device, the response message containing the first IPv6 address corresponding to the first domain name and the type of the first IPv6 address;

[0030] The types of the first IPv6 address include: a first type jointly represented by the first IPv6 address prefix of the network address translation gateway and the first IPv4 address corresponding to the first domain name; and a second type represented by the independent IPv6 address corresponding to the first domain name.

[0031] Optionally, the response message is a DNS response message based on the Domain Name Resolution Extension (EDNS) protocol, and the type of the first IPv6 address is carried in a reserved field in the OPT resource record of the DNS response message, or in a reserved field in the header portion of the DNS response message.

[0032] Optionally, before sending a response message to the user-side device, the method further includes:

[0033] Query the pre-established correspondence between domain names, IPv6 addresses, and IPv6 address types to determine the first IPv6 address corresponding to the first domain name and the type of the first IPv6 address.

[0034] Thirdly, embodiments of this application provide a user-side device, including a transceiver and a processor, wherein...

[0035] The transceiver is configured to receive a first request message sent by a first terminal, the first request message being used to request an IPv4 address corresponding to a first domain name; send a second request message to a domain name resolution server, the second request message being used to request an IPv6 address corresponding to the first domain name; and receive a first response message sent by the domain name resolution server, the first response message containing a first IPv6 address corresponding to the first domain name and the type of the first IPv6 address; wherein the type of the first IPv6 address includes: a first type jointly represented by a first IPv6 address prefix of a network address translation gateway and a first IPv4 address corresponding to the first domain name; and a second type represented by an independent IPv6 address corresponding to the first domain name.

[0036] The processor is configured to, when the first IPv6 address is of the first type, generate a stateless correspondence entry between the first IPv6 address prefix and the first IPv4 address, and send the first IPv4 address corresponding to the first domain name to the first terminal.

[0037] Optionally, the transceiver is further configured to receive a first access request, wherein the destination address of the first access request is the first IPv4 address;

[0038] The processor is further configured to perform a first address translation process on the first access request and send the processed first access request, wherein the first address translation process includes:

[0039] Based on the stateless mapping entry, the destination address of the first access request is converted into a first IPv6 address jointly represented by the first IPv6 address prefix and the first IPv4 address.

[0040] Optionally, the source address of the first access request is a second IPv4 address, and the first address translation process further includes:

[0041] The source address of the first access request is converted into a second IPv6 address represented by the second IPv6 address prefix of the user-side device and the second IPv4 address.

[0042] Optionally, the processor is further configured to, when the first IPv6 address is of the second type, generate a stateful correspondence entry between the third IPv4 address and the first IPv6 address based on the third IPv4 address in the IPv4 address pool, and send the third IPv4 address corresponding to the first domain name to the first terminal.

[0043] Optionally, the transceiver is further configured to receive a second access request, wherein the destination address of the second access request is the third IPv4 address;

[0044] The processor is further configured to perform a second address translation process on the second access request and send the processed second access request, wherein the second address translation process includes:

[0045] Based on the stateful mapping table entry, the destination address of the second access request is converted to the first IPv6 address corresponding to the third IPv4 address.

[0046] Optionally, the source address of the second access request is a second IPv4 address, and the second address translation process further includes:

[0047] The source address of the second access request is converted into a second IPv6 address represented by the second IPv6 address prefix of the user-side device and the second IPv4 address.

[0048] Optionally, the first response message is a DNS response message based on the Domain Name Resolution Extension (EDNS) protocol, and the type of the first IPv6 address is carried in a reserved field in the OPT resource record of the DNS response message, or in a reserved field in the header portion of the DNS response message.

[0049] Fourthly, embodiments of this application provide a user-side device, including: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method described in the first aspect.

[0050] Fifthly, embodiments of this application provide a domain name resolution server, including a transceiver and a processor, wherein...

[0051] The transceiver is used to receive request messages sent by user-side devices, the request messages being used to request the IPv6 address corresponding to the first domain name;

[0052] Send a response message to the user-side device, the response message containing the first IPv6 address corresponding to the first domain name and the type of the first IPv6 address;

[0053] The types of the first IPv6 address include: a first type jointly represented by the first IPv6 address prefix of the network address translation gateway and the first IPv4 address corresponding to the first domain name; and a second type represented by the independent IPv6 address corresponding to the first domain name.

[0054] Optionally, the response message is a DNS response message based on the Domain Name Resolution Extension (EDNS) protocol, and the type of the first IPv6 address is carried in a reserved field in the OPT resource record of the DNS response message, or in a reserved field in the header portion of the DNS response message.

[0055] Optionally, the processor is configured to query a pre-established correspondence between a domain name, an IPv6 address, and the type of an IPv6 address before sending a response message to the user-side device, and determine the first IPv6 address corresponding to the first domain name and the type of the first IPv6 address.

[0056] In a sixth aspect, embodiments of this application provide a domain name resolution server, including: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method described in the second aspect.

[0057] In a seventh aspect, embodiments of this application provide a computer-readable storage medium storing a program that, when executed by a processor, implements the steps of the method described above.

[0058] Compared with existing technologies, the IPv6 network access method, device, and storage medium provided in this application embodiment, when the first IPv6 address is of the first type, only require the user-side device to maintain a stateless mapping entry based on the real IPv4 address (first IPv4 address) corresponding to the first domain name. This eliminates the need to maintain a complex stateful NAT46 session table, thus saving user-side device resources (such as storage and computing resources). Furthermore, the first IPv4 address in the aforementioned stateless mapping entry is an existing IPv4 address corresponding to the first domain name, and does not require occupying IPv4 addresses in the user-side device's local address pool, thereby reducing IPv4 address consumption. Additionally, this application embodiment provides the real IPv4 address corresponding to the first domain name to the first terminal, which facilitates subsequent service access by the first terminal through this real IPv4 address. Attached Figure Description

[0059] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0060] Figure 1 This is a schematic diagram illustrating NAT46 conversion performed by CPE in related technologies.

[0061] Figure 2 This is another schematic diagram illustrating NAT46 conversion performed by CPE in related technologies;

[0062] Figure 3 This is another schematic diagram illustrating NAT46 conversion performed by CPE in related technologies;

[0063] Figure 4 This is a flowchart illustrating an IPv6 network access method according to an embodiment of this application.

[0064] Figure 5 This is another flowchart illustrating an IPv6 network access method according to an embodiment of this application.

[0065] Figure 6 This is an example diagram illustrating the interaction flow between devices in the IPv6 network access method according to an embodiment of this application.

[0066] Figure 7 This is another example diagram illustrating the interaction flow between devices in the IPv6 network access method according to an embodiment of this application;

[0067] Figure 8 This is an example diagram of an EDNS extension method according to an embodiment of this application;

[0068] Figure 9 This is another example diagram of the EDNS extension method in this application embodiment;

[0069] Figure 10 This is a schematic diagram of the structure of a user-side device according to an embodiment of this application;

[0070] Figure 11 This is a schematic diagram of the structure of a user-side device according to another embodiment of this application;

[0071] Figure 12 This is a schematic diagram of the structure of a domain name resolution server according to an embodiment of this application;

[0072] Figure 13 This is a schematic diagram of the structure of a domain name resolution server according to another embodiment of this application;

[0073] Figure 14This is a schematic diagram of the structure of a user-side device according to another embodiment of this application;

[0074] Figure 15 This is a schematic diagram of the structure of a domain name resolution server according to another embodiment of this application. Detailed Implementation

[0075] Exemplary embodiments of the present application will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this application will be thorough and complete, and will fully convey the scope of the present application to those skilled in the art.

[0076] The terms “first,” “second,” etc., used in the specification and claims of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus. The terms “and / or” in the specification and claims indicate at least one of the connected objects.

[0077] The following description provides examples and is not intended to limit the scope, applicability, or configuration set forth in the claims. Changes may be made to the function and arrangement of the elements discussed without departing from the spirit and scope of this disclosure. Various procedures or components may be appropriately omitted, substituted, or added to the examples. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Furthermore, features described with reference to certain examples may be combined in other examples.

[0078] With both the network and service servers upgraded to IPv6 single-stack, but home terminals are only assigned IPv4 private addresses due to reasons such as home wireless routers not supporting IPv6, a CPE is needed to perform NAT46 translation to enable access to the IPv6 network and services. Please refer to... Figure 1 and Figure 2 The main processing steps are as follows:

[0079] Because some home network wireless routers may not support IPv6, home devices may only be assigned IPv4 private addresses. Figure 1Laptops, mobile terminals, and other terminals in the system are only assigned IPv4 private addresses. When these IPv4 terminals access IPv6 services, a NAT46 translation needs to be performed on the CPE, including NAT46 translation of the source address and NAT46 translation of the destination address.

[0080] For NAT46 translation of the source address: the IPv6 source address can be directly generated by adding the IPv4 private address to the LAN-side IPv6 prefix previously obtained by the CPE; this is a stateless NAT46 translation technique. For NAT46 translation of the destination address, stateful NAT46 technology can be used.

[0081] In addition, in fixed-line scenarios, NAT46 can be deployed on the home gateway CPE; in mobile scenarios, NAT46 can be deployed on the terminal. This application primarily uses a fixed-line scenario as an example for illustration. The implementation in mobile scenarios is similar to that in fixed-line scenarios, and this application is applicable to both fixed-line and mobile scenarios.

[0082] The business processes of related technical solutions are as follows: Figure 2 As shown. From the perspective of the terminal accessing IPv6 service server 1 (the return direction is the reverse), it includes:

[0083] (1) The terminal initiates a DNS4 query request to request the IPv4 address corresponding to the domain name (e.g., www.abc.com) of the business server 1. After obtaining the request, the CPE acts as a DNS proxy to initiate a DNS6 query request to request the IPv6 address corresponding to the domain name from the DNS server.

[0084] (2) After receiving the AAAA record (containing the IPv6 address of business server 1) returned by the DNS Server, the CPE performs stateful NAT46 translation, that is, according to the previously configured IPv4 address pool, it generates and saves NAT46 translation entries for business server 1, such as business server 1-IPv4 address <-> business server 1-IPv6 address.

[0085] (3) The CPE sends the converted IPv4 address of the service server 1 (service server 1 - IPv4 address) to the terminal via a DNS4 response message.

[0086] (4) The terminal uses this address as the destination address to initiate an IPv4 access request. After the access request reaches the CPE, it undergoes NAT46 translation:

[0087] Stateless NAT46 translation of the source address: Based on the source IPv4 address of the access request, the IPv4 private address is translated into the source IPv6 address represented by the IPv4 private address and the LAN-side IPv6 prefix of the CPE.

[0088] Stateful NAT46 translation of the destination address: The previous stateful NAT46 translation entry is used for translation, that is, the destination IPv4 address of the access request is translated from the IPv4 address of business server 1 to the IPv6 address of business server 1.

[0089] like Figure 3 As shown, in a NAT46 scenario, there are some Internet Content Providers (ICPs) whose content delivery servers are still IPv4 servers, but they deploy NAT64 gateways to provide services similar to IPv6.

[0090] In this scenario, the ICP's DNS server returns an AAAA record (IPv6 address) to the user that represents the IPv6 address jointly represented by the IPv6 prefix of the NAT64 gateway and IPv4 service server 1 - IPv4 address 1, i.e., the IPv6 prefix of the NAT64 gateway + IPv4 service server 1 - IPv4 address 1. This IPv6 address needs to undergo stateful NAT46 translation on the CPE, resulting in the address: IPv4 service server 1 - IPv4 address 2. This leads to the following problem:

[0091] 1) IPv4 service server 1 consumed IPv4 address 1 and IPv4 address 2, thus resulting in more IPv4 address consumption;

[0092] 2) Maintaining a complex stateful NAT46 session table results in a waste of CPE resources;

[0093] 3) In addition, the real IPv4 address corresponding to the domain name (such as IPv4 service server 1 - IPv4 address 1) is not sent to the client, which is not conducive to business development.

[0094] To address at least one of the above problems, embodiments of this application provide an IPv6 network access method that reduces IPv4 address consumption due to network address translation, thus conserving CPE resources. Please refer to... Figure 4 The IPv6 network access method provided in this application embodiment, when applied to a user-side device, such as a CPE, includes:

[0095] Step 41: Receive a first request message sent by the first terminal. The first request message is used to request the IPv4 address corresponding to the first domain name.

[0096] Here, the first request message can be a DNS4 query request, which contains the first domain name and type A (type: A) to request the IPv4 address corresponding to the first domain name.

[0097] Step 42: Send a second request message to the domain name resolution server. The second request message is used to request the IPv6 address corresponding to the first domain name.

[0098] Here, the second request message can be a DNS query request, which includes the first domain name and type 4A (type: AAAA) to request the IPv6 address corresponding to the first domain name.

[0099] Step 43: Receive a first response message sent by the domain name resolution server. The first response message includes the first IPv6 address corresponding to the first domain name and the type of the first IPv6 address. The type of the first IPv6 address includes: a first type jointly represented by the first IPv6 address prefix of the network address translation gateway and the first IPv4 address corresponding to the first domain name; and a second type represented by the independent IPv6 address corresponding to the first domain name.

[0100] Here, the first response message can be a DNS response message based on the Extension Mechanisms for DNS (EDNS) protocol. The type of the first IPv6 address is carried in the reserved field (Z field) of the OPT resource record in the DNS response message, or in the reserved field (Z field) of the header portion of the DNS response message. The first type of first IPv6 address is an IPv6 address formed by concatenating the first IPv6 address prefix of the network address translation gateway with the first IPv4 address corresponding to the first domain name. The second type of first IPv6 address is an IPv6 address assigned to the first domain name; in this case, the first domain name may not have been assigned an IPv4 address. The independent IPv6 address refers to an IPv6 address that is assigned to the first domain name as a whole, rather than being formed by concatenating the IPv6 address prefix of the network address translation gateway with the first IPv4 address corresponding to the first domain name.

[0101] In this way, by parsing the first response message, the user-side device can obtain the first IPv6 address corresponding to the first domain name and the type of the first IPv6 address.

[0102] Step 44: If the first IPv6 address is of the first type, generate a stateless correspondence table entry between the first IPv6 address prefix and the first IPv4 address, and send the first IPv4 address corresponding to the first domain name to the first terminal.

[0103] Here, when the first IPv6 address is of the first type, the user-side device generates a stateless mapping entry, which maintains the mapping relationship between the first IPv6 address prefix and the first IPv4 address. Additionally, the user-side device also sends the first IPv4 address corresponding to the first domain name to the first terminal.

[0104] Through the above steps, in this embodiment of the application, when the first IPv6 address is of the first type, the user-side device only needs to maintain a stateless mapping entry based on the real IPv4 address (first IPv4 address) corresponding to the first domain name, without needing to maintain a complex stateful NAT46 session table, thereby saving user-side device resources (such as storage and computing resources). Furthermore, the first IPv4 address in the aforementioned stateless mapping entry is an existing IPv4 address corresponding to the first domain name, and does not need to occupy IPv4 addresses in the user-side device's local address pool, thus reducing IPv4 address consumption. Additionally, since this embodiment of the application provides the real IPv4 address corresponding to the first domain name to the first terminal in step 44, this facilitates subsequent service access by the first terminal through this real IPv4 address.

[0105] After obtaining the real IPv4 address corresponding to the first domain name, the first terminal can initiate access to related services based on that real IPv4 address, such as initiating a data plane IPv4 access request (assuming it is the first access request). In this case, the above method also includes:

[0106] Step 45a: The user-side device receives a first access request, the destination address of which is the first IPv4 address.

[0107] Here, the source address of the first access request is the IPv4 address of the first terminal itself (assuming it is the second IPv4 address, such as IPv4 private network address 1), and the destination address is the first IPv4 address mentioned above.

[0108] Step 46a: The user-side device performs a first address translation process on the first access request and sends the processed first access request. The first address translation process includes: converting the destination address of the first access request into a first IPv6 address jointly represented by the first IPv6 address prefix and the first IPv4 address according to the stateless correspondence table entry.

[0109] Here, the first address translation process described above is a NAT46 translation process. Additionally, in step 46a, the first address translation process may further include: converting the source address of the first access request into a second IPv6 address jointly represented by the second IPv6 address prefix of the user-side device and the second IPv4 address. That is, the second IPv6 address is an IPv6 address formed by concatenating the second IPv6 address prefix of the user-side device with the second IPv4 address.

[0110] In this embodiment of the application, if the first IPv6 address obtained in step 43 is of the second type, the user-side device can generate a stateful correspondence table entry between the third IPv4 address and the first IPv6 address based on the third IPv4 address in the IPv4 address pool (such as the address pool configured by the user-side device itself), and send the third IPv4 address corresponding to the first domain name to the first terminal.

[0111] Similarly, after obtaining the third IPv4 address corresponding to the first domain name, the first terminal can initiate access to related services based on the third IPv4 address, such as initiating a data plane IPv4 access request (assuming it is the second access request). In this case, the above method also includes:

[0112] Step 45b: The user-side device receives a second access request, the destination address of which is the third IPv4 address.

[0113] Here, the source address of the second access request is the IPv4 address of the first terminal itself (assuming it is the second IPv4 address, such as IPv4 private network address 1), and the destination address is the third IPv4 address mentioned above.

[0114] Step 46b: The user-side device performs a second address translation process on the second access request and sends the processed second access request. The second address translation process includes: converting the destination address of the second access request to the first IPv6 address corresponding to the third IPv4 address according to the stateful correspondence table entry.

[0115] Here, the second address translation process described above is a NAT46 translation process. Additionally, in step 46b, the second address translation process may further include: converting the source address of the second access request into a second IPv6 address jointly represented by the user-side device's second IPv6 address prefix and the second IPv4 address. That is, the second IPv6 address is an IPv6 address formed by concatenating the user-side device's second IPv6 address prefix and the second IPv4 address.

[0116] Please refer to Figure 5The IPv6 network access method provided in this application embodiment, when applied to a domain name resolution server, includes:

[0117] Step 51: Receive a request message sent by the user-side device, the request message being used to request the IPv6 address corresponding to the first domain name.

[0118] Here, the above request message may be a DNS query request, which contains the first domain name and type 4A (type: AAAA) to request the IPv6 address corresponding to the first domain name.

[0119] Step 52: Send a response message to the user-side device. The response message includes the first IPv6 address corresponding to the first domain name and the type of the first IPv6 address. The type of the first IPv6 address includes: a first type jointly represented by the first IPv6 address prefix of the network address translation gateway and the first IPv4 address corresponding to the first domain name; and a second type represented by the independent IPv6 address corresponding to the first domain name.

[0120] Here, the response message can be a DNS response message based on the EDNS protocol. The type of the first IPv6 address is carried in the reserved field (Z field) of the OPT resource record in the DNS response message, or in the reserved field (Z field) of the header portion of the DNS response message. The first type of first IPv6 address is an IPv6 address formed by concatenating the first IPv6 address prefix of the network address translation gateway with the first IPv4 address corresponding to the first domain name. The second type of first IPv6 address is the IPv6 address assigned to the first domain name.

[0121] Specifically, the domain name resolution server can determine the first IPv6 address corresponding to the first domain name and the type of the first IPv6 address by querying a pre-established correspondence between domain names, IPv6 addresses, and IPv6 address types. This correspondence can be pre-configured on the domain name resolution server.

[0122] Through the above steps, the domain name resolution server can notify the user-side device of the type of the first IPv6 address corresponding to the first domain name, so as to help the user-side device establish a stateless correspondence table entry when the first IPv6 address is of the first type, thereby saving IPv4 resources and user-side device resources.

[0123] The methods of this application embodiment have been described above from the perspectives of the user-side device and the domain name resolution server side. The following further combines... Figure 6 and Figure 7 The methods described above in the embodiments of this application will be further described through examples of interaction processes between devices. Among them, Figure 6 This is a process example for a domain name whose corresponding IPv6 address is of type 1. Figure 7 This is a process example for a domain name whose corresponding IPv6 address is of the second type.

[0124] The following example addresses the relevant NAT46 issue by extending the DNS protocol:

[0125] For the AAAA record returned by the DNS server, the CPE needs to distinguish whether the IPv6 service is provided directly through a pure IPv6 server (corresponding to the second type of IPv6 address) or through a "NAT64 + IPv4 server" method (corresponding to the first type of IPv6 address). For the former, stateful NAT46 is used, while for the latter, stateless NAT46 can be used. This reduces the waste of IPv4 addresses, alleviates the burden on the CPE in maintaining the NAT session table, and still provides the actual IPv4 server address to the terminal (client).

[0126] Specifically, by extending the DNS protocol, the DNS server, while returning the AAAA record in the DNS response message, identifies the IPv6 service mode of the server that records the AAAA record (i.e., the type of IPv6 address corresponding to the domain name).

[0127] Extension Method 1: EDNS Extension

[0128] First, such as Figure 8 As shown, a new bit needs to be added to the "Z" field (i.e., the reserved field) of the OPT resource record in the DNS response message as a "NAT" identifier. When this bit is set to 1, it indicates that "the IPv6 service provided by this AAAA record is in NAT64+IPv4 mode," meaning the IPv6 address corresponding to the domain name is the first type mentioned above; when this bit is set to 0, it indicates that "the IPv6 service provided by this AAAA record is in pure IPv6 mode," meaning the IPv6 address corresponding to the domain name is the second type mentioned above.

[0129] After EDNS extension, the process of the "NAT64+IPv4 server" IPv6 service mode (i.e., the domain name corresponds to the first type of IPv6 address mentioned above) is as follows: Figure 6 As shown, it mainly includes:

[0130] Step a: The terminal initiates a DNS4 query request to obtain the A record of a certain domain name (the IPv4 address corresponding to the requested domain name).

[0131] Step b: After receiving the above query request, the CPE requests the AAAA record of the domain name from the DNS Server (requesting the IPv6 address corresponding to the domain name).

[0132] Step c: The DNS server returns the AAAA record for the domain name, and simultaneously sets the "NAT" flag in the OPT resource record to 1. The IPv6 address included in the AAAA record is an IPv6 address formed by concatenating the NAT64 prefix with the IPv4 address 1 corresponding to the domain name.

[0133] Step d: Since the "NAT" bit is 1, the CPE performs stateless NAT46 translation, that is, generates and saves a stateless correspondence entry between the NAT64 prefix and the IPv4 address 1.

[0134] Step e: The CPE sends a DNS4 response to the terminal, returning the A record (IPv4 address 1) for the domain name;

[0135] Step f: Enable IPv4 data plane access on the terminal: The source address is the terminal's private IPv4 address, and the destination address is IPv4 address 1.

[0136] Step g: The CPE performs NAT46 translation, with both source and destination address translations being stateless NAT46 translations.

[0137] Source address translation: CPE's LAN-side IPv6 prefix + IPv4 private address;

[0138] Destination address is translated to: NAT64 prefix + IPv4 address 1.

[0139] Step h: After NAT46 translation is complete, enable IPv6 data plane access.

[0140] After EDNS extension, the process for the "pure IPv6 server" IPv6 service mode (i.e., the domain name corresponds to the second type of IPv6 address mentioned above) is as follows: Figure 7 As shown, it includes:

[0141] Step a: The terminal initiates a DNS4 query request to obtain the A record of a certain domain name (the IPv4 address corresponding to the requested domain name).

[0142] Step b: After obtaining the query request, the CPE requests the AAAA record of the domain name from the DNS Server (requesting the IPv6 address corresponding to the domain name).

[0143] Step c: The DNS server returns the AAAA record for the domain name, and simultaneously sets the "NAT" flag in the OPT resource record to 0. At this point, the IPv6 address included in the AAAA record is the unique IPv6 address corresponding to the domain name.

[0144] Step d: Since the "NAT" bit is 0, the CPE performs stateful NAT46 translation, that is, according to the configured IPv4 address pool, it generates and saves stateful NAT46 entries: IPv4 address 1 in the IPv4 address pool <-> IPv6 address 1 in the AAAA record.

[0145] Step e: The CPE sends a DNS4 response to the terminal, returning the A record for the domain name (IPv4 address 1 in the IPv4 address pool).

[0146] Step f: The terminal enables IPv4 data plane access: the source address is an IPv4 private address, and the destination address is IPv4 address 1 in the IPv4 address pool.

[0147] Step g: The CPE performs NAT46 translation, where the source address is translated using stateless NAT46, and the destination address is translated using stateful NAT46.

[0148] Source address translation: CPE's LAN-side IPv6 prefix + IPv4 private address;

[0149] Destination address translation: IPv6 address 1 in the AAAA record.

[0150] Step 8: After NAT46 translation is complete, enable IPv6 data plane access.

[0151] As another way to extend EDNS, such as Figure 9 As shown, one bit from the original three reserved bits (Z field) in the Header section of the DNS response message can be used as a "NAT" identifier. When this bit is set to 1, it indicates that "the IPv6 service provided by this AAAA record is in NAT64+IPv4 mode," meaning the IPv6 address corresponding to the domain name is of the first type mentioned above. When this bit is set to 0, it indicates that "the IPv6 service provided by this AAAA record is in pure IPv6 mode," meaning the IPv6 address corresponding to the domain name is of the second type mentioned above.

[0152] After header expansion, the processes for the two IPv6 service modes are respectively as follows: Figure 6 and Figure 7 Similar to each other, the only difference is the location of the "NAT" flag.

[0153] The various methods of the embodiments of this application have been described above. Apparatus for implementing the above methods will now be provided.

[0154] Please refer to Figure 10 This application also provides a user-side device, including:

[0155] The first receiving module 1001 is used to receive a first request message sent by the first terminal, wherein the first request message is used to request the IPv4 address corresponding to the first domain name;

[0156] The first sending module 1002 is used to send a second request message to the domain name resolution server, the second request message being used to request the IPv6 address corresponding to the first domain name;

[0157] The second receiving module 1003 is configured to receive a first response message sent by the domain name resolution server. The first response message includes a first IPv6 address corresponding to the first domain name and the type of the first IPv6 address. The type of the first IPv6 address includes: a first type jointly represented by the first IPv6 address prefix of the network address translation gateway and the first IPv4 address corresponding to the first domain name; and a second type represented by the independent IPv6 address corresponding to the first domain name.

[0158] The first processing module 1004 is configured to generate a stateless correspondence table entry between the first IPv6 address prefix and the first IPv4 address when the first IPv6 address is of the first type, and send the first IPv4 address corresponding to the first domain name to the first terminal.

[0159] Through the above modules, the embodiments of this application can reduce the consumption of IPv4 addresses caused by network address translation and save CPE resources.

[0160] Optionally, the aforementioned user-side equipment also includes:

[0161] The third receiving module is used to receive the first access request, wherein the destination address of the first access request is the first IPv4 address;

[0162] The second processing module is configured to perform a first address translation process on the first access request and send the processed first access request, wherein the first address translation process includes:

[0163] Based on the stateless mapping entry, the destination address of the first access request is converted into a first IPv6 address jointly represented by the first IPv6 address prefix and the first IPv4 address.

[0164] Optionally, the source address of the first access request is a second IPv4 address, and the first address translation process further includes:

[0165] The source address of the first access request is converted into a second IPv6 address represented by the second IPv6 address prefix of the user-side device and the second IPv4 address.

[0166] Optionally, the aforementioned user-side equipment also includes:

[0167] The third processing module is configured to, when the first IPv6 address is of the second type, generate a stateful correspondence entry between the third IPv4 address and the first IPv6 address based on the third IPv4 address in the IPv4 address pool, and send the third IPv4 address corresponding to the first domain name to the first terminal.

[0168] Optionally, the aforementioned user-side equipment also includes:

[0169] The fourth receiving module is used to receive the second access request, wherein the destination address of the second access request is the third IPv4 address;

[0170] The fourth processing module is used to perform a second address translation process on the second access request and send the processed second access request, wherein the second address translation process includes:

[0171] Based on the stateful mapping table entry, the destination address of the second access request is converted to the first IPv6 address corresponding to the third IPv4 address.

[0172] Optionally, the source address of the second access request is a second IPv4 address, and the second address translation process further includes:

[0173] The source address of the second access request is converted into a second IPv6 address represented by the second IPv6 address prefix of the user-side device and the second IPv4 address.

[0174] Optionally, the first response message is a DNS response message based on the Domain Name Resolution Extension (EDNS) protocol, and the type of the first IPv6 address is carried in a reserved field in the OPT resource record of the DNS response message, or in a reserved field in the header portion of the DNS response message.

[0175] It should be noted that the device in this embodiment corresponds to the method applied to the user-side device described above. The implementation methods in each of the above embodiments are applicable to the embodiments of this device and can achieve the same technical effect. The device provided in this application embodiment can implement all the method steps implemented in the above method embodiments and can achieve the same technical effect. Therefore, the parts that are the same as those in the method embodiments and the beneficial effects will not be described in detail here.

[0176] Please refer to Figure 11 This application also provides a terminal 1100, including: a transceiver 1101 and a processor 1102;

[0177] The transceiver 1101 is configured to receive a first request message sent by a first terminal, the first request message being used to request an IPv4 address corresponding to a first domain name; send a second request message to a domain name resolution server, the second request message being used to request an IPv6 address corresponding to the first domain name; and receive a first response message sent by the domain name resolution server, the first response message containing a first IPv6 address corresponding to the first domain name and the type of the first IPv6 address; wherein the type of the first IPv6 address includes: a first type jointly represented by a first IPv6 address prefix of a network address translation gateway and a first IPv4 address corresponding to the first domain name; and a second type represented by an independent IPv6 address corresponding to the first domain name.

[0178] The processor 1102 is configured to generate a stateless correspondence table entry between the first IPv6 address prefix and the first IPv4 address when the first IPv6 address is of the first type, and send the first IPv4 address corresponding to the first domain name to the first terminal.

[0179] Optionally, the transceiver is further configured to receive a first access request, wherein the destination address of the first access request is the first IPv4 address;

[0180] The processor is further configured to perform a first address translation process on the first access request and send the processed first access request, wherein the first address translation process includes:

[0181] Based on the stateless mapping entry, the destination address of the first access request is converted into a first IPv6 address jointly represented by the first IPv6 address prefix and the first IPv4 address.

[0182] Optionally, the source address of the first access request is a second IPv4 address, and the first address translation process further includes:

[0183] The source address of the first access request is converted into a second IPv6 address represented by the second IPv6 address prefix of the user-side device and the second IPv4 address.

[0184] Optionally, the processor is further configured to, when the first IPv6 address is of the second type, generate a stateful correspondence entry between the third IPv4 address and the first IPv6 address based on the third IPv4 address in the IPv4 address pool, and send the third IPv4 address corresponding to the first domain name to the first terminal.

[0185] Optionally, the transceiver is further configured to receive a second access request, wherein the destination address of the second access request is the third IPv4 address;

[0186] The processor is further configured to perform a second address translation process on the second access request and send the processed second access request, wherein the second address translation process includes:

[0187] Based on the stateful mapping table entry, the destination address of the second access request is converted to the first IPv6 address corresponding to the third IPv4 address.

[0188] Optionally, the source address of the second access request is a second IPv4 address, and the second address translation process further includes:

[0189] The source address of the second access request is converted into a second IPv6 address represented by the second IPv6 address prefix of the user-side device and the second IPv4 address.

[0190] Optionally, the first response message is a DNS response message based on the Domain Name Resolution Extension (EDNS) protocol, and the type of the first IPv6 address is carried in a reserved field in the OPT resource record of the DNS response message, or in a reserved field in the header portion of the DNS response message.

[0191] It should be noted that the device in this embodiment corresponds to the method applied to the user-side device described above. The implementation methods in each of the above embodiments are applicable to the embodiments of this device and can achieve the same technical effect. The device provided in this application embodiment can implement all the method steps implemented in the above method embodiments and can achieve the same technical effect. Therefore, the parts that are the same as those in the method embodiments and the beneficial effects will not be described in detail here.

[0192] Please refer to Figure 12 This application also provides a domain name resolution server, including:

[0193] The first receiving module 1201 is used to receive a request message sent by the device, the request message being used to request the IPv6 address corresponding to the first domain name;

[0194] The first sending module 1202 is used to send a response message to the user-side device, the response message including the first IPv6 address corresponding to the first domain name and the type of the first IPv6 address;

[0195] The types of the first IPv6 address include: a first type jointly represented by the first IPv6 address prefix of the network address translation gateway and the first IPv4 address corresponding to the first domain name; and a second type represented by the independent IPv6 address corresponding to the first domain name.

[0196] Through the above modules, the embodiments of this application reduce the consumption of IPv4 addresses caused by network address translation, thus saving CPE resources.

[0197] Optionally, the response message is a DNS response message based on the Domain Name Resolution Extension (EDNS) protocol, and the type of the first IPv6 address is carried in a reserved field in the OPT resource record of the DNS response message, or in a reserved field in the header portion of the DNS response message.

[0198] Optionally, the aforementioned domain name resolution server may also include:

[0199] The query module is used to query the pre-established correspondence between domain names, IPv6 addresses, and IPv6 address types, and to determine the first IPv6 address corresponding to the first domain name and the type of the first IPv6 address.

[0200] It should be noted that the device in this embodiment corresponds to the method applied to the domain name resolution server side described above. The implementation methods in each of the above embodiments are applicable to the embodiments of this device and can achieve the same technical effect. The device provided in this application embodiment can implement all the method steps implemented in the above method embodiments and can achieve the same technical effect. Therefore, the parts that are the same as those in the method embodiments and the beneficial effects will not be described in detail here.

[0201] Please refer to Figure 13 This application embodiment also provides a domain name resolution server 1300, including: a transceiver 1301 and a processor 1302;

[0202] The transceiver 1301 is configured to receive a request message sent by a user-side device, the request message being used to request an IPv6 address corresponding to a first domain name; and to send a response message to the user-side device, the response message containing a first IPv6 address corresponding to the first domain name and the type of the first IPv6 address;

[0203] The types of the first IPv6 address include: a first type jointly represented by the first IPv6 address prefix of the network address translation gateway and the first IPv4 address corresponding to the first domain name; and a second type represented by the independent IPv6 address corresponding to the first domain name.

[0204] Optionally, the response message is a DNS response message based on the Domain Name Resolution Extension (EDNS) protocol, and the type of the first IPv6 address is carried in a reserved field in the OPT resource record of the DNS response message, or in a reserved field in the header portion of the DNS response message.

[0205] Optionally, the processor is configured to query a pre-established correspondence between a domain name, an IPv6 address, and the type of an IPv6 address before sending a response message to the user-side device, and determine the first IPv6 address corresponding to the first domain name and the type of the first IPv6 address.

[0206] It should be noted that the device in this embodiment corresponds to the method applied to the domain name resolution server side described above. The implementation methods in each of the above embodiments are applicable to the embodiments of this device and can achieve the same technical effect. The device provided in this application embodiment can implement all the method steps implemented in the above method embodiments and can achieve the same technical effect. Therefore, the parts that are the same as those in the method embodiments and the beneficial effects will not be described in detail here.

[0207] Please refer to Figure 14 This application also provides a user-side device 1400, including a processor 1401, a memory 1402, and a computer program stored in the memory 1402 and executable on the processor 1401. When the computer program is executed by the processor 1401, it implements the various processes of the above-described IPv6 network access method embodiments executed by the user-side device and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0208] Please refer to Figure 15 This application also provides a domain name resolution server 1500, including a processor 1501, a memory 1502, and a computer program stored in the memory 1502 and executable on the processor 1501. When the computer program is executed by the processor 1501, it implements the various processes of the above-described IPv6 network access method embodiments executed by the domain name resolution server and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0209] This application also provides a computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements the various processes of the above-described IPv6 network access method embodiments and achieves the same technical effects. To avoid repetition, it will not be described again here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0210] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0211] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0212] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. An IPv6 network access method applied to a user side device, characterized in that, The method comprises: receiving a first request message sent by a first terminal, the first request message being used for requesting an IPv4 address corresponding to a first domain name; sending a second request message to a domain name resolution server, the second request message being used for requesting an IPv6 address corresponding to the first domain name; receiving a first response message sent by the domain name resolution server, the first response message containing a first IPv6 address corresponding to the first domain name and a type of the first IPv6 address; wherein the type of the first IPv6 address comprises a first type in which a first IPv6 address prefix through a network address translation gateway is combined with a first IPv4 address corresponding to the first domain name to represent the first IPv6 address; and a second type in which an independent IPv6 address corresponding to the first domain name is used to represent the first IPv6 address; in a case where the first IPv6 address is of the first type, generating a stateless correspondence entry of the first IPv6 address prefix and the first IPv4 address, and sending the first IPv4 address corresponding to the first domain name to the first terminal.

2. The method of claim 1, wherein, The method further comprises: receiving a first access request, a destination address of the first access request being the first IPv4 address; performing first address conversion processing on the first access request, and sending the first access request after processing, wherein the first address conversion processing comprises: according to the stateless correspondence entry, converting the destination address of the first access request into a first IPv6 address in which the first IPv6 address prefix is combined with the first IPv4 address to represent the first IPv6 address.

3. The method of claim 2, wherein, The source address of the first access request is a second IPv4 address, and the first address conversion processing further comprises: converting the source address of the first access request into a second IPv6 address in which a second IPv6 address prefix of a user-side device is combined with the second IPv4 address to represent the second IPv6 address.

4. The method according to any one of claims 1 to 3, characterized in that, The method further comprises: in a case where the first IPv6 address is of the second type, generating a stateful correspondence entry of a third IPv4 address in an IPv4 address pool and the first IPv6 address according to the third IPv4 address, and sending the third IPv4 address corresponding to the first domain name to the first terminal.

5. The method of claim 4, wherein, The method further comprises: receiving a second access request, a destination address of the second access request being the third IPv4 address; performing second address conversion processing on the second access request, and sending the second access request after processing, wherein the second address conversion processing comprises: according to the stateful correspondence entry, converting the destination address of the second access request into the first IPv6 address corresponding to the third IPv4 address.

6. The method of claim 5, wherein, The source address of the second access request is a second IPv4 address, and the second address conversion processing further comprises: converting the source address of the second access request into a second IPv6 address in which a second IPv6 address prefix of a user-side device is combined with the second IPv4 address to represent the second IPv6 address.

7. The method of claim 1, wherein The first response message is a DNS response message based on an EDNS protocol of domain name resolution, and the type of the first IPv6 address is carried in a reserved field in an OPT resource record of the DNS response message, or is carried in a reserved field in a header of the DNS response message.

8. A user-side device, characterized by The transceiver and the processor are included, wherein The transceiver is configured to receive a first request message sent by a first terminal, the first request message being used to request an IPv4 address corresponding to a first domain name; send a second request message to a domain name resolution server, the second request message being used to request an IPv6 address corresponding to the first domain name; and receive a first response message sent by the domain name resolution server, the first response message containing the first IPv6 address corresponding to the first domain name and a type of the first IPv6 address, wherein the type of the first IPv6 address includes a first type in which a first IPv6 address prefix through a network address translation gateway is combined with a first IPv4 address corresponding to the first domain name, and a second type in which an independent IPv6 address corresponding to the first domain name is used. The processor is configured to, in a case where the first IPv6 address is of the first type, generate a stateless correspondence entry of the first IPv6 address prefix and the first IPv4 address, and send the first IPv4 address corresponding to the first domain name to the first terminal.

9. The user-side device of claim 8, wherein The transceiver is further configured to receive a first access request, a destination address of the first access request being the first IPv4 address. The processor is further configured to perform first address conversion processing on the first access request, and send the first access request after processing, wherein the first address conversion processing includes: According to the stateless correspondence entry, converting the destination address of the first access request into a first IPv6 address in which the first IPv6 address prefix is combined with the first IPv4 address.

10. The user-side device of claim 9, wherein, The source address of the first access request is a second IPv4 address, and the first address conversion processing further includes: Converting the source address of the first access request into a second IPv6 address in which a second IPv6 address prefix of the user-side device is combined with the second IPv4 address.

11. The user-side device of any one of claims 8 to 10, wherein The processor is further configured to, in a case where the first IPv6 address is of the second type, generate a stateful correspondence entry of a third IPv4 address in an IPv4 address pool and the first IPv6 address according to the third IPv4 address, and send the third IPv4 address corresponding to the first domain name to the first terminal.

12. The user-side device of claim 11, wherein The transceiver is further configured to receive a second access request, a destination address of the second access request being the third IPv4 address. The processor is further configured to perform second address conversion processing on the second access request and send the processed second access request, wherein the second address conversion processing comprises: According to the stateful correspondence table item, converting the destination address of the second access request into the first IPv6 address corresponding to the third IPv4 address.

13. The user-side device of claim 12, wherein, The source address of the second access request is a second IPv4 address, and the second address conversion processing further comprises: Converting the source address of the second access request into a second IPv6 address jointly represented by a second IPv6 address prefix of the user-side device and the second IPv4 address.

14. The user-side device of claim 8, wherein The first response message is a DNS response message based on an EDNS (Extension for DNS) protocol, and the type of the first IPv6 address is carried in a reserved field in an OPT (Option) resource record of the DNS response message or in a reserved field in a Header section of the DNS response message.

15. A user-side device, comprising: including: a processor, a memory, and a program stored in the memory and executable in the processor, and the program, when executed by the processor, implements the steps of the method of any one of claims 1 to 7.

16. A computer readable storage medium characterized by: The computer program stored in the computer readable storage medium, when executed by the processor, implements the steps of the method of any one of claims 1 to 7.

Images