NAT64 prefix allocation method, device and DNS64 device for IPv6 single stack network
By dynamically allocating NAT64 prefix and adopting distributed deployment methods, the problems of transmission delay and NAT64 device performance pressure in IPv6 single-stack network are solved, and low latency and efficient network access are achieved.
Patent Information
- Application Number
- CN202110279695.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-03-16
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2041-03-16
AI Technical Summary
The lack of a mechanism for assigning NAT64 prefix to users in the prior art, resulting in a long transmission delay in IPv6 single-stack network and a high performance pressure on NAT64 devices.
A method of NAT64 prefix allocation for IPv6 single-stack network is proposed. By obtaining the prefix and IPv4 addresses of the user terminal and the server to be accessed, NAT64 prefix is dynamically assigned to the user terminal, and A record is converted into AAAA records, and NAT64 is mitigated by distributed deployment. Equipment performance pressure.
By dynamically assigning NAT64 prefixes, user traffic is converted on closer NAT64 devices, reducing transmission delay, reducing performance pressure of NAT64 devices, and improving network access efficiency.
Smart Images

Figure CN115086273B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of data communication, and in particular to a NAT64 prefix allocation method, apparatus and DNS64 device for an IPv6 single stack network. Background Art
[0002] NAT (Network Address Translation) 64 / DNS (Domain Name System) 64 is an IPv6 single stack technology. The IPv6 single stack network no longer allocates IPv4 addresses to user terminals, but only allocates IPv6 addresses. In the case of only IPv6 addresses, it supports access to IPv6 services and IPv4 services (IPv4aaS). Generally, the terminal initiates a domain name resolution request to the DNS64 server. If the DNS64 server finds an AAAA record, it returns the record directly to the terminal, and the terminal accesses IPv6 applications on the Internet normally through the IPv6 network. If the DNS64 server finds an A record, the DNS uses the NAT64 prefix (the IPv6 prefix routed to the NAT64 device) and the A record to convert it into an AAAA record, and returns the converted AAAA record to the terminal. The IPv6 data stream of the terminal is routed to the NAT64 device, converted to an IPv4 data stream by NAT64, and accesses IPv4 applications on the Internet. However, in the existing technology, there is a lack of a mechanism for allocating NAT64 prefixes to users, resulting in a long transmission delay. Summary of the invention
[0003] A technical problem to be solved by the present disclosure is to provide a NAT64 prefix allocation method, device and DNS64 device for an IPv6 single stack network, which can alleviate the performance pressure of the NAT64 device and reduce the transmission delay.
[0004] According to one aspect of the present disclosure, a NAT64 prefix allocation method for an IPv6 single stack network is proposed, comprising: after performing domain name resolution on a domain name resolution request initiated by a user terminal, if an A record is queried, obtaining at least one of the prefix of the user terminal and the IPv4 address of the server to be accessed; and allocating a network address translation NAT64 prefix to the user terminal based on at least one of the prefix of the user terminal and the IPv4 address of the server to be accessed, so as to convert the A record into an AAAA record.
[0005] In some embodiments, the NAT64 device is deployed in a distributed manner and is deployed on the user plane function UPF side of the user terminal.
[0006] In some embodiments, a NAT64 prefix is allocated to a user terminal according to a priority of the user terminal.
[0007] In some embodiments, if the servers to be accessed by multiple user terminals are the same, a corresponding NAT64 prefix is determined according to the IPv4 address of the server to be accessed; and
[0008] The NAT64 prefix is allocated to the user terminal of the UPF where the NAT64 device corresponding to the NAT64 prefix is located.
[0009] In some embodiments, the correspondence between the prefix of the user terminal and the IPv4 address of the server and the NAT64 prefix is pre-saved.
[0010] According to another aspect of the present disclosure, a NAT64 prefix allocation device for an IPv6 single stack network is also proposed, comprising: a data acquisition unit, configured to perform domain name resolution on a domain name resolution request initiated by a user terminal, and if an A record is queried, obtain at least one of the prefix of the user terminal and the IPv4 address of the server to be accessed; and a prefix allocation unit, configured to allocate a network address translation NAT64 prefix to the user terminal based on at least one of the prefix of the user terminal and the IPv4 address of the server to be accessed, so as to convert the A record into an AAAA record.
[0011] In some embodiments, the NAT64 device is deployed in a distributed manner and is deployed on the user plane function UPF side of the user terminal.
[0012] In some embodiments, the prefix allocation unit is further configured to allocate a NAT64 prefix to the user terminal according to the priority of the user terminal.
[0013] According to another aspect of the present disclosure, a NAT64 prefix allocation device for an IPv6 single stack network is also proposed, comprising: a memory; and a processor coupled to the memory, the processor being configured to execute the NAT64 prefix allocation method as described above based on instructions stored in the memory.
[0014] According to another aspect of the present disclosure, a domain name system DNS64 device is also proposed, including: the above-mentioned NAT64 prefix allocation device.
[0015] According to another aspect of the present disclosure, a non-transitory computer-readable storage medium is also proposed, on which computer program instructions are stored, and when the instructions are executed by a processor, the above-mentioned NAT64 prefix allocation method is implemented.
[0016] In the disclosed embodiment, before the DNS64 device converts the A record into an AAAA record, two screening conditions, user prefix and server IPv4 address, are configured according to actual conditions, and a NAT64 prefix is allocated to the user terminal, so that user traffic is converted on a closer NAT64 device, which can reduce the performance pressure of the NAT64 device and reduce transmission delay.
[0017] Other features and advantages of the present disclosure will become apparent from the following detailed description of exemplary embodiments of the present disclosure with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] The accompanying drawings, which constitute a part of the specification, illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure.
[0019] The present disclosure may be more clearly understood from the following detailed description with reference to the accompanying drawings, in which:
[0020] Figure 1 The present invention is a flowchart of some embodiments of the method for allocating NAT64 prefixes in an IPv6 single stack network disclosed in the present invention.
[0021] Figure 2 This is a schematic diagram of the NAT64 device deployment disclosed in the present invention.
[0022] Figure 3 The present invention is a flowchart diagram of other embodiments of the method for allocating NAT64 prefixes in an IPv6 single stack network disclosed in the present invention.
[0023] Figure 4 It is a schematic diagram of the structure of some embodiments of the NAT64 prefix allocation device of the IPv6 single stack network disclosed in the present invention.
[0024] Figure 5 It is a schematic diagram of the structure of some other embodiments of the NAT64 prefix allocation device of the IPv6 single stack network disclosed in the present invention. DETAILED DESCRIPTION
[0025] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that the relative arrangement of components and steps, numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present disclosure unless otherwise specifically stated.
[0026] At the same time, it should be understood that for the convenience of description, the sizes of the various parts shown in the drawings are not drawn according to the actual proportional relationship.
[0027] The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the present disclosure, its application, or uses.
[0028] Technologies, methods, and apparatus known to ordinary technicians in the relevant field may not be discussed in detail, but where appropriate, such technologies, methods, and apparatus should be considered part of the authorization specification.
[0029] In all examples shown and discussed herein, any specific values should be interpreted as merely exemplary and not as limiting. Therefore, other examples of the exemplary embodiments may have different values.
[0030] It should be noted that like reference numerals and letters refer to similar items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.
[0031] In order to make the objectives, technical solutions and advantages of the present disclosure more clearly understood, the present disclosure is further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.
[0032] Figure 1 The flowchart of some embodiments of the NAT64 prefix allocation method for an IPv6 single stack network disclosed in the present invention is shown in FIG.
[0033] In step 110, after performing domain name resolution on the domain name resolution request initiated by the user terminal, if an A record is found, at least one of the prefix of the user terminal and the IPv4 address of the server to be accessed is obtained.
[0034] In step 120, a NAT64 prefix is allocated to the user terminal according to at least one of the prefix of the user terminal and the IPv4 address of the server to be accessed, so as to convert the A record into an AAAA record.
[0035] In some embodiments, a NAT64 prefix allocation module is added to the DNS64 device, and the module pre-stores the corresponding relationship between the prefix of the user terminal and the IPv4 address of the server and the NAT64 prefix. After receiving the domain name resolution request initiated by the user terminal and resolving the domain name, if an A record is found, the NAT64 prefix is allocated to the user terminal according to the prefix of the user terminal and the IPv4 address of the server to be accessed. See Table 1.
[0036] Table 1
[0037]
[0038] In some embodiments, assuming that a user with a user prefix of X accesses a server with a server IPv4 address of X_IPv4, the DNS64 device executes the following algorithm.
[0039] if (X's prefix = prefixA or X's accessed address = xxxx)
[0040] Assign a prefix of X = prefixa
[0041] else if (X's prefix = prefixB or X's accessed address = yyyy )
[0042] Assign X prefix = prefixb
[0043] . . .
[0044] . . .
[0045] . . .
[0046] else
[0047] Assign X prefix = prefix_all (default NAT64 server)
[0048] In the above embodiment, before the DNS64 device converts the A record into an AAAA record, two screening conditions, user prefix and server IPv4 address, are configured according to actual conditions, and a NAT64 prefix is allocated to the user terminal, so that user traffic is converted on a closer NAT64 device, which can reduce the performance pressure of the NAT64 device and reduce transmission delay.
[0049] In some embodiments of the present disclosure, Figure 2 As shown in the figure, NAT64 devices are deployed in a distributed manner, and are deployed near the UPF (User Plane Function) side of the user terminal. The DNS64 device allocates a NAT64 prefix to the user terminal based on the prefix of the user terminal and the IPv4 address of the server to be accessed, so that user traffic is converted on the nearest NAT64 device, thereby reducing transmission delay.
[0050] In addition, if the NAT64 device is deployed in a centralized manner, the DNS64 device sends the same NAT64 prefix to all users, so the synthesized traffic is all aggregated to the centrally deployed NAT64 device, which puts great pressure on the NAT64 device. In this embodiment, since the NAT64 device is deployed in a distributed manner, the performance pressure of the NAT device can be reduced.
[0051] In some embodiments, a NAT device with prefix a is set on the UPF side of user A, and a NAT device with prefix b is set on the UPF side of user B. User A wants to access a server with IPv4 address 1, and user B wants to access a server with IPv4 address 2. The server with IPv4 address 1 is closer to the NAT device with prefix a, and the server with IPv4 address 2 is closer to the NAT device with prefix b. Then, DNS64 assigns a NAT device prefix a to user A and b to user B.
[0052] In some embodiments, if the servers to be accessed by multiple user terminals are the same, the corresponding NAT64 prefix is determined based on the IPv4 address of the server to be accessed; and the NAT64 prefix is assigned to the user terminal of the UPF where the NAT64 device corresponding to the NAT64 prefix is located.
[0053] like Figure 2 As shown in the figure, if user A and user B want to access the same server, the IPv4 address of the server is closer to the NAT64 device with prefix a, and the NAT64 device is deployed on the UPF side of user A, when the DNS64 device allocates NAT64 prefixes to user A and user B, it will allocate NAT64 prefix a to user A and reselect the prefix of the NAT device deployed on the UPF side of user B to allocate to user B. By uniformly scheduling NAT64 traffic, users can be provided with a NAT64 traffic path with low latency.
[0054] In other embodiments of the present disclosure, a NAT64 prefix is allocated to a user terminal according to the priority of the user terminal. For example, if there is only one NAT64 prefix left that has not been allocated, but multiple users access the same server, and the server is at the same distance from the NAT64 device on the UPF side of each user, the NAT64 prefix is allocated to the user with a high priority.
[0055] Figure 3 The present invention is a flowchart diagram of other embodiments of the method for allocating NAT64 prefixes in an IPv6 single stack network disclosed in the present invention.
[0056] In step 310, the IPv6 terminal with prefix A initiates a domain name resolution request to the DNS64 device.
[0057] At step 320, the DNS64 device resolves the domain name.
[0058] In step 330 , it is determined whether it is an AAAA record according to the parsing result. If so, step 340 is executed; otherwise, step 360 is executed.
[0059] In step 340, the DNS64 device returns the AAAA record to the terminal normally.
[0060] In step 350, the terminal routes the data packet to the application server.
[0061] In step 360, the DNS64 device allocates a NAT64 prefix to the terminal according to the terminal prefix and the IPv4 address of the application server, converts the A record into an AAAA record, and returns the AAAA record to the terminal.
[0062] In step 370, the terminal routes the data packet to the NAT64 device corresponding to the NAT64 prefix, and the data packet reaches the IPv4 application server after the IPv6 to IPv4 address translation.
[0063] In the above embodiment, the NAT64 prefix is determined by the user prefix and the server IPv4 address, that is, different NAT64 prefixes are allocated to different users, which can provide a NAT64 traffic path with lower latency.
[0064] Figure 4 The structure diagram of some embodiments of the NAT64 prefix allocation device for the IPv6 single stack network disclosed in the present invention includes a data acquisition unit 410 and a prefix allocation unit 420.
[0065] The data acquisition unit 410 is configured to perform domain name resolution for the domain name resolution request initiated by the user terminal, and if an A record is found, obtain at least one of the prefix of the user terminal and the IPv4 address of the server to be accessed.
[0066] The prefix allocation unit 420 is configured to allocate a NAT64 prefix to the user terminal according to at least one of the prefix of the user terminal and the IPv4 address of the server to be accessed, so as to convert the A record into an AAAA record.
[0067] In some embodiments, the NAT64 device is deployed in a distributed manner on the UPF side of the user terminal. The DNS64 device allocates a NAT64 prefix to the user terminal according to the prefix of the user terminal and the IPv4 address of the server to be accessed, so that the user traffic is converted on a closer NAT64 device, thereby reducing the transmission delay. In addition, since the NAT64 device is deployed in a distributed manner, the performance pressure of the NAT device can be reduced.
[0068] In some embodiments, the prefix allocation unit 420 is further configured to allocate a NAT64 prefix to the user terminal according to the priority of the user terminal.
[0069] In some embodiments, the prefix allocation unit 420 is further configured to pre-save the corresponding relationship between the prefix of the user terminal and the IPv4 address of the server and the NAT64 prefix.
[0070] In some embodiments, the prefix allocation unit 420 is also configured to determine the corresponding NAT64 prefix based on the IPv4 address of the server to be accessed if the servers to be accessed by multiple user terminals are the same; and allocate the NAT64 prefix to the user terminal of the UPF where the NAT64 device corresponding to the NAT64 prefix is located.
[0071] In the above embodiment, before the DNS64 device converts the A record into an AAAA record, two screening conditions, user prefix and server IPv4 address, are configured according to actual conditions, and a NAT64 prefix is allocated to the user terminal, which can reduce the performance pressure of the NAT64 device and reduce transmission delay.
[0072] Figure 5 The following is a schematic diagram of the structure of some other embodiments of the NAT64 prefix allocation device for the IPv6 single stack network disclosed in the present invention. The device includes a memory 510 and a processor 520. The memory 510 may be a disk, a flash memory, or any other non-volatile storage medium. The memory 510 is used to store Figure 1 , 2 The processor 520 is coupled to the memory 510 and can be implemented as one or more integrated circuits, such as a microprocessor or a microcontroller. The processor 520 is used to execute the instructions stored in the memory.
[0073] In some embodiments, the processor 520 is coupled to the memory 510 via a BUS 530. The device 500 can also be connected to an external storage system 550 via a storage interface 540 to call external data, and can also be connected to a network or another computer system (not shown) via a network interface 560. No further detailed description will be given here.
[0074] In this embodiment, by storing data instructions in a memory and then processing the instructions through a processor, the performance pressure of the NAT64 device can be alleviated and the transmission delay can be reduced.
[0075] In some other embodiments of the present disclosure, a DNS64 device is protected, and the DNS64 device includes the NAT64 prefix allocation device in the above embodiment.
[0076] In some other embodiments, a computer readable storage medium stores computer program instructions, which when executed by a processor implement Figure 1 , 2 The steps of the method in the corresponding embodiment. Those skilled in the art should understand that the embodiments of the present disclosure can be provided as methods, devices, or computer program products. Therefore, the present disclosure can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present disclosure can take the form of a computer program product implemented on one or more computer-usable non-transient storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0077] The present disclosure is described with reference to flowcharts and / or block diagrams of methods, devices (systems) and computer program products according to embodiments of the present disclosure. It should be understood that each process and / or block in the flowchart and / or block diagram and the combination of processes and / or blocks in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0078] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0079] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0080] So far, the present disclosure has been described in detail. In order to avoid obscuring the concept of the present disclosure, some details known in the art are not described. Based on the above description, those skilled in the art can fully understand how to implement the technical solution disclosed here.
[0081] Although some specific embodiments of the present disclosure have been described in detail by way of example, it should be understood by those skilled in the art that the above examples are for illustration only and are not intended to limit the scope of the present disclosure. It should be understood by those skilled in the art that the above embodiments may be modified without departing from the scope and spirit of the present disclosure. The scope of the present disclosure is defined by the appended claims.
Claims
1. A NAT64 prefix allocation method for an IPv6 single stack network, include: Pre-save the corresponding relationship between the prefix of the user terminal and the IPv4 address of the server and the NAT64 prefix; After performing domain name resolution on the domain name resolution request initiated by the user terminal, if an A record is found, the prefix of the user terminal and the IPv4 address of the server to be accessed are obtained; as well as Determine a corresponding NAT64 prefix according to the prefix of the user terminal and the IPv4 address of the server to be accessed; The NAT64 prefix is allocated to the user terminal so as to convert the A record into an AAAA record.
2. The NAT64 prefix allocation method according to claim 1, in, NAT64 devices are deployed in a distributed manner on the user plane function (UPF) side of the user terminal.
3. The NAT64 prefix allocation method according to claim 1, further comprising: include: A NAT64 prefix is allocated to the user terminal according to the priority of the user terminal.
4. The NAT64 prefix allocation method according to claim 2, in, If the servers to be accessed by multiple user terminals are the same, the corresponding NAT64 prefix is determined according to the IPv4 address of the server to be accessed; as well as The NAT64 prefix is allocated to the user terminal of the UPF where the NAT64 device corresponding to the NAT64 prefix is located.
5. A NAT64 prefix allocation device for an IPv6 single stack network, include: A data acquisition unit is configured to perform domain name resolution on a domain name resolution request initiated by a user terminal, and if an A record is found, obtain the prefix of the user terminal and the IPv4 address of the server to be accessed, wherein a correspondence between the prefix of the user terminal and the IPv4 address of the server and a network address translation NAT64 prefix is pre-stored; and The prefix allocation unit is configured to determine a corresponding NAT64 prefix according to the prefix of the user terminal and the IPv4 address of the server to be accessed, and allocate the NAT64 prefix to the user terminal so as to convert the A record into an AAAA record.
6. The NAT64 prefix allocation device according to claim 5, in, NAT64 devices are deployed in a distributed manner on the user plane function (UPF) side of the user terminal.
7. The NAT64 prefix allocation device according to claim 5 or 6, in, The prefix allocation unit is further configured to allocate a NAT64 prefix to the user terminal according to the priority of the user terminal.
8. A NAT64 prefix allocation device for an IPv6 single stack network, include: Memory; as well as A processor coupled to the memory, wherein the processor is configured to execute the NAT64 prefix allocation method according to any one of claims 1 to 4 based on instructions stored in the memory.
9. A Domain Name System DNS64 device, include: The NAT64 prefix allocation device as described in any one of claims 5 to 8.
10. A non-transitory computer-readable storage medium having computer program instructions stored thereon, wherein the instructions, when executed by a processor, implement the NAT64 prefix allocation method according to any one of claims 1 to 4.
