WO2019011408A1 - Transfert d'application mec - Google Patents

Transfert d'application mec Download PDF

Info

Publication number
WO2019011408A1
WO2019011408A1 PCT/EP2017/067277 EP2017067277W WO2019011408A1 WO 2019011408 A1 WO2019011408 A1 WO 2019011408A1 EP 2017067277 W EP2017067277 W EP 2017067277W WO 2019011408 A1 WO2019011408 A1 WO 2019011408A1
Authority
WO
WIPO (PCT)
Prior art keywords
edge computing
mobile edge
base station
target
terminal
Prior art date
Application number
PCT/EP2017/067277
Other languages
English (en)
Inventor
Juergen Goerge
Jens Andersen
Marcel GABOR
Volker Mendisch
Original Assignee
Nokia Solutions And Networks Oy
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 Nokia Solutions And Networks Oy filed Critical Nokia Solutions And Networks Oy
Priority to PCT/EP2017/067277 priority Critical patent/WO2019011408A1/fr
Publication of WO2019011408A1 publication Critical patent/WO2019011408A1/fr

Links

Classifications

    • 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/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00835—Determination of neighbour cell lists
    • H04W36/008357—Determination of target cell based on access point [AP] properties, e.g. AP service capabilities
    • 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/0016—Hand-off preparation specially adapted for end-to-end data sessions
    • 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/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0061—Transmission or use of information for re-establishing the radio link of neighbour cell information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/249—Reselection being triggered by specific parameters according to timing information

Definitions

  • the present invention relates to an apparatus, a method, and a computer program product related to MEC.
  • the present invention may be related to handover of a MEC application.
  • Cellular mobile networks provide voice and data connections for the mobile user equipment (“UE").
  • the cellular network comprises many base stations ("BTS", e.g. eNB in LTE). Each of these base stations is able to maintain connections to the UE in a limited coverage area defined by the "cells" of the base station.
  • BTS base stations
  • Each of these base stations is able to maintain connections to the UE in a limited coverage area defined by the "cells" of the base station.
  • some of the base stations may be associated with one or more Mobile Edge Computing platforms ("MEC”) to provide computing resources closer to the UE.
  • MEC Mobile Edge Computing platforms
  • This enables local services that are processed locally at site. It avoids the need to transfer all data through the core network in order to reach the service provider. This can be used e.g. to reduce the latency of data transmissions, to cache content locally that shall be transmitted to the UE in a specific area, or to perform calculations that are relevant for specific UE at the location of the base station.
  • MEC Mobile Edge Computing platforms
  • the services that are provided locally by the MEC applications of the MEC platform associated with a specific BTS do not move with the moving UE through the cellular network. If the UE moves to another base station and gets connected to cells of the target base station, then it loses the services provided by the application running in the MEC platform. If the MEC platform associated with the target BTS also runs this service, then the UE has to re-register for this service. If the MEC platform associated with the target BTS does not run this specific service in its MEC platform, then the UE is not able to use this service. For certain services provided by the mobile edge platform this behaviour is reasonable and desirable, e.g. if the service intentionally is provided to a certain area only. E.g. a service to provide video sequences to a sports event might be restricted to the cells that are covering the stadium. If the UE moves out from the stadium then it shall not receive the video anymore.
  • the mobile edge computing resources shall be used to provide services for use cases like autonomous driving, low latency remote control, or data collection for moving platforms, then it is required that, from UE point of view, the serving MEC application running in the MEC platform associated with the source BTS is able to move together with the moving UE to the target BTS, as shown in Fig. 1 .
  • ETSI MEC-0018 E2E Mobility v2.4 introduces a ,,/WE Orchestrator" as central entity to find the neighboring target MEC platforms. This approach has two disadvantages:
  • ⁇ It is a kind of anachronism to base the concept of distributed computing on a central entity.
  • ETSI MEC-0018 E2E Mobility v2.4 "ETSI MEC foresees that the application can react to such handover events" and "ETSI MEC foresees that the application can react to such handover events by application-specific means, or, if the optional SmartRelocation feature is supported, that the mobile edge system relocates the application instance serving the UE to the target host'.
  • This approach has several potential issues:
  • Mobility of MEC is mainly reactive, MEC follows the radio
  • MEC builds a mainly independent mobility management, although mobility of UE and mobility of MEC services are tightly related to each other.
  • an apparatus comprising at least one processor, at least one memory including computer program code, and the at least one processor, with the at least one memory and the computer program code, being arranged to cause the apparatus to at least perform inquiring, from a source mobile edge computing platform, a usage information for a terminal indicating a mobile edge computing application of the source mobile edge computing platform used by the terminal; requesting, from a target base station, a support information indicating if the mobile edge computing application is supported at the target base station; deciding on a handover of the terminal to the target base station based on the usage information and the support information.
  • an apparatus comprising at least one processor, at least one memory including computer program code, and the at least one processor, with the at least one memory and the computer program code, being arranged to cause the apparatus to at least perform monitoring if a request to provide a usage information for a terminal indicating a mobile edge computing application of a source mobile edge computing platform used by the terminal is received from a source base station; determining if the terminal uses the mobile edge computing application; preparing the usage information based on a result of the determining; providing the usage information to the source base station in response to the received request.
  • an apparatus comprising at least one processor, at least one memory including computer program code, and the at least one processor, with the at least one memory and the computer program code, being arranged to cause the apparatus to at least perform monitoring if a request to provide a support information is received from a source base station, wherein the support information indicates if a mobile edge computing application is supported at a target base station; requesting to provide a capability information from a target mobile edge computing platform, wherein the capability information indicates if the target mobile edge computing platform supports the mobile edge computing application; preparing the support information based on the capability information; providing the support information to the source base station in response to the received request.
  • an apparatus comprising at least one processor, at least one memory including computer program code, and the at least one processor, with the at least one memory and the computer program code, being arranged to cause the apparatus to at least perform monitoring if a request to provide a capability information is received from a target base station, wherein the capability information indicates if a target mobile edge computing platform supports a first mobile edge computing application; determining if the target mobile edge computing platform supports the first mobile edge computing application; preparing the capability information based on a result of the determining; providing the capability information to the target base station in response to the received request.
  • an apparatus comprising at least one processor, at least one memory including computer program code, and the at least one processor, with the at least one memory and the computer program code, being arranged to cause the apparatus to at least perform providing a list of one or more target base stations from a source base station to a mobile edge computing platform, wherein a terminal connected to the source base station may handover to each of the one or more target base stations with a probability larger than a predefined threshold.
  • an apparatus comprising at least one processor, at least one memory including computer program code, and the at least one processor, with the at least one memory and the computer program code, being arranged to cause the apparatus to at least perform monitoring if a list of one or more target base stations is received by a source mobile edge computing platform; determining one or more target mobile edge computing platforms, wherein each of the target mobile edge computing platforms corresponds to respective at least one of the one or more target base stations if the list is received; checking, if the list is received, if a terminal uses a mobile edge computing application of the source mobile edge computing platform; providing at least one of an application context and a user context of the application used by the terminal to each of the target mobile edge computing platforms if the terminal uses the mobile edge computing application.
  • a method comprising inquiring, from a source mobile edge computing platform, a usage information for a terminal indicating a mobile edge computing application of the source mobile edge computing platform used by the terminal; requesting, from a target base station, a support information indicating if the mobile edge computing application is supported at the target base station; deciding on a handover of the terminal to the target base station based on the usage information and the support information.
  • a method comprising monitoring if a request to provide a usage information for a terminal indicating a mobile edge computing application of a source mobile edge computing platform used by the terminal is received from a source base station; determining if the terminal uses the mobile edge computing application; preparing the usage information based on a result of the determining; providing the usage information to the source base station in response to the received request.
  • a ninth aspect of the invention there is provided a method, comprising monitoring if a request to provide a support information is received from a source base station, wherein the support information indicates if a mobile edge computing application is supported at a target base station; requesting to provide a capability information from a target mobile edge computing platform, wherein the capability information indicates if the target mobile edge computing platform supports the mobile edge computing application; preparing the support information based on the capability information; providing the support information to the source base station in response to the received request.
  • a method comprising monitoring if a request to provide a capability information is received from a target base station, wherein the capability information indicates if a target mobile edge computing platform supports a first mobile edge computing application; determining if the target mobile edge computing platform supports the first mobile edge computing application; preparing the capability information based on a result of the determining; providing the capability information to the target base station in response to the received request.
  • a method comprising providing a list of one or more target base stations from a source base station to a mobile edge computing platform, wherein a terminal connected to the source base station may handover to each of the one or more target base stations with a probability larger than a predefined threshold.
  • a method comprising monitoring if a list of one or more target base stations is received by a source mobile edge computing platform; determining one or more target mobile edge computing platforms, wherein each of the target mobile edge computing platforms corresponds to respective at least one of the one or more target base stations if the list is received; checking, if the list is received, if a terminal uses a mobile edge computing application of the source mobile edge computing platform; providing at least one of an application context and a user context of the application used by the terminal to each of the target mobile edge computing platforms if the terminal uses the mobile edge computing application.
  • Each of the methods of the seventh to twelfth aspect may be a method of mobile edge computing.
  • a computer program product comprising a set of instructions which, when executed on an apparatus, is configured to cause the apparatus to carry out the method any of the seventh to twelfth aspects.
  • the computer program product may be embodied as a computer-readable medium or directly loadable into a computer.
  • Fig. 1 shows a principle of handover of a UE from a source BTS with an associated MEC platform running a MEC application to a target BTS with its associated MEC platform running the MEC application;
  • Fig. 2 shows a method to evaluate the status of the MEC system (according to some embodiments of the invention
  • Fig. 3 shows a method to prepare the handover of the MEC application according to some embodiments of the invention
  • Fig. 4 shows a situation where a handover of the MEC application fails
  • Fig. 5 shows a method to prepare the handover of the MEC application including pre-emption according to some embodiments of the invention
  • Fig. 6 comprising Figs. 6a and 6b shows a method to execute the handover of the MEC application according to some embodiments of the invention
  • Fig. 7 shows an apparatus according to an embodiment of the invention
  • Fig. 8 shows a method according to an embodiment of the invention
  • Fig. 9 shows an apparatus according to an embodiment of the invention.
  • Fig. 10 shows a method according to an embodiment of the invention
  • Fig. 1 1 shows an apparatus according to an embodiment of the invention
  • Fig. 12 shows a method according to an embodiment of the invention
  • Fig. 13 shows an apparatus according to an embodiment of the invention
  • Fig. 14 shows a method according to an embodiment of the invention
  • Fig. 15 shows an apparatus according to an embodiment of the invention
  • Fig. 16 shows a method according to an embodiment of the invention
  • Fig. 17 shows an apparatus according to an embodiment of the invention
  • Fig. 18 shows a method according to an embodiment of the invention.
  • Fig. 19 shows an apparatus according to an embodiment of the invention. Detailed description of certain embodiments
  • the handover of the UE from the instance of the MEC application running on the MEC platform associated with the source BTS to the instance of the MEC application running on the MEC platform associated with the target BTS may be handled transparently by the same, distributed, de-central mechanisms as the handover of voice calls and data traffic. That is, the mobility management of the MEC applications is integrated in the mobility management of the mobile network.
  • these handovers are distinguished as “handover of the UE (terminal)” related to the conventional 3GPP handover of a terminal from a source cell to a target cell, typically reacting on radio conditions, and “handover of the MEC application” related to handing over the context (user context and/or application context) of the application for the terminal from one MEC platform to another MEC platform.
  • the source BTS may collect for each UE the status of the associated MEC Platform and MEC Applications from each potential target BTS to consider the status of the potential target MEC Platform and MEC Applications for the decision on target and time of handover. For example, the source BTS may decide not to handover the UE to a specific target BTS not supporting the MEC application used by the UE on the source BTS, even though the radio conditions for the UE on the specific target BTS may be better than those on other target BTSs.
  • the terms "base station” or "BTS” may not include the “pure” base station but may include some control portion, too.
  • the terms “base station” or “BTS” may include not only the BTS and NodeB (or the radio control portion thereof), respectively, but also a portion of or the entire associated BSC and RNC, respectively.
  • the portion may be in particular the portion responsible for handover control.
  • the terms “base station” or “BTS” may comprise an entire eNB or a portion thereof (in particular: radio control portion and handover control portion).
  • Fig. 2 shows a method to evaluate the status of the MEC system (MEC platform and MEC application) according to some embodiments of the invention. This method may be performed while the UE is still attached to the source BTS (before handover). The following steps are performed:
  • the source BTS interrogates from its associated MEC platform the MEC applications (services), that a given UE uses ("usage information").
  • the MEC Platform replies the services that the UE uses
  • the source BTS interrogates from its neighbouring BTSs, whether their associated MEC platforms are able to run the requested MEC applications (i.e. the MEC applications used by the UE). For example, the source BTS may interrogate the neighbouring BTS via X2 interface or via S1 interface.
  • the neighbouring BTSs query their associated MEC platforms whether they are able to run the requested MEC application (in other words: whether or not they support the requested MEC applications).
  • the MEC platforms deliver the information ("capability information") to their associated BTSs
  • the neighbouring BTSs deliver the information ("support information") to the source
  • the neighbouring BTS may filter the capability information from the MEC platform such that the support information to the source BTS indicates a smaller capability than the capability information.
  • the neighbouring BTS may combine capability information from plural MEC platforms to which the neighbouring BTS is associated into the support information.
  • the source BTS evaluates the status of the MEC system to determine target and time of a handover. For example, the source BTS may exclude a BTS not supporting a MEC application used by the
  • the source BTS may decide that UEs not using a certain MEC application preferably handover to a target BTS not supporting this MEC application, thus leaving capacity on MEC platforms providing this MEC application for UEs using this MEC application.
  • the source BTS informs its associated MEC Platform about the handover.
  • the currently proposed ETSI MEC RNIS interface supports this step.
  • the interface between BTS and associated MEC platform (RNIS) and the interface between source and target BTS may be enhanced the following way:
  • ETSI MEC already has proposed an interface between the control plane of the BTS and the MEC platform (Radio Network Information Service, RNIS).
  • the MEC platform shall be enabled to collect from the BTS information regarding handovers.
  • the MEC platform and MEC applications shall use this information to manage the mobility of MEC applications. This is sufficient for the concept of "MEC follows radio".
  • the interface may provide information in the opposite direction. I.e. BTS collects information about the status and availability of the MEC platform and its applications.
  • a source BTS requests information from its associated MEC platform about the applications that a given UE is using from the MEC platform.
  • a potential target BTS requests information about the capabilities of its associated MEC platform ("target MEC platform) and the status of requested applications. For example:
  • the source BTS collects various information from each potential target BTS to evaluate potential targets and to plan the handover.
  • these interfaces may be enhanced to enable the source BTS to interrogate information about the MEC platform associated with the neighbouring BTS via standardized interfaces.
  • the eNB are using the X2 interface (3GPP TS 36.423) and S1 interface (3GPP TS 36.413) to control the handover.
  • the eNB may use these interfaces to query information about the capabilities and status of the target, e.g. to perform inter-eNB load balancing or inter-eNB coordinated Power Saving.
  • the interfaces between the BTSs may be enhanced. For example:
  • the source eNB interrogates from the potential target eNBs certain information about the status of these MEC application(s) that UEs in the source cells are using
  • the target eNB must be able to send information about the capabilities of the associated MEC platform and its status.
  • source and target BTS may query the information case by case for each UE that shall perform handover.
  • the BTS may maintain a map about the status of the MEC platforms of neighbouring BTS. BTS might embed this status transfer in the regular messages about the cell state and cell configurations. BTS might collect this information as part of the "automatic neighbour relationship" establishment.
  • the interfaces between different radio technologies may be enhanced, e.g. the interface for "Radio Information Management” (RIM) between LTE and UTRAN.
  • RIM Radio Information Management
  • Newly defined interfaces between the BTS as e.g. for 5G may be designed to offer the corresponding functions right from the start
  • the source BTS considers the status of the MEC system associated with the target BTS for its handover decision. That is, the algorithms in the BTS that evaluate the environment of the UE, that determine the target cells, and that decide on the handover may consider the status of the MEC computing system for its decisions on handover. I.e., the source BTS may consider which services the UE uses in the MEC platform associated with the source BTS, and whether these services are available at the target. In addition, it may consider which QoS the target offers for this service, etc. These algorithms intentionally are not standardized by 3GPP.
  • the source BTS evaluates the measurements reports from the UE, the availability of the links to the target cells, the load of the target cells, capabilities of the UE, and/or several other quantities to select the best target and time for a handover.
  • the source BTS has no access to any status of the MEC system and thus is not able to consider the status of MEC for the handover decision.
  • the MEC system defines its own mobility management, where the mobility of MEC is planned (and according to the architecture has to) follow the decision of the BTS.
  • the BTS initiates a handover towards a target that is not associated to any MEC Platform at all.
  • MEC is not able to do any corrective action and the UE will be dropped from service.
  • the BTS may optimize the handover to guarantee a seamless service by MEC Applications across handovers. This will improve the robustness of handovers within the MEC system, because the BTS might avoid handovers to BTS that are not able to provide the requested MEC Application with the requested level of service.
  • ANR finding neighbour relations automatically
  • the preparation of the handover within the MEC system may be part of the regular preparation of the handover in the mobile network.
  • the handover of the MEC application may be controlled by the BTS.
  • it may be handled via the existing inter-BTS connections within the mobile network (e.g. in LTE: S1 or X2 interface).
  • Fig. 3 shows a method to prepare the handover of the MEC application according to some embodiments of the invention. This method may be performed while the UE is still attached to the source BTS (before handover). The following steps are performed:
  • the source BTS defines a proper target for handover for a given UE.
  • MEC platform is able to instantiate these MEC applications, that the UE requires. This step may be performed as described in section "Evaluation of status of MEC system" hereinabove.
  • the source BTS may inform the target BTS about a planned handover of an UE that is using a specific MEC application.
  • the target BTS may request its associated MEC platform ("target MEC platform") to prepare the requested application.
  • the target MEC platform may prepare the requested MEC applications. For example:
  • the MEC platform may instantiate it
  • the MEC platform may load it from a repository.
  • Target MEC platform may inform the associated BTS about the result of preparation ("provision success information").
  • the target BTS may inform the source BTS about the result of the preparation
  • preparation success information may be the same as the provision success information.
  • the target BTS may filter some positive results from the provision success information such that the preparation success information has less positive results.
  • the target BTS may combine provision success information from plural associated MEC platforms into a single preparation success information.
  • the source BTS may optionally inform its associated MEC Platform about the successful preparation of a handover.
  • source BTS may also inform its associated MEC Platform ("source MEC platform") on the planned handover in order to prepare the source MEC platform on the handover. E.g. such information may be provided in step 2.
  • target MEC platform may inform the source MEC platform accordingly, e.g. in step 5. For example, target MEC platform may inform MEC platform on handover preparation via a link through the MEC system (not via the base stations).
  • step 5 and/or step 6 may be omitted. For example, they may be omitted if the target BTS and/or source BTS trust that the preparation will be successful.
  • step 1 (defining a proper target for handover able to instantiate these MEC applications required by the UE) may be omitted. For example, it may be omitted if all MEC platforms of the network provide the same MEC applications and surely have sufficient capacity. As another example, step 1 may be omitted if a certain rate of service drops at handover is acceptable.
  • step 1 is omitted, some embodiments of the invention provide: Source eNB or component thereof:
  • Apparatus comprising at least one processor, at least one memory including computer program code, and the at least one processor, with the at least one memory and the computer program code, being arranged to cause the apparatus to at least perform
  • a usage information indicating if a terminal uses a mobile edge computing application of the source mobile edge computing platform
  • the preparation request informs the target base station that it is decided that the terminal is handed over to the target base station and that the terminal uses the mobile edge computing application.
  • Target BTS or component thereof:
  • Apparatus comprising at least one processor, at least one memory including computer program code, and the at least one processor, with the at least one memory and the computer program code, being arranged to cause the apparatus to at least perform
  • Target MEC platform or component thereof Apparatus, comprising at least one processor, at least one memory including computer program code, and the at least one processor, with the at least one memory and the computer program code, being arranged to cause the apparatus to at least perform
  • the preparation of the handover of the MEC application may be closely linked to the handover of the UE.
  • the target BTS may prepare radio resources for the terminal upon receipt of the preparation request from the source BTS. If the provision success information is not received from the MEC platform, it may dismantle the radio resources for the terminal. Alternatively, the target BTS may not prepare the radio resources for the terminal until the provision success information is received from the MEC platform.
  • the interface between BTS and MEC platform (RNIS) as well as the interface between the BTS (in LTE: X2 and/or S1 ) is enhanced.
  • the enhanced interface allows the (target) BTS to request from the associated MEC platform to instantiate a set of requested MEC applications. As reply the MEC platform may inform the BTS about the result of the instantiation.
  • the BTS may request from the associated MEC platform to instantiate a set of MEC applications.
  • the MEC platform may inform the BTS about the result of the instantiation of MEC applications.
  • the interfaces that source BTS and target BTS are using to prepare and control the handover may be enhanced to enable the target BTS to prepare its associated MEC platform via standardized interfaces and procedures as follows:
  • the source BTS requests from the target BTS to instantiate a set of MEC applications in its associated MEC platform.
  • the target BTS informs to the source BTS about the result of the instantiation of MEC applications in the associated MEC platform.
  • the source BTS prepares the handover to a target BTS without considering the status and capabilities of the related MEC system.
  • the BTS might prepare a handover which from radio and core perspective would be fine, but that from MEC perspective would fail.
  • the robustness of the handover preparation will be further increased, especially because these links usually are closely monitored.
  • the operability of the overall system would be improved, because the mobility within the MEC system would be based on the same planned, managed, and secured links as the mobility within the mobile network.
  • the mobile network may handover the UE into the target cell, but the UE will not be able to use the service by the corresponding MEC Application. This might cause severe problems for mission critical applications like semi-autonomous (remote-controlled) driving, tele-medicine, or any other mission-critical communication.
  • Fig. 4 Such a situation is depicted in Fig. 4 as an example, where the UE uses MEC application 1 at the source BTS.
  • the target MEC platform at the target BTS is exhausted by other MEC applications such that the UE, if handed over to the target BTS, cannot use the MEC application 1 (at least not with a required QoS).
  • the preparation of the handover of a high priority MEC application may pre-empt low priority MEC applications running on the target MEC platform.
  • a continuous service with a sufficient QoS may be guaranteed for the high priority application at handover.
  • An example of a typical high priority application is a Tsunami or Earthquake warning application.
  • Fig. 5 shows a method to prepare the handover of the MEC application including preemption according to some embodiments of the invention. This method may be performed while the UE is still attached to the source BTS (before handover). The following steps are performed:
  • Source MEC Platform informs the target MEC Platform that the UE requires a high- priority MEC Application.
  • the target MEC Platform instantiates the high-priority MEC Application. To do so, the MEC Platform might drop lower-priority MEC Applications, if necessary.
  • the target MEC Platform informs the source MEC Platform about the result of the pre-emption request. This step may be omitted, e.g. if the source MEC platform trusts on the success of the pre-emption at the target MEC platform.
  • the target MEC Platform may inform the source MEC platform and/or the source BTS thereon.
  • the source BTS may consider if another target BTS able to provide, with its associated MEC platform, the high-priority MEC application is available for the handover.
  • the source MEC platform may determine the priority of each application according to a predetermined table. The priority may depend not only on the application but also on the UE (e.g. the type of terminal). In these embodiments, the Source MEC platform has to inform target MEC platform on the priority, preferably via the source BTS and the target BTS.
  • the target MEC platform may determine the priority of each ME application, e.g. based on a predefined table. In these cases, the priority need not to be transmitted from the source MEC platform to the target MEC platform. Instead, the target MEC platform determines the priority when a request to prepare for a handover of the MEC application is received. In these embodiments, pre-emption may always be active, or it may be activated based on a request e.g. from the source MEC platform or the source BTS. In some embodiments, the priority may be determined at both the source MEC platform and the target MEC platform.
  • the predefined tables in the source MEC platform and the target MEC platform may be the same or different from each other.
  • a prevalence may be decided based on a predefined rule.
  • the table at the target MEC platform may have prevalence over the table at the source MEC platform; or, if the priorities for a MEC application are different according to the two tables, the higher priority has prevalence; etc.
  • the interfaces between MEC Platforms may be enhanced such that the source MEC Platform is able to inform the target MEC Platform about the priority of the MEC Application which is subject of the handover.
  • the target MEC Platform may react in a well-defined manner and either accept or reject the request. If the target MEC Platform accepts the request, it means that the target is able to instantiate the requested MEC Application within a given time frame with a given level of service (QoS).
  • QoS level of service
  • interfaces of the MEC system between MEC Platforms as well as the inter-BTS interfaces of regular mobility management in the mobile network may be used. The providing of the priority information may be considered as a request for pre-emption. If the priority information is provided via interfaces of the MEC system, the source MEC platform has to be informed on the target MEC platform. For example, information on the target MEC platform may be provided by step 7 of the preparation of MEC handover described hereinabove.
  • the request for pre-emption might be part of the handover preparation.
  • the handover preparation may be performed as described hereinabove.
  • the source MEC platform may request pre-emption if it is informed that a handover of the UE to a target BTS is planned.
  • the handover may be planned based on conventional handover preparation without taking into account that the UE uses a MEC application.
  • Apparatus comprising at least one processor, at least one memory including computer program code, and the at least one processor, with the at least one memory and the computer program code, being arranged to cause the apparatus to at least perform
  • the handover information informs that a terminal is planned to be handed over to a target base station
  • Target MEC platform or component thereof
  • Apparatus comprising at least one processor, at least one memory including computer program code, and the at least one processor, with the at least one memory and the computer program code, being arranged to cause the apparatus to at least perform
  • the target BTS may provide an identification of the target MEC platform to the source BTS.
  • the target BTS may provide the identification while evaluating the status of the MEC system and/or at preparation of handover.
  • Source BTS may then inform source MEC platform on the identification of the target MEC platform.
  • source MEC platform is aware of the identification of the target MEC platform and may provide the priority information to the target MEC platform.
  • the source MEC platform may determine the target mobile edge computing platform based on an association table available to the source MEC platform. The association table indicates which MEC platform(s) are associated to which base station(s). It may be stored in one, some, or all of the MEC platforms of the network or separately therefrom.
  • Pre-emption of MEC Applications at the target MEC Platform based on the priority of MEC Applications enables to use MEC applications for mission critical use cases. Otherwise the coverage by the MEC Application cannot be predicted, which might lead to service interruption with serious consequences.
  • the execution of the handover within the MEC system may be part of the regular execution of the handover in the mobile network.
  • the execution may be controlled by the BTS. It may be handled via the existing inter- BTS connections within the mobile network (e.g. in LTE: S1 and X2).
  • Fig. 6 comprising Figs. 6a and 6b shows a method to execute the handover of the MEC application according to some embodiments of the invention. This steps of Fig. 6a may be performed while the UE is still attached to the source BTS (before handover). The following steps are performed:
  • Precondition The BTS has defined a proper target for handover for a given UE and successfully prepared the MEC application at the MEC platform associated with the target BTS.
  • the precondition may be fulfilled by the Evaluation of status and Preparation of the MEC handover described hereinabove.
  • the source MEC platform may be informed about the handover, too.
  • the source BTS may inform its associated MEC platform and the selected target
  • the target BTS may request its associated MEC platform ("target MEC platform”) to execute the handover.
  • target MEC platform associated MEC platform
  • the source MEC platform and target MEC platform create a connection to each other using the same logical interface that the source BTS and target BTS are using for controlling the handover (in LTE: X2 or S1 ).
  • Source and target MEC platform and MEC application instances exchange all information that is necessary for the specific applications to transfer the application context and/or user context ("context") and to execute a handover for the specific UE. The details of such communication are specific for the specific applications.
  • the source BTS may consider a different target for the handover to guarantee to the UE a seamless service by the MEC applications.
  • the final result of this decision depends on the details of the handover algorithms.
  • the interface between BTS and MEC platform (RNIS) as well as the interface between the BTSs (in LTE: X2 and/or S1 ) is enhanced.
  • the interface between BTS and MEC platform may be enhanced as follows: • The source BTS may request from its associated MEC platform to execute the handover to the target MEC application instance(s).
  • the source BTS may offer to its associated MEC platform a generic tunnelling connection via the regular mobility management interfaces towards the target MEC platform.
  • the MEC platform at source BTS may request from source BTS a generic tunnelling connection via the regular mobility management interfaces towards the target MEC platform.
  • the target BTS may request from its associated MEC platform to execute the handover of the UE from the source MEC application instances.
  • the target BTS may offer to its associated MEC platform a generic tunnelling connection via the regular mobility management interfaces towards the source MEC platform.
  • the MEC platform at target BTS may request from target BTS a generic tunnelling connection via the regular mobility management interfaces towards the source MEC platform.
  • Source BTS and target BTS may use standardized interfaces (in LTE: X2 and S1 ) to execute the handover of voice calls and data transfers.
  • the interfaces between the BTS may be enhanced.
  • the source BTS may request the selected target BTS to execute the handover of the MEC application.
  • the source BTS may open a generic tunnelling interface towards the target BTS via the standardized mobility management interfaces.
  • the detailed content and format of the data is defined by the applications; from BTS point of view it is just "data”.
  • the target BTS may open a generic tunnelling interface towards the source BTS via the standardized mobility management interfaces
  • the tunnel between source BTS and source MEC platform and the tunnel between source BTS and target BTS may be connected.
  • the tunnel between target BTS and target MEC platform and the tunnel between target BTS and source BTS may be connected.
  • a tunnel between source MEC platform and target MEC platform is created such that the handover of the MEC application is transparent to the source BTS and the target BTS.
  • step 1 (deciding on a proper target BTS, and/or preparing the handover, both in view of the MEC application the UE is using, and/or informing the source MEC platform on the planned handover) may be omitted. That is, the source BTS may decide on the target BTS and/or prepare the handover thereto without considering that the UE uses a MEC application of the source MEC application platform, which should be handed over to the target MEC application, too. For example, such embodiments may be employed if a certain rate of service drops is acceptable.
  • the source MEC platform may handover the context of the used MEC application not via the base stations (through the tunnel) but within the MEC system.
  • the handover of the MEC application context is controlled via the link between the base stations, but the handover of the context is performed by a different interface between the MEC platforms.
  • the tunnel between source MEC platform and target MEC platform via the base stations is not needed and may not be set up.
  • step 1 some embodiments of the invention provide for example (several alternatives for each of the source BTS, source MEC platform, target BTS, and target MEC platform):
  • Source BTS or component thereof Apparatus, comprising at least one processor, at least one memory including computer program code, and the at least one processor, with the at least one memory and the computer program code, being arranged to cause the apparatus to at least perform
  • a terminal is handed over from a source base station to a target base station; requesting a source mobile edge computing platform to handover a context of a mobile edge computing application used by the terminal to a target mobile edge computing platform associated to the target base station if it is decided that the terminal is handed over from the source base station to the target base station.
  • the at least one processor may be arranged to cause the apparatus to further perform
  • the at least one processor may be arranged to cause the apparatus to further perform
  • the at least one processor may be arranged to cause the apparatus to further perform
  • the at least one processor may be arranged to cause the apparatus to further perform
  • Apparatus comprising at least one processor, at least one memory including computer program code, and the at least one processor, with the at least one memory and the computer program code, being arranged to cause the apparatus to at least perform
  • a source mobile edge computing platform receives, from a source base station, a request to provide a context of a mobile edge computing application for a terminal to a target mobile edge computing platform ;
  • the at least one processor may be arranged to cause the apparatus to further perform
  • the context is provided to the target mobile edge computing platform via the source tunnel.
  • the at least one processor may be arranged to cause the apparatus to further perform
  • Apparatus comprising at least one processor, at least one memory including computer program code, and the at least one processor, with the at least one memory and the computer program code, being arranged to cause the apparatus to at least perform
  • the at least one processor may be arranged to cause the apparatus to further perform
  • the at least one processor may be arranged to cause the apparatus to further perform
  • the at least one processor may be arranged to cause the apparatus to further perform
  • the at least one processor may be arranged to cause the apparatus to further perform
  • Target MEC platform or component thereof
  • Apparatus comprising at least one processor, at least one memory including computer program code, and the at least one processor, with the at least one memory and the computer program code, being arranged to cause the apparatus to at least perform
  • a target mobile edge computing platform receives, from a target base station, a request to provide a mobile edge computing application to a terminal;
  • the at least one processor may be arranged to cause the apparatus to further perform
  • the context of the mobile edge computing application for the terminal is obtained through the target tunnel.
  • the at least one processor may be arranged to cause the apparatus to further perform
  • the context of the mobile edge computing application for the terminal is obtained through the target tunnel.
  • the MEC applications might use a different, private, MEC-specific connection that circumvents the standardized mobility interfaces. But the usage of the standardized interfaces offers the advantage, that MEC would be able to rely on the management, supervision, and security of this already existing connection. In addition, the operability of the overall system would be improved, because the mobility within the MEC system would be based on the same planned, managed, and secured links as the mobility within the mobile network.
  • the source BTS executes the handover to a target BTS without considering the status of the related MEC system.
  • the BTS might execute a handover which from radio and core perspective would be fine, but that from MEC perspective fails. However, the BTS would not be aware of this and would not be able to react.
  • introduction of an architecture that enables the BTS to control the execution of the overall handover, including the handover within the MEC system the robustness of handovers within the MEC system will be improved.
  • the MEC system shall maintain a list of potential targets for MEC handover ("Relocation Group") in order to improve the mobility within the overall MEC system.
  • Relocation Group a list of potential targets for MEC handover
  • all MEc platforms of the relocation group may be provided with user and application information ("context"), so that a handover of the MEC application from one MEC platform to another MEC platform of the relocation group may be performed quickly.
  • the MEC system only has very limited knowledge about the radio conditions, which in the end will determine the actual handover time and target.
  • the BTS of the various radio technologies have very sophisticated mechanisms for the mobility management.
  • the source BTS collects and evaluates various information from the UE and from the potential target BTS to determine the best handover target and best time for a handover.
  • the mobility management of current mobile networks are offering mechanisms to find the neighbour relations automatically ("ANR").
  • the BTS maintains statistics on the performance of the executed or failed handovers. As a consequence the BTS has the best knowledge about the overall performance and probabilities of handovers to all targets, that from radio point of view might be accessible.
  • the source BTS may compile a list of target cells and/or target BTS and pass this list as proposed "Relocation Group" to the MEC Platform.
  • the list may comprise a ranking of the cells and/or target BTS.
  • the list may comprise only those cells and/or target BTS, for which a probability of a handover of a UE handing over from the source BTS to the respective cell and/or target BTS is higher than a predefined threshold. For example, such probability may be evaluated from handover statistics of the past.
  • the MEC system e.g. source MEC platform associated to the source BTS
  • the MEC relocation group may be the same as the MEC platforms corresponding to the cells and/or target BTS of the received list.
  • the source MEC platform may add further MEC platforms or remove some of the MEC platforms of the list, e.g. the MEC platforms associated to lower ranked cells/target BTS.
  • the source MEC platform may determine the mobile edge computing platform(s) corresponding to the cells/target BTS of the list based on an association table available to the source MEC platform.
  • the association table indicates which MEC platform(s) are associated to which base station(s). It may be stored in one, some, or all of the MEC platforms of the network or separately therefrom.
  • the list from the source base station may comprise an identification of the target MEC platform instead of or in addition to the identification of the cells/target BTS.
  • the list of BTS may comprise further information for some or all of the BTS such as number of HO per time window, quality of HO, failure rate of handover etc.
  • the BTS may be able to send a list of potential target cells and target BTS as "Proposed Relocation Group" to the MEC Platform.
  • the BTS may include quality criteria for each potential target cell and target BTS of the "Proposed Relocation Group”.
  • the list may be ranked.
  • the list may comprise identifiers of the MEC platforms associated to the respective cells/BTS.
  • the MEC Platform may request the list (proposed relocation group(s)) from the BTS.
  • the BTS may initiate the transfer of the list to the MEC platform.
  • the BTS Compared to the MEC Platform, the BTS has a much more detailed knowledge on the potential target cells and the corresponding quality and performance of handovers, because the BTS in detail evaluates many properties of the UE, the air interface, the neighbour cells and neighbour BTS. Due to ANR mechanisms the mobile network is able to automatically detect this neighbour information in a very early phase of the lifetime of the BTS without manual intervention. Therefore, the quality of "Relocation Groups" will be much better if the BTS would assist in generating them and would offer proposals. Likewise the robustness and quality of handovers in the MEC system would be improved.
  • Fig. 7 shows an apparatus according to an embodiment of the invention.
  • the apparatus may be a base station such as a source base station (NodeB, eNB, etc.) or an element thereof.
  • Fig. 8 shows a method according to an embodiment of the invention.
  • the apparatus according to Fig. 7 may perform the method of Fig. 8 but is not limited to this method.
  • the method of Fig. 8 may be performed by the apparatus of Fig. 7 but is not limited to being performed by this apparatus.
  • the apparatus comprises inquiring means 10, requesting means 20, and deciding means 30.
  • Each of the inquiring means 10, requesting means 20, and deciding means 30 may be a inquiring processor, requesting processor, and deciding processor, respectively.
  • the inquiring means 10 inquires, from a source mobile edge computing platform, a usage information (S10).
  • the usage information indicates if a terminal uses a mobile edge computing application of the source mobile edge computing platform.
  • the requesting means 20 requests, from a target base station, a support information (S20).
  • the support information indicates if the mobile edge computing application is supported at the target base station.
  • S10 and S20 may be performed in an arbitrary sequence. They may be performed fully or partly in parallel.
  • the deciding means 30 decides on a handover of the terminal to the target base station based on the usage information and the support information (S30). That is, the deciding means decides, based on the usage information and the support information, whether or not the terminal is handed over to the target base station.
  • Fig. 9 shows an apparatus according to an embodiment of the invention.
  • the apparatus may be a MEC platform such as a source MEC platform or an element thereof.
  • Fig. 10 shows a method according to an embodiment of the invention.
  • the apparatus according to Fig. 9 may perform the method of Fig. 10 but is not limited to this method.
  • the method of Fig. 10 may be performed by the apparatus of Fig. 9 but is not limited to being performed by this apparatus.
  • the apparatus comprises monitoring means 1 10, determining means 120, preparing means 130, and providing means 140.
  • Each of the monitoring means 1 10, determining means 120, preparing means 130, and providing means 140 may be a monitoring processor, determining processor, preparing processor, and providing processor, respectively.
  • the monitoring means 1 10 monitors if a request to provide a usage information is received from a source base station (S1 10).
  • the usage information indicates if a terminal uses a mobile edge computing application of a source mobile edge computing platform.
  • the request may comprise an identification of the terminal. Typically, it may not comprise an identification of the mobile edge computing application.
  • the determining means 120 determines if the terminal uses the mobile edge computing application (S120). Based on a result of the determining by the determining means 120, the preparing means 130 prepares the usage information (S130).
  • Each of S120 and S130 may be performed only if the request is received or independent from such a request.
  • the providing means 140 provides the usage information to the source base station in response to the received request (S140).
  • Fig. 1 1 shows an apparatus according to an embodiment of the invention.
  • the apparatus may be a MEC platform such as a target MEC platform or an element thereof.
  • Fig. 12 shows a method according to an embodiment of the invention.
  • the apparatus according to Fig. 1 1 may perform the method of Fig. 12 but is not limited to this method.
  • the method of Fig. 12 may be performed by the apparatus of Fig. 1 1 but is not limited to being performed by this apparatus.
  • the apparatus comprises monitoring means 210, requesting means 220, preparing means 230, and providing means 240.
  • Each of the monitoring means 210, determining means 220, preparing means 230, and providing means 240 may be a monitoring processor, determining processor, preparing processor, and providing processor, respectively.
  • the monitoring means 210 monitors if a request to provide a support information is received from a source base station (S210).
  • the support information indicates if a mobile edge computing application is supported at a target base station.
  • the requesting means 220 requests to provide a capability information from a target mobile edge computing platform (S220).
  • the capability information indicates if the target mobile edge computing platform supports the mobile edge computing application.
  • the preparing means 230 prepares the usage information (S230).
  • Each of S120 and S130 may be performed only if the request for the support information is received or independent from such a request.
  • the providing means 140 provides the support information to the source base station in response to the received request for the support information (S140).
  • Fig. 13 shows an apparatus according to an embodiment of the invention.
  • the apparatus may be a MEC platform such as a target MEC platform or an element thereof.
  • Fig. 14 shows a method according to an embodiment of the invention.
  • the apparatus according to Fig. 13 may perform the method of Fig. 14 but is not limited to this method.
  • the method of Fig. 14 may be performed by the apparatus of Fig. 13 but is not limited to being performed by this apparatus.
  • the apparatus comprises monitoring means 310, determining means 320, preparing means 330, and providing means 340.
  • Each of the monitoring means 310, determining means 320, preparing means 330, and providing means 340 may be a monitoring processor, determining processor, preparing processor, and providing processor, respectively.
  • the monitoring means 310 monitors if a request to provide a capability information is received from a target base station (S310).
  • the capability information indicates if a target mobile edge computing platform supports a mobile edge computing application.
  • the request may comprise an indication of the mobile edge computing application.
  • the determining means 320 determines if the mobile edge computing application supports the mobile edge computing application (S320). Based on a result of the determining by the determining means 320, the preparing means 330 prepares the capability information (S330).
  • Each of S320 and S330 may be performed only if the request is received or independent from such a request.
  • the providing means 340 provides the capability information to the target base station in response to the received request (S340).
  • Fig. 15 shows an apparatus according to an embodiment of the invention.
  • the apparatus may be a base station such as a source base station (NodeB, eNB) or an element thereof.
  • Fig. 16 shows a method according to an embodiment of the invention.
  • the apparatus according to Fig. 15 may perform the method of Fig. 16 but is not limited to this method.
  • the method of Fig. 16 may be performed by the apparatus of Fig. 15 but is not limited to being performed by this apparatus.
  • the apparatus comprises providing means 410.
  • the providing means 410 may be a providing processor.
  • the providing means 410 provides a list of one or more target base stations from a source base station to a mobile edge computing platform (S410).
  • the list comprises those target base station(s), wherein a terminal connected to the source base station may handover to each of the target base station(s) with a probability larger than a predefined threshold.
  • Fig. 17 shows an apparatus according to an embodiment of the invention.
  • the apparatus may be a MEC platform such as a source MEC platform or an element thereof.
  • Fig. 18 shows a method according to an embodiment of the invention.
  • the apparatus according to Fig. 17 may perform the method of Fig. 18 but is not limited to this method.
  • the method of Fig. 18 may be performed by the apparatus of Fig. 17 but is not limited to being performed by this apparatus.
  • the apparatus comprises monitoring means 510, determining means 520, checking means 530, and providing means 540.
  • Each of the monitoring means 510, determining means 520, checking means 530, and providing means 540 may be a monitoring processor, determining processor, checking processor, and providing processor, respectively.
  • the monitoring means 510 monitors if a list of one or more target base stations is received by a source mobile edge computing platform (S510).
  • the determining means 520 determines one or more target mobile edge computing platforms (S520).
  • the target mobile edge computing platforms are determined such that each of the target mobile edge computing platforms corresponds to respective at least one of the one or more target base stations comprised in the list.
  • the checking means 530 checks if a terminal uses a mobile edge computing application of the source mobile edge computing platform (S530).
  • S520 and S530 may be performed in an arbitrary sequence. They may be performed fully or partly in parallel.
  • the providing means 540 provides at least one of an application context and a user context of the application used by the terminal to each of the target mobile edge computing platforms determined by the determining means 520 (S540).
  • Fig. 19 shows an apparatus according to an embodiment of the invention.
  • the apparatus comprises at least one processor 610, at least one memory 620 including computer program code, and the at least one processor 610, with the at least one memory 620 and the computer program code, being arranged to cause the apparatus to at least perform at least one of the methods according to Figs. 8, 10, 12, 14, 16, and 18.
  • One piece of information may be transmitted in one or plural messages from one entity to another entity. Each of these messages may comprise further (different) pieces of information.
  • Names of network elements, protocols, and methods are based on current 3GPP standards, in particular those for LTE. In other versions or other technologies, the names of these network elements and/or protocols and/or methods may be different, as long as they provide a corresponding functionality. For example, embodiments of the invention may be deployed in 2G/3G/4G/5G networks and further generations of 3GPP or a WLAN network.
  • a terminal is a subscription device. It may be e.g. a UE, a UICC, a eUICC, a MTC device, a mobile station, or a SIM card, a USIM card, etc, or any other device related to a subscription in a mobile communication network.
  • An eNB is an example of a base station.
  • Other embodiments of the invention may use e.g. a BTS (e.g. in 2G networks) or a NodeB (e.g. in 3G networks) instead of the eNB.
  • each of the entities described in the present description may be based on a different hardware, or some or all of the entities may be based on the same hardware. It does not necessarily mean that they are based on different software. That is, each of the entities described in the present description may be based on different software, or some or all of the entities may be based on the same software.
  • Each of the entities described in the present description may be embodied in the cloud.
  • example embodiments of the present invention provide, for example, a computing platform such as a MEC platform, or a component thereof, an apparatus embodying the same, a method for controlling and/or operating the same, and computer program(s) controlling and/or operating the same as well as mediums carrying such computer program(s) and forming computer program product(s).
  • example embodiments of the present invention provide, for example, a base station such as a eNodeB or NodeB, or a component thereof, an apparatus embodying the same, a method for controlling and/or operating the same, and computer program(s) controlling and/or operating the same as well as mediums carrying such computer program(s) and forming computer program product(s).
  • Implementations of any of the above described blocks, apparatuses, systems, techniques or methods include, as non-limiting examples, implementations as hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof. Some embodiments of the invention may be implemented in the cloud.

Landscapes

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

Abstract

La présente invention concerne un procédé consistant à demander, à partir d'une plateforme informatique de bord mobile source, des informations d'utilisation se rapportant à un terminal indiquant une application informatique de bord mobile de la plateforme informatique de bord mobile source utilisée par le terminal ; à demander, à partir d'une station de base cible, des informations de prise en charge indiquant si l'application informatique de bord mobile est prise en charge au niveau de la station de base cible ; à décider d'un transfert du terminal vers la station de base cible sur la base des informations d'utilisation et des informations de prise en charge.
PCT/EP2017/067277 2017-07-10 2017-07-10 Transfert d'application mec WO2019011408A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2017/067277 WO2019011408A1 (fr) 2017-07-10 2017-07-10 Transfert d'application mec

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2017/067277 WO2019011408A1 (fr) 2017-07-10 2017-07-10 Transfert d'application mec

Publications (1)

Publication Number Publication Date
WO2019011408A1 true WO2019011408A1 (fr) 2019-01-17

Family

ID=59383542

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2017/067277 WO2019011408A1 (fr) 2017-07-10 2017-07-10 Transfert d'application mec

Country Status (1)

Country Link
WO (1) WO2019011408A1 (fr)

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020156673A1 (fr) * 2019-01-31 2020-08-06 Nokia Technologies Oy Procédé, appareil et produit-programme informatique pour la gestion d'entités mobiles
EP3697132A1 (fr) * 2019-02-13 2020-08-19 Deutsche Telekom AG Transfert d'une application critique de latence
WO2020185000A1 (fr) * 2019-03-12 2020-09-17 Samsung Electronics Co., Ltd. Procédés et systèmes permettant d'optimiser le traitement de demandes d'application
CN112153555A (zh) * 2019-06-28 2020-12-29 中兴通讯股份有限公司 媒体服务在区域间的切换方法、服务器、系统及存储介质
WO2021012926A1 (fr) * 2019-07-25 2021-01-28 中兴通讯股份有限公司 Procédé et dispositif de relocalisation d'application basée sur l'informatique en périphérie
GB2589154A (en) * 2019-11-25 2021-05-26 Ind Tech Res Inst Method and system for accessing private network services
WO2021146289A1 (fr) * 2020-01-13 2021-07-22 Qualcomm Incorporated Système et procédé de mobilité priorisée pour accéder à des serveurs de bord
CN113412646A (zh) * 2019-02-15 2021-09-17 索尼集团公司 信息处理设备、移动体设备、信息处理方法以及信息处理程序
EP3883296A1 (fr) 2020-03-19 2021-09-22 Deutsche Telekom AG Appareil et procédé pour réseaux mobiles permettant une sélection et un transfert optimaux des serveurs d'application
WO2022019676A1 (fr) * 2020-07-23 2022-01-27 Samsung Electronics Co., Ltd. Procédé et appareil de sélection d'un serveur cible d'application de périphérie dans un environnement informatique de périphérie
US20220116831A1 (en) * 2020-10-08 2022-04-14 Samsung Electronics Co., Ltd. Method and apparatus for providing mec service
CN114615274A (zh) * 2020-12-07 2022-06-10 中国移动通信有限公司研究院 边缘应用访问方法、装置及相关设备
JP2022120845A (ja) * 2021-02-05 2022-08-18 ジオ プラットフォームズ リミティド インテリジェントエッジルーティングのシステム及び方法
US11856471B2 (en) 2020-01-23 2023-12-26 Samsung Electronics Co., Ltd. Method and apparatus for edge computing service
US12028754B2 (en) 2019-01-31 2024-07-02 Nokia Technologies Oy Method, apparatus and computer program product for management of mobile entities

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15)", 3GPP STANDARD; 3GPP TS 23.501, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V0.5.0, 1 June 2017 (2017-06-01), pages 1 - 145, XP051298314 *
-: "Mobile Edge Computing (MEC); End to End Mobility Aspects", 23 June 2017 (2017-06-23), 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE, pages 1 - 53, XP055430420, Retrieved from the Internet <URL:https://docbox.etsi.org/ISG/MEC/70-Draft/0018E2EMobility/MEC-0018E2EMobilityv034.docx> [retrieved on 20171130] *
ANDREW MACHEN; SHIQIANG WANG; KIN K. LEUNG; BONG JUN KO; THEODOROS SALONIDIS: "Proceedings of the 22nd Annual International Conference on Mobile Computing and Networking", 3 October 2016, ACM, article "Poster: Migrating running applications across mobile edge clouds", pages: 435 - 436

Cited By (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020156673A1 (fr) * 2019-01-31 2020-08-06 Nokia Technologies Oy Procédé, appareil et produit-programme informatique pour la gestion d'entités mobiles
US20220104077A1 (en) * 2019-01-31 2022-03-31 Nokia Technologies Oy A method, apparatus and computer program product for management of mobile entities
US12028754B2 (en) 2019-01-31 2024-07-02 Nokia Technologies Oy Method, apparatus and computer program product for management of mobile entities
EP3697132A1 (fr) * 2019-02-13 2020-08-19 Deutsche Telekom AG Transfert d'une application critique de latence
WO2020165320A1 (fr) * 2019-02-13 2020-08-20 Deutsche Telekom Ag Transfert intercellulaire d'une application à latence critique
US20220132387A1 (en) * 2019-02-13 2022-04-28 Deutsche Telekom Ag Handover of a latency critical application
US12028767B2 (en) 2019-02-13 2024-07-02 Deutsche Telekom Ag Handover of a latency critical application
EP3927018A4 (fr) * 2019-02-15 2022-04-06 Sony Group Corporation Dispositif de traitement d'informations, dispositif mobile, procédé de traitement d'informations et programme de traitement d'informations
CN113412646A (zh) * 2019-02-15 2021-09-17 索尼集团公司 信息处理设备、移动体设备、信息处理方法以及信息处理程序
US11140565B2 (en) 2019-03-12 2021-10-05 Samsung Electronics Co., Ltd. Methods and systems for optimizing processing of application requests
WO2020185000A1 (fr) * 2019-03-12 2020-09-17 Samsung Electronics Co., Ltd. Procédés et systèmes permettant d'optimiser le traitement de demandes d'application
CN112153555A (zh) * 2019-06-28 2020-12-29 中兴通讯股份有限公司 媒体服务在区域间的切换方法、服务器、系统及存储介质
CN112153555B (zh) * 2019-06-28 2023-07-21 中兴通讯股份有限公司 媒体服务在区域间的切换方法、服务器、系统及存储介质
EP3869835A4 (fr) * 2019-07-25 2022-01-26 ZTE Corporation Procédé et dispositif de relocalisation d'application basée sur l'informatique en périphérie
CN112367605A (zh) * 2019-07-25 2021-02-12 中兴通讯股份有限公司 基于边缘计算的应用重定位方法及装置
WO2021012926A1 (fr) * 2019-07-25 2021-01-28 中兴通讯股份有限公司 Procédé et dispositif de relocalisation d'application basée sur l'informatique en périphérie
GB2589154A (en) * 2019-11-25 2021-05-26 Ind Tech Res Inst Method and system for accessing private network services
GB2589154B (en) * 2019-11-25 2022-05-25 Ind Tech Res Inst Method and system for accessing private network services
US11683747B2 (en) 2020-01-13 2023-06-20 Qualcomm Incorporated System and method for prioritized mobility to access edge servers
WO2021146289A1 (fr) * 2020-01-13 2021-07-22 Qualcomm Incorporated Système et procédé de mobilité priorisée pour accéder à des serveurs de bord
CN114982285A (zh) * 2020-01-13 2022-08-30 高通股份有限公司 用于访问边缘服务器的优先化移动性的系统和方法
CN114982285B (zh) * 2020-01-13 2024-04-26 高通股份有限公司 用于访问边缘服务器的优先化移动性的系统和方法
US11856471B2 (en) 2020-01-23 2023-12-26 Samsung Electronics Co., Ltd. Method and apparatus for edge computing service
EP3883296A1 (fr) 2020-03-19 2021-09-22 Deutsche Telekom AG Appareil et procédé pour réseaux mobiles permettant une sélection et un transfert optimaux des serveurs d'application
US11463519B2 (en) 2020-07-23 2022-10-04 Samsung Electronics Co., Ltd. Method and apparatus for selecting a target edge application server in an edge computing environment
WO2022019676A1 (fr) * 2020-07-23 2022-01-27 Samsung Electronics Co., Ltd. Procédé et appareil de sélection d'un serveur cible d'application de périphérie dans un environnement informatique de périphérie
US11652882B2 (en) 2020-07-23 2023-05-16 Samsung Electronics Co., Ltd. Method and apparatus for selecting a target edge application server in an edge computing environment
US12015668B2 (en) 2020-07-23 2024-06-18 Samsung Electronics Co., Ltd. Method and apparatus for selecting a target edge application server in an edge computing environment
US20220116831A1 (en) * 2020-10-08 2022-04-14 Samsung Electronics Co., Ltd. Method and apparatus for providing mec service
CN114615274A (zh) * 2020-12-07 2022-06-10 中国移动通信有限公司研究院 边缘应用访问方法、装置及相关设备
JP7382429B2 (ja) 2021-02-05 2023-11-16 ジオ プラットフォームズ リミティド インテリジェントエッジルーティングのシステム及び方法
JP2022120845A (ja) * 2021-02-05 2022-08-18 ジオ プラットフォームズ リミティド インテリジェントエッジルーティングのシステム及び方法

Similar Documents

Publication Publication Date Title
WO2019011408A1 (fr) Transfert d&#39;application mec
US11792705B2 (en) Communication method and system in handover carrying NSSAI, and corresponding core network device
CN110419240B (zh) 切片兼容的切换控制设备和方法
US11109217B2 (en) Method for determining target, network element, and system for determining target
EP2995131B1 (fr) Réselection de cellule en fonction de priorité avec des priorités spécifiques des cellules
US9326202B2 (en) Method and system for the common management of communication resources in a telecommunications network having distinct communication resources pools
US20220279403A1 (en) Information transmission method and apparatus, storage medium and electronic apparatus
EP2925081B1 (fr) Procédé de repli sur commutation de circuits, dispositif et station de base
US9883442B2 (en) Offload processing method, control unit, and system
US20230040440A1 (en) Session setup and handover method and device thereof
US9456370B2 (en) Method and system of cell selection for a handover during coexistence of LTE FDD/TDD networks
US20130210438A1 (en) Cell-based inter-frequency measurement events for detected or monitored set cells
US20180007720A1 (en) Service processing method, related apparatus, and system
EP3136784B1 (fr) Procédé d&#39;évaluation du debit entre un point d&#39;access et une cellule source
US20240015599A1 (en) Ran congestion management and service continuity with user consent option
WO2020242368A1 (fr) Nœud de réseau, dispositif de communication et procédé de rapport de mesure
US11218937B2 (en) Method and system for managing user application level quality-of-service aware handover in wireless network
US10499287B1 (en) System, method, and computer program for smart inter-radio access technology (IRAT) voice over long term evolution (LTE) mobility
EP3735031B1 (fr) Procédé de traitement de transfert, dispositif de réseau, dispositif de terminal et support de stockage d&#39;ordinateur
CN113973316A (zh) 一种移动性参数配置方法及相关设备
CN115843074A (zh) 一种优化双连接的方法及设备

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: 17742393

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: 17742393

Country of ref document: EP

Kind code of ref document: A1