A data access method, an access device, a storage medium and a computer program product

Abstract

The embodiment of the application provides a data access method and an access device, a storage medium and a computer program product, comprising: a first access device sending an IPv6 address query request for a target domain name to a second access device in a case that the first access device monitors that a client device requests an IPv6 address of the target domain name from a domain name resolution DNS server, and the DNS server does not find an AAAA record of the target domain name; the second access device performing A record query and NAT64 conversion operations for the target domain name; and the first access device forwarding IPv6 address information of the target domain name returned by the second access device to the client device, so that the client device performs data plane access based on the IPv6 address information of the target domain name.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of electronic applications, and in particular to a data access method, an access device, a storage medium and a computer program product. BACKGROUND

[0002] This year, with the continuous evolution of the Internet Protocol Version 6 (IPv6) new technology, the global IPv6 traffic has increased significantly. With the continuous increase of the existing network IPv6 traffic, most of the devices from the terminal to the content and from the entire network end to end have supported IPv6. In order to save the Internet Protocol Version 4 (IPv4) address resources, the IPv6 single stack address is allocated to the terminal, and when the IPv6 terminal accesses the IPv4 server device, the NAT64 conversion is performed through the Network Address Translation IPv6-to-IPv4 (NAT64) function of the Broadband Remote Access Server (BRAS) device to complete the access. The NAT64 function of the BRAS device is usually realized by the NAT64 plug-in board of the BRAS device.

[0003] However, some BRAS devices do not support the NAT64 plug-in board, which requires an independent NAT64 device to be externally hung on the BRAS device to realize the NAT64 conversion. However, the current IPv6 traffic has become mainstream, and the traffic that needs to be converted is not large. For these small part of conversion traffic, each BRAS device that does not support the NAT64 plug-in board is externally hung with a NAT64 device, which will cause waste of network resources and waste of network energy consumption. SUMMARY

[0004] The present application provides a data access method, an access device, a storage medium and a computer program product, which can.

[0005] The technical solution of the present application is realized as follows:

[0006] In a first aspect, the present application provides a data access method applied to a first access device, and the method comprises:

[0007] In the case that it is monitored that a client device requests an IPv6 address of a target domain name to a domain name resolution DNS server, and the DNS server does not find the AAAA record of the target domain name, an IPv6 address query request for the target domain name is sent to a second access device; so that the second access device performs the operations of A record query and NAT64 conversion for the target domain name.

[0008] forwarding the IPv6 address information of the target domain name returned by the second access device to the client device for the client device to perform data plane access based on the IPv6 address information of the target domain name.

[0009] In a second aspect, the present application provides a data access method, applied to a second access device, and the method comprises:

[0010] receiving an IPv6 address query request for a target domain name sent by a first access device;

[0011] performing A record query and NAT64 conversion operation for the target domain name according to the IPv6 address query request, to obtain IPv6 address information of the target domain name;

[0012] sending the IPv6 address information of the target domain name to the first access device.

[0013] In a third aspect, the present application provides a first access device, which comprises:

[0014] a first sending unit, configured to, in a case where it is monitored that a client device requests IPv6 address of a target domain name from a domain name resolution DNS server and the DNS server does not find AAAA record of the target domain name, send an IPv6 address query request for the target domain name to a second access device, so that the second access device performs A record query and NAT64 conversion operation for the target domain name, and forwards IPv6 address information of the target domain name returned by the second access device to the client device, so that the client device performs data plane access based on the IPv6 address information of the target domain name.

[0015] In a fourth aspect, the present application provides a second access device, which comprises:

[0016] a first receiving unit, configured to receive an IPv6 address query request for a target domain name sent by a first access device;

[0017] a conversion unit, configured to perform A record query and NAT64 conversion operation for the target domain name according to the IPv6 address query request, to obtain IPv6 address information of the target domain name;

[0018] a second sending unit, configured to send the IPv6 address information of the target domain name to the first access device.

[0019] In a fifth aspect, the application provides a first access device, which comprises a first processor and a first memory; the first processor implements the data access method applied to the first access device when executing a running program stored in the first memory.

[0020] In a sixth aspect, the application provides a second access device, which comprises a second processor and a second memory; the second processor implements the data access method applied to the second access device when executing a running program stored in the second memory.

[0021] In a seventh aspect, the application provides a storage medium, which stores a computer program; the computer program is executed by the first processor to implement the data access method applied to the first access device, or the computer program is executed by the second processor to implement the data access method applied to the second access device.

[0022] In an eighth aspect, the application provides a computer program product, which comprises a computer program; the computer program is executed by the first processor to implement the data access method applied to the first access device, or the computer program is executed by the second processor to implement the data access method applied to the second access device.

[0023] The application provides a data access method and an access device, a storage medium and a computer program product, and the method comprises the following steps: when the first access device monitors that a client device requests an IPv6 address of a target domain name from a domain name resolution DNS server, and the DNS server does not find an AAAA record of the target domain name, the first access device sends an IPv6 address query request for the target domain name to a second access device; the second access device performs A record query and NAT64 conversion operations for the target domain name; and the first access device forwards IPv6 address information of the target domain name returned by the second access device to the client device, so that the client device performs data plane access based on the IPv6 address information of the target domain name. By using the implementation scheme, when the first access device that does not support NAT64 monitors that an IPv6 client device accesses an IPv4 server, the first access device forwards the traffic that needs to be converted to the second access device that supports NAT64 to complete NAT64 conversion, and then sends the converted traffic to the client device, and the client device can subsequently realize data plane access to the IPv4 server through the first access device and the second access device, so that the existing second access device that supports NAT64 can be used to realize NAT64 conversion in the process in which the IPv6 client accesses the IPv4 server, and a NAT64 device does not need to be externally connected to the first access device, which can greatly reduce waste of network resources and network energy consumption. BRIEF DESCRIPTION OF DRAWINGS

[0024] Figure 1 This is a schematic diagram of a NAT64 translation scenario;

[0025] Figure 2 A flowchart of a data access method provided in this application embodiment Figure One ;

[0026] Figure 3 A schematic diagram of an exemplary transmission tunnel provided for an embodiment of this application;

[0027] Figure 4 A schematic diagram of an exemplary DNS protocol header format provided for embodiments of this application;

[0028] Figure 5 A flowchart of a data access method provided in this application embodiment Figure Two ;

[0029] Figure 6 A schematic diagram of the interaction flow of an exemplary data access method provided in an embodiment of this application;

[0030] Figure 7 A schematic diagram of the structure of a first access device provided in an embodiment of this application. Figure One ;

[0031] Figure 8 A schematic diagram of the structure of a first access device provided in an embodiment of this application. Figure Two ;

[0032] Figure 9 A schematic diagram of the structure of a second access device provided in an embodiment of this application. Figure One ;

[0033] Figure 10 A schematic diagram of the structure of a second access device provided in an embodiment of this application. Figure Two . Detailed Implementation

[0034] In order to gain a more detailed understanding of the features and technical content of the embodiments of this application, the implementation of the embodiments of this application will be described in detail below with reference to the accompanying drawings. The accompanying drawings are for reference and illustration only and are not intended to limit the embodiments of this application.

[0035] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0036] In the following description, "some embodiments" are referred to, which describe a subset of all possible embodiments, but it can be understood that "some embodiments" can be the same subset or different subsets of all possible embodiments, and can be combined with each other without conflict. It should also be noted that the terms "first, second, third" referred to in the embodiments of the present application are only used to distinguish similar objects, and do not represent a specific order of the objects. Understandably, "first, second, third" can be interchanged with a specific order or sequence as allowed, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein.

[0037] Currently, the scenario of NAT64 conversion can be seen in Figure 1 , Figure 1 BRAS1 does not support NAT64 plug-in, and a NAT64 device needs to be externally hung, and BRAS2 supports NAT64 plug-in. IPv6 client device 1 accesses IPv6 server device through BRAS1 and core router (CR) 1, and IPv6 client device 2 accesses IPv6 server device through BRAS2 and CR2; IPv6 client device 1 accesses IPv4 server device through BRAS1, NAT64S device and CR1, and IPv6 client device 2 accesses IPv4 server device through the NAT64 plug-in of BRAS2 and CR2.

[0038] The above-mentioned IPv6 client device accessing IPv4 server device needs BRAS device to support NAT64, or BRAS device externally hung NAT64 device can be realized, and then a NAT64 device needs to be externally hung for BRAS device that does not support NAT64, causing waste of network resources and waste of network energy consumption.

[0039] To solve the above problems, the embodiments of the present application provide a data access method, as shown in Figure 2 applied to a first access device, which can include:

[0040] S101, in the case that it is monitored that a client device requests an IPv6 address of a target domain name to a domain name resolution DNS server, and the DNS server does not find the AAAA record of the target domain name, an IPv6 address query request for the target domain name is sent to a second access device; so that the second access device performs A record query and NAT64 conversion operation for the target domain name.

[0041] The data access method provided by the embodiments of the present application is applicable to the scenario of IPv6 client device accessing IPv4 server device.

[0042] In this embodiment of the application, the first access device is an access device that does not support NAT64 translation, and the second access device is an access device that supports NAT64 translation.

[0043] In this embodiment of the application, the access device is a BRAS. Accordingly, the first access device is a BRAS that does not support NAT64, and the second access device is a BRAS that supports NAT64.

[0044] In this embodiment, the client device initiates a Domain Name System (DNS) query to request the AAAA record of the target domain from the DNS server. The first access device monitors the AAAA record query for the target domain. When the DNS server returns a Non-Existent Domain (NXDOMAIN) message, the first access device intercepts the message. The NXDOMAIN message indicates that there is no corresponding AAAA record for the target domain. At this time, the first access device sends an IPv6 address query request for the target domain to the second access device through the transmission tunnel between the first and second access devices.

[0045] It should be noted that the AAAA record is a DNS record used to resolve a domain name to an IPv6 address.

[0046] In this embodiment, the client device is an IPv6 client device, and the server device accessed by the client device is an IPv4 server device.

[0047] In this embodiment of the application, the target domain name is the domain name of the server device accessed by the client device, such as the IPv4 server device with the target domain name www.xxx.com.

[0048] It should be noted that a transmission tunnel is established between the first access device and the second access device, and the first access device and the second access device transmit data through this transmission tunnel.

[0049] For example, see Figure 3 The transmission tunnel between the first access device BRAS1 and the second access device BRAS2 can be a BRAS1-CR1-BRAS2 tunnel. The IPv6 terminal can access the IPv4 server device sequentially via BRAS1, the aforementioned transmission tunnel, and CR2. Conversely, the IPv6 terminal accesses the IPv6 server device sequentially via BRAS1 and CR1.

[0050] In this embodiment of the application, an extended DNS request message with the first reserved bit set to a first value is sent to the second access device to request the IPv6 address of the target domain name from the second access device.

[0051] Optionally, the first access device sends, to the second access device, the extended DNS request message with the first reserved bit being the first value through the transmission tunnel.

[0052] In the embodiment of the present application, the first reserved bit is one bit in a reserved field in the extended DNS request message; the first reserved bit being the first value indicates that the corresponding AAAA record does not exist for the corresponding domain name, and requests to generate an AAAA record based on NAT64 conversion.

[0053] In the embodiment of the present application, the extended DNS message is an extended DNS6 message.

[0054] In the embodiment of the present application, the header part of the extended DNS protocol, one bit is taken out from the original three reserved bits (reserved field) as the first reserved bit. The first reserved bit is used to identify the "N64" identifier, and when the first reserved bit is the first value, it indicates that the AAAA record does not exist for the domain name, and requests to generate an AAAA record based on NAT64 conversion.

[0055] In the embodiment of the present application, the reserved field is the Z field of the DNS protocol.

[0056] For example, refer to Figure 4 For the header format of the DNS protocol, the first reserved bit of the Z field is taken as the N64 bit.

[0057] Optionally, the first value can be 1, or other values, which can be selected according to actual conditions, and the embodiment of the present application does not make specific limitations.

[0058] Optionally, the first bit in the Z field can be taken as the first reserved bit, or the second bit in the Z field can be taken as the first reserved bit, or the last bit in the Z field can be taken as the first reserved bit; specifically, any bit in the Z field can be taken as the first reserved bit, and the embodiment of the present application does not make specific limitations.

[0059] S102, the IPv6 address information of the target domain name returned by the second access device is forwarded to the client device, so that the client device performs data plane access based on the IPv6 address information of the target domain name.

[0060] In the embodiment of the present application, the first access device receives the IPv6 address information of the target domain name returned by the second access device through the transmission tunnel, and then the first access device forwards the IPv6 address information of the target domain name to the client device.

[0061] Further, after forwarding the IPv6 address information of the target domain name returned by the second access device to the client device, the client device can perform data plane access based on the IPv6 address information of the target domain name. Specifically, the client device initiates a data plane IPv6 access process for the IPv6 address information of the target domain name, and the first access device forwards the data plane IPv6 access process initiated by the client device for the IPv6 address information of the target domain name to the second access device, so that the second access device converts the data plane IPv6 access process into a data plane IPv4 access process.

[0062] In the embodiment of the present application, the client device initiates a data plane IPv6 access process for the IPv6 address information of the target domain name, and initiates a first packet with IPv6 address information of the client device as source address information and IPv6 address information of the target domain name as destination address information. The first access device forwards the first packet to the second access device through a transmission tunnel, and the second access device performs NAT64 conversion of the source address information and the destination address information and performs a data plane IPv4 access process.

[0063] It can be understood that, in the case that the first access device not supporting NAT64 monitors IPv6 client device access to IPv4 server, the first access device needs to forward the traffic to be converted to the second access device supporting NAT64 to complete NAT64 conversion, and then send the converted traffic to the client device. The client device can subsequently realize data plane access to the IPv4 server through the first access device and the second access device in turn. Thus, the existing second access device supporting NAT64 can be used to realize NAT64 conversion in the process of IPv6 client access to IPv4 server, without the need to externally connect a NAT64 device to the first access device, which can greatly reduce the waste of network resources and network energy consumption.

[0064] Based on the above embodiment, the present application provides a data access method applied to a second access device, as shown in the figure, the method comprises the following steps of: Figure 5

[0065] S201, receiving an IPv6 address query request for a target domain name sent by a first access device.

[0066] In the embodiment of the present application, the first access device is an access device not supporting NAT64 conversion, and the second access device is an access device supporting NAT64 conversion.

[0067] In the embodiment of the present application, a transmission tunnel is established between the first access device and the second access device, and the second access device receives the IPv6 address query request for the target domain name sent by the first access device.

[0068] ​In the embodiment of the present application, the second access device receives the extended DNS request message sent by the first access device; the value of the first reserved bit in the extended DNS request message is set as the first value.

[0069] In the embodiment of the present application, the first reserved bit is one bit in the reserved field in the extended DNS request message; the first reserved bit is the first value, which indicates that the corresponding AAAA record does not exist for the corresponding domain name, and requests to generate an AAAA record based on NAT64 conversion.

[0070] In the embodiment of the present application, the second access device determines the IPv6 address of the target domain name requested by the first access device based on the value of the first reserved bit in the extended DNS request message.

[0071] S202, according to the IPv6 address query request, performing A record query and NAT64 conversion operation for the target domain name, obtaining the IPv6 address information of the target domain name.

[0072] In the embodiment of the present application, the second access device obtains the IPv4 address information of the target domain name from the DNS server; and performs NAT64 conversion on the IPv4 address information of the target domain name to generate the IPv6 address information of the target domain name.

[0073] In the embodiment of the present application, the A record is used to specify the IP address record corresponding to the domain name.

[0074] In the embodiment of the present application, the second access device configures an IPv4 address set and an IPv6 address set for NAT64 conversion.

[0075] It should be noted that the IPv4 address set is used for source address NAT64 conversion, and the IPv6 address set is used for destination address NAT64 conversion.

[0076] In the embodiment of the present application, the second access device selects an address from the configured IPv6 address set to perform NAT64 mapping, obtains the mapping entry of the IPv4 address information of the target domain name and the IPv6 address information of the target domain name, and saves the mapping entry.

[0077] S203, sending the IPv6 address information of the target domain name to the first access device.

[0078] In the embodiment of the present application, the extended DNS response message is sent to the first access device; the first reserved bit in the extended DNS response message is the first value, and the AAAA flag bit is the IPv6 address information of the target domain name.

[0079] In the embodiment of the present application, the second access device sends the IPv6 address information of the target domain name to the first access device through a transmission tunnel.

[0080] Further, after sending the IPv6 address information of the target domain name to the first access device, the second access device acquires a data plane IPv6 access process initiated by the client device for the IPv6 address information of the target domain name and forwarded by the first access device, and then converts the data plane IPv6 access process into a data plane IPv4 access process.

[0081] In the embodiments of the present application, converting the data plane IPv6 access process into the data plane IPv4 access process comprises: converting the IPv6 address information of the client device into IPv4 address information of the client device; converting the IPv6 address information of the target domain name into IPv4 address information of the target domain name; and continuing to execute the data plane IPv4 access process based on the IPv4 address information of the client device and the IPv4 address information of the target domain name.

[0082] Specifically, the second access device performs NAT64 conversion on the IPv6 address information of the client device based on the configured IPv4 address set to obtain the IPv4 address information of the client device, and determines the IPv4 address information of the target domain name based on the saved mapping entry.

[0083] It can be understood that the first access device not supporting NAT64 will forward the traffic to be converted to the second access device supporting NAT64 to complete NAT64 conversion when monitoring that the IPv6 client device accesses the IPv4 server, and then send the converted traffic to the client device, and the client device can subsequently realize data plane access to the IPv4 server through the first access device and the second access device, thereby realizing NAT64 conversion in the process of IPv6 client accessing IPv4 server by using the existing second access device supporting NAT64, without externally connecting a NAT64 device to the first access device, which can greatly reduce the waste of network resources and network energy consumption.

[0084] Based on the above embodiments, the embodiments of the present application propose a data access method, as shown in Figure 6 The method can comprise:

[0085] S1, configuring an IPv4 address set and an IPv6 address set for NAT64 conversion on a BRAS2 supporting NAT64.

[0086] S2, establishing a transmission tunnel Tunnel1 between BRAS1 and BRAS2.

[0087] S3, the IPv6 terminal initiates a DNS query message to the DNS server through BRAS1, requesting the AAAA record of www.xxx.com domain name.

[0088] It should be noted that the name in the DNS query message is www.xxx.com, and the type is AAAA.

[0089] S4, BRAS1 receives the DNS response message returned by the DNS server, which indicates that there is no AAAA record of www.xxx.com domain name.

[0090] S5, BRAS1 sends a DNS query message to BRAS2 through Tunnel1, requesting the AAAA record of www.xxx.com domain name.

[0091] It should be noted that the name in the DNS query message is www.xxx.com, the type is AAAA, and the identifier N64=1.

[0092] S6, BRAS2 requests the A record of the target domain name from the DNS server.

[0093] S7, the DNS server returns the IPv4 address 1 of the target domain name to BRAS2.

[0094] S8, BRAS2 selects an address from the configured IPv6 address set to perform NAT64 mapping, and saves the mapping entry: IPv6 address 1<->IPv4 address 1.

[0095] S9, BRAS2 sends a DNS response message to BRAS1 through Tunnel1, indicating that the AAAA record of the target domain name is IPv6 address 1, but the AAAA record is the NAT64 converted IPv6 address information.

[0096] It should be noted that the name in the DNS response message is www.xxx.com, the AAAA is IPv6 address 1, and the identifier N64=1.

[0097] S10, BRAS1 sends a DNS response message to the IPv6 terminal, indicating that the AAAA record of the domain name is IPv6 address 1.

[0098] It should be noted that the name in the DNS response message is www.xxx.com, and the AAAA is IPv6 address information.

[0099] S11, the IPv6 terminal performs IPv6 access in the data plane (the source address is the IPv6 address Src_IPv6 of the IPv6 terminal, and the destination address is IPv6 address 1), and the packet with the destination address of IPv6 address 1 is sent to BRAS2 through the tunnel Tunnel1.

[0100] S12, BRAS2 performs NAT64 operation.

[0101] It should be noted that, for the source address, the NAT64 conversion is performed according to the configured IPv4 address set: Src_IPv6-->Src_IPv4; and for the destination address, the NAT64 conversion is performed according to the previously saved mapping relationship: IPv6 address 1-->IPv4 address 1.

[0102] S13, after the NAT64 conversion, BRAS2 continues to perform IPv4 access in the data plane (the source address is Src_IPv4, and the destination address is IPv4 address 1).

[0103] An embodiment of the present application provides a first access device 1. As shown in the figure, the first access device 1 comprises: Figure 7

[0104] The first sending unit 10 is configured to, in the case that it is monitored that a client device requests an IPv6 address of a target domain name from a domain name resolution DNS server, and the DNS server does not find an AAAA record of the target domain name, send an IPv6 address query request for the target domain name to a second access device, so that the second access device performs A record query and NAT64 conversion operation for the target domain name, and forwards IPv6 address information of the target domain name returned by the second access device to the client device, so that the client device performs data plane access based on the IPv6 address information of the target domain name.

[0105] Optionally, the first sending unit 10 is further configured to send an extended DNS request packet with a first reserved bit being a first value to the second access device, so as to request the IPv6 address of the target domain name from the second access device.

[0106] Optionally, the first reserved bit is a bit in a reserved field in the extended DNS request packet, and the first reserved bit being the first value indicates that there is no corresponding AAAA record for the corresponding domain name, and an AAAA record is requested to be generated based on NAT64 conversion.

[0107] ​Optionally, the first sending unit 10 is further configured to forward the data plane IPv6 access process initiated by the client device for the IPv6 address information of the target domain name to the second access device, so that the second access device converts the data plane IPv6 access process into a data plane IPv4 access process.

[0108] Optionally, a transmission tunnel is established between the first access device and the second access device.

[0109] Optionally, the first access device is an access device that does not support NAT64 conversion, and the second access device is an access device that supports NAT64 conversion.

[0110] The first access device provided by the embodiment of the present application is configured to, in the case that the client device monitors the DNS server to request the IPv6 address of the target domain name and the DNS server does not find the AAAA record of the target domain name, send an IPv6 address query request for the target domain name to the second access device, so that the second access device performs the operations of A record query and NAT64 conversion for the target domain name, and the first access device forwards the IPv6 address information of the target domain name returned by the second access device to the client device, so that the client device performs data plane access based on the IPv6 address information of the target domain name. It can be seen that, in the case that the first access device that does not support NAT64 monitors the IPv6 client device to access the IPv4 server, the first access device forwards the traffic that needs to be converted to the second access device that supports NAT64 to complete the NAT64 conversion, and then sends the converted traffic to the client device, and the client device can subsequently realize data plane access to the IPv4 server through the first access device and the second access device. Therefore, the NAT64 conversion in the process of IPv6 client access to the IPv4 server can be realized by using the existing second access device that supports NAT64, without externally connecting a NAT64 device to the first access device, which can greatly reduce the waste of network resources and network energy consumption.

[0111] Figure 8 The first access device 1 provided by the embodiment of the present application Figure Two In actual application, based on the same disclosure concept of the above embodiment, as shown in Figure 8 The first access device 1 of the embodiment includes a first processor 11, a first memory 12 and a first communication bus 13.

[0112] The first processor 11 can be at least one of an application specific integrated circuit (ASIC), a digital signal processor (DSP), a digital signal processing device (DSPD), a programmable logic device (PLD), a field programmable gate array (FPGA), a CPU, a controller, a microcontroller, and a microprocessor. It can be understood that, for different devices, the electronic device used to implement the functions of the processor can also be other devices, and the embodiments are not limited in this regard.

[0113] In the embodiments of the present application, the first communication bus 13 is used to realize the connection and communication between the first processor 11 and the first memory 12; and the first processor 11 realizes the following data access method when executing the running program stored in the first memory 12.

[0114] In the case that the client device requests the IPv6 address of the target domain name from the domain name resolution DNS server, and the DNS server does not find the AAAA record of the target domain name, an IPv6 address query request for the target domain name is sent to the second access device; the second access device is requested to perform A record query and NAT64 conversion operation for the target domain name; and the IPv6 address information of the target domain name returned by the second access device is forwarded to the client device, so that the client device performs data plane access based on the IPv6 address information of the target domain name.

[0115] Further, the first processor 11 is further configured to send an extended DNS request message with a first reserved bit being a first value to the second access device, so as to request the IPv6 address of the target domain name from the second access device.

[0116] Further, the first reserved bit is a bit in a reserved field in the extended DNS request message; and the first reserved bit being the first value indicates that there is no corresponding AAAA record for the corresponding domain name, and requests to generate an AAAA record based on NAT64 conversion.

[0117] Further, the first processor 11 is further configured to forward a data plane IPv6 access process initiated by the client device for the IPv6 address information of the target domain name to the second access device, so that the second access device converts the data plane IPv6 access process into a data plane IPv4 access process.

[0118] Further, a transmission tunnel is established between the first access device and the second access device.

[0119] Further, the first access device is an access device that does not support NAT64 conversion, and the second access device is an access device that supports NAT64 conversion.

[0120] Based on the above embodiment, the embodiment of the present application further provides a second access device 2, as shown in the figure, the second access device 2 comprises: Figure 9

[0121] A first receiving unit 20 configured to receive an IPv6 address query request for a target domain name sent by a first access device;

[0122] A conversion unit 21 configured to perform A record query and NAT64 conversion operation for the target domain name according to the IPv6 address query request, and obtain IPv6 address information of the target domain name;

[0123] A second sending unit 22 configured to send the IPv6 address information of the target domain name to the first access device.

[0124] Optionally, the second access device further comprises an acquisition unit.

[0125] The acquisition unit is configured to acquire IPv4 address information of the target domain name from a DNS server.

[0126] The conversion unit 21 is further configured to perform NAT64 conversion on the IPv4 address information of the target domain name, and generate the IPv6 address information of the target domain name.

[0127] Optionally, the first receiving unit 20 is further configured to receive an extended DNS request message sent by the first access device; and a value of a first reserved bit in the extended DNS request message is set to a first value.

[0128] Optionally, the first reserved bit is a bit in a reserved field in the extended DNS request message; and the first reserved bit being the first value indicates that there is no corresponding AAAA record for the corresponding domain name, and requests to generate an AAAA record based on NAT64 conversion.

[0129] ​Optionally, the second sending unit 22 is further configured to send an extended DNS response message to the first access device; a first reserved bit in the extended DNS response message is a first value, and an AAAA flag bit is IPv6 address information of the target domain name.

[0130] Optionally, the obtaining unit is further configured to obtain a data plane IPv6 access process of the client device for the IPv6 address information of the target domain name, which is forwarded by the first access device.

[0131] The conversion unit 21 is further configured to convert the data plane IPv6 access process into a data plane IPv4 access process.

[0132] Optionally, the second access device further comprises an access unit.

[0133] The conversion unit 21 is further configured to convert the IPv6 address information of the client device into IPv4 address information of the client device, and convert the IPv6 address information of the target domain name into IPv4 address information of the target domain name.

[0134] The access unit is configured to continue to execute the data plane IPv4 access process based on the IPv4 address information of the client device and the IPv4 address information of the target domain name.

[0135] Optionally, the second access device is configured with an IPv4 address set and an IPv6 address set for NAT64 conversion.

[0136] Optionally, the first access device is an access device that does not support NAT64 conversion, and the second access device is an access device that supports NAT64 conversion.

[0137] The second access device provided in the embodiment of the present application receives an IPv6 address query request for a target domain name sent by a first access device; performs A record query and NAT64 conversion operation for the target domain name according to the IPv6 address query request, and obtains IPv6 address information of the target domain name; and sends the IPv6 address information of the target domain name to the first access device. As can be seen, the second access device provided in the embodiment, when the first access device not supporting NAT64 monitors that an IPv6 client device accesses an IPv4 server, forwards the traffic that needs to be converted to the second access device supporting NAT64 to complete NAT64 conversion, and then sends the converted traffic to the client device, and the client device can subsequently realize data plane access to the IPv4 server through the first access device and the second access device in turn, thereby, the existing second access device supporting NAT64 can be used to realize NAT64 conversion in the process of IPv6 client accessing IPv4 server, without externally connecting a NAT64 device to the first access device, which can greatly reduce the waste of network resources and network energy consumption.

[0138] Figure 10 The component structure of the second access device 2 provided in the embodiment of the present application Figure Two In actual application, based on the same disclosure concept of the above embodiment, as shown in Figure 10 The second access device 2 of the embodiment includes a second processor 23, a second memory 24 and a second communication bus 25.

[0139] The second processor 23 can be at least one of ASIC, DSP, DSPD, PLD, FPGA, CPU, controller, microcontroller, microprocessor. It can be understood that for different devices, the electronic device used to realize the function of the processor can also be other, and the embodiment does not make specific limitation.

[0140] In the embodiment of the present application, the second communication bus 25 is used to realize the connection and communication between the second processor 23 and the second memory 24; and the second processor 23 realizes the following data access method when executing the running program stored in the second memory 24.

[0141] The second access device provided in the embodiment of the present application receives an IPv6 address query request for a target domain name sent by a first access device; performs A record query and NAT64 conversion operation for the target domain name according to the IPv6 address query request, and obtains IPv6 address information of the target domain name; and sends the IPv6 address information of the target domain name to the first access device. As can be seen, the second access device provided in the embodiment, when the first access device not supporting NAT64 monitors that an IPv6 client device accesses an IPv4 server, forwards the traffic that needs to be converted to the second access device supporting NAT64 to complete NAT64 conversion, and then sends the converted traffic to the client device, and the client device can subsequently realize data plane access to the IPv4 server through the first access device and the second access device in turn, thereby, the existing second access device supporting NAT64 can be used to realize NAT64 conversion in the process of IPv6 client accessing IPv4 server, without externally connecting a NAT64 device to the first access device, which can greatly reduce the waste of network resources and network energy consumption.

[0142] Further, the second processor 23 is further configured to obtain the target domain name IPv4 address information from a DNS server, and perform NAT64 conversion on the target domain name IPv4 address information to generate the target domain name IPv6 address information.

[0143] Further, the second processor 23 is further configured to receive an extended DNS request message sent by the first access device, and set a value of a first reserved bit in the extended DNS request message to a first value.

[0144] Further, the first reserved bit is a bit in a reserved field in the extended DNS request message, and the first reserved bit being the first value indicates that there is no corresponding AAAA record corresponding to the corresponding domain name, and an AAAA record is requested to be generated based on NAT64 conversion.

[0145] Further, the second processor 23 is further configured to send an extended DNS response message to the first access device, and set a first reserved bit in the extended DNS response message to the first value and set an AAAA flag bit to the target domain name IPv6 address information.

[0146] Further, the second processor 23 is further configured to obtain a data plane IPv6 access process initiated by a client device for the target domain name IPv6 address information and forwarded by the first access device, and convert the data plane IPv6 access process into a data plane IPv4 access process.

[0147] Further, the second processor 23 is further configured to convert the IPv6 address information of the client device into IPv4 address information of the client device, convert the IPv6 address information of the target domain name into IPv4 address information of the target domain name, and continue to perform the data plane IPv4 access process based on the IPv4 address information of the client device and the IPv4 address information of the target domain name.

[0148] Further, the second access device is configured with an IPv4 address set and an IPv6 address set for NAT64 conversion.

[0149] Further, the first access device is an access device that does not support NAT64 conversion, and the second access device is an access device that supports NAT64 conversion.

[0150] The embodiment of the present application provides a storage medium, which stores a computer program, the computer readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors, and the computer program implements the data access method.

[0151] Based on the above embodiments, the embodiments of the present application provide a computer program product, comprising a computer program, the computer program can be executed by one or more processors, and the computer program implements the data access method as described above.

[0152] It should be noted that, in this document, the terms "comprising", "including", or any other variant thereof are intended to cover a non-exclusive inclusion, so that a process, method, article, or apparatus that comprises a list of elements does not only include those elements, but can also include other elements not expressly listed, or other elements inherent in such process, method, article, or apparatus. Without more limitations, the element defined by the statement "comprising a" does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0153] From the above description of the embodiments, those skilled in the art can clearly understand that the above-mentioned method of the embodiments can be realized by means of software and the necessary general hardware platform, of course, it can also be realized by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present disclosure or the part that contributes to the related art can be embodied in the form of a software product, which is stored in a storage medium (such as a read-only memory (ROM) / random access memory (RAM), a magnetic disk, an optical disk), and includes a number of instructions to make an image display device (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the method described in each embodiment of the present disclosure.

[0154] The above description is only a preferred embodiment of the present application, and is not intended to limit the protection scope of the present application.

Claims

1. A data access method, characterized by, The method is applied to a first access device which is an access device not supporting NAT64 conversion, and comprises the following steps: In the case that it is monitored that a client device requests an IPv6 address of a target domain name from a domain name system (DNS) server, and the DNS server does not find an AAAA record of the target domain name, an IPv6 address query request for the target domain name is sent to a second access device, so that the second access device performs an A record query and a NAT64 conversion operation for the target domain name; IPv6 address information of the target domain name returned by the second access device is forwarded to the client device, so that the client device performs data plane access based on the IPv6 address information of the target domain name; the second access device is an access device supporting NAT64 conversion; The IPv6 address query request for the target domain name sent to the second access device comprises the following steps: An extended DNS request message with a first reserved bit being a first value is sent to the second access device, so that the second access device is requested to generate an AAAA record for the target domain name based on NAT64 conversion; The first reserved bit is a bit in a reserved field in the extended DNS request message; and the first reserved bit being the first value indicates that there is no corresponding AAAA record for the corresponding domain name.

2. The method of claim 1, wherein, After the IPv6 address information of the target domain name returned by the second access device is forwarded to the client device, the method further comprises the following steps: A data plane IPv6 access process initiated by the client device for the IPv6 address information of the target domain name is forwarded to the second access device, so that the second access device converts the data plane IPv6 access process into a data plane IPv4 access process.

3. The method of claim 1, wherein, A transmission tunnel is established between the first access device and the second access device.

4. A data access method, characterized by, The method is applied to a second access device which is an access device supporting NAT64 conversion, and comprises the following steps: An IPv6 address query request for a target domain name sent by a first access device is received; the first access device is an access device not supporting NAT64 conversion; An A record query and a NAT64 conversion operation for the target domain name are performed according to the IPv6 address query request, so that IPv6 address information of the target domain name is obtained; The IPv6 address information of the target domain name is sent to the first access device; The IPv6 address query request for the target domain name sent by the first access device is received, and comprises the following steps: An extended DNS request message sent by the first access device is received; a value of a first reserved bit in the extended DNS request message is set to a first value; The first reserved bit is a bit in a reserved field in the extended DNS request message; and the first reserved bit being the first value indicates that there is no corresponding AAAA record for the corresponding domain name.

5. The method of claim 4, wherein, The operation of performing A record query and NAT64 conversion for the target domain name according to the IPv6 address query request comprises: Obtaining IPv4 address information of the target domain name from a DNS server; Performing NAT64 conversion on the IPv4 address information of the target domain name to generate IPv6 address information of the target domain name.

6. The method of claim 4, wherein, The operation of sending the IPv6 address information of the target domain name to the first access device comprises: Sending an extended DNS response message to the first access device; the first reserved bit in the extended DNS response message is a first value, and an AAAA flag bit is the IPv6 address information of the target domain name.

7. The method of claim 4, wherein, After the operation of sending the IPv6 address information of the target domain name to the first access device, the method further comprises: Obtaining a data plane IPv6 access process initiated by a client device for the IPv6 address information of the target domain name and forwarded by the first access device; Converting the data plane IPv6 access process into a data plane IPv4 access process.

8. The method of claim 7, wherein, The operation of converting the data plane IPv6 access process into the data plane IPv4 access process comprises: Converting IPv6 address information of the client device into IPv4 address information of the client device; Converting IPv6 address information of the target domain name into IPv4 address information of the target domain name; Continuing to perform the data plane IPv4 access process based on the IPv4 address information of the client device and the IPv4 address information of the target domain name.

9. The method of claim 4, wherein, The second access device is configured with a set of IPv4 addresses and a set of IPv6 addresses for NAT64 conversion.

10. A first access device, comprising: The first access device is an access device that does not support NAT64 conversion, and the first access device comprises: A first sending unit configured to, in a case where it is monitored that a client device requests IPv6 address of a target domain name from a domain name resolution DNS server and the DNS server does not find AAAA record of the target domain name, send an IPv6 address query request for the target domain name to a second access device; the second access device is configured to perform A record query and NAT64 conversion for the target domain name; and IPv6 address information of the target domain name returned by the second access device is forwarded to the client device, so that the client device performs data plane access based on the IPv6 address information of the target domain name; the second access device is an access device that supports NAT64 conversion; The first sending unit is further configured to send an extended DNS request message with a first reserved bit being a first value to the second access device; and request IPv6 address of the target domain name from the second access device; The first reserved bit is a bit in a reserved field in the extended DNS request message; and the first reserved bit being the first value indicates that there is no corresponding AAAA record for the corresponding domain name, and requests to generate an AAAA record based on NAT64 conversion.

11. A second access device, comprising: The second access device is an access device supporting NAT64 conversion, and the second access device comprises: a first receiving unit configured to receive an IPv6 address query request for a target domain name sent by a first access device; the first access device is an access device not supporting NAT64 conversion; a conversion unit configured to perform A record query and NAT64 conversion operation for the target domain name according to the IPv6 address query request, and obtain IPv6 address information of the target domain name; a second sending unit configured to send the IPv6 address information of the target domain name to the first access device; the first receiving unit is further configured to receive an extended DNS request message sent by the first access device; a value of a first reserved bit in the extended DNS request message is set as a first value; the first reserved bit is a bit in a reserved field in the extended DNS request message; the first reserved bit being the first value indicates that there is no corresponding AAAA record corresponding to the corresponding domain name, and requests to generate an AAAA record based on NAT64 conversion.

12. A first access device, comprising: The first access device comprises a first processor and a first memory; the first processor implements the method of any one of claims 1-3 when executing a running program stored in the first memory.

13. A second access device, comprising: The second access device comprises a second processor and a second memory; the second processor implements the method of any one of claims 4-9 when executing a running program stored in the second memory.

14. A storage medium having stored thereon a computer program, characterized in that The computer program is executed by the first processor to implement the method of any one of claims 1-3, or executed by the second processor to implement the method of any one of claims 4-9.

15. A computer program product comprising a computer program, characterized in that, The computer program is executed by the first processor to implement the method of any one of claims 1-3, or executed by the second processor to implement the method of any one of claims 4-9.

Images