CN114513494B - 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
CN114513494B
CN114513494B CN202011276737.8A CN202011276737A CN114513494B CN 114513494 B CN114513494 B CN 114513494B CN 202011276737 A CN202011276737 A CN 202011276737A CN 114513494 B CN114513494 B CN 114513494B
Authority
CN
China
Prior art keywords
http
upf
http dns
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.)
Active
Application number
CN202011276737.8A
Other languages
Chinese (zh)
Other versions
CN114513494A (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

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

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 disclosed by the invention comprises the following steps: the central user plane function UPF obtains access address information of the service according to DNS response sent to the user terminal by the 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 wireless position information in the HTTP DNS request with a mobile edge calculation MEC identification corresponding to the geographic position, and forwards the MEC identification to an HTTP DNS server corresponding to the access address information; the 5GC Proxy receives the HTTP DNS response fed back by the HTTP DNS server, initiates UPF/ULCL insertion to the policy control function PCF entity, and forwards the HTTP DNS response to the user terminal, thereby realizing local flow distribution, reducing network flow burden and improving user access speed.

Description

Service scheduling method, system, storage medium and service system
Technical Field
The disclosure relates to the technical field of mobile edge computing, in particular to a service scheduling method, a service scheduling system, a storage medium and a service system.
Background
In the CDN (Content Delivery Network) architecture, servers accessed by users are distributed nearby, so as to achieve the effects of improving the access speed of the users and reducing the network load. In the 4G network deployment, because PGW (PDN Gateway) adopts a mode of centralized deployment in a provincial layer, MEC cannot be deployed close to a user, so that 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, UPF (User Plane Function ) can be deployed in a sinking mode as required, so that low-latency high-bandwidth CDN service deployment based on the 5G network is possible.
An object of the present disclosure is to propose a solution for implementing CDN services in a 5G SA network.
According to an aspect of some embodiments of the present disclosure, a service scheduling method is provided, including: the central UPF obtains access address information of the service according to DNS response sent to the user terminal by the central DNS (Domain Name System ); the central UPF inserts a private network address, wireless position information, slice information and access address information of the terminal in the HTTP DNS request and sends the processed HTTP DNS request to a 5GC Proxy (5G core network Proxy) under the condition that the HTTP (HyperText Transfer Protocol ) DNS request from the terminal is received; after replacing wireless position information in the HTTP DNS request with MEC (Mobile Edge Computing ) identification corresponding to the geographic position, the 5GC Proxy is forwarded to an HTTP DNS server corresponding to the access address information; 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, and generates the HTTP DNS response; after the 5GC Proxy initiates the UPF/ul cl (Uplink Classifier, upstream classifier) insertion to the PCF (Policy Control Function ) entity, the HTTP DNS response is forwarded to the user terminal so that the user terminal accesses the application server through the corresponding edge UPF.
In some embodiments, the sending of the processed HTTP DNS request by the central UPF to the 5GC Proxy comprises: 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.
In some embodiments, the sending of the processed HTTP DNS request by the 5GC Proxy to the HTTP DNS server comprises: 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 field information of the received HTTP DNS request to initiate UPF/ULCL insertion to the PCF based on the header field information and the HTTP DNS response.
In some embodiments, the service scheduling method further includes: the method comprises the steps that under the condition that the center UPF receives an HTTP DNS request from a terminal, a terminal number is inserted into the HTTP DNS request; after receiving the HTTP DNS response from the HTTP DNS server, the 5GC Proxy determines the terminal attribution province according to the terminal number; initiating a UPF/ULCL insertion to the PCF includes: the UPF/ULCL insertion is initiated to the PCF of the home province of the terminal number or is initiated after the PCF of the home province is addressed through the BSF of the home province.
In some embodiments, the obtaining, by the central UPF, access address information of the service according to a 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 feeds back a DNS response to the user terminal through the center UPF; and under the condition that the central UPF receives the DNS response from the central DNS, recording access address information of the service corresponding to the DNS response, and forwarding the DNS response to the UE.
By the method, MEC (media access control) identifiers capable of reflecting the positions of the terminals can be inserted into HTTP DNS requests initiated by the terminals through improvement of the network side, so that an application server for providing services is distributed nearby by an application scheduling system according to the MEC identifiers, the addresses of the distributed application servers are fed back to the terminals, local flow distribution is achieved, forwarding paths of users for accessing edge applications are shortened, network flow burden is reduced, and user access speed is improved.
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 access address information of the service according to DNS response sent to the user terminal by the center DNS; under the condition that an HTTP DNS request from a terminal is received, inserting a private network address, wireless position information, slice information and access address information of the terminal into the HTTP DNS request, and sending the processed HTTP DNS request to a 5GC Proxy;5GC Proxy configured to replace wireless location information in the HTTP DNS request with MEC identification of the 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/ULCL insertion to PCF entity; the HTTP DNS response is forwarded to the user terminal for the user terminal to access the application server via the corresponding edge UPF.
In some embodiments, the central UPF is configured to insert the terminal private network address, wireless location information, slice information, and access address information into a header field of the HTTP DNS request; the 5GC Proxy is further configured to save header field information of the received HTTP DNS request to initiate a UPF/ULCL insertion to the PCF based on the header field 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 if the HTTP DNS request is received from the terminal; the 5GC Proxy is further configured to determine a terminal attribution province according to the terminal number after receiving the HTTP DNS response from the HTTP DNS server; the UPF/ULCL insertion is initiated to the PCF of the home province of the terminal number or is initiated after the PCF of the home province is addressed through the BSF of the home province.
In some embodiments, the traffic scheduling system further comprises: a central DNS configured to receive a DNS request from the user terminal, and to feed back a DNS response to the user terminal via the central UPF; the central UPF is configured to record access address information of a service corresponding to the DNS response and forward the DNS response to the UE, in case of receiving the DNS response from the central DNS.
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 mark capable of reflecting the terminal position in the HTTP DNS request initiated by the terminal through the improvement of the network side, so that the application scheduling system can distribute the application servers for providing the service nearby according to the MEC mark and feed back the addresses of the distributed application servers to the terminal, thereby realizing the local flow distribution of the flow, shortening the forwarding path of the user for accessing the 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 having stored thereon computer program instructions which, when executed by a processor, implement the steps of any of the traffic scheduling methods above is presented.
By executing the instructions on the computer readable storage medium, MEC (media access control) identifiers capable of reflecting the positions of the terminals can be inserted into HTTP DNS requests initiated by the terminals through improvement of the network side, so that an application scheduling system can distribute application servers for providing services nearby according to the MEC identifiers, and the addresses of the distributed application servers are fed back to the terminals, thereby realizing local flow distribution, shortening forwarding paths of users for accessing edge applications, reducing network flow burden and improving user access speed.
According to an aspect of some embodiments of the present disclosure, there is provided a business service system, comprising: any one of the above service scheduling systems; and the application scheduling server is configured to calculate MEC identification 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 an HTTP DNS response.
The business service system can insert MEC identification capable of reflecting the terminal position into HTTP DNS request initiated by the terminal through improvement of the network side, the application server for providing service is distributed nearby by the application scheduling system according to the MEC identification, and the address of the distributed application server is fed back to the terminal, so that flow local distribution is realized, the forwarding path of the user for accessing the 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, illustrate and explain the present disclosure, and together with the description serve to explain the present 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 flow chart of other embodiments of a traffic scheduling method of 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 a traffic 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 yet other embodiments of a traffic scheduling system of the present disclosure.
Fig. 7 is a schematic diagram of still other embodiments of a traffic scheduling system 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 scheme of the present disclosure is described in further detail below through the accompanying drawings and examples.
The inventor finds that in the related art, a terminal initiates a DNS request, acquires an access address of a scheduling system of an application, and further sends a request message to the scheduling system of the application 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 the access address of the nearby 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 it difficult for the application's scheduling system to correctly determine the application server that is close to the user's location, because the acquired user source IP address cannot match the edge MEC node location.
A flowchart of some embodiments of the traffic scheduling method of the present disclosure is shown in fig. 1.
In step 101, the central UPF obtains access address information of the service according to DNS response sent to the user terminal by the central DNS.
In some embodiments, when a user terminal initiates a service request, a DNS request is sent to the central DNS. The center DNS will feed back the access address information of the service after receiving the request. 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 will be sent to the terminal via the central UPF. 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 central UPF inserts the terminal private network address, the wireless location information, the slice information and the access address information in the HTTP DNS request in case of receiving the HTTP DNS request from the terminal, and sends the processed HTTP DNS request to the system module 5GC Proxy,5GC Proxy, which is added to the 5G core network based system according to the present disclosure.
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 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, after replacing the wireless location information in the HTTP DNS request with the MEC identifier of the corresponding geographic location, 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 to which the access address information corresponds.
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, according to the MEC identifier, an area in which the terminal is located, determines an access address of an application server on a corresponding MEC node, and generates an HTTP DNS response.
In step 105, the 5GC Proxy initiates a UPF/ULCL insertion to the PCF entity, completing the local breakout request, and forwarding 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 so as to realize the nearby access of the application server.
In some embodiments, 5GC Proxy may store header information of the received HTTP DNS request in step 103 described above, such 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, MEC (media access control) identifiers capable of reflecting the positions of the terminals can be inserted into HTTP DNS requests initiated by the terminals through improvement of the network side, so that an application server for providing services is distributed nearby by an application scheduling system according to the MEC identifiers, the addresses of the distributed application servers are fed back to the terminals, local flow distribution is achieved, forwarding paths of users for accessing edge applications are shortened, network flow burden is reduced, and user access speed is improved.
In addition, because the information can be inserted in the HTTP DNS request at the 5GC Proxy termination center UPF, the disclosure of the user privacy information is avoided; the 5GC Proxy can replace a third party application/application scheduling system, initiate an edge UPF/ULCL insertion flow to the core network, do not need to modify the third party application scheduling system to call an API interface, reduce the introduction threshold of a partner, and are 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 an HTTP DNS request is received from the terminal. After receiving the HTTP DNS response from the HTTP DNS server, the 5GC Proxy determines the terminal attribution province according to the terminal number; and then initiates UPF/ULCL insertion to PCF of the home province of the terminal number, or initiates UPF/ULCL insertion after the entity addresses to PCF of the home province through BSF (Binding Support Function ) of the home province.
By the method, cross-province CDN service deployment can be realized, near distribution of the application servers of the cross-province users is realized, and the service deployment range is enlarged.
A flowchart 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 the 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 in the case of receiving the DNS response from the central DNS, and forwards the DNS response to the UE. 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 disclosure 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 cooperated application of the 5G operator, whose HTTP DNS server has the ability to allocate application servers nearby according to MEC identification.
In some embodiments, if the access address information in the DNS response is an owned application or a cooperated application of the 5G operator supporting the CDN, performing recording the access address information of the service corresponding to the DNS response, and subsequent operations; otherwise, the processing is performed according to a conventional flow in the related art.
In step 203, the center UPF, upon receiving the HTTP DNS request from the terminal, 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 some embodiments, the central UPF may, upon receipt of an HTTP DNS request, obtain the access address for which the request is intended, and in case of a match with the access address information of the traffic previously obtained from the DNS response, determine that step 204 needs to be performed. 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, then the subsequent step 204 is not performed according to conventional flow processing.
In step 204, the hub 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.
In step 205, the 5GC Proxy stores header field information of the received HTTP DNS request, and replaces wireless location information in the HTTP DNS request with MEC identification of the corresponding geographic location. The MEC identifier can carry geographic location information, such as GD-GZ-MEC01, and the HTTP DNS server can determine the area of the terminal according to the MEC identifier, so that an application server is distributed recently. In some embodiments, the 5GC Proxy may delete the information inserted by the UPF in step 203 in the HTTP DNS request, and insert only the MEC identifier, so as to better avoid disclosure of user privacy information.
In step 206, the 5GC Proxy replaces the destination address of the HTTP DNS request with the access address information, and sends the HTTP DNS request according to 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 home province of the terminal number. The home province can be determined based on the terminal number. In some embodiments, the UPF/ULCL insertion may be initiated after the PCF of the home province is addressed through the BSF of the home province.
In step 209, the HTTP DNS response is forwarded to the user terminal.
By the method, the home province of the mobile phone number of the user can be judged first, and then the message is forwarded to core network equipment of the home province to realize UPF/ULCL insertion, so that the deployment of the cross-province CDN service is realized, the access accuracy of an application server is improved, and the service deployment range is enlarged.
A schematic diagram of some embodiments of the traffic scheduling system of the present disclosure is shown in fig. 3.
The center UPF 31 can acquire access address information of the service according to DNS response sent to the user terminal by the center DNS. 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, the private network IP address/port information inserted in the HTTP DNS request is used to construct a 5-tuple for 5GC Proxy, initiate ULCL insertion, and the inserted wireless location information provides for traffic scheduling by the 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 can receive an HTTP DNS request from the central UPF 31. In some embodiments, 5gc Proxy32 may store header field information of HTTP DNS requests for later use. The 5gc Proxy32 replaces the wireless location information in the HTTP DNS request with the MEC identification of the corresponding geographic location, and forwards the request to the HTTP DNS server corresponding to the access address information after the replacement is completed. After receiving the HTTP DNS response fed back by the HTTP DNS server, the UPF/ULCL insertion is initiated to the PCF entity, and then the HTTP DNS response is forwarded to the user terminal, so that the user terminal accesses the application server through the corresponding edge UPF. In some embodiments, 5GC Proxy32 may initiate a UPF/ULCL insertion to the PCF based on header field information of the HTTP DNS request and the HTTP DNS response.
The service scheduling system can insert the MEC mark capable of reflecting the terminal position in the HTTP DNS request initiated by the terminal through the improvement of the network side, so that the application scheduling system can distribute the application servers for providing the service nearby according to the MEC mark and feed back the addresses of the distributed application servers to the terminal, thereby realizing the local flow distribution of the flow, shortening the forwarding path of the user for accessing the 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, replace the wireless network location information with the MEC identifier, disclosure 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 the core network, do not need to modify the third party application scheduling system to call an API interface, reduce the introduction threshold of a partner, and are beneficial to popularization and application.
In some embodiments, the central UPF 31 is also capable of inserting the terminal number in the HTTP DNS request (e.g., header field) 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; the UPF/ULCL insertion is initiated to the PCF of the home province of the terminal number or is initiated after the PCF of the home province is addressed through the BSF of the home province.
The service scheduling system can realize the CDN service deployment of the cross-provinces, realize the nearby distribution of the application servers of the cross-province users, and enlarge the service deployment range.
In some embodiments, as shown in fig. 3, the traffic 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 center UPF 31 can record access address information of a service corresponding to the DNS response after receiving the DNS response from the center 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 information such as a private network address into a header domain and forwarding the request to a 5GC Proxy is performed, the requests aiming at different applications can be conveniently distinguished, and the processing efficiency is improved.
The schematic diagram of some embodiments of the service scheduling system in the present disclosure in the network is shown in fig. 4A, a 5GC Proxy function module is introduced in the core network, and the dashed line with an arrow in the figure is the service scheduling process, and after the scheduling is completed, the service access is completed through the path shown by the thick line with an arrow. A signaling flow diagram of the process of traffic scheduling may be as shown in fig. 4B.
In 411, the UE (User Element) initiates a DNS request to obtain an application scheduling system address, which may be as shown in (1) in fig. 4A.
In 412a, the center DNS returns a response message, and after the center UPF detects the domain name information of the HTTP DNS server of the own or partner and records the corresponding IP address, the response message is normally returned to the UE in 412b, which may be as shown in (2) in fig. 4A.
In 413a, the UE initiates an HTTP DNS request, and the central UPF detects the request according to the IP address acquired in (2), inserts the UE private IP address, wireless location information, handset number, slice information, HTTP DNS IP, etc. into the HTTP header, replaces the destination IP with a 5GC Proxy address, and sends the 5GC Proxy through 413 b.
In 413b, the 5GC Proxy receives the HTTP DNS request, saves the header field information, converts the wireless location information in the header field of the HTTP DNS request into a corresponding MEC identifier with a geographic location (e.g., GD-GZ-MEC 01), inserts HTTP, replaces the destination IP with HTTP DNS IP in the header field, and sends to the HTTP DNS server. This process may be as shown in fig. 4A (3).
In 414a, the HTTP DNS server receives the HTTP DNS request, allocates an application server on a corresponding MEC node to the UE according to the MEC identifier in the request, and sends the IP address and port of the application server to the 5GC Proxy in an HTTP DNS response message. Based on the two received information, the 5GC Proxy initiates an edge UPF/ULCL insertion to the core network PCF at 414b, and forwards the HTTP DNS response to the UE at 414c, as shown in (4) of fig. 4A.
In 415, the UE accesses edge MEC node traffic through an edge UPF (local UPF as shown in the figure), as shown in (5) in fig. 4A.
The service scheduling system can realize provincial deployment of CDN based on 5G SA, does not need improvement of a user terminal side, only needs to modify an interface and support service scheduling according to MEC identification for an application side, reserves the existing service scheduling mechanism to the maximum extent, has small 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, the UE (User Element) initiates a DNS request to obtain an application scheduling system address, which may be as shown in (1) in fig. 5A.
In 512a, the central DNS returns a response message, after the central UPF detects the domain name information of the HTTP DNS server of the own or partner, and records the corresponding IP address, the response message is normally returned to the UE in 512b, which may be as shown in (2) in fig. 5A.
In 513a, the UE initiates an HTTP DNS request, and the central UPF detects the request according to the IP address acquired in (2), inserts the UE private IP address, wireless location information, handset number, slice information, HTTP DNS IP, etc. into the HTTP header, replaces the destination IP with a 5GC Proxy address, and sends the 5GC Proxy through 513 b.
In 513b, the 5GC Proxy receives the HTTP DNS request, saves the header field information, converts the wireless location information in the header field of the HTTP DNS request into a corresponding MEC identifier with a geographic location (e.g., GD-GZ-MEC 01), inserts HTTP, replaces the destination IP with HTTP DNS IP in the header field, and sends to the HTTP DNS server. This process may be as shown in fig. 5A (3).
In 514a, the HTTP DNS server receives the HTTP DNS request, allocates an application server on a corresponding MEC node to the UE according to the MEC identifier in the request, and sends the IP address and port of the application server to the 5GC Proxy in an HTTP DNS response message. According to the information received in the two steps, the 5GC Proxy searches the home province according to the identification information such as the mobile phone number of the user received in 513b, forwards the information to the PCF/NEF of the home province, or addresses to the PCF through the BSF of the home province, and initiates the edge UPF/ULCL insertion to the PCF. The HTTP DNS response is then forwarded to the UE in 514c, as shown in fig. 5A (4).
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 cross-province and group level deployment of the CDN based on 5G SA, does not need improvement of a user terminal side, only needs an interface modification for an application side and supports service scheduling according to MEC identification, furthest reserves the existing service scheduling mechanism, has small modification amount, reduces the introduction threshold of application, and is beneficial to popularization and application.
A schematic structural diagram of one embodiment of a traffic 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 used to store instructions in the corresponding embodiments of the traffic scheduling method above. The processor 602 is coupled to the memory 601 and may be implemented as one or more integrated circuits, such as a microprocessor or microcontroller. The processor 602 is configured to execute instructions stored in the memory, so as to reduce network traffic load and increase user access speed.
In one embodiment, as also shown in fig. 7, the traffic scheduling system 700 includes a memory 701 and a processor 702. The processor 702 is coupled to the memory 701 through a BUS 703. The traffic scheduling system 700 may also be connected to external storage 705 via a storage interface 704 for invoking external data, and to a network or another computer system (not shown) via a network interface 706. And will not be described in detail herein.
In this embodiment, the data instruction is stored in the memory, and then the processor processes the instruction, so that the network traffic load can be reduced, and the access speed of the user can be improved.
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 embodiments of the traffic scheduling method. It will be apparent to those skilled in the art that 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, etc.) 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, the capability of supporting service scheduling according to the MEC identifier can be increased on the basis of applying the existing scheduling server, and the service server in the corresponding range is determined according to the MEC identifier.
The business service system can insert MEC identification capable of reflecting the terminal position into HTTP DNS request initiated by the terminal through improvement of the network side, the application server for providing service is distributed nearby by the application scheduling system according to the MEC identification, and the address of the distributed application server is fed back to the terminal, so that flow local distribution is realized, the forwarding path of the user for accessing the 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 flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations 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. In order to avoid obscuring the concepts of the present disclosure, some details known in the art are not described. How to implement the solutions disclosed herein will be fully apparent to those skilled in the art from the above description.
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, firmware. The above-described sequence of steps for the method is for illustration only, and the steps of the method of the present disclosure are not limited to the sequence specifically described above unless specifically stated otherwise. Furthermore, in some embodiments, the present disclosure may also be implemented 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 embodiments are merely for illustrating the technical solution of the present disclosure and are not limiting thereof; although the present disclosure has been described in detail with reference to preferred embodiments, those of ordinary skill in the art will appreciate that: modifications may be made to the specific embodiments of the disclosure or equivalents may be substituted for part of the technical features; without departing from the spirit of the technical solutions of the present disclosure, it should be covered in the scope of the technical solutions claimed in the present disclosure.

