Method, electronic device and storage medium for application instance migration

Abstract

The application provides a method for application instance migration, an electronic device and a storage medium, relates to the technical field of communication, and is used for solving the problem that a suitable MEC host cannot be selected for a UE in the related art, thereby causing the user experience to be reduced. The method comprises the following steps: after a user equipment (UE) moves to a target area, a first target MEC host in the target area receives an application instance migration request of the UE, and sends the application instance migration request to a source MEC host; the source MEC host sends a relocation request to a MEO; the relocation request comprises the identification of a target application instance and the identification of the first target MEC host; the MEO determines a second target MEC host from the adjacent MEC host information of the first target MEC host in response to the relocation request, and sends an instantiation application request to the second target MEC host; the instantiation application request is used for instructing the second target MEC host to create the target application instance.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and particularly relates to a method for application instance migration, an electronic device and a storage medium. BACKGROUND

[0002] Multi-access Edge Computing (MEC) proposed by European Telecommunications Standards Institute (ETSI) is an architecture based on 5th-Generation (5G) evolution, and is a technology that deeply integrates mobile access network and Internet services. MEC can provide services and cloud computing functions required by telecommunication users nearby using wireless access network, thereby creating a high-performance, low-latency and high-bandwidth telecommunication service environment, accelerating the fast download of various contents, services and applications in the network, and allowing consumers to enjoy uninterrupted high-quality network experience. MEC can improve user experience and save bandwidth resources on the one hand, and provide third-party application integration by sinking computing power to mobile edge nodes, thereby providing unlimited possibilities for service innovation of mobile edge portal.

[0003] In the prior art, the specification ETSI GS MEC 012 defines a Radio Network Information Service (RNIS) that can provide real-time radio network condition information and user equipment (UE) information under the radio node associated with the MEC host. The MEC application or the MEC platform on the MEC host can subscribe to the RNIS for cell change notification, and the RNIS sends a notification event to the subscriber when the UE moves across the cell. The MEC platform or the MEC application initiates application instance migration.

[0004] However, in the application instance migration process, the current information related to Quality of Service (QoS) in the RNIS is insufficient to allow necessary prediction about QoS performance (for example, latency, throughput, reliability). For example, due to insufficient RNIS information or inability to collect information in real time, the new MEC host to which the UE migrates cannot guarantee the operation of application instance migration, thereby causing the Quality of Experience (QoE) to decline. SUMMARY

[0005] The application provides a method for application instance migration, an electronic device and a storage medium, and aims at solving the problem that a suitable MEC host cannot be selected for a UE in the prior art, thereby causing the user experience to decrease.

[0006] To achieve the above object, the application adopts the following technical scheme:

[0007] In a first aspect, a method for application instance migration is provided, which is applied to a multi-access edge computing (MEC) system. The MEC system includes a plurality of MEC hosts and a mobile edge orchestrator (MEO). Each MEC host is pre-configured with adjacent MEC host information. After a user equipment (UE) moves to a target area, a first target MEC host in the target area receives an application instance migration request of the UE and sends the application instance migration request to a source MEC host. The source MEC host is a MEC host accessed by the UE in a source area. The application instance migration request is used to request migration of a target application instance. The first target MEC host and the source MEC host are both MEC hosts in the MEC system. The source MEC host sends a relocation request to the MEO. The relocation request includes an identifier of the target application instance and an identifier of the first target MEC host. The MEO determines a second target MEC host from the adjacent MEC host information of the first target MEC host in response to the relocation request, and sends an instantiation application request to the second target MEC host. The instantiation application request is used to instruct the second target MEC host to create the target application instance.

[0008] Optionally, the adjacent MEC host information includes a plurality of MEC hosts. The MEO determines the second target MEC host from the plurality of MEC hosts in the adjacent MEC host information of the first target MEC host in response to the relocation request, including: the MEO determines the second target MEC host from the plurality of MEC hosts in the MEC host information according to a resource occupation of the target application instance and available resources of each MEC host in the MEC host information.

[0009] Optionally, the method further includes: the MEO sends address information of the second target MEC host to the source MEC host; the source MEC host sends a traffic routing rule update request to the second target MEC host according to the address information of the second target MEC host; the traffic routing rule update request includes a traffic routing rule of the target application instance; and the second target MEC host updates the traffic routing rule of the target application instance according to the traffic routing rule update request.

[0010] Optionally, after the second target MEC host updates the traffic routing rule of the target application instance, the method further includes: the second target MEC host sends a traffic routing rule update completion message to the source MEC host; and the source MEC host deactivates the traffic routing rule of the target application instance in response to the traffic routing rule update completion message.

[0011] In a second aspect, a multi-access edge computing (MEC) system is provided. The MEC system includes a plurality of MEC hosts and a mobile edge orchestrator (MEO). Each MEC host is pre-configured with adjacent MEC host information. After a user equipment (UE) moves to a target area, a first target MEC host in the target area receives an application instance migration request of the UE and sends the application instance migration request to a source MEC host. The source MEC host is a MEC host accessed by the UE in a source area. The application instance migration request requests migration of a target application instance. The first target MEC host and the source MEC host are both MEC hosts in the MEC system. The source MEC host sends a relocation request to the MEO. The relocation request includes an identifier of the target application instance and an identifier of the first target MEC host. The MEO determines a second target MEC host from the adjacent MEC host information of the first target MEC host in response to the relocation request, and sends an instantiation application request to the second target MEC host. The instantiation application request instructs the second target MEC host to create the target application instance.

[0012] Optionally, the adjacent MEC host information includes a plurality of MEC hosts. The MEO specifically determines the second target MEC host from the plurality of MEC hosts in the MEC host information according to resource occupation of the target application instance and available resources of each MEC host in the MEC host information.

[0013] Optionally, the MEO further sends address information of the second target MEC host to the source MEC host. The source MEC host further sends a traffic routing rule update request to the second target MEC host according to the address information of the second target MEC host. The traffic routing rule update request includes a traffic routing rule of the target application instance. The second target MEC host further updates the traffic routing rule of the target application instance according to the traffic routing rule update request.

[0014] Optionally, after the second target MEC host updates the traffic routing rule of the target application instance, the second target MEC host further sends a traffic routing rule update completion message to the source MEC host. The source MEC host further deactivates the traffic routing rule of the target application instance in response to the traffic routing rule update completion message.

[0015] In a third aspect, an electronic device is provided. The electronic device includes a processor and a memory storing instructions executable by the processor. The processor is configured to execute the instructions to implement the method of application instance migration of the first aspect.

[0016] In a fourth aspect, a computer-readable storage medium is provided, and the computer-readable storage medium stores instructions. When the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to perform the method for application instance migration in the first aspect.

[0017] The technical scheme provided by the embodiments of the present application at least brings the following beneficial effects: The method for application instance migration provided by the present application is applied to a multi-access edge computing (MEC) system. The MEC system includes a plurality of MEC hosts and a mobile edge orchestrator (MEO). Since each MEC host is pre-configured with adjacent MEC host information, after a user equipment (UE) moves to a target area, a first target MEC host in the target area receives an application instance migration request of the UE and sends the application instance migration request to a source MEC host. The source MEC host is a MEC host accessed by the UE in a source area. The application instance migration request is used to request migration of a target application instance. The first target MEC host and the source MEC host are both MEC hosts in the MEC system. Further, the source MEC host sends a relocation request including an identifier of the target application instance and an identifier of the first target MEC host to the MEO. The MEO determines a second target MEC host from the adjacent MEC host information of the first target MEC host in response to the relocation request and sends an instantiation application request to the second target MEC host. The instantiation application request is used to instruct the second target MEC host to create the target application instance. Through the above scheme, after the UE moves to a new cell, the UE is first accessed to a new MEC host (i.e., pre-relocation), and then a best MEC host is selected for the UE from the adjacent MEC host information of the new MEC host, and the application instance is migrated to the MEC host, so as to improve user experience. BRIEF DESCRIPTION OF DRAWINGS

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings needed to be used in the embodiments or the prior art description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0019] Figure 1 A switching timing prediction schematic diagram of a vehicle is provided for the embodiments of the present application.

[0020] Figure 2 A structure schematic diagram of a MEC system is provided for the embodiments of the present application.

