WO2021098407A1 - 基于mec的服务节点分配方法、装置及相关服务器 - Google Patents

基于mec的服务节点分配方法、装置及相关服务器 Download PDF

Info

Publication number
WO2021098407A1
WO2021098407A1 PCT/CN2020/120328 CN2020120328W WO2021098407A1 WO 2021098407 A1 WO2021098407 A1 WO 2021098407A1 CN 2020120328 W CN2020120328 W CN 2020120328W WO 2021098407 A1 WO2021098407 A1 WO 2021098407A1
Authority
WO
WIPO (PCT)
Prior art keywords
service node
terminal device
index information
information
network index
Prior art date
Application number
PCT/CN2020/120328
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 中移物联网有限公司
Publication of WO2021098407A1 publication Critical patent/WO2021098407A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/101—Server selection for load balancing based on network conditions
    • 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

  • the embodiments of the present disclosure relate to the technical field of edge computing, and in particular to a method, device, cloud server, MEC server, and computer-readable storage medium based on mobile edge computing (Mobile Edge Computing, MEC) service node allocation.
  • edge computing Mobile Edge Computing, MEC
  • DNS Domain Name System
  • IP server Internet Protocol
  • the terminal application needs to support DNS domain name access.
  • the Internet of Things scenario due to some terminal capabilities Limited, it may not support DNS domain name access.
  • dynamic routing methods it needs to rely on network routing equipment, and is generally used to support active and standby server scenarios. Therefore, the service drainage method in related technologies has a problem of poor flexibility.
  • the embodiments of the present disclosure provide a MEC-based method and device for allocating service nodes, a cloud server, an MEC server, and a computer-readable storage medium to solve the problem of poor flexibility in service drainage methods in related technologies.
  • embodiments of the present disclosure provide an MEC-based method for allocating service nodes, which is applied to a cloud server, and the method includes:
  • the network index information of at least one service node controlled by the MEC server that is fed back by the mobile edge computing MEC server based on a query request; wherein the query request includes the identification information, and the network index information of each service node includes Network performance measurement information from the terminal device to the service node corresponding to the identification information;
  • Target service node for the terminal device based on the network index information of the at least one service node; wherein, the target service node is a service node in the at least one service node;
  • the access identifier of the target serving node is sent to the terminal device, where the access identifier is used to instruct the terminal device to access the target serving node.
  • embodiments of the present disclosure provide an MEC-based method for allocating service nodes, which is applied to an MEC server, and the method includes:
  • the network index information of each service node includes the terminal device corresponding to the identification information to the service Network performance measurement information of the node;
  • the network index information of the at least one service node is sent to a cloud server; wherein the network index information of the at least one service node is used to instruct the cloud server to select a target service node for the terminal device.
  • the embodiments of the present disclosure also provide an MEC-based service node allocation method, which is applied to a mobile edge computing MEC server, and the method includes:
  • the query request includes the identification information of the terminal device and the identification information of the target service application;
  • the MEC server Based on the query request, query the MEC server based on the network index information of at least one service node controlled by the service application corresponding to the identification information of the target service application; wherein, the network index information of each service node includes all Network performance measurement information from the terminal device to the service node corresponding to the identification information;
  • Target service node for the terminal device based on the network index information of the at least one service node; wherein, the target service node is a service node in the at least one service node;
  • the access identifier of the target serving node is sent to the terminal device, where the access identifier is used to instruct the terminal device to access the target serving node.
  • an MEC-based service node allocation device which is applied to a cloud server, and the device includes:
  • the first receiving module is configured to receive a login request sent by a terminal device; wherein the login request includes identification information of the terminal device;
  • the second receiving module is configured to receive the network index information of at least one service node controlled by the MEC server that is fed back by the mobile edge computing MEC server based on the query request; wherein, the query request includes the identification information, and each service The network index information of the node includes network performance measurement information from the terminal device corresponding to the identification information to the service node;
  • the first selection module is configured to select a target service node for the terminal device based on the network index information of the at least one service node; wherein, the target service node is a service node in the at least one service node;
  • the first sending module is configured to send the access identifier of the target serving node to the terminal device, where the access identifier is used to instruct the terminal device to access the target serving node.
  • an embodiment of the present disclosure provides an MEC-based service node allocation device, which is applied to an MEC server, and the device includes:
  • the third receiving module is configured to receive a query request sent by a cloud server; wherein the query request includes identification information of the terminal device;
  • the first query module is configured to query and obtain network index information of at least one service node managed and controlled by the MEC server based on the query request; wherein, the network index information of each service node includes the identification information corresponding Network performance measurement information from the terminal device to the service node;
  • the second sending module is configured to send the network index information of the at least one service node to a cloud server; wherein the network index information of the at least one service node is used to instruct the cloud server to select a target service for the terminal device node.
  • embodiments of the present disclosure provide an MEC-based service node allocation device, which is applied to a mobile edge computing MEC server, and the device includes:
  • the obtaining module is used to obtain the query request sent by the terminal device; wherein the query request includes the identification information of the terminal device and the identification information of the target service application;
  • the second query module is configured to query, based on the query request, the MEC server based on the network index information of at least one service node controlled by the service application corresponding to the identification information of the target service application; wherein, each of the service nodes
  • the network index information includes network performance measurement information from the terminal device corresponding to the identification information to the service node;
  • the second selection module is configured to select a target service node for the terminal device based on the network index information of the at least one service node; wherein, the target service node is a service node in the at least one service node;
  • the third sending module is configured to send the access identifier of the target serving node to the terminal device, where the access identifier is used to instruct the terminal device to access the target serving node.
  • an embodiment of the present disclosure provides a cloud server, including a first processor, a first memory, a computer program stored on the first memory and capable of running on the first processor, and the computer When the program is executed by the first processor, the steps of the MEC-based service node allocation method on the cloud server side are implemented.
  • an embodiment of the present disclosure provides an MEC server, including a second processor, a second memory, a computer program stored in the second memory and capable of running on the second processor, the computer When the program is executed by the second processor, the steps of the above-mentioned MEC-based service node allocation method on the MEC server side are implemented.
  • embodiments of the present disclosure provide a computer-readable storage medium having a computer program stored on the computer-readable storage medium, and when the computer program is executed by a first processor, the above-mentioned cloud server-side MEC-based service is implemented The steps of the node allocation method, or the steps of the MEC-based service node allocation method on the MEC server side when executed by the second processor.
  • the MEC-based service node distribution method, device, cloud server, MEC server, and computer-readable storage medium provided by the embodiments of the present disclosure.
  • the cloud server according to the login request sent by the terminal device Query the MEC server for the network index information of each service node based on the application managed and controlled by the MEC server; wherein the network index information includes the network performance measurement information from the terminal device to the service node corresponding to the identification information in the login request; , Select a target service node for the terminal device based on the network index information provided by the MEC server; finally, send the access identifier of the target service node to the terminal device, so as to realize service drainage for the terminal device application.
  • the cloud server when logging in to the cloud server through the terminal device application, allocates service nodes to the terminal device according to the network index information provided by the MEC server to complete service drainage.
  • terminal application support is not required.
  • DNS domain name access is also suitable for terminal devices that do not support DNS domain name access in IoT scenarios.
  • it does not need to rely on DNS update speed.
  • the embodiments of the present disclosure can improve the flexibility of service drainage, at the same time, it is simple to implement, fast switching speed, and terminal device applications can autonomously initiate drainage updates at any time, and quickly respond to the needs of the terminal device.
  • FIG. 1 is one of the schematic flowcharts of the MEC-based service node allocation method provided by an embodiment of the present disclosure
  • Fig. 2 is a second schematic flowchart of the MEC-based service node allocation method provided by an embodiment of the present disclosure
  • FIG. 3 is a schematic structural diagram of a service drainage system applied by an MEC-based service node allocation method provided by an embodiment of the present disclosure
  • FIG. 4 is a sequence diagram of a MEC-based service node allocation method provided by an embodiment of the present disclosure
  • FIG. 5 is the third schematic flowchart of the MEC-based service node allocation method provided by an embodiment of the present disclosure
  • FIG. 6 is one of the structural schematic diagrams of the MEC-based service node allocation apparatus provided by an embodiment of the present disclosure.
  • FIG. 7 is the second structural diagram of the MEC-based service node allocation apparatus provided by an embodiment of the present disclosure.
  • FIG. 8 is the third structural diagram of the MEC-based service node allocation apparatus provided by an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a cloud server provided by an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of an MEC server provided by an embodiment of the present disclosure.
  • This service drainage method has the following problems:
  • Terminal device applications are required to support DNS domain name access, and some terminal devices in the IoT scenario may not support DNS domain name access due to limited capabilities;
  • the switching speed is restricted by the DNS update speed, and will reach a switching delay of more than a minute, and some scenarios may cause business failure;
  • the dynamic routing method is rarely used, and the service diversion method has the following problems:
  • the embodiments of the present disclosure propose a new MEC-based service node allocation solution.
  • the technical solutions in the embodiments of the present disclosure will be described clearly and completely in conjunction with the drawings in the embodiments of the present disclosure. Obviously, The described embodiments are part of the embodiments of the present disclosure, but not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of the present disclosure.
  • the MEC-based service node allocation method provided in the embodiments of the present disclosure can be applied to a service drainage system, which is used to allocate terminal equipment under the scheduling of the cloud server according to the network index information provided by the MEC server
  • the application of the system is diverted to the service node for processing, so as to save the traffic of the business interaction between the terminal device and the cloud server, reduce the delay of business interaction, and reduce the business pressure of the cloud server.
  • the service drainage system includes a cloud server, an MEC server, a terminal device, and at least one service node.
  • the service node is a logical application server, which can be called an edge access application server, which is used to access cloud server distribution Terminal equipment application, to achieve the purpose of service drainage.
  • the figure shows one of the schematic flowcharts of the MEC-based service node allocation method provided by an embodiment of the present disclosure.
  • the method may include the following steps:
  • Step 101 Receive a login request sent by a terminal device; wherein the login request includes identification information of the terminal device.
  • the terminal device application can initiate a login request to the cloud server in order to implement service processing.
  • the login request carries identification information of the terminal device; accordingly, the cloud server receives the login request sent by the terminal device.
  • the identification information may only include network identification, such as the IP address or port number of the terminal device, and the identification information may also include only the device identification, such as International Mobile Subscriber Identity (IMSI) or A unique identification ID (Identification, ID), the identification information may also include a network identification and a device identification at the same time, which is not specifically limited here.
  • network identification such as the IP address or port number of the terminal device
  • ID unique identification ID
  • the identification information may also include a network identification and a device identification at the same time, which is not specifically limited here.
  • the terminal device application may be any application on the terminal device, for example, the terminal device application may be an Alipay application, a WeChat application, and the like.
  • Step 102 Receive network index information of at least one service node controlled by the MEC server that is fed back by the mobile edge computing MEC server based on the query request; wherein, the query request includes the identification information, and the network index of each service node The information includes network performance measurement information from the terminal device to the service node corresponding to the identification information.
  • the cloud server After the cloud server obtains the login request, it triggers a query request and sends the query request to the MEC server, where the query request carries identification information of the terminal device and application identification information of the cloud server.
  • the MEC server receives the query request, and based on the query request, queries and obtains network index information of at least one service node controlled by the MEC server, wherein the network index information of each service node includes all The network performance measurement information from the terminal device to the service node corresponding to the identification information.
  • the network index information of the service node includes at least the network performance measurement information from the terminal device corresponding to the identification information to the service node.
  • the network index information of the service node may also include the information of the edge data center where the service node is located. Load information.
  • the network performance measurement information may include information such as the network delay and network distance from the terminal device to the service node, and the load information may include information such as the operating delay and service status of the service node itself.
  • the MEC server may query the network performance measurement information from the terminal device corresponding to the identification information to the service nodes of the application corresponding to the application identification information based on the identification information and the application identification information, and at the same time, it may further Obtain the load information of the edge data center where each service node is located.
  • the load information of the edge data center where the service node is located can be reported to the MEC server by the service node in real time or at intervals. Accordingly, the MEC server can obtain the load information.
  • the MEC server may feed back network indicator information of at least one serving node according to the query request.
  • the query request may also include feedback strategy information.
  • the feedback strategy information may instruct the MEC server to feed back the network index information of all service nodes that can be queried, and the feedback strategy information may also indicate the MEC server feedback part. Network indicator information of the service node.
  • the feedback strategy information may include the first network indicator threshold, and accordingly, the MEC server only needs to feed back the network indicator information of the service node whose network indicator information meets the first network indicator threshold.
  • the first network indicator threshold may only include the first threshold. Accordingly, the MEC server only needs to feed back the network indicator information of the service node whose network performance measurement information in the network indicator information meets the first threshold.
  • the first network indicator threshold may include both the first threshold and the second threshold. The MEC server only needs to feed back the service node whose network performance measurement information in the network indicator information meets the first threshold and the load information in the network indicator information meets the second threshold. The network indicator information is sufficient.
  • the second method is: the MEC server can comprehensively consider the network performance measurement information and load information of each service node, rank each service node, and feed back the network index information of the top N service nodes, where N is greater than or equal to Positive integer.
  • the MEC can set the weights of network performance measurement information and load information, determine the quality of the network of each service node based on the weighting method, and arrange the service nodes according to the quality of the network to determine the best service of the network The nodes are ranked first, and at the same time, the worst service node on the network is ranked last.
  • the MEC server After the MEC server obtains the network index information of at least one service node, it feeds back the network index information of the at least one service node to the cloud server. Accordingly, the cloud server can receive the network index information of the at least one service node. Network indicator information.
  • Step 103 Select a target service node for the terminal device based on the network index information of the at least one service node; wherein, the target service node is a service node in the at least one service node.
  • a target service node may be selected for the terminal device based on the network index information of the at least one service node according to a traffic diversion strategy preset by the cloud server.
  • the diversion strategy is relatively flexible and supports user granular application-level strategy diversion.
  • the first diversion strategy may be: selecting a target service node for the terminal device only according to the network index information of the service node.
  • the step of selecting a target service node for the terminal device based on the network index information of the at least one service node includes:
  • the service node with the best network index information among the at least one service node is determined as the target service node accessed by the terminal device.
  • the cloud server may set the network performance measurement index and the weight of the load information, determine the quality of the network of each service node in the at least one service node based on a weighted method, and select the network index in the at least one service node
  • the service node with the best information, and at the same time, the service node with the best network index information among the at least one service node is determined as the target service node accessed by the terminal device.
  • the second diversion strategy may be: selecting a target service node for the terminal device according to the network index information of the service node and the level of the terminal device.
  • the step of selecting a target service node for the terminal device based on the network index information of the at least one service node includes:
  • the service node matching the level of the terminal device is determined as the target service node accessed by the terminal device.
  • the level of the terminal device is used to reflect the degree of importance of the terminal device for application processing, and may be an important level, a normal level, or other levels such as a super important level, which is not specifically limited here.
  • the terminal equipment of the important level has a greater processing urgency than the terminal equipment of the general level, and requires priority processing or rapid response processing.
  • the cloud server may determine the level of the terminal device according to the identification information of the terminal device. For example, the cloud server may pre-store the identification information of the terminal device and a mapping table of the level, and based on the identification information, The level of the terminal device can be queried in the mapping table.
  • the cloud server may set the network performance measurement index and the weight of the load information, and determine the quality of the network of each service node in the at least one service node based on a weighted method, and may be based on the quality of the network of each service node, Sort the service nodes. Based on the sorted service nodes, the service node corresponding to the level of the terminal device is matched.
  • the service node corresponding to the level of the terminal device may include only one or multiple service nodes, which is not specifically limited here.
  • the sorted service nodes include service node 1, service node 2, service node 3, and service node 4.
  • service node 1 and service node 2 with better network index information can meet the requirements of the terminal device. That is to say, the service node 1 and service node 2 match the terminal device; for the terminal device of the general level, because its performance requirements for application processing are not very high, the service node 3 and service node with general network index information 4 can meet the requirements of the terminal device, that is, the service node 3 and the service node 4 match the terminal device.
  • the cloud server may determine any one of the multiple service nodes corresponding to the level of the terminal device as the at least one service node
  • the service node whose network index information matches the level of the terminal device may also determine the service node with the best network index information among the plurality of service nodes corresponding to the level of the terminal device as the network of the at least one service node.
  • the service node whose index information matches the level of the terminal device is not specifically limited here.
  • the cloud server may also determine multiple service nodes corresponding to the level of the terminal device as the target service node accessed by the terminal device, and accordingly, send all the access identifiers of each target service node For the terminal device, let the terminal device access the target service node based on any one of the access identifiers of the target service node.
  • the third diversion strategy may be: selecting a target service node for the terminal device according to the network index information of the service node and the characteristic information of the terminal device.
  • the step of selecting a target service node for the terminal device based on the network index information of the at least one service node includes:
  • the service node matching the characteristic information is determined as the target service node accessed by the terminal device.
  • the cloud server may count the historical setting data of the terminal device to determine the characteristic information of the terminal device, and the characteristic information is used to reflect the performance requirements of the terminal device on the network.
  • the terminal device for a video playback application, the terminal device’s preference setting for video resolution is 1080P, and the cloud server counts the historical setting data of the terminal device for the video playback application, and determines that the terminal device is
  • the preference setting of the playback application the preference setting is the characteristic information of the terminal device for the video playback application
  • the characteristic information may include the preference setting of video definition 1080P, that is, the cloud server is based on the clearness of the video in the characteristic information.
  • the preference setting of the degree of 1080P can determine that the terminal device has higher requirements for network performance.
  • the cloud server may determine a second network index threshold value based on the characteristic information, and when the network index information of a service node in the at least one service node is greater than the second network index threshold value, the network index is determined
  • the index information matches the characteristic information, and accordingly, the service node corresponding to the network index information that matches the characteristic information is determined as the target service node.
  • Step 104 Send the access identifier of the target service node to the terminal device, where the access identifier is used to instruct the terminal device to access the target service node.
  • the cloud server After determining the target service node, the cloud server sends the access identifier of the target service node to the terminal device, where the access identifier may be the IP address of the target service node.
  • the terminal device may receive the access identifier of the target service node, and based on the access identifier, access the target service node to perform a business session, thereby realizing processing of terminal device applications.
  • the cloud server can also provide the log-in information return information to the application of the terminal device.
  • the log-in information return information includes an encryption key.
  • the terminal device receives the return information.
  • the cloud server in order to achieve the target service node pairing For processing application services of a terminal device, the cloud server also needs to send service processing information associated with the terminal device to the target service node, where the service processing information includes the login information of the terminal device application and The return information of the login information is used to synchronize the login information of the terminal device, and at the same time, the service processing information also includes information required by the application service of the terminal device.
  • the cloud server allocates service nodes to the terminal device according to the network index information provided by the MEC server to complete the service drainage, which is relative to the DNS analysis and drainage method , Does not require terminal applications to support DNS domain name access, and is also suitable for terminal devices that do not support DNS domain name access in IoT scenarios. At the same time, it does not need to rely on DNS update speed. Compared with the dynamic routing method, it does not need to rely on network routing equipment, is not restricted by the application scenario, and can support multiple active server scenarios.
  • the embodiments of the present disclosure can improve the flexibility of service drainage, at the same time, it is simple to implement, fast switching speed, and terminal device applications can autonomously initiate drainage updates at any time, and quickly respond to the needs of the terminal device.
  • its drainage strategy is more flexible and supports user granular application-level strategy drainage.
  • FIG. 2 shows the second schematic flowchart of the MEC-based service node allocation method provided by an embodiment of the present disclosure.
  • the method may include the following steps:
  • Step 201 Receive a query request sent by a cloud server; wherein the query request includes identification information of the terminal device;
  • Step 202 Based on the query request, query and obtain network index information of at least one service node managed and controlled by the MEC server; wherein, the network index information of each service node includes the terminal device corresponding to the identification information. Network performance measurement information of the service node;
  • Step 203 Send the network index information of the at least one service node to a cloud server; wherein the network index information of the at least one service node is used to instruct the cloud server to select a target service node for the terminal device.
  • the network index information of the at least one service node includes network index information of the service node whose network index information meets a preset threshold; or,
  • the network index information of the at least one service node includes network index information of the first N service nodes among the service nodes ranked according to the network index information; wherein, the N is a positive integer greater than or equal to 1.
  • the foregoing preset threshold is the first network indicator threshold described in the first embodiment.
  • the above-mentioned specific control process is similar to the first embodiment, and will not be repeated here.
  • the cloud server allocates service nodes to the terminal device according to the network index information provided by the MEC server to complete service drainage.
  • the terminal application does not need to support DNS domain names.
  • Access is also suitable for terminal devices that do not support DNS domain name access in IoT scenarios, and at the same time, it does not need to rely on DNS update speed.
  • the embodiments of the present disclosure can improve the flexibility of service drainage, at the same time, it is simple to implement, fast switching speed, and terminal device applications can autonomously initiate drainage updates at any time, and quickly respond to the needs of terminal devices.
  • FIG. 3 shows a schematic structural diagram of a service drainage system applied by the MEC-based service node allocation method provided by an embodiment of the present disclosure.
  • the service drainage system includes: terminal equipment, cloud server , MEC server and edge access application server.
  • Fig. 4 the figure shows a sequence diagram of the MEC-based service node allocation method provided by an embodiment of the present disclosure. As shown in Fig. 4, it is applied to a service drainage system, and the specific process of the method is as follows:
  • the terminal device sends a login request to the cloud server; wherein the login request includes identification information of the terminal device, and the identification information may include a network identification and/or a device identification;
  • the cloud server initiates a query request to the MEC server according to the identification information; wherein the query request includes identification information of the terminal device and application identification information;
  • the MEC server queries and obtains the network index information of at least one edge access application server based on the identification information, and sends the network index information of the at least one edge access application server to the cloud server;
  • the cloud server receives the network index information of the at least one edge access application server, and based on the network index information of the at least one edge access application server, selects a target for the terminal device according to a preset drainage strategy Edge access application server;
  • the terminal device receives the access identifier of the target edge access application server, and accesses the target edge access application server to perform a service session based on the access identifier.
  • the above embodiments describe in detail the implementation process of the terminal device logging into the cloud server, and the cloud server uses the MEC server to allocate the target service node to the terminal device. It should be noted that the following embodiment will introduce the terminal device logging into the MEC server in detail, and the MEC server The realization process of directly assigning the target service node to the terminal device.
  • FIG. 5 shows the third schematic flowchart of the MEC-based service node allocation method provided by an embodiment of the present disclosure.
  • the method may include the following steps:
  • Step 501 Obtain a query request sent by a terminal device; wherein the query request includes identification information of the terminal device and identification information of a target service application;
  • Step 502 Based on the query request, query the MEC server based on the network index information of at least one service node controlled by the service application corresponding to the identification information of the target service application; wherein, the network index information of each service node Includes the network performance measurement information from the terminal device to the service node corresponding to the identification information;
  • Step 503 Select a target service node for the terminal device based on the network index information of the at least one service node; wherein, the target service node is a service node in the at least one service node;
  • Step 504 Send the access identifier of the target serving node to the terminal device, where the access identifier is used to instruct the terminal device to access the target serving node.
  • the terminal device application can initiate a query request to the MEC server to implement service processing.
  • the query request carries the identification information of the terminal device and the identification information of the target service application; correspondingly, the MEC
  • the server receives the query request sent by the terminal device.
  • the identification information of the terminal device may only include network identification, such as the IP address or port number of the terminal device, and the identification information of the terminal device may also include only the device identification, such as the International Mobile Subscriber Identity Code (International Mobile Subscriber Identity). Subscriber Identity, IMSI) or unique identification ID (Identification, ID), the identification information of the terminal device may also include both a network identification and a device identification, which is not specifically limited here.
  • network identification such as the IP address or port number of the terminal device
  • the identification information of the terminal device may also include only the device identification, such as the International Mobile Subscriber Identity Code (International Mobile Subscriber Identity). Subscriber Identity, IMSI) or unique identification ID (Identification, ID)
  • ID unique identification ID
  • the identification information of the target service application may be used to instruct the MEC server to query the network index information of the designated service node under its control.
  • the target service application may be any application on the terminal device.
  • the target service application may be Alipay application, WeChat application, etc.
  • step 502 the implementation process of the MEC server querying the network index information of at least one service node managed and controlled by the MEC server is similar to the foregoing embodiment, and the specific implementation process will not be repeated. Only the triggering condition for triggering the MEC server to query is different.
  • the triggering condition for triggering the MEC server to query in the above embodiment is the query request sent by the cloud server, while the triggering condition for triggering the MEC server to query for this embodiment is the terminal The query request sent by the device.
  • step 503 and step 504 the implementation process is similar to the implementation process of the foregoing embodiment, and the specific implementation process is not repeated here. Only the execution subject is different.
  • the foregoing embodiment is implemented by the processor of the cloud server, while this embodiment is implemented by the processor of the MEC server.
  • the MEC server queries network index information based on the query request sent by the terminal device, and allocates service nodes to the terminal device according to the network index information to complete service drainage.
  • no terminal application is required. It supports DNS domain name access, and is also suitable for terminal devices that do not support DNS domain name access in IoT scenarios. At the same time, it does not need to rely on DNS update speed.
  • the embodiments of the present disclosure can improve the flexibility of service drainage, at the same time, it is simple to implement, fast switching speed, and terminal device applications can autonomously initiate drainage updates at any time, and quickly respond to the needs of the terminal device.
  • the step of selecting a target service node for the terminal device based on the network index information of the at least one service node includes:
  • the service node with the best network index information among the at least one service node is determined as the target service node accessed by the terminal device.
  • the step of selecting a target service node for the terminal device based on the network index information of the at least one service node includes:
  • the service node matching the level of the terminal device is determined as the target service node accessed by the terminal device.
  • the step of selecting a target service node for the terminal device based on the network index information of the at least one service node includes:
  • the service node matching the characteristic information is determined as the target service node accessed by the terminal device.
  • the MEC server selects the target service node drainage strategy for the terminal device can be preset, and can be set to be consistent with the cloud server. Therefore, its specific selection
  • the process of the target service node is similar to the foregoing embodiment, and will not be repeated here.
  • the method further includes:
  • the MEC server sends the access identifier of the target service node to the cloud server, so that the cloud server can send the service processing information associated with the terminal device to the target service node, where the service
  • the processing information includes the login information of the terminal device application and the return information of the login information to synchronize the login information of the terminal device.
  • the service processing information also includes the information required by the application service of the terminal device.
  • the MEC-based service node allocating device provided by the embodiment of the present disclosure will be described below.
  • the figure shows one of the schematic structural diagrams of the MEC-based service node allocation apparatus provided by an embodiment of the present disclosure.
  • the MEC-based service node allocating device 600 includes:
  • the first receiving module 601 is configured to receive a login request sent by a terminal device; wherein the login request includes identification information of the terminal device;
  • the second receiving module 602 is configured to receive network index information of at least one service node controlled by the MEC server that is fed back by the mobile edge computing MEC server based on a query request; wherein, the query request includes the identification information, and each of the The network index information of the service node includes network performance measurement information from the terminal device corresponding to the identification information to the service node;
  • the first selection module 603 is configured to select a target service node for the terminal device based on the network index information of the at least one service node; wherein, the target service node is a service node of the at least one service node;
  • the first sending module 604 is configured to send the access identifier of the target serving node to the terminal device, where the access identifier is used to instruct the terminal device to access the target serving node.
  • the first selection module 603 includes:
  • the first determining unit is configured to determine the service node with the best network index information among the at least one service node;
  • the second determining unit is configured to determine the service node with the best network index information among the at least one service node as the target service node accessed by the terminal device.
  • the first selection module 603 includes:
  • An obtaining unit configured to obtain the level of the terminal device; wherein the level is used to reflect the importance of the terminal device for application processing;
  • a third determining unit configured to determine a service node in the at least one service node whose network index information matches the level of the terminal device
  • the fourth determining unit is configured to determine a service node matching the level of the terminal device as the target service node accessed by the terminal device.
  • the first selection module 603 includes:
  • the fifth determining unit is configured to determine the characteristic information of the terminal device based on the historical setting data of the terminal device; wherein the characteristic information is used to reflect the performance requirements of the terminal device on the network;
  • a sixth determining unit configured to determine a service node whose network index information matches the characteristic information among the at least one service node
  • the seventh determining unit is configured to determine the service node matching the characteristic information as the target service node accessed by the terminal device.
  • the device further includes:
  • the fourth sending module is configured to send the service processing information associated with the terminal device to the target service node.
  • the MEC-based service node allocating device provided in the embodiments of the present disclosure can implement the various processes implemented in the foregoing cloud server-side method embodiments. To avoid repetition, details are not described herein again.
  • the figure shows the second structural diagram of the MEC-based service node allocating device provided by an embodiment of the present disclosure.
  • the MEC-based service node allocating device 700 includes:
  • the third receiving module 701 is configured to receive a query request sent by a cloud server; wherein the query request includes identification information of the terminal device;
  • the first query module 702 is configured to query and obtain network indicator information of at least one service node controlled by the MEC server based on the query request; wherein, the network indicator information of each service node includes the identification information Network performance measurement information from the corresponding terminal device to the service node;
  • the second sending module 703 is configured to send the network index information of the at least one service node to a cloud server; wherein the network index information of the at least one service node is used to instruct the cloud server to select a target for the terminal device Service node.
  • the network index information of the at least one service node includes network index information of the service node whose network index information meets a preset threshold; or,
  • the network index information of the at least one service node includes network index information of the first N service nodes among the service nodes ranked according to the network index information; wherein, the N is a positive integer greater than or equal to 1.
  • the MEC-based service node allocating device provided in the embodiment of the present disclosure can implement the various processes implemented in the above-mentioned MEC server-side method embodiment, and in order to avoid repetition, details are not described herein again.
  • the cloud server allocates service nodes to the terminal device according to the network index information provided by the MEC server to complete the service drainage, which is compared with the DNS analysis and drainage method , Does not require terminal applications to support DNS domain name access, and is also suitable for terminal devices that do not support DNS domain name access in IoT scenarios. At the same time, it does not need to rely on DNS update speed. Compared with the dynamic routing method, it does not need to rely on network routing equipment, is not restricted by the application scenario, and can support multiple active server scenarios.
  • the embodiments of the present disclosure can improve the flexibility of service drainage, at the same time, it is simple to implement, fast switching speed, and terminal device applications can autonomously initiate drainage updates at any time, and quickly respond to the needs of the terminal device.
  • its drainage strategy is more flexible and supports user granular application-level strategy drainage.
  • the figure shows the third structural schematic diagram of the MEC-based service node allocation apparatus provided by an embodiment of the present disclosure.
  • the MEC-based service node allocating device 800 includes:
  • the obtaining module 801 is configured to obtain a query request sent by a terminal device; wherein the query request includes the identification information of the terminal device and the identification information of the target service application;
  • the second query module 802 is configured to query the MEC server based on the network index information of at least one service node controlled by the service application corresponding to the identification information of the target service application based on the query request; wherein, each of the services The network index information of the node includes network performance measurement information from the terminal device corresponding to the identification information to the service node;
  • the second selection module 803 is configured to select a target service node for the terminal device based on the network index information of the at least one service node; wherein, the target service node is a service node in the at least one service node;
  • the third sending module 804 is configured to send the access identifier of the target serving node to the terminal device, where the access identifier is used to instruct the terminal device to access the target serving node.
  • the second selection module 803 is specifically configured to determine the service node with the best network index information among the at least one service node; and determine the service node with the best network index information among the at least one service node as The target service node accessed by the terminal device.
  • the second selection module 803 is specifically configured to obtain the level of the terminal device; wherein, the level is used to reflect the importance of the terminal device for application processing; and determine whether the at least one service node is The service node whose network index information matches the level of the terminal device; and the service node that matches the level of the terminal device is determined as the target service node accessed by the terminal device.
  • the second selection module 803 is specifically configured to determine characteristic information of the terminal device based on historical setting data of the terminal device; wherein, the characteristic information is used to reflect the terminal device’s network Performance requirements; determine the service node whose network index information matches the characteristic information in the at least one service node; determine the service node that matches the characteristic information as the target service node accessed by the terminal device.
  • the device further includes:
  • the fifth sending module is used to send the access identifier of the target service node to the cloud server.
  • the cloud server 900 includes: a first processor 901, a first memory 902, a first user interface 903, and a first bus interface 904.
  • the first processor 901 is configured to read a program in the first memory 902, and execute the following process:
  • the network index information of at least one service node controlled by the MEC server that is fed back by the mobile edge computing MEC server based on a query request; wherein the query request includes the identification information, and the network index information of each service node includes Network performance measurement information from the terminal device to the service node corresponding to the identification information;
  • Target service node for the terminal device based on the network index information of the at least one service node; wherein, the target service node is a service node in the at least one service node;
  • the access identifier of the target serving node is sent to the terminal device, where the access identifier is used to instruct the terminal device to access the target serving node.
  • the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the first processor 901 and various circuits of the memory represented by the first memory 902 are linked together.
  • the bus architecture can also link various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, will not be further described herein.
  • the first bus interface 904 provides an interface.
  • the first user interface 903 may also be an interface capable of externally connecting internally required equipment, and the connected equipment includes but not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.
  • the first processor 901 is responsible for managing the bus architecture and general processing, and the first memory 902 can store data used by the first processor 901 when performing operations.
  • the first processor 901 is specifically configured to:
  • the service node with the best network index information among the at least one service node is determined as the target service node accessed by the terminal device.
  • the first processor 901 is specifically configured to:
  • the service node matching the level of the terminal device is determined as the target service node accessed by the terminal device.
  • the first processor 901 is specifically configured to:
  • the service node matching the characteristic information is determined as the target service node accessed by the terminal device.
  • the first processor 901 is also used for:
  • the embodiment of the present disclosure further provides a cloud server, including a first processor 901, a first memory 902, a computer program stored on the first memory 902 and running on the first processor 901,
  • a cloud server including a first processor 901, a first memory 902, a computer program stored on the first memory 902 and running on the first processor 901,
  • the computer program is executed by the first processor 901
  • each process of the above-mentioned MEC-based service node allocation method embodiment on the cloud server side is realized, and the same technical effect can be achieved. To avoid repetition, details are not repeated here.
  • the MEC server 1000 includes: a second processor 1001, a second memory 1002, a second user interface 1003, and a second bus interface 1004.
  • the second processor 1001 is configured to read a program in the second memory 1002 and execute the following process:
  • the network index information of each service node includes the terminal device corresponding to the identification information to the service Network performance measurement information of the node;
  • the network index information of the at least one service node is sent to a cloud server; wherein the network index information of the at least one service node is used to instruct the cloud server to select a target service node for the terminal device.
  • the second processor 1001 is configured to read the program in the second memory 1002, and also executes the following process:
  • the query request includes the identification information of the terminal device and the identification information of the target service application;
  • the MEC server Based on the query request, query the MEC server based on the network index information of at least one service node controlled by the service application corresponding to the identification information of the target service application; wherein, the network index information of each service node includes all Network performance measurement information from the terminal device to the service node corresponding to the identification information;
  • Target service node for the terminal device based on the network index information of the at least one service node; wherein, the target service node is a service node in the at least one service node;
  • the access identifier of the target serving node is sent to the terminal device, where the access identifier is used to instruct the terminal device to access the target serving node.
  • the second processor 1001 is specifically used for:
  • the service node with the best network index information among the at least one service node is determined as the target service node accessed by the terminal device.
  • the second processor 1001 is specifically used for:
  • the service node matching the level of the terminal device is determined as the target service node accessed by the terminal device.
  • the second processor 1001 is specifically used for:
  • the service node matching the characteristic information is determined as the target service node accessed by the terminal device.
  • the second processor 1001 is also used for:
  • the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the second processor 1001 and various circuits of the memory represented by the second memory 1002 are linked together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, will not be further described herein.
  • the second bus interface 1004 provides an interface. For different user equipment, the second user interface 1003 may also be an interface capable of connecting externally and internally with the required equipment.
  • the connected equipment includes but not limited to a keypad, a display, a speaker, a microphone, a joystick, and so on.
  • the second processor 1001 is responsible for managing the bus architecture and general processing, and the second memory 1002 can store data used by the second processor 1001 when performing operations.
  • the network index information of the at least one service node includes network index information of the service node whose network index information meets a preset threshold; or,
  • the network index information of the at least one service node includes network index information of the first N service nodes among the service nodes ranked according to the network index information; wherein, the N is a positive integer greater than or equal to 1.
  • an embodiment of the present disclosure further provides an MEC server, including a second processor 1001, a second memory 1002, and a computer program that is stored on the second memory 1002 and can run on the second processor 1001,
  • an MEC server including a second processor 1001, a second memory 1002, and a computer program that is stored on the second memory 1002 and can run on the second processor 1001
  • the computer program is executed by the second processor 1001
  • each process of the above-mentioned MEC server-side MEC-based service node allocation method embodiment is realized, and the same technical effect can be achieved. To avoid repetition, details are not repeated here.
  • the embodiments of the present disclosure also provide a computer-readable storage medium, and a computer program is stored on the computer-readable storage medium.
  • a computer program is executed by the first processor
  • the above-mentioned cloud server side MEC-based service node allocation method embodiment is implemented
  • Each process can achieve the same technical effect. In order to avoid repetition, it will not be repeated here.
  • the computer program is executed by the second processor
  • each process of the MEC-based service node allocation method embodiment on the MEC server side is implemented, And can achieve the same technical effect.
  • the computer readable storage medium such as read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk, or optical disk, etc.
  • the disclosed system and method may be implemented in other ways.
  • the system embodiment described above is only illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments of the present disclosure.
  • the functional units in the various embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present disclosure essentially or the part that contributes to the related technology or the part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including several
  • the instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present disclosure.
  • the aforementioned storage media include: U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk and other media that can store program codes.

Abstract

本公开提供一种基于MEC的服务节点分配方法、装置、云端服务器、MEC服务器以及计算机可读存储介质。该方法包括：接收终端设备发送的登录请求；接收移动边缘计算MEC服务器基于查询请求反馈的MEC服务器管控的至少一服务节点的网络指标信息；基于至少一服务节点的网络指标信息，为终端设备选择目标服务节点；将目标服务节点的访问标识发送给终端设备，访问标识用于指示终端设备接入目标服务节点。

Description

基于MEC的服务节点分配方法、装置及相关服务器
相关申请的交叉引用
本申请主张在2019年11月21日在中国提交的中国专利申请号No.201911147857.5的优先权，其全部内容通过引用包含于此。
技术领域
本公开实施例涉及边缘计算技术领域，尤其涉及一种基于移动边缘计算(Mobile Edge Computing，MEC)的服务节点分配方法、装置、云端服务器、MEC服务器以及计算机可读存储介质。
背景技术
随着网络技术、互联网以及物联网业务的发展，人们产生了在移动网络边缘数据中心进行服务部署提供业务服务的需求，以节省移动终端与业务服务器之间的业务交互流量，降低业务交互时延，减少业务服务器的业务压力。特别是在物联网的应用场景中，边缘服务部署的需求巨大，而在移动网络边缘数据中心的接入过程中，会存在边缘接入服务器分配(又称为服务引流)的问题，需要为接入的终端应用分配对应的边缘接入服务器。
目前，服务引流方式主要有两种，分别是域名系统(Domain Name System，DNS)解析引流方式和动态路由方式。对于DNS解析引流方式，利用应用请求的域名，通过DNS解析到需要为应用分配的边缘接入应用服务器，从而达到引流的目的；而对于动态路由方式，通过对服务器互联网协议(Internet Protocol，IP)进行动态路由，将应用请求路由到需要为应用分配的边缘接入应用服务器，从而达到引流的目的。
从上述可以看出，不管是DNS解析引流方式还是动态路由方式，都受限于应用场景，比如，对于DNS解析引流方式，需要终端应用支持DNS域名访问，而在物联网场景中由于部分终端能力受限，其可能并不支持DNS域名访问，对于动态路由方式，需要依赖网络路由设备，且一般用于支持主备服务器场景，因此，相关技术中服务引流方式存在灵活性较差的问题。
发明内容
本公开实施例提供一种基于MEC的服务节点分配方法、装置、云端服务器、MEC服务器以及计算机可读存储介质，以解决相关技术中服务引流方式存在灵活性较差的问题。
第一方面，本公开实施例提供一种基于MEC的服务节点分配方法，应用于云端服务器，所述方法包括：
接收终端设备发送的登录请求；其中，所述登录请求中包括所述终端设备的标识信息；
接收移动边缘计算MEC服务器基于查询请求反馈的所述MEC服务器管控的至少一服务节点的网络指标信息；其中，所述查询请求包括所述标识信息，每一所述服务节点的网络指标信息中包括所述标识信息对应的终端设备到所述服务节点的网络性能度量信息；
基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点；其中，所述目标服务节点为所述至少一服务节点中的服务节点；
将所述目标服务节点的访问标识发送给所述终端设备，所述访问标识用于指示所述终端设备接入所述目标服务节点。
第二方面，本公开实施例提供一种基于MEC的服务节点分配方法，应用于MEC服务器，所述方法包括：
接收云端服务器发送的查询请求；其中，所述查询请求包括终端设备的标识信息；
基于所述查询请求，查询并获得所述MEC服务器管控的至少一服务节点的网络指标信息；其中，每一所述服务节点的网络指标信息中包括所述标识信息对应的终端设备到所述服务节点的网络性能度量信息；
将所述至少一服务节点的网络指标信息发送给云端服务器；其中，所述至少一服务节点的网络指标信息用于指示所述云端服务器为所述终端设备选择目标服务节点。
第三方面，本公开实施例还提供一种基于MEC的服务节点分配方法，应用于移动边缘计算MEC服务器，所述方法包括：
获取终端设备发送的查询请求；其中，所述查询请求中包括所述终端设备的标识信息及目标服务应用的标识信息；
基于所述查询请求，查询所述MEC服务器基于所述目标服务应用的标识信息对应的服务应用管控的至少一服务节点的网络指标信息；其中，每一所述服务节点的网络指标信息中包括所述标识信息对应的终端设备到所述服务节点的网络性能度量信息；
基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点；其中，所述目标服务节点为所述至少一服务节点中的服务节点；
将所述目标服务节点的访问标识发送给所述终端设备，所述访问标识用于指示所述终端设备接入所述目标服务节点。
第四方面，本公开实施例提供一种基于MEC的服务节点分配装置，应用于云端服务器，所述装置包括：
第一接收模块，用于接收终端设备发送的登录请求；其中，所述登录请求中包括所述终端设备的标识信息；
第二接收模块，用于接收移动边缘计算MEC服务器基于查询请求反馈的所述MEC服务器管控的至少一服务节点的网络指标信息；其中，所述查询请求包括所述标识信息，每一所述服务节点的网络指标信息中包括所述标识信息对应的终端设备到所述服务节点的网络性能度量信息；
第一选择模块，用于基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点；其中，所述目标服务节点为所述至少一服务节点中的服务节点；
第一发送模块，用于将所述目标服务节点的访问标识发送给所述终端设备，所述访问标识用于指示所述终端设备接入所述目标服务节点。
第五方面，本公开实施例提供一种基于MEC的服务节点分配装置，应用于MEC服务器，所述装置包括：
第三接收模块，用于接收云端服务器发送的查询请求；其中，所述查询请求包括终端设备的标识信息；
第一查询模块，用于基于所述查询请求，查询并获得所述MEC服务器管控的至少一服务节点的网络指标信息；其中，每一所述服务节点的网络指标 信息中包括所述标识信息对应的终端设备到所述服务节点的网络性能度量信息；
第二发送模块，用于将所述至少一服务节点的网络指标信息发送给云端服务器；其中，所述至少一服务节点的网络指标信息用于指示所述云端服务器为所述终端设备选择目标服务节点。
第六方面，本公开实施例提供一种基于MEC的服务节点分配装置，应用于移动边缘计算MEC服务器，所述装置包括：
获取模块，用于获取终端设备发送的查询请求；其中，所述查询请求中包括所述终端设备的标识信息及目标服务应用的标识信息；
第二查询模块，用于基于所述查询请求，查询所述MEC服务器基于所述目标服务应用的标识信息对应的服务应用管控的至少一服务节点的网络指标信息；其中，每一所述服务节点的网络指标信息中包括所述标识信息对应的终端设备到所述服务节点的网络性能度量信息；
第二选择模块，用于基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点；其中，所述目标服务节点为所述至少一服务节点中的服务节点；
第三发送模块，用于将所述目标服务节点的访问标识发送给所述终端设备，所述访问标识用于指示所述终端设备接入所述目标服务节点。
第七方面，本公开实施例提供一种云端服务器，包括第一处理器，第一存储器，存储在所述第一存储器上并可在所述第一处理器上运行的计算机程序，所述计算机程序被所述第一处理器执行时实现上述云端服务器侧基于MEC的服务节点分配方法的步骤。
第八方面，本公开实施例提供一种MEC服务器，包括第二处理器，第二存储器，存储在所述第二存储器上并可在所述第二处理器上运行的计算机程序，所述计算机程序被所述第二处理器执行时实现上述MEC服务器侧基于MEC的服务节点分配方法的步骤。
第九方面，本公开实施例提供一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被第一处理器执行时实现上述云端服务器侧基于MEC的服务节点分配方法的步骤，或者被第二处理器 执行时实现上述MEC服务器侧基于MEC的服务节点分配方法的步骤。
本公开实施例提供的基于MEC的服务节点分配方法、装置、云端服务器、MEC服务器以及计算机可读存储介质，首先，在终端设备应用登录云端服务器的情况下，云端服务器根据终端设备发送的登录请求，向MEC服务器查询所述MEC服务器管控的基于该应用的各服务节点的网络指标信息；其中，网络指标信息包括所述登录请求中标识信息对应的终端设备到服务节点的网络性能度量信息；然后，基于所述MEC服务器提供的网络指标信息，为所述终端设备选择目标服务节点；最后，将所述目标服务节点的访问标识发送给所述终端设备，从而实现对终端设备应用的服务引流。
本公开实施例中，是通过终端设备应用在登录云端服务器时，云端服务器根据MEC服务器提供的网络指标信息为终端设备分配服务节点来完成服务引流，相对于DNS解析引流方式，不需要终端应用支持DNS域名访问，也适合物联网场景中不支持DNS域名访问的终端设备，同时，不需要依赖于DNS的更新速度。而相对于动态路由方式，不需要依赖网络路由设备，不受应用场景的限制，能支持多活的服务器场景。因此，本公开实施例能够提高服务引流的灵活性，同时，实现简单，切换速度快，且终端设备应用可随时自主发起引流更新，快速响应终端设备的需求。
附图说明
为了更清楚地说明本公开实施例的技术方案，下面将对本公开实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获取其他的附图。
图1是本公开实施例提供的基于MEC的服务节点分配方法的流程示意图之一；
图2是本公开实施例提供的基于MEC的服务节点分配方法的流程示意图之二；
图3是本公开实施例提供的基于MEC的服务节点分配方法应用的服务引流系统的结构示意图；
图4是本公开实施例提供的基于MEC的服务节点分配方法的时序图；
图5是本公开实施例提供的基于MEC的服务节点分配方法的流程示意图之三；
图6是本公开实施例提供的基于MEC的服务节点分配装置的结构示意图之一；
图7是本公开实施例提供的基于MEC的服务节点分配装置的结构示意图之二；
图8是本公开实施例提供的基于MEC的服务节点分配装置的结构示意图之三；
图9是本公开实施例提供的云端服务器的结构示意图；
图10是本公开实施例提供的MEC服务器的结构示意图。
具体实施方式
从背景技术可以看出，服务引流方式主要有两种，分别是DNS解析引流方式和动态路由方式。
目前，由于内容分发网络(Content Delivery Network，CDN)业务的成熟，DNS解析引流方式使用最为广泛，该服务引流方式存在以下问题：
1)需要终端设备应用支持DNS域名访问，而在物联网场景中部分终端设备由于能力受限，可能并不支持DNS域名访问；
2)切换速度受制于DNS的更新速度，会达到分钟级以上的切换时延，一些场景可能会引起业务失败；
3)主要是根据网络性能指标的负载引流，无法支持更丰富的应用级引流策略。
而动态路由方式采用较少，该服务引流方式存在以下问题：
1)需要参与网络路由计算，依赖网络路由设备；
2)复杂性高，一般用于支持主备服务器场景，很难支持多活的服务器场景，而在基于MEC的接入场景中，边缘接入应用服务器都是多活的。
基于此，本公开实施例提出一种新的基于MEC的服务节点分配方案，下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、 完整地描述，显然，所描述的实施例是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获取的所有其他实施例，都属于本公开保护的范围。
下面首先对本公开实施例提供的基于MEC的服务节点分配方法进行说明。
需要说明的是，本公开实施例提供的基于MEC的服务节点分配方法可以应用于服务引流系统，所述服务引流系统用于根据MEC服务器提供的网络指标信息，在云端服务器的调度下将终端设备的应用引流到服务节点去处理，以节省终端设备与云端服务器之间业务交互的流量，降低业务交互的时延，减少云端服务器的业务压力。
其中，所述服务引流系统包括云端服务器、MEC服务器、终端设备和至少一个服务节点，该服务节点为逻辑上的应用服务器，可以称之为边缘接入应用服务器，用于接入云端服务器分配的终端设备应用，达到服务引流的目的。
参见图1，图中示出了本公开实施例提供的基于MEC的服务节点分配方法的流程示意图之一。应用于云端服务器，如图1所示，该方法可以包括如下步骤：
步骤101，接收终端设备发送的登录请求；其中，所述登录请求中包括所述终端设备的标识信息。
终端设备应用为实现业务处理，终端设备应用可以向云端服务器发起登录请求，所述登录请求中携带有终端设备的标识信息；相应的，所述云端服务器接收所述终端设备发送的登录请求。
其中，所述标识信息可以仅包括网络标识，如所述终端设备的IP地址或端口号，所述标识信息也可以仅包括设备标识，如国际移动用户识别码(International Mobile Subscriber Identity，IMSI)或唯一身份标识ID(Identification，ID)，所述标识信息也可以同时包括网络标识和设备标识，这里不做具体限定。
另外，所述终端设备应用可以为终端设备上的任何应用，比如，所述终端设备应用可以为支付宝应用、微信应用等。
步骤102，接收移动边缘计算MEC服务器基于查询请求反馈的所述MEC服务器管控的至少一服务节点的网络指标信息；其中，所述查询请求包括所述标识信息，每一所述服务节点的网络指标信息中包括所述标识信息对应的终端设备到所述服务节点的网络性能度量信息。
所述云端服务器获取登录请求之后，触发查询请求，并将查询请求发送给MEC服务器，其中，所述查询请求中携带有终端设备的标识信息和所述云端服务器的应用标识信息。
所述MEC服务器接收所述查询请求，并基于所述查询请求，查询并获得所述MEC服务器管控的至少一服务节点的网络指标信息，其中，每一所述服务节点的网络指标信息中包括所述标识信息对应的终端设备到所述服务节点的网络性能度量信息。
这里，服务节点的网络指标信息中至少包括所述标识信息对应的终端设备到所述服务节点的网络性能度量信息，同时，服务节点的网络指标信息还可以包括所述服务节点所在边缘数据中心的负载信息。
其中，网络性能度量信息可以包括终端设备到服务节点的网络延迟和网络距离等信息，负载信息可以包括服务节点本身的工作时延和业务状态等信息。
具体的，所述MEC服务器可以基于所述标识信息和应用标识信息，查询所述标识信息对应的终端设备到所述应用标识信息对应的应用各服务节点的网络性能度量信息，同时，还可以进一步获取各服务节点所在边缘数据中心的负载信息。其中，服务节点所在边缘数据中心的负载信息可以由服务节点实时或者间隔时间周期上报至MEC服务器，相应的，MEC服务器即可获取所述负载信息。
所述MEC服务器可以根据所述查询请求，反馈至少一服务节点的网络指标信息。比如，所述查询请求中还可以包括反馈策略信息，比如，所述反馈策略信息可以指示MEC服务器反馈能查询到的所有服务节点的网络指标信息，所述反馈策略信息也可以指示MEC服务器反馈部分服务节点的网络指标信息。
进一步的，根据反馈策略信息有两种方式反馈部分服务节点的网络指标 信息。
第一种方式为：所述反馈策略信息中可以包括第一网络指标阈值，相应的，MEC服务器只需要反馈网络指标信息满足所述第一网络指标阈值的服务节点的网络指标信息即可。所述第一网络指标阈值可以仅包括第一阈值，相应的，MEC服务器只需要反馈网络指标信息中网络性能度量信息满足第一阈值的服务节点的网络指标信息即可。所述第一网络指标阈值可以同时包括第一阈值和第二阈值，MEC服务器只需要反馈网络指标信息中网络性能度量信息满足第一阈值、且网络指标信息中负载信息满足第二阈值的服务节点的网络指标信息即可。
第二种方式为：MEC服务器可以综合考虑各服务节点的网络性能度量信息和负载信息，对各服务节点进行排名，反馈排名前N个服务节点的网络指标信息，所述N为大于或等于的正整数。比如，所述MEC可以设置网络性能度量信息和负载信息的权值，基于加权的方式确定各服务节点的网络的好坏，按照网络的好坏对各服务节点进行排列，将网络最好的服务节点排列在第一名，同时，将网络最坏的服务节点排列在最后一名。
MEC服务器获取到至少一服务节点的网络指标信息之后，将所述至少一服务节点的网络指标信息反馈给所述云端服务器，相应的，所述云端服务器即可接收到所述至少一服务节点的网络指标信息。
步骤103，基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点；其中，所述目标服务节点为所述至少一服务节点中的服务节点。
这里，可以根据云端服务器预先设置的引流策略，基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点。
所述云端服务器预先设置的引流策略可以有三种，其引流策略比较灵活，支持用户颗粒度的应用级策略引流。
第一种引流策略可以为：仅根据服务节点的网络指标信息，为所述终端设备选择目标服务节点。
具体的，所述基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点的步骤包括：
确定所述至少一服务节点中网络指标信息最好的服务节点；
将所述至少一服务节点中网络指标信息最好的服务节点确定为所述终端设备接入的目标服务节点。
所述云端服务器可以设置网络性能度量指标和负载信息的权值，基于加权的方式确定所述至少一服务节点中各服务节点的网络的好坏，并挑选出所述至少一服务节点中网络指标信息最好的服务节点，同时，将所述至少一服务节点中网络指标信息最好的服务节点确定为所述终端设备接入的目标服务节点。
第二种引流策略可以为：根据服务节点的网络指标信息和终端设备的等级，为所述终端设备选择目标服务节点。
具体的，所述基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点的步骤包括：
获取所述终端设备的等级；其中，所述等级用于反映所述终端设备对于应用处理的重要程度；
确定所述至少一服务节点中网络指标信息与所述终端设备的等级匹配的服务节点；
将与所述终端设备的等级匹配的服务节点确定为所述终端设备接入的目标服务节点。
所述终端设备的等级用于反映所述终端设备对于应用处理的重要程度，可以为重要等级，也可以为普通等级，还可以为其他等级如超重要等级，这里不做具体限定。其中，重要等级的终端设备相对于普通等级的终端设备，其应用的处理紧急程度可以大些，需要优先处理或者快速响应处理。
所述云端服务器可以根据所述终端设备的标识信息，确定所述终端设备的等级，比如，所述云端服务器可以预先存储有终端设备的标识信息和等级的映射表，基于所述标识信息，在所述映射表中即可查询到所述终端设备的等级。
所述云端服务器可以设置网络性能度量指标和负载信息的权值，基于加权的方式确定所述至少一服务节点中各服务节点的网络的好坏，并可以基于各服务节点的网络的好坏，对各服务节点进行排序。基于排序后的各服务节 点，匹配出所述终端设备的等级相应的服务节点。
应当说明的是，所述终端设备的等级相应的服务节点可以仅包括一个，也包括多个，这里不做具体限定。比如，排序后的服务节点包括服务节点1、服务节点2、服务节点3和服务节点4，对于重要等级的终端设备，只有网络指标信息较好的服务节点1和服务节点2可以满足该终端设备的要求，也就是说，服务节点1和服务节点2与该终端设备匹配；对于普通等级的终端设备，由于其对于应用处理的性能要求不是很高，网络指标信息一般的服务节点3和服务节点4可以满足该终端设备的要求，也就是说，服务节点3和服务节点4与该终端设备匹配。
在所述终端设备的等级相应的服务节点包括多个的情况下，所述云端服务器可以将所述终端设备的等级相应的多个服务节点中的任一个服务节点确定为所述至少一服务节点中网络指标信息与所述终端设备的等级匹配的服务节点，也可以将所述终端设备的等级相应的多个服务节点中网络指标信息最好的服务节点确定为所述至少一服务节点中网络指标信息与所述终端设备的等级匹配的服务节点，这里不做具体限定。
当然，所述云端服务器也可以将所述终端设备的等级相应的多个服务节点都确定为所述终端设备接入的目标服务节点，相应的，将各所述目标服务节点的访问标识都发送给终端设备，让终端设备基于各所述目标服务节点的访问标识中的任一访问标识接入目标服务节点。
第三种引流策略可以为：根据服务节点的网络指标信息和终端设备的特征信息，为所述终端设备选择目标服务节点。
具体的，所述基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点的步骤包括：
基于所述终端设备的历史设置数据，确定所述终端设备的特征信息；其中，所述特征信息用于反映所述终端设备对网络的性能要求；
确定所述至少一服务节点中网络指标信息与所述特征信息匹配的服务节点；
将与所述特征信息匹配的服务节点确定为所述终端设备接入的目标服务节点。
所述云端服务器可以统计所述终端设备的历史设置数据，确定所述终端设备的特征信息，所述特征信息用于反映所述终端设备对网络的性能要求。举个例子来说，对于视频播放应用，所述终端设备对于视频清晰度的偏好设置是1080P，所述云端服务器统计所述终端设备对于视频播放应用的历史设置数据，确定所述终端设备对于视频播放应用的偏好设置，该偏好设置即为所述终端设备对于视频播放应用的特征信息，该特征信息可以包括视频清晰度的偏好设置1080P，也就是说，所述云端服务器基于特征信息中视频清晰度的偏好设置1080P，可以确定所述终端设备对于网络的性能要求较高。
进一步的，所述云端服务器可以基于所述特征信息，确定第二网络指标阈值，在所述至少一服务节点中存在服务节点的网络指标信息大于所述第二网络指标阈值时，则确定该网络指标信息与所述特征信息匹配，相应的，将与所述特征信息匹配的网络指标信息对应的服务节点确定为目标服务节点。
步骤104，将所述目标服务节点的访问标识发送给所述终端设备，所述访问标识用于指示所述终端设备接入所述目标服务节点。
所述云端服务器在确定目标服务节点之后，将所述目标服务节点的访问标识发送给所述终端设备，其中，所述访问标识可以为所述目标服务节点的IP地址。
相应的，所述终端设备可以接收所述目标服务节点的访问标识，并基于所述访问标识，接入该目标服务节点进行业务会话，从而实现对终端设备应用进行处理。
另外，云端服务器还可以向终端设备的应用提供登录信息的返回信息，如登录信息的返回信息包括加密密钥，相应的，所述终端设备接收所述返回信息，另外，为了实现目标服务节点对终端设备的应用业务的处理，所述云端服务器还需要将所述终端设备所关联的业务处理信息发送至所述目标服务节点，其中，所述业务处理信息包括所述终端设备应用的登录信息和所述登录信息的返回信息，以同步所述终端设备的登录信息，同时，所述业务处理信息还包括所述终端设备的应用业务所需信息。
本公开实施例提供的基于MEC的服务节点分配方法，在终端设备应用登录云端服务器时，云端服务器根据MEC服务器提供的网络指标信息为终端设 备分配服务节点来完成服务引流，相对于DNS解析引流方式，不需要终端应用支持DNS域名访问，也适合物联网场景中不支持DNS域名访问的终端设备，同时，不需要依赖于DNS的更新速度。而相对于动态路由方式，不需要依赖网络路由设备，不受应用场景的限制，能支持多活的服务器场景。因此，本公开实施例能够提高服务引流的灵活性，同时，实现简单，切换速度快，且终端设备应用可随时自主发起引流更新，快速响应终端设备的需求。并且，其引流策略比较灵活，支持用户颗粒度的应用级策略引流。
参见图2，图中示出了本公开实施例提供的基于MEC的服务节点分配方法的流程示意图之二。应用于MEC服务器，如图2所示，该方法可以包括如下步骤：
步骤201，接收云端服务器发送的查询请求；其中，所述查询请求包括终端设备的标识信息；
步骤202，基于所述查询请求，查询并获得所述MEC服务器管控的至少一服务节点的网络指标信息；其中，每一所述服务节点的网络指标信息中包括所述标识信息对应的终端设备到所述服务节点的网络性能度量信息；
步骤203，将所述至少一服务节点的网络指标信息发送给云端服务器；其中，所述至少一服务节点的网络指标信息用于指示所述云端服务器为所述终端设备选择目标服务节点。
所述至少一服务节点的网络指标信息包括网络指标信息满足预设阈值的服务节点的网络指标信息；或者，
所述至少一服务节点的网络指标信息包括根据网络指标信息进行排名的服务节点中前N个服务节点的网络指标信息；其中，所述N为大于或等于1的正整数。
应当说明的是，上述预设阈值即为实施例一中描述的第一网络指标阈值。上述具体的控制过程与实施例一类似，这里就不再对其赘述。
本公开实施例中，在终端设备应用登录云端服务器时，云端服务器根据MEC服务器提供的网络指标信息为终端设备分配服务节点来完成服务引流，相对于DNS解析引流方式，不需要终端应用支持DNS域名访问，也适合物联网场景中不支持DNS域名访问的终端设备，同时，不需要依赖于DNS的 更新速度。而相对于动态路由方式，不需要依赖网络路由设备，不受应用场景的限制，能支持多活的服务器场景。因此，本公开实施例能够提高服务引流的灵活性，同时，实现简单，切换速度快，且终端设备应用可随时自主发起引流更新，快速响应终端设备的需求。
下面对本公开实施例提供的基于MEC的服务节点分配方法举例进行详细说明。
应用场景：参见图3，图中示出了本公开实施例提供的基于MEC的服务节点分配方法应用的服务引流系统的结构示意图，如图3所示，服务引流系统包括：终端设备、云端服务器、MEC服务器和边缘接入应用服务器。参见图4，图中示出了本公开实施例提供的基于MEC的服务节点分配方法的时序图，如图4所示，应用于服务引流系统，该方法流程具体为：
首先，终端设备向云端服务器发送登录请求；其中，登录请求中包括所述终端设备的标识信息，所述标识信息可以包括网络标识和/或设备标识；
然后，所述云端服务器根据所述标识信息，向MEC服务器发起查询请求；其中，所述查询请求中包括所述终端设备的标识信息和应用标识信息；
接着，所述MEC服务器基于所述标识信息，查询并获得至少一边缘接入应用服务器的网络指标信息，并将所述至少一边缘接入应用服务器的网络指标信息发送给所述云端服务器；
接着，所述云端服务器接收所述至少一边缘接入应用服务器的网络指标信息，并基于所述至少一边缘接入应用服务器的网络指标信息，按照预设的引流策略为所述终端设备选择目标边缘接入应用服务器；
接着，将所述目标边缘接入应用服务器的访问标识发送给所述终端设备，同时，将业务处理信息同步至所述目标边缘接入应用服务器；
最后，所述终端设备接收所述目标边缘接入应用服务器的访问标识，并基于所述访问标识接入至所述目标边缘接入应用服务器进行业务会话。
上述实施例详细介绍了终端设备登录云端服务器，并由云端服务器借助MEC服务器为终端设备分配目标服务节点的实现过程，需要说明的是，以下实施例将详细介绍终端设备登录MEC服务器，由MEC服务器直接为终端设备分配目标服务节点的实现过程。
具体的，参见图5，图中示出了本公开实施例提供的基于MEC的服务节点分配方法的流程示意图之三。应用于MEC服务器，如图5所示，该方法可以包括如下步骤：
步骤501，获取终端设备发送的查询请求；其中，所述查询请求中包括所述终端设备的标识信息及目标服务应用的标识信息；
步骤502，基于所述查询请求，查询所述MEC服务器基于所述目标服务应用的标识信息对应的服务应用管控的至少一服务节点的网络指标信息；其中，每一所述服务节点的网络指标信息中包括所述标识信息对应的终端设备到所述服务节点的网络性能度量信息；
步骤503，基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点；其中，所述目标服务节点为所述至少一服务节点中的服务节点；
步骤504，将所述目标服务节点的访问标识发送给所述终端设备，所述访问标识用于指示所述终端设备接入所述目标服务节点。
在步骤501中，终端设备应用为实现业务处理，终端设备应用可以向MEC服务器发起查询请求，所述查询请求中携带有终端设备的标识信息和目标服务应用的标识信息；相应的，所述MEC服务器接收所述终端设备发送的查询请求。
其中，所述终端设备的标识信息可以仅包括网络标识，如所述终端设备的IP地址或端口号，所述终端设备的标识信息也可以仅包括设备标识，如国际移动用户识别码(International Mobile Subscriber Identity，IMSI)或唯一身份标识ID(Identification，ID)，所述终端设备的标识信息也可以同时包括网络标识和设备标识，这里不做具体限定。
所述目标服务应用的标识信息可以用于指示MEC服务器去查询其管控的指定服务节点的网络指标信息，所述目标服务应用可以为终端设备上的任何应用，比如，所述目标服务应用可以为支付宝应用、微信应用等。
在步骤502中，所述MEC服务器查询所述MEC服务器管控的至少一服务节点的网络指标信息的实现过程与上述实施例类似，其具体实现过程不再赘述。只是触发所述MEC服务器去查询的触发条件不同，上述实施例触发所 述MEC服务器去查询的触发条件是云端服务器发送的查询请求，而本实施例触发所述MEC服务器去查询的触发条件是终端设备发送的查询请求。
在步骤503和步骤504中，与上述实施例的实现过程类似，其具体实现过程不再赘述。只是执行主语不同，上述实施例是由云端服务器的处理器运行实现，而本实施例是由MEC服务器的处理器运行实现。
本公开实施例中，MEC服务器基于终端设备发送的查询请求，查询网络指标信息，并根据所述网络指标信息为终端设备分配服务节点来完成服务引流，相对于DNS解析引流方式，不需要终端应用支持DNS域名访问，也适合物联网场景中不支持DNS域名访问的终端设备，同时，不需要依赖于DNS的更新速度。而相对于动态路由方式，不需要依赖网络路由设备，不受应用场景的限制，能支持多活的服务器场景。因此，本公开实施例能够提高服务引流的灵活性，同时，实现简单，切换速度快，且终端设备应用可随时自主发起引流更新，快速响应终端设备的需求。
可选的，所述基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点的步骤包括：
确定所述至少一服务节点中网络指标信息最好的服务节点；
将所述至少一服务节点中网络指标信息最好的服务节点确定为所述终端设备接入的目标服务节点。
可选的，所述基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点的步骤包括：
获取所述终端设备的等级；其中，所述等级用于反映所述终端设备对于应用处理的重要程度；
确定所述至少一服务节点中网络指标信息与所述终端设备的等级匹配的服务节点；
将与所述终端设备的等级匹配的服务节点确定为所述终端设备接入的目标服务节点。
可选的，所述基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点的步骤包括：
基于所述终端设备的历史设置数据，确定所述终端设备的特征信息；其 中，所述特征信息用于反映所述终端设备对网络的性能要求；
确定所述至少一服务节点中网络指标信息与所述特征信息匹配的服务节点；
将与所述特征信息匹配的服务节点确定为所述终端设备接入的目标服务节点。
需要说明的是，所述MEC服务器基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点的引流策略可以预先设置，可以设置的与云端服务器一致，因此，其具体选择目标服务节点的过程与上述实施例类似，这里不再赘述。
可选的，所述将所述目标服务节点的访问标识发送给所述终端设备之后，所述方法还包括：
将所述目标服务节点的访问标识发送至云端服务器。
这里，所述MEC服务器将所述目标服务节点的访问标识发送至云端服务器，使得所述云端服务器可以将所述终端设备所关联的业务处理信息发送至所述目标服务节点，其中，所述业务处理信息包括所述终端设备应用的登录信息和所述登录信息的返回信息，以同步所述终端设备的登录信息，同时，所述业务处理信息还包括所述终端设备的应用业务所需信息。
下面对本公开实施例提供的基于MEC的服务节点分配装置进行说明。
参见图6，图中示出了本公开实施例提供的基于MEC的服务节点分配装置的结构示意图之一。应用于云端服务器，如图6所示，基于MEC的服务节点分配装置600包括：
第一接收模块601，用于接收终端设备发送的登录请求；其中，所述登录请求中包括所述终端设备的标识信息；
第二接收模块602，用于接收移动边缘计算MEC服务器基于查询请求反馈的所述MEC服务器管控的至少一服务节点的网络指标信息；其中，所述查询请求包括所述标识信息，每一所述服务节点的网络指标信息中包括所述标识信息对应的终端设备到所述服务节点的网络性能度量信息；
第一选择模块603，用于基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点；其中，所述目标服务节点为所述至少一服 务节点中的服务节点；
第一发送模块604，用于将所述目标服务节点的访问标识发送给所述终端设备，所述访问标识用于指示所述终端设备接入所述目标服务节点。
可选的，所述第一选择模块603包括：
第一确定单元，用于确定所述至少一服务节点中网络指标信息最好的服务节点；
第二确定单元，用于将所述至少一服务节点中网络指标信息最好的服务节点确定为所述终端设备接入的目标服务节点。
可选的，所述第一选择模块603包括：
获取单元，用于获取所述终端设备的等级；其中，所述等级用于反映所述终端设备对于应用处理的重要程度；
第三确定单元，用于确定所述至少一服务节点中网络指标信息与所述终端设备的等级匹配的服务节点；
第四确定单元，用于将与所述终端设备的等级匹配的服务节点确定为所述终端设备接入的目标服务节点。
可选的，所述第一选择模块603包括：
第五确定单元，用于基于所述终端设备的历史设置数据，确定所述终端设备的特征信息；其中，所述特征信息用于反映所述终端设备对网络的性能要求；
第六确定单元，用于确定所述至少一服务节点中网络指标信息与所述特征信息匹配的服务节点；
第七确定单元，用于将与所述特征信息匹配的服务节点确定为所述终端设备接入的目标服务节点。
可选的，所述装置还包括：
第四发送模块，用于将所述终端设备所关联的业务处理信息发送至所述目标服务节点。
本公开实施例提供的基于MEC的服务节点分配装置能够实现上述云端服务器侧方法实施例中实现的各个过程，为避免重复，这里不再赘述。
参见图7，图中示出了本公开实施例提供的基于MEC的服务节点分配装 置的结构示意图之二。应用于MEC服务器，如图7所示，基于MEC的服务节点分配装置700包括：
第三接收模块701，用于接收云端服务器发送的查询请求；其中，所述查询请求包括终端设备的标识信息；
第一查询模块702，用于基于所述查询请求，查询并获得所述MEC服务器管控的至少一服务节点的网络指标信息；其中，每一所述服务节点的网络指标信息中包括所述标识信息对应的终端设备到所述服务节点的网络性能度量信息；
第二发送模块703，用于将所述至少一服务节点的网络指标信息发送给云端服务器；其中，所述至少一服务节点的网络指标信息用于指示所述云端服务器为所述终端设备选择目标服务节点。
可选的，所述至少一服务节点的网络指标信息包括网络指标信息满足预设阈值的服务节点的网络指标信息；或者，
所述至少一服务节点的网络指标信息包括根据网络指标信息进行排名的服务节点中前N个服务节点的网络指标信息；其中，所述N为大于或等于1的正整数。
本公开实施例提供的基于MEC的服务节点分配装置能够实现上述MEC服务器侧方法实施例中实现的各个过程，为避免重复，这里不再赘述。
本公开实施例提供的基于MEC的服务节点分配装置，在终端设备应用登录云端服务器时，云端服务器根据MEC服务器提供的网络指标信息为终端设备分配服务节点来完成服务引流，相对于DNS解析引流方式，不需要终端应用支持DNS域名访问，也适合物联网场景中不支持DNS域名访问的终端设备，同时，不需要依赖于DNS的更新速度。而相对于动态路由方式，不需要依赖网络路由设备，不受应用场景的限制，能支持多活的服务器场景。因此，本公开实施例能够提高服务引流的灵活性，同时，实现简单，切换速度快，且终端设备应用可随时自主发起引流更新，快速响应终端设备的需求。并且，其引流策略比较灵活，支持用户颗粒度的应用级策略引流。
参见图8，图中示出了本公开实施例提供的基于MEC的服务节点分配装置的结构示意图之三。应用于MEC服务器，如图8所示，基于MEC的服务 节点分配装置800包括：
获取模块801，用于获取终端设备发送的查询请求；其中，所述查询请求中包括所述终端设备的标识信息及目标服务应用的标识信息；
第二查询模块802，用于基于所述查询请求，查询所述MEC服务器基于所述目标服务应用的标识信息对应的服务应用管控的至少一服务节点的网络指标信息；其中，每一所述服务节点的网络指标信息中包括所述标识信息对应的终端设备到所述服务节点的网络性能度量信息；
第二选择模块803，用于基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点；其中，所述目标服务节点为所述至少一服务节点中的服务节点；
第三发送模块804，用于将所述目标服务节点的访问标识发送给所述终端设备，所述访问标识用于指示所述终端设备接入所述目标服务节点。
可选的，所述第二选择模块803，具体用于确定所述至少一服务节点中网络指标信息最好的服务节点；将所述至少一服务节点中网络指标信息最好的服务节点确定为所述终端设备接入的目标服务节点。
可选的，所述第二选择模块803，具体用于获取所述终端设备的等级；其中，所述等级用于反映所述终端设备对于应用处理的重要程度；确定所述至少一服务节点中网络指标信息与所述终端设备的等级匹配的服务节点；将与所述终端设备的等级匹配的服务节点确定为所述终端设备接入的目标服务节点。
可选的，所述第二选择模块803，具体用于基于所述终端设备的历史设置数据，确定所述终端设备的特征信息；其中，所述特征信息用于反映所述终端设备对网络的性能要求；确定所述至少一服务节点中网络指标信息与所述特征信息匹配的服务节点；将与所述特征信息匹配的服务节点确定为所述终端设备接入的目标服务节点。
可选的，所述装置还包括：
第五发送模块，用于将所述目标服务节点的访问标识发送至云端服务器。
参见图9，图中示出了本公开实施例提供的云端服务器的结构示意图。如图9所示，云端服务器900包括：第一处理器901、第一存储器902、第一 用户接口903和第一总线接口904。
第一处理器901，用于读取第一存储器902中的程序，执行下列过程：
接收终端设备发送的登录请求；其中，所述登录请求中包括所述终端设备的标识信息；
接收移动边缘计算MEC服务器基于查询请求反馈的所述MEC服务器管控的至少一服务节点的网络指标信息；其中，所述查询请求包括所述标识信息，每一所述服务节点的网络指标信息中包括所述标识信息对应的终端设备到所述服务节点的网络性能度量信息；
基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点；其中，所述目标服务节点为所述至少一服务节点中的服务节点；
将所述目标服务节点的访问标识发送给所述终端设备，所述访问标识用于指示所述终端设备接入所述目标服务节点。
在图9中，总线架构可以包括任意数量的互联的总线和桥，具体由第一处理器901代表的一个或多个处理器和第一存储器902代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。第一总线接口904提供接口。针对不同的用户设备，第一用户接口903还可以是能够外接内接需要设备的接口，连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
第一处理器901负责管理总线架构和通常的处理，第一存储器902可以存储第一处理器901在执行操作时所使用的数据。
可选的，第一处理器901，具体用于：
确定所述至少一服务节点中网络指标信息最好的服务节点；
将所述至少一服务节点中网络指标信息最好的服务节点确定为所述终端设备接入的目标服务节点。
可选的，第一处理器901，具体用于：
获取所述终端设备的等级；其中，所述等级用于反映所述终端设备对于应用处理的重要程度；
确定所述至少一服务节点中网络指标信息与所述终端设备的等级匹配的 服务节点；
将与所述终端设备的等级匹配的服务节点确定为所述终端设备接入的目标服务节点。
可选的，第一处理器901，具体用于：
基于所述终端设备的历史设置数据，确定所述终端设备的特征信息；其中，所述特征信息用于反映所述终端设备对网络的性能要求；
确定所述至少一服务节点中网络指标信息与所述特征信息匹配的服务节点；
将与所述特征信息匹配的服务节点确定为所述终端设备接入的目标服务节点。
第一处理器901，还用于：
将所述终端设备所关联的业务处理信息发送至所述目标服务节点。
可选的，本公开实施例还提供一种云端服务器，包括第一处理器901，第一存储器902，存储在第一存储器902上并可在所述第一处理器901上运行的计算机程序，该计算机程序被第一处理器901执行时实现上述云端服务器侧基于MEC的服务节点分配方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
参见图10，图中示出了本公开实施例提供的MEC服务器的结构示意图。如图10所示，MEC服务器1000包括：第二处理器1001、第二存储器1002、第二用户接口1003和第二总线接口1004。
第二处理器1001，用于读取第二存储器1002中的程序，执行下列过程：
接收云端服务器发送的查询请求；其中，所述查询请求包括终端设备的标识信息；
基于所述查询请求，查询并获得所述MEC服务器管控的至少一服务节点的网络指标信息；其中，每一所述服务节点的网络指标信息中包括所述标识信息对应的终端设备到所述服务节点的网络性能度量信息；
将所述至少一服务节点的网络指标信息发送给云端服务器；其中，所述至少一服务节点的网络指标信息用于指示所述云端服务器为所述终端设备选择目标服务节点。
进一步的，第二处理器1001，用于读取第二存储器1002中的程序，还执行下列过程：
获取终端设备发送的查询请求；其中，所述查询请求中包括所述终端设备的标识信息及目标服务应用的标识信息；
基于所述查询请求，查询所述MEC服务器基于所述目标服务应用的标识信息对应的服务应用管控的至少一服务节点的网络指标信息；其中，每一所述服务节点的网络指标信息中包括所述标识信息对应的终端设备到所述服务节点的网络性能度量信息；
基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点；其中，所述目标服务节点为所述至少一服务节点中的服务节点；
将所述目标服务节点的访问标识发送给所述终端设备，所述访问标识用于指示所述终端设备接入所述目标服务节点。
第二处理器1001，具体用于：
确定所述至少一服务节点中网络指标信息最好的服务节点；
将所述至少一服务节点中网络指标信息最好的服务节点确定为所述终端设备接入的目标服务节点。
第二处理器1001，具体用于：
获取所述终端设备的等级；其中，所述等级用于反映所述终端设备对于应用处理的重要程度；
确定所述至少一服务节点中网络指标信息与所述终端设备的等级匹配的服务节点；
将与所述终端设备的等级匹配的服务节点确定为所述终端设备接入的目标服务节点。
第二处理器1001，具体用于：
基于所述终端设备的历史设置数据，确定所述终端设备的特征信息；其中，所述特征信息用于反映所述终端设备对网络的性能要求；
确定所述至少一服务节点中网络指标信息与所述特征信息匹配的服务节点；
将与所述特征信息匹配的服务节点确定为所述终端设备接入的目标服务 节点。
第二处理器1001，还用于：
将所述目标服务节点的访问标识发送至云端服务器。
在图10中，总线架构可以包括任意数量的互联的总线和桥，具体由第二处理器1001代表的一个或多个处理器和第二存储器1002代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。第二总线接口1004提供接口。针对不同的用户设备，第二用户接口1003还可以是能够外接内接需要设备的接口，连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
第二处理器1001负责管理总线架构和通常的处理，第二存储器1002可以存储第二处理器1001在执行操作时所使用的数据。
可选的，所述至少一服务节点的网络指标信息包括网络指标信息满足预设阈值的服务节点的网络指标信息；或者，
所述至少一服务节点的网络指标信息包括根据网络指标信息进行排名的服务节点中前N个服务节点的网络指标信息；其中，所述N为大于或等于1的正整数。
可选的，本公开实施例还提供一种MEC服务器，包括第二处理器1001，第二存储器1002，存储在第二存储器1002上并可在所述第二处理器1001上运行的计算机程序，该计算机程序被第二处理器1001执行时实现上述MEC服务器侧基于MEC的服务节点分配方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本公开实施例还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被第一处理器执行时实现上述云端服务器侧基于MEC的服务节点分配方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述，或者，该计算机程序被第二处理器执行时实现上述MEC服务器侧基于MEC的服务节点分配方法实施例的各个过程，且能达到相同的技术效果。其中，所述的计算机可读存储介质，如只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory， RAM)、磁碟或者光盘等。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的实施例中，应该理解到，所揭露的系统和方法，可以通过其它的方式实现。例如，以上所描述的系统实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本公开实施例方案的目的。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本公开的技术方案本质上或者说对相关技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开各个实施例所述方法的全部或部分步骤。而前述的存储 介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应以权利要求的保护范围为准。

