CN116709199A - DNS redirection method and device and readable storage medium - Google Patents

DNS redirection method and device and readable storage medium Download PDF

Info

Publication number
CN116709199A
CN116709199A CN202310673237.5A CN202310673237A CN116709199A CN 116709199 A CN116709199 A CN 116709199A CN 202310673237 A CN202310673237 A CN 202310673237A CN 116709199 A CN116709199 A CN 116709199A
Authority
CN
China
Prior art keywords
request message
dns
dns request
terminal
edge node
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310673237.5A
Other languages
Chinese (zh)
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.)
China United Network Communications Group Co Ltd
Original Assignee
China United Network Communications Group 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 China United Network Communications Group Co Ltd filed Critical China United Network Communications Group Co Ltd
Priority to CN202310673237.5A priority Critical patent/CN116709199A/en
Publication of CN116709199A publication Critical patent/CN116709199A/en
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/029—Location-based management or tracking services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/025—Services making use of location information using location based information parameters

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The application provides a DNS redirection method, a device and a readable storage medium, wherein the method comprises the following steps: receiving a DNS request message sent by a terminal; generating an enhanced DNS request message according to the received DNS request message, wherein the enhanced DNS request message carries identification information capable of identifying the terminal position; sending the enhanced DNS request message to a large network DNS; receiving a DNS request message sent again by a terminal; and redirecting the retransmitted DNS request message to the optimal CDN edge node corresponding to the address. The method, the device and the readable storage medium can solve the problem that the real-time dynamic addressing of the edge application cannot be realized due to the uncertainty of the user position caused by mobility under the cooperative condition of MEC and CDN in the prior art.

Description

DNS redirection method and device and readable storage medium
Technical Field
The present application relates to the field of network technologies, and in particular, to a DNS redirection method, device, and readable storage medium.
Background
Before MEC (Mobile Edge Computing ) service is introduced, the IP (Internet Protocol ) of the server or scheduler to which the CDN (Content Delivery Network ) is addressed is determined and unique, and the DNS (Domain Name System ) resolution process only needs to be queried from pre-registered information; after the MEC service is introduced, the application server is distributed and deployed at the edge, and a plurality of examples are provided, which correspond to different public network IP or multiplex the same private network IP address field; further, for CDNs based on 5G MEC, the obtaining of location information becomes complex due to uncertainty of the location of the user caused by mobility, and the CDN service cannot simply reuse the implementation originally in the fixed network, and no clear theorem exists in the current standard.
Disclosure of Invention
The technical problem to be solved by the application is to provide a DNS redirection method, a device and a readable storage medium for solving at least the problem that the real-time dynamic addressing of the edge application cannot be realized due to the uncertainty of the user position caused by mobility under the cooperative condition of MEC and CDN in the prior art.
In a first aspect, the present application provides a DNS redirection method, applied to a user plane function UPF, the method comprising:
receiving a DNS request message sent by a terminal;
generating an enhanced DNS request message according to the received DNS request message, wherein the enhanced DNS request message carries identification information capable of identifying the terminal position;
sending the enhanced DNS request message to a large network DNS, so that the large network DNS forwards the enhanced DNS request message to a CDN service scheduling system of a content delivery network, and the CDN service scheduling system returns an address of an optimal CDN edge node to the terminal based on a pre-configured scheduling strategy and the identification information, wherein the optimal CDN edge node is the CDN edge node closest to the terminal;
receiving a DNS request message sent again by a terminal;
and redirecting the retransmitted DNS request message to the optimal CDN edge node corresponding to the address.
Further, the generating an enhanced DNS request message according to the received DNS request message specifically includes:
and inserting the identification information into the received DNS request message to obtain the enhanced DNS request message.
Further, the identification information includes at least one of: the identification of the terminal, the location information of the terminal, the identification of the UPF, the data network access identifier DNAI.
Further, the pre-configured scheduling policy includes a correspondence between the identification information and CDN edge nodes.
In a second aspect, the present application provides a DNS redirection method, applied to a CDN service scheduling system of a content delivery network, where the method includes:
receiving an enhanced DNS request message sent by a large network DNS, wherein the enhanced DNS request message is generated by a user plane function UPF according to the DNS request message sent by a terminal and is sent to the large network DNS, and the enhanced DNS request message carries identification information capable of identifying the position of the terminal;
and returning an address of an optimal CDN edge node to the terminal based on a pre-configured scheduling strategy and the identification information, so that after the UPF receives the DNS request message sent again by the terminal, the DNS request message sent again is redirected to the optimal CDN edge node corresponding to the address, wherein the optimal CDN edge node is the CDN edge node closest to the terminal.
Further, the identification information includes at least one of: the identification of the terminal, the location information of the terminal, the identification of the UPF, the data network access identifier DNAI.
Further, the pre-configured scheduling policy includes a correspondence between the identification information and CDN edge nodes.
In a third aspect, the present application provides a DNS redirection device, set in a user plane function UPF, the device comprising:
the first receiving module is used for receiving the DNS request message sent by the terminal;
the message generation module is connected with the first receiving module and is used for generating an enhanced DNS request message according to the received DNS request message, wherein the enhanced DNS request message carries identification information capable of identifying the terminal position;
the first sending module is connected with the message generating module and is used for sending the enhanced DNS request message to a large network DNS, so that the large network DNS forwards the enhanced DNS request message to a CDN service scheduling system of a content delivery network, and the CDN service scheduling system returns an address of an optimal CDN edge node to the terminal based on a pre-configured scheduling strategy and the identification information, wherein the optimal CDN edge node is the CDN edge node nearest to the terminal;
the second receiving module is connected with the first sending module and is used for receiving the DNS request message sent again by the terminal;
and the redirection module is connected with the second receiving module and is used for redirecting the retransmitted DNS request message to the optimal CDN edge node corresponding to the address.
In a fourth aspect, the present application provides a DNS redirection device, including: the CDN service scheduling system is arranged in a content delivery network, and the device comprises:
the third receiving module is used for receiving an enhanced DNS request message sent by a large network DNS, wherein the enhanced DNS request message is generated by a user plane function UPF according to the DNS request message sent by a terminal and is sent to the large network DNS, and the enhanced DNS request message carries identification information capable of identifying the position of the terminal;
the address returning module is connected with the third receiving module and is used for returning an address of an optimal CDN edge node to the terminal based on a pre-configured scheduling strategy and the identification information, so that after the UPF receives the DNS request message sent again by the terminal, the DNS request message sent again is redirected to the optimal CDN edge node corresponding to the address, wherein the optimal CDN edge node is the CDN edge node closest to the terminal.
In a fifth aspect, the present application provides a DNS redirection device comprising a memory, in which a computer program is stored, and a processor arranged to run the computer program to implement the DNS redirection method according to the first or second aspect.
In a sixth aspect, the present application provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the DNS redirection method according to the first or second aspect.
The application provides a DNS redirection method, a device and a readable storage medium. Firstly, receiving a DNS request message sent by a terminal; generating an enhanced DNS request message according to the received DNS request message, wherein the enhanced DNS request message carries identification information capable of identifying the terminal position; the enhanced DNS request message is sent to a large network DNS, so that the large network DNS forwards the enhanced DNS request message to a CDN service scheduling system of a content delivery network, and the CDN service scheduling system returns an address of an optimal CDN edge node to the terminal based on a pre-configured scheduling strategy and the identification information, wherein the optimal CDN edge node is the CDN edge node closest to the terminal; when the UPF receives the DNS request message sent again by the terminal, the sent DNS request message is redirected to the optimal CDN edge node corresponding to the address, so that the real-time dynamic addressing of the edge application under the mobile condition of the UE is realized. The problem that in the prior art, under the condition of cooperation of MEC and CDN, real-time dynamic addressing of edge application cannot be realized due to uncertainty of user position caused by mobility is solved.
Drawings
Fig. 1 is a schematic diagram of a DNS redirection scheduling method in the case of a fixed network according to an embodiment of the present application;
fig. 2 is a flowchart of a DNS redirection method in embodiment 1 of the present application;
fig. 3 is an interaction schematic diagram of a DNS redirection method according to an embodiment of the present application;
fig. 4 is a flowchart of a DNS redirection method in embodiment 2 of the present application
Fig. 5 is a schematic structural diagram of a DNS redirecting device in embodiment 3 of the present application;
fig. 6 is a schematic structural diagram of a DNS redirecting device in embodiment 4 of the present application;
fig. 7 is a schematic structural diagram of a DNS redirecting device in embodiment 5 of the present application.
Detailed Description
In order to make the technical scheme of the present application better understood by those skilled in the art, the following detailed description of the embodiments of the present application will be given with reference to the accompanying drawings.
It is to be understood that the specific embodiments and figures described herein are merely illustrative of the application, and are not limiting of the application.
It is to be understood that the various embodiments of the application and the features of the embodiments may be combined with each other without conflict.
It is to be understood that only the portions relevant to the present application are shown in the drawings for convenience of description, and the portions irrelevant to the present application are not shown in the drawings.
It should be understood that each unit and module in the embodiments of the present application may correspond to only one physical structure, may be formed by a plurality of physical structures, or may be integrated into one physical structure.
It will be appreciated that, without conflict, the functions and steps noted in the flowcharts and block diagrams of the present application may occur out of the order noted in the figures.
It is to be understood that the flowcharts and block diagrams of the present application illustrate the architecture, functionality, and operation of possible implementations of systems, apparatuses, devices, methods according to various embodiments of the present application. Where each block in the flowchart or block diagrams may represent a unit, module, segment, code, or the like, which comprises executable instructions for implementing the specified functions. Moreover, each block or combination of blocks in the block diagrams and flowchart illustrations can be implemented by hardware-based systems that perform the specified functions, or by combinations of hardware and computer instructions.
It should be understood that the units and modules related in the embodiments of the present application may be implemented by software, or may be implemented by hardware, for example, the units and modules may be located in a processor.
Summary of the application
Currently, the work item plan of the ITU (International Telecommunication Union, international telecommunications union standard) covers the agreements and communications between the MEC-CDN nodes and the MEC management layer, but no enabler in the ETSI MEC architecture currently supports such communications in a standardized way, e.g. so far no specific reference point in the MEC architecture between the MEC management layer and any specific MEC-CDN entity, the work being done by the ITU, so there is no standard in the standards for CDN to MEC cooperation; however, along with the explosion of the 5G large-scale video service, the cooperative appeal of the CDN and the MEC is more and more vigorous, the CDN node is truly sunk to the MEC node, the nearby access distribution capacity and the local hit rate of the CDN are greatly improved, a foundation is laid for the explosive development of the 5G-age large-scale video service, and the pressure of a backbone network is reduced while the high-quality experience of the large-scale video service of a user is met. The combination of the MEC and the CDN sufficiently reduces the difficulty of construction of a large number of edge CDN nodes, and the MEC is used for creating and managing a large number of nodes, so that the construction and maintenance cost of the CDN is reduced, meanwhile, the CDN is carried on the MEC, the edge computing power and the edge deployment advantages of the MEC are fully exerted, and the nearby calculation is provided.
Typically, a user accesses a service using a domain name/URL, and the network needs to know the IP address of the destination before forwarding the service data; server IP address discovery is typically achieved through domain name resolution (DNS); in the special service scene of the CDN, the DNS server is used as an intermediary to find a dispatching system of the application, and the dispatching system determines the IP address of the server providing the service according to the access resource of the user and the MEC platform position information accessible to the user. In the business scenario of MEC, the DNS process interprets as discovering the IP address of the local MEC server. In the current mobile situation, the edge application optimal addressing method is not yet decided under the cooperation of MEC and CDN.
Fig. 1 shows a main flow scheduling scheme of a current CDN, that is, a DNS redirection scheduling method in a fixed network situation, specifically including the following steps:
1) A user initiates a DNS request;
2) The DNS is used as an agent to forward the domain name request to a dispatching system of the CDN server, and the dispatching system matches rules to determine edge nodes;
3) DNS returns an edge node address;
4) The user accesses CDN edge nodes;
5) The CDN edge node returns hit content to the user.
However, the above solution is implemented under the fixed network condition, and the solution does not consider how to select the optimal edge node under the terminal mobile condition in the 5G condition.
The current dynamic configuration flow of the DNS address comprises the following steps:
ue (User Equipment) initiates a PDU (Protocol Data Unit ) session establishment procedure and sends a PDU session establishment request to SMF (Session Management Function ), including a DNS request in ePCO information.
2. If local DNS is available to the UE (based on the operator configuration and the location of the UE), the SMF sends local DNS address information to the UE instead of the large network DNS server information.
The smf sends a PDU session establishment accept to the UE, in an extension PCO of this message, a DNS address (IPv 6 and/or IPv 4) is included, which may be a local DNS (if available) or a large network DNS.
The UE moves to another location area and the SMF acquires the latest location information of the UE.
The smf determines whether the current DNS server information for the UE needs to be changed (based on the operator configuration and the location of the UE). The SMF transmits new DNS address information, i.e., large network DNS or LDNS (local DNS) server information, to the UE.
6. If the UE DNS server information needs to be changed, the SMF sends a PDU session modification procedure to the UE, including a DNS address in the ePCO of this message, which may be a local DNS (if available) or a large network DNS.
The ue stores new DNS address information.
The ue responds to the SMF with a PDU session modification complete message.
Although the 5GS (5 g system) network function in the above step ensures that the SMF dynamically configures the DNS address of the UE, the situation of the third party application in the case of the MEC in conjunction with the CDN is not considered, i.e., the domain name resolution does not determine the local DNS in conjunction with the application's own central scheduler.
Aiming at the technical problems, the application provides a DNS redirection method, a device and a readable storage medium, which are used for carrying out DNS redirection in combination with a central dispatcher (namely a CDN service dispatching system) of an application under the condition of considering a third party application, thereby realizing real-time dynamic addressing of an edge application and at least solving the problem that the real-time dynamic addressing of the edge application cannot be realized due to the uncertainty of a user position caused by mobility under the condition of cooperation of MEC and CDN in the prior art.
Having described the basic principles of the present application, various non-limiting embodiments of the present application will now be described in detail with reference to the accompanying drawings.
Example 1:
the present embodiment provides a DNS redirection method applied to UPF (User plane Function ), as shown in fig. 2, including:
step S101: receiving a DNS request message sent by a terminal;
in this embodiment, the terminal initiates a DNS Request message (DNS Request), which the UPF receives.
Step S102: and generating an enhanced DNS request message according to the received DNS request message, wherein the enhanced DNS request message carries identification information capable of identifying the terminal position.
In this embodiment, the enhanced DNS request message, that is, the eDNS request message, specifically, the PSA UPF (PDU session anchor UPF) identifies whether the packet is a DNS request message (DNS request message if the port number is 53) by monitoring the port number, and inserts the identification information into the received DNS request message, so as to obtain the enhanced DNS request message. It should be noted that while the standard defines only a single User Plane Function (UPF), it also defines some of the functional roles that a UPF can play on a user plane path, including PSA UPF and I-UPF (intermediate UPF).
It should be noted that, eDNS is an enhancement mechanism of DNS request messages, and on the basis of following the existing DNS message format, some fields are added to the data portion of the DNS packet to carry some auxiliary information, such as location related information of the carrying terminal, so as to support more DNS request services.
Optionally, the identification information includes at least one of: the identity of the terminal, the location information of the terminal, the identity of the UPF, DNAI (Data Network Access Identifier ).
In this embodiment, the identification information capable of identifying the location of the terminal facilitates the network to determine the location of the terminal, which may be an identifier of the terminal, such as MSISDN (Mobile Subscriber International ISDN/PSTN number, mobile subscriber number), IMSI (International Mobile Subscriber Identity ), IMEI (International Mobile Equipment Identity, international mobile equipment identity), etc., location information of the terminal, such as TAI (Tracking Area identity, tracking area identifier), NCGI (NR Cell Global Identifier, global identifier), ECGI (E-UTRAN Cell Global Identifier E, UTRAN cell global identifier), IP address, etc.), an identifier of the UPF, DNAI.
Step S103: and sending the enhanced DNS request message to a large network DNS, so that the large network DNS forwards the enhanced DNS request message to a CDN service scheduling system of a content delivery network, and the CDN service scheduling system returns an address of an optimal CDN edge node to the terminal based on a pre-configured scheduling strategy and the identification information, wherein the optimal CDN edge node is the CDN edge node closest to the terminal (namely a local CDN edge node).
In this embodiment, the present application upgrades the large network DNS by expanding the message field, and supports the location related information of the terminal (i.e., the identification information capable of identifying the location of the terminal) carrying the initiated DNS request message in the process of recursion analysis, and carries the request source identification. The large network DNS forwards the eDNS request message to a CDN service scheduling system in a DNS CNAME (DNS Canonical name record, DNS alias) mode, the CDN service scheduling system is a central scheduler corresponding to a third party application, and the CDN service scheduling system selects an optimal CDN edge node address (IP address) according to a pre-configured scheduling strategy, wherein the optimal CDN edge node is a local CDN edge node capable of meeting the third party application requirements of a terminal.
Optionally, the pre-configured scheduling policy includes a correspondence between the identification information and CDN edge nodes.
In this embodiment, the pre-configured scheduling policy includes a correspondence between identification information and CDN edge nodes, for example, a correspondence between terminal location information and CDN edge nodes, a correspondence between UPF identification/DNAI and terminal location information, and a correspondence between terminal location information and CDN edge nodes, etc.
Step S104: receiving a DNS request message sent again by a terminal;
step S105: and redirecting the retransmitted DNS request message to the optimal CDN edge node corresponding to the address.
In this embodiment, the terminal initiates a DNS Request message (DNS Request) again, the I-UPF matches according to a ul cl upstream splitting rule ul cl-rule-matched (e.g., a DNS redirection rule performs splitting), streams the user traffic (DNS Request) to the MEP (Multi-access Edge platform, edge platform) - > the CDN edge node (local CDN APP server) corresponding to the address, and the CDN edge node (local CDN APP server) responds to the terminal, sends a DNS Response, and pushes the hit content to the terminal.
In a specific embodiment, referring to fig. 3, an interaction schematic diagram of a DNS redirection method provided by an embodiment of the present application is shown, in which some transit network elements, such as RAN (Radio Access Network ), MEP, etc., are omitted, and the method specifically includes the following steps:
(1) The terminal initiates a DNS Request message (DNS Request);
(2) The PSA UPF (PDU session anchor UPF) identifies the message as a DNS request message (port number is 53) through monitoring the port number, and locally shunts the DNS request message to the large network DNS (Central DNS), the PSA UPF supports eDNS packet processing enhancement function, and the enhanced DNS request message (eDNS request message) is obtained by inserting location related information of a terminal (i.e. identification information capable of identifying the location of the terminal) into the DNS request message
Wherein the location related information (i.e., identification information capable of identifying the location of the terminal) may be: an identification of the terminal (MSISDN, IMSI, IMEI, etc.), location information of the terminal (e.g., TAI, NCGI, ECGI, IP address, etc.), an identification of the UPF, a data network access identifier DNAI.
It should be noted that, eDNS is an enhancement mechanism of DNS request messages, and on the basis of following the existing DNS message format, some fields are added to the data portion of the DNS packet to carry some auxiliary information, such as location related information of the carrying terminal, so as to support more DNS request services.
(3) The large network DNS (Central DNS) performs recursion analysis, upgrades the large network DNS, supports the position related information of the terminal carrying the initiated DNS request message in the recursion analysis process by expanding the message field, and carries a request source identifier, such as a public network IP address (which can be obtained from SMF) after the NAT of the UE;
(4) The large network DNS (Central DNS) forwards the eDNS request message to the CDN service scheduling system in a DNS CNAME mode (Central CDN app server);
(5) The CDN service dispatching system (Central CDN app server) selects the optimal address (IP address) of the CDN edge node according to a pre-configured dispatching strategy, namely the CDN service dispatching system (Central CDN app server) pre-configures the corresponding relation between the position related information and the CDN edge node, such as UPF identification/DNAI and terminal position information, and the corresponding relation between the terminal and the CDN edge node, and the terminal accesses a local UPF based on the position, and the UPF identifies a specific CDN service and implements UPF identification/DNAI insertion; the CDN service scheduling system judges the user position according to the UPF identification/DNAI, and analyzes the DNS request of the terminal according to the request domain name and the request source by managing the topology structure, the node state, the service and other information of the whole network edge computing node (CDN edge node), so as to realize the discovery of the IP address of the local server to determine the CDN edge node providing the service and return the IP address of the CDN edge node;
(6) The CDN service scheduling system (Central CDN app server) returns the address of the selected optimal CDN edge node (local CDN APP server) to the terminal through a DNS response message (DNS response).
(7) The terminal initiates a DNS Request message (DNS Request) again.
(8) I-UPF (intermediate UPF) matches according to ULCL uplink diversion rule ULCL-rule-matched (for example, the DNS redirection rule is used for diversion) according to DNS request initiated by the terminal.
It should be noted that, when the CDN service scheduling system returns the address of the optimal CDN edge node to the terminal, the I-UPF is deployed in advance in the manner of a ULCL, the SMF (5 GC C-Plane) selects a local UPF access path for the terminal based on the terminal location, and a UL CL based on local service IP splitting is inserted/configured on the local UPF.
(9) The I-UPF (intermediate UPF) streams the user traffic (DNS Request) to the CDN edge node (local CDN APP server) to which the MEP- > address corresponds.
(10) The CDN edge node (local CDN APP server) responds to the terminal and sends a DNS Response to push the hit content to the terminal.
Through the steps, an application server (CDN edge node) with the nearest attachment point of the terminal can be guaranteed to provide services for the terminal, and in a CDN scene (a local server is determined by combining domain name resolution with a central dispatcher of an application itself): and the central dispatcher acquires information related to the real-time position of the user, and dispatches the request of the terminal to the APP optimally deployed on the CDN edge node.
The DNS redirection method provided by the embodiment of the application firstly receives the DNS request message sent by the terminal; generating an enhanced DNS request message according to the received DNS request message, wherein the enhanced DNS request message carries identification information capable of identifying the terminal position; the enhanced DNS request message is sent to a large network DNS, so that the large network DNS forwards the enhanced DNS request message to a CDN service scheduling system of a content delivery network, and the CDN service scheduling system returns an address of an optimal CDN edge node to the terminal based on a pre-configured scheduling strategy and the identification information, wherein the optimal CDN edge node is the CDN edge node closest to the terminal; when the UPF receives the DNS request message sent again by the terminal, the sent DNS request message is redirected to the optimal CDN edge node corresponding to the address, so that the real-time dynamic addressing of the edge application under the mobile condition of the UE is realized. The problem that in the prior art, under the condition of cooperation of MEC and CDN, real-time dynamic addressing of edge application cannot be realized due to uncertainty of user position caused by mobility is solved.
Example 2:
as shown in fig. 4, the present embodiment provides a DNS redirection method, which is applied to a CDN service scheduling system of a content delivery network, where the method includes:
step S201: receiving an enhanced DNS request message sent by a large network DNS, wherein the enhanced DNS request message is generated by a user plane function UPF according to the DNS request message sent by a terminal and is sent to the large network DNS, and the enhanced DNS request message carries identification information capable of identifying the position of the terminal;
in this embodiment, the enhanced DNS request message, that is, the eDNS request message, specifically, the PSA UPF (PDU session anchor UPF) identifies whether the packet is a DNS request message (DNS request message if the port number is 53) by monitoring the port number, and inserts the identification information into the received DNS request message, so as to obtain the enhanced DNS request message. It should be noted that while the standard defines only a single User Plane Function (UPF), it also defines some of the functional roles that a UPF can play on a user plane path, including PSA UPF and I-UPF (intermediate UPF).
Optionally, the identification information includes at least one of: the identification of the terminal, the location information of the terminal, the identification of the UPF, the data network access identifier DNAI.
In this embodiment, the identification information capable of identifying the location of the terminal facilitates the network to determine the location of the terminal, which may be the identification of the terminal (MSISDN, IMSI, IMEI, etc.), the location information of the terminal (such as TAI, NCGI, ECGI, IP address, etc.), the identification of the UPF, and the data network access identifier DNAI.
Step S202: and returning an address of an optimal CDN edge node to the terminal based on a pre-configured scheduling strategy and the identification information, so that after the UPF receives the DNS request message sent again by the terminal, the DNS request message sent again is redirected to the optimal CDN edge node corresponding to the address, wherein the optimal CDN edge node is the CDN edge node closest to the terminal.
In this embodiment, the large network DNS performs recursive resolution, and forwards the eDNS request message to the CDN service scheduling system in the DNS CNAME manner, where the CDN service scheduling system is a central scheduler corresponding to the third party application, and the CDN service scheduling system selects, according to a preconfigured scheduling policy, an address (IP address) of an optimal CDN edge node, where the optimal CDN edge node is a local CDN edge node capable of meeting the third party application requirement of the terminal.
Optionally, the pre-configured scheduling policy includes a correspondence between the identification information and CDN edge nodes.
In this embodiment, the pre-configured scheduling policy includes a correspondence between identification information and CDN edge nodes, for example, a correspondence between terminal location information and CDN edge nodes, a correspondence between UPF identification/DNAI and terminal location information, and a correspondence between terminal location information and CDN edge nodes, etc.
In this embodiment, the terminal initiates a DNS Request message (DNS Request) again, the I-UPF matches according to a ul cl upstream splitting rule ul cl-rule-matched (e.g., a DNS redirection rule performs splitting), streams the user traffic (DNS Request) to the MEP (Multi-access Edge platform, edge platform) - > the CDN edge node (local CDN APP server) corresponding to the address, and the CDN edge node (local CDN APP server) responds to the terminal, sends a DNS Response, and pushes the hit content to the terminal.
Example 3:
as shown in fig. 5, this embodiment provides a DNS redirection device, provided in a user plane function UPF, for executing the DNS redirection method in the foregoing embodiment 1, where the device includes:
a first receiving module 11, configured to receive a DNS request message sent by a terminal;
a message generating module 12, connected to the first receiving module 11, configured to generate an enhanced DNS request message according to the received DNS request message, where the enhanced DNS request message carries identification information capable of identifying the location of the terminal;
a first sending module 13, connected to the message generating module 12, configured to send the enhanced DNS request message to a large network DNS, so that the large network DNS forwards the enhanced DNS request message to a content delivery network CDN service scheduling system, and the CDN service scheduling system returns an address of an optimal CDN edge node to the terminal based on a pre-configured scheduling policy and the identification information, where the optimal CDN edge node is a CDN edge node closest to the terminal;
the second receiving module 14 is connected with the first sending module 13 and is used for receiving the DNS request message sent again by the terminal;
and the redirection module 15 is connected with the second receiving module 14 and is used for redirecting the retransmitted DNS request message to the optimal CDN edge node corresponding to the address.
Optionally, the message generating module 12 is specifically configured to:
and inserting the identification information into the received DNS request message to obtain the enhanced DNS request message.
Optionally, the identification information includes at least one of: the identification of the terminal, the location information of the terminal, the identification of the UPF, the data network access identifier DNAI.
Optionally, the pre-configured scheduling policy includes a correspondence between the identification information and CDN edge nodes.
Example 4:
as shown in fig. 6, this embodiment provides a DNS redirection device, configured to be disposed in a CDN service scheduling system of a content delivery network, and configured to execute the DNS redirection method in the foregoing embodiment 2, where the device includes:
a third receiving module 21, configured to receive an enhanced DNS request message sent by a large network DNS, where the enhanced DNS request message is generated by a user plane function UPF according to a DNS request message sent by a terminal and sent to the large network DNS, and the enhanced DNS request message carries identification information capable of identifying a location of the terminal;
the address returning module 22 is connected to the third receiving module 21, and is configured to return, to the terminal, an address of an optimal CDN edge node based on a pre-configured scheduling policy and the identification information, so that after the UPF receives the DNS request message sent again by the terminal, the DNS request message sent again is redirected to the optimal CDN edge node corresponding to the address, where the optimal CDN edge node is a CDN edge node closest to the terminal.
Optionally, the identification information includes at least one of: the identification of the terminal, the location information of the terminal, the identification of the UPF, the data network access identifier DNAI.
Optionally, the pre-configured scheduling policy includes a correspondence between the identification information and CDN edge nodes.
Example 5:
referring to fig. 7, the present embodiment provides a DNS redirection device comprising a memory 31 and a processor 32, the memory 31 storing a computer program, the processor 32 being arranged to run the computer program to perform the DNS redirection method in embodiment 1 or embodiment 2.
The memory 31 is connected to the processor 32, the memory 31 may be a flash memory, a read-only memory, or other memories, and the processor 32 may be a central processing unit or a single chip microcomputer.
Example 6:
the present embodiment provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the DNS redirection method in embodiment 1 or embodiment 2 described above.
Computer-readable storage media include volatile or nonvolatile, removable or non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, computer program modules or other data. Computer-readable storage media includes, but is not limited to, RAM (Random Access Memory ), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory, charged erasable programmable Read-Only Memory), flash Memory or other Memory technology, CD-ROM (Compact Disc Read-Only Memory), digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.
In summary, the DNS redirection method and device and the readable storage medium provided by the embodiments of the present application. Firstly, receiving a DNS request message sent by a terminal; generating an enhanced DNS request message according to the received DNS request message, wherein the enhanced DNS request message carries identification information capable of identifying the terminal position; the enhanced DNS request message is sent to a large network DNS, so that the large network DNS forwards the enhanced DNS request message to a CDN service scheduling system of a content delivery network, and the CDN service scheduling system returns an address of an optimal CDN edge node to the terminal based on a pre-configured scheduling strategy and the identification information, wherein the optimal CDN edge node is the CDN edge node closest to the terminal; when the UPF receives the DNS request message sent again by the terminal, the sent DNS request message is redirected to the optimal CDN edge node corresponding to the address, so that the real-time dynamic addressing of the edge application under the mobile condition of the UE is realized. The problem that in the prior art, under the condition of cooperation of MEC and CDN, real-time dynamic addressing of edge application cannot be realized due to uncertainty of user position caused by mobility is solved.
It is to be understood that the above embodiments are merely illustrative of the application of the principles of the present application, but not in limitation thereof. Various modifications and improvements may be made by those skilled in the art without departing from the spirit and substance of the application, and are also considered to be within the scope of the application.

Claims (11)

1. A domain name system, DNS, redirection method, applied to a user plane function, UPF, the method comprising:
receiving a DNS request message sent by a terminal;
generating an enhanced DNS request message according to the received DNS request message, wherein the enhanced DNS request message carries identification information capable of identifying the terminal position;
sending the enhanced DNS request message to a large network DNS, so that the large network DNS forwards the enhanced DNS request message to a CDN service scheduling system of a content delivery network, and the CDN service scheduling system returns an address of an optimal CDN edge node to the terminal based on a pre-configured scheduling strategy and the identification information, wherein the optimal CDN edge node is the CDN edge node closest to the terminal;
receiving a DNS request message sent again by a terminal;
and redirecting the retransmitted DNS request message to the optimal CDN edge node corresponding to the address.
2. The method according to claim 1, wherein said generating an enhanced DNS request message from said received DNS request message, in particular comprises:
and inserting the identification information into the received DNS request message to obtain the enhanced DNS request message.
3. The method of claim 1, wherein the identification information comprises at least one of: the identification of the terminal, the location information of the terminal, the identification of the UPF, the data network access identifier DNAI.
4. The method of claim 3, wherein the pre-configured scheduling policy includes a correspondence between the identification information and CDN edge nodes.
5. A domain name system DNS redirection method, applied to a content delivery network CDN service scheduling system, the method comprising:
receiving an enhanced DNS request message sent by a large network DNS, wherein the enhanced DNS request message is generated by a user plane function UPF according to the DNS request message sent by a terminal and is sent to the large network DNS, and the enhanced DNS request message carries identification information capable of identifying the position of the terminal;
and returning an address of an optimal CDN edge node to the terminal based on a pre-configured scheduling strategy and the identification information, so that after the UPF receives the DNS request message sent again by the terminal, the DNS request message sent again is redirected to the optimal CDN edge node corresponding to the address, wherein the optimal CDN edge node is the CDN edge node closest to the terminal.
6. The method of claim 5, wherein the identification information comprises at least one of: the identification of the terminal, the location information of the terminal, the identification of the UPF, the data network access identifier DNAI.
7. The method of claim 6, wherein the pre-configured scheduling policy includes a correspondence between the identification information and CDN edge nodes.
8. A domain name system, DNS, redirecting means, arranged in a user plane function, UPF, the means comprising:
the first receiving module is used for receiving the DNS request message sent by the terminal;
the message generation module is connected with the first receiving module and is used for generating an enhanced DNS request message according to the received DNS request message, wherein the enhanced DNS request message carries identification information capable of identifying the terminal position;
the first sending module is connected with the message generating module and is used for sending the enhanced DNS request message to a large network DNS, so that the large network DNS forwards the enhanced DNS request message to a CDN service scheduling system of a content delivery network, and the CDN service scheduling system returns an address of an optimal CDN edge node to the terminal based on a pre-configured scheduling strategy and the identification information, wherein the optimal CDN edge node is the CDN edge node nearest to the terminal;
the second receiving module is connected with the first sending module and is used for receiving the DNS request message sent again by the terminal;
and the redirection module is connected with the second receiving module and is used for redirecting the retransmitted DNS request message to the optimal CDN edge node corresponding to the address.
9. A domain name system DNS redirection device, configured to a CDN service scheduling system of a content delivery network, the device comprising:
the third receiving module is used for receiving an enhanced DNS request message sent by a large network DNS, wherein the enhanced DNS request message is generated by a user plane function UPF according to the DNS request message sent by a terminal and is sent to the large network DNS, and the enhanced DNS request message carries identification information capable of identifying the position of the terminal;
the address returning module is connected with the third receiving module and is used for returning an address of an optimal CDN edge node to the terminal based on a pre-configured scheduling strategy and the identification information, so that after the UPF receives the DNS request message sent again by the terminal, the DNS request message sent again is redirected to the optimal CDN edge node corresponding to the address, wherein the optimal CDN edge node is the CDN edge node closest to the terminal.
10. DNS redirection device comprising a memory in which a computer program is stored and a processor arranged to run the computer program to implement the DNS redirection method according to any of the claims 1-4 or to implement the DNS redirection method according to any of the claims 5-7.
11. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the DNS redirection method according to any of claims 1-4 or implements the DNS redirection method according to any of claims 5-7.
CN202310673237.5A 2023-06-07 2023-06-07 DNS redirection method and device and readable storage medium Pending CN116709199A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310673237.5A CN116709199A (en) 2023-06-07 2023-06-07 DNS redirection method and device and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310673237.5A CN116709199A (en) 2023-06-07 2023-06-07 DNS redirection method and device and readable storage medium

