CN114745353A - Traffic scheduling method for IPv4 end to access IPv4/IPv6 network - Google Patents
Traffic scheduling method for IPv4 end to access IPv4/IPv6 network Download PDFInfo
- Publication number
- CN114745353A CN114745353A CN202210374961.3A CN202210374961A CN114745353A CN 114745353 A CN114745353 A CN 114745353A CN 202210374961 A CN202210374961 A CN 202210374961A CN 114745353 A CN114745353 A CN 114745353A
- Authority
- CN
- China
- Prior art keywords
- record
- ipv4
- ipv6
- domain name
- ipv
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 62
- 238000013519 translation Methods 0.000 claims abstract description 85
- 230000007246 mechanism Effects 0.000 claims abstract description 31
- 238000013507 mapping Methods 0.000 claims description 26
- 230000015654 memory Effects 0.000 claims description 10
- 230000000977 initiatory effect Effects 0.000 claims description 3
- 238000005516 engineering process Methods 0.000 description 10
- 238000005457 optimization Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 5
- 238000004590 computer program Methods 0.000 description 2
- 239000000470 constituent Substances 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000005259 measurement Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 241000282326 Felis catus Species 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000010845 search algorithm Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
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/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/251—Translation of Internet protocol [IP] addresses between different IP versions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
- H04L45/741—Routing in networks with a plurality of addressing schemes, e.g. with both IPv4 and IPv6
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
- H04L45/745—Address table lookup; Address filtering
-
- 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/255—Maintenance or indexing of mapping tables
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application relates to a traffic scheduling method for accessing an IPv4/IPv6 network by an IPv4 end, which comprises the steps of installing and configuring an IPv4/IPv6 translation gateway, and constructing a policy rule table queried by a longest domain name matching mechanism on the IPv4/IPv6 translation gateway; sending a DNS A record request to the IPv4/IPv6 translation gateway through an IPv4 client in an IPv4 network; the IPv4/IPv6 translation gateway receives the DNS A record request, selects an optimal A record from the DNS A record request according to a preset policy rule, and returns the optimal A record to the IPv4 client; the IPv4 client initiates IPv4 address access corresponding to the IPv 4A record according to the IPv 4A record. The method can realize control on different domain name access paths based on an intelligent strategy rule table of a longest domain name matching principle, and realize fine flow control.
Description
Technical Field
The present disclosure relates to the field of network communication technologies, and in particular, to a traffic scheduling method and apparatus for an IPv4 end to access an IPv4/IPv6 network, and a traffic scheduling system for an IPv4 end to access an IPv4/IPv6 network.
Background
With the development of internet technology, the IPv4 network protocol cannot meet the increasing network requirements due to the limitation of its address space, and a new network technology is imperative in order to break through the constraint brought by the IPv4 network protocol. In this context, the next generation internet protocol IPv6 was invented. As a core network protocol of the next generation internet, IPv6 has sufficient address space and advanced protocol characteristics, and has advantages of better security, optimized hierarchical addressing and routing mechanism, better end-to-end characteristics, better quality of service and mobility support, and the like. Therefore, the global deployment rate of IPv6 is increasing.
However, in many access networks, it is still difficult for users in these networks to access the resources in the IPv6 internet due to the fact that the stock equipment and infrastructure only support IPv4 (such as PON facilities/set-top boxes/optical cats). Since IPv4 and IPv6 are not compatible in address and protocol, in order to break through the above bottleneck, IPv4/IPv6 translation technology must be used to realize IPv4 network access to IPv6 internet.
IETF International standards RFC6144, RFC6052, RFC7915 define the framework of IPv4/IPv6 network layer translation technologies, address translation rules, and protocol translation rules, respectively. RFC6144 proposes in scene 2 (The IPv4 Internet to an IPv6 network), and needs a DNS46 technology to solve The problem that an IPv4 network accesses an IPv6 Internet. Subsequently, DNS46 for the IPv4/IPv6 Stateless Translator (https:// www.ietf.org/archive/id/draft-xli-beer-DNS 46-for-stage-07. txt) proposes the overall design scheme of DNS 46; in addition, patent publication No. CN109413227B, IPv4 user access IPv6 network interworking apparatus and device based on multiple IPv6 networks, proposes a DNS46 mapping algorithm for multiple uplink operators.
However, in actual deployment and application, many IPv6 servers are IPv4/IPv6 dual stack, and therefore, IPv4 users may access the servers through IPv6 outlets by translating IPv4/IPv 6; alternatively, instead of IPv4/IPv6 translation, the server is accessed through an IPv4 outlet. This requires the DNS46 translator to schedule. Whether an IPv4 outlet or an IPv6 outlet is used for a specific service is closely related to the load and price of the IPv4/IPv6 outlet of the IPv4 network, and also to the access quality of the service through the IPv4 outlet and the IPv6 outlet. In other words, IPv4 network operation and maintenance personnel need to flexibly and dynamically schedule the IPv4 traffic and the IPv6 traffic of the outlet by using a traffic scheduling technology applied to the DNS46, so as to optimize the use of resources such as IPv4/IPv6 outlet bandwidth; meanwhile, the optimal access of the user access service needs to be realized through dynamic monitoring of the access quality of IPv4/IPv6 of the target service.
However, none of the existing technologies mentioned above have a corresponding design and related mechanisms in terms of traffic scheduling. Specifically, in a scenario that an IPv4 client accesses an IPv4/IPv6 internet, the prior art cannot perform flexible IPv4/IPv6 traffic scheduling for the use condition of IPv4/IPv6 resources and the IPv4/IPv6 access quality of a current access service. For example, when an IPv4 outlet is congested, the corresponding service cannot be selected in a targeted manner to schedule its access to the IPv6 outlet, whereas when the IPv6 outlet is congested, the corresponding service cannot be selected in a targeted manner to schedule its access to the IPv4 outlet; an optimal IPv4/IPv6 traffic scheduling strategy cannot be formulated according to different prices of an IPv4 outlet and an IPv6 outlet; when the quality of service access of a certain IPv6 is poor, the access of other services cannot be switched to IPv4 in a targeted manner under the condition that the access of other services is not changed.
Disclosure of Invention
In order to solve the problems, the application provides a traffic scheduling method and a traffic scheduling device for an IPv4 end to access an IPv4/IPv6 network, and a traffic scheduling system for an IPv4 end to access an IPv4/IPv6 network, so that under the scene that an IPv4 client accesses an IPv4/IPv6 internet, according to the use condition of IPv4/IPv6 resources and the access quality of a currently accessed service IPv4/IPv6, an optimal DNS record is selected in real time and returned to an IPv4 user, and the scheduling of multiple operator IPv4/IPv6 outlets is supported, so that the policy-based IPv4/IPv6 traffic fine control and the optimization of the user access quality are realized.
On one hand, the application provides a traffic scheduling method for an IPv4 terminal to access an IPv4/IPv6 network, which comprises the following steps:
s100, installing and configuring an IPv4/IPv6 translation gateway, and constructing a policy rule table queried by a longest domain name matching mechanism on the IPv4/IPv6 translation gateway;
s200, sending a DNS A record request to the IPv4/IPv6 translation gateway through an IPv4 client in an IPv4 network;
s300, the IPv4/IPv6 translation gateway receives the DNS A record request, inquires the A record and the AAAA record of the specified domain name from the global DNS, and selects the optimal A record or the AAAA record according to the preset policy rule: if the record is A, the record is directly returned to the IPv4 client; if the record is AAAA record, the record is mapped into A record and then returned to the IPv4 client;
s400, the IPv4 client initiates IPv4 address access corresponding to the IPv 4A record according to the IPv 4A record.
As an optional implementation of this application, optionally, in step S100, the constructing a policy rule table queried by the longest domain name matching mechanism on the IPv4/IPv6 translation gateway includes:
s110, presetting a plurality of intelligent strategy rules based on the longest domain name matching principle;
s120, configuring the intelligent policy rules into the IPv4/IPv6 translation gateway;
s130, generating and storing a strategy rule table inquired by the longest domain name matching mechanism according to the intelligent strategy rule.
As an optional implementation of the present application, optionally, the longest domain name matching rule specifically includes:
if the domain name to be matched is completely matched with the domain name sets configured in the two or more intelligent strategy rules, comparing the character string lengths of the domain name ranges in the two or more intelligent strategy rules, and selecting the one with the longest character string length of the domain name range as the domain name matching mechanism query strategy rule which is preferentially used.
As an optional implementation of the present application, optionally, each of the constituent elements of the intelligent policy rule includes: "Domain name scope", "IPv 4/IPv6 priority" and "IPv 4/IPv6 next hop of preferred egress".
As an optional implementation of this application, optionally, in step S300, the IPv4/IPv6 translation gateway receives the DNS a record request, queries an a record and an AAAA record of a specified domain name from the global DNS system, and selects an optimal a record or an optimal AAAA record according to a preset policy rule: if the record is A, the record is directly returned to the IPv4 client; if the record is AAAA record, the record is mapped into A record and then returned to the IPv4 client, and the method comprises the following steps:
s310, inquiring the IPv 4A record and the IPv6 AAAA record of the target domain name from the global DNS through the IPv4/IPv6 translation gateway, and returning an inquiry result of the service domain name to be accessed;
s320, judging whether only IPv 4A records of the service domain name to be accessed exist or not according to the query result;
s330, if only the IPv 4A record of the service domain name to be accessed exists, directly returning the IPv 4A record to the IPv4 client.
As an optional implementation of this application, optionally, in step S300, the IPv4/IPv6 translation gateway receives the DNS a record request, queries an a record and an AAAA record of a specified domain name from the global DNS system, and selects an optimal a record or an optimal AAAA record according to preset policy rules: if the record is A, the record is directly returned to the IPv4 client; if the record is AAAA record, the record is mapped into A record and then returned to the IPv4 client, and the method comprises the following steps:
s310, inquiring the IPv 4A record and the IPv6 AAAA record of the target domain name from the global DNS through the IPv4/IPv6 translation gateway, and returning an inquiry result of the service domain name to be accessed;
s320, judging whether only IPv6 AAAA records of the service domain name to be accessed exist or not according to the query result;
s330, if only the IPv6 AAAA record of the service domain name to be accessed exists, mapping the IPv6 AAAA record into an IPv 4A record through a preset mapping algorithm, and returning the IPv 4A record to the IPv4 client.
As an optional implementation of this application, optionally, in step S300, the IPv4/IPv6 translation gateway receives the DNS a record request, queries an a record and an AAAA record of a specified domain name from the global DNS system, and selects an optimal a record or an optimal AAAA record according to preset policy rules: if the record is A, the record is directly returned to the IPv4 client; if the record is AAAA record, the record is mapped into A record and then returned to the IPv4 client, and the method comprises the following steps:
s310, inquiring the IPv 4A record and the IPv6 AAAA record of the target domain name from the global DNS through the IPv4/IPv6 translation gateway, and returning an inquiry result of the service domain name to be accessed;
s320, judging whether the IPv 4A record and the IPv6 AAAA record of the service domain name to be accessed exist or not according to the query result;
s330, if the IPv 4A record and the IPv6 AAAA record of the service domain name to be accessed exist, inquiring a policy rule table inquired by the longest domain name matching mechanism to obtain a policy with IPv4 priority or IPv6 priority:
if the IPv4 has priority, directly returning the original IPv 4A record to the IPv4 client;
if the IPv6 has priority, the IPv6 AAAA record is mapped into an IPv 4A record through a preset mapping algorithm, and the IPv 4A record is returned to the IPv4 client, and meanwhile, a corresponding IPv4/IPv6 address mapping table entry is established.
As an optional implementation of this application, optionally, in step S300, the IPv4/IPv6 translation gateway receives the DNS a record request, queries an a record and an AAAA record of a specified domain name from the global DNS system, and selects an optimal a record or an optimal AAAA record according to a preset policy rule: if the record is A, the record is directly returned to the IPv4 client; if the record is an AAAA record, the record is mapped into an A record and then returned to the IPv4 client, and the method further comprises the following steps:
s311, receiving the target address recorded by the IPv 4A record sent by the IPv4 client through the IPv4/IPv6 translation gateway;
s321, judging the type of the target address: an IPv4 address after IPv6 address translation or a native IPv4 address;
s331, if the address is the native IPv4 address, directly forwarding the message according to a preset routing path; if the address is the IPv4 address translated by the IPv6 address, the IPv4 address is mapped into a corresponding IPv6 address according to the IPv4/IPv6 address mapping table, and a routing table is searched to find an optimal outlet to send out the message.
In another aspect of the present application, a device for implementing the method for scheduling traffic of an IPv4 end accessing an IPv4/IPv6 network is provided, where the method includes:
the gateway configuration module is used for installing and configuring an IPv4/IPv6 translation gateway and constructing a policy rule table queried by a longest domain name matching mechanism on the IPv4/IPv6 translation gateway;
a DNS A record request module, which is used for sending a DNS A record request to the IPv4/IPv6 translation gateway through an IPv4 client in an IPv4 network;
an IPv4 a record query module, configured to receive the DNS a record request through the IPv4/IPv6 translation gateway, query an a record and an AAAA record of a specified domain name from a global DNS system, and select an optimal a record or an AAAA record from the records according to a preset policy rule: if the record is A, the record is directly returned to the IPv4 client; if the record is AAAA record, the record is mapped into A record and then returned to the IPv4 client;
the IPv4 client is used for receiving an IPv 4A record and initiating IPv4 address access corresponding to the IPv 4A record according to the IPv 4A record.
On the other hand, the application also provides a traffic scheduling system for accessing the IPv4/IPv6 network by the IPv4 terminal, including:
a processor;
a memory for storing processor-executable instructions;
the processor is configured to execute the executable instructions to implement the above-mentioned traffic scheduling method for the IPv4 end to access the IPv4/IPv6 network.
The invention has the technical effects that:
the method comprises the steps that an IPv4/IPv6 translation gateway is installed and configured, and a policy rule table queried by a longest domain name matching mechanism is built on the IPv4/IPv6 translation gateway; sending a DNS A record request to the IPv4/IPv6 translation gateway through an IPv4 client in an IPv4 network; the IPv4/IPv6 translation gateway receives the DNS A record request, inquires the A record and the AAAA record of the specified domain name from the global DNS, and selects the optimal A record or the AAAA record according to the preset policy rule: if the record is A, the record is directly returned to the IPv4 client; if the record is AAAA record, the record is mapped into A record and then returned to the IPv4 client; and the IPv4 client initiates IPv4 address access corresponding to the IPv 4A record according to the IPv 4A record. The access paths of different domain names can be controlled by constructing a uniform intelligent strategy rule table based on the longest domain name matching principle, and the optimal DNS record can be selected and returned to the IPv4 user under the condition that the IPv4 client accesses the IPv4/IPv6 Internet. Therefore, the IPv4/IPv6 traffic fine-grained management and control based on the policy can be realized. For example, when an IPv4 egress is congested, as large a traffic access as possible is configured to be IPv6 prioritized; when the IPv6 outlet is congested, configuring large-flow access as IPv4 priority as possible; under the scene that the IPv6 price is more favorable, the service with more mass flow can be configured as IPv6 priority.
By combining manual configuration and intelligent configuration, the method can realize the fine control of IPv4/IPv6 traffic based on the policy and the optimization of user access quality. Aiming at services with good and bad access quality or service faults or network faults, the algorithm can respond in time and switch the user access path to a high-quality link.
Under the scene of an upper-link multi-IPv 4/IPv6 outlet, the method supports the scheduling of a multi-operator IPv4/IPv6 mixed outlet, and also supports the realization of flexible optimized scheduling in a mode of combining manual configuration and intelligent configuration.
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 disclosure and, together with the description, serve to explain the principles of the disclosure.
FIG. 1 is a schematic flow chart illustrating an implementation of a traffic scheduling method for an IPv4 end to access an IPv4/IPv6 network according to the present invention;
fig. 2 is a schematic diagram showing an application system of the apparatus in embodiment 2 of the present invention.
Detailed Description
Various exemplary embodiments, features and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. In the drawings, like reference numbers can indicate functionally identical or similar elements. While the various aspects of the embodiments are presented in drawings, the drawings are not necessarily drawn to scale unless specifically indicated.
The word "exemplary" is used exclusively 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.
Furthermore, in the following detailed description, numerous specific details are set forth 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 that are well known to those skilled in the art have not been described in detail so as not to obscure the present disclosure.
The invention innovatively provides a flexible IPv4/IPv6 traffic scheduling algorithm, which can select an optimal DNS record in real time and return the optimal DNS record to an IPv4 user according to the use condition of IPv4/IPv6 resources and the IPv4/IPv6 access quality of current access service under the scene that an IPv4 client accesses an IPv4/IPv6 internet, and supports the scheduling of multiple operators IPv4/IPv6 outlets, thereby realizing the policy-based IPv4/IPv6 traffic fine control and the optimization of the user access quality.
The invention is based on DNS46 technology and route configuration, after IPv4/IPv6 translation gateway is installed and configured, a policy rule table queried by a longest domain name matching mechanism is configured on the IPv4/IPv6 translation gateway. The unified intelligent strategy rule table based on the longest domain name matching principle, namely the strategy rule table queried by the longest domain name matching mechanism, is constructed, so that the access paths of different domain names are controlled, and multi-IPv 4/IPv6 outlet optimization can be supported.
The longest domain name matching principle is as follows: for two different rules, if the domain name to be matched is matched with the domain name sets configured by the two rules, the length of the character string in the domain name range of the two rules is compared, and the longer length is preferred.
The policy rule table queried by the longest domain name matching mechanism is constructed in three ways:
(1) manually configuring default policy rules: the default rule refers to a rule matched only when other rules are not matched successfully, and corresponds to a rule followed by default by all domain names which are not configured specially. The default rule can be IPv6 preferred or IPv4 preferred, and can be flexibly switched, and has no influence on the configured policy of the specified domain name. In a multi-egress scenario, a default egress next hop may also be specified based thereon.
(2) Manually configuring policy rules for a particular domain name scope: for a certain specific domain name or a specific domain name range, a policy rule with IPv6 priority or IPv4 priority can be configured through a management interface, and a default next hop for export can be specified on the basis of the policy rule under the multi-export scene. Different domain name ranges can have cross or inclusion relations, and the algorithm can intelligently select by using the longest domain name matching principle.
(3) Intelligently configuring policy rules for a particular domain name: for the domain name list which needs to be accessed or is frequently accessed by the user, the preference determiner can determine the IPv4 priority or the IPv6 priority based on centralized or distributed real-time measurement and comparing the quality of the access through the IPv4 channel with the quality of the access through the IPv6 channel, and the preference determiner is configured in the policy rule table as a rule. Under the multi-outlet scene, the access quality of the IPv4/IPv6 address through different outlets can be measured, the optimal outlet is selected, and the next hop address is configured in the rule table entry. Measured metrics may include, but are not limited to: ICMP latency/ICMP packet loss/HTTP latency/HTTP bandwidth, etc.
Example 1
As shown in fig. 1, in one aspect of the present application, a traffic scheduling method for an IPv4 end to access an IPv4/IPv6 network is provided, including the following steps:
s100, installing and configuring an IPv4/IPv6 translation gateway, and constructing a policy rule table queried by a longest domain name matching mechanism on the IPv4/IPv6 translation gateway;
according to the three ways of constructing the policy rule table queried by the longest domain name matching mechanism, in specific implementation, the following configuration is firstly carried out: and selecting a mode of manually configuring default policy rules, setting configuration rules and configuring the configuration rules to the IPv4/IPv6 translation gateway, wherein the default IPv6 priority or IPv4 priority is included, and in a multi-outlet scene, a default outlet next hop can be designated on the basis. Wherein, in each constructed policy rule, if there is a situation of multiple outlets of the upper-link IPv4/IPv6, the outlet is optimized by configuring a corresponding detailed route.
In the alternative, the following two ways may be selected:
mode (1), manually configuring the policy rule of the specific domain name scope, and manually configuring the specific domain name rule policy according to the known information and experience. For example, when an IPv4 egress is congested, as large a traffic access as possible is configured to be IPv6 prioritized; when an IPv6 outlet is congested, configuring large-flow access as priority as IPv4 as possible; under the condition that the IPv6 price is relatively preferential, more large-flow services can be configured to be IPv6 preferred; for the known services with poor IPv6 access quality, the manual configuration is that IPv4 takes precedence. If there is a case of multiple outlets of the upper-linked IPv4/IPv6, the next-hop address of the optimal outlet can be configured in the above rule.
The method (2) intelligently configures the policy rule of a specific domain name, compares the access quality of accessing the target domain name through each IPv4 outlet passage and each IPv6 outlet passage by centralized or distributed real-time measurement aiming at the specific specified domain name or the access target domain name occurring in real time, dynamically configures IPv4 priority or IPv6 priority, and can configure the next hop address of the optimal outlet in the rule if the uplink IPv4/IPv6 multi-outlet exists.
Similarly, if the mode (1) or the mode (2) is adopted, in each constructed policy rule, if the uplink IPv4/IPv6 has multiple exits, the corresponding detailed route is configured to optimize the exit.
By adopting the configuration mode, the mode of combining manual configuration and intelligent configuration can realize the policy-based IPv4/IPv6 flow fine control and the optimization of user access quality. Aiming at services with good and bad access quality or service faults or network faults, the algorithm can respond in time and switch the user access path to a high-quality link. Under the scene of multi-IPv 4/IPv6 outlets in the upper link, the scheduling of multi-operator IPv4/IPv6 mixed outlets is supported, and flexible optimized scheduling is realized in a mode of combining manual configuration and intelligent configuration.
S200, sending a DNS A record request to the IPv4/IPv6 translation gateway through an IPv4 client in an IPv4 network;
s300, the IPv4/IPv6 translation gateway receives the DNS A record request, inquires the A record and the AAAA record of the specified domain name from the global DNS system, and selects the optimal A record or the optimal AAAA record according to the preset policy rule: if the record is A, the record is directly returned to the IPv4 client; if the record is AAAA record, the record is mapped into A record and then returned to the IPv4 client;
after the IPv4/IPv6 translation gateway receives the DNS A record request, the translation gateway firstly queries the IPv 4A record and the IPv6 AAAA record of the target domain name from the global DNS, queries and obtains the IPv 4A record through a preset judgment mode, and returns the record to the user.
S400, the IPv4 client initiates IPv4 address access corresponding to the IPv 4A record according to the IPv 4A record.
At this time, the IPv4 client initiates access to the IPv4 address corresponding to the DNS a record obtained accordingly. The method is characterized in that an intelligent strategy rule table based on the longest domain name matching principle realizes control on access paths of different domain names, and can select an optimal DNS record and return the DNS record to an IPv4 user under the scene that an IPv4 client accesses an IPv4/IPv6 internet. Therefore, the IPv4/IPv6 traffic fine-grained management and control based on the policy can be realized.
Wherein, in the process of constructing the rule table:
in the above method for constructing the rule table, the manual configuration policy rule and the intelligent configuration policy rule are optional operations except for default rule configuration;
the search algorithm for the longest domain name matching can use any algorithm, and is not limited;
the upper layer operation interface and the operation mode of the intelligent strategy rule table are not limited;
the mode of the intelligent configuration policy rule is not limited;
the algorithm for mapping the AAAA record into the A record is not limited;
the details of the implementation of the translation gateway configuration interface, the deployment location of the translation gateway device, and the like are not limited in the present invention.
As an optional implementation of this application, optionally, in step S100, the constructing a policy rule table queried by the longest domain name matching mechanism on the IPv4/IPv6 translation gateway includes:
s110, presetting a plurality of intelligent strategy rules based on the longest domain name matching principle;
s120, configuring the intelligent strategy rules into the IPv4/IPv6 translation gateway;
s130, generating and storing a strategy rule table inquired by the longest domain name matching mechanism according to the intelligent strategy rule.
The strategy rule table inquired by the longest domain name matching mechanism consists of any two or more than two of the above manually configured default strategy rules, the manually configured strategy rules with the specific domain name range and the intelligently configured strategy rules with the specific domain name. And configuring the determined and selected rules into the IPv4/IPv6 translation gateway, generating a policy rule table queried by a longest domain name matching mechanism according to the rules, and storing the policy rule table in the IPv4/IPv6 translation gateway.
As an optional implementation of the present application, optionally, the longest domain name matching rule specifically includes:
if the domain name to be matched is completely matched with the domain name sets configured in the two or more intelligent strategy rules, comparing the character string lengths of the domain name ranges in the two or more intelligent strategy rules, and selecting the one with the longest character string length of the domain name range as the domain name matching mechanism query strategy rule which is preferentially used.
And inquiring the matched address by the longest domain name matching principle, and for two or more different rules, if the domain name to be matched is completely matched with the domain name sets configured by the rules, comparing the character string lengths of the domain name ranges of the rules, and preferentially matching the domain name with longer length. The optimal DNS record is selected and returned to the IPv4 user. Therefore, the IPv4/IPv6 traffic fine-grained management and control based on the policy can be realized. For example, when an IPv4 egress is congested, as large a traffic access as possible is configured to be IPv6 prioritized; when the IPv6 outlet is congested, configuring large-flow access as IPv4 priority as possible; under the condition that the IPv6 price is relatively preferential, the service with more mass flow can be configured as IPv6 priority.
And the method can also support the scheduling of a multi-operator IPv4/IPv6 mixed outlet under the scene of multi-IPv 4/IPv6 outlets in an upper link, and also support the realization of flexible optimized scheduling in a mode of combining manual configuration and intelligent configuration.
As an optional implementation of the present application, optionally, each of the constituent elements of the intelligent policy rule includes: "domain name scope", "IPv 4/IPv6 precedence" and "IPv 4/IPv6 next hop of precedence egress".
Each intelligent policy rule in the rule table consists of (domain name scope, IPv4/IPv6 takes precedence, IPv4/IPv6 next hop takes precedence). The rule table may consist of any number of rules. When a terminal user initiates a DNS A request, the algorithm firstly queries IPv 4A records and IPv6 AAAA records of a target domain name from a global DNS system, and if both the IPv 4A records and the IPv6 AAAA records exist, a policy rule table queried by a longest domain name matching mechanism is used for querying a policy with IPv4 priority or IPv6 priority. If the IPv4 has priority, directly returning the original A record to the user; if the IPv6 has priority, the AAAA record is mapped into the A record through a certain mapping algorithm and returned to the user, and meanwhile, the mapping relation of the corresponding IPv4/IPv6 addresses is established.
After the IPv4/IPv6 translation gateway receives the DNS a record request, the translation gateway first queries the global DNS system for the IPv4 a record and the IPv6 AAAA record of the target domain name, which has the following three cases:
the first method comprises the following steps:
as an optional implementation of this application, optionally, in step S300, the IPv4/IPv6 translation gateway receives the DNS a record request, queries an a record and an AAAA record of a specified domain name from the global DNS system, and selects an optimal a record or an optimal AAAA record according to a preset policy rule: if the record is A, the record is directly returned to the IPv4 client; if the record is AAAA record, the record is mapped into A record and then returned to the IPv4 client, and the method comprises the following steps:
s310, inquiring the IPv 4A record and the IPv6 AAAA record of the target domain name from the global DNS through the IPv4/IPv6 translation gateway, and returning an inquiry result of the service domain name to be accessed;
s320, judging whether only IPv 4A records of the service domain name to be accessed exist or not according to the query result;
s330, if only the IPv 4A record of the service domain name to be accessed exists, directly returning the IPv 4A record to the IPv4 client.
When the IPv 4A record of only the service domain name to be accessed is found to exist, the IPv4 client is directly returned to.
And the second method comprises the following steps:
as an optional implementation of this application, optionally, in step S300, the IPv4/IPv6 translation gateway receives the DNS a record request, queries an a record and an AAAA record of a specified domain name from the global DNS system, and selects an optimal a record or an optimal AAAA record according to a preset policy rule: if the record is A, the record is directly returned to the IPv4 client; if the record is AAAA record, the record is mapped into A record and then returned to the IPv4 client, and the method comprises the following steps:
s310, inquiring the IPv 4A record and the IPv6 AAAA record of the target domain name from the global DNS through the IPv4/IPv6 translation gateway, and returning an inquiry result of the service domain name to be accessed;
s320, judging whether only IPv6 AAAA records of the service domain name to be accessed exist or not according to the query result;
s330, if only the IPv6 AAAA record of the service domain name to be accessed exists, mapping the IPv6 AAAA record into an IPv 4A record through a preset mapping algorithm, and returning the IPv 4A record to the IPv4 client.
When finding that only IPv6 AAAA records of the service domain name to be accessed exist, mapping the records into IPv 4A records through a certain preset mapping algorithm, and returning the IPv 3556 records to the IPv4 client.
And the third is that:
as an optional implementation of this application, optionally, in step S300, the IPv4/IPv6 translation gateway receives the DNS a record request, queries an a record and an AAAA record of a specified domain name from the global DNS system, and selects an optimal a record or an optimal AAAA record according to preset policy rules: if the record is A, the record is directly returned to the IPv4 client; if the record is the AAAA record, the record is mapped into an A record and then returned to the IPv4 client, and the method comprises the following steps:
s310, inquiring the IPv 4A record and the IPv6 AAAA record of the target domain name from the global DNS through the IPv4/IPv6 translation gateway, and returning an inquiry result of the service domain name to be accessed;
s320, judging whether the IPv 4A record and the IPv6 AAAA record of the service domain name to be accessed exist or not according to the query result;
s330, if the IPv 4A record and the IPv6 AAAA record of the service domain name to be accessed exist, inquiring a policy rule table inquired by the longest domain name matching mechanism to obtain a policy with IPv4 priority or IPv6 priority:
if the IPv4 has priority, directly returning the original IPv 4A record to the IPv4 client;
if the IPv6 has priority, the IPv6 AAAA record is mapped into an IPv 4A record through a preset mapping algorithm, the IPv 4A record is returned to the IPv4 client, and meanwhile, a corresponding IPv4/IPv6 address mapping table entry is established.
When the IPv 4A record and the IPv6 AAAA record of the service domain name to be accessed exist, inquiring the strategy of IPv4 priority or IPv6 priority by using a strategy rule table inquired by a longest domain name matching mechanism. If the IPv4 has priority, directly returning to the original IPv 4A record of the user; if the IPv6 has priority, the AAAA record is mapped into an IPv 4A record through a certain preset mapping algorithm, the record is returned to the user, and meanwhile, a mapping table item of a corresponding IPv4/IPv6 address is established.
After the judgment is completed according to the three situations, the IPv4 client needs to specifically determine the destination address according to the received IPv4 a record type, and then send the message to the user end.
As an optional implementation of this application, optionally, in step S300, the IPv4/IPv6 translation gateway receives the DNS a record request, queries an a record and an AAAA record of a specified domain name from the global DNS system, and selects an optimal a record or an optimal AAAA record according to a preset policy rule: if the record is A, the record is directly returned to the IPv4 client; if the record is an AAAA record, the record is mapped into an A record and then returned to the IPv4 client, and the method further comprises the following steps:
s311, receiving the target address recorded by the IPv 4A record sent by the IPv4 client through the IPv4/IPv6 translation gateway;
s321, judging the type of the target address: an IPv4 address after IPv6 address translation or a native IPv4 address;
s331, if the address is the native IPv4 address, directly forwarding the message according to a preset routing path; if the address is the IPv4 address after the IPv6 address translation, the IPv4 address is mapped into a corresponding IPv6 address according to the IPv4/IPv6 address mapping table entry, and a routing table is searched to find an optimal outlet to send out the message.
When the IPv4/IPv6 translation gateway receives a request sent by an IPv4 client, firstly, whether a target address is an IPv4 address after IPv6 address translation or a native IPv4 address is judged. If the address is the native IPv4 address, directly forwarding according to the route; if the address is the translated address, mapping the address to a corresponding IPv6 address according to the generated IPv4/IPv6 address mapping table entry, searching a routing table to find an optimal outlet, and sending the message.
Therefore, under the scene that an IPv4 client accesses an IPv4/IPv6 internet, the technology can select the optimal DNS record in real time and return the DNS record to an IPv4 user according to the use condition of IPv4/IPv6 resources and the IPv4/IPv6 access quality of the current access service, and support the dispatching of multiple operator IPv4/IPv6 outlets, so that the policy-based IPv4/IPv6 flow fine control and the optimization of user access quality are realized.
It should be noted that although the above-mentioned two configurations, manual and intelligent, are described as examples, those skilled in the art will appreciate that the present disclosure should not be limited thereto. In fact, the user can flexibly set rule construction conditions of the longest domain name matching mechanism query strategy according to actual application scenarios, as long as the IPv4/IPv6 traffic scheduling can be realized according to the technical method.
Example 2
Based on the implementation principle of embodiment 1, as shown in fig. 2, another aspect of the present application provides an apparatus for implementing the method for scheduling traffic of an IPv4 end accessing an IPv4/IPv6 network, where the method includes:
the gateway configuration module is used for installing and configuring an IPv4/IPv6 translation gateway and constructing a policy rule table queried by a longest domain name matching mechanism on the IPv4/IPv6 translation gateway;
a DNS A record request module, which is used for sending a DNS A record request to the IPv4/IPv6 translation gateway through an IPv4 client in an IPv4 network;
an IPv4 a record query module, configured to receive the DNS a record request through the IPv4/IPv6 translation gateway, query an a record and an AAAA record of a specified domain name from a global DNS system, and select an optimal a record or AAAA record from the a record or the AAAA record according to a preset policy rule: if the record is A, the record is directly returned to the IPv4 client; if the record is AAAA record, the record is mapped into A record and then returned to the IPv4 client;
the IPv4 client is used for receiving an IPv 4A record and initiating IPv4 address access corresponding to the IPv 4A record according to the IPv 4A record.
On the other hand, the application provides a traffic scheduling method and device for an IPv4 end to access an IPv4/IPv6 network,
it should be apparent to those skilled in the art that all or part of the processes of the methods of the above embodiments may be implemented by hardware related to instructions of a computer program, and the program may be stored in a computer readable storage medium, and when executed, may include the processes of the embodiments of the control methods as described above. The modules or steps of the invention described above can be implemented by a general purpose computing device, they can be centralized on a single computing device or distributed over a network of multiple computing devices, and they can alternatively be implemented by program code executable by a computing device, so that they can be stored in a storage device and executed by a computing device, or they can be separately fabricated into various integrated circuit modules, or multiple modules or steps thereof can be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
It will be understood by those skilled in the art that all or part of the processes of the methods of the above embodiments may be implemented by hardware related to instructions of a computer program, and the program may be stored in a computer readable storage medium, and when executed, may include the processes of the embodiments of the control methods as described above. The storage medium may be a magnetic disk, an optical disk, a Read-only memory (ROM), a Random Access Memory (RAM), a flash memory (FlashMemory), a hard disk (hard disk drive, abbreviated as HDD) or a Solid State Drive (SSD), etc.; the storage medium may also comprise a combination of memories of the kind described above.
Example 3
Still further, according to another aspect of the present disclosure, the present application further provides a traffic scheduling system for an IPv4 end to access an IPv4/IPv6 network, including:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to execute the executable instructions to implement the above-mentioned traffic scheduling method for the IPv4 end to access the IPv4/IPv6 network.
The traffic scheduling system for IPv4 end access to IPv4/IPv6 network in the embodiment of the disclosure comprises a processor and a memory for storing executable instructions of the processor. The processor is configured to execute the executable instructions to implement any one of the aforementioned traffic scheduling methods for the IPv4 end to access the IPv4/IPv6 network.
Here, it should be noted that the number of processors may be one or more. Meanwhile, the traceability system of the embodiment of the disclosure can further include an input device and an output device. The processor, the memory, the input device, and the output device may be connected by a bus, or may be connected by other means, and are not limited specifically herein.
The memory, which is a computer-readable storage medium, may be used to store software programs, computer-executable programs, and various modules, such as: the embodiment of the disclosure provides a program or a module corresponding to a traffic scheduling method for an IPv4 end to access an IPv4/IPv6 network. The processor executes various functional applications and data processing of the traceability 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 and function control of the device/terminal/server. The output means may comprise a display device such as a display screen.
Having described embodiments of the present disclosure, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terms used herein were chosen in order to best explain the principles of the embodiments, the practical application, or technical improvements to the techniques in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
Claims (10)
1. A traffic scheduling method for IPv4 end to access IPv4/IPv6 network is characterized by comprising the following steps:
s100, installing and configuring an IPv4/IPv6 translation gateway, and constructing a policy rule table queried by a longest domain name matching mechanism on the IPv4/IPv6 translation gateway;
s200, sending a DNS A record request to the IPv4/IPv6 translation gateway through an IPv4 client in an IPv4 network;
s300, the IPv4/IPv6 translation gateway receives the DNS A record request, inquires the A record and the AAAA record of the specified domain name from the global DNS, and selects the optimal A record or the AAAA record according to the preset policy rule: if the record is A, the record is directly returned to the IPv4 client; if the record is AAAA record, the record is mapped into A record and then returned to the IPv4 client;
s400, the IPv4 client initiates IPv4 address access corresponding to the IPv 4A record according to the IPv 4A record: the IPv4/IPv6 translation gateway queries a corresponding IPv4 address, and if the address is an IPv4 address corresponding to the A record after AAAA record mapping, the IPv4 message is translated into an IPv6 message and sent out; otherwise, forwarding the IPv4 message directly.
2. The method for traffic scheduling according to claim 1, where in step S100, the IPv4 peer accesses an IPv4/IPv6 network, where the method for constructing a policy rule table queried by a longest domain name matching mechanism on the IPv4/IPv6 translation gateway includes:
s110, presetting a plurality of intelligent strategy rules based on the longest domain name matching principle;
s120, configuring the intelligent policy rules into the IPv4/IPv6 translation gateway;
s130, generating and storing a strategy rule table inquired by the longest domain name matching mechanism according to the intelligent strategy rule.
3. The traffic scheduling method for IPv 4-end access to IPv4/IPv6 network according to claim 2, wherein the longest domain name matching rule specifically is:
if the domain name to be matched is completely matched with the domain name sets configured in the two or more intelligent strategy rules, comparing the character string lengths of the domain name ranges in the two or more intelligent strategy rules, and selecting the one with the longest character string length of the domain name range as the domain name matching mechanism query strategy rule which is preferentially used.
4. The method for traffic scheduling according to claim 2, where the IPv4 terminal accesses an IPv4/IPv6 network, and where the components of each intelligent policy rule include: "Domain name scope", "IPv 4/IPv6 priority" and "IPv 4/IPv6 next hop of preferred egress".
5. The traffic scheduling method for IPv4 peer access to IPv4/IPv6 network according to claim 1, wherein in step S300, the IPv4/IPv6 translation gateway receives the DNS a record request, queries an a record and an AAAA record of a specified domain name from a global DNS system, and selects an optimal a record or AAAA record from them according to a preset policy rule: if the record is A, the record is directly returned to the IPv4 client; if the record is AAAA record, the record is mapped into A record and then returned to the IPv4 client, and the method comprises the following steps:
s310, inquiring the IPv 4A record and the IPv6 AAAA record of the target domain name from the global DNS through the IPv4/IPv6 translation gateway, and returning an inquiry result of the service domain name to be accessed;
s320, judging whether only IPv 4A records of the service domain name to be accessed exist or not according to the query result;
s330, if only the IPv 4A record of the service domain name to be accessed exists, directly returning the IPv 4A record to the IPv4 client.
6. The traffic scheduling method for IPv4 peer access to IPv4/IPv6 network according to claim 1, wherein in step S300, the IPv4/IPv6 translation gateway receives the DNS a record request, queries an a record and an AAAA record of a specified domain name from a global DNS system, and selects an optimal a record or AAAA record from them according to a preset policy rule: if the record is A, the record is directly returned to the IPv4 client; if the record is AAAA record, the record is mapped into A record and then returned to the IPv4 client, and the method comprises the following steps:
s310, inquiring the IPv 4A record and the IPv6 AAAA record of the target domain name from the global DNS through the IPv4/IPv6 translation gateway, and returning an inquiry result of the service domain name to be accessed;
s320, judging whether only IPv6 AAAA records of the service domain name to be accessed exist or not according to the query result;
s330, if only the IPv6 AAAA record of the service domain name to be accessed exists, mapping the IPv6 AAAA record into an IPv 4A record through a preset mapping algorithm, and returning the IPv 4A record to the IPv4 client.
7. The traffic scheduling method for IPv4 peer access to IPv4/IPv6 network according to claim 1, wherein in step S300, the IPv4/IPv6 translation gateway receives the DNS a record request, queries an a record and an AAAA record of a specified domain name from a global DNS system, and selects an optimal a record or AAAA record from them according to a preset policy rule: if the record is A, the record is directly returned to the IPv4 client; if the record is AAAA record, the record is mapped into A record and then returned to the IPv4 client, and the method comprises the following steps:
s310, inquiring the IPv 4A record and the IPv6 AAAA record of the target domain name from the global DNS through the IPv4/IPv6 translation gateway, and returning an inquiry result of the service domain name to be accessed;
s320, judging whether the IPv 4A record and the IPv6 AAAA record of the service domain name to be accessed exist or not according to the query result;
s330, if the IPv 4A record and the IPv6 AAAA record of the service domain name to be accessed exist, inquiring a policy rule table inquired by the longest domain name matching mechanism to obtain a policy with IPv4 priority or IPv6 priority:
if the IPv4 has priority, directly returning the original IPv 4A record to the IPv4 client;
if the IPv6 has priority, the IPv6 AAAA record is mapped into an IPv 4A record through a preset mapping algorithm, the IPv 4A record is returned to the IPv4 client, and meanwhile, a corresponding IPv4/IPv6 address mapping table entry is established.
8. The traffic scheduling method for IPv4 peer access to IPv4/IPv6 network according to claim 7, wherein in step S300, the IPv4/IPv6 translation gateway receives the DNS a record request, queries an a record and an AAAA record of a specified domain name from a global DNS system, and selects an optimal a record or AAAA record from them according to preset policy rules: if the record is A, the record is directly returned to the IPv4 client; if the record is an AAAA record, the record is mapped into an A record and then returned to the IPv4 client, and the method further comprises the following steps:
s311, receiving the target address recorded by the IPv 4A record sent by the IPv4 client through the IPv4/IPv6 translation gateway;
s321, judging the type of the target address: an IPv4 address after IPv6 address translation or a native IPv4 address;
s331, if the address is the native IPv4 address, directly forwarding the message according to a preset routing path; if the address is the IPv4 address translated by the IPv6 address, the IPv4 address is mapped into a corresponding IPv6 address according to the IPv4/IPv6 address mapping table, and a routing table is searched to find an optimal outlet to send out the message.
9. An apparatus for implementing the traffic scheduling method of the IPv4 peer access IPv4/IPv6 network recited in any one of claims 1-8, the apparatus comprising:
the gateway configuration module is used for installing and configuring an IPv4/IPv6 translation gateway and constructing a policy rule table queried by a longest domain name matching mechanism on the IPv4/IPv6 translation gateway;
a DNS A record request module, which is used for sending a DNS A record request to the IPv4/IPv6 translation gateway through an IPv4 client in an IPv4 network;
an IPv4 a record query module, configured to receive the DNS a record request through the IPv4/IPv6 translation gateway, query an a record and an AAAA record of a specified domain name from a global DNS system, and select an optimal a record or AAAA record from the a record or the AAAA record according to a preset policy rule: if the record is A, the record is directly returned to the IPv4 client; if the record is AAAA record, the record is mapped into A record and then returned to the IPv4 client;
the IPv4 client is used for receiving an IPv 4A record and initiating an IPv4 address access corresponding to the IPv 4A record according to the IPv 4A record.
10. A traffic scheduling system for an IPv4 end to access an IPv4/IPv6 network is characterized by comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to execute the executable instructions to implement the traffic scheduling method of the IPv4 end access IPv4/IPv6 network of any one of claims 1 to 8.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210374961.3A CN114745353B (en) | 2022-04-11 | 2022-04-11 | Flow scheduling method for IPv4 terminal to access IPv4/IPv6 network |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210374961.3A CN114745353B (en) | 2022-04-11 | 2022-04-11 | Flow scheduling method for IPv4 terminal to access IPv4/IPv6 network |
Publications (2)
Publication Number | Publication Date |
---|---|
CN114745353A true CN114745353A (en) | 2022-07-12 |
CN114745353B CN114745353B (en) | 2024-06-25 |
Family
ID=82280738
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202210374961.3A Active CN114745353B (en) | 2022-04-11 | 2022-04-11 | Flow scheduling method for IPv4 terminal to access IPv4/IPv6 network |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN114745353B (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115412531A (en) * | 2022-08-31 | 2022-11-29 | 深圳市创维软件有限公司 | Network query method, device, equipment and storage medium |
CN118590871A (en) * | 2024-08-06 | 2024-09-03 | 天翼视联科技有限公司 | Data access method, device, electronic device and storage medium |
Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2005080146A (en) * | 2003-09-03 | 2005-03-24 | Yokogawa Electric Corp | IPv6/IPv4 TRANSLATOR |
US20110010413A1 (en) * | 2009-07-09 | 2011-01-13 | International Business Machines Corporation | Tcp/ip host name resolution on a private network |
WO2012109917A1 (en) * | 2011-02-18 | 2012-08-23 | 华为技术有限公司 | Message forwarding method, apparatus and system in network |
CN103167045A (en) * | 2011-12-12 | 2013-06-19 | 中国电信股份有限公司 | Method of choosing network layer protocol, domain name server (DNS), and domain-name management system |
US20140258491A1 (en) * | 2013-03-11 | 2014-09-11 | Bluebox Security Inc. | Methods and apparatus for hostname selective routing in dual-stack hosts |
CN104717639A (en) * | 2013-12-17 | 2015-06-17 | 北京邮电大学 | Access method for mobile client to internet and access gateway server |
CN106506729A (en) * | 2017-01-11 | 2017-03-15 | 中国互联网络信息中心 | DNS policy analysis method and device based on DNS view |
CN110225150A (en) * | 2019-06-27 | 2019-09-10 | 中星科源(北京)信息技术有限公司 | Communication means, system and storage medium between different network protocol |
CN112583952A (en) * | 2020-12-09 | 2021-03-30 | 北京金山云网络技术有限公司 | Redirection scheduling processing method, device and system, related equipment and storage medium |
CN113608877A (en) * | 2021-08-13 | 2021-11-05 | 牙木科技股份有限公司 | Load balancing scheduling method for IPV4 and IPV6 resource pools of content providers |
-
2022
- 2022-04-11 CN CN202210374961.3A patent/CN114745353B/en active Active
Patent Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2005080146A (en) * | 2003-09-03 | 2005-03-24 | Yokogawa Electric Corp | IPv6/IPv4 TRANSLATOR |
US20110010413A1 (en) * | 2009-07-09 | 2011-01-13 | International Business Machines Corporation | Tcp/ip host name resolution on a private network |
WO2012109917A1 (en) * | 2011-02-18 | 2012-08-23 | 华为技术有限公司 | Message forwarding method, apparatus and system in network |
CN103167045A (en) * | 2011-12-12 | 2013-06-19 | 中国电信股份有限公司 | Method of choosing network layer protocol, domain name server (DNS), and domain-name management system |
US20140258491A1 (en) * | 2013-03-11 | 2014-09-11 | Bluebox Security Inc. | Methods and apparatus for hostname selective routing in dual-stack hosts |
CN104717639A (en) * | 2013-12-17 | 2015-06-17 | 北京邮电大学 | Access method for mobile client to internet and access gateway server |
CN106506729A (en) * | 2017-01-11 | 2017-03-15 | 中国互联网络信息中心 | DNS policy analysis method and device based on DNS view |
CN110225150A (en) * | 2019-06-27 | 2019-09-10 | 中星科源(北京)信息技术有限公司 | Communication means, system and storage medium between different network protocol |
CN112583952A (en) * | 2020-12-09 | 2021-03-30 | 北京金山云网络技术有限公司 | Redirection scheduling processing method, device and system, related equipment and storage medium |
CN113608877A (en) * | 2021-08-13 | 2021-11-05 | 牙木科技股份有限公司 | Load balancing scheduling method for IPV4 and IPV6 resource pools of content providers |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115412531A (en) * | 2022-08-31 | 2022-11-29 | 深圳市创维软件有限公司 | Network query method, device, equipment and storage medium |
CN115412531B (en) * | 2022-08-31 | 2024-11-12 | 深圳市创维软件有限公司 | Network query method, device, equipment and storage medium |
CN118590871A (en) * | 2024-08-06 | 2024-09-03 | 天翼视联科技有限公司 | Data access method, device, electronic device and storage medium |
Also Published As
Publication number | Publication date |
---|---|
CN114745353B (en) | 2024-06-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10348571B2 (en) | Methods and apparatus for accessing dynamic routing information from networks coupled to a wide area network (WAN) to determine optimized end-to-end routing paths | |
JP3757917B2 (en) | Packet transfer device, packet transfer method resolution server, DNS server, network system, and program | |
US10693791B2 (en) | Software-defined network-based method and system for implementing content distribution network | |
US6304913B1 (en) | Internet system and method for selecting a closest server from a plurality of alternative servers | |
EP1362455B1 (en) | Method and system for multiple hosts anycast routing | |
WO2021043191A1 (en) | Domain name system server determination method, request processing method and apparatus, and system | |
US9699136B2 (en) | Stateless autoconfiguration of hostnames of network devices | |
US9277538B2 (en) | Node selection in a packet core network | |
US20040111529A1 (en) | Dynamic host based load balancing of a multihomed network | |
US20070074281A1 (en) | Presence-base packet routing control apparatus and packet routing control method | |
JP2002084317A (en) | Communication system, mobile terminal equipment, gateway equipment, address assigning method and retrieving service method | |
CN113067909B (en) | Edge node addressing method, device, equipment and storage medium | |
US20130111040A1 (en) | Auto-Split DNS | |
US20120203864A1 (en) | Method and Arrangement in a Communication Network for Selecting Network Elements | |
CN114745353B (en) | Flow scheduling method for IPv4 terminal to access IPv4/IPv6 network | |
JP4944211B2 (en) | Method and apparatus for providing network resources to a content provider | |
US20200228618A1 (en) | Content delivery method, device, and system | |
CN102469015A (en) | Method, device and system for realizing relay selection | |
US20150195764A1 (en) | Network service system and method for providing network service in multiple mobile network environment | |
US9356861B2 (en) | Secondary lookup for scaling datapath architecture beyond integrated hardware capacity | |
CN103460676A (en) | Flow routing protocol by querying a remote server | |
EP3419249A1 (en) | Methods of optimizing traffic in an isp network | |
CN111953806B (en) | Link selection method, device, computer equipment and computer storage medium | |
US10785153B2 (en) | Dynamic segment routing mapping server for a multiprotocol label switching network | |
US20060268853A1 (en) | Methods and apparatus for distributing label information |
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 |