WO2022001298A1 - 通信方法和通信装置 - Google Patents

通信方法和通信装置 Download PDF

Info

Publication number
WO2022001298A1
WO2022001298A1 PCT/CN2021/088136 CN2021088136W WO2022001298A1 WO 2022001298 A1 WO2022001298 A1 WO 2022001298A1 CN 2021088136 W CN2021088136 W CN 2021088136W WO 2022001298 A1 WO2022001298 A1 WO 2022001298A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
mec
mec platform
application instance
application
Prior art date
Application number
PCT/CN2021/088136
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 EP21832819.3A priority Critical patent/EP4156780A4/en
Publication of WO2022001298A1 publication Critical patent/WO2022001298A1/zh
Priority to US18/147,166 priority patent/US11943286B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1014—Server selection for load balancing based on the content of a request
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/148—Migration or transfer of sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1029—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers using data related to the state of servers by a load balancer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0019—Control or signalling for completing the hand-off for data sessions of end-to-end connection adapted for mobile IP [MIP]
    • 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

Definitions

  • the present application relates to the field of communication, and more particularly, to a communication method and a communication device in the field of communication.
  • Multi-access edge computing can provide users with cloud-based computing capabilities at the edge of the operator's network close to mobile users, and users can use this capability to deploy applications at the network edge.
  • cloud computing capabilities After deploying cloud computing capabilities to the network edge, a carrier-class service environment with high performance, low latency and high bandwidth can be created to accelerate the distribution and download of various content, services and applications in the network, allowing consumers to enjoy higher quality web experience.
  • the core network can be divided into centralized control plane network functions and distributed user plane network functions.
  • the control plane network function can select the appropriate user plane network function. Therefore, switching of the user plane network function occurs, and the application instance corresponding to the user plane network function also needs to be switched. There is an urgent need to provide a method that can be used for switching application instances in the MEC scenario.
  • the present application provides a communication method and a communication device, which can be used for the switching of application instances in the MEC scenario, which is beneficial to ensure the continuity of the service and thus the user experience.
  • a communication method including: a multi-access edge computing MEC network element obtains information of a source application instance of an application accessed by a terminal device and information of a target application instance of the application; the MEC network element Send a first message to the first MEC platform, where the first message is used to request to migrate the user context of the application from the source application instance to the target application instance, wherein the source application instance is deployed in the the first MEC platform, where the target application instance is deployed on the second MEC platform; the MEC network element receives a second message from the first MEC platform, where the second message is used to instruct user context migration of the application state.
  • the MEC network element obtains the information of the source application instance and the information of the target application instance, and sends the first message request to the first MEC platform to perform the user context migration of the application, which can realize application-based application in the MEC scenario.
  • the user context migration of the application of the instance is conducive to ensuring the continuity of the business and thus the user experience.
  • the above-mentioned user context migration state may include states such as migration start, migration complete, or migration failure. Due to the movement of the terminal device, the data network will be switched, and the MEC platform corresponding to the data network will also be switched, that is, switched from the first MEC platform to the second MEC platform. In this embodiment of the present application, before the move, the terminal device accesses the application through the source application instance of the first MEC platform. After the move, and if the user context migration state indicates that the migration is complete, the terminal device can access the application through the second MEC platform. The target application instance of the platform accesses the application.
  • the method before the multi-access edge computing MEC network element acquires the information of the source application instance and the information of the target application instance, the method further includes: the MEC The network element receives a third message from the control plane network element of the core network, where the third message is used to notify that the user plane path of the terminal device has changed; the multi-access edge computing MEC network element obtains the information of the source application instance.
  • the MEC network element determining the information of the source application instance and the information of the target application instance based on the third message, wherein the source application instance is located in the source data network
  • the location corresponding to the access identifier of the target application instance is located at the location corresponding to the access identifier of the target data network.
  • the method further includes: the MEC network element sends a fourth message to the core network control plane network element based on the second message, the The fourth message is an acknowledgment or a negative acknowledgment to the third message.
  • the MEC network element may send the above-mentioned fourth message to the core network control plane network element. If the fourth message is an affirmative response, it means that the MEC network element accepts. The user context of the application is migrated, and the user context migration status of the application is migration completed. In this way, the core network control plane network element can activate the new user plane path, so that the terminal device can access the target application instance corresponding to the new user plane path. application. If the fourth message is a negative response, it means that the MEC network element rejects the user context migration of the application, or the user context migration status of the application is migration failure. In this case, the terminal device still uses the old user plane path corresponding to the The source application instance accesses the application.
  • the third message includes at least one of the following information: an identifier of the terminal device, an identifier of the application, and access to the source data network ID, the access ID of the target data network.
  • the MEC network element can determine the information of the source application instance corresponding to the application in the source data network according to the identifier of the application accessed by the terminal device and the access identifier of the source data network; The identifier of the accessed application and the access identifier of the target data network determine the information of the target application instance corresponding to the application in the target data network.
  • the method before the MEC network element receives the third message from the core network control plane network element, the method further includes: the MEC network element sends a message to the MEC network element to the The core network control plane network element sends a fifth message, where the fifth message is used to subscribe to the user plane path change event of the terminal device.
  • the above-mentioned MEC network element sending the fifth message to the core network control plane network element is to facilitate the core network control plane network element to send the third message to the MEC network element when the user plane path of the terminal device changes.
  • the change of the user plane path means that the terminal device has moved, and the user plane path of the terminal device needs to be changed, but the new user plane path has not been activated at this time, and the terminal device still accesses the application through the source application instance.
  • the MEC network element is an MEC orchestrator or an MEC platform manager.
  • the MEC network element in the embodiment of the present application can implement at least one function of the network element in the MEC orchestrator or the MEC platform manager.
  • the MEC network element includes an MEC orchestrator and an MEC platform manager, and the MEC network element sends a first message to the first MEC platform, including: the The MEC orchestrator sends the first message to the first MEC platform through the MEC platform manager; the MEC network element receives the second message from the first MEC platform, including: the MEC orchestrator sends the first message through the MEC platform manager.
  • the MEC platform manager receives the second message from the first MEC platform.
  • the above-mentioned MEC orchestrator may determine the information of the source application instance and the information of the target application instance based on the third message sent by the network element of the core network control plane.
  • the above-mentioned "the MEC orchestrator sends the first message to the first MEC platform through the MEC platform manager" means: the MEC orchestrator first sends the first message to the MEC platform manager, and the MEC platform manager then sends the first message to the MEC platform manager. Forwarded to the first MEC platform.
  • the method further includes: the MEC orchestrator sends a sixth message to the MEC platform manager, where the sixth message is used to subscribe to the application
  • the MEC platform manager receives the sixth message, and sends a first response message to the MEC orchestrator; the MEC orchestrator receives the first response message.
  • the method further includes: the MEC platform manager sending a seventh message to the first MEC platform, where the seventh message is used to subscribe to the The user context transition state of the application; the MEC platform manager receives the second response message from the first MEC platform.
  • the MEC orchestrator receives the second message from the first MEC platform through the MEC platform manager, including: the MEC platform management The MEC platform manager receives the second message from the first MEC platform; the MEC platform manager sends a third response message to the MEC platform; the MEC platform manager sends the second message to the MEC orchestrator message; the MEC orchestrator receives the second message, and sends a fourth response message to the MEC platform manager; the MEC platform manager receives the fourth response message.
  • another communication method including: the first multi-access edge computing MEC platform receives a third message from a core network control plane network element, where the third message is used to notify a user plane path of a terminal device has changed; the first MEC platform obtains, based on the third message, the information of the source application instance of the application accessed by the terminal device and the information of the target application instance of the application; the first MEC platform will The user context of the application is migrated from the source application instance to the target application instance, wherein the source application instance is deployed on the first MEC platform, and the target application instance is deployed on the second MEC platform.
  • the first MEC platform obtains, based on the third message, the information of the source application instance of the application accessed by the terminal device and the target application instance of the application information, including: the first MEC platform sends a request message to the MEC orchestrator based on the third message, where the request message is used to request the information of the target application instance; the first MEC platform receives the The information of the target application instance sent by the MEC orchestrator.
  • the method further includes: the first MEC platform sends a fourth message to the core network control plane network element, the fourth message is to all acknowledgement or negative acknowledgement of the third message.
  • the third message includes at least one of the following information: an identifier of the terminal device, an identifier of the application, and access to the source data network ID, the access ID of the target data network.
  • the method before the first multi-access edge computing MEC platform receives the third message from the core network control plane network element, the method further includes: the The first MEC platform sends a fifth message to the core network control plane network element, where the fifth message is used to subscribe to the user plane path change event of the terminal device.
  • a communication apparatus for executing the method in any possible implementation manner of the above aspects.
  • the apparatus includes a unit for performing the method in any one of the possible implementations of the above aspects.
  • a communication device including a processor, which is coupled to a memory and can be configured to execute instructions in the memory, so as to implement the method in any of the possible implementations of the above aspects.
  • the apparatus may also include a memory.
  • the apparatus may further include a communication interface to which the processor is coupled.
  • the communication device is an MEC network element.
  • the communication interface may be a transceiver, or an input/output interface.
  • the communication device is a chip configured in the MEC network element.
  • the communication interface may be an input/output interface.
  • a processor including: an input circuit, an output circuit, and a processing circuit.
  • the processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, so that the processor performs the method in any of the possible implementations of the above aspects.
  • the above-mentioned processor may be a chip
  • the input circuit may be an input pin
  • the output circuit may be an output pin
  • the processing circuit may be a transistor, a gate circuit, a flip-flop, and various logic circuits.
  • the input signal received by the input circuit may be received and input by, for example, but not limited to, a receiver
  • the signal output by the output circuit may be, for example, but not limited to, output to and transmitted by a transmitter
  • the circuit can be the same circuit that acts as an input circuit and an output circuit at different times.
  • the embodiments of the present application do not limit the specific implementation manners of the processor and various circuits.
  • a processing apparatus including a processor and a memory.
  • the processor is used to read the instructions stored in the memory, and can receive signals through the receiver and transmit signals through the transmitter, so as to execute the method in any possible implementation manner of the above aspects.
  • processors there are one or more processors and one or more memories.
  • the memory may be integrated with the processor, or the memory may be provided separately from the processor.
  • the memory can be a non-transitory memory, such as a read only memory (ROM), which can be integrated with the processor on the same chip, or can be separately set in different On the chip, the embodiment of the present application does not limit the type of the memory and the setting manner of the memory and the processor.
  • ROM read only memory
  • the relevant data interaction process such as sending indication information, may be a process of outputting indication information from the processor, and receiving capability information may be a process of receiving input capability information by the processor.
  • the data output by the processing can be output to the transmitter, and the input data received by the processor can be from the receiver.
  • the transmitter and the receiver may be collectively referred to as a transceiver.
  • the processing device in the sixth aspect may be a chip, and the processor may be implemented by hardware or by software.
  • the processor When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software
  • the processor can be a general-purpose processor, which is realized by reading software codes stored in a memory, and the memory can be integrated in the processor or located outside the processor and exist independently.
  • a computer program product includes: a computer program (also referred to as code, or instruction), which, when the computer program is executed, causes the computer to execute any one of the possible implementations of the above aspects method in .
  • a computer-readable storage medium stores a computer program (which may also be referred to as code, or an instruction), when it runs on a computer, causing the computer to execute any of the above aspects. method in one possible implementation.
  • a communication system including the aforementioned MEC network element and the MEC platform.
  • FIG. 1 is a schematic diagram of a system architecture provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of another system architecture provided by an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of another communication method provided by an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of another communication method provided by an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of another communication method provided by an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of another communication method provided by an embodiment of the present application.
  • FIG. 8 is a schematic block diagram of a communication apparatus provided by an embodiment of the present application.
  • FIG. 9 is a schematic block diagram of another communication apparatus provided by an embodiment of the present application.
  • LTE long term evolution
  • FDD frequency division duplex
  • UMTS universal mobile telecommunication system
  • 5th generation 5G system or new radio (NR)
  • NR new radio
  • the terminal equipment in the embodiments of the present application may also be referred to as: user equipment (user equipment, UE), mobile station (mobile station, MS), mobile terminal (mobile terminal, MT), access terminal, subscriber unit, subscriber station, Mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user equipment, etc.
  • user equipment user equipment
  • MS mobile station
  • MT mobile terminal
  • access terminal subscriber unit, subscriber station, Mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user equipment, etc.
  • the terminal device may be a device that provides voice/data connectivity to the user, such as a handheld device with a wireless connection function, a vehicle-mounted device, and the like.
  • some examples of terminals are: mobile phone (mobile phone), tablet computer, notebook computer, PDA, mobile internet device (MID), wearable device, virtual reality (virtual reality, VR) device, augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, and smart grids wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, cellular phone, cordless phone, session initiation protocol , SIP) telephones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, automotive A device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved public land mobile network (public land mobile network, PLMN), etc., are not
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices, which are the general term for the intelligent design of daily wear and the development of wearable devices using wearable technology, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones.
  • the terminal device may also be a terminal device in an Internet of Things (IoT) system.
  • IoT Internet of Things
  • IoT is an important part of the future development of information technology, and its main technical feature is that items pass through communication technology Connect with the network, so as to realize the intelligent network of human-machine interconnection and interconnection of things.
  • the network device in this embodiment of the present application may be a device for communicating with a terminal device, and the network device may be a transmission reception point (TRP), or may be an evolved NodeB (eNB, eNB) in the LTE system or eNodeB), can also be a home base station (for example, home evolved NodeB, or home Node B, HNB), base band unit (base band unit, BBU), and can also be cloud radio access network (cloud radio access network, CRAN)
  • the wireless controller in the scenario, or the access network device can be a relay station, an access point, a vehicle-mounted device, a wearable device, an access network device in a 5G network, or a future evolution of the public land mobile communication network (public land mobile communication network).
  • an access network device may include a centralized unit (CU) node, or a distributed unit (DU) node, or a RAN device including a CU node and a DU node, or a control plane CU node (CU-CP node) and user plane CU node (CU-UP node) and RAN equipment of DU node.
  • CU centralized unit
  • DU distributed unit
  • RAN device including a CU node and a DU node, or a control plane CU node (CU-CP node) and user plane CU node (CU-UP node) and RAN equipment of DU node.
  • CU-CP node control plane CU node
  • CU-UP node user plane CU node
  • the terminal device or the network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
  • This hardware layer includes hardware such as central processing unit (CPU), memory management unit (MMU), and memory (also called main memory).
  • the operating system may be any one or more computer operating systems that implement business processing through processes, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a Windows operating system.
  • the application layer includes applications such as browsers, address books, word processing software, and instant messaging software.
  • the embodiments of the present application do not specifically limit the specific structure of the execution body of the methods provided by the embodiments of the present application, as long as the program that records the codes of the methods provided by the embodiments of the present application can be executed to provide the methods provided by the embodiments of the present application.
  • the execution subject of the method provided by the embodiment of the present application may be a terminal device or a network device, or a functional module in the terminal device or network device that can call and execute a program.
  • various aspects or features of the present application may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques.
  • article of manufacture encompasses a computer program accessible from any computer readable device, carrier or medium.
  • computer readable media may include, but are not limited to, magnetic storage devices (eg, hard disks, floppy disks, or magnetic tapes, etc.), optical disks (eg, compact discs (CDs), digital versatile discs (DVDs) etc.), smart cards and flash memory devices (eg, erasable programmable read-only memory (EPROM), card, stick or key drives, etc.).
  • various storage media described herein can represent one or more devices and/or other machine-readable media for storing information.
  • the term "machine-readable medium” may include, but is not limited to, wireless channels and various other media capable of storing, containing, and/or carrying instructions and/or data.
  • Multi-access edge computing MEC
  • MEC can provide big data services, IoT services and data services, and open application programming interfaces (APIs) for third parties to rapidly deploy new services.
  • MEC servers usually have high computing power and are especially suitable for analyzing and processing large amounts of data.
  • the MEC server is mainly composed of three parts: the bottom-level infrastructure, the middle MEC platform and the upper-level applications.
  • An application is actually an application instance, and an application instance is a copy of the same application.
  • Application instances are deployed on required edge nodes.
  • the application on the terminal device is served by an application instance of an edge node at a certain moment.
  • the closer the application instance is to the terminal device the smaller the packet transmission delay between the application and the terminal device, and the higher the service quality.
  • the application instance 1 of the edge node 1 located at the position 1 is the optimal application instance of the terminal device.
  • the application instance 2 of the edge node 2 located at the position 2 is the optimal application instance of the terminal device.
  • the physical entity of the above-mentioned edge node is the MEC platform (MEC Platform).
  • MEC platform is used as an example for description later.
  • the system architecture 100 shown in FIG. 1 includes: a terminal device 110, an MEC network element 120, a first MEC platform 130, and a second MEC platform 140, wherein the source application instance is deployed on the first MEC platform 130, and the target application instance is deployed on the first MEC platform 130. on the second MEC platform 140 .
  • the terminal device 110 When the terminal device 110 is located near the location of the first MEC platform 130, it can access the source application instance through the first MEC platform 130. When the terminal device moves and is located near the location of the second MEC platform 140, it can access the source application instance through the second MEC platform 140. 140 Access the target application instance.
  • the source application instance and the target application instance here are different copies of the same application.
  • the MEC network element 120 is used to manage and deploy the MEC platform.
  • the terminal device 110 can access the above application examples through core network network elements, and the core network network elements are not shown in FIG. 1 .
  • the core network network elements may be composed of centralized control plane network function network elements and distributed user plane network function network elements.
  • the control plane network function network element can select the appropriate user plane network function network element. Therefore, the switching of the user plane network function network element will occur, which corresponds to the user plane network function network element.
  • the application instance also needs to be switched. That is, switching from the above source application instance to the target application instance.
  • ETSI European telecommunication standards institute
  • FIG. 2 is another system architecture 200 of an embodiment of the present application.
  • the system architecture 200 may include two parts: the MEC system level and the MEC host level.
  • the MEC system level is responsible for the overall control of the MEC system, and may specifically include the following network elements:
  • MEC host including MEC platform (MEC Platform), virtualization infrastructure (virtualization infrastructure) and MEC application (MEC app).
  • the virtual infrastructure provides virtualized computing, storage and network resources for MEC applications, and can provide continuous storage and time-related information for ME applications. It includes a data forwarding plane to execute data received from the ME platform. Forwarding rules and routing of traffic between various applications, services and networks.
  • the MEC platform is the core of the MEC reference architecture. It mainly receives traffic forwarding rules from the MEC platform manager, MEC application or MEC service, and issues instructions to the forwarding plane based on the forwarding rules.
  • the MEC platform includes service registration, discovery functions, and public services, etc., and can provide data flow distribution (traffic offload function, TOF), wireless network information service (radio network information service, RNIS), communication service (communication service) and service registration (service registry) and other modules in order to provide services for upper-layer application instances through these modules.
  • the MEC platform also supports the configuration of a local domain name system (DNS) proxy server, which can redirect data traffic to corresponding applications and services.
  • DNS domain name system
  • the MEC platform can also communicate with other MEC platforms through the Mp3 reference point. In the cooperation mechanism of the distributed MEC system, the Mp3 reference point can be used as the basis for the interconnection of different MEC platforms.
  • MEC applications are virtual machine instances running on the MEC virtualization infrastructure, and these applications communicate with the MEC platform through the Mp1 reference point.
  • the Mp1 reference point can also provide additional functions such as identifying application availability, preparing or relocating the application state for the user in the event of an MEC handover.
  • MEC orchestrator The core function provided by MEC.
  • the MEC orchestrator can macro-control the resources and capacity of the MEC network, including all deployed MEC hosts and services, available resources in each host, The instantiated MEC application and the topology of the network, etc.
  • the MEC orchestrator can measure the user's needs and the available resources of each host, and select the most suitable MEC host for it. If the user needs to switch the MEC host, the MEC orchestrator will to trigger the switching procedure.
  • the instantiation and termination of the MEC application is triggered through the Mm1 reference point between the MEC orchestrator and the operation support system.
  • the MEC orchestrator and the virtualized infrastructure manager manage virtualized resources and virtual machine images of applications through the Mm4 reference point, while maintaining state information of available resources.
  • MEC platform manager used to manage the MEC platform, manage the life cycle of MEC applications, and manage MEC application rules and requirements.
  • Life cycle management of MEC applications includes creation and termination of MEC applications, and provides MEC orchestrators with indication messages of application-related events.
  • the management of MEC application rules and requirements includes authentication, traffic rules, DNS configuration, and conflict coordination.
  • the Mm5 reference point is used between the MEC platform and the MEC platform manager, which can implement the configuration of the platform and traffic filtering rules, and is responsible for managing application relocation and supporting application life cycle procedures.
  • Mm2 is the reference point between the operation support system and the MEC platform manager, responsible for the configuration and performance management of the MEC platform.
  • Mm3 is the reference point between the MEC orchestrator and the MEC platform manager, and is responsible for providing support for MEC application lifecycle management and MEC application-related policies, as well as providing time-related information for MEC's available services.
  • Virtualization infrastructure manager It is used to manage the virtualization resources required by MEC applications. Management tasks include the allocation and release of virtual computing, storage, and network resources, and software images can also be stored on a virtualized infrastructure manager for rapid instantiation of MEC applications. At the same time, the virtualized infrastructure manager is also responsible for collecting the information of virtual resources, and reporting it to the upper management entities such as the MEC orchestrator and the MEC platform manager through the Mm4 reference point and the Mm6 reference point respectively.
  • Operations support system From the perspective of the MEC system, the operations support system is the highest level management entity that supports the operation of the system.
  • the operations support system receives requests to instantiate or terminate MEC applications from customer-facing service (CFS) portals and end devices (eg, UEs), checks application data packets and requests for integrity and authorization information. Request data packets authenticated and authorized by the operational support system are forwarded to the MEC orchestrator through the Mm1 reference point for further processing.
  • CFS customer-facing service
  • end devices eg, UEs
  • Customer-oriented service portal It is equivalent to a third-party access point. Developers use this interface to access various applications developed by themselves into the operator's MEC system. Enterprises or individual users can also choose through this interface. applications that interest them, and specify when and where they are used.
  • the CFS Portal can communicate with the Operational Support System via the Mx1 reference point.
  • User app LCM proxy an entity used by MEC users to request services related to application-related instantiation and termination. This entity can implement application relocation between the external cloud and the MEC system, and is responsible for authenticating all requests from the external cloud, which are then sent to the operations support system and the MEC orchestrator for further processing through the Mm8 and Mm9 reference points, respectively. It is worth noting that the user application lifecycle agent can only be accessed through the mobile network, and the Mx2 reference point provides the basis for the terminal device and the user application lifecycle agent to communicate with each other.
  • the MEC network element 120 may specifically implement the function of at least one network element in the MEC orchestrator or the MEC platform manager in FIG. 2, which is not limited in this embodiment of the present application.
  • system architecture 200 includes 3 different types of reference points. Among them, Mp represents a reference point related to MEC platform applications, Mm represents a reference point related to management, and Mx represents a reference point related to external entities.
  • system architecture 200 applied to the embodiments of the present application is only an example of a network architecture described from the perspective of reference point architecture, and the network architecture applied to the embodiments of the present application is not limited thereto. All the network architectures are applicable to the embodiments of the present application.
  • each network element eg, MEC orchestrator, MEC platform manager, etc.
  • the name of each network element is only an example, and does not limit the function of the network element itself.
  • the foregoing network elements may also have other names, which are not specifically limited in this embodiment of the present application.
  • some or all of the above-mentioned network elements may use the terminology in 5G, and may also use other names, etc., which will be uniformly described here, and will not be repeated below.
  • the names of the messages (or signaling) transmitted between the above network elements are only an example, and do not constitute any limitation on the functions of the messages themselves.
  • FIG. 3 shows a schematic flowchart of a communication method 300 according to an embodiment of the present application.
  • the method 300 may be applied to the system architecture 100 shown in FIG. 1 , and may also be applied to the system architecture 200 shown in FIG. 2 , and the embodiments of the present application are not limited thereto.
  • the MEC network element acquires the information of the source application instance of the application accessed by the terminal device and the information of the target application instance of the application.
  • the MEC network element sends a first message to the first MEC platform, where the first message is used to request to migrate the user context of the application from the source application instance to the target application instance, where the source application instance is deployed on the first MEC platform, the target application instance is deployed on the second MEC platform; correspondingly, the first MEC platform receives the first message.
  • the first MEC platform sends a second message to the MEC network element, where the second message is used to indicate the user context transition state of the application; correspondingly, the MEC network element receives the second message from the first MEC platform.
  • the above-mentioned user context migration state may include states such as migration start, migration complete, or migration failure. Due to the movement of the terminal device, the data network will be switched, and the MEC platform corresponding to the data network will also be switched, that is, switching from the first MEC platform to the second MEC platform. In this embodiment of the present application, before the move, the terminal device accesses the application through the source application instance of the first MEC platform. After the move, and if the user context migration state indicates that the migration is complete, the terminal device can access the application through the second MEC platform. The target application instance of the platform accesses the application.
  • the MEC network element obtains the information of the source application instance and the information of the target application instance, and sends the first message request to the first MEC platform to perform the user context migration of the application, which can realize application-based application in the MEC scenario.
  • the user context migration of the application of the instance is conducive to ensuring the continuity of the business and thus the user experience.
  • the MEC network element in this embodiment of the present application is an MEC orchestrator or an MEC platform manager.
  • the MEC network element in the embodiment of the present application can implement at least one function of the network element in the MEC orchestrator or the MEC platform manager.
  • the method further includes: the MEC network element receives a third message from the core network control plane network element, the The third message is used to notify that the user plane path of the terminal device has changed; the MEC network element obtains the information of the source application instance and the information of the target application instance, including: the MEC network element determines the source application based on the third message Instance information and information of the target application instance, wherein the source application instance is located at the position corresponding to the access identifier of the source data network, and the target application instance is located at the position corresponding to the access identifier of the target data network.
  • the above-mentioned third message includes at least one of the following information: an identifier of the terminal device, an identifier of the application, an access identifier of the source data network, and an access identifier of the target data network.
  • the MEC network element can determine the information of the source application instance corresponding to the application in the source data network according to the identifier of the application accessed by the terminal device and the access identifier of the source data network; The identifier of the accessed application and the access identifier of the target data network determine the information of the target application instance corresponding to the application in the target data network.
  • the method further includes: based on the second message, the MEC network element sends a fourth message to the core network control plane network element, where the fourth message is an affirmative response or a negative response to the third message answer.
  • the MEC network element may send the above-mentioned fourth message to the core network control plane network element. If the fourth message is an affirmative response, it means that the MEC network element accepts. The user context of the application is migrated, and the user context migration status of the application is migration completed. In this way, the core network control plane network element can activate the new user plane path, so that the terminal device can access the target application instance corresponding to the new user plane path. application. If the fourth message is a negative response, it means that the MEC network element rejects the user context migration of the application, or the user context migration status of the application is migration failure. In this case, the terminal device still uses the old user plane path corresponding to the The source application instance accesses the application.
  • the method further includes: the MEC network element sends a fifth message to the core network control plane network element, the The fifth message is used to subscribe to the user plane path change event of the terminal device, so that the core network control plane network element sends the third message to the MEC network element when the user plane path of the terminal device changes.
  • the change of the user plane path means that the terminal device has moved, and the user plane path of the terminal device needs to be changed, but the new user plane path has not been activated at this time, and the terminal device still accesses the application through the source application instance.
  • the MEC network element includes an MEC orchestrator and a MEC platform manager, and the actions performed by the MEC network element may specifically include: the MEC orchestrator obtains the source application instance of the application accessed by the terminal device. information and information of the target application instance of the application; the MEC orchestrator sends the first message to the first MEC platform through the MEC platform manager; the MEC orchestrator receives the second message from the first MEC platform through the MEC platform manager .
  • the above-mentioned MEC orchestrator may determine the information of the source application instance and the information of the target application instance based on the third message sent by the network element of the core network control plane.
  • the above-mentioned "the MEC orchestrator sends the first message to the first MEC platform through the MEC platform manager" means: the MEC orchestrator first sends the first message to the MEC platform manager, and the MEC platform manager then sends the first message to the MEC platform manager. Forwarded to the first MEC platform.
  • the above method further includes: the MEC orchestrator sends a message for subscribing to the user context transition state of the application to the MEC platform manager; correspondingly, the MEC platform manager receives the message.
  • the MEC platform manager sends a first response message to the MEC orchestrator, indicating that the message for subscribing to the user context transition state of the application is received; correspondingly, the MEC orchestrator receives the first response message.
  • the above method further includes: the MEC platform manager sends a message for subscribing to the user context transition state of the application to the first MEC platform; correspondingly, the first MEC platform receives the message.
  • the first MEC platform sends a second response message to the MEC platform manager, indicating that the message for subscribing to the user context transition state of the application is received; correspondingly, the MEC platform manager receives the second response message.
  • the above-mentioned MEC orchestrator receives the second message from the first MEC platform through the MEC platform manager, including: the first MEC platform sends a message for indicating the user context transition state to the MEC platform manager, Correspondingly, the MEC platform manager receives the message.
  • the MEC platform manager sends a third response message to the first MEC platform, indicating that a message for indicating the user context transition state has been received.
  • the first MEC platform receives the third response message.
  • the MEC platform manager sends a message for indicating the user context transition state to the MEC orchestrator, and correspondingly, the MEC orchestrator receives the message.
  • the MEC orchestrator sends a fourth response message to the MEC platform manager, indicating that a message for indicating the user context transition state has been received.
  • the MEC platform manager receives the fourth response message.
  • FIG. 4 shows a schematic flowchart of a communication method 400 according to an embodiment of the present application.
  • the method 400 may be applied to the system architecture 100 shown in FIG. 1 , and may also be applied to the system architecture 200 shown in FIG. 2 , and the embodiments of the present application are not limited thereto.
  • the core network control plane network element sends a third message to the first multi-access edge computing MEC platform, where the third message is used to notify that the user plane path of the terminal device has changed; correspondingly, the first MEC platform receives the third message.
  • the third message is used to notify that the user plane path of the terminal device has changed; correspondingly, the first MEC platform receives the third message.
  • the first MEC platform obtains, based on the third message, the information of the source application instance of the application accessed by the terminal device and the information of the target application instance of the application;
  • the first MEC platform migrates the user context of the application from the source application instance to the target application instance, where the source application instance is deployed on the first MEC platform, and the target application instance is deployed on the second MEC platform .
  • the information of the source application instance and the information of the target application instance are obtained through the MEC platform, and then the user context migration of the application is performed, so that the user context migration of the application based on the application instance can be realized in the MEC scenario, which is beneficial to Ensure business continuity, thereby safeguarding user experience.
  • the first MEC platform obtains, based on the third message, the information of the source application instance of the application accessed by the terminal device and the information of the target application instance of the application, including: the first MEC platform is based on The third message sends a request message to the MEC orchestrator, where the request message is used to request the information of the target application instance; the first MEC platform receives the information of the target application instance sent by the MEC orchestrator.
  • the method further includes: the first MEC platform sends a fourth message to the network element of the core network control plane, where the fourth message is a positive response or a negative response to the third message.
  • the third message includes at least one of the following information: an identifier of the terminal device, an identifier of the application, an access identifier of the source data network, and an access identifier of the target data network.
  • the method further includes: the first MEC platform reports to the core network control plane network The element sends a fifth message, where the fifth message is used to subscribe to the user plane path change event of the terminal device.
  • FIG. 5 shows a schematic flowchart of another communication method 500 according to an embodiment of the present application.
  • the method 500 may be applied to the system architecture 100 shown in FIG. 1 , and may also be applied to the system architecture 200 shown in FIG. 2 , and the embodiments of the present application are not limited thereto.
  • a terminal device accesses an application through a source application instance.
  • the source application instance is deployed on the first MEC platform.
  • the MEC orchestrator sends a subscription message to the core network element for subscribing to a user plane path change event.
  • the core network element receives the subscription message.
  • the subscription message may be the fifth message in the aforementioned method 300 .
  • the above-mentioned core network element may be a core network control plane network element, for example, a network exposure function (NEF) or a policy control function (PCF).
  • NEF network exposure function
  • PCF policy control function
  • the terminal device moves, triggering user plane path switching.
  • the core network element since the MEC orchestrator subscribes to the user plane path change event, the core network element will send a notification message to the MEC orchestrator to notify the MEC orchestrator that the user plane path of the terminal device changes.
  • the MEC orchestrator receives the notification message.
  • the notification message may be the third message in the aforementioned method 300 .
  • the above notification message may also be called a user plane path change event notification or other names.
  • the above notification message may include the identifier of the terminal device, the identifier of the application accessed by the terminal device, the access identifier of the source data network, and the access identifier of the target data network.
  • the identifier of the terminal device may be an Internet protocol (Internet protocol, IP) address of the terminal device, or a generic public subscription identifier (generic public subscription identifier, GPSI) of the terminal device, etc., which is not limited in this embodiment of the present application.
  • the MEC orchestrator obtains the information of the source application instance and the information of the target application instance of the application accessed by the terminal device according to the above notification message.
  • the data network identifies the deployment location of the application instance
  • the MEC orchestrator can determine the location of the application in the source application instance corresponding to the source data network according to the identifier of the application accessed by the terminal device and the access identifier of the source data network. information; the MEC orchestrator can determine the information of the target application instance corresponding to the application in the target data network according to the identifier of the application accessed by the terminal device and the access identifier of the target data network.
  • the information of the above-mentioned source application instance includes the identifier of the source application instance, the IP address of the source application instance and the port number of the source application instance; the information of the above-mentioned target application instance includes the identification of the target application instance, the IP address of the target application instance. and the port number of the target application instance.
  • the MEC orchestrator sends a migration request message to the first MEC platform through the MEC manager, for requesting user context information of the application to be migrated.
  • the first MEC platform receives the migration request message through the MEC manager.
  • the migration request message includes the identification of the terminal device, the information of the source application instance and the information of the target application instance.
  • the first MEC platform sends a migration request message to the second MEC platform, which is used to request the user context information of the migration application.
  • the second MEC platform receives the migration request message.
  • the migration request message may be the first message in the foregoing method 300 .
  • the migration request message includes the identifier of the terminal device and the information of the target application instance.
  • the above-mentioned first MEC platform may directly send a migration request message to the second MEC platform, or may send a migration request message to the second MEC platform through a dedicated application mobility service entity, which is not limited in this embodiment of the present application.
  • the second MEC platform sends a response message to the first MEC platform, indicating that the above-mentioned migration request message is received and the user context migration of the application is accepted.
  • the first MEC platform receives the response message.
  • the second MEC platform sends a transition state notification message to the first MEC platform, which is used to notify the transition state of the user context.
  • the migration status of the user context may include migration started, migration completed, or migration failed, and the like.
  • the first MEC platform receives the migration state notification message.
  • the migration state notification message may be the second message in the foregoing method 300 .
  • the above-mentioned second MEC platform may directly send a migration state notification message to the first MEC platform, or may send a migration state notification message to the first MEC platform through a dedicated application mobility service entity, which is not performed in this embodiment of the present application. limited.
  • the first MEC platform sends a response message to the second MEC platform, indicating that the above-mentioned migration state notification message is received.
  • the second MEC platform receives the response message.
  • the first MEC platform sends the above-mentioned migration state notification message to the MEC orchestrator through the MEC platform manager.
  • the migration state notification message indicates that the user context migration is completed.
  • the MEC orchestrator receives the migration status notification message through the MEC platform manager.
  • the migration state notification message may also be called a user context migration reply message or other names.
  • the MEC orchestrator sends a response message to the core network element, where the response message is used to respond to the notification message in S504.
  • the response message is an affirmative response, indicating that the context migration is completed.
  • the core network element receives the response message.
  • the response message may be the fourth message in the aforementioned method 300 .
  • the reply message may also be called a user plane path change event reply message or other names.
  • the core network element activates a new user plane path.
  • the terminal device accesses the application through the target application instance on the second MEC platform, that is, accesses the application through a new user plane path.
  • the communication method of the embodiment of the present application can realize the user context migration of the application based on the application instance in the MEC scenario, which is beneficial to ensure the continuity of the service and thus the user experience.
  • the MEC orchestrator, the MEC platform manager, and the first MEC platform use a synchronous manner for message interaction, that is, the first MEC platform detects that the user context migration is completed before passing the MEC platform manager to the MEC orchestrator.
  • Send a user context migration response message ie, the above seventh response message.
  • the following method 600 illustrates another way of message interaction.
  • the method 600 only shows the message interaction process between the MEC orchestrator, the MEC platform manager, and the first MEC platform, and the steps for other network elements (such as terminal equipment, core network elements) are the same as the method 500, No longer.
  • FIG. 6 shows a schematic flowchart of another communication method 600 according to an embodiment of the present application.
  • the method 600 may be applied to the system architecture 100 shown in FIG. 1 , and may also be applied to the system architecture 200 shown in FIG. 2 , and the embodiments of the present application are not limited thereto.
  • the MEC orchestrator sends a subscription message to the MEC platform manager for subscribing to the user context transition state.
  • the MEC platform manager receives the subscription message.
  • the subscription message may be the sixth message in the aforementioned method 300 .
  • the subscription request message includes the identifier of the terminal device, the identifier of the source application instance, and the identifier of the target application instance.
  • the MEC platform manager sends a response message to the MEC orchestrator, indicating that the subscription message is received.
  • the MEC orchestrator receives the reply message.
  • the response message may be the first response message in the aforementioned method 300 .
  • the MEC platform manager sends a subscription message to the first MEC platform for subscribing to the user context transition state.
  • the first MEC platform receives the subscription message.
  • the subscription message may be the seventh message in the aforementioned method 300 .
  • the first MEC platform sends a response message to the MEC platform manager, indicating that the subscription message is received.
  • the MEC platform manager receives the reply message.
  • the response message may be the second response message in the aforementioned method 300 .
  • the first MEC platform sends a transition state notification message to the MEC platform manager, where the transition state notification message is used to notify the transition state of the user context.
  • the migration status of the user context may include migration started, migration completed, or migration failed, and the like.
  • the MEC platform manager receives the migration status notification message.
  • the MEC platform manager sends a response message to the first MEC platform, indicating that the transition state notification message is received.
  • the first MEC platform receives the response message.
  • the response message may be the third response message in the aforementioned method 300 .
  • the MEC platform manager sends the above-mentioned migration state notification message to the MEC orchestrator.
  • the MEC orchestrator receives the migration state notification message.
  • the MEC orchestrator sends a response message to the MEC platform manager, indicating that the transition state notification message is received.
  • the MEC platform manager receives the reply message.
  • the response message may be the fourth response message in the aforementioned method 300 .
  • S605 to S608 may replace S512 in the method 500 .
  • S601 to S604 may be performed in any time period before S510, which is not limited in this embodiment of the present application.
  • FIG. 7 shows a schematic flowchart of another communication method 700 according to an embodiment of the present application.
  • the method 700 may be applied to the system architecture 100 shown in FIG. 1 , and may also be applied to the system architecture 200 shown in FIG. 2 , and the embodiments of the present application are not limited thereto.
  • a terminal device accesses an application through a source application instance.
  • the source application instance is deployed on the first MEC platform.
  • the source application instance sends a subscription message to the first MEC platform for subscribing to the mobility notification event of the terminal device.
  • the first MEC platform receives the subscription message.
  • the subscription message may carry the identifier of the above-mentioned terminal device.
  • the first MEC platform sends a subscription message to the core network element for subscribing to the user plane path change event.
  • the core network element receives the subscription message.
  • the subscription message may be the fifth message in the aforementioned method 300 .
  • the above-mentioned core network element may be a core network control plane network element, for example, a network exposure function (NEF) or a policy control function (PCF).
  • NEF network exposure function
  • PCF policy control function
  • the terminal device moves, triggering user plane path switching.
  • the core network element since the first MEC platform subscribes to the user plane path change event, the core network element will send a notification message to the first MEC platform to notify the first MEC platform that the user plane path of the terminal device changes.
  • the first MEC platform receives the notification message.
  • the notification message may be the third message in the aforementioned method 300 .
  • the above notification message may also be called a user plane path change event notification or other names.
  • the above notification message may include the identifier of the terminal device, the identifier of the application accessed by the terminal device, the access identifier of the source data network, and the access identifier of the target data network.
  • the identifier of the terminal device may be an Internet protocol (Internet protocol, IP) address of the terminal device, or a generic public subscription identifier (generic public subscription identifier, GPSI) of the terminal device, etc., which is not limited in this embodiment of the present application.
  • the first MEC platform sends a migration request message to the MEC orchestrator through the MEC platform manager, where the migration request message may include at least one of the following information: an identifier of a terminal device, an identifier of an application, and an access identifier of the target data network.
  • the MEC orchestrator receives the migration request message.
  • the MEC orchestrator determines information of the target application instance of the application accessed by the terminal device according to the above-mentioned migration request message.
  • the data network identifies the deployment location of the application instance, and the MEC orchestrator can determine the application's location in the target application instance corresponding to the target data network according to the identifier of the application accessed by the terminal device and the access identifier of the target data network. information.
  • the information about the target application instance includes the identifier of the target application instance, the IP address of the target application instance, and the port number of the target application instance.
  • the MEC orchestrator sends a migration response message to the first MEC platform through the MEC manager.
  • the first MEC platform receives the migration response message through the MEC manager.
  • the migration response message includes the identifier of the terminal device and the information of the target application instance.
  • the first MEC platform sends a migration request message to the second MEC platform, which is used to request the user context information of the migration application.
  • the second MEC platform receives the migration request message.
  • the migration request message may be the first message in the foregoing method 300 .
  • the migration request message includes the identifier of the terminal device and the information of the target application instance.
  • the above-mentioned first MEC platform may directly send the second migration request message to the second MEC platform, or may send the second migration request message to the second MEC platform through a dedicated application mobility service entity. This is not limited.
  • the second MEC platform sends a response message to the first MEC platform, indicating that the above-mentioned migration request message is received and the user context migration of the application is accepted.
  • the first MEC platform receives the response message.
  • the second MEC platform sends a transition state notification message to the first MEC platform, which is used to notify the transition state of the user context.
  • the migration status of the user context may include migration started, migration completed, or migration failed, and the like.
  • the first MEC platform receives the migration state notification message.
  • the migration state notification message may be the second message in the foregoing method 300 .
  • the above-mentioned second MEC platform may directly send a migration state notification message to the first MEC platform, or may send a migration state notification message to the first MEC platform through a dedicated application mobility service entity, which is not performed in this embodiment of the present application. limited.
  • the first MEC platform sends a response message to the second MEC platform, indicating that the above-mentioned migration state notification message is received.
  • the second MEC platform receives the response message.
  • the first MEC platform sends a response message to the core network element, where the response message is used to respond to the notification message in S705.
  • the response message is an affirmative response, indicating that the user context migration is completed.
  • the core network element receives the response message.
  • the response message may be the fourth message in the aforementioned method 300 .
  • the reply message may also be called a user plane path change event reply message or other names.
  • the core network element activates a new user plane path.
  • the terminal device accesses the application through the target application instance on the second MEC platform, that is, accesses the application through a new user plane path.
  • the communication method of the embodiment of the present application can realize the user context migration of the application based on the application instance in the MEC scenario, which is beneficial to ensure the continuity of the service and thus the user experience.
  • the target application instance already exists on the second MEC platform, and the user context of the application is migrated from the source application instance to the target application instance. If the target application instance does not exist on the second MEC platform, before migrating the user context of the application, the target application instance needs to be created on the second MEC platform, which will not be repeated here.
  • FIG. 8 shows a communication apparatus 800 provided by an embodiment of the present application.
  • the apparatus 800 includes a processing unit 810 and a transceiver unit 820 .
  • the apparatus 800 may be the aforementioned MEC network element, or may be a chip in the MEC network element, for executing each process or step corresponding to the MEC network element in the foregoing method 300 .
  • the processing unit 810 is used for: acquiring the information of the source application instance of the application accessed by the terminal device and the information of the target application instance of the application; the transceiver unit 820 is used for: sending a first message to the first MEC platform, the said The first message is used to request to migrate the user context of the application from the source application instance to the target application instance, wherein the source application instance is deployed on the first MEC platform, and the target application instance is deployed on the The second MEC platform; the transceiver unit 820 is further configured to: receive a second message from the first MEC platform, where the second message is used to indicate the user context transition state of the application.
  • the transceiver unit 820 is further configured to: receive a third message from a control plane element of the core network, where the third message is used to notify the user plane path of the terminal device that the path has changed; the processing unit 810 is specifically configured to: determine the information of the source application instance and the information of the target application instance based on the third message, wherein the source application instance is located at the position corresponding to the access identifier of the source data network, and the The target application instance is located at the position corresponding to the access identifier of the target data network.
  • the transceiver unit 820 is further configured to: based on the second message, send a fourth message to the core network control plane network element, where the fourth message is an affirmative response to the third message or negative answer.
  • the third message includes at least one of the following information: an identifier of the terminal device, an identifier of the application, an access identifier of the source data network, and an access identifier of the target data network.
  • the transceiver unit 820 is further configured to: send a fifth message to the control plane network element of the core network, where the fifth message is used to subscribe to a user plane path change event of the terminal device.
  • the apparatus is an MEC orchestrator or an MEC platform manager.
  • the apparatus includes an MEC orchestrator and a MEC platform manager, and the MEC orchestrator includes: a first transceiver unit configured to send the first MEC platform to the first MEC platform through the MEC platform manager message; and, receiving, by the MEC platform manager, the second message from the first MEC platform.
  • the MEC orchestrator includes: a first transceiver unit configured to send the first MEC platform to the first MEC platform through the MEC platform manager message; and, receiving, by the MEC platform manager, the second message from the first MEC platform.
  • the first transceiver unit is further configured to: send a sixth message to the MEC platform manager, where the sixth message is used to subscribe to the user context transition state of the application;
  • the MEC platform manager includes : a second transceiver unit, configured to receive the sixth message and send a first response message to the MEC orchestrator;
  • the first transceiver unit is further configured to: receive the first response message.
  • the MEC platform manager includes: a second transceiver unit configured to send a seventh message to the first MEC platform, where the seventh message is used to subscribe to the user context transition state of the application; and receiving A second reply message from the first MEC platform.
  • the MEC platform manager includes: a second transceiver unit, configured to receive the second message from the first MEC platform; send a third response message to the MEC platform;
  • the MEC orchestrator sends the second message;
  • the MEC orchestrator includes: a first transceiving unit, configured to receive the second message and send a fourth reply message to the MEC platform manager; the second transceiving unit The unit is further configured to: receive the fourth response message.
  • the above-mentioned transceiving unit, first transceiving unit, and second transceiving unit may be three independent units, or may be integrated units.
  • the first transceiving unit is used to perform the transceiving action corresponding to the transceiving unit.
  • the transceiver unit and the first transceiver unit are integrated into one unit, or the second transceiver unit is used to perform the transceiver action corresponding to the transceiver unit.
  • the transceiver unit and the second transceiver unit are integrated into one unit, which is not made in this embodiment of the application. limited.
  • the apparatus 800 may be the aforementioned first MEC platform, or may be a chip in the first MEC platform, for executing each process or step corresponding to the first MEC platform in the foregoing method 400 .
  • the transceiver unit 820 is configured to: receive a third message from a control plane network element of the core network, where the third message is used to notify that the user plane path of the terminal device has changed; the processing unit 810 is configured to: based on the third message message, obtain the information of the source application instance of the application accessed by the terminal device and the information of the target application instance of the application; and, migrate the user context of the application from the source application instance to the target application instance , wherein the source application instance is deployed on the device, and the target application instance is deployed on the second MEC platform.
  • the processing unit 810 is specifically configured to: send a request message to the MEC orchestrator based on the third message, where the request message is used to request the information of the target application instance; receive the message sent by the MEC orchestrator information about the target application instance.
  • the transceiver unit 820 is further configured to: send a fourth message to the core network control plane network element, where the fourth message is a positive response or a negative response to the third message.
  • the third message includes at least one of the following information: an identifier of the terminal device, an identifier of the application, an access identifier of the source data network, and an access identifier of the target data network.
  • the transceiver unit 820 is further configured to: send a fifth message to the control plane network element of the core network, where the fifth message is used to subscribe to a user plane path change event of the terminal device.
  • the apparatus 800 here is embodied in the form of functional units.
  • the term "unit” as used herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor for executing one or more software or firmware programs (eg, a shared processor, a dedicated processor, or a group of processors, etc.) and memory, merge logic, and/or other suitable components to support the described functions.
  • ASIC application specific integrated circuit
  • the apparatus 800 may be specifically the MEC network element or the first MEC platform in the foregoing method embodiments, and the apparatus 800 may be configured to perform the communication with the MEC network element or the first MEC platform in the foregoing method embodiments.
  • Various processes and/or steps corresponding to the first MEC platform are not repeated here in order to avoid repetition.
  • the apparatus 800 of each of the above solutions has the function of implementing the corresponding steps performed by the MEC network element or the first MEC platform in the above method; the function may be implemented by hardware, or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the transceiver unit may include a receiving unit and a sending unit, the sending unit may be replaced by a transmitter, the receiving unit may be replaced by a receiver, and other units, such as a processing unit, may be replaced by a processor, respectively performing the transceiver in each method embodiment. operations and related processing operations.
  • the device in FIG. 8 may also be a chip or a system of chips, such as a system on chip (system on chip, SoC).
  • the transceiving unit ie, the receiving unit and the transmitting unit
  • the transceiving circuit of the chip which is not limited herein.
  • FIG. 9 shows yet another communication apparatus 900 provided by an embodiment of the present application.
  • the apparatus 900 includes a processor 910 , a transceiver 920 and a memory 930 .
  • the processor 910, the transceiver 920 and the memory 930 communicate with each other through an internal connection path, the memory 930 is used to store instructions, and the processor 910 is used to execute the instructions stored in the memory 930 to control the transceiver 920 to send signals and / or receive signals.
  • the apparatus 900 is configured to execute each process or step corresponding to the MEC network element in the foregoing method 300 .
  • the processor 910 is configured to: acquire information of the source application instance of the application accessed by the terminal device and information of the target application instance of the application; the transceiver unit 820 is configured to: send a first message to the first MEC platform, the The first message is used to request to migrate the user context of the application from the source application instance to the target application instance, wherein the source application instance is deployed on the first MEC platform, and the target application instance is deployed on the The second MEC platform; the transceiver 920 is further configured to: receive a second message from the first MEC platform, where the second message is used to indicate the user context transition state of the application.
  • the apparatus 900 is configured to execute each process or step corresponding to the first MEC platform in the foregoing method 400 .
  • the transceiver 920 is configured to: receive a third message from a control plane element of the core network, where the third message is used to notify that the user plane path of the terminal device has changed; the processor 910 is configured to: based on the third message message, obtain the information of the source application instance of the application accessed by the terminal device and the information of the target application instance of the application; and, migrate the user context of the application from the source application instance to the target application instance , wherein the source application instance is deployed on the device, and the target application instance is deployed on the second MEC platform.
  • the apparatus 900 may specifically be the MEC network element or the first MEC platform in the above method embodiments, and may be used to execute various steps and/or processes corresponding to the MEC network element or the first MEC platform in the above method embodiments.
  • the memory 930 may include read only memory and random access memory and provide instructions and data to the processor. A portion of the memory may also include non-volatile random access memory.
  • the memory may also store device type information.
  • the processor 910 may be configured to execute the instructions stored in the memory, and when the processor 910 executes the instructions stored in the memory, the processor 910 is configured to execute the above method embodiments corresponding to the MEC network element or the first MEC platform the individual steps and/or processes.
  • transceivers described above may include transmitters and receivers.
  • the transceiver may further include antennas, and the number of the antennas may be one or more.
  • the memory can be a separate device or integrated in the processor.
  • Each of the above-mentioned devices or some of the devices can be implemented by being integrated into a chip, such as a baseband chip.
  • the transceiver in FIG. 9 may also be a communication interface, which is not limited herein.
  • the above-mentioned MEC network element or the first MEC platform may be either a physical entity device or a virtual functional network element, which is not limited herein.
  • the names of the first message, the second message, and other various messages are used.
  • these messages are merely examples to illustrate the content to be carried or the functions to be implemented, and the specific names of the messages do not limit the application, for example, notification messages, response messages, and so on.
  • These messages can be specific messages or some fields in the message.
  • These messages can also represent various serviced operations.
  • the processor of the above device may be a central processing unit (central processing unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (digital signal processor, DSP) ), application specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
  • the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM), which acts as an external cache.
  • RAM random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • direct rambus RAM direct rambus RAM
  • the present application further provides a computer program product, the computer program product includes: computer program code, when the computer program code is run on a computer, the computer is made to execute any one of the above embodiments.
  • the method corresponding to any network element For example, the computer may execute the method corresponding to the MEC network element in the above method 300 , or the method corresponding to the first MEC platform in the above method 400 .
  • the present application further provides a computer-readable medium, where program codes are stored in the computer-readable medium, and when the program codes are run on a computer, the computer is made to execute the programs shown in FIGS. 3 to 7 .
  • a method corresponding to any one of the network elements in any one of the embodiments is shown.
  • the computer may execute the method corresponding to the MEC network element in the above method 300 , or the method corresponding to the first MEC platform in the above method 400 .
  • the present application further provides a system, which includes one or more network elements in the foregoing method embodiments.
  • the system may include the MEC network element in the method 300 described above.
  • the system may include the first MEC platform in the method 400 described above.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line, DSL) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, or the like that includes an integration of one or more available media.
  • the available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, high-density digital video discs (DVDs)), or semiconductor media (eg, solid state discs, SSD)) etc.
  • a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer.
  • an application running on a computing device and the computing device may be components.
  • One or more components may reside within a process and/or thread of execution, and a component may be localized on one computer and/or distributed between two or more computers.
  • these components can execute from various computer readable media having various data structures stored thereon.
  • a component may, for example, be based on a signal having one or more data packets (eg, data from two components interacting with another component between a local system, a distributed system, and/or a network, such as the Internet interacting with other systems via signals) Communicate through local and/or remote processes.
  • data packets eg, data from two components interacting with another component between a local system, a distributed system, and/or a network, such as the Internet interacting with other systems via signals
  • At least one means one or more, and “plurality” means two or more.
  • And/or which describes the association relationship of the associated objects, means that there can be three kinds of relationships, for example, A and/or B, it can mean that A exists alone, A and B exist at the same time, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the associated objects are an “or” relationship.
  • At least one item(s) below” or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s).
  • At least one (a) of a, b or c may represent: a, b, c, a-b, a-c, b-c or a-b-c, wherein a, b, c may be single or multiple.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and 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 in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution, and the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, removable hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes .

Landscapes

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

Abstract

本申请提供了一种通信方法和通信装置，能够用于多接入边缘计算MEC场景下的应用实例的切换，有利于保障业务的连续性，从而保障用户体验。该方法包括：MEC网元获取终端设备所访问的应用的源应用实例的信息和该应用的目标应用实例的信息；该MEC网元向第一MEC平台发送第一消息，该第一消息用于请求将该应用的用户上下文从该源应用实例迁移至该目标应用实例，其中，该源应用实例部署在该第一MEC平台，该目标应用实例部署在第二MEC平台；该MEC网元接收来自该第一MEC平台的第二消息，该第二消息用于指示该应用的用户上下文迁移状态。

Description

通信方法和通信装置
本申请要求于2020年06月29日提交中国专利局、申请号为202010603843.6、申请名称为“通信方法和通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，更具体地，涉及通信领域中的一种通信方法和通信装置。
背景技术
多接入边缘计算(multi-access edge computing，MEC)可以在靠近移动用户的运营商网络的边缘为用户提供基于云计算的能力，用户可以利用该能力在网络边缘部署应用。将云计算能力部署到网络边缘后，可以创造出一个具备高性能、低延迟与高带宽的电信级服务环境，加速网络中各项内容、服务及应用的分发和下载，让消费者享有更高质量的网络体验。
随着通信系统的发展，核心网可以分为由集中的控制面网络功能和分布式的用户面网络功能组成。当终端设备在不同的区域间移动时，控制面网络功能可以选择合适的用户面网络功能，因此，会产生用户面网络功能的切换，与用户面网络功能所对应的应用实例也需要进行切换。目前亟需提供一种方法，能够用于MEC场景下的应用实例的切换。
发明内容
本申请提供一种通信方法和通信装置，能够用于MEC场景下的应用实例的切换，有利于保障业务的连续性，从而保障用户体验。
第一方面，提供了一种通信方法，包括：多接入边缘计算MEC网元获取终端设备所访问的应用的源应用实例的信息和所述应用的目标应用实例的信息；所述MEC网元向第一MEC平台发送第一消息，所述第一消息用于请求将所述应用的用户上下文从所述源应用实例迁移至所述目标应用实例，其中，所述源应用实例部署在所述第一MEC平台，所述目标应用实例部署在第二MEC平台；所述MEC网元接收来自所述第一MEC平台的第二消息，所述第二消息用于指示所述应用的用户上下文迁移状态。
本申请实施例的通信方法，通过MEC网元获取源应用实例的信息和目标应用实例的信息，向第一MEC平台发送第一消息请求进行应用的用户上下文迁移，能够在MEC场景中实现基于应用实例的应用的用户上下文迁移，有利于保障业务的连续性，从而保障用户体验。
上述用户上下文迁移状态可以包括迁移开始、迁移完成、或者迁移失败等状态。由于终端设备的移动，数据网络会发生切换，与数据网络对应的MEC平台也会发生切换，即从第一MEC平台切换至第二MEC平台。在本申请实施例中，在移动之前，终端设备通过第一MEC平台的源应用实例访问应用，在移动之后，且在用户上下文迁移状态表示迁 移完成的情况下，该终端设备可以通过第二MEC平台的目标应用实例访问该应用。
结合第一方面，在第一方面的某些实现方式中，在所述多接入边缘计算MEC网元获取源应用实例的信息和目标应用实例的信息之前，所述方法还包括：所述MEC网元接收来自核心网控制面网元的第三消息，所述第三消息用于通知所述终端设备的用户面路径发生了变化；所述多接入边缘计算MEC网元获取源应用实例的信息和目标应用实例的信息，包括：所述MEC网元基于所述第三消息，确定所述源应用实例的信息和所述目标应用实例的信息，其中，所述源应用实例位于源数据网络的接入标识所对应的位置，所述目标应用实例位于目标数据网络的接入标识所对应的位置。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：所述MEC网元基于所述第二消息，向所述核心网控制面网元发送第四消息，所述第四消息是对所述第三消息的肯定应答或否定应答。
示例性地，在源应用实例和目标应用实例之间完成用户上下文迁移之后，MEC网元可以向核心网控制面网元发送上述第四消息，若第四消息为肯定应答，表示MEC网元接受应用的用户上下文迁移，且该应用的用户上下文迁移状态为迁移完成，这样，核心网控制面网元就可以激活新的用户面路径，使得终端设备通过新的用户面路径对应的目标应用实例访问应用。若第四消息为否定应答，表示MEC网元拒绝该应用的用户上下文迁移，或者，该应用的用户上下文迁移状态为迁移失败，在这种情况下，终端设备依旧通过旧的用户面路径对应的源应用实例访问应用。
结合第一方面，在第一方面的某些实现方式中，所述第三消息包括下列信息中的至少一个：所述终端设备的标识、所述应用的标识、所述源数据网络的接入标识、所述目标数据网络的接入标识。
具体而言，MEC网元可以根据上述终端设备所访问的应用的标识和源数据网络的接入标识，确定该应用在源数据网络对应的源应用实例的信息；MEC网元可以根据上述终端设备所访问的应用的标识和目标数据网络的接入标识，确定该应用在目标数据网络对应的目标应用实例的信息。
结合第一方面，在第一方面的某些实现方式中，在所述MEC网元接收来自核心网控制面网元的第三消息之前，所述方法还包括：所述MEC网元向所述核心网控制面网元发送第五消息，所述第五消息用于订阅所述终端设备的用户面路径变化事件。
上述MEC网元向核心网控制面网元发送第五消息，是为了便于该核心网控制面网元在该终端设备的用户面路径发生变化时向该MEC网元发送该第三消息。应理解，用户面路径发生变化指终端设备发生了移动，终端设备的用户面路径需要改变，但是此时新的用户面路径还未激活，终端设备还是通过源应用实例访问应用的。
结合第一方面，在第一方面的某些实现方式中，所述MEC网元为MEC编排器或MEC平台管理器。或者，本申请实施例中的MEC网元能够实现MEC编排器、或者MEC平台管理器中至少一项网元的功能。
结合第一方面，在第一方面的某些实现方式中，所述MEC网元包括MEC编排器和MEC平台管理器，所述MEC网元向第一MEC平台发送第一消息，包括：所述MEC编排器通过所述MEC平台管理器向所述第一MEC平台发送所述第一消息；所述MEC网元接收来自所述第一MEC平台的第二消息，包括：所述MEC编排器通过所述MEC平台管 理器接收来自所述第一MEC平台的所述第二消息。
上述MEC编排器可以是基于核心网控制面网元发送的第三消息，确定源应用实例的信息和目标应用实例的信息。上述“MEC编排器通过MEC平台管理器向该第一MEC平台发送该第一消息”是指：MEC编排器先将第一消息发送给MEC平台管理器，MEC平台管理器再将该第一消息转发给第一MEC平台。同理，上述“MEC编排器通过该MEC平台管理器接收来自该第一MEC平台的该第二消息”是指：第一MEC平台先将第二消息发送给MEC平台管理器，MEC平台管理器再将该第二消息转发给MEC编排器。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：所述MEC编排器向所述MEC平台管理器发送第六消息，所述第六消息用于订阅所述应用的用户上下文迁移状态；所述MEC平台管理器接收所述第六消息，并向所述MEC编排器发送第一应答消息；所述MEC编排器接收所述第一应答消息。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：所述MEC平台管理器向所述第一MEC平台发送第七消息，所述第七消息用于订阅所述应用的用户上下文迁移状态；所述MEC平台管理器接收来自所述第一MEC平台的第二应答消息。
结合第一方面，在第一方面的某些实现方式中，所述MEC编排器通过所述MEC平台管理器接收来自所述第一MEC平台的所述第二消息，包括：所述MEC平台管理器接收来自所述第一MEC平台的所述第二消息；所述MEC平台管理器向所述MEC平台发送第三应答消息；所述MEC平台管理器向所述MEC编排器发送所述第二消息；所述MEC编排器接收所述第二消息，并向所述MEC平台管理器发送第四应答消息；所述MEC平台管理器接收所述第四应答消息。
第二方面，提供了另一种通信方法，包括：第一多接入边缘计算MEC平台接收来自核心网控制面网元的第三消息，所述第三消息用于通知终端设备的用户面路径发生了变化；所述第一MEC平台基于所述第三消息，获取所述终端设备所访问的应用的源应用实例的信息和所述应用的目标应用实例的信息；所述第一MEC平台将所述应用的用户上下文从所述源应用实例迁移至所述目标应用实例，其中，所述源应用实例部署在所述第一MEC平台，所述目标应用实例部署在第二MEC平台。
结合第二方面，在第二方面的某些实现方式中，所述第一MEC平台基于所述第三消息，获取终端设备所访问的应用的源应用实例的信息和所述应用的目标应用实例的信息，包括：所述第一MEC平台基于所述第三消息，向MEC编排器发送请求消息，所述请求消息用于请求所述目标应用实例的信息；所述第一MEC平台接收所述MEC编排器发送的所述目标应用实例的信息。
结合第二方面，在第二方面的某些实现方式中，所述方法还包括：所述第一MEC平台向所述核心网控制面网元发送第四消息，所述第四消息是对所述第三消息的肯定应答或否定应答。
结合第二方面，在第二方面的某些实现方式中，所述第三消息包括下列信息中的至少一个：所述终端设备的标识、所述应用的标识、所述源数据网络的接入标识、所述目标数据网络的接入标识。
结合第二方面，在第二方面的某些实现方式中，在所述第一多接入边缘计算MEC平台接收来自核心网控制面网元的第三消息之前，所述方法还包括：所述第一MEC平台向 所述核心网控制面网元发送第五消息，所述第五消息用于订阅所述终端设备的用户面路径变化事件。
第三方面，提供了一种通信装置，用于执行上述各方面中任一种可能的实现方式中的方法。具体地，该装置包括用于执行上述各方面中任一种可能的实现方式中的方法的单元。
第四方面，提供了一种通信装置，包括处理器，该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述各方面中任一种可能实现方式中的方法。可选地，该装置还可以包括存储器。可选地，该装置还可以包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该通信装置为MEC网元。当该通信装置为MEC网元时，通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该通信装置为配置于MEC网元中的芯片。当该通信装置为配置于MEC网元中的芯片时，通信接口可以是输入/输出接口。
第五方面，提供了一种处理器，包括：输入电路、输出电路和处理电路。处理电路用于通过输入电路接收信号，并通过输出电路发射信号，使得处理器执行上述各方面中任一种可能实现方式中的方法。
在具体实现过程中，上述处理器可以为芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于接收器接收并输入的，输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电路的具体实现方式不做限定。
第六方面，提供了一种处理装置，包括处理器和存储器。该处理器用于读取存储器中存储的指令，并可通过接收器接收信号，通过发射器发射信号，以执行上述各方面中任一种可能实现方式中的方法。
可选地，处理器为一个或多个，存储器为一个或多个。
可选地，存储器可以与处理器集成在一起，或者存储器与处理器分离设置。
在具体实现过程中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
应理解，相关的数据交互过程例如发送指示信息可以为从处理器输出指示信息的过程，接收能力信息可以为处理器接收输入能力信息的过程。具体地，处理输出的数据可以输出给发射器，处理器接收的输入数据可以来自接收器。其中，发射器和接收器可以统称为收发器。
上述第六方面中的处理装置可以是一个芯片，该处理器可以通过硬件来实现也可以通过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，该存储器可以集成在处理器中，可以位于该处理器之外，独立存在。
第七方面，提供了一种计算机程序产品，计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当计算机程序被运行时，使得计算机执行上述各方面中任一种可能 实现方式中的方法。
第八方面，提供了一种计算机可读存储介质，计算机可读存储介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述各方面中任一种可能实现方式中的方法。
第九方面，提供了一种通信系统，包括前述的MEC网元和MEC平台。
附图说明
图1是本申请实施例提供的系统架构的示意图。
图2是本申请实施例提供的另一系统架构的示意图。
图3是本申请实施例提供的通信方法的示意性流程图。
图4是本申请实施例提供的另一通信方法的示意性流程图。
图5是本申请实施例提供的另一通信方法的示意性流程图。
图6是本申请实施例提供的另一通信方法的示意性流程图。
图7是本申请实施例提供的另一通信方法的示意性流程图。
图8是本申请实施例提供的通信装置的示意性框图。
图9是本申请实施例提供的另一通信装置的示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、第五代(5th generation，5G)系统或新无线(new radio，NR)等。
本申请实施例中的终端设备也可以称为：用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。
终端设备可以是一种向用户提供语音/数据连通性的设备，例如，具有无线连接功能的手持式设备、车载设备等。目前，一些终端的举例为：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例 对此并不限定。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
此外，在本申请实施例中，终端设备还可以是物联网(internet of things，IoT)系统中的终端设备，IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。
本申请实施例中的网络设备可以是用于与终端设备通信的设备，该网络设备可以是传输接收点(transmission reception point，TRP)，还可以是LTE系统中的演进型基站(evolved NodeB，eNB或eNodeB)，还可以是家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(base band unit，BBU)，还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器，或者该接入网设备可以为中继站、接入点、车载设备、可穿戴设备以及5G网络中的接入网设备或者未来演进的陆上公用移动通信网(public land mobile network，PLMN)网络中的接入网设备等，可以是WLAN中的接入点(access point，AP)，可以是新型无线系统(new radio，NR)系统中的gNB，本申请实施例并不限定。在一种网络结构中，接入网设备可以包括集中单元(centralized unit，CU)节点、或分布单元(distributed unit，DU)节点、或包括CU节点和DU节点的RAN设备、或者控制面CU节点(CU-CP节点)和用户面CU节点(CU-UP节点)以及DU节点的RAN设备。
在本申请实施例中，终端设备或网络设备包括硬件层、运行在硬件层之上的操作系统层，以及运行在操作系统层上的应用层。该硬件层包括中央处理器(central processing unit，CPU)、内存管理单元(memory management unit，MMU)和内存(也称为主存)等硬件。该操作系统可以是任意一种或多种通过进程(process)实现业务处理的计算机操作系统，例如，Linux操作系统、Unix操作系统、Android操作系统、iOS操作系统或windows操作系统等。该应用层包含浏览器、通讯录、文字处理软件、即时通信软件等应用。并且，本申请实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可，例如，本申请实施例提供的方法的执行主体可以是终端设备或网络设备，或者，是终端设备或网络设备中能够调用程序并执行程序的功能模块。
另外，本申请的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。本申请中使用的术语“制品”涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。例如，计算机可读介质可以包括，但不限于：磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，压缩盘(compact disc，CD)、数字通用盘(digital versatile disc，DVD)等)，智能卡和闪存器件(例如，可擦写可编程只读存储器(erasable programmable  read-only memory，EPROM)、卡、棒或钥匙驱动器等)。另外，本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可包括但不限于，无线信道和能够存储、包含和/或承载指令和/或数据的各种其它介质。
为便于理解本申请实施例，首先介绍本申请所涉及的相关术语。
1、多接入边缘计算(multi-access edge computing，MEC)
MEC运行于网络边缘，可以提供大数据服务、物联网服务和数据服务，并且开放应用软件编程接口(application programming interface，API)给第三方用来快速部署新业务。MEC服务器通常具有较高的计算能力，特别适合分析处理大量数据。MEC服务器主要由三大部分组成：最底层的基础设施，中间的MEC平台和上层的应用。
2、应用
应用实际是应用实例，应用实例是同一个应用的拷贝。应用实例部署在需要的边缘节点。终端设备上的应用在某个特定时刻由某个边缘节点的某个应用实例提供服务。通常来说，应用实例离终端设备的位置越近，应用和终端设备之间的报文传输延迟就越小，服务质量就越高。当终端设备在位置1时，位于与位置1处的边缘节点1的应用实例1是该终端设备的最优的应用实例。当终端设备移动到位置2时，位于位置2处的边缘节点2的应用实例2是该终端设备的最优的应用实例。
上述边缘节点的物理实体为MEC平台(MEC Platform)，为便于描述，后面以MEC平台为例进行说明。
下面结合图1对适用于本申请实施例的系统架构进行详细说明。图1所示的系统架构100包括：终端设备110、MEC网元120、第一MEC平台130以及第二MEC平台140，其中，源应用实例部署在第一MEC平台130上，目标应用实例部署在第二MEC平台140上。
终端设备110位于第一MEC平台130的位置附近时，可以通过第一MEC平台130访问源应用实例，当终端设备发生了移动，位于第二MEC平台140的位置附近时，可以通过第二MEC平台140访问目标应用实例。这里的源应用实例和目标应用实例是同一个应用的不同拷贝。MEC网元120用于管理和部署MEC平台。
应理解，终端设备110可以通过核心网网元访问上述应用实例，核心网网元在图1中未示出。在一种可能的实现方式中，核心网网元可以由集中的控制面网络功能网元和分布式的用户面网络功能网元组成。当终端设备在不同的区域间移动时，控制面网络功能网元可以选择合适的用户面网络功能网元，因此，会产生用户面网络功能网元的切换，与用户面网络功能网元所对应的应用实例也需要进行切换。即从上述源应用实例切换至目标应用实例。
欧洲电信标准化组织(European telecommunication standards institute，ETSI)在其规范ETSI GS MEC 003中定义了MEC的参考架构，下面结合图2对该参考架构进行详细介绍。
图2是本申请实施例的另一个系统架构200。如图2所示，该系统架构200可以包括MEC系统水平和MEC主机水平两部分，MEC系统水平负责对MEC系统进行全局掌控，具体可以包括下列网元：
1、MEC主机(MEC Host)：包括MEC平台(MEC Platform)、虚拟化基础设施 (virtualization infrastructure)和MEC应用(MEC app)。
其中，虚拟基础设施为MEC应用提供虚拟化的计算、存储和网络资源，并且可以为ME应用提供持续的存储和时间相关的信息，它包含一个数据转发平面来为从ME平台接收到的数据执行转发规则，并在各种应用、服务和网络之间进行流量的路由。
MEC平台是MEC参考架构的核心，它主要从MEC平台管理器、MEC应用或MEC服务处接收流量转发规则，并且基于转发规则向转发平面下发指令。MEC平台包含了服务注册、发现功能、以及公共服务等，可以提供数据流分发(traffic offload function，TOF)、无线网络信息服务(radio network information service，RNIS)、通信服务(communication service)和服务注册(service registry)等模块，以便通过这些模块为上层的应用实例提供服务。MEC平台还支持本地域名系统(domain name system，DNS)代理服务器的配置，可以将数据流量重定向到对应的应用和服务。MEC平台还可以通过Mp3参考点与其他的MEC平台进行通信，在分布式MEC系统的协作机制中，Mp3参考点可以作为不同MEC平台互联的基础。
MEC应用是运行在MEC虚拟化基础设施上的虚拟机实例，这些应用通过Mp1参考点与MEC平台相互通信。Mp1参考点还可提供标识应用可用性、发生MEC切换时为用户准备或重定位应用状态等额外功能。
2、MEC编排器(MEC orchestrator)：MEC提供的核心功能，MEC编排器可以宏观掌控MEC网络的资源和容量，包括所有已经部署好的MEC主机和服务、每个主机中的可用资源、已经被实例化的MEC应用以及网络的拓扑等。在为用户选择接入的目标MEC主机时，MEC编排器可以衡量用户需求和每个主机的可用资源，为其选择最为合适的MEC主机，如果用户需要进行MEC主机的切换，则由MEC编排器来触发切换程序。
MEC编排器与操作支持系统之间通过Mm1参考点来触发MEC应用的实例化和终止。MEC编排器与虚拟化基础设施管理器之间通过Mm4参考点来管理虚拟化资源和应用的虚拟机映像，同时维持可用资源的状态信息。
3、MEC平台管理器(MEC platform manager)：用于管理MEC平台、管理MEC应用的生命周期、管理MEC应用规则和需求。MEC应用的生命周期管理包括MEC应用程序的创建和终止，并且为MEC编排器提供应用相关事件的指示消息。MEC应用规则和需求的管理包括认证、流量规则、DNS配置和冲突协调等。
MEC平台和MEC平台管理器之间使用Mm5参考点，该参考点可以实现平台和流量过滤规则的配置，并且负责管理应用的重定位和支持应用的生命周期程序。Mm2是操作支持系统和MEC平台管理器之间的参考点，负责MEC平台的配置和性能管理。Mm3是MEC编排器和MEC平台管理器之间的参考点，负责为MEC应用的生命周期管理和MEC应用相关的策略提供支持，同时为MEC的可用服务提供时间相关的信息。
4、虚拟化基础设施管理器(virtualization infrastructure manager)：用于管理MEC应用所需的虚拟化资源。管理任务包括虚拟计算、存储和网络资源的分配和释放，软件映像也可以存储在虚拟化基础设施管理器上以供MEC应用的快速实例化。同时，虚拟化基础设施管理器还负责收集虚拟资源的信息，并通过Mm4参考点和Mm6参考点分别上报给MEC编排器和MEC平台管理器等上层管理实体。
5、操作支持系统(operations support system)：从MEC系统的角度来看，操作支持 系统是支持系统运行的最高水平的管理实体。操作支持系统从面向用户服务(customer-facing service，CFS)门户和终端设备(例如UE)接收实例化或终止MEC应用的请求，检查应用数据分组和请求的完整性和授权信息。经过操作支持系统认证授权的请求数据分组会通过Mm1参考点被转发到MEC编排器进行进一步处理。
6、面向客户服务门户(CFS portal)：相当于第三方接入点，开发商使用该接口将自己开发的各种应用接入运营商的MEC系统中，企业或者个人用户也可以通过该接口选择其感兴趣的应用，并指定其使用的时间和地点。CFS门户可以通过Mx1参考点与操作支持系统实现通信。
7、用户应用生命周期代理(user app LCM proxy)：供MEC用户使用来请求应用相关的实例化和终止等服务的实体。该实体可以实现外部云和MEC系统之间的应用重定位，负责对所有来自外部云的请求进行认证，然后分别通过Mm8和Mm9参考点发送给操作支持系统和MEC编排器做进一步处理。值得注意的是，用户应用生命周期代理只能通过移动网络接入，Mx2参考点提供了终端设备与用户应用生命周期代理相互通信的基础。
应理解，在上述系统架构100中，MEC网元120具体可以实现图2中的MEC编排器、或者MEC平台管理器中的至少一项网元的功能，本申请实施例对此不作限定。
还应理解，该系统架构200包括3种不同类型的参考点。其中，Mp代表和MEC平台应用相关的参考点，Mm代表和管理相关的参考点，Mx代表和外部实体相关的参考点。
上述应用于本申请实施例的系统架构200仅是举例说明的从参考点架构的角度描述的网络架构，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
需要说明的是，图2中的各个网元之间的接口名称只是一个示例，具体实现中接口的名称可能为其他的名称，本申请实施例对此不作具体限定。
需要说明的是，图2中包括的各个网元(比如MEC编排器、MEC平台管理器等)的名称也仅是一个示例，对网元本身的功能不构成限定。在未来其它的网络中，上述各个网元也可以是其他的名称，本申请实施例对此不作具体限定。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能采用其他名称，等等，在此进行统一说明，以下不再赘述。此外，应理解，上述各个网元之间的所传输的消息(或信令)的名称也仅仅是一个示例，对消息本身的功能不构成任何限定。
图3示出了本申请实施例的通信方法300的示意性流程图。该方法300可以应用于图1所示的系统架构100，也可以应用于图2所示的系统架构200，本申请实施例不限于此。
S310，MEC网元获取终端设备所访问的应用的源应用实例的信息和该应用的目标应用实例的信息。
S320，MEC网元向第一MEC平台发送第一消息，该第一消息用于请求将该应用的用户上下文从源应用实例迁移至目标应用实例，其中，该源应用实例部署在该第一MEC平台，该目标应用实例部署在第二MEC平台；对应地，第一MEC平台接收该第一消息。
S330，第一MEC平台向MEC网元发送第二消息，该第二消息用于指示该应用的用户上下文迁移状态；对应地，MEC网元接收来自第一MEC平台的第二消息。
上述用户上下文迁移状态可以包括迁移开始、迁移完成、或者迁移失败等状态。由于终端设备的移动，数据网络会发生切换，与数据网络对应的MEC平台也会发生切换，即 从第一MEC平台切换至第二MEC平台。在本申请实施例中，在移动之前，终端设备通过第一MEC平台的源应用实例访问应用，在移动之后，且在用户上下文迁移状态表示迁移完成的情况下，该终端设备可以通过第二MEC平台的目标应用实例访问该应用。
本申请实施例的通信方法，通过MEC网元获取源应用实例的信息和目标应用实例的信息，向第一MEC平台发送第一消息请求进行应用的用户上下文迁移，能够在MEC场景中实现基于应用实例的应用的用户上下文迁移，有利于保障业务的连续性，从而保障用户体验。
可选地，本申请实施例中的MEC网元为MEC编排器、或者MEC平台管理器。或者，本申请实施例中的MEC网元能够实现MEC编排器、或者MEC平台管理器中至少一项网元的功能。
在一种可能的实现方式中，在MEC网元获取源应用实例的信息和目标应用实例的信息之前，该方法还包括：该MEC网元接收来自核心网控制面网元的第三消息，该第三消息用于通知该终端设备的用户面路径发生了变化；该MEC网元获取源应用实例的信息和目标应用实例的信息，包括：该MEC网元基于该第三消息，确定该源应用实例的信息和该目标应用实例的信息，其中，该源应用实例位于源数据网络的接入标识所对应的位置，该目标应用实例位于目标数据网络的接入标识所对应的位置。
可选地，上述第三消息包括下列信息中的至少一个：该终端设备的标识、该应用的标识、该源数据网络的接入标识、该目标数据网络的接入标识。具体而言，MEC网元可以根据上述终端设备所访问的应用的标识和源数据网络的接入标识，确定该应用在源数据网络对应的源应用实例的信息；MEC网元可以根据上述终端设备所访问的应用的标识和目标数据网络的接入标识，确定该应用在目标数据网络对应的目标应用实例的信息。
作为一个可选的实施例，该方法还包括：MEC网元基于该第二消息，向核心网控制面网元发送第四消息，该第四消息是对所述第三消息的肯定应答或否定应答。
示例性地，在源应用实例和目标应用实例之间完成用户上下文迁移之后，MEC网元可以向核心网控制面网元发送上述第四消息，若第四消息为肯定应答，表示MEC网元接受应用的用户上下文迁移，且该应用的用户上下文迁移状态为迁移完成，这样，核心网控制面网元就可以激活新的用户面路径，使得终端设备通过新的用户面路径对应的目标应用实例访问应用。若第四消息为否定应答，表示MEC网元拒绝该应用的用户上下文迁移，或者，该应用的用户上下文迁移状态为迁移失败，在这种情况下，终端设备依旧通过旧的用户面路径对应的源应用实例访问应用。
作为一个可选的实施例，在该MEC网元接收来自核心网控制面网元的第三消息之前，该方法还包括：该MEC网元向该核心网控制面网元发送第五消息，该第五消息用于订阅该终端设备的用户面路径变化事件，以便该核心网控制面网元在该终端设备的用户面路径发生变化时向该MEC网元发送该第三消息。
应理解，用户面路径发生变化指终端设备发生了移动，终端设备的用户面路径需要改变，但是此时新的用户面路径还未激活，终端设备还是通过源应用实例访问应用的。
在一种可能的实现方式中，上述MEC网元包括MEC编排器和MEC平台管理器，上述MEC网元所执行的动作具体可以包括：MEC编排器获取终端设备所访问的应用的源应用实例的信息和该应用的目标应用实例的信息；MEC编排器通过MEC平台管理器向第一 MEC平台发送该第一消息；MEC编排器通过MEC平台管理器接收来自该第一MEC平台的该第二消息。
上述MEC编排器可以是基于核心网控制面网元发送的第三消息，确定源应用实例的信息和目标应用实例的信息。上述“MEC编排器通过MEC平台管理器向该第一MEC平台发送该第一消息”是指：MEC编排器先将第一消息发送给MEC平台管理器，MEC平台管理器再将该第一消息转发给第一MEC平台。同理，上述“MEC编排器通过该MEC平台管理器接收来自该第一MEC平台的该第二消息”是指：第一MEC平台先将第二消息发送给MEC平台管理器，MEC平台管理器再将该第二消息转发给MEC编排器。
可选地，上述方法还包括：该MEC编排器向MEC平台管理器发送用于订阅该应用的用户上下文迁移状态的消息；对应地，该MEC平台管理器接收该消息。该MEC平台管理器向该MEC编排器发送第一应答消息，表示接收到该用于订阅该应用的用户上下文迁移状态的消息；对应地，该MEC编排器接收该第一应答消息。
可选地，上述方法还包括：MEC平台管理器向第一MEC平台发送用于订阅该应用的用户上下文迁移状态的消息；对应地，该第一MEC平台接收该消息。该第一MEC平台向该MEC平台管理器发送第二应答消息，表示接收到该用于订阅该应用的用户上下文迁移状态的消息；对应地，该MEC平台管理器接收该第二应答消息。
可选地，上述MEC编排器通过该MEC平台管理器接收来自该第一MEC平台的该第二消息，包括：第一MEC平台向该MEC平台管理器发送用于指示用户上下文迁移状态的消息，对应地，该MEC平台管理器接收该消息。该MEC平台管理器向第一MEC平台发送第三应答消息，表示接收到用于指示用户上下文迁移状态的消息，对应地，第一MEC平台接收该第三应答消息。该MEC平台管理器向该MEC编排器发送用于指示用户上下文迁移状态的消息，对应地，该MEC编排器接收该消息。该MEC编排器向MEC平台管理器发送第四应答消息，表示接收到用于指示用户上下文迁移状态的消息，对应地，MEC平台管理器接收该第四应答消息。
图4示出了本申请实施例的通信方法400的示意性流程图。该方法400可以应用于图1所示的系统架构100，也可以应用于图2所示的系统架构200，本申请实施例不限于此。
S410，核心网控制面网元向第一多接入边缘计算MEC平台发送第三消息，该第三消息用于通知终端设备的用户面路径发生了变化；对应地，第一MEC平台接收该第三消息。
S420，该第一MEC平台基于该第三消息，获取该终端设备所访问的应用的源应用实例的信息和该应用的目标应用实例的信息；
S430，该第一MEC平台将该应用的用户上下文从该源应用实例迁移至该目标应用实例，其中，该源应用实例部署在所述第一MEC平台，该目标应用实例部署在第二MEC平台。
本申请实施例的通信方法，通过MEC平台获取源应用实例的信息和目标应用实例的信息，再进行应用的用户上下文迁移，能够在MEC场景中实现基于应用实例的应用的用户上下文迁移，有利于保障业务的连续性，从而保障用户体验。
作为一个可选的实施例，该第一MEC平台基于该第三消息，获取终端设备所访问的应用的源应用实例的信息和该应用的目标应用实例的信息，包括：该第一MEC平台基于该第三消息，向MEC编排器发送请求消息，该请求消息用于请求该目标应用实例的信息； 该第一MEC平台接收该MEC编排器发送的该目标应用实例的信息。
作为一个可选的实施例，该方法还包括：该第一MEC平台向该核心网控制面网元发送第四消息，该第四消息是对所述第三消息的肯定应答或否定应答。
作为一个可选的实施例，该第三消息包括下列信息中的至少一个：该终端设备的标识、该应用的标识、该源数据网络的接入标识、该目标数据网络的接入标识。
作为一个可选的实施例，在该第一多接入边缘计算MEC平台接收来自核心网控制面网元的第三消息之前，该方法还包括：该第一MEC平台向该核心网控制面网元发送第五消息，该第五消息用于订阅该终端设备的用户面路径变化事件。
关于方法400的相关细节可以参考上述方法300，此处不再赘述。
图5示出了本申请实施例的另一通信方法500的示意性流程图。该方法500可以应用于图1所示的系统架构100，也可以应用于图2所示的系统架构200，本申请实施例不限于此。
S501，终端设备通过源应用实例访问应用。源应用实例部署在第一MEC平台上。
S502，MEC编排器向核心网网元发送订阅消息，用于订阅用户面路径变化事件。对应地，核心网网元接收该订阅消息。该订阅消息可以为前述方法300中的第五消息。
可选地，上述核心网网元可以是核心网控制面网元，例如，网络开放功能(network exposure function，NEF)、或者策略控制功能(policy control function，PCF)。
S503，终端设备发生移动，触发用户面路径切换。
S504，由于MEC编排器订阅了用户面路径变化事件，核心网网元会向MEC编排器发送通知消息，通知该MEC编排器终端设备的用户面路径发生变化。对应地，MEC编排器接收该通知消息。该通知消息可以为前述方法300中的第三消息。
上述通知消息也可以称作用户面路径变化事件通知或其他名称。
可选地，上述通知消息可以包括终端设备的标识、终端设备所访问的应用的标识、源数据网络的接入标识、以及目标数据网络的接入标识。示例性地，终端设备的标识可以是终端设备的互联网协议(Internet protocol，IP)地址、或者终端设备的通用公共签约标识(generic public subscription identifier，GPSI)等，本申请实施例对此不作限定。
S505，MEC编排器根据上述通知消息，获取终端设备所访问的应用的源应用实例的信息和目标应用实例的信息。
具体而言，数据网络标识了应用实例的部署位置，MEC编排器可以根据上述终端设备所访问的应用的标识和源数据网络的接入标识，确定该应用在源数据网络对应的源应用实例的信息；MEC编排器可以根据上述终端设备所访问的应用的标识和目标数据网络的接入标识，确定该应用在目标数据网络对应的目标应用实例的信息。
可选地，上述源应用实例的信息包括源应用实例的标识、源应用实例的IP地址和源应用实例的端口号；上述目标应用实例的信息包括目标应用实例的标识、目标应用实例的IP地址和目标应用实例的端口号。
S506，MEC编排器通过MEC管理器向第一MEC平台发送迁移请求消息，用于请求迁移应用的用户上下文信息。对应地，第一MEC平台通过MEC管理器接收该迁移请求消息。
可选地，该迁移请求消息包括终端设备的标识、源应用实例的信息以及目标应用实例 的信息。
S507，第一MEC平台向第二MEC平台发送迁移请求消息，用于请求迁移应用的用户上下文信息。对应地，第二MEC平台接收该迁移请求消息。该迁移请求消息可以为前述方法300中的第一消息。
可选地，该迁移请求消息包括终端设备的标识和目标应用实例的信息。
可选地，上述第一MEC平台可以直接向第二MEC平台发送迁移请求消息，也可以通过专门的应用移动性服务实体向第二MEC平台发送迁移请求消息，本申请实施例对此不作限定。
可选地，S508，第二MEC平台向第一MEC平台发送应答消息，表示接收到上述迁移请求消息，并接受该应用的用户上下文迁移。对应地，第一MEC平台接收该应答消息。
S509，第一MEC平台和第二MEC平台之间进行应用的用户上下文迁移。
S510，第二MEC平台向第一MEC平台发送迁移状态通知消息，用于通知用户上下文的迁移状态。用户上下文的迁移状态可以包括迁移开始、迁移完成、或者迁移失败等。对应地，第一MEC平台接收该迁移状态通知消息。该迁移状态通知消息可以为前述方法300中的第二消息。
可选地，上述第二MEC平台可以直接向第一MEC平台发送迁移状态通知消息，也可以通过专门的应用移动性服务实体向第一MEC平台发送迁移状态通知消息，本申请实施例对此不作限定。
可选地，S511，第一MEC平台向第二MEC平台发送应答消息，表示接收到上述迁移状态通知消息。对应地，第二MEC平台接收该应答消息。
S512，第一MEC平台通过MEC平台管理器向MEC编排器发送上述迁移状态通知消息，在本申请实施例中，迁移状态通知消息表示用户上下文迁移完成。对应地，MEC编排器通过MEC平台管理器接收该迁移状态通知消息。
该迁移状态通知消息也可以称为用户上下文迁移应答消息或其他名称。
S513，MEC编排器向核心网网元发送应答消息，该应答消息用于应答S504中的通知消息，在本申请实施例中，应答消息为肯定应答，表示上下文迁移完成。对应地，核心网网元接收该应答消息。该应答消息可以为前述方法300中的第四消息。
该应答消息也可以称为用户面路径变化事件应答消息或其他名称。
S514，核心网网元激活新的用户面路径。
S515，终端设备通过第二MEC平台上的目标应用实例访问应用，即通过新的用户面路径访问应用。
本申请实施例的通信方法，能够在MEC场景中实现基于应用实例的应用的用户上下文迁移，有利于保障业务的连续性，从而保障用户体验。
在上述方法500中，MEC编排器、MEC平台管理器、第一MEC平台之间采用同步方式进行消息交互，即第一MEC平台检测到用户上下文迁移完成之后才通过MEC平台管理器向MEC编排器发送用户上下文迁移应答消息(即上述第七应答消息)。下面的方法600示例出了另一种消息交互的方式。
应理解，方法600仅仅示出了MEC编排器、MEC平台管理器、第一MEC平台之间的消息交互过程，对于其他网元(如终端设备、核心网网元)的步骤与方法500相同，不 再赘述。
图6示出了本申请实施例的另一通信方法600的示意性流程图。该方法600可以应用于图1所示的系统架构100，也可以应用于图2所示的系统架构200，本申请实施例不限于此。
S601，MEC编排器向MEC平台管理器发送订阅消息，用于订阅用户上下文迁移状态。对应地，MEC平台管理器接收该订阅消息。该订阅消息可以为前述方法300中的第六消息。
可选地，该订阅请求消息包括终端设备的标识、源应用实例的标识、以及目标应用实例的标识。
S602，MEC平台管理器向MEC编排器发送应答消息，表示收到该订阅消息。对应地，MEC编排器接收该应答消息。该应答消息可以为前述方法300中的第一应答消息。
S603，MEC平台管理器向第一MEC平台发送订阅消息，用于订阅用户上下文迁移状态。对应地，第一MEC平台接收该订阅消息。该订阅消息可以为前述方法300中的第七消息。
S604，第一MEC平台向MEC平台管理器发送应答消息，表示收到该订阅消息。对应地，MEC平台管理器接收该应答消息。该应答消息可以为前述方法300中的第二应答消息。
S605，第一MEC平台向MEC平台管理器发送迁移状态通知消息，该迁移状态通知消息用于通知用户上下文的迁移状态。用户上下文的迁移状态可以包括迁移开始、迁移完成、或者迁移失败等。对应地，MEC平台管理器接收该迁移状态通知消息。
S606，MEC平台管理器向第一MEC平台发送应答消息，表示收到该迁移状态通知消息。对应地，第一MEC平台接收该应答消息。该应答消息可以为前述方法300中的第三应答消息。
S607，MEC平台管理器向MEC编排器发送上述迁移状态通知消息。对应地，MEC编排器接收该迁移状态通知消息。
S608，MEC编排器向MEC平台管理器发送应答消息，表示收到该迁移状态通知消息。对应地，MEC平台管理器接收该应答消息。该应答消息可以为前述方法300中的第四应答消息。
应理解，上述S605～S608可以替换方法500中的S512。此外，S601～S604可以在S510之前的任意时间段执行，本申请实施例对此不作限定。
图7示出了本申请实施例的另一通信方法700的示意性流程图。该方法700可以应用于图1所示的系统架构100，也可以应用于图2所示的系统架构200，本申请实施例不限于此。
S701，终端设备通过源应用实例访问应用。源应用实例部署在第一MEC平台上。
S702，源应用实例向第一MEC平台发送订阅消息，用于订阅终端设备的移动性通知事件。对应地，第一MEC平台接收该订阅消息。该订阅消息可以携带上述终端设备的标识。
S703，第一MEC平台向核心网网元发送订阅消息，用于订阅用户面路径变化事件。对应地，核心网网元接收该订阅消息。该订阅消息可以为前述方法300中的第五消息。
可选地，上述核心网网元可以是核心网控制面网元，例如，网络开放功能(network exposure function，NEF)、或者策略控制功能(policy control function，PCF)。
S704，终端设备发生移动，触发用户面路径切换。
S705，由于第一MEC平台订阅了用户面路径变化事件，核心网网元会向第一MEC平台发送通知消息，通知该第一MEC平台终端设备的用户面路径发生变化。对应地，第一MEC平台接收该通知消息。该通知消息可以为前述方法300中的第三消息。
上述通知消息也可以称作用户面路径变化事件通知或其他名称。
可选地，上述通知消息可以包括终端设备的标识、终端设备所访问的应用的标识、源数据网络的接入标识、以及目标数据网络的接入标识。示例性地，终端设备的标识可以是终端设备的互联网协议(Internet protocol，IP)地址、或者终端设备的通用公共签约标识(generic public subscription identifier，GPSI)等，本申请实施例对此不作限定。
S706，第一MEC平台通过MEC平台管理器向MEC编排器发送迁移请求消息，该迁移请求消息可以包括下列信息中的至少一个：终端设备的标识、应用的标识、目标数据网络的接入标识。对应地，MEC编排器接收该迁移请求消息。
S707，MEC编排器根据上述迁移请求消息，确定终端设备所访问的应用的目标应用实例的信息。
具体而言，数据网络标识了应用实例的部署位置，MEC编排器可以根据上述终端设备所访问的应用的标识和目标数据网络的接入标识，确定该应用在目标数据网络对应的目标应用实例的信息。
可选地，上述目标应用实例的信息包括目标应用实例的标识、目标应用实例的IP地址和目标应用实例的端口号。
S708，MEC编排器通过MEC管理器向第一MEC平台发送迁移应答消息。对应地，第一MEC平台通过MEC管理器接收该迁移应答消息。
可选地，该迁移应答消息包括终端设备的标识以及目标应用实例的信息。
S709，第一MEC平台向第二MEC平台发送迁移请求消息，用于请求迁移应用的用户上下文信息。对应地，第二MEC平台接收该迁移请求消息。该迁移请求消息可以为前述方法300中的第一消息。
可选地，该迁移请求消息包括终端设备的标识和目标应用实例的信息。
可选地，上述第一MEC平台可以直接向第二MEC平台发送第二迁移请求消息，也可以通过专门的应用移动性服务实体向第二MEC平台发送第二迁移请求消息，本申请实施例对此不作限定。
可选地，S710，第二MEC平台向第一MEC平台发送应答消息，表示接收到上述迁移请求消息，并接受该应用的用户上下文迁移。对应地，第一MEC平台接收该应答消息。
S711，第一MEC平台和第二MEC平台之间进行应用的用户上下文迁移。
S712，第二MEC平台向第一MEC平台发送迁移状态通知消息，用于通知用户上下文的迁移状态。用户上下文的迁移状态可以包括迁移开始、迁移完成、或者迁移失败等。对应地，第一MEC平台接收该迁移状态通知消息。该迁移状态通知消息可以为前述方法300中的第二消息。
可选地，上述第二MEC平台可以直接向第一MEC平台发送迁移状态通知消息，也 可以通过专门的应用移动性服务实体向第一MEC平台发送迁移状态通知消息，本申请实施例对此不作限定。
可选地，S713，第一MEC平台向第二MEC平台发送应答消息，表示接收到上述迁移状态通知消息。对应地，第二MEC平台接收该应答消息。
S714，第一MEC平台向核心网网元发送应答消息，该应答消息用于应答S705中的通知消息，在本申请实施例中，该应答消息为肯定应答，表示用户上下文迁移完成。对应地，核心网网元接收该应答消息。该应答消息可以为前述方法300中的第四消息。
该应答消息也可以称为用户面路径变化事件应答消息或其他名称。
S715，核心网网元激活新的用户面路径。
S716，终端设备通过第二MEC平台上的目标应用实例访问应用，即通过新的用户面路径访问应用。
本申请实施例的通信方法，能够在MEC场景中实现基于应用实例的应用的用户上下文迁移，有利于保障业务的连续性，从而保障用户体验。
应理解，上述实施例均是假设目标应用实例在第二MEC平台已经存在，将应用的用户上下文从源应用实例迁移到目标应用实例上。若第二MEC平台处不存在目标应用实例，则在迁移应用的用户上下文之前，需要在第二MEC平台创建该目标应用实例，此处不再赘述。
应理解，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
上文中结合图1至图7，详细描述了根据本申请实施例的通信方法，下面将结合图8和图9，详细描述根据本申请实施例的通信装置。
图8示出了本申请实施例提供的通信装置800，该装置800包括：处理单元810和收发单元820。
在一种可能的实现方式中，装置800可以是前述的MEC网元，也可以是MEC网元中的芯片，用于执行上述方法300中MEC网元对应的各个流程或步骤。
其中，处理单元810用于：获取终端设备所访问的应用的源应用实例的信息和所述应用的目标应用实例的信息；收发单元820用于：向第一MEC平台发送第一消息，所述第一消息用于请求将所述应用的用户上下文从所述源应用实例迁移至所述目标应用实例，其中，所述源应用实例部署在所述第一MEC平台，所述目标应用实例部署在第二MEC平台；所述收发单元820还用于：接收来自所述第一MEC平台的第二消息，所述第二消息用于指示所述应用的用户上下文迁移状态。
可选地，所述收发单元820还用于：接收来自核心网控制面网元的第三消息，所述第三消息用于通知所述终端设备的用户面路径发生了变化；所述处理单元810具体用于：基于所述第三消息，确定所述源应用实例的信息和所述目标应用实例的信息，其中，所述源应用实例位于源数据网络的接入标识所对应的位置，所述目标应用实例位于目标数据网络的接入标识所对应的位置。
可选地，所述收发单元820还用于：基于所述第二消息，向所述核心网控制面网元发送第四消息，所述第四消息是对所述第三消息的肯定应答或否定应答。
可选地，所述第三消息包括下列信息中的至少一个：所述终端设备的标识、所述应用 的标识、所述源数据网络的接入标识、所述目标数据网络的接入标识。
可选地，所述收发单元820还用于：向所述核心网控制面网元发送第五消息，所述第五消息用于订阅所述终端设备的用户面路径变化事件。
可选地，所述装置为MEC编排器或MEC平台管理器。
可选地，所述装置包括MEC编排器和MEC平台管理器，所述MEC编排器包括：第一收发单元，用于通过所述MEC平台管理器向所述第一MEC平台发送所述第一消息；及，通过所述MEC平台管理器接收来自所述第一MEC平台的所述第二消息。
可选地，所述第一收发单元还用于：向所述MEC平台管理器发送第六消息，所述第六消息用于订阅所述应用的用户上下文迁移状态；所述MEC平台管理器包括：第二收发单元，用于接收所述第六消息，并向所述MEC编排器发送第一应答消息；所述第一收发单元还用于：接收所述第一应答消息。
可选地，所述MEC平台管理器包括：第二收发单元，用于向所述第一MEC平台发送第七消息，所述第七消息用于订阅所述应用的用户上下文迁移状态；以及接收来自所述第一MEC平台的第二应答消息。
可选地，所述MEC平台管理器包括：第二收发单元，用于接收来自所述第一MEC平台的所述第二消息；向所述MEC平台发送第三应答消息；以及，向所述MEC编排器发送所述第二消息；所述MEC编排器包括：第一收发单元，用于接收所述第二消息，并向所述MEC平台管理器发送第四应答消息；所述第二收发单元还用于：接收所述第四应答消息。
应理解，上述收发单元、第一收发单元、第二收发单元可以是三个独立的单元，也可以是集成的单元，例如，第一收发单元用于执行收发单元对应的收发动作，此时，收发单元和第一收发单元集成为一个单元，或者，第二收发单元用于执行收发单元对应的收发动作，此时，收发单元和第二收发单元集成为一个单元，本申请实施例对此不作限定。
在另一种可能的实现方式中，装置800可以是前述的第一MEC平台，也可以是第一MEC平台中的芯片，用于执行上述方法400中第一MEC平台对应的各个流程或步骤。
其中，收发单元820用于：接收来自核心网控制面网元的第三消息，所述第三消息用于通知终端设备的用户面路径发生了变化；处理单元810用于：基于所述第三消息，获取所述终端设备所访问的应用的源应用实例的信息和所述应用的目标应用实例的信息；以及，将所述应用的用户上下文从所述源应用实例迁移至所述目标应用实例，其中，所述源应用实例部署在所述装置，所述目标应用实例部署在第二MEC平台。
可选地，所述处理单元810具体用于：基于所述第三消息，向MEC编排器发送请求消息，所述请求消息用于请求所述目标应用实例的信息；接收所述MEC编排器发送的所述目标应用实例的信息。
可选地，所述收发单元820还用于：向所述核心网控制面网元发送第四消息，所述第四消息是对所述第三消息的肯定应答或否定应答。
可选地，所述第三消息包括下列信息中的至少一个：所述终端设备的标识、所述应用的标识、所述源数据网络的接入标识、所述目标数据网络的接入标识。
可选地，所述收发单元820还用于：向所述核心网控制面网元发送第五消息，所述第五消息用于订阅所述终端设备的用户面路径变化事件。
应理解，这里的装置800以功能单元的形式体现。这里的术语“单元”可以指应用特有集成电路(application specific integrated circuit，ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中，本领域技术人员可以理解，装置800可以具体为上述方法实施例中的MEC网元或第一MEC平台，装置800可以用于执行上述方法实施例中与MEC网元或第一MEC平台对应的各个流程和/或步骤，为避免重复，在此不再赘述。
上述各个方案的装置800具有实现上述方法中MEC网元或第一MEC平台执行的相应步骤的功能；所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。例如，收发单元可以包括接收单元和发送单元，发送单元可以由发射机替代，接收单元可以由接收机替代，其它单元，如处理单元等可以由处理器替代，分别执行各个方法实施例中的收发操作以及相关的处理操作。
在本申请的实施例，图8中的装置也可以是芯片或者芯片系统，例如：片上系统(system on chip，SoC)。对应地，收发单元(即接收单元和发送单元)可以是该芯片的收发电路，在此不做限定。
图9示出了本申请实施例提供的又一通信装置900。该装置900包括处理器910、收发器920和存储器930。其中，处理器910、收发器920和存储器930通过内部连接通路互相通信，该存储器930用于存储指令，该处理器910用于执行该存储器930存储的指令，以控制该收发器920发送信号和/或接收信号。
在一种可能的实现方式中，装置900用于执行上述方法300中MEC网元对应的各个流程或步骤。
其中，处理器910用于：获取终端设备所访问的应用的源应用实例的信息和所述应用的目标应用实例的信息；收发单元820用于：向第一MEC平台发送第一消息，所述第一消息用于请求将所述应用的用户上下文从所述源应用实例迁移至所述目标应用实例，其中，所述源应用实例部署在所述第一MEC平台，所述目标应用实例部署在第二MEC平台；所述收发器920还用于：接收来自所述第一MEC平台的第二消息，所述第二消息用于指示所述应用的用户上下文迁移状态。
在另一种可能的实现方式中，装置900用于执行上述方法400中第一MEC平台对应的各个流程或步骤。
其中，收发器920用于：接收来自核心网控制面网元的第三消息，所述第三消息用于通知终端设备的用户面路径发生了变化；处理器910用于：基于所述第三消息，获取所述终端设备所访问的应用的源应用实例的信息和所述应用的目标应用实例的信息；以及，将所述应用的用户上下文从所述源应用实例迁移至所述目标应用实例，其中，所述源应用实例部署在所述装置，所述目标应用实例部署在第二MEC平台。
应理解，装置900可以具体为上述方法实施例中的MEC网元或第一MEC平台，并且可以用于执行上述方法实施例中MEC网元或第一MEC平台对应的各个步骤和/或流程。可选地，该存储器930可以包括只读存储器和随机存取存储器，并向处理器提供指令和数据。存储器的一部分还可以包括非易失性随机存取存储器。例如，存储器还可以存储设备 类型的信息。该处理器910可以用于执行存储器中存储的指令，并且当该处理器910执行存储器中存储的指令时，该处理器910用于执行上述与MEC网元或第一MEC平台对应的方法实施例的各个步骤和/或流程。
应理解，上述的收发器可以包括发射机和接收机。收发器还可以进一步包括天线，天线的数量可以为一个或多个。存储器可以是一个单独的器件，也可以集成在处理器中。上述的各个器件或部分器件可以集成到芯片中实现，如集成到基带芯片中实现。
在本申请的实施例，图9中的收发器也可以是通信接口，在此不做限定。
在本申请的实施例中，上述MEC网元或第一MEC平台既可以是物理上的实体设备，也可是虚拟的功能网元，在此不做限定。
在本申请的各实施例中，为了方便理解，进行了多种举例说明。然而，这些例子仅仅是一些举例，并不意味着是实现本申请的最佳实现方式。
在本申请的各实施例中，为了方便的描述，采用了第一消息、第二消息以及其他各种消息的名称。然而，这些消息仅仅是以举例方式说明需要携带的内容或者实现的功能，消息的具体名称并不对本申请的做出限定，例如：还可以是通知消息、响应消息等。这些消息可以是具体的一些消息，可以是消息中的某些字段。这些消息还可以代表各种服务化操作。
也应理解，在本申请实施例中，上述装置的处理器可以是中央处理单元(central processing unit，CPU)，该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field-programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
根据本申请实施例提供的方法，本申请还提供一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行上述任意一个实施例中任意一个网元所对应的方法。例如，该计算机可以执行上述方法300中MEC网元所对应的方法，或者上述方法400中第一MEC平台所对应的方法。
根据本申请实施例提供的方法，本申请还提供一种计算机可读介质，该计算机可读介质存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行图3至图7所示实施例中任意一个实施例中任意一个网元所对应的方法。例如，该计算机可以执行上述方法300中MEC网元所对应的方法，或者上述方法400中第一MEC平台所对应的方法。
根据本申请实施例提供的方法，本申请还提供一种系统，其包括前述方法实施例中的一个或多个网元。例如，该系统可以包括上述方法300中的MEC网元。又例如，该系统可以包括上述方法400中的第一MEC平台。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disc，SSD))等。
在本说明书中使用的术语“部件”、“模块”、“系统”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如，部件可以是但不限于，在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序和/或计算机。通过图示，在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程和/或执行线程中，部件可位于一个计算机上和/或分布在两个或更多个计算机之间。此外，这些部件可从在上面存储有各种数据结构的各种计算机可读介质执行。部件可以例如根据具有一个或多个数据分组(例如来自与本地系统、分布式系统和/或网络间的另一部件交互的二个部件的数据，例如通过信号与其它系统交互的互联网)的信号通过本地和/或远程进程来通信。
在本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A、B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a、b或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c或a-b-c，其中a，b， c可以是单个，也可以是多个。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各种说明性逻辑块(illustrative logical block)和步骤(step)，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (33)

  1. 一种通信方法，其特征在于，包括：
    多接入边缘计算MEC网元获取终端设备所访问的应用的源应用实例的信息和所述应用的目标应用实例的信息；
    所述MEC网元向第一MEC平台发送第一消息，所述第一消息用于请求将所述应用的用户上下文从所述源应用实例迁移至所述目标应用实例，其中，所述源应用实例部署在所述第一MEC平台，所述目标应用实例部署在第二MEC平台；
    所述MEC网元接收来自所述第一MEC平台的第二消息，所述第二消息用于指示所述应用的用户上下文迁移状态。
  2. 根据权利要求1所述的方法，其特征在于，在所述多接入边缘计算MEC网元获取源应用实例的信息和目标应用实例的信息之前，所述方法还包括：
    所述MEC网元接收来自核心网控制面网元的第三消息，所述第三消息用于通知所述终端设备的用户面路径发生了变化；
    所述多接入边缘计算MEC网元获取源应用实例的信息和目标应用实例的信息，包括：
    所述MEC网元基于所述第三消息，确定所述源应用实例的信息和所述目标应用实例的信息，其中，所述源应用实例位于源数据网络的接入标识所对应的位置，所述目标应用实例位于目标数据网络的接入标识所对应的位置。
  3. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    所述MEC网元基于所述第二消息，向所述核心网控制面网元发送第四消息，所述第四消息是对所述第三消息的肯定应答或否定应答。
  4. 根据权利要求2或3所述的方法，其特征在于，所述第三消息包括下列信息中的至少一个：
    所述终端设备的标识、所述应用的标识、所述源数据网络的接入标识、所述目标数据网络的接入标识。
  5. 根据权利要求2至4中任一项所述的方法，其特征在于，在所述MEC网元接收来自核心网控制面网元的第三消息之前，所述方法还包括：
    所述MEC网元向所述核心网控制面网元发送第五消息，所述第五消息用于订阅所述终端设备的用户面路径变化事件。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述MEC网元为MEC编排器或MEC平台管理器。
  7. 根据权利要求1至5中任一项所述的方法，其特征在于，所述MEC网元包括MEC编排器和MEC平台管理器，所述MEC网元向第一MEC平台发送第一消息，包括：
    所述MEC编排器通过所述MEC平台管理器向所述第一MEC平台发送所述第一消息；
    所述MEC网元接收来自所述第一MEC平台的第二消息，包括：
    所述MEC编排器通过所述MEC平台管理器接收来自所述第一MEC平台的所述第二消息。
  8. 根据权利要求7所述的方法，其特征在于，所述方法还包括：
    所述MEC编排器向所述MEC平台管理器发送第六消息，所述第六消息用于订阅所述应用的用户上下文迁移状态；
    所述MEC平台管理器接收所述第六消息，并向所述MEC编排器发送第一应答消息；
    所述MEC编排器接收所述第一应答消息。
  9. 根据权利要求7或8所述的方法，其特征在于，所述方法还包括：
    所述MEC平台管理器向所述第一MEC平台发送第七消息，所述第七消息用于订阅所述应用的用户上下文迁移状态；
    所述MEC平台管理器接收来自所述第一MEC平台的第二应答消息。
  10. 根据权利要求7至9中任一项所述的方法，其特征在于，所述MEC编排器通过所述MEC平台管理器接收来自所述第一MEC平台的所述第二消息，包括：
    所述MEC平台管理器接收来自所述第一MEC平台的所述第二消息；
    所述MEC平台管理器向所述MEC平台发送第三应答消息；
    所述MEC平台管理器向所述MEC编排器发送所述第二消息；
    所述MEC编排器接收所述第二消息，并向所述MEC平台管理器发送第四应答消息；
    所述MEC平台管理器接收所述第四应答消息。
  11. 一种通信方法，其特征在于，包括：
    第一多接入边缘计算MEC平台接收来自核心网控制面网元的第三消息，所述第三消息用于通知终端设备的用户面路径发生了变化；
    所述第一MEC平台基于所述第三消息，获取所述终端设备所访问的应用的源应用实例的信息和所述应用的目标应用实例的信息；
    所述第一MEC平台将所述应用的用户上下文从所述源应用实例迁移至所述目标应用实例，其中，所述源应用实例部署在所述第一MEC平台，所述目标应用实例部署在第二MEC平台。
  12. 根据权利要求11所述的方法，其特征在于，所述第一MEC平台基于所述第三消息，获取终端设备所访问的应用的源应用实例的信息和所述应用的目标应用实例的信息，包括：
    所述第一MEC平台基于所述第三消息，向MEC编排器发送请求消息，所述请求消息用于请求所述目标应用实例的信息；
    所述第一MEC平台接收所述MEC编排器发送的所述目标应用实例的信息。
  13. 根据权利要求11或12所述的方法，其特征在于，所述方法还包括：
    所述第一MEC平台向所述核心网控制面网元发送第四消息，所述第四消息是对所述第三消息的肯定应答或否定应答。
  14. 根据权利要求11至13中任一项所述的方法，其特征在于，所述第三消息包括下列信息中的至少一个：
    所述终端设备的标识、所述应用的标识、所述源数据网络的接入标识、所述目标数据网络的接入标识。
  15. 根据权利要求11至14中任一项所述的方法，其特征在于，在所述第一多接入边缘计算MEC平台接收来自核心网控制面网元的第三消息之前，所述方法还包括：
    所述第一MEC平台向所述核心网控制面网元发送第五消息，所述第五消息用于订阅所述终端设备的用户面路径变化事件。
  16. 一种通信装置，其特征在于，包括：
    处理单元，用于获取终端设备所访问的应用的源应用实例的信息和所述应用的目标应用实例的信息；
    收发单元，用于向第一MEC平台发送第一消息，所述第一消息用于请求将所述应用的用户上下文从所述源应用实例迁移至所述目标应用实例，其中，所述源应用实例部署在所述第一MEC平台，所述目标应用实例部署在第二MEC平台；
    所述收发单元还用于：
    接收来自所述第一MEC平台的第二消息，所述第二消息用于指示所述应用的用户上下文迁移状态。
  17. 根据权利要求16所述的装置，其特征在于，所述收发单元还用于：
    接收来自核心网控制面网元的第三消息，所述第三消息用于通知所述终端设备的用户面路径发生了变化；
    所述处理单元具体用于：
    基于所述第三消息，确定所述源应用实例的信息和所述目标应用实例的信息，其中，所述源应用实例位于源数据网络的接入标识所对应的位置，所述目标应用实例位于目标数据网络的接入标识所对应的位置。
  18. 根据权利要求17所述的装置，其特征在于，所述收发单元还用于：
    基于所述第二消息，向所述核心网控制面网元发送第四消息，所述第四消息是对所述第三消息的肯定应答或否定应答。
  19. 根据权利要求17或18所述的装置，其特征在于，所述第三消息包括下列信息中的至少一个：
    所述终端设备的标识、所述应用的标识、所述源数据网络的接入标识、所述目标数据网络的接入标识。
  20. 根据权利要求17至19中任一项所述的装置，其特征在于，所述收发单元还用于：
    向所述核心网控制面网元发送第五消息，所述第五消息用于订阅所述终端设备的用户面路径变化事件。
  21. 根据权利要求16至20中任一项所述的装置，其特征在于，所述装置为MEC编排器或MEC平台管理器。
  22. 根据权利要求16至20中任一项所述的装置，其特征在于，所述装置包括MEC编排器和MEC平台管理器，所述MEC编排器包括：
    第一收发单元，用于通过所述MEC平台管理器向所述第一MEC平台发送所述第一消息；以及，通过所述MEC平台管理器接收来自所述第一MEC平台的所述第二消息。
  23. 根据权利要求22所述的装置，其特征在于，所述第一收发单元还用于：
    向所述MEC平台管理器发送第六消息，所述第六消息用于订阅所述应用的用户上下文迁移状态；
    所述MEC平台管理器包括：
    第二收发单元，用于接收所述第六消息，并向所述MEC编排器发送第一应答消息；
    所述第一收发单元还用于：接收所述第一应答消息。
  24. 根据权利要求22或23所述的装置，其特征在于，所述MEC平台管理器包括：
    第二收发单元，用于向所述第一MEC平台发送第七消息，所述第七消息用于订阅所述应用的用户上下文迁移状态；以及接收来自所述第一MEC平台的第二应答消息。
  25. 根据权利要求22至24中任一项所述的装置，其特征在于，所述MEC平台管理器包括：
    第二收发单元，用于接收来自所述第一MEC平台的所述第二消息；向所述MEC平台发送第三应答消息；以及，向所述MEC编排器发送所述第二消息；
    所述MEC编排器包括：
    第一收发单元，用于接收所述第二消息，并向所述MEC平台管理器发送第四应答消息；
    所述第二收发单元还用于：接收所述第四应答消息。
  26. 一种通信装置，其特征在于，包括：
    收发单元，用于接收来自核心网控制面网元的第三消息，所述第三消息用于通知终端设备的用户面路径发生了变化；
    处理单元，用于基于所述第三消息，获取所述终端设备所访问的应用的源应用实例的信息和所述应用的目标应用实例的信息；以及，将所述应用的用户上下文从所述源应用实例迁移至所述目标应用实例，其中，所述源应用实例部署在所述通信装置，所述目标应用实例部署在第二MEC平台。
  27. 根据权利要求26所述的装置，其特征在于，所述处理单元具体用于：
    基于所述第三消息，向MEC编排器发送请求消息，所述请求消息用于请求所述目标应用实例的信息；
    接收所述MEC编排器发送的所述目标应用实例的信息。
  28. 根据权利要求26或27所述的装置，其特征在于，所述收发单元还用于：
    向所述核心网控制面网元发送第四消息，所述第四消息是对所述第三消息的肯定应答或否定应答。
  29. 根据权利要求26至28中任一项所述的装置，其特征在于，所述第三消息包括下列信息中的至少一个：
    所述终端设备的标识、所述应用的标识、所述源数据网络的接入标识、所述目标数据网络的接入标识。
  30. 根据权利要求26至29中任一项所述的装置，其特征在于，所述收发单元还用于：
    向所述核心网控制面网元发送第五消息，所述第五消息用于订阅所述终端设备的用户面路径变化事件。
  31. 一种通信装置，其特征在于，包括：处理器、存储器以及存储在所述存储器上并可在所述处理器上运行的指令，当所述指令被运行时，使得所述装置执行权利要求1至15中任一项所述的方法。
  32. 一种计算机可读存储介质，其特征在于，包括指令，当其在计算机上运行时，使得所述计算机执行权利要求1至15中任一项所述的方法。
  33. 一种芯片系统，其特征在于，包括：处理器，用于从存储器中调用并运行计算机 程序，使得安装有所述芯片系统的通信设备执行权利要求1至15中任一项所述的方法。
