CN114513494A - Service scheduling method, system, storage medium and service system - Google Patents

Service scheduling method, system, storage medium and service system Download PDF

Info

Publication number
CN114513494A
CN114513494A CN202011276737.8A CN202011276737A CN114513494A CN 114513494 A CN114513494 A CN 114513494A CN 202011276737 A CN202011276737 A CN 202011276737A CN 114513494 A CN114513494 A CN 114513494A
Authority
CN
China
Prior art keywords
http
dns
upf
http dns
proxy
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
Application number
CN202011276737.8A
Other languages
Chinese (zh)
Other versions
CN114513494B (en
Inventor
林奕琳
刘洁
朱红梅
何宇锋
杨峰义
张建敏
曹磊
王波
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Telecom Corp Ltd
Original Assignee
China Telecom Corp 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 Telecom Corp Ltd filed Critical China Telecom Corp Ltd
Priority to CN202011276737.8A priority Critical patent/CN114513494B/en
Publication of CN114513494A publication Critical patent/CN114513494A/en
Application granted granted Critical
Publication of CN114513494B publication Critical patent/CN114513494B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding

Landscapes

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

Abstract

The disclosure provides a service scheduling method, a service scheduling system, a storage medium and a service system, and relates to the technical field of mobile edge computing. The service scheduling method comprises the following steps: a central user plane function UPF acquires access address information of a service according to a DNS response sent to a user terminal by a central domain name system DNS; inserting a terminal private network address, wireless position information, slice information and access address information into the received HTTP DNS request, and sending the processed HTTP DNS request to a 5G core network Proxy 5GC Proxy; 5GC Proxy replaces the wireless position information in the HTTP DNS request with a mobile edge computing MEC identifier corresponding to the geographic position, and forwards the mobile edge computing MEC identifier to an HTTP DNS server corresponding to the access address information; and 5, the GC Proxy receives the HTTP DNS response fed back by the HTTP DNS server, and forwards the HTTP DNS response to the user terminal after initiating UPF/uplink classifier ULCL insertion to the policy control function PCF entity, so that local flow distribution is realized, network flow burden is reduced, and user access speed is improved.

Description

Service scheduling method, system, storage medium and service system
Technical Field
The present disclosure relates to the field of mobile edge computing technologies, and in particular, to a method and a system for scheduling a service, a storage medium, and a service system.
Background
In a Content Delivery Network (CDN) architecture, servers accessed by a user are allocated nearby, so that the user access speed is increased and the Network load is reduced. In 4G network deployment, because a PGW (PDN Gateway, public data network Gateway) adopts a provincial level centralized deployment manner, and an MEC cannot be deployed close to a user, a CDN service based on a mobile network is difficult to land.
Disclosure of Invention
The inventor finds that in a 5G SA (stand alone networking) network, a UPF (User Plane Function) can be deployed in a sunk manner as required, so that low-latency high-bandwidth CDN services can be deployed based on the 5G network.
One objective of the present disclosure is to propose a scheme for implementing CDN services in a 5G SA network.
According to an aspect of some embodiments of the present disclosure, a traffic scheduling method is provided, including: the central UPF acquires the access address information of the service according to a DNS response sent to the user terminal by a central DNS (Domain Name System); the method comprises the steps that a central UPF inserts a terminal private network address, wireless position information, slice information and access address information into an HTTP DNS request under the condition that the HTTP DNS request from a terminal is received, and sends the processed HTTP DNS request to a 5GC Proxy (5G core network agent); 5GC Proxy replaces the wireless position information in the HTTP DNS request with an MEC (Mobile Edge Computing) identifier of a corresponding geographical position, and forwards the wireless position information to an HTTP DNS server corresponding to the access address information; 5GC Proxy receives HTTP DNS response fed back by the HTTP DNS server, wherein the HTTP DNS server determines the access address of the application server on the corresponding MEC node according to the MEC identifier to generate the HTTP DNS response; after initiating a UPF/ULCL (Uplink Classifier) insertion to a PCF (Policy Control Function) entity, the 5GC Proxy forwards the HTTP DNS response to the user terminal, so that the user terminal accesses the application server through the corresponding edge UPF.
In some embodiments, sending the processed HTTP DNS request to the 5GC Proxy by the hub UPF comprises: the center UPF replaces the destination address of the HTTP DNS request with the address of the 5GC Proxy, and transmits the HTTP DNS request according to the replaced destination address.
In some embodiments, the 5GC Proxy sending the processed HTTP DNS request to the HTTP DNS server includes: the 5GC Proxy replaces the destination address of the HTTP DNS request with the access address information.
In some embodiments, the central UPF inserts the terminal private network address, wireless location information, slice information, and access address information into the header field of the HTTP DNS request; the service scheduling method further comprises the following steps: the 5GC Proxy stores header information of the received HTTP DNS request to initiate a UPF/ULCL insertion to the PCF based on the header information and the HTTP DNS response.
In some embodiments, the traffic scheduling method further includes: the method comprises the steps that a center UPF inserts a terminal number into an HTTP DNS request under the condition that the HTTP DNS request from a terminal is received; 5GC Proxy determines the terminal attribution province according to the terminal number after receiving the HTTP DNS response from the HTTP DNS server; initiating a UPF/ULCL insertion to a PCF includes: and initiating UPF/ULCL insertion to PCF of the home province of the terminal number or after addressing the PCF of the home province through the BSF of the home province.
In some embodiments, the obtaining, by the central UPF, the access address information of the service according to the DNS response sent by the central domain name system DNS to the user terminal includes: the center DNS receives a DNS request from the user terminal, and a DNS response is fed back to the user terminal through the center UPF; and the central UPF records the access address information of the service corresponding to the DNS response and forwards the DNS response to the UE under the condition of receiving the DNS response from the central DNS.
By the method, the MEC identifier capable of reflecting the position of the terminal can be inserted into the HTTP DNS request initiated by the terminal through improvement of a network side, so that an application server for providing service is distributed nearby by an application scheduling system according to the MEC identifier, and the address of the distributed application server is fed back to the terminal, thereby realizing local traffic distribution, shortening the forwarding path of the user access edge application, reducing the network traffic burden and improving the user access speed.
According to an aspect of some embodiments of the present disclosure, there is provided a traffic scheduling system, including: the center UPF is configured to acquire the access address information of the service according to a DNS response sent to the user terminal by the center DNS; under the condition of receiving an HTTP DNS request from a terminal, inserting a terminal private network address, wireless position information, slice information and access address information into the HTTP DNS request, and sending the processed HTTP DNS request to a 5GC Proxy; the 5GC Proxy is configured to replace the wireless position information in the HTTP DNS request with the MEC identifier corresponding to the geographic position, and forward the HTTP DNS request to an HTTP DNS server corresponding to the access address information; receiving an HTTP DNS response fed back by the HTTP DNS server, wherein the HTTP DNS server determines an access address of an application server on a corresponding MEC node according to the MEC identifier to generate the HTTP DNS response; initiating UPF/ULCL insertion to the PCF entity; and forwarding the HTTP DNS response to the user terminal so that the user terminal can access the application server through the corresponding edge UPF.
In some embodiments, the central UPF is configured to insert the terminal private network address, the wireless location information, the slice information and the access address information into a header field of the HTTP DNS request; the 5GC Proxy is further configured to save header information of the received HTTP DNS request to initiate a UPF/ULCL insertion to the PCF based on the header information and the HTTP DNS response.
In some embodiments, the central UPF is further configured to insert the terminal number in the HTTP DNS request in case of receiving the HTTP DNS request from the terminal; the 5GC Proxy is further configured to determine a terminal attribution province according to the terminal number after receiving an HTTP DNS response from the HTTP DNS server; and initiating UPF/ULCL insertion to PCF of the home province of the terminal number or after addressing the PCF of the home province through the BSF of the home province.
In some embodiments, the traffic scheduling system further comprises: the central DNS is configured to receive a DNS request from the user terminal and feed back a DNS response to the user terminal through the central UPF; the central UPF is configured to, upon receiving the DNS response from the central DNS, record access address information of a service corresponding to the DNS response and forward the DNS response to the UE.
According to an aspect of some embodiments of the present disclosure, there is provided a traffic scheduling system, including: a memory; and a processor coupled to the memory, the processor configured to perform any of the traffic scheduling methods above based on instructions stored in the memory.
The service scheduling system can insert the MEC identifier capable of reflecting the position of the terminal into the HTTP DNS request initiated by the terminal through improvement of a network side, so that the application scheduling system can distribute the application server for providing service nearby according to the MEC identifier and feed back the address of the distributed application server to the terminal, thereby realizing local flow distribution, shortening the forwarding path of the user access edge application, reducing the network flow burden and improving the user access speed.
According to an aspect of some embodiments of the present disclosure, a computer-readable storage medium is proposed, on which computer program instructions are stored, which instructions, when executed by a processor, implement the steps of any of the above traffic scheduling methods.
By executing the instruction on the computer-readable storage medium, the MEC identifier capable of reflecting the position of the terminal can be inserted into the HTTP DNS request initiated by the terminal through improvement of a network side, so that an application scheduling system can allocate an application server for providing services according to the MEC identifier nearby, and the address of the allocated application server is fed back to the terminal, thereby realizing local traffic distribution, shortening the forwarding path of the user access edge application, reducing the network traffic burden and improving the user access speed.
According to an aspect of some embodiments of the present disclosure, there is provided a business service system, including: any one of the above service scheduling systems; and the application scheduling server is configured to calculate the MEC identifier according to the mobile edge in the HTTP DNS request from the service scheduling system, allocate the access address of the application server on the corresponding MEC node for the UE, and send the access address of the application server to the 5GC Proxy through the HTTP DNS response.
The service system can insert the MEC identifier capable of reflecting the position of the terminal into the HTTP DNS request initiated by the terminal through improvement of a network side, the application scheduling system distributes the application servers providing services nearby according to the MEC identifier and feeds back the address of the distributed application server to the terminal, so that local flow distribution is realized, the forwarding path of the user accessing edge application is shortened, the network flow burden is reduced, and the user access speed is improved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this disclosure, illustrate embodiments of the disclosure and together with the description serve to explain the disclosure and not to limit the disclosure. In the drawings:
fig. 1 is a flow chart of some embodiments of a traffic scheduling method of the present disclosure.
Fig. 2 is a flowchart of another embodiment of a service scheduling method according to the present disclosure.
Fig. 3 is a schematic diagram of some embodiments of a traffic scheduling system of the present disclosure.
Fig. 4A is a schematic diagram of some embodiments of a traffic scheduling system of the present disclosure in a network.
Fig. 4B is a signaling flow diagram for some embodiments of the traffic scheduling system of fig. 4A.
Fig. 5A is a schematic diagram of other embodiments of the service scheduling system of the present disclosure in a network.
Fig. 5B is a signaling flow diagram for some embodiments of the traffic scheduling system of fig. 5A.
Fig. 6 is a schematic diagram of further embodiments of the traffic scheduling system of the present disclosure.
Fig. 7 is a schematic diagram of still further embodiments of traffic scheduling systems of the present disclosure.
Fig. 8 is a schematic diagram of some embodiments of a business service system of the present disclosure.
Detailed Description
The technical solution of the present disclosure is further described in detail by the accompanying drawings and examples.
The inventor finds that, in the related art, a terminal initiates a DNS request to acquire an access address of an applied scheduling system, and then the terminal sends a request message to the applied scheduling system according to the acquired access address, wherein the request carries service domain name information; the Application scheduling system matches the user location information according to the source IP address information of the message, and feeds back an access address of a local CDN AS (Application Server) to the terminal, so that the terminal can access the Application service according to the access address.
However, in the 5G scenario, the user initially accesses the network from the central UPF, which makes the application scheduling system unable to match the edge MEC node location based on the obtained user source IP address, making it difficult to correctly determine the application server close to the user location.
A flow diagram of some embodiments of a traffic scheduling method of the present disclosure is shown in fig. 1.
In step 101, the central UPF obtains the access address information of the service according to the DNS response sent by the central DNS to the user terminal.
In some embodiments, when a user terminal initiates a service request, a DNS request is sent to the central DNS. After receiving the request, the central DNS feeds back the access address information of the service. The access address information of the service may point to an application scheduling system server address of the corresponding service. The DNS response fed back by the central DNS is sent to the terminal via the central UPF. And after receiving the DNS response, the central UPF stores the access address information of the service and sends the DNS response to the user terminal.
In step 102, the center UPF inserts the terminal private network address, the wireless location information, the slice information, and the access address information into the HTTP DNS request when receiving the HTTP DNS request from the terminal, and sends the processed HTTP DNS request to the 5GC Proxy, where the 5GC Proxy is a system module added to the present disclosure based on the 5G core network.
In some embodiments, the central UPF may detect the target access address of the HTTP DNS request, and if it matches the access address information of the service stored in step 101, perform an operation of inserting the information and forwarding to the 5GC Proxy.
In some embodiments, the inserted information may be inserted into the header field of the HTTP DNS request for subsequent resolution. In some embodiments, the central UPF may also insert the terminal handset number in the HTTP DNS request.
In some embodiments, the hub UPF may cause the HTTP DNS request to be sent to the 5GC Proxy by replacing the destination address of the HTTP DNS request with the address of the 5GC Proxy.
In step 103, the 5GC Proxy replaces the wireless location information in the HTTP DNS request with the MEC identifier corresponding to the geographical location, and then forwards the wireless location information to the HTTP DNS server corresponding to the access address information.
In some embodiments, the 5GC Proxy may replace the destination address of the HTTP DNS request with the access address information, thereby enabling the information to be sent to the HTTP DNS server corresponding to the access address information.
In step 104, the 5GC Proxy receives the HTTP DNS response fed back by the HTTP DNS server. In some embodiments, the HTTP DNS server determines the area where the terminal is located according to the MEC identifier, determines an access address of an application server on the corresponding MEC node, and generates an HTTP DNS response.
In step 105, the 5GC Proxy initiates a UPF/ULCL insertion to the PCF entity, completes the local breakout request, and further forwards the HTTP DNS response to the user terminal. After receiving the message, the user terminal initiates a service request, and the service flow is shunted to the local MEC by the edge UPF, thereby realizing the near access of the application server.
In some embodiments, the 5GC Proxy may save the header information of the received HTTP DNS request in step 103 above, so that a UPF/ULCL insertion may be initiated to the PCF in step 105 based on the header information and the HTTP DNS response.
By the method, the MEC identifier capable of reflecting the position of the terminal can be inserted into the HTTP DNS request initiated by the terminal through improvement of a network side, so that an application server for providing service is distributed nearby by an application scheduling system according to the MEC identifier, and the address of the distributed application server is fed back to the terminal, thereby realizing local traffic distribution, shortening the forwarding path of the user access edge application, reducing the network traffic burden and improving the user access speed.
In addition, information inserted in the HTTP DNS request can be terminated in a 5GC Proxy terminal center UPF, so that the privacy information of a user is prevented from being leaked; the 5GC Proxy can replace a third-party application/application scheduling system, initiates an edge UPF/ULCL insertion flow to a core network, does not need the third-party application scheduling system to modify and call an API (application program interface), reduces the introduction threshold of a partner, and is beneficial to popularization and application.
In some embodiments, the central UPF may also insert the terminal number in the header field of the HTTP DNS request in case of receiving the HTTP DNS request from the terminal. After the 5GC Proxy receives an HTTP DNS response from an HTTP DNS server, determining a terminal attribution province according to a terminal number; and further initiates the UPF/ULCL insertion to PCF of the terminal number home province, or initiates the UPF/ULCL insertion after addressing to PCF of the home province through BSF (Binding Support Function) entity of the home province.
By the method, the cross-provincial CDN service deployment can be realized, the application servers of the cross-provincial users can be distributed nearby, and the service deployment range is expanded.
A flow diagram of further embodiments of the traffic scheduling method of the present disclosure is shown in fig. 2.
In step 201, the central DNS receives a DNS request from a user terminal and feeds back a DNS response to the user terminal via the central UPF.
In step 202, the central UPF records access address information of a service corresponding to the DNS response and forwards the DNS response to the UE, when receiving the DNS response from the central DNS. In some embodiments, the central UPF may pre-deploy an activation policy of the service scheduling method of the present disclosure, including: the domain name information configuration of the HTTP DNS server supporting the application of the service scheduling method disclosed by the invention starts the functions of domain name detection, information insertion, message forwarding and the like. In some embodiments, the application supporting the traffic scheduling method of the present disclosure may be an owned or cooperative application of a 5G operator, whose HTTP DNS server has the capability to allocate application servers nearby according to MEC identification.
In some embodiments, if the access address information in the DNS response is an own application or a cooperative application of a 5G operator supporting the CDN, performing recording of the access address information of a service corresponding to the DNS response, and subsequent operations; otherwise, the processing is performed according to the conventional flow in the related art.
In step 203, the center UPF inserts the terminal number, the terminal private network address, the wireless location information, the slice information, and the access address information into the header field of the HTTP DNS request in the case where the HTTP DNS request is received from the terminal.
In some embodiments, the central UPF may obtain the access address for which the HTTP DNS request is intended after receiving the request, and determine that step 204 needs to be performed if the access address information matches the access address information for the service previously obtained from the DNS response. In some embodiments, when the central UPF determines that the access address of the HTTP DNS request does not match the access address information of the stored service, the processing proceeds according to a conventional flow without performing the subsequent step 204.
In step 204, the center UPF replaces the destination address of the HTTP DNS request with the address of the 5GC Proxy, and transmits the HTTP DNS request according to the replaced destination address.
In step 205, the 5GC Proxy stores the header field information of the received HTTP DNS request, and replaces the wireless location information in the HTTP DNS request with the MEC identifier of the corresponding geographical location. The MEC identification can carry geographical location information, such as GD-GZ-MEC01, and the HTTP DNS server can determine the area of the terminal according to the MEC identification and further distribute the application server nearby. In some embodiments, the 5GC Proxy may delete the information inserted in the UPF in step 203 in the HTTP DNS request, and only insert the MEC identifier, so as to better avoid the leakage of the user privacy information.
In step 206, the 5GC Proxy replaces the destination address of the HTTP DNS request with the access address information, and transmits the HTTP DNS request in accordance with the replaced address.
In step 207, the 5GC Proxy receives the HTTP DNS response fed back by the HTTP DNS server. In some embodiments, the HTTP DNS response includes the IP address and port information of the application server.
In step 208, a UPF/ULCL insertion is initiated to the PCF of the terminal number's home province. The home province may be determined from the terminal number. In some embodiments, the UPF/ULCL insertion is initiated after the PCF of the home province is addressed by the BSF of the home province.
In step 209, the HTTP DNS response is forwarded to the user terminal.
By the method, the province of the user mobile phone number can be judged first, and then the message is forwarded to the core network equipment of the province of the user to realize the UPF/ULCL insertion, so that the cross-province CDN service deployment is realized, the access accuracy of the application server is improved, and the service deployment range is expanded.
A schematic diagram of some embodiments of the traffic scheduling system of the present disclosure is shown in fig. 3.
The central UPF 31 can obtain the access address information of the service according to the DNS response sent by the central DNS to the user terminal. In the case of receiving an HTTP DNS request from a terminal, a terminal private network address, wireless location information, slice information, and access address information are inserted in the HTTP DNS request. In some embodiments, the central UPF may insert the terminal private network address, wireless location information, slice information, and access address information into the header field of the HTTP DNS request. In some embodiments, information such as private IP address/port inserted in HTTP DNS request is used for 5GC Proxy to construct 5-tuple, initiate ULCL insertion, and the inserted wireless location information is used for service scheduling with scheduling system.
After completing the processing of the HTTP DNS request, the center UPF 31 sends the request to the 5GC Proxy.
The 5GC Proxy32 is able to receive HTTP DNS requests from the central UPF 31. In some embodiments, the 5GC Proxy32 may store header domain information of the HTTP DNS request for subsequent use. The 5GC Proxy32 replaces the wireless position information in the HTTP DNS request with the MEC identifier corresponding to the geographic position, and forwards the request to the HTTP DNS server corresponding to the access address information after the replacement is completed. And after receiving the HTTP DNS response fed back by the HTTP DNS server, initiating UPF/ULCL insertion to the PCF entity, and then forwarding the HTTP DNS response to the user terminal so that the user terminal can access the application server through the corresponding edge UPF. In some embodiments, the 5GC Proxy32 may initiate a UPF/ULCL insertion to the PCF based on the header information of the HTTP DNS request and the HTTP DNS response.
The service scheduling system can insert the MEC identifier capable of reflecting the position of the terminal into the HTTP DNS request initiated by the terminal through improvement of a network side, so that the application scheduling system can distribute the application server for providing service nearby according to the MEC identifier and feed back the address of the distributed application server to the terminal, thereby realizing local flow distribution, shortening the forwarding path of the user access edge application, reducing the network flow burden and improving the user access speed.
In some embodiments, since the 5GC Proxy32 can terminate the information inserted by the center UPF in the HTTP DNS request, for example, replacing the wireless network location information with the MEC identifier, leakage of user privacy information can be avoided; the 5GC Proxy32 can replace a third-party application/application scheduling system, initiate an edge UPF/ULCL insertion flow to a core network, do not need the third-party application scheduling system to be modified to carry out API interface calling, reduce the introduction threshold of a partner and be beneficial to popularization and application.
In some embodiments, the central UPF 31 is also able to insert the terminal number in the HTTP DNS request (e.g. header) after receiving the HTTP DNS request from the terminal. The 5GC Proxy32 can determine the terminal attribution province according to the terminal number after receiving the HTTP DNS response from the HTTP DNS server; and initiating UPF/ULCL insertion to PCF of the home province of the terminal number, or after addressing the PCF of the home province through the BSF of the home province, initiating UPF/ULCL insertion.
The service scheduling system can realize the cross-provincial CDN service deployment, realize the near distribution of the application servers of the cross-provincial users and enlarge the deployment range of the service.
In some embodiments, as shown in fig. 3, the service scheduling system may further comprise a central DNS 33 capable of receiving DNS requests from the user terminals and feeding back DNS responses to the user terminals via the central UPF.
The central UPF 31 can record the access address information of the service corresponding to the DNS response after receiving the DNS response from the central DNS, and forward the DNS response to the UE.
The service scheduling system can enable the center UPF to obtain the access address information of the service through the process that the terminal initiates the request to the center DNS, so that the information can be conveniently identified under the condition that the HTTP DNS request from the terminal is subsequently received, the operation of inserting the information such as the private network address into the header field and forwarding the request to the 5GC Proxy is executed, the requests aiming at different applications can be conveniently distinguished, and the processing efficiency is improved.
Fig. 4A shows a schematic diagram of some embodiments of the service scheduling system in a network, where a 5GC Proxy function module is introduced into a core network, a dashed line with an arrow in the diagram is a service scheduling process, and after scheduling is completed, service access is completed through a path shown by a thick line with an arrow. A signaling flow diagram of the process of traffic scheduling may be as shown in fig. 4B.
In 411, a UE (User Element) initiates a DNS request to obtain an application scheduling system address, which may be shown as (r) in fig. 4A.
In 412a, the central DNS returns a response message, and after the central UPF detects the domain name information of the HTTP DNS server of its own or a partner and records the corresponding IP address, the central UPF normally returns the response message to the UE in 412b, which may be as shown in (ii) of fig. 4A.
In 413a, the UE initiates an HTTP DNS request, the central UPF detects the request according to the IP address obtained in (c), further inserts the UE private network IP address, wireless location information, mobile phone number, slice information, HTTP DNS IP, etc. into the HTTP header, replaces the destination IP with a 5GC Proxy address, and sends it to the 5GC Proxy through 413 b.
In 413b, the 5GC Proxy receives the HTTP DNS request, stores the header information, converts the wireless location information in the header of the HTTP DNS request into a corresponding MEC identifier with a geographical location (e.g., GD-GZ-MEC01), inserts the HTTP, replaces the destination IP with HTTP DNS IP in the header, and sends it to the HTTP DNS server. This process may be as shown in fig. 4A.
In 414a, the HTTP DNS server receives the HTTP DNS request, allocates an application server on the corresponding MEC node to the UE according to the MEC identifier in the request, and sends the IP address, port, and the like of the application server to the 5GC Proxy in the HTTP DNS response message. The 5GC Proxy initiates an edge UPF/ULCL insertion to the core network PCF in 414b according to the information received in the above two steps, and further forwards the HTTP DNS response to the UE in 414c, as shown in the ((r) of fig. 4A).
In 415, the UE accesses the edge MEC node traffic through the edge UPF (local UPF as shown in the figure), as shown by (c) in fig. 4A.
The service scheduling system can realize provincial deployment of the CDN based on the 5G SA, does not need improvement of a user terminal side, only needs to modify an interface and support service scheduling according to the MEC identification for an application side, reserves the existing service scheduling mechanism to the maximum extent, is small in modification amount, reduces the introduction threshold of application, and is beneficial to popularization and application.
A schematic diagram of further embodiments of the traffic scheduling system of the present disclosure in a network is shown in fig. 5A.
In 511, a UE (User Element) initiates a DNS request to obtain an application scheduling system address, which may be shown as (r) in fig. 5A.
In 512a, the central DNS returns a response message, the central UPF detects the domain name information of the HTTP DNS server of its own or a partner, records the corresponding IP address, and then normally returns the response message to the UE in 512b, which may be as shown in (ii) of fig. 5A.
In 513a, the UE initiates an HTTP DNS request, the central UPF detects the request according to the IP address obtained in (2), further inserts the UE private network IP address, wireless location information, mobile phone number, slice information, HTTP DNS IP, and the like in the HTTP header, replaces the destination IP with a 5GC Proxy address, and sends the address to the 5GC Proxy through 513 b.
In 513b, the 5GC Proxy receives the HTTP DNS request, stores the header information, converts the wireless location information in the header of the HTTP DNS request into a corresponding MEC identifier with a geographic location (e.g., GD-GZ-MEC01), inserts the HTTP, replaces the destination IP with HTTP DNS IP in the header, and sends the HTTP DNS request to the HTTP DNS server. This process may be as shown in fig. 5A.
In 514a, the HTTP DNS server receives the HTTP DNS request, allocates an application server on the corresponding MEC node to the UE according to the MEC identifier in the request, and sends the IP address, the port, and the like of the application server to the 5GC Proxy in the HTTP DNS response message. The 5GC Proxy searches the home province according to the identification information such as the user mobile phone number received from 513b in 514b according to the information received from the two steps, forwards the information to the PCF/NEF of the home province, or addresses the PCF through the BSF of the home province, and initiates edge UPF/ULCL insertion to the PCF. The HTTP DNS response is further forwarded to the UE at 514c as shown by (r) in fig. 5A.
In 515, the UE accesses the edge MEC node traffic through an edge UPF (local UPF as shown in the figure).
The service scheduling system can realize 5G SA-based trans-provincial and group-level deployment of the CDN, does not need improvement of a user terminal side, only needs to modify an interface and support service scheduling according to the MEC identification for an application side, furthest reserves the conventional service scheduling mechanism, is small in modification amount, reduces the introduction threshold of application, and is favorable for popularization and application.
A schematic structural diagram of an embodiment of the service scheduling system of the present disclosure is shown in fig. 6. The traffic scheduling system comprises a memory 601 and a processor 602. Wherein: the memory 601 may be a magnetic disk, flash memory, or any other non-volatile storage medium. The memory is for storing instructions in the corresponding embodiments of the traffic scheduling method above. Processor 602 is coupled to memory 601 and may be implemented as one or more integrated circuits, such as a microprocessor or microcontroller. The processor 602 is used for executing instructions stored in the memory, and can reduce network traffic load and improve user access speed.
In one embodiment, as also shown in fig. 7, a traffic scheduling system 700 includes a memory 701 and a processor 702. Processor 702 is coupled to memory 701 by a BUS BUS 703. The service scheduling system 700 may also be connected to an external storage 705 via a storage interface 704 for invoking external data, and may also be connected to a network or another computer system (not shown) via a network interface 706. And will not be described in detail herein.
In the embodiment, the data instructions are stored in the memory and processed by the processor, so that the network traffic load can be reduced and the user access speed can be increased.
In another embodiment, a computer-readable storage medium has stored thereon computer program instructions which, when executed by a processor, implement the steps of the method in the corresponding embodiment of the service scheduling method. As will be appreciated by one skilled in the art, embodiments of the present disclosure may be provided as a method, apparatus, or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
A schematic diagram of some embodiments of the business service system of the present disclosure is shown in fig. 8.
The traffic scheduling system 81 may be any of those mentioned above.
The application scheduling server 82, such as an HTTP DNS server, can allocate an access address of the application server on the corresponding MEC node to the UE according to the MEC identifier in the HTTP DNS request from the service scheduling system, and send the access address of the application server to the 5GC Proxy through an HTTP DNS response. In some embodiments, on the basis of applying an existing scheduling server, the capability of supporting service scheduling according to the MEC identifier may be added, and a service server within a corresponding range may be determined according to the MEC identifier.
The service system can insert the MEC identifier capable of reflecting the position of the terminal into the HTTP DNS request initiated by the terminal through improvement of a network side, the application scheduling system distributes the application servers providing services nearby according to the MEC identifier and feeds back the address of the distributed application server to the terminal, so that local flow distribution is realized, the forwarding path of the user accessing edge application is shortened, the network flow burden is reduced, and the user access speed is improved.
The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Thus far, the present disclosure has been described in detail. Some details that are well known in the art have not been described in order to avoid obscuring the concepts of the present disclosure. It will be fully apparent to those skilled in the art from the foregoing description how to practice the presently disclosed embodiments.
The methods and apparatus of the present disclosure may be implemented in a number of ways. For example, the methods and apparatus of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.
Finally, it should be noted that: the above examples are intended only to illustrate the technical solutions of the present disclosure and not to limit them; although the present disclosure has been described in detail with reference to preferred embodiments, those of ordinary skill in the art will understand that: modifications to the specific embodiments of the disclosure or equivalent substitutions for parts of the technical features may still be made; all such modifications are intended to be included within the scope of the claims of this disclosure without departing from the spirit thereof.

Claims (13)

1. A service scheduling method comprises the following steps:
a central user plane function UPF acquires access address information of a service according to a DNS response sent to a user terminal by a central domain name system DNS;
the method comprises the steps that under the condition that a hypertext transfer protocol (HTTP) DNS request from a terminal is received, a terminal private network address, wireless position information, slice information and access address information are inserted into the HTTP DNS request by the central UPF, and the processed HTTP DNS request is sent to a 5G core network Proxy 5GC Proxy;
the 5GC Proxy forwards the wireless position information in the HTTP DNS request to an HTTP DNS server corresponding to the access address information after replacing the wireless position information in the HTTP DNS request with a Mobile Edge Computing (MEC) identifier of a corresponding geographic position;
the 5GC Proxy receives an HTTP DNS response fed back by an HTTP DNS server, wherein the HTTP DNS server determines an access address of an application server on a corresponding MEC node according to the MEC identifier to generate the HTTP DNS response;
and after initiating UPF/uplink classifier ULCL insertion to a policy control function PCF entity, the 5GC Proxy forwards the HTTP DNS response to the user terminal so that the user terminal can access the application server through the corresponding edge UPF.
2. The method of claim 1, wherein the central UPF sending the processed HTTP DNS request to a 5GC Proxy comprises:
and the center UPF replaces the destination address of the HTTP DNS request with the address of the 5GC Proxy and sends the HTTP DNS request according to the replaced destination address.
3. The method of claim 2, wherein the 5GC Proxy sending the processed HTTP DNS request to an HTTP DNS server comprises:
the 5GC Proxy replaces the destination address of the HTTP DNS request with the access address information.
4. The method of claim 1, wherein the central UPF inserts a terminal private network address, wireless location information, slice information, and the access address information into a header field of the HTTP DNS request;
further comprising: and the 5GC Proxy stores the header domain information of the received HTTP DNS request so as to initiate UPF/ULCL insertion to the PCF according to the header domain information and the HTTP DNS response.
5. The method of claim 1, further comprising:
the method comprises the steps that a center UPF inserts a terminal number into an HTTP DNS request under the condition that the HTTP DNS request from a terminal is received;
after receiving the HTTP DNS response from the HTTP DNS server, the 5GC Proxy determines the terminal attribution province according to the terminal number;
the initiating the UPF/ULCL insertion to the PCF comprises: and initiating UPF/ULCL insertion to PCF of the home province of the terminal number or after addressing the PCF of the home province through a Binding Support Function (BSF) entity of the home province.
6. The method according to claim 1, wherein the obtaining, by the central UPF, the access address information of the service according to the DNS response sent by the central domain name system DNS to the user terminal includes:
the central DNS receives a DNS request from a user terminal, and a DNS response is fed back to the user terminal through the central UPF;
and the central UPF records the access address information of the service corresponding to the DNS response and forwards the DNS response to the UE under the condition of receiving the DNS response from the central DNS.
7. A traffic scheduling system comprising:
the central user plane function UPF is configured to acquire access address information of a service according to a DNS response sent to the user terminal by a central domain name system DNS; under the condition of receiving a hypertext transfer protocol (HTTP) DNS request from a terminal, inserting a terminal private network address, wireless position information, slice information and access address information into the HTTP DNS request, and sending the processed HTTP DNS request to a 5G core network Proxy 5GC Proxy;
the 5GC Proxy is configured to replace the wireless location information in the HTTP DNS request with a Mobile Edge Computing (MEC) identifier of a corresponding geographic location, and forward the HTTP DNS request to an HTTP DNS server corresponding to the access address information; receiving an HTTP DNS response fed back by an HTTP DNS server, wherein the HTTP DNS server determines an access address of an application server on a corresponding MEC node according to the MEC identifier and generates the HTTP DNS response; initiating UPF/uplink classifier ULCL insertion to a policy control function PCF entity; and forwarding the HTTP DNS response to the user terminal so that the user terminal can access the application server through the corresponding edge UPF.
8. The system of claim 7, wherein the central UPF is configured to insert a terminal private network address, wireless location information, slice information, and the access address information into a header of the HTTP DNS request;
the 5GC Proxy is further configured to save header information of the received HTTP DNS request to initiate a UPF/ULCL insertion to the PCF based on the header information and the HTTP DNS response.
9. The system of claim 7, wherein,
the central UPF is also configured to insert the terminal number in the HTTP DNS request in case of receiving the HTTP DNS request from the terminal;
the 5GC Proxy is further configured to determine a terminal attribution province according to the terminal number after receiving an HTTP DNS response from the HTTP DNS server; and initiating UPF/ULCL insertion to PCF of the home province of the terminal number or after addressing the PCF of the home province through a Binding Support Function (BSF) entity of the home province.
10. The system of claim 7, further comprising:
the central DNS is configured to receive a DNS request from a user terminal and feed back a DNS response to the user terminal through the central UPF;
the central UPF is configured to record access address information of a service corresponding to a DNS response and forward the DNS response to the UE, in case of receiving the DNS response from the central DNS.
11. A traffic scheduling system comprising:
a memory; and
a processor coupled to the memory, the processor configured to perform the method of any of claims 1-6 based on instructions stored in the memory.
12. A computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement the steps of the method of any one of claims 1 to 6.
13. A business service system comprising:
the service scheduling system of any one of claims 7 to 11; and
and the application scheduling server is configured to calculate an MEC identifier according to a mobile edge in a hypertext transfer protocol domain name system (HTTP) DNS request from the service scheduling system, allocate an access address of the application server on a corresponding MEC node for the terminal, and send the access address of the application server to the 5G core network Proxy 5GC Proxy through a HTTP DNS response.
CN202011276737.8A 2020-11-16 2020-11-16 Service scheduling method, system, storage medium and service system Active CN114513494B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011276737.8A CN114513494B (en) 2020-11-16 2020-11-16 Service scheduling method, system, storage medium and service system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011276737.8A CN114513494B (en) 2020-11-16 2020-11-16 Service scheduling method, system, storage medium and service system

Publications (2)

Publication Number Publication Date
CN114513494A true CN114513494A (en) 2022-05-17
CN114513494B CN114513494B (en) 2024-03-19

Family

ID=81546228

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011276737.8A Active CN114513494B (en) 2020-11-16 2020-11-16 Service scheduling method, system, storage medium and service system

Country Status (1)

Country Link
CN (1) CN114513494B (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115002837A (en) * 2022-05-25 2022-09-02 中国联合网络通信集团有限公司 Shunting method, communication vehicle, CDN (content delivery network) scheduling server and system
CN115460091A (en) * 2022-09-09 2022-12-09 中国电信股份有限公司 Edge service processing method and device, storage medium and electronic equipment

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109246783A (en) * 2017-05-27 2019-01-18 中兴通讯股份有限公司 A kind of method, apparatus and system of route test
CN110098947A (en) * 2018-01-31 2019-08-06 华为技术有限公司 A kind of dispositions method of application, equipment and system
CN110535930A (en) * 2019-08-22 2019-12-03 网宿科技股份有限公司 A kind of dispatching method and system of edge C DN node
CN111711670A (en) * 2020-05-29 2020-09-25 腾讯科技（深圳）有限公司 Service connection request response method, system, device, medium and electronic equipment

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109246783A (en) * 2017-05-27 2019-01-18 中兴通讯股份有限公司 A kind of method, apparatus and system of route test
CN110098947A (en) * 2018-01-31 2019-08-06 华为技术有限公司 A kind of dispositions method of application, equipment and system
CN110535930A (en) * 2019-08-22 2019-12-03 网宿科技股份有限公司 A kind of dispatching method and system of edge C DN node
CN111711670A (en) * 2020-05-29 2020-09-25 腾讯科技（深圳）有限公司 Service connection request response method, system, device, medium and electronic equipment

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
3RD GENERATION PARTNERSHIP PROJECT: "Technical Specification Group Services and System Aspects; Study on enhancement of support for Edge Computing in 5G Core network (5GC)", 3GPP TR 23.748, 30 September 2020 (2020-09-30) *
CHINA TELECOM: "S2-2003552，Solution for KI#1: IP address discovery based on LDNS", SA WG2 MEETING #S2-139E, 12 June 2020 (2020-06-12) *
MOTOROLA MOBILITY 等: "KI#1, new solution: Edge Application Server discovery using an Address Resolution Function", 3GPP TSG SA2 MEETING #139E, 12 June 2020 (2020-06-12) *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115002837A (en) * 2022-05-25 2022-09-02 中国联合网络通信集团有限公司 Shunting method, communication vehicle, CDN (content delivery network) scheduling server and system
CN115460091A (en) * 2022-09-09 2022-12-09 中国电信股份有限公司 Edge service processing method and device, storage medium and electronic equipment
CN115460091B (en) * 2022-09-09 2024-07-26 中国电信股份有限公司 Edge service processing method and device, storage medium and electronic equipment

Also Published As

Publication number Publication date
CN114513494B (en) 2024-03-19

Similar Documents

Publication Publication Date Title
JP5575928B2 (en) Various source message associations
US8204482B2 (en) Efficient network resource management in a wireless network
US9002334B2 (en) Systems and methods for delivering multimedia information to mobile devices
CN110247848B (en) Method for sending message, network equipment and computer readable storage medium
WO2018233419A1 (en) Information processing method and apparatus
CN114513494B (en) Service scheduling method, system, storage medium and service system
CN108882305A (en) A kind of shunt method and device of data packet
WO2021197155A1 (en) Communication method and device
WO2014075450A1 (en) Resource download method, service server and cellular phone client
KR20140021372A (en) Contents delivery service method and local cache apparatus using contents identification
CN112825524B (en) Method, device and system for determining network service node
CN114189851A (en) IP address allocation method, SMF and storage medium
CN111050355B (en) Method, device and system for dynamically adjusting Qos of mobile terminal
CN101925158A (en) System and method for obtaining number detail
CN113422772B (en) Private network terminal access processing method and device and electronic equipment
WO2022057497A1 (en) Network capability exposure method, device, and storage medium
CN114598676A (en) Application addressing method, system and storage medium
CN113938814A (en) Service scheduling method, UPF, system and medium for content distribution network
US10728828B2 (en) IP address management method and apparatus, IP address anchor, and mobile node
CN110582090A (en) CDN scheduling method, scheduling system and MEC network element
CN112752300B (en) Method and device for realizing local distribution
WO2022077246A1 (en) System and methods for identifying edge application server
US8473625B1 (en) Preservation of network address translation (NAT) state across wireless sessions
CN114257634B (en) Server discovery method, device and storage medium
JP6807952B2 (en) Methods and devices for determining the communication network that provides communication services to terminal communication devices

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