CN109358967B - ME platform APP instantiation migration method and server - Google Patents
ME platform APP instantiation migration method and server Download PDFInfo
- Publication number
- CN109358967B CN109358967B CN201811126268.4A CN201811126268A CN109358967B CN 109358967 B CN109358967 B CN 109358967B CN 201811126268 A CN201811126268 A CN 201811126268A CN 109358967 B CN109358967 B CN 109358967B
- Authority
- CN
- China
- Prior art keywords
- instantiation
- app
- platform
- migration
- request
- 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 71
- 238000013508 migration Methods 0.000 title claims abstract description 71
- 238000000034 method Methods 0.000 title claims abstract description 39
- 230000004044 response Effects 0.000 claims description 23
- 238000012217 deletion Methods 0.000 claims description 9
- 230000037430 deletion Effects 0.000 claims description 9
- 238000004590 computer program Methods 0.000 claims 3
- 238000002360 preparation method Methods 0.000 claims 1
- 238000004891 communication Methods 0.000 abstract description 5
- 238000013468 resource allocation Methods 0.000 description 11
- 238000007726 management method Methods 0.000 description 9
- 230000008569 process Effects 0.000 description 9
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 238000013475 authorization Methods 0.000 description 1
- 230000010485 coping Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000004927 fusion Effects 0.000 description 1
- 238000011534 incubation Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
Images
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/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
- G06F9/5072—Grid computing
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Mathematical Physics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the invention provides an APP instantiation migration method and a server for a mobile edge ME platform, relates to the field of communication, and can ensure that the APP completes instantiation on a new ME platform under the condition of not interrupting the original service, thereby realizing seamless migration of APP instantiation. The method comprises the following steps: a first ME platform receives an instantiation migration request sent by an APP, wherein the APP is the APP which is instantiated on the first ME platform; and the first ME platform sends the instantiation migration request to an Operation Support System (OSS) through a Mobile Edge Platform Manager (MEPM) and a Mobile Edge Orchestrator (MEO), wherein the instantiation migration request is used for indicating the OSS to migrate the APP.
Description
Technical Field
The invention relates to the field of communication, in particular to an ME platform APP instantiation migration method and a server.
Background
Multi-access Edge Computing (MEC) is a product of Information and Communication Technology (ICT) fusion, and is also a key Technology for supporting operators to perform 5G network transformation, so as to meet business development requirements of future high definition video, VR/AR, industrial internet, car networking, and the like. In addition, tens of thousands of edge DCs are the best dominant resources for operators over OTT, making edge computing a wide application space. An open and open-source edge service PaaS platform is created, and rich platform service capability and uniform API are provided for APP developers, so that innovative service incubation and commercial promotion of edge application are accelerated. And the instantiation of the APP on the mobile edge ME platform is a key ring for acquiring the platform capability of the APP, and the normal work of the APP on the ME platform can be ensured only if the instantiation of the APP is realized.
The european telecommunications standardization institute has now made a very well-established standardization process for the instantiation of APP in the ME platform. However, in the prior art, no related records of cross-ME platform migration are recorded for the APP end in the future under the situations of coping with the mobility environment, ME platform failure, newly-added ME platform requirements and the like.
Disclosure of Invention
Embodiments of the present invention provide an ME platform APP instantiation migration method and a server, which can ensure that an APP completes instantiation on a new ME platform without interrupting an original service, and realize seamless migration of APP instantiation.
To achieve the above object, an embodiment of the present invention provides an ME platform APP instantiation migration method, where the ME platform APP instantiation migration method includes:
a first ME platform receives an instantiation migration request sent by an APP, wherein the APP is the APP which is instantiated on the first ME platform;
and the first ME platform sends the instantiation migration request to an Operation Support System (OSS) through a Mobile Edge Platform Manager (MEPM) and a Mobile Edge Orchestrator (MEO), wherein the instantiation migration request is used for indicating the OSS to migrate the APP.
Correspondingly, the embodiment of the invention also provides a server for the mobile edge ME platform APP instantiation migration, which is characterized in that the server for the ME platform APP instantiation migration comprises:
a receiving module, configured to receive an instantiation migration request sent by an APP, where the APP is an APP that has been instantiated on the server;
and the sending module is used for sending the instantiation migration request to an operation support system OSS through a mobile edge platform manager MEPM and a mobile edge orchestrator MEO, wherein the instantiation migration request is used for indicating the OSS to migrate the APP.
The embodiment of the invention provides an ME platform APP instantiation migration method and a server. The method can ensure that the APP is instantiated on the new ME platform under the condition of not interrupting the original service, and seamless migration of APP instantiation is realized.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a system architecture diagram of a running environment of an ME platform APP instantiation migration method according to an embodiment of the present invention;
fig. 2 is a flowchart of an APP instantiation method on a first ME platform according to an embodiment of the present invention;
fig. 3 is a flowchart of an ME platform APP instantiation migration method according to an embodiment of the present invention;
fig. 4 is a flowchart of an APP instantiation method on a second ME platform according to an embodiment of the present invention;
fig. 5 is a flowchart of another ME platform APP instantiation migration method according to an embodiment of the present invention;
fig. 6 is a functional module schematic diagram of an ME platform APP instantiation migration server according to an embodiment of the present invention;
fig. 7 is a functional module schematic diagram of another ME platform APP instantiation migration server according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
As shown in fig. 1, a network architecture of an implementation environment of the mobile edge ME platform APP instantiation migration method of the present invention is shown. Where Mp denotes a reference point related to the mobile edge ME platform and Mm denotes a reference point related to management.
Under the architecture shown in fig. 1, the ME server includes an ME platform, ME applications, and virtualization infrastructure. The virtualization infrastructure may provide computing, storage, and network resources for the ME application. The ME platform receives traffic forwarding rules from the mobile edge platform manager MEPM, ME application or ME service and issues instructions to the forwarding plane based on the forwarding rules. An ME application is a virtual machine instance running on an ME virtualization infrastructure. The MEPM has the functions of ME platform element management, ME application lifecycle management, ME application rule and requirement management and the like. ME application lifecycle management includes the creation and termination of ME applications and provides indication messages of application related events for mobile edge orchestrator MEOs. The virtual resource manager VIM is used to manage the virtual resources of the ME applications, management tasks including virtual compute, storage, and allocation and release of network resources, and software images may also be stored on the VIM for fast instantiation of the applications. The MEO macroscopically hosts the resources and capabilities of the ME network, including all ME servers and services already deployed, the available resources in each server, the applications that have been instantiated, and the topology of the network, among others. When selecting a target ME server for a user to access, the MEO measures the user requirements and the available resources of each server, and selects the most appropriate ME server for the user. From the perspective of the ME system, OSS is the highest level management entity that supports system operation. The OSS receives requests to instantiate or terminate ME applications from the user-oriented services portal and user terminals, checks the integrity and authorization information of the application data packets and requests.
As shown in FIG. 2, a process of instantiation of an APP on a first ME platform is shown. The process may specifically include:
step 201, the OSS sends an APP instantiation request to the MEO, where the APP instantiation request includes information of an APP image.
Step 202, the MEO checks the APP instantiation configuration data and authenticates the APP instantiation request.
It should be noted that the MEO may select the most appropriate ME platform for the APP by measuring user requirements, available resources of each ME platform, and wireless network conditions. And sending an APP instantiation request to the MEPM corresponding to the ME platform, which is described in the embodiment of the present invention by taking the first ME platform and the MEPM corresponding to the first ME platform as an example.
Step 203, the MEO sends an APP instantiation request to the MEPM.
Step 204, the MEPM sends the resource configuration request and the information of the APP image to the VIM.
It should be noted that the resource allocation request includes: computing resource allocation requests, storage resource allocation requests, network resource allocation requests, and other special resource allocation requests.
Step 205, the VIM allocates resources according to the resource allocation request sent by the MEPM.
It should be noted that, if the APP image information is available, the VIM loads the APP image into the virtual machine, runs the virtual machine to instantiate the APP at the same time, and allocates an APP instantiation ID on the first ME platform to the instantiated APP.
Step 206, the VIM sends a resource configuration response to the MEPM, wherein the resource configuration response comprises an APP instantiation ID on the first ME platform.
Step 207, the MEPM sends a rule configuration request to the first ME platform. The rule configuration request comprises a traffic rule configuration request and a DNS rule configuration request.
And step 208, the first ME platform instantiates a configuration flow rule and a DNS rule for the APP.
It should be noted that, after the APP instantiation is normally running, the first ME platform may activate traffic and DNS policy. After the APP instantiates to operate normally, the first ME platform may provide the APP with available service information.
Step 209, the first ME platform sends a rule configuration response to the MEPM.
Step 210, the MEPM sends an APP instantiation response to the MEO. The instantiation response comprises the allocated resource information and the APP instantiation ID on the first ME platform.
And step 211, the MEO sends the APP instantiation response to the OSS, the result of the instantiation process is fed back to the OSS, and the APP completes instantiation on the first ME platform.
As shown in fig. 3, the mobile edge ME platform APP instantiation migration process of the present invention is shown. The specific process can comprise the following steps:
Conditions that trigger the instantiation migration of the ME platform APP include, but are not limited to: the user terminal installed with the APP moves from the coverage range of the first ME server to the coverage range of the second ME server, when the first ME platform fails and can not repair itself within the second preset time, or the first ME platform can not provide service for the APP.
The method comprises the steps that a first ME platform receives an instantiation migration request sent by an APP, and the instantiation migration request comprises a target ME platform recommended by the APP. The APP is an APP that has been instantiated on the first ME platform.
As shown in FIG. 4, a process is shown for indicating instantiation of the APP on the second ME platform after the OSS receives the instantiation migration request. The process may specifically include:
step 401, the OSS sends an APP instantiation request to the MEO, where the APP instantiation request includes information of an APP image.
Step 402, the MEO checks APP instantiation configuration data and authenticates the APP instantiation request.
It should be noted that the MEO may consider the target ME platform recommended by the APP in step 301, or may also consider the target ME platform recommended by the APP in step 301, and directly select the most appropriate ME platform for the APP by measuring the user requirements, the available resources of each ME platform, and the wireless network conditions. And sending an APP instantiation request to the MEPM corresponding to the ME platform, which is described in the embodiment of the present invention by taking the second ME platform and the MEPM corresponding to the second ME platform as an example.
Step 403, the MEO sends an APP instantiation request to the MEPM.
Step 404, the MEPM sends the resource configuration request and the information of the APP image to the VIM.
The resource configuration request includes: computing resource allocation requests, storage resource allocation requests, network resource allocation requests, and other special resource allocation requests.
It should be noted that, if the ME platform APP is instantiated and migrated due to insufficient resources of the first ME platform, the MEO may directly issue the resource scale reported by the APP to the VIM.
Step 405, the VIM allocates resources according to the resource allocation request sent by the MEPM.
It should be noted that, if the APP image information is available, the VIM loads the APP image into the virtual machine, runs the virtual machine to instantiate the APP at the same time, and allocates an APP instantiation ID on the second ME platform to the instantiated APP.
Step 406, the VIM sends a resource configuration response to the MEPM, where the resource configuration response includes the APP instantiation ID on the second ME platform.
Step 407, the MEPM sends a rule configuration request to the second ME platform. The rule configuration request comprises a traffic rule configuration request and a DNS rule configuration request.
And step 408, the second ME platform instantiates a configuration flow rule and a DNS rule for the APP.
It should be noted that, after the APP instantiation is normally running, the second ME platform may activate the traffic and DNS policy. After the APP instantiates to operate normally, the second ME platform may provide the APP with the available service information.
And step 409, the second ME platform sends a rule configuration response to the MEPM.
Step 410, the MEPM sends an APP instantiation response to the MEO. The instantiation response comprises the allocated resource information and the APP instantiation ID on the second ME platform.
Step 411, the MEO sends the APP instantiation response to the OSS, and feeds back the result of the instantiation process to the OSS, so that the ME platform APP instantiation migration is completed.
The embodiment of the invention provides an ME platform APP instantiation migration method and a server. The method can ensure that the APP is instantiated on the new ME platform under the condition of not interrupting the original service, and seamless migration of APP instantiation is realized.
Further, as shown in fig. 5, it is shown that after the migration of the APP is completed, the method for instantiating and migrating the APP of the ME platform includes:
firstly, the OSS sends an instantiation termination request to the MEO, the MEO may authenticate the instantiation termination request after receiving the instantiation termination request, and the MEPM may forward the instantiation termination request to the first ME platform after the authentication is passed.
It should be noted that, the VIM stops the APP running on the virtual machine that has been instantiated on the first ME platform and releases all resources allocated to the APP that has been instantiated on the first ME platform, and sends a resource deletion response to the MEPM at the same time. The MEPM may send an instantiation terminate response to an OSS via the MEO after receiving the resource delete response.
Further, step 502 includes: the first ME platform instantiates and terminates the APP after first preset time is reached according to the instantiation termination request; or the first ME platform immediately instantiates and terminates the APP according to the instantiation termination request.
It should be noted that the first ME platform may perform graceful termination or non-graceful termination on APP instantiation. When the first ME platform gracefully terminates the instantiation of the APP, the APP may terminate all services within a first preset time, and the first ME platform may terminate the instantiation of the APP after the first preset time arrives. If the APP still has services executing after the first preset time arrives, the first ME platform may directly terminate instantiation of the APP, which may cause service interruption or data loss. When the first ME platform performs non-graceful termination on APP instantiation, the first ME platform immediately performs instantiation termination on the APP after receiving an instantiation termination request which is sent by the OSS and forwarded by the MEO and the MEPM.
Further, step 302 may include: the instantiation migration request is used for indicating the OSS to complete instantiation of the APP on a second ME platform, the second ME platform is a target ME platform selected by the MEO for the APP, and the first ME platform and the second ME platform are in the same MEPM and the same VIM management range.
Correspondingly, the invention also provides a server 6 for the instantiation migration of the mobile edge ME platform APP. As shown in fig. 6, the server includes:
a receiving module 61, configured to receive an instantiation migration request sent by an APP, where the APP is an APP that has been instantiated on the server;
a sending module 62, configured to send the instantiation migration request to an operation support system OSS through a mobile edge platform manager MEPM and a mobile edge orchestrator MEO, where the instantiation migration request is used to instruct the OSS to migrate the APP.
Further, referring to fig. 7, the server 6 further includes:
a receiving module 61, configured to receive an instantiation termination request forwarded by the MEO and the MEPM and sent by the OSS, where the instantiation termination request includes an instantiation ID of the APP on the server;
a termination module 63, configured to terminate instantiation of the APP according to the instantiation termination request;
a sending module 62, configured to send an instantiation termination response to the MEPM, where the instantiation termination response is used to instruct the MEPM to send a resource deletion request to a virtualized resource manager VIM, and the resource deletion request is used to instruct the VIM to stop an APP running on a virtual machine that has been instantiated on the server and release all resources allocated to the APP that has been instantiated on the server.
Further, the termination module 63 is specifically configured to: the server terminates instantiation of the APP after first preset time is reached according to the instantiation termination request; or the server immediately instantiates and terminates the APP according to the instantiation termination request.
Further, the sending module 62 is specifically configured to: and indicating the OSS to complete instantiation of the APP on a second ME platform through an instantiation migration request, wherein the second ME platform is a target ME platform selected by the MEO for the APP, and the server where the second ME platform is located are in the same MEPM and the same VIM management range.
The embodiment of the invention provides an ME platform APP instantiation migration method and a server. The method can ensure that the APP is instantiated on the new ME platform under the condition of not interrupting the original service, and seamless migration of APP instantiation is realized.
In the several embodiments provided in the present application, it should be understood that the disclosed method and apparatus may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be physically included alone, or two or more units may be integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute some steps of the methods according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.
Claims (8)
1. A mobile edge ME platform APP instantiation migration method is characterized by comprising the following steps:
a first ME platform receives an instantiation migration request sent by an APP, wherein the APP is the APP which is instantiated on the first ME platform;
the first ME platform sends the instantiation migration request to an Operation Support System (OSS) through a Mobile Edge Platform Manager (MEPM) and a Mobile Edge Orchestrator (MEO), wherein the instantiation migration request is used for indicating the OSS to migrate the APP;
after the migration of the APP is completed, the ME platform APP instantiation migration method comprises the following steps:
the first ME platform receives an instantiation termination request sent by the OSS and forwarded by the MEO and the MEPM, wherein the instantiation termination request comprises an instantiation ID of the APP on the first ME platform;
the first ME platform instantiates and terminates the APP according to the instantiation termination request;
the first ME platform sends an instantiation termination response to the MEPM, wherein the instantiation termination response is used for indicating the MEPM to send a resource deletion request to a virtual resource manager (VIM), and the resource deletion request is used for indicating the VIM to stop the APP running on the virtual machine and instantiated on the first ME platform and release all resources distributed to the APP instantiated on the first ME platform.
2. The ME platform APP instantiation migration method according to claim 1, wherein the first ME platform instantiates termination of the APP according to the instantiation termination request, comprising:
the first ME platform instantiates and terminates the APP after first preset time is reached according to the instantiation termination request; alternatively, the first and second electrodes may be,
and the first ME platform immediately instantiates and terminates the APP according to the instantiation termination request.
3. The ME platform APP instantiation migration method according to claim 1, wherein the instantiation migration request is used for instructing the OSS to migrate the APP, and comprises:
the instantiation migration request is used for indicating the OSS to complete instantiation of the APP on a second ME platform, the second ME platform is a target ME platform selected by the MEO for the APP, and the first ME platform and the second ME platform are in the same MEPM and the same VIM management range.
4. A mobile edge ME platform APP instantiation migration server, characterized in that the ME platform APP instantiation migration server comprises:
a receiving module, configured to receive an instantiation migration request sent by an APP, where the APP is an APP that has been instantiated on the server;
a sending module, configured to send the instantiation migration request to an operation support system OSS through a mobile edge platform manager MEPM and a mobile edge orchestrator MEO, where the instantiation migration request is used to instruct the OSS to migrate the APP;
the ME platform APP instantiation migration server comprises:
a receiving module, configured to receive an instantiation termination request forwarded by the MEO and the MEPM and sent by the OSS, where the instantiation termination request includes an instantiation ID of the APP on the server;
the termination module is used for carrying out instantiation termination on the APP according to the instantiation termination request;
a sending module, configured to send an instantiation termination response to the MEPM, where the instantiation termination response is used to instruct the MEPM to send a resource deletion request to a virtualized resource manager VIM, and the resource deletion request is used to instruct the VIM to stop running an APP that has been instantiated on the server on a virtual machine and release all resources allocated to the APP that has been instantiated on the server.
5. The ME platform APP instantiation migration server of claim 4, wherein the termination module is specifically configured to:
the server terminates instantiation of the APP after first preset time is reached according to the instantiation termination request; alternatively, the first and second electrodes may be,
and the server immediately instantiates and terminates the APP according to the instantiation termination request.
6. The ME platform APP instantiation migration server of claim 4, wherein the sending module is specifically configured to:
and indicating the OSS to complete instantiation of the APP on a second ME platform through an instantiation migration request, wherein the second ME platform is a target ME platform selected by the MEO for the APP, and the server where the second ME platform is located are in the same MEPM and the same VIM management range.
7. An ME platform APP instantiation migration system, comprising: at least one processor, and a memory; it is characterized in that the preparation method is characterized in that,
the memory is for storing a computer program such that the computer program, when executed by the at least one processor, implements the ME platform APP instantiation migration method as claimed in any one of claims 1-3.
8. A computer storage medium on which a computer program is stored, said program, when executed by a processor, implementing the ME platform APP instantiation migration method as claimed in any one of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811126268.4A CN109358967B (en) | 2018-09-26 | 2018-09-26 | ME platform APP instantiation migration method and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811126268.4A CN109358967B (en) | 2018-09-26 | 2018-09-26 | ME platform APP instantiation migration method and server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109358967A CN109358967A (en) | 2019-02-19 |
| CN109358967B true CN109358967B (en) | 2021-01-05 |
Family
ID=65347798
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811126268.4A Active CN109358967B (en) | 2018-09-26 | 2018-09-26 | ME platform APP instantiation migration method and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109358967B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111722906A (en) * | 2019-03-22 | 2020-09-29 | 华为技术有限公司 | Method and device for deploying virtual machine and container |
| CN111800285B (en) * | 2019-04-08 | 2024-04-09 | 阿里巴巴集团控股有限公司 | Instance migration method and device and electronic equipment |
| CN113032111B (en) * | 2019-12-24 | 2024-04-30 | 中国电信股份有限公司 | Application migration method, device, system and computer readable storage medium |
| CN113381871B (en) * | 2020-03-10 | 2023-04-07 | 中国电信股份有限公司 | Mobile edge service arrangement method, arrangement device and mobile edge computing system |
| CN112822675B (en) * | 2021-01-11 | 2021-11-23 | 北京交通大学 | MEC environment-oriented OAuth 2.0-based single sign-on mechanism |
| CN114090200A (en) * | 2021-11-02 | 2022-02-25 | 中国联合网络通信集团有限公司 | Cross-system application instantiation migration method and device |
| CN115250227A (en) * | 2022-06-02 | 2022-10-28 | 苏州思萃工业互联网技术研究所有限公司 | Scheduling system for realizing fault migration in edge computing scene |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103795650A (en) * | 2014-01-27 | 2014-05-14 | 杭州华三通信技术有限公司 | Configuration information migration method and setting method and device of configuration information migration method and setting method |
| CN106844051A (en) * | 2017-01-19 | 2017-06-13 | 河海大学 | The loading commissions migration algorithm of optimised power consumption in a kind of edge calculations environment |
| CN107305502A (en) * | 2016-04-21 | 2017-10-31 | 中兴通讯股份有限公司 | A kind of method and apparatus of application example migration |
| WO2017206001A1 (en) * | 2016-05-28 | 2017-12-07 | 华为技术有限公司 | Method for migrating application in mobile edge system, and related device and system |
| CN108292245A (en) * | 2015-11-24 | 2018-07-17 | Nec实验室欧洲有限公司 | For managing and the method and network of layout virtual network function and network application |
| CN108509276A (en) * | 2018-03-30 | 2018-09-07 | 南京工业大学 | A kind of video task dynamic migration method in edge calculations environment |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10470192B2 (en) * | 2017-03-08 | 2019-11-05 | Zte Corporation | Traffic path change detection mechanism for mobile edge computing |
-
2018
- 2018-09-26 CN CN201811126268.4A patent/CN109358967B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103795650A (en) * | 2014-01-27 | 2014-05-14 | 杭州华三通信技术有限公司 | Configuration information migration method and setting method and device of configuration information migration method and setting method |
| CN108292245A (en) * | 2015-11-24 | 2018-07-17 | Nec实验室欧洲有限公司 | For managing and the method and network of layout virtual network function and network application |
| CN107305502A (en) * | 2016-04-21 | 2017-10-31 | 中兴通讯股份有限公司 | A kind of method and apparatus of application example migration |
| WO2017206001A1 (en) * | 2016-05-28 | 2017-12-07 | 华为技术有限公司 | Method for migrating application in mobile edge system, and related device and system |
| CN106844051A (en) * | 2017-01-19 | 2017-06-13 | 河海大学 | The loading commissions migration algorithm of optimised power consumption in a kind of edge calculations environment |
| CN108509276A (en) * | 2018-03-30 | 2018-09-07 | 南京工业大学 | A kind of video task dynamic migration method in edge calculations environment |
Non-Patent Citations (3)
| Title |
|---|
| End to End Mobility Aspects.《https://www.etsi.org/deliver/etsi_gr/MEC/001_099/018/01.01.01_60/gr_MEC018v010101p.pdf》.2017,1-52. * |
| ETSI.ETSI GR MEC 018 V1.1.1 Mobile Edge Computing (MEC) * |
| 边缘计算标准化进展与案例分析;吕华章，等；;《计算机研究与发展》;20180331;第55卷(第3期);487-511 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109358967A (en) | 2019-02-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109358967B (en) | ME platform APP instantiation migration method and server | |
| US11586461B2 (en) | Service creation and management | |
| CN109729143B (en) | Deploying a network-based cloud platform on a terminal device | |
| US9628290B2 (en) | Traffic migration acceleration for overlay virtual environments | |
| KR101507919B1 (en) | Method and apparatus for virtual desktop service | |
| EP3200393B1 (en) | Method and device for virtual network function management | |
| US20210072966A1 (en) | Method and system for service rolling-updating in a container orchestrator system | |
| EP3313023A1 (en) | Life cycle management method and apparatus | |
| EP3300298B1 (en) | Method and apparatus for switching vnf | |
| JP2019512967A (en) | Method and server for controlling relocation of MEC application | |
| US10892948B2 (en) | Creating and using service control functions | |
| KR20210020084A (en) | Alarm method and device | |
| CN111221618B (en) | Deployment method and device for containerized virtual network function | |
| US11245636B2 (en) | Distributing computing resources based on location | |
| US11907766B2 (en) | Shared enterprise cloud | |
| CN111858054A (en) | Resource scheduling system and method based on edge computing in heterogeneous environment | |
| US11159646B1 (en) | Identifying, presenting, and launching preferred applications on virtual desktop instances | |
| US20180262403A1 (en) | Monitoring dynamic quality of service based on changing user context | |
| CN108881460B (en) | Method and device for realizing unified monitoring of cloud platform | |
| CN109905258B (en) | PaaS management method, device and storage medium | |
| CN113032111B (en) | Application migration method, device, system and computer readable storage medium | |
| US9668082B2 (en) | Virtual machine based on a mobile device | |
| CN110347473B (en) | Method and device for distributing virtual machines of virtualized network elements distributed across data centers | |
| CN112889247A (en) | VNF service instantiation method and device | |
| US20180123999A1 (en) | Tracking client location using buckets |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |