CN114422469B - IPv4/IPv6 flow intelligent scheduling method, device and scheduling system - Google Patents

IPv4/IPv6 flow intelligent scheduling method, device and scheduling system Download PDF

Info

Publication number
CN114422469B
CN114422469B CN202210084531.8A CN202210084531A CN114422469B CN 114422469 B CN114422469 B CN 114422469B CN 202210084531 A CN202210084531 A CN 202210084531A CN 114422469 B CN114422469 B CN 114422469B
Authority
CN
China
Prior art keywords
address
record
dns
client
domain name
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.)
Active
Application number
CN202210084531.8A
Other languages
Chinese (zh)
Other versions
CN114422469A (en
Inventor
姜作毅
蒋明昊
王帅
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Tianwei Communication Technology Co ltd
Original Assignee
Beijing Tianwei Communication Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing Tianwei Communication Technology Co ltd filed Critical Beijing Tianwei Communication Technology Co ltd
Priority to CN202210084531.8A priority Critical patent/CN114422469B/en
Publication of CN114422469A publication Critical patent/CN114422469A/en
Application granted granted Critical
Publication of CN114422469B publication Critical patent/CN114422469B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types
    • H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/2521—Translation architectures other than single NAT servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The application relates to an IPv4/IPv6 flow intelligent dispatching method, a device and a dispatching system, wherein a client side accesses a server by adopting a domain name and initiates a domain name address resolution request to a uCPE, and the domain name address resolution request contains domain name address information; the uCPE receives the domain name address resolution request and forwards the domain name address resolution request to a DNS through the uCPE; DNS inquiry is carried out through a DNS server, an address record matched with the domain name address is obtained, and the address record is returned to the client; and the client receives the address record and enables the client to access the server according to the address record. The quality of different service addresses IPv4 and IPv6 can be intelligently evaluated through DNS service, and the optimal path is provided for the client; the IPv4 and the IPv6 are converted through the NAT, so that the single stack access can access the optimal path, and the barrier between the IPv4 protocol and the IPv6 protocol is opened.

Description

IPv4/IPv6 flow intelligent scheduling method, device and scheduling system
Technical Field
The disclosure relates to the technical field of information communication of the internet of things, in particular to an IPv4/IPv6 flow intelligent scheduling method, device and scheduling system.
Background
The combination of the IPv6 and the Internet of things makes the SD-WAN more attractive to enterprises, along with the rapid growth of the IPv6 scale, a v6 single stack access mode begins to appear, and the proposal of the Internet of things must simultaneously consider the IPv4 access mode and the IPv6 access mode so as to ensure smooth transition.
In this context, it is common practice in the prior art to provide dual stack access, where a client is assigned both v4 and v6 addresses, accessing the corresponding network via the a record and AAAA record provided by DNS, respectively. In this way, two networks are in a completely split state, and for a single-stack client, dual-stack network resources cannot be used, and optimized resources cannot be shared.
Disclosure of Invention
In view of this, the disclosure provides an intelligent scheduling method, device and scheduling system for IPv4/IPv6 traffic, so as to solve the above technical problems.
According to an aspect of the present disclosure, there is provided an IPv4/IPv6 traffic intelligent scheduling method, including the steps of:
s100, accessing a server by a client side through a domain name, and initiating a domain name address resolution request to a uCPE, wherein the domain name address resolution request contains domain name address information;
s200, the uCPE receives the domain name address resolution request and forwards the domain name address resolution request to a DNS through the uCPE;
s300, performing DNS inquiry through a DNS server, acquiring an address record matched with the domain name address, and returning to the client;
s400, the client receives the address record and enables the client to access the server according to the address record.
In a possible implementation manner, optionally, in step S100, the accessing, by the client, the server using the domain name, and initiating, to the cpe, a domain name address resolution request includes:
s101, judging the IP protocol type of the client to obtain a judging result;
s102, initiating a domain name address resolution request to uCPE according to a judging result, wherein the method comprises the following steps:
if the IP protocol type of the client is judged to be double stack, requesting an A record and an AAAA record from the uCPE at the same time;
if the IP protocol type of the client is judged to be an IPv4 single stack, requesting a record from the uCPE;
and if the IP protocol type of the client is judged to be the IPv6 single stack, requesting an AAAA record from the uCPE.
In a possible implementation manner, optionally, in step S300, the performing, by using a DNS server, a DNS query, obtaining an address record matching the domain name address, and returning to the client, where the step includes:
s301, the DNS server receives the domain name address resolution request and returns a DNS record;
s302, searching in a local temporary storage table by using the domain name address as a keyword by the uCPE to obtain a DNS record address matched with the domain name address;
s303, selecting a DNS record address with path quality meeting a preset quality threshold from the local temporary storage table, and sending the DNS record address to the uCPE.
In a possible implementation manner, optionally, in step S300, the performing, by using a DNS server, a DNS query, obtaining an address record matching the domain name address, and returning the address record to the client, and further includes:
s311, the uCPE obtains a path address matched with the IP protocol type of the client from the DNS record address meeting a preset quality threshold according to the IP protocol type of the client;
s312, returning the path address to the client through the uCPE in the DNS (domain name system).
In one possible implementation, optionally, the DNS record address includes: and the plurality of A record addresses and/or the plurality of AAAA record addresses, wherein the A record addresses are provided with IPv4 addresses obtained through NAT address conversion, and the AAAA record addresses are provided with IPv6 addresses obtained through NAT address conversion.
In a possible implementation manner, optionally, in step S400, the client receives the address record, and makes the client access the server according to the address record, including:
s401, the client accesses a server according to the path address and returns a DNS record to the uCPE;
s402, receiving the DNS record by the uCPE, and updating a DNS record address in the local temporary storage table according to the DNS record by the uCPE;
s403, based on NAT address conversion, the IPv4 address corresponding to the A record address and/or the IPv6 addresses corresponding to the AAAA record addresses are synchronously updated.
In a possible implementation manner, optionally, in step S300, the performing, by using a DNS server, a DNS query, obtaining an address record matching the domain name address, and returning the address record to the client, and further includes:
s321, the uCPE reads a DNS record address in the local temporary storage table;
s322, monitoring the path quality of the DNS record addresses one by one in real time according to preset path quality monitoring conditions, and obtaining a quality monitoring result;
and S323, updating the quality monitoring result to the local temporary storage table regularly.
According to another aspect of the present disclosure, there is provided an apparatus for implementing the intelligent scheduling method for IPv4/IPv6 traffic, including:
domain name address resolution request module: the system is used for accessing the server through the client by adopting the domain name and initiating a domain name address resolution request to the uCPE, wherein the domain name address resolution request contains domain name address information;
and a forwarding module: the method comprises the steps that the uCPE receives the domain name address resolution request and forwards the domain name address resolution request to a DNS through the uCPE;
DNS query module: the method comprises the steps of carrying out DNS inquiry through a DNS server, obtaining an address record matched with the domain name address, and returning to the client;
an address receiving module: and the client receives the address record and accesses the server according to the address record.
In one possible implementation, optionally, the method further includes:
an address reading module: the DNS record address in the local temporary storage table is read by the uCPE;
and a path quality monitoring module: the method is used for monitoring the path quality of the DNS record addresses one by one in real time according to preset path quality monitoring conditions, and obtaining quality monitoring results;
and an updating module: and the quality monitoring result is used for updating the local temporary storage table periodically.
According to another aspect of the present disclosure, there is also provided a scheduling system including:
a processor;
a memory for storing processor-executable instructions;
the processor is configured to implement the IPv4/IPv6 traffic intelligent scheduling method when executing the executable instructions.
The application has the technical effects that:
the method adopts a domain name access server through a client and initiates a domain name address resolution request to uCPE, wherein the domain name address resolution request contains domain name address information; the uCPE receives the domain name address resolution request and forwards the domain name address resolution request to a DNS through the uCPE; DNS inquiry is carried out through a DNS server, an address record matched with the domain name address is obtained, and the address record is returned to the client; and the client receives the address record and enables the client to access the server according to the address record. The method can be used for intelligently evaluating the quality of different service addresses IPv4 and IPv6 through the DNS on the one hand by combining the intelligent DNS service and an address translation (NAT) technology, and providing an optimal path for a client; on the other hand, through NAT, IPv4 and IPv6 are converted, so that the single stack access can access the optimal path, and the barrier between IPv4 and IPv6 protocols is opened.
For a single stack client, dual stack network resources can also be used; IPv4 and IPv6 resources are communicated, and the client can use an optimal path; converting the A record into an AAAA record through an address translation NAT technology, and converting the AAAA record into the A record; each path corresponding to the addresses of the A record and the AAAA record is monitored in real time, and the system knows which path is the optimal path at any time; through the two key points, the uCPE ensures that the uCPE becomes a local optimal DNS and directly provides analysis for the client.
Other features and aspects of the present disclosure will become apparent from the following detailed description of exemplary embodiments, which proceeds with reference to the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments, features and aspects of the present disclosure and together with the description, serve to explain the principles of the disclosure.
FIG. 1 is a schematic diagram of the flow chart of the intelligent scheduling method for IPv4/IPv6 traffic;
fig. 2 shows a timing diagram of the implementation of fig. 1 for the present application.
Detailed Description
Various exemplary embodiments, features and aspects of the disclosure will be described in detail below with reference to the drawings. In the drawings, like reference numbers indicate identical or functionally similar elements. Although various aspects of the embodiments are illustrated in the accompanying drawings, the drawings are not necessarily drawn to scale unless specifically indicated.
The word "exemplary" is used herein to mean "serving as an example, embodiment, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.
In addition, numerous specific details are set forth in the following detailed description in order to provide a better understanding of the present disclosure. It will be understood by those skilled in the art that the present disclosure may be practiced without some of these specific details. In some instances, methods, means, elements, and circuits well known to those skilled in the art have not been described in detail in order not to obscure the present disclosure.
Example 1
The application combines the intelligent DNS service and the address translation (NAT) technology, on one hand, the quality (including the indexes such as reachability, time delay, packet loss rate and the like) of different service addresses (IPv 4 and IPv 6) is intelligently evaluated through the DNS service, and the optimal path is provided for the client; on the other hand, through NAT, IPv4 and IPv6 are converted, so that the single stack access can access the optimal path, and the barrier between IPv4 and IPv6 protocols is opened.
As shown in fig. 1 and 2, according to an aspect of the present disclosure, there is provided an IPv4/IPv6 traffic intelligent scheduling method, including the steps of:
s100, accessing a server by a client side through a domain name, and initiating a domain name address resolution request to a uCPE, wherein the domain name address resolution request contains domain name address information;
the client uses domain name 'domain name com' to access the server, the client initiates a domain name address resolution request to the uCPE, and the corresponding domain name address resolution request content is different according to the different IP protocol types of the client.
In a possible implementation manner, optionally, in step S100, the accessing, by the client, the server using the domain name, and initiating, to the cpe, a domain name address resolution request includes:
s101, judging the IP protocol type of a client to obtain a judging result;
s102, initiating a domain name address resolution request to uCPE according to a judging result, wherein the method comprises the following steps: if the IP protocol type of the client is judged to be double stack, requesting an A record and an AAAA record from the uCPE at the same time; if the IP protocol type of the client is judged to be an IPv4 single stack, requesting a record from the uCPE; and if the IP protocol type of the client is judged to be the IPv6 single stack, requesting an AAAA record from the uCPE.
If the client is dual stack, request A record and AAAA record at the same time; if the client is an IPv4 single stack, only requesting A record; if the client is an IPv6 single stack, only the AAAA record is requested. Thus, for single stack clients, dual stack network resources can also be used.
S200, the uCPE receives the domain name address resolution request and forwards the domain name address resolution request to a DNS through the uCPE;
the uCPE forwards a domain name address resolution request of the client to the DNS, and simultaneously, the A record and the AAAA record are required to be acquired.
S300, performing DNS inquiry through a DNS server, acquiring an address record matched with the domain name address, and returning to the client;
the uCPE forwards the domain name address resolution request of the client to the DNS, and acquires the A record and the AAAA record according to the IP protocol type of the client. If the dual stack is adopted, requesting an A record and an AAAA record from the uCPE at the same time; if the IPv4 single stack is adopted, only the record A is requested; if the IPv6 single stack is adopted, only the AAAA record is requested.
The uCPE does not wait for a reply after sending a request to the DNS, but directly queries the local scratch pad.
In a possible implementation manner, optionally, in step S300, the performing, by using a DNS server, a DNS query, obtaining an address record matching the domain name address, and returning to the client, where the step includes:
s301, the DNS server receives the domain name address resolution request and returns a DNS record;
s302, searching in a local temporary storage table by using the domain name address as a keyword by the uCPE to obtain a DNS record address matched with the domain name address;
s303, selecting a DNS record address with path quality meeting a preset quality threshold from the local temporary storage table, and sending the DNS record address to the uCPE.
The DNS server receives the domain name address resolution request and returns DNS records, and a plurality of records are searched by taking the domain name com as a keyword, wherein the records are A records and AAAA records. And the retrieval and acquisition are specifically required according to the IP protocol type of the client.
In one possible implementation, optionally, the DNS record address includes: and the plurality of A record addresses and/or the plurality of AAAA record addresses, wherein the A record addresses are provided with IPv4 addresses obtained through NAT address conversion, and the AAAA record addresses are provided with IPv6 addresses obtained through NAT address conversion.
Based on NAT technology, IPv4 address 1.2.3.4 in record A has a corresponding translated IPv6 address AA: …:CC: …, and similarly IPv6 address CC:EE: …:FF: … in record AAAA also has a corresponding translated IPv4 address 5.6.7.8. The specific number is set according to the user.
As shown in fig. 2, a local temporary storage table is configured on the uCPE, and each "domain name.com" address in the local temporary storage table is provided with a corresponding a record, AAAA record, IPv4- > IPv6, IPv6- > IPv4 and path quality information. Based on NAT technology, the IPv4 address 1.2.3.4 in the record A has a corresponding converted IPv6 address AA, BB, …, CC …; likewise, the IPv6 address CC in the AAAA record is EE … FF …; there is also a corresponding translated IPv4 address 5.6.7.8. Each row of the table has a "path quality" field, which indicates the path quality of the address to which this DNS record corresponds, and the cpe will take the record with the best quality.
The quality threshold is that the record with the best quality is selected from the local temporary storage table to be judged. After the uCPE finds out the record with the best quality, the address of the path with the best quality is returned to the client in the name of DNS.
S400, the client receives the address record and enables the client to access the server according to the address record.
The client accesses the server through the best path provided by the uCPE, so that IPv4 and IPv6 resources are opened, and the client can use the best path to access the server, so that IPv4/IPv6 flow intelligent scheduling is realized in the SDWAN network.
In a possible implementation manner, optionally, in step S300, the performing, by using a DNS server, a DNS query, obtaining an address record matching the domain name address, and returning the address record to the client, and further includes:
s311, the uCPE obtains a path address matched with the IP protocol type of the client from the DNS record address meeting a preset quality threshold according to the IP protocol type of the client;
s312, returning the path address to the client through the uCPE in the DNS (domain name system).
And firstly, judging the domain name resolution type by the client IP protocol type. And obtaining a path address matched with the IP protocol type of the client from the DNS record addresses meeting a preset quality threshold.
The uCPE returns the address of the best path to the client on behalf of the DNS, and the returned DNS record is the same type as the client request, e.g., the client only requests the A record, and only returns the A record. In this example, the uCPE returns 1.2.3.4,4.5.6.7,1.2.3.5 three A records to the IPv4 single stack client.
The returned a record and AAAA record are not necessarily true DNS configurations, but may contain NAT translation results, such as AA: BB: …: CC address in this example, which is a result of translating 1.2.3.4 to the IPv4 address in the a record, and this IPv6 address will be packaged into AAAA record return. The client accesses the server through the best path provided by the uCPE, and also requires NAT technology on the uCPE to translate the address.
In a possible implementation manner, optionally, in step S400, the client receives the address record, and makes the client access the server according to the address record, including:
s401, the client accesses a server according to the path address and returns a DNS record to the uCPE;
s402, receiving the DNS record by the uCPE, and updating a DNS record address in the local temporary storage table according to the DNS record by the uCPE;
s403, based on NAT address conversion, the IPv4 address corresponding to the A record address and/or the IPv6 addresses corresponding to the AAAA record addresses are synchronously updated.
The DNS returns the true a record and AAAA record corresponding to the server domain name "domain name com", the ucoe will not forward the period back to the client, but will update the local temporary table according to the record returned by the DNS, and similarly, the NAT mechanism will be also replaced in the table by the IPv6 address corresponding to the full IPv4 address and the IPv4 address corresponding to the IPv6 address.
In a possible implementation manner, optionally, in step S300, the performing, by using a DNS server, a DNS query, obtaining an address record matching the domain name address, and returning the address record to the client, and further includes:
s321, the uCPE reads a DNS record address in the local temporary storage table;
s322, monitoring the path quality of the DNS record addresses one by one in real time according to preset path quality monitoring conditions, and obtaining a quality monitoring result;
and S323, updating the quality monitoring result to the local temporary storage table regularly.
In this embodiment, a module for continuously monitoring the quality of the server is built in the ucope, and the path quality of the DNS record address is monitored in real time. The quality of each path is monitored, one by one, in the form of ICMP ping, e.g. by reading the addresses in a temporary table. The latest path quality is updated into the temporary storage table periodically to ensure that the data is valid and up to date.
It should be noted that although the embodiment of the above return a record is described by taking an IPv4 single stack as an example, those skilled in the art will appreciate that the present disclosure should not be limited thereto. In fact, the user can flexibly set the client IP protocol type according to personal preference and/or practical application scenario, so long as the above embodiment principle is satisfied.
In this way, the application adopts the domain name access server through the client and initiates the domain name address resolution request to the uCPE, wherein the domain name address resolution request contains domain name address information; the uCPE receives the domain name address resolution request and forwards the domain name address resolution request to a DNS through the uCPE; DNS inquiry is carried out through a DNS server, an address record matched with the domain name address is obtained, and the address record is returned to the client; and the client receives the address record and enables the client to access the server according to the address record. The method can be used for intelligently evaluating the quality of different service addresses IPv4 and IPv6 through the DNS on the one hand by combining the intelligent DNS service and an address translation (NAT) technology, and providing an optimal path for a client; on the other hand, through NAT, IPv4 and IPv6 are converted, so that the single stack access can access the optimal path, and the barrier between IPv4 and IPv6 protocols is opened.
For a single stack client, dual stack network resources can also be used; IPv4 and IPv6 resources are communicated, and the client can use an optimal path; converting the A record into an AAAA record through an address translation NAT technology, and converting the AAAA record into the A record; each path corresponding to the addresses of the A record and the AAAA record is monitored in real time, and the system knows which path is the optimal path at any time; through the two key points, the uCPE ensures that the uCPE becomes a local optimal DNS and directly provides analysis for the client.
Example 2
Based on the implementation of embodiment 1, the present implementation correspondingly provides a device for implementing the intelligent scheduling method of IPv4/IPv6 traffic, including:
domain name address resolution request module: the system is used for accessing the server through the client by adopting the domain name and initiating a domain name address resolution request to the uCPE, wherein the domain name address resolution request contains domain name address information;
and a forwarding module: the method comprises the steps that the uCPE receives the domain name address resolution request and forwards the domain name address resolution request to a DNS through the uCPE;
DNS query module: the method comprises the steps of carrying out DNS inquiry through a DNS server, obtaining an address record matched with the domain name address, and returning to the client;
an address receiving module: and the client receives the address record and accesses the server according to the address record.
In one possible implementation, optionally, the method further includes:
an address reading module: the DNS record address in the local temporary storage table is read by the uCPE;
and a path quality monitoring module: the method is used for monitoring the path quality of the DNS record addresses one by one in real time according to preset path quality monitoring conditions, and obtaining quality monitoring results;
and an updating module: and the quality monitoring result is used for updating the quality monitoring result in the local temporary storage table periodically.
The functions of the modules of the above device and the interaction manner between the modules are specifically described with reference to embodiment 1, which is not repeated herein,
it will be appreciated by those skilled in the art that the modules or steps of the application described above may be implemented in a general purpose computing device, they may be centralized on a single computing device, or distributed over a network of computing devices, or they may alternatively be implemented in program code executable by computing devices, such that they may be stored in a memory device and executed by computing devices, or they may be separately fabricated as individual integrated circuit modules, or multiple modules or steps within them may be fabricated as a single integrated circuit module. Thus, the present application is not limited to any specific combination of hardware and software.
Example 3
Still further, according to another aspect of the present disclosure, there is also provided an I-scheduling system. According to another aspect of the present disclosure, there is also provided a scheduling system including:
a processor;
a memory for storing processor-executable instructions;
the processor is configured to implement the IPv4/IPv6 traffic intelligent scheduling method when executing the executable instructions.
The disclosed embodiment scheduling system includes a processor and a memory for storing processor-executable instructions. The processor is configured to implement any one of the above-described intelligent scheduling methods for IPv4/IPv6 traffic when executing the executable instructions.
Here, it should be noted that the number of processors may be one or more. Meanwhile, in the scheduling system of the embodiment of the disclosure, an input device and an output device may be further included. The processor, the memory, the input device, and the output device may be connected by a bus, or may be connected by other means, which is not specifically limited herein.
The memory is used as a computer readable storage medium for the intelligent scheduling method of IPv4/IPv6 flow, and can be used for storing software programs, computer executable programs and various modules, such as: a program or a module corresponding to an IPv4/IPv6 flow intelligent scheduling method in an embodiment of the disclosure. The processor executes various functional applications and data processing of the dispatch system by running software programs or modules stored in the memory.
The input device may be used to receive an input number or signal. Wherein the signal may be a key signal generated in connection with user settings of the device/terminal/server and function control. The output means may comprise a display device such as a display screen.
The foregoing description of the embodiments of the present disclosure has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the various embodiments described. The terminology used herein was chosen in order to best explain the principles of the embodiments, the practical application, or the technical improvement of the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims (6)

1. An IPv4/IPv6 flow intelligent scheduling method is characterized by comprising the following steps:
s100, accessing a server by a client side through a domain name, and initiating a domain name address resolution request to a uCPE, wherein the domain name address resolution request contains domain name address information;
s200, the uCPE receives the domain name address resolution request and forwards the domain name address resolution request to a DNS through the uCPE;
s300, performing DNS inquiry through a DNS server, acquiring an address record matched with the domain name address, and returning to the client;
s400, the client receives the address record and enables the client to access a server according to the address record;
in step S100, the accessing, by the client, the server using the domain name, and initiating a domain name address resolution request to the ucope, including:
s101, judging the IP protocol type of the client to obtain a judging result;
s102, initiating a domain name address resolution request to uCPE according to a judging result, wherein the method comprises the following steps:
if the IP protocol type of the client is judged to be double stack, requesting an A record and an AAAA record from the uCPE at the same time;
if the IP protocol type of the client is judged to be an IPv4 single stack, requesting a record from the uCPE;
if the IP protocol type of the client is judged to be IPv6 single stack, the uCPE is requested for an AAAA record
In step S300, the performing DNS query by the DNS server, obtaining an address record matched with the domain name address, and returning to the client, where the step includes:
s301, the DNS server receives the domain name address resolution request and returns a DNS record;
s302, searching in a local temporary storage table by using the domain name address as a keyword by the uCPE to obtain a DNS record address matched with the domain name address;
s303, selecting a DNS record address with path quality meeting a preset quality threshold from the local temporary storage table, and sending the DNS record address to the uCPE;
s311, the uCPE obtains a path address matched with the IP protocol type of the client from the DNS record address meeting a preset quality threshold according to the IP protocol type of the client;
s312, returning the path address to the client through the uCPE in the name of DNS;
a local temporary storage table is configured on the uCPE, and each domain name com address in the local temporary storage table is provided with a corresponding A record, an AAAA record, an IPv4, a corresponding IPv6, an IPv6, a corresponding IPv4 address and path quality information;
the quality threshold value is obtained by selecting the record with the best quality from the local temporary storage table as judgment; after the uCPE finds out the record with the best quality, returning the address of the path with the best quality to the client in the name of DNS;
the returned DNS record is the same type as the client request, contains the true DNS configuration, and also contains the NAT translation result.
2. The IPv4/IPv6 traffic intelligent scheduling method of claim 1, wherein the DNS record address comprises: and the plurality of A record addresses and/or the plurality of AAAA record addresses, wherein the A record addresses are provided with IPv4 addresses obtained through NAT address conversion, and the AAAA record addresses are provided with IPv6 addresses obtained through NAT address conversion.
3. The intelligent scheduling method for IPv4/IPv6 traffic according to claim 1, wherein in step S400, the client receives the address record, and causes the client to access a server according to the address record, comprising:
s401, the client accesses a server according to the path address and returns a DNS record to the uCPE;
s402, receiving the DNS record by the uCPE, and updating a DNS record address in the local temporary storage table according to the DNS record by the uCPE;
s403, based on NAT address conversion, the IPv4 address corresponding to the A record address and/or the IPv6 addresses corresponding to the AAAA record addresses are synchronously updated.
4. The intelligent scheduling method for IPv4/IPv6 traffic according to claim 1, wherein in step S300, the DNS query is performed by the DNS server, the address record matching the domain name address is obtained, and the address record is returned to the client, and further comprising:
s321, the uCPE reads a DNS record address in the local temporary storage table;
s322, monitoring the path quality of the DNS record addresses one by one in real time according to preset path quality monitoring conditions, and obtaining a quality monitoring result;
and S323, updating the quality monitoring result to the local temporary storage table regularly.
5. An apparatus for implementing the intelligent scheduling method of IPv4/IPv6 traffic according to any one of claims 1 to 4, comprising:
domain name address resolution request module: the system is used for accessing the server through the client by adopting the domain name and initiating a domain name address resolution request to the uCPE, wherein the domain name address resolution request contains domain name address information;
and a forwarding module: the method comprises the steps that the uCPE receives the domain name address resolution request and forwards the domain name address resolution request to a DNS through the uCPE;
DNS query module: the method comprises the steps of carrying out DNS inquiry through a DNS server, obtaining an address record matched with the domain name address, and returning to the client;
an address receiving module: the client is used for receiving the address records and accessing the server according to the address records;
an address reading module: the DNS record address in the local temporary storage table is read by the uCPE;
and a path quality monitoring module: the method is used for monitoring the path quality of the DNS record addresses one by one in real time according to preset path quality monitoring conditions, and obtaining quality monitoring results;
and an updating module: the quality monitoring result is used for updating the quality monitoring result in a local temporary storage table periodically;
the method comprises the following steps that a client side accesses a server by adopting a domain name and initiates a domain name address resolution request to a uCPE, and the method comprises the following steps:
s101, judging the IP protocol type of the client to obtain a judging result;
s102, initiating a domain name address resolution request to uCPE according to a judging result, wherein the method comprises the following steps:
if the IP protocol type of the client is judged to be double stack, requesting an A record and an AAAA record from the uCPE at the same time;
if the IP protocol type of the client is judged to be an IPv4 single stack, requesting a record from the uCPE;
if the IP protocol type of the client is judged to be IPv6 single stack, the uCPE is requested for an AAAA record
The DNS query is performed through a DNS server, an address record matched with the domain name address is obtained, and the address record is returned to the client, including the following steps:
s301, the DNS server receives the domain name address resolution request and returns a DNS record;
s302, searching in a local temporary storage table by using the domain name address as a keyword by the uCPE to obtain a DNS record address matched with the domain name address;
s303, selecting a DNS record address with path quality meeting a preset quality threshold from the local temporary storage table, and sending the DNS record address to the uCPE;
s311, the uCPE obtains a path address matched with the IP protocol type of the client from the DNS record address meeting a preset quality threshold according to the IP protocol type of the client;
s312, returning the path address to the client through the uCPE in the name of DNS; and is also provided with
A local temporary storage table is configured on the uCPE, and each domain name com address in the local temporary storage table is provided with a corresponding A record, an AAAA record, an IPv4, a corresponding IPv6, an IPv6, a corresponding IPv4 address and path quality information;
the quality threshold value is obtained by selecting the record with the best quality from the local temporary storage table as judgment; after the uCPE finds out the record with the best quality, returning the address of the path with the best quality to the client in the name of DNS;
the returned DNS record is of the same type as the client request, and is not necessarily a true DNS configuration, but may contain the results of NAT translation.
6. A scheduling system, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to implement the IPv4/IPv6 traffic intelligent scheduling method of any one of claims 1 to 4 when executing the executable instructions.
CN202210084531.8A 2022-01-25 2022-01-25 IPv4/IPv6 flow intelligent scheduling method, device and scheduling system Active CN114422469B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210084531.8A CN114422469B (en) 2022-01-25 2022-01-25 IPv4/IPv6 flow intelligent scheduling method, device and scheduling system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210084531.8A CN114422469B (en) 2022-01-25 2022-01-25 IPv4/IPv6 flow intelligent scheduling method, device and scheduling system

Publications (2)

Publication Number Publication Date
CN114422469A CN114422469A (en) 2022-04-29
CN114422469B true CN114422469B (en) 2023-10-24

Family

ID=81277833

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210084531.8A Active CN114422469B (en) 2022-01-25 2022-01-25 IPv4/IPv6 flow intelligent scheduling method, device and scheduling system

Country Status (1)

Country Link
CN (1) CN114422469B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115801730A (en) * 2022-11-28 2023-03-14 中国科学院信息工程研究所 IPv6 parser association discovery method and system

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102739810A (en) * 2011-04-07 2012-10-17 中国电信股份有限公司 IPv4CP/SP and IPv6 network interworking method and device
CN104079682A (en) * 2014-07-07 2014-10-01 中国联合网络通信集团有限公司 Address translation method and device based on domain name system (DNS)
CN104702707A (en) * 2013-12-06 2015-06-10 中国联合网络通信集团有限公司 Method and device for data processing
CN110784562A (en) * 2019-10-25 2020-02-11 新华三信息安全技术有限公司 Message forwarding method, domain name address query method, device, equipment and medium
CN111158864A (en) * 2019-12-31 2020-05-15 奇安信科技集团股份有限公司 Data processing method, device, system, medium, and program

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9894033B2 (en) * 2014-08-04 2018-02-13 Fortinet, Inc. DNS-enabled communication between heterogeneous devices
US11558342B2 (en) * 2019-09-27 2023-01-17 Samsung Electronics Co., Ltd. Method and device for performing asynchronous operations in a communication system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102739810A (en) * 2011-04-07 2012-10-17 中国电信股份有限公司 IPv4CP/SP and IPv6 network interworking method and device
CN104702707A (en) * 2013-12-06 2015-06-10 中国联合网络通信集团有限公司 Method and device for data processing
CN104079682A (en) * 2014-07-07 2014-10-01 中国联合网络通信集团有限公司 Address translation method and device based on domain name system (DNS)
CN110784562A (en) * 2019-10-25 2020-02-11 新华三信息安全技术有限公司 Message forwarding method, domain name address query method, device, equipment and medium
CN111158864A (en) * 2019-12-31 2020-05-15 奇安信科技集团股份有限公司 Data processing method, device, system, medium, and program

Also Published As

Publication number Publication date
CN114422469A (en) 2022-04-29

Similar Documents

Publication Publication Date Title
US10148612B2 (en) Method and system for increasing speed of domain name system resolution within a computing device
WO2017173766A1 (en) Domain name parsing acceleration method, system and apparatus
US7558880B2 (en) Dynamic DNS registration method, domain name solution method, DNS proxy server, and address translation device
US20070124487A1 (en) DNS server
JP2022551147A (en) Message transfer and domain name address query
CN109729187B (en) Proxy communication method, system, device and storage medium
US11323414B2 (en) Managing domain name system (DNS) record cache across multiple DNS servers using multicast communication
CN103141073A (en) Name-database server, name-resolution system, entry-search method, and entry-search program
CN112770408B (en) Log transmission method and device, computer equipment and storage medium
CN110225144A (en) Obtain and provide method, user equipment and the management server of service
CN114422469B (en) IPv4/IPv6 flow intelligent scheduling method, device and scheduling system
US6724724B1 (en) System and method for resolving an electronic address
CN115297088A (en) Domain name resolution system and method in cloud computing environment
CN109413224B (en) Message forwarding method and device
CN110677512B (en) Address resolution method and device
US7788407B1 (en) Apparatus and methods for providing an application level gateway for use in networks
CN114500456A (en) DNS scheduling optimization method and device based on full-network sniffing and computing equipment
KR100342107B1 (en) Methods for deciding Internet address groups distinguished by assigned organizations or locations and for resolving the geographical information for each address group, which are intended to set up Internet address supplementary system and its applications
CN102143207B (en) Content acquisition method and redirecting node
WO2002039699A1 (en) Domain name system extensions to support reverse proxy operations and layer-7 redirection
RU2726841C2 (en) Ip address conversion method, corresponding server and computer program
CN100454891C (en) IPv6/IPv4 converter
US20020133572A1 (en) Apparatus and method for providing domain name services to mainframe resource mapping
JP3834770B2 (en) Name resolution method and apparatus
KR20010035931A (en) System for Providing the Internet Address Supplementary Services and Method thereof

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
GR01 Patent grant
GR01 Patent grant