CN113032111B - Application migration method, device, system and computer readable storage medium - Google Patents
Application migration method, device, system and computer readable storage medium Download PDFInfo
- Publication number
- CN113032111B CN113032111B CN201911341540.5A CN201911341540A CN113032111B CN 113032111 B CN113032111 B CN 113032111B CN 201911341540 A CN201911341540 A CN 201911341540A CN 113032111 B CN113032111 B CN 113032111B
- Authority
- CN
- China
- Prior art keywords
- application program
- application
- mec
- migration
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 230000005012 migration Effects 0.000 title claims abstract description 122
- 238000013508 migration Methods 0.000 title claims abstract description 122
- 238000000034 method Methods 0.000 title claims abstract description 40
- 230000004044 response Effects 0.000 claims abstract description 45
- 238000004590 computer program Methods 0.000 claims description 4
- 238000012795 verification Methods 0.000 claims description 4
- 238000005516 engineering process Methods 0.000 abstract description 3
- 238000007726 management method Methods 0.000 description 13
- 238000010586 diagram Methods 0.000 description 12
- 230000011664 signaling Effects 0.000 description 7
- 238000013468 resource allocation Methods 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 3
- 239000003795 chemical substances by application Substances 0.000 description 3
- 230000003993 interaction Effects 0.000 description 2
- 238000010926 purge Methods 0.000 description 2
- 238000010200 validation analysis Methods 0.000 description 2
- 238000013475 authorization Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 239000003999 initiator Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
- G06F9/4856—Task life-cycle, e.g. stopping, restarting, resuming execution resumption being on a different machine, e.g. task migration, virtual machine migration
Abstract
The present disclosure relates to a migration method, apparatus, system and computer-readable storage medium for application programs, and relates to the field of computer technology. The method comprises the following steps: according to a migration request of an application program in an MEC system sent by a user terminal, corresponding resources are allocated for the application program in a target cloud system of the migration request, so that instantiation of the application program is completed; sending an instantiation completion response to the MEC system so that the MEC system returns the context information of the application program; and running the instance of the application program according to the context information to complete the migration of the application program in the target cloud system.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to an application migration method, an application migration device, an application migration system, and a computer readable storage medium.
Background
MEC (Mobile Edge Computing ) is a new network architecture concept that can provide cloud computing capabilities and information technology service environments at the edge of cellular networks. The basic idea of the MEC is to migrate the cloud computing platform from the inside of the mobile core network to the edge of the mobile access network, so as to realize the elastic utilization of computing and storage resources.
The method ensures that the terminal user still keeps the connection with the network when the terminal user is switched in the mobile network or between different networks, and the mobility and the continuity support of the service are one of the functional requirements of the MEC system.
In the related art, when a user terminal moves to a target MEC host service area, a MEC application instance is migrated from an external cloud environment to a target MEC host.
Disclosure of Invention
The inventors of the present disclosure found that the above-described related art has the following problems: after a user moves from an MEC coverage area to a non-MEC coverage area, the MEC application program cannot be migrated to a cloud environment outside the MEC system on the premise of maintaining service continuity and guaranteeing good service experience of the user.
In view of this, the present disclosure proposes a migration technical solution of an application program, which can migrate an MEC application program into a cloud environment outside an MEC system on the premise of maintaining service continuity and guaranteeing good service experience of a user.
According to some embodiments of the present disclosure, there is provided a migration method of an application program, including: according to a migration request of an application program in an MEC system sent by a user terminal, corresponding resources are allocated for the application program in a target cloud system of the migration request, so that instantiation of the application program is completed; sending an instantiation completion response to the MEC system so that the MEC system returns the context information of the application program; and running the instance of the application program according to the context information to complete the migration of the application program in the target cloud system.
In some embodiments, completing instantiation of the application includes: after corresponding resources are allocated, relevant service configuration and domain name system configuration are carried out on the application program instance in the target cloud system according to the migration request, so that the application program instantiation is completed.
In some embodiments, allocating respective resources for an application in a target cloud system of a migration request includes: verifying the migration request according to the configuration parameters in the migration request; in case of passing the verification, corresponding resources are allocated to the application program.
In some embodiments, the context information is obtained for the MEC platform and returned through the carrier operating system, MEC management orchestrator, and customer-facing service portal.
In some embodiments, the method further comprises: and sending a successful operation response to the MEC system so that the MEC system deletes the relevant information of the application program in the MEC system according to the service attribute of the application program.
In some embodiments, sending the run success response to the MEC system includes: an success response is sent to the MEC system to terminate the instance of the application at the MEC system if the business attributes of the application are to be serviced for a particular user.
In some embodiments, sending the run success response to the MEC system includes: and sending a successful operation response to the MEC system so that the MEC system can clear the context information of the application program in the condition that the service attribute of the application program is used for providing services for a plurality of users.
According to further embodiments of the present disclosure, there is provided an apparatus for migrating an application program, including: the instantiation unit is used for distributing corresponding resources for the application program in a target cloud system of the migration request according to the migration request of the application program in the MEC system sent by the user terminal so as to complete the instantiation of the application program; the transmission unit is used for transmitting an instantiation completion response to the MEC system so that the MEC system returns the context information of the application program; and the running unit is used for running the instance of the application program according to the context information so as to finish the migration of the application program in the target cloud system.
In some embodiments, after the instantiation unit allocates the corresponding resources, relevant service configuration and domain name system configuration are performed on the application program instance in the target cloud system according to the migration request, so as to complete the instantiation of the application program.
In some embodiments, the instantiation unit validates the migration request according to the configuration parameters in the migration request, and in the case of passing the validation, allocates corresponding resources for the application program.
In some embodiments, the context information is obtained for the MEC platform and returned through the carrier operating system, MEC management orchestrator, and customer-facing service portal.
In some embodiments, the sending unit sends a successful running response to the MEC system, so that the MEC system deletes relevant information of the application program in the MEC system according to the service attribute of the application program.
In some embodiments, the sending unit sends a run success response to the MEC system to terminate the instance of the application at the MEC system if the business attribute of the application is to provide service to a particular user.
In some embodiments, the sending unit sends a run success response to the MEC system to clear the context information of the application at the MEC system if the business attributes of the application are serving multiple users.
According to still further embodiments of the present disclosure, there is provided an application migration apparatus including: a memory; and a processor coupled to the memory, the processor configured to execute the migration method of the application program in any of the above embodiments based on instructions stored in the memory device.
According to still further embodiments of the present disclosure, there is provided a migration system of an application program, including: the target cloud system is used for executing the migration method of the application program in any embodiment; and the MEC system is used for sending the context information of the application program to be migrated to the target cloud system.
According to still further embodiments of the present disclosure, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the migration method of an application in any of the above embodiments.
In the above embodiment, according to the migration request and the context information, the instantiation and the operation of the application program to be migrated are performed in the migrated target cloud system respectively, so as to complete the migration of the application program. Therefore, the MEC application program can be migrated to the cloud environment outside the MEC system on the premise of maintaining service continuity and guaranteeing good service experience of users.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description, serve to explain the principles of the disclosure.
The disclosure may be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings in which:
FIG. 1 illustrates a flow chart of some embodiments of a migration method of an application of the present disclosure;
FIG. 2 illustrates a signaling diagram of some embodiments of a migration method of an application of the present disclosure;
FIG. 3 illustrates a signaling diagram of further embodiments of a migration method of an application of the present disclosure;
FIG. 4 illustrates a block diagram of some embodiments of a migration apparatus of an application of the present disclosure;
FIG. 5 illustrates a block diagram of other embodiments of a migration apparatus of an application of the present disclosure;
FIG. 6 illustrates a block diagram of still further embodiments of a migration apparatus of an application of the present disclosure;
FIG. 7 illustrates a block diagram of some embodiments of a migration system for applications of the present disclosure.
Detailed Description
Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of the components and steps, numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present disclosure unless it is specifically stated otherwise.
Meanwhile, it should be understood that the sizes of the respective parts shown in the drawings are not drawn in actual scale for convenience of description.
The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses.
Techniques, methods, and apparatus known to one of ordinary skill in the relevant art may not be discussed in detail, but should be considered part of the authorization specification where appropriate.
In all examples shown and discussed herein, any specific values should be construed as merely illustrative, and not a limitation. Thus, other examples of the exemplary embodiments may have different values.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further discussion thereof is necessary in subsequent figures.
As described above, after a user moves from an MEC coverage area to a non-MEC coverage area, in order to maintain service continuity and ensure a good service experience for the user, the MEC application needs to be migrated from the MEC host into a cloud environment outside the MEC system.
In an external cloud environment, instantiation of an application program is required, and business services continue to be provided for users. Thus, the migration of MEC applications mainly involves two aspects of processing: transmitting an application file running in the MEC host to an external cloud host; the application instance and user context information are migrated to an external cloud host to maintain business continuity.
In view of the above, for MEC service applications (application programs) that need to be migrated, user context information can be classified into stateless service applications and stateful service applications according to whether the MEC service applications need to store it.
For example, for stateless business applications, there is no need to record or store service states and user-related data, and the new service session is independent of the context information of the previous service session.
For example, for stateful service applications, it is desirable to record service session related state information (including context information), which may be stored in the end user application or MEC service application instance, in order to ensure service continuity when the service session state transitions.
Therefore, when the MEC service application is migrated, the context information of the stateless service application is not required to be transferred to the application instance running on the target cloud host; the context information of the stateful business application needs to be transferred to the target cloud host, so that the continuity of the business application is guaranteed.
In some embodiments, for MEC service applications that need to be migrated, they can be classified into dedicated service applications and shared service applications according to the service attributes of the MEC service applications.
For example, a specialized business application is an application program that specifically serves a particular user. After the end user moves to the external cloud environment, the instance of the dedicated business application needs to be migrated to the target cloud host. The context information of the user in the application of the special service also needs to be synchronized to the target cloud host to maintain the service continuity.
For example, a shared service application is not dedicated to a particular user, but is an application that serves multiple users or all users within the MEC coverage area simultaneously. When the end user has moved out of the coverage of the source MEC, considering that the service application also needs to serve other users, the MEC service application instance does not need to be terminated, and only the context information of the user in the MEC service application needs to be transferred to the target host.
In some embodiments, the MEC application to be migrated is a third party application that is already running in the cloud system. In this case, the image file of the third party application running in the MEC host may be uploaded to the cloud host through a CFS Portal (Customer FACING SERVICE Portal) to complete the migration of the third party application. For example, the MEC file template of the application may be converted to an image file that may be instantiated in the cloud host and uploaded to the cloud host.
The technical scheme of the present disclosure can realize migration of application instances from the MEC system to the external cloud environment. Different migration methods can be adopted for the two application programs according to different characteristics of the special stateful application and the shared stateful application. Therefore, when the user moves from the MEC coverage area to the external cloud environment, service continuity is maintained through migration of the application program and the context information of the user, and good service experience of the user is ensured. For example, this can be achieved by the following embodiments.
FIG. 1 illustrates a flow chart of some embodiments of a migration method of an application of the present disclosure.
As shown in fig. 1, the method includes: step 110, instantiating the application program; step 120, sending an instantiation completion response; and step 130, running an instance of the application.
In step 110, according to a migration request of an application program in the MEC system sent by the user terminal, corresponding resources are allocated to the application program in a target cloud system of the migration request, so as to complete instantiation of the application program. For example, the migration challenge may carry information about the application program, such as an application image file, a user location, an application identifier, a configuration parameter, and the like.
In some embodiments, after a user moves from an MEC coverage area to a non-MEC coverage area, it is desirable to migrate the stateful business application of the MEC from the MEC host into a cloud system external to the MEC system.
In some embodiments, the migration request is validated according to configuration parameters in the migration request; in case of passing the verification, corresponding resources are allocated to the application program.
In some embodiments, after corresponding resources are allocated, relevant service configuration and domain name system configuration are performed on the application program instance in the target cloud system according to the migration request, so as to complete the application program instantiation.
In step 120, an instantiation complete response is sent to the MEC system so that the MEC system returns context information for the application.
In some embodiments, the context information is obtained for the MEC platform and returned through the carrier operating system, MEC management orchestrator, and customer-facing service portal.
In step 130, an instance of the application is run according to the context information to complete the migration of the application in the target cloud system.
In some embodiments, a run success response is sent to the MEC system so that the MEC system deletes relevant information of the application in the MEC system according to the business attributes of the application.
For example, a run success response is sent to the MEC system so that the MEC system terminates an instance of the application at the MEC system if the business attributes of the application are to provide services (dedicated business applications) for a particular user. May be implemented by the corresponding signaling interaction flow of event 215 through event 226 in fig. 2.
For example, a run success response is sent to the MEC system so that the MEC system clears the context information of the application in the event that the business attributes of the application are serving multiple users (shared business applications). This may be achieved by the corresponding signaling interaction flow of events 315 through 320 in fig. 3.
In the above embodiment, according to the migration request and the context information, the instantiation and the operation of the application program to be migrated are performed in the migrated target cloud system respectively, so as to complete the migration of the application program. Therefore, the MEC application program can be migrated to the cloud environment outside the MEC system on the premise of maintaining service continuity and guaranteeing good service experience of users.
In some embodiments, for a migration scenario of a proprietary, stateful application, after an end user moves from the MEC coverage area to the external cloud environment, the application instance running on the MEC host needs to be terminated in addition to transferring the user's context information between the MEC system and the external cloud environment. For example, the above technical solution may be implemented by the embodiment in fig. 2.
Fig. 2 illustrates a signaling diagram of some embodiments of a migration method of an application of the present disclosure.
As shown in fig. 2, in event 201, the UE sends an application migration request to the external cloud system.
For example, an application running on a UE (User Equipment) may send a migration request to an OSS (Operations Support System, operator operating system) through a User lifecycle management agent (User APP LIFE CYCLE MANAGEMENT Proxy). The migration request is used to trigger the migration of an application instance from the MEC system to the external cloud environment.
In event 202, the OSS receives a migration request for an application.
For example, after the OSS receives a migration request of an application, the migration request may be sent to an external CMP (Cloud Management Platforms, cloud management platform) through a CFS Portal. The migration challenge may carry information such as an application image file, a user location, an application identifier, a configuration parameter, and the like.
In event 203, the CMP sends a resource allocation request.
For example, CMP examines the configuration parameters of the application instance to determine if the migration request is authorized. In the event that the migration request is approved, the CMP selects an appropriate cloud host in the target cloud system for carrying the application; and transmits a resource allocation request message to the Cloud VMS (Cloud Virtualization MANAGEMENT SYSTEM ). The resource allocation request message may carry information about the resource requirements of the computing, storage, network, etc. required for the application program instantiation.
In event 204, the Cloud VMS returns a resource allocation response message to the CMP.
For example, the Cloud VMS allocates related resources in the target Cloud system according to the resource allocation request message, and loads the virtual machine containing the application image file. Thus, the running of the virtual machine and the instantiation of the application program are completed, and response information is fed back to the CMP;
In event 205, the CMP sends a configuration request message.
For example, CMP sends configuration request information to Cloud Host. The configuration request information may carry information such as a business rule, a DNS (Domain NAME SYSTEM) rule, and the like.
At event 206, the Cloud Host completes the relevant configuration of the application waiting for the application to run properly in the target Cloud system.
In event 207, the Cloud Host sends a configuration response message to the CMP. The configuration response message identifies that the associated configuration of the application has been successfully executed and is functioning properly.
At event 208, the CMP sends an application instantiation response message to the OSS and MEO (MEC manager).
At event 209, the MEO sends an application state information acquisition command to the MEP via MEPM (MEC Platform Manager, MEC platform management). For example, the status information includes context information of the user.
In event 210, the MEP (MEC Platform) sends the acquired state information of the application to the Cloud Host. For example, the MEP sends status information via OSS and MEO, CFS Portal.
At event 211, the Cloud Host and Cloud App (Cloud application) complete synchronization of the state information of the application.
In event 212, the Cloud Host sends an application state information send response to the MEP. The application state information transmission response indicates that the state information completes synchronization.
At event 213, the Cloud APP sends an application instance running notification to the CMP. For example, the newly created instance of the Cloud APP sends a business application instance running notification to the CMP through the Cloud Host.
In event 214, the CMP sends an application instance running notification to the OSS and MEO. For example, the CMP forwards the received application instance operation notification to the OSS and MEO via the CFS Portal.
At event 215, the MEO sends a terminating application instance request to the MEPM. The terminating application instance requests the migrated dedicated MEC application instance for execution in the terminating MEC host.
At event 216, the MEPM forwards the above-described terminating application instance request to the MEP so that the MEP begins the terminating flow for the dedicated MEC application instance.
In event 217, the MEP sends a terminating application instance request to an instance of the MEC APP.
At event 218, after receiving the application instance termination request, the MEC APP sends a service termination message to the MEP to disable the relevant traffic rules for the dedicated MEC application instance.
At event 219, after the MEP completes the service flow rule configuration, a service broker response message is fed back to the MEC APP.
At event 220, the MEC APP sends a DNS finalization message to the MEP to invalidate the DNS rules associated with the dedicated MEC application instance.
In event 221, after the MEP finishes DNS rule termination, feeding back a DNS termination response message to the MEC APP;
In event 222, the MEP sends an application instance termination response to the MEPM to trigger a resource release process for the application instance.
In event 223, the MEPM sends a resource delete request to the VIM (Virtualization Infrastructure Manager, virtualized infrastructure management) to delete the relevant resources allocated to the application instance.
In event 224, the VIM feeds back a resource delete response to the MEPM after successfully deleting the resource.
In event 225, the MEPM sends a response message to the initiator OSS and MEO that terminated the application instance request, completing the application instantiation termination.
At event 226, the OSS sends an application migration response from the MEC system to the external cloud environment to the UE through the user program lifecycle management agent, completing the application migration.
In some embodiments, for a shared, stateful application instance migration scenario, after an end user moves from the MEC coverage area to the external cloud environment, the application instance running on the MEC host need not be terminated, but only its relevant user context information need be purged. For example, the above technical solution may be implemented by the embodiment in fig. 3.
Fig. 3 shows a signaling diagram of further embodiments of a migration method of an application of the present disclosure.
As shown in fig. 3, the events in fig. 3 may be performed after the events 201 through 214 in fig. 2 are performed.
In event 315, the MEO sends a clear UE context information request to the MEPM.
In event 316, the MEPM forwards the clear UE context information request to the MEP.
In event 317, the MEP sends a clear UE context information command to the MEC APP instance to delete the UE context information of the migrated application.
At event 318, after deleting the UE context information, the MEP forwards a UE context information clear response message to the MEPM.
In event 319, the MEPM sends a UE context information purge response to the OSS and MEOs to complete the UE context information purge.
In event 320, the OSS sends an application migration response from the MEC system to the external cloud environment to the UE through the user program lifecycle management agent, completing the application migration.
In the above embodiment, an application instance migration technical solution from an MEC system to an external cloud environment is provided; and respectively carrying out design consideration on application instance migration of the special-type application, the stateful application and the shared type application and the stateful application in the MEC system and the external cloud environment, and providing a specific signaling flow.
Fig. 4 illustrates a block diagram of some embodiments of a migration apparatus of an application of the present disclosure.
As shown in fig. 4, the migration apparatus 4 of the application program includes an instantiation unit 41, a transmission unit 42, and an operation unit 43.
The instantiation unit 41 allocates corresponding resources for the application program in the target cloud system of the migration request according to the migration request of the application program in the MEC system sent by the user terminal, so as to complete the instantiation of the application program.
In some embodiments, after allocating the corresponding resources, the instantiation unit 41 performs relevant service configuration and domain name system configuration on the application program instance in the target cloud system according to the migration request, so as to complete the instantiation of the application program.
In some embodiments, the instantiation unit 41 validates the migration request according to the configuration parameters in the migration request, and in the event of a validation, allocates the corresponding resources to the application.
The transmitting unit 42 transmits an instantiation completion response to the MEC system so that the MEC system returns the context information of the application.
In some embodiments, the context information is obtained for the MEC platform and returned through the carrier operating system, MEC management orchestrator, and customer-facing service portal.
In some embodiments, the sending unit 42 sends a run success response to the MEC system, so that the MEC system deletes relevant information of the application in the MEC system according to the service attribute of the application.
In some embodiments, the sending unit 42 sends a run success response to the MEC system to terminate the instance of the application at the MEC system if the business attributes of the application are to be serviced for a particular user.
In some embodiments, the sending unit 42 sends a run success response to the MEC system to clear the context information of the application at the MEC system in case the business attributes of the application are serving multiple users.
The operation unit 43 operates an instance of the application program according to the context information to complete migration of the application program in the target cloud system.
In the above embodiment, according to the migration request and the context information, the instantiation and the operation of the application program to be migrated are performed in the migrated target cloud system respectively, so as to complete the migration of the application program. Therefore, the MEC application program can be migrated to the cloud environment outside the MEC system on the premise of maintaining service continuity and guaranteeing good service experience of users.
FIG. 5 illustrates a block diagram of further embodiments of a migration apparatus for applications of the present disclosure.
As shown in fig. 5, the migration device 5 of the application program of this embodiment includes: a memory 51 and a processor 52 coupled to the memory 51, the processor 52 being configured to execute the migration method of the application in any one of the embodiments of the present disclosure based on instructions stored in the memory 51.
The memory 51 may include, for example, a system memory, a fixed nonvolatile storage medium, and the like. The system memory stores, for example, an operating system, application programs, boot loader programs, databases, and other programs.
Fig. 6 illustrates a block diagram of still further embodiments of a migration apparatus for applications of the present disclosure.
As shown in fig. 6, the migration device 6 of the application program of this embodiment includes: a memory 610 and a processor 620 coupled to the memory 610, the processor 620 being configured to execute the migration method of the application program in any of the foregoing embodiments based on instructions stored in the memory 610.
The memory 610 may include, for example, system memory, fixed nonvolatile storage media, and the like. The system memory stores, for example, an operating system, application programs, boot loader programs, and other programs.
The migration device 6 of the application program may further include an input-output interface 630, a network interface 640, a storage interface 650, and the like. These interfaces 630, 640, 650 and the memory 610 and processor 620 may be connected by, for example, a bus 660. The input/output interface 630 provides a connection interface for input/output devices such as a display, a mouse, a keyboard, and a touch screen. Network interface 640 provides a connection interface for various networking devices. The storage interface 650 provides a connection interface for external storage devices such as SD cards, U-discs, and the like.
FIG. 7 illustrates a block diagram of some embodiments of a migration system for applications of the present disclosure.
As shown in fig. 7, the migration system 7 of the application program includes a target cloud system 71 and an MEC system 72.
The target cloud system 71 is used to execute the migration method of the application program in any of the above embodiments; the MEC system 72 is configured to send context information of the application to be migrated to the target cloud system.
It will be appreciated by those skilled in the art that embodiments of the present disclosure may be provided as a method, system, or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable non-transitory storage media having computer-usable program code embodied therein.
Heretofore, a migration method of an application program, a migration apparatus of an application program, a migration system of an application program, and a computer-readable storage medium according to the present disclosure have been described in detail. In order to avoid obscuring the concepts of the present disclosure, some details known in the art are not described. How to implement the solutions disclosed herein will be fully apparent to those skilled in the art from the above description.
The methods and systems of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, firmware. The above-described sequence of steps for the method is for illustration only, and the steps of the method of the present disclosure are not limited to the sequence specifically described above unless specifically stated otherwise. Furthermore, in some embodiments, the present disclosure may also be implemented as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.
Although some specific embodiments of the present disclosure have been described in detail by way of example, it should be understood by those skilled in the art that the above examples are for illustration only and are not intended to limit the scope of the present disclosure. It will be appreciated by those skilled in the art that modifications may be made to the above embodiments without departing from the scope and spirit of the disclosure. The scope of the present disclosure is defined by the appended claims.
Claims (11)
1. A method of application migration, comprising:
calculating a migration request of an application program in an MEC system according to a mobile edge sent by a user terminal, and distributing corresponding resources for the application program in a target cloud system of the migration request so as to complete instantiation of the application program;
sending an instantiation completion response to the MEC system so that the MEC system returns context information of the application;
According to the context information, running an instance of the application program to complete migration of the application program in the target cloud system;
transmitting a successful operation response to the MEC system so that the MEC system deletes relevant information of the application program in the MEC system according to service attributes of the application program, wherein the service attributes comprise a special application for providing service for a specific user and a shared application for providing service for a plurality of users;
Wherein the sending an operation success response to the MEC system includes:
Sending a successful operation response to the MEC system so that the MEC system terminates the instance of the application program at the MEC system if the service attribute of the application program is the dedicated application;
and sending a successful operation response to the MEC system, so that the MEC system can maintain the instance of the application program in the MEC system and clear the context information of the application program in the MEC system under the condition that the service attribute of the application program is the shared application.
2. The migration method of claim 1, wherein the completing instantiation of the application comprises:
And after corresponding resources are allocated, carrying out relevant service configuration and domain name system configuration on the application program instance in the target cloud system according to the migration request so as to complete the application program instantiation.
3. The migration method of claim 1, wherein the allocating, in the target cloud system of the migration request, the respective resources for the application program comprises:
verifying the migration request according to the configuration parameters in the migration request;
And in the case of passing the verification, corresponding resources are allocated for the application program.
4. The migration method of claim 1, wherein,
The context information is obtained for the MEC platform and returned through the operator operating system, MEC management orchestrator, and customer-facing service portal.
5. An application migration apparatus, comprising:
the instantiation unit is used for calculating a migration request of an application program in the MEC system according to a mobile edge sent by a user terminal, and distributing corresponding resources for the application program in a target cloud system of the migration request so as to complete the instantiation of the application program;
a sending unit, configured to send an instantiation completion response to the MEC system, so that the MEC system returns context information of the application program;
the running unit is used for running the instance of the application program according to the context information so as to finish the migration of the application program in the target cloud system;
Wherein,
The sending unit sends a successful operation response to the MEC system so that the MEC system deletes relevant information of the application program in the MEC system according to service attributes of the application program, wherein the service attributes comprise a special application for providing service for a specific user and a shared application for providing service for a plurality of users, the sending unit sends a successful operation response to the MEC system so that the MEC system terminates an instance of the application program when the service attributes of the application program are the special application, and sends a successful operation response to the MEC system so that the MEC system maintains the instance of the application program when the service attributes of the application program are the shared application and clears context information of the application program when the MEC system clears the context information of the application program.
6. The migration apparatus of claim 5, wherein,
And after the corresponding resources are allocated, the instantiation unit carries out relevant service configuration and domain name system configuration on the instance of the application program in the target cloud system according to the migration request so as to complete the instantiation of the application program.
7. The migration apparatus of claim 5, wherein,
And the instantiation unit verifies the migration request according to the configuration parameters in the migration request, and allocates corresponding resources for the application program under the condition of passing the verification.
8. The migration apparatus of claim 5, wherein,
The context information is obtained for the MEC platform and returned through the operator operating system, MEC management orchestrator, and customer-facing service portal.
9. An application migration apparatus, comprising:
A memory; and
A processor coupled to the memory, the processor configured to execute the migration method of the application of any one of claims 1-4 based on instructions stored in the memory.
10. A migration system for an application program, comprising:
The target cloud system for executing the migration method of the application program according to any one of claims 1 to 4;
and the mobile edge computing MEC system is used for sending the context information of the application program to be migrated to the target cloud system.
11. A computer readable storage medium having stored thereon a computer program which when executed by a processor implements the migration method of an application program according to any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911341540.5A CN113032111B (en) | 2019-12-24 | 2019-12-24 | Application migration method, device, system and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911341540.5A CN113032111B (en) | 2019-12-24 | 2019-12-24 | Application migration method, device, system and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113032111A CN113032111A (en) | 2021-06-25 |
| CN113032111B true CN113032111B (en) | 2024-04-30 |
Family
ID=76451277
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911341540.5A Active CN113032111B (en) | 2019-12-24 | 2019-12-24 | Application migration method, device, system and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113032111B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114090200A (en) * | 2021-11-02 | 2022-02-25 | 中国联合网络通信集团有限公司 | Cross-system application instantiation migration method and device |
| CN114172951B (en) * | 2021-12-07 | 2023-06-06 | 中国联合网络通信集团有限公司 | MEC sharing method, communication device and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108632813A (en) * | 2018-05-21 | 2018-10-09 | 北京邮电大学 | The motion management method and system of mobile edge calculations |
| CN109358967A (en) * | 2018-09-26 | 2019-02-19 | 中国联合网络通信集团有限公司 | A kind of ME platform APP instantiation moving method and server |
| CN109429284A (en) * | 2017-08-31 | 2019-03-05 | 华为技术有限公司 | Example switching method and relevant apparatus |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8756611B2 (en) * | 2010-12-07 | 2014-06-17 | International Business Machines Corporation | Delayed expansion of values in context |
| US10517020B2 (en) * | 2017-12-15 | 2019-12-24 | Industrial Technology Research Institute | Mobile edge platform servers and user equipment context migration management methods thereof |
-
2019
- 2019-12-24 CN CN201911341540.5A patent/CN113032111B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109429284A (en) * | 2017-08-31 | 2019-03-05 | 华为技术有限公司 | Example switching method and relevant apparatus |
| CN108632813A (en) * | 2018-05-21 | 2018-10-09 | 北京邮电大学 | The motion management method and system of mobile edge calculations |
| CN109358967A (en) * | 2018-09-26 | 2019-02-19 | 中国联合网络通信集团有限公司 | A kind of ME platform APP instantiation moving method and server |
Non-Patent Citations (1)
| Title |
|---|
| 面向云-端融合的移动互联网应用运行平台;黄罡;刘哲;张颖;;中国科学:信息科学(第01期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113032111A (en) | 2021-06-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109358967B (en) | ME platform APP instantiation migration method and server | |
| US20190123963A1 (en) | Method and apparatus for managing resources of network slice | |
| CN107360310B (en) | mobile terminal and resource management method thereof | |
| EP2925080B1 (en) | Creating method and device for virtual base station | |
| EP3200393B1 (en) | Method and device for virtual network function management | |
| CN111698112B (en) | Resource management method and device for VNF (virtual network function) | |
| EP3133771A1 (en) | Virtual machine resource changing method, device and virtual network function device | |
| WO2016121834A1 (en) | Method, system, device, and program for managing network function virtualization | |
| CN111345008B (en) | Mobile edge host service notification method and device | |
| CN110650503B (en) | Network access method, device, system and computer readable storage medium | |
| US10481921B2 (en) | Cloud platform, application running method, and access network unit | |
| JP7100154B2 (en) | Processor core scheduling method, equipment, terminals and storage media | |
| KR20170118165A (en) | Method and apparatus for updating a network service technician | |
| CN113032111B (en) | Application migration method, device, system and computer readable storage medium | |
| KR102266089B1 (en) | Mec(mobile edge computing) system and control method thereof | |
| CN111835679B (en) | Tenant resource management method and device under multi-tenant scene | |
| CN111221618A (en) | Method and device for deploying containerized virtual network function | |
| CN109155939A (en) | A kind of load migration method, apparatus and system | |
| CN110780871A (en) | Negative one-screen loading method and device, terminal and computer readable storage medium | |
| CN111726241B (en) | Network resource management method, system, network device and readable storage medium | |
| CN114296953A (en) | Multi-cloud heterogeneous system and task processing method | |
| CN109313568A (en) | Method and apparatus for the mobile virtual network function example between network service instance | |
| US20220240158A1 (en) | Method and system for managing components of a fifth generation (5g) network slice | |
| CN109660379B (en) | Network method, system and terminal | |
| US9668082B2 (en) | Virtual machine based on a mobile device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant |