Data access method and access device, storage medium and computer program product

By delegating NAT64 conversion to supporting devices, the method addresses resource and energy waste by enabling IPv6 clients to access IPv4 servers through NAT64-supported devices, reducing the need for additional hardware on non-supporting BRAS devices.

CN119071271AActive Publication Date: 2024-12-03CHINA MOBILE COMM LTD RES INST +1
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
CN202410911029.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-08
Publication Date
2024-12-03
Estimated Expiration
2044-07-08

AI Technical Summary

Technical Problem

The installation of NAT64 devices on BRAS devices that do not support NAT64 plug-in boards results in waste of network resources and energy consumption due to the increasing IPv6 traffic requiring NAT64 conversion.

Method used

A data access method where a first access device, lacking NAT64 support, sends an IPv6 address query request to a second access device that supports NAT64, enabling the second device to perform NAT64 conversion, and forwards the converted IPv6 address information to the client device for accessing IPv4 servers.

Benefits of technology

This method reduces network resource and energy waste by utilizing existing NAT64-supported devices for conversion, eliminating the need for additional NAT64 devices on non-supporting BRAS devices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119071271A_ABST
    Figure CN119071271A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides a data access method and access equipment, a storage medium and a computer program product, and the method comprises the steps: first access equipment sends an IPv6 address of a target domain name to a domain name resolution DNS server when monitoring that client equipment requests the IPv6 address of the target domain name from the DNS server, and the DNS server does not find an AAAA record of the target domain name; sending an IPv6 address query request for the target domain name to a second access device; the second access equipment is used for executing the operations of A record query and NAT64 conversion aiming at 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.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

[0002] This year, with the continuous evolution of the new Internet Protocol Version 6 (IPv6) technology, the global IPv6 traffic has increased significantly. With the continuous increase of IPv6 traffic in the existing network, from terminals to content, from the entire network end to end, most devices already support IPv6. In order to save Internet Protocol Version 4 (IPv4) address resources, IPv6 single stack addresses are allocated to terminals. 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 implemented by the NAT64 plug-in board of the BRAS device.

[0003] However, some BRAS devices do not support NAT64 plug-in boards, so an independent NAT64 device needs to be installed on the BRAS device to implement NAT64 conversion. However, IPv6 traffic has become the mainstream, and the traffic that needs NAT64 conversion is not large. Installing a NAT64 device on each BRAS device that does not support NAT64 plug-in boards for this small portion of conversion traffic will cause a waste of network resources and network energy consumption. Summary of the invention

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

[0005] The technical solution of this application is implemented as follows:

[0006] In a first aspect, the present application proposes a data access method, which is applied to a first access device, and the method includes:

[0007] When it is monitored that the client device requests the IPv6 address of the target domain name from the domain name resolution DNS server, and the DNS server fails to 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; so that the second access device performs the A record query and NAT64 conversion operations for the target domain name;

[0008] 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 can perform data plane access based on the IPv6 address information of the target domain name.

[0009] In a second aspect, the present application proposes a data access method, which is applied to a second access device, and the method includes:

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

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

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

[0013] In a third aspect, the present application proposes a first access device, the first access device comprising:

[0014] The first sending unit is used to send an IPv6 address query request for the target domain name to a second access device when it is monitored that the client device requests the IPv6 address of the target domain name from the domain name resolution DNS server and the DNS server fails to find the AAAA record of the target domain name; so that the second access device can perform A record query and NAT64 conversion operations for the target domain name; and forward the IPv6 address information of the target domain name returned by the second access device to the client device, so that the client device can perform data plane access based on the IPv6 address information of the target domain name.

[0015] In a fourth aspect, the present application proposes a second access device, where the second access device includes:

[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 an A record query and NAT64 conversion operation for the target domain name according to the IPv6 address query request, to obtain the IPv6 address information of the target domain name;

[0018] The second sending unit is used to send the IPv6 address information of the target domain name to the first access device.

[0019] In a fifth aspect, the present application proposes a first access device, which includes: a first processor and a first memory; when the first processor executes a running program stored in the first memory, the above-mentioned data access method applied to the first access device is implemented.

[0020] In a sixth aspect, the present application proposes a second access device, which includes: a second processor and a second memory; when the second processor executes a running program stored in the second memory, the above-mentioned data access method applied to the second access device is implemented.

[0021] In the seventh aspect, the present application proposes a storage medium having a computer program stored thereon, which, when executed by a first processor, implements the above-mentioned data access method applied to a first access device, or, when executed by a second processor, implements the above-mentioned data access method applied to a second access device.

[0022] In an eighth aspect, the present application proposes a computer program product, comprising a computer program, which implements the above-mentioned data access method applied to a first access device when executed by a first processor, or implements the above-mentioned data access method applied to a second access device when executed by a second processor.

[0023] The present application provides a data access method and access device, storage medium, and computer program product, the method comprising: when a 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 fails to find an AAAA record of the target domain name, the first access device sends an IPv6 address query request for a target domain name to a second access device; so that the second access device performs an A record query and NAT64 conversion operation for the target domain name; 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. By adopting the above 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 that does not support NAT64 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. The client device can subsequently access the data plane of the IPv4 server via the first access device and the second access device in sequence. Therefore, the existing second access device that supports NAT64 can be used to implement NAT64 conversion in the process of IPv6 client accessing the IPv4 server, without the need to hang a NAT64 device on the first access device, which can greatly reduce the waste of network resources and network energy consumption. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0025] Figure 2 A data access method process provided in the embodiment of the present application Figure 1 ;

[0026] Figure 3 A schematic diagram of an exemplary transmission tunnel provided in an embodiment of the present application;

[0027] Figure 4 A schematic diagram of an exemplary DNS protocol header format provided in an embodiment of the present application;

[0028] Figure 5 A data access method process provided in the embodiment of the present application Figure 2 ;

[0029] Figure 6 A schematic diagram of an interactive process of an exemplary data access method provided in an embodiment of the present application;

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

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

[0032] Fig. 9 A schematic diagram of a second access device provided in an embodiment of the present application Figure 1 ;

[0033] Fig.10 A schematic diagram of a second access device provided in an embodiment of the present application Figure 2 . DETAILED DESCRIPTION

[0034] In order to enable a more detailed understanding of the features and technical contents of the embodiments of the present application, the implementation of the embodiments of the present application is described in detail below in conjunction with the accompanying drawings. The attached drawings are for reference only and are not used to limit the embodiments of the present application.

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

[0036] In the following description, reference is made to "some embodiments", which describe a subset of all possible embodiments, but it is understood that "some embodiments" may be the same subset or different subsets of all possible embodiments, and may be combined with each other without conflict. It should also be noted that the terms "first\second\third" involved in the embodiments of the present application are only used to distinguish similar objects and do not represent a specific ordering of the objects. It is understandable that "first\second\third" may be interchanged in a specific order or sequence where permitted, 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 NAT64 conversion scenarios can be found in Figure 1 , Figure 1 BRAS1 in the example does not support NAT64 plug-in board, and the BRAS1 needs to be equipped with an external NAT64 device, while BRAS2 supports NAT64 plug-in board. IPv6 client device 1 accesses the IPv6 server device via BRAS1 and core router (CR) 1, and IPv6 client device 2 accesses the IPv6 server device via BRAS2 and CR2; IPv6 client device 1 accesses the IPv4 server device via BRAS1, NAT64S device and CR1, and IPv6 client device 2 accesses the IPv4 server device via BRAS2's NAT64 plug-in board and CR2.

[0038] For the above-mentioned IPv6 client device to access the IPv4 server device, the BRAS device must support NAT64, or the BRAS device must have an external NAT64 device. Furthermore, a NAT64 device must be externally installed for each BRAS device that does not support NAT64, resulting in a waste of network resources and network energy consumption.

[0039] To solve the above problems, the present application provides a data access method, such as Figure 2 As shown, applied to a first access device, the method may include:

[0040] S101. When 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 fails to 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 can perform an A record query and NAT64 conversion operation for the target domain name.

[0041] A data access method provided in an embodiment of the present application is applicable to a scenario in which an IPv6 client device accesses an IPv4 server device.

[0042] In the embodiment of the present application, 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.

[0043] In the embodiment of the present application, the access device is a BRAS, and 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 an embodiment of the present application, a client device initiates a Domain Name System (DNS) query and requests an AAAA record of a target domain name from a DNS server. A first access device monitors the query of the AAAA record of the target domain name, and when the DNS server returns a Non-Existent Domain (NXDOMAIN) message, the message is intercepted. The NXDOMAIN message indicates that the target domain name does not have a corresponding AAAA record. At this time, the first access device sends an IPv6 address query request for the target domain name to the second access device through a transmission tunnel between the first access device and the second access device.

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

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

[0047] In an embodiment of the present application, the target domain name is the domain name of the server device accessed by the client device, such as accessing an IPv4 server device with a target domain name of 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 the transmission tunnel.

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

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

[0051] Optionally, the first access device sends an extended DNS request message in which the first reserved bit is a first value to the second access device through the transmission tunnel.

[0052] In an embodiment of the present application, the first reserved bit is a bit in a reserved field in the extended DNS request message; if the first reserved bit is the first value, it indicates that there is no corresponding AAAA record for the corresponding domain name, and a request is made to generate an AAAA record based on NAT64 conversion.

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

[0054] In the embodiment of the present application, the header of the DNS protocol is extended, and one of the original three reserved bits (reserved fields) is taken out as the first reserved bit. The first reserved bit is used to identify the "N64" identifier. When the first reserved position is the first value, it indicates that there is no corresponding AAAA record for the domain name, and a request is made to generate an AAAA record based on NAT64 conversion.

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

[0056] For example, see Figure 4 , which is the header format of the DNS protocol, and the first reserved bit of the Z field is used as the N64 bit.

[0057] Optionally, the first value may be 1 or other values, which may be selected based on actual conditions and are not specifically limited in the embodiments of the present application.

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

[0059] S102: Forward the IPv6 address information of the target domain name returned by the second access device to the client device, so that the client device can perform data plane access based on the IPv6 address information of the target domain name.

[0060] In an 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 a transmission tunnel, and then the first access device forwards the IPv6 address information of the target domain name to the client device.

[0061] Furthermore, 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 an embodiment of the present application, a client device initiates a data plane IPv6 access process for the IPv6 address information of a target domain name, initiates a first message for the client device, the source address information of which is the IPv6 address information of the client device and the destination address information of which is the IPv6 address information of the target domain name, the first access device forwards the first message to the second access device through a transmission tunnel, 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, when the first access device that does not support NAT64 monitors that an IPv6 client device accesses an IPv4 server, the first access device that does not support NAT64 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. The client device can subsequently access the data plane of the IPv4 server via the first access device and the second access device in sequence. Therefore, the existing second access device that supports NAT64 can be used to implement NAT64 conversion in the process of IPv6 client accessing the IPv4 server, without the need to hang a NAT64 device on the first access device, which can greatly reduce the waste of network resources and network energy consumption.

[0064] Based on the above embodiments, the present application embodiment proposes a data access method, which is applied to a second access device, such as Figure 5 As shown, the method includes:

[0065] S201. Receive 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 that does not support NAT64 conversion, and the second access device is an access device that supports NAT64 conversion.

[0067] In an 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 an IPv6 address query request for a target domain name sent by the first access device.

[0068] In an embodiment of the present application, the second access device receives an 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 to the first value.

[0069] In an embodiment of the present application, the first reserved bit is a bit in a reserved field in the extended DNS request message; if the first reserved bit is the first value, it indicates that there is no corresponding AAAA record for the corresponding domain name, and a request is made to generate an AAAA record based on NAT64 conversion.

[0070] In an embodiment of the present application, the second access device determines, based on the value of the first reserved bit in the extended DNS request message, that the first access device requests to query the IPv6 address for the target domain name.

[0071] S202: According to the IPv6 address query request, perform A record query and NAT64 conversion operations for the target domain name to obtain IPv6 address information of the target domain name.

[0072] In an embodiment of the present application, the second access device obtains the IPv4 address information of the target domain name from the DNS server; 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 an embodiment of the present application, the second access device is configured with 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 translation, and the IPv6 address set is used for destination address NAT64 translation.

[0076] In an embodiment of the present application, the second access device selects an address from the configured IPv6 address set to perform NAT64 mapping, obtains a mapping entry between 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: Send the IPv6 address information of the target domain name to the first access device.

[0078] In an embodiment of the present application, an 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 an 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] Furthermore, after sending the IPv6 address information of the target domain name to the first access device, the second access device obtains the data plane IPv6 access process for the IPv6 address information of the target domain name initiated by the client device and forwarded by the first access device; thereafter, the data plane IPv6 access process is converted into a data plane IPv4 access process.

[0081] In an embodiment of the present application, the data plane IPv6 access process is converted into a data plane IPv4 access process, including: converting the IPv6 address information of the client device into the IPv4 address information of the client device; converting the IPv6 address information of the target domain name into the 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; the second access device determines the corresponding IPv4 address information of the target domain name based on the saved mapping entry for the IPv6 address information of the target domain name.

[0083] It can be understood that, when the first access device that does not support NAT64 monitors that an IPv6 client device accesses an IPv4 server, the first access device that does not support NAT64 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. The client device can subsequently access the data plane of the IPv4 server via the first access device and the second access device in sequence. Therefore, the existing second access device that supports NAT64 can be used to implement NAT64 conversion in the process of IPv6 client accessing the IPv4 server, without the need to hang a NAT64 device on the first access device, which can greatly reduce the waste of network resources and network energy consumption.

[0084] Based on the above embodiments, the present application embodiment proposes a data access method, such as Figure 6 As shown, the method may include:

[0085] S1. Configure an IPv4 address set and an IPv6 address set for NAT64 translation on BRAS2 that supports NAT64.

[0086] S2. Establish 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 the 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 a DNS response message returned by the DNS server, which indicates that the domain name www.xxx.com has no AAAA record.

[0090] S5. BRAS1 sends a DNS query message to BRAS2 through Tunnel1, requesting the AAAA record of the 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, informing that the AAAA record of the target domain name is IPv6 address 1, but the AAAA record is the IPv6 address information converted by NAT64.

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

[0097] S10. BRAS1 sends a DNS response message to the IPv6 terminal, informing 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 AAAA is: IPv6 address information.

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

[0100] S12. BRAS2 performs NAT64 operations.

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

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

[0103] This embodiment of the application provides a first access device 1. Figure 7 As shown, the first access device 1 includes:

[0104] The first sending unit 10 is used to send an IPv6 address query request for the target domain name to the second access device when it is monitored that the client device requests the IPv6 address of the target domain name from the domain name resolution DNS server and the DNS server fails to find the AAAA record of the target domain name; so that the second access device can perform A record query and NAT64 conversion operations for the target domain name; and forward the IPv6 address information of the target domain name returned by the second access device to the client device, so that the client device can perform data plane access based on the IPv6 address information of the target domain name.

[0105] Optionally, the first sending unit 10 is further used to send an extended DNS request message with a first reserved bit as 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 message; if the first reserved bit is a first value, it indicates that there is no corresponding AAAA record for the corresponding domain name, and a request is made to generate an AAAA record based on NAT64 conversion.

[0107] Optionally, the first sending unit 10 is also used 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 can convert 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] An embodiment of the present application provides a first access device. When monitoring that a client device requests an IPv6 address of a target domain name from a domain name resolution DNS server and the DNS server fails to 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; so that the second access device can perform A record query and NAT64 conversion operations for the target domain name; 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 can perform data plane access based on the IPv6 address information of the target domain name. It can be seen that the first access device proposed in this embodiment, which does not support NAT64, forwards the traffic that needs to be converted to the second access device that supports NAT64 to complete the NAT64 conversion when monitoring the IPv6 client device accessing the IPv4 server, and then sends the converted traffic to the client device. The client device can subsequently access the data plane of the IPv4 server through the first access device and the second access device in sequence. Therefore, the existing second access device that supports NAT64 can be used to implement NAT64 conversion in the process of IPv6 client accessing the IPv4 server, without the need to hang a NAT64 device on the first access device, which can greatly reduce the waste of network resources and network energy consumption.

[0111] Figure 8 A schematic diagram of the composition structure of a first access device 1 provided in an embodiment of the present application Figure 2 In practical applications, based on the same disclosure concept of the above embodiments, Figure 8 As shown, the first access device 1 of this embodiment includes: a first processor 11, a first memory 12 and a first communication bus 13.

[0112] The first processor 11 may 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 is understandable that for different devices, the electronic device used to implement the above-mentioned processor function may also be other, and this embodiment does not specifically limit it.

[0113] In the embodiment 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; when the first processor 11 executes the running program stored in the first memory 12, the following data access method is implemented:

[0114] When 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 fails to 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 A record query and NAT64 conversion operations 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] Furthermore, 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] Furthermore, the first reserved bit is a bit in a reserved field in the extended DNS request message; if the first reserved bit is a first value, it indicates that there is no corresponding AAAA record for the corresponding domain name, and a request is made to generate an AAAA record based on NAT64 conversion.

[0117] Furthermore, the first processor 11 is also used 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.

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

[0119] Furthermore, 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 present application embodiment further proposes a second access device 2, such as Fig. 9 As shown, the second access device 2 includes:

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

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

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

[0124] Optionally, the second access device further includes: an acquisition unit;

[0125] The acquiring unit is used to acquire the IPv4 address information of the target domain name from the DNS server;

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

[0127] Optionally, the first receiving unit 20 is further used to receive an 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 to a first value.

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

[0129] Optionally, the second sending unit 22 is further used to send 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 the AAAA flag bit is the IPv6 address information of the target domain name.

[0130] Optionally, the acquisition unit is further used to acquire a data plane IPv6 access process for the IPv6 address information of the target domain name, which is forwarded by the first access device and initiated by the client device;

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

[0132] Optionally, the second access device further includes: an access unit;

[0133] The conversion unit 21 is further used to convert the IPv6 address information of the client device into the IPv4 address information of the client device; convert the IPv6 address information of the target domain name into the IPv4 address information of the target domain name;

[0134] The access unit is used 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 embodiment of the present application provides a second access device, which receives an IPv6 address query request for a target domain name sent by a first access device; performs an A record query and NAT64 conversion operation for the target domain name according to the IPv6 address query request to obtain the IPv6 address information of the target domain name; and sends the IPv6 address information of the target domain name to the first access device. It can be seen that the second access device proposed in this embodiment, when the first access device that does not support NAT64 monitors that an IPv6 client device accesses an IPv4 server, forwards the traffic that needs to be converted to a second access device that supports NAT64 to complete the NAT64 conversion, and then sends the converted traffic to the client device. The client device can subsequently access the data plane of the IPv4 server through the first access device and the second access device in sequence. Therefore, the existing second access device that supports NAT64 can be used to implement NAT64 conversion in the process of an IPv6 client accessing an IPv4 server, without the need to hang a NAT64 device on the first access device, which can greatly reduce the waste of network resources and network energy consumption.

[0138] Fig.10 A schematic diagram of the structure of a second access device 2 provided in an embodiment of the present application Figure 2 In practical applications, based on the same disclosure concept of the above embodiments, Fig.10 As shown, the second access device 2 of this embodiment includes: a second processor 23 , a second memory 24 and a second communication bus 25 .

[0139] The second processor 23 may be at least one of ASIC, DSP, DSPD, PLD, FPGA, CPU, controller, microcontroller, and microprocessor. It is understandable that for different devices, the electronic device used to implement the processor function may also be other, which is not specifically limited in this embodiment.

[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; when the second processor 23 executes the running program stored in the second memory 24, the following data access method is implemented:

[0141] Receive an IPv6 address query request for a target domain name sent by a first access device; based on the IPv6 address query request, perform A record query and NAT64 conversion operations on the target domain name to obtain the IPv6 address information of the target domain name; send the IPv6 address information of the target domain name to the first access device.

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

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

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

[0145] Furthermore, the second processor 23 is also used to send 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 the AAAA flag bit is the IPv6 address information of the target domain name.

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

[0147] Furthermore, the above-mentioned second processor 23 is also used to convert the IPv6 address information of the client device into the IPv4 address information of the client device; convert the IPv6 address information of the target domain name into the IPv4 address information of the target domain name; and 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.

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

[0149] Furthermore, 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] An embodiment of the present application provides a storage medium having a computer program stored thereon. The computer-readable storage medium stores one or more programs. The one or more programs can be executed by one or more processors. The computer program implements the data access method as described above.

[0151] Based on the above embodiments, an embodiment of the present application provides a computer program product, including a computer program, which 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 article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0153] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present disclosure, or the part that contributes to the relevant technology, 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 disk, or an optical disk), including a number of instructions for enabling an image display device (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods 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 in that: Applied to a first access device, the method includes: When it is monitored that the client device requests the IPv6 address of the target domain name from the domain name system DNS server, and the DNS server fails to 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; so that the second access device performs the A record query and NAT64 conversion operations for the target domain name; 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 can perform data plane access based on the IPv6 address information of the target domain name.

2. The method according to claim 1, characterized in that The sending an IPv6 address query request for the target domain name to the second access device includes: Send an extended DNS request message with a first reserved bit as a first value to the second access device to request the IPv6 address of the target domain name from the second access device.

3. The method according to claim 2, characterized in that The first reserved bit is a bit in the reserved field in the extended DNS request message; if the first reserved bit is a first value, it indicates that there is no corresponding AAAA record for the corresponding domain name, and a request is made to generate an AAAA record based on NAT64 conversion.

4. The method according to claim 1, characterized in that: After forwarding the IPv6 address information of the target domain name returned by the second access device to the client device, the method further includes: The 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.

5. The method according to claim 1, characterized in that A transmission tunnel is established between the first access device and the second access device.

6. The method according to claim 1, characterized in that 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.

7. A data access method, characterized in that: Applied to a second access device, the method includes: Receiving an IPv6 address query request for a target domain name sent by a first access device; According to the IPv6 address query request, perform an A record query and NAT64 conversion operation for the target domain name to obtain the IPv6 address information of the target domain name; Send the IPv6 address information of the target domain name to the first access device.

8. The method according to claim 7, characterized in that The step of performing an A record query and NAT64 conversion operation on the target domain name according to the IPv6 address query request to obtain the IPv6 address information of the target domain name includes: Obtain the IPv4 address information of the target domain name from the DNS server; Perform NAT64 conversion on the IPv4 address information of the target domain name to generate the IPv6 address information of the target domain name.

9. The method according to claim 7, characterized in that: The receiving an IPv6 address query request for a target domain name sent by a first access device includes: 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.

10. The method according to claim 9, characterized in that The first reserved bit is a bit in the reserved field in the extended DNS request message; if the first reserved bit is a first value, it indicates that there is no corresponding AAAA record for the corresponding domain name, and a request is made to generate an AAAA record based on NAT64 conversion.

11. The method according to claim 7, characterized in that The sending the IPv6 address information of the target domain name to the first access device includes: An extended DNS response message is sent to the first access device; the first reserved bit in the extended DNS response message is a first value, and the AAAA flag bit is the IPv6 address information of the target domain name.

12. The method according to claim 7, characterized in that After sending the IPv6 address information of the target domain name to the first access device, the method further includes: Acquire a data plane IPv6 access process for the IPv6 address information of the target domain name initiated by the client device and forwarded by the first access device; The data plane IPv6 access process is converted into a data plane IPv4 access process.

13. The method according to claim 12, characterized in that The converting of the data plane IPv6 access process into the data plane IPv4 access process comprises: Converting the IPv6 address information of the client device into the IPv4 address information of the client device; Convert the IPv6 address information of the target domain name into the IPv4 address information of the target domain name; The data plane IPv4 access process is continued based on the IPv4 address information of the client device and the IPv4 address information of the target domain name.

14. The method according to claim 7, characterized in that The second access device is configured with an IPv4 address set and an IPv6 address set for NAT64 conversion.

15. The method according to claim 7, characterized in that 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.

16. A first access device, characterized in that: The first access device includes: The first sending unit is used to send an IPv6 address query request for the target domain name to a second access device when it is monitored that the client device requests the IPv6 address of the target domain name from the domain name resolution DNS server and the DNS server fails to find the AAAA record of the target domain name; so that the second access device can perform A record query and NAT64 conversion operations for the target domain name; and forward the IPv6 address information of the target domain name returned by the second access device to the client device, so that the client device can perform data plane access based on the IPv6 address information of the target domain name.

17. A second access device, characterized in that: The second access device includes: A first receiving unit, configured to receive an IPv6 address query request for a target domain name sent by a first access device; A conversion unit, configured to perform an A record query and NAT64 conversion operation for the target domain name according to the IPv6 address query request, to obtain the IPv6 address information of the target domain name; The second sending unit is used to send the IPv6 address information of the target domain name to the first access device.

18. A first access device, characterized in that: The first access device includes: a first processor and a first memory; when the first processor executes the running program stored in the first memory, the method according to any one of claims 1 to 6 is implemented.

19. A second access device, characterized in that: The second access device includes: a second processor and a second memory; when the second processor executes the running program stored in the second memory, it implements the method according to any one of claims 7 to 15.

20. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a first processor, the method according to any one of claims 1 to 6 is implemented; or when the computer program is executed by a second processor, the method according to any one of claims 7 to 15 is implemented.

21. A computer program product, comprising a computer program, characterized in that The computer program implements the method according to any one of claims 1 to 6 when executed by a first processor, or the computer program implements the method according to any one of claims 7 to 15 when executed by a second processor.

Citation Information

Patent Citations

  • Method utilizing router advertisement carrying options to issue network address translator (NAT) 64 address prefix

    CN102938735A

  • IPv4 and IPv6 compatible domain name resolution method and system

    CN103888554A

  • IPv4 / IPv6 intercommunication system based on HTTP ALG and NAT64 technology

    CN106790098A

  • Message forwarding method and device, domain name address query method and device, equipment and medium

    CN110784562A

  • Secure Internet access control method, gateway equipment and storage medium

    CN112073439A