Service migration control method, device and system

Abstract

The present application provides a service migration control method, device and system, which is applied to the MEC in the edge-cloud collaborative system. The method includes: after receiving the pre-access signal sent by the mobile station terminal when entering the first-level fence of the current MEC to be accessed, obtaining the weight rating and feeding back; after receiving the quasi-migration instruction sent by the mobile station terminal when it determines the current MEC to be accessed as the target MEC and enters its second-level fence, performing service synchronization; when it is detected that the mobile station terminal enters its third-level fence, establishing a link with the mobile station terminal and sending a switching instruction to the mobile station terminal to complete the service migration. The service migration of the mobile station terminal in the present application is based on edge-edge collaboration, which makes full use of the computing power of MEC and can form a wide-area-scale service continuity support capability. The present application also adopts a multi-level dynamic migration method to smoothly switch services, effectively increasing the continuity and reliability of services.

Description

Technical Field

[0001] The present application relates to the field of intelligent transportation technology, and in particular to a service migration control method, device and system. Background Art

[0002] McKinsey predicts that by 2040, smart transportation service providers will account for 55% of PKMT (total passenger kilometers by vehicle type), while privately owned autonomous vehicles will account for only 11%. China is expected to become the world's largest autonomous driving market, and the promotion of autonomous driving will grow in tandem with travel services. Cross-node access and continuity support technology based on edge-cloud collaboration is one of the key capabilities for achieving autonomous driving scenarios on open roads (under wide-area conditions). It will effectively supplement the existing autonomous driving technology system and provide vehicles with safer, more reliable service quality and driving experience across nodes. Compared with traditional edge-cloud collaboration solutions, the cross-edge cloud continuity support capabilities for autonomous driving scenarios require higher requirements. At the same time, it supports driving decisions through predictive algorithms, automated service orchestration, and information migration.

[0003] However, in the existing traditional solutions, the edge cloud (Multi-access Edge Computing, MEC for short) operates relatively independently, and autonomous vehicles obtain application service support within the access range of a single MEC. There is a lack of connection channels and point information interaction mechanisms between MECs (for example, under current conditions, cross-MEC service scenarios must be handled through a two-level mode of node->center->node to achieve information interaction and synchronization, with long links and high latency). The central cloud is mainly responsible for application library management, release management, and operation monitoring. The MEC and the central cloud mainly synchronize operation status data, mainly for operation and maintenance monitoring support. The proportion of business collaboration is relatively low, and there is a lack of effective integration of edge collaboration. This solution is mainly aimed at scenarios with limited access requirements such as closed campuses and factory areas, and cannot effectively support wide-area, cross-MEC service continuity management requirements.

[0004] Traditional edge-cloud collaboration solutions often need to deal with the following events in terms of cross-edge node service continuity support:

[0005] (1) It is impossible to effectively manage the coordinated scheduling between edge-cloud and edge-edge nodes. Each MEC operates relatively independently and in a closed manner, making it difficult to form large-scale (wide-area) cross-site service continuity support capabilities.

[0006] (2) Limited by the constraints of the traditional solution architecture and communication links, the implementation of service migration management and continuity support requires the central cloud to undertake support tasks such as migration process management, predictive analysis modeling, and status monitoring. The high load and high latency caused by centralization require high hardware costs, which is not conducive to the practical promotion of the solution;

[0007] After the MEC access support scope is updated, the central cloud synchronization update and prediction model reconstruction require a long period of time, and twin synchronization cannot be performed in real time at the information system logic layer.

[0008] Traditional cross-site (cross-region) information service migration process description:

[0009] 1. The terminal sends real-time status data (including location, moving direction, moving speed, etc.) and task delay information to the central cloud;

[0010] 2. The central cloud uses a prediction algorithm to predict the migration destination server based on the terminal data and sends the destination server information to the source server;

[0011] 3. The source server transfers the service environment and data to the destination server and, before actually switching, regularly transmits real-time computing data to the destination server.

[0012] 4. When the terminal moves within the range of the destination server and reaches the preset distance threshold, the actual service switch is executed. The source server stops providing services, and the destination server starts providing services to the terminal.

[0013] 5. Complete service migration.

[0014] As can be seen from the above process, modeling, prediction, service scheduling algorithms and status monitoring all run on the central cloud server. The prediction algorithm requires a lot of historical data, especially in the vehicle-road collaboration scenario. To achieve accurate prediction of service status, in addition to terminal status data, edge cloud computing road test fusion perception data is often required. The data of each edge cloud computing must also be transmitted to the operation center server in real time, which not only causes high load and high latency on the cloud center server, but also causes untimely updates of dynamic road condition information data and prediction model data, resulting in poor prediction accuracy, high service latency and service interruption problems.

[0015] Current solutions offer some optimizations, but they still place the data acquisition, prediction, and scheduling modules on cloud-centric servers. This architectural design lacks edge-to-edge collaboration and centralized management, leading to high load and latency. Furthermore, cross-site migrations are prone to the "ping-pong" phenomenon, where service migrations are repeated back and forth. Summary of the Invention

[0016] The technical purpose to be achieved by the embodiments of the present application is to provide a service migration control method, device and system to solve problems such as high service latency in the current service migration process.

[0017] To solve the above technical problems, the present application provides a service migration control method, which is applied to MEC in an edge-cloud collaborative system, including:

[0018] Upon receiving a pre-access signal from a mobile terminal, obtaining a weight rating for the mobile terminal and sending the weight rating to the mobile terminal, wherein the mobile terminal sends the pre-access signal when entering the first-level fence of the MEC to be accessed;

[0019] Upon receiving a quasi-migration instruction sent by the mobile station terminal, performing service synchronization, wherein the mobile station terminal sends the quasi-migration instruction when determining the current MEC to be accessed as the target MEC and entering the second-level fence of the current MEC to be accessed;

[0020] When it is detected that the mobile station terminal enters the third-level fence of the current MEC to be accessed, a link is established with the mobile station terminal and a switching instruction is sent to the mobile station terminal to complete the service migration. The switching instruction is used to disconnect the mobile station terminal from the source MEC, wherein the distances from the first-level fence, the second-level fence, and the third-level fence to the current MEC to be accessed decrease in sequence.

[0021] Specifically, in the service migration control method described above, obtaining a weight rating for a mobile station terminal includes:

[0022] Acquire service requirement information required by the mobile terminal, the service requirement information including at least one of: a service running state, a first middleware dependent on the service, and infrastructure information;

[0023] Deployment resources are obtained based on the service demand information and service migration parameters, where the service migration parameters include at least one of service migration size, quantity, and estimated deployment time, and the deployment resources include at least one of hardware resources, network resources, and time resources;

[0024] Determine the priority of the mobile terminal currently waiting to access the MEC based on the deployment resources, current load, MEC network environment rating, and access demand of the mobile terminal;

[0025] A weight rating is obtained based on the priority and the preset weight rating rules.

[0026] Preferably, in the service migration control method as described above, executing service synchronization includes:

[0027] Sending a first request message to the regional service center, and receiving the target middleware, target service image, and target configuration information issued by the regional service center according to the first request message, wherein the first request message is used to request the target middleware, target service image, and target configuration information corresponding to the mobile terminal from the regional service center;

[0028] Deploy according to the target middleware, target service image and target configuration information to obtain a first deployment result;

[0029] If the first deployment result is successful, the deployment information is sent to the mobile terminal, and the real-time data information and source MEC information sent by the mobile terminal are received;

[0030] Send a historical data request of the mobile station terminal to the source MEC according to the source MEC information, and receive the historical data of the mobile station terminal sent by the source MEC.

[0031] Preferably, the service migration control method as described above further includes:

[0032] When a disconnection command is received from the mobile terminal or the mobile terminal is detected to have returned to the zero-level fence, the service is released and the target application is marked according to the result of the migration algorithm. The zero-level fence is located on the side of the first-level fence away from the second-level fence.

[0033] When the cleanup node of the preset cycle is reached, the target application is released, the application release result is obtained, and the application release result is uploaded to the regional service center.

[0034] Optionally, the service migration control method described above, when used for the first time by the currently accessed MEC, further includes:

[0035] Basic resources for supporting services, application service components for mobile terminals, service migration prediction components and service migration management engines are loaded from the regional service center and initialized.

[0036] Specifically, the service migration control method described above, initialization includes:

[0037] Mobile basic services are launched;

[0038] Mobile basic service preprocessing;

[0039] The mobile terminal registers and logs in for the first time.

[0040] Preferably, in the service migration control method described above, the mobile basic service launch includes:

[0041] Initialize basic service preparation based on the loaded configuration parameters, middleware, and application image manifests;

[0042] Sending a second request message to the regional service center, and receiving the middleware dependency package, basic service image, and basic configuration information issued by the regional service center according to the second request message, where the second request message is used to request the middleware dependency package, basic service image, and basic configuration information from the regional service center;

[0043] Deploy according to the middleware dependency package, basic service image and basic configuration information to obtain a second deployment result;

[0044] If the second deployment result is successful, the mobile basic service online signal is uploaded to the regional service center.

[0045] Preferably, in the service migration control method described above, the mobile basic service preprocessing includes:

[0046] Detect the collaborative gateway service status, identity authentication service status, and service migration management engine status, and receive the MEC topology relationship and mobile terminal identity information periodically issued by the regional service center.

[0047] Preferably, in the service migration control method as described above, the first registration and login of the mobile station terminal includes:

[0048] When receiving registration information sent by the mobile station terminal, determining whether the registration information is valid;

[0049] When the registration information is determined to be valid, the registered information and first positioning information of the mobile terminal are uploaded to the regional service center, and the login authentication code is fed back to the mobile terminal.

[0050] Preferably, the service migration control method as described above, after establishing a link with a mobile terminal or receiving a quasi-migration instruction sent by the mobile terminal, further comprises:

[0051] Obtaining the total delay of the service task corresponding to the mobile terminal and the delay requirements corresponding to the first-level fence, the second-level fence, the third-level fence, and the zero-level fence respectively according to a preset migration algorithm;

[0052] According to the total delay and the delay requirement, it is determined whether the mobile station terminal meets the delay requirements corresponding to the first-level fence, the second-level fence, the third-level fence and the zero-level fence respectively.

[0053] Another preferred embodiment of the present application further provides a service migration control method, applied to a mobile terminal, comprising:

[0054] After receiving a first signal from the source MEC indicating that the mobile station terminal has entered the first-level fence of at least one adjacent MEC to be accessed, the source MEC sends a pre-access signal to the MEC to be accessed;

[0055] Receive a weight rating sent by at least one MEC to be accessed, and determine one of them as a target MEC based on the weight rating sent by each MEC to be accessed and a preset algorithm;

[0056] Upon receiving a second signal from the source MEC or the target MEC, the mobile terminal enters the second level fence of the target MEC, sending a quasi-migration instruction to the target MEC;

[0057] When receiving a handover instruction sent by the target MEC, the link with the source MEC is disconnected, wherein the handover instruction is sent by the target MEC when it detects that the mobile terminal enters the third-level fence of the target MEC.

[0058] Preferably, the service migration control method as described above further includes:

[0059] Send registration information to the first MEC connected to the mobile station terminal, and receive the login authentication code fed back by the first MEC.

[0060] Another preferred embodiment of the present application further provides a control device, applied to MEC, comprising:

[0061] A first processing module is configured to, upon receiving a pre-access signal sent by a mobile station terminal, obtain a weight rating for the mobile station terminal and send the weight rating to the mobile station terminal, wherein the mobile station terminal sends the pre-access signal when entering the first-level fence of the current MEC;

[0062] A second processing module is configured to perform service synchronization upon receiving a quasi-migration instruction sent by a mobile station terminal, wherein the mobile station terminal sends the quasi-migration instruction when determining the current MEC to be accessed as the target MEC and entering the second-level fence of the current MEC to be accessed;

[0063] The third processing module is used to establish a link with the mobile station terminal and send a switching instruction to the mobile station terminal to complete service migration when it is detected that the mobile station terminal enters the third-level fence of the current MEC to be accessed. The switching instruction is used to disconnect the mobile station terminal from the source MEC, wherein the distances from the first-level fence, the second-level fence, and the third-level fence to the current MEC to be accessed decrease in sequence.

[0064] Specifically, in the control device as described above, the first processing module includes:

[0065] The first processing unit is configured to obtain service requirement information required by the mobile station terminal, where the service requirement information includes at least one of a service operation status, a first middleware dependent on the service, and infrastructure information;

[0066] a second processing unit, configured to obtain deployment resources based on the service demand information and service migration parameters, where the service migration parameters include at least one of a service migration size, a quantity, and an estimated deployment time, and the deployment resources include at least one of hardware resources, network resources, and time resources;

[0067] The third processing unit is configured to determine the priority of the mobile terminal to be currently accessed by the MEC based on the deployment resources, the current load, the MEC network environment rating, and the access demand of the mobile terminal;

[0068] The fourth processing unit is used to obtain a weight rating according to the priority and a preset weight rating rule.

[0069] Preferably, in the control device as described above, the second processing module includes:

[0070] a fifth processing unit, configured to send a first request message to the regional service center, and receive target middleware, target service image, and target configuration information issued by the regional service center in response to the first request message, wherein the first request message is used to request the regional service center for target middleware, target service image, and target configuration information corresponding to the mobile terminal;

[0071] a sixth processing unit, configured to perform deployment according to the target middleware, the target service image, and the target configuration information to obtain a first deployment result;

[0072] a seventh processing unit, configured to, if the first deployment result is successful, send deployment information to the mobile station terminal, and receive real-time data information and source MEC information sent by the mobile station terminal;

[0073] The eighth processing unit is configured to send a historical data request of the mobile station terminal to the source MEC according to the source MEC information, and receive the historical data of the mobile station terminal sent by the source MEC.

[0074] Preferably, the control device as described above further includes:

[0075] an eighth processing module, configured to release the service upon receiving a disconnection instruction sent by the mobile terminal or detecting that the mobile terminal has returned to a zero-level fence, and mark the target application according to a migration algorithm result, wherein the zero-level fence is located on a side of the first-level fence away from the second-level fence;

[0076] The ninth processing module is used to release the target application when the cleanup node of the preset cycle is reached, obtain the application release result, and upload the application release result to the regional service center.

[0077] Optionally, the control device as described above, when the MEC to be accessed is used for the first time, further includes:

[0078] The tenth processing module is used to load basic resources for supporting services, application service components for mobile terminals, service migration prediction components and service migration management engines from the regional service center and initialize them.

[0079] Specifically, in the control device as described above, the tenth processing module includes:

[0080] The ninth processing unit, mobile basic services are launched;

[0081] The tenth processing unit, mobile basic service preprocessing;

[0082] The eleventh processing unit is the first registration and login of the mobile station terminal.

[0083] Preferably, in the control device as described above, the ninth processing unit includes:

[0084] A first sub-processing unit is configured to initialize basic service preparation according to the loaded configuration parameters, middleware, and application image manifest;

[0085] a second sub-processing unit, configured to send a second request message to the regional service center, and receive a middleware dependency package, a basic service image, and basic configuration information issued by the regional service center in response to the second request message, wherein the second request message is used to request the middleware dependency package, the basic service image, and the basic configuration information from the regional service center;

[0086] The third sub-processing unit is configured to perform deployment according to the middleware dependency package, the basic service image, and the basic configuration information to obtain a second deployment result;

[0087] The fourth sub-processing unit is configured to upload a mobile basic service online signal to the regional service center if the second deployment result is successful deployment.

[0088] Preferably, in the control device as described above, the tenth processing unit includes:

[0089] The fifth sub-processing unit is used to detect the collaborative gateway service status, identity authentication service status, and service migration management engine status, and receive the MEC topology relationship and mobile terminal identity information periodically issued by the regional service center.

[0090] Preferably, the control device as described above, the eleventh processing unit is configured to include:

[0091] a sixth sub-processing unit, configured to determine whether the registration information is valid when receiving the registration information sent by the mobile station terminal;

[0092] The seventh sub-processing unit is configured to upload the registered information and the first positioning information of the mobile terminal to the regional service center when it is determined that the registration information is valid, and feed back a login authentication code to the mobile terminal.

[0093] Preferably, the control device as described above further includes:

[0094] an eleventh processing module, configured to obtain, according to a preset migration algorithm, a total delay of a service task corresponding to the mobile station terminal, and delay requirements corresponding to the first-level fence, the second-level fence, the third-level fence, and the zero-level fence, respectively;

[0095] The twelfth processing module is used to determine whether the mobile station terminal meets the delay requirements corresponding to the first-level fence, the second-level fence, the third-level fence and the zero-level fence respectively according to the total delay and the delay requirement.

[0096] Another preferred embodiment of the present application further provides a control device, applied to a mobile station terminal, comprising:

[0097] The fourth processing module is configured to send a pre-access signal to the MEC to be accessed after receiving a first signal sent by the source MEC indicating that the mobile station terminal has entered the first-level fence of at least one adjacent MEC to be accessed;

[0098] A fifth processing module is configured to receive a weight rating sent by at least one MEC to be accessed, and determine one of the MECs as a target MEC based on the weight rating sent by each MEC to be accessed and a preset algorithm;

[0099] A sixth processing module is configured to send a quasi-migration instruction to the target MEC upon receiving a second signal sent by the source MEC or the target MEC indicating that the mobile terminal has entered the second level fence of the target MEC;

[0100] The seventh processing module is configured to disconnect the link with the source MEC when receiving a handover instruction sent by the target MEC, wherein the handover instruction is sent when the target MEC detects that the mobile station terminal meets the third level fence of the target MEC.

[0101] Preferably, the control device as described above further includes:

[0102] The thirteenth processing module is used to send registration information to the first MEC connected to the mobile station terminal, and receive a login authentication code fed back by the first MEC.

[0103] Another preferred embodiment of the present application further provides an edge-cloud collaboration system, including:

[0104] Central cloud, regional service center, MEC as described above, and mobile terminal as described above;

[0105] Wherein, the central cloud is linked to at least one regional service center;

[0106] The Regional Service Center is linked to at least one MEC;

[0107] MEC is connected to mobile terminals;

[0108] Links between multiple MECs;

[0109] Links between multiple regional service centers.

[0110] Another preferred embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by the processor, the steps of the service migration control method applied to the MEC as described above are implemented, or the steps of the service migration control method applied to the mobile station terminal as described above are implemented.

[0111] Compared with the prior art, the service migration control method, device, and system provided in the embodiments of the present application have at least the following beneficial effects:

[0112] In this application, the service migration of mobile terminals is mainly implemented through edge-edge collaboration, that is, service migration is achieved synchronously through the services of the current MEC to be accessed and the source MEC, which fully utilizes the computing power of MEC and can share the computing pressure of the central cloud. At the same time, it gives full play to the characteristics of timely dynamic information and model updates of edge nodes, strengthens edge-cloud and edge-edge collaboration, and can form a wide-area and large-scale service continuity support capability. By setting up multiple fences and presenting service migration as multi-level dynamic migration according to the positional relationship between the mobile terminal and the fence, a multi-level dynamic migration method is implemented to smoothly switch services. While ensuring service latency, it effectively reduces the "ping-pong phenomenon" caused by cross-site service migration, increases service continuity and reliability, and can achieve real-time updates and synchronous reconstruction of digital twin access prediction models. BRIEF DESCRIPTION OF THE DRAWINGS

[0113] Figure 1 This is a flow chart of a service migration control method applied to MEC.

[0114] Figure 2 This is the second flow chart of the service migration control method applied to MEC;

[0115] Figure 3 This is the third flow chart of the service migration control method applied to MEC;

[0116] Figure 4 This is the fourth flow chart of the service migration control method applied to MEC;

[0117] Figure 5 This is the fifth flowchart of the service migration control method applied to MEC;

[0118] Figure 6 A flow chart of a service migration control method applied to a mobile terminal;

[0119] Figure 7 It is a structural diagram of the control device applied to MEC;

[0120] Figure 8 A schematic structural diagram of a control device applied to a mobile terminal;

[0121] Figure 9 This is a structural diagram of the edge-cloud collaborative system;

[0122] Figure 10 Schematic diagram of the location of the dynamic fence set between the source MEC and the target MEC. DETAILED DESCRIPTION

[0123] In order to make the technical problems, technical solutions and advantages to be solved by the present application clearer, the following will be described in detail with reference to the accompanying drawings and specific embodiments. In the following description, specific details such as specific configurations and components are provided only to help fully understand the embodiments of the present application. Therefore, it should be clear to those skilled in the art that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present application. In addition, for clarity and brevity, the description of known functions and structures has been omitted.

[0124] It should be understood that references throughout this specification to "one embodiment" or "an embodiment" mean that a particular feature, structure, or characteristic associated with the embodiment is included in at least one embodiment of the present application. Therefore, the appearances of "in one embodiment" or "in an embodiment" throughout this specification do not necessarily refer to the same embodiment. Furthermore, these particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0125] In the various embodiments of the present application, it should be understood that the size of the serial numbers of the following processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0126] It should be understood that the term "and / or" in this document simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0127] In the embodiments provided herein, it should be understood that "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B based solely on A; B can also be determined based on A and / or other information.

[0128] See also Figure 1A preferred embodiment of the present application provides a service migration control method, which is applied to MEC in an edge-cloud collaborative system, including:

[0129] Step S101: upon receiving a pre-access signal from a mobile terminal, obtaining a weight rating for the mobile terminal and sending it to the mobile terminal, wherein the mobile terminal sends the pre-access signal when entering the first level fence of the MEC to be accessed;

[0130] Step S102: upon receiving a quasi-migration instruction sent by the mobile station terminal, performing service synchronization, wherein the mobile station terminal sends the quasi-migration instruction when determining the current MEC to be accessed as the target MEC and entering the second-level fence of the current MEC to be accessed;

[0131] Step S103: When it is detected that the mobile station terminal enters the third-level fence of the current MEC to be accessed, a link is established with the mobile station terminal and a switching instruction is sent to the mobile station terminal to complete the service migration. The switching instruction is used to disconnect the mobile station terminal from the source MEC, wherein the distances from the first-level fence, the second-level fence, and the third-level fence to the current MEC to be accessed decrease in sequence.

[0132] In one embodiment of the present application, a control method for service migration in an edge-cloud collaborative system is provided. Specifically, the method applied in MEC includes: the current MEC to be accessed can receive a pre-access signal sent by a mobile station terminal when the mobile station terminal enters the first-level fence of the current MEC to be accessed, that is, when the mobile station terminal may need the service of the current MEC to be accessed; after receiving the pre-access signal, the current MEC to be accessed will perform a self-test operation, obtain a weight rating for the mobile station terminal through self-test and send it to the mobile station terminal, so that the mobile station terminal can select the optimal MEC to be accessed according to the weight rating sent by at least one MEC to be accessed, thereby ensuring the service quality after service migration; at this time, the current MEC to be accessed can receive a quasi-migration instruction sent by the mobile station terminal, and if the quasi-migration instruction is received, the mobile station terminal will receive the quasi-migration instruction. The migration instruction is sent to the current MEC to be accessed, and it can be determined that the current MEC to be accessed is the optimal MEC to be accessed, and the mobile station terminal has entered the second-level fence of the current MEC to be accessed. At this time, service synchronization is performed, that is, the data information related to the mobile station terminal is synchronized to the current MEC to be accessed, so as to provide timely and accurate services to the mobile station terminal after the subsequent service migration is completed; at the same time, the location information and latency of the mobile station terminal are also monitored. When it is detected that the mobile station terminal enters the third-level fence of the current MEC to be accessed, it is determined that the source MEC that originally provided services to the mobile station terminal will be unable to provide services. At this time, the current MEC to be accessed will formally establish a link with the mobile station terminal and send a switching instruction to the mobile station terminal, so that the mobile station terminal disconnects the link with the source MEC according to the switching instruction, thereby completing the service migration.

[0133] It should be noted that the first fence, the second fence, and the third fence are divided according to geographical regions and are used to describe the positional relationship between the location of the mobile station terminal and the MEC. This positional relationship can be determined based on latency and service loss, and the distances from the first fence, the second fence, and the third fence to the MEC location decrease in sequence. Preferably, the first fence, the second fence, and the third fence are all located within the overlapping range between adjacent MECs (specifically, the overlapping range between the current MEC to be accessed and the source MEC).

[0134] In summary, in this embodiment, the service migration of mobile station terminals is mainly achieved through edge-edge collaboration, that is, service migration is achieved synchronously through the services of the current MEC to be accessed and the source MEC, which fully utilizes the computing power of MEC and can share the computing pressure of the central cloud. At the same time, it gives full play to the characteristics of timely dynamic information and model updates of edge nodes, strengthens edge-cloud and edge-edge collaboration, and can form a wide-area and large-scale service continuity support capability. By setting up multiple fences and presenting service migration as multi-level dynamic migration based on the positional relationship between the mobile station terminal and the fence, smooth switching of services is achieved. While ensuring service latency, it effectively reduces the "ping-pong phenomenon" caused by cross-site service migration, increases service continuity and reliability, and can achieve real-time updates and synchronous reconstruction of digital twin access prediction models.

[0135] See also Figure 2 Specifically, in the service migration control method described above, obtaining a weight rating for a mobile station terminal includes:

[0136] Step S201: obtaining service requirement information required by a mobile terminal, where the service requirement information includes at least one of: a service operation status, a first middleware dependent on the service, and infrastructure information;

[0137] Step S202: Deployment resources are obtained based on the service demand information and service migration parameters, where the service migration parameters include at least one of service migration size, quantity, and estimated deployment time, and the deployment resources include at least one of hardware resources, network resources, and time resources.

[0138] Step S203: Determine the priority of the current MEC to be accessed for the mobile terminal based on the deployed resources, current load, MEC network environment rating, and access demand of the mobile terminal;

[0139] Step S204: Obtain a weight rating according to the priority and a preset weight rating rule.

[0140] In a specific embodiment of the present application, when MEC performs the first self-check, it obtains the service demand information required by the mobile station terminal, and calculates the deployment resources based on the service demand information and the service migration parameters of the required service, wherein it should be noted that the service demand information includes: the service operation status, the first middleware on which the service depends, and at least one of the infrastructure information; the service migration parameters include: at least one of the service migration size, quantity, and deployment estimated time; the deployment resources include: at least one of hardware resources, network resources, and time resources; and then, based on the deployment resources, the current load of the MEC to be accessed, the MEC network environment rating, and the access requirement of the mobile station terminal (whether access is required, whether the mobile station terminal must replace the MEC for service), the priority of the service provided by the MEC to be accessed to the mobile station terminal is determined; further, the MEC to be accessed can be weighted according to the obtained priority and the preset weight rating rules to obtain the weight rating for the mobile station terminal.

[0141] See also Figure 3 Preferably, the service migration control method as described above, performing service synchronization includes:

[0142] Step S301: Send a first request message to a regional service center, and receive target middleware, target service image, and target configuration information issued by the regional service center based on the first request message. The first request message is used to request the regional service center for target middleware, target service image, and target configuration information corresponding to a mobile terminal.

[0143] Step S302, deploying according to the target middleware, target service image and target configuration information to obtain a first deployment result;

[0144] Step S303: If the first deployment result is successful, the deployment information is sent to the mobile terminal, and the real-time data information and source MEC information sent by the mobile terminal are received;

[0145] Step S304: Send a historical data request of the mobile station terminal to the source MEC according to the source MEC information, and receive the historical data of the mobile station terminal sent by the source MEC.

[0146] In another specific embodiment of the present application, when the currently accessed MEC performs service synchronization, a first request message will be sent to the regional service center, wherein the regional service center is connected to the MEC and the central cloud at both ends, serving as an intermediate mechanism for connecting the MEC and the central cloud, wherein the central cloud platform serves as the central management unit, and the central cloud provides a resource registration entry through MEC management, registering the service resources required by the regional cloud and edge cloud to the global application warehouse; the central cloud is responsible for the configuration of migration rules, management of cloud platform services at all levels (service availability), global maintenance of the point network (topology) relationship of the regional cloud and edge cloud, and the identity information of the mobile terminal. The regional service center is responsible for distributing the migration service software package and its version of the central cloud, the configuration of the service, the point network relationship of the regional edge cloud, the static identity information of the mobile station, etc., while maintaining the migration service library version and mapping relationship required by the mobile terminal, and dynamically calculating the MEC that the mobile terminal can access based on the service availability on the MEC and the service fence between the MECs, thereby sharing the computing pressure of the central cloud.

[0147] The first request information is used to request the target middleware, target service image and target configuration information corresponding to the mobile station terminal from the regional service center. The regional service center will determine whether the target middleware, target service image and target configuration information corresponding to the mobile station terminal currently exist based on the first request information. If so, the target middleware, target service image and target configuration information will be directly sent down. If not, the target middleware, target service image and target configuration information will be first requested from the central cloud, and then sent down to the current MEC to be accessed after receiving feedback from the central cloud. After receiving the target middleware, target service image, and target configuration information, the MEC to be connected will deploy according to the target middleware, target service image, and target configuration information. After deployment is complete, it will perform a second self-test to obtain a first deployment result. If the first deployment result is deployment success, it is determined that the MEC to be connected can currently provide services to the mobile terminal. Therefore, the corresponding deployment information is sent to the mobile terminal, allowing the mobile terminal to transmit real-time data and source MEC data according to the deployment information. After receiving the source MEC information sent by the mobile terminal, the MEC will also send a historical data request for the mobile terminal to the source MEC based on the source MEC information and receive the historical data sent by the source MEC. This ensures that the MEC has the historical data related to the mobile terminal, thereby completing service synchronization and providing accurate services to the mobile terminal. If the second self-test result indicates deployment failure, redeployment is preferably performed. If the number of redeployments exceeds a first preset value, a service synchronization failure message is fed back. The source MEC information includes, but is not limited to, identity information of the source MEC.

[0148] See also Figure 4Preferably, the service migration control method as described above further includes:

[0149] Step S401: upon receiving a disconnect command from a mobile terminal or detecting that the mobile terminal has returned to a zero-level fence, a service is released, and a target application is marked according to a migration algorithm result. The zero-level fence is located on the side of the first-level fence away from the second-level fence.

[0150] Step S402: When the preset period of cleanup is reached, the target application is released, an application release result is obtained, and the application release result is uploaded to the regional service center.

[0151] In another preferred embodiment of the present application, when the current MEC receives a disconnect command from a mobile terminal, it can determine that the mobile terminal needs to disconnect from the current MEC. Before reconnecting, the current MEC no longer needs to provide services to the corresponding mobile terminal, or when the mobile terminal returns to the zero-level fence that is close to the edge of the MEC's ​​communication range, especially when the mobile terminal returns to the zero-level fence from the first-level fence or the second-level fence, it can be determined that the mobile terminal no longer needs the services provided by the current MEC. In this case, to avoid unnecessary service occupation of transmission resources, storage resources, and / or computing resources, it is necessary to release the services of the corresponding mobile terminal. At this time, the target application for resource release is marked according to the migration algorithm result. That is, the service migration management engine and the migration algorithm determine that the resources in the current MEC need to be released. When the service release cleanup node is reached within a preset period, the marked target application for release is released. The release includes the cleanup of services, applications, middleware, and other resources to ensure a small proportion of resource occupation and elastic expansion of the current MEC. The release result is then uploaded to the regional service center for recording and filing.

[0152] It should be noted that the release or cleanup process does not include the release of basic resource management, collaborative gateway, and identity authentication proxy services in MEC.

[0153] Preferably, the zeroth-level fence is also located within the overlapping range between adjacent MECs (specifically, within the overlapping range between the current MEC to be accessed and the source MEC), and is located on the side of the first-level fence away from the second-level fence.

[0154] Optionally, the service migration control method described above, when used for the first time by the currently accessed MEC, further includes:

[0155] Basic resources for supporting services, application service components for mobile terminals, service migration prediction components and service migration management engines are loaded from the regional service center and initialized.

[0156] In another preferred embodiment of the present application, when the currently accessed MEC is used for the first time, it is necessary to pre-load and run the necessary components that comply with mobile station migration. At this time, the basic resources and application service components (MEC collaborative gateway, identity authentication, middleware, etc.) used to support the service will be loaded and initialized from the application warehouse of the regional center. The service migration prediction component, service migration management engine, etc. will be loaded (loaded), and basic support will be provided for specific service migration after initialization. Among them, the services in the above-mentioned basic resources for supporting services are especially Platform As A Service (PAAS) and Software As A Service (SAAS).

[0157] Among them, the MEC collaborative gateway application is responsible for connection establishment, connection maintenance, connection switching, and connection release between MEC, regional cloud, central cloud, and mobile terminal;

[0158] The identity authentication proxy application is responsible for synchronizing and caching the identity information of mobile stations and access terminals in the regional cloud or central cloud through the collaborative gateway. It authenticates the mobile station when it connects to the MEC and ensures that the mobile station can legally connect to the MEC.

[0159] The service orchestration engine supports the dynamic orchestration of service applications in MEC. It is responsible for migrating services (or applications) and dynamically orchestrating services according to the service configuration during or at the end of service migration. For example, the vehicle to everything (V2X) service for on-board units (OBUs) requires an OBU gateway, an OBU protocol processor, and a message middleware. These three components, as a set of specific version components, provide V2X services for a certain car manufacturer. During service migration, the orchestration engine needs to dynamically determine whether these three components will run together through predefined orchestration. After verification through service orchestration, the service quality is rated to dynamically provide the migration service quality for use in migration prediction and migration algorithms.

[0160] Access prediction service: The service migration engine supports mobile terminal access prediction calculation based on service migration factors (transmission delay between MEC and device, data migration delay between MECs, and service task execution delay) and MEC fences;

[0161] Service migration (execution) application: The service migration engine executes service migration in MEC based on the service migration prediction and the strategy formulated by the service orchestration engine.

[0162] It should be noted that when no mobile station (vehicle) terminal has been connected and the regional center (regional cloud) and MEC have not initialized any resources or service applications, the regional center also needs to pre-load and run the necessary components that meet the mobile station migration requirements. These components include: loading and initializing basic resources used to support PAAS and SAAS from the hierarchical application repository, MEC management components, service monitoring components for the regional cloud and MEC, the point network (topology) relationship between the regional cloud and MEC, version control components (application versions serving mobile terminals), and computing components for the MEC service area. This facilitates the provision of the above necessary components for MEC.

[0163] It should be noted that, in a specific embodiment, static resource registration will also be performed at the central cloud, which is performed through the service management of the central cloud. Since the migration service software packages, application libraries, container image libraries required in MEC and regional clouds, the point-to-network relationships (topological relationships) between cloud platforms at all levels and the identity information of users or terminals require a unified trusted node to maintain, the central cloud plays a role in the overall management of these static information in the overall solution of edge-cloud collaborative information service migration. At the beginning of the information service migration process, the global static resource information needs to be registered in the central cloud to prepare the necessary basic information and software package support for the subsequent migration process. The steps of static resource registration include:

[0164] 1. Register global MEC application resources, software packages, dependency libraries, image files, etc. to the central cloud platform;

[0165] 2. The service warehouse in the central cloud stores the static application resources of the global MEC for acquisition by the regional cloud and each MEC;

[0166] 3. Enter the basic node information of each MEC and its topological relationship with other MECs in the central cloud;

[0167] 4. Enter the identity information of each vehicle or user that needs to be authenticated in the central cloud so that MEC can authenticate the connected vehicle equipment or user.

[0168] After the static resources of the central cloud are registered, if the static resources (such as the vehicle-road collaborative service container image required by the onboard mobile terminal) change, the new resource version can be registered again through the registration entrance of the central cloud. The topological relationship between the regional service center and MEC, as well as the identity authentication information of the mobile terminal, are also uniformly registered and managed through the MEC management of the central cloud. The central cloud provides global service availability status information for all levels of cloud platforms by monitoring the services of the registered regional service centers and MECs in a point-to-network relationship.

[0169] See also Figure 5Specifically, the service migration control method described above, initialization includes:

[0170] Step S501: Mobile basic service goes online;

[0171] Step S502: Mobile basic service pre-processing;

[0172] Step S503: The mobile station terminal registers and logs in for the first time.

[0173] In a specific implementation of the present application, the initialization performed when the MEC to be accessed is used for the first time includes but is not limited to three stages: mobile basic service online; mobile basic service preprocessing; and first registration and login of the mobile terminal.

[0174] The following are examples for each of the above stages.

[0175] Preferably, in the service migration control method described above, the mobile basic service launch includes:

[0176] Initialize basic service preparations based on the loaded configuration parameters, middleware, and application image manifests;

[0177] Sending a second request message to the regional service center, and receiving the middleware dependency package, basic service image, and basic configuration information issued by the regional service center according to the second request message, where the second request message is used to request the middleware dependency package, basic service image, and basic configuration information from the regional service center;

[0178] Deploy according to the middleware dependency package, basic service image, and basic configuration information and perform a third self-check to obtain a second deployment result;

[0179] If the first deployment result is successful, a mobile basic service online signal is uploaded to the regional service center. The third self-check can be used to check whether the middleware dependency packages, basic service images, and basic configuration information are deployed successfully. If the third self-check result is a deployment failure, redeployment is preferably performed. If the number of redeployments exceeds a first preset value, a service synchronization failure message is fed back.

[0180] It should be noted that after receiving the second request information, the regional service center will check whether it has the corresponding middleware dependency package, basic service image and basic configuration information. If not, it will request the corresponding information from the central cloud and then send it to the corresponding MEC.

[0181] Preferably, in the service migration control method described above, the mobile basic service preprocessing includes:

[0182] Detect the collaborative gateway service status, identity authentication service status, and service migration management engine status, and receive the MEC topology and mobile terminal identity information periodically issued by the regional service center. Each detection step and information reception can be performed gradually to ensure that the basic status and information reserves of the MEC meet the requirements for providing services to mobile terminals. If any of these conditions are not met, the service cannot be provided. It should be noted that the MEC topology and mobile terminal identity information are received by the regional service center from the central cloud periodically, and then sent to the corresponding MEC.

[0183] Preferably, in the service migration control method as described above, the first registration and login of the mobile station terminal includes:

[0184] When receiving registration information sent by the mobile station terminal, determining whether the registration information is valid;

[0185] When the registration information is confirmed to be valid, the mobile terminal's registered information and initial positioning information are uploaded to the regional service center, and a login authentication code is fed back to the mobile terminal to facilitate authentication and verification of the mobile terminal and ensure that the correct service is provided to the mobile terminal.

[0186] Preferably, the service migration control method as described above, after establishing a link with a mobile terminal or receiving a quasi-migration instruction sent by the mobile terminal, further comprises:

[0187] Obtaining the total delay of the service task corresponding to the mobile terminal and the delay requirements corresponding to the first-level fence, the second-level fence, the third-level fence, and the zero-level fence respectively according to a preset migration algorithm;

[0188] According to the total delay and the delay requirement, it is determined whether the mobile station terminal meets the delay requirements corresponding to the first-level fence, the second-level fence, the third-level fence and the zero-level fence respectively.

[0189] like Figure 10The figure shows a schematic diagram of the position of the dynamic fence set between the source MEC and the target MEC (currently accessed MEC). In a specific embodiment of the present application, after the target MEC establishes a link with the mobile terminal or receives a quasi-migration instruction sent by the mobile terminal, the target MEC will obtain the total delay of the service task corresponding to the mobile terminal according to the preset migration algorithm, as well as the delay requirements corresponding to the first-level fence, the second-level fence, the third-level fence and the zero-level fence. It is assumed that the mobility pattern of the mobile terminal satisfies the random walk model and moves to the adjacent edge MEC coverage area with the same probability during the movement. It is hoped that by determining the optimal location for service migration in each time slice, the service indicator can be optimized and the service quality can be guaranteed. Each time slice t is defined as a decision cycle. There are n edge MECs in the area near the device. The migration action set is defined as A, a ij ∈A, the target optimization model of service migration is as follows:

[0190]

[0191] Among them, cost T (t) is the total delay of the service task, including the transmission delay t between MEC and mobile terminal t , data migration delay between MECs t m and MEC execution task delay t r .

[0192] Among them, the transmission delay between MEC and mobile terminal is t t The calculation formula is preferably:

[0193]

[0194] R is : transmission rate;

[0195] : The amount of radio bandwidth resources required to transmit service data between MEC and mobile terminals;

[0196] P s : transmission power;

[0197] d is : is the distance between MEC and the mobile terminal, σ is a distance-related path loss parameter;

[0198] c: indicates the size of the task input data.

[0199] Since data transmission includes data upload and data download (data volume is different), the transmission delay also includes the device data upload delay and MEC data downlink latency

[0200] In the service migration business, data migration between the source MECi and the target MECj is involved, which includes data transmission delay and task queuing delay. If the MECs are connected via wired or dedicated lines, the data transmission delay is much smaller than the task queuing delay. The task queuing waiting delay is proportional to the number of network hops between MECs and is obtained through the network monitoring module. Therefore, the data migration delay between MECs is t m The calculation formula is preferably:

[0201]

[0202] : Network adjustment number;

[0203] α: A preset coefficient greater than 0.

[0204] MEC task execution delay t r The calculation formula is preferably:

[0205]

[0206] : The ratio of computing resources required by the destination MECj to perform service tasks

[0207] Computing capacity of the target MEC

[0208] The computing power required to complete the current service task

[0209] Each MEC runs a service migration decision algorithm, which only makes migration decisions for the devices currently connected to the MEC based on historical observation information, historical decision information, the current distance information of the device, task information, etc.

[0210] When migrating services from source MEC (M1) to target MEC (M2), during the service migration process, M1 is not directly disconnected from M2, but a multi-section dynamic fence is used for smooth switching. Among them, when the vehicle is served by M1, the total service loss is Decide:

[0211]

[0212] When the mobile terminal reaches the first level fence, M2 starts to create services and perform pre-loading operations, that is, perform the first self-check. The first level fence is determined by the following conditions:

[0213]

[0214] When COST0>COST1 is satisfied, it indicates that the mobile terminal has reached the first level fence condition, where: Losses in providing services to M2, Additional cost of creating a service for M2.

[0215] Since COST1 includes the additional cost of creating the service, to meet the condition of COST0>COST1, it is necessary to have a higher service delay for the mobile terminal.

[0216] When the vehicle reaches the second level fence, M2 starts to run the service and uses the weighted algorithm together with M1 to provide services to the device.

[0217] Among them, the second level fence is determined by the following conditions:

[0218]

[0219] When COST0>COST2 is satisfied, it indicates that the second level fence condition is met, and M1 and M2 jointly provide services to the mobile terminal. m (M1, M2) is the queuing delay of data migration from M1 to M2.

[0220] When the vehicle reaches the third level fence, the service switches from M1 to M2, and M1 releases resources.

[0221] Among them, the third level fence is determined by the following conditions:

[0222]

[0223] When COST0>COST3 is satisfied, it indicates that the condition of the third level fence is met and service switching is executed. M1 (destroy) is the loss of destroying the M1 service.

[0224] When the mobile terminal has reached the first or second level fence conditions, but the mobile terminal leaves M2 and returns to M1, the resources of M2 need to be released. This is defined as the zero-level fence. The zero-level fence is determined by the following method:

[0225]

[0226] Among them, COST4 represents the total service loss when the service is provided by M2; COST5 represents the sum of the total losses when the service is provided by M1 and the destruction of M2 service.

[0227] Obviously, in the three levels of fences mentioned above, it is necessary to meet the condition that M2 can provide lower latency services than M1. However, in this case, M1 needs to provide lower service latency than M2. m2 (destroy) is the loss of destroying the M2 service.

[0228] See also Figure 6 Another preferred embodiment of the present application further provides a service migration control method, applied to a mobile terminal, comprising:

[0229] Step S601: After receiving a first signal from a source MEC indicating that a mobile station terminal has entered a first-level fence of at least one adjacent MEC to be accessed, a pre-access signal is sent to the MEC to be accessed.

[0230] Step S602: receiving a weight rating sent by at least one MEC to be accessed, and determining one of them as a target MEC based on the weight rating sent by each MEC to be accessed and a preset algorithm;

[0231] Step S603: After receiving a second signal from the source MEC or the target MEC indicating that the mobile terminal has entered the second level fence of the target MEC, a quasi-migration instruction is sent to the target MEC;

[0232] Step S604: disconnecting the link with the source MEC when receiving the handover instruction sent by the target MEC, wherein the handover instruction is sent by the target MEC when it detects that the mobile station terminal meets the third level fence of the target MEC.

[0233] A specific embodiment of the present application also provides a service migration control method applied to a mobile station terminal, wherein, when the mobile station terminal needs to perform service migration, it is in an area where at least two adjacent MECs (the source MEC and at least one access MEC) overlap. At this time, if the mobile station terminal receives a first signal sent by the source MEC when the mobile station terminal enters the first-level fence of at least one adjacent MEC to be accessed, it is determined that the mobile station terminal may need to perform service migration while continuing to move, and therefore sends a pre-access signal to the MEC to be accessed, so that the MEC to be accessed can create services in advance and perform pre-loading operations such as self-test, thereby improving efficiency during formal access, and at the same time enabling the MEC to be accessed to calculate the weight rating for the mobile station terminal respectively. After receiving the weight rating sent by the MEC to be accessed, it will calculate based on the weight rating sent by each MEC to be accessed and the preset algorithm to determine one of them as the optimal solution, namely the target MEC; when receiving the second signal sent by the source MEC or target MEC to the mobile terminal entering the second-level fence of the target MEC, it is determined that the target MEC will serve as the subsequent service support MEC. At this time, a quasi-migration instruction will be sent to the target MEC, so that the target MEC can obtain the real-time data sent by the mobile terminal, and obtain the corresponding historical data from the source MEC based on the relevant information of the source MEC carried in the quasi-migration instruction, to ensure that the mobile terminal service can be provided in a timely and accurate manner after migrating to the target MEC. Specifically, when receiving the switching instruction sent by the target MEC when detecting that the mobile terminal has entered the third-level fence of the target MEC, the link with the source MEC is disconnected to complete the service migration.

[0234] During this process, the mobile terminal mainly communicates with MEC to achieve service migration, making full use of the computing power of MEC, sharing the computing pressure of the central cloud, and at the same time, facilitating the formation of wide-area and large-scale service continuity support capabilities.

[0235] Preferably, the service migration control method as described above further includes:

[0236] Send registration information to the first MEC connected to the mobile station terminal, and receive the login authentication code fed back by the first MEC.

[0237] In a preferred embodiment of the present application, when a mobile terminal registers and logs in for the first time, it sends registration information to the first MEC connected to it. The first MEC determines whether the registration information is valid based on the information. If valid, it will feedback the login authentication code related to the mobile terminal to facilitate secure login. It should be noted that the first MEC is the first MEC connected to the mobile terminal.

[0238] See also Figure 7Another preferred embodiment of the present application further provides a control device, applied to MEC, comprising:

[0239] The first processing module 701 is configured to, upon receiving a pre-access signal sent by a mobile station terminal, obtain a weight rating for the mobile station terminal and send the weight rating to the mobile station terminal, wherein the mobile station terminal sends the pre-access signal when entering the first-level fence of the current MEC to be accessed;

[0240] The second processing module 702 is configured to perform service synchronization upon receiving a quasi-migration instruction sent by a mobile station terminal, wherein the mobile station terminal sends the quasi-migration instruction when determining the current MEC to be accessed as the target MEC and entering the second-level fence of the current MEC to be accessed;

[0241] The third processing module 703 is used to establish a link with the mobile station terminal and send a switching instruction to the mobile station terminal to complete service migration when it is detected that the mobile station terminal enters the third-level fence of the current MEC to be accessed. The switching instruction is used to disconnect the mobile station terminal from the source MEC, wherein the distances from the first-level fence, the second-level fence, and the third-level fence to the current MEC to be accessed decrease in sequence.

[0242] Specifically, in the control device as described above, the first processing module includes:

[0243] The first processing unit is configured to obtain service requirement information required by the mobile station terminal, where the service requirement information includes at least one of a service operation status, a first middleware dependent on the service, and infrastructure information;

[0244] a second processing unit, configured to obtain deployment resources based on the service demand information and service migration parameters, where the service migration parameters include at least one of a service migration size, a quantity, and an estimated deployment time, and the deployment resources include at least one of hardware resources, network resources, and time resources;

[0245] The third processing unit is configured to determine the priority of the mobile terminal to be currently accessed by the MEC based on the deployment resources, the current load, the MEC network environment rating, and the access demand of the mobile terminal;

[0246] The fourth processing unit is used to obtain a weight rating according to the priority and a preset weight rating rule.

[0247] Preferably, in the control device as described above, the second processing module includes:

[0248] a fifth processing unit, configured to send a first request message to the regional service center, and receive target middleware, target service image, and target configuration information issued by the regional service center in response to the first request message, wherein the first request message is used to request the regional service center for target middleware, target service image, and target configuration information corresponding to the mobile terminal;

[0249] a sixth processing unit, configured to perform deployment according to the target middleware, the target service image, and the target configuration information to obtain a first deployment result;

[0250] a seventh processing unit, configured to, if the first deployment result is successful, send deployment information to the mobile station terminal, and receive real-time data information and source MEC information sent by the mobile station terminal;

[0251] The eighth processing unit is configured to send a historical data request of the mobile station terminal to the source MEC according to the source MEC information, and receive the historical data of the mobile station terminal sent by the source MEC.

[0252] Preferably, the control device as described above further includes:

[0253] an eighth processing module, configured to release the service upon receiving a disconnection instruction sent by the mobile terminal or detecting that the mobile terminal returns to a zero-level fence, and mark the target application according to the result of the migration algorithm, wherein the zero-level fence is located on a side of the first-level fence away from the second-level fence;

[0254] The ninth processing module is used to release the target application when the cleanup node of the preset cycle is reached, obtain the application release result, and upload the application release result to the regional service center.

[0255] Optionally, the control device as described above, when the MEC to be accessed is used for the first time, further includes:

[0256] The tenth processing module is used to load basic resources for supporting services, application service components, service migration prediction components and service migration management engine from the regional service center and initialize them.

[0257] Specifically, in the control device as described above, the tenth processing module includes:

[0258] The ninth processing unit, mobile basic services are launched;

[0259] The tenth processing unit, mobile basic service preprocessing;

[0260] The eleventh processing unit is the first registration and login of the mobile station terminal.

[0261] Preferably, in the control device as described above, the ninth processing unit includes:

[0262] A first sub-processing unit is configured to initialize basic service preparation according to the loaded configuration parameters, middleware, and application image manifest;

[0263] a second sub-processing unit, configured to send a second request message to the regional service center, and receive a middleware dependency package, a basic service image, and basic configuration information issued by the regional service center in response to the second request message, wherein the second request message is used to request the middleware dependency package, the basic service image, and the basic configuration information from the regional service center;

[0264] The third sub-processing unit is configured to perform deployment according to the middleware dependency package, the basic service image, and the basic configuration information to obtain a second deployment result;

[0265] The fourth sub-processing unit is configured to upload a mobile basic service online signal to the regional service center if the second deployment result is successful deployment.

[0266] Preferably, in the control device as described above, the tenth processing unit includes:

[0267] The fifth sub-processing unit is used to detect the collaborative gateway service status, identity authentication service status, and service migration management engine status, and receive the MEC topology relationship and mobile terminal identity information periodically issued by the regional service center.

[0268] Preferably, the control device as described above, the eleventh processing unit is configured to include:

[0269] a sixth sub-processing unit, configured to determine whether the registration information is valid when receiving the registration information sent by the mobile station terminal;

[0270] The seventh sub-processing unit is configured to upload the registered information and the first positioning information of the mobile terminal to the regional service center when it is determined that the registration information is valid, and feed back a login authentication code to the mobile terminal.

[0271] Preferably, the control device as described above further includes:

[0272] an eleventh processing module, configured to obtain, according to a preset migration algorithm, a total delay of a service task corresponding to the mobile station terminal, and delay requirements corresponding to the first-level fence, the second-level fence, the third-level fence, and the zero-level fence, respectively;

[0273] The twelfth processing module is used to determine whether the mobile station terminal meets the delay requirements corresponding to the first-level fence, the second-level fence, the third-level fence and the zero-level fence respectively according to the total delay and the delay requirement.

[0274] The control device embodiment applied to MEC of the present application is a control device corresponding to the embodiment of the service migration control method applied to MEC mentioned above. All implementation means in the above method embodiment are applicable to the embodiment of the control device and can achieve the same technical effect.

[0275] See also Figure 8 Another preferred embodiment of the present application further provides a control device, applied to a mobile station terminal, comprising:

[0276] The fourth processing module 801 is configured to send a pre-access signal to the MEC to be accessed after receiving a first signal sent by the source MEC indicating that the mobile station terminal has entered the first-level fence of at least one adjacent MEC to be accessed;

[0277] The fifth processing module 802 is configured to receive a weight rating sent by at least one MEC to be accessed, and determine one of the MECs as a target MEC based on the weight rating sent by each MEC to be accessed and a preset algorithm;

[0278] The sixth processing module 803 is configured to send a quasi-migration instruction to the target MEC upon receiving a second signal sent by the source MEC or the target MEC indicating that the mobile terminal has entered the second level fence of the target MEC;

[0279] The seventh processing module 804 is configured to disconnect the link with the source MEC upon receiving a handover instruction sent by the target MEC, wherein the handover instruction is sent by the target MEC when it detects that the mobile station terminal meets the third level fence of the target MEC.

[0280] Preferably, the control device as described above further includes:

[0281] The thirteenth processing module is used to send registration information to the first MEC connected to the mobile station terminal, and receive a login authentication code fed back by the first MEC.

[0282] The control device embodiment applied to the mobile station terminal of the present application is a control device corresponding to the embodiment of the service migration control method applied to the mobile station terminal mentioned above. All implementation means in the above method embodiment are applicable to the embodiment of the control device and can also achieve the same technical effect.

[0283] See also Figure 9 Another preferred embodiment of the present application further provides an edge-cloud collaboration system, including:

[0284] Central cloud 901, regional service center 902, MEC 903 as described above, and mobile station terminal 904 as described above;

[0285] The central cloud 901 is linked to at least one regional service center 902;

[0286] The regional service center 902 is linked to at least one MEC 903;

[0287] MEC 903 is linked to mobile station terminal 904;

[0288] Linking multiple MEC903s;

[0289] Multiple regional service centers 902 are linked to each other.

[0290] In a specific embodiment of the present application, an edge-cloud collaborative system is provided, which includes: a central cloud, a regional service center, the MEC as described above, and the mobile terminal as described above. Among them, the central cloud, the regional service center, and the MEC constitute a multi-level service support system with a three-level structure, wherein the central cloud serves as a central management unit, the central cloud connects multiple regional service centers, provides a resource registration entry through MEC management, and registers the service resources required by the regional cloud and edge cloud to the global application warehouse; the central cloud assumes the responsibilities of migration rule configuration, cloud platform service monitoring (service availability) management at all levels, global maintenance of the point network (topology) relationship of the regional cloud and edge cloud, and identity information of the mobile terminal.

[0291] The regional service center connects with the MEC within its jurisdiction and is responsible for distributing the migration service software package and its version, service configuration, regional edge cloud point-to-network relationship, and static identity information of the mobile station. At the same time, it maintains the migration service library version and mapping relationship required by the mobile terminal. Based on the service availability on the MEC and the service fence between MECs, it dynamically calculates the MEC that the mobile terminal can access, thereby allocating the computing pressure of the central cloud. Specifically, the regional service center undertakes the following tasks for the MEC within its jurisdiction:

[0292] MEC status monitoring: monitors the operation of MEC within the scope of jurisdiction, including real-time operation status such as load status and network status.

[0293] Real-time calculation of service range: The service range of MEC is calculated according to the location, status, and service range of the base station, and the service synchronization domain (i.e., the overlapping area between MECs) is calculated in conjunction with other regional centers.

[0294] MEC network status configuration delivery: The regional center stores the topological relationship and specific network and resource configuration of the MECs under its jurisdiction. When the MEC performs service synchronization, the regional center needs to deliver the required configuration information.

[0295] MEC service application warehouse: The regional center stores service images and provides the nearest synchronization node for MEC within its jurisdiction.

[0296] Service version control: Regional centers allocate specific service image versions according to specific needs within their jurisdiction to achieve local version control.

[0297] MEC is responsible for predictive judgment, service orchestration, data migration, access switching, and migration rollback when the service is unavailable during the service migration process. There are even multiple base stations within the communication range of each MEC, and there are overlapping areas between adjacent MECs.

[0298] To sum up, the edge-cloud collaboration system of this application adopts a multi-level hierarchical edge-cloud collaboration architecture, which fully utilizes the characteristics of timely dynamic information and model updates of edge nodes and the global monitoring and coordination characteristics of cloud center nodes, strengthens edge-cloud and edge-edge collaboration, and is more suitable for providing cross-site services over a wide area.

[0299] A multi-level dynamic migration method is used to smoothly switch services, which effectively reduces the "ping-pong phenomenon" caused by cross-site service migration while ensuring service latency, thereby increasing service continuity and reliability.

[0300] Another preferred embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by the processor, the steps of the service migration control method applied to the MEC as described above are implemented, or the steps of the service migration control method applied to the mobile station terminal as described above are implemented.

[0301] In addition, the present application may repeat reference numerals and / or letters in different examples. This repetition is for the purpose of simplicity and clarity and does not in itself indicate the relationship between the various embodiments and / or settings discussed.

[0302] It should also be noted that, in this document, relational terms such as first and second are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "include," "comprises," or any other variations thereof are intended to cover non-exclusive inclusion.

[0303] The above is a preferred embodiment of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles described in the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A service migration control method, applied to edge cloud MEC in edge cloud collaborative system, characterized in that: include: Upon receiving a pre-access signal sent by a mobile station terminal, obtaining a weight rating for the mobile station terminal and sending the weight rating to the mobile station terminal, wherein the mobile station terminal sends the pre-access signal when entering a first-level fence of a current MEC to be accessed; Upon receiving a quasi-migration instruction sent by the mobile station terminal, performing service synchronization, wherein the mobile station terminal sends the quasi-migration instruction when determining the current MEC to be accessed as a target MEC and entering the second level fence of the current MEC to be accessed; When it is detected that the mobile station terminal enters the third-level fence of the current MEC to be accessed, a link is established with the mobile station terminal and a switching instruction is sent to the mobile station terminal to complete the service migration. The switching instruction is used to disconnect the mobile station terminal from the source MEC, wherein the distances from the first-level fence, the second-level fence and the third-level fence to the current MEC to be accessed decrease in sequence.

2. The service migration control method according to claim 1, wherein: The acquiring of the weight rating for the mobile terminal includes: Acquire service requirement information required by the mobile terminal, the service requirement information including at least one of: service running status, first middleware dependent on the service, and infrastructure information; Obtaining deployment resources based on the service demand information and service migration parameters, the service migration parameters including at least one of service migration size, quantity, and deployment estimated time, and the deployment resources including at least one of hardware resources, network resources, and time resources; Determining the priority of the MEC to be accessed for the mobile terminal based on the deployed resources, the current load, the MEC network environment rating, and the access demand of the mobile terminal; The weight rating is obtained according to the priority and a preset weight rating rule.

3. The service migration control method according to claim 1 or 2, characterized in that: The execution service synchronization includes: sending a first request message to a regional service center, and receiving target middleware, target service image, and target configuration information issued by the regional service center in response to the first request message, wherein the first request message is used to request the target middleware, target service image, and target configuration information corresponding to the mobile station terminal from the regional service center; Deploy according to the middleware, the service image and the target configuration information to obtain a first deployment result; If the first deployment result is successful, sending deployment information to the mobile station terminal, and receiving real-time data information and source MEC information sent by the mobile station terminal; Send a historical data request for the mobile station terminal to the source MEC according to the source MEC information, and receive the historical data of the mobile station terminal sent by the source MEC.

4. The service migration control method according to claim 1, wherein: Also includes: releasing the service upon receiving a disconnection instruction sent by the mobile terminal, or detecting that the mobile terminal returns to a zero-level fence, marking the target application according to a migration algorithm result, wherein the zero-level fence is located on a side of the first-level fence away from the second-level fence; When the cleanup node of the preset cycle is reached, the target application is released, an application release result is obtained, and the application release result is uploaded to the regional service center.

5. The service migration control method according to claim 1, wherein: When the MEC to be accessed is used for the first time, the following steps are also included: Basic resources used to support services, application service components, service migration prediction components, and service migration management engines are loaded from the regional service center and initialized.

6. The service migration control method according to claim 5, characterized in that: The initialization includes: Mobile basic services are launched; Mobile basic service preprocessing; The mobile terminal registers and logs in for the first time.

7. The service migration control method according to claim 6, characterized in that: The steps for launching the mobile basic service include: Initialize basic service preparations based on the loaded configuration parameters, middleware, and application image manifests; Sending a second request message to the regional service center, and receiving the middleware dependency package, basic service image, and basic configuration information issued by the regional service center according to the second request message, wherein the second request message is used to request the middleware dependency package, the basic service image, and the basic configuration information from the regional service center; Deploy according to the middleware dependency package, the basic service image and the basic configuration information to obtain a second deployment result; If the second deployment result is successful, the mobile basic service online signal is uploaded to the regional service center.

8. The service migration control method according to claim 6, wherein: The mobile basic service preprocessing step includes: Detect the collaborative gateway service status, identity authentication service status, and service migration management engine status, and receive the MEC topology relationship and mobile terminal identity information periodically issued by the regional service center.

9. The service migration control method according to claim 6, wherein: The steps of registering and logging in the mobile terminal for the first time include: When receiving registration information sent by the mobile station terminal, determining whether the registration information is valid; When it is determined that the registration information is valid, the registered information and the first positioning information of the mobile terminal are uploaded to the regional service center, and a login authentication code is fed back to the mobile terminal.

10. The service migration control method according to claim 1, wherein: After establishing a link with the mobile station terminal or receiving a quasi-relocation instruction sent by the mobile station terminal, the method further includes: Obtaining, according to a preset migration algorithm, a total delay of the service task corresponding to the mobile station terminal, and delay requirements corresponding to the first-level fence, the second-level fence, the third-level fence, and the zero-level fence respectively; Determine whether the mobile station terminal meets the delay requirements corresponding to the first-level fence, the second-level fence, the third-level fence and the zero-level fence respectively according to the total delay and the delay requirement.

11. A service migration control method, applied to a mobile terminal, characterized in that: include: After receiving a first signal from the source MEC indicating that the mobile station terminal has entered the first-level fence of at least one adjacent MEC to be accessed, sending a pre-access signal to the MEC to be accessed; receiving a weight rating sent by at least one of the MECs to be accessed, and determining one of them as a target MEC based on the weight rating sent by each of the MECs to be accessed and a preset algorithm; Upon receiving a second signal sent by the source MEC or the target MEC to the mobile station terminal entering the second level fence of the target MEC, sending a quasi-migration instruction to the target MEC; The link with the source MEC is disconnected when a handover instruction sent by the target MEC is received, wherein the handover instruction is sent by the target MEC when the target MEC detects that the mobile station terminal enters the third-level fence of the target MEC.

12. The service migration control method according to claim 11, characterized in that: Also includes: Send registration information to the first MEC linked to the mobile station terminal, and receive a login authentication code fed back by the first MEC.

13. A control device, applied to MEC, characterized in that: include: A first processing module is configured to, upon receiving a pre-access signal sent by a mobile station terminal, obtain a weight rating for the mobile station terminal and send the weight rating to the mobile station terminal, wherein the mobile station terminal sends the pre-access signal when entering a first-level fence of a current MEC to be accessed; a second processing module, configured to perform service synchronization upon receiving a quasi-migration instruction sent by the mobile station terminal, wherein the mobile station terminal sends the quasi-migration instruction when determining the current MEC to be accessed as a target MEC and entering a second-level fence of the current MEC to be accessed; The third processing module is used to establish a link with the mobile station terminal and send a switching instruction to the mobile station terminal when it is detected that the mobile station terminal enters the third-level fence of the current MEC to be accessed, so as to complete the service migration. The switching instruction is used to disconnect the mobile station terminal from the source MEC, wherein the distances from the first-level fence, the second-level fence and the third-level fence to the current MEC to be accessed decrease in sequence.

14. A control device, applied to a mobile terminal, characterized in that: include: A fourth processing module is configured to, upon receiving a first signal sent by the source MEC indicating that the mobile station terminal meets the first-level fence of at least one adjacent MEC to be accessed, send a pre-access signal to the MEC to be accessed; a fifth processing module, configured to receive a weight rating sent by at least one of the MECs to be accessed, and determine one of them as a target MEC based on the weight rating sent by each of the MECs to be accessed and a preset algorithm; A sixth processing module is configured to send a quasi-migration instruction to the target MEC upon receiving a second signal sent by the source MEC or the target MEC to the mobile station terminal that satisfies the second level fence of the target MEC; The seventh processing module is configured to disconnect the link with the source MEC when receiving a switching instruction sent by the target MEC, wherein the switching instruction is sent by the target MEC when the target MEC detects that the mobile station terminal meets the third level fence of the target MEC.

15. An edge-cloud collaborative system, characterized in that: include: A central cloud, a regional service center, an MEC, and a mobile station terminal, wherein the MEC includes the control device applied to the MEC according to claim 13, and the mobile station terminal includes the control device applied to the mobile station terminal according to claim 14; wherein the central cloud is linked to at least one of the regional service centers; The regional service center is linked to at least one of the MECs; The MEC is linked to the mobile terminal; Linking between multiple MECs; Multiple regional service centers are linked to each other.

16. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by the processor, it implements the steps of the service migration control method applied to MEC as described in any one of claims 1 to 10, or implements the steps of the service migration control method applied to the mobile station terminal as described in claims 11-12.

Images