WO2020228505A1 - 一种移动边缘计算节点的选择方法、装置及系统 - Google Patents

一种移动边缘计算节点的选择方法、装置及系统 Download PDF

Info

Publication number
WO2020228505A1
WO2020228505A1 PCT/CN2020/086398 CN2020086398W WO2020228505A1 WO 2020228505 A1 WO2020228505 A1 WO 2020228505A1 CN 2020086398 W CN2020086398 W CN 2020086398W WO 2020228505 A1 WO2020228505 A1 WO 2020228505A1
Authority
WO
WIPO (PCT)
Prior art keywords
request
domain name
edge
cloud gateway
address
Prior art date
Application number
PCT/CN2020/086398
Other languages
English (en)
French (fr)
Inventor
游志强
楼佳嘉
Original Assignee
腾讯科技（深圳）有限公司
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 腾讯科技（深圳）有限公司 filed Critical 腾讯科技（深圳）有限公司
Priority to JP2021551817A priority Critical patent/JP7278679B2/ja
Priority to EP20806492.3A priority patent/EP3968610A4/en
Publication of WO2020228505A1 publication Critical patent/WO2020228505A1/zh
Priority to US17/380,585 priority patent/US11431673B2/en

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/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • 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]
    • 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
    • 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
    • H04L67/1021—Server selection for load balancing based on client or server locations
    • 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/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/561—Adding application-functional data or data for application control, e.g. adding metadata
    • 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/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/563—Data redirection of data network streams
    • 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/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/566—Grouping or aggregating service requests, e.g. for unified processing
    • 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/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • 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/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Definitions

  • This application relates to the field of mobile communications, and in particular to the selection of mobile edge computing nodes.
  • the embodiments of the present application provide a method, device, and system for selecting a mobile edge computing node to solve the problem that there is no MEC node selection solution for a 5G mobile communication network in the prior art.
  • an embodiment of the present application provides a method for selecting a mobile edge computing node.
  • the method is executed by an edge cloud gateway.
  • the edge cloud gateway is set in a mobile edge computing node selection system, and the system at least includes a user
  • the edge cloud gateway receives the domain name request forwarded by the user plane function, where the domain name in the domain name request is a preset service acceleration domain name, or the destination address is a global load balancing IP address; or, the protocol port information in the domain name request conforms to the preset Set protocol port requirements;
  • domain name response to the terminal through the user plane function, where the domain name response includes at least the edge application VIP;
  • the corresponding MEC processing server is determined, and the service request is distributed to the corresponding MEC processing server.
  • an embodiment of the present application provides an edge cloud gateway selected by a mobile edge computing node.
  • the edge cloud gateway is set in a mobile edge computing node selection system, and the system includes at least a user plane function, and the edge cloud gateway.
  • Cloud gateway and global load balancing including:
  • the first receiving module is configured to receive a domain name request forwarded by a user plane function, wherein the domain name in the domain name request is a preset service acceleration domain name, or the destination address is an IP address for global load balancing; or, the protocol in the domain name request
  • the port information meets the requirements of the preset protocol port;
  • An obtaining module configured to obtain, based on the domain name request, from the global load balancer, the corresponding protocol VIP for interconnection between edge application virtual networks;
  • a sending module configured to return a domain name response to the terminal through the user plane function, wherein the domain name response includes at least the edge application VIP;
  • the second receiving module is configured to receive the service request forwarded by the user plane function, wherein the destination address of the service request is the edge application VIP;
  • the determining module is used to determine the corresponding MEC processing server according to the service request and the preset offload strategy
  • the offloading module is used to offload the service request to the corresponding MEC processing server.
  • it further includes a recording module, configured to record the request status of the domain name request; wherein the request status represents a DNS request or a first HTTP DNS request.
  • the acquisition module is specifically used for:
  • a second HTTP DNS request is sent to the global load balancer, where the second HTTP DNS request includes at least a service acceleration domain name, a source address, and a destination address, and the source address is the edge cloud
  • the IP address of the gateway, and the destination address is the IP address of the global load balancing;
  • the first HTTP DNS response includes at least an edge application VIP
  • the edge application VIP is the global load balancer according to the IP address of the edge cloud gateway
  • the business acceleration domain name is determined.
  • the obtaining module is specifically configured to:
  • the request status of the domain name request is a DNS request
  • parse the domain name request obtain the domain name in the domain name request, and repackage the resolved domain name request into a second HTTP DNS request;
  • the sending module is specifically used for:
  • the request status of the domain name request is the first HTTP DNS request
  • the second HTTP DNS response is returned.
  • the user plane function, the edge cloud gateway, and the global load balance respectively correspond to different pre-configured rules, and the pre-configured rules represent routing configurations for service acceleration.
  • the user plane function corresponds to a first pre-configured rule
  • the first pre-configured rule at least includes: forwarding a domain name request whose domain name is a preset service acceleration domain name to an edge cloud gateway; or, The domain name request whose destination address is the IP address of the global load balancing is forwarded to the edge cloud gateway; or the service request whose destination address is the edge application VIP is forwarded to the edge cloud gateway;
  • the edge cloud gateway corresponds to a second pre-configured rule, and the second pre-configured rule includes at least: a preset offload strategy;
  • the global load balancing corresponds to a third pre-configured rule
  • the third pre-configured rule includes at least: HTTP DNS request for the IP address of the edge cloud gateway whose source address is based on the IP address and service of the edge cloud gateway in the HTTP DNS request
  • the accelerated domain name returns to the corresponding edge application VIP.
  • the user plane function corresponds to a fourth pre-configuration rule
  • the fourth pre-configuration rule at least includes: a domain name request whose protocol port information meets a preset protocol port requirement is forwarded to the edge cloud gateway; Or, the domain name request whose destination address is the IP address of the global load balancing is forwarded to the edge cloud gateway; or, the service request whose destination address is the edge application VIP is forwarded to the edge cloud gateway;
  • the edge cloud gateway corresponds to a fifth pre-configured rule, and the fifth pre-configured rule at least includes: a preset offload strategy; and has the ability to resolve DNS requests.
  • the first pre-configuration rule, the second pre-configuration rule, the fourth pre-configuration rule or the fifth pre-configuration rule are configured by a set edge controller, Or locally configured;
  • the edge controller is set in the cloud center of the core network in the system, and is respectively connected to the edge cloud gateway and the user plane function in communication.
  • the embodiment of the present application provides a system for selecting mobile edge computing nodes, which at least includes: user plane functions, edge cloud gateways, and global load balancing, specifically:
  • the user plane function is used to receive a domain name request sent by a terminal, and if it is determined that the domain name in the domain name request is a preset service acceleration domain name, or the destination address is a global load balancing IP address, or if the domain name is determined When the protocol port information in the request meets the preset protocol port requirements, forward the domain name request to the edge cloud gateway;
  • the edge cloud gateway is configured to obtain, based on the domain name request, from the global load balance, the corresponding protocol VIP for interconnection between edge application virtual networks;
  • domain name response to the terminal through the user plane function, where the domain name response includes at least the edge application VIP;
  • the corresponding MEC processing server is determined, and the service request is distributed to the corresponding MEC processing server.
  • Another embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory and capable of running on the processor.
  • the processor executes the mobile edge computing in the above aspects when the program is executed. Node selection method.
  • an embodiment of the present application provides a storage medium, the storage medium is used to store a computer program, and the computer program is used to execute the method for selecting a mobile edge computing node in the above aspect.
  • the embodiments of the present application provide a computer program product including instructions, which when run on a computer, cause the computer to execute the method for selecting a mobile edge computing node in the above aspect.
  • the edge cloud gateway is set in the mobile edge computing node selection system.
  • the system at least includes user plane functions, edge cloud gateways, and global load balancing.
  • the domain name request sent by the terminal, the domain name request can be a DNS request or HTTP DNS request.
  • the user plane function can analyze and process the domain name request, and forward it to the edge cloud gateway when business acceleration is needed, and then the edge cloud gateway can process it from the global Load balancing obtains the edge application VIP, and sends the edge application VIP to the terminal through the user plane function, so that the terminal sends the service request with the destination address of the edge application VIP, and offloads the terminal service request to the corresponding MEC processing server.
  • the new edge cloud gateway is added.
  • it is compatible with DNS and HTTP DNS addressing scenarios, and the application scenarios are more flexible. It realizes the selection mechanism of mobile edge computing nodes and solves the problem of MEC node selection for 5G mobile communication networks. , Which can select the nearest edge computing node to achieve the purpose of edge acceleration.
  • Figure 1 is a schematic diagram of the process flow of a CDN scheduling method in related technologies
  • FIG. 2 is a schematic diagram of the architecture of a mobile edge computing node selection system in an embodiment of the application
  • FIG. 3 is a flowchart of a method for selecting a mobile edge computing node in an embodiment of the application
  • FIG. 4 is an interactive flowchart of a method for selecting a mobile edge computing node in an embodiment of the application
  • FIG. 5 is an interactive flowchart of another method for selecting a mobile edge computing node in an embodiment of the application
  • FIG. 6 is a schematic structural diagram of a mobile edge computing node selection device in an embodiment of the application.
  • FIG. 7 is a schematic structural diagram of an electronic device in an embodiment of the application.
  • CDN Content Delivery Network
  • DNS Domain Name System
  • UPF User plane Function
  • GSLB Global Server Load Balance
  • MEC It is a technology that is based on the 5G evolution architecture and deeply integrates the mobile access network with Internet services. It can use the wireless access network to provide services and cloud computing functions required by telecommunications users' Internet Technology (IT). , And create a carrier-class service environment with high performance, low latency and high bandwidth, accelerate the rapid download of various content, services and applications in the network, and allow consumers to enjoy an uninterrupted high-quality network experience.
  • IT Internet Technology
  • Virtual IP Virtual IP
  • VIP Virtual IP
  • Edge application VIP Located in the edge computer room, it means that the virtual IP that provides local acceleration for the application.
  • the 5G mobile communication network is gradually developing, and it has higher requirements for communication service processing and transmission rate.
  • MEC can use the mobile access network to provide nearby computing, storage, and processing capabilities to reduce delays, but how to schedule mobile terminals away My own recent MEC node is a problem that needs to be solved urgently, and 5G is a more cutting-edge technology, and there are relatively few related researches. There is no relevant plan for how to select MEC nodes under 5G mobile communication networks.
  • FIG. 1 is a schematic flow diagram of the CDN scheduling method in the related technology, including:
  • Step 1 The terminal sends a DNS request to the local DNS (local DNS).
  • Step 2 The local DNS requests DNS recursive query from GSLB.
  • Step 3 GSLB returns the best access IP address to the local DNS, and the local DNS caches the IP address.
  • Step 4 The local DNS sends the best IP address to the terminal.
  • Step 5 The terminal sends a service request to the CDN node.
  • the CDN node is an edge node (Outer Center, OC).
  • Step 6 The CND node forwards to the intermediate source CDN node based on internal routing.
  • Step 7 The intermediate source CDN node forwards the service request to the service source CDN node.
  • Step 8 The service source CDN node returns the requested data to the intermediate source CDN node.
  • Step 9 The CDN node obtains data from the intermediate source CDN node and caches it.
  • Step 10 The terminal obtains data from the CDN node.
  • this scheduling method is to locate the location of the terminal through the IP address allocated by the operator, thereby scheduling it to the nearest CDN node.
  • the IP positioning technology has a large deviation and low accuracy, and may only be able to reach the province.
  • mobile edge computing nodes in this area which cannot meet the accuracy requirements of mobile edge computing nodes, that is, scheduling to the nearest MEC node cannot be achieved.
  • a method for selecting mobile edge computing nodes is proposed, which is compatible with standard DNS and Hypertext Transport Protocol (HTTP) DNS.
  • the terminal uses standard DNS and The HTTP DNS addressing process transforms the existing network process on the premise that the terminal application is not aware of it, and realizes the access to the nearby edge computing node to achieve the purpose of business acceleration.
  • a system architecture diagram for selecting a mobile edge computing node in this embodiment of the present application includes at least UPF200, edge cloud gateway 210, GSLB220, and edge controller 230.
  • the data path can connect the central cloud and the edge cloud of the operator's core network, and in order to realize the offloading of data to the edge computing node, the edge cloud gateway 210 is added.
  • the edge controller 230 where the edge cloud gateway 210 is set on the MEC node side or the edge data center (DC) side, and the edge controller 230 is set on the central cloud of the core network, and is connected to the edge cloud gateway 210 and the UPF 200 respectively.
  • GSLB220 is also deployed on the central cloud side of the core network, and is a parallel device with edge controller 230, and UPF200, edge cloud gateway 210, and GSLB220 correspond to different pre-configuration rules, which represent the routing configuration for business acceleration .
  • the edge controller 230 is mainly responsible for the scheduling of global service traffic. It controls the service traffic to be dispatched to the edge cloud gateway 210, which is then dispatched by the edge cloud gateway 210 to its local specific MEC processing server, including:
  • the edge controller 230 is configured to configure the first pre-configuration rule and the fourth pre-configuration rule of the UPF 200, and the second pre-configuration rule and the fifth pre-configuration rule of the edge cloud gateway 210, respectively.
  • the above configuration rules will be described in detail in the following embodiments.
  • the edge controller 230 may implement the pre-configuration of the UPF 200 through the operator's capability opening platform and the operator's 5G core network.
  • the user location information can be dynamically collected from the operator's 5G core network side, and edge computing nodes can be selected for each hosting service nearby.
  • each hosting service represents the business that has edge computing requirements in the 5G mobile communication network, that is, the business that needs business acceleration .
  • IaaS and PaaS are not shown in Figure 2. In practice, they can be located between the edge cloud gateway 210 and the edge controller 230.
  • the edge controller 230 can monitor the load status of the edge cloud gateway 210 through IaaS and PaaS. , Control the load scheduling of the edge cloud gateway 210.
  • GSLB220 When deploying edge services, GSLB220 also needs to be pre-configured. Specifically: GSLB220 corresponds to the third pre-configuration rule, where the third pre-configuration rule includes at least:
  • GSLB 220 when GSLB 220 receives the second HTTP DNS request sent by edge cloud gateway 210, it returns the first HTTP DNS response to edge cloud gateway 210; wherein, the second HTTP DNS request includes at least the service acceleration domain name, source address, and destination address.
  • the source address is the IP address of the edge cloud gateway 210
  • the destination address is the IP address of GSLB220.
  • the first HTTP DNS response includes at least the edge application VIP.
  • the edge application VIP is determined by GSLB220 based on the IP address of the edge cloud gateway 210 and the service acceleration domain name. .
  • UPF200 needs to be pre-configured.
  • the pre-configuration function represents routing configuration for service acceleration.
  • the UPF200 needs to provide a routing configuration function.
  • the UPF200 corresponds to the first pre-configuration rule or the fourth pre-configuration rule.
  • the first pre-configuration rule at least includes:
  • the domain name request whose domain name is the preset service acceleration domain name is forwarded to the edge cloud gateway 210.
  • the domain name request sent by the terminal may be a standard DNS request or the first HTTP DNS request, which is not limited in the embodiment of the application.
  • This rule is mainly for domain name requests whose request status is a DNS request.
  • UPF200 can resolve DNS requests and view the domain name in the DNS request. That is, UPF200 in the first pre-configured rule can have the function of parsing DNS requests, and view the domain name in the DNS request. Thus, it can be forwarded to the edge cloud gateway 210.
  • the domain name request whose destination address is the IP address of GSLB220 is forwarded to the edge cloud gateway 210.
  • a and b in the first pre-configuration rule of UPF200 are for the domain name request sent by the terminal. After UPF200 receives the domain name request sent by the terminal, it can resolve the DNS request to view the domain name for the domain name request whose request status is DNS request, or for the request The destination address can be checked for the domain name request whose status is the first HTTP DNS request.
  • the UPF 200 is used to receive the domain name request sent by the terminal, and if it is determined that the domain name in the domain name request is a preset service acceleration domain name or the destination address is the IP address of the GSLB 220, then the domain name request is forwarded to the edge cloud gateway 210.
  • the service request whose destination address is the edge application VIP is forwarded to the edge cloud gateway 210.
  • the UPF 200 is used to receive the service request sent by the terminal, and if it is determined that the destination address in the service request is the edge application VIP, then the service request is forwarded to the edge cloud gateway 210.
  • the fourth pre-configuration rule includes at least:
  • the domain name request whose protocol port information meets the preset protocol port requirements is forwarded to the edge cloud gateway 210.
  • the UPF200 in the fourth pre-configuration rule does not have the function of parsing the domain name request of the DNS request, which is mainly resolved by the edge cloud gateway 210. Therefore, in the fourth pre-configuration rule, the UPF200 receives the terminal sent After the domain name is requested, you can only view its protocol port information or destination address.
  • view protocol port information is mainly for domain name requests whose request status is DNS request, and view protocol port information of DNS request.
  • the preset protocol port requirement is User Datagram Protocol (UDP) port (port) 53, If it is determined that the protocol port information is UDP port 53, it indicates that the domain name request is a DNS request and is forwarded to the edge cloud gateway 210, so that the subsequent edge cloud gateway 210 performs the corresponding DNS request capability to obtain the domain name to determine whether acceleration is required.
  • UDP User Datagram Protocol
  • the domain name request whose destination address is the IP address of GSLB220 is forwarded to the edge cloud gateway 210.
  • the UPF 200 is used to receive the domain name request sent by the terminal, and if it is determined that the protocol port information in the domain name request meets the preset protocol port requirement, or the destination address is the IP address of the GSLB 220, the domain name request is forwarded to the edge cloud gateway 210.
  • the service request whose destination address is the edge application VIP is forwarded to the edge cloud gateway 210.
  • the first pre-configuration rule or the fourth pre-configuration rule is configured for the set edge controller 230, or configured locally, that is, the UPF 200 can not only perform unified configuration management through the edge controller 230, but also Loading through local configuration is not limited in the embodiment of the present application.
  • the edge cloud gateway 210 is mainly used for local traffic, that is, it is responsible for intelligent scheduling, load balancing, statistical analysis, etc. of traffic within a geographical range, and dispatching business traffic to a specific MEC processing server.
  • the edge cloud gateway 210 when deploying edge services, the edge cloud gateway 210 also needs to be pre-configured. Specifically, the edge cloud gateway 210 corresponds to the second pre-configuration rule or the fifth pre-configuration rule.
  • the second pre-configuration rule at least includes: a preset shunt strategy.
  • the preset offload strategy is to perform offload based on IP quintuple information.
  • the IP quintuple includes source IP address, destination IP address, protocol number, source port, and destination port, and the offload can be performed based on the load balancing algorithm.
  • the load balancing algorithm is the source address hash method, the source IP address is hashed, and a hash value is obtained through the hash operation. Based on the hash value and the configuration rules of the MEC processing server list, the corresponding MEC processing server is determined , And then forward it to the corresponding MEC processing server for processing.
  • the preset offloading strategy is to perform offloading based on Uniform Resource Locator (URL) information.
  • URL Uniform Resource Locator
  • it can be based on the type of service requested by the domain name in the service request, and the specific domain name or resource type stored on each MEC processing server For example, a specific domain name or resource type characterizes the service type of processing pictures or videos, and then forwards the service request to the MEC processing server that processes the corresponding service type.
  • URL Uniform Resource Locator
  • the specific distribution strategy is not limited in the embodiments of this application, and can be selected and used according to actual needs and circumstances.
  • the fifth pre-configured rule includes at least: a preset shunt strategy; and the ability to resolve DNS requests.
  • the edge cloud gateway 210 has the ability to resolve standard DNS requests, can parse DNS packets, and obtain the carry The domain name can then be repackaged into a corresponding second HTTP DNS request.
  • the second pre-configuration rule or the fifth pre-configuration request is configured for the set edge controller 230 or configured locally, that is, the edge cloud gateway 210 can not only perform unified configuration management through the edge controller 230 , It can also be loaded through local configuration, which is not limited in the embodiment of this application.
  • the pre-configured rules of the edge cloud gateway 210 correspond to the pre-configured rules of the UPF 200.
  • the edge cloud gateway 210 executes the corresponding behavior based on the second pre-configured rule, and can directly encapsulate the second HTTP DNS request based on the domain name and other information and send it to the GSLB 220; if the UPF200 is based on The fourth pre-configured rule executes the corresponding behavior, that is, no analysis is performed, only the protocol port information or the destination address is viewed, and then forwarded to the edge cloud gateway 210, the edge cloud gateway 210 executes the corresponding behavior based on the fifth pre-configured rule.
  • the DNS request is parsed first, and then encapsulated as a second HTTP DNS request and sent to the terminal
  • the edge cloud gateway 210 is used to:
  • edge cloud gateway 210 is also used to record the request status of the domain name request; where the request status represents the DNS request or the first HTTP DNS request.
  • the terminal it is possible to support the terminal to initiate a domain name request for the original domain name through standard DNS or the first HTTP DNS request, and the destination address is the IP address of GSLB220.
  • the edge cloud gateway 210 is specifically used to:
  • S1.1 Based on the domain name request, send a second HTTP DNS request to GSLB220, where the second HTTP DNS request includes at least the service acceleration domain name, source address, and destination address.
  • the source address is the IP address and destination address of the edge cloud gateway 210 It is the IP address of GSLB220.
  • step S1.1 there can be two situations when performing step S1.1:
  • the first case If the domain name in the domain name request is the preset service acceleration domain name, or the destination address is the IP address of GSLB220.
  • the pre-configured rule of UPF200 is the first pre-configured rule.
  • UPF200 can resolve the domain name request whose request status is a DNS request, and obtain the domain name in the DNS request, regardless of whether the domain name request sent by the terminal is a DNS request or the first HTTP DNS request.
  • the gateway 210 After the gateway 210 receives the domain name request sent by the UPF 200, it is specifically configured to re-transmit its own IP address as the source address to the GSLB 220 in the second HTTP DNS encapsulation based on the domain name request.
  • the first case is for the first pre-configured rule corresponding to UPF200
  • UPF200 has the ability to resolve DNS requests
  • the edge cloud gateway 210 corresponds to the second pre-configured rule, that is, after the edge cloud gateway 210 receives the domain name request, it is a DNS request.
  • the domain name is requested for resolution.
  • the second case If the protocol port information in the domain name request meets the preset protocol port requirements, or the destination address is the IP address of GSLB220.
  • the edge cloud gateway 210 is specifically used to: if the request status of the domain name request is a DNS request, resolve the domain name request, obtain the domain name in the domain name request, and repackage the resolved domain name request into a second HTTP DNS request, and repackage it
  • the second HTTP DNS request is sent to GSLB220.
  • the second case is for the fourth pre-configured rule corresponding to UPF200.
  • UPF200 does not have the ability to resolve DNS requests.
  • the edge cloud gateway 210 corresponds to the fifth pre-configured rule, and the edge cloud gateway 210 It has the ability to resolve DNS requests, resolves the domain name request whose request status is a DNS request, and repackages it as a second HTTP DNS request and sends it to GSLB220.
  • the edge cloud gateway 210 does not need to be resolved, it also needs to be repackaged. For example, the source address is modified to its own IP address and then sent to the GSLB 220.
  • S1.2 Receive the first HTTP DNS response returned by the GSLB 220, where the first HTTP DNS response includes at least the edge application VIP, and the edge application VIP is determined by the GSLB 220 according to the IP address of the edge cloud gateway 210 and the service acceleration domain name.
  • the edge cloud gateway 210 is specifically used for:
  • the request status of the domain name request is the first HTTP DNS request
  • the second HTTP DNS response is returned.
  • the edge cloud gateway 210 after the edge cloud gateway 210 receives the first HTTP DNS response returned by the GSLB220, it needs to return the corresponding response packet to the terminal through UPF200 according to the request status of the terminal sending the domain name request, that is, if the terminal sends the request status If it is a DNS request, it needs to be encapsulated as a standard DNS response packet and returned to UPF200. If the request status sent by the terminal is the first HTTP DNS request, it needs to be encapsulated as a second HTTP DNS response packet and returned to UPF200, and UPF200 will then return the received The response packet is sent to the terminal.
  • edge cloud gateways and edge controllers are added, and the terminal can initiate a domain name request for the original domain name through a standard DNS request or the first HTTP DNS request. Domain name requests that require service acceleration can be forwarded to the edge cloud gateway. If the domain name request sent by the terminal is a DNS request, you can configure UPF to resolve the DNS request, or configure the edge cloud gateway to have the ability to resolve DNS requests, and then the edge cloud gateway can For processing, the edge application VIP is obtained from GSLB, and the edge application VIP is sent to the terminal through UPF, so that the terminal sends service requests based on the edge application VIP, and the service requests of the terminal are offloaded to the specific MEC processing server.
  • the edge cloud gateway is closer to Terminal, and through the edge cloud gateway, the original DNS request can be converted into HTTP DNS request, which can bypass the local DNS and simplify the access process. Therefore, the processing speed is faster, the delay is reduced, and it can be applied to DNS or HTTP DNS addressing.
  • it realizes the correct selection of the nearest edge computing node to achieve the purpose of edge acceleration, and it can provide users with various application services (Over The Top, OTT) services through the Internet under the existing technology framework, without the need to transform and smoothly access the edge Computing nodes, users are not aware, improve the ease of implementation and user experience.
  • OTT Application Services
  • FIG. 3 a flowchart of a method for selecting a mobile edge computing node in an embodiment of this application is mainly applied in an edge cloud gateway.
  • the method includes:
  • Step 300 The edge cloud gateway receives the domain name request forwarded by the user plane function.
  • the domain name request is forwarded when the user plane function resolves to the domain name request sent by the terminal when the domain name is a preset service acceleration domain name, or the destination address is an IP address for global load balancing; or, the domain name request is sent by the user plane function determined by the terminal
  • the protocol port information in the domain name request is forwarded when it meets the preset protocol port requirements, or the destination address is the IP address of global load balancing.
  • it may also include: recording the request status of the domain name request; where the request status represents the DNS request or the first HTTP DNS request.
  • UPF corresponds to the first pre-configured rule
  • the edge cloud gateway corresponds to the second pre-configured rule
  • GSLB corresponds to the third pre-configured rule, which enables UPF to have the ability to resolve DNS requests
  • UPF receives the domain name request sent by the terminal. If the request status of the domain name request is a DNS request, the domain name request sent by the terminal is parsed, and when the domain name is determined to be the preset service acceleration domain name, it is forwarded to the edge cloud gateway. If the request status of the domain name request is The first HTTP DNS request is forwarded to the edge cloud gateway when it is determined that the destination address of the domain name request is the IP address of the GSLB.
  • UPF corresponds to the fourth pre-configured rule
  • the edge cloud gateway corresponds to the fifth pre-configured rule
  • GSLB corresponds to the third pre-configured rule, that is, the edge cloud gateway has the ability to resolve DNS requests
  • UPF receives the domain name request sent by the terminal. If the request status of the domain name request is a DNS request, it determines that the protocol port information in the domain name request meets the preset protocol port requirements and forwards it to the edge cloud gateway. If the request status of the domain name request is the first HTTP DNS request is forwarded to the edge cloud gateway when it is determined that the destination address of the domain name request is the IP address of the GSLB.
  • Step 310 Based on the domain name request, obtain the corresponding edge application VIP from the global load balance.
  • step 310 When step 310 is specifically executed, it includes:
  • the second HTTP DNS request includes at least the service acceleration domain name, source address, and destination address.
  • the source address is the IP address of the edge cloud gateway, and the destination address is the global load. Balanced IP address.
  • step 300 when the S1 is executed, the following two implementation manners may also be correspondingly:
  • UPF corresponds to the first pre-configured rule
  • the edge cloud gateway corresponds to the second pre-configured rule
  • GSLB corresponds to the third pre-configured rule, that is, UPF has the ability to resolve DNS requests:
  • the edge cloud gateway only needs to directly repackage the resolved domain name request into a second HTTP DNS request and send it to GSLB Send the second HTTP DNS request. If the request status of the domain name request is the first HTTP DNS request, the edge cloud gateway can modify the source address in the domain name request and modify it to the IP address of the edge cloud gateway to obtain the second HTTP DNS request and forward it to GSLB .
  • UPF corresponds to the fourth pre-configured rule
  • the edge cloud gateway corresponds to the fifth pre-configured rule
  • GSLB corresponds to the third pre-configured rule, that is, the edge cloud gateway has the ability to resolve DNS requests
  • the edge cloud gateway resolves the domain name request, obtains the domain name in the domain name request, repackages the resolved domain name request into a second HTTP DNS request, and sends the repackaged second HTTP DNS request
  • the edge cloud gateway can modify the source address in the domain name request to obtain the second HTTP DNS request and forward it to GSLB.
  • Step 320 Return a domain name response to the terminal through the user plane function, where the domain name response includes at least the edge application VIP.
  • step 320 When performing step 320, it can be divided into the following two situations:
  • the first case If the request status of the domain name request is a DNS request, a DNS response is returned.
  • the second case If the request status of the domain name request is the first HTTP DNS request, the second HTTP DNS response is returned.
  • Step 330 Receive the service request forwarded by the user plane function, where the destination address of the service request is the edge application VIP.
  • UPF has pre-configured this rule in its first pre-configuration rule or fourth pre-configuration rule, that is, the service request for the edge application VIP with the destination address is forwarded to the edge cloud gateway.
  • Step 340 Determine the corresponding MEC processing server according to the service request and the preset offloading strategy, and offload the service request to the corresponding MEC processing server.
  • an edge cloud gateway is added to be compatible with DNS and HTTP DNS addressing scenarios.
  • the domain name request of the terminal is forwarded to the edge cloud gateway, and processed through the edge cloud gateway, and finally the service request of the terminal is split to
  • the selection mechanism of mobile edge computing nodes is realized, which achieves the purpose of business acceleration and solves the problem of the MEC node selection scheme for 5G mobile communication networks.
  • the first implementation manner if the UPF corresponds to the first pre-configured rule, the edge cloud gateway corresponds to the second pre-configured rule, that is, in the scenario where the UPF resolves the DNS request.
  • FIG. 4 is an interaction flowchart of a method for selecting a mobile edge computing node in an embodiment of this application.
  • Step 400 The terminal sends a domain name request to the UPF.
  • the terminal can initiate a request for the original domain name through standard DNS or HTTP DNS, that is, the terminal can be based on a traditional DNS or HTTP DNS addressing mechanism.
  • the request status of the domain name request is a DNS request or the first HTTP DNS request.
  • Step 401 UPF receives the domain name request sent by the terminal.
  • Step 402 If the UPF determines that the domain name in the domain name request is the preset service acceleration domain name, or the destination address is the IP address of the GSLB, it forwards the domain name request to the edge cloud gateway.
  • the UPF can be configured with a first pre-configuration rule, so that the UPF has the ability to resolve DNS requests.
  • the UPF can resolve the DNS request based on the corresponding first pre-configuration rule, for a domain name request whose request status is a DNS request , Determine whether it is a domain name that needs business acceleration. For a domain name request whose request status is the first HTTP DNS request, you can view the destination address. When the destination address is the GSLB IP address, it is determined that business acceleration is required and forwarded to the edge cloud gateway.
  • Step 403 The edge cloud gateway receives the domain name request forwarded by UPF.
  • Step 404 The edge cloud gateway sends a second HTTP DNS request to the GSLB.
  • the second HTTP DNS request includes at least the service acceleration domain name, source address, and destination address
  • the source address is the IP address of the edge cloud gateway
  • the destination address is the IP address of the GSLB.
  • the edge cloud gateway records the request status of the domain name request.
  • the edge cloud gateway uses its own IP address as the source address to initiate a second HTTP DNS request to GSLB.
  • the edge cloud gateway can convert the original DNS request into a second HTTP DNS request.
  • the edge cloud gateway changes the source address to its own IP address and sends it to GSLB The second HTTP DNS request, so that GSLB can determine that the source address is the IP address of the edge cloud gateway according to the source address, and can return the service acceleration edge application VIP accordingly.
  • Step 405 GSLB receives the second HTTP DNS request sent by the edge cloud gateway.
  • Step 406 GSLB returns the first HTTP DNS response to the edge cloud gateway.
  • the first HTTP DNS response includes at least the edge application VIP, which is determined by the GSLB based on the IP address of the edge cloud gateway and the service acceleration domain name.
  • this step GSLB can be implemented based on its corresponding third pre-configured rule. GSLB determines that the source address in the second HTTP DNS request is the IP address of the edge cloud gateway, and the requested domain name is the service acceleration domain name. According to the service configuration corresponding to the IP address of the edge cloud gateway and the service acceleration domain name, choose to return the actual edge application VIP.
  • Step 407 The edge cloud gateway receives the first HTTP DNS response returned by the GSLB.
  • Step 408 The edge cloud gateway returns a domain name response to the terminal through UPF based on the first HTTP DNS response.
  • the domain name response includes at least the edge application VIP.
  • Step 409 The terminal receives the domain name response returned by the edge cloud gateway through UPF.
  • Step 410 The terminal sends a service request to the UPF based on the domain name response.
  • the terminal can initiate a service request based on the edge application VIP in the domain name response and use this as the destination address, where the destination address in the service request is the edge application VIP.
  • Step 411 UPF receives the service request sent by the terminal.
  • Step 412 When the UPF determines that the destination address of the service request is the edge application VIP, it forwards the service request to the edge cloud gateway.
  • the UPF is implemented based on the corresponding first pre-configuration rule or the fourth pre-configuration rule, and the destination address is the service request of the edge application VIP and forwarded to the edge cloud gateway.
  • Step 413 The edge cloud gateway receives the service request forwarded by the UPF, determines the corresponding MEC processing server according to the service request and the preset distribution strategy, and distributes the service request to the corresponding MEC processing server.
  • a service data flow for the selection of mobile edge computing nodes is proposed.
  • the configuration enables UPF to have the ability to resolve DNS requests. It can be applied in devices such as edge cloud gateways.
  • services can be offloaded to the nearest MEC processing server with higher accuracy, enabling the selection of edge computing nodes, reducing latency, and achieving business acceleration.
  • the second implementation manner if the UPF corresponds to the fourth pre-configuration rule, the edge cloud gateway corresponds to the fifth pre-configuration rule, that is, the edge cloud gateway resolves the DNS request scenario.
  • FIG. 5 is an interaction flowchart of a method for selecting a mobile edge computing node in an embodiment of this application.
  • Step 500 The terminal sends a domain name request to the UPF.
  • the request status of the domain name request is a DNS request or the first HTTP DNS request.
  • Step 501 UPF receives the domain name request sent by the terminal.
  • Step 502 If the UPF determines that the protocol port information in the domain name request meets the preset protocol port requirements, or the destination address is the IP address of the GSLB, it forwards the domain name request to the edge cloud gateway.
  • This step is implemented by UPF based on its corresponding fourth pre-configuration rule.
  • the UPF can be configured with a fourth pre-configuration rule so that UPF does not resolve DNS requests.
  • UPF can, based on the fourth pre-configuration rule, view the protocol port information for a domain name request whose request status is a DNS request. Meet the preset requirements, for example, the protocol port information is UDP port 53, then it is determined as a DNS request and forwarded to the edge cloud gateway, so that the edge cloud gateway resolves the DNS request based on its corresponding fifth pre-configured rule, and the request status is the first For the domain name request of the HTTP DNS request, you can view the destination address. When the destination address is the IP address of the GSLB, it is determined that business acceleration is required, and then forwarded to the edge cloud gateway.
  • Step 503 The edge cloud gateway receives the domain name request forwarded by UPF.
  • Step 504 If the request status of the domain name request is a DNS request, send a second HTTP DNS request to the GSLB.
  • the edge cloud gateway resolves the domain name request, obtains the domain name, and repackages the resolved domain name request into a second HTTP DNS request.
  • the second HTTP DNS request includes at least the service acceleration domain name, source address, and destination address
  • the source address is the IP address of the edge cloud gateway
  • the destination address is the IP address of the GSLB.
  • the edge cloud gateway records the request status of the domain name request.
  • the edge cloud gateway corresponds to the fifth pre-configuration rule configured.
  • the edge cloud gateway is configured to have the ability to resolve DNS requests. If the request status of the domain name request is a DNS request, the domain name request is resolved to obtain the domain name The domain name is included in the request, and the resolved domain name request is repackaged as a second HTTP DNS request, and the repackaged second HTTP DNS request is sent to the GSLB.
  • the request status of the domain name request is the first HTTP DNS request, you can directly use your own IP address as the source address and forward it to the GSLB in the second HTTP DNS encapsulation.
  • Step 505 GSLB receives the second HTTP DNS request sent by the edge cloud gateway.
  • Step 506 GSLB returns the first HTTP DNS response to the edge cloud gateway.
  • the first HTTP DNS response includes at least the edge application VIP, which is determined by the GSLB according to the IP address of the edge cloud gateway and the service acceleration domain name.
  • GSLB can be implemented based on its corresponding third pre-configuration rule.
  • Step 507 The edge cloud gateway receives the first HTTP DNS response returned by the GSLB.
  • the edge cloud gateway can be considered to be a proxy for traditional local DNS (local DNS, LDNS), and has the LDNS function.
  • Step 508 The edge cloud gateway returns a domain name response to the terminal through UPF based on the first HTTP DNS response.
  • the domain name response includes at least the edge application VIP.
  • Step 509 The terminal receives the domain name response returned by the edge cloud gateway through the UPF.
  • Step 510 The terminal sends a service request to the UPF based on the domain name response.
  • the terminal can initiate a service request based on the edge application VIP in the domain name response and use this as the destination address, where the destination address in the service request is the edge application VIP.
  • Step 511 UPF receives the service request sent by the terminal.
  • Step 512 When the UPF determines that the destination address of the service request is the edge application VIP, it forwards the service request to the edge cloud gateway.
  • the UPF is implemented based on the corresponding first pre-configuration rule or the fourth pre-configuration rule, and the destination address is the service request of the edge application VIP and forwarded to the edge cloud gateway.
  • Step 513 The edge cloud gateway receives the service request forwarded by the UPF, determines the corresponding MEC processing server according to the service request and the preset offloading strategy, and offloads the service request to the corresponding MEC processing server.
  • the edge cloud gateway mainly for 5G mobile communication networks.
  • the configuration enables the edge cloud gateway to have the ability to resolve DNS requests.
  • devices such as the edge cloud gateway, It can be used in the DNS addressing or HTTP DNS addressing scenarios of the terminal, and the nearest edge computing node can be correctly selected, and the business can be offloaded to the nearest MEC processing server, with higher location accuracy, thereby achieving edge acceleration.
  • FIG. 6 shows the edge cloud gateway selected by the mobile edge computing node in the embodiment of this application.
  • the edge cloud gateway is set in the mobile edge computing node selection system.
  • the system includes at least UPF, edge cloud gateway, and GSLB Specifically:
  • the first receiving module 60 is configured to receive a domain name request forwarded by UPF, where the domain name in the domain name request is a preset service acceleration domain name, or the destination address is an IP address of GSLB; or, the protocol port information in the domain name request conforms to Preset protocol port requirements;
  • the obtaining module 61 is configured to obtain the corresponding edge application VIP from the GSLB based on the domain name request;
  • the sending module 62 is configured to return a domain name response to the terminal through the UPF, where the domain name response includes at least the edge application VIP;
  • the second receiving module 63 is configured to receive the service request forwarded by the UPF, where the destination address of the service request is the edge application VIP;
  • the determining module 64 is configured to determine the corresponding MEC processing server according to the service request and the preset offload strategy
  • the offloading module 65 is configured to offload the service request to the corresponding MEC processing server.
  • a recording module 66 configured to record the request status of the domain name request; where the request status represents a DNS request or a first HTTP DNS request.
  • the obtaining module 61 is specifically used for:
  • a second HTTP DNS request is sent to the GSLB, where the second HTTP DNS request includes at least a service acceleration domain name, a source address, and a destination address, and the source address is the edge cloud gateway's IP address, the destination address is the IP address of the GSLB;
  • the first HTTP DNS response includes at least an edge application VIP
  • the edge application VIP is the GSLB according to the IP address and service acceleration domain name of the edge cloud gateway definite.
  • the obtaining module 61 is specifically configured to:
  • the request status of the domain name request is a DNS request
  • resolve the domain name request obtain the domain name in the domain name request, and repackage the resolved domain name request into a second HTTP DNS request; repackage the second HTTP
  • the DNS request is sent to the GSLB.
  • the sending module 62 is specifically configured to:
  • the request status of the domain name request is the first HTTP DNS request
  • the second HTTP DNS response is returned.
  • the UPF, the edge cloud gateway, and the GSLB respectively correspond to different pre-configured rules, and the pre-configured rules represent routing configurations for service acceleration.
  • the UPF corresponds to a first pre-configured rule
  • the first pre-configured rule at least includes: forwarding the domain name request with the domain name of the preset service acceleration domain name to the edge cloud gateway; or, the destination address of the IP address of the GSLB The domain name request is forwarded to the edge cloud gateway; or, the service request whose destination address is the edge application VIP is forwarded to the edge cloud gateway;
  • the edge cloud gateway corresponds to a second pre-configured rule, and the second pre-configured rule includes at least: a preset offload strategy;
  • the GSLB corresponds to a third pre-configured rule, and the third pre-configured rule at least includes: an HTTP DNS request for the IP address of the edge cloud gateway whose source address is based on the IP address and service acceleration domain name of the edge cloud gateway in the HTTP DNS request Return the corresponding edge application VIP.
  • the UPF corresponds to a fourth pre-configured rule
  • the fourth pre-configured rule at least includes: forwarding a domain name request whose protocol port information meets the requirements of a preset protocol port to the edge cloud gateway; or, the destination address is an IP of GSLB The domain name request of the address is forwarded to the edge cloud gateway; or the service request with the destination address of the edge application VIP is forwarded to the edge cloud gateway;
  • the edge cloud gateway corresponds to a fifth pre-configured rule, and the fifth pre-configured rule at least includes: a preset offload strategy; and has the ability to resolve DNS requests.
  • the first pre-configuration rule, the second pre-configuration rule, the fourth pre-configuration rule, or the fifth pre-configuration rule is configured by a set edge controller or configured locally;
  • the edge controller is arranged in the cloud center of the core network in the system, and is respectively connected in communication with the edge cloud gateway and the UPF.
  • FIG. 7 a schematic structural diagram of an electronic device in an embodiment of the present application.
  • the embodiment of the present application provides an electronic device.
  • the electronic device may include a processor 710 (Center Processing Unit, CPU), a memory 720, an input device 730, an output device 740, etc.
  • the input device 730 may include a keyboard, a mouse, a touch screen, etc.
  • the output device 740 may include a display device, such as a liquid crystal display (LCD), a cathode ray tube (Cathode Ray Tube, CRT), etc.
  • LCD liquid crystal display
  • CRT cathode Ray Tube
  • the memory 720 may include a read only memory (ROM) and a random access memory (RAM), and provides the processor 710 with program instructions and data stored in the memory 720.
  • the memory 720 may be used to store a program of any mobile edge computing node selection method in the embodiment of the present application.
  • the processor 710 calls the program instructions stored in the memory 720, and the processor 710 is configured to execute any method for selecting a mobile edge computing node in the embodiments of the present application according to the obtained program instructions.
  • a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the mobile edge computing node in any of the above-mentioned method embodiments is implemented. Method of choosing.
  • the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.
  • a computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • a computer program product is also provided.
  • the computer program product When executed, it is used to implement the method for selecting a mobile edge computing node provided in the foregoing embodiment.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Library & Information Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请涉及移动通信领域，尤其涉及一种移动边缘计算节点的选择方法、装置及系统，边缘云网关接收用户面功能转发的域名请求，域名请求中域名为业务加速域名或目的地址为全局负载均衡的IP地址，或者，域名请求中协议端口信息符合协议端口要求；从全局负载均衡获取对应的边缘应用VIP，通过用户面功能发送给终端，接收用户面功能转发的终端发送的业务请求，将业务请求分流到对应的MEC处理服务器。新增边缘云网关，兼容DNS和HTTP DNS寻址场景，实现就近选择边缘计算节点，达到边缘加速目的。

Description

一种移动边缘计算节点的选择方法、装置及系统
本申请要求于2019年05月10日提交中国专利局、申请号为201910387587.9、申请名称为“一种移动边缘计算节点的选择方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及移动通信领域，尤其涉及移动边缘计算节点的选择。
背景技术
目前，随着科技发展，用户对于通信业务处理和传输速率需求越来越高，尤其针对第五代移动通信技术(5-Generation，5G)移动通信网络，处理速度要求会更高，移动边缘计算可利用移动接入网络就近提供计算、存储、处理等能力，减少时延，为此需要将移动终端调度到离该移动终端最近的移动边缘计算(Mobile Edge Computing，MEC)节点。
发明内容
本申请实施例提供一种移动边缘计算节点的选择方法、装置及系统，以解决现有技术中还未有针对5G移动通信网络的MEC节点选择方案的问题。
本申请实施例提供的具体技术方案如下：
一方面，本申请实施例提供了一种移动边缘计算节点的选择方法，所述方法由边缘云网关执行，所述边缘云网关设置在移动边缘计算节点的选择系统中，所述系统至少包括用户面功能、所述边缘云网关和全局负载均衡，具体地：
边缘云网关接收用户面功能转发的域名请求，其中，所述域名请求中域名为预设业务加速域名，或目的地址为全局负载均衡的IP地址；或者，所述域名请求中协议端口信息符合预设协议端口要求；
基于所述域名请求，从所述全局负载均衡获取对应的边缘应用虚拟网络之间互连的协议VIP；
通过所述用户面功能向所述终端返回域名响应，其中，所述域名响应中至少包括所述边缘应用VIP；
接收所述用户面功能转发的业务请求，其中，所述业务请求的目的地址为所述边缘应用VIP；
根据所述业务请求和预设分流策略，确定对应的MEC处理服务器，并将 所述业务请求分流到所述对应的MEC处理服务器。
另一方面，本申请实施例提供了一种移动边缘计算节点选择的边缘云网关，所述边缘云网关设置在移动边缘计算节点的选择系统中，所述系统至少包括用户面功能、所述边缘云网关和全局负载均衡，具体包括：
第一接收模块，用于接收用户面功能转发的域名请求，其中，所述域名请求中域名为预设业务加速域名，或目的地址为全局负载均衡的IP地址；或者，所述域名请求中协议端口信息符合预设协议端口要求；
获取模块，用于基于所述域名请求，从所述全局负载均衡获取对应的边缘应用虚拟网络之间互连的协议VIP；
发送模块，用于通过所述用户面功能向所述终端返回域名响应，其中，所述域名响应中至少包括所述边缘应用VIP；
第二接收模块，用于接收所述用户面功能转发的业务请求，其中，所述业务请求的目的地址为所述边缘应用VIP；
确定模块，用于根据所述业务请求和预设分流策略，确定对应的MEC处理服务器；
分流模块，用于将所述业务请求分流到所述对应的MEC处理服务器。
在一种可选的实现方式中，进一步包括，记录模块，用于：记录所述域名请求的请求状态；其中，所述请求状态表征DNS请求或第一HTTP DNS请求。
在一种可选的实现方式中，获取模块具体用于：
基于所述域名请求，向所述全局负载均衡发送第二HTTP DNS请求，其中，所述第二HTTP DNS请求中至少包括业务加速域名、源地址、目的地址，所述源地址为所述边缘云网关的IP地址，目的地址为所述全局负载均衡的IP地址；
接收所述全局负载均衡返回的第一HTTP DNS响应，其中，所述第一HTTP DNS响应中至少包括边缘应用VIP，所述边缘应用VIP为所述全局负载均衡根据所述边缘云网关的IP地址和业务加速域名确定的。
在一种可选的实现方式中，若所述域名请求中协议端口信息符合预设协议端口要求，或目的地址为全局负载均衡的IP地址，则获取模块具体用于：
若所述域名请求的请求状态为DNS请求，则解析所述域名请求，获取所述域名请求中域名，并将解析后的域名请求重新封装为第二HTTP DNS请求；
将重新封装的第二HTTP DNS请求发送给所述全局负载均衡。
在一种可选的实现方式中，发送模块具体用于：
若所述域名请求的请求状态为DNS请求，则返回DNS响应；
若所述域名请求的请求状态为第一HTTP DNS请求，则返回第二HTTP DNS响应。
在一种可选的实现方式中，所述用户面功能、所述边缘云网关和所述全局负载均衡分别对应不同的预配置规则，所述预配置规则表征业务加速的路由配置。
在一种可选的实现方式中，所述用户面功能对应第一预配置规则，所述第一预配置规则至少包括：域名为预设业务加速域名的域名请求转发至边缘云网关；或，目的地址为全局负载均衡的IP地址的域名请求转发至边缘云网关；或，目的地址为边缘应用VIP的业务请求转发至边缘云网关；
所述边缘云网关对应第二预配置规则，所述第二预配置规则至少包括：预设分流策略；
所述全局负载均衡对应第三预配置规则，所述第三预配置规则至少包括：针对源地址为边缘云网关的IP地址的HTTP DNS请求，基于HTTP DNS请求中边缘云网关的IP地址和业务加速域名返回相应的边缘应用VIP。
在一种可选的实现方式中，所述用户面功能对应第四预配置规则，所述第四预配置规则至少包括：协议端口信息符合预设协议端口要求的域名请求转发至边缘云网关；或，目的地址为全局负载均衡的IP地址的域名请求转发至边缘云网关；或，目的地址为边缘应用VIP的业务请求转发至边缘云网关；
所述边缘云网关对应第五预配置规则，所述第五预配置规则至少包括：预设分流策略；并具备解析DNS请求的能力。
在一种可选的实现方式中，所述第一预配置规则、所述第二预配置规则、所述第四预配置规则或所述第五预配置规则为设置的边缘控制器配置的，或本地配置的；
其中，所述边缘控制器设置在所述系统中核心网的云中心，并分别与边缘云网关、用户面功能通信连接。
另一方面，本申请实施例提供了一种移动边缘计算节点的选择系统，至少 包括：用户面功能、边缘云网关和全局负载均衡，具体地：
所述用户面功能，用于接收终端发送的域名请求，并若确定所述域名请求中域名为预设业务加速域名，或目的地址为全局负载均衡的IP地址时，或者，若确定所述域名请求中协议端口信息符合预设协议端口要求时，则将所述域名请求转发至所述边缘云网关；
所述边缘云网关，用于基于所述域名请求，从所述全局负载均衡获取对应的边缘应用虚拟网络之间互连的协议VIP；
通过所述用户面功能向所述终端返回域名响应，其中，所述域名响应中至少包括所述边缘应用VIP；
接收所述用户面功能转发的业务请求，其中，所述业务请求是所述用户面功能解析到所述终端发送的业务请求中目的地址为所述边缘应用VIP时转发的；
根据所述业务请求和预设分流策略，确定对应的MEC处理服务器，并将所述业务请求分流到所述对应的MEC处理服务器。
本申请另一个实施例提供了一种电子设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时执行以上方面的移动边缘计算节点的选择方法。
另一方面，本申请实施例提供一种存储介质，所述存储介质用于存储计算机程序，所述计算机程序用于执行以上方面的移动边缘计算节点的选择方法。
另一方面，本申请实施例提供了一种包括指令的计算机程序产品，当其在计算机上运行时，使得所述计算机执行以上方面的移动边缘计算节点的选择方法。
本申请实施例提供的技术方案至少包括如下有益效果：
通过提供了一种移动边缘计算节点的选择方法，由边缘云网关执行，边缘云网关设置在移动边缘计算节点的选择系统中，该系统至少包括用户面功能、边缘云网关、全局负载均衡，针对终端发送的域名请求，该域名请求可以为DNS请求或HTTP DNS请求，用户面功能可以对该域名请求进行分析处理，需要业务加速时转发至边缘云网关，进而边缘云网关进行处理，可以从全局负载均衡获取边缘应用VIP，并将边缘应用VIP通过用户面功能发送给终端，以使 终端发送目的地址为边缘应用VIP的业务请求，将该终端的业务请求分流到对应的MEC处理服务器，这样，新增边缘云网关，通过改造现有网络流程，兼容DNS和HTTP DNS寻址场景，应用场景更加灵活，实现移动边缘计算节点的选择机制，解决了针对5G移动通信网络的MEC节点选择方案的问题，从而可以就近选择边缘计算节点，达到边缘加速目的。
附图说明
图1为相关技术中CDN调度的方法流程示意图；
图2为本申请实施例中移动边缘计算节点的选择系统的架构示意图；
图3为本申请实施例中移动边缘计算节点的选择方法流程图；
图4为本申请实施例中一种移动边缘计算节点的选择方法交互流程图；
图5为本申请实施例中另一种移动边缘计算节点的选择方法交互流程图；
图6为本申请实施例中移动边缘计算节点的选择装置结构示意图；
图7为本申请实施例中电子设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，并不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
内容分发网络(Content Delivery Network，CDN)：其基本思路是尽可能避开互联网上有可能影响数据传输速度和稳定性的瓶颈和环节，使内容传输的更快、更稳定，CDN有就近接入，从而加速的目的。
域名系统(Domain Name System，DNS)：作为可以将域名和网络之间互连的协议(Internet Protocol，IP)地址相互映射的一个分布式数据库，能够使用户更方便的访问互联网，而不用去记住能够被机器直接读取的IP地址数据串。
用户面功能(User plane Function，UPF)：负责用户面处理。
全局负载均衡(Global Server Load Balance，GSLB)：实现在广域网包括互联网上不同地域的服务器间的流量调配，将用户的请求定向到最近的节点(或者区域)从而确保访问质量。
MEC：是基于5G演进的架构，并将移动接入网与互联网业务深度融合的 一种技术，可利用无线接入网络就近提供电信用户互联网技术(Internet Technology，IT)所需服务和云端计算功能，而创造出一个具备高性能、低延迟与高带宽的电信级服务环境，加速网络中各项内容、服务及应用的快速下载，让消费者享有不间断的高质量网络体验。
虚拟IP(Virtual IP，VIP)：是一个不与特定计算机或一个计算机中的网络接口卡相连的IP地址，数据包被发送到这个VIP地址，但是所有的数据还是经过真实的网络接口。
边缘应用VIP：处于边缘机房，表示为应用提供本地加速的虚拟IP。
目前，5G移动通信网络逐步发展，其对于通信业务处理和传输速率要求更高，MEC可以利用移动接入网就近提供计算、存储、处理等能力，减少时延，但如何把移动终端调度到离自己最近的MEC节点是急需解决的问题，而5G属于较为前沿的技术，相关研究相对比较少，还未有针对5G移动通信网络下如何选择MEC节点的相关方案。
另外，相关技术中传统的DNS寻址机制，确定相应的IP地址进行数据传输，较为相似，参阅图1所示，为相关技术中CDN调度的方法流程示意图，包括：
步骤1：终端向本地DNS(local DNS)发送DNS请求。
步骤2：本地DNS向GSLB请求DNS递归查询。
步骤3：GSLB向本地DNS返回最佳接入IP地址，同时本地DNS缓存该IP地址。
步骤4：本地DNS将最佳IP地址发送给终端。
步骤5：终端向CDN节点发送业务请求。
其中，该CDN节点为边缘节点(Outer Center，OC)。
步骤6：CND节点基于内部路由转发至中间源CDN节点。
步骤7：中间源CDN节点转发业务请求至业务源CDN节点。
步骤8：业务源CDN节点向中间源CDN节点返回请求的数据。
步骤9：CDN节点从中间源CDN节点获取数据并缓存。
步骤10：终端从CDN节点获取数据。
相关技术中，这种调度方式是通过运营商分配的IP地址定位终端所在的位置，从而将其调度到最近的CDN节点，但是IP定位技术存在较大偏差，精度较 低，可能只能到省级，而该区域移动边缘计算节点有很多，无法满足移动边缘计算节点的精度要求，即无法实现调度到最近的MEC节点。
因此，本申请实施例中，主要针对5G移动通信网络，提出了一种移动边缘计算节点的选择方法，兼容标准DNS和超文本传输协议(Hyper Text Transport Protocol，HTTP)DNS，终端应用标准DNS和HTTP DNS寻址过程，在终端应用无感知的前提下，改造现有网络流程，实现就近接入边缘计算节点，达到业务加速的目的。
参阅图2所示，为本申请实施例中移动边缘计算节点的选择系统架构图，至少包括UPF200、边缘云网关210、GSLB220，还包括边缘控制器230。
需要说明的是，本申请实施例中，在网络架构布局上，数据通路可以连接运营商核心网的中心云和边缘云，并且为了实现将数据分流到边缘计算节点，新增了边缘云网关210和边缘控制器230，其中，边缘云网关210设置在MEC节点侧或边缘数据中心(Data Center，DC)侧，边缘控制器230设置在核心网的中心云，并分别与边缘云网关210、UPF200通信连接，GSLB220也部署在核心网的中心云侧，和边缘控制器230是并列的设备，并且UPF200、边缘云网关210和GSLB220分别对应不同的预配置规则，预配置规则表征业务加速的路由配置。
1)边缘控制器230，主要用于负责全局业务流量的调度，是控制业务流量调度到边缘云网关210，之后再由边缘云网关210调度到其本地具体的MEC处理服务器上，包括：
a、对接运营商能力开放平台，并在部署边缘业务时，对UPF200和边缘云网关210进行预配置。
具体地，边缘控制器230用于分别配置UPF200的第一预配置规则和第四预配置规则，以及边缘云网关210的第二预配置规则和第五预配置规则。上述配置规则将在之后的实施例中详细介绍。
例如，如图2所示，边缘控制器230可以通过运营商能力开放平台、运营商5G核心网，实现对UPF200的预配置。
b、可以从运营商5G核心网侧动态收集用户位置信息，为各托管业务就近选择边缘计算节点，其中，各托管业务表示5G移动通信网络中有边缘计算需求的业务，即需要业务加速的业务。
c、对接云基础设施即服务((Infrastructure as a Service，IaaS)或平台即服务(Platform-as-a-Service，PaaS)控制器，完成对边缘DC资源的控制。
其中，IaaS和PaaS在图2中未示出，实际中可以位于边缘云网关210和边缘控制器230之间，主要是边缘控制器230可以通过IaaS和PaaS对边缘云网关210的负载状态进行监控，控制边缘云网关210的负载调度。
2)GSLB220。在部署边缘业务时，也需要对GSLB220进行预配置，具体地：GSLB220对应第三预配置规则，其中，第三预配置规则至少包括：
a、针对源地址为边缘云网关210的IP地址的HTTP DNS请求，基于HTTP DNS请求中边缘云网关210的IP地址和业务加速域名返回相应的边缘应用VIP。
例如，GSLB220接收到边缘云网关210发送的第二HTTP DNS请求时，向边缘云网关210返回第一HTTP DNS响应；其中，第二HTTP DNS请求中至少包括业务加速域名、源地址、目的地址，源地址为边缘云网关210的IP地址，目的地址为GSLB220的IP地址，第一HTTP DNS响应中至少包括边缘应用VIP，边缘应用VIP为GSLB220根据边缘云网关210的IP地址和业务加速域名确定的。
b、针对GSLB220还可以人为添加干预方式，针对HTTP DNS请求中不同的源地址返回配置的IP地址。
3)UPF200。本申请实施例中需要对UPF200进行预配置，预配置功能表征业务加速的路由配置，UPF200需提供路由配置功能，UPF200对应第一预配置规则或第四预配置规则。
其中，第一预配置规则至少包括：
a、域名为预设业务加速域名的域名请求转发至边缘云网关210。
本申请实施例中，终端发送的域名请求可以为标准的DNS请求或第一HTTP DNS请求，本申请实施例中并不进行限制。
该规则主要针对请求状态为DNS请求的域名请求，UPF200可以解析DNS请求，查看DNS请求中域名，即第一预配置规则中UPF200可以具备对DNS请求的解析功能，查看该DNS请求中的域名，从而可以转发至边缘云网关210。
b、目的地址为GSLB220的IP地址的域名请求转发至边缘云网关210。
其中，UPF200的第一预配置规则中a和b是针对终端发送的域名请求，UPF200接收到终端发送的域名请求后，针对请求状态为DNS请求的域名请求 可以解析DNS请求查看域名，或针对请求状态为第一HTTP DNS请求的域名请求可以查看目的地址。
具体地，UPF200用于接收终端发送的域名请求，并若确定域名请求中域名为预设业务加速域名，或目的地址为GSLB220的IP地址时，则将域名请求转发至边缘云网关210。
c、目的地址为边缘应用VIP的业务请求转发至边缘云网关210。
具体地，UPF200用于接收终端发送的业务请求，并若确定业务请求中目的地址为边缘应用VIP时，则将业务请求转发至边缘云网关210。
第四预配置规则至少包括：
a、协议端口信息符合预设协议端口要求的域名请求转发至边缘云网关210。
本申请实施例中，第四预配置规则中UPF200不具备对DNS请求的域名请求进行解析的功能，主要是由边缘云网关210进行解析，因此，第四预配置规则中UPF200接收到终端发送的域名请求后，可以只查看其协议端口信息或目的地址。
其中，查看协议端口信息主要针对请求状态为DNS请求的域名请求，查看DNS请求的协议端口信息，例如，预设协议端口要求为用户数据报协议(User Datagram Protocol，UDP)端口(port)53，若确定协议端口信息为UDP port 53，说明该域名请求为DNS请求，转发至边缘云网关210，以使后续边缘云网关210执行相应的解析DNS请求能力，来获取域名判断是否需要加速。
b、目的地址为GSLB220的IP地址的域名请求转发至边缘云网关210。
具体地，UPF200用于接收终端发送的域名请求，若确定域名请求中协议端口信息符合预设协议端口要求，或目的地址为GSLB220的IP地址时，则将域名请求转发至边缘云网关210。
c、目的地址为边缘应用VIP的业务请求转发至边缘云网关210。
需要说明的是，第一预配置规则或第四预配置规则为设置的边缘控制器230配置的，或本地配置的，也就是说，UPF200不仅可以通过边缘控制器230统一进行配置管理，还可以通过本地配置加载，本申请实施例中并不进行限制。
4)边缘云网关210，主要用于本地流量即其负责地域范围内的流量的智能调度、负载均衡、统计分析等，将业务流量调度到具体的MEC处理服务器上。 本申请实施例中，部署边缘业务时，也需要对边缘云网关210进行预配置，具体地，边缘云网关210对应第二预配置规则或第五预配置规则。
其中，第二预配置规则至少包括：预设分流策略。
例如，预设分流策略为根据IP五元组信息进行分流，例如，通常IP五元组中包括源IP地址、目的IP地址、协议号、源端口和目的端口，可以基于负载均衡算法进行分流，例如负载均衡算法为源地址哈希法，对源IP地址进行哈希运算，通过哈希运算得到一个哈希值，基于该哈希值和MEC处理服务器列表的配置规则，确定相应的MEC处理服务器，进而转发到相应的MEC处理服务器上进行处理。
又例如，预设分流策略为根据统一资源定位符(Uniform Resource Locator，URL)信息进行分流，例如，可以根据业务请求中域名请求业务的类型，以及各MEC处理服务器上存储的特定域名或资源类型，例如特定域名或资源类型表征处理图片或视频业务类型，进而将业务请求转发到处理相应业务类型的MEC处理服务器上。
具体地分流策略本申请实施例中并不进行限制，可以根据实际需求和情况来选择使用。
第五预配置规则至少包括：预设分流策略；并具备解析DNS请求的能力。
即边缘云网关210的两种预配置规则，第五预配置规则相较于第二预配置规则，使得边缘云网关210具备了解析标准DNS请求的能力，能够对DNS报文进行解析，获取携带的域名，进而可以重新封装成相应的第二HTTP DNS请求。
需要说明的是，第二预配置规则或第五预配置请求为设置的边缘控制器230配置的，或本地配置的，也就是说，边缘云网关210不仅可以通过边缘控制器230统一进行配置管理，还可以通过本地配置加载，本申请实施例中并不进行限制。
另需要说明的是，边缘云网关210的预配置规则是和UPF200的预配置规则对应的，UPF200接收到终端发送的域名请求后，若基于其对应的第一预配置规则执行相应的行为，即解析域名或目的地址，进而转发至边缘云网关210，则边缘云网关210基于第二预配置规则执行相应的行为，可以直接基于域名等信息封装为第二HTTP DNS请求发送给GSLB220；若UPF200基于第四预配置规 则执行相应的行为，即不进行解析，只查看协议端口信息或目的地址，进而转发至边缘云网关210，则边缘云网关210基于第五预配置规则执行相应的行为，若为DNS请求，则先进行解析，再封装为第二HTTP DNS请求发送给GSLB220，对于这两种实施方式，本申请实施例中并不进行限制。
具体地，边缘云网关210用于：
S1、基于域名请求，从GSLB220获取对应的边缘应用VIP。
进一步地，边缘云网关210还用于：记录域名请求的请求状态；其中，请求状态表征DNS请求或第一HTTP DNS请求。
即本申请实施例中，可以支持终端通过标准DNS或第一HTTP DNS请求发起针对原始域名的域名请求，目的地址为GSLB220的IP地址。
执行S1时，边缘云网关210具体用于：
S1.1、基于域名请求，向GSLB220发送第二HTTP DNS请求，其中，第二HTTP DNS请求中至少包括业务加速域名、源地址、目的地址，源地址为边缘云网关210的IP地址，目的地址为GSLB220的IP地址。
具体地，执行步骤S1.1时可以有两种情况：
第一种情况：若域名请求中域名为预设业务加速域名，或目的地址为GSLB220的IP地址。
即UPF200的预配置规则为第一预配置规则，UPF200可以解析请求状态为DNS请求的域名请求，获取DNS请求中域名，则不管终端发送的域名请求为DNS请求还是第一HTTP DNS请求，边缘云网关210接收到UPF200发送的域名请求后，具体用于基于域名请求重新将自身的IP地址作为源地址以第二HTTP DNS封装转发至GSLB220。
即第一种情况针对UPF200对应的第一预配置规则，UPF200具有解析DNS请求的能力，边缘云网关210对应第二预配置规则，即边缘云网关210接收到域名请求后，不对为DNS请求的域名请求进行解析。
第二种情况：若域名请求中协议端口信息符合预设协议端口要求，或目的地址为GSLB220的IP地址。
则边缘云网关210具体用于：若域名请求的请求状态为DNS请求，则解析该域名请求，获取域名请求中域名，并将解析后的域名请求重新封装为第二 HTTP DNS请求，将重新封装的第二HTTP DNS请求发送给GSLB220。
即第二种情况针对UPF200对应的第四预配置规则，UPF200不具备解析DNS请求的能力，将域名请求发送给边缘云网关210后，边缘云网关210对应第五预配置规则，边缘云网关210具备解析DNS请求的能力，对请求状态为DNS请求的域名请求进行解析，并重新封装为第二HTTP DNS请求发送给GSLB220。
另外，若域名请求的请求状态为第一HTTP DNS请求，边缘云网关210虽然不需要解析，但也需要重新封装，例如将源地址修改为自身的IP地址，再发送给GSLB220。
S1.2、接收GSLB220返回的第一HTTP DNS响应，其中，第一HTTP DNS响应中至少包括边缘应用VIP，边缘应用VIP为GSLB220根据边缘云网关210的IP地址和业务加速域名确定的。
S2、通过UPF200向终端返回域名响应，其中，域名响应中至少包括边缘应用VIP。
执行步骤S2时，边缘云网关210具体用于：
若域名请求的请求状态为DNS请求，则返回DNS响应；
若域名请求的请求状态为第一HTTP DNS请求，则返回第二HTTP DNS响应。
本申请实施例中，边缘云网关210接收到GSLB220返回的第一HTTP DNS响应后，需要根据终端发送域名请求的请求状态，相应地通过UPF200向终端返回相应的响应包，即若终端发送请求状态为DNS请求，则需封装为标准的DNS响应包返回给UPF200，若终端发送的请求状态为第一HTTP DNS请求，则需封装为第二HTTP DNS响应包返回给UPF200，UPF200再将接收到的响应包发送给终端。
S3、接收UPF200转发的业务请求，其中，业务请求是UPF200解析到终端发送的业务请求中目的地址为边缘应用VIP时转发的。
S4、根据业务请求和预设分流策略，确定对应的MEC处理服务器，并将业务请求分流到对应的MEC处理服务器。
这样，本申请实施例中，可以兼容标准DNS和HTTP DNS寻址机制，新增边缘云网关和边缘控制器，终端可以通过标准DNS请求或第一HTTP DNS请求 发起针对原始域名的域名请求，对需要业务加速的域名请求可以转发至边缘云网关，其中若终端发送的域名请求为DNS请求，则可以配置UPF解析DNS请求，或者，配置边缘云网关具备解析DNS请求的能力，进而边缘云网关可以进行处理，从GSLB获取边缘应用VIP，将边缘应用VIP通过UPF发送给终端，使终端基于边缘应用VIP发送业务请求，将终端的业务请求分流到具体的MEC处理服务器，由于边缘云网关更接近于终端，并且通过边缘云网关可以将原始的DNS请求转换为HTTP DNS请求，可以绕过本地DNS，简化接入流程，因此，处理速率更快，减少时延，能够应用在DNS或HTTP DNS寻址场景下，实现正确就近选择边缘计算节点，达到边缘加速目的，并且，可以实现在现有技术框架下，通过互联网向用户提供各种应用服务(Over The Top，OTT)业务无需改造平滑接入边缘计算节点，用户无感知，提升实现简便性和用户体验。
基于上述实施例中图2所示的系统架构图，参阅图3所示，为本申请实施例中移动边缘计算节点的选择方法流程图，主要应用在边缘云网关中，该方法包括：
步骤300：边缘云网关接收用户面功能转发的域名请求。
其中，域名请求是用户面功能解析到终端发送的域名请求中域名为预设业务加速域名，或目的地址为全局负载均衡的IP地址时转发的；或者，域名请求是用户面功能确定终端发送的域名请求中协议端口信息符合预设协议端口要求，或目的地址为全局负载均衡的IP地址时转发的。
进一步地，还可以包括：记录域名请求的请求状态；其中，请求状态表征DNS请求或第一HTTP DNS请求。
本申请实施例中，针对终端发送的域名请求，在转发至边缘云网关时，基于UPF和边缘云网关不同的配置规则，提供了两种可能的实施方式，具体地：
第一种实施方式：UPF对应第一预配置规则，边缘云网关对应第二预配置规则，GSLB对应第三预配置规则，即可以使UPF具备解析DNS请求的能力，则：
UPF接收终端发送的域名请求，若域名请求的请求状态为DNS请求，则解析终端发送的域名请求，并且确定域名为预设业务加速域名时，转发至边缘云网关，若域名请求的请求状态为第一HTTP DNS请求，则确定该域名请求的目 的地址为GSLB的IP地址时转发至边缘云网关。
第二种实施方式：UPF对应第四预配置规则，边缘云网关对应第五预配置规则，GSLB对应第三预配置规则，即可以使边缘云网关具备解析DNS请求的能力，则：
UPF接收终端发送的域名请求，若域名请求的请求状态为DNS请求，则确定域名请求中协议端口信息符合预设协议端口要求时，转发至边缘云网关，若域名请求的请求状态为第一HTTP DNS请求，则确定该域名请求的目的地址为GSLB的IP地址时转发至边缘云网关。
步骤310：基于域名请求，从全局负载均衡获取对应的边缘应用VIP。
具体执行步骤310时，包括：
S1、基于域名请求，向GSLB发送第二HTTP DNS请求，其中，第二HTTP DNS请求中至少包括业务加速域名、源地址、目的地址，源地址为边缘云网关的IP地址，目的地址为全局负载均衡的IP地址。
基于步骤300中描述的两种实施方式，则在执行该S1时，相应地也可以有以下两种实施方式：
第一种实施方式：UPF对应第一预配置规则，边缘云网关对应第二预配置规则，GSLB对应第三预配置规则，即可以使UPF具备解析DNS请求的能力则：
若域名请求的请求状态为DNS请求，此时UPF已经解析完DNS请求，并转发至边缘云网关，则边缘云网关只需直接将解析后的域名请求重新封装为第二HTTP DNS请求，向GSLB发送第二HTTP DNS请求，若域名请求的请求状态为第一HTTP DNS请求，则边缘云网关可修改域名请求中源地址，修改为边缘云网关的IP地址，得到第二HTTP DNS请求转发至GSLB。
第二种实施方式：UPF对应第四预配置规则，边缘云网关对应第五预配置规则，GSLB对应第三预配置规则，即可以使边缘云网关具备解析DNS请求的能力，则：
若域名请求的请求状态为DNS请求，则边缘云网关解析域名请求，获取域名请求中域名，并将解析后的域名请求重新封装为第二HTTP DNS请求，将重新封装的第二HTTP DNS请求发送给全局负载均衡，若域名请求的请求状态为第一HTTP DNS请求，则边缘云网关可修改域名请求中源地址，得到第二HTTP  DNS请求转发至GSLB。
S2、接收GSLB返回的第一HTTP DNS响应，其中，第一HTTP DNS响应中至少包括边缘应用VIP，边缘应用VIP为全局负载均衡根据边缘云网关的IP地址和业务加速域名确定的。
步骤320：通过用户面功能向终端返回域名响应，其中，域名响应中至少包括边缘应用VIP。
执行步骤320时，可以分为以下两种情况：
第一种情况：若域名请求的请求状态为DNS请求，则返回DNS响应。
第二种情况：若域名请求的请求状态为第一HTTP DNS请求，则返回第二HTTP DNS响应。
步骤330：接收用户面功能转发的业务请求，其中，业务请求的目的地址为边缘应用VIP。
此时UPF在其第一预配置规则或第四预配置规则中，均预先配置了该条规则，即针对目的地址为边缘应用VIP的业务请求转发至边缘云网关。
步骤340：根据业务请求和预设分流策略，确定对应的MEC处理服务器，并将业务请求分流到对应的MEC处理服务器。
这样，本申请实施例中，新增边缘云网关，兼容DNS和HTTP DNS寻址场景，将终端的域名请求转发至边缘云网关，通过边缘云网关进行处理，最终实现将终端的业务请求分流到对应的MEC处理服务器上，实现移动边缘计算节点的选择机制，达到了业务加速的目的，解决了针对5G移动通信网络的MEC节点选择方案的问题。
基于上述实施例，下面采用具体应用场景进行说明，针对UPF和边缘云网关的不同预配置规则，下面可以采用两种不同的实施方式，对本申请实施例中移动边缘计算节点的选择方法进行说明。
第一种实施方式：若UPF对应第一预配置规则，边缘云网关对应第二预配置规则，即UPF解析DNS请求场景下。
具体参阅图4所示，为本申请实施例中一种移动边缘计算节点的选择方法交互流程图。
步骤400：终端向UPF发送域名请求。
具体地，终端可以通过标准DNS或HTTP DNS发起针对原始域名的请求，即终端可以基于传统的DNS或HTTP DNS寻址机制。
其中，该域名请求的请求状态为DNS请求或第一HTTP DNS请求。
步骤401：UPF接收终端发送的域名请求。
步骤402：UPF若确定域名请求中域名为预设业务加速域名，或目的地址为GSLB的IP地址时，将域名请求转发至边缘云网关。
本申请实施例中，可以对UPF配置第一预配置规则，使UPF具备解析DNS请求的能力，UPF可以基于对应的第一预配置规则，对于请求状态为DNS请求的域名请求，可以解析DNS请求，确定是否是需要业务加速的域名，对于请求状态为第一HTTP DNS请求的域名请求，可以查看目的地址，目的地址为GSLB的IP地址时确定需要业务加速，转发至边缘云网关。
步骤403：边缘云网关接收UPF转发的域名请求。
步骤404：边缘云网关向GSLB发送第二HTTP DNS请求。
其中，第二HTTP DNS请求中至少包括业务加速域名、源地址、目的地址，源地址为边缘云网关的IP地址，目的地址为GSLB的IP地址。
进一步地，边缘云网关记录域名请求的请求状态。
即边缘云网关将自身的IP地址作为源地址，向GSLB发起第二HTTP DNS请求，这样，针对请求状态为DNS请求的域名请求，通过边缘云网关，可以将原始DNS请求转换为第二HTTP DNS请求，再次发送时可以绕过本地DNS直接发送到GSLB，可以简化接入流程，针对请求状态为第一HTTP DNS请求的域名请求，边缘云网关将源地址修改为自身的IP地址，向GSLB发送第二HTTP DNS请求，以使GSLB可以根据源地址，确定源地址为边缘云网关的IP地址时，可以相应返回业务加速的边缘应用VIP。
步骤405：GSLB接收边缘云网关发送的第二HTTP DNS请求。
步骤406：GSLB向边缘云网关返回第一HTTP DNS响应。
其中，第一HTTP DNS响应中至少包括边缘应用VIP，边缘应用VIP为GSLB根据边缘云网关的IP地址和业务加速域名确定的。
本申请实施例中，该步骤GSLB可以基于其对应的第三预配置规则来实现，GSLB确定第二HTTP DNS请求中源地址为边缘云网关的IP地址，请求的域名 为业务加速域名，则可以根据边缘云网关的IP地址和业务加速域名对应的业务配置，选择返回实际的边缘应用VIP。
步骤407：边缘云网关接收GSLB返回的第一HTTP DNS响应。
步骤408：边缘云网关基于第一HTTP DNS响应通过UPF向终端返回域名响应。
其中，域名响应中至少包括边缘应用VIP。
具体地可以两种情况：
1)若域名请求的请求状态为DNS请求，则返回DNS响应。
2)若域名请求的请求状态为第一HTTP DNS请求，则返回第二HTTP DNS响应。
步骤409：终端接收边缘云网关通过UPF返回的域名响应。
步骤410：终端基于域名响应向UPF发送业务请求。
具体地，终端接收到域名响应后，可以根据域名响应中边缘应用VIP，以此为目的地址发起业务请求，其中，业务请求中目的地址为边缘应用VIP。
步骤411：UPF接收终端发送的业务请求。
步骤412：UPF确定业务请求的目的地址为边缘应用VIP时，将业务请求转发至边缘云网关。
这里UPF是基于对应的第一预配置规则或第四预配置规则来实现的，目的地址为边缘应用VIP的业务请求转发至边缘云网关。
步骤413：边缘云网关接收UPF转发的业务请求，根据业务请求和预设分流策略，确定对应的MEC处理服务器，并将业务请求分流到对应的MEC处理服务器。
这样，本申请实施例中，主要针对5G移动通信网络，提出了一种移动边缘计算节点的选择的业务数据流程，配置使得UPF具备解析DNS请求的能力，通过边缘云网关等设备，能够应用在终端的DNS寻址或HTTP DNS寻址场景下，可以将业务分流到最近的MEC处理服务器，精度更高，实现选择边缘计算节点，降低时延，达到业务加速目的。
第二种实施方式：若UPF对应第四预配置规则，边缘云网关对应第五预配置规则，即边缘云网关解析DNS请求场景下。
具体参阅图5所示，为本申请实施例中一种移动边缘计算节点的选择方法交互流程图。
步骤500：终端向UPF发送域名请求。
其中，该域名请求的请求状态为DNS请求或第一HTTP DNS请求。
步骤501：UPF接收终端发送的域名请求。
步骤502：UPF若确定域名请求中协议端口信息符合预设协议端口要求，或目的地址为GSLB的IP地址时，将域名请求转发至边缘云网关。
该步骤是UPF基于其对应的第四预配置规则实现的。
本申请实施例中，可以对UPF配置第四预配置规则，使UPF不解析DNS请求，UPF可以基于第四预配置规则，针对请求状态为DNS请求的域名请求，可以查看其协议端口信息，若符合预设要求，例如协议端口信息为UDP port 53，则确定为DNS请求并转发至边缘云网关，使边缘云网关基于其对应的第五预配置规则，解析DNS请求，对于请求状态为第一HTTP DNS请求的域名请求，可以查看目的地址，目的地址为GSLB的IP地址时确定需要业务加速，转发至边缘云网关。
步骤503：边缘云网关接收UPF转发的域名请求。
步骤504：若域名请求的请求状态为DNS请求，向GSLB发送第二HTTP DNS请求。
其中，若域名请求的请求状态为DNS请求，则边缘云网关解析该域名请求，获取域名，并将解析后的域名请求重新封装为第二HTTP DNS请求。
其中，第二HTTP DNS请求中至少包括业务加速域名、源地址、目的地址，源地址为边缘云网关的IP地址，目的地址为GSLB的IP地址。
进一步地，边缘云网关记录域名请求的请求状态。
这里边缘云网关对应配置的第五预配置规则，本申请实施例中，通过配置使边缘云网关具备解析DNS请求的能力，若域名请求的请求状态为DNS请求，则解析该域名请求，获取域名请求中域名，并将解析后的域名请求重新封装为第二HTTP DNS请求，将重新封装的第二HTTP DNS请求发送给GSLB。
若域名请求的请求状态为第一HTTP DNS请求，则可以直接将自身的IP地址作为源地址，以第二HTTP DNS封装转发至GSLB。
步骤505：GSLB接收边缘云网关发送的第二HTTP DNS请求。
步骤506：GSLB向边缘云网关返回第一HTTP DNS响应。
其中，第一HTTP DNS响应中至少包括边缘应用VIP，边缘应用VIP为GSLB根据边缘云网关的IP地址和业务加速域名确定的。
这里GSLB可以基于其对应的第三预配置规则来实现。
步骤507：边缘云网关接收GSLB返回的第一HTTP DNS响应。
本申请实施例中，上述步骤504、步骤507，边缘云网关可以认为是代理传统本地DNS(local DNS，LDNS)，具备LDNS功能。
步骤508：边缘云网关基于第一HTTP DNS响应通过UPF向终端返回域名响应。
其中，域名响应中至少包括边缘应用VIP。
具体地可以两种情况：
1)若域名请求的请求状态为DNS请求，则返回DNS响应。
2)若域名请求的请求状态为第一HTTP DNS请求，则返回第二HTTP DNS响应。
步骤509：终端接收边缘云网关通过UPF返回的域名响应。
步骤510：终端基于域名响应向UPF发送业务请求。
具体地，终端接收到域名响应后，可以根据域名响应中边缘应用VIP，以此为目的地址发起业务请求，其中，业务请求中目的地址为边缘应用VIP。
步骤511：UPF接收终端发送的业务请求。
步骤512：UPF确定业务请求的目的地址为边缘应用VIP时，将业务请求转发至边缘云网关。
这里UPF是基于对应的第一预配置规则或第四预配置规则来实现的，目的地址为边缘应用VIP的业务请求转发至边缘云网关。
步骤513：边缘云网关接收UPF转发的业务请求，根据业务请求和预设分流策略，确定对应的MEC处理服务器，并将业务请求分流到对应的MEC处理服务器。
这样，本申请实施例中，主要针对5G移动通信网络，提出了另一种移动边缘计算节点的选择的业务数据流程，配置使得边缘云网关具备解析DNS请求 的能力，通过边缘云网关等设备，能够应用在终端的DNS寻址或HTTP DNS寻址场景下，正确选择就近的边缘计算节点，可以将业务分流到最近的MEC处理服务器，位置精度更高，从而实现边缘加速。
基于上述实施例，参阅图6所示为本申请实施例中移动边缘计算节点选择的边缘云网关，边缘云网关设置在移动边缘计算节点的选择系统中，该系统至少包括UPF、边缘云网关、GSLB具体包括：
第一接收模块60，用于接收UPF转发的域名请求，其中，所述域名请求中域名为预设业务加速域名，或目的地址为GSLB的IP地址；或者，所述域名请求中协议端口信息符合预设协议端口要求；
获取模块61，用于基于所述域名请求，从所述GSLB获取对应的边缘应用VIP；
发送模块62，用于通过所述UPF向所述终端返回域名响应，其中，所述域名响应中至少包括所述边缘应用VIP；
第二接收模块63，用于接收所述UPF转发的业务请求，其中，所述业务请求的目的地址为所述边缘应用VIP；
确定模块64，用于根据所述业务请求和预设分流策略，确定对应的MEC处理服务器；
分流模块65，用于将所述业务请求分流到所述对应的MEC处理服务器。
可选的，进一步包括，记录模块66，用于：记录所述域名请求的请求状态；其中，所述请求状态表征DNS请求或第一HTTP DNS请求。
可选的，获取模块61具体用于：
基于所述域名请求，向所述GSLB发送第二HTTP DNS请求，其中，所述第二HTTP DNS请求中至少包括业务加速域名、源地址、目的地址，所述源地址为所述边缘云网关的IP地址，目的地址为所述GSLB的IP地址；
接收所述GSLB返回的第一HTTP DNS响应，其中，所述第一HTTP DNS响应中至少包括边缘应用VIP，所述边缘应用VIP为所述GSLB根据所述边缘云网关的IP地址和业务加速域名确定的。
可选的，若所述域名请求中协议端口信息符合预设协议端口要求，或目的地址为GSLB的IP地址，则获取模块61具体用于：
若所述域名请求的请求状态为DNS请求，则解析所述域名请求，获取所述域名请求中域名，并将解析后的域名请求重新封装为第二HTTP DNS请求；将重新封装的第二HTTP DNS请求发送给所述GSLB。
可选的，发送模块62具体用于：
若所述域名请求的请求状态为DNS请求，则返回DNS响应；
若所述域名请求的请求状态为第一HTTP DNS请求，则返回第二HTTP DNS响应。
可选的，所述UPF、所述边缘云网关和所述GSLB分别对应不同的预配置规则，所述预配置规则表征业务加速的路由配置。
可选的，所述UPF对应第一预配置规则，所述第一预配置规则至少包括：域名为预设业务加速域名的域名请求转发至边缘云网关；或，目的地址为GSLB的IP地址的域名请求转发至边缘云网关；或，目的地址为边缘应用VIP的业务请求转发至边缘云网关；
所述边缘云网关对应第二预配置规则，所述第二预配置规则至少包括：预设分流策略；
所述GSLB对应第三预配置规则，所述第三预配置规则至少包括：针对源地址为边缘云网关的IP地址的HTTP DNS请求，基于HTTP DNS请求中边缘云网关的IP地址和业务加速域名返回相应的边缘应用VIP。
可选的，所述UPF对应第四预配置规则，所述第四预配置规则至少包括：协议端口信息符合预设协议端口要求的域名请求转发至边缘云网关；或，目的地址为GSLB的IP地址的域名请求转发至边缘云网关；或，目的地址为边缘应用VIP的业务请求转发至边缘云网关；
所述边缘云网关对应第五预配置规则，所述第五预配置规则至少包括：预设分流策略；并具备解析DNS请求的能力。
可选的，所述第一预配置规则、所述第二预配置规则、所述第四预配置规则或所述第五预配置规则为设置的边缘控制器配置的，或本地配置的；
其中，所述边缘控制器设置在所述系统中核心网的云中心，并分别与边缘云网关、UPF通信连接。
基于上述实施例，参阅图7所示，本申请实施例中，一种电子设备的结构 示意图。
本申请实施例提供了一种电子设备，该电子设备可以包括处理器710(Center Processing Unit，CPU)、存储器720、输入设备730和输出设备740等，输入设备730可以包括键盘、鼠标、触摸屏等，输出设备740可以包括显示设备，如液晶显示器(Liquid Crystal Display，LCD)、阴极射线管(Cathode Ray Tube，CRT)等。
存储器720可以包括只读存储器(ROM)和随机存取存储器(RAM)，并向处理器710提供存储器720中存储的程序指令和数据。在本申请实施例中，存储器720可以用于存储本申请实施例中任一种移动边缘计算节点的选择方法的程序。
处理器710通过调用存储器720存储的程序指令，处理器710用于按照获得的程序指令执行本申请实施例中任一种移动边缘计算节点的选择方法。
基于上述实施例，本申请实施例中，提供了一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现上述任意方法实施例中的移动边缘计算节点的选择方法。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
在示例性实施例中，还提供了一种计算机程序产品，当该计算机程序产品被执行时，其用于实现上述实施例提供的移动边缘计算节点的选择方法。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和修改。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的精神和范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (17)

  1. 一种移动边缘计算节点的选择方法，所述方法由边缘云网关执行，所述边缘云网关设置在移动边缘计算节点的选择系统中，所述系统至少包括用户面功能、所述边缘云网关和全局负载均衡，具体地：
    边缘云网关接收用户面功能转发的域名请求，其中，所述域名请求中域名为预设业务加速域名，或目的地址为全局负载均衡的IP地址；或者，所述域名请求中协议端口信息符合预设协议端口要求；
    基于所述域名请求，从所述全局负载均衡获取对应的边缘应用虚拟网络之间互连的协议虚拟VIP；
    通过所述用户面功能向所述终端返回域名响应，其中，所述域名响应中至少包括所述边缘应用VIP；
    接收所述用户面功能转发的业务请求，其中，所述业务请求的目的地址为所述边缘应用VIP；
    根据所述业务请求和预设分流策略，确定对应的移动边缘计算MEC处理服务器，并将所述业务请求分流到所述对应的MEC处理服务器。
  2. 如权利要求1所述的方法，所述方法还包括：
    记录所述域名请求的请求状态；其中，所述请求状态表征DNS请求或第一HTTP DNS请求。
  3. 如权利要求2所述的方法，所述基于所述域名请求，从所述全局负载均衡获取对应的边缘应用虚拟网络之间互连的边缘应用虚拟VIP，具体包括：
    基于所述域名请求，向所述全局负载均衡发送第二HTTP DNS请求，其中，所述第二HTTP DNS请求中至少包括业务加速域名、源地址、目的地址，所述源地址为所述边缘云网关的IP地址，目的地址为所述全局负载均衡的IP地址；
    接收所述全局负载均衡返回的第一HTTP DNS响应，其中，所述第一HTTP DNS响应中至少包括边缘应用VIP，所述边缘应用VIP为所述全局负载均衡根据所述边缘云网关的IP地址和业务加速域名确定的。
  4. 如权利要求3所述的方法，若所述域名请求中协议端口信息符合预设协议端口要求，或目的地址为全局负载均衡的IP地址，则所述基于所述域名 请求，向所述全局负载均衡发送第二HTTP DNS请求，包括：
    若所述域名请求的请求状态为DNS请求，则解析所述域名请求，获取所述域名请求中域名，并将解析后的域名请求重新封装为第二HTTP DNS请求；
    将重新封装的第二HTTP DNS请求发送给所述全局负载均衡。
  5. 如权利要求2所述的方法，所述通过所述用户面功能向所述终端返回域名响应，包括：
    若所述域名请求的请求状态为DNS请求，则返回DNS响应；
    若所述域名请求的请求状态为第一HTTP DNS请求，则返回第二HTTP DNS响应。
  6. 如权利要求1-5任一项所述的方法，所述用户面功能、所述边缘云网关和所述全局负载均衡分别对应不同的预配置规则，所述预配置规则表征业务加速的路由配置。
  7. 如权利要求6所述的方法，所述用户面功能对应第一预配置规则，所述第一预配置规则至少包括：域名为预设业务加速域名的域名请求转发至边缘云网关；或，目的地址为全局负载均衡的IP地址的域名请求转发至边缘云网关；或，目的地址为边缘应用VIP的业务请求转发至边缘云网关；
    所述边缘云网关对应第二预配置规则，所述第二预配置规则至少包括：预设分流策略；
    所述全局负载均衡对应第三预配置规则，所述第三预配置规则至少包括：针对源地址为边缘云网关的IP地址的HTTP DNS请求，基于HTTP DNS请求中边缘云网关的IP地址和业务加速域名返回相应的边缘应用VIP。
  8. 如权利要求6所述的方法，所述用户面功能对应第四预配置规则，所述第四预配置规则至少包括：协议端口信息符合预设协议端口要求的域名请求转发至边缘云网关；或，目的地址为全局负载均衡的IP地址的域名请求转发至边缘云网关；或，目的地址为边缘应用VIP的业务请求转发至边缘云网关；
    所述边缘云网关对应第五预配置规则，所述第五预配置规则至少包括：预设分流策略；并具备解析DNS请求的能力。
  9. 如权利要求7或8所述的方法，所述第一预配置规则、所述第二预配置规则、所述第四预配置规则或所述第五预配置规则为设置的边缘控制器配置 的，或本地配置的；
    其中，所述边缘控制器设置在所述系统中核心网的云中心，并分别与边缘云网关、用户面功能通信连接。
  10. 如权利要求1-5任一项所述的方法，所述边缘云网关设置在所述系统的MEC节点侧或边缘数据中心DC侧。
  11. 一种移动边缘计算节点选择的边缘云网关，所述边缘云网关设置在移动边缘计算节点的选择系统中，所述系统至少包括用户面功能、所述边缘云网关和全局负载均衡，具体包括：
    第一接收模块，用于接收用户面功能转发的域名请求，其中，所述域名请求中域名为预设业务加速域名，或目的地址为全局负载均衡的IP地址；或者，所述域名请求中协议端口信息符合预设协议端口要求；
    获取模块，用于基于所述域名请求，从所述全局负载均衡获取对应的边缘应用虚拟网络之间互连的协议虚拟VIP；
    发送模块，用于通过所述用户面功能向所述终端返回域名响应，其中，所述域名响应中至少包括所述边缘应用VIP；
    第二接收模块，用于接收所述用户面功能转发的业务请求，其中，所述业务请求的目的地址为所述边缘应用VIP；
    确定模块，用于根据所述业务请求和预设分流策略，确定对应的移动边缘计算MEC处理服务器；
    分流模块，用于将所述业务请求分流到所述对应的MEC处理服务器。
  12. 一种移动边缘计算节点的选择系统，至少包括：用户面功能、边缘云网关和全局负载均衡，具体地：
    所述用户面功能，用于接收终端发送的域名请求，并若确定所述域名请求中域名为预设业务加速域名，或目的地址为全局负载均衡的IP地址时，或者，若确定所述域名请求中协议端口信息符合预设协议端口要求时，则将所述域名请求转发至所述边缘云网关；
    所述边缘云网关，用于基于所述域名请求，从所述全局负载均衡获取对应的边缘应用虚拟网络之间互连的协议虚拟VIP；
    通过所述用户面功能向所述终端返回域名响应，其中，所述域名响应中至 少包括所述边缘应用VIP；
    接收所述用户面功能转发的业务请求，其中，所述业务请求是所述用户面功能解析到所述终端发送的业务请求中目的地址为所述边缘应用VIP时转发的；
    根据所述业务请求和预设分流策略，确定对应的移动边缘计算MEC处理服务器，并将所述业务请求分流到所述对应的MEC处理服务器。
  13. 如权利要求12所述的系统，所述边缘云网关具体用于：
    基于所述域名请求，向所述全局负载均衡发送第二HTTP DNS请求，其中，所述第二HTTP DNS请求中至少包括业务加速域名、源地址、目的地址，所述源地址为所述边缘云网关的IP地址，目的地址为所述全局负载均衡的IP地址；
    接收所述全局负载均衡返回的第一HTTP DNS响应，其中，所述第一HTTP DNS响应中至少包括边缘应用VIP，所述边缘应用VIP为所述全局负载均衡根据所述边缘云网关的IP地址和业务加速域名确定的。
  14. 如权利要求13所述的系统，若所述域名请求是所述用户面功能确定终端发送的域名请求中协议端口信息符合预设协议端口要求，或目的地址为全局负载均衡的IP地址时转发的，所述边缘云网关具体用于：
    若所述域名请求的请求状态为DNS请求，则解析所述域名请求，获取所述域名请求中域名，并将解析后的域名请求重新封装为第二HTTP DNS请求；
    将重新封装的第二HTTP DNS请求发送给所述全局负载均衡。
  15. 一种电子设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时执行权利要求1-10任一项所述方法。
  16. 一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序用于执行权利要求1-10任一项所述方法。
  17. 一种包括指令的计算机程序产品，当其在计算机上运行时，使得所述计算机执行权利要求1-10任一项所述的方法。
PCT/CN2020/086398 2019-05-10 2020-04-23 一种移动边缘计算节点的选择方法、装置及系统 WO2020228505A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2021551817A JP7278679B2 (ja) 2019-05-10 2020-04-23 モバイルエッジコンピューティングノードの選択方法、装置及びシステム
EP20806492.3A EP3968610A4 (en) 2019-05-10 2020-04-23 METHOD, DEVICE AND SYSTEM FOR SELECTING A MOBILE NETWORK EDGE COMPUTER NODE
US17/380,585 US11431673B2 (en) 2019-05-10 2021-07-20 Method, apparatus, and system for selecting MEC node

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910387587.9A CN110198363B (zh) 2019-05-10 2019-05-10 一种移动边缘计算节点的选择方法、装置及系统
CN201910387587.9 2019-05-10

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/380,585 Continuation US11431673B2 (en) 2019-05-10 2021-07-20 Method, apparatus, and system for selecting MEC node

Publications (1)

Publication Number Publication Date
WO2020228505A1 true WO2020228505A1 (zh) 2020-11-19

Family

ID=67752528

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/086398 WO2020228505A1 (zh) 2019-05-10 2020-04-23 一种移动边缘计算节点的选择方法、装置及系统

Country Status (5)

Country Link
US (1) US11431673B2 (zh)
EP (1) EP3968610A4 (zh)
JP (1) JP7278679B2 (zh)
CN (1) CN110198363B (zh)
WO (1) WO2020228505A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113556727A (zh) * 2021-07-19 2021-10-26 中国联合网络通信集团有限公司 基于移动容器的云设备的数据传输方法及系统

Families Citing this family (48)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110198307B (zh) 2019-05-10 2021-05-18 深圳市腾讯计算机系统有限公司 一种移动边缘计算节点的选择方法、装置及系统
CN110198363B (zh) * 2019-05-10 2021-05-18 深圳市腾讯计算机系统有限公司 一种移动边缘计算节点的选择方法、装置及系统
CN112104680B (zh) 2019-06-17 2023-03-31 中国移动通信有限公司研究院 一种确定边缘应用的方法、装置、设备及存储介质
CN110290140B (zh) * 2019-06-28 2021-09-24 腾讯科技（深圳）有限公司 多媒体数据处理方法及装置、存储介质、电子设备
CN110445886B (zh) * 2019-07-05 2020-11-06 网宿科技股份有限公司 一种实现域名访问加速的方法和系统
CN114938362A (zh) * 2019-09-06 2022-08-23 华为技术有限公司 域名系统服务器的确定方法、请求处理方法和装置、系统
WO2021051420A1 (zh) * 2019-09-21 2021-03-25 华为技术有限公司 一种dns缓存记录的确定方法及装置
CN110769039B (zh) * 2019-10-09 2021-12-10 腾讯科技（深圳）有限公司 资源调度方法及装置、电子设备和计算机可读存储介质
CN110912835B (zh) * 2019-11-08 2023-04-07 腾讯科技（深圳）有限公司 业务分流方法、装置及系统
CN112825524B (zh) * 2019-11-20 2022-12-27 中国电信股份有限公司 网络服务节点的确定方法、装置和系统
CN110933061B (zh) * 2019-11-22 2022-02-18 中国联合网络通信集团有限公司 一种通信方法及装置
CN110995826B (zh) * 2019-11-29 2022-05-03 腾讯科技（深圳）有限公司 通信处理方法、装置、计算机可读介质及电子设备
CN112954084B (zh) * 2019-12-11 2022-11-08 中移物联网有限公司 边缘计算的处理方法、网络功能实例及边缘服务管控中心
CN111064821A (zh) * 2019-12-23 2020-04-24 北京达佳互联信息技术有限公司 边缘节点的ip地址的确定方法和装置
CN113055426A (zh) * 2019-12-28 2021-06-29 中移(成都)信息通信科技有限公司 业务访问方法、装置、设备和介质
CN113067907B (zh) * 2020-01-02 2023-04-07 中国移动通信有限公司研究院 一种边缘应用寻址的方法和相关设备
CN113067909B (zh) * 2020-01-02 2023-04-07 中国移动通信有限公司研究院 边缘节点寻址方法、装置、设备及存储介质
CN113382028B (zh) * 2020-03-10 2023-04-07 中国电信股份有限公司 内容分发网络实现方法和系统、边缘用户面功能实体
CN114124817B (zh) * 2020-03-15 2023-03-14 腾讯科技（深圳）有限公司 基于边缘计算的通信方法、装置、介质及电子设备
CN111427679B (zh) * 2020-03-25 2023-12-22 中国科学院自动化研究所 面向边缘计算的计算任务调度方法、系统、装置
CN113472822A (zh) * 2020-03-30 2021-10-01 中移(上海)信息通信科技有限公司 数据分流方法、装置、设备及介质
CN111565218B (zh) * 2020-04-08 2023-03-10 深圳数联天下智能科技有限公司 一种数据处理方法、电子设备
CN113301077B (zh) * 2020-05-20 2022-06-03 阿里巴巴集团控股有限公司 云计算服务部署与分流方法、系统、设备及存储介质
CN113766629B (zh) * 2020-06-03 2022-12-27 中国移动通信集团浙江有限公司 5g边缘计算场景下的业务处理方法及系统
CN111405614B (zh) * 2020-06-04 2020-09-29 北京东方通科技股份有限公司 一种移动边缘计算app负荷分担的方法
CN111683139B (zh) * 2020-06-05 2022-10-21 北京百度网讯科技有限公司 用于均衡负载的方法和装置
CN111770477B (zh) * 2020-06-08 2024-01-30 中天通信技术有限公司 一种mec网络的保护资源的部署方法及相关装置
CN111901387B (zh) * 2020-07-01 2022-07-08 中国联合网络通信集团有限公司 一种云专线的连接方法及装置
CN113973099B (zh) * 2020-07-24 2023-12-15 中国电信股份有限公司 获取eas的ip地址的方法、装置及系统
CN114095562B (zh) * 2020-07-31 2024-10-15 中国电信股份有限公司 边缘应用发现方法、系统以及增强防火墙
CN114080061A (zh) * 2020-08-17 2022-02-22 华为技术有限公司 一种基于数据边缘协议的通信方法
CN114598676A (zh) * 2020-11-19 2022-06-07 中国电信股份有限公司 应用寻址方法、系统和存储介质
CN112637310B (zh) * 2020-12-17 2022-05-27 中国联合网络通信集团有限公司 边缘服务发现的方法、边缘服务网络
CN113037884A (zh) * 2021-02-25 2021-06-25 浙江九州云信息科技有限公司 一种基于边缘管理的增强dns分流应用的方法
CN112995320B (zh) * 2021-03-03 2024-05-14 浪潮通信技术有限公司 基于流表的upf扩容下的负荷分担方法及系统
CN115118786B (zh) * 2021-03-22 2024-03-19 中国电信股份有限公司 边缘业务调度方法、装置和系统、存储介质
CN115426413B (zh) * 2021-05-14 2024-03-12 贵州白山云科技股份有限公司 基于5g的边缘节点调度方法、装置、介质及设备
CN113381894B (zh) * 2021-06-10 2024-04-12 北京小程科技有限公司 用于城市路内停车管理的去中心化数据通讯系统及方法
CN115529631B (zh) * 2021-06-24 2024-05-28 中移(成都)信息通信科技有限公司 通信系统、方法、装置、第一设备及存储介质
CN113179190B (zh) * 2021-06-29 2022-01-07 深圳智造谷工业互联网创新中心有限公司 边缘控制器、边缘计算系统及其配置方法
CN114584558B (zh) * 2022-01-17 2024-03-15 深圳渊联技术有限公司 云边协同分布式api网关系统及api调用方法
CN114401502B (zh) * 2022-01-21 2023-07-18 中国联合网络通信集团有限公司 配置方法、装置、电子设备及存储介质
CN114827276B (zh) * 2022-04-22 2023-10-24 网宿科技股份有限公司 基于边缘计算的数据处理方法、设备及可读存储介质
CN115242817B (zh) * 2022-07-21 2023-10-24 阿里巴巴（中国）有限公司 数据访问处理方法、装置、设备和存储介质
CN115297179B (zh) * 2022-07-25 2024-03-08 天翼云科技有限公司 一种数据传输方法及装置
CN118075231A (zh) * 2022-11-23 2024-05-24 腾讯科技（深圳）有限公司 域名查询方法、装置、设备及存储介质
CN116170303A (zh) * 2022-12-02 2023-05-26 中国联合网络通信集团有限公司 一种数据配置方法、装置、服务器及存储介质
TWI838172B (zh) * 2023-03-16 2024-04-01 中華電信股份有限公司 企業專網與邊緣應用開通管理系統、方法及其電腦可讀媒介

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109640319A (zh) * 2019-01-16 2019-04-16 腾讯科技（深圳）有限公司 基于接入信息的调度方法、装置及电子设备
US20190138934A1 (en) * 2018-09-07 2019-05-09 Saurav Prakash Technologies for distributing gradient descent computation in a heterogeneous multi-access edge computing (mec) networks
CN110198307A (zh) * 2019-05-10 2019-09-03 深圳市腾讯计算机系统有限公司 一种移动边缘计算节点的选择方法、装置及系统
CN110198363A (zh) * 2019-05-10 2019-09-03 深圳市腾讯计算机系统有限公司 一种移动边缘计算节点的选择方法、装置及系统
CN110769039A (zh) * 2019-10-09 2020-02-07 腾讯科技（深圳）有限公司 资源调度方法及装置、电子设备和计算机可读存储介质

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6119143A (en) * 1997-05-22 2000-09-12 International Business Machines Corporation Computer system and method for load balancing with selective control
US6150875A (en) * 1998-04-17 2000-11-21 Advanced Micro Devices, Inc. Apparatus and method for equalizing received network signals using a transconductance controlled single zero single pole filter
EP1244262B1 (en) * 2001-03-23 2005-05-11 Sun Microsystems, Inc. Redirection of client requests
US7970876B2 (en) * 2002-07-23 2011-06-28 Avaya Communication Israel Ltd. Global server load balancer
US8756340B2 (en) * 2007-12-20 2014-06-17 Yahoo! Inc. DNS wildcard beaconing to determine client location and resolver load for global traffic load balancing
CA2711467A1 (en) * 2008-01-23 2009-07-30 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for pooling network resources
CN102404378B (zh) * 2010-09-07 2014-11-05 成都索贝数码科技股份有限公司 一种流媒体分发传输网络系统
CN101984637B (zh) * 2010-11-02 2014-06-11 中兴通讯股份有限公司 内容分发实现方法及系统
CN103181148B (zh) * 2010-11-08 2017-05-31 瑞典爱立信有限公司 移动网络中的业务加速
US20150188807A1 (en) * 2012-06-26 2015-07-02 Nec Corporation Communication method, information processing apparatus, communication system, communication terminal, and program
US10516608B2 (en) * 2014-09-11 2019-12-24 Oath Inc. Systems and methods for directly responding to distributed network traffic
CN104660700B (zh) * 2015-03-03 2019-02-19 网宿科技股份有限公司 一种内容分发网络的方法和系统
WO2017176307A1 (en) * 2016-04-08 2017-10-12 Intel Corporation User-plane path selection for the edge service
CN109257781B (zh) * 2017-07-13 2021-03-26 鸿海精密工业股份有限公司 换手方法与装置
US11258873B2 (en) * 2017-11-10 2022-02-22 Intel Corporation Multi-access edge computing (MEC) architecture and mobility framework
US10523748B2 (en) * 2017-12-22 2019-12-31 A10 Networks, Inc. Managing health status of network devices in a distributed global server load balancing system
US11134410B2 (en) * 2017-12-25 2021-09-28 Nokia Solutions And Networks Oy Quality of service (QoS) control in mobile edge computing (MEC)
CN116232667A (zh) * 2018-07-13 2023-06-06 三星电子株式会社 用于边缘计算服务的方法及其电子装置
US11257361B2 (en) * 2019-08-15 2022-02-22 National Yunlin University Of Science And Technology Vehicle driving shockwave prediction system for active safe driving and method thereof
KR20210098724A (ko) * 2020-02-03 2021-08-11 삼성전자주식회사 엣지 컴퓨팅 서비스 제공을 위한 방법 및 장치
US20220052961A1 (en) * 2020-08-11 2022-02-17 Verizon Patent And Licensing Inc. Resource discovery in a multi-edge computing network

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190138934A1 (en) * 2018-09-07 2019-05-09 Saurav Prakash Technologies for distributing gradient descent computation in a heterogeneous multi-access edge computing (mec) networks
CN109640319A (zh) * 2019-01-16 2019-04-16 腾讯科技（深圳）有限公司 基于接入信息的调度方法、装置及电子设备
CN110198307A (zh) * 2019-05-10 2019-09-03 深圳市腾讯计算机系统有限公司 一种移动边缘计算节点的选择方法、装置及系统
CN110198363A (zh) * 2019-05-10 2019-09-03 深圳市腾讯计算机系统有限公司 一种移动边缘计算节点的选择方法、装置及系统
CN110769039A (zh) * 2019-10-09 2020-02-07 腾讯科技（深圳）有限公司 资源调度方法及装置、电子设备和计算机可读存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3968610A4

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113556727A (zh) * 2021-07-19 2021-10-26 中国联合网络通信集团有限公司 基于移动容器的云设备的数据传输方法及系统
CN113556727B (zh) * 2021-07-19 2022-08-23 中国联合网络通信集团有限公司 基于移动容器的云设备的数据传输方法及系统