Claims (13)

1. A traffic scheduling method, comprising:
the central user plane function UPF obtains access address information of the service according to DNS response sent to the user terminal by the central domain name system DNS;
the center UPF inserts a private network address, wireless position information, slice information and access address information of a terminal into the HTTP DNS request under the condition that the HTTP DNS request from the terminal is received, and sends the processed HTTP DNS request to a 5G core network Proxy 5GC Proxy;
the 5GC Proxy is used for replacing the wireless position information in the HTTP DNS request with a mobile edge of a corresponding geographic position to calculate MEC identification and then forwarding the MEC identification to the HTTP DNS server corresponding to the access address information;
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, and generates the HTTP DNS response;
after the 5GC Proxy initiates UPF/uplink classifier ULCL insertion to the policy control function PCF entity, the HTTP DNS response is forwarded to the user terminal so that the user terminal accesses the application server through the corresponding edge UPF.
2. The method of claim 1, wherein the sending the processed HTTP DNS request by the central UPF to the 5GC Proxy comprises:
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 sending the processed HTTP DNS request by the 5GC Proxy 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 comprises: and the 5GC Proxy stores header field information of the received HTTP DNS request so as to initiate UPF/ULCL insertion to the PCF according to the header field information and the HTTP DNS response.
5. The method of claim 1, further comprising:
the method comprises the steps that under the condition that the center UPF receives an HTTP DNS request from a terminal, a terminal number is inserted into the HTTP DNS request;
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 UPF/ULCL insertion to the PCF comprises: the UPF/ULCL insertion is initiated to the PCF of the home province of the terminal number or is initiated after the address of the PCF of the home province is carried out through the binding support function BSF entity of the home province.
6. The method of claim 1, wherein the center UPF obtains access address information of the service according to DNS response sent to the user terminal by the center domain name system DNS, including:
the center DNS receives a DNS request from a user terminal, and feeds back a DNS response to the user terminal through the center UPF;
and under the condition that the central UPF receives the DNS response from the central DNS, recording access address information of the service corresponding to the DNS response, and forwarding the DNS response to the UE.
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 a user terminal by a central domain name system DNS; under the condition that a hypertext transfer protocol (HTTP) DNS request from a terminal is received, inserting a private network address, wireless position information, slice information and access address information of the terminal into the HTTP DNS request, and sending the processed HTTP DNS request to a 5G core network Proxy (5 GC Proxy);
the 5GC Proxy is configured to replace the wireless location information in the HTTP DNS request with a mobile edge computing MEC identifier corresponding to the 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/ULCL insertion of an uplink classifier to a policy control function PCF entity; and forwarding the HTTP DNS response to the user terminal so that the user terminal accesses 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 field of the HTTP DNS request;
the 5GC Proxy is further configured to save header field information of the received HTTP DNS request to initiate a UPF/ULCL insertion to the PCF based on the header field information and the HTTP DNS response.
9. The system of claim 7, wherein,
the central UPF is further configured to insert the terminal number in the HTTP DNS request in case of receipt of the HTTP DNS request from the terminal;
the 5GC Proxy is further configured to determine a terminal attribution province according to a terminal number after receiving an HTTP DNS response from an HTTP DNS server; the UPF/ULCL insertion is initiated to the PCF of the home province of the terminal number or is initiated after the address of the PCF of the home province is carried out through the binding support function BSF entity of the home province.
10. The system of claim 7, further comprising:
a central DNS configured to receive a DNS request from a user terminal, and to feed back a DNS response to the user terminal via 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 the 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 of claims 1 to 6.
13. A business service system, comprising:
the traffic scheduling system of any one of claims 7 to 11; and
and the application scheduling server is configured to calculate MEC identification according to a mobile edge in a HTTP DNS request from the service scheduling system, allocate an access address of an 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 CN114513494A (en) 2022-05-17
CN114513494B true 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)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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 (4)

