Network communication system

Abstract

The present application discloses a network communication system. The system includes a domain name system DNS device, a first network address translation device, a second network address translation device, and an Internet data center IDC. The DNS device is used to respond to a domain name query request sent by an IPv4 single-stack user device, determine the protocol version of the IP address corresponding to the target domain name in the domain name query request, and determine the destination IP address based on the protocol version and the IP address; the first network address translation device is used to convert the IPv4 request message sent by the user device into an IPv6 request message based on a mapping relationship or a preset prefix; the second network address translation device is used to determine the target request message by comparing the prefix part of the IPv6 request message with the preset prefix to see whether it is consistent, and send the target request message to the Internet data center IDC corresponding to the destination IP address. The present application solves the technical problem that the related technology cannot cover the application scenario where a single-stack IPv4 user accesses both IPv4 and IPv6 data centers at the same time.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a network communication system. Background Art

[0002] As IPv4 (Internet Protocol version 4) address resources become depleted, IPv6 (Internet Protocol version 6) networks are increasingly being deployed in newly built IDCs (Internet Data Centers), providing public services over IPv6 networks. However, due to the impact of the IPv4 to IPv6 upgrade process (client operating systems, routing and switching network hardware, etc.), clients and most IDCs cannot implement IPv6 network access in the short term. Therefore, there is a widespread demand for coexisting IPv4 and IPv6 access.

[0003] However, related technologies cannot cover application scenarios where single-stack IPv4 users access IPv4 and IPv6 data centers at the same time.

[0004] To address the above-mentioned problems, no effective solutions have been proposed so far. Summary of the Invention

[0005] The embodiments of the present application provide a network communication system to at least solve the technical problem that related technologies cannot cover application scenarios in which single-stack IPv4 users access IPv4 and IPv6 data centers at the same time.

[0006] According to one aspect of an embodiment of the present application, a network communication system is provided, including: a domain name system DNS device, a first network address translation device, a second network address translation device and an Internet data center IDC, wherein the DNS device is used to respond to a domain name query request sent by an IPv4 single-stack user device, determine the protocol version of the IP address corresponding to the target domain name in the domain name query request, and determine the destination IP address based on the protocol version and the IP address, and send the destination IP address to the user device, wherein the protocol version includes: IPv4 and IPv6, and the protocol version of the destination IP address is IPv4; the first network address translation device is used to convert the user set to IPv6 based on a mapping relationship or a preset prefix. The device converts the IPv4 request message sent by the device into an IPv6 request message, and sends the IPv6 request message to the second network address translation device, wherein the mapping relationship is determined by the DNS device when determining the destination IP address, and the IPv4 request message contains the destination IP address with the protocol version of IPv4; the second network address translation device is used to determine the target request message by comparing whether the prefix part of the IPv6 request message is consistent with the preset prefix, and send the target request message to the Internet data center IDC corresponding to the destination IP address to realize communication between the Internet data center IDC and the user device, wherein the protocol version of the target request message includes: IPv4 and IPv6.

[0007] Optionally, the DNS device is used to determine the protocol version of the IP address corresponding to the target domain name in the domain name query request through the following steps, including: performing a recursive query to the DNS server based on the target domain name to obtain a target record returned by the DNS server; when the target record is an A record, determining that the protocol version of the IP address corresponding to the target domain name is IPv4, wherein the A record is a DNS record used to specify the IPv4 address corresponding to the domain name; when the target record is an AAAA record, determining that the protocol version of the IP address corresponding to the target domain name is IPv6, wherein the AAAA record is a DNS record used to resolve the domain name to an IPv6 address.

[0008] Optionally, the DNS device is used to, when the protocol version of the IP address is IPv4, directly determine the IP address as the destination IP address; and, when the protocol version of the IP address is IPv6, determine a mapping relationship and synchronize the mapping relationship to the first network address translation device, wherein the mapping relationship is used to characterize the correspondence between the IPv6 protocol version and the IPv4 protocol version of the IP address; based on the mapping relationship, convert the IP address with the protocol version of IPv6 into the corresponding IPv4 protocol version, and determine the converted IP address with the protocol version of IPv4 as the destination IP address.

[0009] Optionally, when a mapping relationship exists in the first network address translation device, the first network address translation device is used to convert the destination IP address with a protocol version of IPv4 in the IPv4 request message sent by the user device into a corresponding IPv6 protocol version based on the mapping relationship, to obtain an IPv6 request message; when no mapping relationship exists in the first network address translation device, the first network address translation device is used to convert the destination IP address with an IPv4 protocol version into a corresponding IPv6 protocol version by adding a preset prefix to the front end of the destination IP address with a protocol version of IPv4, to obtain an IPv6 request message.

[0010] Optionally, when the second network address translation device receives an IPv6 request message sent by the first network address translation device, the second network address translation device is used to, when the prefix part of the IPv6 request message is consistent with a preset prefix, convert the IPv6 request message into an IPv4 request message and determine the IPv4 request message as a target request message; when the prefix part of the IPv6 request message is inconsistent with the preset prefix, directly determine the IPv6 request message as the target request message.

[0011] Optionally, when the second network address translation device receives the IPv4 response message fed back by the Internet data center IDC in response to the target request message, the second network address translation device is used to convert the IPv4 response message into a corresponding IPv6 response message based on a preset prefix, and send the IPv6 response message to the first network address translation device.

[0012] Optionally, when the second network address translation device receives the IPv6 response message fed back by the Internet data center IDC in response to the target request message, the second network address translation device is used to forward the IPv6 response message directly to the first network address translation device.

[0013] Optionally, when the first network address translation device receives an IPv6 response message, the first network address translation device is used to convert the IPv6 response message into an IPv4 response message based on the preset prefix when the prefix part of the IPv6 response message is consistent with the preset prefix, and send the IPv4 response message to the user device.

[0014] Optionally, when the first network address translation device receives an IPv6 response message, the first network address translation device is used to convert the IPv6 response message into an IPv4 response message based on a mapping relationship when the prefix part of the IPv6 response message is inconsistent with a preset prefix, and send the IPv4 response message to the user device.

[0015] Optionally, a connection is established between the first network address translation device and the second network address translation device via a Border Gateway Protocol (BGP), wherein the preset prefix is ​​shared among the devices connected via the Border Gateway Protocol (BGP).

[0016] In an embodiment of the present application, a domain name system DNS device, a first network address translation device, a second network address translation device and an Internet data center IDC are used, wherein the DNS device is used to respond to a domain name query request sent by an IPv4 single-stack user device, determine the protocol version of the IP address corresponding to the target domain name in the domain name query request, and determine the destination IP address based on the protocol version and the IP address, and send the destination IP address to the user device, wherein the protocol version includes: IPv4 and IPv6, and the protocol version of the destination IP address is IPv4; the first network address translation device is used to convert the IPv4 request message sent by the user device into an IPv6 request message based on a mapping relationship or a preset prefix, and send the IPv6 request message to the second network address translation device, wherein the mapping relationship is determined by the DNS device when determining the destination IP address, I The Pv4 request message contains a destination IP address with a protocol version of IPv4; the second network address translation device is used to determine the target request message by comparing the prefix part of the IPv6 request message with the preset prefix, and send the target request message to the Internet data center IDC corresponding to the destination IP address to realize communication between the Internet data center IDC and the user device, wherein the protocol version of the target request message includes: IPv4 and IPv6. By using the transition technology and deployment solution of NAT46+DNS46+BGP, it is achieved that IPv4 single-stack intranet users can access IPv6 public network resources and can access IPv4 public network resources that need to be reached through the IPv6 single-stack network, thereby solving the technical problem that the relevant technology cannot cover the application scenario where single-stack IPv4 users can access IPv4 and IPv6 data centers at the same time. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0018] Figure 1 is a structural diagram of a network communication system provided according to an embodiment of the present application;

[0019] Figure 2 This is a schematic diagram of a NAT46 usage scenario in a related technology provided according to an embodiment of the present application;

[0020] Figure 3This is a schematic diagram of a scenario in which NAT46+DNS46+BGP is used to implement IPv4 single stack access to IPv4 public network resources across IPv6 single stack, according to an embodiment of the present application;

[0021] Figure 4 It is a schematic diagram of a network communication process provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0022] In order to enable those skilled in the art to better understand the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.

[0023] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in a sequence other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0024] To facilitate those skilled in the art to better understand the embodiments of the present application, some technical terms or nouns involved in the embodiments of the present application are explained as follows:

[0025] NAT (Network Address Translator) is a technology used to switch from private addresses within a local network to global IP addresses when connecting to the internet. NAT was developed to address the shortage of IPv4 addresses. NAT46 is an IPv4-to-IPv6 transition mechanism, providing a way for endpoints in the IPv6 domain to communicate with those in the IPv4 domain, and vice versa.

[0026] DNS (Domain Name System): It is a system used to resolve domain names into IP addresses. On the internet, every device requires a unique IP address to communicate, but humans are more likely to remember domain names than IP addresses. The role of DNS is to resolve human-readable domain names into corresponding IP addresses, enabling devices to communicate with each other and access various services and resources on the internet. The DNS46 gateway uses the destination IP in the header to query the mapping, obtains the actual IPv6 destination address, replaces the IPv4 protocol header with an IPv6 header, and initiates a request to the service domain name using the IPv6 protocol through the IPv6 egress of the NAT46 gateway.

[0027] BGP (Border Gateway Protocol) is an autonomous system routing protocol that runs on TCP. BGP is used to exchange routing information between autonomous systems (AS). When two ASes need to exchange routing information, each AS must designate a node running BGP to represent the AS in exchanging routing information with the other AS. This node can be a host, but is typically implemented by a router.

[0028] Internet Data Center (IDC): refers to a data center with complete equipment (including high-speed Internet access bandwidth, high-performance local area network, safe and reliable computer room environment, etc.), professional management, and complete application service platform.

[0029] As IPv4 address resources become depleted, IPv6 networks are increasingly being deployed in newly built IDCs and data centers, providing public services over IPv6 networks. However, due to the impact of the IPv4 to IPv6 upgrade process (client operating systems, routing and switching network hardware, etc.), IPv6 network access cannot be achieved in the short term. Therefore, there is a widespread demand for coexisting IPv4 and IPv6 access.

[0030] The usage scenarios of NAT46 devices in related technologies are as follows: Figure 2 shown.

[0031] Specifically, in related technologies, when an IPv4 single-stack client device initiates an access request to an IPv6 single-stack IDC data center, the NAT46 device forwards the request to DNS46 for domain name resolution, synchronizes an IPv4 address pool with the mapping of the service domain name to the IPv6 address, and forwards the IPv4 address to the user. The user then uses the IPv4 address to initiate an access request, and the NAT46 device converts the IPv4 protocol packet into an IPv6 packet, initiating the request to the IDC data center over the IPv6 network.

[0032] Since most IDC data centers have not upgraded to IPv6, Figure 2 The NAT46+DNS46 deployment method shown in the has significant limitations. When multiple NAT46 devices are required, each NAT46-deployed device must be independently configured and managed, increasing manual maintenance costs and difficulty. Furthermore, this deployment method only describes a single IPv4-to-IPv6 conversion method and is not compatible with scenarios where IPv4 is accessed via an IPv6 network. The application scenarios are significantly limited and cannot cover scenarios where a single-stack IPv4 user accesses both IPv4 and IPv6 data centers simultaneously.

[0033] In order to solve the above problems, relevant solutions are provided in the embodiments of the present application, which are described in detail below.

[0034] The present application provides an embodiment of a network communication system. Figure 1 is a structural diagram of a network communication system provided according to an embodiment of the present application, such as Figure 1 As shown, the system includes: a domain name system DNS device 10, a first network address translation device 12, a second network address translation device 14 and an Internet data center IDC 16, wherein,

[0035] The DNS device 10 is configured to respond to a domain name query request sent by an IPv4 single-stack user device, determine the protocol version of the IP address corresponding to the target domain name in the domain name query request, determine a destination IP address based on the protocol version and the IP address, and send the destination IP address to the user device. The protocol version includes: IPv4 and IPv6, and the protocol version of the destination IP address is IPv4.

[0036] The first network address translation device 12 is configured to translate the IPv4 request message sent by the user device into an IPv6 request message based on the mapping relationship or the preset prefix, and send the IPv6 request message to the second network address translation device 14, wherein the mapping relationship is determined by the DNS device 10 when determining the destination IP address, and the IPv4 request message includes the destination IP address with the protocol version of IPv4;

[0037] The second network address translation device 14 is used to determine the target request message by comparing the prefix portion of the IPv6 request message with a preset prefix, and send the target request message to the Internet data center IDC 16 corresponding to the destination IP address to achieve communication between the Internet data center IDC 16 and the user device, wherein the protocol version of the target request message includes: IPv4 and IPv6.

[0038] In this embodiment, the DNS device 10 is a DNS46 device, the first network address translation device 12 is a NAT46 device A, and the second network address translation device 14 is a NAT46 device B.

[0039] This application solution optimizes the notification and processing flow in related technologies by deploying NAT46 device B (i.e., the second network address translation device mentioned above) at the edge of the IPv6 data center network side, which is compatible with and supports forwarding IPv4 and IPv6 requests at the same time. The detailed description is given below.

[0040] Figure 3 This is a schematic diagram of a scenario in which an IPv4 single stack accesses an IPv4 public network resource across an IPv6 single stack using NAT46+DNS46+BGP according to an embodiment of the present application. Figure 3 shown.

[0041] In some embodiments of the present application, a DNS device is used to determine the protocol version of the IP address corresponding to the target domain name in a domain name query request through the following steps, including: performing a recursive query on the DNS server based on the target domain name to obtain the target record returned by the DNS server; when the target record is an A record, determining that the protocol version of the IP address corresponding to the target domain name is IPv4, wherein the A record is a DNS record for specifying the IPv4 address corresponding to the domain name; when the target record is an AAAA record, determining that the protocol version of the IP address corresponding to the target domain name is IPv6, wherein the AAAA record is a DNS record for resolving the domain name to an IPv6 address.

[0042] In some embodiments of the present application, the DNS device is used to, when the protocol version of the IP address is IPv4, directly determine the IP address as the destination IP address; and, when the protocol version of the IP address is IPv6, determine a mapping relationship and synchronize the mapping relationship to the first network address translation device, wherein the mapping relationship is used to characterize the correspondence between the IPv6 protocol version and the IPv4 protocol version of the IP address; based on the mapping relationship, convert the IP address with the protocol version of IPv6 into the corresponding IPv4 protocol version, and determine the converted IP address with the protocol version of IPv4 as the destination IP address.

[0043] Specifically, when an IPv4 single-stack client user (user device) initiates an access request to an IPv6 single-stack IDC data center (i.e., the above-mentioned domain name query request), the NAT46 device A (i.e., the above-mentioned first network address translation device) forwards the request to DNS46 (i.e., the above-mentioned DNS device) for domain name resolution. If the query domain name (i.e., the above-mentioned target domain name) is an AAAA record (i.e., the protocol version of the IP address corresponding to the target domain name is IPv6), then the mapping relationship between an IPv4 in the address pool and the service domain name IPv6 is synchronized to the NAT46 device, and the IPv6 address queried by the domain name is converted into an IPv4 address (i.e., the above-mentioned destination IP address) based on the mapping relationship; if the query domain name is an A record (i.e., the protocol version of the IP address corresponding to the target domain name is IPv4), it is directly returned to the NAT46 device, and the IPv4 address (i.e., the above-mentioned destination IP address) is forwarded to the user device.

[0044] In some embodiments of the present application, when a mapping relationship exists in the first network address translation device, the first network address translation device is used to convert the destination IP address with a protocol version of IPv4 in the IPv4 request message sent by the user device into the corresponding IPv6 protocol version based on the mapping relationship, so as to obtain an IPv6 request message; when no mapping relationship exists in the first network address translation device, the first network address translation device is used to convert the destination IP address with an IPv4 protocol version into the corresponding IPv6 protocol version by adding a preset prefix to the front end of the destination IP address with a protocol version of IPv4, so as to obtain an IPv6 request message.

[0045] Specifically, the user initiates an access request (i.e., the IPv4 request message) using an IPv4 address (i.e., the aforementioned destination IP address). If a mapping relationship exists that matches the requested IPv4 address (destination IP address), NAT46 device A (i.e., the aforementioned first network address translation device) converts the IPv4 message into an IPv6 message based on the mapping relationship. Otherwise, based on the IPv6 prefix (i.e., the aforementioned preset prefix), it converts the IPv4 message into an IPv6 message and initiates a request (IPv6 request message) to the IDC data center via the IPv6 network.

[0046] In some embodiments of the present application, when the second network address translation device receives an IPv6 request message sent by the first network address translation device, the second network address translation device is used to, if the prefix part of the IPv6 request message is consistent with a preset prefix, convert the IPv6 request message into an IPv4 request message and determine the IPv4 request message as a target request message; if the prefix part of the IPv6 request message is inconsistent with the preset prefix, directly determine the IPv6 request message as the target request message.

[0047] Specifically, after NAT46 device B (i.e., the above-mentioned second network address translation device) receives the IPv6 request message, if it matches the IPv6 Prefix (i.e., the above-mentioned preset prefix), it converts the IPv6 request message into an IPv4 request message (i.e., the above-mentioned target request message) based on the preset prefix; otherwise, it directly forwards the IPv6 request message.

[0048] In some embodiments of the present application, when the second network address translation device receives an IPv4 response message fed back by an Internet data center IDC in response to a target request message, the second network address translation device is used to convert the IPv4 response message into a corresponding IPv6 response message based on a preset prefix, and send the IPv6 response message to the first network address translation device.

[0049] In some embodiments of the present application, when the second network address translation device receives an IPv6 response message fed back by an Internet data center IDC in response to a target request message, the second network address translation device is configured to forward the IPv6 response message directly to the first network address translation device.

[0050] Specifically, if NAT46 device B (i.e., the above-mentioned second network address translation device) receives an IPv6 response message from the Internet data center IDC, it will directly forward it to NAT46 device A (i.e., the above-mentioned first network address translation device). If it receives an IPv4 response message, it will convert it into an IPv6 response message according to the IPv6 Prefix (i.e., the above-mentioned preset prefix) and forward it to NAT46 device A (i.e., the above-mentioned first network address translation device).

[0051] In some embodiments of the present application, when the first network address translation device receives an IPv6 response message, the first network address translation device is configured to convert the IPv6 response message into an IPv4 response message based on the preset prefix when the prefix part of the IPv6 response message is consistent with the preset prefix, and send the IPv4 response message to the user device.

[0052] In some embodiments of the present application, when the first network address translation device receives an IPv6 response message, the first network address translation device is configured to convert the IPv6 response message into an IPv4 response message based on a mapping relationship when the prefix part of the IPv6 response message is inconsistent with a preset prefix, and send the IPv4 response message to the user device.

[0053] Specifically, after NAT46 device A (i.e., the above-mentioned first network address translation device) receives the IPv6 response message, if it matches the IPv6 Prefix (i.e., the above-mentioned preset prefix), it converts the IPv6 response message into an IPv4 message based on the preset prefix; otherwise, it converts it into an IPv4 message according to the mapping relationship and forwards it to the user device.

[0054] In some embodiments of the present application, a connection is established between the first network address translation device and the second network address translation device via the Border Gateway Protocol BGP, wherein the preset prefix is ​​shared among the devices connected via the Border Gateway Protocol BGP.

[0055] Specifically, in this embodiment, multiple NAT46 devices (such as Figure 3 ) and establish BGP neighbors between the NAT46 devices. That is, connections are established through the Border Gateway Protocol (BGP). Only one of the NAT46 devices needs to be configured with an IPv6 address prefix (that is, the preset prefix mentioned above) and announced to the other NAT46 devices, which facilitates deployment, management, and maintenance.

[0056] The following further introduces the process steps in the network communication system in the embodiment of the present application.

[0057] Figure 4 This is a schematic diagram of a network communication process provided according to an embodiment of the present application, such as Figure 4 As shown, the process includes the following steps:

