WO2018153357A1 - Relocalisation d'instance d'application - Google Patents

Relocalisation d'instance d'application Download PDF

Info

Publication number
WO2018153357A1
WO2018153357A1 PCT/CN2018/077135 CN2018077135W WO2018153357A1 WO 2018153357 A1 WO2018153357 A1 WO 2018153357A1 CN 2018077135 W CN2018077135 W CN 2018077135W WO 2018153357 A1 WO2018153357 A1 WO 2018153357A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobile edge
edge host
host
switch
application instance
Prior art date
Application number
PCT/CN2018/077135
Other languages
English (en)
Inventor
David Huo
Original Assignee
Zte Corporation
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 Zte Corporation filed Critical Zte Corporation
Publication of WO2018153357A1 publication Critical patent/WO2018153357A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/18—Performing reselection for specific purposes for allowing seamless reselection, e.g. soft reselection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0019—Control or signalling for completing the hand-off for data sessions of end-to-end connection adapted for mobile IP [MIP]

Definitions

  • This document relates to mobile computing.
  • This document describes technologies, among other things, providing seamless application instance relocation in mobile communication networks.
  • a method of relocating an application instance includes a preparation phase in which an image of an application instance at a source mobile edge host is prepared by making, at a predetermined timing, a complete copy of the application instance to be transmitted to a target mobile edge host, and an adaptation phase in which a difference between a current application instance and the complete copy that was previously transmitted is measured and whether to switch bearers is decided.
  • the method may further include a switch phase in which, upon making the decision to switch, the application instance is relocated.
  • an apparatus for relocating an application instance includes a memory, a processor and a network interface, wherein the memory stores processor-executable instructions and the processor is enabled to read the instructions from the memory and implement a method of relocating an application instance between mobile edge hosts (MEHs) using the network interface for communication with other network entities.
  • the method includes a preparation phase in which an image of an application instance at a source mobile edge host is prepared by making, at a predetermined timing, a complete copy of the application instance to be transmitted to a target mobile edge host, and an adaptation phase in which a difference between a current application instance and the complete copy that was previously transmitted is measured and whether to switch bearers is decided.
  • a communication system that implements application instance relocation techniques.
  • the communication system includes a network including one or more mobile edge hosts, and a computer platform.
  • the computer platform implements a preparation phase in which an image of the application instance at a source mobile edge host is prepared by making a complete copy of the application instance for transmission to a target mobile edge host, and implements an adaptation phase in which a difference between a current application instance and the complete copy that was previously transmitted is measured and a decision is made to switch bearers.
  • FIG. 1 shows three basic scenarios for application instance relocation (AIR) .
  • FIG. 2 shows an example method of creating virtual machine (VM) overlay from base VM.
  • VM virtual machine
  • FIG. 3 is a flowchart showing an example method of implementing a procedure for application instance relocation.
  • FIG. 4 is a flowchart showing an example application instance relocation method.
  • FIG. 5 shows entities involved in application instance relocation (AIR) from source mobile edge host (S_MEH) to target mobile edge host (T_MEH) .
  • AIR application instance relocation
  • FIG. 6 shows dynamics of data amount transmitted from source mobile edge host (S_MEH) to target mobile edge host (T_MEH) during AIR.
  • FIG. 7 shows an example for consecutive segmented transmission of instance data in AIR.
  • FIG. 8A shows scenarios of attach point changes from source attach point (S_AtP) to target attach point (T_AtP)
  • FIG. 8B shows scenarios of unchanged attach point (AtP) .
  • FIG. 9 shows an example of software architecture in the virtual infrastructure.
  • FIG. 10 is a block diagram showing an example of an apparatus used to implement a disclosed technique.
  • FIG. 11 is a block diagram of an example communication system.
  • next generation 5G systems architectures for new services and new devices are continually evolving.
  • One feature offered by these architectures is to simultaneously connect through multiple interfaces for variety of radio technologies such as Wi-Fi, 4G, 5G sub 6 GHz and 5G high band or mmwave.
  • Various industry standards organizations are in the process of specifying network architecture and device functionality for next generation networks (NextGen) , which are expected to be deployed in near future and be used for many years thereafter. Therefore, it would be beneficial to specify and deploy techniques that are future-proof and meet the challenges not just in near term but many years down the road also.
  • Examples of next generation network architectures include Edge Computing (EC) , which enables cloud computing capabilities at edge layers of the network.
  • the EC attempts to leverages the storage and processing capacities of the edge layers between end devices and data centers by handling some of the requests directed to the data centers at the edge layers.
  • Example implementations of the EC include Mobile Edge Computing (MEC) and Cloudlet Computing (CC) .
  • MEC Mobile Edge Computing
  • CC Cloudlet Computing
  • a virtualized application may be migrated between mobile edge hosts (MEHs) , which are entities that contain the mobile edge platform and a virtualization infrastructure which provides compute, storage, and network resources for the mobile edge applications.
  • the virtualization infrastructure includes a data plane that executes the traffic rules received by the mobile edge platform, and routes the traffic among applications, services, DNS server/proxy, cellular network, local networks and external networks.
  • FIG. 1 shows three basic scenarios for application instance relocation (AIR) .
  • AIR application instance relocation
  • UE user equipment
  • ME mobile edge
  • the first scenario concerns AIR from a source mobile edge host S_MEH to a target mobile edge host T_MEH. This is the scenario where the majority of the resource consumed by the application instance is located on the MEH side, e.g. via server-client relation.
  • the second scenario concerns AIR from UE to a source mobile edge host S_MEH and to a target mobile edge host T_MEH. This is the scenario where the resource consumed by the application is distributed in UE and MEH, e.g. via peer to peer relation.
  • the third scenario concerns AIR from UE to the target mobile edge host T_MEH. This is the scenario where the majority of the resource consumed by the application instance is on the UE.
  • Various embodiments of the disclosed technology are applicable to the first scenario. The same technique can be applied to the second and third scenarios with appropriate additional procedures.
  • FIG. 2 shows an example method of creating virtual machine (VM) overlay from base VM.
  • a mobile device delivers a VM overlay to a cloudlet that already possesses a base VM from which this overlay was derived.
  • the delivery can form either the cloud or the storage on the mobile device.
  • the cloudlet decompresses the overlay, applies it to the base to derive a launch VM, and then creates a VM instance from it to perform offload operations on this instance.
  • This example applies to the second and third scenarios, but lacks UE mobility aspect, in particular, when UE is resource limited.
  • Various embodiments of the disclosed technology may concern the ME system specific issues, while making use of the available software technology.
  • the first scenario may be used as a basic scheme to serve a rather broader spectrum of scenarios.
  • an application is implemented in the MEH virtually on a cloudlet or a cloud.
  • a live migration of the application is to be performed with minim service interruption.
  • a connection between the source mobile edge host S_MEH and the target mobile edge host T_MEH is provided with limited capacity.
  • a mobile edge platform (MEP) is in the position to coordinate code, data and environment (CDE) for the migration.
  • AIR procedure is triggered so that the source mobile edge host S_MEH and the target mobile edge host T_MEH know each other.
  • a low service continuity can be provided by the technique of state information transfer between MEHs, in particular when assistance of connectivity provider network (CPN) is available.
  • CPN connectivity provider network
  • AIR application instance relocation
  • QoS quality of service
  • RNIS Radio Network Information Service
  • the disclosed technology is not limited thereto, and thus various implementations may be made available independently of CPN.
  • the CPN may also have problem to provide connectivity to the MEH.
  • Various embodiments of the disclosed technology may minimize such potential problems.
  • a mobile edge orchestrator works with virtualization infrastructure (VI) to accomplish on-boarding, installing and maintaining the applications running on virtual machines hosted by the MEH.
  • This software environment is referred to as “data plane” as service provided by the virtualization infrastructure hosted by the MEH.
  • the application instances are carried by the data plane.
  • capability of the data plane can be measured by computing speed, storage space, communications capacity and dependency scope.
  • An application instance relocation (AIR) implies moving information regarding these from one MEH to another MEH, i.e. image migration between clouds or cloudlets. This can take place at different levels of the software architecture, for example, via OS migration, VIM migration or application migration.
  • VM synthesis, App virtualization, and VM handoff may be used.
  • Data segments are selected based on application specific criteria and host specific environment. This is software intensive work and is subject to the virtualization infrastructure of the host system.
  • selective packaging, including compression and encryption, and scheduled transmission can be deployed to further reduce the latency and enhance customer experience, and a data transport can be made adaptive to the transport capacity and resource sharing policy. As this is application specific and host specific, it should be controlled and coordinated by MEP.
  • FIG. 3 is a flowchart for a method 300 for application instance relocation.
  • MEP performs a plurality of steps.
  • images may be generated with respect to the application instance.
  • necessary AIR data may be prepared.
  • proper scheduler may be enabled for the data transmission, and iterative delta data transmission may be provided to achieve state synchronization.
  • the application instance may be encapsulated to a VIM that is adequate for migration.
  • static information and dynamic information related to the instance may be separated.
  • the data segments may be packaged to be transmitted, with appropriate compression and encryption.
  • transmission at the source mobile edge host S_MEH and unpacking and installation at the target mobile edge host T_MEH may be scheduled.
  • URL for resources that are available at centralized location may be provided.
  • the application state and transport channel may be monitored to allow for adaptive packaging, scheduling, configuration and synchronization.
  • switch decision may be made based on multiple factors, e.g. instance transfer progress, transmission resource status and target service quality, etc.
  • One issue not explicitly discussed here is the MEH discovery procedure, and it can take place either through CPN’s assistance via the RNIS or on service level mechanism via a hyper text transfer protocol (HTTP) server implemented on designated network entity.
  • HTTP hyper text transfer protocol
  • FIG. 4 is a flowchart for a method 400 for application instance relocation.
  • the method 100 includes a preparation phase.
  • the method 400 includes an adaptation phase.
  • the method 400 includes a switching phase.
  • the preparation phase some processes are performed to prepare for graceful transmission of instance data from the source mobile edge host S_MEH to the target mobile edge host T_MEH.
  • the major challenge in this phase is to maximal transmission speed under minimal bandwidth usage.
  • synchronization of state information is performed between the source mobile edge host S_MEH and the target mobile edge host T_MEH.
  • the completion of this phase can be subject to many criteria, and the MEC operator decides which criterion is the best for the given circumstance.
  • an old bearer release and a new bearer establishment may be carried out in an optimal way and at an optimal time point. This phase may be omitted if the UE’s access point to the CPN does not need to change for the AIR.
  • FIG. 5 shows entities involved in application instance relocation (AIR) from the source mobile edge host S_MEH to the target mobile edge host T_MEH.
  • AIR application instance relocation
  • A_s (t) refers to the data associated with the instance running at the source mobile edge host S_MEH
  • A_s (t) refers to the instance to be installed and running at the target mobile edge host T_MEH.
  • A_s (t) will be removed and A_t (t) will be initiated and running at the target mobile edge host T_MEH.
  • the image of the application instance at the source mobile edge host S_MEH is copied and transmitted to the target mobile edge host T_MEH.
  • the duration of the preparation phase may vary.
  • UE is connected to the source mobile edge host S_MEH via the same channel provided by CPN.
  • a temporary complete copy of the application instance at that time is installed and ready to run at the target mobile edge host T_MEH.
  • the duration of the adaptation phase can be determined.
  • a decision to switch the MEH is made based on whether D (t) is under a given threshold or not.
  • a decision for switching MEH is made, UE starts to maintain a single channel with mobile edge systems via CPN.
  • UE In the switching phase, UE is connected to the target mobile edge host T_MEH only, but data transmission and related signaling between the source mobile edge host S_MEH and the target mobile edge host T_MEH have not been finished yet. Final copy is to be completed at the target mobile edge host T_MEH and the copy at the source mobile edge host S_MEH needs to be cleaned up.
  • mobile edge platform MEP
  • mobile edge platform manager MEPM
  • connectivity provider network CPN
  • the operational goal is to achieve maximal synchronization of two copies of the application instance.
  • the final switch decision is made with awareness that quality degradation is tolerated or accepted.
  • FIG. 6 shows dynamics of data amount transmitted from the source mobile edge host S_MEH to the target mobile edge host T_MEH during AIR.
  • the difference between images on the data plane of the target mobile edge host T_MEH and that on the data plane of the source mobile edge host S_MEH is not zero during the preparation phase and can still be larger than zero in the adaptation phase. Even in the switching phase, there can be artefacts due to CPN issues (route change, channel quality, handover failure, etc. ) . Hence, QoS degradation is expected during the entire process of AIR.
  • FIG. 7 shows an example for consecutive segmented transmission of instance data in AIR.
  • the application is divided into pieces in terms of instance resource, given as data in appropriate format:
  • i refers to data segment and k refers to application instance.
  • the application is transferred or isolated, i.e. relocated within the MEH, to a VIM of appropriate size, so that:
  • Transport channel between the target mobile edge host T_MEH and the source mobile edge host S_MEH has the capacity C, and is shared by n VIMs (or application instances) , so that:
  • Equation (6) indicates the latency of the i-th segment of k-th VIM, i.e. Vi, k, excluding the processing time on both end.
  • the scheduler at the transmitter side should be aware of all the applications being involved in live migration at any given time. That means it is necessary for MEP, to configure and control by scheduler and packaging, assisted by MEPM and MEO, so that:
  • L_k is the accumulated latency budget for application instance k.
  • a complete copy of the application instance image is transmitted from the source mobile edge host S_MEH to the target mobile edge host T_MEH.
  • This basic copy is also kept by the source mobile edge host S_MEH, referred to as A_0.
  • D is transmitted to the target mobile edge host T_MEH. Then, the same timer is reset. The delta data is used to update the installed image.
  • host switch command is sent to the target mobile edge host T_MEH, which, on receiving the command, requests CPN to establish the new bearer and release the old bearer, if applicable, and starts to serve the client of the transferred application instance and send a confirmation to the source mobile edge host S_MEH. Next, a transition to the switching phase takes place.
  • MEC is concerned primarily with the procedure of switching the role of serving entity from the source mobile edge host S_MEH to the target mobile edge host T_MEH for the client UE.
  • the responsibility for connectivity between MEH and UE lies with CPN.
  • the UE is connected to the application server. First, the UE releases the old bearer and establishes the new bearer, without changing IP address. Second, the UE releases the old bearer and establishes the new bearer, while changing the IP address. Third, the UE maintains the same single bearer and IP address. Fourth, the UE maintains the same single bearer, but changes IP address.
  • the UE can also be served with multiple IP addresses, all pointing to the same server that is relocated from the source mobile edge host S_MEH to the target mobile edge host T_MEH.
  • the UE can also be served with multiple IP addresses, all pointing to the same server that is relocated from the source mobile edge host S_MEH to the target mobile edge host T_MEH.
  • FIG. 8A shows scenarios of attach point changes from a source attach point S_AtP to a target attach point T_AtP.
  • the target mobile edge host T_MEH uses the topology information obtained from MEHM to find the IP address of the target attach point T_AtP.
  • the target mobile edge host T_MEH contacts the target attach point T_AtP and starts the mutual authentication and authorization protocols.
  • the target mobile edge host T_MEH sets up a secure connection between the target mobile edge host T_MEH and CPN at the target attach point T_AtP.
  • the target mobile edge host T_MEH On receiving a “switch command” from the source mobile edge host S_MEH, the target mobile edge host T_MEH sends a “bearer establishment” request to CPN at the target attach point T_AtP and wait for confirmation. On receiving a “bearer establishment” confirmation from CPN at the target attach point T_AtP, the target mobile edge host T_MEH starts to send application data to UE via the target attach point T_AtP. When the first transmission is acknowledged by the UE, the target mobile edge host T_MEH sends “switch confirmation” to the source mobile edge host S_MEH, so that this release the connection to a source attach point S_AtP.
  • FIG. 8B shows scenarios of unchanged attach point (AtP) .
  • the target mobile edge host T_MEH contacts the attach point AtP, using its IP address, which is obtained from the source mobile edge host S_MEH before AIR, to start mutual authentication and authorization protocols. Unless this fails, the operation continues.
  • the target mobile edge host T_MEH sets up a secure connection between the target mobile edge host T_MEH and CPN at the attach point AtP.
  • the target mobile edge host T_MEH starts to send application data to the UE via the attach point AtP.
  • the target mobile edge host T_MEH sends “switch confirmation” to the source mobile edge host S_MEH, which then release the connection to the attach point AtP.
  • data plane at the MEH exchanges information with the peer entity.
  • the information includes static part of the instance image via direct data transmission or passing ULR pointer, dependency information via direct data transmission or passing URL pointer, and rules and polices via direct data transmission or passing URL pointer.
  • the pointed server constitutes an ME system entity that has a clearly defined function, such as service continuity manger (SCM) .
  • SCM service continuity manger
  • FIG. 9 shows an example of software architecture in the virtual infrastructure.
  • the transmission side i.e., the source mobile edge host S_MEH
  • compression, encryption, VIM adaption and scheduled transmission of the VIM are needed.
  • the receiving side i.e., the target mobile edge host T_MEH
  • decompression, decryption, VIM re-adaptation, and reassemble of segment are needed.
  • General requirement on MEH includes coordination by MEP between application and data plane, whenever application instance handover is identified, control of migration procedure via MEO to assure resources are available and applicable, enforce necessary actions, e.g. adaptive compression and encryption, depending on application and transport capacity, and perform scheduling, with application aware priority setting. This implies a need for a MEC specific transport interface between MEH data planes.
  • Table 1 shows an impact of different aspect of the live migration on different layers of the virtual infrastructure:
  • Success of AIR depends on data volume, processing speed, compression ratio, transport bandwidth and tolerable quality degradation. How to balance those factors is a decision to be made by the MEC operator based on customer expectation, operation budget and maintenance complexity.
  • FIG. 10 is a block diagram of an example communication apparatus 1000.
  • the apparatus 1000 may include one or more memories 1002, one or more processors 1004 and a network interface front end 1006 that is coupled with a communication link 1008.
  • the memory 1002 may store processor-executable instructions and/or data during processor operation.
  • the processor 1004 may read instructions from the one or memories 1002 and implement a technique described in the present document.
  • the apparatus 1000 may implement various methods (e.g., the method 400) described herein.
  • FIG. 11 is a block diagram of an example communication system 1100.
  • the communication system 1100 includes a network 1102 including one or more mobile edge hosts 1104, and a computer platform 1106.
  • the computer platform may be similar to the apparatus 1000.
  • the computer platform 1106 implements a preparation phase in which an image of the application instance at a source mobile edge host is prepared by making a complete copy of the application instance for transmission to a target mobile edge host, and implements an adaptation phase in which a difference between a current application instance and the complete copy that was previously transmitted is measured and a decision is made to switch bearers.
  • the decision regarding switching the bearer is based on an absolute value of a difference between data associated with an instance running at the source mobile edge host and data associated with an instance to be installed and running at the target mobile edge host. For example, the absolute value of the difference is above the threshold, a host switch command is sent to the target mobile edge host and a request is sent to a connectivity provider network to establish a new bearer and release an old bearer.
  • the computer platform may be configured to implement a switch phase as described in the present document.
  • a method of relocating an application instance between mobile edge hosts may include a preparation phase in which an image of an application instance at a source mobile edge host is prepared by making, at a predetermined timing, a complete copy of the application instance to be transmitted to a target mobile edge host, and an adaptation phase in which a difference between a current application instance and the complete copy that was previously transmitted is measured and whether to switch bearers is decided.
  • the method of relocating an application instance between MEHs may further include a switch phase in which, upon making the decision to switch, the application instance is relocated.
  • the preparation phase may further include, for example, encapsulating the application instance to a virtualized infrastructure manager that is adequate for migration, separating static information and dynamic information related to the application instance, and selecting data segments based on application specific criteria and host specific environment and packaging the data segments to be transmitted with appropriate compression and encryption.
  • the complete copy is kept by the source mobile edge host to compare the difference between the current application instance and the previously transmitted complete copy.
  • whether to switch bearers is decided based on delta data is larger than a threshold.
  • the delta data is an absolute value of a difference between data associated with an instance running at the source mobile edge host and data associated with an instance to be installed and running at the target mobile edge host.
  • a host switch command is sent to the target mobile edge host and a request is sent to a connectivity provider network to establish a new bearer and release an old bearer.
  • the delta data is below the threshold, the delta data is transmitted to the target mobile edge host.
  • the application instance is relocated.
  • the switch phase may include completing a copy of the application at the target mobile edge host, and cleaning up the complete copy at the source mobile edge host.
  • a connectivity of a user equipment with mobile edge hosts is provided by a connectivity provider network at the same attach point for the source mobile edge host and the target mobile edge host.
  • a connectivity of a user equipment with mobile edge hosts is provided by a connectivity provider network at different attach points for the source mobile edge host and the target mobile edge host.
  • an apparatus comprising a memory, a processor and a network interface, wherein the memory stores processor-executable instructions and the processor is enabled to read the instructions from the memory and implement a method of relocating an application instance between mobile edge hosts (MEHs) using the network interface for communication with other network entities.
  • the method may include the preparation phase, the adaptation phase, and switch phase discussed above.
  • the disclosed and other embodiments, modules and the functional operations described in this document can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this document and their structural equivalents, or in combinations of one or more of them.
  • the disclosed and other embodiments can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer readable medium for execution by, or to control the operation of, data processing apparatus.
  • the computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable propagated signal, or a combination of one or more them.
  • data processing apparatus encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers.
  • the apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them.
  • a propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.
  • a computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.
  • a computer program does not necessarily correspond to a file in a file system.
  • a program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document) , in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code) .
  • a computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
  • the processes and logic flows described in this document can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output.
  • the processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit) .
  • processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer.
  • a processor will receive instructions and data from a read only memory or a random access memory or both.
  • the essential elements of a computer are a processor for performing instructions and one or more memory devices for storing instructions and data.
  • a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks.
  • mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks.
  • a computer need not have such devices.
  • Computer readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto optical disks; and CD ROM and DVD-ROM disks.
  • semiconductor memory devices e.g., EPROM, EEPROM, and flash memory devices
  • magnetic disks e.g., internal hard disks or removable disks
  • magneto optical disks e.g., CD ROM and DVD-ROM disks.
  • the processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des techniques de relocalisation d'une instance d'application, qui comprennent une phase de préparation au cours de laquelle une image d'une instance d'application au niveau d'un hôte de bord mobile source est préparée en réalisant, à une temporisation prédéterminée, une copie complète de l'instance d'application à transmettre à un hôte de bord mobile cible, et une phase d'adaptation au cours de laquelle une différence entre une instance d'application en cours et la copie complète qui a été précédemment transmise est mesurée, et il est décidé s'il convient ou pas de commuter les porteuses. Le procédé peut en outre comprendre une phase de commutation au cours de laquelle, lors de la prise de décision de commutation, l'instance d'application est relocalisée. Une expérience informatique mobile sans coupure peut être obtenue à l'aide des techniques décrites.
PCT/CN2018/077135 2017-02-24 2018-02-24 Relocalisation d'instance d'application WO2018153357A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762463527P 2017-02-24 2017-02-24
US62/463,527 2017-02-24

Publications (1)

Publication Number Publication Date
WO2018153357A1 true WO2018153357A1 (fr) 2018-08-30

Family

ID=63252404

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/077135 WO2018153357A1 (fr) 2017-02-24 2018-02-24 Relocalisation d'instance d'application

Country Status (1)

Country Link
WO (1) WO2018153357A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112445582A (zh) * 2019-08-28 2021-03-05 中国电信股份有限公司 应用迁移方法、装置和系统、计算机可读存储介质
WO2021157963A1 (fr) * 2020-02-03 2021-08-12 Samsung Electronics Co., Ltd. Procédé et appareil pour fournir des services informatiques de bord

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101803344A (zh) * 2007-09-20 2010-08-11 爱立信电话股份有限公司 通信网络中的定位符编码
US20130066980A1 (en) * 2011-09-12 2013-03-14 Microsoft Corporation Mapping raw event data to customized notifications
US9451393B1 (en) * 2012-07-23 2016-09-20 Amazon Technologies, Inc. Automated multi-party cloud connectivity provisioning
US20160373502A1 (en) * 2015-06-19 2016-12-22 Microsoft Technology Licensing, Llc Low latency application streaming using temporal frame transformation

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101803344A (zh) * 2007-09-20 2010-08-11 爱立信电话股份有限公司 通信网络中的定位符编码
US20130066980A1 (en) * 2011-09-12 2013-03-14 Microsoft Corporation Mapping raw event data to customized notifications
US9451393B1 (en) * 2012-07-23 2016-09-20 Amazon Technologies, Inc. Automated multi-party cloud connectivity provisioning
US20160373502A1 (en) * 2015-06-19 2016-12-22 Microsoft Technology Licensing, Llc Low latency application streaming using temporal frame transformation

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA NETWORKS: "pCR for TR 28.802 Add a use case to support management of Service Hosting Environment", 3GPP TSG SA WG5 (TELECOM MANAGEMENT) MEETING #110 S 5-166187, 18 November 2016 (2016-11-18), XP051186329 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112445582A (zh) * 2019-08-28 2021-03-05 中国电信股份有限公司 应用迁移方法、装置和系统、计算机可读存储介质
WO2021157963A1 (fr) * 2020-02-03 2021-08-12 Samsung Electronics Co., Ltd. Procédé et appareil pour fournir des services informatiques de bord
US11445039B2 (en) 2020-02-03 2022-09-13 Samsung Electronics Co., Ltd. Method and apparatus for providing edge computing services