PCT/CN2021/088136 2020-06-29 2021-04-19 通信方法和通信装置 WO2022001298A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21832819.3A EP4156780A4 (en) 2020-06-29 2021-04-19 COMMUNICATION METHOD AND COMMUNICATION DEVICE
US18/147,166 US11943286B2 (en) 2020-06-29 2022-12-28 Application instance switching method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010603843.6 2020-06-29
CN202010603843.6A CN113949705B (zh) 2020-06-29 2020-06-29 通信方法和通信装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/147,166 Continuation US11943286B2 (en) 2020-06-29 2022-12-28 Application instance switching method and apparatus

Publications (1)

Publication Number Publication Date
WO2022001298A1 true WO2022001298A1 (zh) 2022-01-06

Family

ID=79315112

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/088136 WO2022001298A1 (zh) 2020-06-29 2021-04-19 通信方法和通信装置

Country Status (4)

Country Link
US (1) US11943286B2 (zh)
EP (1) EP4156780A4 (zh)
CN (1) CN113949705B (zh)
WO (1) WO2022001298A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023155105A1 (en) * 2022-02-17 2023-08-24 Zte Corporation Method for application mobility service across multi-access edge computing
CN115022343B (zh) * 2022-06-17 2024-05-24 阿里云计算有限公司 对象迁移方法、装置及设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017066945A1 (zh) * 2015-10-21 2017-04-27 华为技术有限公司 Mec平台的切换方法、装置及系统
CN109429284A (zh) * 2017-08-31 2019-03-05 华为技术有限公司 实例切换方法及相关装置
WO2020072222A1 (en) * 2018-10-04 2020-04-09 Cisco Technology, Inc. Placement of container workloads triggered by network traffic for efficient computing at network edge devices
CN111225348A (zh) * 2018-11-23 2020-06-02 华为技术有限公司 一种应用实例迁移的方法及多接入边缘计算主机

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1437020B1 (en) * 2001-09-21 2013-02-27 Nokia Siemens Networks Oy System and method for enabling mobile edge services
US6909899B2 (en) * 2002-03-11 2005-06-21 Qualcomm, Incoporated Method and apparatus for handoff in a communication system supporting multiple service instances
WO2016134772A1 (en) * 2015-02-26 2016-09-01 Nokia Solutions And Networks Oy Charging and control of edge services
CN106254408A (zh) * 2015-06-12 2016-12-21 财团法人工业技术研究院 移动边缘计算的控制方法、网络系统与服务平台
CN107736044B (zh) * 2015-06-18 2021-10-19 索尼公司 系统、方法和终端设备
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
CN108028783B (zh) * 2015-11-30 2020-07-24 华为技术有限公司 切换移动边缘平台的方法、装置和系统
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 诺基亚通信公司 用于利用移动边缘计算的改进服务连续性的方法、装置和计算机程序产品
EP3409044B1 (en) * 2016-01-27 2020-04-15 Nokia Solutions and Networks Oy Method and apparatus for implementing mobile edge application session connectivity and mobility
CN107305502B (zh) * 2016-04-21 2022-01-25 中兴通讯股份有限公司 一种应用实例迁移的方法及设备
US10440096B2 (en) * 2016-12-28 2019-10-08 Intel IP Corporation Application computation offloading for mobile edge computing
CN108574728B (zh) * 2017-03-08 2021-05-04 中兴通讯股份有限公司 用于移动边缘计算的流量路径改变检测的方法和装置
CN109218455B (zh) * 2017-06-30 2021-04-09 华为技术有限公司 一种应用实例地址的转换方法和装置
US10517020B2 (en) * 2017-12-15 2019-12-24 Industrial Technology Research Institute Mobile edge platform servers and user equipment context migration management methods thereof
US20190034917A1 (en) * 2017-12-29 2019-01-31 Intel Corporation Tracking an Electronic Wallet Using Radio Frequency Identification (RFID)
US10455640B2 (en) * 2017-12-30 2019-10-22 Intel Corporation IoT networking extension with bi-directional packet relay
DE112018007463T5 (de) * 2018-04-11 2020-12-24 Intel IP Corporation Flexibler Mehrfachzugriffs-Edge-Computing-Dienstverbrauch (Mec-Dienstverbrauch) durch Hostzoning
US10813010B2 (en) * 2018-12-17 2020-10-20 Verizon Patent And Licensing Inc. Method and system for edge computing handover service
CN111132253B (zh) * 2019-12-31 2021-03-30 北京邮电大学 一种通信切换和服务迁移的联合移动性管理方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017066945A1 (zh) * 2015-10-21 2017-04-27 华为技术有限公司 Mec平台的切换方法、装置及系统
CN109429284A (zh) * 2017-08-31 2019-03-05 华为技术有限公司 实例切换方法及相关装置
WO2020072222A1 (en) * 2018-10-04 2020-04-09 Cisco Technology, Inc. Placement of container workloads triggered by network traffic for efficient computing at network edge devices
CN111225348A (zh) * 2018-11-23 2020-06-02 华为技术有限公司 一种应用实例迁移的方法及多接入边缘计算主机

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4156780A4

Also Published As

Publication number Publication date
US11943286B2 (en) 2024-03-26
EP4156780A4 (en) 2023-11-08
US20230134708A1 (en) 2023-05-04
CN113949705B (zh) 2023-07-11
CN113949705A (zh) 2022-01-18
EP4156780A1 (en) 2023-03-29

Similar Documents

Publication Publication Date Title
JP7184922B2 (ja) Ｕｅのためにポリシーを構成するための方法、装置、及びシステム
WO2018153346A1 (zh) 一种网络切片的选择方法及装置
WO2020224575A1 (zh) 通信方法与装置
US11637891B2 (en) Method and apparatus for transferring an edge computing application
US11943286B2 (en) Application instance switching method and apparatus
JP7389225B2 (ja) セキュリティ保護モードを決定するための方法および装置
CN112823564B (zh) 提供动态nef隧道分配的方法和相关的网络节点
WO2020253551A1 (zh) 通信方法和通信装置
US11310658B2 (en) Method and apparatus for determining status of terminal device, and device
WO2022089163A1 (zh) 一种管理网络切片数据的方法和装置
WO2019057015A1 (zh) 一种网络切片管理方法及装置
US20220295383A1 (en) Object-resource model to facilitate iot services
WO2021223637A1 (zh) 应用迁移方法及装置
WO2022152089A1 (zh) 一种信息传输方法及其装置
CN110958623A (zh) 一种小区的配置方法和装置
JP2021514130A (ja) 無線アクセス技術間ハンドオーバの方法
WO2022022322A1 (zh) 访问本地网络的方法和装置
WO2023051288A1 (zh) 一种隧道管理方法、装置及系统
WO2022253137A1 (zh) 接入业务的方法、装置和系统
WO2021203983A1 (zh) 处理时间同步报文的方法和装置
WO2023246104A1 (zh) 通信方法及相关装置
WO2024032552A1 (zh) 通信方法、装置及存储介质
WO2023185572A1 (zh) 通信方法和装置
WO2022213824A1 (zh) 一种用于传输上下文的方法和通信装置
EP4262244A1 (en) Method and device for determining mec access point

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021832819

Country of ref document: EP

Effective date: 20221220

NENP Non-entry into the national phase

Ref country code: DE