WO2019042000A1 - 实例切换方法及相关装置 - Google Patents

实例切换方法及相关装置 Download PDF

Info

Publication number
WO2019042000A1
WO2019042000A1 PCT/CN2018/093308 CN2018093308W WO2019042000A1 WO 2019042000 A1 WO2019042000 A1 WO 2019042000A1 CN 2018093308 W CN2018093308 W CN 2018093308W WO 2019042000 A1 WO2019042000 A1 WO 2019042000A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
instance
base station
mec platform
service
Prior art date
Application number
PCT/CN2018/093308
Other languages
English (en)
French (fr)
Inventor
金爱进
张丰裕
帅扬来
王岩
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP18850083.9A priority Critical patent/EP3664508A4/en
Publication of WO2019042000A1 publication Critical patent/WO2019042000A1/zh
Priority to US16/805,180 priority patent/US20200205040A1/en

Links

Images

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/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/508—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement
    • H04L41/5096—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement wherein the managed service relates to distributed or central networked applications
    • 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
    • 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/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • 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/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • H04W36/322—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by location data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements

Definitions

  • the present application relates to the field of communications, and in particular, to an example switching method and related apparatus.
  • the construction of the wireless communication network is centered on the data center (English: data center).
  • Each data center uses distributed cloud (English: cloud) technology to manage, forming a hierarchical cloud system (edge cloud) plus central cloud (English: central cloud).
  • An application instance (hereinafter referred to as an instance) that provides an application service for the user equipment (English: user equipment, abbreviated as the UE) is deployed on each edge cloud, so that the application service instance is deployed closer to the UE, and the service is reduced. Delays and improve the service experience.
  • the target UE originally accesses the first base station, and the first instance deployed on the first mobile edge platform (English: mobile edge platform) provides the service of the target UE.
  • the mobile edge platform is also known as the MEC platform.
  • the target UE moves from the cell of the first base station to the cell range of the second base station, the target UE switches from the first base station to the second base station, and the instance serving the target UE also needs to be switched to the second MEC platform.
  • the second instance of the deployment is also known as the MEC platform.
  • the current stage of the handover method is: when the first base station determines that the target UE is handed over to the second base station, the first base station instructs the first MEC platform to perform instance switching, and the first MEC platform sends the status content of the first instance to the second MEC. In the second instance on the platform.
  • the target UE cannot perform normal services, and the handover process takes a long time, which affects the user's service continuity to the service.
  • An embodiment of the present application provides an example switching method and related apparatus, which are used to reduce the time spent on instance switching and provide a user experience.
  • an embodiment of the present application provides an example switching method, including:
  • the first switching device determines that the target UE provides the target application service on the first mobile edge MEC platform.
  • the first instance is to be switched to the second instance on the second MEC platform, where the first MEC platform and the second MEC platform are respectively used to provide the UE in the cell of the first base station and the UE in the cell of the second base station Target application service.
  • the target application service is an application service accessed by the target UE.
  • the first switching device notifies the first MEC platform that the first instance that provides the target application service for the target UE will switch to the second instance.
  • the first switching device indicates the first MEC platform: the first instance that provides the target UE with the target application service is switched to the second instance on the second MEC platform.
  • the first MEC platform learns that the instance providing the target application service for the target UE will switch to the second instance on the second MEC platform.
  • the network side device starts to find, for the target UE, which instance of the MEC platform the instance of the target application service is to be switched to for the target UE.
  • the first MEC platform learns that the instance that provides the target application service for the target UE will switch to the second instance on the second MEC platform. Therefore, in the subsequent instance switching, the search of the MEC platform and the searching process of the second instance are not required, thereby reducing the interruption time of the service and improving the user experience.
  • the first switching device determines that the first instance on the first MEC platform that provides the target application service for the target UE to be switched to the second instance on the second MEC platform may include:
  • the first switching device acquires the location information of the target UE from the first base station, determines the second switching device according to the location information of the target UE, and sends a first request message including the service identifier ID of the target application service to the second switching device, where
  • the second switching device is configured to provide an instance of the handover service for the UE connected to the second base station, and the service ID of the target application service is associated with the second instance of the second MEC platform.
  • the first switching device receives, from the second switching device, a first response message carrying the instance ID of the second instance, and the first switching device determines, according to the instance ID of the second instance, that the target UE provides the first MEC platform of the target application service.
  • the first instance above is to be switched to the second instance on the second MEC platform.
  • the first switching device acquires the instance ID of the second instance from the second switching device before notifying the first MEC platform, thereby determining that the instance providing the target UE for the target UE is to be switched to the second instance.
  • the instance ID of the second instance may be notified to the first MEC platform, and the first MEC platform may determine, by using the instance ID of the second instance, the target application for the target UE.
  • the instance of the service will switch to the second instance on the second MEC platform.
  • the first MEC platform does not need to obtain the instance ID of the second instance from the second MEC platform, which reduces the signaling interaction of the first MEC platform, thereby reducing the burden on the first MEC platform.
  • the method further includes:
  • the first switching device creates a service feature according to the instance ID of the second instance, and sends the packet forwarding policy to the first gateway, where the packet forwarding policy includes a service feature, and the packet forwarding policy is used to indicate the first gateway: according to the service feature Identifying the target uplink packet, and forwarding the target uplink packet to the second gateway, where the target uplink packet is an uplink packet that the target UE interacts with the target application service, where the first gateway is used to provide the service service for the first base station,
  • the second gateway is configured to provide a service service for the second base station.
  • the first gateway and the second gateway establish a service forwarding tunnel.
  • the target UE may report the information or the context content of the transport protocol used by the target UE to connect with the first instance.
  • the manner of the text is sent to the second instance through the service forwarding tunnel.
  • the uplink packet sent by the target UE may be forwarded to the second instance by using the service forwarding tunnel of the first gateway and the second gateway.
  • the target UE sends the uplink packet to the first gateway, when the packet is not forwarded to the first instance, and the target UE accesses the second base station and starts the instance switch, the packet is sent. Cannot be forwarded to the second instance and thus discarded.
  • the uplink packet sent by the target UE is not discarded due to the instance handover.
  • an embodiment of the present application provides an example switching method, including:
  • the first handover apparatus determines to provide the target UE with an instance of the target application service to be switched.
  • the first MEC platform is configured to provide a target application service for the UE in the cell of the first base station, where the target application service is an application service accessed by the target UE.
  • the first switching device notifies the first MEC platform that an instance of providing the target application service for the target UE will be handed over.
  • the first switching device indicates the first MEC platform: the instance that provides the target UE with the target application service is switched.
  • the first switching device only determines that the target UE provides an instance of the target application service to be switched, thereby notifying the first MEC platform that the first MEC platform receives After the notification, the network device of the second base station side obtains the instance ID of the target instance, and further determines that the instance of the target application service provided by the target UE is to be switched to the second instance of the second MEC platform.
  • the first switching device only determines that the target UE provides an instance of the target application service to be switched, and the step of determining the second instance is performed by the first MEC platform, improving resource utilization of the network side device, and reducing the first switching device. burden.
  • the embodiment of the present application provides a switching device, such as the first switching device of the first aspect, the device includes:
  • a determining unit configured to determine, before the target user equipment UE moves to the cell range of the second base station, and before successfully accessing the second base station, determine that the first instance on the first mobile edge MEC platform that provides the target application service for the target UE Switching to the second instance on the second MEC platform, where the target UE is the UE accessing the first base station, the first MEC platform is used to provide the target application service for the UE in the cell of the first base station, and the second MEC platform is used for Providing target application services for UEs in the second base station cell.
  • the notifying unit is configured to notify the first MEC platform before the target UE successfully accesses the second base station: the first instance that provides the target application service to the target UE will be switched to the second instance.
  • an indication unit configured to: after the target UE successfully accesses the second base station, instruct the first MEC platform to: switch the first instance that provides the target application service to the target UE to the second instance on the second MEC platform.
  • an embodiment of the present application provides an example switching system, which is applicable to a mobile communication network, where the example switching system includes: a first base station, a first mobile edge MEC platform, a second base station, and a second MEC platform. And a first switching device, where the first MEC platform is configured to provide a target application service for the UE in the first base station cell, and the second MEC platform is used to provide the target application service by the UE in the second base station cell.
  • the first switching device is configured to provide an example handover service for the UE connected to the first base station, and the second handover device is configured to provide an instance handover service for the UE connected to the second base station; wherein the first handover device is as described in the third aspect The first switching device.
  • the present application provides an example switching apparatus, including: a processor, a memory, a transceiver, a processor, a memory, and a transceiver connected by a bus, where the memory stores computer instructions, and the processor implements by executing computer instructions.
  • the present application provides a readable storage medium storing computer instructions for implementing the method as described in the first aspect or the second aspect.
  • the present application provides a computer program product, the computer program product comprising computer software instructions executable by a processor to implement a process in a method as described in the first aspect or the second aspect .
  • the present application provides a chip system including a processor, and a conversion device for supporting an application instance address implements functions involved in the above aspects, for example, generating or processing information involved in the above method.
  • the chip system further includes a memory for holding program instructions and data necessary for the conversion device supporting the application instance address.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • the embodiment of the present application provides a communication device, where the communication device may include an entity such as a terminal device or a chip, the communication device includes: a processor and a memory; the memory is configured to store an instruction; and the processor is configured to execute in the memory.
  • the instructions cause the communication device to perform the method of any of the preceding first or second aspects.
  • FIG. 1(a) is a schematic diagram of a communication network architecture in an embodiment of the present application.
  • FIG. 1(b) is another schematic diagram of a communication network architecture in an embodiment of the present application.
  • FIG. 1(c) is another schematic diagram of a communication network architecture in an embodiment of the present application.
  • FIG. 2 is a schematic diagram of an embodiment of an example handover in an embodiment of the present application.
  • FIG. 3 is a schematic diagram of another embodiment of an example handover in an embodiment of the present application.
  • FIG. 4 is a schematic diagram of another embodiment of an example handover in an embodiment of the present application.
  • FIG. 5 is a schematic diagram of another embodiment of example switching in an embodiment of the present application.
  • FIG. 6 is a schematic diagram of an embodiment of a switching device according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of another embodiment of a switching device according to an embodiment of the present application.
  • the embodiment of the present application provides an instance switching method, which can complete an instance of providing an application service to a target UE in a faster manner.
  • the present application also proposes related switching devices, which will be separately described below.
  • FIG. 1(a) For the basic architecture of the communication network involved in this application, refer to FIG. 1(a), including: a core network (English: core network, abbreviated: CN) device, a first base station, a second base station, a first MEC platform, and a second MEC. platform.
  • CN core network
  • Each MEC platform is connected to a corresponding base station through a gateway, and each base station is connected to a core network device.
  • the MEC platform is a mobile edge infrastructure. For example, it can be composed of one or more servers, or a network architecture composed of one or more servers and other network devices (such as gateways, switches, etc.). Network resources are used to provide a service platform for an instance. At least one instance is deployed in each MEC platform, and the instance is used to provide application services for the UE.
  • the application service refers to a service provided by the terminal through various types of applications, such as a vehicle network application service operated by a certain developer.
  • the example refers to a specific application where an application service is deployed on different MEC platforms. Therefore, an application service can correspond to multiple instances.
  • the first MEC platform is deployed with the first instance
  • the second MEC platform is deployed with the second instance, where the first instance and the second instance are instances of the same application service.
  • the communication network shown in Fig. 1(a) can be extended with various variations.
  • the control plane (English: control plane, abbreviated: CP) and the user plane (English: user plane, abbreviation: UP) can be divided into a core network to form a control and user plane separation (English: control and user plane) Separation, abbreviation: CUPS) communication network, as shown in Figure 1 (b).
  • the device CN-CP indicates that the core network device only includes the control plane function.
  • the user plane of the core network is implemented by each gateway, that is, each gateway belongs to the core network side device, and performs the user plane function of the core network.
  • the data connection between the gateway and the base station is uniformly controlled by the control plane of the core network.
  • the base station (including the first base station and the second base station) of the present application is a new radio access base station (English: new radio gNB, abbreviated as: NR gNB) or other wireless access device, which is not limited in this application.
  • a new radio access base station English: new radio gNB, abbreviated as: NR gNB
  • NR gNB new radio access base station
  • the base station in this application may also perform a splitting of a centralized unit (English: centralized unit, CU) and a distributed unit (English: distributed unit, abbreviated as DU), as shown in FIG. 1(c). Show. Under this network architecture, the information interaction function of the data plane of the base station is implemented by the DU, and the management function of the control plane needs to be implemented by the CU.
  • An example of the application service in the present application is distributedly deployed on multiple MEC platforms in the vicinity of the base station, and is used to provide application services for UEs in the cell of the connected base station.
  • an example of an ultra reliable and low latency communication (URLLC) application would be deployed on multiple MEC platforms close to the base station.
  • the URLLC instances deployed on each MEC platform provide URLLC services for the UE respectively.
  • URLLC ultra reliable and low latency communication
  • the identifier corresponding to each application service can be recorded in the MEC platform.
  • An application service ID (hereinafter referred to as a service ID) is used to uniquely identify a corresponding application service to distinguish different application services.
  • the service ID may be in the form of a domain name (English: domain name).
  • the MEC platform may uniformly allocate a service ID for each application service.
  • the service ID may be a network protocol (English: Internet Protocol, short name: IP) address.
  • IP Internet Protocol
  • An instance of each application service also has an instance ID.
  • the instance ID is used to uniquely identify the corresponding instance to distinguish different instances of the same application service. That is, different instances of the same application service have the same service ID but different instance IDs.
  • the instance ID may be in the form of an IP address of the instance, or may be in other forms, which is not limited in the present application. It should be noted that when the service ID and the instance ID are in the form of an IP address, the sender or the receiver can distinguish the two by using different fields in the packet. For example, the sender and the receiver mutually agree that the first field of the message is the service ID, and the second field is the instance ID. When the sender sends a message to the receiver, it is set in the first field of the message. Is the IP address of the application service. The second field of the packet is the IP address of the instance. After receiving the packet, the receiving end can parse the IP address of the application service and the IP address of the instance from the corresponding field.
  • each switching device corresponds to one or more base stations, for example, the first switching device corresponds to the first base station, and the second switching device corresponds to the second base station.
  • Each switching device is configured to: provide an instance of the application service for the UE according to the location of the target UE moving in cooperation with the corresponding MEC platform.
  • the position of the switching device in the communication network is not limited in this application.
  • the switching device may be an independent device, or may be set together with one of a network device such as a base station, a gateway, and a core network device, or may be disposed in a network device such as a base station, a gateway, or a core network device in the form of a function module. Or it can be directly implemented by base stations, gateways, and core network devices.
  • the switching device can also be in other forms, which is not limited in the present application.
  • the present application provides an example handover method, where the handover apparatus switches to an instance of the application service provided by the target UE when the target UE moves from the cell of the first base station to the cell range of the second base station. See Figure 2 for the flow.
  • the target UE Before the process starts, the target UE is in the cell range of the first base station and accesses the first base station.
  • the target UE connects to the first instance of the target application service.
  • the process provided in this embodiment is started.
  • the first switching device determines that the first instance on the first MEC platform that provides the target application service for the target UE is to be switched to the second instance on the second MEC platform.
  • the first switching device determines that the first instance on the first MEC platform that provides the target application service for the target UE is to be switched to the second MEC platform. The second instance above.
  • the first switching device starts a process of determining that the target UE provides an instance of the target application service to be switched to the second instance on the second MEC platform, At the same time, the target UE also initiates a process of accessing the second base station.
  • the first handover apparatus Since the target UE takes a certain time from the start of accessing the second base station to completing the access to the second base station, the first handover apparatus starts to determine that the target application service instance of the target UE is to be switched to the second MEC platform. The flow of the second instance is performed before the target UE successfully accesses the second base station.
  • the first switching device may determine, by using multiple manners, that the target UE provides an instance of the target application service to be switched. For example, when the first base station determines that the target UE is to be handed over to the second base station, the first switching device is notified, and the first switching device determines to provide the target UE with an instance of the target application service to be switched. Alternatively, the first switching device may determine, according to the location information of the target UE, that the target UE enters the second base station cell range, and further determines that the target UE provides an instance of the target application service to be switched. The first switching device may also determine to provide an instance of the target application service to be switched by the target UE by using another method, which is not limited herein.
  • the first switching device may determine, in various manners, that the instance providing the target application service for the target UE is to be switched to the second instance on the second MEC platform.
  • the first switching device stores a correspondence between the first base station and the first MEC platform, and the first switching device has the capability of acquiring state information of the UE accessing the first base station.
  • the first handover device acquires the UE ID of the target UE, the service ID of the target application service, and the instance ID of the first instance.
  • the first switching device stores a service correspondence between an ID of a plurality of other base station side network devices and a plurality of other base station side network devices, wherein the plurality of other base stations are adjacent to the first base station, and multiple
  • the ID of the network device on the other base station side includes the ID of the second base station and the ID of the second switching device
  • the service correspondence relationship between the network devices on the other base station side includes the service correspondence relationship between the second base station and the second switching device.
  • the first switching device may determine, according to the location information of the target UE, the target UE to enter the cell range of the second base station, and the first switching device sends the service ID of the target application service to the network device of the second base station side (for example, the second The network device on the base station side is a second base station or a second switching device).
  • the network device on the second base station side obtains the instance ID of the second instance from the corresponding second MEC platform according to the service ID, and further feeds back the instance ID of the second instance to the first switching device. If the second base station corresponds to multiple MEC platforms, the network device on the second base station side needs to feed back the ID of the MEC platform corresponding to the second instance to the first switching device.
  • the first switching device can determine the unique second MEC platform by the second base station. After receiving the instance ID of the second instance, the first switching device can determine that the first instance of the target application service is to be switched to the second instance provided by the second MEC platform corresponding to the second base station.
  • the first base station determines, according to the location information of the UE, that the target UE is to be switched to the second base station, and notifies the first handover device of the ID of the second base station, and the first handover device determines that the target UE is the target UE.
  • the first instance of the target application service is to be switched to the second instance provided by the second MEC platform corresponding to the second base station (similar to the determination manner discussed in the previous implementation manner, and details are not described herein).
  • the first switching device may also determine, by other methods, that the first instance of the target application service is to be switched to the second instance on the second MEC platform, which is not limited herein.
  • the location information of the target UE may be in the form of a base station ID of the second base station or a cell ID of the cell corresponding to the second base station, or may be the gateway ID of the gateway corresponding to the second base station, or may be the target UE.
  • the geographic location information, or may be the ID of the second MEC platform, etc., is not limited herein.
  • the first switching device notifies the first MEC platform that the first instance that provides the target UE with the target application service will be switched to the second instance.
  • the first switching device Before the target UE successfully accesses the second base station, the first switching device notifies the first MEC platform that the first instance of providing the target application service to the target UE will switch to the second instance. For example, the first switching device sends a handover preparation message to the first MEC platform.
  • the handover preparation message includes a UE ID of the target UE, a service ID of the target application service, an ID of the second MEC platform, and an instance ID of the second instance.
  • the first MEC platform learns that the instance that provides the target application service for the target UE will switch to the second instance on the second MEC platform.
  • the first MEC platform may further forward the handover preparation message to the second MEC platform, and the second MEC platform also knows that the instance that provides the target application service for the target UE will be switched to the second on the second MEC platform.
  • the first switching device acquires the instance ID of the second instance by the network device on the second base station side, and the network device on the second base station side notifies the instance ID of the second instance of the second MEC platform after receiving the instance ID of the second instance
  • the second MEC platform an instance of providing the target application service to the target UE will switch to the second instance on the second MEC platform.
  • both the first MEC platform and the second MEC platform know that the instance that provides the target application service for the target UE will be switched to the second MEC platform.
  • the network side device starts to find, for the target UE, which instance of the MEC platform the instance of the target application service is to be switched to for the target UE.
  • the target UE cannot perform normal service work with the instance, thereby affecting the user's experience of continuity of the service of the service.
  • both the first MEC platform and the second MEC platform learn that the instance that provides the target application service for the target UE will be switched to the second MEC platform. Second example. Therefore, in the subsequent instance switching, the search of the MEC platform and the searching process of the second instance are not required, thereby reducing the interruption time of the service and improving the user experience.
  • the first MEC platform may perform the handover preparation work in cooperation with the second MEC platform according to the indication of the handover preparation message.
  • the first MEC platform may send part of the data of the target UE on the first instance to the second MEC platform.
  • part of the data includes: a transmission protocol of the target UE with the first instance, or static context content.
  • the handover preparation work cannot complete all data migration between the first instance and the second instance, but updates the context content of the information such as the foregoing transmission protocol or the static class to the second instance in advance.
  • the first MEC platform cooperates with the second MEC platform for instance switching, all data related to the target UE in the first instance is all updated to the second instance.
  • the first MEC platform may also cooperate with the second MEC platform to perform handover preparation work by other methods, which is not limited in this application.
  • the first MEC platform cooperates with the second MEC platform to update part of the data about the target UE in the first instance to the second instance, so that in the subsequent instance switching process, The partial data updated to the second instance does not need to be sent again, thereby reducing the time for instance switching.
  • the first switching device determines that the first instance on the first MEC platform that provides the target application service for the target UE is to be switched to the second instance on the second MEC platform, and the first switching device sends the first instance to the first MEC platform.
  • the process of the handover preparation message and the preparation process of the first MEC platform and the second MEC platform for handover preparation, and the process of accessing the second base station by the target UE may be simultaneously performed in the simultaneous interval. That is, the first switching device determines that the first instance on the first MEC platform that provides the target application service for the target UE is to be switched to the second instance on the second MEC platform, and the first switching device sends the handover preparation message to the first MEC platform.
  • the process of preparing the handover by the first MEC platform and the second MEC platform, and the process of accessing the second UE by the target UE does not affect each other.
  • the first handover device is triggered to determine that the first instance on the first MEC platform that provides the target application service for the target UE is to be switched to the second instance on the second MEC platform. And a process step of the target UE accessing the second base station.
  • the time that the existing UE accesses the base station is about 50 ms, and the first switching device determines that the first instance on the first MEC platform that provides the target application service for the target UE is to be switched to the second instance on the second MEC platform,
  • the time taken by the first switching device to send the handover preparation message to the first MEC platform and the process for the first MEC platform to cooperate with the second MEC platform for handover preparation is far less than 50 ms (except in the case of network abnormality). Therefore, the first switching device determines that the first instance to be switched on the first MEC platform that provides the target application service for the target UE is completed from the time when the target UE starts to access the second base station to the target UE accessing the second base station.
  • the first handover device sends a handover preparation message to the first MEC platform, and the first MEC platform cooperates with the second MEC platform to complete the handover preparation process, and the time taken to complete is less than the target The time taken by the UE to access the second base station.
  • the air interface will adopt the dual-connection mode, that is, the target UE accesses the second base station while maintaining the connection with the first base station without interruption, which is a dual connection technology. That is, after the target UE accesses the second base station, the target UE maintains an air interface connection with the first base station, and the target UE maintains a service connection with the first instance on the first MEC platform.
  • the target UE accesses the second base station while maintaining the connection with the first base station without interruption, which is a dual connection technology. That is, after the target UE accesses the second base station, the target UE maintains an air interface connection with the first base station, and the target UE maintains a service connection with the first instance on the first MEC platform.
  • the time required for the target UE to access the second base station is 50 ms
  • the time required for the instance handover (including determining the second instance and data synchronization between the instances) in the prior art is 30 ms
  • the time taken to determine the second instance is 20 ms
  • the time taken to synchronize the data between the instances is 10 ms.
  • the target UE If not based on the dual connectivity technology, that is, the target UE first accesses the second base station, and then performs instance switching. Then, the total time taken by the target UE from the handover of the second base station to the completion of the instance handover is at least 80 ms.
  • the service disconnection time perceived by the user side is 80 ms.
  • the target UE Because the target UE disconnects from the first base station, the target UE cannot perform normal service with the first instance on the first base station side. After the target UE accesses the second base station, the target UE cannot perform normal service with the second instance on the second base station side in the process of performing the instance handover.
  • the total time taken by the target UE to switch from the second base station to the completion of the instance handover is still at least 80 ms, and for the user side, the service disconnection time that the user side can perceive is 30 ms because the target UE During the 50 ms period of accessing the second base station, the target UE can still perform normal service with the first instance on the first base station side, and after the target UE accesses the second base station, the UE cannot perform normal service when performing instance switching.
  • the target UE performs the target instance lookup in the same period of accessing the second base station, that is, the determination of the second instance is completed. Then, the target UE accesses the second base station and the network side device (such as the first MEC platform), and the total time taken to determine the second instance is only 50 ms (because the network side device determines that the second instance is the target UE accessing the second base station). During the time period of the 50 ms, the user side does not perceive the service disconnection because the target UE can still perform normal service with the first instance on the first base station side. The time required for data synchronization in instance switching is 10ms.
  • the total time that the target UE needs to switch from the second base station to the completion of the instance handover may be at least 60 ms.
  • the time for instance switching is 10ms.
  • the service disconnection time that the user side can perceive is 10 ms. Therefore, the solution of the present application can complete the instance switching faster than the prior art solution, and shortens the time of service interruption and improves the continuity of the application service.
  • the first switching device notifies the first MEC platform that the first instance that provides the target application service for the target UE is switched to the second instance.
  • the first switching device After the target UE accesses the second base station, the first switching device sends a handover indication message to the first MEC platform, where the handover indication message is used to indicate that the first instance of the target application service is switched to the first MEC platform.
  • the handover indication message is used to indicate that the first instance of the target application service is switched to the first MEC platform.
  • the first MEC platform After receiving the handover indication message, the first MEC platform cooperates with the second MEC platform to switch the first instance that provides the target service on the target UE to the second instance. For example, the first MEC platform sends the information and data about the target UE of the first instance to the second MEC platform, and the second MEC platform imports the received information and data into the second instance, thereby completing the information of the second instance. And data updates.
  • the information includes information about a transmission protocol used by the target UE to perform data transmission with the first instance, and an IP address of the target UE, where the data includes data such as context content of the service performed by the target UE and the first instance.
  • the first MEC platform and the second MEC platform have cooperated to update part of the data (such as the transmission protocol and static context content) in the first instance to the second instance, then In the step, the first MEC platform does not need to send the foregoing part of the data to the second MEC platform, thereby reducing the time for instance switching.
  • part of the data such as the transmission protocol and static context content
  • the instance switching in this step is faster than the prior art.
  • the target UE accesses the second base station and performs data interaction with the second instance of the target application service provided by the second MEC platform, thereby implementing fast handover of the target application service instance for the target UE.
  • the first handover device before the first handover device sends the handover preparation message to the first MEC platform, it is determined that the first instance of providing the target application service for the target UE is to be switched to the second MEC platform.
  • the step of determining that the first instance of the target application service is to be switched to the second instance on the second MEC platform for the target UE may also be performed by the first MEC platform.
  • the first switching device determines to provide an instance of the target application service to be switched by the target UE.
  • step 201 The manner in which the first switching device determines to provide the target UE with the target application service to be switched is as described in step 201 in the embodiment of FIG. 2, and details are not described herein.
  • step 201 the first switching device only determines that the target UE provides an instance of the target application service to be switched, and does not determine that the target UE provides an instance of the target application service to be switched to the second MEC platform. The second instance above.
  • the first switching device notifies the first MEC platform that an instance of providing the target application service to the target UE will be switched.
  • the first switching device Before the target UE successfully accesses the second base station, the first switching device sends a handover preparation message to the first MEC platform.
  • the handover preparation message includes a UE ID of the target UE, a service ID of the target application service, and location information of the target UE.
  • the first MEC platform determines the second MEC platform according to the location information of the target UE, where the first MEC platform sends the service ID of the target application service to the second MEC platform, and the second MEC platform queries the service ID according to the service ID of the target application service.
  • the second instance corresponding to the target application service, and obtains the instance ID of the second instance.
  • the second MEC platform also knows that the instance providing the target application service for the target UE will switch to the second instance on the local.
  • the first switching device notifies the first MEC platform: the instance that provides the target UE with the target application service is switched.
  • step 203 For details, refer to step 203 in the embodiment of FIG. 2, and details are not described herein.
  • the first switching device only determines that the target UE is provided with the target application service to be switched, thereby notifying the first MEC platform, the first MEC platform.
  • the network device of the second base station side acquires the instance ID of the destination instance, and determines that the instance of the target application service provided by the target UE is to be switched to the second instance of the second MEC platform.
  • the first switching device only determines that the target UE provides an instance of the target application service to be switched, and the step of determining the second instance is performed by the first MEC platform, improving resource utilization of the network side device, and reducing the first switching device. burden.
  • the first switching device is an independent device.
  • the detailed flow of another embodiment of the example switching method provided by the present application will be exemplarily described below with reference to FIG. 4.
  • the first base station determines that the target UE is to be handed over to the second base station.
  • the first base station decides to switch the network connection of the target UE from the first base station to the second base station.
  • the target UE when the target UE moves to the cell range of the second base station, the target UE sends a measurement report to the first base station, and the first base station determines, according to the measurement report, that the base station to be handed over by the target UE is the second base station.
  • the first base station sends a handover request to the second base station based on the measurement report, and after receiving the handover request acknowledgement message of the second base station, the base station to be switched by the decision target UE is the second base station.
  • the first base station sends a preparation notification message to the first switching device.
  • the first base station After confirming that the base station of the target UE is to be handed over, the first base station sends a preparation notification message to the first handover apparatus.
  • the first switching device receives the preparation notification message.
  • the preparation notification message is used to notify the first handover apparatus that the target UE is to be accessed by the second base station to trigger a preparation process of the instance handover.
  • the preparation notification message carries a UE ID of the target UE and a base station ID of the second base station.
  • the preparation notification message may not carry the base station ID of the second base station, but carry the UE ID of the target UE and the location information of the target UE, and the first switching device may use the location information of the target UE. Determining a second base station to which the target UE is to be accessed.
  • each switching device may also store a range of service areas of each switching device in the communication network. Therefore, the first switching device may further determine the second switching device according to the location information of the UE.
  • a scenario including multiple switching devices in a communication network is further described in step 403.
  • the first switching device sends a first request message to the second switching device.
  • the first switching device is a network device on the first base station side
  • the second switching device is a network device on the second base station side.
  • the second switching device has the same function as the first switching device, and is used to provide an instance switching service for the UE connected to the corresponding base station.
  • the manner in which the communication connection between the switching device and the switching device is established is similar to the manner in which the base station and the base station are established.
  • the first switching device stores a communication identifier of the switching device corresponding to the plurality of base stations in the vicinity, and includes a communication identifier of the second switching device.
  • the first switching device queries the communication identifier of the corresponding second switching device by using the base station ID of the second base station, and establishes a communication connection with the second switching device according to the communication identifier.
  • the first switching device transmits a broadcast signal to a plurality of nearby switching devices, and after receiving the plurality of feedbacks, selects the corresponding second switching device to establish a communication connection according to the base station ID of the second base station.
  • the first switching device After receiving the preparation notification message, the first switching device establishes a communication connection with the second switching device corresponding to the second base station according to the base station ID of the second base station in the preparation notification message, and performs a second connection to the second switching device.
  • the device sends a first request message.
  • the first request message includes a UE ID of the target UE and a service ID of the target application service, and the first request message is used to request the second handover apparatus to return information of the new instance of the target application service on the target UE.
  • the first response message returned by the second switching device to the first switching device carries the information of the determined new instance.
  • the first switching device after receiving the handover notification message, is the second corresponding to the second base station.
  • the switching device establishes a communication connection
  • the first request message is sent to the second switching device. That is, the first switching device carries the first request message in the request information for establishing a communication connection sent to the second switching device.
  • the second switching device carries the first response message corresponding to the first request message in the acknowledgement information for establishing the communication connection fed back to the first switching device.
  • the establishment of the communication connection between the first switching device and the second switching device may also be established when the switching device is deployed and installed. Since the switching device generally only performs service interaction with the switching device corresponding to the adjacent base station, since the first base station is adjacent to the second base station, the first switching device and the second switching device are deployed and installed in the corresponding base station.
  • the first switching device establishes a communication connection with the second switching device. After receiving the handover notification message, the first switching device queries the second switching device corresponding to the second base station according to the base station ID of the second base station in the handover notification message, thereby transmitting the second switching device to the second switching device. A request message.
  • the UE ID is used to uniquely identify the corresponding UE.
  • the UE ID may be in the form of an IP address of the UE, or may be in the form of a device identifier of the UE. That is, the UE ID of the target UE may be the IP address of the target UE, or the gateway side S1-U (English plane S1 interface) endpoint identifier of the target UE, or may be the device identifier of the target UE.
  • the UE ID may also be other types of information that can identify the corresponding UE, which is not limited in this application.
  • the second switching device returns a first response message to the first switching device.
  • the second switching device stores instance information deployed in the second MEC platform corresponding to the second base station. After receiving the first request message, the second switching device queries the second instance corresponding to the application service from the second MEC platform according to the service ID of the target application service, and acquires the instance ID of the second instance. The second switching device carries the ID of the second MEC platform and the instance ID of the second instance in the first response message, and returns to the first switching device. The first switching device receives the first response message, and further determines that the instance that provides the target application service on the target UE is to be switched to the second instance.
  • the first switching device sends a handover preparation message to the first MEC platform.
  • the first switching device sends a handover preparation message to the first MEC platform, where the handover preparation message carries the UE ID of the target UE, the service ID of the target application service, the ID of the second MEC platform, and the instance ID of the second instance.
  • the first MEC platform learns that the instance that provides the target application service for the target UE will switch to the second instance on the second MEC platform.
  • the first MEC platform may further send the handover preparation message to the second MEC platform, so that the second MEC platform also knows that the instance that provides the target application service for the target UE will be switched to the second instance.
  • Step 405 is an optional step, and only the instance that the first switching device notifies the first MEC platform to provide the target application service to the target UE will be switched to the second instance.
  • the first switching device notifying the first MEC platform to provide the target UE with the target application service to be switched to the second instance may also be implemented in other manners.
  • the communication network may also be provided with an application controller, as shown in any of Figures 1(a), 1(b) and 1(c).
  • the application controller is used to manage each MEC platform in the communication network, thereby controlling all applications in the communication network.
  • the application controller is a network device on the core network side, and the application controller is connected to each MEC platform in the communication network, and is used to send control information to each MEC platform.
  • the application controller is also connected to the network device on each base station side (for example, the network device may be a base station or a handover device), and is used to perform control decision of the application instance according to the needs of the user side, such as the cell-wide movement of the UE.
  • the first switching device may send a second request message to the application controller.
  • the second request message carries the service ID of the target application service and the location information of the target UE, and is used to request the application controller to return information of the new instance of the target application service.
  • the application controller determines that it is to access the second MEC platform according to the location information of the target UE, and the application controller cooperates with the second MEC platform to determine the second instance of the target application.
  • the second MEC platform also knows that the instance that provides the target application service for the target UE will switch to the second instance.
  • the target application service applies for the service that needs to be forwarded in the instance switching preparation phase, and the first switching device may also perform some handover preparation work.
  • the instance switching preparation phase refers to: before the target UE successfully accesses the second base station, the first switching device determines that the target UE provides the target application service instance to be switched to the second instance, and after the target UE accesses the second base station, The first switching device instructs the first MEC platform to perform a time period between instance switching.
  • the handover preparation process is: the first switching device generates a packet forwarding policy, and sends the packet forwarding policy to a corresponding forwarding device (for example, a gateway device), and the forwarding device completes the packet between the target UE and the instance. Forward work.
  • the packet forwarding policy is used to instruct the forwarding device to forward the uplink packet of the target UE to the second instance according to the packet forwarding policy, and forward the downlink packet of the second instance to the target UE.
  • the target UE can perform data interaction with the destination instance.
  • the target UE and the second instance of the target application service may perform data interaction.
  • the two parties establish a transmission control protocol (English: transmission control protocol, abbreviation: TCP) connection in advance. Therefore, the underlying link connection of the gateway corresponding to the second base station to the second base station needs to be established, that is, the low-level link connection is: the first gateway (the gateway corresponding to the first base station) - the second gateway (the second base station Corresponding gateway).
  • the underlying link connection forms a service forwarding tunnel. The establishment of the service forwarding tunnel is completed by the first gateway and the second gateway.
  • the first gateway sends the tunnel identifier of the first gateway to the second gateway, and the second gateway receives the first After the tunnel identifier of the gateway is sent, the tunnel identifier of the second gateway is sent to the first gateway.
  • the two gateways can identify the tunnel type and the tunnel identity, thereby establishing the service forwarding tunnel.
  • the packet that the target UE interacts with the target application service still performs service identification on the first gateway.
  • the first switching device sends the message forwarding policy to the first gateway.
  • the first switching device In order to enable the first gateway to identify the target packet sent to the second instance, and then forward the packet using the service forwarding tunnel, the first switching device further needs to create a service feature according to the instance ID of the second instance, and carry the service feature in the The packet forwarding policy is sent to the first gateway. After receiving the packet, the first gateway determines, according to the service feature, whether the packet is a packet that the target UE needs to send to the second instance.
  • the service feature may be a service flow feature for the target UE to perform packet interaction with the instance of the target application service.
  • the business feature can be a five-tuple information or a partial information in a five-tuple.
  • the quintuple information may include: an IP address of the target UE, an IP address of the second instance, a transmission protocol, a target port number, and a source port number.
  • the partial information in the quintuple may include the IP address and/or port number of the second instance.
  • the first gateway identifies the uplink service flow of the target UE and the second instance.
  • the identification mode is: determining whether the instance ID of the second instance is carried in the exchanged message, and if yes, indicating that the message is a message that the target UE interacts with the second instance, and if not, the report is The text is not a message that the target UE interacts with the second instance.
  • the target UE may send the information of the transport protocol used by the target UE to the first instance or the manner in which the context content is sent to the second instance through the service forwarding tunnel.
  • the processing of the second gateway is: the second gateway forwards the downlink service of the target UE to the first gateway by using the service forwarding tunnel, and the first gateway performs service identification and then forwards the packet to the first base station.
  • the UE is switched to the second base station, and the S1-U transmission channel of the UE of the second base station and the second gateway is established, the downlink service of the target UE is directly sent to the second base station.
  • the first MEC platform needs to obtain the instance ID of the second instance.
  • the instance ID (such as an IP address) of the second instance is sent to the target UE such that the target UE can perform data interaction with the second instance.
  • the uplink packet sent by the target UE may be forwarded to the second instance by using the service forwarding tunnel of the first gateway and the second gateway.
  • the target UE sends the uplink packet to the first gateway, when the packet is not forwarded to the first instance, and the target UE accesses the second base station and starts the instance switch, the packet is sent. Cannot be forwarded to the second instance and thus discarded.
  • the uplink packet sent by the target UE is not discarded due to the instance handover.
  • the first MEC platform cooperates with the second MEC platform for data synchronization preparation.
  • the first MEC platform After receiving the handover preparation message, the first MEC platform cooperates with the second MEC platform to prepare for data synchronization.
  • the data synchronization preparation may send part of the data to the second MEC platform for the first MEC platform, and after receiving the partial data, the second MEC platform updates the partial data to the second instance.
  • part of the data includes: a transmission protocol of the target UE with the first instance, or static context content.
  • step 405 the first switching device has completed the foregoing handover preparation work, and the first switching device may notify the first MEC platform, and the data synchronization preparation is not required to cooperate with the second MEC platform, and step 406 may be performed. Not executed.
  • the target UE accesses the second base station.
  • the target application service of the target UE is still supported by the first instance of the first MEC platform, so the target UE continues to maintain the air interface connection with the first base station.
  • the process of the target UE accessing the second base station is started.
  • the network side device simultaneously performs the determination of the destination instance and the handover preparation work for the instance handover that provides the target application service for the target UE. Even after the target UE accesses the second base station, the handover preparation work is still not completed.
  • the solution can be performed in advance by determining the destination instance and the manner of handover preparation to complete the instance handover.
  • the second base station After the target UE accesses the second base station, the second base station sends a notification message to the first base station.
  • the notification message indicates that the target UE has successfully accessed the second base station.
  • the notification message may also be sent by the target UE to the first base station.
  • the first base station sends a handover notification message to the first switching device.
  • the first base station After the target UE is handed over from the first base station to the second base station, the first base station sends a handover notification message to the first handover device.
  • the handover notification message carries the UE ID of the target UE.
  • the target UE After the target UE establishes a radio resource control (English: Radio Resource Control, abbreviated RRC) connection, the target UE or the second base station sends a notification message to the first base station.
  • the first base station After receiving the notification message, the first base station sends a handover notification message to the first switching device.
  • RRC Radio Resource Control
  • the first base station may receive the end marker message (indicating the last packet sent by the core network on the source side path) sent by the core network (indicating that the target UE has accessed the second base station), The first base station then sends a handover notification message to the first handover device.
  • the end marker message indicating the last packet sent by the core network on the source side path
  • the core network indicating that the target UE has accessed the second base station
  • the first switching device receives the end maker message sent by the core network before the first base station. At this time, the first switching device may directly perform step 410 without the first base station sending a handover notification message.
  • the first switching device sends a handover indication message to the first MEC platform.
  • the first switching device After receiving the handover notification message, the first switching device sends a handover indication message to the first MEC platform.
  • the first MEC platform receives the handover indication message.
  • the handover indication message carries the UE ID of the target UE, and is used to indicate that the first MEC platform handover provides an instance of the target application service to the target UE.
  • the first MEC platform cooperates with the second MEC platform to perform instance switching.
  • the first MEC platform After receiving the handover indication message, the first MEC platform cooperates with the second MEC platform to switch the target application on the target UE from the first instance to the second instance to complete data migration.
  • the data migration refers to that the first MEC platform sends all the data about the target UE in the first instance to the second MEC platform, and the second MEC platform updates the data to the second instance. It should be noted that, in the foregoing handover preparation phase, the target UE or the first MEC platform has updated part of the data to the second instance, in this step, the first MEC platform does not need to send the foregoing partial data to the second. In the MEC platform, this reduces the time for data migration.
  • the target UE releases the service connection with the first instance in the first MEC platform.
  • the instance to which the target UE provides the target application service is switched from the first instance to the second instance, and after the data migration is completed, the service connection with the first instance in the first MEC platform is released.
  • step 412 is an optional step.
  • the implementation described in step 412 is that when the first MEC platform and the second MEC platform cooperate to switch the instance, the target UE is notified to replace the address of the instance of the target application service with the address of the second instance. Therefore, the target UE needs to be according to the second instance.
  • the address establishes a service connection with the second instance and releases the service connection with the first instance.
  • the target UE does not sense that the address of the instance has been replaced, so the target UE may continue to perform service interaction with the first instance.
  • the exchanged message is forwarded by the network side to the second instance according to the address translation rule. Therefore, the target UE does not need to release the service connection with the first instance.
  • the target UE uses the service address of the target application service when accessing the target application service, and therefore, regardless of which instance of the target application service is replaced with the target UE, the service interaction is performed.
  • the target UE does not perceive the address translation of the instance, and still uses the service address of the target application service for service interaction. Therefore, the target UE does not perceive which instance to perform service interaction with, so that there is no step of the target UE releasing the service connection with the first instance.
  • the target UE may also remain connected and interact with the first instance before the data of the first instance is not completely migrated to the second instance. For example, the target UE performs a signaling interaction for releasing the TCP connection with the first instance; or, the target UE performs a small amount of service interaction with the first instance.
  • the first switching device notifies the second switching device of the service feature, and the second switching device sends the packet forwarding policy to the second gateway, where the packet forwarding policy includes the service feature.
  • the second gateway determines, according to the service feature, whether the received packet is a packet that the target UE interacts with the instance of the target application service.
  • the service feature may be a service flow feature that performs packet exchange between the target UE and an instance of the target application service.
  • it is quintuple information or partial information in a quintuple, wherein the quintuple information may include: an IP address of the target UE, an IP address of the first instance, a transmission protocol, a target port number, and a source port number.
  • the partial information in the quintuple may include the IP address of the first instance.
  • the second gateway For the uplink service with the first instance, the second gateway performs traffic flow identification.
  • the second gateway uses the packet forwarding policy sent by the second switching device to identify the uplink packet. If the uplink packet is the service packet sent by the target UE to the first instance, the second gateway forwards the packet to the first instance.
  • the forwarding process is performed by the first gateway.
  • the processing of the first gateway is: if the downlink S1-U of the first gateway and the first base station has been released, the downlink packet identified by the first gateway is forwarded to the second gateway, and then forwarded to the second gateway by the second gateway.
  • the base station is further forwarded to the target UE by the second base station; if the downlink S1-U of the first gateway and the first base station is not released yet, the base station directly forwards to the first base station, and then the first base station forwards to the target UE.
  • the first handover device before the first handover device sends the handover preparation message to the first MEC platform, it is determined that the first instance of the target application service for the target UE is to be switched to the second MEC platform.
  • the step of determining that the first instance of the target application service is to be switched to the second instance on the second MEC platform for the target UE may also be performed by the first MEC platform.
  • the first switching device does not send the instance ID of the second instance to the first MEC platform. Rather, the location information of the target UE is sent to the first MEC platform, and the instance in which the first MEC platform cooperates with the second MEC platform to determine that the target UE provides the target application service will be switched to the second instance.
  • steps 403 and 404 in the embodiment of FIG. 4 are optional steps, that is, the first switching device does not need to acquire the instance ID of the second instance.
  • the handover preparation message carries the UE ID of the target UE, the service ID of the target application service, and the location information of the target UE.
  • the first MEC platform determines the second MEC platform according to the location information of the target UE, and acquires the instance ID of the second instance according to the service ID of the target application service and the second MEC platform.
  • the second MEC platform also knows that the instance that provides the target application service for the target UE will switch to the second instance.
  • the UE ID here may be the same as or different from the UE ID described in step 402 in FIG. 4 .
  • the UE ID here is used to identify the identity between the switching device and the instance on the MEC platform, and generally refers to the UE ID in the form of an IP address.
  • the UE ID described in step 402 is used for the identifier between the switching device and the base station, and may be referred to by an IP address or by a device identifier or a device name.
  • the function of the switching device in the foregoing embodiment may also be combined with the core network device, that is, the core network device has the function of the foregoing switching device.
  • the detailed flow of another embodiment of the example switching method provided by the present application will be exemplarily described below with reference to FIG. 5.
  • the core network device in the embodiment of FIG. 5 may be a network device in a core network in any one of the communication networks as shown in FIG. 1(a) to FIG. 1(c).
  • the core network device of Fig. 5 has the functions of the switching device in the embodiment of Figs. 2 to 4.
  • the process description is as follows:
  • the first base station determines that the target UE is to be switched to the second base station.
  • step 401 in the embodiment of FIG. 4, and details are not described herein.
  • the first base station sends a preparation notification message to the core network device.
  • the first base station After confirming that the base station of the target UE is to be handed over, the first base station sends a preparation notification message to the core network device.
  • the core network device receives the preparation notification message.
  • the preparation notification message is used to notify the core network device that the target UE is to be accessed by the second base station to trigger an instance handover preparation process.
  • the preparation notification message includes a UE ID of the target UE and a base station ID of the second base station.
  • the preparation notification message may also be sent by the second base station to the core network device. If the second base station receives the handover request sent by the first base station, the second base station may send the preparation notification message to the core network device when confirming that the target UE can access the second base station.
  • the core network device sends a handover preparation message to the first MEC platform.
  • the first MEC platform receives the handover preparation message sent by the core network device.
  • the core network device sends a handover preparation message to the first MEC platform, where the handover preparation message carries the UE ID of the target UE, and the instance ID of the second instance of the target application service, to indicate that the first MEC platform provides the target for the target UE.
  • the instance of the application service will switch to the second instance.
  • the target application service applies for the service that needs to be forwarded in the instance switching preparation phase.
  • the core network device can also generate a packet forwarding policy and send the packet forwarding policy to the corresponding forwarding device (for example, a gateway device), and the forwarding device completes the target UE and the instance.
  • a forwarding device for example, a gateway device
  • the forwarding device completes the target UE and the instance.
  • the detailed execution content is similar to that described in step 405 in the embodiment of FIG. 4. For example, the establishment of the service forwarding tunnel is still established by the first gateway and the second gateway, and the functions and operations of the first switching device are implemented by the core network device. I will not repeat them here.
  • the first MEC platform cooperates with the second MEC platform for data synchronization preparation.
  • step 406 in the embodiment of FIG. 4, and details are not described herein.
  • the target UE accesses the second base station.
  • step 407 in the embodiment of FIG. 4, and details are not described herein.
  • the second base station sends a notification message to the core network device, where the notification message indicates that the target UE has accessed the second base station.
  • the core network device sends a handover indication message to the first MEC platform.
  • the core network device After detecting that the target UE accesses the second base station, the core network device sends a handover indication message to the first MEC platform.
  • the first MEC platform receives the handover indication message.
  • the handover indication message carries the UE ID of the target UE, and is used to indicate that the first MEC platform switches the instance of the target application service of the target UE.
  • the first MEC platform cooperates with the second MEC platform to perform instance switching.
  • step 411 in the embodiment of FIG. 4, and details are not described herein.
  • the target UE releases the service connection with the first instance in the first ME platform.
  • step 412 in the embodiment of FIG. 4, and details are not described herein.
  • the core network device may also separately generate an application controller for centralized management of the first MEC platform and the second MEC platform.
  • the signaling interaction between the core network device and the first MEC platform and the second MEC platform needs to be forwarded by the application controller.
  • the handover preparation message in step 503 in the embodiment of FIG. 5 may be the UE ID of the target UE and the location information of the target UE. So that the application controller determines the second MEC platform that the target UE is to access according to the location information of the target UE, thereby determining the instance ID of the second instance.
  • Other processing procedures are similar to the embodiment of FIG. 5, and are not described herein.
  • the core network device may also be configured with a separate proxy network element on each MEC platform. In this way, when the MEC platform needs to send signaling to the core network device, it only needs to perform local interaction.
  • FIG. 6 is an embodiment of a switching device according to an embodiment of the present disclosure.
  • the switching device is the first switching device in any of the embodiments of FIG. 2 to FIG.
  • a determining unit 601 configured to determine, on the first mobile edge MEC platform that provides the target application service for the target UE, before the target user equipment UE moves to the cell range of the second base station and successfully accesses the second base station
  • the first instance is to be switched to the second instance on the second MEC platform, where the target UE is a UE accessing the first base station, and the first MEC platform is used to be a UE in the cell of the first base station Providing the target application service, where the second MEC platform is configured to provide the target application service for a UE in the second base station cell;
  • the notifying unit 602 is configured to notify the first MEC platform before the target UE successfully accesses the second base station: the first instance that provides the target application service for the target UE will be switched to Said second example;
  • the indicating unit 603, configured to: after the target UE successfully accesses the second base station, the indication that the first MEC platform: the first instance that provides the target UE with the target application service is switched to the Said second instance on the second MEC platform.
  • the determining unit 601 is specifically configured to:
  • the UE of the second base station provides an instance handover service; the service ID of the target application service is associated with the second instance of the second MEC platform;
  • the instance ID of the second instance it is determined that the first instance on the first MEC platform that provides the target application service for the target UE is to be switched to the second instance on the second MEC platform.
  • the notification unit 602 is specifically configured to:
  • the handover preparation message carries a UE identity ID of the target UE and an instance ID of the second instance.
  • the device further includes:
  • the receiving unit 604 is configured to: before the indicating unit indicates the first MEC platform, receive a handover notification message from the first base station, where the handover notification message carries a UE ID of the target UE, and the handover notification The message is used to indicate that the target UE has successfully accessed the second base station.
  • the device further includes:
  • a creating unit 605, configured to create a service feature according to the instance ID of the second instance
  • the sending unit 606 is configured to send a packet forwarding policy to the first gateway, where the packet forwarding policy is used to indicate that the first gateway: identifies a target uplink packet according to the service feature, and sends the target uplink packet Forwarding to the second gateway, where the target uplink packet is an uplink packet that the target UE interacts with the target application service, where the first gateway is configured to provide a service service for the first base station, The second gateway is configured to provide a service service for the second base station.
  • the components described in the embodiment of FIG. 6 can also perform the steps performed by the first switching device in any of the embodiments of FIG. 2 to FIG. 5, and the details can be referred to the embodiment of FIG. 2 to FIG. 5, and details are not described herein. .
  • the example switching system includes: a first base station, a first moving edge.
  • the MEC platform, the second base station, the second MEC platform, the first switching device, and the second switching device where the first MEC platform is configured to provide the target application service for the UE in the first base station cell, where The second MEC platform is used by the UE in the second base station cell to provide the target application service, and the first switching device is configured to provide an instance handover service for the UE connected to the first base station, where the second switching device
  • the processor 701 includes a processor 701, a memory 702, a transceiver 703, the processor 701, the memory 702, and the transceiver.
  • the 703 is coupled by a bus 704, which may include a transmitter and a receiver, the memory 702 storing computer instructions for implementing the computer instructions for implementing any of the embodiments of FIGS. 2 through 5.
  • the function of the instance switching method may adopt various flexible design manners, and the corresponding functions of the respective devices may be further referred to the foregoing method embodiments, and the application is not limited.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • wire eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be stored by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).
  • the disclosed system, apparatus, and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application, in essence or the contribution to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • a computer device which may be a personal computer, server, or network device, etc.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read only memory (English full name: read-only memory, abbreviated: ROM), a random access memory (English full name: random access memory, shorthand: RAM), a disk or A variety of media such as optical discs that can store program code.

Abstract

本申请实施例公开了一种实例切换方法，包括：在目标用户设备UE移动至第二基站的小区范围内，且成功接入第二基站前，第一切换装置确定为目标UE提供目标应用服务的第一移动边缘MEC平台上的第一实例待切换为第二MEC平台上的第二实例，在目标UE成功接入第二基站前，第一切换装置通知第一MEC平台：为目标UE提供目标应用服务的第一实例将切换为第二实例。目标UE在未成功接入第二基站时，第一MEC平台获知了为目标UE提供目标应用服务的实例将切换为第二MEC平台上的第二实例。从而在后续的实例切换时，无需进行MEC平台的查找以及第二实例的查找过程，从而减少了业务的中断时间，提高了用户体验。

Description

实例切换方法及相关装置
本申请要求于2017年08月31日提交中国专利局、申请号为201710777786.1、申请名称为“实例切换方法及相关装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种实例切换方法及相关装置。
背景技术
无线通信网络的建设是以数据中心(英文：data center)为中心的。各数据中心使用分布式云(英文：cloud)技术进行管理，形成边缘云(英文：edge cloud)加中心云(英文：central cloud)的分级网络系统。数据中心为用户设备(英文：user equipment，缩写：UE)提供应用服务的应用实例(以下简称为实例)部署在各边缘云上，使得应用服务的实例部署到更靠近UE的位置，减少了服务时延，提高服务体验。
现有技术中，目标UE原本接入第一基站，并由第一移动边缘平台(英文：mobile edge platform)上所部署的第一实例来提供目标UE的服务。移动边缘平台又称MEC平台。当目标UE从第一基站的小区移动到第二基站的小区范围内时，目标UE的从第一基站切换到第二基站，为目标UE提供服务的实例也需要切换为第二MEC平台上所部署的第二实例。
现阶段的切换方法为：第一基站在确定目标UE切换至第二基站时，第一基站指示第一MEC平台进行实例切换，第一MEC平台则将第一实例的状态内容发送至第二MEC平台上的第二实例中。在实例切换过程中，目标UE无法进行正常的业务，由于切换过程时间花费较长，影响了用户对业务的服务连续性的体验。
发明内容
本申请实施例提供了一种实例切换方法及相关装置，用于减少实例切换的花费时间，提供用户的体验。
第一方面，本申请实施例提供一种实例切换方法，包括：
在接入第一基站的目标用户设备UE移动至第二基站的小区范围内，且成功接入第二基站前，第一切换装置确定为目标UE提供目标应用服务的第一移动边缘MEC平台上的第一实例待切换为第二MEC平台上的第二实例，其中，第一MEC平台和第二MEC平台分别用于为第一基站的小区内的UE和第二基站的小区内的UE提供目标应用服务。目标应用服务为目标UE所接入的应用服务。在目标UE成功接入所述第二基站前，第一切换装置通知第一MEC平台：为目标UE提供目标应用服务的第一实例将切换为第二实例。在目标UE成功接入第二基站后，第一切换装置指示第一MEC平台：将为目标UE提供目标应用服务的第一实例切换为第二MEC平台上的第二实例。
在目标UE进入第二基站的小区范围内，但尚未成功接入第二基站时，第一MEC平台则获知了为目标UE提供目标应用服务的实例将切换为第二MEC平台上的第二实例。现有技术方案中，当目标UE接入第二基站后，在进行实例切换时，网络侧设备才开始为该目标UE查找为目标UE提供目标应用服务的实例待切换为哪个MEC平台哪个实例。而通过本申请实 施例上述的方法，目标UE在未接入第二基站时，第一MEC平台获知了为目标UE提供目标应用服务的实例将切换为第二MEC平台上的第二实例。从而在后续的实例切换时，无需进行MEC平台的查找以及第二实例的查找过程，从而减少了业务的中断时间，提高了用户体验。
一种可能的实现方式中，第一切换装置确定为所述目标UE提供目标应用服务的第一MEC平台上的第一实例待切换为第二MEC平台上的第二实例，可以包括：
第一切换装置从第一基站获取目标UE的位置信息，再根据目标UE的位置信息确定第二切换装置，并向第二切换装置发送包括目标应用服务的服务标识ID的第一请求消息，其中，第二切换装置用于为连接第二基站的UE提供实例的切换服务，目标应用服务的服务ID与第二MEC平台的第二实例关联。第一切换装置从第二切换装置接收携带有第二实例的实例ID的第一响应消息，第一切换装置根据第二实例的实例ID，确定所述目标UE提供目标应用服务的第一MEC平台上的第一实例待切换为第二MEC平台上的第二实例。
第一切换装置在通知第一MEC平台之前，从第二切换装置获取了第二实例的实例ID，从而确定了为目标UE提供目标应用服务的实例待切换为第二实例。第一切换装置在通知第一MEC平台进行切换准备时，则可以将第二实例的实例ID告知第一MEC平台，第一MEC平台则可以通过第二实例的实例ID确定为目标UE提供目标应用服务的实例将切换为第二MEC平台上的第二实例。第一MEC平台则无需向第二MEC平台获取第二实例的实例ID，减少了第一MEC平台的信令交互，从而减少了第一MEC平台的负担。
另一种可能的实现方式中，该方法还包括：
第一切换装置根据第二实例的实例ID创建业务特征，并向第一网关发送该报文转发策略，该报文转发策略包括业务特征，报文转发策略用于指示第一网关：根据业务特征识别目标上行报文，并将目标上行报文转发至第二网关，目标上行报文为目标UE与目标应用服务交互的上行报文；其中，第一网关用于为第一基站提供业务服务，第二网关用于为第二基站提供业务服务。
第一网关与第二网关建立有业务转发隧道，当第一网关接收到该报文转发策略后，目标UE可以将目标UE与第一实例连接所使用的传输协议的信息或者上下文内容以上行报文的方式通过该业务转发隧道发送至第二实例。在实例切换准备阶段，目标UE发送的上行报文则可以通过第一网关与第二网关的业务转发隧道转发至第二实例。而现有技术中，若目标UE发送上行报文至第一网关后，当该报文还未转发至第一实例时，目标UE则接入第二基站并开始实例切换时，那么该报文无法被转发至第二实例，从而被丢弃。通过本申请方案，目标UE发送的上行报文不会由于实例切换的原因而被丢弃。
第二方面，本申请实施例提供一种实例切换方法，包括：
在接入第一基站的目标用户设备UE移动至第二基站的小区范围内，且成功接入第二基站前，第一切换装置确定为目标UE提供目标应用服务的实例待切换。其中，第一MEC平台用于为第一基站的小区内的UE提供目标应用服务，目标应用服务为目标UE所接入的应用服务。在目标UE成功接入所述第二基站前，第一切换装置通知第一MEC平台：为目标UE提供目标应用服务的实例将切换。在目标UE成功接入第二基站后，第一切换装置指示第一 MEC平台：将为目标UE提供目标应用服务的实例进行切换。
与第一方面所提供的实例切换方法不同，本方面实施例中，第一切换装置只确定了为目标UE提供目标应用服务的实例待切换，从而通知第一MEC平台，第一MEC平台接收到该通知后，则协同第二基站侧的网络设备获取目的实例的实例ID，进而确定为目标UE提供目标应用服务的实例待切换为第二MEC平台的第二实例。这样，第一切换装置只确定为目标UE提供目标应用服务的实例待切换，而确定第二实例的步骤由第一MEC平台执行，提高网络侧设备的资源利用率，减少了第一切换装置的负担。
第四方面，本申请实施例提供一种切换装置，该切换装置如第一方面的第一切换装置，该装置包括：
确定单元，用于在目标用户设备UE移动至第二基站的小区范围内，且成功接入第二基站前，确定为目标UE提供目标应用服务的第一移动边缘MEC平台上的第一实例待切换为第二MEC平台上的第二实例，其中目标UE为接入第一基站的UE，第一MEC平台用于为第一基站的小区内的UE提供目标应用服务，第二MEC平台用于为第二基站小区内的UE提供目标应用服务。
通知单元，用于在目标UE成功接入第二基站前，通知第一MEC平台：为目标UE提供目标应用服务的第一实例将切换为第二实例。
指示单元，用于在目标UE成功接入第二基站后，指示第一MEC平台：将为目标UE提供目标应用服务的第一实例切换为第二MEC平台上的第二实例。
第五方面，本申请实施例提供一种实例切换系统，适用于移动通信网络，其特征在于，该实例切换系统包括：第一基站、第一移动边缘MEC平台、第二基站、第二MEC平台、第一切换装置以及第二切换装置；其中，第一MEC平台用于为第一基站小区内的UE提供目标应用服务，第二MEC平台用于第二基站小区内的UE提供目标应用服务，第一切换装置用于为连接第一基站的UE提供实例的切换服务，第二切换装置用于为连接第二基站的UE提供实例的切换服务；其中，第一切换装置如第三方面所描述的第一切换装置。
第六方面，本申请提供了一种实例切换装置，包括：处理器、存储器、收发器，处理器、存储器以及收发器通过总线连接，存储器存储有计算机指令，处理器通过执行计算机指令用于实现如第一方面或第二方面所描述的方法。
第七方面，本申请提供了一种可读存储介质，该存储介质存储有用于实现如第一方面或第二方面所描述的方法的计算机指令。
第八方面，本申请提供了一种计算机程序产品，该计算机程序产品包括计算机软件指令，该计算机软件指令可通过处理器进行加载来实现如第一方面或第二方面所描述的方法中的流程。
第九方面，本申请提供了一种芯片系统，该芯片系统包括处理器，用于支持应用实例地址的转换装置实现上述方面中所涉及的功能，例如，生成或处理上述方法中所涉及的信息。在一种可能的设计中，芯片系统还包括存储器，该存储器，用于保存支持应用实例地址的转换装置必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
第十方面，本申请实施例提供一种通信装置，该通信装置可以包括终端设备或者芯片等实体，所述通信装置包括：处理器、存储器；存储器用于存储指令；处理器用于执行存储器中的指令，使得通信装置执行如前述第一方面或第二方面中任一项所述的方法。
附图说明
图1(a)为本申请实施例中通信网络架构的一个示意图；
图1(b)为本申请实施例中通信网络架构的另一示意图；
图1(c)为本申请实施例中通信网络架构的另一示意图；
图2为本申请实施例中实例切换的一个实施例示意图；
图3为本申请实施例中实例切换的另一实施例示意图；
图4为本申请实施例中实例切换的另一实施例示意图；
图5为本申请实施例中实例切换的另一实施例示意图；
图6为本申请实施例中切换装置的一个实施例示意图；
图7为本申请实施例中切换装置的另一实施例示意图。
具体实施方式
本申请实施例提供了一种实例切换方法，可以较快完成切换为目标UE提供应用服务的实例。本申请还提出了相关的切换装置，以下将分别进行说明。
本申请所涉及的通信网络的基本架构请参阅图1(a)，包括：核心网(英文：corenetwork，缩写：CN)设备、第一基站、第二基站、第一MEC平台、以及第二MEC平台。其中，各MEC平台通过网关与对应的基站相连，各基站与核心网设备相连。
MEC平台是一种移动边缘的基础设施，例如，可以由一个或多个服务器组成，或者由一个或多个服务器与其它网络设备(比如网关、交换机等设备)组成，所组成的网络架构形成的网络资源用于给实例提供服务平台。每个MEC平台中部署有至少一个实例，该实例用于为UE提供应用服务。在本申请实施例中，应用服务指：通过各个类型的应用为终端提供的服务，比如某个开发商所运营的车辆网应用服务。而实例指的是一个应用服务部署在不同的MEC平台上的具体的应用。因此，一个应用服务可以对应多个实例。本申请中，第一MEC平台部署有第一实例，第二MEC平台部署有第二实例，其中，第一实例与第二实例为同一应用服务的实例。
图1(a)所示的通信网络可以扩展出多种变形。举例来说，可以对核心网进行控制面(英文：control plane，缩写：CP)和用户面(英文：user plane，缩写：UP)的划分，形成控制与用户面分离(英文：control and user plane separation，缩写：CUPS)通信网络，如图1(b)所示。其中，设备CN-CP表示核心网设备只包含控制面功能。而核心网的用户面由各网关实现，即各网关属于核心网侧设备，执行核心网的用户面功能。网关与基站的数据连接由核心网控制面统一管控。
本申请所涉及的基站(包括第一基站、第二基站)为新无线接入基站(英文：new radio gNB，缩写：NR gNB)或其它无线接入设备，本申请中不做限定。
可选的，本申请中的基站还可以进行集中式单元(英文：centralized unit，缩写：CU)和分布式单元(英文：distributed unit，缩写：DU)的切分，如图1(c)所示。在这种网络架构下，基站数据面的信息交互功能由DU实现，控制面的管理功能则需要通过CU实现。
本申请中的应用服务的实例分布式地部署在基站附近的多个MEC平台上，用于为其相连基站的小区内的UE提供应用服务。举例来说，超高可靠低时延(英文：ultra reliableand low latency communication，缩写：URLLC)应用的实例会被部署在多个靠近基站的MEC平台上。每个MEC平台上所部署的URLLC实例分别为UE提供URLLC服务。
MEC平台中可以记载有各应用服务对应的标识(英文：identification，缩写：ID)。应用服务ID(以下简称为服务ID)用于唯一标识对应的应用服务，以将不同的应用服务区分开。服务ID可以是域名(英文：domain name)的形式，或者，也可以由MEC平台统一为每个应用服务分配服务ID，比如服务ID可以为网络协议(英文：Internet Protocol，简写：IP)地址。服务ID也可以是其它的形式，本申请中不做限定。
每个应用服务的实例还具有实例ID。实例ID用于唯一标识对应的实例，以将同一应用服务的不同实例区分开。即，同一应用服务的不同实例，其服务ID相同，但实例ID不同。实例ID可以是实例的IP地址的形式，也可以是其它的形式，本申请中不做限定。需要说明的是，当服务ID与实例ID均为IP地址形式时，发送端或接收端可通过报文中的不同字段对两者进行区分。比如，发送端与接收端互相约定报文的第一个字段为服务ID，第二个字段为实例ID，发送端在向接收端发送报文时，在该报文的第一个字段设置的是应用服务的IP地址，在该报文的第二个字段设置的是实例的IP地址。接收端接收到该报文后，则能够从相应的字段中解析出应用服务的IP地址以及实例的IP地址。
在图1(a)～(c)的基础上，本申请还向通信网络中引入了切换装置。每个切换装置均对应有一个或多个基站，例如第一切换装置对应第一基站，第二切换装置对应第二基站。每个切换装置用于：根据目标UE移动的位置协同相应的MEC平台切换为UE提供应用服务的实例。
本申请中不限定切换装置在通信网络中的地位。切换装置可以是独立的设备，也可以和基站、网关、核心网设备等网络设备中的一项设置在一起，还可以以功能模块的形式设置在基站、网关、核心网设备等网络设备中，或是可以直接由基站、网关、核心网设备来实现。切换装置也可以为其它的形式，本申请中不做限定。
基于该切换装置，本申请提供了一种实例切换方法，在目标UE从第一基站的小区移动到第二基站的小区范围内时，该切换装置切换为目标UE提供应用服务的实例。其流程请参阅图2。
在流程开始前，目标UE处于第一基站的小区范围内并接入第一基站。目标UE连接目标应用服务的第一实例。当目标UE移动到第二基站的小区范围内时，启动本实施例提供的流程。
201、第一切换装置确定为目标UE提供目标应用服务的第一MEC平台上的第一实例待切换为第二MEC平台上的第二实例。
在目标UE移动至第二基站小区范围内，成功接入第二基站前，第一切换装置确定：为目标UE提供目标应用服务的第一MEC平台上的第一实例待切换为第二MEC平台上的第二实例。目标UE从第一基站的小区范围移动至第二基站的小区范围内时，第一切换装置启动确定为目标UE提供目标应用服务的实例待切换为第二MEC平台上的第二实例的流程，同时，目标UE也启动接入第二基站的流程。由于目标UE从开始接入第二基站至完成接入第二基站需要花费一定的时间，因此，第一切换装置启动确定为目标UE提供目标应用服务的实例待切换为第二MEC平台上的第二实例的流程是在目标UE成功接入第二基站之前进行。
其中，第一切换装置可以通过多种方式确定为目标UE提供目标应用服务的实例待切换。例如，第一基站确定目标UE待切换至第二基站时，告知第一切换装置，进而第一切换装置确定为目标UE提供目标应用服务的实例待切换。或者，第一切换装置可以根据目标UE的位置信息，确定目标UE进入第二基站小区范围，进而确定为目标UE提供目标应用服务的实例待切换。第一切换装置也可以通过别的方法确定为目标UE提供目标应用服务的实例待切换，此处不做限定。
第一切换装置可以通过多种方式确定为目标UE提供目标应用服务的实例待切换为第二MEC平台上的第二实例。
例如，在一种可能的实现方式中，第一切换装置存储有第一基站与第一MEC平台的对应关系，且第一切换装置具备获取接入第一基站的UE的状态信息的能力。当目标UE接入第一基站，以及目标UE接入目标应用服务的第一实例时，第一切换装置则获取了目标UE的UE ID、目标应用服务的服务ID以及第一实例的实例ID。例如，第一切换装置存储有多个其它基站侧的网络设备的ID和多个其它基站侧的网络设备之间的服务对应关系，其中，该多个其它基站与第一基站相邻，多个其它基站侧的网络设备的ID包括第二基站的ID、第二切换装置的ID，个其它基站侧的网络设备之间的服务对应关系包括第二基站与第二切换装置的服务对应关系。当目标UE移动至第二基站的小区范围内时，第一基站获取到目标UE发送的测量报告，第一基站将该测量报告中的目标UE的位置信息发送给第一切换装置。第一切换装置可以根据目标UE的位置信息，确定目标UE进入第二基站的小区范围，第一切换装置则将该目标应用服务的服务ID发送给第二基站侧的网络设备(比如，第二基站侧的网络设备为第二基站或第二切换装置)。第二基站侧的网络设备则根据该服务ID从所对应的第二MEC平台上获取到第二实例的实例ID，进而将该第二实例的实例ID反馈给第一切换装置。若第二基站对应有多个MEC平台，第二基站侧的网络设备还需将该第二实例所对应的MEC平台的ID反馈给第一切换装置。若第二基站只对应一个MEC平台，由于第一切换装置存储有多个其它基站与其所服务的MEC平台的对应关系，多个其它基站与第一基站相邻且多个其它基站中包含第二基站，那么第一切换装置能够通过第二基站确定该唯一的第二MEC平台。第一切换装置在接收到第二实例的实例ID后，则能确定为目标UE提供目标应用服务的第一实例待切换为第二基站对应的第二MEC平台所提供的第二实例。
在另一种可能的实现方式中，第一基站根据UE的位置信息确定目标UE待切换为第二基站时，将第二基站的ID告知第一切换装置，进而第一切换装置确定为目标UE提供目标应用服务的第一实例待切换为第二基站对应的第二MEC平台所提供的第二实例(与前一种 实现方式中论述的确定方式类似，此处不做赘述)。
第一切换装置也可以通过其它方法确定为目标UE提供目标应用服务的第一实例待切换为第二MEC平台上的第二实例，此处不做限定。
其中，目标UE的位置信息的形式有多种，例如可以为第二基站的基站ID或第二基站对应小区的小区ID，也可以是第二基站对应网关的网关ID，也可以是目标UE的地理位置信息，或者，也可以是第二MEC平台的ID等，此处不做限定。
202、第一切换装置通知第一MEC平台：为目标UE提供目标应用服务的第一实例将切换为第二实例。
在目标UE成功接入第二基站前，第一切换装置通知第一MEC平台：为目标UE提供目标应用服务的第一实例将切换为第二实例。例如，第一切换装置向第一MEC平台发送切换准备消息。该切换准备消息包含目标UE的UE ID、目标应用服务的服务ID、第二MEC平台的ID以及第二实例的实例ID。第一MEC平台接收到该切换准备消息后，第一MEC平台则获知为目标UE提供目标应用服务的实例将切换为第二MEC平台上的第二实例。
可选的，第一MEC平台还可以将该切换准备消息转发给第二MEC平台，则第二MEC平台也获知了为目标UE提供目标应用服务的实例将切换为第二MEC平台上的第二实例。或者，第一切换装置在通过第二基站侧的网络设备获取第二实例的实例ID过程中，第二基站侧的网络设备在获取到第二MEC平台的第二实例的实例ID后，则通知第二MEC平台：为目标UE提供目标应用服务的实例将切换为第二MEC平台上的第二实例。这样，在目标UE进入第二基站的小区范围内，成功接入第二基站前，第一MEC平台与第二MEC平台均获知了为目标UE提供目标应用服务的实例将切换为第二MEC平台上的第二实例。现有技术方案中，当目标UE接入第二基站后，在进行实例切换时，网络侧设备才开始为该目标UE查找为目标UE提供目标应用服务的实例待切换为哪个MEC平台哪个实例。在实例切换时，目标UE是无法与实例进行正常的业务工作的，从而影响了用户对业务的服务的连续性的体验。而通过本实施例上述的方法，目标UE在成功接入第二基站前，第一MEC平台与第二MEC平台均获知了为目标UE提供目标应用服务的实例将切换为第二MEC平台上的第二实例。从而在后续的实例切换时，无需进行MEC平台的查找以及第二实例的查找过程，从而减少了业务的中断时间，提高了用户体验。
可选的，第一MEC平台接收到该切换准备消息后，还可以根据该切换准备消息的指示，协同第二MEC平台进行切换准备工作。例如，第一MEC平台可以将第一实例上目标UE的部分数据发送给第二MEC平台。比如，部分数据包括：目标UE与第一实例的传输协议，或者静态的上下文内容。该切换准备工作并不能完成第一实例与第二实例之间的所有数据迁移，而是将如前述的传输协议等信息或静态类的上下文内容提前更新至第二实例上。在后续步骤中，第一MEC平台协同第二MEC平台进行实例切换时，第一实例中的所有与目标UE相关的数据才会全部更新至第二实例中。第一MEC平台也可以通过其它方法来协同第二MEC平台进行切换准备工作，本申请中不做限定。
在目标UE成功接入第二基站之前，第一MEC平台则协同第二MEC平台将第一实例中有关目标UE的部分数据更新至第二实例中，这样，在后续的实例切换过程中，已经更新至第 二实例中的部分数据则无需再次发送，从而减少了实例切换的时间。
需要说明的是，第一切换装置确定为目标UE提供目标应用服务的第一MEC平台上的第一实例待切换为第二MEC平台上的第二实例、第一切换装置向第一MEC平台发送切换准备消息以及第一MEC平台协同第二MEC平台进行切换准备的流程，与目标UE接入第二基站的流程是可以在同时间段内同时进行。即，第一切换装置确定为目标UE提供目标应用服务的第一MEC平台上的第一实例待切换为第二MEC平台上的第二实例、第一切换装置向第一MEC平台发送切换准备消息以及第一MEC平台协同第二MEC平台进行切换准备的流程，与目标UE接入第二基站的流程互相不影响。在目标UE进入第二基站的小区范围内时，同时触发第一切换装置确定为目标UE提供目标应用服务的第一MEC平台上的第一实例待切换为第二MEC平台上的第二实例的步骤，以及目标UE接入第二基站的流程步骤。
由于现有的UE接入基站的时间大概为50ms，而第一切换装置确定为目标UE提供目标应用服务的第一MEC平台上的第一实例待切换为第二MEC平台上的第二实例、第一切换装置向第一MEC平台发送切换准备消息以及第一MEC平台协同第二MEC平台进行切换准备的流程所花费的时间远远小于50ms(网络异常的情况除外)。因此，从目标UE开始接入第二基站至目标UE接入第二基站完成的这段时间内，第一切换装置确定为目标UE提供目标应用服务的第一MEC平台上的第一实例待切换为第二MEC平台上的第二实例、第一切换装置向第一MEC平台发送切换准备消息以及第一MEC平台协同第二MEC平台进行切换准备的流程已经完成，而且完成所花费的时间小于目标UE接入第二基站所花费的时间。
对于未来5G低时延的业务，空口会采用双连接的方式，即在目标UE接入第二基站的同时，保持与第一基站的连接不中断，此为双连接技术。也就是说，目标UE在接入第二基站后，目标UE保持与第一基站的空口连接，并且目标UE保持与第一MEC平台上第一实例的业务连接。为了便于理解，下面对本实施例方案的花费时间进行举例说明：
例如，在现有方案中，目标UE接入第二基站的需要花费的时间为50ms，现有技术中实例切换(包括确定第二实例以及实例之间数据同步)需要花费的时间为30ms，其中确定第二实例花费的时间为20ms，进行实例之间数据同步花费的时间为10ms。若不基于双连接技术，即，目标UE先接入第二基站，再进行实例切换。那么，目标UE从切换第二基站至完成实例切换需要花费的总时间至少为80ms。用户侧所感知的业务断开时间为80ms，因为目标UE断开与第一基站的连接，目标UE无法与第一基站侧的第一实例进行正常业务。在目标UE接入第二基站后，在进行实例切换的过程中，目标UE还无法与第二基站侧的第二实例进行正常业务。即使基于双连接技术，目标UE从切换第二基站至完成实例切换需要花费的总时间仍然至少为80ms，对于用户侧而言，用户侧能够感知到的业务断开时长为30ms，因为在目标UE接入第二基站的50ms时间段内，目标UE仍可以与第一基站侧的第一实例进行正常业务，而在目标UE接入第二基站后，进行实例切换时UE无法进行正常业务。
而基于本申请方案，目标UE在接入第二基站的同时段中，则进行目标实例查找，即，完成了第二实例的确定。那么目标UE接入第二基站与网络侧设备(比如为第一MEC平台)确定第二实例总共所花费的时间只需50ms(因为网络侧设备确定第二实例是在目标UE接入第二基站的时间段内完成的，该50ms时间段内，用户侧不会感知业务断开，因为目标 UE仍可以与第一基站侧的第一实例进行正常业务)。实例切换中数据同步需要花费的时间10ms。因此，基于本申请方案，目标UE从切换第二基站至完成实例切换需要花费的总时间可以至少为60ms。其中，实例切换的时间为10ms。对于用户侧而言，用户侧能够感知到的业务断开时长为10ms。因此，本申请方案相对于现有技术方案能够更快的完成实例切换，且缩短了业务中断的时间，提升了应用服务的连续性。
203、第一切换装置通知第一MEC平台：为目标UE提供目标应用服务的第一实例切换为第二实例。
在目标UE接入第二基站后，第一切换装置向第一MEC平台发送切换指示消息，该切换指示消息用于指示第一MEC平台：为目标UE提供目标应用服务的第一实例切换为第二实例。
第一MEC平台接收到该切换指示消息后，协同第二MEC平台，将为目标UE上提供目标服务的第一实例切换为第二实例。比如，第一MEC平台将第一实例的有关该目标UE的信息和数据发送给第二MEC平台，第二MEC平台将接收到的信息和数据导入第二实例中，从而完成第二实例的信息和数据的更新。其中，该信息包括目标UE与第一实例进行数据传输所使用的传输协议以及目标UE的IP地址等信息，该数据包括目标UE与第一实例进行业务的上下文内容等数据。需要说明的是，若在实例切换之前，第一MEC平台与第二MEC平台已经协同将第一实例中的部分数据(比如传输协议和静态上下文内容)已经更新至第二实例中，则在该步骤中，第一MEC平台则无需将上述部分数据发送至第二MEC平台，从而减少了实例切换的时间。
值得指出的是，由于步骤202中第一MEC平台已经完成了对第二实例的确定，以及与第二MEC平台的切换准备，故本步骤中的实例切换要比现有技术更加快捷。这样目标UE接入了第二基站，并与第二MEC平台提供的目标应用服务的第二实例进行数据交互，实现了为目标UE提供目标应用服务的实例的快速切换。
图2实施例所描述的方案中，第一切换装置在向第一MEC平台发送切换准备消息之前，已经确定了为目标UE提供目标应用服务的第一实例待切换为第二MEC平台上的第二实例。可选的，确定为目标UE提供目标应用服务的第一实例待切换为第二MEC平台上的第二实例的步骤也可以由第一MEC平台执行。下面将结合图3，对本申请提供的实例切换方法的另一个实施例的流程进行示例性的介绍。
301、第一切换装置确定为目标UE提供目标应用服务的实例待切换。
第一切换装置确定为目标UE提供目标应用服务的实例待切换的方式如图2实施例中步骤201所述，此处不做赘述。与步骤201区别的是，在该步骤中，第一切换装置只确定为目标UE提供目标应用服务的实例待切换，而并不确定为目标UE提供目标应用服务的实例待切换为第二MEC平台上的第二实例。
302、第一切换装置通知第一MEC平台：为目标UE提供目标应用服务的实例将切换。
在目标UE成功接入第二基站前，第一切换装置向第一MEC平台发送切换准备消息。该切换准备消息包含目标UE的UE ID、目标应用服务的服务ID以及目标UE的位置信息。
第一MEC平台则根据目标UE的位置信息确定第二MEC平台，第一MEC平台将目标应用服务的服务ID发送给第二MEC平台，第二MEC平台再根据目标应用服务的服务ID查询到 该目标应用服务所对应的第二实例，并获取第二实例的实例ID。在该协同过程中，第二MEC平台也获知了为目标UE提供目标应用服务的实例将切换为本地上的第二实例。
303、第一切换装置通知第一MEC平台：将为目标UE提供目标应用服务的实例进行切换。
详细内容参照图2实施例中步骤203，此处不做赘述。
与图2实施例所提供的实例切换方法不同，在图3实施例中，第一切换装置只确定了为目标UE提供目标应用服务的实例待切换，从而通知第一MEC平台，第一MEC平台接收到该通知后，则协同第二基站侧的网络设备获取目的实例的实例ID，进而确定为目标UE提供目标应用服务的实例待切换为第二MEC平台的第二实例。这样，第一切换装置只确定为目标UE提供目标应用服务的实例待切换，而确定第二实例的步骤由第一MEC平台执行，提高网络侧设备的资源利用率，减少了第一切换装置的负担。
上面的实施例介绍了本申请提供的应用服务切换方法的流程。在图4的实施例中，上述第一切换装置为独立的设备。下面将结合图4，对本申请提供的实例切换方法的另一个实施例的详细流程进行示例性的介绍。
401、第一基站决策目标UE待切换至第二基站。
在目标UE进入第二基站的小区范围内，但尚成功接入第二基站前，第一基站决策待将目标UE的网络连接由第一基站切换至第二基站。
例如，当目标UE移动至第二基站的小区范围内时，目标UE向第一基站发送测量报告，第一基站根据该测量报告决策目标UE待切换的基站为第二基站。或者，第一基站基于测量报告向第二基站发送切换请求，并接收第二基站的切换请求确认消息后决策目标UE待切换的基站为第二基站。
402、第一基站向第一切换装置发送准备通知消息。
在确认目标UE的基站待切换后，第一基站向第一切换装置发送准备通知消息。第一切换装置接收该准备通知消息。
该准备通知消息用于通知第一切换装置目标UE待接入第二基站，以触发实例切换的准备流程。在一种实现方式中，该准备通知消息中携带目标UE的UE ID，以及所述第二基站的基站ID。另一种实现方式中，该准备通知消息中也可以不携带第二基站的基站ID，而是携带目标UE的UE ID以及目标UE的位置信息，由第一切换装置根据目标UE的位置信息来确定目标UE待接入的第二基站。可选的，每个切换装置还可以存储有通信网络中各个切换装置服务范围。因此，第一切换装置还可以根据UE的位置信息确定第二切换装置。通信网络中包括多个切换装置的场景在步骤403中进一步描述。
403、第一切换装置向第二切换装置发送第一请求消息。
在本实施例所应用的通信网络架构中，第一切换装置为第一基站侧的网络设备，第二切换装置为第二基站侧的网络设备。第二切换装置与第一切换装置的功能相同，均用于为其所对应的基站下所连接的UE提供实例切换服务。切换装置和切换装置之间的通信连接的建立方式与基站和基站之间的建立方式相似。比如，第一切换装置存储有附近的多个基站对应的切换装置的通信标识，其中包括第二切换装置的通信标识。在需要建立通信连接时， 第一切换装置通过第二基站的基站ID查询到对应的第二切换装置的通信标识，再根据该通信标识与第二切换装置建立通信连接。或者，第一切换装置向附近的多个切换装置发送广播信号，在接收到多个反馈后，根据第二基站的基站ID选择所对应的第二切换装置建立通信连接。第一切换装置与第二切换装置建立通信连接的方式有多种，本申请不做限定。
第一切换装置在接收到准备通知消息后，第一切换装置根据该准备通知消息中的第二基站的基站ID，与第二基站对应的第二切换装置建立通信连接，并向该第二切换装置发送第一请求消息。该第一请求消息中包括目标UE的UE ID以及目标应用服务的服务ID，该第一请求消息用于请求第二切换装置返回目标UE上的目标应用服务的新的实例的信息。第二切换装置向第一切换装置返回的第一响应消息中携带所确定的新的实例的信息。
可选的，一种可能的实现方式中，第一切换装置在接收到切换通知消息后，第一切换装置根据该切换通知消息中的第二基站的基站ID，与第二基站对应的第二切换装置建立通信连接时，将第一请求消息发送给第二切换装置。即，第一切换装置在向第二切换装置所发送的建立通信连接的请求信息中携带该第一请求消息。第二切换装置在向第一切换装置反馈的建立通信连接的确认信息中携带与第一请求消息所对应的第一响应消息。
可选的，另一种可能的实现方式中，第一切换装置与第二切换装置的通信连接的建立也可以是在切换装置部署安装时所建立的。由于切换装置一般只会跟相邻的基站所对应的切换装置进行业务交互，因此，由于第一基站与第二基站相邻，第一切换装置与第二切换装置在部署安装在所对应的基站时，第一切换装置则与第二切换装置建立了通信连接。第一切换装置在接收到切换通知消息后，第一切换装置根据该切换通知消息中的第二基站的基站ID查询到第二基站所对应的第二切换装置，从而向第二切换装置发送第一请求消息。
其中，UE ID用于唯一标识对应的UE。在本申请的一些实施例中，UE ID可以是UE的IP地址的形式，也可以是UE的设备标识的形式。即，目标UE的UE ID可以是目标UE的IP地址，或目标UE的网关侧S1-U(英文：User plane S1interface)端点标识，也可以是目标UE的设备标识。UE ID也可以是其它形式的能够标识对应的UE的信息，本申请不做限定。
404、第二切换装置向第一切换装置返回第一响应消息。
第二切换装置中存储有第二基站所对应的第二MEC平台中所部署的实例信息。第二切换装置接收到第一请求消息后，根据目标应用服务的服务ID从第二MEC平台上查询到与该应用服务对应的第二实例，并获取第二实例的实例ID。第二切换装置将第二MEC平台的ID以及第二实例的实例ID携带在第一响应消息中，返回给第一切换装置。第一切换装置接收该第一响应消息，进而可以确定为目标UE上提供目标应用服务的实例待切换为第二实例。
405、第一切换装置向第一MEC平台发送切换准备消息。
第一切换装置向第一MEC平台发送切换准备消息，该切换准备消息中携带有目标UE的UE ID、目标应用服务的服务ID、第二MEC平台的ID以及第二实例的实例ID。第一MEC平台在接收到该切换准备消息后，则获知为目标UE提供目标应用服务的实例将切换为第二MEC平台上的第二实例。
可选的，第一MEC平台还可以将该切换准备消息再发送给第二MEC平台，从而使得第 二MEC平台也获知为目标UE提供目标应用服务的实例将切换为第二实例。
其中，步骤405为可选步骤，仅用于第一切换装置通知第一MEC平台为目标UE提供目标应用服务的实例将切换为第二实例。第一切换装置通知第一MEC平台为目标UE提供目标应用服务的实例将切换为第二实例也可以通过其它方式实现。
举例来说，通信网络还可以设置有应用控制器，如图1(a)、图1(b)以及图1(c)任意一附图所示。应用控制器用于管理通信网络中的各MEC平台，进而对通信网络中的所有应用进行管控。该应用控制器为核心网侧的网络设备，应用控制器连接该通信网络中的各个MEC平台，用于向各个MEC平台发送控制信息。应用控制器还连接各个基站侧的网络设备(比如，网络设备可以为基站或者切换装置)，用于根据用户侧的需求(比如UE发生小区范围的移动)进行应用实例的控制决策等。第一切换装置在接收到准备通知消息后，可以向应用控制器发送第二请求消息。该第二请求消息中携带有目标应用服务的服务ID以及目标UE的位置信息，用于请求应用控制器返回目标应用服务新的实例的信息。应用控制器接收到该第二请求消息后，根据目标UE的位置信息确定其待接入第二MEC平台，进而应用控制器协同第二MEC平台确定目标应用的第二实例。此时，第二MEC平台也获知了为目标UE提供目标应用服务的实例将切换为第二实例。
可选的，若该目标应用服务在MEC平台进行实例注册时，该目标应用服务申请了在实例切换准备阶段需要做报文转发的业务，第一切换装置还可以进行一些切换准备工作。其中，实例切换准备阶段指的是：目标UE成功接入第二基站前，第一切换装置确定为目标UE提供目标应用服务的实例待切换为第二实例，至目标UE接入第二基站后，第一切换装置指示第一MEC平台进行实例切换之间的时间段。例如，切换准备工作是指：第一切换装置生成报文转发策略，并将报文转发策略发送给相应的转发设备(比如，网关设备)，由转发设备完成目标UE与实例之间的报文转发工作。该报文转发策略用于指示转发设备在实例切换准备阶段时，将目标UE的上行报文按照报文转发策略转发至第二实例中，以及将第二实例的下行报文转发至目标UE中。这样，即使在实例切换准备阶段(即，目标UE仍与第一基站连接时)，目标UE则可以与目的实例进行数据交互。下面对报文转发策略的内容进行示例性描述：
在实例切换准备阶段，目标UE与目标应用服务的第二实例可以进行数据交互。比如，双方提前建立好传输控制协议(英文：transmission control protocol，缩写：TCP)连接。因此需要建立第一基站到第二基站所对应的网关的底层链路连接，即，该底层链路连接为：第一网关(第一基站所对应的网关)-第二网关(第二基站所对应的网关)。该底层链路连接形成一种业务转发隧道。该业务转发隧道的建立由第一网关与第二网关完成。比如，基于用户面的隧道协议(英文：Tunnelling Protocol for User Plane，缩写：GTP-U)的类型的隧道，第一网关将第一网关的隧道标识发送给第二网关，第二网关接收到第一网关的隧道标识后，则将第二网关的隧道标识发送给第一网关。这样，两个网关能识别隧道类型与隧道标识，从而建立了该业务转发隧道。此时，目标UE与目标应用服务交互的报文仍在第一网关上做业务识别。第一切换装置将报文转发策略发送至第一网关。为了使得第一网关能够识别出发送至第二实例的目标报文，从而使用业务转发隧道进行转发，第一切 换装置还需根据第二实例的实例ID创建业务特征，并将该业务特征携带在该报文转发策略中发送至第一网关。第一网关在接收到报文后，根据该业务特征判断该报文是否为目标UE需要发送至第二实例的报文。该业务特征可以为目标UE与目标应用服务的实例进行报文交互的业务流特征。比如，业务特征可以为五元组信息或五元组中的部分信息。其中，五元组信息可以包括：目标UE的IP地址、第二实例的IP地址，传输协议，目标端口号以及源端口号的。其中，五元组中部分信息可以包括第二实例的IP地址和/或端口号。
对于上行业务，第一网关将目标UE与第二实例的上行业务流识别出来。例如，识别方式为：通过判断在交互的报文中是否携带的第二实例的实例ID，若是，则表示该报文为目标UE与第二实例交互的报文，如否，则表示该报文不是目标UE与第二实例交互的报文)。并通过该业务转发隧道转发至第二实例。比如，目标UE可以将目标UE与第一实例连接所使用的传输协议的信息或者上下文内容以上行报文的方式通过该业务转发隧道发送至第二实例。
对于下行业务，第二网关的处理方式是：第二网关通过业务转发隧道将目标UE的下行业务转发至第一网关，由第一网关进行业务识别后再转发至第一基站。待UE切换至第二基站，第二基站与第二网关的UE的S1-U传输通道建好后，则直接将目标UE的下行业务发送至第二基站。
可选的，若该目标应用服务在第一MEC平台注册时，申请了在实例切换准备阶段需要做报文转发的业务，那么第一MEC平台在获取到第二实例的实例ID后，还需要将第二实例的实例ID(比如IP地址)发送给目标UE，以使得目标UE可以与第二实例进行数据交互。
在实例切换准备阶段，目标UE发送的上行报文则可以通过第一网关与第二网关的业务转发隧道转发至第二实例。而现有技术中，若目标UE发送上行报文至第一网关后，当该报文还未转发至第一实例时，目标UE则接入第二基站并开始实例切换时，那么该报文无法被转发至第二实例，从而被丢弃。通过本申请方案，目标UE发送的上行报文不会由于实例切换的原因而被丢弃。
406、第一MEC平台协同第二MEC平台进行数据同步准备。
第一MEC平台接收到切换准备消息后，协同第二MEC平台进行数据同步准备。
该数据同步准备可以为第一MEC平台将部分数据发送给第二MEC平台，第二MEC平台接收到该部分数据后，则将该部分数据更新至第二实例中。比如，部分数据包括：目标UE与第一实例的传输协议，或者静态的上下文内容。
需要说明的是，若如步骤405所述，第一切换装置已完成了上述切换准备工作，第一切换装置可以通知第一MEC平台，无需协同第二MEC平台进行数据同步准备，则步骤406可以不执行。
407、目标UE接入第二基站。
在目标UE接入第二基站时，目标UE的目标应用服务仍由第一MEC平台的第一实例支持，因此目标UE继续保持与第一基站的空口连接。
需要说明的是，步骤407所描述的目标UE接入第二基站的过程，与步骤402至406所描述的第一基站、第二基站、第一切换装置、第二切换装置、第一MEC平台以及第二MEC 平台的切换准备过程是同时段进行的。在第一基站决策目标UE待切换为第二基站后(即，在步骤401后)，则开始进行目标UE接入第二基站的流程。在本申请中，在目标UE接入第二基站的时段中，网络侧设备同时对为目标UE提供目标应用服务的实例切换做目的实例的确定以及切换准备工作。即使在目标UE接入第二基站后，该切换准备工作仍未完成，但相比现有技术，本方案提前做目的实例的确定以及切换准备的方式从而完成实例切换仍会更为快捷。
408、在目标UE接入第二基站后，第二基站向第一基站发送知会消息。
该知会消息表示目标UE已经成功接入第二基站。可选的，由于此时目标UE并未释放与第一基站的空口连接，该知会消息也可以由目标UE发送给第一基站。
409、第一基站向第一切换装置发送切换通知消息。
目标UE由第一基站切换至第二基站后，由第一基站向第一切换装置发送切换通知消息。该切换通知消息携带有目标UE的UE ID。例如，目标UE与第二基站建立无线资源控制(英文：Radio Resource Control，缩写RRC)连接后，目标UE或第二基站向第一基站发送知会消息。第一基站接收到该知会消息后，向第一切换装置发送切换通知消息。或，第一基站可以在接收到核心网发送的结束标志(英文：end marker)报文(表示核心网在源侧路径最后发送的报文)后(表示目标UE已接入第二基站)，第一基站则向第一切换装置发送切换通知消息。
可选的，若第一切换装置与网关合设，则第一切换装置会先于第一基站接收到核心网发送的end maker报文。此时第一切换装置可以直接执行步骤410，无需第一基站发送切换通知消息。
410、第一切换装置向第一MEC平台发送切换指示消息。
第一切换装置接收到切换通知消息后，向第一MEC平台发送切换指示消息。第一MEC平台接收该切换指示消息。该切换指示消息携带有目标UE的UE ID，用于指示第一MEC平台切换为目标UE提供目标应用服务的实例。
411、第一MEC平台协同第二MEC平台进行实例切换。
第一MEC平台接收到该切换指示消息后，协同第二MEC平台，将目标UE上的目标应用由第一实例切换为第二实例，完成数据迁移。该数据迁移指的是第一MEC平台将第一实例中有关目标UE的数据全部发送至第二MEC平台中，第二MEC平台再将该数据更新至第二实例中。需要说明的是，若在上述的切换准备阶段，目标UE或者第一MEC平台已经将部分数据更新至第二实例中，则在该步骤中，第一MEC平台无需再发送前述部分数据至第二MEC平台中，从而减少了数据迁移的时间。
412、目标UE释放与第一MEC平台中第一实例的业务连接。
目标UE待其提供目标应用服务的实例由第一实例切换为第二实例，且完成数据迁移后，释放与第一MEC平台中第一实例的业务连接。
需要说明的是，步骤412为可选步骤。步骤412所描述的实现方式为第一MEC平台与第二MEC平台协同切换实例时，通知了目标UE更换目标应用服务的实例的地址为第二实例的地址，因此，目标UE需要根据第二实例的地址与第二实例建立业务连接，并释放与第一 实例的业务连接。
可选的，在一种实现方式中，第一MEC平台与第二MEC平台协同切换实例后，目标UE并不感知已经更换了实例的地址，所以目标UE可以继续与第一实例进行业务交互，所交互的报文由网络侧根据地址转换规则把报文转发至第二实例中。因此，目标UE则不需释放与第一实例的业务连接。
可选的，在另一种实现方式中，目标UE在接入该目标应用服务时所使用的是目标应用服务的服务地址，因此，无论目标应用服务更换为哪个实例与目标UE进行业务交互，目标UE都不会感知实例的地址变换，仍使用目标应用服务的服务地址进行业务交互。所以，目标UE也不会感知具体与哪个实例进行业务交互，从而也不会有目标UE释放与第一实例的业务连接的步骤。
另要说明的是，在第一实例的数据未完全迁移至第二实例之前，目标UE可能还与第一实例保持连接与交互。比如，目标UE与第一实例进行释放TCP连接的信令交互；或者，目标UE与第一实例进行少量业务交互。在实例切换准备阶段，第一切换装置把业务特征告诉第二切换装置，第二切换装置将报文转发策略发送至第二网关，该报文转发策略包含该业务特征。第二网关在接收到报文后，根据该业务特征判断所接收到的报文是否为目标UE与目标应用服务的实例交互的报文。其中，该业务特征可以为目标UE与目标应用服务的实例进行报文交互的业务流特征。比如为五元组信息或五元组中的部分信息，其中，该五元组信息可以包括：目标UE的IP地址、第一实例的IP地址、传输协议、目标端口号以及源端口号。其中，该五元组中的部分信息可以包括第一实例的IP地址。
对于与第一实例的上行业务，由第二网关做业务流识别。第二网关通过第二切换装置发送的报文转发策略，对上行报文进行识别，若上行报文为目标UE发送给第一实例的业务报文，则通过业务转发隧道转发至第一实例。
对于与第一实例的下行业务，由第一网关进行转发处理。第一网关的处理方式是：如果第一网关与第一基站的下行S1-U已经释放了，第一网关则识别出的下行报文转发到第二网关，再由第二网关转发至第二基站，再由第二基站转发至目标UE；如果第一网关与第一基站的下行S1-U还没有释放，则直接转发到第一基站，再由第一基站转发至目标UE。
图4实施例所描述的方案中，第一切换装置在向第一MEC平台发送切换准备消息之前，已经确定了为目标UE提供目标应用服务的第一实例待切换为第二MEC平台上的第二实例。可选的，确定为目标UE提供目标应用服务的第一实例待切换为第二MEC平台上的第二实例的步骤也可以由第一MEC平台执行。第一切换装置不向第一MEC平台发送第二实例的实例ID。而是将目标UE的位置信息发送给第一MEC平台，由第一MEC平台与第二MEC平台协同确定位目标UE提供目标应用服务的实例将切换为第二实例。其中，协同确定的方式如图3实施例中步骤302所述，此处不做赘述。基于这种实现方式，图4实施例中的步骤403、404则为可选步骤，即，第一切换装置无需获取到第二实例的实例ID。那么在第一切换装置向第一MEC平台发送的切换准备消息中，该切换准备消息中携带有目标UE的UE ID、目标应用服务的服务ID以及目标UE的位置信息。第一MEC平台在接收到该切换准备消息后，则根据目标UE的位置信息确定第二MEC平台，再根据目标应用服务的服务ID协同第二MEC 平台获取到第二实例的实例ID。此时，第二MEC平台也获知了为目标UE提供目标应用服务的实例将切换为第二实例。
需要说明的是，此处的UE ID与图4中步骤402中所述的UE ID的表现形式可以相同，也可以不同。此处的UE ID是用于切换装置与MEC平台上的实例之间标识，一般通过IP地址的形式指代该UE ID。而步骤402中所描述的UE ID是用于切换装置和基站之间的标识，既可以通过IP地址的形式指代，也可以通过设备标识或设备名称等形式指代。
可选的，上述实施例中的切换装置的功能还可以与核心网设备合设，即，核心网设备具备上述切换装置的功能。下面将结合图5，对本申请提供的实例切换方法的另一实施例的详细流程进行示例性的介绍。图5实施例中的核心网设备可以为如图1(a)至图1(c)中任意一种通信网络中的核心网中的网络设备。图5中的核心网设备具备如图2至图4实施例中切换装置的功能。下面进行流程描述：
501、第一基站确定目标UE待切换为第二基站。
详细内容参照图4实施例中步骤401，此处不做赘述。
502、第一基站向核心网设备发送准备通知消息。
在确认目标UE的基站待切换后，第一基站向核心网设备发送准备通知消息。核心网设备接收该准备通知消息。
该准备通知消息用于通知核心网设备目标UE待接入第二基站，以触发实例切换准备流程。该准备通知消息中包括目标UE的UE ID，以及所述第二基站的基站ID。可选的，该准备通知消息也可以由第二基站向核心网设备发送。若第二基站接收到第一基站发送的切换请求，第二基站在确认目标UE可以接入第二基站时，则可以向核心网设备发送该准备通知消息。
503、核心网设备向第一MEC平台发送切换准备消息。第一MEC平台接收核心网设备发送的切换准备消息。
核心网设备向第一MEC平台发送切换准备消息，该切换准备消息中携带有目标UE的UE ID，以及目标应用服务的第二实例的实例ID，用于指示第一MEC平台为目标UE提供目标应用服务的实例将切换为第二实例。
可选的，若该目标应用服务在第一MEC平台进行实例注册时，该目标应用服务申请了在实例切换准备阶段需要做报文转发的业务。那么，核心网设备在切换准备阶段时，还可以生成报文转发策略，并将该报文转发策略发送给相应的转发设备(比如，网关设备)，由转发设备完成目标UE与实例之间的报文转发工作。详细的执行内容与图4实施例中步骤405所描述的类似，比如，业务转发隧道的建立仍由第一网关与第二网关建立，而第一切换装置的功能与操作由核心网设备实现。此处不做赘述。
504、第一MEC平台协同第二MEC平台进行数据同步准备。
详细内容参照图4实施例中步骤406，此处不做赘述。
505、目标UE接入第二基站。
详细内容参照图4实施例中步骤407，此处不做赘述。
506、第二基站向核心网设备发送知会消息，该知会消息表示目标UE已经接入第二基 站。
507、核心网设备向第一MEC平台发送切换指示消息。
核心网设备在检测到目标UE接入至第二基站后，向第一MEC平台发送切换指示消息。第一MEC平台接收该切换指示消息。该切换指示消息携带有目标UE的UE ID，用于指示第一MEC平台切换目标UE的目标应用服务的实例。
508、第一MEC平台协同第二MEC平台进行实例切换。
详细内容参照图4实施例中步骤411，此处不做赘述。
509、目标UE释放与第一ME平台中第一实例的业务连接。
详细内容参照图4实施例中步骤412，此处不做赘述。
可选的，一种可能的实现方式中，核心网设备还可以独立出一个应用控制器，用于对第一MEC平台与第二MEC平台进行集中式管理。基于图5实施例所示，核心网设备与第一MEC平台以及第二MEC平台所进行的信令交互均需通过该应用控制器进行转发。其中，基于该实现方式，图5实施例中步骤503中的切换准备消息中携带的可以是目标UE的UE ID，以及目标UE的位置信息。以使得应用控制器根据目标UE的位置信息确定目标UE待接入的第二MEC平台，从而确定第二实例的实例ID。其它处理流程与图5实施例类似，此处不做赘述。
可选的，在另一种可能的实现方式中，核心网设备在每个MEC平台上还可以部署有单独的代理网元。这样，MEC平台需要向核心网设备发送信令时，则只需要进行给本地交互。
参照图6所示，图6为本申请实施例所提供的切换装置的一个实施例，该切换装置为图2至图5任意实施例中的第一切换装置，包括：
确定单元601，用于在目标用户设备UE移动至第二基站的小区范围内，且成功接入所述第二基站前，确定为所述目标UE提供目标应用服务的第一移动边缘MEC平台上的第一实例待切换为第二MEC平台上的第二实例，其中所述目标UE为接入第一基站的UE，所述第一MEC平台用于为所述第一基站的小区内的UE提供所述目标应用服务，所述第二MEC平台用于为所述第二基站小区内的UE提供所述目标应用服务；
通知单元602，用于在所述目标UE成功接入所述第二基站前，通知所述第一MEC平台：为所述目标UE提供所述目标应用服务的所述第一实例将切换为所述第二实例；
指示单元603，用于在所述目标UE成功接入所述第二基站后，所述指示所述第一MEC平台：将为所述目标UE提供目标应用服务的所述第一实例切换为所述第二MEC平台上的所述第二实例。
可选的，所述确定单元601具体用于：
获取所述目标UE的位置信息；
根据所述目标UE的位置信息向第二切换装置发送第一请求消息，所述第一请求消息中包括所述目标应用服务的服务标识ID；所述第二切换装置用于为连接所述第二基站的UE提供实例的切换服务；所述目标应用服务的服务ID与所述第二MEC平台的所述第二实例关联；
从所述第二切换装置接收第一响应消息，所述第一响应消息中携带有所述第二实例的 实例ID；
根据所述第二实例的实例ID，确定为所述目标UE提供目标应用服务的第一MEC平台上的第一实例待切换为所述第二MEC平台上的所述第二实例。
可选的，所述通知单元602具体用于：
向所述第一MEC平台发送切换准备消息，所述切换准备消息中携带有所述目标UE的UE标识ID以及所述第二实例的实例ID。
可选的，所述装置还包括：
接收单元604，用于在所述指示单元指示所述第一MEC平台之前，从所述第一基站接收切换通知消息，所述切换通知消息携带有所述目标UE的UE ID，所述切换通知消息用于表示所述目标UE已成功接入所述第二基站。
可选的，所述装置还包括：
创建单元605，用于根据所述第二实例的实例ID创建业务特征；
发送单元606，用于向第一网关发送报文转发策略，所述报文转发策略用于指示所述第一网关：根据所述业务特征识别目标上行报文，并将所述目标上行报文转发至第二网关，所述目标上行报文为所述目标UE与所述目标应用服务交互的上行报文；其中，所述第一网关用于为所述第一基站提供业务服务，所述第二网关用于为所述第二基站提供业务服务。
图6实施例所描述的各个单元在运行时还可以执行图2至图5任意实施例中第一切换装置所执行的步骤，详细内容可参照图2至图5实施例，此处不做赘述。
本申请实施例提供了一种实例切换系统，适用于移动通信网络，如图1(a)～1(c)任意附图所示，所述实例切换系统包括：第一基站、第一移动边缘MEC平台、第二基站、第二MEC平台、第一切换装置以及第二切换装置；其中，所述第一MEC平台用于为所述第一基站小区内的UE提供所述目标应用服务，所述第二MEC平台用于第二基站小区内的UE提供所述目标应用服务，所述第一切换装置用于为连接所述第一基站的UE提供实例的切换服务，所述第二切换装置用于为连接所述第二基站的UE提供实例的切换服务；其中，第一切换装置如图2至图5任意实施例中所述的第一切换装置。
图6实施例所述的装置还有另一个形式的实施例，参照图7所示，包括：处理器701、存储器702、收发器703，所述处理器701、所述存储器702以及所述收发器703通过总线704连接，收发器703可以包括发送器与接收器，所述存储器702存储有计算机指令，所述处理器701通过执行所述计算机指令用于实现图2至图5任意实施例中实例切换方法的功能。具体的实现可以采用各类灵活的设计方式，各个器件相应的功能可以进一步的参考上述方法实施例，本申请不做限制。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。
所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一计算机可读存储介质传 输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存储的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(英文全称：read-only memory，简写：ROM)、随机存取存储器(英文全称：random access memory，简写：RAM)、磁碟或者光盘等各种可以存储程序代码的介质。

Claims (13)

  1. 一种实例切换方法，其特征在于，所述方法包括：
    在目标用户设备UE移动至第二基站的小区范围内，且成功接入所述第二基站前，第一切换装置确定为所述目标UE提供目标应用服务的第一移动边缘MEC平台上的第一实例待切换为第二MEC平台上的第二实例，其中，所述目标UE为接入第一基站的UE，所述第一MEC平台用于为所述第一基站的小区内的UE提供所述目标应用服务，所述第二MEC平台用于为所述第二基站小区内的UE提供所述目标应用服务；
    在所述目标UE成功接入所述第二基站前，所述第一切换装置通知所述第一MEC平台：为所述目标UE提供所述目标应用服务的所述第一实例将切换为所述第二实例；
    在所述目标UE成功接入所述第二基站后，所述第一切换装置指示所述第一MEC平台：将为所述目标UE提供目标应用服务的所述第一实例切换为所述第二MEC平台上的所述第二实例。
  2. 根据权利要求1所述的方法，其特征在于，所述第一切换装置确定为所述目标UE提供目标应用服务的第一MEC平台上的第一实例待切换为第二MEC平台上的第二实例，包括：
    所述第一切换装置获取所述目标UE的位置信息；
    所述第一切换装置根据所述目标UE的位置信息向第二切换装置发送第一请求消息，所述第一请求消息中包括所述目标应用服务的服务标识ID；所述第二切换装置用于为连接所述第二基站的UE提供实例的切换服务；所述目标应用服务的服务ID与所述第二MEC平台的所述第二实例关联；
    所述第一切换装置从所述第二切换装置接收第一响应消息，所述第一响应消息中携带有所述第二实例的实例ID；
    所述第一切换装置根据所述第二实例的实例ID，确定为所述目标UE提供目标应用服务的第一MEC平台上的第一实例待切换为所述第二MEC平台上的所述第二实例。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一切换装置通知所述第一MEC平台，包括：
    所述第一切换装置向所述第一MEC平台发送切换准备消息，所述切换准备消息中携带有所述目标UE的UE标识ID以及所述第二实例的实例ID。
  4. 根据权利要求1至3其中任意一项所述的方法，其特征在于，在所述第一切换装置指示所述第一MEC平台之前，所述方法还包括：
    所述第一切换装置从所述第一基站接收切换通知消息，所述切换通知消息携带有所述目标UE的UE ID，所述切换通知消息用于表示所述目标UE已成功接入所述第二基站。
  5. 根据权利要求1至4其中任意一项所述的方法，其特征在于，所述方法还包括：
    所述第一切换装置根据所述第二实例的实例ID创建业务特征；
    所述第一切换装置向第一网关发送报文转发策略，所述报文转发策略用于指示所述第一网关：根据所述业务特征识别目标上行报文，并将所述目标上行报文转发至第二网关，所述目标上行报文为所述目标UE与所述目标应用服务交互的上行报文；其中，所述第一网 关用于为所述第一基站提供业务服务，所述第二网关用于为所述第二基站提供业务服务。
  6. 一种切换装置，当所述切换装置为第一切换装置时，其特征在于，所述装置包括：
    确定单元，用于在目标用户设备UE移动至第二基站的小区范围内，且成功接入所述第二基站前，确定为所述目标UE提供目标应用服务的第一移动边缘MEC平台上的第一实例待切换为第二MEC平台上的第二实例，其中，所述目标UE为接入第一基站的UE，所述第一MEC平台用于为所述第一基站的小区内的UE提供所述目标应用服务，所述第二MEC平台用于为所述第二基站小区内的UE提供所述目标应用服务；
    通知单元，用于在所述目标UE成功接入所述第二基站前，通知所述第一MEC平台：为所述目标UE提供所述目标应用服务的所述第一实例将切换为所述第二实例；
    指示单元，用于在所述目标UE成功接入所述第二基站后，所述指示所述第一MEC平台：将为所述目标UE提供目标应用服务的所述第一实例切换为所述第二MEC平台上的所述第二实例。
  7. 根据权利要求6所述的装置，其特征在于，所述确定单元具体用于：
    获取所述目标UE的位置信息；
    根据所述目标UE的位置信息向第二切换装置发送第一请求消息，所述第一请求消息中包括所述目标应用服务的服务标识ID；所述第二切换装置用于为连接所述第二基站的UE提供实例的切换服务；所述目标应用服务的服务ID与所述第二MEC平台的所述第二实例关联；
    从所述第二切换装置接收第一响应消息，所述第一响应消息中携带有所述第二实例的实例ID；
    根据所述第二实例的实例ID，确定为所述目标UE提供目标应用服务的第一MEC平台上的第一实例待切换为所述第二MEC平台上的所述第二实例。
  8. 根据权利要求6或7所述的装置，其特征在于，所述通知单元具体用于：
    向所述第一MEC平台发送切换准备消息，所述切换准备消息中携带有所述目标UE的UE标识ID以及所述第二实例的实例ID。
  9. 根据权利要求6至8其中任意一项所述的装置，其特征在于，所述装置还包括：
    接收单元，用于在所述指示单元指示所述第一MEC平台之前，从所述第一基站接收切换通知消息，所述切换通知消息携带有所述目标UE的UE ID，所述切换通知消息用于表示所述目标UE已成功接入所述第二基站。
  10. 根据权利要求6至9其中任意一项所述的装置，其特征在于，所述装置还包括：
    创建单元，用于根据所述第二实例的实例ID创建业务特征；
    发送单元，用于向第一网关发送报文转发策略，所述报文转发策略用于指示所述第一网关：根据所述业务特征识别目标上行报文，并将所述目标上行报文转发至第二网关，所述目标上行报文为所述目标UE与所述目标应用服务交互的上行报文；其中，所述第一网关用于为所述第一基站提供业务服务，所述第二网关用于为所述第二基站提供业务服务。
  11. 一种实例切换系统，适用于移动通信网络，其特征在于，所述实例切换系统包括：第一基站、第一移动边缘MEC平台、第二基站、第二MEC平台、第一切换装置以及第二切 换装置；其中，所述第一MEC平台用于为所述第一基站小区内的UE提供所述目标应用服务，所述第二MEC平台用于第二基站小区内的UE提供所述目标应用服务，所述第一切换装置用于为连接所述第一基站的UE提供实例的切换服务，所述第二切换装置用于为连接所述第二基站的UE提供实例的切换服务；其中，第一切换装置如权利要求6至10所述的装置。
  12. 一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行如权利要求1-5任意一项所述的方法。
  13. 一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如权利要求1-5任意一项所述的方法。
PCT/CN2018/093308 2017-08-31 2018-06-28 实例切换方法及相关装置 WO2019042000A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18850083.9A EP3664508A4 (en) 2017-08-31 2018-06-28 PROCESS FOR SWITCHING INSTANCES AND ASSOCIATED DEVICE
US16/805,180 US20200205040A1 (en) 2017-08-31 2020-02-28 Instance switching method and related apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710777786.1A CN109429284B (zh) 2017-08-31 2017-08-31 实例切换方法、相关装置、实例切换系统及存储介质
CN201710777786.1 2017-08-31

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/805,180 Continuation US20200205040A1 (en) 2017-08-31 2020-02-28 Instance switching method and related apparatus

Publications (1)

Publication Number Publication Date
WO2019042000A1 true WO2019042000A1 (zh) 2019-03-07

Family

ID=65512721

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/093308 WO2019042000A1 (zh) 2017-08-31 2018-06-28 实例切换方法及相关装置

Country Status (4)

Country Link
US (1) US20200205040A1 (zh)
EP (1) EP3664508A4 (zh)
CN (1) CN109429284B (zh)
WO (1) WO2019042000A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111564037A (zh) * 2020-04-14 2020-08-21 深圳市灵犀智汇科技有限公司 一种面向轨道交通的数据计算方法
WO2020207266A1 (zh) * 2019-04-08 2020-10-15 阿里巴巴集团控股有限公司 网络系统、实例管控方法、设备及存储介质

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112153098B (zh) * 2019-06-28 2023-09-29 华为技术有限公司 一种应用迁移方法及装置
CN112187495B (zh) * 2019-07-01 2023-12-12 阿里巴巴集团控股有限公司 终端与服务器的通信方法、通信系统
CN112217856A (zh) * 2019-07-11 2021-01-12 华为技术有限公司 应用实例的地址获取方法、装置、设备及存储介质
CN113032111B (zh) * 2019-12-24 2024-04-30 中国电信股份有限公司 应用程序的迁移方法、装置、系统和计算机可读存储介质
CN111132253B (zh) * 2019-12-31 2021-03-30 北京邮电大学 一种通信切换和服务迁移的联合移动性管理方法
US11683747B2 (en) * 2020-01-13 2023-06-20 Qualcomm Incorporated System and method for prioritized mobility to access edge servers
CN113395238B (zh) * 2020-03-12 2022-09-23 华为技术有限公司 一种认证授权方法及对应装置
CN113949705B (zh) * 2020-06-29 2023-07-11 华为技术有限公司 通信方法和通信装置
CN111884847B (zh) * 2020-07-20 2022-06-28 北京百度网讯科技有限公司 用于处理故障的方法和装置
CN112105069B (zh) * 2020-09-22 2023-04-28 云南电网有限责任公司电力科学研究院 一种互联网边缘计算无线网络切换方法及系统
CN112130931B (zh) * 2020-09-27 2023-01-06 联想(北京)有限公司 一种应用部署方法、节点、系统及存储介质
CN112218351B (zh) * 2020-10-27 2022-07-12 中国联合网络通信集团有限公司 数据传输方法、装置及系统
CN112584439A (zh) * 2020-11-27 2021-03-30 重庆邮电大学 一种边缘计算中的缓存方法
US20240056497A1 (en) * 2020-12-14 2024-02-15 Koninklijke Kpn N.V. Enabling multi-edge applications
CN114090200A (zh) * 2021-11-02 2022-02-25 中国联合网络通信集团有限公司 一种跨系统进行应用程序实例化迁移方法及装置
KR20230118418A (ko) * 2022-02-04 2023-08-11 삼성전자주식회사 무선 통신 시스템에서 에지 컴퓨팅 서비스를 제공하기 위한 장치 및 방법
WO2023155105A1 (en) * 2022-02-17 2023-08-24 Zte Corporation Method for application mobility service across multi-access edge computing

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030058874A1 (en) * 2001-09-21 2003-03-27 Nokia Corporation System and method for enabling mobile edge services
CN101232723A (zh) * 2002-03-11 2008-07-30 高通股份有限公司 支持多服务实例的通信系统内切换的方法和装置
CN106231607A (zh) * 2016-09-21 2016-12-14 北京佰才邦技术有限公司 一种资源分配的方法及基站
CN106254408A (zh) * 2015-06-12 2016-12-21 财团法人工业技术研究院 移动边缘计算的控制方法、网络系统与服务平台
WO2016203874A1 (ja) * 2015-06-18 2016-12-22 ソニー株式会社 システム、方法及び端末装置
CN107018534A (zh) * 2016-01-28 2017-08-04 中兴通讯股份有限公司 一种实现移动边缘计算服务的方法、装置及系统

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016134772A1 (en) * 2015-02-26 2016-09-01 Nokia Solutions And Networks Oy Charging and control of edge services
US20170118311A1 (en) * 2015-10-22 2017-04-27 Saguna Networks Ltd. Methods Circuits Devices Systems and Functionally Associated Computer Executable Code for Facilitating Edge Computing on a Mobile Data Communication Network
WO2017091960A1 (zh) * 2015-11-30 2017-06-08 华为技术有限公司 切换移动边缘平台的方法、装置和系统
WO2017118488A1 (en) * 2016-01-08 2017-07-13 Nec Europe Ltd. A method for operating a network, a network and an orchestrator for use within the method
CN108886718B (zh) * 2016-01-20 2021-12-28 诺基亚通信公司 用于利用移动边缘计算的改进服务连续性的方法、装置和计算机程序产品

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030058874A1 (en) * 2001-09-21 2003-03-27 Nokia Corporation System and method for enabling mobile edge services
CN101232723A (zh) * 2002-03-11 2008-07-30 高通股份有限公司 支持多服务实例的通信系统内切换的方法和装置
CN106254408A (zh) * 2015-06-12 2016-12-21 财团法人工业技术研究院 移动边缘计算的控制方法、网络系统与服务平台
WO2016203874A1 (ja) * 2015-06-18 2016-12-22 ソニー株式会社 システム、方法及び端末装置
CN107018534A (zh) * 2016-01-28 2017-08-04 中兴通讯股份有限公司 一种实现移动边缘计算服务的方法、装置及系统
CN106231607A (zh) * 2016-09-21 2016-12-14 北京佰才邦技术有限公司 一种资源分配的方法及基站

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
See also references of EP3664508A4
YUN CHAO: "Mobile edge computing A key technology towards 5G", ETSI WHITE PAPER NO. 11, 30 September 2015 (2015-09-30), XP055537310 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020207266A1 (zh) * 2019-04-08 2020-10-15 阿里巴巴集团控股有限公司 网络系统、实例管控方法、设备及存储介质
CN111564037A (zh) * 2020-04-14 2020-08-21 深圳市灵犀智汇科技有限公司 一种面向轨道交通的数据计算方法
CN111564037B (zh) * 2020-04-14 2022-06-10 深圳市灵犀智汇科技有限公司 一种面向轨道交通的数据计算方法

Also Published As

Publication number Publication date
US20200205040A1 (en) 2020-06-25
CN109429284B (zh) 2020-08-25
EP3664508A4 (en) 2020-07-22
CN109429284A (zh) 2019-03-05
EP3664508A1 (en) 2020-06-10

Similar Documents

Publication Publication Date Title
WO2019042000A1 (zh) 实例切换方法及相关装置
US11297543B2 (en) Method and apparatus for managing session to change a user plane function in a wireless communication system
CN113194157B (zh) 一种应用实例地址的转换方法和装置
CN110933623B (zh) 一种通信方法和装置
EP3409044B1 (en) Method and apparatus for implementing mobile edge application session connectivity and mobility
US20220174759A1 (en) Method and apparatus for operating wireless communication system having separated mobility management and session management
CN112153098B (zh) 一种应用迁移方法及装置
US11032745B2 (en) Handover for mobile edge computing applications in mobile networks
JP6195312B2 (ja) 通信システム
CN109156040B (zh) 一种通信控制的方法及相关网元
JP2023036640A (ja) イーサネットｐｄｕセッションのためのアンカー変更を提供する方法および関係するネットワークエンティティ／ノード
CN111937461B (zh) 分割基站中的rrc版本处理
US20210120620A1 (en) Communication Method and Apparatus
US10299181B2 (en) Method and apparatus for configuring disconnected TCP connection in communication system, handover support method and apparatus therefor
EP3570491B1 (en) Association management method and network node
US20100272068A1 (en) Method for supporting multiple interfaces in proxy mobile ipv6
US9247483B2 (en) Method and system for data traffic offload
WO2013107260A1 (zh) 中继节点移动过程中路由标识的处理方法、装置及系统
CN115226174B (zh) 一种定位管理切换方法、系统、电子设备和存储介质
CN113676962A (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: 18850083

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018850083

Country of ref document: EP

Effective date: 20200303