CN112825527A

CN112825527A - Service node distribution method and device based on MEC and related server

Info

Publication number: CN112825527A
Application number: CN201911147857.5A
Authority: CN
Inventors: 毛峻岭; 方绍波
Original assignee: China Mobile Communications Group Co Ltd; China Mobile IoT Co Ltd
Current assignee: China Mobile Communications Group Co Ltd; China Mobile IoT Co Ltd
Priority date: 2019-11-21
Filing date: 2019-11-21
Publication date: 2021-05-21
Also published as: WO2021098407A1

Abstract

The invention provides a service node distribution method and device based on an MEC, a cloud server, an MEC server and a computer readable storage medium. The method comprises the following steps: receiving a login request sent by terminal equipment; receiving network index information of at least one service node managed and controlled by the MEC server, which is fed back by the mobile edge computing MEC server based on the query request; selecting a target service node for the terminal equipment based on the network index information of the at least one service node; and sending an access identifier of the target service node to the terminal equipment, wherein the access identifier is used for indicating the terminal equipment to access the target service node. The embodiment of the invention can improve the flexibility of service drainage.

Description

Service node distribution method and device based on MEC and related server

Technical Field

The embodiment of the invention relates to the technical field of Edge Computing, in particular to a Mobile Edge Computing (MEC) -based service node distribution method, a device, a cloud server, an MEC server and a computer-readable storage medium.

Background

With the development of network technology, internet and internet of things services, people have a demand for service deployment and service provision in a mobile network edge data center, so that service interaction flow between a mobile terminal and a service server is saved, service interaction delay is reduced, and service pressure of the service server is reduced. Particularly, in an application scenario of the internet of things, the demand for edge service deployment is huge, and in an access process of a mobile network edge data center, there is a problem of edge access server allocation (also called service drainage), and a corresponding edge access server needs to be allocated for an accessed terminal application.

At present, there are two main service drainage modes, namely a Domain Name System (DNS) analysis drainage mode and a dynamic routing mode. For the DNS analysis drainage mode, the domain name of the application request is analyzed to the edge access application server needing to be distributed for the application through the DNS, so that the drainage purpose is achieved; for the dynamic routing mode, the application request is routed to the edge access application server which needs to be allocated for the application by dynamically routing a server Internet Protocol (IP), so as to achieve the purpose of drainage.

As can be seen from the above description, both the DNS resolution drainage manner and the dynamic routing manner are limited to an application scenario, for example, for the DNS resolution drainage manner, a terminal application is required to support DNS domain name access, while in the scenario of the internet of things, because part of terminals are limited in capability, the terminal application may not support DNS domain name access, and for the dynamic routing manner, a network routing device is required to be relied on and is generally used to support a primary and standby server scenario, so the service drainage manner in the prior art has a problem of poor flexibility.

Disclosure of Invention

The embodiment of the invention provides a service node distribution method and device based on an MEC, a cloud server, an MEC server and a computer readable storage medium, and aims to solve the problem that a service drainage mode in the prior art is poor in flexibility.

In a first aspect, an embodiment of the present invention provides a service node allocation method based on MEC, which is applied to a cloud server, and the method includes:

receiving a login request sent by terminal equipment; the login request comprises identification information of the terminal equipment;

receiving network index information of at least one service node managed and controlled by the MEC server, which is fed back by the mobile edge computing MEC server based on the query request; the query request comprises the identification information, and the network index information of each service node comprises network performance measurement information from the terminal equipment corresponding to the identification information to the service node;

selecting a target service node for the terminal equipment 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;

and sending an access identifier of the target service node to the terminal equipment, wherein the access identifier is used for indicating the terminal equipment to access the target service node.

In a second aspect, an embodiment of the present invention provides a service node allocation method based on an MEC, which is applied to an MEC server, and the method includes:

receiving a query request sent by a cloud server; the query request comprises identification information of the terminal equipment;

inquiring and obtaining network index information of at least one service node managed and controlled by the MEC server based on the inquiry request; the network index information of each service node comprises network performance measurement information from the terminal equipment corresponding to the identification information to the service node;

sending the network index information of the at least one service node to a cloud server; the network index information of the at least one service node is used for indicating the cloud server to select a target service node for the terminal device.

In a third aspect, an embodiment of the present invention further provides a service node allocation method based on MEC, which is applied to a mobile edge computing MEC server, and the method includes:

acquiring a query request sent by terminal equipment; the query request comprises identification information of the terminal equipment and identification information of a target service application;

based on the query request, querying network index information of at least one service node managed and controlled by the MEC server based on the service application corresponding to the identification information of the target service application; the network index information of each service node comprises network performance measurement information from the terminal equipment corresponding to the identification information to the service node;

In a fourth aspect, an embodiment of the present invention provides an MEC-based service node allocation apparatus, which is applied to a cloud server, and the apparatus includes:

the first receiving module is used for receiving a login request sent by the terminal equipment; the login request comprises identification information of the terminal equipment;

