CN111836261B

CN111836261B - Data management method, LEPM and MEPM

Info

Publication number: CN111836261B
Application number: CN201910324562.4A
Authority: CN
Inventors: 赵凯
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-04-22
Filing date: 2019-04-22
Publication date: 2021-10-15
Anticipated expiration: 2039-04-22
Also published as: WO2020216038A1; CN111836261A

Abstract

The embodiment of the application discloses a data management method, an LEPM and an MEPM, which are used for reducing the management load of the MEPM. The method in the embodiment of the application comprises the following steps: a local edge platform manager receives a management command sent by a mobile edge platform manager, wherein the management command is a management task distributed to the local edge platform manager by the mobile edge platform manager; the local edge platform manager executes corresponding operation according to the management command; the local edge platform manager sends a management command response message to the mobile edge platform manager, wherein the management command response message is used for informing the mobile edge platform manager that the local edge platform manager executes corresponding operation completion and the mobile edge platform manager updates data of the mobile edge platform manager.

Description

Data management method, LEPM and MEPM

Technical Field

The present application relates to the field of communications technologies, and in particular, to a data management method, an LEPM, and an MEPM.

Background

Mobile-edge computing (MEC) provides services and cloud computing functions required by a user nearby by using a wireless access network. After the cloud computing function is deployed to the edge of the network, a carrier-class service environment with high performance, low time delay and high bandwidth can be created, the rapid downloading of various contents, services and applications in the network is accelerated, and consumers can enjoy higher-quality network experience.

Currently, the mobile edge computing architecture is mainly composed of two parts: a mobile edge host and a mobile edge computing management system. A mobile edge host is an entity that contains the mobile edge platform and the virtualization infrastructure, providing computing, storage, and network resources for MEC applications. The mobile edge computing management system includes an MEC orchestrator (multi-access edge manager), a Mobile Edge Platform Manager (MEPM), a Virtual Infrastructure Manager (VIM), and the like. The MEC orchestrator is used for maintaining an overall view of all mobile edge hosts, available resources and available MEC services in the MEC system, and triggering instantiation and termination of applications. The MEPM is used to manage the MEC platform, manage the lifecycle of MEC applications, manage the flow rules and Domain Name Service (DNS) rules of MEC applications. Currently, a mobile edge host connects to the MEPM, and then the MEC application on the mobile edge host is managed by the MEPM. For example, the MEPM may issue management commands such as deployment installation, start stop, uninstallation deletion, elastic scaling, capacity expansion, and the like of the MEC application to the mobile edge host, and the local mobile edge platform local to the mobile edge host processes the commands to perform operations such as lifecycle management and running condition monitoring of the local edge application. The MEPM takes centralized control over the mobile edge hosts and records data for all mobile edge hosts, MEC applications, it manages.

However, in the existing architecture, the MEPM is connected with the mobile edge host, and then the MEPM performs corresponding management operations on the mobile edge host and the MEC application on the mobile edge host. When the number of the mobile edge hosts is large and the scale is large, the management load of the MEPM is increased, and the MEPM is very likely to become a bottleneck of the performance of the whole network, so that the problems of slow response, increased time delay and the like of the management action of the MEPM are caused.

Disclosure of Invention

The embodiment of the application provides a data management method, an LEPM and an MEPM, which are used for reducing the management load of the MEPM and avoiding or preventing the MEPM from becoming the bottleneck of the whole network performance and the problems of slow response, increased time delay and the like of the management action of the MEPM.

A first aspect of an embodiment of the present application provides a data management method, including:

the LEPM receives a management command sent by the MEPM, and the management command is a management task distributed by the MEPM for the LEPM; then, the LEPM executes corresponding operation according to the management command, and then sends a management command response message to the MEPM, wherein the management command response message is used for notifying the MEPM that the LEPM executes corresponding operation completion and the MEPM updates data of the MEPM. Therefore, in the technical solution of the present application, the LEPM receives the management command sent by the MEPM, and executes the corresponding operation according to the management command, and the MEPM does not need to execute the management operation, thereby reducing the management load of the MEPM, and avoiding or preventing the MEPM from becoming a bottleneck of the overall network performance, and the problems of slow response of the management action of the MEPM, increased delay, and the like.

In a possible implementation manner of the first aspect, before the LEPM receives the management command sent by the MEPM, the method further includes: firstly, the LEPM sends a registration request message to the MEPM, wherein the registration request message comprises an access address and position information of the LEPM and information of a mobile edge host managed by the LEPM; the LEPM then receives a registration response message sent by the MEPM, which determines the identity assigned by the MEPM to the LEPM based on the registration response message. In this possible implementation, a specific registration procedure of the LEPM is provided, so that the MEPM issues a management command to the LEPM, and the LEPM performs a management operation, thereby reducing the management load of the LEPM.

In another possible implementation manner of the first aspect, the registration request message further includes an identity certificate of the LEPM or attribute information of the LEPM; the authentication data is used for the MEPM to authenticate the LEPM. In this possible implementation, by performing authentication on the LEPM, security of LEPM registration is improved, preventing an illegal edge device from also registering in the network.

In another possible implementation manner of the first aspect, the management command includes an application instantiation command, where the application instantiation command carries information of the MEC application requested to be created; the LEPM executing corresponding operations according to the management command comprises the following steps: the LEPM applies for resources for the MEC application according to the information of the MEC application, creates the MEC application through the resources and runs the MEC application; the LEPM sending a management command response message to the MEPM includes: the LEPM sends application instance data for the MEC application to the MEPM. In this possible implementation, a specific procedure is provided for executing the management operations instantiated by the application by the LEPM.

In another possible implementation manner of the first aspect, the management command includes an application instance termination command, and the application instance termination command carries an identifier of the MEC application; the LEPM executing corresponding operations according to the management command comprises the following steps: and the LEPM uninstalls the MEC application according to the identification of the MEC application and releases the resources occupied by the MEC application. In this possible implementation, this provides a specific procedure for execution by the LEPM of the management operation terminated by the application instance.

In another possible implementation manner of the first aspect, before the LEPM receives the management command sent by the MEPM, the method further includes: the LEPM receives a subscription indication message sent by the MEPM, wherein the subscription indication message is used for indicating that when change data exists in the LEPM, the LEPM sends the change notification message to the MEPM, and the change data comprises information of a change edge host managed by the LEPM, application instance data of a change MEC application or running state data of the change MEC application. In this possible implementation, the MEPM may synchronize data with the LEPM by subscribing to change data.

In another possible implementation manner of the first aspect, after the LEPM sends the management response message to the MEPM, the method further includes: the LEPM determining that there is change data for the LEPM; the LEPM then sends a change notification message to the MEPM, the change notification message notifying the MEPM that the LEPM has changed data. In this possible implementation, the LEPM informs the MEPM that there is change data for the LEPM by sending a notification message to the MEPM.

In another possible implementation manner of the first aspect, the change notification message carries the change data, and the change data is used for the MEPM to update the data of the LEPM stored by the MEPM. In this possible implementation, the notification message directly carries the change data, and the MEPM may update the local data according to the notification message.

In another possible implementation manner of the first aspect, before the LEPM determines that there is change data for the LEPM, the method further includes: firstly, the LEPM acquires index data for changing the MEC application; then, the LEPM allocates an application instance to the changed MEC application or releases the application instance of the changed MEC application according to the index data and a preset elastic scaling rule. In this possible implementation manner, the LEPM performs elastic scaling control on the managed application instance of the changed MEC application according to a preset elastic scaling rule and index data of the changed MEC application, and it is not necessary for the MEP to report the index data of the changed MEC application to the MEPM, that is, it is not necessary for the MEPM to perform elastic scaling control on the application instance of the changed MEC application, so as to reduce the management load of the MEPM.

A second aspect of an embodiment of the present application provides a data management method, including:

the MEPM sends a management command to the LEPM, and the management command is a management task distributed by the MEPM to the LEPM; then, the MEPM receives the management command response message sent by the LEPM, and updates the data of the MEPM according to the management command response message. In the technical scheme of the application, the MEPM issues a management command to the LEPM so that the LEPM executes corresponding operation according to the management command. Therefore, management operation does not need to be executed by the MEPM, so that the management load of the MEPM is reduced, and the problems that the MEPM becomes a bottleneck of the whole network performance, the management action of the MEPM is slow in response, the time delay is increased and the like are avoided or prevented.

In one possible implementation manner of the second aspect, before the MEPM sends the management command to the LEPM, the method further includes: the MEPM receives a registration request message sent by the LEPM, wherein the registration request message carries the access address and the position information of the LEPM and the information of the mobile edge host managed by the LEPM; then, the MEPM determines that the LEPM is an LEPM managed by the MEPM according to the location information, and sends a registration response message to the LEPM through the access address, wherein the registration response message carries the identifier allocated by the MEPM to the LEPM. In this possible implementation, a process is provided in which the MEPM registers and assigns an identity to the LEPM.

In a possible implementation manner of the second aspect, the registration request message further includes identity authentication data of the LEPM; before the MEPM sends a registration response message to the LEPM through the access address, the method further comprises: the MEPM verifies the LEPM according to the identity authentication data to obtain a verification result; and the MEPM determines that the LEPM is successfully verified according to the verification result. In the possible implementation mode, before the MEPM allocates the identifier to the LEPM, the LEPM is authenticated, so that illegal equipment is prevented from being forged into the LEPM to be registered, and the security of the system is improved.

In one possible implementation of the second aspect, the management command comprises an application instantiation command; the MEPM receiving the management command sent by the LEPM comprises the following steps: the MEPM receives application instance data of the MEC application sent by the LEPM; the updating, by the MEPM according to the management response message, data of the MEPM includes: and the MEPM records the corresponding relation between the MEC application and the LEPM in the MEPM according to the application instance data and stores the application instance data of the MEC application. In this possible implementation manner, the MEPM may respond to the message about the application instance data of the MEC application and the corresponding relationship between the MEC application and the LEPM according to the management command, so that when the MEPM queries the application instance data of the MEC application or terminates the application instance of the MEC application, the LEPM may be determined according to the corresponding relationship, and a corresponding management command is issued to the LEPM.

In one possible implementation manner of the second aspect, before the MEPM sends the management command to the LEPM, the method further includes: firstly, the MEPM acquires an application instantiation command, wherein the application instantiation command carries the position information of a target mobile edge host corresponding to the MEC application which is requested to be created; the MEPM then determines an LEPM that manages the target mobile edge host based on the location information. In this possible implementation, a way is provided how the MEPM specifically determines to which LEPM to issue the application instantiation command.

In a possible implementation manner of the second aspect, the management command includes an application instance termination command, and the application instance termination command carries an identifier of the MEC application; the updating, by the MEPM according to the management response message, data of the MEPM includes: the MEPM deletes the corresponding relation between the MEC application corresponding to the identification and the LEPM stored by the MEPM and the application instance data of the MEC application.

In one possible implementation manner of the second aspect, before the MEPM sends the management command to the LEPM, the method further includes: the MEPM sends a subscription indication message to the LEPM, the subscription indication message indicating that the LEPM sends a change notification message to the MEPM when change data exists in the LEPM, the change data including information of a changing mobile edge host managed by the LEPM, application instance data of a changing MEC application managed by the LEPM, or running state data of the changing MEC application. In this possible implementation manner, a scheme is provided for implementing data synchronization by subscribing to the changed data by the MEPM.

In a possible implementation manner of the second aspect, after the MEPM updates the data of the MEPM according to the management command response message, the method further includes: firstly, the MEPM receives a change notification message sent by the LEPM, wherein the change notification message carries the change data; the MEPM then updates the data of the LEPM stored by the MEPM according to the change data. In this possible implementation, the MEPM updates the local data by a change notification message.

In a possible implementation manner of the second aspect, after the MEPM updates the data of the MEPM according to the management command response message, the method further includes: firstly, the MEPM receives a change notification message sent by the LEPM; then, the MEPM determines that the LEPM has change data according to the change notification message; the MEPM then obtains the changed data through the interface of the LEPM and updates its local data. In this possible implementation, the MEPM provides another way to achieve synchronization with the LEPM data by calling the LEPM's interface to obtain the change data and update its local data.

In one possible implementation manner of the second aspect, the method further includes: the MEPM acquires application instance data of the MEC application in the latest state and information of a mobile edge host managed by the LEPM by calling an interface of the LEPM according to a preset period; the MEPM then updates its data based on the application instance data of the MEC application in the up-to-date state and the information of the mobile edge host managed by the LEPM. In this possible implementation, another way is provided for the MEPM to update the local data to achieve synchronization with the LEPM data, and the MEPM actively and periodically obtains the latest state data from the LEPM and updates its local data.

A third aspect of an embodiment of the present application provides an LEPM, where the LEPM has a function of implementing the LEPM behavior of the first aspect, and the function may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions.

A fourth aspect of the embodiments of the present application provides an MEPM, where the MEPM has a function of implementing the behavior of the MEPM in the second aspect, and the function may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions.

A fifth aspect of an embodiment of the present application provides an LEPM, comprising: a processor, a memory, an input-output device, and a bus; the memory having stored therein computer instructions; when the processor executes the computer instructions in the memory, the memory stores the computer instructions; the processor, when executing the computer instructions in the memory, is adapted to implement any of the implementations of the first aspect.

In a possible implementation manner of the fifth aspect, the processor, the memory, and the input/output device are respectively connected to the bus.

A sixth aspect in an embodiment of the present application provides an MEPM, including: a processor, a memory, an input-output device, and a bus; the memory having stored therein computer instructions; when the processor executes the computer instructions in the memory, the memory stores the computer instructions; the processor, when executing the computer instructions in the memory, is adapted to implement an implementation as in any of the second aspects.

In a possible implementation manner of the sixth aspect, the processor, the memory, and the input/output device are respectively connected to the bus.

A seventh aspect of embodiments of the present application provides a data management system, including an LEPM according to the third aspect and an MEPM according to the fourth aspect.

An eighth aspect of embodiments of the present application provides a computer program product including instructions, which when run on a computer, causes the computer to perform the implementation manner as in any one of the first aspect or the second aspect.

A ninth aspect of embodiments of the present application provides a computer-readable storage medium, which is characterized by instructions that, when executed on a computer, cause the computer to perform the implementation manner as in any one of the first aspect or the second aspect.

According to the technical scheme, the embodiment of the application has the following advantages:

according to the technical scheme, the LEPM receives a management command sent by the MEPM, and the management command carries a management task distributed by the MEPM to the LEPM; then, the LEPM executes corresponding operation according to the management task and sends a management command response message to the MEPM, so that the MEPM updates local data according to the management command response message. Therefore, in the technical scheme of the application, the management command sent by the MEPM can be received by the LEPM, corresponding operation is executed according to the management command, and the management operation is not required to be executed by the MEPM, so that the management load of the MEPM is reduced, and the problems that the MEPM becomes the bottleneck of the whole network performance, the management action reaction of the MEPM is slow, the time delay is increased and the like are avoided or prevented.

Drawings

Fig. 1A is a schematic structural diagram of a management network of a mobile edge host according to an embodiment of the present application;

fig. 1B is another schematic structural diagram of a management network of a mobile edge host according to an embodiment of the present application;

FIG. 2 is a schematic diagram of an embodiment of a data management method according to an embodiment of the present application;

FIG. 3 is a schematic diagram of another embodiment of a data management method according to an embodiment of the present application;

FIG. 4 is a schematic diagram of another embodiment of a data management method according to an embodiment of the present application;

FIG. 5 is a schematic diagram of another embodiment of a data management method according to an embodiment of the present application;

FIG. 6 is a schematic diagram of another embodiment of a data management method according to an embodiment of the present application;

FIG. 7 is a schematic diagram of another embodiment of a data management method according to an embodiment of the present application;

FIG. 8 is a schematic diagram of the structure of an LEPM in an embodiment of the present application;

FIG. 9 is a schematic structural diagram of an MEPM in an embodiment of the present application;

FIG. 10 is another schematic diagram of the structure of an LEPM according to an embodiment of the present application;

FIG. 11 is another schematic diagram of the structure of an MEPM according to the embodiment of the present application;

fig. 12 is a schematic diagram of a data management system in an embodiment of the present application.

Detailed Description

The embodiment of the application provides a data management method and a data management device, which are used for reducing the management load of an MEPM and avoiding or preventing the MEPM from becoming the bottleneck of the whole network performance and the problems of slow response, increased time delay and the like of the management action of the MEPM.

Referring to fig. 1A, fig. 1A is a schematic structural diagram of a management network of a mobile edge host according to an embodiment of the present disclosure; the management network includes a mobile edge host, a Local Edge Platform Manager (LEPM), an MEPM, a VIM, and the like. The local edge platform manager LEPM1 is integrated in the mobile edge host 1, and has the capability of connecting with other mobile edge hosts in the area 1 and performing local small-scale management on the mobile edge hosts in the area 1. The LEPM1 primarily provides the following management capabilities: the method includes performing application lifecycle management on an MEC application on a mobile edge host in a network in which an area 1 is located (for example, deployment, start, stop, restart, uninstallation, monitoring, elastic scaling, capacity expansion, and the like of the MEC application), establishing a connection with a mobile edge platform manager MEPM, processing a command issued by the MEPM, reporting application instance data and running state data of the MEC application managed by the LEPM1, and the like, where a network in which the area 1 managed by the LEPM1 is located may be in a local area network or in a subnet, and specifically, the size of the network in which the area 1 is located is determined by the geographical location distribution of the mobile edge host, the Mobile Edge Platform (MEP), and the computing capability of the mobile edge host managed by the LEPM 1. Second, the LEPM1 may be connected to a VIM to apply for computing, storage, or network resources, etc. needed by the MEC application, or to release resources that are no longer used, etc.

The MEPM is provided with connection with LEPMs in various areas so as to send management commands to the LEPM, or receive application instance data or running state data of the MEC application from the LEPM, so as to update the data of the MEPM. The function of the LEPM2 for zone 2 shown in FIG. 1A is similar to LEPM1 and will not be described again.

Since the LEPM1 needs to establish a connection with the MEPM, the embodiment of the present application proposes to establish a connection between the LEPM1 and the MEPM through an Mm5-r interface, where the Mm5-r interface has interface capabilities related to establishment, data synchronization, data transmission, and the like. The LEPM1 may perform application lifecycle operations on the network closed loop in which the area 1 is located, and implement applying for resources for the MEC application or releasing resources occupied by the MEC application by interacting with the VIM. Therefore, an Mm6-1 interface is newly added between the LEPM1 and the VIM, and connection is established through the Mm6-1 interface, so that interaction with the VIM is realized, and operation on the application life cycle is realized. And the mobile edge host 3 can be connected with the LEPM through Mm5-1, so that the LEPM1 can realize application management in the mobile edge host 3.

Therefore, as can be seen from fig. 1A, the mobile edge hosts managed by the LEPM are connected, and then the LEPM is connected with the MEPM, so as to form a cascaded network of the mobile edge hosts. The LEPM can manage the mobile edge hosts in the region, effectively share the management load of the MEPM, and the cascade networking can effectively reduce the network entrance bandwidth of the MEPM. In the management network, the MEPM shares the calculation task and the network resource overhead to a plurality of LEPMs, so that the MEPM is no longer a management bottleneck, and the problems of slow response, increased time delay and the like of management actions of the MEPM are avoided or reduced.

Note that fig. 1A shows only area 1 and area 2, and the LEPM1 manages the mobile edge host in the network in which area 1 is located, and the LEPM2 manages the mobile edge host in the network in which area 2 is located. In practical application, more areas may be included, and then each LEPM is connected to a mobile edge platform manager to implement a cascaded networking, which is not limited in the present application. Fig. 1A is merely to illustrate a data management method according to an embodiment of the present application.

In this embodiment, fig. 1A is a scheme in which an LEPM and an MEP are simultaneously deployed on a mobile edge host, that is, the mobile edge host is an edge center node device in the area and has a local application management capability. In practical application, the LEPM may also be deployed alone, that is, exclusive of one mobile edge host, and the MEP is not deployed on the mobile edge host, as shown in fig. 1B, where fig. 1B is another schematic structural diagram of a management network of the mobile edge host provided in the embodiment of the present application; in fig. 1B, the LEPMs are respectively connected to the MEPs to provide the MEPMs with the functions of connecting and communicating with the MEPs, and only MEPs are deployed on other mobile edge hosts in the local network and then respectively connected to the LEPMs to form a local management network, which is not limited in the present application.

Referring to fig. 2, a data management method in an embodiment of the present application is described below from the perspective of an LEPM, where an embodiment of the data management method in the embodiment of the present application includes:

201. the LEPM receives the management command sent by the MEPM.

Wherein, the management command is a management task issued by the MEPM for the LEPM. There are many specific management commands, such as: an application instantiation command and an application instance termination command.

202. And the LEPM executes corresponding operation according to the management command.

For example, when the management command is an application instantiation command, the LEPM applies for a resource for the MEC application according to the application instantiation command, and creates and runs the MEC application through the resource. And the MEPM issues a management command to the LEPM, and the LEPM executes corresponding management operation, so that the management load of the MEPM is reduced. When the management command is an application instantiation command or an application instance termination command, the specific execution operation of the LEPM is described in detail in the following embodiments of fig. 3 and fig. 5, and is not described again here.

203. The LEPM sends a management command response message to the MEPM.

The LEPM sends a management command response message to the MEPM so that the MEPM determines that the LEPM executes the corresponding management operation according to the management command response message and updates the local data according to the management command response message.

For example, after the LEPM applies for a resource for the MEC application according to an application instantiation command, and creates and runs the MEC application through the resource, the LEPM sends a management command response message to the mecm, and the management command response message carries application instance data of the MEC application, the MEPM records the application instance data of the MEC application and records a corresponding relationship between the MEC application and the LEPM, so that when the MEPM queries the application instance data of the MEC application or terminates the application instance of the MEC application, the LEPM can be determined according to the corresponding relationship and issue a corresponding management command to the LEPM.

In the embodiment of the application, an LEPM receives a management command sent by an MEPM, and the management command carries a management task distributed by the MEPM to the LEPM; then, the LEPM executes corresponding operation according to the management task and sends a management command response message to the MEPM, so that the MEPM updates local data according to the management command response message. Therefore, in the technical scheme of the application, the LEPM receives the management command issued by the MEPM and executes corresponding operation according to the management command, and the MEPM does not need to execute the management operation, so that the management load of the MEPM is reduced, and the problems that the MEPM becomes a bottleneck of the whole network performance, the management action of the MEPM is slow in response, the time delay is increased and the like are avoided or prevented.

A specific process of the LEPM executing the management operation when the management command exemplified in step 202 in fig. 2 is an application instantiation command or an application instance termination command will be described below with reference to a specific embodiment.

Please refer to fig. 3, which is a diagram illustrating a data management method according to an embodiment of the present application. The management command is an application instantiation command, and fig. 3 shows a specific process of the LEPM applying for a resource for the MEC application according to the application instantiation command, and creating and running the MEC application through the resource. Referring to fig. 3, the method includes:

301. the MEPM obtains an application instantiation command.

The application instantiation command carries the position information of the target mobile edge host, and the target mobile edge host is the mobile edge host for installing and running the MEC application.

Illustratively, a tenant initiates an application instantiation command through an Operation Support System (OSS); then, the OSS sends the application instance command to the MEC orchestrator; the MEPM then receives the application instantiation command sent by the MEC orchestrator.

302. The MEPM determines the LEPM according to the location information of the target mobile edge host carried by the application instantiation command.

For example, the specific determination process may be that the MEPM determines according to the geographical location information provided by the LEPM to the MEPM at the time of registration and the location information of the target mobile edge host, and when the location information is consistent, it may be determined that the management operation for executing the instantiation of the application is performed by the LEPM.

The registration process of the LEPM in the embodiment of the present application is described below with reference to fig. 4, and the method includes:

401. the LEPM sends a registration request message to the MEPM.

Illustratively, upon startup of the LEPM, the LEPM actively establishes a connection with the MEPM via an Mm5-r interface as shown in fig. 1A, and then the LEPM sends a registration request message to the MEPM, the registration request message including an access address of the LEPM, location information, attribute information, authentication data, information of a mobile edge host managed by the LEPM, and the like.

Wherein the access address includes a service IP address and a port number of the LEPM, or a service domain name of the LEPM.

The location information includes a network name of a network in which the LEPM is located or a geographical location of the LEPM.

The attribute information includes a name of the LEPM or a description of the LEPM.

The information of the mobile edge host managed by the LEPM includes an identification ID list of the mobile edge host managed by the LEPM, and the like.

The authentication data includes an identity credential (e.g., a security certificate and/or a key of the LEPM, and the security certificate and the key are assigned to the LEPM by the MEPM) of the LEPM.

402. The MEPM determines the LEPM for which it manages based on the location information of the LEPM.

The MEPM determines that the LEPM is an LEPM managed by the LEPM if the LEPM is within the range of a network to which the LEPM is connected according to the location information of the LEPM.

403. And the MEPM verifies the LEPM according to the identity verification data of the LEPM to obtain a verification result.

For example, the MEPM determines whether the security certificate and/or the key carried in the registration request message is consistent with the security certificate or the key of the LEPM stored locally by the MEPM, and if so, the MEPM may determine that the LEPM is successfully verified; if not, the MEPM determines that the LEPM fails to verify.

404. The MEPM sends a registration response message to the LEPM via the access address of the LEPM.

When the LEPM is successfully verified in step 403, the MEPM sends a registration response message to the LEPM through the access address of the LEPM, and the registration response message carries the identification ID allocated by the MEPM to the LEPM; optionally, the registration response message further carries access control data of the LEPM, where the access control data is used to indicate that the LEPM can interact with the MEPM without performing authentication again within a preset time period. For example, the MEPM may send a registration response message to the LEPM via the IP address and port number of the LEPM.

405. The LEPM determines the identity to which the MEPM is assigned from the registration response message.

The LEPM can determine the identifier distributed by the MEPM according to the identifier carried by the registration response message; optionally, when the registration response message further carries the access control data, the LEPM may further determine that authentication is not required to be performed again within a preset time period.

A possible implementation manner is also provided in this embodiment of the present application, which is similar to the foregoing embodiment shown in fig. 4, except that in step 403, step 403 may not be executed, step 404 is directly executed, and in step 404, the MEPM directly sends a registration response message to the LEPM through the access address, that is, the MEPM directly assigns a corresponding identifier to the LEPM without performing identity verification on the LEPM.

Thus, as can be seen from the embodiment illustrated in fig. 4 above, the MEPM determines the geographic location of each LEPM and assigns a corresponding identifier to each LEPM.

The location information of the target mobile edge host may be various, which is exemplified as follows:

mode 1: the geographical location information of the target mobile edge host may include specific location information such as "province, city, district/county, street, cell/machine room", etc. And carrying the geographical location information of the target mobile edge host in the application instantiation request, then determining a corresponding LEPM according to the geographical location information provided during LEPM registration, and deploying the MEC application at the target mobile edge host by the LEPM.

Mode 2: the subnet attribute information of the target mobile edge host, for example, the subnet attribute information includes an IP address range of a network segment, and can be specifically identified by a certain IP address and a subnet mask in the network segment, for example, 192.168.0.1/255.255.255.0. That is, the application instantiation request carries the IP address and subnet mask of the target mobile edge host, the MEPM matches the IP address and subnet mask of the target mobile edge host with the IP address and subnet mask provided during registration of the LEPM, so as to determine the corresponding LEPM, and the LEPM deploys the MEC application on the target mobile edge host.

It should be noted that, when the application instantiation command does not carry the location information of the target mobile edge host, the MEPM selects one LEPM from the LEPMs managed by the MEPM to deploy the MEC application. The specific selection strategy includes randomly selecting or selecting the LEPM with the least number of currently deployed applications, and the like, and is not limited herein.

303. The MEPM sends the application instantiation command to the LEPM.

The application instantiation command carries information of the MEC application, for example, the size of the resource required by the MEC application. After the MEPM determines the corresponding LEPM, an application instantiation command is sent to the LEPM to instruct the LEPM to perform the management operation instantiated by the application in its place.

304. The LEPM sends a resource request message to the VIM.

Wherein the resource request message is used for requesting to create the MEC application and to run the resources of the MEC application.

305. The LEPM receives the resource request response message sent by the VIM.

Wherein the resource request response message is used to indicate that the LEPM requested the resource successfully and to indicate that the VIM applied for the resource by the MEC application. Specifically, if the resource is a container resource, the VIM creates a corresponding container when receiving the resource request message, and then the MEC application preset in the container is also started immediately. If the virtual resource exists, the VIM creates a virtual machine, and optionally, when the MEC application is preset in the virtual machine, the MEC application is started to run immediately; and when the MEC application is not preset in the virtual machine, the subsequent LEPM installs the MEC application on the virtual machine and runs the MEC application.

306. The LEPM sends a configuration request message to the MEP on the target mobile edge host.

The VIM applies for the corresponding resource for the MEC application, that is, determines a target mobile edge host corresponding to the MEC application, and the LEPM interacts with the MEP on the target mobile edge host, and sends a configuration request message to the MEP to request for initial configuration of the resource applied for the MEC application. For example, when the resource is a container resource, the MEP performs initial configuration on the container, and when the resource is a virtual resource, the MEP performs initial configuration on the created virtual machine.

307. The LEPM receives the configuration response message sent by the MEP.

After the MEP performs initialization configuration on the resources applied by the MEC application, a configuration response message is sent to the LEPM, and the configuration response message is used for indicating that the MEP completes the initialization configuration on the resources applied by the MEC application.

308. The LEPM sends application instance data of the MEC application to the MEPM.

After the MEC application creation is complete and the MEC application is launched, the LEPM sends the application instance data for the MEC application to the MEPM.

309. The MEPM updates the data of the MEPM according to the application instance data of the MEC application.

The MEPM updates its local data according to the application instance data of the MEC application. For example, the MEPM may locally record a corresponding relationship between the MEC application and the LEPM and store instance data of the MEC application, where the corresponding relationship is used to indicate management of the application instance of the MEC application by the LEPM, so that when the MEPM queries the application instance data of the MEC application or terminates the application instance of the MEC application, the MEPM may issue a management command to the LEPM, and the LEPM performs a corresponding operation according to the management command, thereby reducing the management load of the MEPM.

In the embodiment of the application, the LEPM receives an application instantiation command sent by the MEPM; the LEPM may then create an application instance of the MEC application from the application instantiation command; after execution is complete, the LEPM sends the application instance data of the MEC application to the MEPM, so that the MEPM updates its local data according to the application instance data of the MEC application. Therefore, in the technical scheme of the application, the application instantiation command sent by the MEPM is received through the LEPM; then, the LEPM creates an application instance of the MEC application according to the application instantiation command without executing the management operation by the MEPM, thereby reducing the management load of the MEPM, and avoiding or preventing the MEPM from becoming a bottleneck of the whole network performance and the problems of slow response, increased time delay and the like of the management action of the MEPM.

Please refer to fig. 5, which is a schematic diagram of a data management method according to an embodiment of the present application, where the management command is an application instance termination command, and fig. 5 illustrates a specific process of the LEPM uninstalling the MEC application and releasing the resource occupied by the MEC application according to the application instance termination command. Referring to fig. 5, the method includes:

501. the MEPM obtains an application instance termination command.

Wherein the application instance termination command carries an identification of the MEC application.

Illustratively, a tenant requests an application instance termination through the OSS, and then the OSS sends the application instance termination command to the MEC orchestrator; the MEC orchestrator then forwards the application instantiation terminate command to the MEPM.

502. The MEPM determines the LEPM according to the identification of the MEC application carried by the application instance termination command.

As can be seen from the embodiment shown in fig. 3, after the application instantiation of the MEC application, the MEPM determines the correspondence relationship between the MEC application and the LEPM according to the application instance data sent by the LEPM; therefore, the MEPM can determine the corresponding LEPM according to the identity of the MEC application.

503. The MEPM sends an application termination command to the LEPM.

The MEPM sends an application termination command to the LEPM, the application termination command carrying an identification of the MEC application.

504. The LEPM sends the application termination request message to the MEP of the target mobile edge host.

Wherein the application termination request message is for requesting the MEP to uninstall the MEC application. Illustratively, as can be seen from the registration embodiment of the LEPM shown in fig. 4, each LEPM has a correspondingly managed mobile edge host and an MEC application, and the LEPM determines, according to the identifier of the MEC application carried by the application termination command, a target mobile edge host where the MEC application is located; the LEPM then sends an application termination request message to the MEP on the target mobile edge host.

505. The LEPM receives an application termination response message sent by the MEP of the target mobile edge host.

After the MEC completes the uninstalling of the MEC application on the target mobile edge host, the MEP sends an application termination response message to the LEPM, where the application termination response message is used to notify the LEPM that the MEC application uninstalls.

506. The LEPM sends a resource release request message to the VIM.

Wherein the resource release request message is used for requesting the VIM to release the resources occupied by the MEC application.

507. The LEPM receives the resource release request response message sent by the VIM.

And the VIM releases the resources occupied by the MEC application, wherein the resources can be container resources or virtual resources. And after the VIM finishes releasing the resources, sending a resource release request response message to the LEPM, wherein the resource release request response message is used for informing the LEPM that the release of the resources occupied by the MEC application is finished.

508. The LEPM sends an application instance termination command response message to the MEPM.

After receiving the resource release request response message, the LEPM may determine that the termination of the application instance of the MEC application is completed, and then the LEPM sends an application instance termination command response message to the MEPM, where the application instance termination command response message is used to notify the MEPM of the completion of the termination of the application instance of the MEC application.

509. The MEPM updates data of the MEPM according to the application instance termination command response message.

And after receiving the application instance termination command response message, the MEPM determines that the termination of the application instance is completed, and then deletes the locally stored corresponding relation between the MEC application and the LEPM and the application instance data of the MEC application.

In the embodiment of the application, the LEPM receives an application termination command sent by the MEPM; then, the LEPM uninstalls the MEC application according to the application termination command, and releases the resources occupied by the MEC application; after the execution is completed, the LEPM sends an application termination command response message to the MEPM, so that the MEPM updates its local data according to the application termination command response message. Therefore, in the technical scheme of the application, the application termination command sent by the MEPM is received by the LEPM, then the lecm uninstalls the MEC application according to the application termination command, and releases the resources occupied by the MEC application without executing management operation by the MEPM, so that the management load of the MEPM is reduced, and the problems that the MEPM becomes a bottleneck of the whole network performance and the management action of the MEPM is slow in reaction, time delay is increased and the like are avoided or prevented.

In the embodiment of the application, in a network managed by the LEPM, the LEPM performs elastic scaling control on the application instance of the MEC application managed by the LEPM according to a preset elastic scaling rule and the index data of the MEC application, and the MEP is not required to report the index data of the MEC application to the MEPM, that is, the MEPM is not required to perform elastic scaling control on the application instance of the MEC application. The process of the flexible expansion and contraction control of the application example of the MEC application by the specific LEPM is described in detail by the embodiment shown in fig. 6, and referring to fig. 6, the method includes:

601. the LEPM sends a subscription request to the MEP on the target mobile edge host.

The subscription request is used for requesting subscription to index data of a target MEC application, the subscription request carries an ID of the target MEC application, a reporting period of the index data of the target MEC application, and the like, the index data includes indexes of resources occupied by the target MEC application (for example, CPU, memory, input/output (IO), network IO, and the like) and indexes of the target MEC application itself (for example, message processing rate, client connection number, and the like), and the target mobile edge host is a mobile edge host managed by the LEPM and is a mobile edge host where the target MEC application is located.

602. The LEPM receives index data of a target MEC application sent by the MEP.

The MEP acquires instance data of the target MEC application according to the ID of the target MEC application indicated in the subscription request, counts index data of the target MEC application, and sends the index data of the target MEC application to the LEPM, wherein the index data comprises the application instance ID, the index name, the index value, the time stamp for reporting the index data and the like of the target MEC application.

603. The LEPM determines whether the index value in the index data is greater than a first preset index value and less than a second preset index value, if yes, step 607 is executed; if not, go to step 604.

The first preset index value is an index threshold value for releasing the application instance of the MEC application specified in an elastic scaling rule preset in the LEPM, and the second preset index value is an index threshold value for distributing the application instance for the MEC application specified in the elastic scaling rule. The elastic expansion rule comprises attribute information such as observed indexes, observed time, index threshold values, execution actions and the like. Illustratively, when the MEC application runs, the occupancy rate of the MEC application to the CPU in one minute is less than 40%, an application instance is released; when the occupancy rate is greater than 80%, an application instance is expanded, namely the observed index is the CPU occupancy rate, the observation time is one minute, the execution action is 'the occupancy rate of the CPU corresponding to the MEC application in one minute', the first preset index value is 40%, and the second preset index value is 80%.

604. The LEPM determines whether the index value is smaller than a first preset index value, if yes, step 605 is executed; if not, step 606.

605. The LEPM releases the application instance of the target MEC application.

When the index value is smaller than a first preset index value, the LEPM releases the existing part of the application instances of the target application. Illustratively, the LEPM requests the MEP and VIM on the target mobile edge host where the target MEC application resides to release the application instance of the target MEC application.

606. The LEPM allocates an application instance for the target MEC application.

As can be seen from the above, when the index value is greater than the second preset index value, the LEPM allocates an application instance to the target MEC application. Illustratively, the LEPM applies for a resource for the target MEC application from the VIM, and performs initial configuration on the resource through the MEP on the target mobile edge host, so as to facilitate the running of the target MEC application.

607. The LEPM does not perform operations on the application instance of the target MEC application.

When the index value is greater than the first preset index value and less than the second preset index value, the LEPM does not execute any operation on the application instance of the MEC application.

In the embodiment of the application, the LEPM receives index data of the MEC application sent by the MEP platform; the LEPM then allocates an application instance to the MEC application, releases the application instance of the MEC application, or does not perform an operation on the MEC application according to a preset elastic scaling rule and the index data. Therefore, in the technical scheme of the application, the application of the MEC application is elastically controlled through the LEPM, the MEPM does not need to report index data of the MEC application to the MEPM, and the MEPM is used for elastically controlling the application of the MEC application, so that the management load of the MEPM is reduced, and the problems that the MEPM becomes a bottleneck of the whole network performance, the management action of the MEPM is slow in response, the time delay is increased and the like are avoided or prevented.

Please refer to fig. 7, which is a diagram illustrating a data management method according to an embodiment of the present application. In fig. 7, the MEPM sends a subscription indication message to the LEPM, the subscription indication message indicating that when there is change data in the LEPM, the LEPM sends a change notification message to the LEPM, the change data including information of a changing mobile edge host managed by the LEPM or application instance data and/or running state data of a changing MEC application on a mobile edge host managed by the LEPM, the change notification message being used for the MEPM to update its local data. Referring to fig. 7, the method includes:

701. the MEPM sends a subscription indication message to the LEPM.

Wherein, the subscription indication message is used to indicate that when the LEPM has change data, the LEPM actively sends a change notification to the MEPM, and the change data includes information of changing the mobile edge host managed by the LEPM, application instance data and/or running state data of changing the MEC application, and the like.

Illustratively, as depicted in fig. 1A, the MEPM manages application instance data and run state data for mobile edge hosts, MEC applications on the mobile edge hosts in multiple zones. After the LEPM is successfully registered, the LEPM establishes connection with the MEPM, and the MEPM sends a subscription indication message to the LEPM.

702. The LEPM determines that there is change data.

For example, as shown in fig. 6, in the embodiment, the LEPM performs scaling control on the application instance of the target MEC application according to the index data of the target MEC application, and when the LEPM allocates an application instance to the target MEC application or releases the allocated application instance, the LEPM determines that the application instance data of the target MEC application is changed or the operation state is changed, that is, the application instance data and the operation state data of the target MEC application may be understood as the application instance data and the operation state data of the changed MEC application in the change data. When the number of mobile edge hosts managed by the LEPM increases or decreases, the LEPM can determine that the information of the mobile edge hosts it manages has changed, i.e., the increased mobile edge hosts or the decreased mobile edge hosts can understand the information of the changed mobile edge hosts in the change data.

703. The LEPM sends a change notification message to the MEPM.

When the LEPM determines that the change data exists, the LEPM generates a change notification message to the MEPM, wherein the change notification message carries change data, such as information of a change mobile edge host, application instance data or running state data of an MEC application, and the like.

704. The MEPM updates the data of the MEPM according to the change notification message.

The change notification message carries change data, for example, information of a change mobile edge host, or application instance data or running state data of the MEC application. For example, if the MEPM updates the locally recorded information of the mobile edge hosts managed by the LEPM according to the information of the changed mobile edge hosts, for example, the LEPM adds a managed mobile edge host, the MEPM may add the ID of the added mobile edge host in the ID list of the mobile edge hosts managed by the LEPM stored in the MEPM. For another example, if the LEPM adds an application instance to a changing MEC application, the MEPM updates locally stored application instance data for the changing MEC application.

In the embodiment of the application, the LEPM receives a subscription indication message sent by the MEPM; then, when the LEPM determines that there is change data, the LEPM sends a change notification message to the MEPM; then, the MEPM updates the data of the MEPM according to the change notification message. Therefore, in the technical scheme of the application, the MEPM subscribes to the application instance data of the MEC application and the information of the mobile edge host managed by the application instance data to the LEPM, so that the data synchronization of the MEPM and the LEPM is realized.

A possible implementation manner is also provided in the embodiment of the present application, which is similar to the foregoing embodiment of fig. 7, except that in step 703 and step 704, in this embodiment, step 703 may be replaced with: the LEPM sends a change notification message to the MEPM, wherein the change notification message is used for notifying the MEPM that the LEPM has change data and does not carry the change data. Step 704 may be replaced with: the MEPM queries the information of the mobile edge host managed by the LEPM and the application instance data and the running state data of the MEC application by calling the interface of the LEPM so as to acquire the change data and update the local data. Secondly, in this embodiment of the present application, the MEPM may also periodically query the application instance data and the running state data of the newly-updated MEC application by calling the interface of the LEPM, and update the local data thereof.

An LEPM provided in the embodiment of the present application is described below. Referring to fig. 8, in an embodiment of the LEPM in the present application, the LEPM800 may be used to perform the steps performed by the LEPM in the embodiments shown in fig. 2, 3, 4, 5, 6, and 7, and reference may be made to the related description in the above method embodiments.

The LEPM800 includes: a transceiver module 801 and a processing module 802.

A transceiver module 801, configured to receive a management command sent by an MEPM, where the management command is a management task allocated by the MEPM to the LEPM;

a processing module 802, configured to execute a corresponding operation according to the management command;

the transceiver module 801 is configured to send a management command response message to the MEPM, where the management command response message is used to notify the MEPM that the LEPM executes corresponding operation completion and the MEPM updates data of the MEPM.

In a possible implementation manner, the transceiver module 801 is further configured to:

sending a registration request message to the MEPM, the registration request message including an access address of the LEPM, location information, and information of a mobile edge host managed by the LEPM;

receiving a registration response message sent by the MEPM;

the processing module 802 is further configured to:

and determining the identification allocated by the MEPM to the LEPM according to the registration response message.

In another possible implementation manner, the registration request message further includes an identity certificate of the LEPM or attribute information of the LEPM; the authentication data is used for the MEPM to authenticate the LEPM.

In another possible implementation manner, the management command includes an application instantiation command, where the application instantiation command carries information of the MEC application requested to be created; the processing module 802 is specifically configured to:

applying for resources for the MEC application according to the information of the MEC application, and creating the MEC application and running the MEC application through the resources;

the transceiver module 801 is specifically configured to:

the application instance data of the MEC application is sent to the MEPM.

In another possible implementation manner, the management command includes an application instance termination command, and the application instance termination command carries an identifier of the MEC application; the processing module 802 is specifically configured to:

and unloading the MEC application according to the mark of the MEC application, and releasing the resources occupied by the MEC application.

In another possible implementation manner, the transceiver module 801 is further configured to:

and receiving a subscription indication message sent by the MEPM, wherein the subscription indication message is used for indicating that when the LEPM has change data, the LEPM sends the change notification message to the MEPM, and the change data comprises information of a change edge host managed by the LEPM, application instance data of a change MEC application or running state data of the change MEC application.

In another possible implementation manner, the processing module 802 is further configured to:

determining that the LEPM has change data;

the transceiver module 801 is further configured to:

sending a change notification message to the MEPM, the change notification message being used to notify the MEPM that the LEPM has change data.

In another possible implementation manner, the change notification message carries the change data, and the change data is used for the MEPM to update the data of the LEPM stored by the MEPM.

acquiring index data for changing the MEC application;

the processing module 802 is further configured to:

and allocating an application instance to the changed MEC application according to the index data and a preset elastic scaling rule, or releasing the application instance of the changed MEC application.

In the embodiment of the present application, the transceiver module 801 receives a management command sent by the MEPM, and the processing module 802 executes a corresponding operation according to the management command; the transceiving module 801 then sends a management response message to the MEPM for the MEPM to update its local data. Therefore, management operation does not need to be executed by the MEPM, so that the management load of the MEPM is reduced, and the problems that the MEPM becomes a bottleneck of the whole network performance, the management action of the MEPM is slow in response, the time delay is increased and the like are avoided or prevented.

An MEPM provided in the embodiment of the present application is described below. Referring to fig. 9, in an embodiment of the MEPM in the present application, the MEPM900 may be used to execute the steps executed by the MEPMs in the embodiments shown in fig. 2, fig. 3, fig. 4, fig. 5, and fig. 7, and reference may be made to the related description in the foregoing method embodiments.

The MEPM900 includes: a transceiver module 901, and a processing module 902.

A transceiver module 901, configured to send a management command to an LEPM, where the management command is a management task allocated by the MEPM to the LEPM;

a transceiver module 901, configured to receive a management command response message sent by the LEPM,

a processing module 902, configured to update the data of the MEPM according to the management command response message.

In a possible implementation manner, the transceiver module 901 is further configured to:

receiving a registration request message sent by the LEPM, wherein the registration request message carries an access address and position information of the LEPM and information of a mobile edge host managed by the LEPM;

the processing module 902 is further configured to:

determining the LEPM is the LEPM managed by the MEPM according to the position information;

the transceiver module 901 is further configured to:

and sending a registration response message to the LEPM through the access address, wherein the registration response message carries the identification which is allocated by the MEPM to the LEPM.

In another possible implementation manner, the registration request message further includes the identity authentication data of the LEPM; the processing module 902 is further configured to:

verifying the LEPM according to the identity authentication data to obtain a verification result;

and determining that the LEPM verification is successful according to the verification result.

In another possible implementation, the management command includes an application instantiation command; the transceiver module 901 is specifically configured to:

receiving application instance data of the MEC application sent by the LEPM;

the processing module 902 is specifically configured to:

and recording the corresponding relation between the MEC application and the LEPM in the MEPM according to the application instance data and storing the application instance data of the MEC application.

In another possible implementation manner, the transceiver module 901 is further configured to:

acquiring an application instantiation command, wherein the application instantiation command carries the position information of a target mobile edge host corresponding to the MEC application which is requested to be created;

the processing module 902 is further configured to:

an LEPM managing the target mobile edge host is determined based on the location information.

In another possible implementation manner, the management command includes an application instance termination command, and the application instance termination command carries an identifier of the MEC application; the processing module 902 is specifically configured to:

and deleting the corresponding relation between the MEC application and the LEPM stored by the MEPM and the application instance data of the MEC application.

sending a subscription indication message to the LEPM, the subscription indication message indicating that the LEPM sends a change notification message to the MEPM when change data exists in the LEPM, the change data including information of a changing mobile edge host managed by the LEPM, application instance data of a changing MEC application managed by the LEPM, or running state data of the changing MEC application.

receiving a change notification message sent by the LEPM, wherein the change notification message carries the change data;

the processing module 902 is further configured to:

and updating the data of the LEPM stored by the MEPM according to the change data.

receiving a change notification message sent by an LEPM;

the processing module 902 is further configured to:

determining that the LEPM has changed data according to the change notification message;

the transceiver module 901 is further configured to:

then obtaining the change data through an interface of the LEPM;

the processing module 902 is further configured to:

and updating the data of the local edge platform manager stored by the mobile edge platform manager according to the change data.

acquiring application instance data of the MEC application in the latest state and information of a mobile edge host managed by an LEPM (unified extensible firmware protocol) by calling an interface of the LEPM according to a preset period;

the processing module 902 is further configured to:

and updating the data of the MEPM according to the application instance data of the MEC application in the latest state and the information of the mobile edge host managed by the LEPM.

In this embodiment of the present application, the transceiver module 901 sends a management command to the LEPM, where the management command is a management task that the MEPM allocates to the LEPM; then, the transceiver module 901 receives the management command response message sent by the LEPM, and the processing module 902 updates the data of the MEPM according to the management command response message. In the technical solution of the present application, the transceiver module 901 issues a management command to the LEPM, so that the LEPM executes a corresponding operation according to the management command. Therefore, management operation does not need to be executed by the MEPM, so that the management load of the MEPM is reduced, and the problems that the MEPM becomes a bottleneck of the whole network performance, the management action of the MEPM is slow in response, the time delay is increased and the like are avoided or prevented.

Referring to fig. 10, an embodiment of the LEPM in the embodiment of the present application, which can be used to execute the steps executed by the LEPM in the embodiments shown in fig. 2, fig. 3, fig. 4, fig. 5, fig. 6, and fig. 7, may refer to the related description in the above method embodiment.

The LEPM1000 includes: a processor 1001, a memory 1002, an input-output device 1003, and a bus 1004.

In one possible implementation, the processor 1001, the memory 1002, and the input/output device 1003 are each connected to a bus 1004, and the memory stores computer instructions.

The processor 1001 is configured to execute computer instructions to cause the LEPM to perform the associated method steps performed by the LEPM in the above-described method embodiments.

The processing module 802 in the foregoing embodiment may be specifically the processor 1001 in this embodiment, and therefore, detailed implementation of the processor 1001 is not described again. The transceiver module 801 in the foregoing embodiment may specifically be the input/output device 1003 in this embodiment, and therefore details of the specific implementation of the input/output device 1003 are not described again.

Referring to fig. 11, an embodiment of the MEPM in the embodiment of the present application may be used to execute steps executed by the MEPMs in the embodiments shown in fig. 2, fig. 3, fig. 4, fig. 5, and fig. 7, which may refer to relevant descriptions in the above method embodiments.

The MEPM1100 includes: a processor 1101, a memory 1102, an input-output device 1103, and a bus 1104.

In one possible implementation, the processor 1101, the memory 1102 and the input/output device 1103 are each coupled to the bus 1104, and the memory stores computer instructions.

The processor 1101 is configured to execute computer instructions to cause the MEPM to perform the relevant method steps performed by the MEPM in the above-described method embodiments.

The processing module 902 in the foregoing embodiment may be specifically the processor 1101 in this embodiment, and therefore, detailed implementation of the processor 1101 is not described again. The transceiver module 901 in the foregoing embodiment may specifically be the input/output device 1103 in this embodiment.

Referring to fig. 12, an embodiment of the present application further provides a data management system, where the data management system includes an LEPM and an MEPM, and specifically, the LEPM may include an LEPM as shown in fig. 8 and the MEPM may include an MEPM as shown in fig. 9, where the LEPM may be used to perform all or part of the steps performed by the LEPM in the embodiments shown in fig. 2, 3, 4, 5, 6 and 7, and the MEPM may be used to perform all or part of the steps performed by the MEPM in the embodiments shown in fig. 2, 3, 4, 5 and 7.

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 several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical 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.

In addition, functional units in the embodiments of the present application 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 integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit 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 application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in 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 application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims

1. A method for managing data, the method comprising:

a local edge platform manager receives a management command sent by a mobile edge platform manager, wherein the management command is a management task distributed to the local edge platform manager by the mobile edge platform manager;

the local edge platform manager executes corresponding operation according to the management command;

the local edge platform manager sends a management command response message to the mobile edge platform manager, wherein the management command response message is used for informing the mobile edge platform manager that the local edge platform manager executes corresponding operation completion and the mobile edge platform manager updates data of the mobile edge platform manager.

2. The method of claim 1, wherein before the local edge platform manager receives the management command sent by the mobile edge platform manager, the method further comprises:

the local edge platform manager sends a registration request message to the mobile edge platform manager, wherein the registration request message comprises an access address and position information of the local edge platform manager and information of a mobile edge host managed by the local edge platform manager;

the local edge platform manager receives a registration response message sent by the mobile edge platform manager;

and the local edge platform manager determines the identifier distributed by the mobile edge platform manager for the local edge platform manager according to the registration response message.

3. The method according to claim 1 or 2, wherein the management command comprises an application instantiation command, the application instantiation command carrying information of the mobile edge computing, MEC, application that requested creation;

the local edge platform manager executes corresponding operations according to the management command, and the operations comprise:

the local edge platform manager applies for resources for the MEC application according to the information of the MEC application, and creates the MEC application and runs the MEC application through the resources;

the local edge platform manager sending a management command response message to the mobile edge platform manager includes:

the local edge platform manager sends application instance data of the MEC application to the mobile edge platform manager.

4. The method according to claim 1 or 2, wherein the management command comprises an application instance termination command, and the application instance termination command carries an identification of the MEC application;

and the local edge platform manager unloads the MEC application according to the mark of the MEC application and releases the resources occupied by the MEC application.

5. The method of claim 1 or 2, wherein after the local edge platform manager sends a management command response message to the mobile edge platform manager, the method further comprises:

the local edge platform manager determining that there is change data for the local edge platform manager, the change data including information of a changed mobile edge host managed by the local edge platform manager, application instance data of a changed MEC application managed by the local edge platform manager, or running state data of the changed MEC application;

the local edge platform manager sends a change notification message to the mobile edge platform manager, wherein the change notification message is used for notifying the mobile edge platform manager that change data exists in the local edge platform manager.

6. The method of claim 5, wherein before the local edge platform manager determines that change data exists for the local edge platform manager, the method further comprises:

the local edge platform manager acquires index data of the changed MEC application;

and the local edge platform manager distributes an application instance for the changed MEC application according to the index data and a preset elastic expansion rule, or releases the application instance of the changed MEC application.

7. A method for managing data, the method comprising:

a mobile edge platform manager sends a management command to a local edge platform manager, wherein the management command is a management task distributed to the local edge platform manager by the mobile edge platform manager;

the mobile edge platform manager receives a management command response message sent by the local edge platform manager;

and the mobile edge platform manager updates the data of the mobile edge platform manager according to the management command response message.

8. The method of claim 7, wherein prior to the mobile edge platform manager sending the management command to the local edge platform manager, the method further comprises:

the mobile edge platform manager receives a registration request message sent by the local edge platform manager, wherein the registration request message carries an access address and position information of the local edge platform manager and information of a mobile edge host managed by the local edge platform manager;

the mobile edge platform manager determines that the local edge platform manager is the local edge platform manager managed by the mobile edge platform manager according to the position information;

and the mobile edge platform manager sends a registration response message to the local edge platform manager through the access address, wherein the registration response message carries the identifier distributed to the local edge platform manager by the mobile edge platform manager.

9. The method of claim 7 or 8, wherein the management command comprises an application instantiation command; the receiving, by the mobile edge platform manager, the management command response message sent by the local edge platform manager includes:

the mobile edge platform manager receives application instance data of a mobile edge computing MEC application sent by the local edge platform manager;

the updating, by the mobile edge platform manager, the data of the mobile edge platform manager according to the management response message includes:

and the mobile edge platform manager records the corresponding relation between the MEC application and the local edge platform manager according to the application instance data and stores the application instance data of the MEC application.

10. The method according to claim 7 or 8, wherein the management command comprises an application instance termination command, and the application instance termination command carries an identification of the MEC application; the updating, by the mobile edge platform manager, the data of the mobile edge platform manager according to the management response message includes:

the mobile edge platform manager deletes the corresponding relation of the MEC application and the local edge platform manager and the application instance data of the MEC application stored by the mobile edge platform manager.

11. The method of claim 7 or 8, wherein after the mobile edge platform manager updates the data of the mobile edge platform manager according to the management command response message, the method further comprises:

the mobile edge platform manager receives a change notification message sent by the local edge platform manager, where the change notification message carries change data, and the change data includes information of a change mobile edge host managed by the local edge platform manager, application instance data of a change MEC application managed by the local edge platform manager, or running state data of the change MEC application;

and the mobile edge platform manager updates the data of the local edge platform manager stored by the mobile edge platform manager according to the change data.

12. The method of claim 7 or 8, wherein after the mobile edge platform manager updates the data of the mobile edge platform manager according to the management command response message, the method further comprises:

the mobile edge platform manager receives a change notification message sent by the local edge platform manager;

the mobile edge platform manager determines that change data exists in the local edge platform manager according to the change notification message, wherein the change data comprises information of a change mobile edge host managed by the local edge platform manager, application instance data of a change MEC application managed by the local edge platform manager, or running state data of the change MEC application;

the mobile edge platform manager acquires the change data by calling an interface of the local edge platform manager;

13. A local edge platform manager, the local edge platform manager comprising:

a receiving and sending module, configured to receive a management command sent by a mobile edge platform manager, where the management command is a management task that is allocated by the mobile edge platform manager to the local edge platform manager;

the processing module is used for executing corresponding operation according to the management command;

the receiving and sending module is configured to send a management command response message to the mobile edge platform manager, where the management command response message is used to notify the mobile edge platform manager that the local edge platform manager performs corresponding operation completion and the mobile edge platform manager updates data of the mobile edge platform manager.

14. The local edge platform manager according to claim 13, wherein the transceiver module is further configured to:

sending a registration request message to the mobile edge platform manager, wherein the registration request message comprises an access address and position information of the local edge platform manager and information of a mobile edge host managed by the local edge platform manager;

receiving a registration response message sent by the mobile edge platform manager;

the processing module is further configured to:

and determining the identifier distributed by the mobile edge platform manager for the local edge platform manager according to the registration response message.

15. The local edge platform manager according to claim 13 or 14, wherein the management command comprises an application instantiation command carrying information of the mobile edge computing, MEC, application requested to be created; the processing module is specifically configured to:

the transceiver module is specifically configured to:

sending application instance data of the MEC application to the mobile edge platform manager.

16. The local edge platform manager according to claim 13 or 14, wherein the management command comprises an application instance termination command, and the application instance termination command carries an identification of the MEC application; the processing module is specifically configured to:

17. The local edge platform manager according to claim 13 or 14, wherein the processing module is further configured to:

determining that change data exists for the local edge platform manager, the change data including information of a changing mobile edge host managed by the local edge platform manager, application instance data of a changing MEC application managed by the local edge platform manager, or running state data of the changing MEC application;

the transceiver module is further configured to:

and sending a change notification message to the mobile edge platform manager, wherein the change notification message is used for notifying the mobile edge platform manager that the local edge platform manager has change data.

18. The local edge platform manager according to claim 17, wherein the transceiver module is further configured to:

acquiring index data of the changed MEC application;

the processing module is further configured to:

and distributing an application instance for the changed MEC application according to the index data and a preset elastic expansion rule, or releasing the application instance of the changed MEC application.

19. A mobile edge platform manager, the mobile edge platform manager comprising:

a receiving and sending module, configured to send a management command to a local edge platform manager, where the management command is a management task that is allocated by the mobile edge platform manager to the local edge platform manager;

the receiving and sending module is used for receiving a management command response message sent by the local edge platform manager;

and the processing module is used for updating the data of the mobile edge platform manager according to the management command response message.

20. The mobile edge platform manager of claim 19, wherein the transceiver module is further configured to:

receiving a registration request message sent by the local edge platform manager, wherein the registration request message carries an access address and position information of the local edge platform manager and information of a mobile edge host managed by the local edge platform manager;

the processing module is further configured to:

determining that the local edge platform manager is a local edge platform manager managed by the mobile edge platform manager according to the position information;

the transceiver module is further configured to:

and sending a registration response message to the local edge platform manager through the access address, wherein the registration response message carries the identifier distributed by the mobile edge platform manager for the local edge platform manager.

21. The mobile edge platform manager according to claim 19 or 20, wherein the management command comprises an application instantiation command; the transceiver module is specifically configured to:

receiving application instance data of a mobile edge computing MEC application sent by the local edge platform manager;

the processing module is further configured to:

and recording the corresponding relation between the MEC application and the local edge platform manager according to the application instance data and storing the application instance data of the MEC application.

22. The mobile edge platform manager according to claim 19 or 20, wherein the management command comprises an application instance termination command, and wherein the application instance termination command carries an identification of the MEC application; the processing module is specifically configured to:

deleting the corresponding relation between the MEC application and the local edge platform manager and the application instance data of the MEC application stored in the mobile edge platform manager.

23. The mobile edge platform manager according to claim 19 or 20, wherein the transceiving module is further configured to:

receiving a change notification message sent by the local edge platform manager, where the change notification message carries change data, and the change data includes information of a changed mobile edge host managed by the local edge platform manager, application instance data of a changed MEC application managed by the local edge platform manager, or running state data of the changed MEC application;

the processing module is further configured to:

24. The mobile edge platform manager according to claim 19 or 20, wherein the transceiving module is further configured to:

receiving a change notification message sent by the local edge platform manager;

the processing module is further configured to:

determining that there is change data for the local edge platform manager according to the change notification message, the change data including information of a changed mobile edge host managed by the local edge platform manager, application instance data of a changed MEC application managed by the local edge platform manager, or running state data of the changed MEC application;

the transceiver module is further configured to:

acquiring the change data by calling an interface of the local edge platform manager;

the processing module is further configured to:

25. A data management system comprising a local edge platform manager according to any of claims 13 to 18 and a mobile edge platform manager according to any of claims 19 to 24.

26. A computer-readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the method of any of claims 1 to 12.