Similar Documents

Publication Publication Date Title
EP3732846B1 (fr) Contrôle de qualité de service (qos) dans l'informatique de périphérie mobile (mec)
US11477846B2 (en) Application mobility mechanism for edge computing
Taleb et al. " Anything as a service" for 5G mobile systems
US11070442B2 (en) Method and network for managing and orchestrating virtual network functions and network applications
US10693791B2 (en) Software-defined network-based method and system for implementing content distribution network
US20210281473A1 (en) Management Services for 5G Networks and Network Functions
US10299171B2 (en) First service network node, a second service network node and methods relating to handling of a service session
US11743953B2 (en) Distributed user plane functions for radio-based networks
US11184228B2 (en) Configuration control for network
US11888701B1 (en) Self-healing and resiliency in radio-based networks using a community model
CN111406437B (zh) 多路径数据通信
WO2018153357A1 (fr) Relocalisation d'instance d'application
Santos et al. Towards enabling RAN as a service-The extensible virtualisation layer
EP3804276A1 (fr) Migration de service
EP3652980B1 (fr) Ancrage virtuel dans des réseaux mobiles sans ancrage
US20240114070A1 (en) Distributed and synchronized network core for radio-based networks
US20230388890A1 (en) Handover of a communication session
WO2023133598A1 (fr) Rapport de bande passante sensible au service dynamique et messagerie de transport à faible latence de mobilité

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18757470

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18757470

Country of ref document: EP

Kind code of ref document: A1