the second receiving module is used for receiving network index information of at least one service node managed and controlled by the MEC server, which is fed back by the mobile edge computing MEC server based on the query request; the query request comprises the identification information, and the network index information of each service node comprises network performance measurement information from the terminal equipment corresponding to the identification information to the service node;

a first selection module, 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;

a first sending module, configured to send an 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.

In a fifth aspect, an embodiment of the present invention provides an MEC-based service node allocation apparatus, which is applied to an MEC server, and the apparatus includes:

the third receiving module is used for receiving a query request sent by the cloud server; the query request comprises identification information of the terminal equipment;

the first query module is used for querying and obtaining network index information of at least one service node managed and controlled by the MEC server based on the query request; the network index information of each service node comprises network performance measurement information from the terminal equipment corresponding to the identification information to the service node;

the second sending module is used for sending the network index information of the at least one service node to the cloud server; the network index information of the at least one service node is used for indicating the cloud server to select a target service node for the terminal device.

In a sixth aspect, an embodiment of the present invention provides an MEC-based service node allocation apparatus, applied to a mobile edge computing MEC server, where the apparatus includes:

the acquisition module is used for acquiring the query request sent by the terminal equipment; the query request comprises identification information of the terminal equipment and identification information of a target service application;

a second query module, configured to query, based on the query request, network index information of at least one service node managed and controlled by the MEC server based on the service application corresponding to the identification information of the target service application; the network index information of each service node comprises network performance measurement information from the terminal equipment corresponding to the identification information to the service node;

a second selection module, 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;

a third sending module, configured to send an 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.

In a seventh aspect, an embodiment of the present invention provides a cloud server, including a first processor, a first memory, and a computer program that is stored in the first memory and is executable on the first processor, where the computer program, when executed by the first processor, implements the steps of the service node allocation method based on MEC on the cloud server side.

In an eighth aspect, an embodiment of the present invention provides an MEC server, including a second processor, a second memory, and a computer program stored on the second memory and executable on the second processor, where the computer program, when executed by the second processor, implements the steps of the MEC server-side service node allocation method based on MEC.

In a ninth aspect, an embodiment of the present invention provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and the computer program, when executed by a first processor, implements the steps of the method for allocating service nodes based on MECs on the cloud server side, or when executed by a second processor, implements the steps of the method for allocating service nodes based on MECs on the MEC server side.

According to the service node allocation method and device based on the MEC, the cloud server, the MEC server and the computer readable storage medium provided by the embodiment of the invention, firstly, under the condition that a terminal device application logs in the cloud server, the cloud server queries network index information of each service node based on the application, which is managed and controlled by the MEC server, from the MEC server according to a login request sent by the terminal device; the network index information comprises network performance measurement information of the terminal equipment to the service node corresponding to the identification information in the login request; then, selecting a target service node for the terminal equipment based on the network index information provided by the MEC server; and finally, sending the access identifier of the target service node to the terminal equipment, thereby realizing service drainage of the application of the terminal equipment.

In the embodiment of the invention, when the terminal device is applied to log in the cloud server, the cloud server allocates the service nodes to the terminal device according to the network index information provided by the MEC server to complete service drainage, and compared with a DNS (domain name system) analysis drainage mode, the terminal device does not need to support DNS (domain name system) domain name access by terminal application, is also suitable for the terminal device which does not support DNS domain name access in the scene of the Internet of things, and does not need to rely on the updating speed of the DNS. Compared with a dynamic routing mode, the method does not need to rely on network routing equipment, is not limited by application scenes, and can support multi-live server scenes. Therefore, the embodiment of the invention can improve the flexibility of service drainage, is simple to realize and high in switching speed, and the terminal equipment application can autonomously initiate drainage updating at any time and quickly respond to the requirement of the terminal equipment.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.

Fig. 1 is one of the flow diagrams of a service node allocation method based on MEC according to an embodiment of the present invention;

fig. 2 is a second schematic flowchart of a service node allocation method based on MEC according to an embodiment of the present invention;

fig. 3 is a schematic structural diagram of a service drainage system applied to the MEC-based service node allocation method according to the embodiment of the present invention;

fig. 4 is a timing diagram of a service node allocation method based on MEC according to an embodiment of the present invention;

fig. 5 is a third schematic flowchart of a service node allocation method based on MEC according to an embodiment of the present invention;

fig. 6 is one of schematic structural diagrams of a service node allocation apparatus based on MEC according to an embodiment of the present invention;

fig. 7 is a second schematic structural diagram of a service node allocation apparatus based on MEC according to an embodiment of the present invention;

fig. 8 is a third schematic structural diagram of an MEC-based service node allocation apparatus according to an embodiment of the present invention;

fig. 9 is a schematic structural diagram of a cloud server according to an embodiment of the present invention;

fig. 10 is a schematic structural diagram of an MEC server according to an embodiment of the present invention.

Detailed Description

As can be seen from the background art, there are two main service drainage manners, which are a DNS resolution drainage manner and a dynamic routing manner.

At present, due to the maturity of Content Delivery Network (CDN) services, a DNS resolution drainage method is most widely used, and the service drainage method has the following problems:

1) terminal equipment application is required to support DNS domain name access, and in the scene of the Internet of things, part of terminal equipment possibly does not support DNS domain name access due to limited capability;

2) the switching speed is limited by the updating speed of the DNS, the switching time delay of more than a minute level can be reached, and service failure can be caused in some scenes;

3) load drainage mainly according to network performance indexes cannot support richer application level drainage strategies.

And the dynamic routing mode is less adopted, and the service drainage mode has the following problems:

1) the network routing equipment is required to participate in network routing calculation and is relied on;

2) the complexity is high, generally used for supporting a primary and standby server scenario, and it is difficult to support a multi-active server scenario, and in an access scenario based on the MEC, an edge access application server is multi-active.

Based on this, the embodiment of the present invention provides a new service node allocation scheme based on MEC, and the following will clearly and completely describe the technical solution in the embodiment of the present invention with reference to the drawings in the embodiment of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

First, a service node allocation method based on MEC provided in an embodiment of the present invention is described below.

It should be noted that the service node allocation method based on the MEC provided by the embodiment of the present invention may be applied to a service drainage system, where the service drainage system is configured to drain the application of the terminal device to the service node for processing under the scheduling of the cloud server according to the network index information provided by the MEC server, so as to save traffic of service interaction between the terminal device and the cloud server, reduce time delay of the service interaction, and reduce service pressure of the cloud server.

The service drainage system comprises a cloud server, an MEC server, terminal equipment and at least one service node, wherein the service node is a logical application server and can be called as an edge access application server, and the edge access application server is used for accessing the terminal equipment application distributed by the cloud server to achieve the purpose of service drainage.

Referring to fig. 1, a flowchart of a service node allocation method based on MEC according to an embodiment of the present invention is shown. Applied to a cloud server, as shown in fig. 1, the method may include the following steps:

step 101, receiving a login request sent by terminal equipment; and the login request comprises identification information of the terminal equipment.

In order to realize service processing, the terminal device application can initiate a login request to the cloud server, wherein the login request carries identification information of the terminal device; correspondingly, the cloud server receives the login request sent by the terminal equipment.

The Identification information may only include a network identifier, such as an IP address or a port number of the terminal device, or may only include a device identifier, such as an International Mobile Subscriber Identity (IMSI) or a unique Identity ID (Identity), or may include both a network identifier and a device identifier, which is not limited herein.

In addition, the terminal device application may be any application on the terminal device, for example, the terminal device application may be a pay-for-use application, a WeChat application, or the like.

Step 102, receiving network index information of at least one service node managed and controlled by the MEC server, which is fed back by the mobile edge computing MEC server based on a query request; the query request includes the identification information, and the network index information of each service node includes network performance metric information from the terminal device corresponding to the identification information to the service node.

After the cloud server acquires the login request, triggering a query request and sending the query request to the MEC server, wherein 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 queries and obtains 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 comprises network performance measurement information from the terminal device corresponding to the identification information to the service node.

Here, the network index information of the service node at least includes network performance metric information from the terminal device corresponding to the identification information to the service node, and meanwhile, the network index information of the service node may further include load information of an edge data center where the service node is located.

The network performance metric information may include information such as network delay and network distance from the terminal device to the service node, and the load information may include information such as working delay and service state of the service node itself.

Specifically, the MEC server may query, based on the identification information and the application identification information, network performance metric information from the terminal device corresponding to the identification information to each service node of the application corresponding to the application identification information, and may further obtain load information of an 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 of time period, and accordingly, the MEC server can obtain the load information.

The MEC server can feed back network index information of at least one service node according to the query request. For example, the query request may further include feedback policy information, for example, the feedback policy information may indicate that the MEC server feeds back the network index information of all service nodes that can be queried, and the feedback policy information may also indicate that the MEC server feeds back the network index information of some service nodes.

Furthermore, there are two ways to feed back the network index information of part of the service nodes according to the feedback strategy information.

The first mode is as follows: the feedback policy information may include a first network index threshold, and correspondingly, the MEC server only needs to feed back the network index information of the service node whose network index information satisfies the first network index threshold. The first network index threshold may only include the first threshold, and correspondingly, the MEC server only needs to feed back the network index information of the service node whose network performance metric information satisfies the first threshold in the network index information. The first network index threshold may include a first threshold and a second threshold, and the MEC server only needs to feed back the network index information of the service node whose network performance metric information in the network index information satisfies the first threshold and whose load information in the network index information satisfies the second threshold.

The second way is: the MEC server can comprehensively consider the network performance measurement information and the load information of each service node, rank each service node, and feed back the network index information of N service nodes before ranking, wherein N is a positive integer greater than or equal to N. For example, the MEC may set the weight values of the network performance metric information and the load information, determine the quality of the network of each service node based on a weighting manner, arrange each service node according to the quality of the network, arrange the service node with the best network in the first name, and arrange the service node with the worst network in the last name.

After the MEC server acquires the network index information of at least one service node, the network index information of the at least one service node is fed back to the cloud server, and correspondingly, the cloud server can receive the network index information of the at least one service node.

103, selecting a target service node for the terminal equipment 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.

Here, 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 drainage policy preset by the cloud server.

The cloud server can be used for setting three drainage strategies in advance, the drainage strategies are flexible, and application-level strategy drainage of user granularity is supported.

A first drainage strategy may be: and selecting a target service node for the terminal equipment only according to the network index information of the service node.

Specifically, 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:

determining a service node with the best network index information in the at least one service node;

and determining the service node with the best network index information in the at least one service node as a target service node accessed by the terminal equipment.

The cloud server may set a network performance metric index and a weight of load information, determine whether a network of each service node in the at least one service node is good or bad based on a weighting manner, select a service node with the best network index information in the at least one service node, and determine the service node with the best network index information in the at least one service node as a target service node to which the terminal device is accessed.

A second drainage strategy may be: and selecting a target service node for the terminal equipment according to the network index information of the service node and the grade of the terminal equipment.

acquiring the grade of the terminal equipment; wherein the grade is used for reflecting the importance degree of the terminal equipment to the application processing;

determining a service node of the at least one service node, wherein the network index information of the service node is matched with the grade of the terminal equipment;

and determining the service node matched with the grade of the terminal equipment as a target service node accessed by the terminal equipment.

The grade of the terminal device is used for reflecting the importance degree of the terminal device for application processing, and may be an importance grade, a common grade, or other grades such as an overweight grade, and is not specifically limited herein. The terminal device of the important class may have a greater processing urgency than the terminal device of the normal class, and needs priority processing or quick 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 a mapping table of the identification information and the level of the terminal device, and based on the identification information, the level of the terminal device may be queried in the mapping table.

The cloud server can set a network performance metric index and a weight of load information, determine the quality of the network of each service node in the at least one service node based on a weighting mode, and sort the service nodes based on the quality of the network of each service node. And matching service nodes corresponding to the grade of the terminal equipment based on the sorted service nodes.

It should be noted that the service node corresponding to the terminal device class may include only one service node, or include a plurality of service nodes, and is not specifically limited herein. For example, the sequenced service nodes include a service node 1, a service node 2, a service node 3, and a service node 4, and for the terminal device of the important level, only the service node 1 and the service node 2 with better network index information can meet the requirement of the terminal device, that is, the service node 1 and the service node 2 are matched with the terminal device; for a terminal device of a common class, since the performance requirement of the terminal device for application processing is not very high, the service node 3 and the service node 4 with general network index information can meet the requirement of the terminal device, that is, the service node 3 and the service node 4 are matched with the terminal device.

When the service node corresponding to the level of the terminal device includes a plurality of service nodes, the cloud server may determine any one of the plurality of service nodes corresponding to the level of the terminal device as the service node whose network index information matches the level of the terminal device in the at least one service node, or may determine the service node whose network index information is the best in the plurality of service nodes corresponding to the level of the terminal device as the service node whose network index information matches the level of the terminal device in the at least one service node, which is not specifically limited herein.

Of course, the cloud server may also determine a plurality of service nodes corresponding to the class of the terminal device as target service nodes to which the terminal device is accessed, and correspondingly, send the access identifier of each target service node to the terminal device, so that the terminal device accesses the target service nodes based on any access identifier of the access identifiers of each target service node.

A third drainage strategy may be: and selecting a target service node for the terminal equipment according to the network index information of the service node and the characteristic information of the terminal equipment.

determining characteristic information of the terminal equipment based on historical setting data of the terminal equipment; the characteristic information is used for reflecting the performance requirement of the terminal equipment on the network;

determining a service node of the at least one service node, wherein the network index information is matched with the characteristic information;

and determining the service node matched with the characteristic information as a target service node accessed by the terminal equipment.

The cloud server can count the historical setting data of the terminal equipment and determine the characteristic information of the terminal equipment, wherein the characteristic information is used for reflecting the performance requirement of the terminal equipment on the network. For example, for a video playing application, the preference setting of the terminal device for video definition is 1080P, the cloud server counts historical setting data of the terminal device for the video playing application, determines the preference setting of the terminal device for the video playing application, where the preference setting is feature information of the terminal device for the video playing application, and the feature information may include the preference setting 1080P of video definition, that is, the cloud server may determine that the performance requirement of the terminal device for a network is high based on the preference setting 1080P of video definition in the feature information.

Further, the cloud server may determine a second network index threshold based on the feature information, determine that the network index information matches the feature information when the network index information of a service node existing in the at least one service node is greater than the second network index threshold, and correspondingly determine a service node corresponding to the network index information matching the feature information as a target service node.

And step 104, sending an access identifier of the target service node to the terminal device, where the access identifier is used to indicate that the terminal device accesses the target service node.

After determining a target service node, the cloud server sends an access identifier of the target service node to the terminal device, where the access identifier may be an IP address of the target service node.

Correspondingly, the terminal device may receive the access identifier of the target service node, and access the target service node to perform a service session based on the access identifier, thereby implementing processing of the terminal device application.

In addition, the cloud server may also provide return information of the login information to the application of the terminal device, and if the return information of the login information includes an encryption key, the terminal device receives the return information, and in addition, in order to implement processing of the application service of the terminal device by the target service node, the cloud server needs to send the service processing information associated with the terminal device to the target service node, wherein the service processing information includes the login information of the terminal device application and the return information of the login information, so as to synchronize the login information of the terminal device, and meanwhile, the service processing information further includes information required by the application service of the terminal device.

According to the service node distribution method based on the MEC, when the terminal device application logs in the cloud server, the cloud server distributes the service nodes for the terminal device according to the network index information provided by the MEC server to complete service drainage, and compared with a DNS (domain name system) resolution drainage mode, the method is not required to be used for supporting DNS (domain name system) domain name access by the terminal application, is also suitable for the terminal device which does not support DNS domain name access in the scene of the internet of things, and is not required to depend on the updating speed of the DNS. Compared with a dynamic routing mode, the method does not need to rely on network routing equipment, is not limited by application scenes, and can support multi-live server scenes. Therefore, the embodiment of the invention can improve the flexibility of service drainage, is simple to realize and high in switching speed, and the terminal equipment application can autonomously initiate drainage updating at any time and quickly respond to the requirement of the terminal equipment. Moreover, the drainage strategy is flexible, and application-level strategy drainage of user granularity is supported.

Referring to fig. 2, a second flowchart of the service node allocation method based on MEC according to the embodiment of the present invention is shown. Applied to an MEC server, as shown in fig. 2, the method may include the steps of:

step 201, receiving a query request sent by a cloud server; the query request comprises identification information of the terminal equipment;

step 202, inquiring and obtaining network index information of at least one service node managed and controlled by the MEC server based on the inquiry request; the network index information of each service node comprises network performance measurement information from the terminal equipment corresponding to the identification information to the service node;

step 203, sending the network index information of the at least one service node to a cloud server; the network index information of the at least one service node is used for indicating the cloud server to select a target service node for the terminal device.

The network index information of at least one service node comprises the network index information of the service node of which the network index information meets a preset threshold value; alternatively, the first and second electrodes may be,

the network index information of the at least one service node comprises the network index information of the first N service nodes in the service nodes ranked according to the network index information; wherein N is a positive integer greater than or equal to 1.

It should be noted that the preset threshold is the first network indicator threshold described in the first embodiment. The above-described specific control process is similar to the embodiment, and the detailed description thereof is omitted here.

In the embodiment of the invention, when the terminal device application logs in the cloud server, the cloud server allocates the service nodes for the terminal device according to the network index information provided by the MEC server to complete service drainage, and compared with a DNS (domain name system) analysis drainage mode, the terminal device does not need to support DNS domain name access by the terminal application, is also suitable for the terminal device which does not support DNS domain name access in the scene of the internet of things, and does not need to rely on the updating speed of the DNS. Compared with a dynamic routing mode, the method does not need to rely on network routing equipment, is not limited by application scenes, and can support multi-live server scenes. Therefore, the embodiment of the invention can improve the flexibility of service drainage, is simple to realize and high in switching speed, and the terminal equipment application can autonomously initiate drainage updating at any time and quickly respond to the requirement of the terminal equipment.

The following describes an example of a service node allocation method based on MEC according to an embodiment of the present invention in detail.

Application scenarios: referring to fig. 3, a schematic structural diagram of a service drainage system applied to the MEC-based service node allocation method according to the embodiment of the present invention is shown in the drawing, and as shown in fig. 3, the service drainage system includes: the system comprises terminal equipment, a cloud server, an MEC server and an edge access application server. Referring to fig. 4, a timing diagram of the service node allocation method based on MEC according to the embodiment of the present invention is shown in the diagram, and as shown in fig. 4, the method is applied to a service drainage system, and a flow of the method specifically includes:

firstly, terminal equipment sends a login request to a cloud server; the login request comprises identification information of the terminal device, wherein the identification information may comprise a network identification and/or a device identification;

then, the cloud server initiates a query request to the MEC server according to the identification information; the query request comprises identification information and application identification information of the terminal equipment;

then, the MEC server inquires and obtains 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;

then, the cloud server receives the network index information of the at least one edge access application server, and selects a target edge access application server for the terminal equipment according to a preset drainage strategy based on the network index information of the at least one edge access application server;

then, sending the access identifier of the target edge access application server to the terminal equipment, and synchronizing the service processing information to the target edge access application server;

and finally, the terminal equipment receives the access identifier of the target edge access application server and accesses to the target edge access application server to perform service session based on the access identifier.