Claims (18)

  1. 一种基于MEC的服务节点分配方法，应用于云端服务器，其中，所述方法包括：
    接收终端设备发送的登录请求；其中，所述登录请求中包括所述终端设备的标识信息；
    接收移动边缘计算MEC服务器基于查询请求反馈的所述MEC服务器管控的至少一服务节点的网络指标信息；其中，所述查询请求包括所述标识信息，每一所述服务节点的网络指标信息中包括所述标识信息对应的终端设备到所述服务节点的网络性能度量信息；
    基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点；其中，所述目标服务节点为所述至少一服务节点中的服务节点；
    将所述目标服务节点的访问标识发送给所述终端设备，所述访问标识用于指示所述终端设备接入所述目标服务节点。
  2. 根据权利要求1所述的方法，其中，所述基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点的步骤包括：
    确定所述至少一服务节点中网络指标信息最好的服务节点；
    将所述至少一服务节点中网络指标信息最好的服务节点确定为所述终端设备接入的目标服务节点。
  3. 根据权利要求1所述的方法，其中，所述基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点的步骤包括：
    获取所述终端设备的等级；其中，所述等级用于反映所述终端设备对于应用处理的重要程度；
    确定所述至少一服务节点中网络指标信息与所述终端设备的等级匹配的服务节点；
    将与所述终端设备的等级匹配的服务节点确定为所述终端设备接入的目标服务节点。
  4. 根据权利要求1所述的方法，其中，所述基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点的步骤包括：
    基于所述终端设备的历史设置数据，确定所述终端设备的特征信息；其中，所述特征信息用于反映所述终端设备对网络的性能要求；
    确定所述至少一服务节点中网络指标信息与所述特征信息匹配的服务节点；
    将与所述特征信息匹配的服务节点确定为所述终端设备接入的目标服务节点。
  5. 根据权利要求1所述的方法，其中，所述将所述目标服务节点的访问标识发送给所述终端设备之后，所述方法还包括：
    将所述终端设备所关联的业务处理信息发送至所述目标服务节点。
  6. 一种基于MEC的服务节点分配方法，应用于移动边缘计算MEC服务器，其中，所述方法包括：
    接收云端服务器发送的查询请求；其中，所述查询请求包括终端设备的标识信息；
    基于所述查询请求，查询并获得所述MEC服务器管控的至少一服务节点的网络指标信息；其中，每一所述服务节点的网络指标信息中包括所述标识信息对应的终端设备到所述服务节点的网络性能度量信息；
    将所述至少一服务节点的网络指标信息发送给云端服务器；其中，所述至少一服务节点的网络指标信息用于指示所述云端服务器为所述终端设备选择目标服务节点。
  7. 根据权利要求6所述的方法，其中，所述至少一服务节点的网络指标信息包括网络指标信息满足预设阈值的服务节点的网络指标信息；或者，
    所述至少一服务节点的网络指标信息包括根据网络指标信息进行排名的服务节点中前N个服务节点的网络指标信息；其中，所述N为大于或等于1的正整数。
  8. 一种基于MEC的服务节点分配方法，应用于移动边缘计算MEC服务器，其中，所述方法包括：
    获取终端设备发送的查询请求；其中，所述查询请求中包括所述终端设备的标识信息及目标服务应用的标识信息；
    基于所述查询请求，查询所述MEC服务器基于所述目标服务应用的标识 信息对应的服务应用管控的至少一服务节点的网络指标信息；其中，每一所述服务节点的网络指标信息中包括所述标识信息对应的终端设备到所述服务节点的网络性能度量信息；
    基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点；其中，所述目标服务节点为所述至少一服务节点中的服务节点；
    将所述目标服务节点的访问标识发送给所述终端设备，所述访问标识用于指示所述终端设备接入所述目标服务节点。
  9. 根据权利要求8所述的方法，其中，所述基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点的步骤包括：
    确定所述至少一服务节点中网络指标信息最好的服务节点；
    将所述至少一服务节点中网络指标信息最好的服务节点确定为所述终端设备接入的目标服务节点。
  10. 根据权利要求8所述的方法，其中，所述基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点的步骤包括：
    获取所述终端设备的等级；其中，所述等级用于反映所述终端设备对于应用处理的重要程度；
    确定所述至少一服务节点中网络指标信息与所述终端设备的等级匹配的服务节点；
    将与所述终端设备的等级匹配的服务节点确定为所述终端设备接入的目标服务节点。
  11. 根据权利要求8所述的方法，其中，所述基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点的步骤包括：
    基于所述终端设备的历史设置数据，确定所述终端设备的特征信息；其中，所述特征信息用于反映所述终端设备对网络的性能要求；
    确定所述至少一服务节点中网络指标信息与所述特征信息匹配的服务节点；
    将与所述特征信息匹配的服务节点确定为所述终端设备接入的目标服务节点。
  12. 根据权利要求8所述的方法，其中，所述将所述目标服务节点的访 问标识发送给所述终端设备之后，所述方法还包括：
    将所述目标服务节点的访问标识发送至云端服务器。
  13. 一种基于MEC的服务节点分配装置，应用于云端服务器，其中，所述装置包括：
    第一接收模块，用于接收终端设备发送的登录请求；其中，所述登录请求中包括所述终端设备的标识信息；
    第二接收模块，用于接收移动边缘计算MEC服务器基于查询请求反馈的所述MEC服务器管控的至少一服务节点的网络指标信息；其中，所述查询请求包括所述标识信息，每一所述服务节点的网络指标信息中包括所述标识信息对应的终端设备到所述服务节点的网络性能度量信息；
    第一选择模块，用于基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点；其中，所述目标服务节点为所述至少一服务节点中的服务节点；
    第一发送模块，用于将所述目标服务节点的访问标识发送给所述终端设备，所述访问标识用于指示所述终端设备接入所述目标服务节点。
  14. 一种基于MEC的服务节点分配装置，应用于移动边缘计算MEC服务器，其中，所述装置包括：
    第三接收模块，用于接收云端服务器发送的查询请求；其中，所述查询请求包括终端设备的标识信息；
    第一查询模块，用于基于所述查询请求，查询并获得所述MEC服务器管控的至少一服务节点的网络指标信息；其中，每一所述服务节点的网络指标信息中包括所述标识信息对应的终端设备到所述服务节点的网络性能度量信息；
    第二发送模块，用于将所述至少一服务节点的网络指标信息发送给云端服务器；其中，所述至少一服务节点的网络指标信息用于指示所述云端服务器为所述终端设备选择目标服务节点。
  15. 一种基于MEC的服务节点分配装置，应用于移动边缘计算MEC服务器，其中，所述装置包括：
    获取模块，用于获取终端设备发送的查询请求；其中，所述查询请求中 包括所述终端设备的标识信息及目标服务应用的标识信息；
    第二查询模块，用于基于所述查询请求，查询所述MEC服务器基于所述目标服务应用的标识信息对应的服务应用管控的至少一服务节点的网络指标信息；其中，每一所述服务节点的网络指标信息中包括所述标识信息对应的终端设备到所述服务节点的网络性能度量信息；
    第二选择模块，用于基于所述至少一服务节点的网络指标信息，为所述终端设备选择目标服务节点；其中，所述目标服务节点为所述至少一服务节点中的服务节点；
    第三发送模块，用于将所述目标服务节点的访问标识发送给所述终端设备，所述访问标识用于指示所述终端设备接入所述目标服务节点。
  16. 一种云端服务器，包括第一处理器，第一存储器，存储在所述第一存储器上并可在所述第一处理器上运行的计算机程序，所述计算机程序被所述第一处理器执行时实现如权利要求1至5中任一项所述的基于MEC的服务节点分配方法的步骤。
  17. 一种移动边缘计算MEC服务器，包括第二处理器，第二存储器，存储在所述第二存储器上并可在所述第二处理器上运行的计算机程序，所述计算机程序被所述第二处理器执行时实现如权利要求6至12中任一项所述的基于MEC的服务节点分配方法的步骤。
  18. 一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被第一处理器执行时实现如权利要求1至5中任一项所述的基于MEC的服务节点分配方法的步骤，或者被第二处理器执行时实现如权利要求6至12中任一项所述的基于MEC的服务节点分配方法的步骤。