[0021] Figure 3 A structure schematic diagram of a MEC architecture is provided for the embodiments of the present application.

[0022] Figure 4 A flowchart of a method for application instance migration provided in an embodiment of the present application Figure 1 ;

[0023] Figure 5 A repositioning group schematic diagram provided in an embodiment of the present application

[0024] Figure 6 A switching schematic diagram provided in an embodiment of the present application

[0025] Figure 7 A flowchart of a method for application instance migration provided in an embodiment of the present application Figure 2 ;

[0026] Figure 8 A flowchart of a method for application instance migration provided in an embodiment of the present application Figure 3 ;

[0027] Figure 9 A structural schematic diagram of an application instance migration device provided in an embodiment of the present application

[0028] Figure 10 A structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0029] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of protection of the present application.

[0030] It should be noted that in the embodiments of the present application, the words such as “exemplary” or “for example” are used to mean serving as an example, an instance, or an illustration. Any embodiment or design scheme described as “exemplary” or “for example” in the embodiments of the present application should not be interpreted as being more preferred or having more advantages than other embodiments or design schemes. Rather, the words “exemplary” or “for example” are used in the sense of presenting a related concept in a specific manner.

[0031] It should also be noted that in the embodiments of the present application, “of”, “corresponding” and “corresponding” can be used interchangeably at times. It should be pointed out that when the distinction is not emphasized, the meanings expressed are consistent.

[0032] In order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, the terms "first", "second", etc. are used to distinguish the same or similar items with basically the same function and role, and those skilled in the art can understand that the terms "first", "second", etc. are not used to limit the quantity and execution order.

[0033] Before the embodiments of the present application are explained in detail, some related technologies involved in the embodiments of the present application are introduced.

[0034] MEC runs at the edge of the network, can provide big data services, Internet of Things services and data services, and opens application software programming interfaces (application programming interfaces, APIs) to third parties for rapid deployment of new businesses. MEC servers usually have high computing power, and are particularly suitable for analyzing and processing large amounts of data. MEC servers are mainly composed of three parts: the bottommost infrastructure, the middle MEC platform and the upper layer application.

[0035] The application is actually an application instance, and the application instance is a copy of the same application. The application instance is deployed on the required edge node. The application on the UE is served by a certain application instance of a certain edge node at a certain time.

[0036] 5G is developing rapidly, and UE mobility is enhanced, especially the nature of most vehicle to X (V2X) applications requires high mobility support to ensure the quality of experience, especially for advanced driving use cases that will benefit from predicted reliability. This means that vehicles in motion should have the possibility to receive predictions of network availability in advance, in order to plan ahead and ensure driving safety.

[0037] Generally speaking, the closer the application instance is to the location of the UE, the smaller the packet transmission delay between the application and the UE, and the higher the quality of service (QoS). Therefore, when the UE moves across the cell, the RNIS sends a notification event to the subscriber, and the MEC platform or MEC application initiates application instance migration. For example, as shown in Figure 1 , an example of handover timing prediction for a vehicle is shown, in which the vehicle travels along the trajectory shown in Figure 1 , and constantly switches to access a new cell, which will continue to provide MEC services for the vehicle to ensure the quality of experience (QoE).

[0038] However, in the application instance migration process, the current QoS-related information in the RNIS is insufficient to allow necessary predictions about QoS performance (e.g., latency, throughput, reliability), for example, due to insufficient RNIS information or the inability to collect RNIS in real time, the new MEC host to which the UE migrates cannot guarantee the operation of application instance migration, thereby causing QoE degradation.

[0039] Therefore, based on the prediction of QoS, the assistance of RNIS information is needed. However, collecting and processing RNIS to complete the relocation process can not only take a lot of time, but also will generally not meet the requirements of high-mobility UEs.

[0040] The application instance migration method provided by the embodiments of the present application can solve the problem that whether two associated services are synchronized cannot be determined in the related art. The application instance migration method provided by the embodiments of the present application can be applied to a MEC system, Figure 2 A structural schematic diagram of the MEC system is shown.

[0041] As Figure 2 shown, the MEC system 10 includes a plurality of MEC hosts 11 and a mobile edge orchestrator MEO 12. Each MEC host 11 is connected to the MEO 12. The MEC host 11 and the MEO 12 can be connected in a wired manner or in a wireless manner, and the embodiments of the present application do not limit this.

[0042] The MEC host 11 is composed of an ME platform (MEP), an MEC application (APP), and a virtualization infrastructure. The virtualization infrastructure can provide computing, storage, and network resources for the MEC application, and can provide continuous storage and time-related information for the MEC application. It contains a data forwarding plane to execute forwarding rules for data received from the MEC platform and route traffic between various applications, services, and networks. The MEC platform receives traffic forwarding rules from the MEC platform manager, the MEC application, or the MEC service, and issues instructions to the forwarding plane based on the forwarding rules. In addition, the MEC platform also supports the configuration of a local domain name system (DNS) proxy server, which can redirect data traffic to corresponding applications and services. The MEC platform can also communicate with other MEC platforms through the Mp3 reference point, which can serve as the basis for interconnection between different MEC platforms in the collaboration mechanism of a distributed MEC system.

[0043] MEC applications are virtual machine instances running on the MEC virtualization infrastructure, which communicate with the MEC platform through the Mp1 reference point. The Mp1 reference point can also provide additional functionalities such as identifying application availability, preparing or relocating application state for a user when a MEC handover occurs, etc.

[0044] The MEC platform manager (MECPM) has functions such as MEC platform element management, MEC application lifecycle management, and MEC application rules and requirements management. MEC application lifecycle management includes the creation and termination of MEC applications, and provides indication messages for application-related events to the MEC orchestrator (MECO). MEC application rules and requirements management includes authentication, traffic rules, DNS configuration, and conflict coordination, etc. The Mm5 reference point is used between the MEC platform and the MECPM, which implements the configuration of platform and traffic filtering rules, and is responsible for managing the relocation of applications and supporting the lifecycle procedures of applications. Mm2 is a reference point between the Operation Support System (OSS) and the MEPM, which is responsible for the configuration and performance management of the ME platform. Mm3 is a reference point between the MEO and the MEPM, which is responsible for supporting the lifecycle management of applications and application-related policies, while providing time-related information for available services of the ME.

[0045] The MEO 12 is the core function of the MEC architecture, which macro-manages the resources and capacity of the MEC network, including all deployed MEC hosts and services, available resources in each MEC host, base station information connected to each MEC host, instantiated applications, and network topology, etc.

[0046] Each MEC host 11 is pre-configured with adjacent MEC host information; after a user equipment (UE) moves to a target area, a first target MEC host in the target area is used to receive an application instance migration request of the UE, and send the application instance migration request to a source MEC host; the source MEC host is a MEC host accessed by the UE in a source area; the application instance migration request is used to request migration of a target application instance; the first target MEC host and the source MEC host are both MEC hosts in the MEC system; the source MEC host is used to send a relocation request to the MEO; the relocation request includes an identifier of the target application instance and an identifier of the first target MEC host; the MEO is used to determine a second target MEC host from adjacent MEC host information of the first target MEC host in response to the relocation request, and send an instantiation application request to the second target MEC host; the instantiation application request is used to instruct the second target MEC host to create the target application instance.

[0047] Optionally, the adjacent MEC host information includes a plurality of MEC hosts; and the MEO is specifically configured to: determine a second target MEC host from the plurality of MEC hosts in the MEC host information according to resource occupation of the target application instance and available resources of each MEC host in the MEC host information.

[0048] Optionally, the MEO is further configured to send address information of the second target MEC host to the source MEC host; the source MEC host is further configured to send a traffic routing rule update request to the second target MEC host according to the address information of the second target MEC host; the traffic routing rule update request includes the traffic routing rule of the target application instance; and the second target MEC host is further configured to update the traffic routing rule of the target application instance according to the traffic routing rule update request.

[0049] Optionally, after the second target MEC host updates the traffic routing rule of the target application instance, the second target MEC host is further configured to send a traffic routing rule update completion message to the source MEC host; and the source MEC host is further configured to deactivate the traffic routing rule of the target application instance in response to the traffic routing rule update completion message.

[0050] As shown in Figure 3 , a structure diagram of a MEC architecture is shown, which includes a wireless access network intelligence controller (RIC), a base station, a MEC data plane (MEC DP), a MEC host (MEC host) and a MEO. The MEC host is composed of a MEP, a MEC application (MEC APP) and a MEP manager (MEPM). The RIC is connected with the base station, the base station is connected with the MEP in the MEC host through the MEC DP, the MEP is further connected with the RIC, and the MEPM is connected with the MEO. In different application scenarios, the MEP and the MEC host can be independent devices or integrated in the same device, and the embodiments of the present application do not make specific limitation thereon.

[0051] The method for application instance migration provided by the embodiments of the present application will be described below in combination with a MEC system as shown in Figure 2 and a MEC architecture as shown in Figure 3 .

[0052] Figure 4 is a flow diagram of a method for application instance migration according to some example embodiments. In some embodiments, the above-mentioned method for application instance migration can be applied to a MEC system as shown in Figure 2The MEC host and MEO shown can also be applied to other similar devices.

[0053] As shown in Figure 4 The application instance migration method provided by the embodiments of the present application includes the following S201-S203.

[0054] S201, after the UE moves to the target area, the first target MEC host in the target area receives the application instance migration request of the UE, and sends the application instance migration request to the source MEC host.

[0055] The source MEC host is the MEC host accessed by the UE in the source area; the application instance migration request is used to request migration of the target application instance; the first target MEC host and the source MEC host are both MEC hosts in the MEC system.

[0056] As a possible implementation, after the UE roams to the target area, the UE initiates an application instance migration request to the MEC DP (referred to as T-DP) in the target area through the uplink (i.e. base station). The T-DP then forwards the application instance migration request to the first target MEC host connected thereto. Further, the first target MEC host receives the application instance migration request and sends the application instance migration request to the source MEC host.

[0057] It should be noted that each MEC host is pre-configured with adjacent MEC host information (such as host identifier), and the MEC application program is allowed to run when the UE moves among these MEC hosts. As shown in Figure 5 The group of MEC hosts can be referred to as a "relocation group". All MEC hosts in the group can share UE and application program information, so that when the UE changes its connection point, communication between the MEC hosts of the relocation group can be quickly established. In addition, the MEC application can even start communicating with the UE before the actual handover.

[0058] In some embodiments, the source MEP (referred to as S-MEP) in the source MEC host receives a RNIS cell change notification (including UE identifier (UE ID), indicating migration status (denoted as hostatus, where hostatus takes 1 to indicate preparation, takes 2 to indicate execution, takes 3 to indicate completion, takes 4 to indicate rejection, and takes 5 to indicate cancellation), target cell ID) from the source base station. At this time, the source base station has detected that the UE is switched to another wireless node. The notification is used to indicate that the UE switching of the source mobile edge platform is in progress.

[0059] S202, the source MEC host sends a relocation request to the MEO.

[0060] The relocation request includes an identifier of the target application instance and an identifier of the first target MEC host.

[0061] As a possible implementation, the source MEC host receives the application instance migration request sent by the first target MEC host to obtain the identifier of the target application instance and the identifier of the first target MEC host. Further, the source MEC host sends a relocation request including the identifier of the target application instance and the identifier of the first target MEC host to the MEO.

[0062] For example, the S-MEP sends a relocation request including the identifier of the target application instance and the identifier of the first target MEC host to the MEO through the S-MEPM.

[0063] S203, the MEO determines a second target MEC host from the neighboring MEC host information of the first target MEC host in response to the relocation request, and sends an instantiation application request to the second target MEC host.

[0064] The instantiation application request is used to instruct the second target MEC host to create the target application instance.

[0065] As a possible implementation, the MEO determines the second target MEC host from the multiple MEC hosts in the MEC host information according to the resource occupancy of the target application instance and the available resources of each MEC host in the MEC host information.

[0066] It can be understood that, considering the operator policy, the mobility policy, the application program requirement, the application program function, the mobile edge host function, the state of the mobile edge system, etc., finally, the MEO selects the second target MEC host adjacent to the first target MEC host, and sends an instantiation application request to the second target MEC host to instruct the second target MEC host to create the target application instance.

[0067] As shown in Figure 6 The above method preliminarily locates the UE to the first target MEC host, and uses the method of breaking first and then connecting to relocate the application program state information to another MEC host before changing the best MEC host. The MEC system predicts the switching time and notifies the MEC application, which will reposition the state to the best MEC host in advance. The preliminary relocation can reduce the end-to-end delay and relocation delay of the MEC service when the UE is highly mobile.

[0068] In some embodiments, the first target MEC host and the second target MEC host can be the same. That is, the MEO considers that the first target MEC host is the best MEC host after analysis.

[0069] The technical scheme provided by the embodiments of the present application at least brings the following beneficial effects: The application instance migration method provided by the present application is applied to a multi-access edge computing (MEC) system, the MEC system comprising a plurality of MEC hosts and a mobile edge orchestrator (MEO), and because each MEC host is preconfigured with adjacent MEC host information, after a user equipment (UE) moves to a target area, a first target MEC host in the target area receives an application instance migration request of the UE and sends the application instance migration request to a source MEC host. The source MEC host is a MEC host accessed by the UE in a source area; the application instance migration request is used to request migration of a target application instance; the first target MEC host and the source MEC host are both MEC hosts in the MEC system. Further, the source MEC host sends a relocation request comprising an identifier of the target application instance and an identifier of the first target MEC host to the MEO. The MEO determines a second target MEC host from adjacent MEC host information of the first target MEC host in response to the relocation request and sends an instantiation application request to the second target MEC host; the instantiation application request is used to instruct the second target MEC host to create the target application instance. Through the above scheme, after the UE moves to a new cell, the present application first accesses a new MEC host for the UE (i.e., pre-relocation), further selects a best MEC host for the UE from adjacent MEC host information of the new MEC host, and migrates the application instance to the MEC host, so as to improve user experience.

[0070] In one design, in order to update the traffic routing rule of the target application instance, as shown in FIG. 6, the application instance migration method provided by the embodiments of the present application further comprises the following steps. Figure 7

[0071] S301, the MEO sends address information of the second target MEC host to the source MEC host.

[0072] As a possible implementation manner, the MEO determines the second target MEC host from the plurality of MEC hosts in the MEC host information according to resource occupation of the target application instance and available resources of each MEC host in the MEC host information. Further, the MEO sends address information of the determined second target MEC host to the source MEC host.

[0073] S302, the source MEC host sends a traffic routing rule update request to the second target MEC host according to the address information of the second target MEC host.

[0074] The traffic routing rule update request comprises the traffic routing rule of the target application instance.

[0075] S303, the second target MEC host updates the traffic routing rule of the target application instance according to the traffic routing rule update request.​

[0076] In one design, to complete the update of the traffic routing rule, as shown in Figure 8 After the second target MEC host updates the traffic routing rule of the target application instance, the method for application instance migration provided by the embodiments of the present application further includes:

[0077] S304, the second target MEC host sends a traffic routing rule update completion message to the source MEC host.

[0078] It can be understood that this message indicates that the second target MEC host is ready to perform application relocation and provide services for the UE.

[0079] In actual application, after the target application instance is created on the second target MEC host, the second target MEC host will activate the traffic rule through the Mp1 interface and activate the corresponding data plane traffic routing rule through the Mp2 interface after the relocation is completed.

[0080] S305, in response to the traffic routing rule update completion message, the source MEC host deactivates the traffic routing rule of the target application instance.

[0081] As a possible implementation, in response to the traffic routing rule update completion message, the source MEC host deactivates the traffic routing rule of the target application instance through the Mp1 interface.

[0082] The above embodiments mainly introduce the schemes provided by the embodiments of the present application from the perspective of the device (apparatus). It can be understood that, in order to implement the above method, the apparatus or device contains the corresponding hardware structure and / or software module for executing each method process, and these corresponding hardware structure and / or software module for executing each method process can constitute an application information determination apparatus. Those skilled in the art should easily realize that, in combination with the algorithm steps of each example described in the embodiments of the present application, the present application can be realized in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software driven hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0083] The embodiments of the present application can divide the functions of the device or equipment according to the above-mentioned method examples, for example, the device or equipment can correspond to each function to divide each function module, or two or more functions can be integrated in one processing module. The above-mentioned integrated module can be realized in the form of hardware or in the form of a software function module. It should be noted that the division of the module in the embodiments of the present application is illustrative, and is only a logical function division. When actually implemented, another division mode can be used.

