WO2022213824A1 - 一种用于传输上下文的方法和通信装置 - Google Patents

一种用于传输上下文的方法和通信装置 Download PDF

Info

Publication number
WO2022213824A1
WO2022213824A1 PCT/CN2022/083051 CN2022083051W WO2022213824A1 WO 2022213824 A1 WO2022213824 A1 WO 2022213824A1 CN 2022083051 W CN2022083051 W CN 2022083051W WO 2022213824 A1 WO2022213824 A1 WO 2022213824A1
Authority
WO
WIPO (PCT)
Prior art keywords
edge
information
enabled
server
context
Prior art date
Application number
PCT/CN2022/083051
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 EP22783891.9A priority Critical patent/EP4304248A4/en
Publication of WO2022213824A1 publication Critical patent/WO2022213824A1/zh
Priority to US18/482,820 priority patent/US20240040005A1/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/14—Session management
    • H04L67/148—Migration or transfer of sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • 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/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies

Definitions

  • the present application relates to the field of communication, and more particularly, to a method and communication apparatus for transmitting context.
  • the edge application server (EAS) currently providing services may not be able to continue to provide services for the currently running application, or the edge currently providing services may not be able to continue to provide services.
  • the application server is no longer the optimal edge application server that can provide services for the terminal.
  • Other edge application servers may be more suitable for serving the terminal.
  • a new edge application server can be selected to provide services for the terminal.
  • the application service may be temporarily suspended or interrupted, which affects the transmission of the application service.
  • the present application provides a method and a communication device for transmitting context, which help to reduce the duration of application service suspension or interruption during the switching of edge application servers, thereby improving the continuity of application service transmission.
  • the present application provides a method for transmitting a context, the method comprising: when an edge enabler client (EEC) context is transmitted by a second edge enabler server (EES)
  • EEC edge enabler client
  • EES edge enabler server
  • the first device sends first information to the first edge application server EAS corresponding to the first EES, where the first information is used by the first EAS to send the first EES to the first EES. Subscribe to EES capability disclosure information.
  • the above-mentioned first apparatus may be a source EES, a target EES or an EEC.
  • the EEC context is transmitted from the second EES to the first EES, which can also be understood as the first EES is the target EES and the second EES is the source EES.
  • the first device when the EEC context transmission fails, can instruct the target EAS to subscribe the EES capability opening information to the target EES, which can avoid re-executing the entire EEC context migration process, and help reduce the number of applications in the edge application server switching process.
  • the duration of service suspension or interruption thereby improving the continuity of application service transmission.
  • the first information includes EEC context transmission failure notification information or first indication information
  • the EEC context transmission failure notification information is used to notify the first EAS that the The EEC context transmission fails
  • the first indication information is used to instruct the first EAS to subscribe the EES capability opening information to the first EES.
  • the first information includes EEC context transmission failure notification information and application context transmission success notification information, where the EEC context transmission failure notification information is used to notify the EEC that the EEC context transmission fails, and the application context transmission success notification information is used to notify the EEC Notifies the application that the context transfer was successful.
  • the first information may directly or indirectly instruct the first EAS to subscribe the EES capability opening information to the first EES.
  • the EES capability opening information includes at least one of the following information: user equipment (user equipment, UE) location application programming Interface (application program interface, API), application context relocation event, application client (application client, AC) information open API, UE identification API, and quality of service (quality of service, QoS) session API.
  • the EES exposes the UE Location API to the EAS to support tracking or checking the valid location of the UE.
  • the UE location API exposed by EES relies on 3GPP core network capabilities.
  • the EAS can request a one-time report from the UE location API to check the current UE location, and continuous reporting to track the location of the UE.
  • the UE Location API supports both a request-response for a one-time query (in order to check the current location of the UE) and a subscription notification model for continuously providing the UE's location to the EAS and enabling the EAS to track the UE's location (as the UE's location changes) Variety).
  • Application Context Migration Event The EES opens the EAS for notification of ACR management events for one or more UEs (eg, to trigger ACR).
  • ACR management event notifications exposed by EES may rely on the network exposure function (NEF) northbound API to monitor user plane path management events.
  • NEF network exposure function
  • Application context migration events can also be replaced with application context relocation events.
  • AC Information Open API It means that EAS obtains AC capability information from EES. This information may facilitate communication between EAS and AC, such as push notifications. Shared information is subject to access controls and privacy and security mechanisms.
  • the EES exposes the UE Identification API to the EAS in order to provide an identifier that uniquely identifies the UE. When the EAS does not have the UE's identity, the EAS uses this API to obtain the UE's identity. This identifier is called the Edge UE ID and is used by EAS to call UE-specific capability APIs via EDGE-3.
  • QoS session API EES opens session API with QoS to EAS to support establishing a data session with specific QoS between AC and EAS, and modify the QoS of this data session.
  • the first device is the first EES or the second EES; the method further includes: the The first apparatus sends second information to the EEC, where the second information is used by the EEC to initiate registration with the first EES.
  • the second information may directly or indirectly instruct the EEC to initiate registration with the first EES.
  • the second information includes EEC context transmission failure notification information, where the EEC context transmission failure notification information is used to notify the EEC that the EEC context transmission fails.
  • the second information includes EEC context transmission failure notification information and application context transmission success notification information, the EEC context transmission failure notification information is used to notify the EEC that the EEC context transmission fails, and the application context transmission success notification information is used to notify the EEC of the application context. The transfer was successful.
  • the second information includes second indication information, where the second indication information is used to instruct the EEC to initiate registration with the first EES.
  • the target EES may determine whether to instruct the EEC to register with the target EES according to its actual situation.
  • the first device instructs the EEC to register with the first EES in order to use the edge application service.
  • the first device is the first EES or the second EES; the method further includes: the The first device sends third information to the EEC, where the third information is used for the EEC to subscribe the first EES to a service of EAS discovery and/or EAS information. It can also be understood that the EEC subscribes to the information of Edge-1 (that is, between EEC and EES), for example, EAS availability changes, EAS dynamic information changes, and so on.
  • Edge-1 that is, between EEC and EES
  • the third information may directly or indirectly instruct the EEC to subscribe the first EES to the service of EAS discovery and/or EAS information.
  • the third information includes EEC context transmission failure notification information, and the EEC context transmission failure notification information is used to notify the EEC that the EEC context transmission fails.
  • the third information includes EEC context transmission failure notification information and application context transmission success notification information, the EEC context transmission failure notification information is used to notify the EEC of the EEC context transmission failure, and the application context transmission successful notification information is used to notify the EEC of the application context. The transfer was successful.
  • the third information includes third indication information, where the third indication information is used to instruct the EEC to subscribe the first EES to the service of EAS discovery and/or EAS information.
  • the first device is the second EES
  • the method further includes: the first device receives an Fourth information of the second EES, where the fourth information is used to indicate that the EEC context transmission fails; the first apparatus determines, according to the fourth information, that the EEC context transmission fails.
  • the method further includes: in the case of triggering application context migration, the first apparatus determines the first EES and the first EAS; the first device transmits the EEC context to the first EES; the first device instructs the second EAS corresponding to the first device to send the application context to the first EAS , or, the first apparatus sends the application context obtained from the second EAS to the first EAS through the first EES.
  • the source EES initiates and coordinates the transmission of the application context and the EEC context, thereby ensuring that when the application context is relocated, both the application context and the EEC context are migrated to the target side, which can prevent the application from running short of necessary subscription information , which helps to reduce the duration of application service suspension or interruption during the switching of edge application servers, thereby improving the continuity of application service transmission.
  • the first device is the EEC; the method further includes: the first device reports to the first device EES subscribes to EAS discovery and/or EAS information services. It can also be understood that the EEC subscribes to the information of Edge-1 (that is, between EEC and EES), for example, EAS availability changes, EAS dynamic information changes, and so on.
  • Edge-1 that is, between EEC and EES
  • the first apparatus sends the first information to the first EAS corresponding to the first EES, including: the The first device sends the first information to the first EAS through the first EES.
  • the above-mentioned indication sent by the S-EES is transparently transmitted or forwarded by the T-EES to the T-EAS.
  • the S-EES may indicate to the T-EES that the T-EAS needs to subscribe the required service to the T-EES, and further instruct the T-EAS to subscribe the required service to the T-EES by the T-EES.
  • the first device is the first EES
  • the method further includes: when the first device does not receive When the EEC context is from the second EES, the first apparatus determines that the transmission of the EEC context has failed.
  • the method further includes: in the case of triggering application context migration, the first apparatus determines the second EES and a second EAS corresponding to the second EES; the first device requests the EEC context from the second EES; the first device instructs the first EAS to request the second EAS for the EEC context application context, or the first apparatus requests the application context from the second EES.
  • the target EES initiates and coordinates the transmission of the application context and the EEC context, thereby ensuring that when the application context is relocated, both the application context and the EEC context are migrated to the target side, which can prevent the application from running short of necessary subscription information , which helps to reduce the duration of application service suspension or interruption during the switching of edge application servers, thereby improving the continuity of application service transmission.
  • the first device is the EEC
  • the method further includes: the first device reports to the first device EES initiates registration.
  • the EEC registers with the first EES to use the edge application service.
  • the method further includes: receiving, by the first device, the first information from the first EES or the second EES. Five pieces of information, where the fifth information is used to indicate that the EEC context transmission fails; the first apparatus determines, according to the fifth information, that the EEC context transmission fails.
  • the method further includes: in the case of triggering application context migration, the first device sends a message to the first EES Or the second EES sends sixth information, where the sixth information is used to instruct to initiate transmission of the application context and the EEC context.
  • the EEC initiates and coordinates the transmission of the application context and the EEC context, thereby ensuring that when the application context is relocated, both the application context and the EEC context are migrated to the target side, which can avoid the lack of necessary subscription information for the application to run. It helps to reduce the duration of application service suspension or interruption during the switching of edge application servers, thereby improving the continuity of application service transmission.
  • the first apparatus sends the first information to the first EAS corresponding to the first EES, including: the The first device sends the first information to the first EAS through the first EES.
  • the above-mentioned indication sent by the EEC is transparently transmitted or forwarded by the T-EES to the T-EAS.
  • the EEC may indicate to the T-EES that the T-EAS needs to subscribe the required service to the T-EES, and further instruct the T-EAS to subscribe the required service to the T-EES by the T-EES.
  • the present application provides a method for transmitting a context, the method comprising: a first EAS receiving first information from a first device, where the first information is used by the first EAS to communicate with the other device.
  • the first EES corresponding to the first EAS subscribes to the EES capability opening information; the first EAS subscribes the EES capability opening information to the first EES according to the first information.
  • the above-mentioned first apparatus may be a source EES, a target EES or an EEC.
  • the first EAS can subscribe the EES capability opening information to the target EES according to the instruction of the first device, which can avoid re-executing the entire EEC context migration process and help reduce application service hangs during the switching process of the edge application server.
  • the duration of the start or interruption thereby improving the continuity of application service transmission.
  • the first information includes EEC context transmission failure notification information or first indication information
  • the EEC context transmission failure notification information is used to notify the first EAS that the The EEC context transmission fails
  • the first indication information is used to instruct the first EAS to subscribe the EES capability opening information to the first EES.
  • the first information includes EEC context transmission failure notification information and application context transmission success notification information, where the EEC context transmission failure notification information is used to notify the EEC that the EEC context transmission fails, and the application context transmission success notification information is used to notify the EEC Notifies the application that the context transfer was successful.
  • the EES capability opening information includes at least one of the following information: UE location API, application context relocation event, AC Information Open API, UE Identity API, and QoS Session API.
  • the present application provides a method for transmitting a context, the method comprising: when the application context transmission succeeds and the EEC context transmission fails, the first device requests the second EES to retransmit the the EEC context, or the first apparatus retransmits the EEC context to the first EES, and the EEC context is transmitted from the second EES to the first EES.
  • the first device may instruct the source EES to retransmit the EEC context to the target EES, or instruct the target EES to request the source EES to retransmit the EEC context, which can avoid re-execution
  • the entire EEC context migration process helps to reduce the duration of application service suspension or interruption during the switching of edge application servers, thereby improving the continuity of application service transmission.
  • the present application provides a method for transmitting a context, the method comprising: when the application context transmission succeeds and the EEC context transmission fails, the first device sends seventh information to the second EES, the seventh information is used to instruct the second EES to retransmit the EEC context to the first EES, or the first device sends eighth information to the first EES, where the eighth information is used to instruct the first EES
  • the first EES requests the second EES to retransmit the EEC context, which is transmitted by the second EES to the first EES.
  • the first device may instruct the source EES to retransmit the EEC context to the target EES, or instruct the target EES to request the source EES to retransmit the EEC context, which can avoid re-execution
  • the entire EEC context migration process helps to reduce the duration of application service suspension or interruption during the switching of edge application servers, thereby improving the continuity of application service transmission.
  • the present application provides a method for transmitting a context, the method comprising: when the transmission of the EEC context is successful, the transmission of the application context fails and the EES needs to be re-selected, the first device deletes the EEC context, or, The first apparatus sends ninth information to the first EES, where the ninth information is used to instruct the first EES to delete the EEC context, and the EEC context is transmitted from the second EES to the first EES.
  • the first device can delete the EEC context, or can instruct the target EES to delete the EEC context, which can avoid storing unnecessary EECs on the EES context.
  • the present application provides a method for transmitting a context, the method comprising: when the transmission of the EEC context is successful, the transmission of the application context fails and there is no need to reselect the EES, the first device sends tenth information to the second EAS , the tenth information is used to instruct the second EAS to retransmit the application context to the first EAS, or the first device sends eleventh information to the first EAS, where the eleventh information is used for The first EAS is instructed to request the second EAS to retransmit the application context.
  • the first device determines not to delete the EEC context, and instructs the source EAS to retransmit the application context.
  • the above-mentioned first apparatus may be a source EES, a target EES or an EEC.
  • the first device may instruct the source EAS to retransmit the application context to the target EAS, or instruct the target EAS to request the source EAS to retransmit the application Context can avoid re-executing the entire application context migration process, which helps to reduce the duration of application service suspension or interruption during the switching process of the edge application server, thereby improving the continuity of application service transmission.
  • the first apparatus is the source EES
  • the method further includes: in the case of triggering application context migration, the first apparatus determines the a target EES and a target EAS corresponding to the target EES; the first device transmits the EEC context to the target EES; the first device instructs the source EAS corresponding to the first device to the target EAS
  • the application context is sent, or the first apparatus sends the application context obtained from the source EAS to the target EES.
  • the method further includes: receiving, by the first device, fourth information from the target EES , the fourth information is used to indicate the transmission result of the EEC context; the first apparatus determines the transmission result of the EEC context transmission according to the fourth information.
  • the first device is the target EES
  • the method further includes: in the case of triggering application context migration Next, the first device determines a source EES and a source EAS corresponding to the source EES; the first device requests the EEC context from the source EES; the first device instructs the target EAS to The source EAS requests the application context, or the first apparatus requests the application context from the source EES.
  • the method further includes: the first apparatus according to whether the received information from the source EES The EEC context is determined, and the transmission result of the EEC context is determined.
  • the first device is an EEC
  • the method further includes: in the case of triggering application context migration , the first apparatus sends sixth information to the source EES or the target EES, where the sixth information is used to indicate initiating transmission of the application context and the EEC context.
  • the method further includes: the first apparatus receiving data from the source EES or the target EES
  • the fifth information is used to indicate the transmission result of the EEC context; the first apparatus determines the transmission result of the EEC context according to the fifth information.
  • the present application provides a method for transmitting a context, the method comprising: the EEC receives second information from a first device, where the EEC initiates registration with the first EES; The EEC initiates registration with the first EES according to the second information.
  • the second information may directly or indirectly instruct the EEC to initiate registration with the first EES.
  • the second information includes EEC context transmission failure notification information, where the EEC context transmission failure notification information is used to notify the EEC that the EEC context transmission fails.
  • the second information includes EEC context transmission failure notification information and application context transmission success notification information, the EEC context transmission failure notification information is used to notify the EEC that the EEC context transmission fails, and the application context transmission success notification information is used to notify the EEC of the application context. The transfer was successful.
  • the second information includes second indication information, where the second indication information is used to instruct the EEC to initiate registration with the first EES.
  • the method further includes: receiving, by the EEC, third information from the first device, where the third information is used to instruct the EEC to report to the first device
  • An EES subscribes to the service of EAS discovery and/or EAS information; the EEC subscribes the service of EAS discovery and/or EAS information to the first EES according to the third information.
  • the third information may directly or indirectly instruct the EEC to subscribe the first EES to the service of EAS discovery and/or EAS information.
  • the third information includes EEC context transmission failure notification information, and the EEC context transmission failure notification information is used to notify the EEC that the EEC context transmission fails.
  • the third information includes EEC context transmission failure notification information and application context transmission success notification information, the EEC context transmission failure notification information is used to notify the EEC of the EEC context transmission failure, and the application context transmission successful notification information is used to notify the EEC of the application context. The transfer was successful.
  • the third information includes third indication information, where the third indication information is used to instruct the EEC to subscribe the first EES to the service of EAS discovery and/or EAS information.
  • the present application provides a communication apparatus, the apparatus comprising a module for executing the method in any one of the foregoing aspects or any possible implementation manners thereof.
  • the present application provides a communication device including a processor.
  • the processor is coupled to the memory and is operable to execute instructions in the memory to implement the method in any of the possible implementations of any of the above aspects.
  • the apparatus further includes a memory.
  • the apparatus further includes a communication interface to which the processor is coupled.
  • the present application provides a chip including a processor.
  • the processor is coupled to the memory and is operable to execute instructions in the memory to implement the method in any of the possible implementations of any of the above aspects.
  • the apparatus further includes a memory.
  • the apparatus further includes a communication interface to which the processor is coupled.
  • the present application provides a processor, including: an input circuit, an output circuit, and a processing circuit.
  • the processing circuit is configured to receive a signal through the input circuit and output a signal through the output circuit, so that the processor executes the method in any one of the possible implementation manners of any one 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.
  • the present application provides a communication device 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 of the possible implementation manners of any one 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 device in the twelfth aspect above may be a chip, and the processor may be implemented by hardware or software.
  • the processor When implemented by hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented by software, the processor may be a logic circuit, an integrated circuit, etc.
  • the processor may be a general-purpose processor, which is realized by reading software codes stored in a memory, and the memory may be integrated in the processor, or located outside the processor, and exists independently.
  • the present application provides a computer-readable storage medium, in which a computer program or instruction is stored, and when the computer program or instruction is executed, any possibility in any of the above-mentioned aspects is realized. method in the implementation.
  • the present application provides a computer program product comprising instructions that, when executed, implement the method in any possible implementation of any of the foregoing aspects.
  • the present application provides a communication system, which includes any one or more of the foregoing communication devices.
  • FIG. 1 is a schematic structural diagram of a communication system 1000 to which an embodiment of the present application is applied.
  • Figure 2 is an implementation of application context migration.
  • FIG. 3 is a schematic diagram of a service provisioning process.
  • FIG. 4 is a schematic diagram of a conventional EAS discovery process.
  • Figure 5 is another implementation of application context migration.
  • Figure 6 is another implementation of application context migration.
  • Figure 7 is another implementation of application context migration.
  • Figure 8 is another implementation of application context migration.
  • Figure 9 is another implementation of application context migration.
  • FIG. 10 is a schematic flowchart of a method for transmitting context provided by the present application.
  • FIG. 11 is an example of a method for transmitting context provided by the present application.
  • FIG. 12 is another example of a method for transmitting context provided by the present application.
  • FIG. 13 is another example of a method for transmitting context provided by the present application.
  • FIG. 14 is a schematic structural diagram of a possible communication apparatus provided by an embodiment of the present application.
  • FIG. 15 is another schematic structural diagram of a possible communication apparatus provided by an embodiment of the present application.
  • the technical solutions of the embodiments of the present application can be applied to various communication systems, for example, fifth generation ( 5th generation, 5G) mobile communication systems, new radio access technology (NR) systems, long-term evolution (long-term evolution) term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile telecommunication system (UMTS), or global interconnection microwave Access (worldwide interoperability for microwave access, WiMAX) communication system.
  • the mobile communication system may include a non-standalone (NSA, NSA) and/or an independent network (standalone, SA).
  • the technical solutions provided in this application can be applied to future communication systems, such as the sixth generation mobile communication system. This application does not limit this.
  • the technical solutions provided in this application can also be applied to machine type communication (MTC), Long Term Evolution-machine (LTE-M), device-to-device (D2D) Network, machine to machine (M2M) network, internet of things (IoT) network or other network.
  • the IoT network may include, for example, the Internet of Vehicles.
  • vehicle to X, V2X, X can represent anything
  • the V2X may include: vehicle to vehicle (vehicle to vehicle, V2V) communication, vehicle and vehicle Infrastructure (V2I) communication, vehicle to pedestrian (V2P) or vehicle to network (V2N) communication, etc.
  • the technical solutions of the present application can be applied to various communication scenarios, such as service continuity scenarios, mobile edge computing (mobile edge computing, MEC) scenarios, etc., which are not limited in this application.
  • FIG. 1 is a schematic structural diagram of a communication system 1000 to which an embodiment of the present application is applied.
  • the communication system includes a terminal 110 , a core network 120 , an edge data network (EDN) 130 and an edge configuration server (ECS) 140 .
  • the terminal 110 may be deployed with one or more ACs 111 and one or more EECs 112
  • the EDN 130 may be deployed with one or more EAS 131 and one or more EES 132 .
  • the EDGE-1 interface is the interface between the EES132 and the EEC112
  • the EDGE-2 interface is the interface between the EES132 and the core network 120
  • the EDGE-3 interface is the interface between the EAS131 and the EES132
  • the EDGE-4 interface is the interface between the EEC112 and the core network 120.
  • the interface between ECS140, EDGE-5 interface is the interface between AC111 and EEC112
  • EDGE-6 interface is the interface between EES132 and ECS140
  • EDGE-7 interface is the interface between EAS131 and core network 120
  • EDGE-8 The interface is the interface between the ECS 140 and the core network 120
  • the EDGE-9 interface is the interface between the EES 132.
  • FIG. 1 is only a schematic diagram, and the communication system may also include other network devices, which are not shown in FIG. 1 .
  • the application user signs a service agreement with the application provider, so as to provide services for the application user.
  • the application user can log in to the AC111 on the terminal 110, and communicate with the EDN130 through the connection between the AC111 and the EAS131.
  • the EEC112 is a middleware layer, generally located in the operating system, or between the AC111 and the operating system.
  • the AC111 can obtain edge-enabled services from the EEC112 in the form of an API.
  • MEC can use the wireless access network to provide the services and cloud computing functions required by telecom users' IT nearby, and create a carrier-class service environment with high performance, low latency and high bandwidth, and accelerate the network content, services and applications. Fast downloads allow consumers to enjoy an uninterrupted high-quality web experience.
  • a data network refers to a service network of an operator or a third party, which can provide services (for example, operator services, Internet services, etc.) to terminals.
  • a local data network may be an access point to a data network that is very close to the user's attachment point.
  • EDN corresponds to only one data network, which is a special local data network that includes edge-enabled functions and can use data network access identifier (DNAI) and data network name (data network name). , DNN) logo, is a network logic concept.
  • DNAI data network access identifier
  • DNN data network name
  • EDN is a peer-to-peer concept of central cloud, which can be understood as a local data center (geographical location concept), which can be identified by DNAI and can contain one or more local data networks.
  • EAS may refer to an instance (instance) of a server application (eg, social media software, augmented reality (AR), virtual reality (VR)) deployed and running on the EDN.
  • a server application eg, social media software, augmented reality (AR), virtual reality (VR) deployed and running on the EDN.
  • AR augmented reality
  • VR virtual reality
  • An application can deploy one or more EASs in one or more EDNs.
  • EAS deployed and running in different EDNs can be considered as different EASs of an application, which can share a domain name, use an IP address, or use different IP addresses.
  • edge application servers can also be replaced with edge applications, edge application servers, application instances, edge application instances, MEC applications, MEC application servers, EAS functions, etc., which are not limited in this application.
  • edge application servers For the convenience of description, hereinafter collectively referred to as edge application servers.
  • the AC is the peer entity of the application server on the terminal side, and is used for the application user (user) to obtain the application service from the application server.
  • the AC can be a client program applied on the terminal side, can be connected to an application server on the cloud to obtain application services, or can be connected to an EAS deployed and run in one or more EDNs to obtain application services.
  • the AC may also be called an application client, which is not limited in this application.
  • EES can provide some enabling capabilities for EAS deployed in EDN.
  • EES can support the registration of edge application servers, authentication and authentication of terminals, and provide IP address information of edge application servers for terminals.
  • the EES can also support obtaining the identification and IP address information of the edge application server, and support further sending the obtained identification and IP address information to the ECS.
  • EES is deployed in EDN.
  • an EAS is registered with an EES, or the information of an EAS is configured on an EES through a management system, the EES is called the EES associated with the EAS, or the EAS is called the EAS associated with the EES, EES Controls or manages the EAS registered or configured on this EES.
  • the EAS associated with the EES may also be replaced with the EAS corresponding to the EES, and the EES associated with the EAS may also be replaced with the EES corresponding to the EAS, which is not limited in this application.
  • EEC is the peer entity of EES on the terminal side.
  • EEC can be used to register EEC information and AC information with EES, perform security authentication and authentication, obtain EAS IP address from EES, provide edge computing enabling capabilities to AC, etc.
  • EEC can discover services through EAS, and use EAS The IP address is returned to the AC.
  • ECS is mainly responsible for the configuration of EDN.
  • the ECS may provide information of the EES to the terminal.
  • the ECS may also interact with the DNS of the application to obtain EAS information, and directly provide the EAS information to the terminal.
  • ECS may also obtain and store EAS and IP address information from other functional entities.
  • a terminal may also be referred to as terminal equipment, user equipment (UE), mobile station, mobile terminal, and the like.
  • Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things ( internet of things, IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc.
  • Terminals can be mobile phones, tablet computers, computers with wireless transceiver functions, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc.
  • the embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal.
  • Application context may refer to running state information related to one or a group of users, such as game progress, historical data of ML, etc.
  • the application context may further include the context of the subscription of the one or more users in the EAS and the core network, such as the transaction identifier of the subscription and the like.
  • the application context may further include the context of the one or more users on the EES, for example, the transaction identifier of the EAS's subscription to the one or more users.
  • EEC context EEC context
  • the EEC context may refer to user-related data stored in the EES.
  • the EEC context may include EEC side information and EAS-EES subscription information.
  • the EEC side information may include EEC registration information, EEC subscription information (for example, EAS discovery subscription, EAS dynamic information subscription, etc.);
  • EAS-EES subscription information may include UE location API, application context relocation event, AC information open API, UE identification API, and QoS session API, etc.
  • Application context migration may also be referred to as application context relocation, and no distinction is made in this application.
  • the EAS currently providing services may not be able to continue to provide services for the currently running application, or the EAS currently providing services may no longer be able to provide services for the terminal.
  • the optimal EAS, other EAS may be more suitable for serving the terminal, at this time, a new EAS can be selected to provide services for the terminal.
  • the application service may be temporarily suspended or interrupted, which affects the transmission of the application service.
  • source EAS source EAS
  • target EAS target EAS
  • the application context migration process can be divided into the following four stages.
  • the target event can be detected by the detection entity.
  • the target event may include terminal location change, terminal user plane path update, and the like.
  • the need for context transfer is determined by the decision-making entity.
  • the context of the application is transferred from the source EAS to the target EAS by the executing entity. Further, including the discovery of the target EAS, the relevant information of the target EAS can also be notified to the terminal, and the EAS (which can be the source EAS and the target EAS) can be notified to initiate application context transmission, and the EES or EAS executes the application function (application function, AF) traffic impact (AF traffic influence) and carry N6 routing information of T-EAS
  • the EAS notifies the EEC of the application context transmission result through the EES, and the AC initiates a new socket connection to the target EAS.
  • Figure 2 is an implementation of application context migration.
  • ACR is initiated by the EEC, and a conventional EAS discovery process is adopted.
  • step 201 the EEC detects the target event and decides to trigger application context migration.
  • the target event may include UE location change, UE user plane path update, and the like.
  • the EEC detects a UE location update.
  • Step 202 the EEC executes a service provisioning process (service provisioning) process to discover the T-EES.
  • service provisioning service provisioning
  • Step 202 will be described in detail below with reference to FIG. 3 .
  • step 203 the EEC performs a regular EAS discovery (regular EAS) process to discover one or more EASs.
  • regular EAS regular EAS
  • Step 202 will be described in detail below with reference to FIG. 4 .
  • step 204 the AC selects a T-EAS from one or more EASs discovered by the EEC.
  • Step 205 the EEC sends an application context relocation request message (application context relocation request) to the S-EES.
  • Step 206 the S-EES sends an application context relocation response message (application context relocation response) to the EEC.
  • Step 207 the application context is transmitted between the S-EAS and the T-EAS.
  • the EEC performs detection, decision-making, and determination of T-EES and T-EAS, the EEC requests the S-EES to initiate user plane path modification, and the EEC or AC initiates application context transmission.
  • FIG. 3 is a schematic diagram of a service provisioning process.
  • the ECS configures the available edge computing service information related to the EEC according to the UE location, service requirements, service preferences, and connectivity, so that the EEC can discover the available EES.
  • Step 301 the EEC sends a service provisioning (service provisioning) request message to the ECS.
  • the service activation request message may include an EEC ID (identifier), a security credential, an AC profile (AC profile), a UE identity, connection information, and a UE location.
  • EEC ID identifier
  • security credential identifier
  • AC profile AC profile
  • Table 1 shows the information elements that the service provisioning request message may include.
  • Step 303 the ECS sends a service provisioning response message to the EEC.
  • the ECS shall reject the service provisioning request of the EEC and give the reason for the failure.
  • the ECS may provide EDN connection information, a list of EESs that satisfy the EEC request information, and address identification information of the EES.
  • Table 2 shows the information elements that the service provisioning response message may include.
  • FIG. 4 is a schematic diagram of a conventional EAS discovery process.
  • Step 401 the EEC sends an EAS discovery request message to the EES.
  • the EAS discovery request message may include the EEC ID and security credentials.
  • the EAS discovery request message may also include an EAS discovery filter in order to retrieve information about a specific EAS or a specific class of EAS (eg a gaming application).
  • Table 3 shows the information elements that the EAS discovery request message may include.
  • Step 402 after receiving the EAS discovery request sent by the EEC, the EES performs authorization verification and determines one or more EASs.
  • Figure 5 is another implementation of application context migration.
  • ACR is performed by the EEC through the S-EES.
  • step 501 the EEC detects a target event.
  • Step 502 the EEC decides to trigger application context migration.
  • Step 504 the EEC sends an application context migration request to the S-EES.
  • Step 507 After the application context transmission is completed, the S-EAS sends an application context migration complete message to the S-EES, indicating that the T-EES application context transmission is completed, and indicates the application context transmission result.
  • Step 508 After receiving the application context migration complete message sent from the S-EAS, the S-EES sends an application context migration complete message to the EEC, indicating that the EEC application context transfer is completed.
  • Figure 6 is another implementation of application context migration.
  • ACR is performed by the EEC through the T-EES.
  • step 601 the EEC detects a target event.
  • Step 602 the EEC decides to trigger application context migration.
  • Step 603 the EEC determines the T-EAS.
  • Step 605 the T-EES instructs the T-EAS to request an application context from the S-EAS, and the application context is transmitted between the S-EAS and the T-EAS.
  • Step 606 after the application context transmission is completed, the T-EAS sends an application context migration complete message to the T-EES, indicating that the T-EES application context transmission is completed, and indicates the application context transmission result.
  • Step 701 the S-EAS detects the target event, or the S-EES detects the target event and notifies the S-EAS.
  • the target event may include UE location change, UE user plane path update, and the like.
  • Step 702 the S-EAS determines to initiate application context migration.
  • Step 704 the S-EAS notifies the target side information.
  • Step 706 After the application context is transmitted, each entity performs a cleanup process.
  • S-EAS or S-EES performs detection, S-EAS makes decisions, determines T-EES and T-EAS, S-EAS initiates user plane path modification, and S-EAS initiates user plane path modification.
  • S-EAS initiates the transfer of the application context.
  • Figure 8 is another implementation of application context migration.
  • ACR is performed by the S-EES.
  • Step 802 the EEC or the S-EAS notifies the S-EES that the target event is detected.
  • This step is optional. If the target event is detected by the EEC or the S-EAS, the EEC or the S-EAS needs to notify the S-EES that the target event is detected.
  • Step 803 the S-EES determines to initiate application context migration.
  • Step 805 the S-EES notifies the target side information.
  • Step 806 the S-EES notifies the S-EAS to perform context migration.
  • Step 807 the application context is transmitted between the S-EAS and the T-EAS.
  • Step 808 after the application context transmission is completed, the T-EAS sends an application context migration complete message to the T-EES, indicating that the T-EES application context transmission is completed, and indicates the application context transmission result.
  • the detection is performed by EEC, S-EAS or S-EES
  • the S-EES makes decisions, determines T-EES and T-EAS, and the S-EES initiates the modification of the user plane path.
  • the S-EAS is notified by the S-EES to initiate the transfer of the application context.
  • Figure 9 is another implementation of application context migration.
  • the ACR method shown in FIG. 9 is automatic ACR.
  • Step 901 an automatic ACR is initiated by the S-EAS or the S-EES.
  • Step 902 EEC, S-EAS or S-EES detects a target event.
  • This step is optional. If the target event is detected by the EEC or the S-EAS, the EEC or the S-EAS needs to notify the S-EES that the target event is detected.
  • Step 904 the S-EES determines to initiate application context migration.
  • Step 905 the S-EES determines the T-EAS.
  • Step 907 the S-EES notifies the S-EAS to perform context migration.
  • Step 908 the S-EES executes the application traffic influencing process.
  • Step 910 after the application context transmission is completed, the T-EAS sends an application context migration complete message to the T-EES, indicating that the T-EES application context transmission is completed, and indicates the application context transmission result.
  • the detection is performed by EEC, S-EAS or S-EES
  • the S-EES makes decisions, determines T-EES and T-EAS, and the S-EES initiates the modification of the user plane path.
  • the S-EAS is notified by the S-EES to initiate the transfer of the application context.
  • the context migration of the application can be implemented.
  • the EEC context also needs to be migrated, so as to synchronize the registration data and subscription data of the terminal, and the subscription information of the EAS corresponding to the AC on the terminal.
  • application context migration and EEC context migration are not coordinated in the application context migration process.
  • Application context migration and EEC context migration are independent processes. This may cause the application context migration and EEC context to be out of synchronization, which may cause application context migration.
  • FIG. 10 is a schematic flowchart of a method for transmitting context provided by the present application.
  • the method shown in Figure 10 can be performed by EEC, S-EAS, S-EES, T-EAS and T-EES, or by modules in EEC, S-EAS, S-EES, T-EAS and T-EES or unit execution.
  • EEC EEC
  • S-EAS S-EES
  • T-EAS T-EAS
  • T-EES T-EAS
  • T-EES T-EAS
  • T-EES T-EAS
  • the method shown in FIG. 10 may include at least part of the following.
  • Step 1001 the EEC context is transmitted between the S-EES and the T-EES, and the application context is transmitted between the S-EAS and the T-EAS.
  • the transmission of EEC context and application context is initiated by the S-EES.
  • the S-EES determines the T-EES and the T-EAS associated with the T-EES; the S-EES transmits the EEC context to the T-EES; the S-EES indicates that the S-EAS associated with the S-EES sends the T-EAS Application context, or the S-EES sends the application context obtained from the S-EAS to the T-EES.
  • the transfer of EEC context and application context is initiated by the T-EES.
  • the T-EES determines the S-EES and the S-EAS associated with the S-EES; the T-EES requests the S-EES for an EEC context; the T-EES instructs the T-EAS to request an application context from the S-EAS, or, the T-EES - EES requests application context from S-EES.
  • This application does not limit the decision node that initiates application context migration.
  • it may be the EEC in Figure 2, Figure 5, and Figure 6, or the S-EES or S-EAS in Figure 7 and Figure 9, or the EEC in Figure 7 and Figure 9.
  • the S-EES may initiate the transmission of the EEC context and the application context after detecting the target event and determining to initiate the ACR.
  • the S-EES or the T-EES may initiate the transmission of the EEC context and the application context after receiving the sixth information sent by the EEC, where the sixth information is used to indicate initiating the transmission of the application context and the EEC context.
  • the present application does not limit the manner in which the EES (eg, the above-mentioned S-EES or T-EES) determines the T-EES and T-EAS.
  • S-EES can determine T-EES and T-EAS through the discovery target EAS (discovery target EAS) process.
  • the S-EAS sends an EAS discovery request message to the S-EES, the S-EES requests the ECS to acquire the T-EES, and the S-EES discovers the T-EAS through the T-EES.
  • the T-EES and T-EAS may be indicated to the EES after being discovered and selected by other devices.
  • the EEC may directly send the above-mentioned indication information to the S-EES, or the EEC may send the above-mentioned indication information to the S-EES through the S-EES and the T-EES.
  • Step 1003 the first device sends the first information to the T-EAS.
  • the first information is used by the T-EAS to subscribe the EES capability opening information to the T-EES.
  • the EES capability opening information includes at least one of the following information: UE location API, application context relocation event, AC information opening API, UE identification API, and QoS session API.
  • the first information may directly or indirectly instruct the T-EAS to subscribe the EES capability opening information to the T-EES.
  • the first information includes EEC context transmission failure notification information, where the EEC context transmission failure notification information is used to notify the T-EAS that the EEC context transmission fails.
  • the first information includes first indication information, where the first indication information is used to instruct the T-EAS to subscribe the EES capability opening information to the T-EES.
  • the first information includes EEC context transmission failure notification information and application context transmission success notification information, where the EEC context transmission failure notification information is used to notify the EEC that the EEC context transmission fails, and the application context transmission success notification information is used to notify the EEC of the application context. The transfer was successful.
  • the first information may also indicate a service to be subscribed to.
  • Step 1004 after receiving the first information of the first device, the T-EAS may subscribe the above-mentioned EES capability opening information to the T-EES.
  • the T-EAS may determine the service that needs to be subscribed according to the service that needs to be subscribed indicated by the first information and/or according to the application business requirement, and subscribe the service to the T-EES.
  • the first device may be EEC, S-EES or T-EES.
  • the first device may also send second information to the EEC, where the second information is used for the EEC to initiate registration with the T-EES, and the EEC After receiving the second information, the registration may be initiated to the T-EES according to the second information. If the first device is an EEC, the first device may also initiate registration with the T-EES.
  • the second information may directly or indirectly instruct the EEC to initiate registration with the T-EES.
  • the second information includes EEC context transmission failure notification information, where the EEC context transmission failure notification information is used to notify the EEC that the EEC context transmission fails.
  • the second information includes EEC context transmission failure notification information and application context transmission success notification information, the EEC context transmission failure notification information is used to notify the EEC that the EEC context transmission fails, and the application context transmission success notification information is used to notify the EEC of the application context. The transfer was successful.
  • the second information includes second indication information, where the second indication information is used to instruct the EEC to initiate registration with the T-EES.
  • the first device may also send third information to the EEC, where the third information is used by the EEC to subscribe the required service to the T-EES , after receiving the third information, the EEC can subscribe the required service to the T-EES according to the third information.
  • the first device may also subscribe to the required service from the T-EES.
  • the EEC may subscribe to the T-EES for EAS discovery or EAS information related services, or Edge-1 (ie, between EEC-EES) subscribes for information, such as EAS availability change, EAS dynamic information change, and so on.
  • the third information may directly or indirectly instruct the EEC to subscribe the T-EES to the service of EAS discovery and/or EAS information.
  • the third information includes EEC context transmission failure notification information, and the EEC context transmission failure notification information is used to notify the EEC that the EEC context transmission fails.
  • the third information includes EEC context transmission failure notification information and application context transmission success notification information, the EEC context transmission failure notification information is used to notify the EEC of the EEC context transmission failure, and the application context transmission successful notification information is used to notify the EEC of the application context. The transfer was successful.
  • the third information includes third indication information, where the third indication information is used to instruct the EEC to subscribe the T-EES to the service of EAS discovery and/or EAS information.
  • the EEC context transmitted to the T-EES is meaningless due to the need to re-selection the EES. Therefore, for case 2, steps 1005-1006 may be performed.
  • the first device when the first device is EEC or S-EES, the first device may instruct the T-EES to delete the EEC context.
  • the T-EES may delete the EEC context.
  • Step 1007 the first device instructs the S-EAS to retransmit the application context to the T-EAS, or the first device instructs the T-EAS to request the S-EAS to retransmit the application context.
  • the first device may directly instruct the S-EAS to retransmit the application context to the T-EAS; it may also indirectly instruct the S-EAS to retransmit the application context to the T-EAS through other devices. For example, the first device may instruct the T-EAS to retransmit the application context.
  • the S-EAS is requested to retransmit the application context, and the T-EAS requests the S-EAS to retransmit the application context, thereby instructing the S-EAS to retransmit the application context to the T-EAS.
  • the EEC can send the above-mentioned indication information to the S-EAS through the S-EES, or the EEC can send the above-mentioned indication information to the S-EAS through the S-EES, T-EES, and T-EAS.
  • the S-EES can directly send the above-mentioned indication information to the S-EAS, or the S-EES can send the above-mentioned indication information to the S-EAS through T-EES and T-EAS.
  • the S-EES may also acquire the application context from the S-EAS, and retransmit the application context to the T-EAS through the T-EES.
  • Step 1007 the first device determines that the application context relocation is successful.
  • the first device may be EEC, S-EES or T-EES.
  • the first device may also send indication information to the EEC to indicate that the application context relocation is successful.
  • step 1010 may be performed.
  • Step 1007 the first device determines that the application context relocation fails.
  • the first device may be EEC, S-EES or T-EES.
  • the present application does not specifically limit the manner in which the first device determines the transmission result of the application context and the EEC context.
  • the S-EES may determine the transmission result of the EEC context according to the feedback of the T-EES, and the S-EES may determine the transmission result of the EEC context according to the feedback of the S-EAS or the feedback of the T-EES.
  • the transfer result of the application context may be determined.
  • the T-EES determines the EEC context Transmission failed.
  • the EEC receives fifth information from the S-EES or the T-EES, where the fifth information is used to indicate a transmission result of the EEC context; the EEC determines the EEC according to the fifth information Context transfer result.
  • the transfer of the application context and the EEC context can be completed at the same time when the migration of the application context is initiated, which helps to reduce the duration of application service suspension or interruption during the switching of the edge application server. Improve the continuity of application service transmission.
  • Step 1101 the AC is connected to the S-EAS, and the application runs on the S-EAS.
  • Step 1102 after the S-EES or the S-EAS detects the target event, the S-EAS determines to trigger the ACR process to relocate the application context.
  • Step 1103 the S-EAS executes the discovery target EAS (discovery target EAS) process through the S-EES and the ECS, the S-EES discovers the T-EES through the ECS, and the T-EES sends the discovered T-EES to the S-EAS through the S-EES.
  • EAS configuration file the S-EAS
  • a possible implementation is that the S-EES sends the T-EES and T-EAS information to the EEC by sending a target information notification (target information notification) message to the EEC. At this time, the EEC can obtain the discovered T-EES and T-EAS.
  • target information notification target information notification
  • Step 1105 the S-EES sends an application context relocation notification (application context relocation notify) to the S-EAS to notify the S-EAS to start the transmission of the application context.
  • application context relocation notify application context relocation notify
  • the S-EES sends the EEC context to the T-EES, and the S-EAS sends the application context to the T-EAS.
  • the S-EES obtains the application context from the S-EAS, and sends the EEC context and the obtained application context to the T-EES.
  • the T-EES sends the application context to the T-EAS.
  • This step is optional.
  • a possible implementation is that the S-EAS sends an application context transfer complete (application context transfer complete) message to the S-EES, and the application context transfer complete message may carry the transfer result. If the transmission result indicates that the transmission fails, the application context transmission completion message may also carry the reason for the failure. As an example, Table 7 shows the information elements that the application context transfer complete message may include.
  • Step 1108 the S-EES determines the transmission result of the application context and the EEC context.
  • the S-EES may determine the transmission result of the EEC context according to the feedback of the T-EES.
  • the S-EES can determine the transmission result of the application context according to the feedback of the S-EAS.
  • the feedback of the S-EAS may refer to the application context transmission completion message sent by the S-EAS to the S-EES in step 1107 .
  • the feedback from the T-EES may refer to an EEC context transfer complete (EEC context transfer complete) message sent by the T-EES to the S-EES.
  • EEC context transfer complete EEC context transfer complete
  • Table 8 shows the information elements that the EEC context transfer complete message may include.
  • EEC context transfer complete Incates that the EEC context transfer is complete result optional Indicates the result of the EEC context transfer reason optional Indicates the reason why the EEC context transfer failed Application context transfer complete optional Indicates that the application context transfer is complete result optional Indicates the result of the application context transfer reason optional Indicates the reason for the application context transfer failure
  • the subsequent process can be in the following situations.
  • Step 1109 the S-EES retransmits the EEC context to the T-EES, or it is called as the S-EES initiates retransmission of the EEC context to the T-EES.
  • Step 1110 the S-EES instructs the T-EAS to subscribe the required service to the T-EES.
  • This application does not specifically limit the manner in which the S-EES indicates the T-EAS.
  • the S-EES may instruct the T-EAS to subscribe the desired service to the T-EES through the T-EES.
  • the above-mentioned indication sent by the S-EES is transparently transmitted or forwarded by the T-EES to the T-EAS.
  • the required services mentioned here may be the services in the EES capability opening information described above.
  • the T-EAS After the T-EAS receives the instruction of the S-EES, it can subscribe the required service to the T-EES.
  • Step 1111 the S-EES instructs the EEC to register with the T-EES. This step is optional.
  • the EEC may initiate a registration with the T-EES after receiving the indication from the S-EES.
  • step 1112 may be performed.
  • Step 1112 the S-EES instructs the T-EES to delete the EEC context.
  • the T-EES deletes the EEC context after receiving the instruction from the S-EES.
  • step 1116 may also be performed.
  • Step 1116 the S-EES instructs the EEC to subscribe the required service to the T-EES.
  • the S-EES instructs the EEC to subscribe the required service to the T-EES.
  • the EEC may subscribe to EAS discovery or EAS information related services, or Edge-1 (ie, between EEC and EES) subscribes information, such as EAS availability change, EAS dynamic information change, and the like.
  • Edge-1 ie, between EEC and EES subscribes information, such as EAS availability change, EAS dynamic information change, and the like.
  • the EEC may subscribe to the required service from the T-EES after receiving the instruction from the S-EES.
  • step 1113 may be performed.
  • Step 1113 the S-EES instructs the S-EAS to retransmit the application context to the T-EAS.
  • steps 1114-1115 may be performed.
  • Step 1114 the S-EES sends an application context relocation complete (application context relocation complete) message to the EEC, which is used to indicate the result of the application context relocation to the EEC.
  • application context relocation complete application context relocation complete
  • the application context relocation complete message may indicate that the application context relocation was successful.
  • the application context relocation complete message may indicate that the application context relocation fails, and optionally, may carry the failure reason.
  • Step 1115 after receiving the application context relocation complete message, the EEC determines the application context relocation result. If the application context relocation complete message can indicate that the application context relocation is successful, the EEC determines that the application context relocation is successful. If the application context relocation complete message can indicate that the application context relocation failed, the EEC determines that the application context relocation failed.
  • the S-EES initiates and coordinates the transmission of the application context and the EEC context, specifically, the S-EES detects or receives the transmission result of the EEC context and the application context.
  • both contexts are successfully transmitted or both fail, send an indication of ACR success or failure to EEC;
  • EEC context transmission fails and application context transmission is successful S-EES initiates EEC context retransmission or instructs T-EAS according to the failure reason Re-subscribe the required service to the T-EES;
  • the ACT fails, the reason for the failure is that the T-EES does not meet the application requirements, and the T-EES needs to be re-selected, and the S-EES instructs the T-EES to delete the EEC context; otherwise, perform ACT retransmission.
  • FIG. 12 is another example of a method for transmitting context provided by the present application.
  • the AC is connected to the source EAS (S-EAS)
  • the EEC detects the target event and triggers the ACR
  • the T-EES determines the subsequent process according to the transmission result of the application context and the transmission result of the EEC context.
  • Step 1201 the AC is connected to the S-EAS, and the application runs on the S-EAS.
  • Step 1202 after detecting the target event, the EEC determines to trigger the ACR process, and performs context relocation on the application.
  • Step 1204 the EEC sends an application context relocation request message to the T-EES.
  • the application context relocation request message may include an application context transfer indication for indicating whether to transfer the application context and whether to transfer the EEC context.
  • Table 10 shows the information elements that the application context relocation request message may include.
  • Step 1205 the T-EES performs application context and EEC context transmission.
  • the T-EES requests the T-EES to send the EEC context to the T-EES
  • the S-EES sends the EEC context to the T-EES
  • the T-EAS requests the S-EAS for the application context
  • the S-EAS sends the application context to the T-EAS .
  • Step 1206 after detecting that the application context transmission is completed, the T-EAS notifies the T-EES that the application context transmission is completed, and sends the transmission result to the T-EES.
  • This step is optional.
  • a possible implementation is that the T-EAS sends an application context transfer complete (application context transfer complete) message to the T-EES, and the application context transfer complete message may carry the transfer result. If the transmission result indicates that the transmission fails, the application context transmission completion message may also carry the reason for the failure.
  • the information elements that the application context transfer complete message may include may be as shown in Table 7 above.
  • Step 1207 the T-EES determines the transmission result of the application context and the EEC context.
  • the T-EES may determine the transmission result of the EEC context according to whether the EEC context is received.
  • the T-EES can determine the transmission result of the application context according to the feedback from the T-EAS.
  • the feedback from the S-EAS may refer to the application context transmission completion message sent by the T-EAS to the T-EES in step 1206 .
  • the subsequent process can be in the following situations.
  • Step 1208 the T-EES requests the S-EES to retransmit the EEC context.
  • Step 1209 the T-EES instructs the T-EAS to subscribe the required service to the T-EES.
  • the required services mentioned here may be the services in the EES capability opening information described above.
  • the T-EAS After the T-EAS receives the instruction of the T-EES, it can subscribe to the required service from the T-EES.
  • Step 1210 the T-EES instructs the EEC to register with the T-EES. This step is optional.
  • the EEC may initiate registration with the T-EES after receiving the indication from the T-EES.
  • step 1215 may also be performed.
  • Step 1215 the T-EES instructs the EEC to subscribe the required service to the T-EES.
  • the T-EES instructs the EEC to subscribe the required service to the T-EES.
  • the EEC may subscribe to the T-EES for EAS discovery or EAS information related services, or Edge-1 (ie, between EEC-EES) subscribes for information, such as EAS availability change, EAS dynamic information change, and so on.
  • Edge-1 ie, between EEC-EES subscribes for information, such as EAS availability change, EAS dynamic information change, and so on.
  • the EEC may subscribe to the required service from the T-EES after receiving the instruction from the S-EES.
  • step 1211 may be performed.
  • Step 1211 the T-EES deletes the EEC context.
  • step 1212 may be performed.
  • Step 1212 the T-EES instructs the S-EAS to retransmit the application context to the T-EAS, or the T-EES initiates the application context retransmission to the S-EES.
  • This application does not specifically limit the manner in which the T-EES indicates the S-EAS.
  • the T-EES may instruct the S-EAS to retransmit the application context to the T-EAS through the S-EES.
  • the above-mentioned instruction sent by the T-EES is transparently transmitted or forwarded by the S-EES to the S-EAS.
  • the T-EES may indicate to the S-EES that the S-EAS needs to initiate the retransmission of the application context, and further, the S-EES instructs the S-EAS to initiate the retransmission of the application context to the T-EAS.
  • steps 1213-1214 may be performed.
  • the application context relocation complete message may indicate that the application context relocation was successful.
  • the application context relocation complete message may indicate that the application context relocation fails, and optionally, may carry the failure reason.
  • Step 1214 after receiving the application context relocation complete message, the EEC determines the application context relocation result. If the application context relocation complete message can indicate that the application context relocation is successful, the EEC determines that the application context relocation is successful. If the application context relocation complete message can indicate that the application context relocation failed, the EEC determines that the application context relocation failed.
  • the T-EES initiates and coordinates the transmission of the application context and the EEC context. Specifically, the T-EES detects or receives the EEC context and the application context transmission result, and after the context transmission fails, the T-EES fails to initiate the transmission. This ensures that when the application context is relocated, both the application context and the EEC context are migrated to the target side, and when a failure occurs, it can avoid re-executing the entire ACR process or EEC context relocation process, which helps to avoid application context. The problem of large service interruption and delay.
  • FIG. 13 is another example of a method for transmitting context provided by the present application.
  • the AC is connected to the source EAS (S-EAS), the EEC detects the target event and triggers the ACR, and the EEC determines the subsequent process according to the transmission result of the application context and the transmission result of the EEC context.
  • S-EAS source EAS
  • the EEC detects the target event and triggers the ACR
  • the EEC determines the subsequent process according to the transmission result of the application context and the transmission result of the EEC context.
  • Step 1301 the AC is connected to the S-EAS, and the application runs on the S-EAS.
  • step 1302 after detecting the target event, the EEC determines to trigger the ACR process to relocate the application context.
  • Step 1303 the EEC executes the service provisioning process and the EAS discovery process, and determines or discovers the T-EES and the T-EAS.
  • Step 1304 the EEC sends an application context relocation request message to the T-EES.
  • Step 1305 the T-EES performs application context and EEC context transmission.
  • Steps 1301-1305 and steps 1201-1205 may be referred to or referred to each other, and are not repeated here.
  • Step 1306 after detecting that the application context transmission is completed, the S-EAS notifies the S-EES that the application context transmission is completed, and sends the transmission result to the S-EES.
  • This step is optional.
  • the S-EAS sends an application context transmission complete message to the S-EES, and the application context transmission complete message may carry the transmission result. If the transmission result indicates that the transmission fails, the application context transmission completion message may also carry the reason for the failure.
  • the information elements that the application context transmission complete message may include may be as shown in Table 7.
  • Step 1307 the S-EES determines the transmission result of the application context and the EEC context.
  • Step 1307 and step 1108 may be referred to or referred to each other, and are not repeated here.
  • Step 1308, the S-EES indicates to the EEC the transmission result of the application context and the transmission result of the EEC context.
  • a possible implementation is for the S-EES to send an application context relocation complete message.
  • Table 11 shows the information elements that the application context relocation complete message may include.
  • EEC context transfer complete optional Indicates that the EEC context transfer is complete result optional Indicates the result of the EEC context transfer reason optional Indicates the reason for the failure of the EEC context transfer
  • Application context transfer complete optional Indicates that the application context transfer is complete result optional Indicates the result of the application context transfer reason optional Indicates the reason for the application context transfer failure
  • the EEC When the EEC receives the application context relocation complete message, it detects whether the EEC context and the application context are successfully transmitted. According to the transmission result of the application context and the EEC context, the subsequent process can be in the following situations.
  • Step 1309 the EEC instructs the S-EES to retransmit the EEC context to the T-EES.
  • Step 1310 the EEC instructs the T-EAS to subscribe the required service to the T-EES.
  • the required services mentioned here may be the services in the EES capability opening information described above.
  • This application does not specifically limit the manner in which the EEC indicates the T-EAS.
  • the EEC may send the above indication to the T-EAS through the S-EES and the T-EES.
  • the EEC may instruct the T-EAS through the T-EES to subscribe the desired service to the T-EES.
  • the above-mentioned indication sent by the EEC is forwarded or transparently transmitted by the T-EES to the T-EAS.
  • the EEC may indicate to the T-EES that the T-EAS needs to subscribe the required service to the T-EES, and further instruct the T-EAS to subscribe the required service to the T-EES by the T-EES.
  • Step 1311 the EEC initiates registration with the T-EES. This step is optional.
  • the T-EAS After the T-EAS receives the EEC's instruction, it can subscribe the required service to the T-EES.
  • step 1315 may also be performed.
  • Step 1315 the EEC subscribes the required service to the T-EES.
  • the EEC may subscribe to the T-EES for EAS discovery or EAS information related services, or Edge-1 (ie, between EEC-EES) subscribes for information, such as EAS availability change, EAS dynamic information change, and so on.
  • Edge-1 ie, between EEC-EES subscribes for information, such as EAS availability change, EAS dynamic information change, and so on.
  • step 1312 may be performed.
  • Step 1112 the EEC instructs the T-EES to delete the EEC context.
  • the EEC may send the above indication to the T-EES through the S-EES.
  • the T-EES deletes the EEC context after receiving the EEC's indication.
  • step 1313 may be performed.
  • Step 1313 the EEC instructs the S-EAS to retransmit the application context to the T-EAS.
  • the EEC may send the above indication to the S-EAS through the S-EES.
  • step 1314 may be performed.
  • step 1314 the EEC determines the result of the application context relocation.
  • the EEC determines that the application context relocation is successful.
  • the EEC instructs the S-EES to initiate the application context transfer and/or the EEC context transfer
  • the S-EES receives and applies the context transfer result and the EEC context transfer result, and sends the transfer result to the EEC
  • the EEC transmits according to the two
  • the context retransmission or EEC context deletion is initiated, or the EAS re-subscribes the required services to the EES, so as to ensure that during the application context relocation process, both the application context and the EEC context are migrated to the target side, and when the context transmission fails, avoid Execute the full ACR process or EEC context relocation process.
  • the communication apparatus includes corresponding hardware structures and/or software modules for performing each function.
  • the units and method steps of each example described in conjunction with the embodiments disclosed in the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed by hardware or computer software-driven hardware depends on the specific application scenarios and design constraints of the technical solution.
  • FIG. 14 and FIG. 15 are schematic structural diagrams of possible communication apparatuses provided by embodiments of the present application. These communication apparatuses can be used to implement the functions of the first apparatus or the target EAS in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.
  • the communication device may be EEC112, EAS131 or EES132 as shown in FIG. 1, and may also be a module (such as a chip) applied to EEC112, EAS131 or EES132.
  • the communication apparatus 1400 includes a processing unit 1410 and a transceiver unit 1420 .
  • the transceiver unit 1420 is configured to send first information to the first EAS corresponding to the first EES when the EEC context fails to migrate from the second EES to the first EES, where the first information uses Subscribing EES capability opening information to the first EAS with the first EES.
  • the first information includes EEC context transmission failure notification information or first indication information, and the EEC context transmission failure notification information is used to notify the first EAS that the EEC context transmission fails, and the first indication The information is used to instruct the first EAS to subscribe the EES capability opening information to the first EES.
  • the first information includes EEC context transmission failure notification information and application context transmission success notification information
  • the EEC context transmission failure notification information is used to notify the EEC that the EEC context transmission fails
  • the application context transmission success notification information is used to notify the EEC of the application. Context transfer succeeded.
  • the EES capability opening information includes at least one of the following information: UE location API, application context relocation event, AC information opening API, UE identification API, and QoS session API.
  • the device is the first EES or the second EES.
  • the transceiver unit 1420 is further configured to send second information to the EEC, where the second information is used to instruct the EEC to initiate registration with the first EES.
  • the second information may directly or indirectly instruct the EEC to initiate registration with the first EES.
  • the second information includes EEC context transmission failure notification information, and the EEC context transmission failure notification information is used to notify the EEC that the EEC context transmission fails.
  • the second information includes EEC context transmission failure notification information and application context transmission success notification information, the EEC context transmission failure notification information is used to notify the EEC that the EEC context transmission fails, and the application context transmission success notification information is used to notify the EEC of the application context. The transfer was successful.
  • the second information includes second indication information, where the second indication information is used to instruct the EEC to initiate registration with the first EES.
  • the first device is the first edge-enabled server or the second edge-enabled server; the transceiver unit 1420 is further configured to send third information to the EEC, and the third information uses and instructing the EEC to subscribe the first EES to the service of EAS discovery and/or EAS information.
  • the third information may directly or indirectly instruct the EEC to subscribe the first EES to the service of EAS discovery and/or EAS information.
  • the third information includes EEC context transmission failure notification information, and the EEC context transmission failure notification information is used to notify the EEC that the EEC context transmission fails.
  • the third information includes EEC context transmission failure notification information and application context transmission success notification information, the EEC context transmission failure notification information is used to notify the EEC of the EEC context transmission failure, and the application context transmission successful notification information is used to notify the EEC of the application context. The transfer was successful.
  • the third information includes third indication information, where the third indication information is used to instruct the EEC to subscribe the first EES to the service of EAS discovery and/or EAS information.
  • the apparatus is the second EES
  • the transceiver unit 1420 is further configured to receive fourth information from the first EES, where the fourth information is used to indicate that the EEC context transmission fails.
  • the processing unit 1410 is configured for the first device to determine, according to the fourth information, that the transmission of the EEC context fails.
  • the processing unit 1410 is further configured to determine the first EES and the first EAS when application context migration is triggered.
  • the transceiver unit 1420 is further configured to transmit the EEC context to the first EES.
  • the transceiver unit 1420 is further configured to instruct the second EAS associated with the device to send the application context to the first EAS, or send the application context from the first EAS to the first EAS through the first EES. 2.
  • the apparatus is the first EES
  • the processing unit 1410 is configured to determine that the EEC context transmission fails when the apparatus does not receive the EEC context from the second EES.
  • the processing unit 1410 is further configured to determine the second EES and the second EAS associated with the second EES in the case of triggering application context migration.
  • the transceiver unit 1420 is further configured to request the EEC context from the second EES.
  • the transceiver unit 1420 is further configured to instruct the first EAS to request the application context from the second EAS, or request the application context from the second EAS.
  • the first device is the EEC
  • the transceiver unit 1420 is further configured to initiate registration with the first EES.
  • the transceiver unit 1420 is further configured to receive fifth information from the first EES or the second EES, where the fifth information is used to indicate that the EEC context transmission fails.
  • the processing unit 1410 is configured to determine, according to the fifth information, that the EEC context transmission fails.
  • the transceiving unit 1420 is further configured to send sixth information to the first EES or the second EES in the case of triggering application context migration, where the sixth information is used to indicate that the Application context and transmission of the EEC context.
  • the first device is the EEC; the transceiver unit 1420 is further configured to subscribe to the first EES for services of EAS discovery and/or EAS information.
  • the transceiver unit 1420 is specifically configured to send the first information to the first EAS through the first EES.
  • the transceiver unit 1420 is configured to, when the application context transmission succeeds and the EEC context transmission fails, the first device requests the second EES to retransmit the EEC context to the first device, or the first device A device retransmits the EEC context to the first EES, the EEC context being transmitted by the second EES to the first EES.
  • the transceiver unit 1420 is configured to, when the application context transmission succeeds and the EEC context transmission fails, the first device sends seventh information to the second EES, where the seventh information is used to indicate the second EES retransmitting the EEC context to the first EES, or the first apparatus sends eighth information to the first EES, where the eighth information is used to instruct the first EES to send the second EES A request for retransmission of the EEC context, which was transmitted by the second EES to the first EES.
  • the transceiver unit 1420 is configured to delete the EEC context by the first device when the transmission of the EEC context succeeds, the transmission of the application context fails and the EES needs to be re-selected, or the first device sends ninth information to the first EES, the The ninth information is used to instruct the first EES to delete the EEC context, and the EEC context is transmitted from the second EES to the first EES.
  • the transceiver unit 1420 is configured to send the tenth information to the second EAS by the first device when the EEC context transmission succeeds, the application context transmission fails, and no EES re-selection is required, where the tenth information is used to instruct the second EAS to send the second EAS to the second EAS.
  • An EAS retransmits the application context, or the first device sends eleventh information to the first EAS, where the eleventh information is used to instruct the first EAS to request the second EAS to retransmit the the application context.
  • the first apparatus is a source EES
  • the processing unit 1410 is configured to determine the target EES and a target EAS associated with the target EES in the case of triggering application context migration.
  • the transceiver unit 1420 is further configured to transmit the EEC context to the target EES.
  • the transceiver unit 1420 is further configured to instruct the source EAS associated with the first device to send the application context to the target EAS, or send the application context obtained from the source EAS to the target EAS .
  • the transceiver unit 1420 is further configured to receive fourth information from the target EES, where the fourth information is used to indicate a transmission result of the EEC context.
  • the processing unit 1410 is further configured to determine a transmission result of the EEC context transmission according to the fourth information.
  • the first device is a target EES
  • the processing unit 1410 is further configured to determine a source EES and a source EAS associated with the source EES in the case of triggering application context migration.
  • the transceiver unit 1420 is further configured to request the EEC context from the source EES.
  • the transceiving unit 1420 is further configured to instruct the target EAS to request the application context from the source EAS, or request the application context from the source EAS.
  • the processing unit 1410 is further configured to determine a transmission result of the EEC context according to whether the EEC context from the source EES is received.
  • the first device is an EEC
  • the transceiver unit 1420 is further configured to send sixth information to the source EES or the target EES in the case of triggering application context migration, where the sixth information is used to indicate initiation of the transfer of the application context and the EEC context.
  • the transceiving unit 1420 is further configured to receive fifth information from the source EES or the target EES, where the fifth information is used to indicate a transmission result of the EEC context.
  • the processing unit 1410 is further configured to determine the transmission result of the EEC context according to the fifth information.
  • the transceiver unit 1420 is configured to receive first information from the first device, where the first information is used by the first EAS to subscribe the EES capability opening information to the first EES associated with the first EAS; The first information is subscribed to the first EES for the EES capability opening information.
  • the above-mentioned first apparatus may be a source EES, a target EES or an EEC.
  • the first information includes EEC context transmission failure notification information or first indication information, and the EEC context transmission failure notification information is used to notify the first EAS that the EEC context transmission fails, and the first indication The information is used to instruct the first EAS to subscribe the EES capability opening information to the first EES.
  • the first information includes EEC context transmission failure notification information and application context transmission success notification information
  • the EEC context transmission failure notification information is used to notify the EEC that the EEC context transmission fails
  • the application context transmission success notification information is used to notify the EEC of the application. Context transfer succeeded.
  • the EES capability opening information includes at least one of the following information: UE location API, application context relocation event, AC information opening API, UE identification API, and QoS session API.
  • the transceiver unit 1420 is configured to receive second information from the first device, where the EEC initiates registration with the first EES according to the second information; and initiates registration with the first EES according to the second information.
  • the second information may directly or indirectly instruct the EEC to initiate registration with the first EES.
  • the second information includes EEC context transmission failure notification information, where the EEC context transmission failure notification information is used to notify the EEC that the EEC context transmission fails.
  • the second information includes EEC context transmission failure notification information and application context transmission success notification information, the EEC context transmission failure notification information is used to notify the EEC that the EEC context transmission fails, and the application context transmission success notification information is used to notify the EEC of the application context. The transfer was successful.
  • the second information includes second indication information, where the second indication information is used to instruct the EEC to initiate registration with the first EES.
  • the transceiver unit 1420 is further configured to receive third information from the first device, where the third information is used to instruct the EEC to subscribe to the first EES for EAS discovery and/or EAS information. a service; and a service of subscribing to the first EES for EAS discovery and/or EAS information according to the third information.
  • the third information may directly or indirectly instruct the EEC to subscribe the first EES to the service of EAS discovery and/or EAS information.
  • the third information includes EEC context transmission failure notification information, and the EEC context transmission failure notification information is used to notify the EEC that the EEC context transmission fails.
  • the third information includes EEC context transmission failure notification information and application context transmission success notification information, the EEC context transmission failure notification information is used to notify the EEC of the EEC context transmission failure, and the application context transmission successful notification information is used to notify the EEC of the application context. The transfer was successful.
  • the third information includes third indication information, where the third indication information is used to instruct the EEC to subscribe the first EES to the service of EAS discovery and/or EAS information.
  • the communication device 1500 includes a processor 1510 and an interface circuit 1520 .
  • the processor 1510 and the interface circuit 1520 are coupled to each other.
  • the interface circuit 1520 can be a transceiver or an input-output interface.
  • the communication apparatus 1500 may further include a memory 1530 for storing instructions executed by the processor 1510 or input data required by the processor 1510 to execute the instructions or data generated after the processor 1510 executes the instructions.
  • the processor 1510 is used to implement the function of the above-mentioned processing unit 1410
  • the interface circuit 1520 is used to implement the function of the above-mentioned transceiver unit 1420.
  • the first device chip When the above communication device is a chip applied to the first device, the first device chip implements the function of the first device in the above method embodiment.
  • the first device chip receives information from other modules (such as a radio frequency module or an antenna) in the first device, and the information is sent to the first device by other devices; or, the first device chip sends information to other modules in the first device (such as a radio frequency module or an antenna) to send information that the first device sends to other devices.
  • the chip When the above communication device is a chip applied to the target EAS, the chip implements the function of the target EAS in the above method embodiments.
  • the chip receives information from other modules in the target EAS (such as radio frequency modules or antennas) that other devices send to the target EAS; or, the chip sends information to other modules in the target EAS (such as radio frequency modules or antennas) , which is sent by the target EAS to other devices.
  • processor in the embodiments of the present application may be a central processing unit (central processing unit, CPU), and may also be other general-purpose processors, digital signal processors (digital signal processors, DSP), application-specific integrated circuits (application specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
  • CPU central processing unit
  • DSP digital signal processors
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor may be a microprocessor or any conventional processor.
  • the method steps in the embodiments of the present application may be implemented in a hardware manner, or may be implemented in a manner in which a processor executes software instructions.
  • Software instructions may be composed of corresponding software modules, and software modules may be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory memory, registers, hard disk, removable hard disk, CD-ROM or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor, such that the processor can read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and storage medium may reside in an ASIC. Additionally, the ASIC may reside in the first device or in the target EAS. Of course, the processor and the storage medium may also exist as discrete components in the first device or the target EAS.
  • 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 programs or instructions.
  • the processes or functions described in the embodiments of the present application are executed in whole or in part.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, network equipment, user equipment, or other programmable apparatus.
  • the computer program or instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program or instructions may be downloaded from a website site, computer, A server or data center transmits by wire or wireless to another website site, computer, server or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server, data center, or the like that integrates one or more available media.
  • the usable media may be magnetic media, such as floppy disks, hard disks, magnetic tapes; optical media, such as digital video discs; and semiconductor media, such as solid-state drives.
  • “at least one” means one or more, and “plurality” means two or more.
  • “And/or”, which describes the relationship between the related objects, means that there can be three kinds of relationships, for example, A and/or B, which can mean: 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 related objects are a kind of "or” relationship; in the formula of this application, the character "/” indicates that the related objects are a kind of "division” Relationship.

Landscapes

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

Abstract

本申请提供了一种用于传输上下文的方法和通信装置，该方法包括：当边缘使能客户端上下文由第二边缘使能服务器迁移到第一边缘使能服务器失败时，第一装置向与第一边缘使能服务器对应的第一边缘应用服务器发送第一信息，第一信息用于第一边缘应用服务器向第一边缘使能服务器订阅边缘使能服务器能力开放信息。在上述技术方案中，当边缘使能客户端上下文传输失败，第一装置可以指示目标边缘应用服务器向目标边缘使能服务器订阅边缘使能服务器能力开放信息，可以避免重新执行全部边缘使能客户端上下文迁移流程，有助于降低边缘应用程序服务器切换过程中应用服务挂起或中断的时长，从而提高应用业务的传输的连续性。

Description

一种用于传输上下文的方法和通信装置
本申请要求于2021年04月07日提交中国专利局、申请号为202110374553.3、申请名称为“一种用于传输上下文的方法和通信装置”的中国专利申请，于2021年05月19日提交中国专利局、申请号为202110545128.6、申请名称为“一种用于传输上下文的方法和通信装置”的中国专利申请，以及于2021年07月06日提交中国专利局、申请号为202110763755.7、申请名称为“一种用于传输上下文的方法和通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及一种用于传输上下文的方法和通信装置。
背景技术
在边缘应用运行的过程中，当终端移动到当前的服务区之外，当前提供服务的边缘应用服务器(edge application server，EAS)可能无法继续为当前运行的应用提供服务，或者当前提供服务的边缘应用服务器已经不是可以为该终端提供服务的最优的边缘应用服务器，其他的边缘应用服务器可能更适合为终端服务，此时可以选择新的边缘应用程序服务器为该终端提供服务。然而，在新的边缘应用程序服务器替换当前进行服务的边缘应用程序服务器的过程中会引起应用服务短暂挂起或中断，影响应用业务的传输。
发明内容
本申请提供了一种用于传输上下文的方法和通信装置，有助于降低边缘应用程序服务器切换过程中应用服务挂起或中断的时长，从而提高应用业务的传输的连续性。
第一方面，本申请提供了一种用于传输上下文的方法，所述方法包括：当边缘使能客户端(edge enabler client，EEC)上下文由第二边缘使能服务器(edge enabler server，EES)迁移到第一EES失败时，第一装置向与所述第一EES对应的第一边缘应用服务器EAS发送第一信息，所述第一信息用于所述第一EAS向与所述第一EES订阅EES能力开放信息。
可选地，上述第一装置可以为源EES、目标EES或EEC。
EEC上下文由第二EES传输到第一EES，也可以理解为，第一EES为目标EES，第二EES为源EES。
在上述技术方案中，当EEC上下文传输失败，第一装置可以指示目标EAS向目标EES订阅EES能力开放信息，可以避免重新执行全部EEC上下文迁移流程，有助于降低边缘应用程序服务器切换过程中应用服务挂起或中断的时长，从而提高应用业务的传输的连续性。
结合第一方面，在一种可能的实现方式中，所述第一信息包括EEC上下文传输失败通知信息或第一指示信息，所述EEC上下文传输失败通知信息用于通知所述第一EAS所 述EEC上下文传输失败，所述第一指示信息用于指示所述第一EAS向所述第一EES订阅所述EES能力开放信息。
在一些实现方式中，第一信息包括EEC上下文传输失败通知信息和应用上下文传输成功通知信息，EEC上下文传输失败通知信息用于向EEC通知EEC上下文传输失败，应用上下文传输成功通知信息用于向EEC通知应用上下文传输成功。
在上述技术方案中，第一信息可以通过直接或间接的方式指示第一EAS向第一EES订阅EES能力开放信息。
结合第一方面或其任一种可能的实现方式，在另一种可能的实现方式中，所述EES能力开放信息包括以下信息中的至少一项：用户设备(user equipment，UE)位置应用编程接口(application program interface，API)、应用上下文重定位事件、应用客户端(application client，AC)信息开放API、UE标识API、以及服务质量(quality of service，QoS)会话API。
UE位置API：EES向EAS开放UE位置API，以支持跟踪或检查UE的有效位置。EES公开的UE位置API依赖于3GPP核心网能力。EAS可以请求UE位置API进行一次性报告以检查当前UE位置，并请求连续报告以跟踪UE的位置。UE位置API既支持一次性查询的请求响应(以便检查UE的当前位置)，也支持订阅通知模型，用于连续向EAS提供UE的位置，并使EAS能够跟踪UE的位置(随着UE位置的变化)。
应用上下文迁移事件：EES向EAS开放一个或多个UE的ACR管理事件通知(例如，为了触发ACR)。EES开放的ACR管理事件通知可能依赖于网络开放功能(network exposure function，NEF)北向API来监控用户面路径管理事件。应用上下文迁移事件也可以被替换为应用上下文重定位事件。
AC信息开放API：是指EAS从EES获取AC能力信息。此信息可能有助于EAS和AC之间的通信，例如推送通知。共享的信息受访问控制以及隐私和安全机制的约束。
UE标识API：EES向EAS开放UE标识API，以便提供唯一标识UE的标识符。当EAS没有UE的标识时，EAS使用该API获取UE的标识。此标识符称为边缘UE ID，用于EAS通过EDGE-3调用特定于UE的能力API。
QoS会话API：EES向EAS开放具有QoS的会话API，以支持在AC和EAS之间建立具有特定QoS的数据会话，并修改此数据会话的QoS。
结合第一方面或其任一种可能的实现方式，在另一种可能的实现方式中，所述第一装置为所述第一EES或所述第二EES；所述方法还包括：所述第一装置向EEC发送第二信息，所述第二信息用于所述EEC向所述第一EES发起注册。
可选地，第二信息可以直接或间接的指示EEC向第一EES发起注册。例如，第二信息包括EEC上下文传输失败通知信息，EEC上下文传输失败通知信息用于通知所述EEC所述EEC上下文传输失败。又例如，第二信息包括EEC上下文传输失败通知信息和应用上下文传输成功通知信息，EEC上下文传输失败通知信息用于向EEC通知EEC上下文传输失败，应用上下文传输成功通知信息用于向EEC通知应用上下文传输成功。又例如，第二信息包括第二指示信息，第二指示信息用于指示EEC向第一EES发起注册。
可选地，若第一装置为目标EES，目标EES可以根据自己的实际情况，确定是否指示EEC注册到目标EES。
考虑到一些EES需要EEC注册到该EES才可以使EEC使用边缘应用服务，在上述技术方案中，第一装置指示EEC向第一EES注册，以便使用边缘应用服务。
结合第一方面或其任一种可能的实现方式，在另一种可能的实现方式中，所述第一装置为所述第一EES或所述第二EES；所述方法还包括：所述第一装置向EEC发送第三信息，所述第三信息用于所述EEC向所述第一EES订阅EAS发现和/或EAS信息的服务。也可以理解为EEC订阅Edge-1(即EEC-EES之间)的信息，例如，EAS可用性改变、EAS动态信息改变等。
可选地，第三信息可以直接或间接的指示EEC向第一EES订阅EAS发现和/或EAS信息的服务。例如，第三信息包括EEC上下文传输失败通知信息，EEC上下文传输失败通知信息用于通知所述EEC所述EEC上下文传输失败。又例如，第三信息包括EEC上下文传输失败通知信息和应用上下文传输成功通知信息，EEC上下文传输失败通知信息用于向EEC通知EEC上下文传输失败，应用上下文传输成功通知信息用于向EEC通知应用上下文传输成功。又例如，第三信息包括第三指示信息，第三指示信息用于指示EEC向所述第一EES订阅EAS发现和/或EAS信息的服务。
结合第一方面或其任一种可能的实现方式，在另一种可能的实现方式中，所述第一装置为所述第二EES，所述方法还包括：所述第一装置接收到来自所述第二EES的第四信息，所述第四信息用于指示所述EEC上下文传输失败；所述第一装置根据所述第四信息确定所述EEC上下文传输失败。
结合第一方面或其任一种可能的实现方式，在另一种可能的实现方式中，所述方法还包括：在触发应用上下文迁移的情况下，所述第一装置确定所述第一EES和第一EAS；所述第一装置向所述第一EES传输所述EEC上下文；所述第一装置指示与所述第一装置对应的第二EAS向所述第一EAS发送所述应用上下文，或者，所述第一装置通过所述第一EES向所述第一EAS发送从所述第二EAS获取的所述应用上下文。
在上述技术方案中，由源EES发起并协调应用上下文和EEC上下文的传输，从而可以保证发生应用上下文重定位时，应用上下文和EEC上下文均迁移至目标侧，可以避免应用运行缺少必要的订阅信息，有助于降低边缘应用程序服务器切换过程中应用服务挂起或中断的时长，从而提高应用业务的传输的连续性。
结合第一方面或其任一种可能的实现方式，在另一种可能的实现方式中，所述第一装置为所述EEC；所述方法还包括：所述第一装置向所述第一EES订阅EAS发现和/或EAS信息的服务。也可以理解为EEC订阅Edge-1(即EEC-EES之间)的信息，例如，EAS可用性改变、EAS动态信息改变等。
结合第一方面或其任一种可能的实现方式，在另一种可能的实现方式中，所述第一装置向与所述第一EES对应的第一EAS发送第一信息，包括：所述第一装置通过所述第一EES向所述第一EAS发送所述第一信息。
例如，S-EES发送的上述指示由T-EES透传或转发至T-EAS。
又例如，S-EES可以向T-EES指示T-EAS需要向T-EES订阅所需服务，进一步地由T-EES指示T-EAS向T-EES订阅所需服务。
结合第一方面或其任一种可能的实现方式，在另一种可能的实现方式中，所述第一装置为所述第一EES，所述方法还包括：当所述第一装置未接收来自所述第二EES的所述 EEC上下文时，所述第一装置确定所述EEC上下文传输失败。
结合第一方面或其任一种可能的实现方式，在另一种可能的实现方式中，所述方法还包括：在触发应用上下文迁移的情况下，所述第一装置确定所述第二EES和与所述第二EES对应的第二EAS；所述第一装置向所述第二EES请求所述EEC上下文；所述第一装置指示所述第一EAS向所述第二EAS请求所述应用上下文，或者，所述第一装置向所述第二EES请求所述应用上下文。
在上述技术方案中，由目标EES发起并协调应用上下文和EEC上下文的传输，从而可以保证发生应用上下文重定位时，应用上下文和EEC上下文均迁移至目标侧，可以避免应用运行缺少必要的订阅信息，有助于降低边缘应用程序服务器切换过程中应用服务挂起或中断的时长，从而提高应用业务的传输的连续性。
结合第一方面或其任一种可能的实现方式，在另一种可能的实现方式中，所述第一装置为所述EEC，所述方法还包括：所述第一装置向所述第一EES发起注册。
考虑到一些EES需要EEC注册到该EES才可以使EEC使用边缘应用服务，在上述技术方案中，EEC向第一EES注册，以便使用边缘应用服务。
结合第一方面或其任一种可能的实现方式，在另一种可能的实现方式中，所述方法还包括：所述第一装置接收来自所述第一EES或所述第二EES的第五信息，所述第五信息用于指示所述EEC上下文传输失败；所述第一装置根据所述第五信息，确定所述EEC上下文传输失败。
结合第一方面或其任一种可能的实现方式，在另一种可能的实现方式中，所述方法还包括：在触发应用上下文迁移的情况下，所述第一装置向所述第一EES或所述第二EES发送第六信息，所述第六信息用于指示发起所述应用上下文和所述EEC上下文的传输。
在上述技术方案中，由EEC发起并协调应用上下文和EEC上下文的传输，从而可以保证发生应用上下文重定位时，应用上下文和EEC上下文均迁移至目标侧，可以避免应用运行缺少必要的订阅信息，有助于降低边缘应用程序服务器切换过程中应用服务挂起或中断的时长，从而提高应用业务的传输的连续性。
结合第一方面或其任一种可能的实现方式，在另一种可能的实现方式中，所述第一装置向与所述第一EES对应的第一EAS发送第一信息，包括：所述第一装置通过所述第一EES向所述第一EAS发送所述第一信息。
例如，EEC发送的上述指示由T-EES透传或转发至T-EAS。
又例如，EEC可以向T-EES指示T-EAS需要向T-EES订阅所需服务，进一步地由T-EES指示T-EAS向T-EES订阅所需服务。
第二方面，本申请提供了一种用于传输上下文的方法，所述方法包括：第一EAS接收来第一装置的第一信息，所述第一信息用于所述第一EAS向与所述第一EAS对应的第一EES订阅EES能力开放信息；所述第一EAS根据所述第一信息，向所述第一EES订阅所述EES能力开放信息。
可选地，上述第一装置可以为源EES、目标EES或EEC。
在上述技术方案中，第一EAS可以根据第一装置的指示，向目标EES订阅EES能力开放信息，可以避免重新执行全部EEC上下文迁移流程，有助于降低边缘应用程序服务器切换过程中应用服务挂起或中断的时长，从而提高应用业务的传输的连续性。
结合第二方面，在一种可能的实现方式中，所述第一信息包括EEC上下文传输失败通知信息或第一指示信息，所述EEC上下文传输失败通知信息用于通知所述第一EAS所述EEC上下文传输失败，所述第一指示信息用于指示所述第一EAS向所述第一EES订阅所述EES能力开放信息。
在一些实现方式中，第一信息包括EEC上下文传输失败通知信息和应用上下文传输成功通知信息，EEC上下文传输失败通知信息用于向EEC通知EEC上下文传输失败，应用上下文传输成功通知信息用于向EEC通知应用上下文传输成功。
结合第二方面或其任一种可能的实现方式，在另一种可能的实现方式中，所述EES能力开放信息包括以下信息中的至少一项：UE位置API、应用上下文重定位事件、AC信息开放API、UE标识API、以及QoS会话API。
第三方面，本申请提供了一种用于传输上下文的方法，所述方法包括：当应用上下文传输成功且EEC上下文传输失败时，第一装置请求第二EES向所述第一装置重传所述EEC上下文，或者，所述第一装置向所述第一EES重传所述EEC上下文，所述EEC上下文由第二EES传输到所述第一EES。
在上述技术方案中，当应用上下文传输成功且EEC上下文传输失败，第一装置可以指示源EES向目标EES重传EEC上下文，或者，指示目标EES向源EES请求重传EEC上下文，可以避免重新执行全部EEC上下文迁移流程，有助于降低边缘应用程序服务器切换过程中应用服务挂起或中断的时长，从而提高应用业务的传输的连续性。
第四方面，本申请提供了一种用于传输上下文的方法，所述方法包括：当应用上下文传输成功且EEC上下文传输失败时，第一装置向第二EES发送第七信息，所述第七信息用于指示所述第二EES向所述第一EES重传所述EEC上下文，或者，所述第一装置向所述第一EES发送第八信息，所述第八信息用于指示所述第一EES向所述第二EES请求重传所述EEC上下文，所述EEC上下文由第二EES传输到所述第一EES。
在上述技术方案中，当应用上下文传输成功且EEC上下文传输失败，第一装置可以指示源EES向目标EES重传EEC上下文，或者，指示目标EES向源EES请求重传EEC上下文，可以避免重新执行全部EEC上下文迁移流程，有助于降低边缘应用程序服务器切换过程中应用服务挂起或中断的时长，从而提高应用业务的传输的连续性。
第五方面，本申请提供了一种用于传输上下文的方法，所述方法包括：当EEC上下文传输成功、应用上下文传输失败且需要重选EES时，第一装置删除所述EEC上下文，或者，所述第一装置向第一EES发送第九信息，所述第九信息用于指示所述第一EES删除所述EEC上下文，所述EEC上下文由第二EES传输到所述第一EES。
在上述技术方案中，当EEC上下文传输成功、应用上下文传输失败且需要重选EES时，第一装置可以删除EEC上下文，或者，可以指示目标EES删除EEC上下文，可以避免EES上存储不需要的EEC上下文。
第六方面，本申请提供了一种用于传输上下文的方法，所述方法包括：当EEC上下文传输成功、应用上下文传输失败且无需重选EES时，第一装置向第二EAS发送第十信息，所述第十信息用于指示所述第二EAS向第一EAS重传所述应用上下文，或者，所述第一装置向第一EAS发送第十一信息，所述第十一信息用于指示所述第一EAS向所述第二EAS请求重传所述应用上下文。
也就是说，在此情况下，第一装置确定不删除EEC上下文，并指示源EAS重传应用上下文。
可选地，上述第一装置可以为源EES、目标EES或EEC。
在上述技术方案中，当EEC上下文传输成功、应用上下文传输失败且无需重选EES时，第一装置可以指示源EAS向目标EAS重传应用上下文，或者，指示目标EAS向源EAS请求重传应用上下文，可以避免重新执行全部应用上下文迁移流程，有助于降低边缘应用程序服务器切换过程中应用服务挂起或中断的时长，从而提高应用业务的传输的连续性。
结合第三方面至第六方面，在一种可能的实现方式中，所述第一装置为源EES，所述方法还包括：在触发应用上下文迁移的情况下，所述第一装置确定所述目标EES和与所述目标EES对应的目标EAS；所述第一装置向所述目标EES传输所述EEC上下文；所述第一装置指示与所述第一装置对应的源EAS向所述目标EAS发送所述应用上下文，或者，所述第一装置向所述目标EES发送从所述源EAS获取的所述应用上下文。
结合第三方面至第六方面或其任一种可能的实现方式，在另一种可能的实现方式中，所述方法还包括：所述第一装置接收到来自所述目标EES的第四信息，所述第四信息用于指示所述EEC上下文的传输结果；所述第一装置根据所述第四信息确定所述EEC上下文传输的传输结果。
结合第三方面至第六方面或其任一种可能的实现方式，在另一种可能的实现方式中，所述第一装置为目标EES，所述方法还包括：在触发应用上下文迁移的情况下，所述第一装置确定源EES和与所述源EES对应的源EAS；所述第一装置向所述源EES请求所述EEC上下文；所述第一装置指示所述目标EAS向所述源EAS请求所述应用上下文，或者，所述第一装置向所述源EES请求所述应用上下文。
结合第三方面至第六方面或其任一种可能的实现方式，在另一种可能的实现方式中，所述方法还包括：所述第一装置根据是否接收到来自所述源EES的所述EEC上下文，确定所述EEC上下文的传输结果。
结合第三方面至第六方面或其任一种可能的实现方式，在另一种可能的实现方式中，所述第一装置为EEC，所述方法还包括：在触发应用上下文迁移的情况下，所述第一装置向所述源EES或所述目标EES发送第六信息，所述第六信息用于指示发起所述应用上下文和所述EEC上下文的传输。
结合第三方面至第六方面或其任一种可能的实现方式，在另一种可能的实现方式中，所述方法还包括：所述第一装置接收来自所述源EES或所述目标EES的第五信息，所述第五信息用于指示所述EEC上下文的传输结果；所述第一装置根据所述第五信息，确定所述EEC上下文的传输结果。
第七方面，本申请提供了一种用于传输上下文的方法，所述方法包括：EEC接收来第一装置的第二信息，所述第二信息所述EEC向第一EES发起注册；所述EEC根据所述第二信息，向所述第一EES发起注册。
可选地，第二信息可以直接或间接的指示EEC向第一EES发起注册。例如，第二信息包括EEC上下文传输失败通知信息，EEC上下文传输失败通知信息用于通知所述EEC所述EEC上下文传输失败。又例如，第二信息包括EEC上下文传输失败通知信息和应用 上下文传输成功通知信息，EEC上下文传输失败通知信息用于向EEC通知EEC上下文传输失败，应用上下文传输成功通知信息用于向EEC通知应用上下文传输成功。又例如，第二信息包括第二指示信息，第二指示信息用于指示EEC向第一EES发起注册。
结合第七方面，在一种可能的实现方式中，所述方法还包括：所述EEC接收来自所述第一装置的第三信息，所述第三信息用于指示所述EEC向所述第一EES订阅EAS发现和/或EAS信息的服务；所述EEC根据所述第三信息，向所述第一EES订阅EAS发现和/或EAS信息的服务。
可选地，第三信息可以直接或间接的指示EEC向第一EES订阅EAS发现和/或EAS信息的服务。例如，第三信息包括EEC上下文传输失败通知信息，EEC上下文传输失败通知信息用于通知所述EEC所述EEC上下文传输失败。又例如，第三信息包括EEC上下文传输失败通知信息和应用上下文传输成功通知信息，EEC上下文传输失败通知信息用于向EEC通知EEC上下文传输失败，应用上下文传输成功通知信息用于向EEC通知应用上下文传输成功。又例如，第三信息包括第三指示信息，第三指示信息用于指示EEC向第一EES订阅EAS发现和/或EAS信息的服务。第八方面，本申请提供一种通信装置，该装置包括用于执行上述任意一方面或其任意可能的实现方式中的方法的模块。
第九方面，本申请提供了一种通信装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述任意一方面中任一种可能实现方式中的方法。可选地，该装置还包括存储器。可选地，该装置还包括通信接口，处理器与通信接口耦合。
第十方面，本申请提供了一种芯片，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述任意一方面中任一种可能实现方式中的方法。可选地，该装置还包括存储器。可选地，该装置还包括通信接口，处理器与通信接口耦合。
第十一方面，本申请提供了一种处理器，包括：输入电路、输出电路和处理电路。所述处理电路用于通过所述输入电路接收信号，并通过所述输出电路输出信号，使得所述处理器执行上述任意一方面中的任一种可能实现方式中的方法。
在具体实现过程中，上述处理器可以为芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于接收器接收并输入的，输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电路的具体实现方式不做限定。
第十二方面，本申请提供了一种通信装置，包括处理器和存储器。该处理器用于读取存储器中存储的指令，并可通过接收器接收信号，通过发射器发射信号，以执行上述任意一方面中的任一种可能实现方式中的方法。
可选地，所述处理器为一个或多个，所述存储器为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
在具体实现过程中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
应理解，相关的数据交互过程例如发送指示信息可以为从处理器输出指示信息的过程，接收能力信息可以为处理器接收输入能力信息的过程。具体地，处理输出的数据可以输出给发射器，处理器接收的输入数据可以来自接收器。其中，发射器和接收器可以统称为收发器。
上述第十二方面中的装置可以是芯片，该处理器可以通过硬件来实现也可以通过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，该存储器可以集成在处理器中，可以位于该处理器之外，独立存在。
第十三方面，本申请提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序或指令，当该计算机程序或指令被执行时，实现上述任意一方面中的任意可能的实现方式中的方法。
第十四方面，本申请提供了一种计算机程序产品，包含指令，当该指令被运行时，实现上述任意一方面中的任意可能的实现方式中的方法。
第十五方面，本申请提供了一种通信系统，该通信系统包括上述任意一种或多种通信装置。
附图说明
图1是本申请的实施例应用的通信系统1000的架构示意图。
图2是应用上下文迁移的一种实现方式。
图3是服务开通流程的示意图。
图4是常规的EAS发现流程的示意图。
图5是应用上下文迁移的另一种实现方式。
图6是应用上下文迁移的另一种实现方式。
图7是应用上下文迁移的另一种实现方式。
图8是应用上下文迁移的另一种实现方式。
图9是应用上下文迁移的另一种实现方式。
图10是本申请提供的用于传输上下文的方法的示意性流程图。
图11是本申请提供的用于传输上下文的方法的一个示例。
图12是本申请提供的用于传输上下文的方法的另一个示例。
图13是本申请提供的用于传输上下文的方法的另一个示例。
图14是本申请的实施例提供的可能的通信装置的结构示意图。
图15是本申请的实施例提供的可能的通信装置的另一结构示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：第五代(5 th generation，5G)移动通信系统、新无线接入技术(new radio access technology，NR)系统、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile  telecommunication system，UMTS)、或者全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统。其中，移动通信系统可以包括非独立组网(non-standalone，NSA)和/或独立组网(standalone，SA)。或者，本申请提供的技术方案可以应用于未来的通信系统，如第六代移动通信系统等。本申请对此不作限定。
本申请提供的技术方案还可以应用于机器类通信(machine type communication，MTC)、机器间通信长期演进技术(Long Term Evolution-machine，LTE-M)、设备到设备(device-to device，D2D)网络、机器到机器(machine to machine，M2M)网络、物联网(internet of things，IoT)网络或者其他网络。其中，IoT网络例如可以包括车联网。其中，车联网系统中的通信方式统称为车到其他设备(vehicle to X，V2X，X可以代表任何事物)，例如，该V2X可以包括：车辆到车辆(vehicle to vehicle，V2V)通信，车辆与基础设施(vehicle to infrastructure，V2I)通信、车辆与行人之间的通信(vehicle to pedestrian，V2P)或车辆与网络(vehicle to network，V2N)通信等。
本申请的技术方案可以应用于各种通信场景中，例如服务连续性场景、移动边缘计算(mobile edge computing，MEC)场景等，本申请不予限制。
图1是本申请的实施例应用的通信系统1000的架构示意图。如图1所示，该通信系统包括终端110、核心网120、边缘数据网络(edge data network，EDN)130和边缘配置服务器(edge configuration server，ECS)140。其中，终端110可以部署有一个或多个AC111和一个或多个EEC112，EDN130中可以部署有一个或多个EAS131和一个或多个EES132。其中，EDGE-1接口是EES132与EEC112之间的接口，EDGE-2接口是EES132与核心网120之间的接口，EDGE-3接口是EAS131与EES132之间的接口，EDGE-4接口是EEC112与ECS140之间的接口，EDGE-5接口是AC111与EEC112之间的接口，EDGE-6接口是EES132与ECS140之间的接口，EDGE-7接口是EAS131与核心网120之间的接口，EDGE-8接口是ECS140与核心网120之间的接口，EDGE-9接口是EES132之间的接口。图1只是示意图，该通信系统中还可以包括其它网络设备，在图1中未画出。
其中，应用用户与应用的提供商签订服务协议，从而为应用用户提供服务。而应用用户可以登录终端110上的AC111，并通过AC111与EAS131的连接与EDN130进行通信。EEC112为中间件层，一般位于操作系统中，或者位于AC111与操作系统中间。AC111可以以API的方式从EEC112获取边缘使能服务。
为了方便理解，下面对本申请涉及的一些网元、术语等进行描述。
1、多接入边缘计算MEC
MEC可利用无线接入网络就近提供电信用户IT所需服务和云端计算功能，而创造出一个具备高性能、低延迟与高带宽的电信级服务环境，加速网络中各项内容、服务及应用的快速下载，让消费者享有不间断的高质量网络体验。
2、数据网络
数据网络(data network，DN)指运营商或第三方的服务网络，可以向终端提供服务(例如，运营商业务、互联网业务等)。
3、本地数据网络
本地数据网络(local DN)可以是距离用户的附着点(attachment point)很近的一个数据网络的接入点(access point)。
4、边缘数据网络EDN
一种理解为，EDN只对应一个数据网络，是一个特别的本地数据网络，包含边缘使能功能，可以使用数据网络接入标识符(data network access identifier，DNAI)和数据网络名称(data network name，DNN)标识，是网络逻辑概念。
另一种理解为，EDN是中心云的对等概念，可以理解为是一个本地的数据中心(地理位置概念)，可以使用DNAI来标识，可以包含一个或多个本地数据网络。
5、边缘应用服务器EAS
部署在EDN中的应用可以称为EAS。具体地，EAS可以是指一个服务器应用程序(例如，社交媒体软件、增强现实(augmented reality，AR)、虚拟现实(virtual reality，VR))部署运行在EDN的实例(instance)。
一个应用可在一个或多个EDN中部署一个或多个EAS。部署运行在不同的EDN中的EAS可以认为是一个应用的不同的EAS，可以共享一个域名，可以使用一个IP地址，也可以使用不同的IP地址。
EAS也可以被替换为边缘应用、边缘应用服务器、应用实例、边缘应用实例、MEC应用、MEC应用服务器、EAS功能等，本申请不予限制。为了描述方便，下文统一称为边缘应用服务器。
6、应用客户端AC
AC是应用服务器在终端侧的对等实体，用于应用用户(user)从应用服务器获取应用业务。AC可以是应用在终端侧的客户端程序，可以连接到云上的应用服务器获取应用业务，也可以连接到部署运行在一个或多个EDN中的EAS以获取应用业务。AC也可以称为应用程序客户端，本申请不予限制。
7、边缘使能服务器EES
EES可以为部署在EDN中的EAS提供一些使能能力。EES可以支持边缘应用服务器的注册、对终端的认证和鉴权、为终端提供边缘应用服务器的IP地址信息等。EES还可以支持获取边缘应用服务器的标识和IP地址信息，并支持进一步将获取的标识和IP地址信息发送给ECS。EES部署在EDN中。
一般情况下，EAS注册到一个EES上，或者，通过管理系统将一个EAS的信息配置在一个EES上，该EES称为该EAS关联的EES，或者，该EAS称为该EES关联的EAS，EES控制或管理注册或配置在该EES上的EAS。
EES关联的EAS也可以替换为EES对应的EAS，EAS关联的EES也可以替换为EAS对应的EES，本申请不予限制。
8、边缘使能客户端EEC
EEC是EES在终端侧的对等实体。EEC可以用于向EES注册EEC的信息及AC的信息、执行安全认证和鉴权、从EES获取EAS的IP地址、向AC提供边缘计算使能能力等，例如EEC可以通过EAS发现服务，将EAS的IP地址返回给AC。
9、边缘配置服务器ECS
ECS主要负责EDN的配置。例如，ECS可以向终端提供EES的信息。又例如，ECS还可以与应用的DNS交互获取EAS的信息，并直接向终端提供EAS的信息。ECS还可以从其他功能实体获取并保存EAS和IP地址的信息。
10、终端
终端也可以称为终端设备、用户设备(user equipment，UE)、移动台、移动终端等。终端可以广泛应用于各种场景，例如，设备到设备(device-to-device，D2D)、车物(vehicle to everything，V2X)通信、机器类通信(machine-type communication，MTC)、物联网(internet of things，IoT)、虚拟现实、增强现实、工业控制、自动驾驶、远程医疗、智能电网、智能家具、智能办公、智能穿戴、智能交通、智慧城市等。终端可以是手机、平板电脑、带无线收发功能的电脑、可穿戴设备、车辆、无人机、直升机、飞机、轮船、机器人、机械臂、智能家居设备等。本申请的实施例对终端所采用的具体技术和具体设备形态不做限定。
11、应用上下文(application context)
应用上下文可以指和一个或一组用户相关的运行状态信息，例如，游戏进程、ML的历史数据等。可选地，应用上下文还可以包含该一个或多个用户在EAS与核心网的订阅的上下文，例如订阅的事务标识等。可选地，应用上下文还可以包括该一个或多个用户在EES上的上下文，例如，EAS对该一个或多个用户的订阅的事务标识。
12、EEC上下文(EEC context)
EEC上下文可以指存储在EES中的与用户相关的数据。
EEC上下文可以包括EEC侧信息和EAS-EES订阅信息。其中，EEC侧信息可以包括EEC注册信息、EEC订阅信息(例如，EAS发现订阅、EAS动态信息订阅等)；EAS-EES订阅信息可以包括UE位置API、应用上下文重定位事件、AC信息开放API、UE标识API、以及QoS会话API等。
13、应用上下文迁移(application context relocation，ACR)
应用上下文迁移也可以称为应用上下文重定位，在本申请中对比不做区分。
在边缘应用运行的过程中，当终端移动到当前的服务区之外，当前提供服务的EAS可能无法继续为当前运行的应用提供服务，或者当前提供服务的EAS已经不是可以为该终端提供服务的最优的EAS，其他的EAS可能更适合为终端服务，此时可以选择新的EAS为该终端提供服务。然而，在新的边缘应用程序服务器替换当前进行服务的边缘应用程序服务器的过程中会引起应用服务短暂挂起或中断，影响应用业务的传输。
为了将应用运行中断的影响降至最低，可以对应用上下文进行迁移。为了描述方便，下文将当前提供服务的EAS称为源EAS(source EAS，S-EAS)，将新的EAS称为目标EAS(target EAS，T-EAS)。
应用上下文迁移流程主要可以分为以下四个阶段。
阶段1：应用上下文迁移的检测
在此阶段，可以判断可能需要进行上下文迁移。可以由检测实体检测到目标事件。目标事件可以包括终端位置变化、终端用户面路径发生更新等。
阶段2：应用上下文迁移的决策
在此阶段，由决策实体确定需要进行上下文迁移。
阶段3：应用上下文迁移的执行
在此阶段，由执行实体将应用的上下文从源EAS传送至目标EAS。进一步地，包括目标EAS的发现，还可以向终端通知目标EAS的相关信息、通知EAS(可以是源EAS 和目标EAS)发起应用上下文传输，EES或EAS执行应用功能(application function，AF)流量影响(AF traffic influence)并携带T-EAS的N6路由信息
阶段4：应用上下文迁移后的清理工作
在此阶段会涉及到多个实体，EAS通过EES通知EEC应用上下文传输结果，AC发起一个新的socket连接到目标EAS等。
需要说明的是，上述各实体可以是同一实体，也可以是不同的实体，不予限制。
下面结合图2至图9对应用上下文迁移的几种具体实现方式进行描述。
图2是应用上下文迁移的一种实现方式。
在本实现方式中，由EEC发起ACR，并采用常规的EAS发现流程。
步骤201，EEC检测到目标事件，决定触发应用上下文迁移。
其中，目标事件可以包括UE位置变化、UE用户面路径发生更新等。
例如，EEC检测到UE的位置更新(UE location update)。
步骤202，EEC执行服务开通流程(service provisioning)流程，以便发现T-EES。
下文将结合图3对步骤202进行详细描述。
步骤203，EEC执行常规的EAS发现(regular EAS)流程，以便发现一个或多个EAS。
下文将结合图4对步骤202进行详细描述。
步骤204，AC从EEC发现的一个或多个EAS中选择T-EAS。
步骤205，EEC向S-EES发送应用上下文迁移请求消息(application context relocation request)。
步骤206，S-EES向EEC发送应用上下文迁移响应消息(application context relocation response)。
步骤207，S-EAS和T-EAS之间传输应用上下文。
步骤208，在应用上下文传输完之后，各实体执行清理流程。
可知，在图2所示的实现方式中由EEC进行检测、决策、确定T-EES和T-EAS，由EEC向S-EES请求发起用户面路径修改，由EEC或AC发起应用上下文的传输。
图3是服务开通流程的示意图。
前提条件：ECS根据UE位置、服务需求、服务偏好和连接性，配置EEC有关的可用的边缘计算服务信息，用于EEC发现有关可用的EES。
步骤301，EEC向ECS发送服务开通(service provisioning)请求消息。
其中，服务开通请求消息中可以包括EEC ID(identifier)、安全凭据、AC配置文件(AC profile)、UE标识、连接信息、和UE位置等。其中，UE标识可以包括通用公共订阅标识符(generic public subscription identifier，GPSI)等。
作为一个示例，表1示出了服务开通请求消息可以包括的信元。
表1
Figure PCTCN2022083051-appb-000001
Figure PCTCN2022083051-appb-000002
步骤302，在接收到服务开通请求消息后，ECS处理服务开通请求。
具体地，ECS进行认证授权，并根据EEC提供的AC配置文件和UE位置信息，匹配注册到ECS上的EES。
步骤303，ECS向EEC发送服务开通响应消息。
若ECS无法根据服务开通请求消息确定EEC信息，则ECS应拒绝该EEC的服务开通请求，并给出失败原因。
若ECS成功处理该EEC的服务开通请求，则ECS可以提供EDN连接信息、满足EEC请求信息的EES列表、以及EES的地址标识信息等。
作为一个示例，表2示出了服务开通响应消息可以包括的信元。
表2
Figure PCTCN2022083051-appb-000003
Figure PCTCN2022083051-appb-000004
图4是常规的EAS发现流程的示意图。
前提条件：1)EEC收到EES的信息，例如EES的URL、IP地址等；2)EES上配置ECSP的EAS发现策略。
步骤401，EEC向EES发送EAS发现请求消息。
其中，EAS发现请求消息可以包括EEC ID以及安全凭据。EAS发现请求消息还可以包括EAS发现过滤器(EAS discovery filter)，以便检索有关特定EAS或特定某类EAS(例如游戏应用程序)的信息。
作为一个示例，表3示出了EAS发现请求消息可以包括的信元。
表3
Figure PCTCN2022083051-appb-000005
作为一个示例，表4示出了EAS发现过滤器可以包括的信元。
表4
Figure PCTCN2022083051-appb-000006
Figure PCTCN2022083051-appb-000007
作为一个示例，表5示出了AC配置文件可以包括的信元。
表5
Figure PCTCN2022083051-appb-000008
步骤402，在接收到EEC发送的EAS发现请求后，EES进行授权检验并确定一个或多个EAS。
具体地，若EES确定该EEC被授权发现所请求的EAS，则EES根据提供的EAS发现过滤器和UE的位置确定一个或多个EAS。若在EAS发现请求消息中未提供EAS发现过滤器，则EES基于EES上的UE特定业务信息和UE位置确定一个或多个EAS，或者，EES通过应用ECSP策略(例如，仅基于UE位置)，确定一个或多个EAS。若果EES无法通过EAS发现请求消息中携带的信息、EES上的UE特定业务信息和UE位置、或ECSP策略确定一个或多个EAS，则EES拒绝该EEC的EAS发现请求，并给出相应的失败原因。若UE位于EAS的地理或拓扑服务区之外，则EES不应在EAS发现响应消息中包括该EAS。
步骤403，EES向EEC发送EAS发现响应消息。
其中，若EEC的EAS发现请求处理成功，EAS发现响应消息包括已发现的一个或多 个EAS的信息、及其端点信息；若EEC的EAS发现请求处理失败，EAS发现响应消息包括失败指示、以及失败原因。
作为一个示例，表6示出了EAS发现响应消息可以包括的信元。
表6
Figure PCTCN2022083051-appb-000009
图5是应用上下文迁移的另一种实现方式。
在本实现方式中，由EEC通过S-EES执行ACR。
步骤501，EEC检测到目标事件。
其中，目标事件可以包括UE位置变化、UE用户面路径发生更新等。
步骤502，EEC决定触发应用上下文迁移。
步骤503，EEC确定T-EAS。
步骤504，EEC向S-EES发送应用上下文迁移请求。
步骤505，S-EES向S-EAS指示传输应用上下文，S-EAS和T-EAS之间传输应用上下文。
步骤506，在应用上下文传输完之后，T-EAS向T-EES发送应用上下文迁移完成消息，指示T-EES应用上下文传输完成，并指示应用上下文传输结果。
步骤507，在应用上下文传输完之后，S-EAS向S-EES发送应用上下文迁移完成消息，指示T-EES应用上下文传输完成，并指示应用上下文传输结果。
步骤508，在接收到来自S-EAS发送的应用上下文迁移完成消息后，S-EES向EEC发送应用上下文迁移完成消息，指示EEC应用上下文传输完成。
可知，在图5所示的实现方式中由EEC进行检测、决策、确定T-EES和T-EAS，由EEC向S-EES请求发起用户面路径修改，由S-EES发起应用上下文的传输。图5所示的各阶段的更具体的描述可以参考图2中的相关描述，在此不再赘述。与图2所示的实现方式中不同的是由S-EES发起应用上下文的传输。
图6是应用上下文迁移的另一种实现方式。
在本实现方式中，由EEC通过T-EES执行ACR。
步骤601，EEC检测到目标事件。
其中，目标事件可以包括UE位置变化、UE用户面路径发生更新等。
步骤602，EEC决定触发应用上下文迁移。
步骤603，EEC确定T-EAS。
步骤604，EEC向T-EES发送应用上下文迁移请求。
步骤605，T-EES向T-EAS指示向S-EAS请求应用上下文，S-EAS和T-EAS之间传 输应用上下文。
步骤606，在应用上下文传输完之后，T-EAS向T-EES发送应用上下文迁移完成消息，指示T-EES应用上下文传输完成，并指示应用上下文传输结果。
步骤607，在接收到来自T-EAS发送的应用上下文迁移完成消息后，T-EES向EEC发送应用上下文迁移完成消息，指示EEC应用上下文传输完成。
可知，在图6所示的实现方式中由EEC进行检测、决策、确定T-EES和T-EAS，由EEC向T-EES请求发起用户面路径修改，由T-EES通知T-EAS发起应用上下文的传输。图6所示的各阶段的更具体的描述可以参考图5中的相关描述，在此不再赘述。与图5所示的实现方式中不同的是由T-EES发起应用上下文的传输。
图7是应用上下文迁移的另一种实现方式。
在本实现方式中，由S-EAS决策发起ACR。
步骤701，S-EAS检测到目标事件，或由S-EES检测到目标事件并通知S-EAS。
其中，目标事件可以包括UE位置变化、UE用户面路径发生更新等。
步骤702，S-EAS确定发起应用上下文迁移。
步骤703，S-EAS确定T-EAS。
步骤704，S-EAS进行目标侧信息的通知。
步骤705，S-EAS和T-EAS之间传输应用上下文。
步骤706，在应用上下文传输完之后，各实体执行清理流程。
可知，在图7所示的实现方式中由S-EAS或S-EES进行检测，由S-EAS进行决策、确定T-EES和T-EAS，由S-EAS发起用户面路径修改，由S-EES发起应用上下文的传输。
图8是应用上下文迁移的另一种实现方式。
在本实现方式中，由S-EES执行ACR。
步骤801，EEC、S-EAS或S-EES检测到目标事件。
其中，目标事件可以包括UE位置变化、UE用户面路径发生更新等。
步骤802，EEC或S-EAS向S-EES通知检测到目标事件。
该步骤为可选步骤，若由EEC或S-EAS检测目标事件，则需EEC或S-EAS向S-EES通知检测到目标事件。
步骤803，S-EES确定发起应用上下文迁移。
步骤804，S-EES确定T-EAS。
步骤805，S-EES进行目标侧信息的通知。
步骤806，S-EES通知S-EAS进行上下文迁移。
步骤807，S-EAS和T-EAS之间传输应用上下文。
步骤808，在应用上下文传输完之后，T-EAS向T-EES发送应用上下文迁移完成消息，指示T-EES应用上下文传输完成，并指示应用上下文传输结果。
步骤809，在应用上下文传输完之后，S-EAS向S-EES发送应用上下文迁移完成消息，指示T-EES应用上下文传输完成，并指示应用上下文传输结果。
步骤810，在接收到来自S-EAS发送的应用上下文迁移完成消息后，S-EES向EEC发送应用上下文迁移完成消息，指示EEC应用上下文传输完成。
可知，在图8所示的实现方式中由EEC、S-EAS或S-EES进行检测，由S-EES进行 决策、确定T-EES和T-EAS，由S-EES发起用户面路径修改，由S-EES通知S-EAS发起应用上下文的传输。
图9是应用上下文迁移的另一种实现方式。
图9所示的ACR方式为自动ACR。
步骤901，由S-EAS或S-EES发起自动ACR。
步骤902，EEC、S-EAS或S-EES检测到目标事件。
其中，目标事件可以包括UE位置变化、UE用户面路径发生更新等。
步骤903，EEC或S-EAS向S-EES通知检测到目标事件。
该步骤为可选步骤，若由EEC或S-EAS检测目标事件，则需EEC或S-EAS向S-EES通知检测到目标事件。
步骤904，S-EES确定发起应用上下文迁移。
步骤905，S-EES确定T-EAS。
步骤906，S-EES进行目标侧信息的通知。
步骤907，S-EES通知S-EAS进行上下文迁移。
步骤908，S-EES执行应用流量影响流程。
步骤909，S-EAS和T-EAS之间传输应用上下文。
步骤910，在应用上下文传输完之后，T-EAS向T-EES发送应用上下文迁移完成消息，指示T-EES应用上下文传输完成，并指示应用上下文传输结果。
步骤911，在应用上下文传输完之后，S-EAS向S-EES发送应用上下文迁移完成消息，指示T-EES应用上下文传输完成，并指示应用上下文传输结果。
步骤912，在接收到来自S-EAS发送的应用上下文迁移完成消息后，S-EES向EEC发送应用上下文迁移完成消息，指示EEC应用上下文传输完成。
可知，在图9所示的实现方式中由EEC、S-EAS或S-EES进行检测，由S-EES进行决策、确定T-EES和T-EAS，由S-EES发起用户面路径修改，由S-EES通知S-EAS发起应用上下文的传输。
通过图2-图9中的流程，可以实现应用的上下文的迁移。然而对于服务连续性场景，EEC上下文同样需要迁移，以便同步终端的注册数据和订阅数据、以及终端上AC对应的EAS的订阅信息。目前，应用上下文迁移流程中没有协调应用上下文迁移和EEC上下文迁移，应用上下文迁移和EEC上下文迁移为相互独立的流程，这样有可能存在应用上下文迁移和EEC上下文不同步问题，有可能会造成应用上下文迁移至目标EAS，但是EAS所需要的服务订阅信息、EEC注册信息和EEC订阅信息还没有迁移至目标侧，可能会导致应用运行缺少必要的订阅信息，这样会延长应用服务短暂挂起或中断时间，影响应用业务的传输。
因此，如何在服务连续性场景中优化应用上下文和EEC上下文迁移流程成为亟需解决的问题。
针对上述问题，本申请提供了一种用于传输上下文的方法，有助于降低边缘应用程序服务器切换过程中应用服务挂起或中断的时长，从而提高应用业务的传输的连续性。
图10是本申请提供的用于传输上下文的方法的示意性流程图。图10所示的方法可以由EEC、S-EAS、S-EES、T-EAS和T-EES执行，也可以由EEC、S-EAS、S-EES、T-EAS 和T-EES中的模块或单元执行。下面以执行主体为EEC、S-EAS、S-EES、T-EAS和T-EES对本申请的技术方案进行描述。图10所示的方法可以包括以下内容的至少部分内容。
步骤1001，S-EES与T-EES之间传输EEC上下文，S-EAS与T-EAS之间传输应用上下文。
在一些实现方式中，当发起应用上下文迁移时，S-EES与T-EES之间传输EEC上下文，S-EAS与T-EAS之间传输应用上下文。
作为一个示例，当发起应用上下文迁移时，由S-EES发起EEC上下文和应用上下文的传输。具体地，S-EES确定T-EES和与T-EES关联的T-EAS；S-EES向T-EES传输EEC上下文；S-EES指示与S-EES关联的S-EAS向T-EAS发送应用上下文，或者，S-EES向T-EES发送从S-EAS获取的应用上下文。
作为另一个示例，当发起应用上下文迁移时，由T-EES发起EEC上下文和应用上下文的传输。具体地，T-EES确定S-EES和与S-EES关联的S-EAS；T-EES向S-EES请求EEC上下文；T-EES指示T-EAS向S-EAS请求应用上下文，或者，T-EES向S-EES请求应用上下文。
本申请对于发起应用上下文迁移的决策节点并不限制，例如，可以是图2、图5、图6中的EEC，也可以是图7和图9中S-EES或S-EAS，也可以是图8中的EEC、S-EES或S-EAS。作为一个示例，S-EES可以在检测到目标事件并确定发起ACR后，发起EEC上下文和应用上下文的传输。作为另一个示例，S-EES或T-EES可以在接收到EEC发送的第六信息后，发起EEC上下文和应用上下文的传输，其中，第六信息用于指示发起应用上下文和EEC上下文的传输。
本申请并不限制EES(例如上述S-EES或T-EES)确定T-EES和T-EAS的方式并不限制。例如，S-EES可以通过发现目标EAS(discovery target EAS)流程确定T-EES和T-EAS。具体地，S-EAS向S-EES发送EAS发现请求消息，S-EES向ECS请求获取T-EES，S-EES通过T-EES发现T-EAS。又例如，T-EES和T-EAS可以是其他装置发现并选择后指示给EES的。
在本申请中，EEC上下文和应用上下文的传输结果不同，后续所执行的步骤可能不同。
情况1：应用上下文传输成功且EEC上下文传输失败
针对情况1，可以有以下两种处理方式。
方式1：步骤1002
步骤1002，第一装置向T-EES重传EEC上下文，或者，第一装置指示S-EES向T-EES重传EEC上下文。
例如，当第一装置为EEC时，EEC可以直接向S-EES发送上述指示信息，或者，EEC可以通过S-EES、T-EES向S-EES发送上述指示信息。
又例如，当第一装置为S-EES时，S-EES可以向T-EES重传EEC上下文。
又例如，当第一装置为T-EES时，T-EES可以请求S-EES重传EEC上下文。
方式2：步骤1003-1004
步骤1003，第一装置向T-EAS发送第一信息。
其中，第一信息用于T-EAS向T-EES订阅EES能力开放信息。
可选地，EES能力开放信息包括以下信息中的至少一个：UE位置API、应用上下文 重定位事件、AC信息开放API、UE标识API、以及QoS会话API。
可选地，第一信息可以直接或间接的指示T-EAS向T-EES订阅EES能力开放信息。例如，第一信息包括EEC上下文传输失败通知信息，EEC上下文传输失败通知信息用于通知所述T-EAS所述EEC上下文传输失败。又例如，第一信息包括第一指示信息，第一指示信息用于指示T-EAS向T-EES订阅EES能力开放信息。又例如，第一信息包括EEC上下文传输失败通知信息和应用上下文传输成功通知信息，EEC上下文传输失败通知信息用于向EEC通知EEC上下文传输失败，应用上下文传输成功通知信息用于向EEC通知应用上下文传输成功。
可选地，第一信息还可以指示需要订阅的服务。
步骤1004，在接收到第一装置的第一信息后，T-EAS可以向T-EES订阅上述EES能力开放信息。
在一些实现方式中，T-EAS可以根据第一信息指示的需要订阅的服务和/或根据应用业务需求，确定需要订阅的服务，并向T-EES订阅该服务。
可选地，第一装置可以为EEC、S-EES或T-EES。
可选地，在方式2中，若第一装置为S-EES或T-EES，第一装置还可以向EEC发送第二信息，其中，第二信息用于EEC向T-EES发起注册，EEC在接收到第二信息后可以根据第二信息向T-EES发起注册。若第一装置为EEC，第一装置还可以向T-EES发起注册。
其中，第二信息可以直接或间接的指示EEC向T-EES发起注册。例如，第二信息包括EEC上下文传输失败通知信息，EEC上下文传输失败通知信息用于通知所述EEC所述EEC上下文传输失败。又例如，第二信息包括EEC上下文传输失败通知信息和应用上下文传输成功通知信息，EEC上下文传输失败通知信息用于向EEC通知EEC上下文传输失败，应用上下文传输成功通知信息用于向EEC通知应用上下文传输成功。又例如，第二信息包括第二指示信息，第二指示信息用于指示EEC向T-EES发起注册。
可选地，在方式2中，若第一装置为S-EES或T-EES，第一装置还可以向EEC发送第三信息，其中，第三信息用于EEC向T-EES订阅所需服务，EEC在接收到第三信息后可以根据第三信息向T-EES订阅所需服务。若第一装置为EEC，第一装置还可以向T-EES订阅所需服务。可选地，EEC可以向T-EES订阅EAS发现或EAS信息的相关的服务，或者说Edge-1(即EEC-EES之间)订阅信息，例如EAS可用性改变、EAS动态信息改变等。
其中，第三信息可以直接或间接的指示EEC向T-EES订阅EAS发现和/或EAS信息的服务。例如，第三信息包括EEC上下文传输失败通知信息，EEC上下文传输失败通知信息用于通知所述EEC所述EEC上下文传输失败。又例如，第三信息包括EEC上下文传输失败通知信息和应用上下文传输成功通知信息，EEC上下文传输失败通知信息用于向EEC通知EEC上下文传输失败，应用上下文传输成功通知信息用于向EEC通知应用上下文传输成功。又例如，第三信息包括第三指示信息，第三指示信息用于指示EEC向T-EES订阅EAS发现和/或EAS信息的服务。
情况2：应用上下文传输失败且需要重选EES、且EEC上下文传输成功
由于需要重选EES，传输到T-EES的EEC上下文没有意义。因此，针对情况2，可以执行步骤1005-1006。
步骤1005，第一装置指示T-EES删除EEC上下文，或，第一装置删除EEC上下文。
例如，当第一装置为EEC或S-EES时，第一装置可以指示T-EES删除EEC上下文。
又例如，当第一装置为T-EES时，T-EES可以删除EEC上下文。
步骤1006，T-EES可以删除EEC上下文。
情况3：应用上下文传输失败且不需要重选EES、且EEC上下文传输成功
由于不需要重选EES，传输到T-EES的EEC上下文仍然可以使用。因此，针对情况3，可以执行步骤1007。
步骤1007，第一装置指示S-EAS向T-EAS重传应用上下文，或，第一装置指示T-EAS向S-EAS请求重传应用上下文。
其中，第一装置可以直接指示S-EAS向T-EAS重传应用上下文；也可以通过其他装置间接指示S-EAS向T-EAS重传应用上下文，例如，第一装置可以通过指示T-EAS请求S-EAS重传应用上下文，T-EAS请求S-EAS重传应用上下文，从而实现指示S-EAS向T-EAS重传应用上下文。
例如，当第一装置为EEC时，EEC可以通过S-EES向S-EAS发送上述指示信息，或者，EEC可以通过S-EES、T-EES、T-EAS向S-EAS发送上述指示信息。
又例如，当第一装置为S-EES时，S-EES可以直接向S-EAS发送上述指示信息，或者，S-EES可以通过T-EES、T-EAS向S-EAS发送上述指示信息。
又例如，当第一装置为T-EES时，T-EES可以通过T-EAS向S-EAS发送上述指示信息，或者，T-EES可以通过S-EES向S-EAS发送上述指示信息。
当第一装置我S-EES时，在另一种可能的实现方式中，S-EES还可以从S-EAS获取应用上下文，并通过T-EES向T-EAS重传应用上下文。
情况4：应用上下文传输成功且EEC上下文传输成功
针对情况4，可以执行步骤1009。
步骤1007，第一装置确定应用上下文重定位成功。
可选地，第一装置可以为EEC、S-EES或T-EES。
可选地，若第一装置为S-EES或T-EES，第一装置还可以向EEC发送指示信息，用于指示应用上下文重定位成功。
情况5：应用上下文传输失败且EEC上下文传输失败
针对情况5，可以执行步骤1010。
步骤1007，第一装置确定应用上下文重定位失败。
可选地，第一装置可以为EEC、S-EES或T-EES。
可选地，若第一装置为S-EES或T-EES，第一装置还可以向EEC发送指示信息，用于指示应用上下文重定位失败。
本申请对于第一装置确定应用上下文和EEC上下文的传输结果的方式不作具体限定。
作为一个示例，当第一装置为S-EES时，S-EES可以根据T-EES的反馈，确定EEC上下文的传输结果，S-EES可以根据S-EAS的反馈或T-EES的反馈，确定应用上下文的传输结果。
作为另一个示例，当第一装置为T-EES时，针对T-EES向S-EES请求EEC上下文的情况，若T-EES未接收来自S-EES的EEC上下文时，T-EES确定EEC上下文传输失败。
作为又一个示例，当第一装置为EEC时，EEC接收来自S-EES或T-EES的第五信息，其中，第五信息用于指示EEC上下文的传输结果；EEC根据第五信息，确定EEC上下文的传输结果。
这样，通过图2所示的技术方案，可以在发起应用上下文的迁移时同时完成应用上下文和EEC上下文的传输，有助于降低边缘应用程序服务器切换过程中应用服务挂起或中断的时长，从而提高应用业务的传输的连续性。
下面结合具体的示例，对本申请的技术方案进行详细描述。
示例1
图11是本申请提供的用于传输上下文的方法的一个示例。
在本示例中，AC与源EAS(S-EAS)连接，由源EES(S-EES)或S-EAS检测目标事件，由S-EAS触发ACR，由S-EES根据应用上下文的传输结果和EEC上下文的传输结果，确定后续流程。
步骤1101，AC连接到S-EAS，应用在S-EAS上运行。
步骤1102，S-EES或S-EAS检测到目标事件后，S-EAS确定触发ACR流程，对应用进行上下文重定位。
步骤1103，S-EAS通过S-EES和ECS，执行发现目标EAS(discovery target EAS)流程，S-EES通过ECS发现T-EES，T-EES通过S-EES向S-EAS发送发现的T-EAS配置文件。
步骤1104，S-EES向EEC发送目标侧信息。
一种可能的实现方式为S-EES通过向EEC发送目标信息通知(target information notification)消息，实现将T-EES和T-EAS的信息发送至EEC。此时EEC可以获取到发现的T-EES和T-EAS。
步骤1105，S-EES向S-EAS发送应用上下文迁移通知(application context relocation notify)，通知S-EAS开始应用上下文的传输。
步骤1106，S-EES执行应用上下文和EEC上下文传输。
具体地，S-EES向T-EES发送EEC上下文，S-EAS向T-EAS发送应用上下文。或者，S-EES从S-EAS获取应用上下文，并向T-EES发送EEC上下文和获取到的应用上下文，T-EES收到应用上下文后，再将应用上下文发送至T-EAS。
步骤1107，S-EAS检测到应用上下文传输完成后，通知S-EES应用上下文传输完成，并将传输结果发送给S-EES。
该步骤为可选步骤。
一种可能的实现方式为S-EAS向S-EES发送应用上下文传输完成(application context transfer complete)消息，应用上下文传输完成消息中可以携带传输结果。若传输结果指示传输失败，应用上下文传输完成消息中还可以携带失败的原因。作为一个示例，表7示出了应用上下文传输完成消息可以包括的信元。
表7
信元 状态 描述
结果 可选 指示应用上下文传输的结果
原因 可选 指示应用上下文传输失败的原因
步骤1108，S-EES确定应用上下文和EEC上下文的传输结果。
在一种可能的实现方式中，S-EES可以根据T-EES的反馈，确定EEC上下文的传输结果。S-EES可以根据S-EAS的反馈，确定应用上下文的传输结果。
可选地，S-EAS的反馈可以指步骤1107中S-EAS向S-EES发送的应用上下文传输完成消息。
可选地，T-EES的反馈可以指T-EES向S-EES发送的EEC上下文传输完成(EEC context transfer complete)消息。作为一个示例，表8示出了EEC上下文传输完成消息可以包括的信元。
表8
信元 状态 描述
结果 可选 指示EEC上下文传输的结果
原因 可选 指示EEC上下文传输失败的原因
在另一种可能的实现方式中，若应用上下文由S-EES传输至T-EES在传输至T-EAS，则S-EES可以根据T-EES的反馈，确定EEC上下文的传输结果和应用上下文的传输结果。
可选地，T-EES的反馈可以包括EEC上下文传输完成消息和应用上下文传输完成消息。作为一个示例，表9示出了T-EES的反馈可以包括的信元。
表9
信元 状态 描述
EEC上下文传输完成 可选 指示EEC上下文传输完成
结果 可选 指示EEC上下文传输的结果
原因 可选 指示EEC上下文传输失败的原因
应用上下文传输完成 可选 指示应用上下文传输完成
结果 可选 指示应用上下文传输的结果
原因 可选 指示应用上下文传输失败的原因
根据应用上下文和EEC上下文的传输结果，后续的流程可以由以下几种情况。
情况1：应用上下文传输成功且EEC上下文传输失败
针对情况1，可以有以下两种处理方式。
方式1：步骤1109
步骤1109，S-EES向T-EES重传EEC上下文，或者，称为S-EES向T-EES发起EEC上下文的重传。
方式2：步骤1110-1111
步骤1110，S-EES指示T-EAS向T-EES订阅所需服务。
本申请对于S-EES指示T-EAS的方式不作具体限定。
作为一个示例，S-EES可以通过T-EES指示T-EAS向T-EES订阅所需服务。
例如，S-EES发送的上述指示由T-EES透传或转发至T-EAS。
又例如，S-EES可以向T-EES指示T-EAS需要向T-EES订阅所需服务，进一步地由T-EES指示T-EAS向T-EES订阅所需服务。
这里所说的所需服务可以为上文所述的EES能力开放信息中的服务。
T-EAS接收到S-EES的指示后，可以向T-EES订阅所需服务。
步骤1111，S-EES指示EEC向T-EES注册。该步骤为可选步骤。
EEC在接收到S-EES的指示后可以向T-EES发起注册。具体的指示方式可以参考图10的相关描述。
情况2：应用上下文传输失败且需要重选EES、且EEC上下文传输成功
由于需要重选EES，传输到T-EES的EEC上下文没有意义。因此，针对情况2，可以执行步骤1112。
步骤1112，S-EES指示T-EES删除EEC上下文。
T-EES在接收到S-EES的指示后删除EEC上下文。
可选地，在方式2中，还可以执行步骤1116。
步骤1116，S-EES指示EEC向T-EES订阅所需服务。具体的指示方式可以参考图10的相关描述。
可选地，EEC可以向EES订阅EAS发现或EAS信息的相关的服务，或者说Edge-1(即EEC-EES之间)订阅信息，例如EAS可用性改变、EAS动态信息改变等。
EEC在接收到S-EES的指示后可以向T-EES订阅所需服务。
情况3：应用上下文传输失败且不需要重选EES、且EEC上下文传输成功
由于不需要重选EES，传输到T-EES的EEC上下文仍然可以使用。因此，针对情况3，可以执行步骤1113。
步骤1113，S-EES指示S-EAS向T-EAS重传应用上下文。
情况4：应用上下文传输成功且EEC上下文传输成功
情况5：应用上下文传输失败且EEC上下文传输失败
针对情况4和5，可以执行步骤1114-1115。
步骤1114，S-EES向EEC发送应用上下文重定位完成(application context relocation complete)消息，用于向EEC指示应用上下文重定位的结果。
针对情况4，应用上下文重定位完成消息可以指示应用上下文重定位成功。
针对情况5，应用上下文重定位完成消息可以指示应用上下文重定位失败，可选地，可以携带失败原因。
步骤1115，在接收到应用上下文重定位完成消息后，EEC确定应用上下文重定位结果。若应用上下文重定位完成消息可以指示应用上下文重定位成功，则EEC确定应用上下文重定位成功。若应用上下文重定位完成消息可以指示应用上下文重定位失败，则EEC确定应用上下文重定位失败。
在示例1中，由S-EES发起并协调应用上下文和EEC上下文的传输，具体地，S-EES检测或接收EEC上下文与应用上下文的传输结果。当两种上下文均传输成功或均失败时，向EEC发送ACR成功或失败的指示；当EEC上下文传输失败，应用上下文传输成功后，S-EES根据失败原因发起EEC上下文重传或指示T-EAS重新向T-EES订阅所需服务；当ACT失败，失败原因为T-EES不满足应用需求，需要重选T-EES，S-EES则指示T-EES删除EEC上下文；否则执行ACT重传。从而可以保证发生应用上下文重定位时，应用上下文和EEC上下文均迁移至目标侧，且发生失败时，可以避免重新执行全部的ACR流程或EEC上下文重定位流程，有助于避免应用业务中断时延较大的问题。
示例2
图12是本申请提供的用于传输上下文的方法的另一个示例。
在本示例中，AC与源EAS(S-EAS)连接，由EEC检测目标事件、以及触发ACR,由T-EES根据应用上下文的传输结果和EEC上下文的传输结果，确定后续流程。
步骤1201，AC连接到S-EAS，应用在S-EAS上运行。
步骤1202，EEC检测到目标事件后，确定触发ACR流程，对应用进行上下文重定位。
步骤1203，EEC执行服务开通流程和EAS发现流程，确定或发现T-EES和T-EAS。
步骤1204，EEC向T-EES发送应用上下文重定位请求消息。
其中，应用上下文重定位请求消息可以指示发起应用上下文传输和EEC上下文传输。
例如，应用上下文重定位请求消息可以包括应用上下文传输指示，用于指示是否传输应用上下文和是否传输EEC上下文。
作为一个示例，表10示出了应用上下文重定位请求消息可以包括的信元。
表10
Figure PCTCN2022083051-appb-000010
步骤1205，T-EES执行应用上下文和EEC上下文传输。
具体地，T-EES请求T-EES向T-EES发送EEC上下文，S-EES向T-EES发送EEC上下文，T-EAS向S-EAS请求应用上下文，S-EAS向T-EAS发送应用上下文。
步骤1206，T-EAS检测到应用上下文传输完成后，通知T-EES应用上下文传输完成，并将传输结果发送给T-EES。
该步骤为可选步骤。
一种可能的实现方式为T-EAS向T-EES发送应用上下文传输完成(application context transfer complete)消息，应用上下文传输完成消息中可以携带传输结果。若传输结果指示传输失败，应用上下文传输完成消息中还可以携带失败的原因。应用上下文传输完成消息可以包括的信元可以如上文的表7所示。
步骤1207，T-EES确定应用上下文和EEC上下文的传输结果。
在一种可能的实现方式中，T-EES可以根据是否接收到EEC上下文，确定EEC上下文的传输结果。T-EES可以根据T-EAS的反馈，确定应用上下文的传输结果。
可选地，S-EAS的反馈可以指步骤1206中T-EAS向T-EES发送的应用上下文传输完成消息。
根据应用上下文和EEC上下文的传输结果，后续的流程可以由以下几种情况。
情况1：应用上下文传输成功且EEC上下文传输失败
针对情况1，可以有以下两种处理方式。
方式1：步骤1208
步骤1208，T-EES请求S-EES重传EEC上下文。
方式2：步骤1209-1210
步骤1209，T-EES指示T-EAS向T-EES订阅所需服务。
这里所说的所需服务可以为上文所述的EES能力开放信息中的服务。
T-EAS接收到T-EES的指示后，可以向T-EES订阅所需服务。
步骤1210，T-EES指示EEC向T-EES注册。该步骤为可选步骤。
EEC在接收到T-EES的指示后可以向T-EES发起注册。具体的指示方式可以参考图10的相关描述。
可选地，在方式2中，还可以执行步骤1215。
步骤1215，T-EES指示EEC向T-EES订阅所需服务。具体的指示方式可以参考图10的相关描述。
可选地，EEC可以向T-EES订阅EAS发现或EAS信息的相关的服务，或者说Edge-1(即EEC-EES之间)订阅信息，例如EAS可用性改变、EAS动态信息改变等。
EEC在接收到S-EES的指示后可以向T-EES订阅所需服务。
情况2：应用上下文传输失败且需要重选EES、且EEC上下文传输成功
由于需要重选EES，传输到T-EES的EEC上下文没有意义。因此，针对情况2，可以执行步骤1211。
步骤1211，T-EES删除EEC上下文。
情况3：应用上下文传输失败且不需要重选EES、且EEC上下文传输成功
由于不需要重选EES，传输到T-EES的EEC上下文仍然可以使用。因此，针对情况3，可以执行步骤1212。
步骤1212，T-EES指示S-EAS向T-EAS重传应用上下文，或者，T-EES向S-EES发起应用上下文重传。
本申请对于T-EES指示S-EAS的方式不作具体限定。
作为一个示例，如图12所示，T-EES可以通过S-EES指示S-EAS向T-EAS重传应 用上下文。
例如，T-EES发送的上述指示由S-EES透传或转发至S-EAS。
又例如，T-EES可以向S-EES指示S-EAS需要发起应用上下文的重传，进一步地由S-EES指示S-EAS向T-EAS发起应用上下文的重传。
情况4：应用上下文传输成功且EEC上下文传输成功
情况5：应用上下文传输失败且EEC上下文传输失败
针对情况4和5，可以执行步骤1213-1214。
步骤1213，T-EES向EEC发送应用上下文重定位完成(application context relocation complete)消息，用于向EEC指示应用上下文重定位的结果。
针对情况4，应用上下文重定位完成消息可以指示应用上下文重定位成功。
针对情况5，应用上下文重定位完成消息可以指示应用上下文重定位失败，可选地，可以携带失败原因。
步骤1214，在接收到应用上下文重定位完成消息后，EEC确定应用上下文重定位结果。若应用上下文重定位完成消息可以指示应用上下文重定位成功，则EEC确定应用上下文重定位成功。若应用上下文重定位完成消息可以指示应用上下文重定位失败，则EEC确定应用上下文重定位失败。
在示例2中，由T-EES发起并协调应用上下文和EEC上下文的传输，具体地，T-EES检测或接收EEC上下文与应用上下文传输结果，并在上下文传输失败后，T-EES发起失败后的处理流程，从而可以保证发生应用上下文重定位时，应用上下文和EEC上下文均迁移至目标侧，且发生失败时，可以避免重新执行全部的ACR流程或EEC上下文重定位流程，有助于避免应用业务中断时延较大的问题。
示例3
图13是本申请提供的用于传输上下文的方法的另一个示例。
在本示例中，AC与源EAS(S-EAS)连接，由EEC检测目标事件、以及触发ACR，由EEC根据应用上下文的传输结果和EEC上下文的传输结果，确定后续流程。
步骤1301，AC连接到S-EAS，应用在S-EAS上运行。
步骤1302，EEC检测到目标事件后，确定触发ACR流程，对应用进行上下文重定位。
步骤1303，EEC执行服务开通流程和EAS发现流程，确定或发现T-EES和T-EAS。
步骤1304，EEC向T-EES发送应用上下文重定位请求消息。
步骤1305，T-EES执行应用上下文和EEC上下文传输。
步骤1301-1305可以与步骤1201-1205相互参考或引用，在此不再赘述。
步骤1306，S-EAS检测到应用上下文传输完成后，通知S-EES应用上下文传输完成，并将传输结果发送给S-EES。
该步骤为可选步骤。
一种可能的实现方式为S-EAS向S-EES发送应用上下文传输完成消息，应用上下文传输完成消息中可以携带传输结果。若传输结果指示传输失败，应用上下文传输完成消息中还可以携带失败的原因。应用上下文传输完成消息可以包括的信元可以如表7所示。
步骤1307，S-EES确定应用上下文和EEC上下文的传输结果。
步骤1307可以与步骤1108相互参考或引用，在此不再赘述。
步骤1308，S-EES向EEC指示应用上下文的传输结果和EEC上下文的传输结果。
一种可能的实现方式为S-EES发送应用上下文重定位完成消息。作为一个示例，表11示出了应用上下文重定位完成消息可以包括的信元。
表11
信元 状态 描述
EEC上下文传输完成 可选 指示EEC上下文传输完成
结果 可选 指示EEC上下文传输的结果
原因 可选 指示EEC上下文传输失败的原因
应用上下文传输完成 可选 指示应用上下文传输完成
结果 可选 指示应用上下文传输的结果
原因 可选 指示应用上下文传输失败的原因
当EEC收到应用上下文重定位完成消息后，检测EEC上下文与应用上下文是否成功传输。根据应用上下文和EEC上下文的传输结果，后续的流程可以由以下几种情况。
情况1：应用上下文传输成功且EEC上下文传输失败
针对情况1，可以有以下两种处理方式。
方式1：步骤1309
步骤1309，EEC指示S-EES向T-EES重传EEC上下文。
方式2：步骤1310-1311
步骤1310，EEC指示T-EAS向T-EES订阅所需服务。
这里所说的所需服务可以为上文所述的EES能力开放信息中的服务。
本申请对于EEC指示T-EAS的方式不作具体限定。
作为一个示例，EEC可以通过S-EES、T-EES向T-EAS发送上述指示。
作为另一个示例，EEC可以通过T-EES指示T-EAS向T-EES订阅所需服务。
例如，EEC发送的上述指示由T-EES转发或透传至T-EAS。
又例如，EEC可以向T-EES指示T-EAS需要向T-EES订阅所需服务，进一步地由T-EES指示T-EAS向T-EES订阅所需服务。
步骤1311，EEC向T-EES发起注册。该步骤为可选步骤。
T-EAS接收到EEC的指示后，可以向T-EES订阅所需服务。
可选地，在方式2中，还可以执行步骤1315。
步骤1315，EEC向T-EES订阅所需服务。
可选地，EEC可以向T-EES订阅EAS发现或EAS信息的相关的服务，或者说Edge-1(即EEC-EES之间)订阅信息，例如EAS可用性改变、EAS动态信息改变等。
情况2：应用上下文传输失败且需要重选EES、且EEC上下文传输成功
由于需要重选EES，传输到T-EES的EEC上下文没有意义。因此，针对情况2，可以执行步骤1312。
步骤1112，EEC指示T-EES删除EEC上下文。
可选地，EEC可以通过S-EES向T-EES发送上述指示。
T-EES在接收到EEC的指示后删除EEC上下文。
情况3：应用上下文传输失败且不需要重选EES、且EEC上下文传输成功
由于不需要重选EES，传输到T-EES的EEC上下文仍然可以使用。因此，针对情况 3，可以执行步骤1313。
步骤1313，EEC指示S-EAS向T-EAS重传应用上下文。
可选地。EEC可以通过S-EES向S-EAS发送上述指示。
情况4：应用上下文传输成功且EEC上下文传输成功
情况5：应用上下文传输失败且EEC上下文传输失败
针对情况4和5，可以执行步骤1314。
步骤1314，EEC确定应用上下文重定位的结果。
针对情况4，EEC确定应用上下文重定位成功。
针对情况5，EEC确定应用上下文重定位失败。
在示例3中，EEC指示S-EES发起应用上下文传输和/或EEC上下文传输，S-EES接收并应用上下文传输结果和EEC上下文传输结果，并将传输结果发送至EEC，EEC根据两者的传输结果发起上下文重传或EEC上下文删除或EAS重新向EES订阅所需服务，从而可以保证在应用上下文重定位过程中，将应用上下文和EEC上下文均迁移至目标侧，并当上下文传输失败时，避免执行全部的ACR流程或EEC上下文重定位流程。
可以理解的是，为了实现上述实施例中功能，通信装置包括了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本申请中所公开的实施例描述的各示例的单元及方法步骤，本申请能够以硬件或硬件和计算机软件相结合的形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用场景和设计约束条件。
图14和图15为本申请的实施例提供的可能的通信装置的结构示意图。这些通信装置可以用于实现上述方法实施例中第一装置或目标EAS的功能，因此也能实现上述方法实施例所具备的有益效果。在本申请的实施例中，该通信装置可以是如图1所示的EEC112、EAS131或EES132，还可以是应用于EEC112、EAS131或EES132的模块(如芯片)。
如图14所示，通信装置1400包括处理单元1410和收发单元1420。
当通信装置1400用于实现方法实施例中第一装置的功能时：
在一些实施例中，收发单元1420，用于当EEC上下文由第二EES迁移到第一EES失败时，向与所述第一EES对应的第一EAS发送第一信息，所述第一信息用于所述第一EAS向与所述第一EES订阅EES能力开放信息。
可选地，所述第一信息包括EEC上下文传输失败通知信息或第一指示信息，所述EEC上下文传输失败通知信息用于通知所述第一EAS所述EEC上下文传输失败，所述第一指示信息用于指示所述第一EAS向所述第一EES订阅所述EES能力开放信息。
可选地，第一信息包括EEC上下文传输失败通知信息和应用上下文传输成功通知信息，EEC上下文传输失败通知信息用于向EEC通知EEC上下文传输失败，应用上下文传输成功通知信息用于向EEC通知应用上下文传输成功。
可选地，所述EES能力开放信息包括以下信息中的至少一项：UE位置API、应用上下文重定位事件、AC信息开放API、以及UE标识API、以及QoS会话API。
可选地，所述装置为所述第一EES或所述第二EES。所述收发单元1420，还用于向EEC发送第二信息，所述第二信息用于指示所述EEC向所述第一EES发起注册。
可选地，第二信息可以直接或间接的指示EEC向第一EES发起注册。例如，第二信 息包括EEC上下文传输失败通知信息，EEC上下文传输失败通知信息用于通知所述EEC所述EEC上下文传输失败。又例如，第二信息包括EEC上下文传输失败通知信息和应用上下文传输成功通知信息，EEC上下文传输失败通知信息用于向EEC通知EEC上下文传输失败，应用上下文传输成功通知信息用于向EEC通知应用上下文传输成功。又例如，第二信息包括第二指示信息，第二指示信息用于指示EEC向第一EES发起注册。
可选地，所述第一装置为所述第一边缘使能服务器或所述第二边缘使能服务器；所述收发单元1420，还用于向EEC发送第三信息，所述第三信息用于指示所述EEC端向所述第一EES订阅EAS发现和/或EAS信息的服务。
可选地，第三信息可以直接或间接的指示EEC向第一EES订阅EAS发现和/或EAS信息的服务。例如，第三信息包括EEC上下文传输失败通知信息，EEC上下文传输失败通知信息用于通知所述EEC所述EEC上下文传输失败。又例如，第三信息包括EEC上下文传输失败通知信息和应用上下文传输成功通知信息，EEC上下文传输失败通知信息用于向EEC通知EEC上下文传输失败，应用上下文传输成功通知信息用于向EEC通知应用上下文传输成功。又例如，第三信息包括第三指示信息，第三指示信息用于指示EEC向所述第一EES订阅EAS发现和/或EAS信息的服务。
可选地，所述装置为所述第二EES，所述收发单元1420，还用于接收来自所述第一EES的第四信息，所述第四信息用于指示所述EEC上下文传输失败。所述处理单元1410，用于所述第一装置根据所述第四信息，确定所述EEC上下文传输失败。
可选地，所述处理单元1410，还用于在触发应用上下文迁移的情况下，确定所述第一EES和第一EAS。所述收发单元1420，还用于向所述第一EES传输所述EEC上下文。所述收发单元1420，还用于指示与所述装置关联的第二EAS向所述第一EAS发送所述应用上下文，或者，通过所述第一EES向所述第一EAS发送从所述第二EAS获取的所述应用上下文。
可选地，所述装置为所述第一EES，所述处理单元1410，用于当所述装置未接收来自所述第二EES的所述EEC上下文时，确定所述EEC上下文传输失败。
可选地，所述处理单元1410，还用于在触发应用上下文迁移的情况下，确定所述第二EES和与所述第二EES关联的第二EAS。所述收发单元1420，还用于向所述第二EES请求所述EEC上下文。所述收发单元1420，还用于指示所述第一EAS向所述第二EAS请求所述应用上下文，或者，向所述第二EES请求所述应用上下文。
可选地，所述第一装置为所述EEC，所述收发单元1420，还用于向所述第一EES发起注册。
可选地，所述收发单元1420，还用于接收来自所述第一EES或所述第二EES的第五信息，所述第五信息用于指示所述EEC上下文传输失败。所述处理单元1410用于根据所述第五信息，确定所述EEC上下文传输失败。
可选地，所述收发单元1420，还用于在触发应用上下文迁移的情况下，向所述第一EES或所述第二EES发送第六信息，所述第六信息用于指示发起所述应用上下文和所述EEC上下文的传输。
可选地，所述第一装置为所述EEC；所述收发单元1420，还用于向所述第一EES订阅EAS发现和/或EAS信息的服务。
可选地，所述收发单元1420，具体用于通过所述第一EES向所述第一EAS发送所述第一信息。
在另一些实施例中，收发单元1420，用于当应用上下文传输成功且EEC上下文传输失败时，第一装置请求第二EES向所述第一装置重传所述EEC上下文，或者，所述第一装置向所述第一EES重传所述EEC上下文，所述EEC上下文由第二EES传输到所述第一EES。
在另一些实施例中，收发单元1420，用于当应用上下文传输成功且EEC上下文传输失败时，第一装置向第二EES发送第七信息，所述第七信息用于指示所述第二EES向所述第一EES重传所述EEC上下文，或者，所述第一装置向所述第一EES发送第八信息，所述第八信息用于指示所述第一EES向所述第二EES请求重传所述EEC上下文，所述EEC上下文由第二EES传输到所述第一EES。
收发单元1420，用于当EEC上下文传输成功、应用上下文传输失败且需要重选EES时，第一装置删除所述EEC上下文，或者，所述第一装置向第一EES发送第九信息，所述第九信息用于指示所述第一EES删除所述EEC上下文，所述EEC上下文由第二EES传输到所述第一EES。
收发单元1420，用于当EEC上下文传输成功、应用上下文传输失败且无需重选EES时，第一装置向第二EAS发送第十信息，所述第十信息用于指示所述第二EAS向第一EAS重传所述应用上下文，或者，所述第一装置向第一EAS发送第十一信息，所述第十一信息用于指示所述第一EAS向所述第二EAS请求重传所述应用上下文。
可选地，所述第一装置为源EES，所述处理单元1410，用于在触发应用上下文迁移的情况下，确定所述目标EES和与所述目标EES关联的目标EAS。所述收发单元1420，还用于向所述目标EES传输所述EEC上下文。所述收发单元1420，还用于指示与所述第一装置关联的源EAS向所述目标EAS发送所述应用上下文，或者，向所述目标EES发送从所述源EAS获取的所述应用上下文。
可选地，所述收发单元1420，还用于接收到来自所述目标EES的第四信息，所述第四信息用于指示所述EEC上下文的传输结果。所述处理单元1410还用于根据所述第四信息确定所述EEC上下文传输的传输结果。
可选地，所述第一装置为目标EES，所述处理单元1410，还用于在触发应用上下文迁移的情况下，确定源EES和与所述源EES关联的源EAS。所述收发单元1420，还用于向所述源EES请求所述EEC上下文。所述收发单元1420，还用于指示所述目标EAS向所述源EAS请求所述应用上下文，或者，向所述源EES请求所述应用上下文。
可选地，所述处理单元1410还用于根据是否接收到来自所述源EES的所述EEC上下文，确定所述EEC上下文的传输结果。
可选地，所述第一装置为EEC，所述收发单元1420还用于在触发应用上下文迁移的情况下，向所述源EES或所述目标EES发送第六信息，所述第六信息用于指示发起所述应用上下文和所述EEC上下文的传输。
可选地，所述收发单元1420还用于接收来自所述源EES或所述目标EES的第五信息，所述第五信息用于指示所述EEC上下文的传输结果。所述处理单元1410还用于根据所述第五信息，确定所述EEC上下文的传输结果。
当通信装置1400用于实现方法实施例中目标EAS的功能时：
所述收发单元1420，用于接收来第一装置的第一信息，所述第一信息用于所述第一EAS向与所述第一EAS关联的第一EES订阅EES能力开放信息；根据所述第一信息，向所述第一EES订阅所述EES能力开放信息。
可选地，上述第一装置可以为源EES、目标EES或EEC。
可选地，所述第一信息包括EEC上下文传输失败通知信息或第一指示信息，所述EEC上下文传输失败通知信息用于通知所述第一EAS所述EEC上下文传输失败，所述第一指示信息用于指示所述第一EAS向所述第一EES订阅所述EES能力开放信息。
可选地，第一信息包括EEC上下文传输失败通知信息和应用上下文传输成功通知信息，EEC上下文传输失败通知信息用于向EEC通知EEC上下文传输失败，应用上下文传输成功通知信息用于向EEC通知应用上下文传输成功。
可选地，所述EES能力开放信息包括以下信息中的至少一项：UE位置API、应用上下文重定位事件、AC信息开放API、UE标识API、以及QoS会话API。
当通信装置1400用于实现方法实施例中EEC的功能时：
收发单元1420，用于接收来第一装置的第二信息，所述第二信息所述EEC向第一EES发起注册；以及根据所述第二信息，向所述第一EES发起注册。
可选地，第二信息可以直接或间接的指示EEC向第一EES发起注册。例如，第二信息包括EEC上下文传输失败通知信息，EEC上下文传输失败通知信息用于通知所述EEC所述EEC上下文传输失败。又例如，第二信息包括EEC上下文传输失败通知信息和应用上下文传输成功通知信息，EEC上下文传输失败通知信息用于向EEC通知EEC上下文传输失败，应用上下文传输成功通知信息用于向EEC通知应用上下文传输成功。又例如，第二信息包括第二指示信息，第二指示信息用于指示EEC向第一EES发起注册。
可选地，所述收发单元1420还用于接收来自所述第一装置的第三信息，所述第三信息用于指示所述EEC向所述第一EES订阅EAS发现和/或EAS信息的服务；以及根据所述第三信息，向所述第一EES订阅EAS发现和/或EAS信息的服务。
可选地，第三信息可以直接或间接的指示EEC向第一EES订阅EAS发现和/或EAS信息的服务。例如，第三信息包括EEC上下文传输失败通知信息，EEC上下文传输失败通知信息用于通知所述EEC所述EEC上下文传输失败。又例如，第三信息包括EEC上下文传输失败通知信息和应用上下文传输成功通知信息，EEC上下文传输失败通知信息用于向EEC通知EEC上下文传输失败，应用上下文传输成功通知信息用于向EEC通知应用上下文传输成功。又例如，第三信息包括第三指示信息，第三指示信息用于指示EEC向第一EES订阅EAS发现和/或EAS信息的服务。
有关上述处理单元1410和收发单元1420更详细的描述可以直接参考方法实施例中相关描述直接得到，这里不加赘述。
如图15所示，通信装置1500包括处理器1510和接口电路1520。处理器1510和接口电路1520之间相互耦合。可以理解的是，接口电路1520可以为收发器或输入输出接口。可选地，通信装置1500还可以包括存储器1530，用于存储处理器1510执行的指令或存储处理器1510运行指令所需要的输入数据或存储处理器1510运行指令后产生的数据。
当通信装置1500用于实现方法实施例中的方法时，处理器1510用于实现上述处理单 元1410的功能，接口电路1520用于实现上述收发单元1420的功能。
当上述通信装置为应用于第一装置的芯片时，该第一装置芯片实现上述方法实施例中第一装置的功能。该第一装置芯片从第一装置中的其它模块(如射频模块或天线)接收信息，该信息是其他装置发送给第一装置的；或者，该第一装置芯片向第一装置中的其它模块(如射频模块或天线)发送信息，该信息是第一装置发送给其他装置的。
当上述通信装置为应用于目标EAS的芯片时，该芯片实现上述方法实施例中目标EAS的功能。该芯片从目标EAS中的其它模块(如射频模块或天线)接收信息，该信息是其他装置发送给目标EAS的；或者，该芯片向目标EAS中的其它模块(如射频模块或天线)发送信息，该信息是目标EAS发送给其他装置的。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其它通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field programmable gate array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请的实施例中的方法步骤可以通过硬件的方式来实现，也可以由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器、闪存、只读存储器、可编程只读存储器、可擦除可编程只读存储器、电可擦除可编程只读存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于第一装置或目标EAS中。当然，处理器和存储介质也可以作为分立组件存在于第一装置或目标EAS中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、用户设备或者其它可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序或指令可以从一个网站站点、计算机、服务器或数据中心通过有线或无线方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，数字视频光盘；还可以是半导体介质，例如，固态硬盘。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示： 单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。在本申请的文字描述中，字符“/”，一般表示前后关联对象是一种“或”的关系；在本申请的公式中，字符“/”，表示前后关联对象是一种“相除”的关系。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。
除非另有说明，本申请实施例所使用的所有技术和科学术语与本申请的技术领域的技术人员通常理解的含义相同。本申请中所使用的术语只是为了描述具体的实施例的目的，不是旨在限制本申请的范围。应理解，上述为举例说明，上文的例子仅仅是为了帮助本领域技术人员理解本申请实施例，而非要将申请实施例限制于所示例的具体数值或具体场景。本领域技术人员根据上文所给出的例子，显然可以进行各种等价的修改或变化，这样的修改和变化也落入本申请实施例的范围内。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (49)

  1. 一种用于传输上下文的方法，其特征在于，所述方法包括：
    当边缘使能客户端上下文由第二边缘使能服务器迁移到第一边缘使能服务器失败时，第一装置向与所述第一边缘使能服务器对应的第一边缘应用服务器发送第一信息，所述第一信息用于所述第一边缘应用服务器向与所述第一边缘使能服务器订阅边缘使能服务器能力开放信息。
  2. 根据权利要求1所述的方法，其特征在于，
    所述第一信息包括边缘使能客户端上下文传输失败通知信息或第一指示信息，所述边缘使能客户端上下文传输失败通知信息用于通知所述第一边缘应用服务器所述边缘使能客户端上下文传输失败，所述第一指示信息用于指示所述第一边缘应用服务器向所述第一边缘使能服务器订阅所述边缘使能服务器能力开放信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述边缘使能服务器能力开放信息包括以下信息中的至少一项：用户设备位置应用编程接口、应用上下文重定位事件、应用客户端信息开放应用编程接口、用户设备标识应用编程接口、以及服务质量会话应用编程接口。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述第一装置为所述第一边缘使能服务器或所述第二边缘使能服务器；
    所述方法还包括：
    所述第一装置向边缘使能客户端发送第二信息，所述第二信息用于所述边缘使能客户端向所述第一边缘使能服务器发起注册。
  5. 根据权利要求4所述的方法，其特征在于，所述第二信息包括边缘使能客户端上下文传输失败通知信息或第二指示信息，所述边缘使能客户端上下文传输失败通知信息用于通知所述第一边缘应用服务器所述边缘使能客户端上下文传输失败，所述第二指示信息用于指示所述边缘使能客户端向所述第一边缘使能服务器发起注册。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述第一装置为所述第一边缘使能服务器或所述第二边缘使能服务器；
    所述方法还包括：
    所述第一装置向边缘使能客户端发送第三信息，所述第三信息用于所述边缘使能客户端向所述第一边缘使能服务器订阅边缘应用服务器发现和/或边缘应用服务器信息的服务。
  7. 根据权利要求6所述的方法，其特征在于，所述第三信息包括边缘使能客户端上下文传输失败通知信息或第三指示信息，所述边缘使能客户端上下文传输失败通知信息用于通知所述第一边缘应用服务器所述边缘使能客户端上下文传输失败，所述第三指示信息用于指示所述边缘使能客户端向所述第一边缘使能服务器订阅边缘应用服务器发现和/或边缘应用服务器信息的服务。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述第一装置为所述第二边缘使能服务器，所述方法还包括：
    所述第一装置接收来自所述第一边缘使能服务器的第四信息，所述第四信息用于指示 所述边缘使能客户端上下文传输失败；
    所述第一装置根据所述第四信息，确定所述边缘使能客户端上下文传输失败。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    在触发应用上下文迁移的情况下，所述第一装置确定所述第一边缘使能服务器和第一边缘应用服务器；
    所述第一装置向所述第一边缘使能服务器传输所述边缘使能客户端上下文；
    所述第一装置指示与所述第一装置对应的第二边缘应用服务器向所述第一边缘应用服务器发送所述应用上下文，或者，所述第一装置通过所述第一边缘使能服务器向所述第一边缘应用服务器发送从所述第二边缘应用服务器获取的所述应用上下文。
  10. 根据权利要求1至7中任一项所述的方法，其特征在于，所述第一装置为所述第一边缘使能服务器，所述方法还包括：
    当所述第一装置未接收来自所述第二边缘使能服务器的所述边缘使能客户端上下文时，所述第一装置确定所述边缘使能客户端上下文传输失败。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    在触发应用上下文迁移的情况下，所述第一装置确定所述第二边缘使能服务器和与所述第二边缘使能服务器对应的第二边缘应用服务器；
    所述第一装置向所述第二边缘使能服务器请求所述边缘使能客户端上下文；
    所述第一装置指示所述第一边缘应用服务器向所述第二边缘应用服务器请求所述应用上下文，或者，所述第一装置向所述第二边缘使能服务器请求所述应用上下文。
  12. 根据权利要求1至3中任一项所述的方法，其特征在于，所述第一装置为所述边缘使能客户端，所述方法还包括：
    所述第一装置向所述第一边缘使能服务器发起注册。
  13. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    所述第一装置接收来自所述第一边缘使能服务器或所述第二边缘使能服务器的第五信息，所述第五信息用于指示所述边缘使能客户端上下文传输失败；
    所述第一装置根据所述第五信息，确定所述边缘使能客户端上下文传输失败。
  14. 根据权利要求12或13所述的方法，其特征在于，所述方法还包括：
    在触发应用上下文迁移的情况下，所述第一装置向所述第一边缘使能服务器或所述第二边缘使能服务器发送第六信息，所述第六信息用于指示发起所述应用上下文和所述边缘使能客户端上下文的传输。
  15. 根据权利要求1至3、12至14中任一项所述的方法，其特征在于，所述第一装置为所述边缘使能客户端；
    所述方法还包括：
    所述第一装置向所述第一边缘使能服务器订阅边缘应用服务器发现和/或边缘应用服务器信息的服务。
  16. 根据权利要求8至9、12至14中任一项所述的方法，其特征在于，所述第一装置向与所述第一边缘使能服务器对应的第一边缘应用服务器发送第一信息，包括：
    所述第一装置通过所述第一边缘使能服务器向所述第一边缘应用服务器发送所述第一信息。
  17. 一种用于传输上下文的方法，其特征在于，所述方法包括：
    第一边缘应用服务器接收来第一装置的第一信息，所述第一信息用于所述第一边缘应用服务器向与所述第一边缘应用服务器对应的第一边缘使能服务器订阅边缘使能服务器能力开放信息；
    所述第一边缘应用服务器根据所述第一信息，向所述第一边缘使能服务器订阅所述边缘使能服务器能力开放信息。
  18. 根据权利要求17所述的方法，其特征在于，
    所述第一信息包括边缘使能客户端上下文传输失败通知信息或第一指示信息，所述边缘使能客户端上下文传输失败通知信息用于通知所述第一边缘应用服务器所述边缘使能客户端上下文传输失败，所述第一指示信息用于指示所述第一边缘应用服务器向所述第一边缘使能服务器订阅所述边缘使能服务器能力开放信息。
  19. 根据权利要求17或18所述的方法，其特征在于，所述边缘使能服务器能力开放信息包括以下信息中的至少一项：用户设备位置应用编程接口、应用上下文重定位事件、应用客户端信息开放应用编程接口、用户设备标识应用编程接口、以及服务质量会话应用编程接口。
  20. 一种用于传输上下文的方法，其特征在于，所述方法包括：
    边缘使能客户端接收来第一装置的第二信息，所述第二信息所述边缘使能客户端向第一边缘使能服务器发起注册；
    所述边缘使能客户端根据所述第二信息，向所述第一边缘使能服务器发起注册。
  21. 根据权利要求20所述的方法，其特征在于，所述第二信息包括边缘使能客户端上下文传输失败通知信息或第二指示信息，所述边缘使能客户端上下文传输失败通知信息用于通知所述第一边缘应用服务器所述边缘使能客户端上下文传输失败，所述第二指示信息用于指示所述边缘使能客户端向所述第一边缘使能服务器发起注册。
  22. 根据权利要求20或21所述的方法，其特征在于，所述方法还包括：
    所述边缘使能客户端接收来自所述第一装置的第三信息，所述第三信息用于指示所述边缘使能客户端向所述第一边缘使能服务器订阅边缘应用服务器发现和/或边缘应用服务器信息的服务；
    所述边缘使能客户端根据所述第三信息，向所述第一边缘使能服务器订阅边缘应用服务器发现和/或边缘应用服务器信息的服务。
  23. 根据权利要求22所述的方法，其特征在于，所述第三信息包括边缘使能客户端上下文传输失败通知信息或第三指示信息，所述边缘使能客户端上下文传输失败通知信息用于通知所述第一边缘应用服务器所述边缘使能客户端上下文传输失败，所述第三指示信息用于指示所述边缘使能客户端向所述第一边缘使能服务器订阅边缘应用服务器发现和/或边缘应用服务器信息的服务。
  24. 一种通信装置，其特征在于，所述装置包括：
    收发单元，用于当边缘使能客户端边缘使能客户端上下文由第二边缘使能服务器迁移到第一边缘使能服务器失败时，向与所述第一边缘使能服务器对应的第一边缘应用服务器发送第一信息，所述第一信息用于所述第一边缘应用服务器向与所述第一边缘使能服务器订阅边缘使能服务器能力开放信息。
  25. 根据权利要求24所述的装置，其特征在于，
    所述第一信息包括边缘使能客户端上下文传输失败通知信息或第一指示信息，所述边缘使能客户端上下文传输失败通知信息用于通知所述第一边缘应用服务器所述边缘使能客户端上下文传输失败，所述第一指示信息用于指示所述第一边缘应用服务器向所述第一边缘使能服务器订阅所述边缘使能服务器能力开放信息。
  26. 根据权利要求24或25所述的装置，其特征在于，所述边缘使能服务器能力开放信息包括以下信息中的至少一项：用户设备位置应用编程接口、应用上下文重定位事件、应用客户端信息开放应用编程接口、用户设备标识应用编程接口、以及服务质量会话应用编程接口。
  27. 根据权利要求24至26中任一项所述的装置，其特征在于，所述装置为所述第一边缘使能服务器或所述第二边缘使能服务器；
    所述收发单元，还用于向边缘使能客户端发送第二信息，所述第二信息用于所述边缘使能客户端向所述第一边缘使能服务器发起注册。
  28. 根据权利要求27所述的装置，其特征在于，所述第二信息包括边缘使能客户端上下文传输失败通知信息或第二指示信息，所述边缘使能客户端上下文传输失败通知信息用于通知所述第一边缘应用服务器所述边缘使能客户端上下文传输失败，所述第二指示信息用于指示所述边缘使能客户端向所述第一边缘使能服务器发起注册。
  29. 根据权利要求24至28中任一项所述的装置，其特征在于，所述装置为所述第一边缘使能服务器或所述第二边缘使能服务器；
    所述收发单元，还用于向边缘使能客户端发送第三信息，所述第三信息用于所述边缘使能客户端向所述第一边缘使能服务器订阅边缘应用服务器发现和/或边缘应用服务器信息的服务。
  30. 根据权利要求29所述的装置，其特征在于，所述第三信息包括边缘使能客户端上下文传输失败通知信息或第三指示信息，所述边缘使能客户端上下文传输失败通知信息用于通知所述第一边缘应用服务器所述边缘使能客户端上下文传输失败，所述第三指示信息用于指示所述边缘使能客户端向所述第一边缘使能服务器订阅边缘应用服务器发现和/或边缘应用服务器信息的服务。
  31. 根据权利要求24至30中任一项所述的装置，其特征在于，所述装置为所述第二边缘使能服务器，
    所述收发单元，还用于接收来自所述第一边缘使能服务器的第四信息，所述第四信息用于指示所述边缘使能客户端上下文传输失败；
    所述装置还包括处理单元，所述处理单元，用于所述第一装置根据所述第四信息，确定所述边缘使能客户端上下文传输失败。
  32. 根据权利要求31所述的装置，其特征在于，
    所述处理单元，还用于在触发应用上下文迁移的情况下，确定所述第一边缘使能服务器和第一边缘应用服务器；
    所述收发单元，还用于向所述第一边缘使能服务器传输所述边缘使能客户端上下文；
    所述收发单元，还用于指示与所述装置对应的第二边缘应用服务器向所述第一边缘应用服务器发送所述应用上下文，或者，通过所述第一边缘使能服务器向所述第一边缘应用 服务器发送从所述第二边缘应用服务器获取的所述应用上下文。
  33. 根据权利要求24至30中任一项所述的装置，其特征在于，所述装置为所述第一边缘使能服务器，所述装置还包括处理单元，
    所述处理单元，用于当所述装置未接收来自所述第二边缘使能服务器的所述边缘使能客户端上下文时，确定所述边缘使能客户端上下文传输失败。
  34. 根据权利要求33所述的装置，其特征在于，
    所述处理单元，还用于在触发应用上下文迁移的情况下，确定所述第二边缘使能服务器和与所述第二边缘使能服务器对应的第二边缘应用服务器；
    所述收发单元，还用于向所述第二边缘使能服务器请求所述边缘使能客户端上下文；
    所述收发单元，还用于指示所述第一边缘应用服务器向所述第二边缘应用服务器请求所述应用上下文，或者，向所述第二边缘使能服务器请求所述应用上下文。
  35. 根据权利要求24至30中任一项所述的装置，其特征在于，所述第一装置为所述边缘使能客户端，所述收发单元，还用于向所述第一边缘使能服务器发起注册。
  36. 根据权利要求35所述的装置，其特征在于，
    所述收发单元，还用于接收来自所述第一边缘使能服务器或所述第二边缘使能服务器的第五信息，所述第五信息用于指示所述边缘使能客户端上下文传输失败；
    所述装置还包括处理单元，所述处理单元用于根据所述第五信息，确定所述边缘使能客户端上下文传输失败。
  37. 根据权利要求35或36所述的装置，其特征在于，所述收发单元，还用于在触发应用上下文迁移的情况下，向所述第一边缘使能服务器或所述第二边缘使能服务器发送第六信息，所述第六信息用于指示发起所述应用上下文和所述边缘使能客户端上下文的传输。
  38. 根据权利要求24至26、35至37中任一项所述的装置，其特征在于，所述第一装置为所述边缘使能客户端；
    所述收发单元，还用于向所述第一边缘使能服务器订阅边缘应用服务器发现和/或边缘应用服务器信息的服务。
  39. 根据权利要求31至32、35至37中任一项所述的装置，其特征在于，所述收发单元具体用于通过所述第一边缘使能服务器向所述第一边缘应用服务器发送所述第一信息。
  40. 一种通信装置，其特征在于，所述装置包括：
    收发单元，用于接收来第一装置的第一信息，所述第一信息用于所述第一边缘应用服务器向与所述第一边缘应用服务器对应的第一边缘使能服务器订阅边缘使能服务器能力开放信息；
    所述收发单元，还用于根据所述第一信息，向所述第一边缘使能服务器订阅所述边缘使能服务器能力开放信息。
  41. 根据权利要求40所述的装置，其特征在于，
    所述第一信息包括边缘使能客户端上下文传输失败通知信息或第一指示信息，所述边缘使能客户端上下文传输失败通知信息用于通知所述第一边缘应用服务器所述边缘使能客户端上下文传输失败，所述第一指示信息用于指示所述第一边缘应用服务器向所述第一边缘使能服务器订阅所述边缘使能服务器能力开放信息。
  42. 根据权利要求40或41所述的装置，其特征在于，所述边缘使能服务器能力开放 信息包括以下信息中的至少一项：用户设备位置应用编程接口、应用上下文重定位事件、应用客户端信息开放应用编程接口、用户设备标识应用编程接口、以及服务质量会话应用编程接口。
  43. 一种通信装置，其特征在于，所述装置包括：
    收发单元，用于接收来第一装置的第二信息，所述第二信息所述边缘使能客户端向第一边缘使能服务器发起注册；
    所述收发单元，还用于根据所述第二信息，向所述第一边缘使能服务器发起注册。
  44. 根据权利要求43所述的装置，其特征在于，所述第二信息包括边缘使能客户端上下文传输失败通知信息或第二指示信息，所述边缘使能客户端上下文传输失败通知信息用于通知所述第一边缘应用服务器所述边缘使能客户端上下文传输失败，所述第二指示信息用于指示所述边缘使能客户端向所述第一边缘使能服务器发起注册。
  45. 根据权利要求43或44所述的装置，其特征在于，
    所述收发单元，还用于接收来自所述第一装置的第三信息，所述第三信息用于指示所述边缘使能客户端向所述第一边缘使能服务器订阅边缘应用服务器发现和/或边缘应用服务器信息的服务；
    所述收发单元，还用于根据所述第三信息，向所述第一边缘使能服务器订阅边缘应用服务器发现和/或边缘应用服务器信息的服务。
  46. 根据权利要求45所述的装置，其特征在于，所述第三信息包括边缘使能客户端上下文传输失败通知信息或第三指示信息，所述边缘使能客户端上下文传输失败通知信息用于通知所述第一边缘应用服务器所述边缘使能客户端上下文传输失败，所述第三指示信息用于指示所述边缘使能客户端向所述第一边缘使能服务器订阅边缘应用服务器发现和/或边缘应用服务器信息的服务。
  47. 一种通信装置，其特征在于，包括：处理器，所述处理器与存储器耦合，所述存储器用于存储程序或指令，当所述程序或指令被所述处理器执行时，使得所述装置执行如权利要求1至3、12至16中任一项所述的方法，或者执行如权利要求1至9、16中任一项所述的方法，或者执行如权利要求1至7、10至11中任一项所述的方法，或者执行如权利要求17至19中任一项所述的方法，或者执行如权利要求20至23中任一项所述的方法。
  48. 一种计算机可读存储介质，其上存储有计算机程序或指令，其特征在于，所述计算机程序或指令被执行时使得计算机执行如权利要求1至3、12至16中任一项所述的方法，或者执行如权利要求1至9、16中任一项所述的方法，或者执行如权利要求1至7、10至11中任一项所述的方法，或者执行如权利要求17至19中任一项所述的方法，或者执行如权利要求20至23中任一项所述的方法。
  49. 一种计算机程序产品，其特征在于，包括计算机程序指令，该计算机程序指令使得计算机执行：如权利要求1至3、12至16中任一项所述的方法，或者执行如权利要求1至9、16中任一项所述的方法，或者执行如权利要求1至7、10至11中任一项所述的方法，或者执行如权利要求17至19中任一项所述的方法，或者执行如权利要求20至23中任一项所述的方法。
PCT/CN2022/083051 2021-04-07 2022-03-25 一种用于传输上下文的方法和通信装置 WO2022213824A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP22783891.9A EP4304248A4 (en) 2021-04-07 2022-03-25 METHOD FOR TRANSFERRING CONTEXT AND COMMUNICATION DEVICE
US18/482,820 US20240040005A1 (en) 2021-04-07 2023-10-06 Context transfer method and communication apparatus

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
CN202110374553.3 2021-04-07
CN202110374553 2021-04-07
CN202110545128.6 2021-05-19
CN202110545128 2021-05-19
CN202110763755.7A CN115175256A (zh) 2021-04-07 2021-07-06 一种用于传输上下文的方法和通信装置
CN202110763755.7 2021-07-06

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/482,820 Continuation US20240040005A1 (en) 2021-04-07 2023-10-06 Context transfer method and communication apparatus

Publications (1)

Publication Number Publication Date
WO2022213824A1 true WO2022213824A1 (zh) 2022-10-13

Family

ID=83475768

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/083051 WO2022213824A1 (zh) 2021-04-07 2022-03-25 一种用于传输上下文的方法和通信装置

Country Status (4)

Country Link
US (1) US20240040005A1 (zh)
EP (1) EP4304248A4 (zh)
CN (1) CN115175256A (zh)
WO (1) WO2022213824A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240137422A1 (en) * 2021-02-24 2024-04-25 Telefonaktiebolaget Lm Ericsson (Publ) Edge exposure context transfer

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112153098A (zh) * 2019-06-28 2020-12-29 华为技术有限公司 一种应用迁移方法及装置
WO2021031562A1 (zh) * 2019-08-20 2021-02-25 华为技术有限公司 一种获取信息的方法及装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112153098A (zh) * 2019-06-28 2020-12-29 华为技术有限公司 一种应用迁移方法及装置
WO2021031562A1 (zh) * 2019-08-20 2021-02-25 华为技术有限公司 一种获取信息的方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
SAMSUNG: "Terms and abbreviations for service continuity", 3GPP DRAFT; S6-210633, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG6, no. e-meeting; 20210301 - 20210309, 6 March 2021 (2021-03-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051983084 *
See also references of EP4304248A4

Also Published As

Publication number Publication date
TW202241175A (zh) 2022-10-16
US20240040005A1 (en) 2024-02-01
EP4304248A1 (en) 2024-01-10
EP4304248A4 (en) 2024-07-03
CN115175256A (zh) 2022-10-11

Similar Documents

Publication Publication Date Title
JP7437372B2 (ja) ネットワークスライシング操作
US11711869B2 (en) Message and system for application function influence on traffic routing
US11956332B2 (en) Edge aware distributed network
KR102224248B1 (ko) 통신 시스템에서 PDU(Protocol Data Unit) 세션을 설립하는 방법
KR102387239B1 (ko) 모바일 네트워크 상호 작용 프록시
WO2022012310A1 (zh) 一种通信方法及装置
EP3977792A1 (en) Systems and methods for supporting traffic steering through a service function chain
JP2024506961A (ja) エッジアプリケーションサーバディスカバリ方法及び装置
JP2021518075A (ja) サービス加入方法および装置
JP2021534661A (ja) 通信方法および通信装置
WO2022067829A1 (zh) 动态触发边缘应用服务器实例化的方法及装置
US20230413212A1 (en) User equipment/wireless transmit/receive unit-provided data networks on wtrus
WO2023143574A1 (zh) 设备选择的方法以及装置
JP2023526542A (ja) 無線通信システムで端末にローカルデータネットワーク情報を提供するための方法及び装置
JP2023519873A (ja) 接続確立方法、通信装置、およびシステム
US20240040005A1 (en) Context transfer method and communication apparatus
WO2022244533A1 (ja) Ｓｍｆノード、ａｆノード、ｕｅ、及びこれらの方法
WO2022022322A1 (zh) 访问本地网络的方法和装置
WO2022001298A1 (zh) 通信方法和通信装置
CN114071649B (zh) 访问本地网络的方法和装置
WO2022099484A1 (zh) 标识发送方法和通信装置
WO2023185567A1 (zh) 发现应用服务器的方法和装置
WO2023185710A1 (zh) 一种应用上下文迁移场景的确定方法及通信装置
WO2024174803A1 (zh) 应用上下文迁移方法、通信方法及相关装置、系统
US20230254267A1 (en) Methods and apparatus for policy management in media applications using network slicing

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202327063764

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2022783891

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022783891

Country of ref document: EP

Effective date: 20231004

NENP Non-entry into the national phase

Ref country code: DE