The foregoing embodiment describes in detail an implementation process in which the terminal device logs in the cloud server, and the cloud server allocates the target service node to the terminal device by using the MEC server, and it should be noted that the following embodiment describes in detail an implementation process in which the terminal device logs in the MEC server, and the MEC server directly allocates the target service node to the terminal device.

Specifically, referring to fig. 5, a third flowchart of the service node allocation method based on MEC according to the embodiment of the present invention is shown in the drawing. Applied to the MEC server, as shown in fig. 5, the method may include the steps of:

step 501, acquiring a query request sent by a terminal device; the query request comprises identification information of the terminal equipment and identification information of a target service application;

step 502, based on the query request, querying network index information of at least one service node managed and controlled by the MEC server based on the service application corresponding to the identification information of the target service application; the network index information of each service node comprises network performance measurement information from the terminal equipment corresponding to the identification information to the service node;

step 503, selecting 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;

step 504, sending 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.

In step 501, in order to implement service processing, a terminal device application may initiate a query request to an MEC server, where the query request carries identification information of the terminal device and identification information of a target service application; correspondingly, the MEC server receives the query request sent by the terminal equipment.

The Identification information of the terminal device may only include a network identifier, such as an IP address or a port number of the terminal device, or only include a device identifier, such as an International Mobile Subscriber Identity (IMSI) or a unique Identity ID (Identity), or both, and the Identification information of the terminal device may also include a network identifier and a device identifier, which is not limited specifically herein.

The identification information of the target service application may be used to instruct the MEC server to query network index information of a specific service node managed and controlled by the MEC server, and the target service application may be any application on the terminal device, for example, the target service application may be a pay bank application, a wechat application, or the like.

In step 502, an 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 above embodiment, and a specific implementation process is not repeated. Only the triggering conditions for triggering the MEC server to query are different, the triggering condition for triggering the MEC server to query in the above embodiment is the query request sent by the cloud server, and the triggering condition for triggering the MEC server to query in the embodiment is the query request sent by the terminal device.

In step 503 and step 504, similar to the implementation process of the above embodiment, the specific implementation process is not described again. The implementation is only different in subject, the above embodiment is implemented by running a processor of the cloud server, and the embodiment is implemented by running a processor of the MEC server.

In the embodiment of the invention, the MEC server inquires the network index information based on the inquiry request sent by the terminal equipment, and allocates the service node for the terminal equipment according to the network index information to complete service drainage, so that compared with a DNS (domain name system) analysis drainage mode, the MEC server does not need a terminal application to support DNS (domain name system) domain name access, is also suitable for the terminal equipment which does not support DNS domain name access in the scene of the Internet of things, and does not need to depend on the updating speed of the DNS. Compared with a dynamic routing mode, the method does not need to rely on network routing equipment, is not limited by application scenes, and can support multi-live server scenes. Therefore, the embodiment of the invention can improve the flexibility of service drainage, is simple to realize and high in switching speed, and the terminal equipment application can autonomously initiate drainage updating at any time and quickly respond to the requirement of the terminal equipment.

Optionally, 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:

It should be noted that, based on the network index information of the at least one service node, the MEC server may preset a drainage policy for selecting a target service node for the terminal device, where the drainage policy may be set to be consistent with the cloud server, and therefore, a process of specifically selecting the target service node is similar to that in the foregoing embodiment, and is not described herein again.

Optionally, after the sending the access identifier of the target service node to the terminal device, the method further includes:

and sending the access identifier of the target service node to a cloud server.

Here, the MEC server sends the access identifier of the target service node to a cloud server, so that the cloud server can send the business processing information associated with the terminal device to the target service node, where the business processing information includes login information applied by the terminal device and return information of the login information to synchronize the login information of the terminal device, and the business processing information further includes information required by an application business of the terminal device.

The following describes a service node allocation apparatus based on MEC according to an embodiment of the present invention.

Referring to fig. 6, a schematic structural diagram of a service node allocation apparatus based on MEC according to an embodiment of the present invention is shown. Applied to a cloud server, as shown in fig. 6, the service node allocation apparatus 600 based on MEC includes:

a first receiving module 601, configured to receive a login request sent by a terminal device; the login request comprises identification information of the terminal equipment;

a second receiving module 602, configured to receive network index information of at least one service node managed and controlled by the MEC server, which is fed back by the mobile edge computing MEC server based on the query request; the query request comprises the identification information, and the network index information of each service node comprises network performance measurement information from the terminal equipment corresponding to the identification information to the service node;

a first selecting module 603, 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;

a first sending module 604, configured to send an access identifier of the target service node to the terminal device, where the access identifier is used to indicate that the terminal device accesses the target service node.

Optionally, the first selecting module 603 includes:

the first determining unit is used for determining a service node with the best network index information in the at least one service node;

a second determining unit, configured to determine a service node with the best network indicator information among the at least one service node as a target service node accessed by the terminal device.

Optionally, the first selecting module 603 includes:

an obtaining unit, configured to obtain a class of the terminal device; wherein the grade is used for reflecting the importance degree of the terminal equipment to the application processing;

a third determining unit, configured to determine a service node in the at least one service node where the network index information matches the rank of the terminal device;

a fourth determining unit, configured to determine a service node that matches the class of the terminal device as a target service node to which the terminal device accesses.

Optionally, the first selecting module 603 includes:

a fifth determining unit configured to determine feature information of the terminal device based on history setting data of the terminal device; the characteristic information is used for reflecting the performance requirement of the terminal equipment on the network;

a sixth determining unit, configured to determine a service node of the at least one service node where the network indicator information matches the feature information;

and a seventh determining unit, configured to determine a service node matching the feature information as a target service node accessed by the terminal device.

Optionally, the apparatus further comprises:

and the fourth sending module is used for sending the service processing information associated with the terminal equipment to the target service node.

The service node allocation device based on the MEC provided by the embodiment of the invention can realize each process realized in the method embodiment of the cloud server side, and is not described herein again in order to avoid repetition.

Referring to fig. 7, a second schematic structural diagram of a service node allocation apparatus based on MEC according to an embodiment of the present invention is shown. As shown in fig. 7, the MEC-based service node allocating apparatus 700 applied to the MEC server includes:

a third receiving module 701, configured to receive a query request sent by a cloud server; the query request comprises identification information of the terminal equipment;

a first query module 702, 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; the network index information of each service node comprises network performance measurement information from the terminal equipment corresponding to the identification information to the service node;

a second sending module 703, configured to send the network index information of the at least one service node to a cloud server; the network index information of the at least one service node is used for indicating the cloud server to select a target service node for the terminal device.

Optionally, the network index information of the at least one service node includes network index information of a service node whose network index information meets a preset threshold; alternatively, the first and second electrodes may be,

The service node allocation device based on the MEC provided by the embodiment of the present invention can implement each process implemented in the embodiment of the method on the MEC server side, and is not described herein again to avoid repetition.

According to the service node distribution device based on the MEC, provided by the embodiment of the invention, when the terminal equipment application logs in the cloud server, the cloud server distributes the service nodes for the terminal equipment according to the network index information provided by the MEC server to complete service drainage, and compared with a DNS (domain name system) resolution drainage mode, the device does not need the terminal application to support DNS (domain name system) domain name access, is also suitable for the terminal equipment which does not support the DNS domain name access in the scene of the internet of things, and does not need to rely on the updating speed of the DNS. Compared with a dynamic routing mode, the method does not need to rely on network routing equipment, is not limited by application scenes, and can support multi-live server scenes. Therefore, the embodiment of the invention can improve the flexibility of service drainage, is simple to realize and high in switching speed, and the terminal equipment application can autonomously initiate drainage updating at any time and quickly respond to the requirement of the terminal equipment. Moreover, the drainage strategy is flexible, and application-level strategy drainage of user granularity is supported.

Referring to fig. 8, a third schematic structural diagram of a service node allocation apparatus based on MEC according to an embodiment of the present invention is shown. As shown in fig. 8, the MEC-based service node allocating apparatus 800 applied to the MEC server includes:

an obtaining module 801, configured to obtain an inquiry request sent by a terminal device; the query request comprises identification information of the terminal equipment and identification information of a target service application;

a second query module 802, configured to query, based on the query request, network index information of at least one service node managed and controlled by the MEC server based on the service application corresponding to the identification information of the target service application; the network index information of each service node comprises network performance measurement information from the terminal equipment corresponding to the identification information to the service node;

a second selecting module 803, 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;

a third sending module 804, configured to send an access identifier of the target service node to the terminal device, where the access identifier is used to indicate that the terminal device accesses the target service node.

Optionally, the second selecting module 803 is specifically configured to determine a service node with the best network index information in the at least one service node; and determining the service node with the best network index information in the at least one service node as a target service node accessed by the terminal equipment.

Optionally, the second selecting module 803 is specifically configured to obtain a grade of the terminal device; wherein the grade is used for reflecting the importance degree of the terminal equipment to the application processing; determining a service node of the at least one service node, wherein the network index information of the service node is matched with the grade of the terminal equipment; and determining the service node matched with the grade of the terminal equipment as a target service node accessed by the terminal equipment.

Optionally, the second selecting module 803 is specifically configured to determine feature information of the terminal device based on historical setting data of the terminal device; the characteristic information is used for reflecting the performance requirement of the terminal equipment on the network; determining a service node of the at least one service node, wherein the network index information is matched with the characteristic information; and determining the service node matched with the characteristic information as a target service node accessed by the terminal equipment.

Optionally, the apparatus further comprises:

and the fifth sending module is used for sending the access identifier of the target service node to a cloud server.

Referring to fig. 9, a schematic structural diagram of a cloud server provided in the embodiment of the present invention is shown in the drawing. As shown in fig. 9, 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 the program in the first memory 902, and execute the following processes:

In fig. 9, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by the first processor 901 and various circuits of the memory represented by the first memory 902 being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The first bus interface 904 provides an interface. For different user devices, the first user interface 903 may also be an interface capable of interfacing with a desired device, including but not limited to a keypad, a display, a speaker, a microphone, a joystick, etc.

The first processor 901 is responsible for managing a bus architecture and general processing, and the first memory 902 may store data used by the first processor 901 when performing operations.

Optionally, the first processor 901 is specifically configured to:

A first processor 901, further configured to:

and sending the service processing information associated with the terminal equipment to the target service node.

Preferably, an embodiment of the present invention further provides a cloud server, which includes a first processor 901, a first memory 902, and a computer program that is stored in the first memory 902 and is capable of running on the first processor 901, and when the computer program is executed by the first processor 901, the computer program implements each process of the embodiment of the service node allocation method based on MEC on the cloud server side, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

Referring to fig. 10, a schematic structural diagram of an MEC server provided by an embodiment of the present invention is shown. As shown in fig. 10, 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, configured to read the program in the second memory 1002, executes the following processes:

Further, the second processor 1001, configured to read the program in the second memory 1002, further performs the following processes:

The second processor 1001 is specifically configured to:

The second processor 1001 is further configured to:

and sending the access identifier of the target service node to a cloud server.

In fig. 10, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by the second processor 1001 and various circuits of the memory represented by the second memory 1002 being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. A second bus interface 1004 provides an interface. For different user devices, the second user interface 1003 may also be an interface capable of externally connecting a desired device, including but not limited to a keypad, a display, a speaker, a microphone, a joystick, etc.

The second processor 1001 is responsible for managing a bus architecture and general processing, and the second memory 1002 may store data used by the second processor 1001 when performing operations.

Preferably, an embodiment of the present invention further provides an MEC server, including a second processor 1001, a second memory 1002, and a computer program stored in the second memory 1002 and capable of running on the second processor 1001, where the computer program, when executed by the second processor 1001, implements each process of the embodiment of the service node allocation method based on MEC at the MEC server side, and can achieve the same technical effect, and in order to avoid repetition, details are not described here again.

The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when executed by the first processor, the computer program implements each process of the embodiment of the service node allocation method based on the MEC on the cloud server side, and can achieve the same technical effect, and in order to avoid repetition, the description is omitted here, or when executed by the second processor, the computer program implements each process of the embodiment of the service node allocation method based on the MEC server side, and can achieve the same technical effect. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the embodiments provided in the present application, it should be understood that the disclosed system and method may be implemented in other ways. For example, the above-described system embodiments are merely illustrative, and for example, the division of the units is only one logical functional division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment of the present invention.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A service node distribution method based on MEC is applied to a cloud server, and is characterized by comprising the following steps:

2. The method of claim 1, wherein the step of selecting the target serving node for the terminal device based on the network index information of the at least one serving node comprises:

3. The method of claim 1, wherein the step of selecting the target serving node for the terminal device based on the network index information of the at least one serving node comprises:

4. The method of claim 1, wherein the step of selecting the target serving node for the terminal device based on the network index information of the at least one serving node comprises:

5. The method of claim 1, wherein after sending the access identifier of the target serving node to the terminal device, the method further comprises:

6. A service node distribution method based on MEC is applied to a mobile edge computing MEC server, and is characterized in that the method comprises the following steps:

7. The method of claim 6, wherein the network index information of the at least one service node comprises network index information of service nodes whose network index information meets a preset threshold; alternatively, the first and second electrodes may be,

8. A service node distribution method based on MEC is applied to a mobile edge computing MEC server, and is characterized in that the method comprises the following steps:

9. The method of claim 8, wherein the step of selecting the target serving node for the terminal device based on the network index information of the at least one serving node comprises:

10. The method of claim 8, wherein the step of selecting the target serving node for the terminal device based on the network index information of the at least one serving node comprises:

11. The method of claim 8, wherein the step of selecting the target serving node for the terminal device based on the network index information of the at least one serving node comprises:

12. The method of claim 8, wherein after sending the access identifier of the target serving node to the terminal device, the method further comprises:

and sending the access identifier of the target service node to a cloud server.

13. The utility model provides a service node distribution device based on MEC, is applied to the high in the clouds server, its characterized in that, the device includes:

14. An MEC-based service node distribution device applied to a mobile edge computing MEC server, the device comprising:

15. An MEC-based service node distribution device applied to a mobile edge computing MEC server, the device comprising:

16. Cloud server, comprising a first processor, a first memory, a computer program stored on the first memory and executable on the first processor, the computer program, when executed by the first processor, implementing the steps of the MEC-based service node allocation method according to any one of claims 1 to 5.

17. A mobile edge computing, MEC, server comprising a second processor, a second memory, a computer program stored on said second memory and executable on said second processor, said computer program, when executed by said second processor, implementing the steps of the MEC based service node allocation method according to any of the claims 6 to 12.

18. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a first processor, carries out the steps of the MEC based service node allocation method according to any one of claims 1 to 5, or which, when executed by a second processor, carries out the steps of the MEC based service node allocation method according to any one of claims 6 to 12.