CN116800710A - Network communication system - Google Patents
Network communication system Download PDFInfo
- Publication number
- CN116800710A CN116800710A CN202310948474.8A CN202310948474A CN116800710A CN 116800710 A CN116800710 A CN 116800710A CN 202310948474 A CN202310948474 A CN 202310948474A CN 116800710 A CN116800710 A CN 116800710A
- Authority
- CN
- China
- Prior art keywords
- ipv6
- ipv4
- address
- network address
- protocol version
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000004891 communication Methods 0.000 title claims abstract description 28
- 238000013519 translation Methods 0.000 claims abstract description 79
- 238000013507 mapping Methods 0.000 claims abstract description 46
- 238000006243 chemical reaction Methods 0.000 claims abstract description 22
- 230000004044 response Effects 0.000 claims description 70
- 238000000034 method Methods 0.000 claims description 11
- 238000005516 engineering process Methods 0.000 abstract description 11
- 238000010586 diagram Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 5
- 238000012423 maintenance Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 3
- 230000007704 transition Effects 0.000 description 3
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000013468 resource allocation Methods 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application discloses a network communication system. The system comprises Domain Name System (DNS) equipment, first network address conversion equipment, second network address conversion equipment and an Internet Data Center (IDC), wherein the DNS equipment is used for responding to a domain name query request sent by IPv4 single stack user equipment, determining a protocol version of an IP address corresponding to a target domain name in the domain name query request, and determining a target IP address according to the protocol version and the IP address; the first network address conversion device is used for converting an IPv4 request message sent by the user equipment into an IPv6 request message according to the mapping relation or a preset prefix; the second network address translation device is configured to determine a target request packet by comparing whether the prefix portion of the IPv6 request packet is consistent with the preset prefix, and send the target request packet to the internet data center IDC corresponding to the destination IP address. The application solves the technical problem that the related technology cannot cover the application scene of the IPv4 and IPv6 data centers which are accessed by the Shan Zhan IPv4 user at the same time.
Description
Technical Field
The application relates to the technical field of communication, in particular to a network communication system.
Background
With the exhaustion of IPv4 (Internet Protocol version, internet protocol version 4) address resource allocation, IPv6 (Internet Protocol version, internet protocol version 6) networks are being increasingly deployed to newly built IDCs (Internet Data Center, internet data centers) to serve the public with IPv6 networks. The client and most IDC data centers are affected by the process of upgrading IPv4 to IPv6 (client operating system, routing switch network hardware, etc.), and cannot realize access to the IPv6 network in a short period, so there is a universal requirement for coexistence of IPv4 and IPv6 access.
However, the related art cannot cover an application scenario in which Shan Zhan IPv4 users access both IPv4 and IPv6 data centers.
In view of the above problems, no effective solution has been proposed at present.
Disclosure of Invention
The embodiment of the application provides a network communication system to at least solve the technical problem that the application scenes of IPv4 and IPv6 data centers can not be accessed by a Shan Zhan IPv4 user simultaneously which cannot be covered by related technologies.
According to an aspect of an embodiment of the present application, there is provided a network communication system including: the system comprises domain name system DNS equipment, first network address conversion equipment, second network address conversion equipment and an internet data center IDC, wherein the DNS equipment is used for responding to a domain name query request sent by IPv4 single stack user equipment, determining a protocol version of an IP address corresponding to a target domain name in the domain name query request, determining a target IP address according to the protocol version and the IP address, and sending the target IP address to the user equipment, wherein the protocol version comprises: IPv4 and IPv6, the protocol version of the destination IP address is IPv4; the first network address conversion device is used for converting an IPv4 request message sent by the user equipment into an IPv6 request message according to a mapping relation or a preset prefix, and sending the IPv6 request message to the second network address conversion device, wherein the mapping relation is determined by the DNS device when determining a target IP address, and the IPv4 request message contains the target IP address with a protocol version of IPv4; the second network address translation device is configured to determine a target request packet by comparing whether a prefix portion of the IPv6 request packet is consistent with a preset prefix, and send the target request packet to an internet data center IDC corresponding to a destination IP address, so as to implement communication between the internet data center IDC and the user equipment, where a protocol version of the target request packet includes: IPv4 and IPv6.
Optionally, the DNS device is configured to determine a protocol version of an IP address corresponding to the target domain name in the domain name query request, including: recursively inquiring a DNS server according to the target domain name to obtain a target record returned by the DNS server; under the condition that 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; and under the condition that 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 the IPv6 address.
Optionally, the DNS device is configured to directly determine the IP address as the destination IP address in the case where the protocol version of the IP address is IPv4; and determining a mapping relation and synchronizing the mapping relation to the first network address conversion equipment under the condition that the protocol version of the IP address is IPv6, wherein the mapping relation is used for representing the corresponding relation between the IPv6 protocol version and the IPv4 protocol version of the IP address; according to the mapping relation, converting the IP address with the protocol version of IPv6 into a corresponding IPv4 protocol version, and determining the IP address with the converted protocol version of IPv4 as a target IP address.
Optionally, under the condition that a mapping relationship exists in the first network address translation device, the first network address translation device is configured to translate, according to the mapping relationship, a protocol version in an IPv4 request message sent by the user equipment into an IPv6 protocol version corresponding to a destination IP address translation of IPv4, so as to obtain the IPv6 request message; under the condition that the mapping relation does not exist in the first network address conversion equipment, the first network address conversion equipment is used for converting the destination IP address of the IPv4 protocol version into a corresponding IPv6 protocol version in a mode that a preset prefix is added to the front end of the destination IP address of the IPv4 protocol version, so that an IPv6 request message is obtained.
Optionally, 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 translate the IPv6 request message into an IPv4 request message and determine the IPv4 request message as a target request message when a prefix portion of the IPv6 request message is consistent with a preset prefix; and under the condition that the prefix part of the IPv6 request message is inconsistent with the preset prefix, directly determining the IPv6 request message as a target request message.
Optionally, when the second network address translation device receives the IPv4 response message fed back by the internet data center IDC response target request message, the second network address translation device is configured to translate the IPv4 response message into a corresponding IPv6 response message according to a preset prefix, and send the IPv6 response message to the first network address translation device.
Optionally, in the case that 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 configured to forward the IPv6 response message directly to the first network address translation device.
Optionally, when the first network address translation device receives the IPv6 response message, the first network address translation device is configured to translate the IPv6 response message into the IPv4 response message according to the preset prefix and send the IPv4 response message to the user equipment, where the prefix portion of the IPv6 response message is consistent with the preset prefix.
Optionally, when the first network address translation device receives the IPv6 response message, the first network address translation device is configured to translate the IPv6 response message into the IPv4 response message according to the mapping relationship and send the IPv4 response message to the user equipment when the prefix portion of the IPv6 response message is inconsistent with the preset prefix.
Optionally, a connection is established between the first network address translation device and the second network address translation device through a border gateway protocol BGP, where the preset prefix is shared among the devices that establish the connection through the border gateway protocol BGP.
In the embodiment of the application, a Domain Name System (DNS) device, a first network address conversion device, a second network address conversion device and an Internet Data Center (IDC) are adopted, wherein the DNS device is used for responding to a domain name query request sent by IPv4 single stack user equipment, determining a protocol version of an IP address corresponding to a target domain name in the domain name query request, determining a target IP address according to the protocol version and the IP address, and sending the target IP address to the user equipment, wherein the protocol version comprises: IPv4 and IPv6, the protocol version of the destination IP address is IPv4; the first network address conversion device is used for converting an IPv4 request message sent by the user equipment into an IPv6 request message according to a mapping relation or a preset prefix, and sending the IPv6 request message to the second network address conversion device, wherein the mapping relation is determined by the DNS device when determining a target IP address, and the IPv4 request message contains the target IP address with a protocol version of IPv4; the second network address translation device is configured to determine a target request packet by comparing whether a prefix portion of the IPv6 request packet is consistent with a preset prefix, and send the target request packet to an internet data center IDC corresponding to a destination IP address, so as to implement communication between the internet data center IDC and the user equipment, where a protocol version of the target request packet includes: by using the transition technology and deployment scheme of NAT46+DNS46+BGP in the modes of IPv4 and IPv6, the effect that an IPv4 single stack intranet user can access IPv6 public network resources and can access IPv4 public network resources which need to be reached through an IPv6 single stack network is achieved, and the technical problem that the application scene of an IPv4 data center and an IPv6 data center can not be accessed by a Shan Zhan IPv4 user can not be covered by the related technology is solved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:
fig. 1 is a schematic structural diagram of a network communication system according to an embodiment of the present application;
fig. 2 is a schematic diagram of a related art NAT46 usage scenario according to an embodiment of the present application;
fig. 3 is a schematic diagram of a scenario in which IPv4 single stack cross-IPv 6 single stack access to IPv4 public network resources is implemented using NAT46+dns46+bgp according to an embodiment of the present application;
fig. 4 is a schematic diagram of a flow of network communication according to an embodiment of the present application.
Detailed Description
In order that those skilled in the art will better understand the present application, a technical solution in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present application without making any inventive effort, shall fall within the scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the application described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
In order to facilitate a better understanding of the embodiments of the present application, some technical terms or terms related to the embodiments of the present application will be explained below:
NAT (Network Address Translator, network address translation): is a technique for using private addresses in a local network, which in turn uses global IP addresses when connecting to the internet. NAT is actually a technology developed to solve the shortage of IPv4 addresses. NAT46 is an IPv4 to IPv6 transitional mechanism that provides an endpoint in the IPv6 domain with a way to communicate with an endpoint in the IPv4 domain and vice versa.
DNS (Domain Name System ): it is a system for resolving domain names into IP addresses. On the internet, each device requires a unique IP address to communicate, but it is easier for humans to remember a domain name rather than an IP address. DNS functions to resolve human-readable domain names to corresponding IP addresses, thereby enabling devices to communicate with each other and access various services and resources on the internet. The DNS46 gateway queries the mapping by the IP of the header destination to obtain a real IPv6 destination address, the IPv4 protocol header is replaced by the IPv6 header, and a request is initiated to the service domain name by the IPv6 protocol through the IPv6 outlet of the NAT46 gateway.
BGP (Border Gateway Protocol ): is a routing protocol of an autonomous system running on TCP. BGP is used to exchange routing information between different autonomous systems (ases). When two ases need to exchange routing information, each AS must designate a BGP-running node to exchange routing information with other ases on behalf of the AS. This node may be a host. But is typically a router that performs BGP.
Internet data center (Internet Data Center, IDC): the system is a specialized management and perfect application service platform with perfect equipment (including high-speed Internet access bandwidth, high-performance local area network, safe and reliable machine room environment and the like).
With the exhaustion of IPv4 address resource allocation, IPv6 networks are being increasingly and practically deployed to new IDC data centers to provide services to the public by the IPv6 networks. However, the client and most IDC data centers are affected by the process of upgrading IPv4 to IPv6 (client operating system, routing switching network hardware, etc.), and cannot realize access to the IPv6 network in a short period, so there is a universal requirement for coexistence of IPv4 and IPv6 access.
A related art use scenario of the NAT46 device is shown in fig. 2.
Specifically, in the related art, when the IPv4 single stack client user equipment initiates an access request to the IPv6 single stack IDC data center, the NAT46 device forwards the request to the DNS46 for domain name resolution, synchronizes mapping of one IPv4 in the address pool and the service domain name IPv6 to the NAT46 device, and forwards the IPv4 address to the user. The user initiates an access request by using the IPv4 address, the NAT46 device converts the IPv4 protocol message into an IPv6 message, and initiates a request to the IDC data center through an IPv6 network.
Since most IDC data centers are not upgraded to IPv6, the NAT46+ DNS46 deployment approach shown in fig. 2 is very limited in application. When multiple NAT46 devices are needed, each NAT46 deployed device is configured and managed independently, which increases the cost and difficulty of manual maintenance. Moreover, the deployment mode only describes a single IPv4 access IPv6 conversion mode, cannot be compatible with IPv4 access IPv4 scenes converted by an IPv6 network, has obvious limitation on application scenes, and cannot cover the application scenes of Shan Zhan IPv4 users for simultaneously accessing IPv4 and IPv6 data centers
In order to solve the above problems, related solutions are provided in the embodiments of the present application, and are described in detail below.
An embodiment of the present application provides an embodiment of a network communication system, and fig. 1 is a schematic structural diagram of a network communication system provided according to an embodiment of the present application, as shown in fig. 1, where 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,
the DNS device 10 is configured to determine a protocol version of an IP address corresponding to a target domain name in a domain name query request in response to the domain name query request sent by the IPv4 single stack user device, determine a destination IP address according to the protocol version and the IP address, and send the destination IP address to the user device, where the protocol version includes: IPv4 and IPv6, the protocol version of the destination IP address is IPv4;
the first network address translation device 12 is configured to translate an 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 14, where the mapping relationship is determined by the DNS device 10 when determining the destination IP address, and the IPv4 request message includes a destination IP address with a protocol version of IPv4;
the second network address translation device 14 is configured to determine a target request packet by comparing whether a prefix portion of the IPv6 request packet is consistent with a preset prefix, and send the target request packet to the internet data center IDC 16 corresponding to the destination IP address, so as to implement communication between the internet data center IDC 16 and the user equipment, where a protocol version of the target request packet includes: IPv4 and IPv6.
In the present embodiment, the DNS device 10 employs a DNS46 device, the first network address translation device 12 employs a NAT46 device a, and the second network address translation device 14 employs a NAT46 device B.
The scheme of the application optimizes the notification and processing flow in the related technology by adding the NAT46 device B (namely the second network address translation device) on the network side edge of the IPv6 data center and compatibly supporting the simultaneous forwarding of IPv4 and IPv6 requests, and is described in detail below.
Fig. 3 is a schematic diagram of a scenario in which IPv4 single stack cross-IPv 6 single stack access to IPv4 public network resources is implemented using NAT46+dns46+bgp according to an embodiment of the present application, as shown in fig. 3.
In some embodiments of the present application, the DNS device is configured to determine a protocol version of an IP address corresponding to a target domain name in a domain name query request, including: recursively inquiring a DNS server according to the target domain name to obtain a target record returned by the DNS server; under the condition that 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; and under the condition that 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 the IPv6 address.
In some embodiments of the present application, the DNS device is configured to directly determine the IP address as the destination IP address in the case where the protocol version of the IP address is IPv4; and determining a mapping relation and synchronizing the mapping relation to the first network address conversion equipment under the condition that the protocol version of the IP address is IPv6, wherein the mapping relation is used for representing the corresponding relation between the IPv6 protocol version and the IPv4 protocol version of the IP address; according to the mapping relation, converting the IP address with the protocol version of IPv6 into a corresponding IPv4 protocol version, and determining the IP address with the converted protocol version of IPv4 as a target IP address.
Specifically, when an IPv4 single stack client user (user equipment) initiates an access request (i.e., the above domain name query request) to an IPv6 single stack IDC data center, the NAT46 device a (i.e., the above first network address translation device) forwards the request to the DNS46 (i.e., the above DNS device) to perform domain name resolution, if the query domain name (i.e., the above target domain name) is an AAAA record (i.e., the protocol version of the IP address corresponding to the target domain name is IPv 6), the mapping relationship between one IPv4 in the synchronous address pool and the serving domain name IPv6 is transferred to the NAT46 device, and the IPv6 address queried by the domain name is converted into the IPv4 address (i.e., the above target IP address) according to the mapping relationship; if the query domain name is record A (i.e. the protocol version of the IP address corresponding to the target domain name is IPv 4), the query domain name is directly returned to the NAT46 device, and the IPv4 address (i.e. the target IP address) is forwarded to the user device.
In some embodiments of the present application, in the case that a mapping relationship exists in the first network address translation device, the first network address translation device is configured to translate, according to the mapping relationship, an IPv6 protocol version corresponding to a destination IP address of IPv4, where the protocol version in the IPv4 request packet sent by the user equipment, to obtain the IPv6 request packet; under the condition that the mapping relation does not exist in the first network address conversion equipment, the first network address conversion equipment is used for converting the destination IP address of the IPv4 protocol version into a corresponding IPv6 protocol version in a mode that a preset prefix is added to the front end of the destination IP address of the IPv4 protocol version, so that an IPv6 request message is obtained.
Specifically, the user initiates an access request (i.e., the above-described IPv4 request message) using an IPv4 address (i.e., the above-described destination IP address). If there is a mapping relation that the request IPv4 address (destination IP address) matches, the NAT46 device a (i.e., the first network address translation device) translates the IPv4 message into an IPv6 message according to the mapping relation; otherwise, according to the IPv6 Prefix (i.e. the preset Prefix), the IPv4 message is converted into an IPv6 message, and a request (IPv 6 request message) is initiated to the IDC data center through the IPv6 network.
In some embodiments of the present application, 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 translate the IPv6 request message into an IPv4 request message and determine the IPv4 request message as a target request message when a prefix portion of the IPv6 request message is consistent with a preset prefix; and under the condition that the prefix part of the IPv6 request message is inconsistent with the preset prefix, directly determining the IPv6 request message as a target request message.
Specifically, after receiving the IPv6 request message, the NAT46 device B (i.e., the second network address translation device) translates the IPv6 request message into an IPv4 request message (i.e., the target request message) according to the preset Prefix if the IPv6 Prefix (i.e., the preset Prefix) is matched, or directly forwards the IPv6 request message.
In some embodiments of the present application, when the second network address translation device receives an 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 configured to translate the IPv4 response message into a corresponding IPv6 response message according to a preset prefix, and send the IPv6 response message to the first network address translation device.
In some embodiments of the present application, in the case that 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 configured to forward the IPv6 response message directly to the first network address translation device.
Specifically, if the NAT46 device B (i.e. the second network address translation device) receives the IPv6 response message of the internet data center IDC, the IPv6 response message is directly forwarded to the NAT46 device a (i.e. the first network address translation device), and if the IPv4 response message is received, the IPv6 response message is translated into an IPv6 response message according to the IPv6 Prefix (i.e. the preset Prefix), and then the IPv6 response message is forwarded to the NAT46 device a (i.e. the first network address translation device).
In some embodiments of the present application, when the first network address translation device receives the IPv6 response message, the first network address translation device is configured to translate the IPv6 response message into the IPv4 response message according to the preset prefix and send the IPv4 response message to the user equipment, where the prefix portion of the IPv6 response message is consistent with the preset prefix.
In some embodiments of the present application, when the first network address translation device receives the IPv6 response message, the first network address translation device is configured to translate the IPv6 response message into the IPv4 response message according to the mapping relationship and send the IPv4 response message to the user equipment, where a prefix portion of the IPv6 response message is inconsistent with a preset prefix.
Specifically, after receiving the IPv6 response message, the NAT46 device a (i.e., the first network address translation device) translates the IPv6 response message into an IPv4 message according to the preset Prefix if the IPv6 Prefix (i.e., the preset Prefix) is matched, or translates the IPv6 response message into an IPv4 message according to the mapping relationship, and forwards the IPv4 message to the ue.
In some embodiments of the present application, a connection is established between a first network address translation device and a second network address translation device via border gateway protocol BGP, wherein a preset prefix is shared among the devices that establish the connection via border gateway protocol BGP.
Specifically, in this embodiment, since multiple NAT46 devices (such as NAT46 device a, device B, and device N shown in fig. 3) are deployed, and BGP neighbors are established between NAT46 devices, that is, connection is established through border gateway protocol BGP, only one of the NAT46 devices needs to be configured with an IPv6 address prefix (i.e., the preset prefix) and notified to other NAT46 devices, so that deployment management and maintenance are facilitated.
The following describes the steps of the flow in the network communication system in the embodiment of the present application.
Fig. 4 is a schematic diagram of a flow of network communication according to an embodiment of the present application, as shown in fig. 4, the flow includes the following steps:
step 1, IPv4 single stack user equipment initiates a DNS domain name query request.
In step 2, the DNS46 device (i.e., the DNS device described above) obtains a record or AAAA record query results by recursively querying the DNS server for domain names.
Step 3, if the DNS46 equipment returns the record A, directly forwarding the destination IPv4 to the user; if the AAAA record is returned, the destination IPv6 is converted into the destination IPv4 according to the mapping relation, and the mapping relation is synchronously mapped to the NAT46 equipment.
And step 4, the user initiates a request by using the destination IPv4 (namely the destination IP address).
And 5, in the NAT46 device A (i.e. the first network address translation device), if the mapping relation exists in the target IPv4, according to the mapping relation, if the mapping relation does not exist in the target IPv4, according to the IPv6 Prefix (i.e. the preset Prefix), converting the IPv4 message protocol into the IPv6 message.
And 6, receiving the IPv6 request message by the NAT46 device B (namely the second network address translation device), translating the IPv6 request message into an IPv4 message if the IPv6 Prefix (preset Prefix) is matched, and then sending the IPv4 message to the corresponding IDC, otherwise, directly forwarding the IPv6 message to the corresponding IDC.
Step 7, if receiving the IPv4 response message sent by the IDC, the NAT46 device B converts the IPv4 response message into an IPv6 message according to an IPv6 Prefix (preset Prefix) and sends the IPv6 message to the NAT46 device A; if the IPv6 response message is received, the response message is directly forwarded to the NAT46 device A.
Step 8, the nat46 device a (i.e. the first network address translation device) receives the IPv6 response message, and if the IPv6 Prefix (preset Prefix) is matched, the nat46 device a translates the IPv4 message according to the preset Prefix, otherwise translates the IPv4 message according to the mapping relationship, and forwards the IPv4 message to the user equipment.
The scheme of the application realizes that an IPv4 single-stack intranet user based on the NAT46+DNS46 transition technology can access IPv6 public network resources and can access a scene that the IPv4 single-stack intranet user needs to reach the IPv4 public network resources through an IPv6 single-stack network by using the transition technology and the deployment scheme of the NAT46+DNS46+BGP, and is convenient for deployment and maintenance by adding the assistance of the BGP.
The scheme of the application supports the compatibility of single stack IPv4 and simultaneously accesses IPv4 and IPv6 networks, the scene applicability is wider, the NAT46 simultaneously supports the protocol conversion processing of converting IPv4 into IPv6, and the IPv6 does not convert and transmit, the deployment and maintenance cost of a plurality of NAT46 devices are simplified by utilizing the address notification capability of BGP protocol, and the method is applicable to the scene that a client is single stack IPv4 and a server is upgraded to the single stack IPv6 network; or the core network upgrade provides a single stack IPv6 forwarding service, and the client and the server still use the single stack IPv4 service because of the influence of the process from IPv4 upgrade to IPv 6; or a scenario where multiple NAT46 devices need to be deployed, etc.
Through the steps, through the transitional technology and the deployment scheme of using NAT46+DNS46+BGP, the effect that an IPv4 single stack intranet user can access IPv6 public network resources and can access IPv4 public network resources which need to be reached through an IPv6 single stack network is achieved, and further the technical problem that the application scene of an IPv4 data center and an IPv6 data center can not be accessed by a Shan Zhan IPv4 user in a covering mode in the related technology is solved.
The foregoing embodiment numbers of the present application are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
In the foregoing embodiments of the present application, the descriptions of the embodiments are emphasized, and for a portion of this disclosure that is not described in detail in this embodiment, reference is made to the related descriptions of other embodiments.
In the several embodiments provided in the present application, it should be understood that the disclosed technology may be implemented in other manners. The above-described embodiments of the apparatus are merely exemplary, and the division of the units, for example, may be a logic function division, and may be implemented in another manner, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interfaces, units or modules, or may be in electrical or other forms.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in part or all of the technical solution or in part in the form of a software product stored in a storage medium, including instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing is merely a preferred embodiment of the present application and it should be noted that modifications and adaptations to those skilled in the art may be made without departing from the principles of the present application, which are intended to be comprehended within the scope of the present application.
Claims (10)
1. A network communication system, comprising: 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 configured to determine a protocol version of an IP address corresponding to a target domain name in a domain name query request in response to the domain name query request sent by an IPv4 single stack user device, determine a destination IP address according to the protocol version and the IP address, and send the destination IP address to the user device, where the protocol version includes: IPv4 and IPv6, wherein the protocol version of the destination IP address is IPv4;
the first network address translation device is configured to translate an IPv4 request packet sent by the user equipment into an IPv6 request packet according to a mapping relationship or a preset prefix, and send the IPv6 request packet to the second network address translation device, where the mapping relationship is determined by the DNS device when determining the destination IP address, and the IPv4 request packet includes the destination IP address with a protocol version of IPv4;
the second network address translation device is configured to determine a target request packet by comparing whether a prefix portion of the IPv6 request packet is consistent with the preset prefix, and send the target request packet 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, where a protocol version of the target request packet includes: IPv4 and IPv6.
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 the target domain name in the domain name query request by:
recursively inquiring a DNS server according to 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 for specifying the IPv4 address corresponding to the domain name;
and under the condition that 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 the IPv6 address.
3. The network communication system of claim 2, wherein the DNS device is configured to,
under the condition that the protocol version of the IP address is IPv4, directly determining the IP address as the destination IP address; the method comprises the steps of,
under the condition that the protocol version of the IP address is IPv6, determining the mapping relation and synchronizing the mapping relation to the first network address conversion equipment, wherein the mapping relation is used for representing the corresponding relation between the IPv6 protocol version and the IPv4 protocol version of the IP address;
according to the mapping relation, converting the IP address with the protocol version of IPv6 into a corresponding IPv4 protocol version, and determining the IP address with the converted protocol version of IPv4 as the destination IP address.
4. A network communication system as claimed in claim 3, wherein,
under the condition that the mapping relationship exists in the first network address translation equipment, the first network address translation equipment is used for translating a target IP address with a protocol version of IPv4 in the IPv4 request message sent by the user equipment into a corresponding IPv6 protocol version according to the mapping relationship to obtain the IPv6 request message;
and under the condition that the mapping relation does not exist in the first network address conversion equipment, the first network address conversion equipment is used for converting the destination IP address of the IPv4 protocol version into a corresponding IPv6 protocol version in a mode that the preset prefix is added to the front end of the destination IP address of the IPv4 protocol version, so as to obtain the IPv6 request message.
5. The network communication system according to claim 1, wherein in the case where 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
Under the condition that the prefix part of the IPv6 request message is consistent with the preset prefix, converting the IPv6 request message into an IPv4 request message, and determining the IPv4 request message as the target request message;
and under the condition that the prefix part of the IPv6 request message is inconsistent with the preset prefix, directly determining the IPv6 request message as the target request message.
6. The network communication system according to claim 5, wherein, in the case that the second network address translation device receives an 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 configured to translate the IPv4 response message into a corresponding IPv6 response message according to the preset prefix, and send the IPv6 response message to the first network address translation device.
7. The network communication system according to claim 6, wherein in case that the second network address translation device receives an 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 configured to forward the IPv6 response message directly to the first network address translation device.
8. The network communication system according to claim 7, wherein, in a case where the first network address translation device receives the IPv6 response message, the first network address translation device is configured to translate the IPv6 response message into an IPv4 response message according to the preset prefix, and send the IPv4 response message to the user equipment, in a case where a prefix portion of the IPv6 response message is identical to the preset prefix.
9. The network communication system according to claim 7, wherein, in a case where the first network address translation device receives the IPv6 response message, the first network address translation device is configured to translate the IPv6 response message into an IPv4 response message according to the mapping relationship, and send the IPv4 response message to the user equipment, in a case where a prefix portion of the IPv6 response message is inconsistent with the preset prefix.
10. The network communication system of claim 1, wherein a connection is established between the first network address translation device and the second network address translation device via a border gateway protocol BGP, and wherein the pre-set prefix is shared among the devices that establish the connection via the border gateway protocol BGP.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202310948474.8A CN116800710A (en) | 2023-07-28 | 2023-07-28 | Network communication system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202310948474.8A CN116800710A (en) | 2023-07-28 | 2023-07-28 | Network communication system |
Publications (1)
Publication Number | Publication Date |
---|---|
CN116800710A true CN116800710A (en) | 2023-09-22 |
Family
ID=88034933
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202310948474.8A Pending CN116800710A (en) | 2023-07-28 | 2023-07-28 | Network communication system |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN116800710A (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN118199991A (en) * | 2024-03-26 | 2024-06-14 | 北京英迪瑞讯网络科技有限公司 | Secure access protected application method, system and medium for fixed network environment |
-
2023
- 2023-07-28 CN CN202310948474.8A patent/CN116800710A/en active Pending
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN118199991A (en) * | 2024-03-26 | 2024-06-14 | 北京英迪瑞讯网络科技有限公司 | Secure access protected application method, system and medium for fixed network environment |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP4303600B2 (en) | Connection setting mechanism between networks with different address areas | |
EP1410579B1 (en) | Method for configuring a computer network | |
US6480508B1 (en) | Router-based domain name system proxy agent using address translation | |
US8046452B2 (en) | Inter-network address translator that is separately addressable from address alias assignment process | |
US7046666B1 (en) | Method and apparatus for communicating between divergent networks using media access control communications | |
US7630374B2 (en) | Address translation method | |
US6581108B1 (en) | Managing multiple private data networks using network and payload address translation | |
CN101238453A (en) | Setting up a name resolution system for home-to-home communications | |
US9191317B2 (en) | Method and system for implementing interconnection between internet protocol version 4 network and new network | |
JPH07118717B2 (en) | Multi-protocol packet network configuration method | |
JP2003249942A (en) | Internet protocol address translator, home network system using the same, and communication method therefor | |
EP1579656A1 (en) | System and method for establishing communication between a client and a server in a heterogenous ip network | |
US20240430226A2 (en) | Method and Device for Obtaining an IP Address | |
CN103338151A (en) | Method of accessing private network server on public network client side, and router | |
CN110691150A (en) | SDN-based IPv4 and IPv6 interconnection method and system | |
US7764686B1 (en) | Migration to IPv6 using combination of globally significant and locally significant IPv4 addresses | |
EP1187426B1 (en) | Method for using a unique IP address in a private IP address domain | |
US7440466B2 (en) | Method, apparatus and system for accessing multiple nodes on a private network | |
CN116800710A (en) | Network communication system | |
JP3680499B2 (en) | IP network connection control apparatus with built-in DNS function | |
JPH11252172A (en) | Packet generation method, information processing apparatus having the function, and recording medium recording packet generation program | |
US20040153502A1 (en) | Enhanced DNS server | |
US20020065936A1 (en) | Multi-platform application | |
CN104935677B (en) | A NAT64 resource acquisition method and acquisition/allocation device | |
KR100355288B1 (en) | Apparatus and method for providing service server functionality to the hosts of a private network |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination |