CN114090200A - Cross-system application instantiation migration method and device - Google Patents

Cross-system application instantiation migration method and device Download PDF

Info

Publication number
CN114090200A
CN114090200A CN202111289410.9A CN202111289410A CN114090200A CN 114090200 A CN114090200 A CN 114090200A CN 202111289410 A CN202111289410 A CN 202111289410A CN 114090200 A CN114090200 A CN 114090200A
Authority
CN
China
Prior art keywords
instantiation
target
application program
target application
systems
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.)
Pending
Application number
CN202111289410.9A
Other languages
Chinese (zh)
Inventor
黄倩
黄蓉
杨剑键
赫罡
高功应
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China United Network Communications Group Co Ltd
Original Assignee
China United Network Communications Group Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by China United Network Communications Group Co Ltd filed Critical China United Network Communications Group Co Ltd
Priority to CN202111289410.9A priority Critical patent/CN114090200A/en
Publication of CN114090200A publication Critical patent/CN114090200A/en
Pending legal-status Critical Current

Links

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/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/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
    • 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
    • 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/5083—Techniques for rebalancing the load in a distributed system
    • G06F9/5088—Techniques for rebalancing the load in a distributed system involving task migration

Abstract

The invention discloses a method and a device for performing instantiation migration of an application program across a system, relates to the technical field of communication, and is used for realizing the APP instantiation migration across an MEP platform under an MEC system and improving the efficiency of the APP instantiation migration and rapid deployment, and comprises the following steps: under the condition that a target application program is instantiated on a first system, when the state corresponding to the target application program meets a preset condition, the target application program initiates a request for performing instantiation migration across systems to the first system; the method comprises the steps that a first system sends a request for performing instantiation migration across systems to a target control system; the target control system corresponds to a plurality of systems, the first system and the second system are all systems in the plurality of systems, and the target control system is used for acquiring parameter information of the plurality of systems and managing the plurality of systems; the target control system sends a request for performing instantiation migration across the systems to the second system, and instantiates the target application program on the second system.

Description

Cross-system application instantiation migration method and device
Technical Field
The invention relates to the technical field of communication, in particular to a method and a device for performing instantiation migration of an application program across systems.
Background
A Mobile Edge Computing (MEC) platform can provide an open-source, open and friendly deployment environment for a third-party APP, and an application APP can also utilize various platform capabilities provided by the MEC platform to provide a better service for a user to the maximum extent. Instantiation of the APP on the MEC platform is a premise for acquiring various platform capabilities by the APP. Considering that the APP side has a need of performing instantiation migration across the MEP platform in the situations of coping with mobility environment, MEC platform failure and the like, especially when the cross-MEP platform does not belong to the same MEC system, the migration of the application needs to be completed through interconnection between the MEC systems.
In the prior art scheme, the number of the current MEC platforms is large, the overall architecture of each MEC platform is different, the existing application program is tightly coupled with the platforms and executed in a chimney mode, so that the APP is difficult to dynamically migrate among different MEC platforms, the cloud and the edge cannot cooperate, the adaptation work difficulty of the edge application developer for developing and deploying the edge application to the MEC platform is large, the edge application APP freely migrates, the rapid deployment efficiency is low, and the development cost is high.
Disclosure of Invention
The invention provides a method and a device for performing instantiation migration of an application program across a system, which are used for realizing the APP instantiation migration across an MEP platform under an MEC system and improving the APP instantiation migration and rapid deployment efficiency.
In order to achieve the purpose, the invention adopts the following technical scheme:
in a first aspect, a method for migrating instantiation of an application program across systems is provided, and the method includes: under the condition that a target application program is instantiated on a first system, when the state corresponding to the target application program meets a preset condition, the target application program initiates a request for performing instantiation migration across systems to the first system; the preset conditions include at least one of the following: the terminal corresponding to the target application program moves from the coverage range of the first system to the coverage range corresponding to the second system, and the first system is overloaded; the method comprises the steps that a first system sends a request for performing instantiation migration across systems to a target control system; the target control system corresponds to a plurality of systems, the first system and the second system are all systems in the plurality of systems, and the target control system is used for acquiring parameter information of the plurality of systems and managing the plurality of systems; the target control system sends a request for performing instantiation migration across the systems to the second system, and instantiates the target application program on the second system.
In one possible implementation, the target application program initiates a request for an instantiated migration across systems to a first system, including: the target application program sends a request for carrying out instantiation migration across the systems to a first MEP included in the first system; the cross-system instantiation migration request comprises target information, and the target information is used for indicating the tendency selection of a target application program to a second system; the first MEP sends a request for performing instantiation migration across the systems to a first OSS included in the first system through a first MEPM and a first MEO included in the first system.
In one possible implementation, the sending, by the first system, a request for instantiation migration across systems to the target control system includes: the first OSS sends a request for performing instantiation migration across the systems to the target control system.
In one possible implementation, the sending, by the target control system, a request for instantiation migration across systems to a second system, and instantiating a target application on the second system, includes: the target control system initiates a request for establishing the instantiation of the target application program to a second MEO included in a second system through a second OSS included in the second system based on a request for performing instantiation migration across the systems; the second MEO determines a second MEP from a plurality of MEPs included in the second system and sends a request for establishing the instantiation of the target application program to the second MEP; the second MEP instantiates and configures a target rule for the target application program, and activates the target rule under the condition that the target application program is instantiated to normally run; the target rule includes at least one of: traffic rules, DNS rules.
In one possible implementation, after activating the target rule in the case that the target application instantiates normal operation, the method further includes: the second MEP sends a configuration response to a second MEPM included in the second system; the second MEPM sends an instantiation completion response and target resource information to the second MEO according to the configuration response; the target resource information is VIM included in the second system, and is resource allocation information determined according to the resource allocation request sent by the second MEPM; the second MEO sends a completion instantiation response and the target application instantiation ID to the second OSS.
In one possible implementation, after instantiating the target application on the second system, the method further includes: the second OSS included in the second system sends a completion instantiation response and a target application instantiation ID to the target control system; the target control system sends a target application program instantiation termination request to the first system under the condition of receiving the instantiation completion response and the target application program instantiation ID; the target application program instantiation termination request comprises a target application program instantiation ID; the first system authenticates the instantiation termination request of the target application program, and determines whether the instantiation of the target application program exists in the first system according to the instantiation ID of the target application program; and under the condition that the target application program instantiation exists in the first system, terminating the target application program instantiation, and releasing resources occupied by the target application program instantiation.
In a second aspect, an apparatus for migrating instantiation of an application program across systems is provided, and the apparatus for migrating instantiation of an application program across systems comprises: a transmitting unit and a processing unit; the sending unit is used for initiating a request for cross-system instantiation migration to the first system by the target application program when the state corresponding to the target application program meets the preset condition under the condition that the target application program is instantiated on the first system; the preset conditions include at least one of the following: the terminal corresponding to the target application program moves from the coverage range of the first system to the coverage range corresponding to the second system, and the first system is overloaded; the sending unit is also used for sending a request for performing instantiation migration across the systems to the target control system by the first system; the target control system corresponds to a plurality of systems, the first system and the second system are all systems in the plurality of systems, and the target control system is used for acquiring parameter information of the plurality of systems and managing the plurality of systems; the sending unit is also used for sending a request for performing instantiation migration across the systems to the second system by the target control system; a processing unit to instantiate the target application on the second system.
In a third aspect, there is provided a computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by a computer, cause the computer to perform a cross-system application instantiation migration method as in the first aspect.
In a fourth aspect, an electronic device includes: a processor and a memory; wherein the memory is used for storing one or more programs, the one or more programs comprising computer executable instructions, and the processor executes the computer executable instructions stored by the memory when the electronic device is running, so as to make the electronic device execute the cross-system application instantiation migration method according to the first aspect.
The invention provides a method and a device for performing instantiation migration of an application program across systems, which are applied to a scene of performing instantiation migration of the application program across systems. Further, the first system sends a request for performing instantiation migration across the systems to a target control system for acquiring parameter information of the systems and managing the systems. Therefore, the target control system sends the request for performing the instantiation migration of the cross-system to the second system, and instantiates the target application program on the second system, so as to achieve the purpose of performing the instantiation migration of the application program on the cross-system, thereby improving the efficiency of the instantiation migration and the rapid deployment of the application program.
Drawings
FIG. 1 is a first structural diagram of a system for performing application instantiation and migration across systems according to an embodiment of the present invention;
fig. 2 is a first flowchart illustrating a method for migrating an application instantiation across systems according to an embodiment of the present invention;
fig. 3 is a flowchart illustrating a method for migrating an application instantiation across systems according to an embodiment of the present invention;
FIG. 4 is a structural diagram of a system for performing application instantiation and migration across systems according to an embodiment of the present invention;
fig. 5 is a flowchart illustrating a third method for migrating an application instantiation across systems according to an embodiment of the present invention;
fig. 6 is a flowchart illustrating a method for migrating an application instantiation across systems according to an embodiment of the present invention;
fig. 7 is a flowchart illustrating a method for migrating an application instantiation across systems according to an embodiment of the present invention;
fig. 8 is a flowchart illustrating a sixth method for migrating an application instantiation across systems according to an embodiment of the present invention;
FIG. 9 is a schematic structural diagram of an apparatus for migrating an application instantiation across systems according to an embodiment of the present invention;
fig. 10 is a first schematic structural diagram of an electronic device according to an embodiment of the present invention;
fig. 11 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be described below with reference to the drawings in the embodiments of the present invention.
In the description of the present invention, "/" means "or" unless otherwise specified, for example, a/B may mean a or B. "and/or" herein is merely an association describing an associated object, and means that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. Further, "at least one" or "a plurality" means two or more. The terms "first", "second", and the like do not necessarily limit the number and execution order, and the terms "first", "second", and the like do not necessarily limit the difference.
The method for performing instantiation migration of the application program across the systems, provided by the embodiment of the invention, can be suitable for performing instantiation migration of the application program across the systems. Fig. 1 shows a schematic structural diagram of the cross-system application instantiation migration system. As shown in FIG. 1, a cross-system application instantiation migration system 20 comprises: the first MEC system 21, the second MEC system 22, and the target control system 23, in the actual application process, the cross-system application instantiation migration system 20 may further include a plurality of other MEC systems. The first MEC system 21 is connected to a target control system 23, and the second MEC system 22 is connected to the target control system 23. The first MEC system 21, the second MEC system 22, and the target control system 23 may be connected in a wired manner or in a wireless manner, which is not limited in the embodiment of the present invention.
The cross-system application instantiation migration system 20 may be used for the internet of things, and the cross-system application instantiation migration system 20 may include hardware such as a plurality of Central Processing Units (CPUs), a plurality of memories, and a storage device storing a plurality of operating systems.
The first MEC system 21 and the second MEC system 22 may be used in the internet of things, and are used to provide an open-source, open, and friendly deployment environment for the third-party application program, and complete instantiation of the application program.
The target control system 23 may be used for the internet of things, and is configured to connect with the first MEC system 21, the second MEC system 22, and other MEC systems, so as to obtain parameter information of a plurality of MEC systems and manage the plurality of MEC systems, and control the application to perform instantiation migration of the application across the systems.
It should be noted that the first MEC system 21, the second MEC system 22, and the target control system 23 may be independent devices or may be integrated into the same device, and the present invention is not limited in this respect.
When the first MEC system 21, the second MEC system 22, and the target control system 23 are integrated in the same equipment, the communication mode among the first MEC system 21, the second MEC system 22, and the target control system 23 is communication among modules inside the equipment. In this case, the communication flow between the two is the same as "the communication flow between the first MEC system 21, the second MEC system 22, and the target control system 23 when they are independent of each other".
In the following embodiments provided by the present invention, the present invention is described by taking as an example that the first MEC system 21, the second MEC system 22, and the target control system 23 are independently provided from each other.
The following describes a method for migrating an application instantiation across systems according to an embodiment of the present invention with reference to the drawings.
As shown in fig. 2, a method for performing instantiation migration of an application across systems according to an embodiment of the present invention is applied to a terminal including a plurality of memories and a plurality of CPUs, and includes S201 to S203:
s201, under the condition that the target application program is instantiated on the first system, when the state corresponding to the target application program meets a preset condition, the target application program initiates a request for performing instantiation migration across systems to the first system.
Wherein the preset condition comprises at least one of the following conditions: and the terminal corresponding to the target application program moves from the coverage range of the first system to the coverage range corresponding to the second system, and the first system is overloaded.
As a possible implementation manner, when the state corresponding to the target application program meets a preset condition, the target application program proposes a request for performing a cross-system MEC platform switching, and feeds the request back to the first system.
As a possible implementation manner, the target application is currently instantiated on the first system, and when the terminal corresponding to the target application moves out of the coverage of the first system (i.e., the system corresponding to the current area), the target application needs to be instantiated and migrated across the systems.
As a possible implementation manner, when the load of the first system corresponding to the currently instantiated target application is overloaded, instantiation migration can be performed across systems so as to migrate to other systems for instantiation.
It will be appreciated that the conditions that trigger the target application to initiate a request for an instantiated migration across systems include: the terminal moves from the coverage of the first system to the coverage of other systems (second systems) (the first system and the second system are in different MEPM and VIM management ranges), and application instantiation is required to be carried out on the second system in order to ensure that the terminal can still continuously access the target application program; load balancing: when the performance of the current edge node (first system) is not satisfied (such as a fault) due to some conditions, the edge node (second system) also needs to be reselected for instantiation migration of the edge application (target application).
It should be noted that different telecommunication operators are usually deployed with different MEC systems, and the same operator may also be deployed with heterogeneous MEC systems due to historical reasons such as service development.
S202, the first system sends a request for performing instantiation migration across the systems to the target control system.
The target control system corresponds to a plurality of systems, the first system and the second system are all systems in the plurality of systems, and the target control system is used for acquiring parameter information of the plurality of systems and managing the plurality of systems.
As a possible implementation manner, the multiple systems corresponding to the target control system may be an MEC system or an edge computing system.
As one possible implementation, the target control system may include a plurality of MEC systems (e.g., a plurality of edge computing systems of different operators), and the target control system connected to each edge computing system may also be referred to as an "edge Federation" (MEC Federation system).
As a possible implementation, the target control system may obtain information for a plurality of different edge computing systems and manage them, thereby enabling edge node switching across the MEC system.
As a possible implementation manner, when a terminal moves across an MEC host service area, user context migration and/or application intelligent relocation need to be supported, a need to change the MEC platform for re-instantiation may occur on the APP side, but service continuity is ensured, and the APP side can interrupt an existing service and re-instantiate on a second system.
S203, the target control system sends the request for performing instantiation migration across the systems to the second system, and instantiates the target application program on the second system.
As a possible implementation manner, the second system is a choice of tendency of the target application program to perform on various different edge systems according to the situation of the target application program.
As one possible implementation, "edge system selection tendency information" may include at least one of: designated availability area (system) as a preference, decides on which edge cloud (system) to deploy an application, or which mep (mec host) to provide resources available for reservation; information of an operator supported by the terminal accessing the target application (for example, a network roaming agreement needs to be signed between two edge computing systems to determine whether the terminal is allowed to use its edge node, where the operator is the Qos of the local area network); and accessing the processing capacity information of hardware resources (such as CPU, memory and storage) required by the target application program.
As one possible implementation, the target application may be caused to be instantiated on the second system after the second system receives the request to perform the instantiation migration across the systems.
In one design, to implement that a target application initiates a request for performing instantiation migration across systems to a first system, as shown in fig. 3, in the method for performing instantiation migration of an application across systems according to an embodiment of the present invention, the "request for initiating instantiation migration across systems to a first system by a target application" in S201 may specifically include the following S301 to S302:
s301, the target application program sends a request for carrying out instantiation migration across the systems to a first MEP included in the first system.
The request for performing instantiation migration across the systems comprises target information, and the target information is used for indicating the tendency selection of a target application program to the second system.
As one possible implementation, the target application first sends a request for migration across instantiations of the system to a first MEP included in the first system.
Illustratively, as shown in fig. 4, a cross-system application instantiation migration system 30 provided for the embodiment of the present invention includes a first system 31, a second system 32, and a target control system 33. Wherein, the first system 31 comprises a first OSS311, a first MEO312, a first MEPM313 and a first MEC host 314; included in the second system 32 are a second OSS321, a second MEO322, a second MEPM323, and a second MEC host 324.
S302, the first MEP sends a request for performing instantiation migration across the systems to a first OSS included in the first system through a first MEPM and a first MEO included in the first system.
As one possible implementation, after the first MEP receives the request for the instantiation migration across the systems, the first MEP sends the request for the instantiation migration across the systems to the first MEPM.
As one possible implementation, after the first MEPM receives the request for the instantiation migration across the systems, the first MEPM sends the request for the instantiation migration across the systems to the first MEO.
As one possible implementation, after the first MEO receives the request for the instantiation migration across the systems, the first MEO sends the request for the instantiation migration across the systems to the first OSS.
In one design, in order to implement that the first system sends a request for performing instantiation migration across systems to the target control system, as shown in fig. 5, in the method for performing instantiation migration of an application across systems according to an embodiment of the present invention, the step S202 may specifically include the following step S2021:
s2021, the first OSS sends a request for performing instantiation migration across the systems to the target control system.
As a possible implementation, the request for the instantiation migration across the systems may be sent to the target control system by the first OSS included in the first system.
In one design, in order to implement that a target control system sends a request for performing instantiation migration across systems to a second system and instantiates a target application on the second system, as shown in fig. 6, an application instantiation migration method across systems according to an embodiment of the present invention may specifically include the following steps S401 to S403:
s401, the target control system initiates a request for establishing the instantiation of the target application program to a second MEO included in a second system through a second OSS included in the second system based on a request for performing instantiation migration across the systems.
As one possible implementation, after the target control system receives the request for instantiation migration across systems, the target control system may send a request to establish instantiation of the target application to a second OSS included in a second system.
As a possible implementation manner, after the second OSS included in the second system receives the request for establishing the instantiation of the target application, the second OSS initiates the request for establishing the instantiation of the target application to the second MEO included in the second system.
As one possible implementation, the target control system may obtain and manage information for a plurality of different edge computing systems.
As a possible implementation manner, the target control system may obtain at least one of the following information corresponding to multiple systems: identifiers (such as longitude and latitude) of an area where the system is deployed, computing resources (such as provided resource directories, cpu, memory, storage and the like) provided by the system, special computer resources (additional resource directories, such as graphics processing unit gpu, visual processing unit vpu, neural processing unit npu and field programmable gate array fpga) provided by the system, network QoS parameters supported by a system home operator, such as delay, jitter, maximum value of packet loss rate and the like.
As a possible implementation, the first MEP included in the first system and the second MEP included in the enemy system belong to different MEPM management categories.
S402, the second MEO determines a second MEP from a plurality of MEPs included in the second system, and sends a request for establishing the instantiation of the target application program to the second MEP.
As a possible implementation manner, the second system includes a plurality of MEPs (i.e., MEC hosts), and after the second MEO receives the request for instantiation of the target application, the second MEP may be determined from the plurality of MEPs, and then the request for establishing instantiation of the target application is sent to the second MEP.
And S403, the second MEP instantiates and configures a target rule for the target application program, and activates the target rule under the condition that the target application program instantiates and runs normally.
Wherein the target rule comprises at least one of: traffic rules, DNS rules.
As one possible implementation, the second MEP configures the traffic rules and DNS rules to instantiate the target application. The second MEP also needs to wait until the target application instantiates normal operation before activating the traffic rules and DNS rule policies.
As one possible implementation, after the target application instantiates normal operation, the second MEP provides the available service information to the target application.
In one design, to implement the resource information configuration for instantiation of the target application, as shown in fig. 7, the method for migrating instantiation of an application across systems according to the embodiment of the present invention may further include, after the step S403, the following steps S501 to S503:
s501, the second MEP sends a configuration response to the second MEPM included in the second system.
As a possible implementation, after the second MEP activates the target rule, a configuration response may be sent to the second MEPM included in the second system.
S502, the second MEPM sends the instantiation completion response and the target resource information to the second MEO according to the configuration response.
The target resource information is the VIM included in the second system, and the resource allocation information is determined according to the resource allocation request sent by the second MEPM.
As a possible implementation, the second MEPM sends an instantiation response to the second MEO. The second MEPM is to send target resource information allocated in the instantiation of the target application to the second MEO as well.
As a possible implementation manner, the second MEPM sends a resource allocation request to the VIM, where the resource allocation request is used to request a target resource, and the resource allocation request includes: computing resources, storage resources, network resources, and other special resources, etc.
As a possible implementation, the VIM allocates resources according to the request sent by the second MEPM. If the target application image is complete and available, the VIM loads the target application image package into the virtual machine, running the virtual machine and the target application instantiation at the same time.
As a possible implementation, the VIM also sends a resource allocation response to the second MEPM, and further the second MEPM sends a configuration request to the second MEPM. The configuration request message also includes the configured traffic rules and DNS rules.
S503, the second MEO sends the instantiation completion response and the instantiation ID of the target application program to the second OSS.
As a possible implementation, the second MEO sends an instantiation response of the target application to the second OSS, and returns the result of the instantiation process to the second OSS. The second MEO also feeds back the target application instantiation ID to the second OSS.
In one design, to implement the instantiation termination of the target application on the first system, as shown in fig. 8, the method for migrating the instantiation of the application across systems according to the embodiment of the present invention may further include, after the step S203, the following steps S601 to S604:
s601, the second OSS included in the second system sends a completion instantiation response and a target application instantiation ID to the target control system.
As a possible implementation, the second system sends the target application instantiation response to the target control system through the second OSS, and the second OSS also feeds back the target application instantiation ID to the target control system. Thereby completing the process of instantiating the target application at the second system.
S602, the target control system sends a target application program instantiation termination request to the first system under the condition of receiving the instantiation completion response and the target application program instantiation ID.
And the target application program instantiation termination request comprises a target application program instantiation ID.
As a possible implementation manner, after the target application completes the instantiation process in the second system, the instantiation of the target application in the first system is not terminated, so that the instantiation of the target application in the first system needs to be terminated.
As a possible implementation manner, the target control system sends a target application instantiation termination request to the first OSS of the first system, so as to send the termination request to the first MEO through the first OSS for terminating the instantiation of the target application, where the termination request includes the target application instantiation ID.
S603, the first system authenticates the instantiation termination request of the target application program, and determines whether the instantiation of the target application program exists in the first system according to the instantiation ID of the target application program.
As a possible implementation, the first MEO authenticates the termination request while verifying whether the instantiation (i.e., the target application is instantiated at the first system) exists.
S604, under the condition that the target application program instantiation exists in the first system, the target application program instantiation is stopped, and resources occupied by the target application program instantiation are released.
As a possible implementation, in case it is determined that there is an instantiation of the target application in the first system, the first MEO sends an instantiation termination request to the first MEPM, while configuring the termination of the instantiation of the target application.
Further, the first MEPM forwards the target application instantiation termination request to the first MEP, so that the first MEP terminates instantiation of the target application.
Further, after the instantiation of the target application is terminated, the first MEP sends a target application instantiation termination response to the first MEPM, so that the first MEPM sends a resource deletion request to the VIM to terminate the running of the virtual machine and release all occupied resources. The VIM also sends a resource deletion response to the first MEPM while the VIM releases all resources allocated to the instantiation of the target application, such that the first MEPM sends a target application instantiation termination response to the first MEO, such that the first MEO sends a target application instantiation termination response to the first OSS, and the first MEO also feeds back the target application instantiation ID to the first OSS.
Further, the first OSS sends a target application instantiation termination response to the target control system, and the first OSS also feeds back the target application instantiation ID to the target control system, so that instantiation of the target application on the first system is terminated and all relevant resources are released. And meanwhile, the APP is instantiated on the second system to execute the related service.
The invention provides a method and a device for performing instantiation migration of an application program across systems, which are applied to a scene of performing instantiation migration of the application program across systems. Further, the first system sends a request for performing instantiation migration across the systems to a target control system for acquiring parameter information of the systems and managing the systems. Therefore, the target control system sends the request for performing the instantiation migration of the cross-system to the second system, and instantiates the target application program on the second system, so as to achieve the purpose of performing the instantiation migration of the application program on the cross-system, thereby improving the efficiency of the instantiation migration and the rapid deployment of the application program.
The scheme provided by the embodiment of the invention is mainly introduced from the perspective of a method. To implement the above functions, it includes hardware structures and/or software modules for performing the respective functions. Those of skill in the art will readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The embodiment of the present invention may perform the division of the functional modules for the application instantiation migration device across systems according to the above method examples, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. Optionally, the division of the modules in the embodiment of the present invention is schematic, and is only a logic function division, and there may be another division manner in actual implementation.
Fig. 9 is a schematic structural diagram of an apparatus for migrating an application instantiation across systems according to an embodiment of the present invention. As shown in fig. 9, a cross-system application instantiation migration device 40 is used to implement APP instantiation migration across an MEP platform under an MEC system, and improve efficiency of APP instantiation migration and rapid deployment, for example, is used to execute a cross-system application instantiation migration method shown in fig. 2. The device 40 for migrating the instantiation of the application program across the systems comprises: a sending unit 401 and a processing unit 402.
A sending unit 401, configured to, when a target application is instantiated on a first system, and a state corresponding to the target application meets a preset condition, initiate, by the target application, a request for performing instantiation migration across systems to the first system; the preset conditions include at least one of the following: and the terminal corresponding to the target application program moves from the coverage range of the first system to the coverage range corresponding to the second system, and the first system is overloaded.
The sending unit 401 is further configured to send, by the first system, a request for performing instantiation migration across systems to the target control system; the target control system corresponds to a plurality of systems, the first system and the second system are all systems in the plurality of systems, and the target control system is used for acquiring parameter information of the plurality of systems and managing the plurality of systems.
The sending unit 401 is further configured to send, by the target control system, a request for performing instantiation migration across systems to the second system.
A processing unit 402 for instantiating the target application on the second system.
Optionally, in the apparatus 40 for performing instantiation migration of an application across systems according to an embodiment of the present invention, the sending unit 401 is specifically configured to send, to a first MEP included in a first system, a request for performing instantiation migration across systems by a target application; the request for the instantiation migration across the systems comprises target information, and the target information is used for indicating the tendency selection of the target application program to the second system.
The sending unit 401 is further configured to send, by the first MEP, a request for performing instantiation migration across the systems to the first OSS included in the first system through the first MEPM and the first MEO included in the first system.
Optionally, in the apparatus 40 for performing instantiation migration of an application across systems according to an embodiment of the present invention, the sending unit 401 is specifically configured to send, by the first OSS, a request for performing instantiation migration across systems to the target control system.
Optionally, in the apparatus 40 for performing instantiation migration of an application across systems according to an embodiment of the present invention, the sending unit 401 is specifically configured to initiate, by a second OSS included in a second system, a request for establishing instantiation of a target application to a second MEO included in the second system based on a request for performing instantiation migration across systems by the target control system.
The sending unit 401 is further configured to determine, by the second MEO, a second MEP from a plurality of MEPs included in the second system, and send a request for establishing an instantiation of the target application to the second MEP.
The processing unit 402 is further configured to configure a target rule for the instantiation of the target application by the second MEP, and activate the target rule when the instantiation of the target application runs normally; the target rule includes at least one of: traffic rules, DNS rules.
Optionally, in the apparatus 40 for instantiating an application program across systems according to the embodiment of the present invention, the sending unit 401 is further configured to send a configuration response to the second MEPM included in the second system.
The sending unit 401 is further configured to send, by the second MEPM, an instantiation completion response and target resource information to the second MEO according to the configuration response; the target resource information is the VIM included in the second system, and the resource allocation information is determined according to the resource configuration request sent by the second MEPM.
The sending unit 401 is further configured to send, by the second MEO, the instantiation completion response and the instantiation ID of the target application to the second OSS.
Optionally, in the apparatus 40 for performing instantiation and migration of an application across systems according to an embodiment of the present invention, the sending unit 401 is further configured to send, to the target control system, an instantiation completion response and an instantiation ID of the target application by a second OSS included in the second system.
The sending unit 401 is further configured to send, by the target control system, a target application instantiation termination request to the first system when receiving the instantiation completion response and the target application instantiation ID; the target application instantiation termination request includes a target application instantiation ID.
The processing unit 402 is further configured to authenticate the target application instantiation termination request by the first system, and determine whether there is a target application instantiation in the first system according to the target application instantiation ID.
The processing unit 402 is further configured to terminate the instantiation of the target application program and release resources occupied by the instantiation of the target application program, if the instantiation of the target application program exists in the first system.
In the case of implementing the functions of the integrated modules in the form of hardware, the embodiment of the present invention provides another possible structural schematic diagram of the electronic device related to the above embodiment. As shown in fig. 10, an electronic device 60 for improving efficiency of traffic cleansing and traffic reinjection when traffic is attacked, such as for executing a cross-system application instantiation migration method as shown in fig. 2. The electronic device 60 includes a processor 601, a memory 602, and a bus 603. The processor 601 and the memory 602 may be connected by a bus 603.
The processor 601 is a control center of the communication apparatus, and may be a single processor or a collective term for a plurality of processing elements. For example, the processor 601 may be a Central Processing Unit (CPU), other general-purpose processors, or the like. Wherein a general purpose processor may be a microprocessor or any conventional processor or the like.
For one embodiment, processor 601 may include one or more CPUs, such as CPU 0 and CPU 1 shown in FIG. 10.
The memory 602 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that may store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that may store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
As a possible implementation, the memory 602 may be present separately from the processor 601, and the memory 602 may be connected to the processor 601 via a bus 603 for storing instructions or program code. When the processor 601 calls and executes the instructions or program codes stored in the memory 602, the method for performing instantiation migration of the application program across the systems provided by the embodiment of the present invention can be implemented.
In another possible implementation, the memory 602 may also be integrated with the processor 601.
The bus 603 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 10, but this is not intended to represent only one bus or type of bus.
It is to be noted that the structure shown in fig. 10 does not constitute a limitation of the electronic apparatus 60. In addition to the components shown in FIG. 10, the electronic device 60 may include more or fewer components than shown, or some components may be combined, or a different arrangement of components.
As an example, in connection with fig. 9, the functions implemented by the sending unit 401 and the processing unit 402 in the electronic device are the same as the functions of the processor 601 in fig. 10.
Optionally, as shown in fig. 10, the electronic device 60 provided in the embodiment of the present invention may further include a communication interface 604.
A communication interface 604 for connecting with other devices via a communication network. The communication network may be an ethernet network, a radio access network, a Wireless Local Area Network (WLAN), etc. The communication interface 604 may include a receiving unit for receiving data and a transmitting unit for transmitting data.
In one design, in the electronic device provided by the embodiment of the present invention, the communication interface may be further integrated in the processor.
Fig. 11 shows another hardware configuration of the electronic apparatus in the embodiment of the present invention. As shown in fig. 11, the electronic device 70 may include a processor 701, a communication interface 702, a memory 703, and a bus 704. The processor 701 is coupled to a communication interface 702 and a memory 703.
The functions of the processor 701 may refer to the description of the processor 601 above. The processor 701 also has a memory function, and the function of the memory 602 can be referred to.
The communication interface 702 is used to provide data to the processor 701. The communication interface 702 may be an internal interface of the communication apparatus, or may be an external interface of the communication apparatus (corresponding to the communication interface 604).
It should be noted that the configuration shown in fig. 11 does not constitute a limitation of the electronic device 70, and the electronic device 70 may include more or less components than those shown in fig. 11, or combine some components, or arrange different components, in addition to the components shown in fig. 11.
Through the above description of the embodiments, it is clear for a person skilled in the art that, for convenience and simplicity of description, only the division of the above functional units is illustrated. In practical applications, the above function allocation can be performed by different functional units according to needs, that is, the internal structure of the device is divided into different functional units to perform all or part of the above described functions. For the specific working processes of the system, the apparatus and the unit described above, reference may be made to the corresponding processes in the foregoing method embodiments, and details are not described here again.
The embodiment of the present invention further provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instructions are executed by a computer, the computer executes each step in the method flow shown in the above method embodiment.
Embodiments of the present invention provide a computer program product comprising instructions which, when run on a computer, cause the computer to perform a method for application instantiation migration across systems in the above method embodiments.
The computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, and a hard disk. Random Access Memory (RAM), Read-Only Memory (ROM), Erasable Programmable Read-Only Memory (EPROM), registers, a hard disk, an optical fiber, a portable Compact disk Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any other form of computer-readable storage medium, in any suitable combination, or as appropriate in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an Application Specific Integrated Circuit (ASIC). In embodiments of the invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
Since the electronic device, the computer-readable storage medium, and the computer program product in the embodiments of the present invention may be applied to the method described above, for technical effects obtained by the method, reference may also be made to the method embodiments described above, and details of the embodiments of the present invention are not repeated herein.
The above description is only an embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions within the technical scope of the present invention are intended to be covered by the scope of the present invention.

Claims (14)

1. A method for migrating instantiation of an application program across systems, the method comprising:
under the condition that a target application program is instantiated on a first system, when the state corresponding to the target application program meets a preset condition, the target application program initiates a request for performing instantiation migration across systems to the first system; the preset condition comprises at least one of the following conditions: the terminal corresponding to the target application program moves from the coverage range of the first system to the coverage range corresponding to the second system, and the first system is overloaded;
the first system sends the request for performing instantiation migration across the systems to a target control system; the target control system corresponds to a plurality of systems, the first system and the second system are both systems of the plurality of systems, and the target control system is used for acquiring parameter information of the plurality of systems and managing the plurality of systems;
and the target control system sends the cross-system instantiation migration request to the second system, and instantiates the target application program on the second system.
2. The method of claim 1, wherein the target application initiating a request to the first system for an instantiated migration across systems comprises:
the target application program sends the request for performing instantiation migration across the systems to a first MEP included in the first system; the cross-system instantiation migration request comprises target information, and the target information is used for indicating the tendency selection of the target application program to the second system;
and the first MEP sends the request for performing instantiation migration across the systems to a first OSS included in the first system through a first MEPM and a first MEO included in the first system.
3. The method of claim 2, wherein the first system sending the request for the cross-system instantiation migration to a target control system comprises:
and the first OSS sends the request for performing instantiation migration across the systems to the target control system.
4. The method of claim 3, wherein the target control system sending the request for the cross-system instantiation migration to the second system and instantiating the target application on the second system comprises:
the target control system initiates a request for establishing instantiation of the target application program to a second MEO included in the second system through a second OSS included in the second system based on the request for performing instantiation migration across the systems;
the second MEO determines a second MEP from a plurality of MEPs included in the second system and sends the request for establishing the instantiation of the target application program to the second MEP;
the second MEP configures a target rule for the instantiation of the target application program, and activates the target rule under the condition that the instantiation of the target application program normally runs; the target rule includes at least one of: traffic rules, DNS rules.
5. The method of claim 4, wherein after activating the target rule in the case that the target application instantiates normal operation, the method further comprises:
the second MEP sending a configuration response to a second MEPM included in the second system;
the second MEPM sends an instantiation completion response and target resource information to the second MEO according to the configuration response; the target resource information is VIM included in the second system, and resource allocation information determined according to the resource allocation request sent by the second MEPM;
the second MEO sends the instantiation completion response and the instantiation ID of the target application program to the second OSS.
6. The method of any of claims 1-5, wherein after instantiating the target application on the second system, the method further comprises:
a second OSS included by the second system sends an instantiation completion response and a target application instantiation ID to the target control system;
the target control system sends the instantiation termination request of the target application program to the first system under the condition of receiving the instantiation completion response and the instantiation ID of the target application program; the instantiation termination request of the target application program comprises the instantiation ID of the target application program;
the first system authenticates the instantiation termination request of the target application program, and determines whether the instantiation of the target application program exists in the first system according to the instantiation ID of the target application program;
and under the condition that the instantiation of the target application program exists in the first system, terminating the instantiation of the target application program and releasing resources occupied by the instantiation of the target application program.
7. An apparatus for migrating instantiation of an application program across systems, comprising: a transmitting unit and a processing unit;
the sending unit is used for initiating a request for performing instantiation migration across systems to a first system by a target application program when a state corresponding to the target application program meets a preset condition under the condition that the target application program performs instantiation on the first system; the preset condition comprises at least one of the following conditions: the terminal corresponding to the target application program moves from the coverage range of the first system to the coverage range corresponding to the second system, and the first system is overloaded;
the sending unit is further configured to send, by the first system, the request for performing instantiation migration across systems to a target control system; the target control system corresponds to a plurality of systems, the first system and the second system are both systems of the plurality of systems, and the target control system is used for acquiring parameter information of the plurality of systems and managing the plurality of systems;
the sending unit is further configured to send, by the target control system, the request for performing instantiation migration across systems to the second system;
the processing unit is configured to instantiate the target application on the second system.
8. The apparatus according to claim 7, wherein the sending unit is specifically configured to send, by the target application, the request for performing instantiation migration across the systems to the first MEP included in the first system; the cross-system instantiation migration request comprises target information, and the target information is used for indicating the tendency selection of the target application program to the second system;
the sending unit is further configured to send the request for performing instantiation migration across the systems to a first OSS included in the first system through a first MEPM and a first MEO included in the first system by the first MEP.
9. The device according to claim 8, wherein the sending unit is specifically configured to send the request for performing instantiation migration of the application across systems to the target control system by the first OSS.
10. The device according to claim 9, wherein the sending unit is specifically configured to initiate, by the target control system, a request for establishing instantiation of the target application to a second MEO included in the second system through a second OSS included in the second system based on the request for performing instantiation migration across systems;
the sending unit is further configured to determine, by the second MEO, a second MEP from a plurality of MEPs included in the second system, and send the request for establishing the instantiation of the target application to the second MEP;
the processing unit is further configured to configure a target rule for the instantiation of the target application program by the second MEP, and activate the target rule when the instantiation of the target application program normally runs; the target rule includes at least one of: traffic rules, DNS rules.
11. The apparatus for migrating instantiation of an application program across systems according to claim 10, wherein said sending unit is further configured to send a configuration response to a second MEPM included in said second system by said second MEP;
the sending unit is further configured to send, by the second MEPM, an instantiation completion response and target resource information to the second MEO according to the configuration response; the target resource information is VIM included in the second system, and resource allocation information determined according to the resource allocation request sent by the second MEPM;
the sending unit is further configured to send, by the second MEO, the instantiation completion response and the instantiation ID of the target application to the second OSS.
12. The device for migrating instantiation of application programs across systems according to any one of claims 7-11, wherein the sending unit is further configured to send a completion instantiation response and an instantiation ID of a target application program to the target control system by a second OSS included in the second system;
the sending unit is further used for sending the instantiation termination request of the target application program to the first system by the target control system under the condition of receiving the instantiation completion response and the instantiation ID of the target application program; the instantiation termination request of the target application program comprises the instantiation ID of the target application program;
the processing unit is further configured to authenticate the instantiation termination request of the target application program by the first system, and determine whether the instantiation of the target application program exists in the first system according to the instantiation ID of the target application program;
the processing unit is further configured to terminate the instantiation of the target application program and release resources occupied by the instantiation of the target application program when the instantiation of the target application program exists in the first system.
13. A computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by a computer, cause the computer to perform a cross-system application instantiation migration method as claimed in any one of claims 1 to 6.
14. An electronic device, comprising: a processor and a memory; wherein the memory is configured to store one or more programs, the one or more programs including computer executable instructions that, when executed by the electronic device, are executed by the processor to cause the electronic device to perform a cross-system application instantiation migration method as recited in any one of claims 1-6.
CN202111289410.9A 2021-11-02 2021-11-02 Cross-system application instantiation migration method and device Pending CN114090200A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111289410.9A CN114090200A (en) 2021-11-02 2021-11-02 Cross-system application instantiation migration method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111289410.9A CN114090200A (en) 2021-11-02 2021-11-02 Cross-system application instantiation migration method and device

Publications (1)

Publication Number Publication Date
CN114090200A true CN114090200A (en) 2022-02-25

Family

ID=80298629

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111289410.9A Pending CN114090200A (en) 2021-11-02 2021-11-02 Cross-system application instantiation migration method and device

Country Status (1)

Country Link
CN (1) CN114090200A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114827172A (en) * 2022-03-30 2022-07-29 阿里云计算有限公司 Data migration method and device based on Internet of things and electronic equipment

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130198564A1 (en) * 2012-01-27 2013-08-01 Empire Technology Development, Llc Parameterized dynamic model for cloud migration
CN108781229A (en) * 2016-05-10 2018-11-09 索尼移动通讯有限公司 Control the method and server of the reorientation of MEC applications
CN109076357A (en) * 2016-05-28 2018-12-21 华为技术有限公司 Application method, relevant device and system are migrated in mobile limbic system
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
CN109691147A (en) * 2016-08-30 2019-04-26 索尼移动通讯有限公司 The repositioning of mobile edge calculations service
CN109802934A (en) * 2018-12-13 2019-05-24 中国电子科技网络信息安全有限公司 A kind of MEC system based on container cloud platform
CN111132253A (en) * 2019-12-31 2020-05-08 北京邮电大学 Joint mobility management method for communication switching and service migration
CN112788086A (en) * 2019-11-11 2021-05-11 中国移动通信有限公司研究院 Mobile edge computing application data migration method and device and core network node
CN113032111A (en) * 2019-12-24 2021-06-25 中国电信股份有限公司 Application program migration method, device, system and computer readable storage medium
WO2021158018A1 (en) * 2020-02-03 2021-08-12 Samsung Electronics Co., Ltd. Method and apparatus for improving a multi-access edge computing (mec) network

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130198564A1 (en) * 2012-01-27 2013-08-01 Empire Technology Development, Llc Parameterized dynamic model for cloud migration
CN108781229A (en) * 2016-05-10 2018-11-09 索尼移动通讯有限公司 Control the method and server of the reorientation of MEC applications
CN109076357A (en) * 2016-05-28 2018-12-21 华为技术有限公司 Application method, relevant device and system are migrated in mobile limbic system
CN109691147A (en) * 2016-08-30 2019-04-26 索尼移动通讯有限公司 The repositioning of mobile edge calculations service
CN109429284A (en) * 2017-08-31 2019-03-05 华为技术有限公司 Example switching method and relevant apparatus
CN109358967A (en) * 2018-09-26 2019-02-19 中国联合网络通信集团有限公司 A kind of ME platform APP instantiation moving method and server
CN109802934A (en) * 2018-12-13 2019-05-24 中国电子科技网络信息安全有限公司 A kind of MEC system based on container cloud platform
CN112788086A (en) * 2019-11-11 2021-05-11 中国移动通信有限公司研究院 Mobile edge computing application data migration method and device and core network node
CN113032111A (en) * 2019-12-24 2021-06-25 中国电信股份有限公司 Application program migration method, device, system and computer readable storage medium
CN111132253A (en) * 2019-12-31 2020-05-08 北京邮电大学 Joint mobility management method for communication switching and service migration
WO2021158018A1 (en) * 2020-02-03 2021-08-12 Samsung Electronics Co., Ltd. Method and apparatus for improving a multi-access edge computing (mec) network

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
黄倩 等: "边缘应用迁移和服务连续性保障研究", 《推动网络演进 促进应用创新——5G网络创新研讨会（2021）论文集》, 31 October 2021 (2021-10-31), pages 1 - 3 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114827172A (en) * 2022-03-30 2022-07-29 阿里云计算有限公司 Data migration method and device based on Internet of things and electronic equipment

Similar Documents

Publication Publication Date Title
CN109548082B (en) Service redirection method and device
EP3068157B1 (en) Network management
CN105335229B (en) Scheduling method and device of service resources
US8589920B2 (en) Resource allocation
CN109586938B (en) Method and device for generating instance service topology
KR20170056350A (en) NFV(Network Function Virtualization) resource requirement verifier
US11818576B2 (en) Systems and methods for low latency cloud computing for mobile applications
CN108628660B (en) Virtual machine capacity expansion and reduction method and virtual management equipment
EP3742785A1 (en) Session management method and device
CN107251486A (en) A kind of method for extending linkage, apparatus and system
EP3203686B1 (en) Virtualized network function interworking
JP6924895B2 (en) Battery virtualization
EP3860176A1 (en) Method, apparatus, and system for obtaining capability information of terminal
CN105429938A (en) Resource allocation method and device
CN106576260B (en) Strategy coordination method and device in NFV system
EP4280685A1 (en) Information transmission method and device thereof
WO2023064018A1 (en) Efficiency of routing traffic to an edge compute server at the far edge of a cellular network
KR20200135520A (en) Access method, IoT platform, application device, service device
CN108228350B (en) Resource allocation method and device
CN114090200A (en) Cross-system application instantiation migration method and device
CN112243036B (en) Data processing method and device for PaaS service, equipment and storage medium
US10848377B2 (en) Access point instantiation of a mesh network
CN114172951B (en) MEC sharing method, communication device and storage medium
US7669202B1 (en) Resource management
EP3376711A1 (en) Management method and device for managing instruction transmission and automatic vnf scaling function

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