PCT/CN2020/120328 2019-11-21 2020-10-12 基于mec的服务节点分配方法、装置及相关服务器 WO2021098407A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911147857.5 2019-11-21
CN201911147857.5A CN112825527A (zh) 2019-11-21 2019-11-21 基于mec的服务节点分配方法、装置及相关服务器

Publications (1)

Publication Number Publication Date
WO2021098407A1 true WO2021098407A1 (zh) 2021-05-27

Family

ID=75907452

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/120328 WO2021098407A1 (zh) 2019-11-21 2020-10-12 基于mec的服务节点分配方法、装置及相关服务器

Country Status (2)

Country Link
CN (1) CN112825527A (zh)
WO (1) WO2021098407A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113726882A (zh) * 2021-08-30 2021-11-30 中国电信股份有限公司 基于5g网络的信息服务系统、方法及装置、设备、介质
CN114039977A (zh) * 2021-11-10 2022-02-11 北京奇艺世纪科技有限公司 一种基于边缘计算的应用任务的实现方法、系统及装置
CN114978917A (zh) * 2022-03-28 2022-08-30 慧之安信息技术股份有限公司 基于边缘计算的网络性能提升方法和装置
CN115514663A (zh) * 2022-09-23 2022-12-23 北京奇艺世纪科技有限公司 一种拨测方法、系统、装置、电子设备及存储介质
CN116865952A (zh) * 2023-05-23 2023-10-10 江苏华存电子科技有限公司 一种数据的加密管理方法及系统

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113434289A (zh) * 2021-06-16 2021-09-24 北京达佳互联信息技术有限公司 云主机分配方法、装置、电子设备及存储介质
CN115103007A (zh) * 2022-05-19 2022-09-23 亿点云计算(珠海)有限公司 基于分布式云的服务发现方法、装置及可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104767629A (zh) * 2014-01-06 2015-07-08 腾讯科技（深圳）有限公司 分配服务节点的方法、装置及系统
WO2017100640A1 (en) * 2015-12-11 2017-06-15 Interdigital Patent Holdings, Inc. Method and apparatus for enabling third party edge clouds at the mobile edge
CN106899681A (zh) * 2017-03-10 2017-06-27 腾讯科技（深圳）有限公司 一种信息推送的方法以及服务器
WO2018093638A1 (en) * 2016-11-16 2018-05-24 Cisco Technology, Inc. Application based intelligent edge computing in a low power wide area network environment

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100396016C (zh) * 2006-03-01 2008-06-18 华为技术有限公司 在内容分发网络中保障服务水平的系统和方法
US10419533B2 (en) * 2010-03-01 2019-09-17 Genghiscomm Holdings, LLC Edge server selection for device-specific network topologies
CN109379774B (zh) * 2018-11-08 2021-04-16 网宿科技股份有限公司 智能调度方法、终端设备、边缘节点集群与智能调度系统
CN109617957A (zh) * 2018-12-05 2019-04-12 量子云未来（北京）信息科技有限公司 一种基于cdn网络的文件上传方法、装置、服务器

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104767629A (zh) * 2014-01-06 2015-07-08 腾讯科技（深圳）有限公司 分配服务节点的方法、装置及系统
WO2017100640A1 (en) * 2015-12-11 2017-06-15 Interdigital Patent Holdings, Inc. Method and apparatus for enabling third party edge clouds at the mobile edge
WO2018093638A1 (en) * 2016-11-16 2018-05-24 Cisco Technology, Inc. Application based intelligent edge computing in a low power wide area network environment
CN106899681A (zh) * 2017-03-10 2017-06-27 腾讯科技（深圳）有限公司 一种信息推送的方法以及服务器

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113726882A (zh) * 2021-08-30 2021-11-30 中国电信股份有限公司 基于5g网络的信息服务系统、方法及装置、设备、介质
CN113726882B (zh) * 2021-08-30 2023-08-11 中国电信股份有限公司 基于5g网络的信息服务系统、方法及装置、设备、介质
CN114039977A (zh) * 2021-11-10 2022-02-11 北京奇艺世纪科技有限公司 一种基于边缘计算的应用任务的实现方法、系统及装置
CN114039977B (zh) * 2021-11-10 2024-03-26 北京奇艺世纪科技有限公司 一种基于边缘计算的应用任务的实现方法、系统及装置
CN114978917A (zh) * 2022-03-28 2022-08-30 慧之安信息技术股份有限公司 基于边缘计算的网络性能提升方法和装置
CN115514663A (zh) * 2022-09-23 2022-12-23 北京奇艺世纪科技有限公司 一种拨测方法、系统、装置、电子设备及存储介质
CN115514663B (zh) * 2022-09-23 2023-10-27 北京奇艺世纪科技有限公司 一种拨测方法、系统、装置、电子设备及存储介质
CN116865952A (zh) * 2023-05-23 2023-10-10 江苏华存电子科技有限公司 一种数据的加密管理方法及系统
CN116865952B (zh) * 2023-05-23 2024-02-20 江苏华存电子科技有限公司 一种数据的加密管理方法及系统

Also Published As

Publication number Publication date
CN112825527A (zh) 2021-05-21

Similar Documents

Publication Publication Date Title
WO2021098407A1 (zh) 基于mec的服务节点分配方法、装置及相关服务器
US10374955B2 (en) Managing network computing components utilizing request routing
EP3968605A1 (en) Method for providing edge service, apparatus and device
US10009284B2 (en) Policy-based session establishment and transfer in a virtualized/cloud environment
US20200195511A1 (en) Network management method and related device
CN106534328B (zh) 节点连接方法及分布式计算系统
US9294433B1 (en) Multiple-master DNS system
US9979656B2 (en) Methods, systems, and computer readable media for implementing load balancer traffic policies
CN109151009B (zh) 一种基于mec的cdn节点分配方法和系统
CN110086886B (zh) 动态会话保持方法及装置
US11394683B2 (en) Domain name resolution method and apparatus based on a plurality of availability zones AZ
CN108124020B (zh) 域名解析方法、系统及设备
CN110474802B (zh) 设备切换方法及装置、服务系统
US9729347B2 (en) System and method for selection of a conference bridge master server
CN114095430B (zh) 一种访问报文的处理方法、系统及工作节点
CN111327668A (zh) 网络管理方法、装置、设备和存储介质
US20110153826A1 (en) Fault tolerant and scalable load distribution of resources
CN109743357B (zh) 一种业务访问连续性的实现方法及装置
US7711780B1 (en) Method for distributed end-to-end dynamic horizontal scalability
JP2022533639A (ja) エッジアプリケーションを確定する方法、装置、機器及び記憶媒体
WO2023207189A1 (zh) 负载均衡方法及系统、计算机存储介质、电子设备
WO2020119699A1 (zh) 物联网的资源发布方法、装置、设备及存储介质
CA2860509A1 (en) Central conferencing routing server
US20220263759A1 (en) Addressing method, addressing system, and addressing apparatus
CN107528884B (zh) 一种聚合服务器的用户请求处理方法和装置

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: 20890414

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20890414

Country of ref document: EP

Kind code of ref document: A1