Publications (1)

Publication Number Publication Date
CN116709199A true CN116709199A (en) 2023-09-05

Family

ID=87838696

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310673237.5A Pending CN116709199A (en) 2023-06-07 2023-06-07 DNS redirection method and device and readable storage medium

Country Status (1)

Country Link
CN (1) CN116709199A (en)

Similar Documents

Publication Publication Date Title
EP4213577A1 (en) Address information sending method and apparatus, address information obtaining method and apparatus, device, and medium
JP5384745B2 (en) Method for managing a P2P network based on cellular communication
US6490451B1 (en) System and method for providing packet-switched telephony
CN113596191B (en) Data processing method, network element equipment and readable storage medium
CN114747252A (en) Method for identifying traffic suitable for edge breakout and for traffic steering in a mobile network
JP2007528157A (en) Domain ID mapping for wireless device identifier
CN111615844B (en) Method and apparatus for selecting a session management entity serving a wireless communication device
KR20090057025A (en) Method for discovering outbound sip proxy server
CN114902634A (en) Apparatus and method for providing information of application server in mobile communication system
WO2019245711A1 (en) Session control logic with internet protocol (ip)-based routing
KR20110044840A (en) System and method for resolving contention among applications requiring data connections between a mobile communications device and a wireless network
US20230032185A1 (en) Apparatus and method for supporting edge computing service in wireless communication system
US20140357300A1 (en) System and method for acquiring user location through user bearer identifier
US11863519B2 (en) Communication method and apparatus for handling DNS messages
US20180317155A1 (en) Wireless network brokerage
CN105101176A (en) Session binding method, device and system in roaming scene
CN102651862B (en) IP (Internet Protocol) address configuration method of WAP (Wireless Application Protocol) gateway and equipment thereof
US7684794B1 (en) Managing endpoint addresses separately from managing endpoint mobility
US20080235185A1 (en) Communication system and method of accessing therefor
US20040240441A1 (en) Enabling packet switched calls to a wireless telephone user
WO2010012189A1 (en) Method and system for transmitting the gtp message
US20070049284A1 (en) Supporting communication sessions at a mobile node
CN116709199A (en) DNS redirection method and device and readable storage medium
CN116458137A (en) Method and system for identifying edge application server
EP2078354B1 (en) Mobility support based on prefix binding

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