[0058] Step 1: The IPv4 single-stack user device initiates a DNS domain name query request.

[0059] In step 2, the DNS 46 device (ie, the above-mentioned DNS device) obtains an A record or AAAA record query result by recursively querying the domain name to the DNS server.

[0060] Step 3: If the DNS46 device returns an A record, it directly forwards the destination IPv4 to the user; if it returns an AAAA record, it converts the destination IPv6 to the destination IPv4 based on the mapping relationship and synchronizes the mapping relationship to the NAT46 device.

[0061] Step 4: The user initiates a request using the destination IPv4 (i.e., the destination IP address mentioned above).

[0062] Step 5: If there is a mapping relationship for the destination IPv4 in NAT46 device A (i.e., the above-mentioned first network address translation device), the IPv4 message protocol is converted into an IPv6 message according to the mapping relationship; if there is no mapping relationship, the IPv6 Prefix (i.e., the above-mentioned preset prefix) is used.

[0063] Step 6: NAT46 device B (i.e., the second network address translation device) receives the IPv6 request message. If it matches the IPv6 Prefix (preset prefix), it converts it into an IPv4 message and sends it to the corresponding IDC. Otherwise, it directly forwards it to the corresponding IDC.

[0064] In step 7, if NAT46 device B receives the IPv4 response message sent by IDC, it converts it into an IPv6 message according to the IPv6 Prefix protocol (preset prefix) and sends it to NAT46 device A; if it receives an IPv6 response message, it directly forwards it to NAT46 device A.

[0065] In step 8, NAT46 device A (i.e., the first network address translation device mentioned above) receives the IPv6 response message. If it matches the IPv6 Prefix (preset prefix), it converts it into an IPv4 message based on the preset prefix. Otherwise, it converts it into an IPv4 message based on the mapping relationship and forwards it to the user device.

[0066] This application solution uses NAT46+DNS46+BGP transition technology and deployment solution to achieve scenarios where IPv4 single-stack intranet users can access IPv6 public network resources based on NAT46+DNS46 transition technology, and IPv4 single-stack intranet users can access IPv4 public network resources that need to be reached through an IPv6 single-stack network. At the same time, by adding the assistance of BGP, deployment and maintenance are facilitated.

[0067] This application solution supports compatible single-stack IPv4 access to IPv4 and IPv6 networks at the same time, and has a wider range of applicability scenarios. NAT46 also supports protocol conversion processing for IPv4 to IPv6, as well as IPv6 forwarding without conversion. It uses the address announcement capability of the BGP protocol to simplify the deployment and maintenance costs of multiple NAT46 devices. It is suitable for scenarios where the client is a single-stack IPv4 and the server is upgraded to a single-stack IPv6 network; or scenarios where the core network is upgraded to provide single-stack IPv6 forwarding services, and the client and server still use single-stack IPv4 services due to the impact of the IPv4 to IPv6 upgrade process; or scenarios where multiple NAT46 devices need to be deployed, etc.

[0068] Through the above steps, by using the NAT46+DNS46+BGP transition technology and deployment solution, it is achieved that IPv4 single-stack intranet users can access both IPv6 public network resources and IPv4 public network resources that need to be reached through the IPv6 single-stack network. This solves the technical problem that the relevant technology cannot cover the application scenario where single-stack IPv4 users can access IPv4 and IPv6 data centers at the same time.

[0069] The serial numbers of the above embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0070] In the above embodiments of the present application, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0071] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only exemplary. For example, the division of the units can be a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0072] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0073] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0074] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0075] The above is only a preferred embodiment of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A network communication system, characterized in that: include: Domain Name System DNS device, first Network Address Translation device, second Network Address Translation device and Internet Data Center IDC, wherein, The DNS device is configured to respond to a domain name query request sent by an IPv4 single-stack user device, determine a protocol version of an IP address corresponding to a target domain name in the domain name query request, determine a destination IP address based on the protocol version and the IP address, and send the destination IP address to the user device, wherein the protocol version includes: IPv4 and IPv6, and the protocol version of the destination IP address is IPv4; The first network address translation device is configured to translate the IPv4 request message sent by the user equipment into an IPv6 request message according to a mapping relationship or a preset prefix, and send the IPv6 request message to the second network address translation device, wherein the mapping relationship is determined by the DNS device when determining the destination IP address, and the IPv4 request message includes the destination IP address with a protocol version of IPv4; The second network address translation device is configured to determine a target request message by comparing a prefix portion of the IPv6 request message with the preset prefix to determine whether the prefix portion is consistent, and send the target request message to the Internet data center IDC corresponding to the destination IP address, so as to implement communication between the Internet data center IDC and the user equipment, wherein the protocol version of the target request message includes: IPv4 and IPv6; If the mapping relationship exists in the first network address translation device, the first network address translation device is configured to translate the destination IP address with the protocol version of IPv4 in the IPv4 request message sent by the user equipment into the corresponding IPv6 protocol version according to the mapping relationship, so as to obtain the IPv6 request message; if the mapping relationship does not exist in the first network address translation device, the first network address translation device is configured to translate the destination IP address with the protocol version of IPv4 into the corresponding IPv6 protocol version by adding the preset prefix to the front end of the destination IP address with the protocol version of IPv4, so as to obtain the IPv6 request message; When the second network address translation device receives the IPv6 request message sent by the first network address translation device, the second network address translation device is configured to, if the prefix portion of the IPv6 request message is consistent with the preset prefix, convert the IPv6 request message into an IPv4 request message and determine the IPv4 request message as the target request message; and if the prefix portion of the IPv6 request message is inconsistent with the preset prefix, directly determine the IPv6 request message as the target request message.

2. The network communication system according to claim 1, wherein: The DNS device is configured to determine a protocol version of an IP address corresponding to a target domain name in the domain name query request through the following steps, including: Perform a recursive query on the DNS server based on the target domain name, and obtain the target record returned by the DNS server; In a case where the target record is an A record, determining that the protocol version of the IP address corresponding to the target domain name is IPv4, wherein the A record is a DNS record for specifying the IPv4 address corresponding to the domain name; In a case where the target record is an AAAA record, it is determined that the protocol version of the IP address corresponding to the target domain name is IPv6, wherein the AAAA record is a DNS record used to resolve a domain name to an IPv6 address.

3. The network communication system according to claim 2, wherein: The DNS device is used to: When the protocol version of the IP address is IPv4, directly determining the IP address as the destination IP address; and In a case where the protocol version of the IP address is IPv6, determining the mapping relationship and synchronizing the mapping relationship to the first network address translation device, wherein the mapping relationship is used to characterize the correspondence between the IPv6 protocol version and the IPv4 protocol version of the IP address; According to the mapping relationship, the IP address with the protocol version of IPv6 is converted into the corresponding IPv4 protocol version, and the converted IP address with the protocol version of IPv4 is determined as the destination IP address.

4. The network communication system according to claim 1, wherein: When the second network address translation device receives the IPv4 response message fed back by the Internet data center IDC in response to the target request message, the second network address translation device is used to convert the IPv4 response message into a corresponding IPv6 response message based on the preset prefix, and send the IPv6 response message to the first network address translation device.

5. The network communication system according to claim 4, characterized in that: When the second network address translation device receives the IPv6 response message fed back by the Internet data center IDC in response to the target request message, the second network address translation device is used to forward the IPv6 response message directly to the first network address translation device.

6. The network communication system according to claim 5, characterized in that: When the first network address translation device receives the IPv6 response message, the first network address translation device is used to convert the IPv6 response message into an IPv4 response message based on the preset prefix when the prefix part of the IPv6 response message is consistent with the preset prefix, and send the IPv4 response message to the user device.

7. The network communication system according to claim 5, wherein: When the first network address translation device receives the IPv6 response message, the first network address translation device is used to, if the prefix part of the IPv6 response message is inconsistent with the preset prefix, convert the IPv6 response message into an IPv4 response message according to the mapping relationship, and send the IPv4 response message to the user device.

8. The network communication system according to claim 1, wherein: A connection is established between the first network address translation device and the second network address translation device via the Border Gateway Protocol BGP, wherein the preset prefix is ​​shared among the devices connected via the Border Gateway Protocol BGP.

Images