Also Published As

Publication number Publication date
CN110198363A (zh) 2019-09-03
CN110198363B (zh) 2021-05-18
EP3968610A1 (en) 2022-03-16
US20210352042A1 (en) 2021-11-11
EP3968610A4 (en) 2022-07-06
JP2022522368A (ja) 2022-04-18
JP7278679B2 (ja) 2023-05-22
US11431673B2 (en) 2022-08-30

Similar Documents

Publication Publication Date Title
WO2020228505A1 (zh) 一种移动边缘计算节点的选择方法、装置及系统
WO2020228469A1 (zh) 一种移动边缘计算节点的选择方法、装置及系统
KR101987784B1 (ko) 소프트웨어 정의 네트워크를 기반으로 내용 배포 네트워크를 구현하는 방법 및 시스템
US9647871B2 (en) Routing proxy for resource requests and resources
WO2023000935A1 (zh) 一种数据处理方法、网元设备以及可读存储介质
Liu et al. CFN-dyncast: Load Balancing the Edges via the Network
US20170155730A1 (en) Terminating connections and selecting target source devices for resource requests
US8341285B2 (en) Method and system for transferring files
US11128733B2 (en) Server-side resource prioritization
CN112087382B (zh) 一种服务路由方法及装置
WO2023151264A1 (zh) 负载均衡方法、装置、节点及存储介质
US20140025800A1 (en) Systems and methods for multi-blade load balancing
US20180091631A1 (en) Systems and methods for writing prioritized http/2 data to a socket buffer
CN117546453A (zh) 用于基于服务质量参数建立网络切片中的消息优先级的方法、系统和计算机可读介质
US20180063220A1 (en) Systems and methods to provide hypertext transfer protocol 2.0 optimization through multiple links
Yan et al. Design and implementation of integrated ICN and CDN as a video streaming service
CN113973086B (zh) 一种数据传输方法、装置及存储介质
US12010012B2 (en) Application-aware BGP path selection and forwarding
US20240179223A1 (en) Method for providing edge computing service and apparatus for edge computing service
CN116418794A (zh) 适用于http3服务的cdn调度方法、装置、系统、设备及介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20806492

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021551817

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020806492

Country of ref document: EP

Effective date: 20211210