* Cited by examiner, † Cited by third party
Title
3rd Generation Partnership Project.Technical Specification Group Services and System Aspects *
KI#1, new solution: Edge Application Server discovery using an Address Resolution Function;Motorola Mobility 等;3GPP TSG SA2 Meeting #139E;20200612;全文 *
S2-2003552，Solution for KI#1: IP address discovery based on LDNS;China Telecom;SA WG2 Meeting #S2-139E;20200612;全文 *
Study on enhancement of support for Edge Computing in 5G Core network (5GC).3GPP TR 23.748.2020,全文. *

Also Published As

Publication number Publication date
CN114513494A (en) 2022-05-17

Similar Documents

Publication Publication Date Title
CN109842906B (en) Communication method, device and system
JP5575928B2 (en) Various source message associations
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
WO2022033345A1 (en) Pdu session establishment method, terminal device, and chip system
US9585052B2 (en) Determining a traffic bearer for data traffic between a terminal and a content data source of a content data network
WO2014075450A1 (en) Resource download method, service server and cellular phone client
KR20140021372A (en) Contents delivery service method and local cache apparatus using contents identification
EP3917083A1 (en) Network device and method for searching for edge service implemented in network device
CN114513494B (en) Service scheduling method, system, storage medium and service system
US10425323B2 (en) Distributed producer mobility management in information centric networking
CN111050355A (en) Method, device and system for dynamically adjusting Qos of mobile terminal
CN110582090A (en) CDN scheduling method, scheduling system and MEC network element
US8473625B1 (en) Preservation of network address translation (NAT) state across wireless sessions
CN114629912B (en) Communication transmission method and device based on MEC
CN114257634B (en) Server discovery method, device and storage medium
CN112825524B (en) Method, device and system for determining network service node
WO2018090335A1 (en) Cache data requesting method and related device
JP6807952B2 (en) Methods and devices for determining the communication network that provides communication services to terminal communication devices
WO2017008288A1 (en) Ip address management method, device, ip address anchor and mobile node
CN115118786B (en) Edge service scheduling method, device and system and storage medium
CN114286450B (en) Bearer establishment method and device, electronic equipment and storage medium
CN113422772B (en) Private network terminal access processing method and device and electronic equipment
WO2021249213A1 (en) Information processing method, and network element and computer-readable storage medium
WO2024001561A1 (en) Construction method for data offloading system, network device, and storage medium

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