[0084] Figure 9 is a structural schematic diagram of an application instance migration device according to an exemplary embodiment. Referring to Figure 9 application instance migration device 40 provided by the embodiments of the present application, applied to a multi-access edge computing (MEC) system, the MEC system includes a plurality of MEC hosts and a mobile edge orchestrator (MEO), and each MEC host is pre-configured with adjacent MEC host information.

[0085] The application instance migration device 40 includes a receiving unit 401, a determining unit 402, and a sending unit 403.

[0086] The receiving unit 401 is configured to receive a relocation request of a source MEC, and the relocation request includes an identifier of a target application instance and an identifier of a first target MEC host. The determining unit 402 is configured to determine a second target MEC host from the adjacent MEC host information of the first target MEC host in response to the relocation request. The sending unit 403 is configured to send an instantiation application request to the second target MEC host.

[0087] Figure 10 is a structural schematic diagram of an electronic device provided by the present application. As Figure 10 The electronic device 50 can include at least one processor 501 and a memory 502 for storing processor-executable instructions, wherein the processor 501 is configured to execute the instructions in the memory 502 to implement the application instance migration method in the above-mentioned embodiments.

[0088] In addition, the electronic device 50 can further include a communication bus 503 and at least one communication interface 504.

[0089] The processor 501 can be a central processing unit (CPU), a micro processing unit, an ASIC, or one or more integrated circuits for controlling the execution of programs of the present application scheme.

[0090] The communication bus 503 can include a path for transmitting information between the above-mentioned components.

[0091] The communication interface 504, using any transceiver-like mechanism, is used to communicate with other devices or communication networks such as an Ethernet, a radio access network (RAN), a wireless local area network (WLAN), and so on.

[0092] The memory 502 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM), or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, a magnetic disk storage or other magnetic storage devices, or any other medium capable of storing desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to. The memory can exist independently, connected to the processor 501 through a bus. The memory can also be integrated with the processor 501.

[0093] The memory 502 is configured to store instructions for implementing the solutions of the present application, and the processor 501 is configured to control the execution of the instructions. The processor 501 is configured to execute the instructions stored in the memory 502, thereby realizing the functions in the methods of the present application.

[0094] As an example, the functions implemented by the receiving unit 401, the determining unit 402, and the sending unit 403 in the application instance migration apparatus 40 are the same as the functions of the processor 501 in the Figure 9 . Figure 10

[0095] In a specific implementation, as an embodiment, the processor 501 can include one or more CPUs, for example, the CPU0 and the CPU1 in the Figure 10 .

[0096] In a specific implementation, as an embodiment, the electronic device 50 can include a plurality of processors, for example, the CPU0 and the CPU1 in the Figure 10 ​The processors 501 and 507 can each be a single-CPU processor or a multi-CPU processor. The processor herein can refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0097] In a specific implementation, as an example, the electronic device 50 can further include an output device 505 and an input device 506. The output device 505 is in communication with the processor 501 and can display information in various ways. For example, the output device 505 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, a projector, or the like. The input device 506 is in communication with the processor 501 and can accept input from a user in various ways. For example, the input device 506 can be a mouse, a keyboard, a touch screen device, a sensor device, or the like.

[0098] Those skilled in the art can understand that the structure shown in the above Figure 10 The structure shown in the above does not constitute a limitation on the electronic device 50, and can include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0099] In addition, the present application also provides a computer readable storage medium, when the instructions in the computer readable storage medium are executed by the processor of the electronic device, the electronic device can execute the application instance migration method provided by the above embodiments.

[0100] In addition, the present application also provides a computer program product, including computer instructions, when the computer instructions run on the electronic device, the electronic device executes the application instance migration method provided by the above embodiments.

[0101] Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. It is intended that the present application cover any and all variations of the application that come within the scope of the claims and their equivalents. It is intended that the specification and examples be considered exemplary only, with the true scope and spirit of the application being indicated by the following claims.

Claims

1. A method for migrating application instances, characterized in that, The method is applied to a multi-access edge computing (MEC) system, wherein the MEC system includes multiple MEC hosts and a mobile edge orchestrator (MEO), and each MEC host is pre-configured with adjacent MEC host information; the method includes: After the User Equipment (UE) moves to the target area, the first target MEC host in the target area receives the UE's application instance migration request and sends the application instance migration request to the source MEC host; the source MEC host is the MEC host that the UE accesses in the source area; the application instance migration request is used to request the migration of the target application instance; both the first target MEC host and the source MEC host are MEC hosts in the MEC system; The source MEC host sends a relocation request to the MEO; the relocation request includes the identifier of the target application instance and the identifier of the first target MEC host; In response to the relocation request, the MEO determines a second target MEC host from the neighboring MEC host information of the first target MEC host based on the resource usage of the target application instance and the available resources of each MEC host in the MEC host information, and sends an application instantiation request to the second target MEC host; the application instantiation request is used to instruct the second target MEC host to create the target application instance, and the neighboring MEC host information includes multiple MEC hosts.

2. The application instance migration method according to claim 1, characterized in that, The method further includes: The MEO sends the address information of the second target MEC host to the source MEC host; The source MEC host sends a traffic routing rule update request to the second target MEC host based on the address information of the second target MEC host; the traffic routing rule update request includes the traffic routing rules of the target application instance; The second target MEC host updates the traffic routing rules of the target application instance according to the traffic routing rule update request.

3. The method for migrating application instances according to claim 2, characterized in that, After the second target MEC host completes updating the traffic routing rules of the target application instance, the method further includes: The second target MEC host sends a traffic routing rule update completion message to the source MEC host; In response to the traffic routing rule update completion message, the source MEC host disables the traffic routing rule for the target application instance.

4. A multi-access edge computing (MEC) system, characterized in that, The MEC system includes multiple MEC hosts and a mobile edge orchestrator (MEO), and each MEC host is pre-configured with adjacent MEC host information. After the User Equipment (UE) moves to the target area, the first target MEC host in the target area is used to receive the UE's application instance migration request and send the application instance migration request to the source MEC host; the source MEC host is the MEC host that the UE accesses in the source area; the application instance migration request is used to request the migration of the target application instance; Both the first target MEC host and the source MEC host are MEC hosts in the MEC system; The source MEC host is used to send a relocation request to the MEO; the relocation request includes the identifier of the target application instance and the identifier of the first target MEC host; In response to the relocation request, the MEO determines a second target MEC host from the neighboring MEC host information of the first target MEC host based on the resource usage of the target application instance and the available resources of each MEC host in the MEC host information, and sends an application instantiation request to the second target MEC host; the application instantiation request instructs the second target MEC host to create the target application instance, and the neighboring MEC host information includes multiple MEC hosts.

5. The MEC system according to claim 4, characterized in that, The MEO is also used to send the address information of the second target MEC host to the source MEC host; The source MEC host is also configured to send a traffic routing rule update request to the second target MEC host based on the address information of the second target MEC host; the traffic routing rule update request includes the traffic routing rules of the target application instance; The second target MEC host is also used to update the traffic routing rules of the target application instance according to the traffic routing rule update request.

6. The MEC system according to claim 5, characterized in that, After the second target MEC host completes the update of the traffic routing rules of the target application instance, the second target MEC host is also used to send a traffic routing rule update completion message to the source MEC host; The source MEC host is also used to disable the traffic routing rules of the target application instance in response to the traffic routing rule update completion message.

7. An electronic device, characterized in that, include: A processor, and a memory for storing instructions executable by the processor; wherein the processor is configured to execute instructions to implement the method for migrating an application instance as described in any one of claims 1-3.

8. A computer-readable storage medium storing instructions thereon, characterized in that, When the instructions in the computer-readable storage medium are executed by the processor of the electronic device, the electronic device is able to perform the application instance migration method as described in any one of claims 1-3.

Images