CN110311979B - Task migration method of MEC server and related device - Google Patents
Task migration method of MEC server and related device Download PDFInfo
- Publication number
- CN110311979B CN110311979B CN201910595116.7A CN201910595116A CN110311979B CN 110311979 B CN110311979 B CN 110311979B CN 201910595116 A CN201910595116 A CN 201910595116A CN 110311979 B CN110311979 B CN 110311979B
- Authority
- CN
- China
- Prior art keywords
- subtask
- container
- mec server
- user
- mec
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B17/00—Monitoring; Testing
- H04B17/30—Monitoring; Testing of propagation channels
- H04B17/309—Measuring or estimating channel quality parameters
- H04B17/318—Received signal strength
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/563—Data redirection of data network streams
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- Electromagnetism (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application provides a task migration method of an MEC server, which comprises the following steps: acquiring signal intensity information of a user side under a current MEC server; judging whether the user side is displaced or not according to the change rate of the signal intensity information; if the user side does not displace, performing subtask migration according to the running state of the MEC server; if the user side is displaced, judging whether the user side carries out cross-region displacement; if the user side carries out cross-region displacement, executing cross-region subtask migration; and if the user side does not perform cross-regional displacement, performing subtask migration in the distributed regional service center. During the whole task execution process, the task execution failure condition caused by multiple data transmission or equipment downtime and the like can be avoided, and the task completeness is guaranteed to the maximum extent. The present application also provides an MEC server and a computer-readable storage medium having the above-described advantageous effects.
Description
Technical Field
The present application relates to the field of servers, and in particular, to a task migration method and a related device for an MEC server.
Background
In recent years, in order to effectively solve the problems of high time delay, high network load and low efficiency caused by the rapid development of the Mobile internet and the internet of things, a Mobile Edge Computing (MEC) technology, hereinafter referred to as MEC in a unified manner, has attracted extensive attention and research. The idea of mobile edge computing is to migrate a cloud computing platform to the edge of a mobile access network, attempt to perform deep fusion on the traditional telecommunication cellular network and internet services, reduce end-to-end time delay of mobile service delivery, explore the capability of a wireless network, and improve user experience. In particular, mobile edge computing extends network, computing, storage capabilities from the cloud to the network edge, deploying various services and caches content at the network edge, mobile core networks further alleviate congestion and can efficiently service local demands.
With the development of the code decomposition technology, the task division model in the MEC gets a lot of attention. Generally, one mobile terminal application task is composed of a plurality of subtasks, wherein the mobile terminal application task is a basic unit of the MEC processing task. Assuming that subtasks 1, 2, 3, 4, and 5 constitute one task, the input data source of the subtask 5 comes from the subtask 3 and the subtask 4, and the subtask 5 can start to execute only when the subtask 3 and the subtask 4 are both completed and the subtask 5 receives data from both parties.
Firstly, since a part of subtasks into which a task is divided by a task division decision is migrated to a container side of the MEC server to be executed, the container side and the user side of the MEC server tend to frequently perform data interaction, and thus the probability of packet loss increases accordingly. Secondly, once the container of the MEC server or the whole MEC itself goes down during the execution process, the task will be declared to be failed. Finally, if a subtask suddenly experiences execution confusion such that data results cannot be returned in time, a task failure may also result.
Secondly, the container in the prior art stores all data, and when the user moves, the MEC server needs to migrate the entire container. Migration of the entire container will inevitably result in a large amount of data transfer. Supposing that, when multiple users migrate for multiple times, network delay and network load are inevitably increased greatly, impact is caused to a communication system, task completeness cannot be guaranteed, meanwhile, multiple times of large data transmission increase execution time of tasks, and finally, experience quality of the users is reduced.
Therefore, how to improve the reliability of task migration of the MEC server is a problem that needs to be solved by those skilled in the art.
Disclosure of Invention
The utility model aims to provide a task migration method of MEC server, an MEC server and a computer readable storage medium, effectively improved the reliability when MEC server carries out the task migration.
In order to solve the technical problem, the application provides a task migration method of an MEC server, and the specific technical scheme is as follows:
acquiring signal intensity information of a user side under a current MEC server;
judging whether the user side is displaced or not according to the change rate of the signal intensity information;
if the user side is not displaced, performing subtask migration according to the running state of the MEC server;
if the user side is displaced, judging whether the user side carries out trans-regional displacement or not;
if the user side carries out cross-region displacement, executing cross-region subtask migration;
if the user side does not perform cross-regional displacement, performing subtask migration in the distributed regional service center;
the distributed regional service center is composed of resource data areas of all MEC servers in a preset geographic position range.
Wherein, include:
updating the online information of the MEC server every other first preset time;
updating a user subtask list at a user side every time one subtask is added or every time one subtask is completed, and updating a container subtask list at the MEC server;
and updating the signal intensity information every second preset time.
Wherein, include:
the user registers first registration information with a distributed regional service center, wherein the first registration information comprises user online information, signal strength information of the user under the MEC server and the user subtask list;
registering second registration information by the MEC container to a distributed regional service center, wherein the second registration information comprises container online information and the container subtask list;
wherein the MEC server comprises an MEC container, the resource data area and a data storage area.
And the user online information, the signal strength information, the user subtask list, the container online information and the container subtask list all adopt a node data format.
The node data format comprises an MEC server sequence, a service ranking serial number of a user, a registered information type and a registered information state.
Wherein, still include:
and storing the first registration information and the second registration information in the data storage area.
Wherein, performing subtask migration according to the running state of the MEC server comprises:
if the MEC server is down, the distributed regional service center determines a task pointer according to the container subtask list updated by the down MEC container for the last time before the shutdown; migrating the unexecuted subtasks from the data storage area to a normal MEC container according to the task pointer for execution, and updating a container subtask list of the normal MEC container;
if the MEC server is completely down, the distributed regional service center determines the MEC server closest to the user side according to the signal intensity information, calls all container subtask lists of the down MEC server from the data storage area, and synchronizes the subtasks to the normal MEC server according to all the container subtask lists.
The present application further provides an MEC server, comprising:
the resource data areas of all MEC servers in a preset geographic range form a distributed regional service center;
the data storage area is used for storing subtask data, subtask execution data, execution result data and instruction information of the distributed regional server center by a user;
and the MEC container is used for executing the user subtasks.
The present application also provides a computer-readable storage medium having stored thereon a computer program which, when being executed by a processor, carries out the steps of the task migration method as described above.
The application provides a task migration method of an MEC server, which comprises the following steps: acquiring signal intensity information of a user side under a current MEC server; judging whether the user side is displaced or not according to the change rate of the signal intensity information; if the user side does not displace, performing subtask migration according to the running state of the MEC server; if the user side is displaced, judging whether the user side carries out cross-region displacement; if the user side carries out cross-region displacement, executing cross-region subtask migration; if the user side does not perform cross-regional displacement, performing subtask migration in the distributed regional service center; the distributed regional service center is composed of resource data areas of all MEC servers in a preset geographic position range.
According to the method and the device, the task execution failure condition caused by multiple data transmission or equipment downtime and other reasons can be avoided in the whole task execution process, and the task completeness is guaranteed to the maximum extent. Meanwhile, when the user moves, the task data can be recovered and executed more quickly, the transmission of data volume is reduced, the total execution time of the task is reduced, and the network delay and the network load are reduced, so that the real-time requirements of the user are met, and the experience quality of the user is improved. The present application further provides an MEC server and a computer-readable storage medium, which have the above-mentioned advantages and are not described herein again.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a task migration method of an MEC server according to an embodiment of the present disclosure;
FIG. 2 is a schematic diagram of a node data format provided herein;
FIG. 3 is a diagram illustrating a subtask list format provided by the present application;
fig. 4 is a schematic diagram of an example of node data provided in an embodiment of the present application;
FIG. 5 is a schematic diagram of a first migration process provided herein;
fig. 6 is a schematic diagram of node data update corresponding to a first migration process provided in the present application;
FIG. 7 is a schematic illustration of a second migration process provided herein;
FIG. 8 is a schematic illustration of a third migration process provided herein;
fig. 9 is a schematic diagram of node data update corresponding to a third migration process provided in the present application;
FIG. 10 is a schematic illustration of a fourth migration process provided herein;
fig. 11 is a schematic diagram of node data update corresponding to a fourth migration process provided in the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a flowchart of a task migration method of an MEC server according to an embodiment of the present disclosure, where the task migration method includes:
s101: acquiring signal intensity information of a user side under a current MEC server;
this step aims to obtain the signal strength information of the user side under the MEC server.
The task migration strategy is an important step in the task migration process, and refers to a process of taking a certain index as an optimization target, measuring migration consumption through a related scientific method, and making a process of migrating sub-tasks to a remote server container.
This step may be performed by a distributed regional service center. The distributed regional service center analyzes the registered/updated signal strength of the user terminal.
It is easily understood that before this step is performed, a connection between the user terminal and the MEC server needs to be established, and a corresponding registration procedure is required. The specific registration process may be as follows:
a user registers first registration information to a distributed regional service center, wherein the first registration information comprises user online information, signal intensity information of the user under an MEC server and a user subtask list;
the MEC container registers second registration information to the distributed regional service center, wherein the second registration information comprises container online information and a container subtask list;
it is worth mentioning that the user online information, the signal strength information, the user subtask list, the container online information, and the container subtask list all adopt a node data format. The node data format includes the MEC server sequence, the user's service ranking sequence number, the registered information type, and the registered information status.
After the subtasks are migrated, the user side and the MEC container side need to register information with the distributed regional service center before starting to execute the subtasks. The information registered by the user side comprises: user presence information, user signal strength information under the current MEC server, and subtask lists (including user subtask lists and container subtask lists). The information registered by the MEC container end comprises: container online information and subtask lists. The subtask list records the subtasks that the container side/user side needs to execute.
In the invention, the online information and the signal strength information registered by the user side and the MEC container side to the distributed regional service center adopt a node data format, refer to fig. 2 and fig. 3, wherein fig. 2 is a schematic diagram of the node data format provided by the application, and fig. 3 is a schematic diagram of a subtask list format provided by the application;
wherein the position of the task pointer describes the execution of the subtask.
For convenience of management, the invention uniformly adopts a node data format for the online information, the signal strength information and the subtask list, and the node data format is shown in fig. 2.
The data information of the added node/MEC _ number and node/serial _ number is provided by the distributed regional service center.
In fig. 2, a node/MEC _ number provides a serial number of an MEC server for a current user to provide a service; the/serial _ number is the service ranking serial number of the user; type is the information type of the book; the/status is the information status of the book.
For example, a user in an area served by the MEC server a (assuming that the service ranking number of the user is 10, and the signal strength under the current MEC server is-50 db (decibel to one milliwatt, abbreviated as dBm)) needs to execute a task composed of 5 subtasks, as shown in fig. 4, and if the subtasks 2, 3, and 5 need to be migrated to the MEC server and executed by the idle container 2, the node information that the user side and the container side need to be registered before executing the subtasks is shown in fig. 4.
Of course, it is easily understood that the first registration information and the second registration information may also be stored in the data storage area after the registration is completed.
S102: judging whether the user side is displaced or not according to the change rate of the signal intensity information; (ii) a
Specifically, the step may generally determine whether the change rate of the signal strength information is greater than a preset threshold, so as to determine whether the ue is displaced.
The user terminal is connected to an MEC server, and the MEC server provides services for the user. With the movement of a user, the distance between the user side and the MEC server is gradually increased, the transmission delay is increased, and in order to ensure the service experience quality of the user, the whole container of the MEC server is migrated to a new MEC server and is restored to be calculated again through a migration strategy between the MECs (the strategy comprehensively considers the factors of energy consumption, transmission cost and the like), so that the user is continuously served.
The size of the preset threshold is not particularly limited. For example, when the rate of change of the signal strength of the ue is smaller than the set value within t seconds, the ue is considered not to move, i.e. to perform a task under the MEC server currently providing service. Otherwise, the user is considered to be moving.
S103: if the user side does not displace, performing subtask migration according to the running state of the MEC server;
s104: if the user side is displaced, judging whether the user side carries out trans-regional displacement or not;
s105: if the user side carries out cross-region displacement, executing cross-region subtask migration;
s106: if the user side does not perform cross-regional displacement, performing subtask migration in the distributed regional service center;
when the user moves, whether the user moves under the same distributed regional service center is judged firstly. It should be noted that the distributed regional service center is composed of resource data areas of all MEC servers within a preset geographic location range.
Because each MEC server has certain calculation and storage capacity, the method selects N MEC servers with close geographic positions, and then each MEC server contributes a small resource group to form the distributed regional service center. The distributed regional service center not only manages the N resources, but also has the functions of caching and synchronizing data, managing the MEC server and the user and the like.
The user and the MEC server are connected in the same network through the base station. Generally, a user in one area is served by an MEC server in a relatively close geographical position, and the user migrates a subtask requiring migration calculation to the MEC server through task division and migration decision. Meanwhile, the user also needs to send the execution result of the subtask in time and receive the execution result of the subtask from the MEC container end.
Preferably, the MEC server includes an MEC container, a resource data area, and a data storage area.
The MEC server divides a part of resources as a data storage area, and can store the subtasks migrated from the user terminal and the execution data thereof, the subtask execution results sent from the user terminal and information from the distributed regional service center. In addition, one MEC server is composed of a plurality of containers, and the containers are only responsible for executing the sub tasks of migration and do not store data. Typically, a container serves only one user until the migrated subtasks are performed. As with the user side, the MEC server container side also needs to send the execution results of the subtasks and receive the execution results of the subtasks from the user side in time.
For user mobility under the same distributed regional service center:
and when the signal intensity change rate of the user side is larger than the set value, the user is considered to move. First, the distributed regional service center broadcasts all MEC servers managed by the same distributed regional service center, and the MEC servers monitor the mobile subscriber. Then, when other MEC servers monitor the user and the signal intensity change rate under the MEC servers is smaller than the set value, the MEC server responds to the distributed regional service center. And finally, the distributed regional service center migrates the related executed subtask result data to the corresponding MEC server data storage area, and meanwhile, the unexecuted subtasks are restored to the idle container to be executed according to the synchronized subtask list, and the node information is updated.
A user under the MEC server a needs to execute a task consisting of 5 sub-tasks, and the sub-tasks 2, 3 and 5 need to be migrated to the MEC server a and executed by the container 1. As shown in figure 5 of the drawings,
the method comprises the following steps: when the container 1 executes the subtask 5, the user moves. The user moves from the service scope of MEC server a to under MEC server B. At this point, a management event is triggered;
② to fourthly: the distributed regional service center broadcasts the MEC server under the management of the distributed regional service center, and at the moment, the MEC server B monitors the user and responds after the signal intensity change rate meets the requirement;
fifthly: the distributed regional service center transmits the input data of the subtask 5 (if the data storage area receives the execution result of the user terminal task 4, the input data are the execution results of the subtasks 3 and 4, otherwise, the input data are the execution result of the subtask 3) to the data storage area of the MEC server B;
sixthly, the method comprises the following steps: and restoring the unexecuted subtasks 5 to the idle container 10 according to the synchronized container subtask list to continue to execute, and simultaneously updating the node information. The updated node information is shown in fig. 6.
For mobility under different distributed regional service centers:
after the distributed regional service center broadcasts, no server responds, and then the user is considered to move out of the service range of the original distributed regional service center. Firstly, the original distributed regional service center broadcasts to other distributed regional service centers, and then the other distributed regional service centers broadcast and manage the MEC servers under the management of the distributed regional service centers. And then, the responding MEC server responds to the original distributed regional service center from the distributed regional service center. And finally, the original distributed regional service center migrates the unexecuted subtask data and the execution result data of the executed subtasks to the corresponding MEC server data storage area according to the subtask list and resumes execution in the idle container, and meanwhile, the user side and the container side register the node information again.
Similarly, following the example cited above, a user under MEC server a needs to execute a task consisting of 5 subtasks, and subtasks 2, 3, and 5 need to be migrated to MEC server a and executed by container 1. As shown in figure 7 of the drawings,
the method comprises the following steps: when the container 1 executes to the subtask 5, the user moves across the distributed regional service center;
② fifthly: at this time, after broadcasting, the MEC server A under the distributed regional service center B manages the user, and then the MEC server responds to the distributed regional service center B, and then the distributed regional service center B responds to the distributed regional service center A;
sixthly, the step of: finally, the distributed regional service center A transmits the data of the unexecuted subtask 5 and the input data of the subtask 5 (if the data storage area has received the execution result of the user terminal task 4, the input data are the execution results of the subtasks 3 and 4, otherwise, the input data are the execution result of the subtask 3) to the corresponding MEC server and restores the MEC server to the idle container 10 to continue executing, meanwhile, the user terminal and the container terminal register the node information again, and at the moment, the MEC container terminal registers the subtask list only with the subtask 5 information.
The core of the application is the construction of a distributed regional service center. Each MEC server contributes to a distributed regional service center consisting of a part of resources, and has the functions of caching and synchronizing data and managing the MEC servers and users. In addition, the establishment of the data storage area replaces the mode of storing data in the original container, and ensures that the data volume of migration can be reduced.
Secondly, whether the user migrates or not is distinguished by managing the registered/updated signal intensity information of the user side. Under the condition that the migration does not occur, the condition that the tasks fail due to equipment downtime or subtask execution errors is avoided by managing the online node information and the subtask list, the subtasks can be ensured to be executed smoothly at the container end and the user end, and the task completeness is finally ensured. Under the condition that a user moves, the distributed regional service center obtains the position information of the user by broadcasting to an MEC server or other distributed regional service centers under the management of the user, migrates the related data into a corresponding MEC server data storage area, recovers the execution and updates the related node information. The method reduces network delay and network load in a mode of reducing data transmission quantity, and improves the experience quality of users.
Based on the above embodiments, as a preferred embodiment, the method includes:
updating the online information of the MEC server every other first preset time;
updating a user subtask list at the user side every time a subtask is added or every time a subtask is completed, and updating a container subtask list at the MEC server;
and updating the signal strength information every second preset time.
In the process of executing the subtasks by the MEC container and the user side, the MEC container and the user side need to update the online information and the subtask list (i.e. update the position of the task pointer) to the distributed regional service center respectively for a first preset time and a second preset time, and in addition, the user side needs to update the signal intensity information of the user. Meanwhile, when the user side/MEC container side finishes one subtask, the corresponding subtask list also needs to be updated to the distributed regional service center in time. The first preset time and the second preset time are not particularly limited herein. In particular, the first preset time and the second preset time may be equal. It should be noted that when the ue presence sub-task is executed in the MEC container, the update frequency of the ue signal strength information should be at a higher level, and can be updated even in real time.
Based on the above embodiment, as a preferred embodiment, performing subtask migration according to the running state of the MEC server includes:
if the MEC server is down in part of the MEC containers, the distributed regional service center determines a task pointer according to a container subtask list updated by the down MEC container last time before the shutdown; migrating the unexecuted subtasks from the data storage area to a normal MEC container according to the task pointer for execution, and updating a container subtask list of the normal MEC container;
if the MEC server is completely crashed, the distributed regional service center determines the MEC server closest to the user side according to the signal intensity information, retrieves all container subtask lists of the crashed MEC server from the data storage area, and synchronizes the subtasks to the normal MEC server according to all the container subtask lists.
Firstly, in the process of executing a subtask at an MEC container end, when a certain or some registered containers in the MEC are down, the containers cannot update online information in time within t seconds, so that a management event is triggered. At this time, the distributed regional service center can restore the unexecuted subtasks from the data storage area to a new idle container to be continuously executed according to the position of the subtask list task pointer which is normally updated last time before the container is down, and meanwhile, the container information of the node/type is updated. As shown in fig. 8, if container 1 under MEC server a is executing migration subtasks 2, 3, 5, then:
the first step and the second step: if the container 1 goes down while executing the subtask 5, the container 1 cannot update the online information in time within t seconds, and the distributed regional service center triggers a management event;
③: the distributed regional service center restores the unexecuted subtasks 5 to the idle container 10 to be executed according to the subtask list of the container, and meanwhile, the updated node information is shown in fig. 9.
When the whole MEC server is down, the corresponding resources forming the distributed regional service center will disappear, the data in the data storage area will also disappear, and meanwhile, the MEC server will not provide services for the users in the region. At this time, since the distributed regional service center manages the resources shared by the MEC servers, it will trigger a management event, it will select another MEC server closer to the user geographical location to provide services for the user, and since the user and the previously registered/updated node information of the MEC container end are synchronized, the distributed regional service center can restore the migrated subtask in the new MEC idle container according to the subtask list of the container end, and update the node information at the same time. It should be noted that, since the present invention does not synchronize the actual execution of the subtasks in order to reduce the network load, it is necessary to restore the task pointer in the container-side task list to the registration-time state (i.e., to re-execute the migrated subtask) in updating the node information.
Referring to FIG. 10, container 1 under MEC Server A is executing migration subtasks 2, 3, 5, if container 1 is executing subtask 5, then
Firstly, the following steps: the method comprises the following steps that a whole MEC server is down, and a distributed regional service center triggers a management event;
③: the distributed regional service center selects an MEC server B which is close to the geographical position of the user to provide service for the user;
fourthly, the method comprises the following steps: the distributed regional service center restores all the migrated subtasks 2, 3, and 5 to the idle container 10 according to the synchronized container subtask list, and executes the migrated subtasks again, and meanwhile, the updated node information is as shown in fig. 11 (if the service ranking sequence number of the user at the MEC server a is 10, and the service ranking sequence number at the MEC server B is 11).
When the container end/user end exceeds t seconds (possibly due to execution errors) and does not reach the distributed regional service center to update the subtask list, a management event is triggered, so that the distributed regional service center restores the container end/user end task list to the last normal update state, and the corresponding user end/container end continues to execute from the normal subtask state to ensure the task completeness.
And when the user side is down, the task execution is cancelled.
The present application also provides a computer readable storage medium having stored thereon a computer program which, when executed, may implement the steps provided by the above-described embodiments. The storage medium may include: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. For the system provided by the embodiment, the description is relatively simple because the system corresponds to the method provided by the embodiment, and the relevant points can be referred to the method part for description.
The principles and embodiments of the present application are explained herein using specific examples, which are provided only to help understand the method and the core idea of the present application. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
It is further noted that, in the present specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Claims (8)
1. A task migration method of an MEC server is characterized by comprising the following steps:
acquiring signal intensity information of a user side under a current MEC server;
judging whether the user side is displaced or not according to the change rate of the signal intensity information;
if the user side is not displaced, performing subtask migration according to the running state of the MEC server;
if the user side is displaced, judging whether the user side carries out trans-regional displacement or not;
if the user side carries out cross-region displacement, executing cross-region subtask migration;
if the user side does not perform cross-regional displacement, performing subtask migration in the distributed regional service center;
the distributed regional service center is composed of resource data areas of all MEC servers in a preset geographic position range;
updating the online information of the MEC server every other first preset time;
updating a user subtask list at a user side every time one subtask is added or every time one subtask is completed, and updating a container subtask list at the MEC server;
and updating the signal strength information every other second preset time.
2. The task migration method according to claim 1, comprising:
the user registers first registration information with a distributed regional service center, wherein the first registration information comprises user online information, signal strength information of the user under the MEC server and the user subtask list;
registering second registration information by the MEC container to a distributed regional service center, wherein the second registration information comprises container online information and the container subtask list;
wherein the MEC server comprises an MEC container, the resource data area and a data storage area.
3. The task migration method according to claim 2, wherein the user presence information, the signal strength information, the user subtask list, the container presence information, and the container subtask list all adopt a node data format.
4. The task migration method according to claim 3, wherein the node data format comprises an MEC server sequence, a service ranking sequence number of a user, a registered information type, and a registered information status.
5. The task migration method according to claim 2, further comprising:
storing the first registration information and the second registration information in the data storage area.
6. The task migration method according to claim 5, wherein performing subtask migration according to the running state of the MEC server comprises:
if the MEC server is down, the distributed regional service center determines a task pointer according to the container subtask list updated by the down MEC container for the last time before the shutdown; migrating the unexecuted subtasks from the data storage area to a normal MEC container according to the task pointer for execution, and updating a container subtask list of the normal MEC container;
if the MEC server is completely down, the distributed regional service center determines the MEC server closest to the user side according to the signal intensity information, calls all container subtask lists of the down MEC server from the data storage area, and synchronizes the subtasks to the normal MEC server according to all the container subtask lists.
7. An MEC server, comprising:
the resource data areas of all MEC servers in a preset geographic range form a distributed regional service center;
the data storage area is used for storing subtask data, subtask execution data, execution result data and instruction information of the distributed regional server center by a user;
and the MEC container is used for executing the user subtasks.
8. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the task migration method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910595116.7A CN110311979B (en) | 2019-07-03 | 2019-07-03 | Task migration method of MEC server and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910595116.7A CN110311979B (en) | 2019-07-03 | 2019-07-03 | Task migration method of MEC server and related device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110311979A CN110311979A (en) | 2019-10-08 |
| CN110311979B true CN110311979B (en) | 2022-05-17 |
Family
ID=68078096
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910595116.7A Active CN110311979B (en) | 2019-07-03 | 2019-07-03 | Task migration method of MEC server and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110311979B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP4091317A1 (en) * | 2020-01-15 | 2022-11-23 | Samsung Electronics Co., Ltd. | Method and system for improvements in and relating to microservices for mec networks |
| CN111600648B (en) * | 2020-05-25 | 2022-02-22 | 中国矿业大学 | Mobile relay position control method of mobile edge computing system |
| CN113556727B (en) * | 2021-07-19 | 2022-08-23 | 中国联合网络通信集团有限公司 | Data transmission method and system of cloud equipment based on mobile container |
| CN115051931B (en) * | 2022-06-08 | 2024-03-08 | 广东工业大学 | Virtual avatar migration method based on reinforcement learning and control system thereof |
Family Cites Families (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9503333B2 (en) * | 2013-08-08 | 2016-11-22 | Level 3 Communications, Llc | Content delivery methods and systems |
| CN107391239B (en) * | 2016-03-11 | 2021-06-22 | 阿里巴巴集团控股有限公司 | Scheduling method and device based on container service |
| CN106125038B (en) * | 2016-06-15 | 2019-03-22 | 北京工业大学 | Indoor wireless positioning method based on edge calculations and Bayes posterior probability model |
| US10484451B2 (en) * | 2016-10-18 | 2019-11-19 | Huawei Technologies Co., Ltd. | Virtual network state management in mobile edge computing |
| CN108076488B (en) * | 2016-11-14 | 2021-01-05 | 华为技术有限公司 | Method, device and system for cell switching |
| CN106933508B (en) * | 2017-02-14 | 2020-05-12 | 深信服科技股份有限公司 | Application container migration method and device |
| US11726813B2 (en) * | 2017-08-01 | 2023-08-15 | Cable Television Laboratories, Inc. | Systems and methods for establishing scalable credential creation and access |
| CN108494612B (en) * | 2018-01-19 | 2021-06-08 | 西安电子科技大学 | Network system for providing mobile edge computing service and service method thereof |
| CN108762882B (en) * | 2018-04-02 | 2021-12-21 | 杭州朗和科技有限公司 | Docker container migration method, migration device, medium and computing equipment |
| CN109413676B (en) * | 2018-12-11 | 2021-11-02 | 西北大学 | Combined downstream and upstream edge calculation migration method in ultra-dense heterogeneous network |
| CN109889599B (en) * | 2019-03-07 | 2020-08-28 | 北京邮电大学 | Data processing method and system |
-
2019
- 2019-07-03 CN CN201910595116.7A patent/CN110311979B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN110311979A (en) | 2019-10-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110311979B (en) | Task migration method of MEC server and related device | |
| CN111262906A (en) | Method for unloading mobile user terminal task under distributed edge computing service system | |
| CN111338774B (en) | Distributed timing task scheduling system and computing device | |
| CN109257440A (en) | A kind of service discovery and client load equalization methods based on service register center | |
| CN111338773B (en) | Distributed timing task scheduling method, scheduling system and server cluster | |
| WO2018072708A1 (en) | Cloud platform service capacity reduction method, apparatus, and cloud platform | |
| US10491535B2 (en) | Adaptive data synchronization | |
| CN113068232B (en) | Switching method and device of edge application server | |
| CN109995844B (en) | Method and device for realizing control plane resource migration and network function entity | |
| EP3873066A1 (en) | Method for managing resource state information, and resource downloading system | |
| CN108337691A (en) | A kind of services migrating method and system of mobile edge user oriented movement | |
| CN102546226B (en) | Multi-node-based network service provision system and method | |
| CN109995845A (en) | A kind of implementation method, device and the network functional entity of control plane resource migration | |
| US11102289B2 (en) | Method for managing resource state information and system for downloading resource | |
| CN101710902A (en) | Unstructured P2P network, data searching method thereof and index updating method thereof | |
| CN115499447A (en) | Cluster master node confirmation method and device, electronic equipment and storage medium | |
| CN111082954B (en) | Network element load balancing method and network equipment | |
| WO2022001555A1 (en) | Wireless resource management method, storage medium, and electronic device | |
| CN113326100A (en) | Cluster management method, device and equipment and computer storage medium | |
| CN112243243B (en) | Network slice implementation method, entity and system | |
| WO2023071999A1 (en) | User matching method and apparatus, and device and storage medium | |
| CN110213778B (en) | Method and device for intelligently pairing main network element and standby network element | |
| CN104468674B (en) | Data migration method and device | |
| CN116389454A (en) | Data downloading system | |
| CN112131142B (en) | Method, system, equipment and medium for quickly caching data set |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |