WO2023185710A1 - 一种应用上下文迁移场景的确定方法及通信装置 - Google Patents

一种应用上下文迁移场景的确定方法及通信装置 Download PDF

Info

Publication number
WO2023185710A1
WO2023185710A1 PCT/CN2023/084010 CN2023084010W WO2023185710A1 WO 2023185710 A1 WO2023185710 A1 WO 2023185710A1 CN 2023084010 W CN2023084010 W CN 2023084010W WO 2023185710 A1 WO2023185710 A1 WO 2023185710A1
Authority
WO
WIPO (PCT)
Prior art keywords
eas
application context
ees
eass
entity
Prior art date
Application number
PCT/CN2023/084010
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
Priority claimed from CN202210689587.6A external-priority patent/CN116939746A/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023185710A1 publication Critical patent/WO2023185710A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management

Definitions

  • the present application relates to the field of communication technology, and in particular, to a method for determining an application context migration scenario and a communication device.
  • Multi-access edge computing refers to the use of wireless access networks to provide users with services required by Internet technology (IT) and cloud computing functions nearby, thereby creating a high-performance, Low latency and high bandwidth carrier-grade service environment.
  • application clients can be served by multiple edge application servers (edge application servers, EAS).
  • edge application servers EAS
  • each EAS stores the application context corresponding to the AC.
  • the service provided to the AC may be interrupted.
  • This application provides a method and communication device for determining application context migration scenarios, which are used to realize the simultaneous migration of application contexts in multiple EASs and avoid service interruption during the application context migration process.
  • this application provides a method for determining an application context migration scenario, including: a first entity determines whether multiple application context migration scenarios include an EAS decision-making application context migration scenario based on first information, where the first information indicates Application contexts in multiple first EAS need to be migrated together.
  • the first entity may select a target application context migration scenario from a plurality of application context migration scenarios.
  • the first entity determines whether the multiple application context migration scenarios include the EAS decision-making application context migration scenario based on the first information. Specifically, the first entity determines whether the multiple application context migration scenarios are based on the first information. Context migration scenarios do not include application context migration scenarios for EAS decisions.
  • the first entity can select the target application context from other application context migration scenarios except the application context migration scenario decided by EAS.
  • Migration scenario Through the application context migration scenario decided by the edge enabler client (EEC), AC or edge enabler server (EES), the application contexts in multiple first EAS can be migrated together to avoid application confusion. Service interruption occurred during context migration.
  • EAC edge enabler client
  • AC or edge enabler server EES
  • the first entity can also receive the first information.
  • the AC may send the first information to the first entity, and accordingly, the first entity may receive the first information from the AC.
  • the AC may be served by multiple second EASs, and the multiple first EASs are part or all of the multiple second EASs.
  • the first entity receives the first information from the AC. Specifically, the first entity receives the AC configuration information (AC profile) from the AC, and the AC configuration information includes the first information.
  • AC profile AC configuration information
  • the first information includes identifiers and/or first instructions of multiple first EASs; the first indication is used to indicate that application contexts in multiple first EASs need to be migrated together.
  • the first entity may also receive second information, and the second information indicates whether a third EAS exists in the plurality of first EASs, where the third EAS has applications in the plurality of first EASs.
  • the first entity determines whether the multiple application context migration scenarios include the EAS decision-making application context migration scenario based on the first information. Specifically, the first entity determines, based on the first information and the second information, Determine whether the multiple application context migration scenarios include the application context migration scenario of the EAS decision.
  • the multiple application context migration scenarios do not include the application context migration scenario of EAS decision; or, when there is a third EAS in multiple first EAS, below, multiple application context migration scenarios include EAS decision-making application context migration scenarios.
  • the first entity when the application context migration scenario of the EAS decision is not included in the multiple application context migration scenarios, the first entity can select the target application from other application context migration scenarios except the application context migration scenario of the EAS decision. Context migration scenario.
  • the application context migration scenarios decided by EEC, AC or EES are used to realize the simultaneous migration of application contexts in multiple first EASs, thereby avoiding service interruption during the application context migration process.
  • the first entity may select the target application context migration scenario from the plurality of application context migration scenarios. Further, when the target application context migration scenario selected by the first entity is the application context migration scenario decided by EEC, AC or EES, application contexts in multiple first EASs can be migrated together. When the target application context migration scenario selected by the first entity is the application context migration scenario decided by the EAS, the decision can be executed through the third EAS, that is, other EASs other than the third EAS among the multiple first EASs are discovered or notified, so that Implement application context migration in multiple first EASs together. This helps avoid service interruptions during application context migration.
  • the first entity is an EEC or EES.
  • the first entity when the first entity is an EEC, the first information is preconfigured in the AC, and the EEC receives the first information from the AC; or, the first information is preconfigured in the EEC.
  • the EEC receives from the EES the second information forwarded by the EES.
  • the AC is preconfigured with the first information, and the EES receives the first information forwarded by the EEC from the EEC.
  • the EEC is preconfigured with the first information, and the EES receives the first information from the EEC.
  • the EES receives the second information from the third EAS.
  • the AC may also send multiple identities of the first EAS to the third EAS.
  • the third EAS may send the second information to the first entity based on the received identities of the multiple first EASs.
  • this application provides a method for determining an application context migration scenario, which includes: a first entity receiving first information indicating that application contexts in multiple first EASs need to be migrated together; the first entity receives the first information according to the first information, sending the identifiers of multiple first EASs to the third EAS, where the third EAS is one or more of the multiple first EASs.
  • the first entity sends the identifiers of multiple first EASs to the third EAS.
  • the third EAS obtains the identifiers of the multiple first EASs, it can combine the application contexts in the multiple first EASs.
  • the ability to migrate When the first entity selects a target application context migration scenario, it can select an application context migration scenario decided by EEC, AC or EES, thereby realizing simultaneous migration of application contexts in multiple first EASs.
  • the first entity can also select the application context migration scenario of the EAS decision.
  • the third EAS can discover or notify other EASs among the multiple first EASs except the third EAS based on the identifiers of the multiple first EASs. This enables application contexts in multiple first EAS to be migrated together. This helps avoid service interruptions during application context migration.
  • the first entity may also determine a target application context migration scenario.
  • the first entity sends the identifiers of multiple first EASs to the third EAS based on the first information.
  • the target application context migration scenario includes an application context migration scenario determined by the EAS
  • the first entity sends the identifiers of multiple first EASs to the third EAS based on the first information.
  • the first entity can send multiple identifications of the first EAS to the third EAS based on the first information after determining that the target application context migration scenario includes the EAS decision-making application context migration scenario. In this way, it helps to avoid unnecessary Necessary signaling transmission.
  • the first entity receives the first information.
  • the AC sends the first information to the first entity, and accordingly, the first entity receives the first information from the AC.
  • the AC is provided with services by multiple second EASs, and the multiple first EASs are part or all of the multiple second EASs.
  • the first entity receives the first information from the AC. Specifically, the first entity receives AC configuration information from the AC, and the AC configuration information includes the first information.
  • the first information includes identifiers and/or first instructions of multiple first EASs; the first indication is used to indicate that application contexts in multiple first EASs need to be migrated together.
  • the first entity is an EEC or EES.
  • the AC is preconfigured with the first information
  • the EEC can receive the first information from the AC.
  • the first information is preconfigured in the EEC.
  • the EEC may also send multiple identities of the first EAS to the third EAS through the EES.
  • the AC is preconfigured with the first information, and the EES receives the first information from the EEC and is forwarded by the EEC.
  • the EEC is preconfigured with the first information, and the EES receives the first information from the EEC. Further, the EES may also send multiple identities of the first EAS to the third EAS.
  • the present application provides a method for determining an application context migration scenario, including: EAS determines, based on first information, that the application context migration scenario supported by EAS does not include the application context migration scenario decided by EAS, and the first information indicates a plurality of third The application context in an EAS needs to be migrated together; EAS sends the application context migration scenario supported by EAS.
  • the EAS here may specifically be the fourth EAS in this application.
  • the first entity can select an application context migration scenario other than the application context migration scenario decided by EAS as the target application context migration scenario, that is, the target application context migration scenario selected by the first entity is the application context decided by EEC, AC or EES.
  • the target application context migration scenario selected by the first entity is the application context decided by EEC, AC or EES.
  • migrating scenarios it helps to migrate application contexts in multiple first EAS together, thereby avoiding service interruption during the application context migration process.
  • the application context migration scenario supported by EAS can be used to determine the target application context migration scenario.
  • the EAS sends the application context migration scenario supported by the EAS. Specifically, the EAS sends the application context migration scenario supported by the EAS to the first entity.
  • the first entity receives the application context migration scenario supported by the EAS, and determines the target application context migration scenario according to the application context migration scenario supported by the EAS.
  • the first entity may be EEC or EES. Specifically, when the first entity is an EEC, EAS sends the application context migration scenario supported by EAS to EEC through EES.
  • the first information may be preconfigured in the EAS, or the first information may be received by the EAS from the AC or EEC.
  • the EAS receives the first information from the AC.
  • the AC sends AC configuration information to the EAS, and the AC configuration information includes the first information.
  • this application provides a method for determining an application context migration scenario, including: a first entity obtains capability information of multiple first EASs; the first entity obtains capability information for multiple first EASs based on the capability information of multiple first EASs.
  • the EAS determines the corresponding target application context migration scenario; wherein, the multiple first EASs are associated EASs, and the application contexts in the associated EASs need to be migrated together; the capability information of the first EAS indicates whether the first EAS is capable of processing the associated EAS The ability to migrate together with the application context in the
  • the first entity determines corresponding target application context migration scenarios for multiple first EASs based on the capability information of multiple first EASs, specifically, the first entity determines corresponding target application context migration scenarios for multiple first EASs based on the capability information of multiple first EASs.
  • the capability information determines whether the target application context migration scenario includes an application context migration scenario decided by a first EAS among the plurality of first EASs.
  • the capability information of the first EAS indicates whether the first EAS has the ability to process the application context migration in the associated EAS together, so that the first entity determines the multiple first EASs based on the capability information of the multiple first EASs. Whether there is a first EAS in the EAS that has the ability to process application contexts in associated EASs to be migrated together, and then determine corresponding target application context migration scenarios for multiple first EASs.
  • the first entity may use the application context migration scenario decided by the first EAS as the target application context migration scenario, Therefore, in the application context migration scenario decided by the first EAS, the first EAS can instruct other EASs among multiple first EASs (that is, other first EAS) to perform application context migration together to avoid occurrences during the application context migration process. Service interruption.
  • the first entity determines, based on the capability information of multiple first EASs, that one of the multiple first EASs has the ability to process the migration of application contexts in the associated EASs together. , the first entity determines that the target application context migration scenario includes an application context migration scenario decided by the first EAS among the plurality of first EASs; the first entity determines the plurality of first EASs based on the capability information of the plurality of first EASs. When none of the EASs has the ability to process the migration of application contexts in associated EASs together, the first entity determines that the target application context migration scenario does not include the application context migration scenario decided by the first EAS.
  • the first entity determines whether the first EAS has the ability to process application contexts in associated EASs to be migrated together according to the capability information of the first EAS. Specifically, the first entity may determine according to the first EAS The capability information of the EAS determines whether the first EAS supports one or more of the following capabilities 1 to 4:
  • Capability 2 the ability to send migration notifications to other EASs among multiple first EASs except the first EAS;
  • Capability 3 the ability to receive migration notifications from EASs other than the first EAS among multiple first EASs
  • Capability 4 supports application context migration scenarios decided by the first EAS
  • the migration notifications in capabilities 2 and 3 are used to trigger application context migration.
  • the first entity determines that the first EAS has the first capability, it determines that the first EAS has the capability to process application contexts in associated EASs to be migrated together.
  • the first entity determines that the first EAS does not have the first capability, it determines that the first EAS does not have the capability to process the migration of application contexts in the associated EAS together.
  • the first ability is one of ability 1, ability 2 and ability 4.
  • the first entity determines that the first EAS has the first capability group, it determines that the first EAS has the ability to process the migration of application contexts in the associated EAS together.
  • the first entity determines that the first EAS does not have any capability in the first capability group, it determines that the first EAS does not have the capability to process the migration of application contexts in the associated EAS together.
  • the first ability group is a combination of certain items among ability 1, ability 2 and ability 4.
  • the first entity determines that a certain first EAS has the ability to process the migration of application contexts in associated EASs, it may further determine that other first EASs among the plurality of first EASs other than the first EAS
  • the target application context migration scenario includes an application context migration scenario decided by the first EAS among the multiple first EASs.
  • the EEC when the first entity is an EEC, the EEC also receives the capability information of multiple first EASs forwarded by the EES from the EES; or, when the first entity is an EES, the EES also receives from the EES Capability information of the first EAS is received in each first EAS of the plurality of first EASs to obtain capability information of the plurality of first EASs. In this way, based on different first entities, an implementation method is provided for the first entity to obtain the capability information of multiple first EASs.
  • the first entity also receives first information, and the first information indicates that the plurality of first EASs are associated EASs. In this way, after receiving the first information, the first entity determines that the multiple first EASs are associated EASs, that is, determines that the application contexts of the multiple first EASs need to be migrated together.
  • the first entity when the first entity is an EEC, the first information is preconfigured in the AC, and the EEC receives the first information from the AC; or, the first information is preconfigured in the EEC.
  • the AC is preconfigured with the first information, and the EES receives the first information forwarded by the EEC from the EEC.
  • the EEC is preconfigured with the first information, and the EES receives the first information from the EEC.
  • the present application provides a method for determining an application context migration scenario, including: a first entity obtains capability information of a second entity; and the first entity determines the capability information for at least one of multiple first EASs based on the capability information of the second entity.
  • a first EAS determines the corresponding target application context migration scenario; among them, multiple first EASs are associated EASs, and the application contexts in the associated EASs need to be migrated together; the capability information of the second entity indicates whether the second entity has the processing association The ability to migrate together with the application context in EAS.
  • the one second entity is AC, EEC, or EES
  • there are two second entities and the two second entities are respectively AC and EEC, or AC and EES, or EEC and EES.
  • There are three second entities and the three second entities are AC, EEC and EES respectively.
  • the multiple second entities may include multiple EES.
  • there are five second entities and the five second entities are AC, EEC and three EES respectively.
  • the five second entities are AC and four EES respectively, or the five second entities are five EES, etc.
  • the first entity determines a corresponding target application context migration scenario for at least one first EAS among the plurality of first EASs based on the capability information of the second entity, specifically, when one or more When the capability information of the two second entities indicates that one of the second entities has the ability to process and migrate the application contexts in the associated EAS together, the first entity determines that the target application context migration scenario includes at least one application context in the first EAS. The application context migration scenario of the first EAS decision. In addition, when the capability information of one or more second entities indicates that none of the one or more second entities has the ability to process the migration of application contexts in the associated EAS together, the first entity determines the target application context migration scenario. The application context migration scenario decided by the first EAS is not included.
  • the first entity determines whether there is a second entity among the one or more second entities that has the ability to process the migration of application contexts in the associated EAS together, based on the capability information of one or more second entities.
  • a corresponding target application context migration scenario is determined for at least one first EAS among the plurality of first EASs.
  • a target application context migration scenario corresponding to an EAS so that in the application context migration scenario decided by the first EAS, the second entity can be used to trigger the plurality of first EASs under the instruction of a first EAS.
  • Other EASs in the first EAS perform application context migration together to avoid service interruption during the application context migration process.
  • the capability information of the second entity indicates whether the second entity supports one or more of the following capabilities:
  • Capability b Support application context migration scenarios decided by the first EAS
  • Capability c the ability to receive an indication of triggering a migration notification from a first EAS among multiple first EASs, and to send migration notifications to other first EASs among multiple first EASs based on the indication of triggering a migration notification;
  • migration notification is used to trigger application context migration.
  • the first entity determines that the second entity has the second capability, it determines that the second entity has the capability to process the application context in the associated EAS and migrate it together.
  • the first entity determines that the second entity does not have the second capability, it determines that the second entity does not have the capability to process the migration of application contexts in the associated EAS together.
  • the second ability is one of ability a, ability b and ability c.
  • the first entity determines that the second entity possesses the second capability group, it determines that the second entity has the ability to process the migration of application contexts in the associated EAS together.
  • the first entity determines that the second entity does not possess any capability in the second capability group, it determines that the second entity does not have the capability to process the migration of application contexts in the associated EAS together.
  • the second ability group is a combination of certain items among ability a, ability b and ability c.
  • the application context migration scenario supported by a first EAS among the plurality of first EAS includes: an application context migration scenario decided by the first EAS.
  • the first EAS supports the application context migration scenario decided by the first EAS. It can be understood that the first EAS can detect the trigger and decide the application context migration.
  • the first EAS determines that application context migration needs to be performed, it can The second entity sends an instruction to trigger the migration notification to instruct the second entity to send the migration notification to other EASs among the plurality of first EASs except the first EAS.
  • application context migration scenarios supported by EASs other than one of the multiple first EASs include: application context migration scenarios triggered by second entity detection.
  • the other EAS supports the application context migration scenario triggered by the detection of the second entity. It can be understood that the other EAS can receive the migration notification from the second entity and perform application context migration in response to the migration notification.
  • the first entity determines a target application context migration scenario for at least one first EAS among the plurality of first EASs based on the capability information of the second entity and the application context migration scenarios respectively supported by the plurality of first EASs.
  • the application context migration scenario includes an application context migration scenario decided by a certain first EAS. Using the application context migration scenario decided by the first EAS can avoid service interruption during the application context migration process.
  • the first entity is EEC or EES.
  • the second entity may be an AC or an EES.
  • the EEC also receives the capability information of the AC from the AC; and/or, when the second entity is an EES, the EEC also receives the capability information of the EES from the EES.
  • the EEC also receives the capability information of the AC from the AC and the capability information of the EES from the EES.
  • the second entity may be an AC or an EEC.
  • the EEC also receives the AC's capability information from the AC; and/or, when the second entity is an EEC, the EES also Receives EEC capability information from the EEC.
  • the EEC also receives the capability information of the AC from the AC and the capability information of the EES from the EES. .
  • the first entity also receives first information, and the first information indicates that the plurality of first EASs are associated EASs. In this way, after receiving the first information, the first entity determines that the multiple first EASs are associated EASs, that is, determines that the application contexts of the multiple first EASs need to be migrated together.
  • the first entity when the first entity is an EEC, the first information is preconfigured in the AC, and the EEC receives the first information from the AC; or, the first information is preconfigured in the EEC.
  • the AC is preconfigured with the first information, and the EES receives the first information forwarded by the EEC from the EEC.
  • the EEC is preconfigured with the first information, and the EES receives the first information from the EEC.
  • the first entity when multiple second entities include multiple EESs, that is, when multiple first EASs are registered with multiple EESs, the first entity can obtain the information of multiple EESs. Capability information. Among them, the capability information of each EES may indicate whether the EES has the ability to process the migration of application contexts in the associated EAS together.
  • the capability information of the first EES indicates whether the first EES supports one or more of the following capabilities:
  • Capability A the ability to obtain the identification of multiple first EAS
  • Capability B the ability to obtain the identity of at least one first EAS registered in the first EES.
  • the at least one first EAS registered in the first EES is at least one of the plurality of first EAS (associated EAS) mentioned above. ;
  • Capability C the ability to obtain the identities of multiple EES
  • Capability D the ability to receive an instruction to trigger a migration notification from a first EAS among multiple first EASs, and to send migration notifications to other EASs among multiple first EASs except the first EAS;
  • capability D may further include one or more of the following capabilities D1 to D3:
  • Capability D1 the ability to receive an instruction to trigger a migration notification from a first EAS registered in the first EES, and to send migration notifications to other EAS registered in the first EES (that is, other first EAS);
  • Capability D2 the ability to receive instructions to trigger migration notifications sent by other EESs other than the first EES among multiple EESs, and to send migration notifications to at least one first EAS registered in the first EES according to the instructions to trigger migration notifications;
  • Capability D3 the ability to receive an instruction to trigger a migration notification from a first EAS registered in the first EES, and to send an instruction to trigger a migration notification to other EESs other than the first EES among multiple EESs, so that the other EESs can At least one first EAS registered in the other EES sends a migration notification.
  • migration notification is used to trigger application context migration.
  • the first entity determines that the first EES has the third capability, it determines that the first EES has the ability to process the migration of application contexts in the associated EAS together.
  • the first entity determines that the first EES does not have the third capability, it determines that the first EES does not have the ability to process the migration of application contexts in the associated EAS together.
  • the third ability is one of ability A, ability B, ability C, and ability D.
  • the third capability may be one or more of the capabilities D1 to D3.
  • the first entity determines that the first EES has the third capability group, it determines that the first EES has the ability to process the migration of application contexts in the associated EAS together.
  • the first entity determines that the first EES does not have any capability in the third capability group, it determines that the first EES does not have the capability to process the migration of application contexts in the associated EAS together.
  • the third ability group is a combination of certain items among ability A, ability B, ability C, and ability D. Further, the third ability group is a combination of certain items among ability A, ability B, ability C, ability D1, ability D2 and ability D3.
  • the first entity determines a corresponding target application context migration scenario for at least one first EAS among the plurality of first EASs based on the capability information of the second entity, specifically, when the first entity When it is an EEC, the EEC determines the corresponding target application context migration scenarios for all the first EASs among the plurality of first EASs based on the capability information of the second entity; when the first entity is the first EES, the first EES determines the corresponding target application context migration scenarios according to the second entity's capability information.
  • the entity's capability information determines corresponding target application context migration scenarios for all first EASs among the plurality of first EASs, or the first EES determines corresponding target application context migration scenarios for some of the first EASs according to the capability information of the second entity.
  • the EAS determines the corresponding target application context migration scenario, where the part of the first EAS is specifically at least one first EAS among the plurality of first EASs registered in the first EES.
  • the first entity determines a corresponding target application context migration scenario for at least one first EAS among the plurality of first EASs based on the capability information of the second entity
  • the first entity is In the case of the first EES, the first EES determines corresponding target application context migration scenarios for all EASs in the plurality of first EASs (ie, the plurality of first EASs) based on the capability information of the second entity.
  • the first EAS may be called the main EAS, and the first EES is one of multiple EESs designated by the AC or EEC; or, the first EES is preconfigured with a third indication, and the third indication is used to indicate
  • the first EES is an EES among multiple EESs used to determine corresponding target application context migration scenarios for multiple first EASs; or, the first EES is an EES among multiple EESs in which a specified EAS is registered.
  • the designated EAS may be called the main EAS. Specifically, the designated EAS may be one of multiple first EASs designated by the AC or EEC, or the designated EAS may be pre-configured with a fourth instruction.
  • the indication is used to indicate that the EAS is the primary EAS.
  • the first EES when the first entity is a first EES and the second entity is another EES among multiple EESs, the first EES also receives capability information of other EESs from other EESs.
  • embodiments of the present application provide a communication device.
  • the device has the function of realizing the first entity in the above-mentioned first aspect or any possible implementation of the first aspect, or the function of the first entity in the second aspect or any possible implementation of the second aspect, Or the function of the first entity in the fourth aspect or any possible implementation of the fourth aspect, or the function of the first entity in the fifth aspect or any possible implementation of the fifth aspect, the device can specifically It's EEC or EES.
  • the device has the function of realizing the AC in the first aspect or any possible implementation of the first aspect, or the function of the AC in the second aspect or any possible implementation of the second aspect, or the third aspect Or the function of AC in any possible implementation of the third aspect, or the function of AC in the fourth aspect or any possible implementation of the fourth aspect, or the fifth aspect or any of the fifth aspects AC functionality among possible implementations.
  • the device has the function of implementing the EAS in the above third aspect or any possible implementation manner of the third aspect.
  • the device has the function of realizing the fifth aspect or the second entity in any possible implementation manner of the fifth aspect.
  • the device may specifically be EEC, EES or AC.
  • the functions of the above communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules or units or means corresponding to the above functions.
  • the structure of the device includes a processing module and a transceiver module, wherein,
  • the processing module is configured to support the device to perform the function of the first entity in the above-mentioned first aspect or any possible implementation of the first aspect, or the second aspect or any possible implementation of the second aspect, Or the function of the first entity in the fourth aspect or any possible implementation of the fourth aspect, or the function of the first entity in the fifth aspect or any possible implementation of the fifth aspect, the first entity Specifically, it can be EEC or EES; or,
  • the processing module is configured to support the device to perform the above-mentioned first aspect or any possible implementation manner of the first aspect, or the second aspect or any possible implementation manner of the second aspect, or the third aspect or The function of AC in any possible implementation of the third aspect, or the function of AC in the fourth aspect or any possible implementation of the fourth aspect, or the fifth aspect or any possibility of the fifth aspect
  • the processing module is configured to support the device to perform the function of the EAS in the above third aspect or any possible implementation of the third aspect; or,
  • the processing module is configured to support the device to perform the function of the second entity in the above-mentioned fifth aspect or any possible implementation manner of the fifth aspect.
  • the second entity may be an EEC, an EES, or an AC.
  • the transceiver module is used to support communication between the device and other communication devices. For example, when the device is the first entity, the transceiver module is used to receive the first information from the AC.
  • the communication device may also include a storage module, which is coupled to the processing module and stores necessary program instructions and data for the device.
  • the processing module can be a processor
  • the communication module can be a transceiver
  • the storage module can be a memory.
  • the memory can be integrated with the processor, or can be provided separately from the processor.
  • the structure of the device includes a processor and may also include a memory.
  • the processor is coupled to the memory and can be used to execute computer program instructions stored in the memory, so that the device executes the above-mentioned first aspect or the method in any possible implementation of the first aspect, or executes the above-mentioned second aspect or the second aspect.
  • the method in any possible implementation of the aspect, or the method in any possible implementation of the third aspect or the third aspect, or the method in any possible implementation of the fourth aspect or the fourth aspect.
  • the device further includes a communication interface, and the processor is coupled to the communication interface.
  • the communication interface may be a transceiver or an input/output interface; when the device is a chip included in a network device or a chip included in a terminal device, the communication interface may be an input of the chip /Output Interface.
  • the transceiver may be a transceiver circuit, and the input/output interface may be an input/output circuit.
  • embodiments of the present application provide a chip system, including: a processor.
  • the processor is coupled to a memory.
  • the memory is used to store programs or instructions.
  • the chip system implements the above-mentioned first aspect.
  • the method in one aspect or any possible implementation of the first aspect, or the method in realizing the above second aspect or any possible implementation of the second aspect, or the method in realizing the above third aspect or the third aspect.
  • the method in any possible implementation manner, or the method in any possible implementation manner of realizing the above fourth aspect or the fourth aspect, or the method in any possible implementation manner of realizing the above fifth aspect or the fifth aspect Methods in the implementation.
  • the chip system further includes an interface circuit for communicating code instructions to the processor.
  • processors in the chip system there may be one or more processors in the chip system, and the processor may be implemented by hardware or software.
  • the processor may be a logic circuit, an integrated circuit, or the like.
  • the processor may be a general-purpose processor implemented by reading software code stored in memory.
  • the memory can be integrated with the processor or can be provided separately from the processor.
  • the memory may be a non-transient processor, such as a read-only memory ROM, which may be integrated with the processor on the same chip, or may be separately provided on different chips.
  • embodiments of the present application provide a computer-readable storage medium on which a computer program or instructions are stored.
  • the computer is caused to execute the above-mentioned first aspect or any one of the first aspects.
  • a method in a possible implementation manner, or perform the above second aspect or a method in any possible implementation manner of the second aspect, or perform a method in the above third aspect or any possible implementation manner of the third aspect The method, or performs the method in the above fourth aspect or any possible implementation of the fourth aspect, or performs the method in the above fifth aspect or any possible implementation of the fifth aspect.
  • embodiments of the present application provide a computer program product.
  • a computer When a computer reads and executes the computer program product, it causes the computer to execute the method in the above-mentioned first aspect or any possible implementation of the first aspect, or Perform the above second aspect or the method in any possible implementation of the second aspect, or perform the above third aspect or the method in any possible implementation of the third aspect, or perform the above fourth aspect or The method in any possible implementation manner of the fourth aspect, or the method in any possible implementation manner of the above-mentioned fifth aspect or the fifth aspect.
  • embodiments of the present application provide a communication system that includes one or more of the first entity, AC, or third EAS in the first aspect; or includes the first entity in the second aspect.
  • the first entity may be EEC or EES; the second entity may be EEC, EES or AC.
  • FIG. 1 is a schematic diagram of an edge application architecture provided by this application.
  • FIG. 2 is a schematic flow chart of an EEC discovering EES and EAS provided by this application;
  • Figures 3 to 6 are schematic flow charts of methods for determining application context migration scenarios in implementation mode 1 provided by this application;
  • Figures 7-9 are schematic flow charts of the method for determining application context migration scenarios in the second implementation method provided by this application.
  • Figures 10 and 11 are schematic flow charts of the method for determining application context migration scenarios in the third implementation method provided by this application;
  • Figures 12 to 16 are flowcharts of the method for determining application context migration scenarios in specific scenarios provided by this application;
  • Figure 17 is a schematic flowchart of a method for determining an application context migration scenario in Implementation Mode 1 provided by this application;
  • Figure 18 is a schematic flowchart of a method for determining an application context migration scenario in Implementation Mode 2 provided by this application;
  • Figure 19 is a schematic flowchart of a method for determining application context migration scenarios in specific scenarios according to Implementation Mode 1 provided by this application;
  • Figures 20 to 22 are schematic flow charts of the method for determining application context migration scenarios in specific scenarios according to Implementation Mode 2 provided by this application;
  • Figure 23 is a schematic diagram of a communication device provided by this application.
  • Figure 24 is a schematic diagram of yet another communication device provided by this application.
  • the 3rd generation partnership project (3GPP) is conducting research on application-enabled multi-access edge computing (MEC) and has defined the edge as shown in Figure 1 Application architecture.
  • the application architecture includes terminals, edge data network (EDN) and edge configuration server (ECS).
  • the terminal may include an application client (AC) and an edge enabler client (EEC).
  • Edge data network (EDN) can include edge application server (EAS) and edge enabler server (EES).
  • the terminal can also be called terminal equipment, user equipment (UE), mobile station, mobile terminal, etc.
  • 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, tablets, computers with wireless transceiver functions, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc.
  • the embodiments of this application do not limit the specific technology and specific equipment form used by the terminal.
  • AC is a client program for edge applications on the terminal side.
  • AC is used by users to obtain application services from application servers (AS).
  • AS application servers
  • AC can connect to AS on the cloud to obtain application services, or it can also connect to servers deployed and running in one or more EDNs. EAS to obtain application business.
  • EEC is the peer entity of EES on the terminal side.
  • the EEC can be the middleware layer of the terminal, which can be located in the operating system, or between the AC and the operating system.
  • EEC is used to register EEC information and AC information with EES, perform security authentication and authentication, obtain the Internet Protocol (IP) address of EAS from EES, and provide edge computing enabling capabilities to AC.
  • IP Internet Protocol
  • the EEC can provide edge enablement services to the AC through an application program interface (API).
  • API application program interface
  • EDN is a special local data network (LDN).
  • LDN has edge enablement function.
  • EDN can use data network access point identifier (data network access identifier, DNAI) and data network name (data network name, DNN) logo. It can be understood that EDN is a local data center (geographic location concept) and can contain multiple local data networks (local DN). Among them, the local data network refers to the access point of a data network that is very close to the user's attachment point.
  • EAS refers to applications deployed in EDN.
  • EAS can be a server application (for example, social media software, augmented reality (AR), virtual reality (VR)) deployed on an instance running on EDN.
  • An application can deploy one or more EASs in one or more EDNs.
  • EASs deployed and running in different EDNs can be considered as different EASs of one application. These different EASs can share a domain name and use an IP address. , you can also use a different IP address.
  • EAS can also be called edge applications (services), application instances, edge application instances, MEC applications (services), EAS functions, etc.
  • EES can also be called MEC platform or edge platform.
  • EES is deployed in the EDN, and one or more EES can be deployed in an EDN.
  • EES is used to provide some enabling capabilities for EAS deployed in EDN to better support the deployment of applications in MEC.
  • EES can support the registration of edge applications, authentication and authentication of terminals, provide EAS IP address information for terminals, and provide EAS identification and IP address information for ECS, etc.
  • an EAS is registered on an EES, or the information of an EAS is configured on an EES through the management system.
  • the EES is called the EES associated with the EAS.
  • the EES controls/manages the EAS registered/configured on the EES. .
  • ECS can also be called EDN configuration server (edge data network configuration server, EDN CS).
  • ECS can be used to configure EDN, such as providing EES information to terminals, providing EAS information to terminals, interacting with the application's domain name system (DNS) to obtain EAS information, and obtaining and obtaining EAS information from other functional entities. Save EAS and IP address information, etc.
  • DNS domain name system
  • AC, EEC, EAS, EES and ECS can be collectively referred to as entities.
  • the two entities can be connected through the interface corresponding to the edge application architecture.
  • AC and EEC are connected through EDGE-5.
  • EEC and ECS are connected through EDGE-4, etc.
  • steps 201 to 203 are the discovery process of EES
  • steps 204 to 206 are the discovery process of EAS.
  • Step 201 EEC requests/subscribes to EES from ECS.
  • the EEC sends an EES discovery request to the ECS.
  • ECS receives the EES discovery request from the EEC.
  • the EES discovery request may include the terminal location.
  • Step 202 ECS selects EES based on the terminal location.
  • ECS can determine the DNAI of the data network that the terminal needs to access based on the terminal location. Then, ECS selects the corresponding EES for the EEC based on the multiple EES configuration information (EES profile), DNAI and fully qualified domain name (fully qualified domain name, FQDN) recorded by it. Optionally, ECS can obtain the current/potential DNAI from the session management function (SMF) before selecting EES.
  • EES profile multiple EES configuration information
  • FQDN fully qualified domain name
  • SMF session management function
  • Step 203 ECS sends EES information to EEC.
  • Step 204 EEC sends an EAS discovery request to EES.
  • the EAS discovery request may include a filter parameter, and the filter parameter may include one or more of an AC identifier and a terminal identifier.
  • Step 205 the EES matches the registered EAS.
  • the local record of EES contains the configuration information (EAS profile) of one or more registered/online EAS.
  • EES can determine the EAS that satisfies the EEC request based on the filtering parameters and the configuration information of one or more EASs recorded locally.
  • EES can match one or more EAS that satisfy the EEC request.
  • Step 206 EES sends an EAS discovery response to EEC.
  • the EAS discovery response may include information discovered by the EES that satisfies the EEC's request for EAS.
  • the EEC can provide the EAS information to the AC, so that the AC can connect to the EAS based on the EAS information. In this way, the EAS can provide relevant services to the AC.
  • the EAS currently providing services for the AC (can be recorded as source EAS, source-EAS, S-EAS) has a certain geographical service range.
  • the source EAS may not be able to continue to provide services for the AC, or the source EAS may no longer be the optimal service provider for the AC.
  • a new EAS (can be recorded as target EAS, target-EAS, T-EAS) is required to provide services for the AC, and the target EAS replaces the source EAS.
  • the EES registered by the source EAS can be recorded as source EES, source-EES, and S-EES
  • the EES registered by the target EAS can be recorded as target EES, target-EES, and T-EES.
  • the source EAS and the target EAS can be registered in the same EES. In this case, the source EES and the target EES are the same.
  • both the target EAS and the source EAS need to perform application context relocation (ACR), that is, the source EAS migrates the locally stored application context (application context, AC) to the target EAS. , to ensure that the impact of application interruptions is minimized.
  • ACR application context relocation
  • the application context refers to the running status information related to the user.
  • the application context can include the context of the source EAS and the core network subscription, such as the transaction identifier of the subscription, etc., or it can also include the user's context in the EES, such as the source EAS.
  • the transaction ID for this user's subscription can include the context of the source EAS and the core network subscription, such as the transaction identifier of the subscription, etc., or it can also include the user's context in the EES, such as the source EAS.
  • the transaction ID for this user's subscription can include the context of the source EAS and the core network subscription, such as the transaction identifier of the subscription, etc.
  • the process of application context migration can include the following four steps:
  • Step 1 detection process:
  • changes in the terminal location can be detected, or whether the user plane path of the terminal is updated, etc. can be detected to obtain the detection result.
  • the detection process may be performed by one or more of the source EAS, source EES, EEC, and AC.
  • Step 2 decision-making process
  • the decision-making process may be executed by one or more of the source EAS, source EES, EEC, and AC.
  • Step three execution process:
  • the execution process may include a discovery process of the target EAS, and the discovery process may be executed by one or more of the source EAS, source EES, EEC, and AC.
  • the execution process may also include an application context migration process.
  • the source EAS may migrate the application context in the source EAS to the target EAS.
  • the migration process may be initiated by the source EAS, the target EAS, or the EEC.
  • the source EAS can notify the terminal or the network of the target EAS information; or, after obtaining the application context from the source EAS, the target EAS can notify the terminal or the network of the target EAS information.
  • the information of the target EAS may include the address information of the target EAS (such as IP address, FQDN, etc.), the N6 routing information corresponding to the target EAS, etc.
  • the AC can initiate a new socket connection to the target EAS.
  • This application provides the following multiple application context migration scenarios (application context relocation scenario, ACR scenario).
  • the application context migration scenario may also be called an application context migration mode, an application context migration method, an application context migration method, etc.
  • Application context migration scenario 1 Application context migration scenario for EEC decision or AC decision.
  • the detection process of application context migration is performed by EEC.
  • the decision-making process of application context migration is performed by EEC or AC.
  • the specific execution process of application context migration may be that the EEC discovers the target EES and the target EAS, the EEC requests the source EES to initiate user plane path modification, and the EEC and AC initiate application context migration.
  • the cleanup process of application context migration is performed jointly by multiple entities.
  • Application context migration scenario 2 Application context migration scenario for EEC decision-making. Further, the EEC performs application context migration scenarios through the source EES.
  • the detection process of application context migration is performed by EEC.
  • the decision-making process for application context migration is also performed by the EEC.
  • the specific execution process of application context migration may be that the EEC discovers the target EES and the target EAS, the EEC requests the source EES to initiate user plane path modification, and then the source EES notifies the source EAS to initiate application context migration.
  • the cleanup process of application context migration is performed jointly by multiple entities.
  • Application context migration scenario 3 Application context migration scenario for EEC decision-making. Further, EEC performs application context migration through the target EES.
  • the detection process of application context migration is performed by EEC.
  • the decision-making process for application context migration is also performed by the EEC.
  • the specific execution process of application context migration may be that the EEC discovers the target EES and the target EAS, the EEC requests the target EES to initiate user plane path modification, and the target EES notifies the target EAS to initiate application context migration.
  • the cleanup process of application context migration is performed jointly by multiple entities.
  • Application context migration scenario 4 Application context migration scenario for EAS decision-making.
  • the specific detection process of application context migration may be that the source EES detects and notifies the source EAS that application context migration is needed, or that the source EAS detects and determines that application context migration is needed.
  • the decision-making process of application context migration is performed by the source EAS.
  • the specific execution process of application context migration may be that the source EAS discovers the target EES and the target EAS, and the source EAS initiates user plane path modification and initiates application context migration.
  • the cleanup process of application context migration is performed jointly by multiple entities.
  • Application context migration scenario 5 Application context migration scenario for source EES decisions.
  • the detection process of application context migration can be executed by one or more of the source EES, source EAS, and EEC.
  • the decision-making process for application context migration is also performed by the source EES.
  • the source EES may decide to perform application context migration based on the detection results of the above detection entities (ie, one or more of the source EES, source EAS, and EEC).
  • the specific execution process of application context migration may be that the source EES discovers the target EES and the target EAS, the source EES initiates user plane path modification, and notifies the source EAS to initiate application context migration.
  • the cleanup process of application context migration is performed jointly by multiple entities.
  • Application context migration scenario 6 Application context migration scenario for source EES decisions.
  • the detection process of application context migration is performed by the source EES.
  • the decision-making process for application context migration is also performed by the source EES.
  • the specific execution process of application context migration may be as follows: the source EES discovers the target EES and the target EAS, the source EES initiates user plane path modification, and initiates application context migration.
  • the cleanup process of application context migration is performed jointly by multiple entities.
  • the AC may be served by multiple EAS.
  • game AC requires a total of two EAS to provide services: graphics rendering EAS and chat function EAS.
  • chat function EAS graphics rendering EAS
  • the road traffic prediction AC may require a total of two EAS, namely the road monitoring EAS and the weather forecast EAS, to provide services.
  • the application context of the AC in multiple EASs is related, which means that the application contexts of the AC in multiple EASs need to be migrated together. This helps to ensure that multiple EASs provide services to the AC. Continuity.
  • the EAS whose application context needs to be migrated together may be called the first EAS.
  • the two first EASs that provide services for the game AC are respectively represented as graphics rendering EAS11 and chat function EAS12.
  • Application context 1 in graphics rendering EAS11 and application context 2 in chat function EAS12 need to be migrated together.
  • graphics rendering EAS11 migrates application context 1 in graphics rendering EAS11 to graphics rendering EAS12
  • chat function EAS12 migrates application context 2 in chat function EAS12 to chat function EAS22.
  • graphics rendering EAS21 and chat function EAS22 You can continue to provide services for the game AC based on the application context obtained by migration.
  • the EEC and AC are both located in the terminal, and the EEC and AC can obtain the identities of multiple first EASs. That is, in an application context migration scenario decided by the EEC, or in an application context migration scenario decided by the AC, the EEC or AC can instruct multiple first EASs to perform application context migration together based on the identifiers of multiple first EASs.
  • the configuration information of multiple first EASs is registered in EES, and EES can also obtain the identifiers of multiple first EASs.
  • the EES may instruct multiple first EASs to perform application context migration together according to the identifiers of the multiple first EASs.
  • the configuration information may specifically be a configuration file (profile).
  • the first EAS can only obtain its own configuration information, but cannot obtain the identifiers of other first EASs other than itself among the multiple first EASs. It is impossible to instruct other first EASs other than itself among multiple first EASs to perform application context migration together.
  • the graphics rendering EAS11 can migrate the application context 1 to the graphics rendering EAS12, but cannot instruct the chat function EAS12 to migrate the application context 2 to the graphics rendering EAS22. That is, in the application context migration scenario decided by the first EAS, there are situations where multiple first EASs cannot migrate application context migration together, resulting in service interruption during the application context migration process.
  • the identifier of the first EAS may specifically be the address information of the first EAS, such as the IP address and/or FQDN of the first EAS.
  • this application provides multiple implementation methods for determining application context migration scenarios, which are used to determine appropriate target application context migration scenarios to avoid service interruption during the application context migration process. For example:
  • the first entity may determine whether the multiple application context migration scenarios include an application context migration scenario determined by the EAS, and then select a target application context migration scenario from the multiple application context migration scenarios.
  • Implementation method 1 may be specifically described in the relevant embodiments of FIGS. 3 to 6 , FIG. 12 and FIG. 13 .
  • the first entity sends identifiers of multiple first EASs to a third EAS among multiple first EASs, so that the third EAS has the ability to migrate application contexts in multiple first EASs together.
  • the first entity selects a target application context migration scenario from multiple application context migration scenarios (application context migration scenarios including EAS decisions).
  • application context migration scenarios including EAS decisions.
  • the fourth EAS among the multiple first EASs determines that the application context migration scenarios it supports do not include the application context migration decided by the EAS. scenario, and sends its supported application context migration scenario to the first entity.
  • Implementation method three may be specifically described in the relevant embodiments of FIG. 10 , FIG. 11 and FIG. 16 .
  • the first entity is EEC or EES.
  • EEC EEC
  • EES EES
  • multiple application context migration scenarios can be considered as multiple candidate application context migration scenarios.
  • the first entity selects a target application context migration scenario from the multiple application context migration scenarios.
  • the target application context migration scenario is specifically an application context migration scenario selected by the first entity for at least one first EAS among the plurality of first EASs and corresponding to the at least one first EAS.
  • Figure 3 is a schematic flow chart of the method for determining the first application context migration scenario in implementation mode 1 provided by this application:
  • Step 301 The first entity determines, based on the first information, whether the multiple application context migration scenarios include the application context migration scenario of the EAS decision.
  • the first entity may be EEC or EES.
  • the first information indicates that application contexts in multiple first EASs need to be migrated together. That is, the first information indicates that application contexts in multiple first EASs are associated, or that multiple first EASs are associated. Wherein, the application contexts in multiple first EASs need to be (or need to be) migrated together, which can also be said that the application contexts in multiple first EASs are to be migrated together.
  • the first information includes identifiers of multiple first EASs, and the identifiers of the multiple first EASs are used to indicate that application contexts in multiple first EASs need to be migrated together.
  • the first information may include the identification of two first EASs, the graphics rendering EAS11 and the chat function EAS12.
  • the first information includes a first indication
  • the first indication may be used to indicate that application contexts in multiple first EASs need to be migrated together.
  • the first indication occupies 1 bit. When the value of this 1 bit is 1, it indicates that application contexts in multiple first EASs need to be migrated together.
  • the first indication is the field "Yes", which indicates that application contexts in multiple first EASs need to be migrated together.
  • the first information includes identifiers and first instructions of multiple first EASs.
  • identifiers of the multiple first EASs please refer to the description in Example 1
  • first instructions please refer to the description in Example 2.
  • this application can also be one of the following situations: the first information is a plurality of first EAS identifiers; the first information is a first indication; the first information is a combination of multiple first EAS identifiers and a first indication.
  • the first entity may receive the first information from the AC.
  • the AC is pre-configured with the first information.
  • the EEC can receive the first information from the AC, that is, the AC sends the first information to the EEC.
  • the EES may receive the first information forwarded by the EEC from the EEC, that is, the AC sends the first information to the EEC, and the EEC sends the first information to the EES.
  • the first information may be pre-configured in the EEC.
  • the EEC can also obtain the first information from the local pre-configuration.
  • the EES can obtain the first information from the EEC.
  • the first entity After the first entity determines that the application contexts in multiple first EASs need to be migrated together based on the first information, it needs to further determine whether the multiple application context migration scenarios do not include the application context migration scenario of the EAS decision.
  • the first entity determines whether one of the multiple application context migration scenarios does not include an EAS decision. There may be two situations:
  • Case 1 The first entity determines that the application context migration scenario among the multiple application context migration scenarios does not include the EAS decision.
  • the application context migration scenario for EAS decision-making is application context migration scenario 4.
  • the first entity determines that the multiple application context migration scenarios do not include application context migration scenario 4. That is, the first entity may determine that the multiple application context migration scenarios include application context migration scenario 1 to application context migration scenario 3, application context migration scenario 3, and application context migration scenario 3. Scenario 5 and application context migration scenario 6.
  • the first entity receives the second information, and determines whether the multiple application context migration scenarios include the EAS decision-making application context migration scenario based on the first information and the second information.
  • the second information indicates whether there is a third EAS among the plurality of first EASs.
  • the third EAS has the ability to migrate application contexts in multiple first EASs together. It can also be understood that the third EAS has the ability to discover other EASs among the plurality of first EASs except the third EAS, or the third EAS has the ability to notify other EASs among the plurality of first EASs except the third EAS to perform application context migration. .
  • the third EAS has the ability to migrate application contexts in multiple first EASs together.
  • the third EAS may store identifiers of multiple first EASs.
  • the third EAS may receive identifiers of multiple first EASs from the AC, or may receive identifiers of multiple first EASs from the EEC, or may be preconfigured with identifiers of multiple first EASs.
  • the AC may establish a connection with the third EAS, and the AC sends the identifiers of the multiple first EASs to the third EAS through the established connection.
  • the AC can send the identifiers of multiple first EASs to each of the multiple first EASs, and the first EAS with the decision-making function among the multiple first EASs can store the identifiers of the multiple first EASs. Identification, that is, as the third EAS.
  • the first EAS with the decision-making function is, for example, an EAS that supports the application context migration scenario of EAS decision-making (for example, supports application context migration scenario 4).
  • the third EAS may be all or part of the plurality of first EASs. That is, in multiple first EASs, if each first EAS has the ability to migrate application contexts in multiple first EASs together, then each first EAS is a third EAS; in multiple first EASs, In an EAS, if there is a part of the first EAS that has the ability to migrate application contexts in multiple first EASs together, then the part of the first EAS is the third EAS.
  • the first entity may receive second information sent from each first EAS in the plurality of first EASs, the second information being used to indicate whether the first EAS sending the second information is a third EAS.
  • the first entity determines whether there is a third EAS in the plurality of first EASs based on the second information of each first EAS in the plurality of first EASs.
  • the second information may include a first option or a second option.
  • the first option indicates that the first EAS that sends the second information stores the identities of multiple first EASs, that is, the first EAS that sends the first option.
  • EAS is the third EAS.
  • the second option indicates that the first EAS that sends the second information does not store the identifiers of multiple first EASs, that is, the first EAS that sends the second option is not the third EAS.
  • the second information may be the first option or the second option.
  • the second information may occupy 1 bit, where the first option is that the 1 bit has a value of 1, and the second option is that the 1 bit has a value of 0.
  • the first entity may receive the second information sent from a third EAS among the plurality of first EASs. Specifically, after receiving the second information from the first EAS, the first entity may determine that the first EAS that sent the second information is the third EAS.
  • the second information may include the first option, or the second information may be the first option.
  • the second information includes identifiers of multiple first EASs, or the second information is identifiers of multiple first EASs.
  • the plurality of application context migration scenarios do not include the application context migration scenario of the EAS decision.
  • the first entity determines that the application contexts in multiple first EASs need to be migrated together based on the first information, and determines based on the second information that there is no third EAS among the multiple first EASs, then the first entity can further determine the multiple application contexts.
  • Migration scenarios do not include application context migration scenarios for EAS decisions.
  • the application context migration scenario decided by the EAS is application context migration scenario 4.
  • the first entity determines that the multiple application context migration scenarios do not include application context migration scenario 4, that is, it determines that the multiple application context migration scenarios include the application context.
  • the multiple application context migration scenarios include application context migration scenarios decided by the EAS.
  • the first entity determines that the application contexts in multiple first EASs need to be migrated together based on the first information, and determines based on the second information that there is a third EAS in the multiple first EASs, then determines that the multiple application context migration scenarios include Application context migration scenario for EAS decision-making.
  • the application context migration scenario for EAS decision-making is application context migration scenario 4.
  • the first entity determines that the multiple application context migration scenarios include application context migration scenario 4, that is, determines that the multiple application context migration scenarios include application context migration scenario 1 to application context migration scenario 6.
  • Step 302 The first entity selects a target application context migration scenario from multiple application context migration scenarios.
  • the multiple application context migration scenarios do not include the application context migration scenario decided by EAS, and the first entity can select the target application context migration scenario from other application context migration scenarios except the application context migration scenario decided by EAS. .
  • the application context migration scenarios decided by EEC, AC or EES are used to realize the simultaneous migration of application contexts in multiple first EASs, thereby avoiding service interruption during the application context migration process.
  • the multiple application context migration scenarios include the application context migration scenario of the EAS decision, and the first entity can select the target application context migration scenario from the multiple application context migration scenarios.
  • the target application context migration scenario selected by the first entity is the application context migration scenario decided by EEC, AC or EES
  • application contexts in multiple first EASs can be migrated together.
  • the decision can be executed through the third EAS, that is, other EASs other than the third EAS among the multiple first EASs are discovered or notified, so that Implement application context migration in multiple first EASs together. This helps avoid service interruptions during application context migration.
  • Figure 4 is a schematic flowchart of a method for determining the second application context migration scenario in implementation mode 1 provided by this application.
  • the method for determining the application context migration scenario shown in FIG. 4 is specifically a specific implementation of the method for determining the application context migration scenario shown in FIG. 3 .
  • For technical solutions that are not described in detail in the relevant embodiment of FIG. 4 please refer to the description of the relevant embodiment of FIG. 3 .
  • Step 401 The first entity determines, based on the first information, that the multiple application context migration scenarios do not include the EAS decision-making application context migration scenario.
  • the first information please refer to the description of the first information in step 301.
  • the first entity determines, based on the first information, that the multiple application context migration scenarios do not include the EAS decision-making application context migration scenario.
  • the multiple application context migration scenarios do not include the EAS decision-making application context migration scenario.
  • Step 402 The first entity selects a target application context migration scenario from multiple application context migration scenarios.
  • the first entity selects the target application context migration scenario from other application context migration scenarios except the application context migration scenario decided by the EAS.
  • the application context migration scenario decided by EEC, AC or EES is used to realize the simultaneous migration of application contexts in multiple first EAS, which helps to avoid service interruption during the application context migration process.
  • Figure 5 is a schematic flowchart of a method for determining the third application context migration scenario in implementation mode 1 provided by this application.
  • the method for determining the application context migration scenario shown in FIG. 5 is specifically another specific implementation of the method for determining the application context migration scenario shown in FIG. 3 .
  • For technical solutions that are not described in detail in the relevant embodiment of FIG. 5 please refer to the description in the relevant embodiment of FIG. 3 .
  • Step 501 The first entity receives second information.
  • Step 502 The first entity determines whether the multiple application context migration scenarios include the EAS decision-making application context migration scenario based on the first information and the second information.
  • the first information please refer to the description of the first information in step 301.
  • the first entity determines, based on the first information and the second information, that the multiple application context migration scenarios do not include the application context migration scenarios of the EAS decision.
  • the multiple application context migration scenarios do not include the application context migration scenarios of the EAS decision.
  • the first entity determines, based on the first information and the second information, that multiple application context migration scenarios include application context migration scenarios decided by EAS.
  • multiple application context migration scenarios include application context migration scenarios decided by EAS.
  • the situation 2 in step 301 please refer to the situation 2 in step 301 regarding multiple first EASs. Includes instructions for third EAS.
  • Step 503 The first entity selects a target application context migration scenario from multiple application context migration scenarios.
  • the first entity may also perform the following operations:
  • the first entity can obtain the application context migration scenarios supported by each of the EES, AC, multiple first EAS, and EEC, and then determine the application context migration scenarios jointly supported by the multiple entities based on the application context migration scenarios supported by each of these entities. . The first entity then determines whether the multiple application context migration scenarios include the application context migration scenario of the EAS decision based on the application context migration scenarios jointly supported by the multiple entities and the first information.
  • EES, AC, and EEC all support application context migration scenario 1 to application context migration scenario 6, and multiple first EASs all support application context migration scenario 1 to application context migration scenario 4.
  • the first entity may use application context migration scenario 1 to application context migration scenario 4 that are jointly supported by multiple entities as multiple application context migration scenarios. The first entity then determines whether application context migration scenario 4 is included in the multiple application context migration scenarios. If so, the first entity can select the target application context migration scenario from application context migration scenario 1 to application context migration scenario 4; if it is not included , the first entity may select a target application context migration scenario from application context migration scenario 1 to application context migration scenario 3.
  • the first entity can obtain the application context migration scenarios supported by each of the EES, AC, multiple first EAS, and EEC, and then based on the respective support of these entities.
  • application context migration scenarios determine the application context migration scenarios jointly supported by the multiple entities, and then determine whether the multiple application context migration scenarios include the application context migration scenario of the EAS decision.
  • the first entity may also send the target application context migration scenario.
  • the EES may send target application context migration scenarios to the AC, multiple first EASs, and EEC respectively.
  • the EES may specifically send the target application context migration scenario to the EEC, and the EEC then sends the target application context migration scenario to the AC.
  • the EES, AC, multiple first EASs and EEC can perform relevant actions in application context migration according to the target application context migration scenario.
  • the EEC may send target application context migration scenarios to the EES, AC, and multiple first EAS respectively.
  • the EEC sends the target application context migration scenario to the first EAS
  • specifically the EEC may send the target application context migration scenario to the EES
  • the EES then sends the target application context migration scenario to the first EAS.
  • the EES, AC, multiple first EASs and EEC can perform relevant actions in application context migration according to the target application context migration scenario.
  • Figure 6 is a schematic flowchart of a method for determining the fourth application context migration scenario in implementation mode 1 provided by this application.
  • the method for determining the application context migration scenario shown in Figure 6 is specifically a specific implementation of the method for determining the application context migration scenario shown in Figure 5.
  • This specific implementation can be implemented interactively by the AC, EEC, EES and the third EAS. .
  • For technical solutions that are not described in detail in the relevant embodiment of FIG. 6 please refer to the description of the relevant embodiment of FIG. 5 , or further refer to the description of the relevant embodiment of FIG. 3 .
  • Step 601 The AC is preconfigured with multiple first EAS identifiers.
  • the AC configuration information includes a first EAS list (EAS list), and the first EAS list may be a list composed of multiple first EAS identifiers.
  • the AC configuration information may also include the AC's identification (AC ID), application context migration scenarios supported by the AC, etc.
  • AC ID AC's identification
  • application context migration scenarios supported by the AC etc.
  • Step 602 The AC sends the identifiers of multiple first EASs (or first EAS lists) to the third EAS.
  • Step 603-a The third EAS sends the second information to the EES.
  • the EES may obtain the second information from the third EAS during the EAS registration process.
  • the third EAS sends an EAS registration request (EAS registration request) to the EES.
  • the EAS registration request includes EAS configuration information (EAS profile), and the EAS configuration information includes the second information.
  • EES sends an EAS registration response (EAS registration response) to the third EAS.
  • the EAS configuration information also includes the identification of the third EAS (EAS ID) and the application context migration scenarios supported by the third EAS.
  • EAS registration process can also be replaced with an EAS update process, that is, the EAS registration request is replaced with an EAS update request (EAS update request), and the EAS registration response is replaced with an EAS update response (EAS update response).
  • EAS update request EAS update request
  • EAS update response EAS update response
  • Step 604-a AC sends the first information to EES.
  • the EES may obtain the first information from the AC based on the AC registration process and the EEC registration process.
  • the AC sends an AC registration request (AC registration request) to the EEC.
  • the AC registration request includes AC configuration information
  • the AC configuration information includes the first information.
  • the AC configuration information also includes application context migration scenarios supported by the AC.
  • the EEC sends an AC registration response (AC registration request) to the AC.
  • the EEC further sends an EEC registration request (EEC registration request) to the EES, where the EEC registration request includes the AC configuration information, that is, the first information.
  • EES sends an EEC registration response (EEC registration response) to EEC.
  • the above AC registration process can also be replaced by an AC update process, that is, the AC registration request is replaced by an AC update request (AC update request), and the AC registration response is replaced by an AC update response (AC update response).
  • the above EEC registration process can also be replaced by an EEC update process, that is, the EEC registration request is replaced by an EEC update request (EEC update request), and the EEC registration response is replaced by an EEC update response (EEC update response).
  • step 603-a and step 604-a is not limited.
  • Step 605-a EES determines whether the multiple application context migration scenarios include the application context migration scenario decided by EAS based on the second information and the first information.
  • Step 606-a EES selects a target application context migration scenario from multiple application context migration scenarios.
  • Step 607-a The EES sends the target application context migration scenarios to the AC, EEC, and multiple first EAS respectively.
  • the EES can send the target application context migration scenario to the AC through the EEC. That is, the EES first sends the target application context migration scenario to the EEC, and then the EEC sends the target application context migration scenario to the AC.
  • steps 603-a to 607-a please refer to the description in step 502, or refer to the description of case 2 in step 301.
  • Step 603-b The third EAS sends the second information to the EEC.
  • the third EAS may send the second information to the EEC through the EES, that is, the third EAS first sends the second information to the EES, and then the EES sends the second information to the EEC.
  • the EEC may obtain the second information based on the EAS registration process and the EEC registration process.
  • the third EAS sends an EAS registration request to the EES
  • the EAS registration request includes EAS configuration information
  • the EAS configuration information includes the second information.
  • the EAS configuration information also includes the identification of the third EAS and the application context migration scenarios supported by the third EAS.
  • the EES sends an EAS registration response to the third EAS.
  • the EES receives the EEC registration request from the EEC and sends an EEC registration response to the EEC, where the EEC registration response includes the second information.
  • the EEC registration response also includes the application context migration scenario supported by the EES, the identification of the third EAS, and the application context migration scenario supported by the third EAS.
  • the above-mentioned EAS registration process can also be replaced by an EAS update process, that is, the EAS registration request is replaced by an EAS update request, and the EAS registration response is replaced by an EAS update response.
  • the above EEC registration process can also be replaced by an EEC update process, that is, the EEC registration request is replaced by an EEC update request, and the EEC registration response is replaced by an EEC update response.
  • Step 604-b AC sends the first information to EEC.
  • the EEC may obtain the first information from the AC during the AC registration process.
  • the AC sends an AC registration request to the EEC
  • the AC registration request includes AC configuration information
  • the AC configuration information includes the first information.
  • the EEC sends an AC registration response to the AC.
  • the above AC registration process can also be replaced by an AC update process, that is, the AC registration request is replaced by an AC update request, and the AC registration response is replaced by an AC update response.
  • step 603-b and step 604-b is not limited.
  • Step 605-b The EEC determines whether the multiple application context migration scenarios include the application context migration scenario decided by the EAS based on the second information and the first information.
  • Step 606-b The EEC selects a target application context migration scenario from multiple application context migration scenarios.
  • Step 607-b The EEC sends the target application context migration scenarios to the AC, EEC, and multiple first EAS respectively.
  • the EEC may send the target application context migration scenario to the first EAS through the EES. That is, the EEC first sends the target application context migration scenario to the EES, and then the EES sends the target application context migration scenario to the first EAS.
  • steps 603-b to 607-b please refer to the description in step 502, or refer to the description of case 2 in step 301.
  • Figure 7 is a schematic flowchart of the method for determining the first application context migration scenario in the second implementation mode provided by this application.
  • terminology and technical solutions that are not described in detail in the method for determining the application context migration scenario shown in Figure 7, please refer to the descriptions in the relevant embodiments in Implementation Mode 1.
  • Step 701 The first entity receives first information.
  • step 301 For the first information and the description of the first entity receiving the first information, please refer to the description in step 301, step 604-a, or step 604-b.
  • the first entity may determine the identifiers of the multiple first EASs based on the first information.
  • the first entity may determine the identities of the multiple first EASs based on the first information. .
  • the first entity may also obtain the identities of multiple first EASs based on the first indication. For example, when the first entity is an EES, the EES may receive multiple first EAS identities from the AC or EEC. When the first entity is an EEC, the EEC may receive identities of multiple first EASs from the AC.
  • Step 701 is optional.
  • the first entity is an EEC
  • the first information may be pre-configured in the EEC.
  • multiple first EAS identifiers may be preconfigured in the EEC.
  • Step 702 The first entity sends multiple first EAS identifiers to the third EAS based on the first information.
  • the first entity may first receive an application context migration scenario supported by the third EAS from the third EAS. After determining that the third EAS has the decision-making function, the first entity sends multiple identifications of the first EAS to the third EAS.
  • the third EAS has a decision-making function.
  • the third EAS supports the application context migration scenario of EAS decision-making (such as application context migration scenario 4).
  • the plurality of first EASs include EAS1 to EAS5.
  • EAS1 supports application context migration scenario 1 to application context migration scenario 4, while EAS2 to EAS5 only support application context migration scenario 1 to application context migration scenario 3.
  • the first entity determines that EAS1 supports application context migration scenario 4, and sends multiple identifications of the first EAS to EAS1 (ie, the third EAS).
  • the first entity determines that none of EAS2 to EAS5 supports application context migration scenario 4, and may not send multiple first EAS identifiers to EAS2 to EAS5.
  • the first entity after determining the target application context migration scenario, the first entity sends multiple identifications of the first EAS to the third EAS based on the first information.
  • the first entity after determining the target application context migration scenario, the first entity further determines whether to send the identifiers of multiple first EASs to the third EAS based on the first information.
  • the first entity determines that the target application context migration scenario includes an application context migration scenario of EAS decisions (step 703 in Figure 7), the first entity further sends multiple first EASs to the third EAS based on the first information. logo.
  • the first entity may not send the identifiers of the multiple first EASs to the third EAS.
  • the first entity may send the target application context migration scenario and the identifiers of multiple first EASs to the third EAS through the same message, or may send the target application context migration scenario and multiple first EAS identities to the third EAS through two different messages. The identification of the first EAS.
  • the first entity may first send multiple first EAS identifiers to the third EAS based on the first information, and then determine the target application context migration scenario. At this time, the first entity may select a target application context migration scenario from a plurality of application context migration scenarios including application context migration scenarios of the EAS decision.
  • the first entity may first determine, based on the first information, that the application contexts in multiple first EASs need to be migrated together, and then determine the target application context migration scenario. For details, please refer to the steps. In 302, the first entity determines the relevant description of the target application context migration scenario.
  • the EES may send the target application context migration scenario to the multiple first EAS, EEC, and AC respectively.
  • the EES, AC, multiple first EASs and EEC can perform relevant actions in application context migration according to the target application context migration scenario.
  • the EEC may send the target application context migration scenarios to the multiple first EAS, EES, and AC respectively.
  • the EES, AC, multiple first EASs and EEC can perform relevant actions in application context migration according to the target application context migration scenario.
  • Figure 8 is a schematic flowchart of a method for determining the second application context migration scenario in implementation mode 2 provided by this application.
  • the method for determining the application context migration scenario shown in FIG. 8 is specifically a specific implementation of the method for determining the application context migration scenario shown in FIG. 7 .
  • For technical solutions that are not described in detail in the relevant embodiment of FIG. 8 please refer to the description in the relevant embodiment of FIG. 7 , or further refer to the description in the relevant embodiment of Implementation Mode 1.
  • Step 801 The AC is preconfigured with multiple first EAS identifiers. This step can be referred to the description in step 601.
  • Step 802-a AC sends first information to EEC. This step can be referred to the description in step 701.
  • step 802-a is an optional step.
  • Step 803-a The EEC sends multiple first EAS identifiers to the third EAS according to the first information.
  • Step 804-a the EEC determines the target application context migration scenario.
  • Step 805-a The EEC sends the target application context migration scenarios to the AC, EEC and multiple first EAS respectively.
  • steps 803-a to 805-a please refer to the description in step 702.
  • Step 802-b AC sends the first information to EES.
  • the AC may send the first information to the EES through the EEC, that is, the AC first sends the first information to the EEC, and then the EEC sends the first information to the EES.
  • This step can be referred to the description in step 701.
  • the EEC may also be configured with the first information, and the EES may directly receive the first information from the EEC.
  • Step 803-b The EES sends multiple first EAS identifiers to the third EAS according to the first information.
  • Step 804-b EES determines the target application context migration scenario.
  • Step 805-b The EES sends the target application context migration scenarios to the AC, EEC, and multiple first EAS respectively.
  • steps 803-b to 805-b please refer to the description in step 702.
  • Figure 9 is a schematic flowchart of a method for determining the third application context migration scenario in implementation mode 2 provided by this application.
  • the method for determining the application context migration scenario shown in FIG. 9 is specifically another specific implementation of the method for determining the application context migration scenario shown in FIG. 7 .
  • For technical solutions that are not described in detail in the relevant embodiment of FIG. 9 please refer to the description in the relevant embodiment of FIG. 7 , or further refer to the description in the relevant embodiment of Implementation Mode 1.
  • Step 901 The AC is preconfigured with multiple first EAS identifiers.
  • This step can be referred to the description in step 601.
  • Step 902-a AC sends first information to EEC.
  • step 902-a is an optional step.
  • step 902-a Contents not described in detail in step 902-a may also refer to the description in step 701.
  • Step 903-a EEC determines the target application context migration scenario.
  • Step 904-a The EEC sends the target application context migration scenario and the identifiers of multiple first EASs to the third EAS according to the first information.
  • the EEC can send the target application context migration scenario and the identifiers of multiple first EASs to the third EAS through the EES. That is, the EEC first sends the target application context migration scenarios and the identifiers of the multiple first EASs to the EES, and the EES then sends the target application context migration scenarios and the identifiers of the multiple first EASs to the third EAS. The third EAS sends the target application context migration scenario and multiple identifications of the first EAS.
  • the EES forwards the target application context migration scenario and the identifiers of multiple first EASs, it can also obtain the target application context migration scenario.
  • the EEC may also send target application context migration scenarios to the AC and other first EASs among the plurality of first EASs except the third EAS respectively.
  • the EES, AC, multiple first EASs and EEC can perform relevant actions in application context migration according to the target application context migration scenario.
  • step 903-a and step 904-a may also refer to the description in step 702 and step 703.
  • Step 902-b AC sends the first information to EES.
  • the AC may send the first information to the EES through the EEC, that is, the AC first sends the first information to the EEC, and then the EEC sends the first information to the EES.
  • the EEC can also be configured with the first information, and the EES directly receives the first information from the EEC.
  • step 902-b may also refer to the description in step 701.
  • Step 903-b EES determines the target application context migration scenario.
  • Step 904-b The EES sends the target application context migration scenario and the identifiers of multiple first EASs to the third EAS according to the first information.
  • the EES can also send target application context migration scenarios to the AC, other first EASs among the plurality of first EASs except the third EAS, and the EEC respectively.
  • the EES, AC, multiple first EASs and EEC can perform relevant actions in application context migration according to the target application context migration scenario.
  • step 903-b and step 904-b may also refer to the description in step 702 and step 703.
  • Figure 10 is a schematic flowchart of the method for determining the (1) application context migration scenario in the third implementation provided by this application.
  • FIG. 10 For technical solutions that are not described in detail in the method for determining the application context migration scenario shown in FIG. 10 , please refer to the descriptions in the relevant embodiments of Implementation Mode 1 and Implementation Mode 2.
  • Step 1001 The fourth EAS determines, based on the first information, that the application context migration scenario supported by the fourth EAS does not include the application context migration scenario decided by the EAS.
  • the first information please refer to the description of the first information in step 301.
  • the fourth EAS may be one or more of the plurality of first EASs.
  • the first information may be pre-configured in the fourth EAS, or the fourth EAS may receive the first information from the AC, EEC or EES.
  • the third EAS please refer to the third EAS to pre-configure the first information, or the third EAS may receive the first information from the AC, EEC Or the implementation of the first information of EES.
  • the fourth EAS determines that the application contexts in multiple first EASs need to be migrated together based on the first information, and further determines that the application context migration scenarios supported by the fourth EAS do not include the application context migration scenarios decided by the EAS.
  • the fourth EAS is configured to support application context migration scenario 1 to application context migration scenario 4.
  • the fourth EAS determines that application contexts in multiple first EASs need to be migrated together based on the first information, and then determines that the fourth EAS can support application context migration scenario 1 to application context migration scenario 3.
  • Step 1002 The fourth EAS sends the application context migration scenario supported by the fourth EAS.
  • the fourth EAS may send the application context migration scenario supported by the fourth EAS to the first entity.
  • the fourth EAS sends the application context migration scenario supported by the fourth EAS to the EES.
  • the fourth EAS may send the application context migration scenario supported by the fourth EAS to the EEC through the EES.
  • the first entity receives the application context migration scenario supported by the fourth EAS, and selects the target application context migration scenario according to the application context migration scenario supported by the fourth EAS (excluding the application context migration scenario decided by the EAS).
  • the first entity determines that the fourth EAS can support application context migration scenario 1 to application context migration scenario 3, and the first entity can select a target application context migration scenario from application context migration scenario 1 to application context migration scenario 3.
  • the implementation method of the first entity selecting the target application context migration scenario please refer to the description in step 302.
  • the first entity can select an application context migration scenario other than the application context migration scenario decided by EAS as the target application context migration scenario, that is, the target application context migration scenario selected by the first entity is the application context decided by EEC, AC or EES.
  • the target application context migration scenario selected by the first entity is the application context decided by EEC, AC or EES.
  • migrating scenarios it helps to migrate application contexts in multiple first EAS together, thereby avoiding service interruption during the application context migration process.
  • the EES may send the target application context migration scenario to the multiple first EAS, EEC, and AC respectively.
  • the EES, AC, multiple first EASs and EEC can perform relevant actions in application context migration according to the target application context migration scenario.
  • the EEC may send the target application context migration scenarios to the multiple first EAS, EES, and AC respectively.
  • the EES, AC, multiple first EASs and EEC can perform relevant actions in application context migration according to the target application context migration scenario.
  • Figure 11 is a schematic flowchart of the method for determining the (2) application context migration scenario in the third implementation mode provided by this application.
  • the method for determining the application context migration scenario shown in FIG. 11 is a specific implementation of the method for determining the application context migration scenario shown in FIG. 10 .
  • Step 1101 The AC is preconfigured with multiple first EAS identifiers.
  • Step 1102 The AC sends the identifiers of multiple first EASs to the fourth EAS.
  • the AC sends the identifiers of the multiple first EASs to all or part of the multiple first EASs.
  • the AC is connected to the fourth EAS, and the AC can directly send the identifiers of multiple first EASs to the fourth EAS.
  • the AC can send multiple first EAS identifiers to the fourth EAS through the EEC and EES.
  • the AC first sends multiple first EAS identifiers to the EEC, and the EEC then sends multiple first EAS identifiers to the EES.
  • the EES After receiving the identification of an EAS, the EES sends multiple identifications of the first EAS to the fourth EAS.
  • Step 1103-a The fourth EAS determines, based on the identifiers of the multiple first EASs, that the application context migration scenario supported by the fourth EAS does not include the application context migration scenario decided by the EAS. For details, please refer to the description in the relevant embodiments of step 1001.
  • Step 1104-a The fourth EAS sends the application context migration scenario supported by the fourth EAS to the EES.
  • Step 1105-a EES selects a target application context migration scenario based on the application context migration scenario supported by the fourth EAS.
  • Step 1106-a The EES sends the target application context migration scenarios to the AC, EEC, and multiple first EAS respectively.
  • the EES can send the target application context migration scenario to the AC through the EEC. That is, the EES first sends the target application context migration scenario to the EEC, and then the EEC sends the target application context migration scenario to the AC.
  • steps 1104-a to 1106-a please refer to the description in the relevant embodiments of step 1002.
  • Step 1103-b The fourth EAS determines, based on the identifiers of the multiple first EASs, that the application context migration scenario supported by the fourth EAS does not include the application context migration scenario decided by the EAS. Please refer to the description in relevant embodiments of step 1001.
  • Step 1104-b The fourth EAS sends the application context migration scenario supported by the fourth EAS to the EEC.
  • Step 1105-b The EEC selects a target application context migration scenario based on the application context migration scenario supported by the fourth EAS.
  • Step 1106-b The EEC sends the target application context migration scenarios to the AC, EES, and multiple first EAS respectively.
  • the EEC may send the target application context migration scenario to the first EAS through the EES.
  • steps 1104-b to 1106-b please refer to the description in the relevant embodiments of step 1002.
  • the AC may also be provided with services by other EASs besides multiple first EASs. It can be understood that the AC is provided with services by multiple second EASs, wherein the multiple first EASs are parts of the multiple second EASs.
  • game AC not only needs to be provided by graphics rendering EAS and chat function EAS, but also needs to be provided by game acceleration EAS.
  • the graphics rendering EAS and the chat function EAS are the first EAS, that is, there is a correlation between the application context of AC in the graphics rendering EAS and the application context of AC in the chat function EAS.
  • the application context in the game acceleration EAS can be independent of the application context in the graphics rendering EAS and chat function EAS.
  • the application context of AC in game acceleration EAS does not need to be migrated together with the application context in graphics rendering EAS and chat function EAS.
  • the first EAS can also be called linked EAS (linked EAS), that is, multiple first EASs are related to each other, that is, the application contexts of multiple first EASs are related to each other.
  • EASs other than the first EAS among the multiple second EASs may be called non-associated EASs (unlinked EASs).
  • Associated EAS and non-associated EAS are just exemplary names. Those skilled in the art can also make other names.
  • the first EAS can also be called a paired EAS (pair EAS).
  • the first EAS Other EAS can be called non-paired EAS (non-pair EAS).
  • the second EAS can be called associated EAS or common service EAS, etc.; for another example, the first EAS can also be called co-migration EAS. (ACR-together EAS), the second EAS can also be called a non-co-migration EAS (non-ACR-together EAS), at this time the second EAS can also be called an associated EAS or a common service EAS, etc.
  • the first EAS list composed of the identifier of the first EAS can also be called a linked EAS list (linked EAS list), a paired EAS list (pair EAS list), or a jointly migrated EAS list (ACR-together EAS list). )etc.
  • the application context in the non-linked EAS can be independent of the application context in the linked EAS.
  • the application context in linked EAS is migrated together, the application context in non-linked EAS does not need to be migrated, or does not need to be migrated together with the application context in linked EAS.
  • context migration occurs in a non-linked EAS, the non-linked EAS can only migrate its own local application context without triggering other non-linked EAS or linked EAS to migrate the application context.
  • the AC may be pre-configured with identifiers of multiple second EASs, and the AC may send the identifiers of multiple second EASs to the first entity, where the identifiers of the multiple second EASs may further include the first Information (specifically, the identifiers of multiple first EAS).
  • the first entity may obtain the identities of multiple first EASs from the identities of multiple second EASs.
  • the AC sending multiple second EAS identifiers to the first entity please refer to the implementation of the AC sending multiple first EAS identifiers to the first entity in step 301.
  • the EEC may also be pre-configured with multiple second EAS identifiers, and the first entity may obtain multiple first EAS identifiers from the multiple second EAS identifiers.
  • the third EAS may obtain the identities of multiple second EASs from the AC or EEC, and send the second instruction to the first entity based on the identities of the multiple first EASs among the identities of the multiple second EASs.
  • the third EAS is preconfigured with identifiers of multiple second EASs, and the third EAS sends the second instruction to the first entity based on the identifiers of the multiple first EASs among the identifiers of the multiple second EASs.
  • the AC may be pre-configured with the identifiers of multiple second EASs, and the AC may send the identifiers of multiple second EASs to the first entity, where the identifiers of the multiple second EASs may further include the first information.
  • the first entity may obtain the identities of multiple first EASs from the identities of multiple second EASs.
  • the first entity sends the identifiers of multiple second EASs to the third EAS, or sends the identifiers of multiple first EASs.
  • the third EAS obtains the identifiers of multiple first EASs.
  • the AC may be pre-configured with identifiers of multiple second EASs, and the AC may send the identifiers of multiple second EASs to the fourth EAS, where the identifiers of the multiple second EASs may further include the first Information (specifically, the identifiers of multiple first EAS).
  • the fourth EAS acquires the identifiers of multiple first EASs from the identifiers of multiple second EASs, and determines that the application context migration scenario supported by the fourth EAS does not include the application context migration scenario decided by the EAS.
  • the first entity may obtain the application context migration scenarios supported by each of the EES, AC, multiple second EAS, and EEC, and then based on the applications supported by these entities.
  • Context migration scenarios determine the application context migration scenarios jointly supported by the multiple entities.
  • the first entity determines the target application context migration scenario from the application context migration scenarios jointly supported by multiple entities based on any one of the above implementation methods one to three.
  • the target application context migration scenario may be sent to multiple second EASs.
  • the EEC can send target application context migration scenarios to multiple second EAS, AC, and EES.
  • multiple second EAS, AC, EES, and EEC can send target application contexts according to the target application context.
  • Migration scenario perform related actions in application context migration.
  • the EES can send the target application context migration scenario to multiple second EAS, AC, and EEC.
  • the multiple second EAS, AC, EES, and EEC can migrate the scenario according to the target application context. Perform related actions in application context migration.
  • the multiple first EASs may also be all of the multiple second EASs, that is, the multiple first EASs are multiple second EASs, and the application contexts in the multiple second EASs all have an associated relationship and need to be migrated together.
  • the multiple first EASs are EASs that provide services for the same AC. Therefore, for this application, the first EAS and the second EAS are the same and can be used interchangeably, and their names can also be the same.
  • Embodiment 1 is a more specific implementation of FIG. 6 .
  • Step 1201 is the specific implementation of step 602
  • step 1202 and step 1203 are the specific implementation of step 603-a
  • steps 1205 to 1208 are the implementation of step 604-a
  • step 1209 is a specific implementation of step 605-a and step 606-a
  • step 1204, step 1210 to step 1213 are specific implementations of step 607-a.
  • Step 1201 The AC sends the first EAS list to the third EAS.
  • Step 1202 The third EAS sends an EAS registration request to the EES.
  • the EAS registration request includes EAS configuration information (EAS profile), and the EAS configuration information may include the identification of the third EAS (EAS ID), the second information, and the application context migration scenario supported by the third EAS.
  • the second information is specifically the first EAS list.
  • Step 1203 EES sends an EAS registration response to the third EAS.
  • Step 1204 The EEC and the third EAS subscribe to the target application context migration scenario to the EES respectively.
  • Step 1205 The AC is preconfigured with AC configuration information.
  • the AC configuration information may include application context migration scenarios supported by the AC, an identity of the AC, and the first EAS list.
  • Step 1206 The AC sends an AC registration request to the EEC, where the AC registration request includes AC configuration information (ie, includes the first EAS list).
  • Step 1207 The EEC sends an AC registration response to the AC.
  • Step 1208 The EEC sends an EEC registration request to the EES, where the EEC registration request includes AC configuration information (that is, including the first EAS list) and application context migration scenarios supported by the EEC.
  • AC configuration information that is, including the first EAS list
  • Step 1209 EES determines that the application contexts of multiple first EASs need to be migrated together according to the first EAS list in the AC configuration information. Based on the application context migration scenarios supported by AC, EEC, EES and multiple first EASs, EES determines the application context migration scenarios that include EAS decisions among the multiple application context migration scenarios. EES then selects the target application from the multiple application context migration scenarios. Context migration scenario.
  • Step 1210 The EES sends an application context migration scenario notification to the third EAS, where the application context migration scenario notification includes the target application context migration scenario.
  • Step 1211 EES sends an EEC registration response to EEC, where the EEC registration response includes the target application context migration scenario.
  • Step 1212 AC subscribes to the EEC for the target application context migration scenario.
  • Step 1213 The EEC sends an application context migration scenario notification to the AC.
  • the application context migration scenario notification includes the target application context migration scenario.
  • This Embodiment 2 is specifically another specific implementation manner of FIG. 6 .
  • Step 1301 is a specific implementation of step 602
  • steps 1302 to 1305 are a specific implementation of step 603-b
  • step 1306 is a specific implementation of step 601
  • steps Step 1307 and step 1308 are the specific implementation methods of step 604-b
  • step 1309 is the specific implementation method of step 605-b and step 606-b
  • steps 1310 to step 1315 are the specific implementation methods of step 607-b.
  • Step 1301 The AC sends the first EAS list to the third EAS.
  • Step 1302 The third EAS sends an EAS registration request to the EES.
  • the EAS registration request includes second information, and the second information is specifically the first EAS list.
  • Step 1303 EES sends an EAS registration response to the third EAS.
  • Step 1304 the EEC sends an EEC registration request to the EES.
  • Step 1305 The EES sends an EEC registration response to the EEC.
  • the EEC registration response may include the application context migration scenario supported by the EES, the application context migration scenario supported by the third EAS, and the first EAS list.
  • Step 1306 The AC is pre-configured with AC configuration information, where the AC configuration information may include application context migration scenarios supported by the AC, an identity of the AC, and the first EAS list.
  • Step 1307 The AC sends an AC registration request to the EEC, where the AC registration request includes AC configuration information (ie, includes the first EAS list).
  • Step 1308 The EEC sends an AC registration response to the AC.
  • Step 1309 The EEC determines that the application contexts of multiple first EASs need to be migrated together according to the first EAS list in the AC configuration information. Based on the application context migration scenarios supported by AC, EEC, EES and multiple first EASs, EES determines the application context migration scenarios that include EAS decisions among the multiple application context migration scenarios. EES then selects the target from the multiple application context migration scenarios. Application context migration scenario.
  • Step 1310 The EEC sends an EAS discovery request to the EES, and the EAS discovery request includes the target application context migration scenario.
  • Step 1311 EES sends an EAS discovery response to EEC.
  • Step 1312 The third EAS subscribes to the target application context migration scenario to the EES.
  • Step 1313 The EES sends an application context migration scenario notification to the third EAS, where the application context migration scenario notification includes the target application context migration scenario.
  • Step 1314 AC subscribes to the EEC for the target application context migration scenario.
  • Step 1315 The EEC sends an application context migration scenario notification to the AC.
  • the application context migration scenario notification includes the target application context migration scenario.
  • This Embodiment 3 is specifically a specific implementation manner of FIG. 8 .
  • Step 1402 is a specific implementation of step 801
  • steps 1403 to 1405 are specific implementations of step 802-b
  • steps 1406 and 1407 are implementations of step 803-b
  • step 1408 is a specific implementation of step 804-b
  • step 1401, step 1409 to step 1412 are specific implementations of step 805-b.
  • Step 1401 The EEC and the third EAS subscribe to the target application context migration scenario to the EES respectively.
  • Step 1402 The AC is preconfigured with AC configuration information.
  • the AC configuration information includes application context migration scenarios supported by the AC, an identity of the AC, and a first EAS list.
  • the first EAS list may be a list composed of identities of multiple first EASs.
  • Step 1403 The AC sends an AC registration request to the EEC, where the AC registration request includes AC configuration information.
  • Step 1404 The EEC sends an AC registration response to the AC.
  • Step 1405 The EEC sends an EEC registration request to the EES, where the EEC registration request includes AC configuration information and application context migration scenarios supported by the EEC.
  • Step 1406 The third EAS sends an EAS registration request to the EES, where the EAS registration request includes EAS configuration information.
  • the EAS configuration information includes the identification of the third EAS and the application context migration scenarios supported by the third EAS.
  • Step 1407 The EES sends an EAS registration response to the third EAS, where the EAS registration response includes the AC's identity and the first EAS list.
  • Step 1408 EES determines that multiple first EASs need to migrate the application context together according to the first EAS list in the AC configuration information. Based on the application context migration scenarios supported by AC, EEC, EES and multiple first EASs, EES determines the application context migration scenarios that include EAS decisions among the multiple application context migration scenarios. EES then determines the target from the multiple application context migration scenarios. Application context migration scenario.
  • Step 1409 The EES sends an application context migration scenario notification to the third EAS, where the application context migration scenario notification includes the target application context migration scenario.
  • Step 1410 EES sends an EEC registration response to EEC, where the EEC registration response includes the target application context migration scenario.
  • Step 1411 AC subscribes to the EEC for the target application context migration scenario.
  • Step 1412 The EEC sends an application context migration scenario notification to the AC.
  • the application context migration scenario notification includes the target application context migration scenario.
  • This Embodiment 4 is specifically a specific implementation manner of FIG. 9 .
  • Steps 1504 to 1507 are the specific implementation of step 902-b
  • step 1508 is the specific implementation of step 903-b
  • steps 1501 to 1503 is the specific implementation of step 904-b.
  • Step 1501 The third EAS sends an EAS registration request to the EES, where the EAS registration request includes EAS configuration information, and the EAS configuration information includes the identification of the third EAS and the application context migration scenario supported by the third EAS.
  • Step 1502 EES sends an EAS registration response to the third EAS.
  • Step 1503 The EEC and the third EAS subscribe to the target application context migration scenario to the EES respectively.
  • Step 1504 The AC is pre-configured with AC configuration information, where the AC configuration information includes application context migration scenarios supported by the AC, an identity of the AC, and the first EAS list.
  • Step 1505 The AC sends an AC registration request to the EEC, where the AC registration request includes AC configuration information.
  • Step 1506 The EEC sends an AC registration response to the AC.
  • Step 1507 The EEC sends an EEC registration request to the EES, where the EEC registration request includes AC configuration information and application context migration scenarios supported by the EEC.
  • Step 1508 EES determines that the application contexts of multiple first EASs need to be migrated together according to the first EAS list in the AC configuration information.
  • the EES determines the target application context migration scenario based on the application context migration scenarios supported by the AC, EEC, EES, and multiple first EASs.
  • Step 1509 The EES sends an application context migration scenario notification to the third EAS.
  • the application context migration scenario notification includes the target application context migration scenario and the first EAS list.
  • Step 1510 EES sends an EEC registration response to EEC, where the EEC registration response includes the target application context migration scenario.
  • Step 1511 AC subscribes to the EEC for the target application context migration scenario.
  • Step 1512 The EEC sends an application context migration scenario notification to the AC.
  • the application context migration scenario notification includes the target application context migration scenario.
  • This Embodiment 5 is specifically a specific implementation manner of FIG. 11 .
  • Step 1602 is a specific implementation of step 1101
  • steps 1603 to 1606 are a specific implementation of step 1102
  • step 1607 is a specific implementation of step 1103-a
  • steps Step 1608 and step 1609 are the specific implementation methods of step 1104-a
  • step 1610 is the specific implementation method of step 1105-a
  • step 1601 step 1611 to step 1614 are the specific implementation methods of step 1106-a.
  • Step 1601 The EEC and the fourth EAS subscribe to the target application context migration scenario to the EES respectively.
  • Step 1602 The AC is preconfigured with AC configuration information.
  • the AC configuration information includes application context migration scenarios supported by the AC, an identity of the AC, and a first EAS list.
  • the first EAS list may be a list composed of identities of multiple first EASs.
  • Step 1603 The AC sends an AC registration request to the EEC, where the AC registration request includes AC configuration information (that is, including the first EAS list).
  • Step 1604 The EEC sends an AC registration response to the AC.
  • Step 1605 The EEC sends an EEC registration request to the EES, where the EEC registration request includes AC configuration information (that is, including the first EAS list) and application context migration scenarios supported by the EEC.
  • AC configuration information that is, including the first EAS list
  • Step 1606 the EES sends an AC information notification (AC information notification) to the fourth EAS.
  • the AC information notification may include the first EAS list.
  • Step 1607 The fourth EAS determines, based on the first EAS list, that the application context migration scenario supported by the fourth EAS does not include the application context migration scenario decided by the EAS.
  • Step 1608 The fourth EAS sends an EAS registration request to the EES.
  • the EAS registration request includes EAS configuration information.
  • the EAS configuration information includes the identification of the fourth EAS and the application context migration scenarios supported by the fourth EAS.
  • Step 1609 EES sends an EAS registration response to the fourth EAS.
  • Step 1610 EES determines the target application context migration scenario based on the application context migration scenarios supported by the AC, EEC, EES, and multiple first EASs.
  • Step 1611 The EES sends an application context migration scenario notification to the fourth EAS, where the application context migration scenario notification includes the target application context migration scenario.
  • Step 1612 EES sends an EEC registration response to EEC, and the EEC registration response includes the target application context migration scenario.
  • Step 1613 AC subscribes to the EEC for the target application context migration scenario.
  • Step 1614 The EEC sends an application context migration scenario notification to the AC.
  • the application context migration scenario notification includes the target application context migration scenario.
  • the first entity can also be replaced by EEC.
  • the difference lies in whether the first entity communicates directly with the first EAS or indirectly communicates through the EES; and the difference between the first entity and the AC Is it direct communication or indirect communication through EEC. And the specific messages differ between entities.
  • the registration request can be replaced with an update request (update request), and the registration response can be replaced with an update response (update response).
  • the EAS registration request is replaced by an EAS update request (EAS update request)
  • the EAS registration response is replaced by an EAS update response (EAS update response)
  • the above information can also be carried in other types of messages, which is not limited in this application.
  • the first entity may further determine whether the application context migration of the EAS decision is included in the multiple application context migration scenarios based on the capability information of multiple first EASs or based on the capability information of the second entity. scenario (or called an application context migration scenario decided by the EAS, an application context migration scenario decided by the first EAS), and then select a target application context migration scenario from the multiple application context migration scenarios.
  • implementation method 1 can include implementation method 1 and implementation method 2:
  • Implementation Mode 1 The first entity determines, based on the capability information of multiple first EASs, whether there is a first EAS among the multiple first EASs that has the ability to process the migration of application contexts in associated EASs together. Subsequently, the first entity determines whether the multiple application context migration scenarios include the EAS decision-making application context migration scenario, and selects the target application context migration scenario from the multiple application context migration scenarios.
  • Step 1701 The first entity obtains capability information of multiple first EASs.
  • the first entity receives capability information of multiple first EASs.
  • the first entity can be EEC or EES.
  • the EEC receives the capability information of multiple first EASs forwarded by the EES; when the first entity is an EES, the EES receives capabilities information from each of the multiple first EASs. , the capability information of the first EAS, thereby obtaining the capability information of the multiple first EASs.
  • the multiple first EASs are associated EASs, that is, the application contexts in the multiple first EASs are associated. Furthermore, the application contexts in the associated EASs (or EASs with associated relationships) need to be migrated together. Where multiple first EASs, associated EASs, and application contexts need to be migrated together, please refer to the description in step 301 above, and also refer to the supplementary description after the relevant embodiment in Figure 11 above.
  • the first entity may also receive the first information, and determine, based on the first information, that the multiple first EASs are associated EASs, or determine that the application contexts of the multiple first EASs need to be migrated together.
  • the first information the way in which the first entity receives the first information, and the way in which the first entity determines that the application contexts of multiple first EASs need to be migrated together, please refer to the description in step 301 above.
  • the capability information of the first EAS indicates whether the first EAS has the capability of processing application contexts in associated EASs to be migrated together.
  • the capability information of the first EAS indicates whether the first EAS has one or more of the following capabilities 1 to 4:
  • Capability 1 the ability to obtain the identification of multiple first EAS. In other words, the ability to obtain the identity of the associated EAS, or the ability to obtain the identity of the EAS that needs to be migrated together with the application context, etc.
  • the first EAS may receive the identifiers of multiple first EASs from the AC, or receive the identifiers of multiple first EASs from the EEC, or be pre-configured with the identifiers of multiple first EASs, or pre-store multiple first EAS identifiers. The identification of the first EAS. In this way, the first EAS has the ability to obtain the identifiers of multiple first EASs.
  • Capability 2 the ability to send migration notifications to other EASs other than the first EAS among multiple first EASs (that is, other first EASs).
  • capability 2 is the ability to send migration notifications to other EASs other than the first EAS through the application layer between the first EAS and the plurality of first EASs.
  • Capability 3 the ability to receive migration notifications from EASs other than the first EAS among multiple first EASs.
  • capability 3 is the ability to receive migration notifications from other EASs other than the first EAS through the application layer between the first EAS and the other EASs among the plurality of first EASs.
  • the migration notification is used to trigger application context migration, that is, after an EAS receives the migration notification, the application context migration is performed based on the triggering of the migration notification.
  • EAS1 sends a migration notification to EAS2, and EAS2 performs application context migration based on the triggering of the migration notification.
  • EAS1 has the ability to send migration notifications to other EASs in multiple first EASs (ie, capability 2)
  • EAS2 has the ability to receive migration notifications from other EASs in multiple first EASs (ie, capability 3).
  • Capability 4 the ability to support application context migration scenarios decided by the first EAS.
  • the configuration information of the first EAS includes the application context migration scenario supported by the first EAS, and the application context migration scenario supported by the first EAS includes the application context migration scenario decided by the first EAS, it means that the first EAS EAS is capable of 4.
  • Step 1702 The first entity determines corresponding target application context migration scenarios for the plurality of first EASs based on the capability information of the plurality of first EASs.
  • the first entity determines whether the target application context migration scenario includes the application context migration scenario decided by the first EAS based on the capability information of multiple first EASs.
  • the target application context migration scenario includes the application context migration scenario decided by the first EAS.
  • the first entity determines the target application context migration.
  • the scenario does not include the application context migration scenario decided by the first EAS.
  • the first entity determines whether the first EAS has the ability to process application contexts in associated EASs to be migrated together based on the capability information of the first EAS, specifically, the first entity determines whether the first EAS has the capability to process the migration of application contexts in the associated EAS based on the capability information of the first EAS. Whether an EAS possesses one or more of the above capabilities 1, 2 and 4. When the first entity determines that the first EAS has one or more of the above capabilities 1, 2, and 4, it determines that the first EAS has the ability to process the migration of application contexts in the associated EAS together.
  • the first entity determines that the first EAS has the first capability, it determines that the first EAS has the capability to process the application context migration in the associated EAS together; the first entity determines that the first EAS does not have the first capability. At this time, it is determined that the first EAS does not have the ability to process the migration of application contexts in the associated EAS together.
  • the first ability is one of ability 1, ability 2 and ability 4.
  • the first capability is capability 1.
  • the first entity determines that the first EAS has capability 1, it is determined that the first EAS has the capability to process the application context migration in the associated EAS together; when the first entity determines that the first EAS does not When capability 1 is present, it is determined that the first EAS does not have the ability to process the migration of application contexts in associated EASs together.
  • the first ability is ability 2 or ability 4
  • the implementation method is similar to the above-mentioned ability 1.
  • the above-mentioned “ability 1" can be replaced with “ability 2", or the above-mentioned “ability 1" can be replaced with "ability 3".
  • the first entity may also determine that the first EAS has the ability to process the migration of application contexts in the associated EAS together when determining that the first EAS has the first capability group.
  • the first entity may determine that the first EAS does not have the first capability.
  • the first ability group is a combination of certain items among ability 1, ability 2 and ability 4.
  • the first capability group consists of capability 1 and capability 2.
  • the first ability group can also be other combinations of ability 1, ability 2 and ability 4. The implementation of these other combinations is similar to the above-mentioned combination of ability 1 and ability 2.
  • an ability group can be understood by replacing the above-mentioned "ability 1 and ability 2" with “ability 2 and ability 4", and replacing the above-mentioned "ability 1 or ability 2" with "ability 2 or ability 4".
  • the capability information of the first EAS may also be used to indicate whether the first EAS has other capabilities (such as capability 3) to indicate whether the first EAS has the capability to process the migration of application contexts in associated EASs together, which is not limited by this application.
  • the first EAS used for decision-making is one of multiple first EASs.
  • the first EAS here may be called the fifth EAS
  • the EASs other than the fifth EAS among the multiple first EASs may be called the sixth EAS.
  • the sixth EAS is an EAS among the plurality of first EASs that performs application context migration based on the trigger of the fifth EAS.
  • the sixth EAS may be one or more.
  • the first entity can not only determine whether the fifth EAS possesses one or more of the above capabilities 1, 2, and 4 based on the capability information of the fifth EAS, but also determine whether the fifth EAS has one or more of the above capabilities 1, 2, and 4 based on the capability information of the sixth EAS. Capability information to determine whether the sixth EAS has the above capabilities3. For example, if the first entity determines that the fifth EAS has one or more of the above capabilities 1, 2, and 4, and the sixth EAS has the above capability 3, it determines that the target application context migration scenario includes the first The application context migration scenario decided by the EAS (or, in other words, the application context migration scenario decided by the fifth EAS), that is, it is determined that the fifth EAS can instruct the sixth EAS to perform application context migration together.
  • the first entity determines the target application context migration scenario based on the capability information of multiple first EASs, it may specifically include the following steps a and b:
  • Step a The first entity determines whether the multiple (candidate) application context migration scenarios include the application context migration scenario of the fifth EAS decision based on the capability information of the multiple first EASs.
  • the first entity determines, based on the capability information of multiple first EASs, that one of the multiple first EASs (that is, the fifth EAS) has the ability to process the migration of application contexts in the associated EASs together.
  • the first entity determines that the multiple application context migration scenarios include the application context migration scenario decided by the fifth EAS.
  • the first entity determines based on the capability information of multiple first EASs that none of the multiple first EASs has the ability to process the migration of application contexts in associated EASs together, the first entity determines that the multiple application contexts The migration scenario does not include the application context migration scenario decided by the first EAS.
  • Step b The first entity determines corresponding target application context migration scenarios for multiple first EASs from multiple application context migration scenarios.
  • step b please refer to the description in step 302.
  • the first entity determines the target application context migration scenario from the multiple application context migration scenarios, and the determination determines
  • the target application context migration scenario may include an application context migration scenario decided by the fifth EAS.
  • the method also includes: the first entity sends a target application context migration scenario.
  • the first entity sends a target application context migration scenario.
  • the migration scenario of the target application context sent by the first entity please refer to the description in the relevant embodiment of Figure 5 above.
  • the first entity determines whether there is a certain first EAS (i.e., the fifth EAS) among the plurality of first EASs that is capable of processing the application context migration in the associated EASs together based on the capability information of the multiple first EASs. capability, and then the first entity determines whether the target application context migration scenario includes the application context migration scenario decided by the first EAS (that is, the application context migration scenario decided by the fifth EAS). In this way, when there is a fifth EAS among multiple first EASs, the fifth EAS can instruct other first EASs (ie, the sixth EAS) to perform application context migration together. Correspondingly, the first entity can determine the target application context.
  • the migration scenario includes the application context migration scenario decided by the fifth EAS, which helps avoid service interruption during the application context migration process.
  • Implementation Mode 2 The first entity determines whether the second entity has the ability to process and migrate the application context in the associated EAS together based on the capability information of the second entity. Subsequently, the first entity determines whether the multiple application context migration scenarios include the application context migration scenario decided by the EAS (that is, the application context migration scenario decided by the first EAS, or the application context migration scenario decided by the first EAS), and from Select a target application context migration scenario among the multiple application context migration scenarios.
  • Step 1801 The first entity obtains the capability information of the second entity.
  • the one second entity is AC, EEC, or EES
  • there are two second entities and the two second entities are respectively AC and EEC, or AC and EES, or EEC and EES.
  • the first entity and the second entity are the same entity or different entities.
  • the first entity may obtain the capability information of the first entity.
  • the first entity obtains the capability information of the first entity from the configuration of the first entity.
  • the first entity may receive the capability information of the second entity.
  • the EEC receives the capability information of the AC from the AC
  • the EEC receives the capability information from the EES.
  • Capability information of EES when the first entity is EES and the second entity is AC, EES receives the capability information of AC forwarded by EEC; when the first entity is EES and the second entity is EEC, EES receives the capability information from EEC , EEC capability information.
  • the capability information of the second entity may be used to indicate whether the second entity has the capability to process the migration of application contexts in the associated EAS together.
  • the second entity's ability to process the application context in the associated EAS and migrate it together is different from the first EAS's ability to process the application context in the associated EAS to migrate together in the above implementation mode 1.
  • the capability information of the second entity indicates whether the second entity supports one or more of the following capabilities a to capability c:
  • Capability a the ability to obtain the identities of multiple first EASs. In other words, the ability to obtain the identity of the associated EAS, or the ability to obtain the identity of the EAS that needs to be migrated together with the application context, etc.
  • the second entity is the AC, and multiple first EAS identities are configured in the AC.
  • the second entity is an EEC, and the EEC is configured with the identities of multiple first EASs, or the EEC receives the identities of multiple first EASs from the AC.
  • the second entity is an EES, and the EES is configured with the identities of multiple first EASs, or the EES receives the identities of multiple first EASs from the EEC, where the identities of the multiple first EASs may be
  • the identifiers configured in the EEC and sent to the EES, or the identifiers of the multiple first EASs may be configured in the AC and forwarded by the EEC to the EES. In this way, the second entity has the ability to obtain the identities of multiple first EASs.
  • Capability b supports application context migration scenarios decided by the first EAS.
  • the configuration information of the second entity includes the application context migration scenario supported by the second entity, and the application context migration scenario supported by the second entity includes the application context migration scenario decided by the first EAS.
  • Capability c receive an indication of triggering a migration notification from one of the first EASs among multiple first EASs, and send migration notifications to other first EASs among the multiple first EASs based on the indication of triggering a migration notification from the first EAS. ability. Among them, migration notification is used to trigger application context migration.
  • the capability c of the second entity is explained as follows:
  • the capability c possessed by the AC is specifically that the AC can receive an indication triggering a migration notification from one of the multiple first EASs through the application layer, and based on the indication, send notifications to other first EASs.
  • the AC receives an instruction that triggers the migration notification.
  • the AC subscribes to the event that triggers the application context migration of the first EAS.
  • the AC can receive the event that triggers the application context migration. That is, an instruction from the first EAS to trigger the migration notification is received.
  • the EEC has the capability c. Specifically, the EEC can receive an instruction to trigger a migration notification from one of the multiple first EASs through the AC, and then send the instruction to the multiple first EASs through the AC.
  • the other first EAS has the ability to send migration notifications.
  • EEC and AC communicate through the EDGE-5 interface, and EAS and AC communicate through the application layer. That is, the AC receives the instruction to trigger the migration notification from one of the multiple first EASs through the application layer, and then sends the instruction to trigger the migration notification to the EEC through the EDGE-5 interface; the EEC receives the instruction to trigger the migration notification. Afterwards, a migration notification is sent to the AC through the EDGE-5 interface, and then the AC sends a migration notification to other first EASs among the plurality of first EASs through the application layer.
  • the capability c possessed by the EEC is specifically the ability of the EEC to receive an instruction to trigger a migration notification from one of the multiple first EASs through the EES, and to send migration notifications to other first EASs through the EES.
  • EEC and EES communicate through the EDGE-1 interface, and EAS and EES communicate through the EDGE-3 interface. That is, the EES receives the instruction to trigger the migration notification from one of the multiple first EASs through the EDGE-3 interface, and then sends the instruction to trigger the migration notification to the EEC through the EDGE-1 interface; the EEC receives the trigger migration notification After the instruction, a migration notification is sent to the EES through the EDGE-1 interface, and then the EES sends a migration notification to other first EASs among the multiple first EASs through the EDGE-3 interface.
  • the capability c possessed by the EES is specifically that the EES can receive instructions that trigger a migration notification from one of the multiple first EASs through the AC and EEC, and send instructions to other first EASs through the AC and EEC.
  • the first EAS has the ability to send migration notifications.
  • EES and EEC communicate through the EDGE-1 interface, EEC and AC communicate through the EDGE-5 interface, and EAS and AC communicate through the application layer. That is, the AC receives the instruction to trigger the migration notification from one of the multiple first EASs through the application layer, and then sends the instruction to trigger the migration notification to the EEC through the EDGE-5 interface; the EEC then sends the instruction to the EEC through the EDGE-1 interface. EES sends the indication that triggers the migration notification.
  • the EES sends a migration notification to the EEC through the EDGE-1 interface.
  • the EEC sends a migration notification to the AC through the EDGE-5 interface.
  • the AC sends a migration notification to other first EASs through the application layer.
  • First EAS sends migration notification.
  • the capability c possessed by the EES is specifically the ability of the EES to receive an instruction to trigger a migration notification from one of the first EASs among the plurality of first EASs, and to send migration notifications to other first EASs.
  • the EES has the ability to receive an instruction to trigger a migration notification from a first EAS among multiple first EASs through an EDGE-3 interface, and to send migration notifications to other first EASs through an EDGE-3 interface.
  • Step 1802 The first entity determines a corresponding target application context migration scenario for at least one first EAS among the plurality of first EASs based on the capability information of the second entity.
  • the first entity determines corresponding target application context migration scenarios for all first EASs in the plurality of first EASs (ie, the plurality of first EASs) based on the capability information of one or more second entities.
  • the first entity determines that one of the multiple second entities (recorded as the third entity) has the above-mentioned capability a based on the capability information of the multiple second entities. When one or more of the capabilities c is reached, it is determined that the third entity has the ability to process and migrate the application context in the associated EAS together.
  • the first entity determines corresponding target application context migration scenarios for the plurality of first EASs, including application context migration scenarios decided by the first EAS.
  • the first entity determines that the second entity possesses one or more of the above capabilities a to c based on the capability information of the second entity, that is, determines that the second entity possesses one or more of the capabilities a to c.
  • the second entity has the ability to process application contexts in associated EASs to be migrated together, and then the first entity determines corresponding target application context migration scenarios for multiple first EASs, including the application context migration scenarios decided by the first EAS.
  • the second entity here can also be called the third entity.
  • the first entity determines that the second entity has the second capability, it determines that the second entity has the capability to process the application context in the associated EAS and migrate it together.
  • the first entity determines that the second entity does not have the second capability, it determines that the second entity does not have the capability to process the migration of application contexts in the associated EAS together.
  • the second ability is one of ability a, ability b and ability c.
  • the second capability is capability a.
  • the first entity determines that the second entity has capability a, it determines that the second entity has the ability to process the application context in the associated EAS and migrate it together; when the first entity determines that the first EAS does not When it has capability a, it is determined that the second entity does not have the ability to process the migration of the application context in the associated EAS together.
  • Ability b and ability c are similar to the above-mentioned ability a. The above-mentioned “ability a" can be understood by replacing “ability b", or the above-mentioned “ability a” can be understood by “ability c".
  • the first entity determines that the second entity possesses the second capability group, it determines that the second entity has the ability to process the migration of application contexts in the associated EAS together.
  • the first entity determines that the second entity does not possess any capability in the second capability group, it determines that the second entity does not have the capability to process the migration of application contexts in the associated EAS together.
  • the second ability group is a combination of certain items among ability a, ability b and ability c.
  • the second capability group consists of capability a and capability b.
  • the first entity determines that the second entity has capability a and capability b, it is determined that the second entity has the ability to process the application context in the associated EAS and migrate together; when When the first entity determines that the second entity does not have capability a or capability b, it determines that the first EAS does not have the capability to process the migration of application contexts in the associated EAS together.
  • the implementation of other combinations of capabilities a to capability c is similar to the above. For example, for the second capability group composed of capability a and capability c, the above “capability a and capability b" can be replaced by "capacity a and capability c", and Replace the above "ability a or ability b" with “ability a or ability c" to understand.
  • the first entity determines corresponding targets for the plurality of first EASs based on the capability information of one or more second entities and the application context migration scenarios respectively supported by the plurality of first EASs.
  • Application context migration scenario Specifically, when the application context migration scenario supported by a first EAS (denoted as the fifth EAS) among the plurality of first EAS includes: the application context migration scenario of the first EAS decision (that is, the application context of the fifth EAS decision) Migration scenario); and the application context migration scenarios supported by other EASs (denoted as the sixth EAS) among the multiple first EASs except the one first EAS include: triggered by third entity detection (also called decision-making ) application context migration scenario; and the third entity satisfies one or more of the above capabilities a to c, the first entity determines the corresponding target application context migration scenario for multiple first EASs including the first The target application context migration scenario of the EAS decision (ie, the application context migration scenario of the fifth EAS decision).
  • the capability ie, the application
  • the fifth EAS supports the application context migration scenario decided by the fifth EAS. It can be understood that the fifth EAS can detect the trigger and decide the application context migration. When the fifth EAS determines that application context migration is needed, it can transfer the application context to the third entity. An instruction to trigger the migration notification is sent to instruct the third entity to send the migration notification to the sixth EAS.
  • the sixth EAS supports application context migration scenarios triggered by third entity detection. It can be understood that the sixth EAS can receive a migration notification from the third entity and perform application context migration in response to the migration notification.
  • the first entity may also receive multiple application context migration scenarios supported by the first EAS. Specifically, when the first entity is an EEC, the EEC receives the application context migration scenarios supported by multiple first EASs forwarded by the EES; when the first entity is an EES, the EES receives the application context migration scenarios from each first EAS. One application context migration scenario supported by EAS, thereby obtaining multiple application context migration scenarios supported by the first EAS.
  • the first entity not only takes the application context migration scenario of the fifth EAS decision as the target application context migration scenario, but also takes the application context migration scenario triggered by the detection of the third entity as the target application context migration scenario.
  • the fifth EAS sends an instruction to trigger the migration notification to the third entity.
  • the third entity sends a migration notification to the sixth EAS based on the instruction that triggers the migration notification, so that the sixth EAS can perform application context migration according to the migration notification.
  • the three second entities are AC, EEC and EES respectively.
  • the fifth EAS supports the application context migration scenario decided by the fifth EAS
  • the sixth EAS supports the application context migration scenario triggered by AC detection
  • the AC has the processing associated EAS
  • the first entity may determine the fifth EAS.
  • the AC can instruct the sixth EAS to perform application context migration together, that is, the corresponding target application context migration scenarios are determined for multiple first EASs, including the application context migration scenario decided by the fifth EAS and the application context migration scenario triggered by AC detection. .
  • the three second entities are AC, EEC and EES respectively.
  • the fifth EAS supports the application context migration scenario decided by the fifth EAS
  • the sixth EAS supports the application context migration scenario triggered by AC detection and the application context triggered by EEC detection.
  • Migration scenario and AC has the ability to process the application context in the associated EAS to migrate together
  • EEC does not have the ability to process the application context in the associated EAS to migrate together
  • EES does not have the ability to process the application context in the associated EAS to migrate together
  • the first entity may determine that the fifth EAS can instruct the sixth EAS to perform application context migration together through the AC, that is, the corresponding target application context migration scenarios determined for multiple first EASs include the application context migration scenario decided by the fifth EAS. and application context migration scenarios triggered by AC detection.
  • the first entity determines the target application context migration scenario based on the capability information of multiple first EASs, it may specifically include the following steps A and B:
  • Step A The first entity determines whether the multiple application context migration scenarios include the application context migration scenario of the fifth EAS decision based on the capability information of the second entity.
  • the first entity determines that the third entity has the ability to process the migration of application contexts in the associated EAS based on the capability information of the second entity, the first entity determines that the fifth EAS is included in the multiple application context migration scenarios. Decision-making application context migration scenarios.
  • the first entity determines that the second entity does not have the ability to process the migration of application contexts in the associated EAS based on the capability information of the second entity, the first entity determines that the multiple application context migration scenarios do not include The fifth EAS decision-making application context migration scenario.
  • Step B The first entity determines the target application context migration scenario from multiple application context migration scenarios.
  • step B please refer to the description in step 302.
  • the first entity determines the target application context migration scenario from the multiple application context migration scenarios, and the target application context
  • the migration scenario may include an application context migration scenario decided by the fifth EAS.
  • the method also includes: the first entity sends a target application context migration scenario.
  • the first entity may send the application context migration scenario decided by the fifth EAS to the third entity and the fifth EAS respectively, and send the application context migration scenario triggered by the third entity detection to the sixth EAS.
  • the first entity determines whether there is a certain second entity (that is, a third entity) based on the capability information of one or more second entities that has the ability to process the migration of the application context in the associated EAS together.
  • the third entity can specifically receive an instruction to trigger a migration notification from a certain first EAS (i.e., the fifth EAS) among the plurality of first EASs, and send the instruction to the other first EAS (i.e., the sixth EAS) among the plurality of first EASs.
  • a migration notification is sent, so that the sixth EAS performs application context migration together.
  • the first entity may determine that the target application context migration scenario includes the application context migration scenario decided by the fifth EAS.
  • the third entity may determine based on the application context migration scenario of the fifth EAS.
  • the instruction to trigger the migration notification triggers the sixth EAS to perform application context migration together with the fifth EAS, which helps avoid service interruption during the application context migration process.
  • the first entity obtains the capability information of the one EES, or obtains the capability information of the one EES and other third entities.
  • the capability information of the two entities is used as the capability information of the second entity.
  • the first entity determines corresponding target application context migration scenarios for all first EASs in the plurality of first EASs based on the capability information of the second entity.
  • this application does not rule out the situation where multiple first EASs are registered in multiple different EESs, that is, one or more first EASs are registered in each EES.
  • the plurality of first EASs are EAS1 to EAS3 respectively, where EAS1 and EAS2 are registered in EES1, and EAS3 is registered in EES2.
  • the multiple second entities there may be multiple EESs included in the multiple second entities.
  • the five second entities are AC, EEC and three EES respectively, or the five second entities are AC and four EES respectively, or the five second entities are five EES.
  • the multiple second entities can also be implemented in other ways, and no examples will be given one by one.
  • the first entity may obtain the capability information of the multiple different EESs, or acquire the capability information of the multiple EESs and the capability information of other second entities as the capability information of the multiple second entities. . Then, the first entity determines a corresponding target application context migration scenario for at least one first EAS among the plurality of first EASs based on the capability information of the plurality of second entities. It should be understood that the plurality of EESs are the EESs registered by the plurality of first EASs.
  • the EEC may determine corresponding target application context migration scenarios for all first EASs in the plurality of first EASs based on the capability information of the plurality of second entities.
  • the plurality of first EASs are EAS1 to EAS3, and the EEC determines corresponding target application context migration scenarios for EAS1 to EAS3.
  • the first EES can determine the correspondence for all the first EASs among the multiple first EASs based on the capability information of the multiple second entities.
  • Target application context migration scenario For example, the plurality of first EASs are EAS1 to EAS3, and the first entity is EES1 (that is, the first EES).
  • the EES1 can determine corresponding target application context migration scenarios for EAS1 to EAS3.
  • the first EES may determine corresponding target application context migration scenarios for some of the first EASs among the plurality of first EASs based on the capability information of the plurality of second entities.
  • the plurality of first EASs are EAS1 to EAS3, and the first entity is EES1 (i.e., the first EES).
  • EAS1 can determine the corresponding target application context migration for at least one first EAS registered in EAS1 (such as EAS1 and EAS2). Scenes.
  • the first entity is EEC.
  • steps 1801-a and 1802-a are a specific implementation of steps 1801 and 1802 in the case where the first entity is an EEC and the plurality of second entities include multiple EESs.
  • the first entity is an EEC
  • the plurality of second entities include multiple EESs.
  • Step 1801-a EEC obtains capability information of multiple second entities.
  • the plurality of second entities include multiple EESs, and correspondingly, the EEC obtains the capability information of the multiple EESs.
  • the EEC receives the capability information of each EES from multiple EESs, thereby acquiring the capability information of the multiple EESs.
  • the capability information of the EES can be used to indicate whether the EES has the ability to process the migration of application contexts in the associated EAS together.
  • the capability information of the first EES is used to indicate whether the first EES has the ability to process the migration of application contexts in the associated EAS together.
  • each of the multiple EESs is registered with one or more first EASs.
  • the one or more first EASs registered by the multiple EESs respectively constitute the above-mentioned multiple first EASs.
  • the multiple first EASs are The first EAS is an associated EAS, and the multiple EESs can be called associated EESs.
  • the capability information of the first EES indicates whether the first EES has one or more of the following capabilities A - capabilities D:
  • Capability A the ability to obtain the identities of multiple first EASs.
  • the first EES can not only obtain the identity of at least one first EAS registered in the first EES, but can also obtain the identity of at least one first EAS registered in the other EES from other EESs of the plurality of EESs.
  • EES1 multiple EESs are EES1 and EES2 respectively, and multiple EASs are EAS1 to EAS3 respectively.
  • the first EES is EES1.
  • EES1 can not only obtain the first EAS registered in EES1 (such as EAS1 and EAS2), but EES1 can also The first EAS registered in EES2 (such as EAS3) can be obtained from EES2. In this way, EES1 can obtain the identities of multiple EASs (that is, EAS1 to EAS3).
  • Capability B the ability to obtain the identity of at least one first EAS registered in the first EES.
  • the first EES can obtain the identity of at least one first EAS registered in the first EES.
  • the first EES is EES1
  • EES1 can obtain the identity of the first EAS (such as EAS1 and EAS2) registered in EES1.
  • At least one first EAS registered in the first EES is at least one of the above-mentioned plurality of first EASs (associated EASs). That is, at least one first EAS registered in the first EES is included in the plurality of first EASs.
  • Capability C the ability to obtain the identities of multiple EES.
  • the first EES may receive identifications of EESs sent from other EESs among the plurality of EESs except the first EES.
  • Capability D the ability to receive an instruction to trigger a migration notification from one of the first EASs among the plurality of first EASs, and to send migration notifications to other EASs among the plurality of first EASs;
  • capability D may further include one or more of the following capabilities D1 to D3:
  • Capability D1 the ability to receive an instruction to trigger a migration notification from a first EAS registered in the first EES, and to send migration notifications to other EAS registered in the first EES (that is, other first EAS); for example, the first EES is EES1, EAS1 and EAS2 are registered in EES1, and capability D1 is the ability of the first EES to receive the instruction to trigger the migration notification from EAS1, and then send the migration notification to EAS2 according to the instruction to trigger the migration notification.
  • Capability D2 is the ability to receive instructions for triggering migration notifications sent by other EESs other than the first EES among multiple EESs, and to send migration notifications to at least one first EAS registered in the first EES according to the instructions for triggering migration notifications.
  • multiple EESs include EES1 and EES2.
  • the first EES is EES1
  • EAS1 and EAS2 are registered in EES1.
  • EES1 can receive instructions from EES2 that trigger migration notifications, and register with EES1 respectively according to the instructions that trigger migration notifications.
  • EAS1 and EAS2 send migration notifications.
  • Capability D3 the ability to receive an instruction to trigger a migration notification from a first EAS registered in the first EES, and to send an instruction to trigger a migration notification to other EESs other than the first EES among multiple EESs, so that the other EESs can At least one first EAS registered in the other EES sends a migration notification.
  • multiple EESs include EES1 and EES2, where the first EES is EES1, and the capability D3 is for EES1 to send an instruction to trigger a migration notification to EES2 to instruct EES2 to send a migration notification to at least one first EAS registered in EES2.
  • the EEC can also obtain the capability information of other second entities other than the multiple EES. That is, the EEC can also obtain the capability information of the AC and/or the EEC's capability information. Capability information.
  • the capability information of other second entities please refer to the description in step 1801 above.
  • Step 1802-a The EEC determines corresponding target application context migration scenarios for multiple first EASs based on the capability information of multiple second entities.
  • the multiple second entities are multiple EESs, that is, the capability information of the multiple second entities is the capability information of multiple EESs.
  • the EEC determines target application context migration scenarios corresponding to the plurality of first EASs for the plurality of first EASs based on the capability information of the plurality of EESs.
  • the first entity determines, based on the capability information of multiple EESs, that one of the multiple EESs (recorded as the second EES) has the ability to process the migration of application contexts in the associated EAS together
  • the target application context migration scenarios corresponding to the plurality of first EASs are determined, including the application context migration scenarios decided by the first EAS.
  • the first entity determines based on the capability information of multiple EESs that none of the multiple EESs have the ability to process the application context migration in the associated EAS together, it determines that in the migration scenario of the target application context corresponding to the multiple first EASs, it is not possible to Includes application context migration scenarios decided by the first EAS.
  • the first entity determines whether the EES has the ability to process and migrate the application context in the associated EAS together. Specifically, the first entity determines whether the second EES has one of the above capabilities A, capability B, capability C, and capability D. or multiple items.
  • the first entity determines that the first EES has the third capability, it determines that the first EES has the ability to process the migration of application contexts in the associated EAS together.
  • the first entity determines that the first EES does not have the third capability, it determines that the first EES does not have the ability to process the migration of application contexts in the associated EAS together.
  • the third ability is one of ability A, ability B, ability C, and ability D.
  • the third capability is capability A.
  • the first entity determines that EES has capability A, it is determined that EES has the ability to process the application context in the associated EAS and migrates together; when the first entity determines that EES does not have capability A, that is It is determined that EES does not have the capability to handle the migration of application contexts in associated EAS together.
  • the third ability is ability B, ability C, or ability D
  • the implementation method is similar to the above-mentioned ability A.
  • the above-mentioned "ability A” can be replaced with “ability B", “ability C” or “ability D” respectively.
  • the first entity determines that the first EES has the third capability group, it determines that the first EES has the ability to process the migration of application contexts in the associated EAS together.
  • the first entity determines that the first EES does not have any capability in the third capability group, it determines that the first EES does not have the capability to process the migration of application contexts in the associated EAS together.
  • the third ability group is a combination of certain items among ability A, ability B, ability C, and ability D (such as ability D1 or ability D3).
  • the third capability group consists of capability A and capability C.
  • the first entity determines that EES has capability A and capability C, it is determined that EES has the ability to process the application context migration in the associated EAS together; when the first entity determines When EES does not have capability A or capability C, it is determined that EES does not have the ability to process the application context in the associated EAS and migrate it together.
  • the third ability group is obtained by other combinations of ability A, ability B, ability C, and ability D, the specific implementation method is similar to the above. For example, for the third ability group composed of ability A and ability D, you can The above-mentioned "ability A and ability C" are replaced with “ability A and ability D", and the above-mentioned "ability A or ability C" is replaced with "ability A or ability D".
  • the EEC can further determine whether other EESs other than the second EES among the multiple EESs possess one or more of the above capabilities A, capability B, and capability D (such as capability D2), and determine whether other EESs have the above capabilities.
  • A. After one or more of the capabilities B and D, determine the target application context migration scenarios corresponding to multiple first EASs, including the application context migration scenarios decided by the first EAS.
  • the application context migration scenario decided by the first EAS is specifically the application context migration scenario decided by the fifth EAS, where one or more first EASs are registered in the second EES, and the fifth EAS is A first EAS among the one or more first EASs, and the fifth EAS supports the application context migration scenario decided by the fifth EAS.
  • the first EAS other than the fifth EAS among the multiple first EASs may be recorded as a sixth EAS, and the sixth EAS may support the third EAS. 2.
  • the second EES here is a specific implementation of the third entity in the above step 1802, that is, for the fifth EAS and the second EES, the fifth EAS can migrate to the second EES when determining that the application context needs to be migrated.
  • the migration notification is used to trigger the sixth EAS to migrate the application context. .
  • the second EES may also send an instruction to trigger a migration notification to other EESs among the plurality of EESs except the second EES based on the instruction to trigger the migration notification, so that the other EES may send an instruction to the other EES based on the instruction to trigger the migration notification.
  • At least one first EAS registered in the EES sends a migration notification, and the migration notification is used to trigger at least one first EAS registered in the other EES to migrate the application context.
  • multiple second entities include multiple EESs, and ACs and/or EECs. That is, the capability information of multiple second entities includes capability information of multiple EESs, as well as capability information of ACs and/or EECs. or EEC capability information.
  • the EEC determines target application context migration scenarios corresponding to the plurality of first EASs for the plurality of first EASs based on the capability information of the multiple EESs, the capability information of the AC and/or the capability information of the EEC.
  • a certain second entity that is, the third entity
  • multiple second entities including multiple EES, and AC and/or EEC
  • the EEC determines corresponding target application context migration scenarios for the plurality of first EASs
  • the EEC includes the application context migration scenarios decided by the first EAS.
  • the AC or EEC has the ability to process the application context migration in the associated EAS together, that is, it has one or more of the above capabilities a to c.
  • the second EES has the ability to process the application context migration in the associated EAS together, that is, it has one of the above capabilities a to capability c. or more than one; or, specifically, possessing one or more of the above abilities A, ability B, ability C, and ability D (such as ability D1 or ability D3). Further, among the multiple EESs, other EESs other than the second EES may also possess one or more of the above capabilities A, capability B, and capability D (such as capability D2).
  • the first entity is an EES, that is, the first entity is one EES among multiple EESs.
  • any EES among multiple EESs may be used as the first entity.
  • EES EES as the first entity
  • the EES as the first entity may be called the main EES.
  • Example a AC or EEC designates one EES among multiple EESs as the first entity.
  • the AC sends a first designated message to multiple EESs respectively.
  • the first designated message includes the identity of one of the multiple EESs.
  • the multiple EESs determine that the The EES corresponding to the EES identifier in the first specified message serves as the primary EES, that is, the first entity.
  • Example b a certain EES among the plurality of EESs is preconfigured with a third indication, wherein the third indication is used to indicate that the EES is one of the plurality of EESs and is used to determine corresponding target application contexts for the plurality of first EASs. EES for migration scenarios.
  • the EES with the third indication will be pre-configured as the primary EES, that is, the first entity.
  • a specified EAS is registered in one of the multiple EESs, and the EES registered with the specified EAS will be used as the first entity.
  • the designated EAS may also be called a main EAS.
  • the main EAS may be an EAS among multiple first EASs used to provide main services for applications, or a main program among multiple first EASs used to run applications.
  • EAS EAS.
  • the three first EASs that provide services for the game AC are graphics rendering EAS, chat function EAS and game acceleration EAS.
  • the game acceleration EAS can be used as the main EAS of the game AC.
  • the designated EAS may be one of multiple first EASs designated by the AC or EEC.
  • the AC sends second designated messages to multiple first EASs respectively.
  • the second designated messages include the identification of a certain first EAS among the multiple first EASs.
  • the multiple first EASs receive the After the second designation message, the first EAS corresponding to the identification of the first EAS in the second designation message is determined as the primary EAS.
  • the designated EAS is preconfigured with a fourth indication, and the fourth indication is used to indicate that the EAS is the primary EAS.
  • steps 1801-b and 1802-b are specific steps 1801 and 1802 in the case where the first entity is the master EES among multiple EESs, and the multiple second entities include multiple EESs. Method to realize.
  • steps 1801-b and step 1802-b please refer to the above-mentioned step 1801 and step 1802, or refer to the description in step 1801-a and step 1802-a.
  • the main EES is the first EES as an example.
  • Step 1801-b The first EES obtains capability information of multiple second entities.
  • the plurality of second entities include multiple EESs, and correspondingly, the first EES obtains capability information of the multiple EESs.
  • the first EES can not only obtain the capability information of the first EES, but also obtain the capability information of other EESs among multiple EESs except the first EES.
  • the first EES receives information from other EESs among the multiple EESs. the capability information of the other EES, thereby obtaining the capability information of the multiple EES.
  • the first EES may send a first capability request to the other EES.
  • the first capability request is used by the first EES to request the other EES for the capability information of the other EES.
  • the other EES receives After receiving the first capability request, the capability information of the other EES is sent to the first EES.
  • the capability information of the EES can be used to indicate whether the EES has the ability to process and migrate the application context in the associated EAS together.
  • the capability information of the EES can be used to indicate whether the EES has the ability to process and migrate the application context in the associated EAS together.
  • the first EES can also acquire the capability information of other second entities other than the multiple EESs. That is, the first EES can also acquire the capability of the AC. information and/or EEC capability information.
  • the capability information of other second entities please refer to the description in step 1801 above.
  • Step 1802-b The first EES determines a corresponding target application context migration scenario for at least one first EAS among the plurality of first EASs based on the capability information of the plurality of second entities.
  • the corresponding target application context migration scenario is determined based on whether the first EES is all the first EASs among the plurality of first EASs or part of the first EASs, as explained in Example (1) and Example (2) below.
  • Example (1) The first EES determines corresponding target application context migration scenarios for all first EASs in the plurality of first EASs based on the capability information of the plurality of second entities.
  • the EEC can be replaced by the first EES.
  • EES1 Multiple EESs include EES1 and EES2.
  • EAS1 and EAS2 are registered in EES1, and EAS3 is registered in EES2.
  • the first EES is EES1.
  • EES1 determines the target application context migration scenarios for EAS1, EAS2 and EAS3 based on the capability information of EES1, the capability information of EES2, and the application context migration scenarios supported by EAS1 to EAS3.
  • the application context migration scenario includes the application context migration scenario decided by EAS1. .
  • EAS1 supports the application context migration scenario decided by EAS1
  • EAS2 supports the application context migration scenario triggered by EES1 detection
  • EAS3 supports the application context migration scenario triggered by EES2 detection
  • EES1 has capability A, capability B, capability C, capability One or more of D (such as ability D1 or ability D3)
  • EES2 has one or more of ability A, ability B, and ability D (such as ability D2).
  • EES1 receives the instruction to trigger the migration notification from EAS1, sends the migration notification to EAS2, and sends the instruction to trigger the migration notification to EES2; accordingly, EES2 receives the trigger from EES1 Instructions for migration notification, send migration notification to EAS3.
  • EAS1 to EAS3 can perform application context migration together.
  • the capability information of other EES obtained by the first EES can not only be used to indicate whether the other EES possesses one or more of the above capabilities A to D, but can also be directly used to indicate that the other EES has Whether other EES have the ability to process the application context in the associated EAS and migrate it together.
  • the first EES obtains capability information of other EESs among the multiple EESs except the first EES, and the capability information is specifically the processing results of the other EESs.
  • the other EES determines whether the other EES has the ability to process the application context migration in the associated EAS together based on its own capability information and the application context migration scenario supported by at least one first EAS registered in the other EES.
  • the processing result is "has" or "does not have”.
  • the processing result is represented by 1 bit. When the value of this 1 bit is 1, it means “has”. When the value of this 1 bit is 0, It means "does not have".
  • the other EES determines whether it has the ability to handle the migration of the application context in the associated EAS based on its own capability information and the application context migration scenario supported by at least one registered first EAS, therefore, the other EES There is no need to send the application context migration scenario supported by at least one first EAS registered in other EES to the first EES. That is, in this specific implementation, the first EES obtains the processing results of other EESs among the multiple EESs except the first EES, and based on the processing results of the other EESs, the capability information of the first EES, and the information registered in the first EES application context migration scenarios supported by at least one first EAS, and determine corresponding target application context migration scenarios for all first EASs in the plurality of first EASs.
  • Example 2 Multiple EESs include EES1 and EES2.
  • EAS1 and EAS2 are registered in EES1, and EAS3 is registered in EES2.
  • the first EES is EES1.
  • EES2 first determines that EES2 has the ability to process the application context migration in the associated EAS based on the capability information of EES2 and the application context migration scenario supported by EAS3. The obtained processing result is "have”.
  • EES1 obtains the capability information of EES1, the processing results of EES2, and the application context migration scenarios supported by EAS1 and EAS2, and determines the target application context migration scenario for EAS1, EAS2, and EAS3, including the application context migration scenario decided by EAS1.
  • the application context migration scenarios supported by EAS1 to EAS3, the capabilities of EES1 and EES2, and how to implement application context migration from EAS1 to EAS3 together can be seen in Example 1 above.
  • Example (2) The first EES determines corresponding target application context migration scenarios for some of the first EASs among the plurality of first EASs based on the capability information of the plurality of second entities.
  • the part of the first EAS is at least one first EAS registered in the first EES.
  • multiple EESs are each registered with at least one first EAS.
  • the EES is at least one registered in the EES based on the capability information of multiple second entities.
  • the first EAS determines the corresponding target application context migration scenario. That is to say, this application not only includes the first EES determining the corresponding target application context migration scenario for at least one first EAS registered in the first EES based on the capability information of multiple second entities; it also includes the following: Other EESs other than the first EES determine a corresponding target application context migration scenario for at least one first EAS registered in the other EESs based on the capability information of the plurality of second entities.
  • the first EES determines the corresponding target application context migration scenario for one or more first EASs registered in the respective EESs based on the capability information of the multiple second entities.
  • the implementation method please refer to the description of the above example (1).
  • Example 3 Multiple EESs include EES1 and EES2.
  • EAS1 and EAS2 are registered in EES1, and EAS3 is registered in EES2.
  • the first EES is EES1.
  • EES1 determines the target application context migration scenario for EAS1 and EAS2 based on the capability information of multiple second entities and the application context migration scenarios supported by EAS1 and EAS2 respectively.
  • the determined target application context migration scenario includes, for example Application context migration scenario decided by EAS1.
  • other EESs ie EES2 among multiple EESs determine the target application context migration scenario for EAS3 based on the capability information of multiple second entities and the application context migration scenarios supported by EAS3, where the determined target application context migration Scenarios include, for example, application context migration scenarios determined by EAS3.
  • the application context migration scenarios supported by EAS1 to EAS3, the capability information of EES1 and EES2, and how to implement application context migration from EAS1 to EAS3 together can be found in Example 1 and Example 2 above.
  • the first entity determines whether there is a certain EES (that is, the third entity, or the second EES) based on the capability information of multiple EESs that has the ability to process the application context migration in the associated EAS together.
  • the EES as the third entity can specifically receive an instruction to trigger a migration notification from a first EAS registered in the EES (i.e., the fifth EAS), and send a migration notification to other first EAS registered in the EES. , and sending an instruction to trigger a migration notification to other EES, so that the other EES sends a migration notification to at least one first EAS registered in the other EES.
  • the first entity can determine that the target application context migration scenario includes the application context migration scenario decided by the fifth EAS.
  • the EES as the third entity can based on the third entity.
  • the instruction of the fifth EAS to trigger the migration notification respectively triggers other EAS registered in the EES to perform application context migration together with the fifth EAS, and instructs the other EES to send a migration notification to at least one first EAS registered in the other EES, so as to The at least one first EAS and the fifth EAS are instructed to perform application context migration together. This helps avoid service interruptions during application context migration.
  • implementation method 1 also includes implementation method 3, in which the first entity determines whether multiple application context migration scenarios contain application contexts for EAS decisions based on the capability information of multiple first EASs and the capability information of the second entity.
  • Migration scenarios or called application context migration scenarios decided by the EAS, application context migration scenarios decided by the first EAS, and then select a target application context migration scenario from the multiple application context migration scenarios.
  • the first entity obtains the capability information of multiple first EASs and the capability information of one or more second entities.
  • the acquisition method please refer to the descriptions in Implementation Mode 1 and Implementation Mode 2, respectively.
  • the first entity determines whether the multiple application context migration scenarios include the application context migration scenario decided by the EAS based on the capability information of multiple first EASs and the capability information of one or more second entities, and then determines the target application. Context migration scenario.
  • the first entity first determines whether there is a first EAS among the plurality of first EASs that has the capability of processing application contexts in associated EASs to be migrated together based on the capability information of the plurality of first EASs. If the first entity determines that there is a first EAS in the plurality of first EASs that has the ability to process the application context migration in the associated EAS together, then it determines that the plurality of application context migration scenarios include the application context migration scenario decided by the EAS. , that is, the first entity no longer determines whether the multiple application context migration scenarios include the application context migration scenario decided by the EAS based on the capability information of the second entity.
  • the first entity determines that there is no first EAS among the plurality of first EASs that has the ability to process the migration of application contexts in the associated EASs, it further determines the migration scenario of the plurality of application contexts based on the capability information of the second entity. Whether to include application context migration scenarios determined by EAS. Specifically, if the first entity determines that there is a second entity in the one or more second entities that has the ability to process the migration of application contexts in the associated EAS, it further determines that the multiple application context migration scenarios include the EAS Decision-making application context migration scenarios. If the first entity determines that there is no second entity in the one or more second entities that has the ability to process the migration of application contexts in the associated EAS, it further determines that the multiple application context migration scenarios do not include decisions made by the EAS. Application context migration scenario.
  • the first entity first determines, based on the capability information of one or more second entities, whether there is a second entity among the one or more second entities that has the ability to process the migration of the application context in the associated EAS together. If the first entity determines that there is a second entity in the one or more second entities that has the ability to process the migration of application contexts in the associated EAS, it determines that the multiple application context migration scenarios include the application context decided by the EAS. Migration scenario, that is, the first entity no longer determines whether the multiple application context migration scenarios include the application context migration scenario decided by the EAS based on the capability information of the multiple first EASs.
  • the first entity determines that there is no second entity in the second entity that has the ability to process the migration of application contexts in the associated EAS, it further determines the migration scenario of multiple application contexts based on the capability information of multiple first EASs. Whether to include application context migration scenarios determined by EAS. Specifically, if the first entity determines that there is a first EAS in the plurality of first EASs that has the ability to migrate application contexts in associated EASs together, then it further determines that the plurality of application context migration scenarios include the ones decided by the EAS. Application context migration scenario.
  • the first entity determines that there is no first EAS in the plurality of first EASs that has the ability to process the application context migration in the associated EAS, it further determines that the plurality of application context migration scenarios do not include applications decided by the EAS. Context migration scenario.
  • the first entity may also determine, based on the capability information of one or more second entities, whether there is a second entity among the one or more second entities that has the ability to process the migration of the application context in the associated EAS together; and based on The capability information of multiple first EASs determines whether there is a first EAS among the multiple first EASs that has the capability of processing application contexts in associated EASs to be migrated together.
  • the first entity further determines multiple application context migration scenarios.
  • this application can also have other methods, which will not be listed here.
  • the first entity determines whether the multiple application context migration scenarios include EAS decision-making application context migration scenarios based on the capability information of multiple first EASs. Please refer to the description in Implementation Mode 1.
  • the first entity determines whether multiple application context migration scenarios include the EAS decision-making application context migration scenario based on the capability information of one or more second entities. Please refer to the description in Implementation Mode 2.
  • Figure 19 shows a specific implementation of Implementation Mode 1, in which the first entity is an EES, and the EES determines whether the target application context migration scenario includes application context migration decided by the first EAS based on the capability information of multiple first EASs. Scenes.
  • the EES determines whether the target application context migration scenario includes application context migration decided by the first EAS based on the capability information of multiple first EASs. Scenes.
  • the EES determines whether the target application context migration scenario includes application context migration decided by the first EAS based on the capability information of multiple first EASs. Scenes.
  • Step 1901 Multiple first EASs respectively send EAS registration requests to EES. Correspondingly, EES receives registration requests from multiple first EASs.
  • the registration request of the first EAS includes the configuration information of the first EAS.
  • the configuration information of the first EAS includes capability information of the first EAS, and the capability information of the first EAS indicates whether the first EAS has one or more of capabilities 1 to 4.
  • the configuration information of the first EAS also includes the identification of the first EAS and the application context migration scenario supported by the first EAS.
  • the application context migration scenario supported by the first EAS can be used to indicate whether the first EAS has capability 4. That is, the application context migration scenario supported by the first EAS can be considered as the capability information of the first EAS.
  • Step 1902 EES sends EAS registration responses to multiple first EAS respectively.
  • Step 1903 The EEC and multiple first EAS subscribe to the target application context migration scenario to the EES respectively.
  • Step 1904 The AC is preconfigured with AC configuration information.
  • the AC configuration information may include application context migration scenarios supported by the AC, an identity of the AC, and first information.
  • the first information is, for example, a first EAS list, which is a list composed of identifiers of multiple first EASs.
  • Step 1905 The AC sends an AC registration request to the EEC, where the AC registration request includes AC configuration information.
  • Step 1906 The EEC sends an AC registration response to the AC.
  • Step 1907 The EEC sends an EEC registration request to the EES, where the EEC registration request includes AC configuration information and application context migration scenarios supported by the EEC.
  • Step 1908 EES determines, based on the first information, that the application contexts of multiple first EASs need to be migrated together; EES determines, based on the capability information of multiple first EASs, whether there are applications in the EASs with processing associations in the multiple first EASs.
  • the first EAS i.e. the fifth EAS with the ability to migrate the context together.
  • the EES determines that the fifth EAS among the multiple first EASs has the ability to process the application context migration in the associated EAS together, then it determines that the multiple application context migration scenarios include the application context migration scenario decided by the fifth EAS; if it is determined that none of the multiple first EASs has the ability to process the application context migration in the associated EAS together, then it is determined that the multiple application context migration scenarios do not include the application context migration scenario decided by the fifth EAS.
  • EES selects a target application context migration scenario from the determined multiple application context migration scenarios.
  • Step 1909 The EES sends application context migration scenario notifications to multiple first EASs respectively, and the application context migration scenario notifications include target application context migration scenarios.
  • Step 1910 EES sends an EEC registration response to EEC, and the EEC registration response includes the target application context migration scenario.
  • Step 911 AC subscribes to the EEC for the target application context migration scenario.
  • Step 1912 The EEC sends an application context migration scenario notification to the AC.
  • the application context migration scenario notification includes the target application context migration scenario.
  • the first entity can also be replaced by EEC.
  • the difference lies in whether the first entity communicates directly with the first EAS or indirectly communicates through the EES; and in that the first entity communicates directly with the AC. , or indirect communication through EEC. And the specific messages differ between entities.
  • the registration request can be replaced by an update request
  • the registration response can be replaced by an update response
  • the EAS registration request is replaced by an EAS update request
  • the EAS registration response is replaced by an EAS update response.
  • the above information can also be carried in other types of messages, which is not limited in this application.
  • Figure 20 shows a specific implementation of Implementation Mode 2, in which the first entity is an EES, and multiple second entities include AC, EEC, and EES. There is one EES, that is, multiple first entities that need to migrate application context together.
  • the EAS is registered in the EES.
  • the EES determines whether the target application context migration scenario includes the application context migration scenario decided by the first EAS based on the capability information of the plurality of second entities.
  • Implementation Mode 2 or the related embodiment in Figure 18 please refer to Implementation Mode 2 or the related embodiment in Figure 18 .
  • Step 2001 Multiple first EASs respectively send EAS registration requests to EES.
  • EES receives registration requests from multiple first EASs.
  • the registration request of the first EAS includes the configuration information of the first EAS.
  • the configuration information of the first EAS includes application context migration scenarios supported by the first EAS.
  • the configuration information of the first EAS also includes the identification of the first EAS.
  • Step 2002 EES sends EAS registration responses to multiple first EAS respectively.
  • Step 2003 The EEC and multiple first EAS subscribe to the target application context migration scenario to the EES respectively.
  • Step 2004 The AC is preconfigured with AC configuration information.
  • the AC configuration information includes the AC's capability information.
  • the AC's capability information is used to indicate whether the AC has the ability to process and migrate the application context in the associated EAS together, or whether it has one of the above capabilities a to c. or multiple items.
  • capabilities a to c please refer to the description of the relevant embodiment in Figure 18 .
  • the AC configuration information may also include application context migration scenarios supported by the AC, the identity of the AC, and the first information.
  • the first information is, for example, a first EAS list, that is, a list composed of identifiers of multiple first EASs.
  • the application context migration scenario supported by the AC can be used to indicate whether the AC has capability b.
  • the application context migration scenarios supported by the AC can also be considered as the capability information of the AC.
  • Step 2005 The AC sends an AC registration request to the EEC, where the AC registration request includes AC configuration information, that is, the first information and AC capability information.
  • Step 2006 The EEC sends an AC registration response to the AC.
  • Step 2007 EEC is preconfigured with EEC configuration information.
  • the EEC configuration information includes the EEC's capability information.
  • the EEC's capability information is used to indicate whether the EEC has the ability to process and migrate the application context in the associated EAS together, or whether it has one of the above capabilities a to c. or multiple items.
  • capabilities a to c please refer to the description of the relevant embodiment in Figure 18 .
  • the EEC configuration information may also include the application context migration scenarios supported by the EEC and the identification of the EEC.
  • the application context migration scenario supported by the EEC can be used to indicate whether the EEC has capability b.
  • the application context migration scenarios supported by EEC can also be considered as EEC capability information.
  • Step 2008 The EEC sends an EEC registration request to the EES, where the EEC registration request includes AC configuration information and EEC configuration information. Accordingly, the EES receives the EEC registration request from the EEC.
  • Step 2009 EES determines that the application contexts of multiple first EASs need to be migrated together based on the first information carried in the AC configuration information in the EEC registration request; EES determines that the application context migration scenarios supported by multiple first EASs and the capabilities of EES Information, the AC's capability information and the EEC's capability information determine whether there is a second entity (ie, a third entity) in the AC, EEC, and EES that has the ability to process the migration of application contexts in the associated EAS together.
  • a second entity ie, a third entity
  • the EES determines that there is a third entity in the AC, EEC, and EES that has the ability to process the application contexts in the associated EAS and migrate them together, that is, it determines that the fifth EAS among the multiple first EASs can indicate through the third entity.
  • Other EASs in multiple first EASs perform application context migration together, and then determine that multiple application context migration scenarios include the application context migration scenarios decided by the fifth EAS; if the EES determines that among AC, EEC, and EES There is no third entity capable of processing the migration of application contexts in associated EAS together, that is, it is determined that the fifth EAS among the plurality of first EASs cannot indicate other EASs among the plurality of first EASs through the third entity ( That is, if the sixth EAS) performs application context migration together, it is determined that the multiple application context migration scenarios do not include the application context migration scenario decided by the fifth EAS.
  • the fifth EAS can instruct the sixth EAS among the multiple first EASs to perform application context migration together through the third entity.
  • the third entity can receive the instruction from the fifth EAS to trigger the migration notification, Then send a migration notification to the sixth EAS. This description may also be applied to other examples in this application.
  • EES is pre-configured with EES configuration information.
  • the EES configuration information includes the capability information of the EES.
  • the capability information of the EES is used to indicate whether the EES has the ability to process and migrate the application context in the associated EAS together, or whether it has one of the above capabilities a to capability c. or multiple items.
  • capabilities a to c please refer to the description of the relevant embodiment in Figure 18 .
  • the EES configuration information may also include the application context migration scenarios supported by the EES and the identification of the EES.
  • the application context migration scenario supported by the EES can be used to indicate whether the EES has capability b.
  • the application context migration scenarios supported by EES can also be considered as EES capability information.
  • Step 2010 EES selects a target application context migration scenario from multiple application context migration scenarios.
  • the EES may determine the application context migration scenario decided by the fifth EAS and the application context migration scenario decided by the third entity. , jointly serve as the target application context migration scenario.
  • the EES can determine that the fifth EAS among the multiple first EASs can instruct multiple first EASs through the AC.
  • the sixth EAS among the first EAS performs application context migration together. That is, the EES determines the application context migration scenario decided by the fifth EAS and the application context migration scenario decided by the AC, which together serve as the target application context migration scenario.
  • Step 2011 EES sends application context migration scenario notifications to multiple first EASs respectively, and the application context migration scenario notifications include target application context migration scenarios.
  • the target application context migration scenarios included in the application context migration scenario notifications sent by EES to multiple first EASs respectively include: the application context migration scenario decided by the fifth EAS, and the application context migration decided by the AC. Scenes.
  • Step 2012 EES sends an EEC registration response to EEC, where the EEC registration response includes the target application context migration scenario.
  • Step 2013 AC subscribes to the EEC for the target application context migration scenario.
  • Step 2014 The EEC sends an application context migration scenario notification to the AC.
  • the application context migration scenario notification includes the target application context migration scenario.
  • the first entity can also be replaced by EEC.
  • the difference lies in whether the first entity communicates directly with the first EAS or indirectly communicates through the EES; and in the communication between the first entity and the second entity. Communication methods; and specific messages between entities vary.
  • the registration request can be replaced by an update request
  • the registration response can be replaced by an update response
  • the EAS registration request is replaced by an EAS update request
  • the EAS registration response is replaced by an EAS update response.
  • the above information can also be carried in other types of messages, which is not limited in this application.
  • Figure 21 shows another specific implementation of Implementation Mode 2, in which multiple second entities include AC, EEC and EES, where there are multiple EESs, that is, multiple first EASs that need to perform application context migration together are registered in multiple different EES.
  • the first entity is an EES (denoted as the first EES) among the plurality of EESs.
  • the first EES determines the target application context for all the first EASs among the plurality of first EASs based on the capability information of the plurality of second entities.
  • Migration scenario In this specific implementation, content that is not described in detail may be referred to the description in Implementation Mode 2 or the relevant embodiments in Figure 18 or Figure 20 .
  • the interaction method between the first EES and the third EES can be referred to the interaction method between the first EES and the second EES.
  • this application does not limit the number of multiple EESs.
  • steps 2001 to 2014 included in Figure 21 can be understood by referring to steps 2001 to 2014 shown in Figure 20 , and the EES in Figure 20 can be replaced with the first EES.
  • one or more first EASs among the plurality of first EASs may register with the first EES, and the other one or more first EASs may register with the second EES.
  • the first EES needs to migrate the application context based on the first information, multiple first EAS supported application context scenarios, AC capability information, EEC capability information, first EES capability information, and second EES capabilities. information to determine whether the multiple application context migration scenarios include the application context migration scenario decided by the first EAS.
  • the second entity also includes other EES (such as a third EES)
  • the first EES also needs to consider the capability information of the third EES, which will not be described again.
  • Figure 21 also includes the following steps 2015 and 2016:
  • Step 2015 The first EES sends a first capability request to the second EES.
  • the first capability request is used by the first EES to request the second EES for capability information of the second EES.
  • Step 2016 After receiving the first capability request, the second EES sends the capability information of the second EES to the first EES. In this way, the first EES obtains the capability information of the second EES.
  • this application may also have other implementation methods for the first EES to obtain the capability information of the second EES.
  • step 2015 and step 2016 precede step 2009.
  • Figure 22 shows another specific implementation of Implementation Mode 2, in which the multiple second entities include AC, EEC and EES, where there are multiple EESs, that is, multiple first EASs that need to perform application context migration together are registered in multiple different EES.
  • the first entity is an EES (denoted as a first EES) among multiple EESs.
  • the first EES is at least one of the plurality of first EASs registered with the first EES based on the capability information of the multiple second entities.
  • the first EAS determines the target application context migration scenario.
  • EESs among the plurality of EESs can also determine the target application for at least one first EAS among the plurality of second EASs registered with the second EES based on the capability information of the plurality of second entities.
  • Context migration scenario In this specific implementation, content that is not described in detail may be referred to the description in Implementation Mode 2 or the relevant embodiments in Figure 18 or Figure 20 or Figure 21 .
  • the interaction method between the first EES and the third EES can be referred to the interaction method between the first EES and the second EES.
  • this application does not limit the number of multiple EESs.
  • steps 2001 to 2016 included in FIG. 22 please refer to steps 2001 to 2016 shown in FIG. 21 .
  • the first EES determines the target application context migration scenario
  • it specifically determines the target application context migration scenario for at least one first EAS registered in the first EES.
  • the second EES can also perform steps 2009 and 2010, so that the second EES can migrate the application context based on the first information, multiple first EAS supported application context scenarios, AC capability information, and EEC capability information.
  • the capability information of the first EES and the capability information of the second EES determine whether the multiple application context migration scenarios include the application context migration scenario decided by the first EAS, and then at least one first EAS registered in the second EES Determine the target application context migration scenario.
  • step 2009 and step 2010, please refer to the description of step 1802-b above.
  • Figure 22 also includes the following steps 2017 and 2018:
  • Step 2017 The second EES sends a second capability request to the first EES.
  • the second capability request is used by the second EES to request the first EES for capability information of the first EES.
  • Step 2018 After receiving the second capability request, the first EES sends the capability information of the first EES to the second EES. In this way, the second EES obtains the capability information of the first EES.
  • this application may also have other implementation methods for the second EES to obtain the capability information of the first EES.
  • step 2017 and step 2018 precede step 2009.
  • FIG. 23 and FIG. 24 are schematic structural diagrams of possible communication devices provided by the present application. These communication devices can be used to implement the functions in the above method embodiments, and therefore can also achieve the beneficial effects of the above method embodiments.
  • the communication device may be EEC, EES, AC or EAS as shown in Figure 1 .
  • the communication device 2300 includes a processing module 2301 and a transceiver module 2302.
  • the processing module 2301 in the communication device 2300 can be used to implement the first entity (such as EEC, EES), AC or EAS (such as the first entity) in the method embodiment shown in any of the above figures 3 to 6, 12 and 13. Three EAS) functions.
  • the transceiver module 2302 can be used to support communication between the communication device 2300 and other communication devices. For example, when the communication device 2300 is an EES, the transceiver module 2302 can be used by the EES to receive the first information from the AC. or,
  • the processing module 2301 in the communication device 2300 can be used to implement the first entity (such as EEC, EES), AC or EAS (such as the Three EAS) functions.
  • the transceiver module 2302 can be used to support communication between the communication device 2300 and other communication devices. For example, when the communication device 2300 is an EES, the transceiver module 2302 can be used by the EES to receive the first information from the AC. or,
  • the processing module 2301 in the communication device 2300 may be used to implement the functions of the EAS (such as the fourth EAS) or AC in the method embodiments shown in FIG. 10, FIG. 11 or FIG. 16.
  • the transceiver module 2302 can be used to support communication between the communication device 2300 and other communication devices. For example, when the communication device 2300 is the fourth EAS, the transceiver module 2302 can be used by the fourth EAS to send the first entity (such as EEC, EES) to the first entity.
  • EES electronic entity
  • the processing module 2301 in the communication device 2300 may be used to implement the functions of the first entity (such as EEC, EES), AC or EAS (such as the first EAS) in the method embodiment shown in FIG. 17 or FIG. 19 .
  • the transceiver module 2302 can be used to support communication between the communication device 2300 and other communication devices. For example, when the communication device 2300 is a first entity (such as an EES), the transceiver module 2302 can be used by the EES to receive the first EAS from the first EAS. Capability information. or,
  • the processing module 2301 in the communication device 2300 can be used to implement the first entity (such as EEC, EES), the second entity (such as EEC, EES or AC), AC or EAS (such as the first EAS) function.
  • the transceiver module 2302 can be used to support communication between the communication device 2300 and other communication devices. For example, when the communication device 2300 is a first entity (such as an EES) and the second entity is an EEC, the transceiver module 2302 can be used by the EES to receive data from the EEC. EEC capability information.
  • Figure 24 shows a device 2400 provided by an embodiment of the present application.
  • the device shown in Figure 24 can be a hardware circuit implementation of the device shown in Figure 23. This device can be adapted to the flow chart shown above to perform the functions of the first terminal device or the second terminal device in the above method embodiment.
  • Figure 24 shows only the main components of the device.
  • the device 2400 shown in Figure 24 includes a communication interface 2410, a processor 2420, and a memory 2430, where the memory 2430 is used to store program instructions and/or data.
  • the processor 2420 may cooperate with the memory 2430.
  • Processor 2420 may execute program instructions stored in memory 2430. When the instructions or programs stored in the memory 2430 are executed, the processor 2420 is used to perform the operations performed by the processing module 2301 in the above embodiment, and the communication interface 2410 is used to perform the operations performed by the transceiver module 2302 in the above embodiment.
  • Memory 2430 and processor 2420 are coupled.
  • the coupling in the embodiment of this application is an indirect coupling or communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information interaction between devices, units or modules.
  • At least one of memories 2430 may be included in processor 2420.
  • the communication interface may be a transceiver, a circuit, a bus, a module, or other types of communication interfaces.
  • the transceiver when the communication interface is a transceiver, the transceiver may include an independent receiver or an independent transmitter; it may also be a transceiver with integrated transceiver functions or a communication interface.
  • Apparatus 2400 may also include communication lines 2440.
  • the communication interface 2410, the processor 2420 and the memory 2430 can be connected to each other through a communication line 2440;
  • the communication line 2440 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (extended industry standard architecture) , referred to as EISA) bus, etc.
  • the communication line 2440 can be divided into an address bus, a data bus, a control bus, etc. For ease of presentation, only one thick line is used in Figure 24, but it does not mean that there is only one bus or one type of bus.
  • Embodiments of the present application also provide a computer-readable storage medium that includes instructions that, when run on a computer, cause the computer to implement the method embodiments shown in any of Figures 3 to 6, Figure 12, and Figure 13 function of the first entity (such as EEC, EES), AC or EAS (such as the third EAS); or implement the first method embodiment shown in any of the above figures 7 to 9, 14 and 15
  • the functions of the entity such as EEC or EES), AC or EAS (such as the third EAS); or implement the EAS (such as the fourth EAS) or The function of the AC; or realize the function of the first entity (such as EEC, EES), AC or EAS (such as the first EAS) in the method embodiment shown in the above-mentioned Figure 17 or Figure 19; or realize the above-mentioned Figure 18, Figure 20 , the functions of the first entity (such as EEC or EES), the second entity (such as EEC, EES or AC), AC or EAS (such as the first EAS) in the method embodiment shown in
  • Embodiments of the present application also provide a computer program product, which includes computer instructions. When run on a computer, it causes the computer to implement the method embodiments shown in any one of Figures 3 to 6, Figure 12, and Figure 13.
  • the functions of the first entity such as EEC, EES), AC or EAS (such as the third EAS); or the first entity in the method embodiment shown in any of the above figures 7 to 9, 14 and 15 (such as EEC or EES), AC or EAS (such as the third EAS); or implement the functions of the EAS (such as the fourth EAS) or AC in the method embodiments shown in Figure 10, Figure 11 or Figure 16; Or implement the functions of the first entity (such as EEC, EES), AC or EAS (such as the first EAS) in the method embodiment shown in the above-mentioned Figure 17 or Figure 19; or implement the above-mentioned Figure 18, Figure 20, Figure 21 or Functions of the first entity (such as EEC, EES), the second entity (such as EEC, EES or AC), AC or EAS (
  • Embodiments of the present application also provide a chip system, including: a processor, the processor is coupled to a memory, and the memory is used to store programs or instructions.
  • the chip system implements FIGS. 3 to 6 , the functions of the first entity (such as EEC, EES), AC or EAS (such as the third EAS) in the method embodiment shown in any of the figures of Figure 12 and Figure 13; or implement the above-mentioned Figures 7 to 9 and Figure 14 , the functions of the first entity (such as EEC, EES), AC or EAS (such as the third EAS) in the method embodiment shown in any of the figures in Figure 15; or implement the functions shown in the above-mentioned Figure 10, Figure 11 or Figure 16
  • the function of the EAS (such as the fourth EAS) or AC in the method embodiment or implement the first entity (such as EEC, EES), AC or EAS (such as the first EAS); or implement the first entity (such as EEC, EES), the second entity (such
  • An embodiment of the present application also provides a communication system, including: one or more of a first entity (such as EEC, EES), AC or EAS.
  • a first entity such as EEC, EES
  • AC has the methods shown in Figures 3 to 6, Figure 12 and Figure 13.
  • the function of the AC in the embodiment the EAS has the function of the third EAS in the method embodiment shown in the above-mentioned Figures 3 to 6, Figure 12 and Figure 13.
  • An embodiment of the present application also provides a communication system, including: one or more of a first entity (such as EEC, EES), AC or EAS.
  • a first entity such as EEC, EES
  • AC has the methods shown in Figures 7 to 9, Figure 14 and Figure 15.
  • the function of the AC in the embodiment the EAS has the function of the third EAS in the method embodiment shown in the above-mentioned Figures 7 to 9, Figure 14 and Figure 15.
  • An embodiment of the present application also provides a communication system, including: one or more of a first entity (such as EEC, EES), AC or EAS.
  • a first entity such as EEC, EES
  • AC has the functions of AC in the method embodiments shown in Figures 10, 11 and 16.
  • EAS has the function of the fourth EAS in the above method embodiments shown in Figures 10, 11 and 16.
  • Embodiments of the present application also provide a communication system, including: one or more of a first entity (such as an EEC or EES), an AC, or an EAS.
  • a first entity such as an EEC or EES
  • an AC has the functions of the AC in the method embodiment shown in Figure 17 or Figure 19
  • the EAS has the functions in the above figure. 17 or the function of the first EAS in the method embodiment shown in Figure 19.
  • Embodiments of the present application also provide a communication system, including: a first entity (such as EEC or EES), a second entity (such as EEC, EES or AC), one or more of AC or EAS.
  • a first entity such as EEC or EES
  • a second entity such as EEC, EES or AC
  • the first entity has the function of the first entity in the method embodiment shown in any of the above-mentioned Figures 18 and 20-22
  • the AC has the method shown in any of the above-mentioned Figures 18, 20-22
  • the second entity has the functions of the AC in the method embodiment shown in any of the above-mentioned Figures 18, 20-22
  • the EAS has the functions of the AC in any of the above-mentioned Figures 18, 20-22.
  • a figure illustrates the functionality of the first EAS in a method embodiment.
  • a computer program product includes one or more computer instructions.
  • Computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, e.g., computer instructions may be transmitted from a website, computer, server or data center via a wired link (e.g.
  • Coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless means to transmit to another website site, computer, server or data center.
  • Computer-readable storage media can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or other integrated media that includes one or more available media. Available media may be magnetic media (eg, floppy disk, hard disk, tape), optical media (eg, DVD), or semiconductor media (eg, solid state disk (SSD)), etc.
  • the various illustrative logic units and circuits described in the embodiments of this application can be implemented by a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, Discrete gate or transistor logic, discrete hardware components, or any combination of the foregoing are designed to implement or operate the functions described.
  • the general-purpose processor may be a microprocessor.
  • the general-purpose processor may also be any conventional processor, controller, microcontroller or state machine.
  • a processor may also be implemented as a combination of computing devices, such as a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration. accomplish.
  • the above functions described in this application may be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, these functions may be stored on a computer-readable medium, or transmitted on a computer-readable medium in the form of one or more instructions or code.
  • Computer-readable media includes computer storage media and communications media that facilitate transfer of a computer program from one place to another. Storage media can be any available media that can be accessed by a general purpose or special purpose computer.
  • Such computer-readable media may include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other device that may be used to carry or store instructions or data structures and Other media containing program code in a form readable by a general-purpose or special-purpose computer, or by a general-purpose or special-purpose processor.
  • any connection may be properly defined as a computer-readable medium, for example, if the software is transferred from a website, server, or other remote source to a computer over a coaxial cable, fiber optic cable, twisted pair cable, or digital subscriber line (DSL) Or transmitted by wireless means such as infrared, wireless and microwave are also included in the definition of computer-readable media.
  • DSL digital subscriber line
  • Disks and discs include compressed disks, laser disks, optical discs, digital versatile discs (English: Digital Versatile Disc, referred to as DVD), floppy disks and Blu-ray discs. Disks usually copy data magnetically, while discs usually copy data magnetically. Optical copying of data is usually done with a laser. Combinations of the above can also be contained in a computer-readable medium.
  • Computer-readable media includes computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • Storage media can be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

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

Abstract

一种应用上下文迁移场景的确定方法及通信装置，用于实现多个EAS中应用上下文一起迁移，避免在应用上下文迁移过程中出现服务中断。其中，方法包括：第一实体根据第一信息，确定多个应用上下文迁移场景是否包括EAS决策的应用上下文迁移场景，其中，第一信息指示多个第一EAS中的应用上下文需一起迁移。第一实体可从多个应用上下文迁移场景中选择目标应用上下文迁移场景。

Description

一种应用上下文迁移场景的确定方法及通信装置
相关申请的交叉引用
本申请要求在2022年03月29日提交中国专利局、申请号为202210323867.5、申请名称为“一种应用上下文迁移场景的确定方法及通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中；本申请要求在2022年06月16日提交中国专利局、申请号为202210689587.6、申请名称为“一种应用上下文迁移场景的确定方法及通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种应用上下文迁移场景的确定方法及通信装置。
 背景技术
多接入边缘计算(multi-access edge computing，MEC)指的是利用无线接入网络向用户就近提供互联网技术(internet technology，IT)所需服务和云端计算功能，而创造出一个具备高性能、低延迟与高带宽的电信级服务环境。
在MEC中，应用客户端(application client，AC)可由多个边缘应用服务器(edge application sever，EAS)提供服务，相应的，每个EAS存储有该AC对应的应用上下文。在多个EAS中的EAS进行应用上下文迁移时，可能会导致向AC提供的服务发生中断。
如何避免在应用上下文迁移过程中出现服务中断，是目前亟待解决的技术问题。
发明内容
本申请提供一种应用上下文迁移场景的确定方法及通信装置，用于实现多个EAS中应用上下文一起迁移，避免在应用上下文迁移过程中出现服务中断。
第一方面，本申请提供一种应用上下文迁移场景的确定方法，包括：第一实体根据第一信息，确定多个应用上下文迁移场景是否包括EAS决策的应用上下文迁移场景，其中，第一信息指示多个第一EAS中的应用上下文需一起迁移。第一实体可从多个应用上下文迁移场景中选择目标应用上下文迁移场景。
在一种可能的实现方式中，第一实体根据第一信息，确定多个应用上下文迁移场景是否包括EAS决策的应用上下文迁移场景，具体可以是，第一实体根据第一信息，确定多个应用上下文迁移场景不包括EAS决策的应用上下文迁移场景。
上述技术方案中，多个应用上下文迁移场景中不包括EAS决策的应用上下文迁移场景的情况下，第一实体可从除EAS决策的应用上下文迁移场景以外的其他应用上下文迁移场景中选择目标应用上下文迁移场景。通过边缘使能客户端(edge enabler client，EEC)、AC或边缘使能服务器(edge enabler server，EES)决策的应用上下文迁移场景，可实现多个第一EAS中应用上下文一起迁移，避免在应用上下文迁移过程中出现服务中断。
在一种可能的实现方式中，第一实体还可接收第一信息。
一个具体实现中，AC可以向第一实体发送第一信息，相应的，第一实体可接收来自AC的第一信息。其中，AC可由多个第二EAS提供服务，多个第一EAS是多个第二EAS中的部分或全部。
一个具体实现中，第一实体接收来自AC的第一信息，具体可以是，第一实体接收来自AC的AC配置信息(AC profile)，AC配置信息中包括第一信息。
在一种可能的实现方式中，第一信息中包括多个第一EAS的标识和/或第一指示；第一指示用于指示多个第一EAS中的应用上下文需一起迁移。
在一种可能的实现方式中，第一实体还可以接收第二信息，第二信息指示多个第一EAS中是否存在第三EAS，其中，第三EAS具有对多个第一EAS中的应用上下文一起迁移的能力，或者认为，第三EAS具有发现多个第一EAS中除第三EAS以外其他EAS的能力，或者第三EAS具有通知多个第一EAS中除第三EAS以外其他EAS进行应用上下文迁移的能力。
在一种可能的实现方式中，第一实体根据第一信息，确定多个应用上下文迁移场景是否包括EAS决策的应用上下文迁移场景，具体可以是，第一实体根据第一信息和第二信息，确定多个应用上下文迁移场景是否包括EAS决策的应用上下文迁移场景。
具体的，在多个第一EAS中不存在第三EAS的情况下，多个应用上下文迁移场景不包括EAS决策的应用上下文迁移场景；或，在多个第一EAS中存在第三EAS的情况下，多个应用上下文迁移场景包括EAS决策的应用上下文迁移场景。
上述技术方案中，在多个应用上下文迁移场景中不包括EAS决策的应用上下文迁移场景的情况下，第一实体可从除EAS决策的应用上下文迁移场景以外的其他应用上下文迁移场景中选择目标应用上下文迁移场景。如此，通过EEC、AC或EES决策的应用上下文迁移场景来实现多个第一EAS中应用上下文一起迁移，避免在应用上下文迁移过程中出现服务中断。
在多个应用上下文迁移场景中包括EAS决策的应用上下文迁移场景的情况下，第一实体可从该多个应用上下文迁移场景中选择目标应用上下文迁移场景。进一步的，当第一实体选择的目标应用上下文迁移场景为EEC、AC或EES决策的应用上下文迁移场景时，可实现多个第一EAS中应用上下文一起迁移。当第一实体选择的目标应用上下文迁移场景为EAS决策的应用上下文迁移场景时，可以通过第三EAS来执行决策，即发现或通知多个第一EAS中除第三EAS以外的其他EAS，从而实现多个第一EAS中应用上下文一起迁移。如此，有助于避免在应用上下文迁移过程中出现服务中断。
在一种可能的实现方式中，第一实体是EEC或EES。
具体的，第一实体是EEC的情况下，AC中预配置有第一信息，EEC从AC接收第一信息；或者，EEC中预配置有第一信息。EEC从EES接收由EES转发的第二信息。
具体的，第一实体是EES的情况下，AC中预配置有第一信息，EES从EEC接收由EEC转发的第一信息。或者，EEC中预配置有第一信息，EES从EEC接收第一信息。EES从第三EAS接收第二信息。
在一种可能的实现方式中，AC也可以向第三EAS发送多个第一EAS的标识。如此，第三EAS可以基于接收到的多个第一EAS的标识，向第一实体发送第二信息。
第二方面，本申请提供一种应用上下文迁移场景的确定方法，包括：第一实体接收第一信息，第一信息指示多个第一EAS中的应用上下文需一起迁移；第一实体根据第一信息，向第三EAS发送多个第一EAS的标识，第三EAS是多个第一EAS中的一个或多个。
上述技术方案中，第一实体向第三EAS发送多个第一EAS的标识，相应的，第三EAS获取到多个第一EAS的标识之后，可具备将多个第一EAS中应用上下文一起迁移的能力。第一实体在选择目标应用上下文迁移场景时，可以选择EEC、AC或EES决策的应用上下文迁移场景，从而实现多个第一EAS中应用上下文一起迁移。或者，第一实体还可以选择EAS决策的应用上下文迁移场景，相应的，第三EAS可根据多个第一EAS的标识，发现或通知多个第一EAS中除第三EAS以外的其他EAS，从而实现多个第一EAS中应用上下文一起迁移。如此，有助于避免在应用上下文迁移过程中出现服务中断。
在一种可能的实现方式中，第一实体还可以确定目标应用上下文迁移场景。第一实体根据第一信息，向第三EAS发送多个第一EAS的标识，具体可以是，在目标应用上下文迁移场景包括EAS决策的应用上下文迁移场景的情况下，第一实体根据第一信息，向第三EAS发送多个第一EAS的标识。上述技术方案中，第一实体可在确定目标应用上下文迁移场景包括EAS决策的应用上下文迁移场景之后，根据第一信息向第三EAS发送多个第一EAS的标识，如此，有助于避免不必要的信令传输。
在一种可能的实现方式中，第一实体接收第一信息，具体可以是，AC向第一实体发送第一信息，相应的，第一实体接收来AC的第一信息。其中，AC由多个第二EAS提供服务，多个第一EAS是多个第二EAS中的部分或全部。
一个具体实现中，第一实体接收来自AC的第一信息，具体可以是，第一实体接收来自AC的AC配置信息，AC配置信息中包括第一信息。
在一种可能的实现方式中，第一信息中包括多个第一EAS的标识和/或第一指示；第一指示用于指示多个第一EAS中的应用上下文需一起迁移。
在一种可能的实现方式中，第一实体是EEC或EES。
具体的，第一实体是EEC的情况下，AC中预配置有第一信息，EEC可从AC接收第一信息。或者，EEC中预配置有第一信息。进一步的，EEC还可以通过EES向第三EAS发送多个第一EAS的标识。
第一实体是EES的情况下，AC中预配置有第一信息，EES从EEC接收由EEC转发的第一信息。或者，EEC中预配置有第一信息，EES从EEC接收第一信息。进一步的，EES还可向第三EAS发送多个第一EAS的标识。
第三方面，本申请提供一种应用上下文迁移场景的确定方法，包括：EAS根据第一信息，确定EAS支持的应用上下文迁移场景不包括EAS决策的应用上下文迁移场景，第一信息指示多个第一EAS中的应用上下文需一起迁移；EAS发送EAS支持的应用上下文迁移场景。此处的EAS具体可以是本申请中的第四EAS。
如此，第一实体可选择除EAS决策的应用上下文迁移场景以外的应用上下文迁移场景，作为目标应用上下文迁移场景，即第一实体选择的目标应用上下文迁移场景为EEC、AC或EES决策的应用上下文迁移场景时，有助于实现多个第一EAS中应用上下文一起迁移，进而避免在应用上下文迁移过程中出现服务中断。
在一种可能的实现方式中，EAS支持的应用上下文迁移场景可用于确定目标应用上下文迁移场景。
在一种可能的实现方式中，EAS发送EAS支持的应用上下文迁移场景，具体可以是，EAS向第一实体发送EAS支持的应用上下文迁移场景。相应的，第一实体接收EAS支持的应用上下文迁移场景，根据EAS支持的应用上下文迁移场景确定目标应用上下文迁移场景。其中，第一实体可以是EEC或EES。具体的，第一实体是EEC的情况下，EAS通过EES向EEC发送EAS支持的应用上下文迁移场景。
在一种可能的实现方式中，第一信息可预配置于EAS中，或第一信息是EAS从AC或者EEC接收的。
在一种可能的实现方式中，EAS从AC中接收第一信息，具体可以是，AC向EAS发送AC配置信息，AC配置信息中包括第一信息。
第四方面，本申请提供一种应用上下文迁移场景的确定方法，包括：第一实体获取多个第一EAS的能力信息；第一实体根据多个第一EAS的能力信息，为多个第一EAS确定对应的目标应用上下文迁移场景；其中，该多个第一EAS是关联的EAS，关联的EAS中的应用上下文需一起迁移；第一EAS的能力信息指示第一EAS是否具备处理关联的EAS中的应用上下文一起迁移的能力。
在一种可能的实现方式中，第一实体根据多个第一EAS的能力信息，为多个第一EAS确定对应的目标应用上下文迁移场景时，具体是，第一实体根据多个第一EAS的能力信息，确定目标应用上下文迁移场景中是否包括由多个第一EAS中的一个第一EAS决策的应用上下文迁移场景。
上述技术方案中，第一EAS的能力信息指示第一EAS是否具备处理关联的EAS中的应用上下文一起迁移的能力，从而第一实体根据多个第一EAS的能力信息，确定该多个第一EAS中是否存在具备处理关联的EAS中的应用上下文一起迁移的能力的第一EAS，进而为多个第一EAS确定对应的目标应用上下文迁移场景。如此，在多个第一EAS中存在具备处理关联的EAS中的应用上下文一起迁移的能力的第一EAS时，第一实体可将由第一EAS决策的应用上下文迁移场景作为目标应用上下文迁移场景，从而在由第一EAS决策的应用上下文迁移场景中，该第一EAS可以指示多个第一EAS中的其他EAS(即其他第一EAS)一起进行应用上下文迁移，避免在应用上下文迁移过程中出现服务中断。
在一种可能的实现方式中，第一实体根据多个第一EAS的能力信息，确定多个第一EAS中的一个第一EAS具备处理关联的EAS中的应用上下文一起迁移的能力的情况下，第一实体确定目标应用上下文迁移场景中包括由多个第一EAS中的该一个第一EAS决策的应用上下文迁移场景；第一实体根据多个第一EAS的能力信息，确定多个第一EAS均不具备处理关联的EAS中的应用上下文一起迁移的能力的情况下，第一实体确定目标应用上下文迁移场景中不包括由第一EAS决策的应用上下文迁移场景。
在一种可能的实现方式中，第一实体根据第一EAS的能力信息，确定该第一EAS是否具备处理关联的EAS中的应用上下文一起迁移的能力，具体可以是，第一实体根据第一EAS的能力信息，确定该第一EAS是否支持如下能力1至能力4中的一项或多项：
能力1，获取多个第一EAS的标识的能力；
能力2，向多个第一EAS中除该一个第一EAS以外的其他EAS发送迁移通知的能力；
能力3，接收来自多个第一EAS中该一个第一EAS以外的其他EAS的迁移通知的能力；
能力4，支持由第一EAS决策的应用上下文迁移场景；
其中，能力2和能力3中的迁移通知用于触发应用上下文迁移。
一个具体实现中，第一实体在确定第一EAS具备第一能力时，即确定第一EAS具备处理关联的EAS中的应用上下文一起迁移的能力。第一实体在确定第一EAS不具备该第一能力时，即确定第一EAS不具备处理关联的EAS中的应用上下文一起迁移的能力。其中，第一能力是能力1、能力2和能力4中的某一项。
再一个具体实现中，第一实体在确定第一EAS具备第一能力组时，即确定第一EAS具备处理关联的EAS中的应用上下文一起迁移的能力。第一实体在确定第一EAS不具备该第一能力组中的任一个能力时，即确定第一EAS不具备处理关联的EAS中的应用上下文一起迁移的能力。其中，第一能力组是能力1、能力2和能力4中的某多项的组合。
此外，第一实体在确定某一个第一EAS具备处理关联的EAS中的应用上下文一起迁移的能力的情况下，还可在进一步确定多个第一EAS中除该一个第一EAS以外的其他第一EAS具备上述能力3的情况下，确定目标应用上下文迁移场景中包括由多个第一EAS中的该一个第一EAS决策的应用上下文迁移场景。
在一种可能的实现方式中，第一实体是EEC的情况下，EEC还从EES接收由EES转发的多个第一EAS的能力信息；或，第一实体是EES的情况下，EES还从多个第一EAS中的每个第一EAS中接收该第一EAS的能力信息，以得到多个第一EAS的能力信息。如此，基于不同的第一实体，提供第一实体获取多个第一EAS的能力信息的实现方式。
在一种可能的实现方式中，第一实体还接收第一信息，第一信息指示多个第一EAS是关联的EAS。如此，第一实体在接收到第一信息之后，确定多个第一EAS是关联的EAS，即确定该多个第一EAS的应用上下文需一起迁移。
具体的，第一实体是EEC的情况下，AC中预配置有第一信息，EEC从AC接收第一信息；或者，EEC中预配置有第一信息。
具体的，第一实体是EES的情况下，AC中预配置有第一信息，EES从EEC接收由EEC转发的第一信息。或者，EEC中预配置有第一信息，EES从EEC接收第一信息。
第五方面，本申请提供一种应用上下文迁移场景的确定方法，包括：第一实体获取第二实体的能力信息；第一实体根据第二实体的能力信息，为多个第一EAS中的至少一个第一EAS确定对应的目标应用上下文迁移场景；其中，多个第一EAS是关联的EAS，关联的EAS中的应用上下文需一起迁移；第二实体的能力信息指示第二实体是否具备处理关联的EAS中的应用上下文一起迁移的能力。
在一种可能的实现方式中，第二实体可以是一个或多个。示例性的，第二实体是一个，该一个第二实体是AC、EEC或EES；第二实体是两个，该两个第二实体分别是AC和EEC，或AC和EES，或EEC和EES；第二实体是三个，该三个第二实体分别是AC、EEC和EES。此外，在多个第二实体包括EES的情况下，该多个第二实体中可包括多个EES，比如第二实体是五个，该五个第二实体分别是AC、EEC和三个EES，或者该五个第二实体分别是AC和四个EES，或者该五个第二实体是五个EES等。
在一种可能的实现方式中，第一实体根据第二实体的能力信息，为多个第一EAS中的至少一个第一EAS确定对应的目标应用上下文迁移场景时，具体是，在一个或多个第二实体的能力信息指示其中的一个第二实体具备处理关联的EAS中的应用上下文一起迁移的能力的情况下，第一实体确定目标应用上下文迁移场景中包括由至少一个第一EAS中的第一EAS决策的应用上下文迁移场景。此外，当一个或多个第二实体的能力信息指示该一个或多个第二实体均不具备处理关联的EAS中的应用上下文一起迁移的能力的情况下，第一实体确定目标应用上下文迁移场景中不包括由第一EAS决策的应用上下文迁移场景。
上述技术方案中，第一实体根据一个或多个第二实体的能力信息，确定一个或多个第二实体中是否存在某个第二实体具备处理关联的EAS中的应用上下文一起迁移的能力。在确定存在该具备处理关联的EAS中的应用上下文一起迁移的能力的第二实体时，进而为多个第一EAS中的至少一个第一EAS确定出对应的目标应用上下文迁移场景。如此，在某个第二实体具备处理关联的EAS中的应用上下文一起迁移的能力的情况下，第一实体可将由第一EAS决策的应用上下文迁移场景作为多个第一EAS中的至少一个第一EAS对应的目标应用上下文迁移场景，从而在由第一EAS决策的应用上下文迁移场景中，该第二实体可用于在多个第一EAS中的一个第一EAS的指示下，触发该多个第一EAS中的其他EAS一起进行应用上下文迁移，避免在应用上下文迁移过程中出现服务中断。
在一种可能的实现方式中，第二实体的能力信息指示第二实体是否支持如下能力中的一项或多项：
能力a，获取多个第一EAS的标识的能力；
能力b：支持由第一EAS决策的应用上下文迁移场景；
能力c，接收多个第一EAS中一个第一EAS的触发迁移通知的指示，基于该触发迁移通知的指示向多个第一EAS中其他的第一EAS发送迁移通知的能力；
其中，迁移通知用于触发应用上下文迁移。
一个具体实现中，第一实体在确定第二实体具备第二能力时，即确定第二实体具备处理关联的EAS中的应用上下文一起迁移的能力。第一实体在确定第二实体不具备该第二能力时，即确定第二实体不具备处理关联的EAS中的应用上下文一起迁移的能力。其中，第二能力是能力a、能力b和能力c中的某一项。
再一个具体实现中，第一实体在确定第二实体具备第二能力组时，即确定第二实体具备处理关联的EAS中的应用上下文一起迁移的能力。第一实体在确定第二实体不具备该第二能力组中的任一个能力时，即确定第二实体不具备处理关联的EAS中的应用上下文一起迁移的能力。其中，第二能力组是能力a、能力b和能力c中的某多项的组合。
在一种可能的实现方式中，多个第一EAS中的一个第一EAS支持的应用上下文迁移场景包括：由第一EAS决策的应用上下文迁移场景。其中，第一EAS支持由第一EAS决策的应用上下文迁移场景，可以理解为，该第一EAS能够检测触发并决策应用上下文迁移，该第一EAS在确定需要进行应用上下文迁移时，能够向第二实体发送触发迁移通知的指示，以指示第二实体向多个第一EAS中除该第一EAS以外的其他EAS发送迁移通知。
在一种可能的实现方式中，多个第一EAS中除一个第一EAS以外的其他EAS支持的应用上下文迁移场景包括：由第二实体检测触发的应用上下文迁移场景。其中，该其他EAS支持由第二实体检测触发的应用上下文迁移场景，可以理解为，该其他EAS能够接收来自第二实体的迁移通知，并响应于该迁移通知，进行应用上下文迁移。
如上，第一实体根据第二实体的能力信息，以及多个第一EAS分别支持的应用上下文迁移场景，为多个第一EAS中的至少一个第一EAS确定出目标应用上下文迁移场景，该目标应用上下文迁移场景中包括由某个第一EAS决策的应用上下文迁移场景，使用该第一EAS决策的应用上下文迁移场景，可避免在应用上下文迁移过程中出现服务中断。
在一种可能的实现方式中，第一实体是EEC或者EES。
第一实体是EEC的情况下，第二实体可以是AC或EES。当第二实体是AC时，EEC还从AC接收AC的能力信息；和/或，当第二实体是EES时，EEC还从EES接收EES的能力信息。此外，当第二实体是多个时，比如第二实体是两个，该两个第二实体分别是AC和EES，则EEC还从AC接收AC的能力信息，以及从EES接收EES的能力信息。
或者，
第一实体是EES的情况下，第二实体可以是AC或EEC，当第二实体是AC时，EEC还从AC接收AC的能力信息；和/或，当第二实体是EEC时，EES还从EEC接收EEC的能力信息。此外，当第二实体是多个时，比如第二实体是两个，该两个第二实体分别是AC和EES，则EEC还从AC接收AC的能力信息，以及从EES接收EES的能力信息。
如此，基于不同的第一实体和第二实体，提供第一实体获取第二实体的能力信息的实现方式。
在一种可能的实现方式中，第一实体还接收第一信息，第一信息指示多个第一EAS是关联的EAS。如此，第一实体在接收到第一信息之后，确定多个第一EAS是关联的EAS，即确定该多个第一EAS的应用上下文需一起迁移。
具体的，第一实体是EEC的情况下，AC中预配置有第一信息，EEC从AC接收第一信息；或者，EEC中预配置有第一信息。
具体的，第一实体是EES的情况下，AC中预配置有第一信息，EES从EEC接收由EEC转发的第一信息。或者，EEC中预配置有第一信息，EES从EEC接收第一信息。
在一种可能的实现方式中，在多个第二实体中包括多个EES的情况下，也即在多个第一EAS注册于多个EES的情况下，第一实体可获取多个EES的能力信息。其中，每个EES的能力信息可指示该EES是否具备处理关联的EAS中的应用上下文一起迁移的能力。
以多个EES中的一个EES(记为第一EES)说明，其中，第一EES的能力信息指示第一EES是否支持如下能力中的一项或多项：
能力A，获取多个第一EAS的标识的能力；
能力B，获取第一EES中注册的至少一个第一EAS的标识的能力，此处，第一EES中注册的至少一个第一EAS是上述多个第一EAS(关联的EAS)中的至少一个；
能力C，获取多个EES的标识的能力；
能力D，接收来自多个第一EAS中的一个第一EAS的触发迁移通知的指示，向多个第一EAS中除该一个第一EAS以外的其他EAS发送迁移通知的能力；
示例性的，能力D可进一步包括如下能力D1至D3中一项或多项：
能力D1，接收第一EES中注册的一个第一EAS的触发迁移通知的指示，向第一EES中注册的其他EAS(即其他的第一EAS)发送迁移通知的能力；
能力D2，接收多个EES中除第一EES以外的其他EES发送的触发迁移通知的指示，根据该触发迁移通知的指示，向第一EES中注册的至少一个第一EAS发送迁移通知的能力；
能力D3，接收第一EES中注册的一个第一EAS的触发迁移通知的指示，向多个EES中除第一EES以外的其他EES发送触发迁移通知的指示的能力，以使得该其他的EES向该其他的EES中注册的至少一个第一EAS发送迁移通知。
其中，迁移通知用于触发应用上下文迁移。
一个具体实现中，第一实体在确定第一EES具备第三能力时，即确定第一EES具备处理关联的EAS中的应用上下文一起迁移的能力。第一实体在确定第一EES不具备该第三能力时，即确定第一EES不具备处理关联的EAS中的应用上下文一起迁移的能力。其中，第三能力是能力A、能力B、能力C、能力D中的某一项。进一步的，第三能力可以是能力D1至能力D3中一项或多项。
再一个具体实现中，第一实体在确定第一EES具备第三能力组时，即确定第一EES具备处理关联的EAS中的应用上下文一起迁移的能力。第一实体在确定第一EES不具备该第三能力组中的任一个能力时，即确定第一EES不具备处理关联的EAS中的应用上下文一起迁移的能力。其中，第三能力组是能力A、能力B、能力C、能力D中的某多项的组合。进一步的，第三能力组是能力A、能力B、能力C、能力D1、能力D2和能力D3中的某多项的组合。
在一种可能的实现方式中，第一实体根据第二实体的能力信息，为多个第一EAS中的至少一个第一EAS确定对应的目标应用上下文迁移场景时，具体是，当第一实体是EEC时，EEC根据第二实体的能力信息，为多个第一EAS中的全部第一EAS确定对应的目标应用上下文迁移场景；当第一实体是第一EES时，第一EES根据第二实体的能力信息，为多个第一EAS中的全部第一EAS确定对应的目标应用上下文迁移场景，或者，第一EES根据第二实体的能力信息，为多个第一EAS中的部分第一EAS确定对应的目标应用上下文迁移场景，其中，该部分第一EAS具体是多个第一EAS中、注册于该第一EES中的至少一个第一EAS。
在一种可能的实现方式中，第一实体根据第二实体的能力信息，为多个第一EAS中的至少一个第一EAS确定对应的目标应用上下文迁移场景时，具体是，第一实体是第一EES的情况下，第一EES根据第二实体的能力信息，为多个第一EAS中全部EAS(即该多个第一EAS)确定对应的目标应用上下文迁移场景。该第一EAS可称为是主EAS，该第一EES是由AC或EEC指定的、多个EES中的一个EES；或，第一EES中预配置有第三指示，第三指示用于指示第一EES是多个EES中、用于为多个第一EAS确定对应的目标应用上下文迁移场景的EES；或，第一EES是多个EES中注册有指定EAS的EES。其中，该指定EAS可称为是主EAS，该指定EAS具体可以是由AC或EEC指定的、多个第一EAS中的一个EAS，或者是该指定EAS中预配置有第四指示，第四指示即用于指示该EAS是主EAS。
在一种可能的实现方式中，第一实体是第一EES、第二实体是多个EES中的其他EES的情况下，第一EES还从其他EES处接收其他EES的能力信息。
第六方面，本申请实施例提供一种通信装置。
该装置具有实现上述第一方面或第一方面的任一种可能的实现方式中第一实体的功能，或者第二方面或第二方面的任一种可能的实现方式中第一实体的功能，或者第四方面或第四方面的任一种可能的实现方式中第一实体的功能，或者第五方面或第五方面的任一种可能的实现方式中第一实体的功能，该装置具体可以是EEC或者EES。
该装置具有实现上述第一方面或第一方面的任一种可能的实现方式中AC的功能，或者第二方面或第二方面的任一种可能的实现方式中AC的功能，或者第三方面或第三方面的任一种可能的实现方式中AC的功能，或者第四方面或第四方面的任一种可能的实现方式中AC的功能，或者第五方面或第五方面的任一种可能的实现方式中AC的功能。
该装置具有实现上述第三方面或第三方面的任一种可能的实现方式中EAS的功能。
该装置具有实现上述第五方面或第五方面的任一种可能的实现方式中第二实体的功能。该装置具体可以是EEC、EES或AC。
上述通信装置的功能可以通过硬件实现，也可以通过硬件执行相应的软件实现，硬件或软件包括一个或多个与上述功能相对应的模块或单元或手段(means)。
在一种可能的实现方式中，该装置的结构中包括处理模块和收发模块，其中，
处理模块被配置为支持该装置执行上述第一方面或第一方面的任一种可能的实现方式中，或者第二方面或第二方面的任一种可能的实现方式中第一实体的功能，或者第四方面或第四方面的任一种可能的实现方式中第一实体的功能，或者第五方面或第五方面的任一种可能的实现方式中第一实体的功能，该第一实体具体可以是EEC或者EES；或者，
处理模块被配置为支持该装置执行上述第一方面或第一方面的任一种可能的实现方式中，或者第二方面或第二方面的任一种可能的实现方式中，或者第三方面或第三方面的任一种可能的实现方式中AC的功能，或者第四方面或第四方面的任一种可能的实现方式中AC的功能，或者第五方面或第五方面的任一种可能的实现方式中AC的功能；或者，
处理模块被配置为支持该装置执行上述第三方面或第三方面的任一种可能的实现方式中EAS的功能；或者，
处理模块被配置为支持该装置执行上述第五方面或第五方面的任一种可能的实现方式中第二实体的功能，该第二实体具体可以是EEC或EES或AC。
收发模块用于支持该装置与其他通信设备之间的通信，例如该装置为第一实体时，收发模块用于接收来自AC的第一信息。该通信装置还可以包括存储模块，存储模块与处理模块耦合，其保存有装置必要的程序指令和数据。作为一种示例，处理模块可以为处理器，通信模块可以为收发器，存储模块可以为存储器，存储器可以和处理器集成在一起，也可以和处理器分离设置。
在另一种可能的实现方式中，该装置的结构中包括处理器，还可以包括存储器。处理器与存储器耦合，可用于执行存储器中存储的计算机程序指令，以使装置执行上述第一方面或第一方面的任一种可能的实现方式中的方法，或者执行上述第二方面或第二方面的任一种可能的实现方式中的方法，或者执行上述第三方面或第三方面的任一种可能的实现方式中的方法，或者执行上述第四方面或第四方面的任一种可能的实现方式中的方法，或者执行上述第五方面或第五方面的任一种可能的实现方式中的方法。
可选地，该装置还包括通信接口，处理器与通信接口耦合。当装置为网络设备或终端设备时，该通信接口可以是收发器或输入/输出接口；当该装置为网络设备中包含的芯片或终端设备中包含的芯片时，该通信接口可以是芯片的输入/输出接口。可选地，收发器可以为收发电路，输入/输出接口可以是输入/输出电路。
第七方面，本申请实施例提供一种芯片系统，包括：处理器，处理器与存储器耦合，存储器用于存储程序或指令，当程序或指令被处理器执行时，使得该芯片系统实现上述第一方面或第一方面的任一种可能的实现方式中的方法，或实现上述第二方面或第二方面的任一种可能的实现方式中的方法，或实现上述第三方面或第三方面的任一种可能的实现方式中的方法，或者实现上述第四方面或第四方面的任一种可能的实现方式中的方法，或者实现上述第五方面或第五方面的任一种可能的实现方式中的方法。
可选地，该芯片系统还包括接口电路，该接口电路用于交互代码指令至处理器。
可选地，该芯片系统中的处理器可以为一个或多个，该处理器可以通过硬件实现也可以通过软件实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等。当通过软件实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现。
可选地，该芯片系统中的存储器也可以为一个或多个。该存储器可以与处理器集成在一起，也可以和处理器分离设置。示例性的，存储器可以是非瞬时性处理器，例如只读存储器ROM，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上。
第八方面，本申请实施例提供一种计算机可读存储介质，其上存储有计算机程序或指令，当该计算机程序或指令被执行时，使得计算机执行上述第一方面或第一方面的任一种可能的实现方式中的方法，或执行上述第二方面或第二方面的任一种可能的实现方式中的方法，或执行上述第三方面或第三方面的任一种可能的实现方式中的方法，或者执行上述第四方面或第四方面的任一种可能的实现方式中的方法，或者执行上述第五方面或第五方面的任一种可能的实现方式中的方法。
第九方面，本申请实施例提供一种计算机程序产品，当计算机读取并执行计算机程序产品时，使得计算机执行上述第一方面或第一方面的任一种可能的实现方式中的方法，或执行上述第二方面或第二方面的任一种可能的实现方式中的方法，或执行上述第三方面或第三方面的任一种可能的实现方式中的方法，或者执行上述第四方面或第四方面的任一种可能的实现方式中的方法，或者执行上述第五方面或第五方面的任一种可能的实现方式中的方法。
第十方面，本申请实施例提供一种通信系统，该通信系统包括上述第一方面中的第一实体、AC或第三EAS中一项或多项；或者包括上述第二方面中的第一实体、AC或第三EAS中一项或多项；或者包括上述第三方面中的第一实体、AC或EAS中一项或多项；或者包括上述第四方面中的第一实体、AC或EAS中一项或多项；或者包括上述第五方面中的第一实体、第二实体或EAS中一项或多项。其中，第一实体具体可以是EEC或EES；第二实体具体可以是EEC或EES或AC。
上述第六方面至第十方面中任一方面可以达到的技术效果可以参照上述第一方面至第五方面任一方面中有益效果的描述，此处不再重复赘述。
 附图说明
图1为本申请提供的一种边缘应用架构的示意图；
图2为本申请提供的一种EEC发现EES和EAS的流程示意图；
图3-图6为本申请提供的实现方式一中应用上下文迁移场景的确定方法流程示意图；
图7-图9为本申请提供的实现方式二中应用上下文迁移场景的确定方法流程示意图；
图10、图11为本申请提供的实现方式三中应用上下文迁移场景的确定方法流程示意图；
图12-图16为本申请提供的具体场景中应用上下文迁移场景的确定方法的流程示意图；
图17为本申请提供的实现方式1的应用上下文迁移场景的确定方法的流程示意图；
图18为本申请提供的实现方式2的应用上下文迁移场景的确定方法的流程示意图；
图19为本申请提供的实现方式1在具体场景中应用上下文迁移场景的确定方法的流程示意图；
图20-图22为本申请提供的实现方式2在具体场景中应用上下文迁移场景的确定方法的流程示意图；
图23为本申请提供的一种通信装置的示意图；
图24为本申请提供的再一种通信装置的示意图。
 具体实施方式
第三代伙伴计划(the 3rd generation partnership project，3GPP)正在进行应用使能的多接入边缘计算(multi-access edge computing，MEC)的研究，并定义了如图1所示的边缘(edge)应用架构。
该应用架构包括终端、边缘数据网络(edge data network，EDN)和边缘配置服务器(edge configuration server，ECS)。终端可包括应用客户端(application client，AC)和边缘使能客户端(edge enabler client，EEC)。边缘数据网络(edge data network，EDN)可包括边缘应用服务器(edge application sever，EAS)和边缘使能服务器(edge enabler server，EES)。
终端也可以称为终端设备、用户设备(user equipment，UE)、移动台、移动终端等。终端可以广泛应用于各种场景，例如，设备到设备(device-to-device，D2D)、车物(vehicle to everything，V2X)通信、机器类通信(machine-type communication，MTC)、物联网(internet of things，IOT)、虚拟现实、增强现实、工业控制、自动驾驶、远程医疗、智能电网、智能家具、智能办公、智能穿戴、智能交通、智慧城市等。终端可以是手机、平板电脑、带无线收发功能的电脑、可穿戴设备、车辆、无人机、直升机、飞机、轮船、机器人、机械臂、智能家居设备等。本申请的实施例对终端所采用的具体技术和具体设备形态不做限定。
AC，是边缘应用在终端侧的客户端程序。AC用于用户(user)从应用服务器(application sever，AS)获取应用业务，具体的，AC可以连接到云上的AS从而获取应用业务，也可以连接到部署运行在一个或多个EDN中的EAS以获取应用业务。
EEC，是EES在终端侧的对等实体。EEC可以是终端的中间件层，具体可位于操作系统中，或者位于AC与操作系统中间。EEC用于向EES注册EEC的信息及AC的信息、执行安全认证和鉴权、从EES获取EAS的网际互连协议(internet protocol，IP)地址、向AC提供边缘计算使能能力等。示例性的，EEC可通过应用编程接口(application program interface，API)向AC提供边缘使能服务。
EDN，是一个特别的本地数据网络(local data network，LDN)，EDN具有边缘使能功能，EDN可以使用数据网接入点标识(data network access identifier，DNAI)和数据网络名称(data network name，DNN)标识。可以理解，EDN是一个本地的数据中心(地理位置概念)，可以包含多个本地数据网络(local DN)。其中，本地数据网络指的是，距离用户的附着点(attachment point)很近的一个数据网络的接入点(access point)。
EAS，是指部署在EDN中的应用。EAS具体可以是，一个服务器应用程序(例如，社交媒体软件、增强现实(augmented reality，AR)、虚拟现实(virtual reality，VR))部署运行在EDN的实例(instance)。一个应用可在一个或多个EDN中部署一个或多个EAS，部署运行在不同的EDN中的EAS可以认为是一个应用的不同的EAS，这些不同的EAS可以共享一个域名，可以使用一个IP地址，也可以使用不同的IP地址。EAS也可以称为边缘应用(服务)、应用实例、边缘应用实例、MEC应用(服务)、EAS功能等。
EES，又可称为是MEC平台或边缘平台。EES部署在EDN中，一个EDN中可部署一个或多个EES。EES用于为部署在EDN中的EAS提供一些使能能力，从而更好的支持应用在MEC的部署情况。具体的，EES可以支持边缘应用的注册、对终端的认证和鉴权、为终端提供EAS的IP地址信息、为ECS提供EAS的标识和IP地址信息等。一般情况下，EAS注册到一个EES上，或者，通过管理系统将一个EAS的信息配置在一个EES上，该EES称为该EAS关联的EES，EES控制/管理注册/配置在该EES上的EAS。
ECS，又可称为是EDN配置服务器(edge data network configuration server，EDN CS)。ECS可用于负责EDN的配置，如向终端提供EES的信息，向终端提供EAS的信息，以及和应用的域名解析系统(domain name system，DNS)交互获取EAS的信息，从其他功能实体中获取并保存EAS和IP地址的信息等。
本申请中，终端和EDN之间可建立连接，以用于传输应用数据。可将AC、EEC、EAS、EES和ECS统称为是实体，两个实体之间可通过边缘(edge)应用架构对应的接口连通，比如AC与EEC之间通过EDGE-5连通，再比如EEC与ECS之间通过EDGE-4连通等。
结合图1的结构，如下解释EEC发现EES和EAS的流程，该流程可参见图2所示。其中，步骤201至步骤203为EES的发现过程，步骤204至步骤206为EAS的发现过程。
EES的发现过程：
步骤201，EEC向ECS请求/订阅EES。
示例性的，EEC向ECS发送EES发现请求。相应的，ECS接收来自EEC的EES发现请求。其中，EES发现请求中可包括终端位置。
步骤202，ECS根据终端位置选择EES。
具体的，ECS可根据终端位置确定终端需要接入的数据网的DNAI。然后，ECS根据其记录的多个EES配置信息(EES profile)、DNAI和全限定域名(fully qualified domain name，FQDN)，为EEC选择其对应的EES。可选的，ECS在选择EES之前，可先从会话管理功能(session management function，SMF)中获取当前/潜在的DNAI。
步骤203，ECS向EEC发送EES的信息。
EAS的发现过程：
步骤204，EEC向EES发送EAS发现请求。其中EAS发现请求可包括过滤(filter)参数，该过滤参数可包括AC的标识、终端的标识中一项或多项。
步骤205，EES匹配注册的EAS。
EES的本地记录有已注册/上线的一个或多个EAS的配置信息(EAS profile)。EES可根据过滤参数和本地记录的一个或多个EAS的配置信息，确定满足EEC请求的EAS。可选的，EES可匹配出一个或多个满足EEC请求的EAS。
步骤206，EES向EEC发送EAS发现响应。其中，EAS发现响应中可包括EES发现的满足EEC请求EAS的信息。
进一步的，EEC可将EAS的信息提供给AC，从而AC可根据EAS的信息，连接至该EAS，如此，EAS可以为AC提供相关服务。
可以认为，当前为AC提供服务的EAS(可记为源EAS、source-EAS、S-EAS)在地理上具有一定的服务范围。当AC(或AC所在终端)发生移动时，比如AC由当前EDN移动至另外一个EDN中，源EAS可能无法继续为AC提供服务，或者源EAS已经不再是为该AC提供服务的最优的EAS，则需要新的EAS(可记为目标EAS、target-EAS、T-EAS)为该AC提供服务，该目标EAS即替换源EAS。
进一步的，可将源EAS注册的EES记为是源EES、source-EES、S-EES，将目标EAS注册的EES记为是目标EES、target-EES、T-EES。在一些示例中，源EAS和目标EAS可注册于同一个EES中，此时，源EES和目标EES为同一个。
在目标EAS替换源EAS的过程中，目标EAS和源EAS二者需要执行应用上下文迁移(application context relocation，ACR)，即源EAS将本地存储的应用上下文(application context，AC)迁移至目标EAS中，以保证应用运行中断的影响降至最低。
其中，应用上下文指的是和用户相关的运行状态信息，应用上下文中可以包含源EAS与核心网订阅的上下文，例如订阅的事务标识等，或者，还包含用户在EES中的上下文，例如源EAS针对该用户的订阅的事务标识。
应用上下文迁移的流程可包括如下四个步骤：
步骤一，检测过程：
示例性的，可检测终端位置的变化情况，或者检测终端用户面路径是否发生更新等，以得到检测结果。
其中，该检测过程可以是由源EAS、源EES、EEC、AC中的一个或多个执行。
步骤二，决策过程：
根据检测结果，确定是否需要执行应用上下文迁移。其中，该决策过程可以是由源EAS、源EES、EEC、AC中的一个或多个执行。
步骤三，执行过程：
执行过程可包括目标EAS的发现过程，该发现过程可以由源EAS、源EES、EEC、AC中的一个或多个执行。
执行过程还可包括应用上下文的迁移过程，具体的，源EAS可将源EAS中应用上下文迁移至目标EAS中，该迁移过程可是由源EAS、目标EAS或EEC发起。
此外，源EAS在将源EAS中应用上下文迁移至目标EAS中之后，可向终端或者网络通知目标EAS的信息；或者，目标EAS在从源EAS中获取应用上下文之后，可向终端或者网络通知目标EAS的信息。其中，目标EAS的信息可包括目标EAS的地址信息(比如IP地址、FQDN等)、目标EAS对应N6路由信息等。
步骤四，清理过程：
在应用上下文由源EAS迁移至目标EAS之后，多个实体执行应用上下文迁移的清理工作，例如AC可发起一个新的套接字(socket)连接到目标EAS等。
本申请提供如下多种应用上下文迁移场景(application context relocation scenario，ACR scenario)。本申请中，应用上下文迁移场景又可称为应用上下文迁移模式、应用上下文迁移方式、应用上下文迁移方法等。
应用上下文迁移场景1：EEC决策或AC决策的应用上下文迁移场景。
应用上下文迁移的检测流程由EEC执行。
应用上下文迁移的决策流程由EEC或AC执行。
应用上下文迁移的执行流程具体可以是EEC发现目标EES和目标EAS，EEC请求源EES发起用户面路径修改，EEC和AC发起应用上下文迁移。
应用上下文迁移的清理流程由多个实体共同执行。
应用上下文迁移场景2：EEC决策的应用上下文迁移场景。进一步的，EEC通过源EES执行应用上下文迁移的场景。
应用上下文迁移的检测流程由EEC执行。
应用上下文迁移的决策流程也由EEC执行。
应用上下文迁移的执行流程具体可以是EEC发现目标EES和目标EAS，EEC请求源EES发起用户面路径修改，随后源EES通知源EAS发起应用上下文迁移。
应用上下文迁移的清理流程由多个实体共同执行。
应用上下文迁移场景3：EEC决策的应用上下文迁移场景。进一步的，EEC通过目标EES执行应用上下文迁移。
应用上下文迁移的检测流程由EEC执行。
应用上下文迁移的决策流程也由EEC执行。
应用上下文迁移的执行流程具体可以是EEC发现目标EES和目标EAS，EEC请求目标EES发起用户面路径修改，目标EES通知目标EAS发起应用上下文迁移。
应用上下文迁移的清理流程由多个实体共同执行。
应用上下文迁移场景4：EAS决策的应用上下文迁移场景。
应用上下文迁移的检测流程具体可以是，源EES检测并通知源EAS需要进行应用上下文迁移，或者源EAS检测确定需要进行应用上下文迁移。
应用上下文迁移的决策流程由源EAS执行。
应用上下文迁移的执行流程具体可以是源EAS发现目标EES和目标EAS，源EAS发起用户面路径修改，并发起应用上下文迁移。
应用上下文迁移的清理流程由多个实体共同执行。
应用上下文迁移场景5：源EES决策的应用上下文迁移场景。
应用上下文迁移的检测流程可由源EES、源EAS、EEC中一项或多项执行。
应用上下文迁移的决策流程也由源EES执行。具体的，源EES可基于上述检测实体(即源EES、源EAS、EEC中一项或多项)的检测结果，决策进行应用上下文迁移。
应用上下文迁移的执行流程具体可以是源EES发现目标EES和目标EAS，源EES发起用户面路径修改，并通知源EAS发起应用上下文迁移。
应用上下文迁移的清理流程由多个实体共同执行。
应用上下文迁移场景6：源EES决策的应用上下文迁移场景。
应用上下文迁移的检测流程由源EES执行。
应用上下文迁移的决策流程也由源EES执行。
应用上下文迁移的执行流程具体可以是，源EES发现目标EES和目标EAS，源EES发起用户面路径修改，以及发起应用上下文迁移。
应用上下文迁移的清理流程由多个实体共同执行。
AC可能由多个EAS提供服务。比如，游戏AC需要由图形渲染EAS和聊天功能EAS共计2个EAS来提供服务。再比如，道路流量预测AC可需要由道路监控EAS、天气预报EAS共计2个EAS来提供服务。
可认为，该AC在多个EAS中的应用上下文是具有关联关系的，相当于，AC在多个EAS中的应用上下文需要进行一起迁移，如此，有助于保障多个EAS向AC提供服务的连续性。本申请中，可以将应用上下文需要进行一起迁移的EAS称为是第一EAS。
结合上述游戏AC的例子，为游戏AC提供服务的2个第一EAS分别表示为图形渲染EAS11和聊天功能EAS12。图形渲染EAS11中的应用上下文1与聊天功能EAS12中的应用上下文2，需要一起进行迁移。具体的，图形渲染EAS11将图形渲染EAS11中的应用上下文1迁移至图形渲染EAS12中，聊天功能EAS12将聊天功能EAS12中的应用上下文2迁移至聊天功能EAS22中，如此，图形渲染EAS21和聊天功能EAS22可以基于各自迁移得到的应用上下文继续为游戏AC提供服务。
在上述多个应用上下文迁移场景中：
EEC、AC均位于终端中，EEC、AC可获取多个第一EAS的标识。即在EEC决策的应用上下文迁移场景，或者由AC决策的应用上下文迁移场景中，EEC或AC可根据多个第一EAS的标识，指示多个第一EAS一起执行应用上下文迁移。
EES中注册有多个第一EAS的配置信息，EES也可获取多个第一EAS的标识。在EES决策的应用上下文迁移场景中，EES可根据多个第一EAS的标识，指示多个第一EAS一起执行应用上下文迁移。本申请中，配置信息具体可以是配置文件(profile)。
但对于多个第一EAS中的一个第一EAS来说，该第一EAS只能获取到自己的配置信息，而无法获取多个第一EAS中除自己以外的其他第一EAS的标识，则无法指示多个第一EAS中除自己以外的其他第一EAS一起执行应用上下文迁移。比如上述游戏AC的例子中，图形渲染EAS11可实现将应用上下文1迁移至图形渲染EAS12中，但是无法指示聊天功能EAS12将应用上下文2迁移至图形渲染EAS22中。也即，在由第一EAS决策的应用上下文迁移场景中，存在多个第一EAS无法一起迁移应用上下文迁移的情况，导致应用上下文迁移过程中存在服务中断。
本申请中，第一EAS的标识，具体可以是第一EAS的地址信息，比如第一EAS的IP地址和/或FQDN。
为此，本申请提供多种应用上下文迁移场景的确定方法的实现方式，用于确定合适的目标应用上下文迁移场景，以避免在应用上下文迁移过程中出现服务中断。例如：
在实现方式一中，第一实体可确定多个应用上下文迁移场景中是否包含EAS决策的应用上下文迁移场景，进而从该多个应用上下文迁移场景中选择目标应用上下文迁移场景。实现方式一具体可参见图3至图6、图12和图13相关实施例中描述。
在实现方式二中，第一实体向多个第一EAS中的第三EAS发送多个第一EAS的标识，以使得该第三EAS具备将多个第一EAS中应用上下文一起迁移的能力。第一实体进而从多个应用上下文迁移场景(包含EAS决策的应用上下文迁移场景)中选择目标应用上下文迁移场景。实现方式二具体可参见图7至图9、图14和图15相关实施例中描述。
在实现方式三中，多个第一EAS中的第四EAS在获取多个第一EAS中应用上下文需一起迁移的指示之后，确定自己支持的应用上下文迁移场景中不包括EAS决策的应用上下文迁移场景，并向第一实体发送自己支持的应用上下文迁移场景。实现方式三具体可参见图10、图11和图16相关实施例中描述。
其中，第一实体是EEC或者EES，具体可参见各实现方式中的说明。
在实现方式一和实现方式二中，多个应用上下文迁移场景可认为是多个候选的应用上下文迁移场景，进一步的，第一实体从该多个应用上下文迁移场景中选择目标应用上下文迁移场景。该目标应用上下文迁移场景具体是第一实体为多个第一EAS中至少一个第一EAS选择的、该至少一个第一EAS对应的应用上下文迁移场景。
如下，结合各流程图解释说明本申请提供的实现方式一至实现方式三。
实现方式一
如图3为本申请提供的实现方式一的第一种应用上下文迁移场景的确定方法的流程示意图：
步骤301，第一实体根据第一信息，确定多个应用上下文迁移场景是否包括EAS决策的应用上下文迁移场景。
其中，第一实体可以是EEC或EES。
其中，第一信息指示多个第一EAS中的应用上下文需一起迁移。也即，第一信息指示多个第一EAS中应用上下文是具有关联关系的，或者多个第一EAS是具有关联关系的。其中，多个第一EAS中的应用上下文需(或需要)一起迁移，也可称为是，多个第一EAS中的应用上下文待一起迁移。
示例1中，第一信息中包括多个第一EAS的标识，该多个第一EAS的标识用于指示多个第一EAS中的应用上下文需一起迁移。结合上述游戏AC的例子，第一信息中可包括图形渲染EAS11和聊天功能EAS12共计两个第一EAS的标识。
示例2中，第一信息中包括第一指示，该第一指示可用于指示多个第一EAS中的应用上下文需一起迁移。比如第一指示占用1比特，当该1比特取值为1时，指示多个第一EAS中的应用上下文需一起迁移。再比如，第一指示为字段“是”，该字段“是”指示多个第一EAS中的应用上下文需一起迁移。
示例3中，第一信息中包括多个第一EAS的标识和第一指示。其中，多个第一EAS的标识可参见示例1中说明，第一指示可参见示例2中说明。
此外，本申请还可以是如下情况中的一个：第一信息是多个第一EAS标识；第一信息是第一指示；第一信息是多个第一EAS标识和第一指示的组合。
可选的，第一实体可接收来自AC的第一信息。具体的，AC中预先配置有第一信息，在第一实体是EEC时，EEC可从AC中接收第一信息，即AC向EEC发送第一信息。在第一实体是EES时，EES可从EEC接收由EEC转发的第一信息，即AC向EEC发送第一信息，EEC再向EES发送第一信息。
此外，还是可以是EEC中预先配置有第一信息。在该情况中，若第一实体是EEC时，则EEC还可从本地的预先配置中获取第一信息。若第一实体是EES时，则EES可从EEC中获取第一信息。
第一实体根据第一信息，确定多个第一EAS中的应用上下文需一起迁移之后，需进一步确定多个应用上下文迁移场景中是否不包括EAS决策的应用上下文迁移场景。
第一实体确定多个应用上下文迁移场景中是否不包括EAS决策的应用上下文迁移场景，可以有如下两种情况：
情况一，第一实体确定多个应用上下文迁移场景中不包括EAS决策的应用上下文迁移场景。示例性的，EAS决策的应用上下文迁移场景是应用上下文迁移场景4。第一实体确定多个应用上下文迁移场景中不包括应用上下文迁移场景4，也即，第一实体可以确定多个应用上下文迁移场景中包括应用上下文迁移场景1至应用上下文迁移场景3、应用上下文迁移场景5和应用上下文迁移场景6。
情况二，第一实体接收第二信息，根据第一信息和第二信息，确定多个应用上下文迁移场景是否包括EAS决策的应用上下文迁移场景。
其中，第二信息指示多个第一EAS中是否存在第三EAS。
第三EAS具有对多个第一EAS中的应用上下文一起迁移的能力。也可以理解，第三EAS具有发现多个第一EAS中除第三EAS以外其他EAS的能力，或者第三EAS具有通知多个第一EAS中除第三EAS以外其他EAS进行应用上下文迁移的能力。
一个具体实现中，第三EAS具有对多个第一EAS中的应用上下文一起迁移的能力，可以是，第三EAS中可存储有多个第一EAS的标识。可选的，第三EAS可接收来自AC的多个第一EAS的标识，或者接收来自EEC的多个第一EAS的标识，或者预先配置有多个第一EAS的标识。
其中，在第三EAS接收来自AC的多个第一EAS的标识的情况中，AC可与第三EAS建立连接，AC通过该建立的连接向第三EAS发送多个第一EAS的标识。示例性的，AC可向多个第一EAS中每个第一EAS发送多个第一EAS的标识，该多个第一EAS中具备决策功能的第一EAS可存储该多个第一EAS的标识，即作为第三EAS。
其中，具备决策功能的第一EAS比如是支持EAS决策的应用上下文迁移场景(比如支持应用上下文迁移场景4)的EAS。
进一步的，第三EAS可以是多个第一EAS中的全部或部分。也即，在多个第一EAS中，若每个第一EAS均具有对多个第一EAS中的应用上下文一起迁移的能力，则每个第一EAS均为第三EAS；在多个第一EAS中，若存在部分第一EAS具有对多个第一EAS中的应用上下文一起迁移的能力，则该部分第一EAS为第三EAS。
在一种可能方式中，第一实体可接收来自多个第一EAS中每个第一EAS发送的第二信息，该第二信息用于指示发送该第二信息的第一EAS是否为第三EAS。第一实体根据该多个第一EAS中每个第一EAS的第二信息，确定多个第一EAS中是否存在第三EAS。
示例性的，第二信息中可包括第一选项或第二选项，第一选项指示发送该第二信息的第一EAS中存储有多个第一EAS的标识，即发送第一选项的第一EAS为第三EAS。第二选项指示发送该第二信息的第一EAS中未存储有多个第一EAS的标识，即发送第二选项的第一EAS不是第三EAS。
示例性的，第二信息可以是第一选项或第二选项。比如，第二信息可以占用1比特，其中，第一选项是该1比特取值为1，第二选项是该1比特取值为0。
在又一种可能方式中，第一实体可接收来自多个第一EAS中第三EAS发送的第二信息。具体的，第一实体在接收到来自第一EAS的第二信息之后，可确定发送该第二信息的第一EAS为第三EAS。示例性的，第二信息中可包括第一选项，或第二信息是第一选项。再示例性的，第二信息中包括多个第一EAS的标识，或第二信息是多个第一EAS的标识。
在情况二的一种可能方式中，在多个第一EAS中不存在第三EAS的情况下，多个应用上下文迁移场景不包括EAS决策的应用上下文迁移场景。
具体的，第一实体根据第一信息确定多个第一EAS中的应用上下文需一起迁移，以及根据第二信息确定多个第一EAS中不存在第三EAS，则可进一步确定多个应用上下文迁移场景不包括EAS决策的应用上下文迁移场景。示例性的，EAS决策的应用上下文迁移场景是应用上下文迁移场景4，第一实体确定多个应用上下文迁移场景中不包括应用上下文迁移场景4，也即确定多个应用上下文迁移场景中包括应用上下文迁移场景1至应用上下文迁移场景3、应用上下文迁移场景5和应用上下文迁移场景6。
在情况二的另一种可能方式中，在多个第一EAS中存在第三EAS的情况下，多个应用上下文迁移场景包括EAS决策的应用上下文迁移场景。
具体的，第一实体根据第一信息确定多个第一EAS中的应用上下文需一起迁移，以及根据第二信息确定多个第一EAS中存在第三EAS，则确定多个应用上下文迁移场景包括EAS决策的应用上下文迁移场景。示例性的，EAS决策的应用上下文迁移场景是应用上下文迁移场景4。第一实体确定多个应用上下文迁移场景中包括应用上下文迁移场景4，也即确定多个应用上下文迁移场景中包括应用上下文迁移场景1至应用上下文迁移场景6。
步骤302，第一实体从多个应用上下文迁移场景中选择目标应用上下文迁移场景。
在一个可能方式中，多个应用上下文迁移场景中不包括EAS决策的应用上下文迁移场景，第一实体可从除EAS决策的应用上下文迁移场景以外的其他应用上下文迁移场景中选择目标应用上下文迁移场景。如此，通过EEC、AC或EES决策的应用上下文迁移场景来实现多个第一EAS中应用上下文一起迁移，避免在应用上下文迁移过程中出现服务中断。
在又一个可能方式中，多个应用上下文迁移场景中包括EAS决策的应用上下文迁移场景，第一实体可从该多个应用上下文迁移场景中选择目标应用上下文迁移场景。进一步的，当第一实体选择的目标应用上下文迁移场景为EEC、AC或EES决策的应用上下文迁移场景时，可实现多个第一EAS中应用上下文一起迁移。当第一实体选择的目标应用上下文迁移场景为EAS决策的应用上下文迁移场景时，可以通过第三EAS来执行决策，即发现或通知多个第一EAS中除第三EAS以外的其他EAS，从而实现多个第一EAS中应用上下文一起迁移。如此，有助于避免在应用上下文迁移过程中出现服务中断。
如图4为本申请提供的实现方式一的第二种应用上下文迁移场景的确定方法的流程示意图。其中，图4示出的应用上下文迁移场景的确定方法具体是图3示出的应用上下文迁移场景的确定方法的一个具体实现方式。该图4相关实施例中未详细描述的技术方案，均可参见图3相关实施例中描述。
步骤401，第一实体根据第一信息，确定多个应用上下文迁移场景不包括EAS决策的应用上下文迁移场景。
其中，第一信息可参见步骤301中关于第一信息的说明。
可选的，第一实体根据第一信息，确定多个应用上下文迁移场景不包括EAS决策的应用上下文迁移场景，具体实现方式可参见步骤301中情况一的说明。
步骤402，第一实体从多个应用上下文迁移场景中选择目标应用上下文迁移场景。
具体的，第一实体从除EAS决策的应用上下文迁移场景以外的其他应用上下文迁移场景中选择目标应用上下文迁移场景。
如此，通过EEC、AC或EES决策的应用上下文迁移场景来实现多个第一EAS中应用上下文一起迁移，有助于避免在应用上下文迁移过程中出现服务中断。
如图5为本申请提供的实现方式一的第三种应用上下文迁移场景的确定方法的流程示意图。其中，图5示出的应用上下文迁移场景的确定方法具体是图3示出的应用上下文迁移场景的确定方法的再一个具体实现方式。该图5相关实施例中未详细描述的技术方案，均可参见图3相关实施例中描述。
步骤501，第一实体接收第二信息。
其中，第二信息可参见步骤301中关于第二信息的说明。
步骤502，第一实体根据第一信息和第二信息，确定多个应用上下文迁移场景是否包括EAS决策的应用上下文迁移场景。
其中，第一信息可参见步骤301中关于第一信息的说明。
可选的，第一实体根据第一信息和第二信息，确定多个应用上下文迁移场景不包括EAS决策的应用上下文迁移场景，具体实现方式可参见步骤301中情况二的关于多个第一EAS中不包括第三EAS的说明。
可选的，第一实体根据第一信息和第二信息，确定多个应用上下文迁移场景包括EAS决策的应用上下文迁移场景，具体实现方式可参见步骤301中情况二的关于多个第一EAS中包括第三EAS的说明。
步骤503，第一实体从多个应用上下文迁移场景中选择目标应用上下文迁移场景。
具体实现方式，可参见步骤302中描述。
需要补充的是，在上述步骤301，第一实体根据第一信息，确定多个应用上下文迁移场景是否包括EAS决策的应用上下文迁移场景之前，第一实体还可执行如下操作：
第一实体可获取EES、AC、多个第一EAS、EEC这些实体各自支持的应用上下文迁移场景，然后根据这些实体各自支持的应用上下文迁移场景，确定该多个实体共同支持的应用上下文迁移场景。第一实体进而根据该多个实体共同支持的应用上下文迁移场景和第一信息，确定多个应用上下文迁移场景中是否包括EAS决策的应用上下文迁移场景。
示例性的，EES、AC、EEC均支持应用上下文迁移场景1至应用上下文迁移场景6，多个第一EAS均支持应用上下文迁移场景1至应用上下文迁移场景4。相应的，第一实体可将多个实体共同支持的应用上下文迁移场景1至应用上下文迁移场景4作为多个应用上下文迁移场景。第一实体进而确定多个应用上下文迁移场景中是否包括应用上下文迁移场景4，若包括，第一实体可从应用上下文迁移场景1至应用上下文迁移场景4中选择目标应用上下文迁移场景；若不包括，第一实体可从应用上下文迁移场景1至应用上下文迁移场景3中选择目标应用上下文迁移场景。
同理的，在上述步骤401之前，以及在上述步骤502之前，第一实体均可获取EES、AC、多个第一EAS、EEC这些实体各自支持的应用上下文迁移场景，然后根据这些实体各自支持的应用上下文迁移场景，确定该多个实体共同支持的应用上下文迁移场景，进而确定多个应用上下文迁移场景中是否包括EAS决策的应用上下文迁移场景。
可选的，在第一实体从多个应用上下文迁移场景中选择目标应用上下文迁移场景之后，第一实体还可发送目标应用上下文迁移场景。
具体的，在第一实体是EES时，EES可向AC、多个第一EAS、EEC分别发送目标应用上下文迁移场景。其中，EES在向AC发送目标应用上下文迁移场景时，具体可以是EES向EEC发送目标应用上下文迁移场景，EEC再向AC发送目标应用上下文迁移场景。相应的，EES、AC、多个第一EAS和EEC可根据该目标应用上下文迁移场景，执行应用上下文迁移中的相关动作。
在第一实体是EEC时，EEC可向EES、AC、多个第一EAS分别发送目标应用上下文迁移场景。其中，EEC在向第一EAS发送目标应用上下文迁移场景时，具体可以是EEC向EES发送目标应用上下文迁移场景，EES再向第一EAS发送目标应用上下文迁移场景。相应的，EES、AC、多个第一EAS和EEC可根据该目标应用上下文迁移场景，执行应用上下文迁移中的相关动作。
如图6为本申请提供的实现方式一的第四种应用上下文迁移场景的确定方法的流程示意图。其中，图6示出的应用上下文迁移场景的确定方法具体是图5示出的应用上下文迁移场景的确定方法的一个具体实现方式，该具体实现方式可由AC、EEC、EES和第三EAS交互实现。该图6相关实施例中未详细描述的技术方案，均可参见图5相关实施例中描述，或者进一步参见图3相关实施例中描述。
步骤601，AC预配置有多个第一EAS的标识。
可选的，AC配置信息(AC profile)中包括第一EAS列表(EAS list)，第一EAS列表可以是由多个第一EAS的标识组成的列表。
AC配置信息中还可包括AC的标识(AC ID)、AC支持的应用上下文迁移场景等。
步骤602，AC向第三EAS发送多个第一EAS的标识(或者称为第一EAS列表)。
其中，具体实现方式可参见步骤301中情况二的关于AC向第三EAS发送多个第一EAS的标识的说明。
在第一实体是EES时，可参见步骤603-a至步骤607-a所示。
步骤603-a，第三EAS向EES发送第二信息。
示例性的，EES可在EAS注册流程中获取来自第三EAS的第二信息。具体的，第三EAS向EES发送EAS注册请求(EAS registration request)，EAS注册请求中包括EAS配置信息(EAS profile)，EAS配置信息中包括第二信息。相应的，EES向第三EAS发送EAS注册响应(EAS registration response)。可选的，EAS配置信息中还包括第三EAS的标识(EAS ID)和第三EAS支持的应用上下文迁移场景。
此外，上述EAS注册流程还可替换为EAS更新流程，即将EAS注册请求替换为EAS更新请求(EAS update request)，EAS注册响应替换为EAS更新响应(EAS update response)。
步骤604-a，AC向EES发送第一信息。
示例性的，EES可基于AC注册流程和EEC注册流程获取来自AC的第一信息。具体的，AC向EEC发送AC注册请求(AC registration request)，AC注册请求中包括AC配置信息，AC配置信息中包括第一信息。可选的，AC配置信息中还包括AC支持的应用上下文迁移场景。相应的，EEC向AC发送AC注册响应(AC registration request)。
EEC进一步向EES发送EEC注册请求(EEC registration request)，其中，EEC注册请求包括AC配置信息，即包括第一信息。相应的，EES向EEC发送EEC注册响应(EEC registration response)。
此外，上述AC注册流程还可替换为AC更新流程，即将AC注册请求替换为AC更新请求(AC update request)，AC注册响应替换为AC更新响应(AC update response)。同理的，上述EEC注册流程还可替换为EEC更新流程，即将EEC注册请求替换为EEC更新请求(EEC update request)，EEC注册响应替换为EEC更新响应(EEC update response)。
本申请中，不限定步骤603-a和步骤604-a的先后顺序。
步骤605-a，EES根据第二信息和第一信息，确定多个应用上下文迁移场景是否包括EAS决策的应用上下文迁移场景。
步骤606-a，EES从多个应用上下文迁移场景中选择目标应用上下文迁移场景。
步骤607-a，EES向AC、EEC和多个第一EAS，分别发送目标应用上下文迁移场景。
其中，EES可通过EEC向AC发送目标应用上下文迁移场景，即，EES先向EEC发送目标应用上下文迁移场景，然后EEC向AC发送目标应用上下文迁移场景。
其中，步骤603-a至步骤607-a的具体实现方式还可进一步参见步骤502中的说明，或者可参见步骤301中情况二的说明。
在第一实体是EEC时，可参见步骤603-b至步骤607-b所示。
步骤603-b，第三EAS向EEC发送第二信息。
具体的，第三EAS可通过EES向EEC发送第二信息，即，第三EAS先向EES发送第二信息，然后EES向EEC发送第二信息。
示例性的，EEC可基于EAS注册流程和EEC注册流程，获取第二信息。示例性的，第三EAS向EES发送EAS注册请求，EAS注册请求中包括EAS配置信息，EAS配置信息中包括第二信息。可选的，EAS配置信息中还包括第三EAS的标识和第三EAS支持的应用上下文迁移场景。相应的，EES向第三EAS发送EAS注册响应。
进一步的，EES接收来自EEC的EEC注册请求，向EEC发送EEC注册响应，该EEC注册响应中包括第二信息。可选的，EEC注册响应中还包括EES支持的应用上下文迁移场景、第三EAS的标识和第三EAS支持的应用上下文迁移场景。
此外，上述EAS注册流程还可替换为EAS更新流程，即将EAS注册请求替换为EAS更新请求，EAS注册响应替换为EAS更新响应。同理的，上述EEC注册流程还可替换为EEC更新流程，即将EEC注册请求替换为EEC更新请求，EEC注册响应替换为EEC更新响应。
步骤604-b，AC向EEC发送第一信息。
示例性的，EEC可在AC注册流程中获取来自AC的第一信息。具体的，AC向EEC发送AC注册请求，AC注册请求中包括AC配置信息，AC配置信息中包括第一信息。相应的，EEC向AC发送AC注册响应。此外，上述AC注册流程还可替换为AC更新流程，即将AC注册请求替换为AC更新请求，AC注册响应替换为AC更新响应。
本申请中，不限定步骤603-b和步骤604-b的先后顺序。
步骤605-b，EEC根据第二信息和第一信息，确定多个应用上下文迁移场景是否包括EAS决策的应用上下文迁移场景。
步骤606-b，EEC从多个应用上下文迁移场景中选择目标应用上下文迁移场景。
步骤607-b，EEC向AC、EEC和多个第一EAS，分别发送目标应用上下文迁移场景。
其中，EEC可通过EES向第一EAS发送目标应用上下文迁移场景，即，EEC先向EES发送目标应用上下文迁移场景，然后EES向第一EAS发送目标应用上下文迁移场景。
其中，步骤603-b至步骤607-b的具体实现方式可参见步骤502中的说明，或者可参见步骤301中情况二的说明。
实现方式二
如图7为本申请提供的实现方式二的第1种应用上下文迁移场景的确定方法的流程示意图。其中，图7示出的应用上下文迁移场景的确定方法中未详细描述的术语、技术方案，均可参见实现方式一中相关实施例中的描述。
[根据细则91更正 26.04.2023]
步骤701，第一实体接收第一信息。
[根据细则91更正 26.04.2023]
其中，第一信息，以及第一实体接收第一信息的说明，可参照步骤301、步骤604-a、或步骤604-b中描述。
在第一信息包括多个第一EAS的标识，或者是多个第一EAS的标识时，第一实体可根据第一信息确定多个第一EAS的标识。
在第一信息包括多个第一EAS的标识和第一指示，或者是多个第一EAS的标识和第一指示的组合时，第一实体可根据第一信息确定多个第一EAS的标识。
在第一信息包括第一指示，或者是第一指示时，第一实体还可根据第一指示，获取多个第一EAS的标识。示例性的，在第一实体是EES时，EES可从AC或者EEC中接收多个第一EAS的标识。在第一实体是EEC时，EEC可从AC中接收多个第一EAS的标识。
其中，步骤701为可选的，在第一实体是EEC时，EEC中可预先配置有第一信息。或者，EEC中可预配置有多个第一EAS的标识。
步骤702，第一实体根据第一信息，向第三EAS发送多个第一EAS的标识。
其中，第三EAS的说明可参见步骤301中情况二中描述。
可选的，第一实体可先接收来自第三EAS的、第三EAS支持的应用上下文迁移场景。第一实体在确定第三EAS具备决策功能之后，向第三EAS发送多个第一EAS的标识。第三EAS具备决策功能比如是第三EAS支持EAS决策的应用上下文迁移场景(比如应用上下文迁移场景4)。
举例来说，多个第一EAS包括EAS1至EAS5，EAS1支持应用上下文迁移场景1至应用上下文迁移场景4，而EAS2至EAS5均只支持应用上下文迁移场景1至应用上下文迁移场景3。第一实体确定EAS1支持应用上下文迁移场景4，向EAS1(即第三EAS)发送多个第一EAS的标识。第一实体确定EAS2至EAS5均不支持应用上下文迁移场景4，可不向EAS2至EAS5发送多个第一EAS的标识。
在一种可能实现方式中，第一实体在确定目标应用上下文迁移场景之后，根据第一信息向第三EAS发送多个第一EAS的标识。
在又一种可能实现方式中，第一实体在确定目标应用上下文迁移场景之后，进一步确定是否根据第一信息向第三EAS发送多个第一EAS的标识。
示例性的，第一实体在确定目标应用上下文迁移场景中包括EAS决策的应用上下文迁移场景(如图7中步骤703)的情况下，进一步根据第一信息向第三EAS发送多个第一EAS的标识。第一实体在确定目标应用上下文迁移场景中不包括EAS决策的应用上下文迁移场景的情况下，可不向第三EAS发送多个第一EAS的标识。示例性的，第一实体可通过同一条消息向第三EAS发送目标应用上下文迁移场景和多个第一EAS的标识，也可通过两条不同消息向第三EAS发送目标应用上下文迁移场景和多个第一EAS的标识。
在另一种可能实现方式中，第一实体可先根据第一信息，向第三EAS发送多个第一EAS的标识，然后再确定目标应用上下文迁移场景。此时，第一实体可从包含EAS决策的应用上下文迁移场景的多个应用上下文迁移场景中选择目标应用上下文迁移场景。
可选的，第一实体在确定目标应用上下文迁移场景时，还可先根据第一信息，确定多个第一EAS中的应用上下文需一起迁移，进而确定目标应用上下文迁移场景，具体可参见步骤302中第一实体确定目标应用上下文迁移场景的相关描述。
可选的，当第一实体是EES时，EES在确定目标应用上下文迁移场景之后，可以向多个第一EAS、EEC和AC分别发送目标应用上下文迁移场景。相应的，EES、AC、多个第一EAS和EEC可根据该目标应用上下文迁移场景，执行应用上下文迁移中的相关动作。
当第一实体是EEC时，EEC在确定目标应用上下文迁移场景之后，可以向多个第一EAS、EES和AC分别发送目标应用上下文迁移场景。相应的，EES、AC、多个第一EAS和EEC可根据该目标应用上下文迁移场景，执行应用上下文迁移中的相关动作。
如图8为本申请提供的实现方式二的第2种应用上下文迁移场景的确定方法的流程示意图。其中，图8示出的应用上下文迁移场景的确定方法具体是图7示出的应用上下文迁移场景的确定方法的一个具体实现方式。图8相关实施例中未详细描述的技术方案，均可参见图7相关实施例中描述，或进一步参见实现方式一相关实施例中的描述。
步骤801，AC预配置有多个第一EAS的标识。该步骤可参见步骤601中描述。
在第一实体是EEC时，可参见步骤802-a至步骤805-a所示。
步骤802-a，AC向EEC发送第一信息。该步骤可参见步骤701中描述。
需要补充的是，EEC中也可以配置有第一信息，EEC可无需从AC中接收第一信息，即步骤802-a为可选步骤。
步骤803-a，EEC根据第一信息向第三EAS发送多个第一EAS的标识。
步骤804-a，EEC确定目标应用上下文迁移场景。
步骤805-a，EEC向AC、EEC和多个第一EAS，分别发送目标应用上下文迁移场景。
其中，该步骤803-a至步骤805-a可参见步骤702中描述。
在第一实体是EES时，可参见步骤802-b至步骤805-b所示。
步骤802-b，AC向EES发送第一信息。
具体的，AC可通过EEC向EES发送第一信息，即，AC先向EEC发送第一信息，然后EEC向EES发送第一信息。该步骤可参见步骤701中描述。
此处，EEC中也可以配置有第一信息，EES可直接从EEC中接收第一信息。
步骤803-b，EES根据第一信息向第三EAS发送多个第一EAS的标识。
步骤804-b，EES确定目标应用上下文迁移场景。
步骤805-b，EES向AC、EEC和多个第一EAS，分别发送目标应用上下文迁移场景。
其中，该步骤803-b至步骤805-b可参见步骤702中描述。
如图9为本申请提供的实现方式二的第3种应用上下文迁移场景的确定方法的流程示意图。其中，图9示出的应用上下文迁移场景的确定方法具体是图7示出的应用上下文迁移场景的确定方法的再一个具体实现方式。图9相关实施例中未详细描述的技术方案，均可参见图7相关实施例中描述，或进一步参见实现方式一相关实施例中的描述。
步骤901，AC预配置有多个第一EAS的标识。
该步骤可参见步骤601中描述。
进一步的，在第一实体是EEC时，可参见步骤902-a至步骤904-a所示。
步骤902-a，AC向EEC发送第一信息。
需要补充的是，EEC中也可以配置有第一信息，EEC可无需从AC中接收第一信息，即步骤902-a为可选步骤。
该步骤902-a中未详尽描述的内容还可参见步骤701中描述。
步骤903-a，EEC确定目标应用上下文迁移场景。
步骤904-a，EEC根据第一信息，向第三EAS发送目标应用上下文迁移场景和多个第一EAS的标识。
具体的，EEC可通过EES向第三EAS发送目标应用上下文迁移场景和多个第一EAS的标识，即EEC先向EES发送目标应用上下文迁移场景和多个第一EAS的标识，EES再向第三EAS发送目标应用上下文迁移场景和多个第一EAS的标识。
其中，EES在转发目标应用上下文迁移场景和多个第一EAS的标识时，也可获取到该目标应用上下文迁移场景。
EEC还可向AC、多个第一EAS中除第三EAS以外的其他第一EAS分别发送目标应用上下文迁移场景。相应的，EES、AC、多个第一EAS和EEC可根据该目标应用上下文迁移场景，执行应用上下文迁移中的相关动作。
步骤903-a和步骤904-a中未详尽描述的内容还可参见步骤702和步骤703中描述。
在第一实体是EES时，可参见步骤902-b至步骤904-b所示。
步骤902-b，AC向EES发送第一信息。
具体的，AC可通过EEC向EES发送第一信息，即，AC先向EEC发送第一信息，然后EEC向EES发送第一信息。
需要补充的是，EEC中也可以配置有第一信息，EES直接从EEC中接收第一信息。
该步骤902-b中未详尽描述的内容还可参见步骤701中描述。
步骤903-b，EES确定目标应用上下文迁移场景。
步骤904-b，EES根据第一信息，向第三EAS发送目标应用上下文迁移场景和多个第一EAS的标识。
此外，EES还可向AC、多个第一EAS中除第三EAS以外的其他第一EAS、EEC分别发送目标应用上下文迁移场景。相应的，EES、AC、多个第一EAS和EEC可根据该目标应用上下文迁移场景，执行应用上下文迁移中的相关动作。
步骤903-b和步骤904-b中未详尽描述的内容还可参见步骤702和步骤703中描述。
实现方式三
如图10为本申请提供的实现方式三的第(1)种应用上下文迁移场景的确定方法的流程示意图。其中，图10示出的应用上下文迁移场景的确定方法中未详细描述的技术方案，均可参见实现方式一和实现方式二相关实施例中的描述。
步骤1001，第四EAS根据第一信息，确定第四EAS支持的应用上下文迁移场景不包括EAS决策的应用上下文迁移场景。
其中，第一信息可参见步骤301中关于第一信息的说明。
第四EAS可以是多个第一EAS中的一个或多个。第四EAS中可预配置第一信息，或者第四EAS可接收来自AC、EEC或者EES的第一信息，具体方式可参见第三EAS预配置第一信息，或第三EAS接收来自AC、EEC或者EES的第一信息的实现方式。
具体的，第四EAS根据第一信息，确定多个第一EAS中的应用上下文需一起迁移，进而确定第四EAS支持的应用上下文迁移场景不包括EAS决策的应用上下文迁移场景。
示例性的，第四EAS配置为可支持应用上下文迁移场景1至应用上下文迁移场景4。第四EAS根据第一信息，确定多个第一EAS中的应用上下文需一起迁移，则确定第四EAS可支持应用上下文迁移场景1至应用上下文迁移场景3。
步骤1002，第四EAS发送第四EAS支持的应用上下文迁移场景。
具体的，第四EAS可向第一实体发送第四EAS支持的应用上下文迁移场景。在第一实体是EES时，第四EAS向EES发送第四EAS支持的应用上下文迁移场景。在第一实体是EEC时，第四EAS可通过EES向EEC发送第四EAS支持的应用上下文迁移场景。
相应的，第一实体接收第四EAS支持的应用上下文迁移场景，根据第四EAS支持的应用上下文迁移场景(不包括EAS决策的应用上下文迁移场景)，选择目标应用上下文迁移场景。结合上述例子，第一实体确定第四EAS可支持应用上下文迁移场景1至应用上下文迁移场景3，第一实体可从应用上下文迁移场景1至应用上下文迁移场景3中选择目标应用上下文迁移场景。其中，第一实体选择目标应用上下文迁移场景的实现方式，还可参见步骤302中说明。
如此，第一实体可选择除EAS决策的应用上下文迁移场景以外的应用上下文迁移场景，作为目标应用上下文迁移场景，即第一实体选择的目标应用上下文迁移场景为EEC、AC或EES决策的应用上下文迁移场景时，有助于实现多个第一EAS中应用上下文一起迁移，进而避免在应用上下文迁移过程中出现服务中断。
可选的，当第一实体是EES时，EES在确定目标应用上下文迁移场景之后，可以向多个第一EAS、EEC和AC分别发送目标应用上下文迁移场景。相应的，EES、AC、多个第一EAS和EEC可根据该目标应用上下文迁移场景，执行应用上下文迁移中的相关动作。
当第一实体是EEC时，EEC在确定目标应用上下文迁移场景之后，可以向多个第一EAS、EES和AC分别发送目标应用上下文迁移场景。相应的，EES、AC、多个第一EAS和EEC可根据该目标应用上下文迁移场景，执行应用上下文迁移中的相关动作。
如图11为本申请提供的实现方式三的第(2)种应用上下文迁移场景的确定方法的流程示意图。其中，图11示出的应用上下文迁移场景的确定方法是图10示出的应用上下文迁移场景的确定方法的一个具体实现方式。图11相关实施例中未详细描述的技术方案，均可参见图10相关实施例中描述，或进一步参见实现方式一和实现方式二相关实施例中的描述。
步骤1101，AC预配置有多个第一EAS的标识。
AC预配置有多个第一EAS的标识的具体实现方式可参见步骤601中描述。
步骤1102，AC向第四EAS发送多个第一EAS的标识。
示例性的，AC向多个第一EAS中全部EAS或者部分EAS发送多个第一EAS的标识。
其中，AC与第四EAS连通，AC可直接向第四EAS发送多个第一EAS的标识。
或者，AC可通过EEC、EES，向第四EAS发送多个第一EAS的标识，参见图11中示出，AC先向EEC发送多个第一EAS的标识，EEC再向EES发送多个第一EAS的标识，EES再向第四EAS发送多个第一EAS的标识。
在第一实体是EES时，可参见步骤1103-a至步骤1106-a所示。
步骤1103-a，第四EAS根据多个第一EAS的标识，确定第四EAS支持的应用上下文迁移场景不包括EAS决策的应用上下文迁移场景。具体参见步骤1001相关实施例中描述。
步骤1104-a，第四EAS向EES发送第四EAS支持的应用上下文迁移场景。
步骤1105-a，EES根据第四EAS支持的应用上下文迁移场景，选择目标应用上下文迁移场景。
步骤1106-a，EES向AC、EEC和多个第一EAS，分别发送目标应用上下文迁移场景。
其中，EES可通过EEC向AC发送目标应用上下文迁移场景，即，EES先向EEC发送目标应用上下文迁移场景，然后EEC向AC发送目标应用上下文迁移场景。
其中，步骤1104-a至步骤1106-a还可参见步骤1002相关实施例中描述。
[根据细则91更正 26.04.2023]
在第一实体是EEC时，可参见步骤1103-b至步骤1106-b所示。
[根据细则91更正 26.04.2023]
步骤1103-b，第四EAS根据多个第一EAS的标识，确定第四EAS支持的应用上下文迁移场景不包括EAS决策的应用上下文迁移场景。可参见步骤1001相关实施例中描述。
[根据细则91更正 26.04.2023]
步骤1104-b，第四EAS向EEC发送第四EAS支持的应用上下文迁移场景。
[根据细则91更正 26.04.2023]
步骤1105-b，EEC根据第四EAS支持的应用上下文迁移场景，选择目标应用上下文迁移场景。
[根据细则91更正 26.04.2023]
步骤1106-b，EEC向AC、EES和多个第一EAS，分别发送目标应用上下文迁移场景。其中，EEC可通过EES向第一EAS发送目标应用上下文迁移场景。
[根据细则91更正 26.04.2023]
其中，步骤1104-b至步骤1106-b还可参见步骤1002相关实施例中描述。
本申请中，AC还可由除多个第一EAS以外的其他EAS提供服务。可以理解，AC由多个第二EAS来提供服务，其中多个第一EAS是多个第二EAS中的部分。比如，游戏AC不仅需要由图形渲染EAS、聊天功能EAS来提供服务，还需要由游戏加速EAS来提供服务。图形渲染EAS、聊天功能EAS为第一EAS，即AC在图形渲染EAS中的应用上下文，与AC在聊天功能EAS中的应用上下文之间是具有关联关系的。而游戏加速EAS中的应用上下文可独立于图形渲染EAS、聊天功能EAS中的应用上下文。AC在游戏加速EAS中的应用上下文无需与图形渲染EAS、聊天功能EAS中的应用上下文一起迁移。
本申请中，第一EAS又可称为是关联EAS(linked EAS)，即多个第一EAS之间是相互关联的，也即是多个第一EAS的应用上下文之间是关联的。多个第二EAS中除第一EAS以外的其他EAS可称为是非关联EAS(非linked EAS)。关联EAS，非关联EAS只是一种示例性名称，本领域技术人员也可以做其他命名，例如，第一EAS又可称为是配对EAS(pair EAS)，多个第二EAS中除第一EAS以外的其他EAS又可以称为非配对EAS(非pair EAS)，此时该第二EAS又可以称为关联EAS或者共同服务EAS等等；再例如，第一EAS又可称为是共同迁移EAS(ACR-together EAS)，第二EAS又可称为是非共同迁移EAS(非ACR-together EAS)，此时该第二EAS又可以称为关联EAS或者共同服务EAS等等。进一步的，由第一EAS的标识组成的第一EAS列表，又可称为是关联EAS列表(linked EAS list)，配对EAS列表(pair EAS list)，或共同迁移EAS列表(ACR-together EAS list)等等。
可以理解，非linked EAS中的应用上下文可独立于linked EAS中的应用上下文。在linked EAS中的应用上下文发生一起迁移时，非linked EAS中的应用上下文，可以不发生迁移，或者不需要与linked EAS中应用上下文一起迁移。在非linked EAS中上下文发生迁移时，非linked EAS可以只迁移自己本地的应用上下文，而无需触发其他的非linked EAS，或者linked EAS进行应用上下文的迁移。
在实现方式一中，AC中可预先配置有多个第二EAS的标识，AC可向第一实体发送多个第二EAS的标识，其中，多个第二EAS的标识中可进一步包括第一信息(具体是多个第一EAS的标识)。相应的，第一实体可从多个第二EAS的标识中获取多个第一EAS的标识。其中，AC向第一实体发送多个第二EAS的标识的实现方式，可参见步骤301中AC向第一实体发送多个第一EAS的标识的实现方式。又或者，在第一实体是EEC时，EEC中也可预先配置有多个第二EAS的标识，第一实体可从多个第二EAS的标识中获取多个第一EAS的标识。进一步的，第三EAS可以从AC或EEC中获取多个第二EAS的标识，根据多个第二EAS的标识中的多个第一EAS的标识，向第一实体发送第二指示。或者，第三EAS中预配置有多个第二EAS的标识，第三EAS根据多个第二EAS的标识中的多个第一EAS的标识，向第一实体发送第二指示。
在实现方式二中，AC中可预先配置有多个第二EAS的标识，AC可向第一实体发送多个第二EAS的标识，其中多个第二EAS的标识中可进一步包括第一信息(具体是多个第一EAS的标识)。相应的，第一实体可从多个第二EAS的标识中获取多个第一EAS的标识。第一实体向第三EAS发送多个第二EAS的标识，或者发送多个第一EAS的标识，相应的，第三EAS获取到多个第一EAS的标识。
在实现方式三中，AC中可预先配置有多个第二EAS的标识，AC可向第四EAS发送多个第二EAS的标识，其中，多个第二EAS的标识中可进一步包括第一信息(具体是多个第一EAS的标识)。相应的，第四EAS从多个第二EAS的标识中获取多个第一EAS的标识，确定第四EAS支持的应用上下文迁移场景不包括EAS决策的应用上下文迁移场景。
进一步的，在第一实体确定出目标应用上下文迁移场景之前，第一实体可获取EES、AC、多个第二EAS、EEC这些实体各自支持的应用上下文迁移场景，然后根据这些实体各自支持的应用上下文迁移场景，确定该多个实体共同支持的应用上下文迁移场景。第一实体再基于上述实现方式一至实现方式三中任一种实现方式，从多个实体共同支持的应用上下文迁移场景中，确定目标应用上下文迁移场景。
在第一实体确定出目标应用上下文迁移场景之后，可将目标应用上下文迁移场景发送至多个第二EAS中。具体的，当第一实体是EEC时，EEC可向多个第二EAS、AC和EES发送目标应用上下文迁移场景，相应的，多个第二EAS、AC、EES和EEC可根据该目标应用上下文迁移场景，执行应用上下文迁移中的相关动作。当第一实体是EES时，EES可向多个第二EAS、AC和EEC发送目标应用上下文迁移场景，相应的，多个第二EAS、AC、EES和EEC可根据该目标应用上下文迁移场景，执行应用上下文迁移中的相关动作。
此外，多个第一EAS还可以是多个第二EAS的全部，即多个第一EAS是多个第二EAS，多个第二EAS中应用上下文均具有关联关系，需要一起发生迁移。或者可以理解，该多个第一EAS是为同一个AC提供服务的EAS。则，对于本申请来说，第一EAS和第二EAS是相同的，可以互相替换使用，名称也可以是相同的。
如下，结合具体场景提供5种第一实体确定目标应用上下文迁移场景的实施例。
实施例1
该实施例1为图6的一种更为具体的实现方式。
在图12示出的实施例1的流程图中：步骤1201是步骤602的具体实现方式，步骤1202和步骤1203是步骤603-a的具体实现方式，步骤1205至步骤1208是步骤604-a的具体实现方式，步骤1209是步骤605-a和步骤606-a的具体实现方式，步骤1204、步骤1210至步骤1213是步骤607-a的具体实现方式。
步骤1201，AC向第三EAS发送第一EAS列表。
步骤1202，第三EAS向EES发送EAS注册请求。其中，EAS注册请求包括EAS配置信息(EAS profile)，EAS配置信息中可以包括第三EAS的标识(EAS ID)、第二信息和第三EAS支持的应用上下文迁移场景。其中，第二信息具体是第一EAS列表。
步骤1203，EES向第三EAS发送EAS注册响应。
步骤1204，EEC、第三EAS分别向EES订阅目标应用上下文迁移场景。
步骤1205，AC预配置有AC配置信息。其中，AC配置信息可以包括AC支持的应用上下文迁移场景、AC的标识和第一EAS列表。
步骤1206，AC向EEC发送AC注册请求，其中，AC注册请求包括AC配置信息(即包括第一EAS列表)。
步骤1207，EEC向AC发送AC注册响应。
步骤1208，EEC向EES发送EEC注册请求，其中，EEC注册请求包括AC配置信息(即包括第一EAS列表)和EEC支持的应用上下文迁移场景。
步骤1209，EES根据AC配置信息中第一EAS列表，确定多个第一EAS的应用上下文需一起迁移。EES根据AC、EEC、EES和多个第一EAS支持的应用上下文迁移场景，确定多个应用上下文迁移场景中包括EAS决策的应用上下文迁移场景，EES进而从多个应用上下文迁移场景中选择目标应用上下文迁移场景。
步骤1210，EES向第三EAS发送应用上下文迁移场景通知，应用上下文迁移场景通知中包括目标应用上下文迁移场景。
步骤1211，EES向EEC发送EEC注册响应，该EEC注册响应包括目标应用上下文迁移场景。
步骤1212，AC向EEC订阅目标应用上下文迁移场景。
步骤1213，EEC向AC发送应用上下文迁移场景通知，应用上下文迁移场景通知中包括目标应用上下文迁移场景。
实施例2
该实施例2具体为图6的又一种具体实现方式。
在图13示出的实施例2的流程图中：步骤1301是步骤602的具体实现方式，步骤1302至步骤1305是步骤603-b的具体实现方式，步骤1306是步骤601的具体实现方式，步骤1307和步骤1308是步骤604-b的具体实现方式，步骤1309是步骤605-b和步骤606-b的具体实现方式，步骤1310至步骤1315是步骤607-b的具体实现方式。
步骤1301，AC向第三EAS发送第一EAS列表。
步骤1302，第三EAS向EES发送EAS注册请求。其中，EAS注册请求包括第二信息，第二信息具体是第一EAS列表。
步骤1303，EES向第三EAS发送EAS注册响应。
步骤1304，EEC向EES发送EEC注册请求。
步骤1305，EES向EEC发送EEC注册响应，该EEC注册响应中可以包括EES支持的应用上下文迁移场景、第三EAS支持的应用上下文迁移场景和第一EAS列表。
步骤1306，AC预配置有AC配置信息，其中，AC配置信息可以包括AC支持的应用上下文迁移场景、AC的标识和第一EAS列表。
步骤1307，AC向EEC发送AC注册请求，其中，AC注册请求包括AC配置信息(即包括第一EAS列表)。
步骤1308，EEC向AC发送AC注册响应。
步骤1309，EEC根据AC配置信息中第一EAS列表，确定多个第一EAS的应用上下文需一起迁移。EES根据AC、EEC、EES和多个第一EAS支持的应用上下文迁移场景，确定多个应用上下文迁移场景中包括EAS决策的应用上下文迁移场景，EES进而从该多个应用上下文迁移场景中选择目标应用上下文迁移场景。
步骤1310，EEC向EES发送EAS发现请求，EAS发现请求中包括目标应用上下文迁移场景。
步骤1311，EES向EEC发送EAS发现响应。
步骤1312，第三EAS向EES订阅目标应用上下文迁移场景。
步骤1313，EES向第三EAS发送应用上下文迁移场景通知，应用上下文迁移场景通知中包括目标应用上下文迁移场景。
步骤1314，AC向EEC订阅目标应用上下文迁移场景。
步骤1315，EEC向AC发送应用上下文迁移场景通知，应用上下文迁移场景通知中包括目标应用上下文迁移场景。
实施例3
该实施例3具体为图8的一种具体实现方式。
在图14示出的实施例3的流程图中：步骤1402是步骤801的具体实现方式，步骤1403至步骤1405是步骤802-b的具体实现方式，步骤1406和步骤1407是步骤803-b的具体实现方式，步骤1408是步骤804-b的具体实现方式，步骤1401、步骤1409至步骤1412是步骤805-b的具体实现方式。
具体可参见图14所示：
步骤1401，EEC、第三EAS分别向EES订阅目标应用上下文迁移场景。
步骤1402，AC预配置有AC配置信息。其中，AC配置信息包括AC支持的应用上下文迁移场景、AC的标识和第一EAS列表，第一EAS列表可以是由多个第一EAS的标识组成的列表。
步骤1403，AC向EEC发送AC注册请求，其中，AC注册请求包括AC配置信息。
步骤1404，EEC向AC发送AC注册响应。
步骤1405，EEC向EES发送EEC注册请求，其中，EEC注册请求包括AC配置信息和EEC支持的应用上下文迁移场景。
步骤1406，第三EAS向EES发送EAS注册请求，其中，EAS注册请求包括EAS配置信息。EAS配置信息中包括第三EAS的标识和第三EAS支持的应用上下文迁移场景。
步骤1407，EES向第三EAS发送EAS注册响应，其中，EAS注册响应包括AC的标识和第一EAS列表。
步骤1408，EES根据AC配置信息中第一EAS列表，确定多个第一EAS需一起迁移应用上下文。EES根据AC、EEC、EES和多个第一EAS支持的应用上下文迁移场景，确定多个应用上下文迁移场景中包括EAS决策的应用上下文迁移场景，EES进而从该多个应用上下文迁移场景中确定目标应用上下文迁移场景。
步骤1409，EES向第三EAS发送应用上下文迁移场景通知，应用上下文迁移场景通知包括目标应用上下文迁移场景。
步骤1410，EES向EEC发送EEC注册响应，该EEC注册响应中包括目标应用上下文迁移场景。
步骤1411，AC向EEC订阅目标应用上下文迁移场景。
步骤1412，EEC向AC发送应用上下文迁移场景通知，应用上下文迁移场景通知中包括目标应用上下文迁移场景。
实施例4
该实施例4具体为图9的一种具体实现方式。
在图15示出的实施例4的流程图中：步骤1504至步骤1507是步骤902-b的具体实现方式，步骤1508是步骤903-b的具体实现方式，步骤1501至步骤1503、步骤1509至步骤1512是步骤904-b的具体实现方式。
步骤1501，第三EAS向EES发送EAS注册请求，其中，EAS注册请求包括EAS配置信息，EAS配置信息中包括第三EAS的标识和第三EAS支持的应用上下文迁移场景。
步骤1502，EES向第三EAS发送EAS注册响应。
步骤1503，EEC、第三EAS分别向EES订阅目标应用上下文迁移场景。
步骤1504，AC预配置有AC配置信息，其中，AC配置信息包括AC支持的应用上下文迁移场景、AC的标识和第一EAS列表。
步骤1505，AC向EEC发送AC注册请求，其中，AC注册请求包括AC配置信息。
步骤1506，EEC向AC发送AC注册响应。
步骤1507，EEC向EES发送EEC注册请求，其中，EEC注册请求包括AC配置信息和EEC支持的应用上下文迁移场景。
步骤1508，EES根据AC配置信息中第一EAS列表，确定多个第一EAS的应用上下文需一起迁移。EES根据AC、EEC、EES和多个第一EAS支持的应用上下文迁移场景，确定目标应用上下文迁移场景。
步骤1509，EES向第三EAS发送应用上下文迁移场景通知，应用上下文迁移场景通知中包括目标应用上下文迁移场景和第一EAS列表。
步骤1510，EES向EEC发送EEC注册响应，该EEC注册响应包括目标应用上下文迁移场景。
步骤1511，AC向EEC订阅目标应用上下文迁移场景。
步骤1512，EEC向AC发送应用上下文迁移场景通知，应用上下文迁移场景通知中包括目标应用上下文迁移场景。
实施例5
该实施例5具体为图11的一种具体实现方式。
在图16示出的实施例5的流程图中：步骤1602是步骤1101的具体实现方式，步骤1603至步骤1606是步骤1102的具体实现方式，步骤1607是步骤1103-a的具体实现方式，步骤1608和步骤1609是步骤1104-a的具体实现方式，步骤1610是步骤1105-a的具体实现方式，步骤1601、步骤1611至步骤1614是步骤1106-a的具体实现方式。
具体可参见图16所示：
步骤1601，EEC、第四EAS分别向EES订阅目标应用上下文迁移场景。
步骤1602，AC预配置有AC配置信息。其中，AC配置信息包括AC支持的应用上下文迁移场景、AC的标识和第一EAS列表，第一EAS列表可以是由多个第一EAS的标识组成的列表。
步骤1603，AC向EEC发送AC注册请求，其中，AC注册请求包括AC配置信息(即包括第一EAS列表)。
步骤1604，EEC向AC发送AC注册响应。
步骤1605，EEC向EES发送EEC注册请求，其中，EEC注册请求包括AC配置信息(即包括第一EAS列表)和EEC支持的应用上下文迁移场景。
步骤1606，EES向第四EAS发送AC信息通知(AC information notification)。其中，AC信息通知中可包括第一EAS列表。
步骤1607，第四EAS根据第一EAS列表，确定第四EAS支持的应用上下文迁移场景不包括EAS决策的应用上下文迁移场景。
步骤1608，第四EAS向EES发送EAS注册请求。
其中，EAS注册请求包括EAS配置信息。EAS配置信息中包括第四EAS的标识和第四EAS支持的应用上下文迁移场景。
步骤1609，EES向第四EAS发送EAS注册响应。
步骤1610，EES根据AC、EEC、EES和多个第一EAS支持的应用上下文迁移场景，确定目标应用上下文迁移场景。
步骤1611，EES向第四EAS发送应用上下文迁移场景通知，应用上下文迁移场景通知包括目标应用上下文迁移场景。
步骤1612，EES向EEC发送EEC注册响应，该EEC注册响应中包括目标应用上下文迁移场景。
步骤1613，AC向EEC订阅目标应用上下文迁移场景。
步骤1614，EEC向AC发送应用上下文迁移场景通知，应用上下文迁移场景通知中包括目标应用上下文迁移场景。
此外，上述实施例3至5中，第一实体也可替换为EEC，区别在于第一实体与第一EAS之间是直接通信，还是通过EES进行间接通信；以及在于第一实体与AC之间是直接通信，还是通过EEC进行间接通信。以及各实体之间的具体消息存在不同。
上述步骤实施例1至实施例5中，注册请求均可替换为更新请求(update request)，注册响应均可替换为更新响应(update response)。比如EAS注册请求替换为EAS更新请求(EAS update request)，EAS注册响应替换为EAS更新响应(EAS update response)等。当然，上述各信息也可承载于其他类型的消息中，本申请不做限定。
此外，在上述实现方式一中，第一实体还可进一步根据多个第一EAS的能力信息，或者根据第二实体的能力信息，确定多个应用上下文迁移场景中是否包含EAS决策的应用上下文迁移场景(或称为由EAS决策的应用上下文迁移场景、由第一EAS决策的应用上下文迁移场景)，进而从该多个应用上下文迁移场景中选择目标应用上下文迁移场景。
具体可包括实现方式1和实现方式2：
实现方式1，第一实体根据多个第一EAS的能力信息，确定多个第一EAS中是否存在某个第一EAS具备处理关联的EAS中的应用上下文一起迁移的能力。随后，第一实体再确定多个应用上下文迁移场景中是否包含EAS决策的应用上下文迁移场景，并从该多个应用上下文迁移场景中选择目标应用上下文迁移场景。
具体可参见图17示出的一种应用上下文迁移场景的确定方法的流程示意图。
步骤1701，第一实体获取多个第一EAS的能力信息。
可选的，第一实体接收多个第一EAS的能力信息。
第一实体可以是EEC或EES。示例性的，当第一实体是EEC时，EEC接收由EES转发的、多个第一EAS的能力信息；当第一实体是EES时，EES接收来自多个第一EAS中每个第一EAS的、该第一EAS的能力信息，从而获取到该多个第一EAS的能力信息。
多个第一EAS是关联的EAS，即多个第一EAS中应用上下文是具有关联关系的，进一步的，关联的EAS(或者具有关联关系的EAS)中的应用上下文需一起迁移。其中，多个第一EAS、关联的EAS、应用上下文需一起迁移等均可参见上述步骤301中描述，还可参见上述图11相关实施例之后的补充说明。
可选的，第一实体还可接收第一信息，以及根据第一信息，确定多个第一EAS是关联的EAS，或者确定多个第一EAS的应用上下文需一起迁移。其中，第一信息的解释、第一实体接收第一信息的方式、第一实体确定多个第一EAS的应用上下文需一起迁移的方式，可参见上述步骤301中描述。
对于多个第一EAS中的一个第一EAS，该第一EAS的能力信息指示该第一EAS是否具备处理关联的EAS中的应用上下文一起迁移的能力。
一个具体实现中，第一EAS的能力信息指示该第一EAS是否具备如下能力1至能力4中的一项或多项：
能力1，获取多个第一EAS的标识的能力。或者说，获取关联的EAS的标识的能力，或获取需要进行应用上下文一起迁移的EAS的标识的能力等。
可选的，第一EAS可接收来自AC的多个第一EAS的标识，或者接收来自EEC的多个第一EAS的标识，或者预先配置有多个第一EAS的标识，或者预先存储有多个第一EAS的标识。如此，该第一EAS即具备获取多个第一EAS的标识的能力。
能力2，向多个第一EAS中除该第一EAS以外的其他EAS(即其他的第一EAS)发送迁移通知的能力。
示例性的，能力2是通过该第一EAS与多个第一EAS中除该第一EAS以外的其他EAS之间的应用层，向该其他EAS发送迁移通知的能力。
能力3，接收来自多个第一EAS中除该第一EAS以外的其他EAS的迁移通知的能力。示例性的，能力3是通过该第一EAS与多个第一EAS中除该第一EAS以外的其他EAS之间的应用层，接收来自该其他EAS的迁移通知的能力。
本申请中，迁移通知用于触发应用上下文迁移，即在某个EAS接收到该迁移通知之后，基于该迁移通知的触发，进行应用上下文迁移。举例来说，EAS1向EAS2发送迁移通知，EAS2基于该迁移通知的触发，进行应用上下文迁移。其中，EAS1具备向多个第一EAS中其他EAS发送迁移通知的能力(即能力2)，EAS2具备接收来自多个第一EAS中其他EAS的迁移通知的能力(即能力3)。
能力4，支持由第一EAS决策的应用上下文迁移场景的能力。
示例性的，第一EAS的配置信息中包括第一EAS支持的应用上下文迁移场景，且该第一EAS支持的应用上下文迁移场景中包括由第一EAS决策的应用上下文迁移场景，则表明第一EAS是具备能力4的。
步骤1702，第一实体根据多个第一EAS的能力信息，为多个第一EAS确定对应的目标应用上下文迁移场景。
一个具体实现中，第一实体根据多个第一EAS的能力信息，确定目标应用上下文迁移场景中是否包括由第一EAS决策的应用上下文迁移场景。
示例性的，第一实体在根据多个第一EAS的能力信息，确定多个第一EAS中包括的一个第一EAS具备处理关联的EAS中的应用上下文一起迁移的能力时，第一实体确定目标应用上下文迁移场景中包括由该一个第一EAS决策的应用上下文迁移场景。
再示例性的，第一实体在根据多个第一EAS的能力信息，确定多个第一EAS均不具备处理关联的EAS中的应用上下文一起迁移的能力时，第一实体确定目标应用上下文迁移场景中不包括由第一EAS决策的应用上下文迁移场景。
其中，第一实体根据第一EAS的能力信息，确定第一EAS是否具备处理关联的EAS中的应用上下文一起迁移的能力时，具体可以是，第一实体根据第一EAS的能力信息，确定第一EAS是否具备上述能力1、能力2和能力4中一项或多项。当第一实体确定第一EAS具备上述能力1、能力2和能力4中一项或多项时，即确定第一EAS具备处理关联的EAS中的应用上下文一起迁移的能力。
可以理解，第一实体在确定第一EAS具备第一能力时，即确定第一EAS具备处理关联的EAS中的应用上下文一起迁移的能力；第一实体在确定第一EAS不具备该第一能力时，即确定第一EAS不具备处理关联的EAS中的应用上下文一起迁移的能力。其中，第一能力是能力1、能力2和能力4中的某一项。比如，第一能力是能力1，当第一实体确定第一EAS具备能力1时，即确定第一EAS具备处理关联的EAS中的应用上下文一起迁移的能力；当第一实体确定第一EAS不具备能力1时，即确定第一EAS不具备处理关联的EAS中的应用上下文一起迁移的能力。当第一能力是能力2或能力4时，实现方式与上述能力1类似，可将上述“能力1”替换为“能力2”理解，或者将上述“能力1”替换为“能力3”理解。
第一实体还可在确定第一EAS具备第一能力组时，即确定第一EAS具备处理关联的EAS中的应用上下文一起迁移的能力，第一实体在确定第一EAS不具备该第一能力组中的任一个能力时，即确定第一EAS不具备处理关联的EAS中的应用上下文一起迁移的能力。其中，第一能力组是能力1、能力2和能力4中的某多项的组合。比如，第一能力组由能力1和能力2组成，当第一实体确定第一EAS具备能力1和能力2时，即确定第一EAS具备处理关联的EAS中的应用上下文一起迁移的能力；当第一实体确定第一EAS不具备能力1或能力2时，即确定第一EAS不具备处理关联的EAS中的应用上下文一起迁移的能力。此外，第一能力组还可以是能力1、能力2和能力4的其他组合方式，该其他组合方式的实现与上述能力1和能力2的组合方式类似，比如对于能力2和能力4组成的第一能力组，可将上述“能力1和能力2”替换为“能力2和能力4”，以及将上述“能力1或能力2”替换为“能力2或能力4”理解。
此外，还可通过第一EAS的能力信息指示第一EAS是否具备其他能力(比如能力3)，来表明第一EAS是否具备处理关联的EAS中的应用上下文一起迁移的能力，本申请不限定。
此处，用于决策的第一EAS是多个第一EAS中的一个。为方便描述，可将此处的第一EAS称为是第五EAS，将多个第一EAS中除第五EAS以外的其他EAS称为是第六EAS。可以理解，第六EAS是多个第一EAS中、基于第五EAS的触发进行应用上下文迁移的EAS。其中，第六EAS可以是一个或多个。
在另外的一个具体实现中，第一实体不仅可根据第五EAS的能力信息，确定第五EAS是否具备上述能力1、能力2和能力4中一项或多项，还可根据第六EAS的能力信息，确定第六EAS是否具备上述能力3。示例性的，第一实体若确定第五EAS具备上述能力1、能力2和能力4中一项或多项，且第六EAS具备上述能力3，则确定目标应用上下文迁移场景中包括由第一EAS决策的应用上下文迁移场景(或者说，由第五EAS决策的应用上下文迁移场景)，也即确定第五EAS能够指示该第六EAS一起进行应用上下文迁移。
还需要补充的是，第一实体根据多个第一EAS的能力信息，确定目标应用上下文迁移场景时，具体可包括如下步骤a和步骤b：
步骤a，第一实体根据多个第一EAS的能力信息，确定多个(候选的)应用上下文迁移场景中是否包括第五EAS决策的应用上下文迁移场景。
示例性的，第一实体在根据多个第一EAS的能力信息，确定多个第一EAS中的一个第一EAS(即第五EAS)具备处理关联的EAS中的应用上下文一起迁移的能力时，第一实体确定多个应用上下文迁移场景中包括由第五EAS决策的应用上下文迁移场景。
再示例性的，第一实体在根据多个第一EAS的能力信息，确定多个第一EAS均不具备处理关联的EAS中的应用上下文一起迁移的能力时，第一实体确定多个应用上下文迁移场景中不包括由第一EAS决策的应用上下文迁移场景。
步骤b，第一实体从多个应用上下文迁移场景中为多个第一EAS确定对应的目标应用上下文迁移场景。步骤b的具体实现可参见步骤302中描述。
示例性的，在确定多个应用上下文迁移场景中包括由第五EAS决策的应用上下文迁移场景的情况下，第一实体从多个应用上下文迁移场景中确定目标应用上下文迁移场景，且该确定出的目标应用上下文迁移场景中可以包括由第五EAS决策的应用上下文迁移场景。
可选的，方法还包括：第一实体发送目标应用上下文迁移场景。其中，第一实体发送目标应用上下文迁移场景的具体实现，可参见上述图5相关实施例中描述。
上述技术方案中，第一实体根据多个第一EAS的能力信息，确定多个第一EAS中是否存在某个第一EAS(即第五EAS)具备处理关联的EAS中的应用上下文一起迁移的能力，进而第一实体确定目标应用上下文迁移场景是否包括由第一EAS决策的应用上下文迁移场景(即由第五EAS决策的应用上下文迁移场景)。如此，在多个第一EAS中存在第五EAS情况下，该第五EAS能够指示其他的第一EAS(即第六EAS)一起进行应用上下文迁移，相应的，第一实体可确定目标应用上下文迁移场景中包括由第五EAS决策的应用上下文迁移场景，有助于避免在应用上下文迁移过程中出现服务中断。
实现方式2，第一实体根据第二实体的能力信息，确定第二实体是否具备处理关联的EAS中的应用上下文一起迁移的能力。随后，第一实体再确定多个应用上下文迁移场景中是否包含EAS决策的应用上下文迁移场景(即第一EAS决策的应用上下文迁移场景，或由第一EAS决策的应用上下文迁移场景)，并从该多个应用上下文迁移场景中选择目标应用上下文迁移场景。
具体可参见图18示出的一种应用上下文迁移场景的确定方法的流程示意图。
步骤1801，第一实体获取第二实体的能力信息。
第二实体可以是一个或多个。示例性的，第二实体是一个，该一个第二实体是AC、EEC或EES；第二实体是两个，该两个第二实体分别是AC和EEC，或AC和EES，或EEC和EES；第二实体是三个，该三个第二实体分别是AC、EEC和EES。
可选的，第一实体和第二实体是相同实体或者不同实体。
当第一实体和第二实体是相同实体时，第一实体可获取第一实体的能力信息，比如，第一实体从第一实体的配置中获取第一实体的能力信息。
当第一实体和第二实体是不同实体时，第一实体可接收第二实体的能力信息。示例性的，当第一实体是EEC、第二实体是AC时，EEC接收来自AC的、AC的能力信息；当第一实体是EEC、第二实体是EES时，EEC接收来自EES的、该EES的能力信息；当第一实体是EES、第二实体是AC时，EES接收由EEC转发的、AC的能力信息；当第一实体是EES、第二实体是EEC时，EES接收来自EEC的、EEC的能力信息。
如下以一个第二实体为例说明第二实体的能力信息：
第二实体的能力信息可用于指示第二实体是否具备处理关联的EAS中的应用上下文一起迁移的能力。
需要注意的是，第二实体具备的处理关联的EAS中的应用上下文一起迁移的能力，与上述实现方式1中第一EAS具备的处理关联的EAS中的应用上下文一起迁移的能力不同。
一个具体实现中，第二实体的能力信息指示第二实体是否支持如下能力a至能力c中的一项或多项：
能力a，获取多个第一EAS的标识的能力。或者说，获取关联的EAS的标识的能力，或获取需要进行应用上下文一起迁移的EAS的标识的能力等。
示例性的，第二实体是AC，AC中配置有多个第一EAS的标识。示例性的，第二实体是EEC，EEC中配置有多个第一EAS的标识，或者，EEC接收来自AC的多个第一EAS的标识。示例性的，第二实体是EES，EES中配置有多个第一EAS的标识，或者，EES接收来自EEC的多个第一EAS的标识，其中，该多个第一EAS的标识，可以是EEC中配置、并发送至EES的，或者，该多个第一EAS的标识，可以是AC中配置的、由EEC转发给EES的。如此，该第二实体即具备获取多个第一EAS的标识的能力。
能力b，支持由第一EAS决策的应用上下文迁移场景。
示例性的，第二实体的配置信息中包括第二实体支持的应用上下文迁移场景，且该第二实体支持的应用上下文迁移场景中包括由第一EAS决策的应用上下文迁移场景。
能力c，接收多个第一EAS中一个第一EAS的触发迁移通知的指示，基于该一个第一EAS的触发迁移通知的指示，向多个第一EAS中其他的第一EAS发送迁移通知的能力。其中，迁移通知用于触发应用上下文迁移。
进一步的，基于第二实体是AC、EEC还是EES，如下解释说明第二实体的能力c：
当第二实体是AC时，AC具备的能力c具体是，AC能够通过应用层从多个第一EAS中的一个第一EAS处接收触发迁移通知的指示，并基于该指示向其他的第一EAS发送迁移通知的能力。其中，AC接收触发迁移通知的指示，比如是AC订阅第一EAS的触发应用上下文迁移的事件，当第一EAS触发该应用上下文迁移的事件时，AC可接收到该触发应用上下文迁移的事件，也即接收到来自第一EAS的触发迁移通知的指示。
当第二实体是EEC时，EEC具备的能力c具体是，EEC能够通过AC从多个第一EAS中的一个第一EAS处接收触发迁移通知的指示，然后通过AC向多个第一EAS中的其他的第一EAS发送迁移通知的能力。
其中，EEC与AC之间通过EDGE-5接口通信，EAS与AC之间通过应用层通信。即，AC通过应用层从多个第一EAS中的一个第一EAS处接收触发迁移通知的指示，然后通过EDGE-5接口向EEC发送该触发迁移通知的指示；EEC在接收触发迁移通知的指示之后，通过EDGE-5接口向AC发送迁移通知，然后该AC通过应用层向多个第一EAS中的其他的第一EAS发送迁移通知。
又或者，EEC具备的能力c具体是，EEC能够通过EES从多个第一EAS中的一个第一EAS处接收触发迁移通知的指示，并通过EES向其他的第一EAS发送迁移通知的能力。
其中，EEC与EES之间通过EDGE-1接口通信，EAS与EES之间通过EDGE-3接口通信。即，EES通过EDGE-3接口从多个第一EAS中的一个第一EAS处接收触发迁移通知的指示，然后通过EDGE-1接口向EEC发送该触发迁移通知的指示；EEC在接收触发迁移通知的指示之后，通过EDGE-1接口向EES发送迁移通知，然后该EES通过EDGE-3接口向多个第一EAS中的其他的第一EAS发送迁移通知。
当第二实体是EES时，EES具备的能力c具体是，EES能够分别通过AC和EEC从多个第一EAS中的一个第一EAS处接收触发迁移通知的指示，以及通过AC和EEC向其他的第一EAS发送迁移通知的能力。
其中，EES与EEC之间通过EDGE-1接口通信，EEC与AC之间通过EDGE-5接口通信，EAS与AC之间通过应用层通信。即，AC通过应用层从多个第一EAS中的一个第一EAS处接收触发迁移通知的指示，然后通过EDGE-5接口向EEC发送该触发迁移通知的指示；EEC再通过EDGE-1接口向EES发送该触发迁移通知的指示。相应的，EES在接收触发迁移通知的指示之后，通过EDGE-1接口向EEC发送迁移通知，EEC通过EDGE-5接口向AC发送迁移通知，AC通过应用层向多个第一EAS中的其他的第一EAS发送迁移通知。
又或者，EES具备的能力c具体是，EES能够从多个第一EAS中的一个第一EAS处接收触发迁移通知的指示，并向其他的第一EAS发送迁移通知的能力。具体的，EES通过EDGE-3接口从多个第一EAS中的一个第一EAS处接收触发迁移通知的指示，并通过EDGE-3接口向其他的第一EAS发送迁移通知的能力。
步骤1802，第一实体根据第二实体的能力信息，为多个第一EAS中的至少一个第一EAS确定对应的目标应用上下文迁移场景。
一个具体实现中，第一实体根据一个或多个第二实体的能力信息，为多个第一EAS中的全部第一EAS(即该多个第一EAS)确定对应的目标应用上下文迁移场景。
示例性的，当第二实体是多个时，第一实体根据该多个第二实体的能力信息，确定多个第二实体中的一个第二实体(记为第三实体)具备上述能力a至能力c中一项或多项时，即确定第三实体具备处理关联的EAS中的应用上下文一起迁移的能力。第一实体为多个第一EAS确定对应的目标应用上下文迁移场景中包括由第一EAS决策的应用上下文迁移场景。
再示例性的，当第二实体是一个时，第一实体根据该一个第二实体的能力信息，确定该一个第二实体具备上述能力a至能力c中一项或多项，即确定该一个第二实体具备处理关联的EAS中的应用上下文一起迁移的能力，进而第一实体为多个第一EAS确定对应的目标应用上下文迁移场景中包括由第一EAS决策的应用上下文迁移场景。此处的第二实体，也可称为是第三实体。
一个具体实现中，第一实体在确定第二实体具备第二能力时，即确定第二实体具备处理关联的EAS中的应用上下文一起迁移的能力。第一实体在确定第二实体不具备该第二能力时，即确定第二实体不具备处理关联的EAS中的应用上下文一起迁移的能力。其中，第二能力是能力a、能力b和能力c中的某一项。比如，第二能力是能力a，当第一实体确定第二实体具备能力a时，即确定第二实体具备处理关联的EAS中的应用上下文一起迁移的能力；当第一实体确定第一EAS不具备能力a时，即确定第二实体不具备处理关联的EAS中的应用上下文一起迁移的能力。能力b和能力c与上述能力a类似，可将上述“能力a”替换为“能力b”理解，或者将上述“能力a”替换为“能力c”理解。
再一个具体实现中，第一实体在确定第二实体具备第二能力组时，即确定第二实体具备处理关联的EAS中的应用上下文一起迁移的能力。第一实体在确定第二实体不具备该第二能力组中的任一个能力时，即确定第二实体不具备处理关联的EAS中的应用上下文一起迁移的能力。其中，第二能力组是能力a、能力b和能力c中的某多项的组合。比如，第二能力组由能力a和能力b组成，当第一实体确定第二实体具备能力a和能力b时，即确定第二实体具备处理关联的EAS中的应用上下文一起迁移的能力；当第一实体确定第二实体不具备能力a或能力b时，即确定第一EAS不具备处理关联的EAS中的应用上下文一起迁移的能力。能力a至能力c的其他组合的实现方式与上述类似，比如对于能力a和能力c组成的第二能力组，可将上述“能力a和能力b”替换为“能力a和能力c”，以及将上述“能力a或能力b”替换为“能力a或能力c”来理解。
在一种可能的具体方式中，第一实体根据一个或多个第二实体的能力信息，以及该多个第一EAS分别支持的应用上下文迁移场景，为该多个第一EAS确定对应的目标应用上下文迁移场景。具体的，当多个第一EAS中的一个第一EAS(记为第五EAS)支持的应用上下文迁移场景中包括：该第一EAS决策的应用上下文迁移场景(即第五EAS决策的应用上下文迁移场景)；且多个第一EAS中的除该一个第一EAS以外的其他EAS(记为第六EAS)支持的应用上下文迁移场景包括：由第三实体检测触发(也可称为是决策)的应用上下文迁移场景；且第三实体满足上述能力a至能力c中一项或多项的情况下，第一实体为多个第一EAS确定对应的目标应用上下文迁移场景中包括由第一EAS决策的目标应用上下文迁移场景(即第五EAS决策的应用上下文迁移场景)。此处，第三实体具备的能力b具体是第三实体支持由第五EAS决策的应用上下文迁移场景。
其中，第五EAS支持由第五EAS决策的应用上下文迁移场景，可以理解为，第五EAS能够检测触发并决策应用上下文迁移，第五EAS在确定需要进行应用上下文迁移时，能够向第三实体发送触发迁移通知的指示，以指示第三实体向第六EAS发送迁移通知。第六EAS支持由第三实体检测触发的应用上下文迁移场景，可以理解为，第六EAS能够接收来自第三实体的迁移通知，响应于该迁移通知，进行应用上下文迁移。
可选的，第一实体还可接收多个第一EAS支持的应用上下文迁移场景。具体的，当第一实体是EEC时，EEC接收由EES转发的、多个第一EAS支持的应用上下文迁移场景；当第一实体是EES时，EES接收来自每个第一EAS的、该第一EAS支持的应用上下文迁移场景，从而获取到多个第一EAS支持的应用上下文迁移场景。
可选的，第一实体不仅将第五EAS决策的应用上下文迁移场景，作为目标应用上下文迁移场景，还将第三实体检测触发的应用上下文迁移场景，作为目标应用上下文迁移场景。如此，对于第五EAS和第三实体来说，在第五EAS决策的应用上下文迁移场景下，第五EAS向第三实体发送触发迁移通知的指示。而对于第六EAS和第三实体来说，第三实体基于触发迁移通知的指示，向第六EAS发送迁移通知，从而第六EAS可根据迁移通知进行应用上下文迁移。
比如，三个第二实体分别是AC、EEC和EES，当第五EAS支持第五EAS决策的应用上下文迁移场景，第六EAS支持AC检测触发的应用上下文迁移场景，且AC具备处理关联的EAS中的应用上下文一起迁移的能力、EEC不具备处理关联的EAS中的应用上下文一起迁移的能力、EES不具备处理关联的EAS中的应用上下文一起迁移的能力时，第一实体可确定第五EAS能够通过AC指示第六EAS一起进行应用上下文迁移，即为多个第一EAS确定对应的目标应用上下文迁移场景中包括由第五EAS决策的应用上下文迁移场景和由AC检测触发的应用上下文迁移场景。
再比如，三个第二实体分别是AC、EEC和EES，当第五EAS支持第五EAS决策的应用上下文迁移场景，第六EAS支持AC检测触发的应用上下文迁移场景和EEC检测触发的应用上下文迁移场景，且AC具备处理关联的EAS中的应用上下文一起迁移的能力、EEC不具备处理关联的EAS中的应用上下文一起迁移的能力、EES不具备处理关联的EAS中的应用上下文一起迁移的能力时，第一实体可确定第五EAS能够通过AC指示第六EAS一起进行应用上下文迁移，即为多个第一EAS确定对应的目标应用上下文迁移场景中包括由第五EAS决策的应用上下文迁移场景和由AC检测触发的应用上下文迁移场景。
还需要补充的是，第一实体根据多个第一EAS的能力信息，确定目标应用上下文迁移场景时，具体可包括如下步骤A和步骤B：
步骤A，第一实体根据第二实体的能力信息，确定多个应用上下文迁移场景中是否包括第五EAS决策的应用上下文迁移场景。
示例性的，第一实体在根据第二实体的能力信息，确定第三实体具备处理关联的EAS中的应用上下文一起迁移的能力时，第一实体确定多个应用上下文迁移场景中包括第五EAS决策的应用上下文迁移场景。
再示例性的，第一实体在根据第二实体的能力信息，确定第二实体不具备处理关联的EAS中的应用上下文一起迁移的能力时，第一实体确定多个应用上下文迁移场景中不包括第五EAS决策的应用上下文迁移场景。
步骤B，第一实体从多个应用上下文迁移场景中确定出的目标应用上下文迁移场景。步骤B的具体实现可参见步骤302中描述。
示例性的，在多个应用上下文迁移场景中包括由第五EAS决策的应用上下文迁移场景的情况下，第一实体从多个应用上下文迁移场景中确定目标应用上下文迁移场景，且该目标应用上下文迁移场景中可以包括由第五EAS决策的应用上下文迁移场景。
可选的，方法还包括：第一实体发送目标应用上下文迁移场景。其中，第一实体发送目标应用上下文迁移场景的具体实现，可参见上述图5相关实施例中描述。在另外的实现中，第一实体可向第三实体和第五EAS分别发送由第五EAS决策的应用上下文迁移场景，以及向第六EAS发送由第三实体检测触发的应用上下文迁移场景。
上述技术方案中，第一实体根据一个或多个第二实体的能力信息，确定是否存在某个第二实体(即第三实体)具备处理关联的EAS中的应用上下文一起迁移的能力。其中第三实体具体能够接收来自多个第一EAS中某个第一EAS(即第五EAS)的触发迁移通知的指示，向多个第一EAS中其他的第一EAS(即第六EAS)发送迁移通知，以使得该第六EAS一起进行应用上下文迁移。如此，第一实体可确定目标应用上下文迁移场景中包括由第五EAS决策的应用上下文迁移场景，相应的，该第五EAS在确定需要进行应用上下文迁移时，第三实体可基于第五EAS的触发迁移通知的指示，触发该第六EAS与第五EAS一起进行应用上下文迁移，有助于避免在应用上下文迁移过程中出现服务中断。
可以理解，在上述步骤1801和步骤1802中，多个第一EAS注册于同一个EES中，从而第一实体获取到该一个EES的能力信息，或者获取到该一个EES的能力信息和其他的第二实体的能力信息，以作为该第二实体的能力信息。然后第一实体根据第二实体的能力信息，为多个第一EAS中的全部第一EAS确定对应的目标应用上下文迁移场景。
此外，本申请不排除多个第一EAS注册于多个不同的EES中的情况，即每个EES中注册有一个或多个第一EAS。举例来说，多个第一EAS分别是EAS1至EAS3，其中，EAS1和EAS2注册于EES1中，EAS3注册于EES2中。
也即，多个第二实体中包括的EES可以是多个。比如第二实体是五个，该五个第二实体分别是AC、EEC和三个EES，或者该五个第二实体分别是AC和四个EES，或者该五个第二实体是五个EES。当然，多个第二实体还可以是其他的实现方式，不再一一举例。
在该情况中，第一实体可获取该多个不同EES的能力信息，或者获取到该多个EES的能力信息和其他的第二实体的能力信息，以作为该多个第二实体的能力信息。然后第一实体根据多个第二实体的能力信息，为多个第一EAS中的至少一个第一EAS确定对应的目标应用上下文迁移场景。应理解，该多个EES为该多个第一EAS所注册的EES。
具体的，当第一实体是EEC时，该EEC可以根据多个第二实体的能力信息，为多个第一EAS中的全部第一EAS确定对应的目标应用上下文迁移场景。比如，多个第一EAS是EAS1至EAS3，该EEC为EAS1至EAS3确定对应的目标应用上下文迁移场景。
当第一实体是多个EES中的一个EES(记为第一EES)时，该第一EES可以根据多个第二实体的能力信息，为多个第一EAS中的全部第一EAS确定对应的目标应用上下文迁移场景。比如，多个第一EAS是EAS1至EAS3，第一实体是EES1(即第一EES)，该EES1可以为EAS1至EAS3确定对应的目标应用上下文迁移场景。
或者，该第一EES可根据多个第二实体的能力信息，为多个第一EAS中的部分第一EAS确定对应的目标应用上下文迁移场景。比如，多个第一EAS是EAS1至EAS3，第一实体是EES1(即第一EES)，EAS1可以为注册于EAS1中的至少一个第一EAS(比如EAS1和EAS2)确定对应的目标应用上下文迁移场景。
如下基于第一实体是EEC还是EES，分情况a和情况b说明。
情况a，第一实体是EEC。
可以理解，下述步骤1801-a和步骤1802-a是步骤1801和步骤1802在第一实体是EEC，多个第二实体中包括多个EES的情况下的一种具体实现方式。在步骤1801-a和步骤1802-a中未详尽描述的部分，可参见上述步骤1801和步骤1802中描述。
步骤1801-a，EEC获取多个第二实体的能力信息。
其中，多个第二实体包括多个EES，相应的，EEC获取多个EES的能力信息。
示例性的，EEC接收来自多个EES中每个EES的、该EES的能力信息，从而获取到该多个EES的能力信息。
对于多个EES中一个EES，该EES的能力信息可用于指示该EES是否具备处理关联的EAS中的应用上下文一起迁移的能力。以多个EES中第一EES为例，第一EES的能力信息即用于指示第一EES是否具备处理关联的EAS中的应用上下文一起迁移的能力。
本申请中，该多个EES中每个EES均注册有一个或多个第一EAS，该多个EES分别注册的一个或多个第一EAS即组成了上述多个第一EAS，该多个第一EAS为关联EAS，可将该多个EES称为是关联EES。
一个具体实现中，第一EES的能力信息指示该第一EES是否具备如下能力A-能力D中的一项或多项：
能力A，获取多个第一EAS的标识的能力。
可选的，第一EES不仅能够获取第一EES中注册的至少一个第一EAS的标识，还能够从多个EES的其他EES中获取该其他EES中注册的至少一个第一EAS的标识。
比如，多个EES分别是EES1和EES2，多个EAS分别是EAS1至EAS3，其中，第一EES是EES1，EES1不仅能获取注册于EES1中的第一EAS(比如EAS1和EAS2)，EES1还能从EES2处可获取注册于EES2中的第一EAS(比如EAS3)，如此，EES1即可获取到多个EAS(即EAS1至EAS3)的标识。
能力B，获取第一EES中注册的至少一个第一EAS的标识的能力。
可选的，第一EES能够获取第一EES中注册的至少一个第一EAS的标识。比如，第一EES是EES1，EES1能够获取注册于EES1中的第一EAS(比如EAS1和EAS2)的标识。
可以理解，第一EES中注册的至少一个第一EAS，是上述多个第一EAS(关联的EAS)中的至少一个。也即，第一EES中注册的至少一个第一EAS包含于上述多个第一EAS中。
能力C，获取多个EES的标识的能力。示例性的，第一EES可以接收来自多个EES中除该第一EES以外的其他EES发送的EES的标识。
能力D，接收来自所述多个第一EAS中的一个第一EAS的触发迁移通知的指示，向所述多个第一EAS中的其他EAS发送迁移通知的能力；
示例性的，能力D可进一步包括如下能力D1至D3中一项或多项：
能力D1，接收第一EES中注册的一个第一EAS的触发迁移通知的指示，向第一EES中注册的其他EAS(即其他的第一EAS)发送迁移通知的能力；比如，第一EES是EES1，EES1中注册有EAS1和EAS2，能力D1即第一EES能够从EAS1处接收触发迁移通知的指示，然后根据触发迁移通知的指示，向EAS2发送迁移通知的能力。
能力D2，接收多个EES中除第一EES以外的其他EES发送的触发迁移通知的指示，根据该触发迁移通知的指示，向第一EES中注册的至少一个第一EAS发送迁移通知的能力。比如，多个EES中包括EES1和EES2，其中，第一EES是EES1，EES1中注册有EAS1和EAS2，EES1能够接收来自EES2的触发迁移通知的指示，根据触发迁移通知的指示分别向EES1中注册的EAS1和EAS2发送迁移通知。
能力D3，接收第一EES中注册的一个第一EAS的触发迁移通知的指示，向多个EES中除第一EES以外的其他EES发送触发迁移通知的指示的能力，以使得该其他的EES向该其他的EES中注册的至少一个第一EAS发送迁移通知。比如，多个EES中包括EES1和EES2，其中，第一EES是EES1，能力D3为EES1向EES2发送触发迁移通知的指示，以指示EES2向EES2中注册的至少一个第一EAS发送迁移通知。
此外，在EEC获取多个第二实体的能力信息的过程中，EEC还可获取除该多个EES以外的其他第二实体的能力信息，即EEC还可获取AC的能力信息和/或EEC的能力信息。其中，其他第二实体的能力信息，可参见上述步骤1801中的描述。
步骤1802-a，EEC根据多个第二实体的能力信息，为多个第一EAS确定对应的目标应用上下文迁移场景。
第一个具体示例中，多个第二实体是多个EES，即多个第二实体的能力信息是多个EES的能力信息。EEC根据多个EES的能力信息，为多个第一EAS确定该多个第一EAS对应的目标应用上下文迁移场景。
在第一个具体示例中，第一实体根据多个EES的能力信息，确定多个EES中的某个EES(记为第二EES)具备处理关联的EAS中的应用上下文一起迁移的能力时，确定多个第一EAS对应的目标应用上下文迁移场景中，包括由第一EAS决策的应用上下文迁移场景。
或者，第一实体根据多个EES的能力信息，确定多个EES均不具备处理关联的EAS中的应用上下文一起迁移的能力时，确定多个第一EAS对应的目标应用上下文迁移场景中，不包括由第一EAS决策的应用上下文迁移场景。
其中，第一实体确定EES是否具备处理关联的EAS中的应用上下文一起迁移的能力，具体可以是，第一实体确定第二EES是否具备上述能力A、能力B、能力C、能力D中一项或多项。
一个具体实现中，第一实体在确定第一EES具备第三能力时，即确定第一EES具备处理关联的EAS中的应用上下文一起迁移的能力。第一实体在确定第一EES不具备该第三能力时，即确定第一EES不具备处理关联的EAS中的应用上下文一起迁移的能力。其中，第三能力是能力A、能力B、能力C、能力D中的某一项。比如，第三能力是能力A，当第一实体确定EES具备能力A时，即确定EES具备处理关联的EAS中的应用上下文一起迁移的能力；当第一实体确定EES不具备能力A时，即确定EES不具备处理关联的EAS中的应用上下文一起迁移的能力。当第三能力是能力B、能力C、能力D时，实现方式与上述能力A类似，可将上述“能力A”分别替换为“能力B”、“能力C”或“能力D”理解。
再一个具体实现中，第一实体在确定第一EES具备第三能力组时，即确定第一EES具备处理关联的EAS中的应用上下文一起迁移的能力。第一实体在确定第一EES不具备该第三能力组中的任一个能力时，即确定第一EES不具备处理关联的EAS中的应用上下文一起迁移的能力。其中，第三能力组是能力A、能力B、能力C、能力D(比如能力D1或能力D3)中的某多项的组合。比如，第三能力组由能力A和能力C组成，当第一实体确定EES具备能力A和能力C时，即确定EES具备处理关联的EAS中的应用上下文一起迁移的能力；当第一实体确定EES不具备能力A或能力C时，即确定EES不具备处理关联的EAS中的应用上下文一起迁移的能力。在第三能力组由能力A、能力B、能力C、能力D中的其他组合方式得到时，具体实现方式与上述类似，比如，对于由能力A和能力D组成的第三能力组，可将上述“能力A和能力C”替换为“能力A和能力D”，以及将上述“能力A或能力C”替换为“能力A或能力D”理解。
此外，EEC还可进一步确定多个EES中除第二EES以外的其他EES是否具备上述能力A、能力B、能力D(比如能力D2)中一项或多项，并在确定其他EES具备上述能力A、能力B、能力D中一项或多项之后，确定多个第一EAS对应的目标应用上下文迁移场景中，包括由第一EAS决策的应用上下文迁移场景。
可以理解的是，由第一EAS决策的应用上下文迁移场景，具体是由第五EAS决策的应用上下文迁移场景，其中，第二EES中注册有一个或多个第一EAS，该第五EAS是该一个或多个第一EAS中的某个第一EAS，且该第五EAS支持由第五EAS决策的应用上下文迁移场景。此外，在第二EES中注册有多个第一EAS的情况下，可将该多个第一EAS中除第五EAS以外的第一EAS记为第六EAS，该第六EAS可支持由第二EES检测触发的应用上下文迁移场景。
其中，第五EAS支持由第五EAS决策的应用上下文迁移场景，以及第六EAS支持由第二EES检测触发的应用上下文迁移场景的具体说明，可参见步骤1802中说明。
可以理解，此处的第二EES是上述步骤1802中第三实体的一个具体实现，即对于第五EAS和第二EES，第五EAS可在确定需要进行应用上下文的迁移时，向第二EES发送触发迁移通知的指示；对于第六EAS和第二EES，第二EES可基于触发迁移通知的指示，向第六EAS发送迁移通知，该迁移通知即用于触发第六EAS进行应用上下文的迁移。
此外，第二EES还可基于触发迁移通知的指示，向多个EES中除第二EES以外的其他EES发送触发迁移通知的指示，从而该其他EES可基于触发迁移通知的指示，向该其他EES中注册的至少一个第一EAS发送迁移通知，该迁移通知即用于触发该其他EES中注册的至少一个第一EAS进行应用上下文的迁移。
第二个具体示例中，多个第二实体包括多个EES，以及AC和/或EEC，也即，多个第二实体的能力信息包括多个EES的能力信息，以及AC的能力信息和/或EEC的能力信息。EEC根据该多个EES的能力信息，以及AC的能力信息和/或EEC的能力信息，为多个第一EAS确定该多个第一EAS对应的目标应用上下文迁移场景。
在该场景中，在多个第二实体(包括多个EES，以及AC和/或EEC)中的某个第二实体(即第三实体)具备处理关联的EAS中的应用上下文一起迁移的能力时，EEC为多个第一EAS确定对应的目标应用上下文迁移场景中包括由第一EAS决策的应用上下文迁移场景。
进一步的，在第三实体是AC或者EEC时，该AC或者EEC具备处理关联的EAS中的应用上下文一起迁移的能力，即具备上述能力a至能力c中一项或多项。
在第三实体是多个EES中的某个EES(即第二EES)时，该第二EES具备处理关联的EAS中的应用上下文一起迁移的能力，即具备上述能力a至能力c中一项或多项；或者，具体是，具备上述能力A、能力B、能力C、能力D(比如能力D1或能力D3)中一项或多项。进一步的，多个EES中除第二EES以外的其他EES，还可具备上述能力A、能力B、能力D(比如能力D2)中一项或多项。
情况b，第一实体是EES，即，第一实体是多个EES中的一个EES。
此处，可将多个EES中的任一个EES作为第一实体。
或者，将多个EES中的某个指定的EES作为第一实体。本申请中，可将该作为第一实体的EES称为是主EES。
示例a，AC或EEC指定多个EES中的某一个EES作为该第一实体。比如，AC向多个EES分别发送第一指定消息，该第一指定消息中包括多个EES中某一个EES的标识，相应的，该多个EES在接收到该第一指定消息之后，确定该第一指定消息中EES的标识对应的EES，作为主EES，也即第一实体。
示例b，该多个EES中的某一个EES预配置有第三指示，其中，该第三指示用于指示该EES是多个EES中、用于为多个第一EAS确定对应的目标应用上下文迁移场景的EES。将预配置有第三指示的EES，作为主EES，也即第一实体。
示例c，该多个EES中的某一个EES中注册有某个指定的EAS，将注册有该指定的EAS的EES，作为第一实体。其中，指定的EAS也可称为是主EAS，该主EAS具体可以是多个第一EAS中用于为应用提供主要服务的EAS，或者是多个第一EAS中用于运行应用的主要程序的EAS。以游戏AC为例，为游戏AC提供服务的三个第一EAS分别是图形渲染EAS、聊天功能EAS和游戏加速EAS提供服务，其中，游戏加速EAS可作为游戏AC的主EAS。
该指定的EAS具体可以是由AC或EEC指定的、多个第一EAS中的一个EAS。比如，AC向多个第一EAS分别发送第二指定消息，该第二指定消息中包括多个第一EAS中某一个第一EAS的标识，相应的，该多个第一EAS在接收到该第二指定消息之后，确定该第二指定消息中第一EAS的标识对应的第一EAS作为主EAS。或者，该指定EAS中预配置有第四指示，第四指示即用于指示该EAS是主EAS。
本申请中，“指定的”又可称为是“确定的”、“选择的”、“特定的”等。
可以理解，下述步骤1801-b和步骤1802-b是步骤1801和步骤1802在第一实体是多个EES中的主EES，多个第二实体中包括多个EES的情况下的一种具体实现方式。在步骤1801-b和步骤1802-b中未详尽描述的部分，可参见上述步骤1801和步骤1802，或者参见步骤1801-a和步骤1802-a中描述。如下，以主EES是第一EES为例说明。
步骤1801-b，第一EES获取多个第二实体的能力信息。
其中，多个第二实体包括多个EES，相应的，第一EES获取多个EES的能力信息。
示例性的，第一EES不仅能获取第一EES的能力信息，还能获取多个EES中除第一EES以外的其他EES的能力信息，比如第一EES接收来自多个EES中其他EES的、该其他EES的能力信息，从而获取到该多个EES的能力信息。
在一个具体实现中，第一EES可以向该其他EES发送第一能力请求，该第一能力请求用于第一EES向该其他EES请求该其他EES的能力信息，相应的，该其他EES在接收到第一能力请求之后，向第一EES发送该其他EES的能力信息。
其中，EES的能力信息可用于指示EES是否具备处理关联的EAS中的应用上下文一起迁移的能力。具体说明可参见上述步骤1801-a中关于EES的能力信息的描述。
此外，在第一EES获取多个第二实体的能力信息的过程中，第一EES还可获取除该多个EES以外的其他第二实体的能力信息，即第一EES还可获取AC的能力信息和/或EEC的能力信息。其中，其他第二实体的能力信息，可参见上述步骤1801中的描述。
步骤1802-b，第一EES根据多个第二实体的能力信息，为多个第一EAS中的至少一个第一EAS确定对应的目标应用上下文迁移场景。
基于第一EES为多个第一EAS中全部第一EAS，还是部分第一EAS确定对应的目标应用上下文迁移场景，如下分示例(1)和示例(2)解释说明。
示例(1)，第一EES根据多个第二实体的能力信息，为多个第一EAS中全部第一EAS确定对应的目标应用上下文迁移场景。具体实现可参见上述情况a中步骤1802-a的描述，可将EEC替换为第一EES。
例子1，多个EES中包括EES1和EES2，其中EES1中注册有EAS1和EAS2，EES2中注册有EAS3。第一EES是EES1，EES1根据EES1的能力信息、EES2的能力信息、EAS1至EAS3支持的应用上下文迁移场景，为EAS1、EAS2和EAS3确定目标应用上下文迁移场景中包括由EAS1决策的应用上下文迁移场景。
其中，EAS1支持由EAS1决策的应用上下文迁移场景，EAS2支持由EES1检测触发的应用上下文迁移场景，EAS3支持由EES2检测触发的应用上下文迁移场景，且EES1具备能力A、能力B、能力C、能力D(比如能力D1或能力D3)中一项或多项，EES2具备能力A、能力B、能力D(比如能力D2)中一项或多项。
进一步的，在触发应用上下文的迁移场景中，EES1接收来自EAS1的触发迁移通知的指示，向EAS2发送迁移通知，以及向EES2发送触发迁移通知的指示；相应的，EES2接收到该来自EES1的触发迁移通知的指示，向EAS3发送迁移通知。如此，EAS1至EAS3可一起执行应用上下文的迁移。
在该示例(1)中，第一EES获取到的其他EES的能力信息不仅可以用于指示该其他EES是否具备上述能力A至能力D中一项或多项，还可以是直接用于指示该其他EES是否具备处理关联的EAS中的应用上下文一起迁移的能力。
在后一个可能方式的一个具体实现中，该第一EES获取多个EES中除第一EES以外的其他EES的能力信息，该能力信息具体是该其他EES的处理结果。具体的，该其他EES根据自己的能力信息以及注册于该其他EES中的至少一个第一EAS支持的应用上下文迁移场景，确定该其他EES是否具备处理关联的EAS中的应用上下文一起迁移的能力。示例性的，该处理结果是“具备”或者“不具备”，比如该处理结果用1比特表示，其中该1比特取值为1时，表示“具备”，该1比特取值为0时，表示“不具备”。
此处，由于该其他EES根据自己的能力信息和其中注册的至少一个第一EAS支持的应用上下文迁移场景，判断自己是否具备处理关联的EAS中的应用上下文一起迁移的能力，所以，该其他EES无需再向该第一EES发送该其他EES中注册的至少一个第一EAS所支持的应用上下文迁移场景。也即，在该具体实现中，第一EES获取多个EES中除第一EES以外的其他EES的处理结果，根据该其他EES的处理结果、第一EES的能力信息，以及第一EES中注册的至少一个第一EAS所支持的应用上下文迁移场景，为多个第一EAS中全部第一EAS确定对应的目标应用上下文迁移场景。
例子2，多个EES中包括EES1和EES2，其中EES1中注册有EAS1和EAS2，EES2中注册有EAS3。第一EES是EES1，其中，EES2先根据EES2的能力信息和EAS3支持的应用上下文迁移场景，确定EES2具备处理关联的EAS中的应用上下文一起迁移的能力，得到的处理结果即为“具备”。EES1获取EES1的能力信息、EES2的处理结果、EAS1和EAS2支持的应用上下文迁移场景，为EAS1、EAS2和EAS3确定目标应用上下文迁移场景中包括由EAS1决策的应用上下文迁移场景。其中，EAS1至EAS3各自支持的应用上下文迁移场景，EES1和EES2各自具备的能力，以及如何实现EAS1至EAS3一起执行应用上下文的迁移，均可参见上述例子1中说明。
示例(2)，第一EES根据多个第二实体的能力信息，为多个第一EAS中部分第一EAS确定对应的目标应用上下文迁移场景。
可选的，该部分第一EAS是注册于该第一EES中的至少一个第一EAS。
可以理解的是，多个EES各自注册有至少一个第一EAS，对于该多个EES中的每个EES来说，该EES根据多个第二实体的能力信息，为本EES中注册的至少一个第一EAS，确定对应的目标应用上下文迁移场景。也即，本申请中，不仅包括第一EES根据多个第二实体的能力信息，为第一EES中注册的至少一个第一EAS确定对应的目标应用上下文迁移场景；还包括多个EES中除第一EES以外的其他EES，根据多个第二实体的能力信息，为该其他EES中注册的至少一个第一EAS确定对应的目标应用上下文迁移场景。
第一EES，或者多个EES中除第一EES以外的其他EES，根据多个第二实体的能力信息，为各自EES中注册的一个或多个第一EAS确定对应的目标应用上下文迁移场景的实现方式，可参见上述示例(1)的说明。
例子3，多个EES中包括EES1和EES2，其中EES1中注册有EAS1和EAS2，EES2中注册有EAS3。第一EES是EES1，EES1根据多个第二实体的能力信息、EAS1和EAS2各自支持的应用上下文迁移场景，为EAS1和EAS2确定目标应用上下文迁移场景，其中，确定的目标应用上下文迁移场景比如包括由EAS1决策的应用上下文迁移场景。同理的，多个EES中的其他EES(即EES2)根据多个第二实体的能力信息、EAS3支持的应用上下文迁移场景，为EAS3确定目标应用上下文迁移场景，其中，确定的目标应用上下文迁移场景比如包括由EAS3决策的应用上下文迁移场景。本例子中，EAS1至EAS3各自支持的应用上下文迁移场景，EES1和EES2各自的能力信息，以及如何实现EAS1至EAS3一起执行应用上下文的迁移，均可参见上述例子1和例子2中说明。
上述技术方案中，第一实体根据多个EES的能力信息，确定是否存在某个EES(即第三实体，或者第二EES)具备处理关联的EAS中的应用上下文一起迁移的能力。其中该作为第三实体的EES，具体能够接收来自该EES中注册的某个第一EAS(即第五EAS)的触发迁移通知的指示，向该EES中注册的其他的第一EAS发送迁移通知，以及向其他EES发送触发迁移通知的指示，以使得该其他EES向该其他EES中注册的至少一个第一EAS发送迁移通知。如此，第一实体可确定目标应用上下文迁移场景中包括由第五EAS决策的应用上下文迁移场景，相应的，该第五EAS在确定需要进行应用上下文迁移时，作为第三实体的EES可基于第五EAS的触发迁移通知的指示，分别触发该EES中注册的其他EAS与第五EAS一起进行应用上下文迁移，以及指示其他EES向注册在该其他EES中的至少一个第一EAS发送迁移通知，以指示该至少一个第一EAS与第五EAS一起进行应用上下文迁移。如此，有助于避免在应用上下文迁移过程中出现服务中断。
需要补充的是，实现方式一还包括实现方式3，第一实体根据多个第一EAS的能力信息，以及第二实体的能力信息，确定多个应用上下文迁移场景中是否包含EAS决策的应用上下文迁移场景(或称为由EAS决策的应用上下文迁移场景、由第一EAS决策的应用上下文迁移场景)，进而从该多个应用上下文迁移场景中选择目标应用上下文迁移场景。
具体的，第一实体获取多个第一EAS的能力信息，以及一个或多个第二实体的能力信息，其中，获取方式可分别参见上述实现方式1和实现方式2中的描述。
进一步的，第一实体根据多个第一EAS的能力信息和一个或多个第二实体的能力信息，确定多个应用上下文迁移场景中是否包含由EAS决策的应用上下文迁移场景，进而确定目标应用上下文迁移场景。
一个示例中，第一实体先根据多个第一EAS的能力信息，确定多个第一EAS中是否存在具备处理关联的EAS中的应用上下文一起迁移的能力的第一EAS。第一实体若确定该多个第一EAS中存在该具备处理关联的EAS中的应用上下文一起迁移的能力的第一EAS，则确定多个应用上下文迁移场景中包含由EAS决策的应用上下文迁移场景，也即第一实体不再根据第二实体的能力信息确定多个应用上下文迁移场景中是否包含由EAS决策的应用上下文迁移场景。第一实体若确定该多个第一EAS中不存在该具备处理关联的EAS中的应用上下文一起迁移的能力的第一EAS，则进一步根据第二实体的能力信息确定多个应用上下文迁移场景中是否包含由EAS决策的应用上下文迁移场景。具体的，第一实体若确定该一个或多个第二实体中存在该具备处理关联的EAS中的应用上下文一起迁移的能力的第二实体，则进一步确定多个应用上下文迁移场景中包含由EAS决策的应用上下文迁移场景。第一实体若确定该一个或多个第二实体中不存在该具备处理关联的EAS中的应用上下文一起迁移的能力的第二实体，则进一步确定多个应用上下文迁移场景中不包含由EAS决策的应用上下文迁移场景。
又一个示例中，第一实体先根据一个或多个第二实体的能力信息，确定一个或多个第二实体中是否存在具备处理关联的EAS中的应用上下文一起迁移的能力的第二实体。第一实体若确定该一个或多个第二实体中存在该具备处理关联的EAS中的应用上下文一起迁移的能力的第二实体，则确定多个应用上下文迁移场景中包含由EAS决策的应用上下文迁移场景，也即第一实体不再根据多个第一EAS的能力信息确定多个应用上下文迁移场景中是否包含由EAS决策的应用上下文迁移场景。第一实体若确定该第二实体中不存在该具备处理关联的EAS中的应用上下文一起迁移的能力的第二实体，则进一步根据多个第一EAS的能力信息确定多个应用上下文迁移场景中是否包含由EAS决策的应用上下文迁移场景。具体的，第一实体若确定该多个第一EAS中存在该具备处理关联的EAS中的应用上下文一起迁移的能力的第一EAS，则进一步确定多个应用上下文迁移场景中包含由EAS决策的应用上下文迁移场景。第一实体若确定该多个第一EAS中不存在该具备处理关联的EAS中的应用上下文一起迁移的能力的第一EAS，则进一步确定多个应用上下文迁移场景中不包含由EAS决策的应用上下文迁移场景。
此外，第一实体还可以根据一个或多个第二实体的能力信息，确定一个或多个第二实体中是否存在具备处理关联的EAS中的应用上下文一起迁移的能力的第二实体；以及根据多个第一EAS的能力信息，确定多个第一EAS中是否存在具备处理关联的EAS中的应用上下文一起迁移的能力的第一EAS。从而第一实体进一步确定多个应用上下文迁移场景。当然，本申请还可以有其他方式，不再列举。
实现方式3中，第一实体根据多个第一EAS的能力信息，确定多个应用上下文迁移场景中是否包含EAS决策的应用上下文迁移场景的实现方式，可参见实现方式1中描述。第一实体根据一个或多个第二实体的能力信息，确定多个应用上下文迁移场景中是否包含EAS决策的应用上下文迁移场景的实现方式，可参见实现方式2中描述。
下面结合具体实现场景，解释说明上述实现方式1和实现方式2。
图19示出实现方式1的一种具体实现，其中，第一实体是EES，EES根据多个第一EAS的能力信息，确定目标应用上下文迁移场景中是否包括由第一EAS决策的应用上下文迁移场景。在该具体实现中，未详尽描述的内容可参见实现方式1或图17相关实施例。
步骤1901，多个第一EAS分别向EES发送EAS注册请求，相应的，EES接收来自多个第一EAS的注册请求。
以其中一个第一EAS为例，第一EAS的注册请求中包括该第一EAS的配置信息。第一EAS的配置信息中包括第一EAS的能力信息，该第一EAS的能力信息指示第一EAS是否具备能力1至能力4中的一项或多项。
其中，能力1至能力4的说明可参见图17相关实施例中描述。
此处，第一EAS的配置信息还包括第一EAS的标识和第一EAS支持的应用上下文迁移场景。其中，第一EAS支持的应用上下文迁移场景可用于指示该第一EAS是否具备能力4，也即，第一EAS支持的应用上下文迁移场景，可认为是第一EAS的能力信息。
步骤1902，EES向多个第一EAS分别发送EAS注册响应。
步骤1903，EEC、多个第一EAS分别向EES订阅目标应用上下文迁移场景。
步骤1904，AC预配置有AC配置信息。其中，AC配置信息可以包括AC支持的应用上下文迁移场景、AC的标识和第一信息。其中第一信息比如是第一EAS列表，第一EAS列表即由多个第一EAS的标识组成的列表。
步骤1905，AC向EEC发送AC注册请求，其中，AC注册请求包括AC配置信息。
步骤1906，EEC向AC发送AC注册响应。
步骤1907，EEC向EES发送EEC注册请求，其中，EEC注册请求包括AC配置信息和EEC支持的应用上下文迁移场景。
步骤1908，EES根据第一信息，确定多个第一EAS的应用上下文需一起迁移；EES根据多个第一EAS的能力信息，确定多个第一EAS中是否存在具备处理关联的EAS中的应用上下文一起迁移的能力的第一EAS(即第五EAS)。具体的，EES若确定多个第一EAS中第五EAS具备处理关联的EAS中的应用上下文一起迁移的能力，则确定多个应用上下文迁移场景包括由第五EAS决策的应用上下文迁移场景；若确定多个第一EAS均不具备处理关联的EAS中的应用上下文一起迁移的能力，则确定多个应用上下文迁移场景不包括由第五EAS决策的应用上下文迁移场景。EES从确定出的多个应用上下文迁移场景中，选择目标应用上下文迁移场景。
步骤1909，EES分别向多个第一EAS发送应用上下文迁移场景通知，应用上下文迁移场景通知中包括目标应用上下文迁移场景。
步骤1910，EES向EEC发送EEC注册响应，该EEC注册响应中包括目标应用上下文迁移场景。
步骤1911，AC向EEC订阅目标应用上下文迁移场景。
步骤1912，EEC向AC发送应用上下文迁移场景通知，应用上下文迁移场景通知中包括目标应用上下文迁移场景。
此外，上述实施例中，第一实体也可替换为EEC，区别在于第一实体与第一EAS之间是直接通信，还是通过EES进行间接通信；以及在于第一实体与AC之间是直接通信，还是通过EEC进行间接通信。以及各实体之间的具体消息存在不同。
上述实施例中，注册请求均可替换为更新请求，注册响应均可替换为更新响应。比如EAS注册请求替换为EAS更新请求，EAS注册响应替换为EAS更新响应等。当然，上述各信息也可承载于其他类型的消息中，本申请不做限定。
图20示出实现方式2的一种具体实现，其中，第一实体是EES，多个第二实体包括AC、EEC和EES，其中EES为一个，即需要一起进行应用上下文迁移的多个第一EAS是注册于该一个EES中的。EES根据该多个第二实体的能力信息，确定目标应用上下文迁移场景中是否包括由第一EAS决策的应用上下文迁移场景。在该具体实现中，未详尽描述的内容可参见实现方式2或图18相关实施例。
步骤2001，多个第一EAS分别向EES发送EAS注册请求，相应的，EES接收来自多个第一EAS的注册请求。
以其中一个第一EAS为例，第一EAS的注册请求中包括该第一EAS的配置信息。第一EAS的配置信息中包括第一EAS支持的应用上下文迁移场景。第一EAS支持的应用上下文迁移场景的说明可参见图18相关实施例中描述。此处，第一EAS的配置信息还包括第一EAS的标识。
步骤2002，EES向多个第一EAS分别发送EAS注册响应。
步骤2003，EEC、多个第一EAS分别向EES订阅目标应用上下文迁移场景。
步骤2004，AC预配置有AC配置信息。
其中，AC配置信息中包括AC的能力信息，AC的能力信息用于指示AC是否具备处理关联的EAS中的应用上下文一起迁移的能力，或者说，是否具备上述能力a至能力c中的一项或多项。其中，能力a至能力c的说明可参见图18相关实施例中描述。
AC配置信息还可包括AC支持的应用上下文迁移场景、AC的标识和第一信息。其中第一信息比如是第一EAS列表，即由多个第一EAS的标识组成的列表。AC支持的应用上下文迁移场景可用于指示该AC是否具备能力b。AC支持的应用上下文迁移场景，也可认为是AC的能力信息。
步骤2005，AC向EEC发送AC注册请求，其中，AC注册请求中包括AC配置信息，即包括第一信息和AC的能力信息。
步骤2006，EEC向AC发送AC注册响应。
步骤2007，EEC预配置有EEC配置信息。
其中，EEC配置信息中包括EEC的能力信息，EEC的能力信息用于指示EEC是否具备处理关联的EAS中的应用上下文一起迁移的能力，或者说，是否具备上述能力a至能力c中的一项或多项。其中，能力a至能力c的说明可参见图18相关实施例中描述。
EEC配置信息还可包括EEC支持的应用上下文迁移场景和EEC的标识。EEC支持的应用上下文迁移场景可用于指示该EEC是否具备能力b。EEC支持的应用上下文迁移场景，也可认为是EEC的能力信息。
步骤2008，EEC向EES发送EEC注册请求，其中，EEC注册请求包括AC配置信息和EEC配置信息。相应的，EES接收来自EEC的EEC注册请求。
步骤2009，EES根据EEC注册请求中的AC配置信息中携带的第一信息，确定多个第一EAS的应用上下文需一起迁移；EES根据多个第一EAS支持的应用上下文迁移场景、EES的能力信息、AC的能力信息和EEC的能力信息，确定AC、EEC、EES中是否存在具备处理关联的EAS中的应用上下文一起迁移的能力的第二实体(即第三实体)。具体的，EES若确定AC、EEC、EES中存在具备处理关联的EAS中的应用上下文一起迁移的能力的第三实体，即确定多个第一EAS中第五EAS能够通过第三实体，来指示多个第一EAS中的其他EAS(即第六EAS)一起进行应用上下文迁移，则确定多个应用上下文迁移场景包括由第五EAS决策的应用上下文迁移场景；EES若确定AC、EEC、EES中不存在具备处理关联的EAS中的应用上下文一起迁移的能力的第三实体，即确定多个第一EAS中第五EAS不能够通过第三实体，来指示多个第一EAS中的其他EAS(即第六EAS)一起进行应用上下文迁移，则确定多个应用上下文迁移场景不包括由第五EAS决策的应用上下文迁移场景。
此处，第五EAS能够通过第三实体，来指示多个第一EAS中的第六EAS一起进行应用上下文迁移，可以理解为，第三实体可接收来自第五EAS的触发迁移通知的指示，然后向第六EAS发送迁移通知。该说明还可适用于本申请的其他示例中。
此处，还可以理解的是，EES预配置有EES配置信息。其中，EES配置信息中包括EES的能力信息，EES的能力信息用于指示EES是否具备处理关联的EAS中的应用上下文一起迁移的能力，或者说，是否具备上述能力a至能力c中的一项或多项。其中，能力a至能力c的说明可参见图18相关实施例中描述。
EES配置信息还可包括EES支持的应用上下文迁移场景和EES的标识。EES支持的应用上下文迁移场景可用于指示该EES是否具备能力b。EES支持的应用上下文迁移场景，也可认为是EES的能力信息。
步骤2010，EES从多个应用上下文迁移场景中，选择目标应用上下文迁移场景。
在EES确定多个应用上下文迁移场景中包括由第五EAS决策的应用上下文迁移场景的情况下，EES可确定由第五EAS决策的应用上下文迁移场景，以及由第三实体决策的应用上下文迁移场景，共同作为目标应用上下文迁移场景。
以第三实体是AC为例，在AC具备能力a至能力c，第六EAS支持AC决策的应用上下文迁移场景时，EES可确定多个第一EAS中的第五EAS能够通过AC来指示多个第一EAS中的第六EAS一起进行应用上下文迁移，即，EES确定由第五EAS决策的应用上下文迁移场景，以及由AC决策的应用上下文迁移场景，共同作为目标应用上下文迁移场景。
步骤2011，EES分别向多个第一EAS发送应用上下文迁移场景通知，应用上下文迁移场景通知中包括目标应用上下文迁移场景。
结合上述例子，EES分别向多个第一EAS发送的应用上下文迁移场景通知中包括的目标应用上下文迁移场景中携带有：由第五EAS决策的应用上下文迁移场景，以及由AC决策的应用上下文迁移场景。
步骤2012，EES向EEC发送EEC注册响应，该EEC注册响应包括目标应用上下文迁移场景。
步骤2013，AC向EEC订阅目标应用上下文迁移场景。
步骤2014，EEC向AC发送应用上下文迁移场景通知，应用上下文迁移场景通知中包括目标应用上下文迁移场景。
此外，上述实施例中，第一实体也可替换为EEC，区别在于第一实体与第一EAS之间是直接通信，还是通过EES进行间接通信；以及在于第一实体与第二实体之间的通信方式；以及各实体之间的具体消息存在不同。
上述实施例中，注册请求均可替换为更新请求，注册响应均可替换为更新响应。比如EAS注册请求替换为EAS更新请求，EAS注册响应替换为EAS更新响应等。当然，上述各信息也可承载于其他类型的消息中，本申请不做限定。
图21示出实现方式2的再一种具体实现，其中，多个第二实体包括AC、EEC和EES，其中，EES为多个，即需要一起进行应用上下文迁移的多个第一EAS是注册于多个不同的EES中的。第一实体是多个EES中的一个EES(记为第一EES)，该第一EES根据该多个第二实体的能力信息，为多个第一EAS中全部的第一EAS确定目标应用上下文迁移场景。在该具体实现中，未详尽描述的内容可参见实现方式2或图18或图20相关实施例中描述。
需要说明的是，为方便描述，如图21中仅画出第一EES和第二EES，其中第二EES即多个EES中除第一EES以外的其他的一个EES。当多个第二实体还包括其他EES(比如第三EES)时，该第一EES和第三EES的交互方式，可参见第一EES和第二EES交互方式。当然本申请并不限定多个EES的个数。
进一步的，图21中包括的步骤2001至步骤2014，可参见图20所示的步骤2001至步骤2014，可将图20中的EES替换为第一EES来理解。
此外，区别还在于：
图21的步骤2001和步骤2002中，多个第一EAS中的一个或多个第一EAS可向第一EES注册，而其他的一个或多个第一EAS可向第二EES注册。
图21的步骤2009中，第一EES需要根据第一信息、多个第一EAS支持的应用上下文迁移场景、AC的能力信息、EEC的能力信息、第一EES的能力信息、第二EES的能力信息，确定多个应用上下文迁移场景中是否包括由第一EAS决策的应用上下文迁移场景，该步骤2009的实现方式可参见上述步骤1802-b的说明。此外，当第二实体还包括其他EES(比如第三EES)，第一EES还需要考虑第三EES的能力信息，不再赘述。
此外，图21中还包括如下步骤2015和步骤2016：
步骤2015，第一EES向第二EES发送第一能力请求，该第一能力请求用于第一EES向第二EES请求第二EES的能力信息。
步骤2016，第二EES在接收到第一能力请求之后，向第一EES发送第二EES的能力信息。如此，第一EES即获取到第二EES的能力信息。
当然，本申请还可以有其他的第一EES获取第二EES的能力信息的实现方式。
其中，该步骤2015和步骤2016在步骤2009之前。
图22示出实现方式2的又一种具体实现，其中，多个第二实体包括AC、EEC和EES，其中，EES为多个，即需要一起进行应用上下文迁移的多个第一EAS是注册于多个不同的EES中的。第一实体是多个EES中的一个EES(记为第一EES)，该第一EES根据该多个第二实体的能力信息，为多个第一EAS中、注册于第一EES的至少一个第一EAS确定目标应用上下文迁移场景。此外，多个EES中的其他EES(比如第二EES)也可以根据该多个第二实体的能力信息，为多个第二EAS中、注册于第二EES的至少一个第一EAS确定目标应用上下文迁移场景。在该具体实现中，未详尽描述的内容可参见实现方式2或图18或图20或图21相关实施例中描述。
需要说明的是，为方便描述，如图22中仅画出第一EES和第二EES，其中第二EES即多个EES中除第一EES以外的其他的一个EES。当多个第二实体还包括其他EES(比如第三EES)时，该第一EES和第三EES的交互方式，可参见第一EES和第二EES交互方式。当然本申请并不限定多个EES的个数。
进一步的，图22中包括的步骤2001至步骤2016，可参见图21所示的步骤2001至步骤2016。区别在于，第一EES在确定目标应用上下文迁移场景时，具体是为注册于第一EES中的至少一个第一EAS确定。相应的，在图22中，第二EES也可执行步骤2009和步骤2010，从而第二EES根据第一信息、多个第一EAS支持的应用上下文迁移场景、AC的能力信息、EEC的能力信息、第一EES的能力信息、第二EES的能力信息，确定多个应用上下文迁移场景中是否包括由第一EAS决策的应用上下文迁移场景，进而为注册于第二EES中的至少一个第一EAS确定目标应用上下文迁移场景，该步骤2009和步骤2010的实现方式可参见上述步骤1802-b的说明。
此外，图22中还包括如下步骤2017和步骤2018：
步骤2017，第二EES向第一EES发送第二能力请求，该第二能力请求用于第二EES向第一EES请求第一EES的能力信息。
步骤2018，第一EES在接收到第二能力请求之后，向第二EES发送第一EES的能力信息。如此，第二EES即获取到第一EES的能力信息。
当然，本申请还可以有其他的第二EES获取第一EES的能力信息的实现方式。
其中，该步骤2017和步骤2018在步骤2009之前。
基于上述内容和相同构思，图23和图24为本申请的提供的可能的通信装置的结构示意图。这些通信装置可以用于实现上述方法实施例中的功能，因此也能实现上述方法实施例所具备的有益效果。
在本申请中，该通信装置可以是如图1所示的EEC、EES、AC或EAS。
如图23所示，该通信装置2300包括处理模块2301和收发模块2302。
该通信装置2300中处理模块2301可用于实现上述图3至图6、图12和图13任一个图中所示的方法实施例中第一实体(比如EEC、EES)、AC或EAS(比如第三EAS)的功能。收发模块2302可用于支持该通信装置2300与其他通信设备之间的通信，例如该通信装置2300为EES时，收发模块2302可用于EES接收来自AC的第一信息。或，
该通信装置2300中处理模块2301可用于实现上述图7至图9、图14和图15任一个图中所示的方法实施例中第一实体(比如EEC、EES)、AC或EAS(比如第三EAS)的功能。收发模块2302可用于支持该通信装置2300与其他通信设备之间的通信，例如该通信装置2300为EES时，收发模块2302可用于EES接收来自AC的第一信息。或，
该通信装置2300中处理模块2301可用于实现上述图10、图11或图16中所示的方法实施例中EAS(比如第四EAS)或AC的功能。收发模块2302可用于支持该通信装置2300与其他通信设备之间的通信，例如该通信装置2300为第四EAS时，收发模块2302可用于第四EAS向第一实体(比如EEC、EES)发送第四EAS支持的应用上下文迁移场景。或，
该通信装置2300中处理模块2301可用于实现上述图17或图19中所示的方法实施例中第一实体(比如EEC、EES)、AC或EAS(比如第一EAS)的功能。收发模块2302可用于支持该通信装置2300与其他通信设备之间的通信，例如该通信装置2300为第一实体(比如EES)时，收发模块2302可用于EES接收来自第一EAS的第一EAS的能力信息。或，
该通信装置2300中处理模块2301可用于实现上述图18、图20、图21或图22中所示的方法实施例中第一实体(比如EEC、EES)、第二实体(比如EEC、EES或AC)、AC或EAS(比如第一EAS)的功能。收发模块2302可用于支持该通信装置2300与其他通信设备之间的通信，例如该通信装置2300为第一实体(比如EES)时，第二实体是EEC时，收发模块2302可用于EES接收来自EEC的EEC的能力信息。
如图24所示为本申请实施例提供的装置2400，图24所示的装置可以为图23所示的装置的一种硬件电路的实现方式。该装置可适用于前面所示出的流程图中，执行上述方法实施例中第一终端设备或者第二终端设备的功能。
为了便于说明，图24仅示出了该装置的主要部件。
图24所示的装置2400包括通信接口2410、处理器2420和存储器2430，其中存储器2430用于存储程序指令和/或数据。处理器2420可能和存储器2430协同操作。处理器2420可能执行存储器2430中存储的程序指令。存储器2430中存储的指令或程序被执行时，该处理器2420用于执行上述实施例中处理模块2301执行的操作，通信接口2410用于执行上述实施例中收发模块2302执行的操作。
存储器2430和处理器2420耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。存储器2430中的至少一个可以包括于处理器2420中。
在本申请实施例中，通信接口可以是收发器、电路、总线、模块或其它类型的通信接口。在本申请实施例中，通信接口为收发器时，收发器可以包括独立的接收器、独立的发射器；也可以集成收发功能的收发器、或者是通信接口。
装置2400还可以包括通信线路2440。其中，通信接口2410、处理器2420以及存储器2430可以通过通信线路2440相互连接；通信线路2440可以是外设部件互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended industry standard architecture，简称EISA)总线等。通信线路2440可以分为地址总线、数据总线、控制总线等。为便于表示，图24中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
本申请实施例中还提供一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机实现图3至图6、图12、图13任一个图中所示的方法实施例中第一实体(比如EEC、EES)、AC或EAS(比如第三EAS)的功能；或者实现上述图7至图9、图14、图15任一个图中所示的方法实施例中第一实体(比如EEC或EES)、AC或EAS(比如第三EAS)的功能；或者实现上述图10、图11或图16任一个图中所示的方法实施例中EAS(比如第四EAS)或AC的功能；或者实现上述图17或图19中所示的方法实施例中第一实体(比如EEC、EES)、AC或EAS(比如第一EAS)的功能；或者实现上述图18、图20、图21或图22中所示的方法实施例中第一实体(比如EEC或EES)、第二实体(比如EEC、EES或AC)、AC或EAS(比如第一EAS)的功能。
本申请实施例中还提供一种计算机程序产品，包括计算机指令，当其在计算机上运行时，使得计算机实现图3至图6、图12、图13任一个图中所示的方法实施例中第一实体(比如EEC、EES)、AC或EAS(比如第三EAS)的功能；或者实现上述图7至图9、图14、图15任一个图中所示的方法实施例中第一实体(比如EEC或EES)、AC或EAS(比如第三EAS)的功能；或者实现上述图10、图11或图16中所示的方法实施例中EAS(比如第四EAS)或AC的功能；或者实现上述图17或图19中所示的方法实施例中第一实体(比如EEC、EES)、AC或EAS(比如第一EAS)的功能；或者实现上述图18、图20、图21或图22中所示的方法实施例中第一实体(比如EEC、EES)、第二实体(比如EEC、EES或AC)、AC或EAS(比如第一EAS)的功能。
本申请实施例还提供一种芯片系统，包括：处理器，处理器与存储器耦合，存储器用于存储程序或指令，当程序或指令被处理器执行时，使得该芯片系统实现图3至图6、图12、图13任一个图中所示的方法实施例中第一实体(比如EEC、EES)、AC或EAS(比如第三EAS)的功能；或者实现上述图7至图9、图14、图15任一个图中所示的方法实施例中第一实体(比如EEC、EES)、AC或EAS(比如第三EAS)的功能；或者实现上述图10、图11或图16中所示的方法实施例中EAS(比如第四EAS)或AC的功能；或者实现上述图17或图19中所示的方法实施例中第一实体(比如EEC、EES)、AC或EAS(比如第一EAS)的功能；或者实现上述图18、图20、图21或图22中所示的方法实施例中第一实体(比如EEC、EES)、第二实体(比如EEC、EES或AC)、AC或EAS(比如第一EAS)的功能。
本申请实施例还提供一种通信系统，包括：第一实体(比如EEC、EES)、AC或EAS中的一个或多个。其中，第一实体具备上述图3至图6、图12和图13所示的方法实施例中的第一实体的功能，AC具备上述图3至图6、图12和图13所示的方法实施例中的AC的功能，EAS具备上述图3至图6、图12和图13所示的方法实施例中的第三EAS的功能。
本申请实施例还提供一种通信系统，包括：第一实体(比如EEC、EES)、AC或EAS中的一个或多个。其中，第一实体具备上述图7至图9、图14和图15所示的方法实施例中的第一实体的功能，AC具备上述图7至图9、图14和图15所示的方法实施例中的AC的功能，EAS具备上述图7至图9、图14和图15所示的方法实施例中第三EAS的功能。
本申请实施例还提供一种通信系统，包括：第一实体(比如EEC、EES)、AC或EAS中的一个或多个。其中，第一实体具备上述图10、图11和图16所示的方法实施例中的第一实体的功能，AC具备上述图10、图11和图16所示的方法实施例中的AC的功能，EAS具备上述图10、图11和图16所示的方法实施例中第四EAS的功能。
本申请实施例还提供一种通信系统，包括：第一实体(比如EEC或EES)、AC或EAS中的一个或多个。其中，第一实体具备上述图17或图19所示的方法实施例中的第一实体的功能，AC具备上述图17或图19所示的方法实施例中的AC的功能，EAS具备上述图17或图19所示的方法实施例中第一EAS的功能。
本申请实施例还提供一种通信系统，包括：第一实体(比如EEC或EES)、第二实体(比如EEC、EES或AC)、AC或EAS中的一个或多个。其中，第一实体具备上述图18、图20-图22任一个图所示的方法实施例中的第一实体的功能，AC具备上述图18、图20-图22任一个图所示的方法实施例中的AC的功能，第二实体具备上述图18、图20-图22任一个图所示的方法实施例中的第二实体的功能，EAS具备上述图18、图20-图22任一个图所示的方法实施例中第一EAS的功能。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
本申请实施例中所描述的各种说明性的逻辑单元和电路可以通过通用处理器，数字信号处理器，专用集成电路(ASIC)，现场可编程门阵列(FPGA)或其它可编程逻辑装置，离散门或晶体管逻辑，离散硬件部件，或上述任何组合的设计来实现或操作所描述的功能。通用处理器可以为微处理器，可选地，该通用处理器也可以为任何传统的处理器、控制器、微控制器或状态机。处理器也可以通过计算装置的组合来实现，例如数字信号处理器和微处理器，多个微处理器，一个或多个微处理器联合一个数字信号处理器核，或任何其它类似的配置来实现。
在一个或多个示例性的设计中，本申请所描述的上述功能可以在硬件、软件、固件或这三者的任意组合来实现。如果在软件中实现，这些功能可以存储与电脑可读的媒介上，或以一个或多个指令或代码形式传输于电脑可读的媒介上。电脑可读媒介包括电脑存储媒介和便于使得让电脑程序从一个地方转移到其它地方的通信媒介。存储媒介可以是任何通用或特殊电脑可以接入访问的可用媒体。例如，这样的电脑可读媒体可以包括但不限于RAM、ROM、EEPROM、CD-ROM或其它光盘存储、磁盘存储或其它磁性存储装置，或其它任何可以用于承载或存储以指令或数据结构和其它可被通用或特殊电脑、或通用或特殊处理器读取形式的程序代码的媒介。此外，任何连接都可以被适当地定义为电脑可读媒介，例如，如果软件是从一个网站站点、服务器或其它远程资源通过一个同轴电缆、光纤电脑、双绞线、数字用户线(DSL)或以例如红外、无线和微波等无线方式传输的也被包含在所定义的电脑可读媒介中。的碟片(disk)和磁盘(disc)包括压缩磁盘、镭射盘、光盘、数字通用光盘(英文：Digital Versatile Disc，简称：DVD)、软盘和蓝光光盘，磁盘通常以磁性复制数据，而碟片通常以激光进行光学复制数据。上述的组合也可以包含在电脑可读媒介中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包括这些改动和变型在内。

Claims (47)

  1. 一种应用上下文迁移场景的确定方法，其特征在于，包括：
    所述第一实体根据第一信息，确定多个应用上下文迁移场景是否包括边缘应用服务器EAS决策的应用上下文迁移场景，所述第一信息指示多个第一EAS中的应用上下文需一起迁移；
    所述第一实体从所述多个应用上下文迁移场景中选择目标应用上下文迁移场景。
  2. 如权利要求1所述的方法，其特征在于，所述第一实体根据所述第一信息，确定多个应用上下文迁移场景是否包括EAS决策的应用上下文迁移场景，包括：
    所述第一实体根据所述第一信息，确定所述多个应用上下文迁移场景不包括EAS决策的应用上下文迁移场景。
  3. 如权利要求1或2所述的方法，其特征在于，还包括：
    第一实体接收第一信息。
  4. 如权利要求3所述的方法，其特征在于，所述第一实体接收第一信息，包括：
    所述第一实体接收来自应用客户端AC的所述第一信息，所述AC由多个第二EAS提供服务，所述多个第一EAS是所述多个第二EAS中的部分或全部。
  5. 如权利要求1-4任一项所述的方法，其特征在于，所述第一信息包含于AC的配置信息中。
  6. 如权利要求1-5任一项所述的方法，其特征在于，所述第一信息包括所述多个第一EAS的标识和/或第一指示；
    所述第一指示用于指示所述多个第一EAS中的应用上下文需一起迁移。
  7. 如权利要求1-6任一项所述的方法，其特征在于，还包括：
    所述第一实体接收第二信息，所述第二信息指示所述多个第一EAS中是否存在第三EAS，所述第三EAS具有对所述多个第一EAS中的应用上下文一起迁移的能力；
    所述第一实体根据所述第一信息，确定多个应用上下文迁移场景是否包括EAS决策的应用上下文迁移场景，包括：
    所述第一实体根据所述第一信息和所述第二信息，确定所述多个应用上下文迁移场景是否包括EAS决策的应用上下文迁移场景。
  8. 如权利要求7所述的方法，其特征在于，
    在所述多个第一EAS中不存在所述第三EAS的情况下，所述多个应用上下文迁移场景不包括所述EAS决策的应用上下文迁移场景；或，
    在所述多个第一EAS中存在所述第三EAS的情况下，所述多个应用上下文迁移场景包括所述EAS决策的应用上下文迁移场景。
  9. 如权利要求1-8任一项所述的方法，其特征在于，所述第一实体是边缘使能客户端EEC或边缘使能服务器EES。
  10. 如权利要求9所述的方法，其特征在于，
    所述第一实体是所述EEC的情况下，所述EEC从AC接收所述第一信息，所述EEC从EES接收由所述EES转发的第二信息；或，
    所述第一实体是所述EES的情况下，所述EES从EEC接收所述第一信息，所述EES从第三EAS接收第二信息。
  11. 如权利要求1-10任一项所述的方法，其特征在于，还包括：
    AC向所述第一实体发送所述第一信息。
  12. 如权利要求1-11任一项所述的方法，其特征在于，还包括：
    AC向第三EAS发送所述多个第一EAS的标识。
  13. 一种应用上下文迁移场景的确定方法，其特征在于，包括：
    第一实体接收第一信息，所述第一信息指示多个第一边缘应用服务器EAS中的应用上下文需一起迁移；
    所述第一实体根据所述第一信息，向第三EAS发送所述多个第一EAS的标识，所述第三EAS是所述多个第一EAS中的一个或多个。
  14. 如权利要求13所述的方法，其特征在于，所述方法还包括：所述第一实体确定目标应用上下文迁移场景；
    所述第一实体根据所述第一信息，向第三EAS发送所述多个第一EAS的标识，包括：
    在所述目标应用上下文迁移场景包括EAS决策的应用上下文迁移场景的情况下，所述第一实体根据所述第一信息，向所述第三EAS发送所述多个第一EAS的标识。
  15. 如权利要求13或14所述的方法，其特征在于，
    所述第一实体接收第一信息，包括：
    所述第一实体接收来自应用客户端AC的所述第一信息，所述AC由多个第二EAS提供服务，所述多个第一EAS是所述多个第二EAS中的部分或全部。
  16. 如权利要求13-15任一项所述的方法，其特征在于，所述第一信息包含于所述AC的配置信息中。
  17. 如权利要求13-16任一项所述的方法，其特征在于，所述第一信息中包括所述多个第一EAS的标识和/或第一指示；
    所述第一指示用于指示所述多个第一EAS中的应用上下文需一起迁移。
  18. 如权利要求13-17任一项所述的方法，其特征在于，所述第一实体是边缘使能客户端EEC或边缘使能服务器EES。
  19. 如权利要求18所述的方法，其特征在于，
    所述第一实体是所述EEC的情况下，所述EEC从AC接收所述第一信息，所述EEC通过EES向所述第三EAS发送所述多个第一EAS的标识；或，
    所述第一实体是所述EES的情况下，所述EES从EEC接收所述第一信息，所述EES向所述第三EAS发送所述多个第一EAS的标识。
  20. 如权利要求13-19任一项所述的方法，其特征在于，还包括：
    所述AC向所述第一实体发送所述第一信息。
  21. 一种应用上下文迁移场景的确定方法，其特征在于，包括：
    边缘应用服务器EAS根据第一信息，确定所述EAS支持的应用上下文迁移场景不包括EAS决策的应用上下文迁移场景，所述第一信息指示多个第一EAS中的应用上下文需一起迁移；
    所述EAS发送所述EAS支持的应用上下文迁移场景。
  22. 如权利要求21所述的方法，其特征在于，所述EAS支持的应用上下文迁移场景用 于确定目标应用上下文迁移场景。
  23. 如权利要求21或22所述的方法，其特征在于，所述EAS发送所述EAS支持的应用上下文迁移场景，包括：
    所述EAS向第一实体发送所述EAS支持的应用上下文迁移场景，所述第一实体是边缘使能客户端EEC或边缘使能服务器EES。
  24. 如权利要求21-23任一项所述的方法，其特征在于，还包括：
    所述EAS接收来自应用客户端AC的所述第一信息，所述AC由多个第二EAS提供服务，所述多个第一EAS是所述多个第二EAS中的部分或全部。
  25. 如权利要求21-24任一项所述的方法，其特征在于，所述第一信息包含于所述AC的配置信息中。
  26. 一种应用上下文迁移场景的确定方法，其特征在于，包括：
    第一实体获取多个第一边缘应用服务器EAS的能力信息；
    所述第一实体根据所述多个第一EAS的能力信息，为所述多个第一EAS确定对应的目标应用上下文迁移场景；
    所述多个第一EAS是关联的EAS，所述关联的EAS中的应用上下文需一起迁移；
    所述第一EAS的能力信息指示所述第一EAS是否具备处理所述关联的EAS中的应用上下文一起迁移的能力。
  27. 如权利要求26所述的方法，其特征在于，所述第一EAS的能力信息指示所述第一EAS是否支持如下能力中的一项或多项：
    获取所述多个第一EAS的标识的能力；
    向所述多个第一EAS中其他EAS发送迁移通知的能力；
    接收来自所述多个第一EAS中其他EAS的迁移通知的能力；
    支持由所述第一EAS决策的应用上下文迁移场景；
    其中，所述迁移通知用于触发应用上下文迁移。
  28. 如权利要求26或27所述的方法，其特征在于，所述第一实体根据所述多个第一EAS的能力信息，为所述多个第一EAS确定对应的目标应用上下文迁移场景，包括：
    所述第一实体根据所述多个第一EAS的能力信息，确定所述目标应用上下文迁移场景中是否包括由所述多个第一EAS中的一个第一EAS决策的应用上下文迁移场景。
  29. 如权利要求28所述的方法，其特征在于，所述第一实体根据所述多个第一EAS的能力信息，确定所述目标应用上下文迁移场景中是否包括由所述多个第一EAS中的一个第一EAS决策的应用上下文迁移场景，包括：
    在所述多个第一EAS中的所述一个第一EAS支持如下能力中的一项或多项：获取所述多个第一EAS的标识的能力、向所述多个第一EAS中其他EAS发送迁移通知的能力、支持由所述第一EAS决策的应用上下文迁移场景的情况下，所述第一实体确定所述目标应用上下文迁移场景中包括由所述一个第一EAS决策的应用上下文迁移场景。
  30. 如权利要求26-29中任一项所述的方法，其特征在于，还包括：
    所述第一实体是边缘使能客户端EEC的情况下，所述EEC从边缘使能服务器EES接收由所述EES转发的所述多个第一EAS的能力信息；或，
    所述第一实体是EES的情况下，所述EES从第一EAS接收所述第一EAS的能力信息。
  31. 如权利要求26-30中任一项所述的方法，其特征在于，还包括：
    所述第一实体接收第一信息，所述第一信息指示所述多个第一EAS是关联的EAS。
  32. 一种应用上下文迁移场景的确定方法，其特征在于，包括：
    第一实体获取第二实体的能力信息；
    所述第一实体根据所述第二实体的能力信息，为多个第一边缘应用服务器EAS中的至少一个第一EAS确定对应的目标应用上下文迁移场景；
    所述多个第一EAS是关联的EAS，所述关联的EAS中的应用上下文需一起迁移；
    所述第二实体的能力信息指示所述第二实体是否具备处理所述关联的EAS中的应用上下文一起迁移的能力。
  33. 如权利要求32所述的方法，其特征在于，所述第二实体是应用客户端AC、边缘使能客户端EEC或边缘使能服务器EES。
  34. 如权利要求32或33所述的方法，其特征在于，所述第二实体的能力信息指示所述第二实体是否支持如下能力中的一项或多项：
    获取所述多个第一EAS的标识的能力；
    接收所述多个第一EAS中一个第一EAS的触发迁移通知的指示，向所述多个第一EAS中其他的第一EAS发送所述迁移通知的能力；
    其中，所述迁移通知用于触发应用上下文迁移。
  35. 如权利要求32-34中任一项所述的方法，其特征在于，所述多个第一EAS中的一个第一EAS支持的应用上下文迁移场景包括：由所述第一EAS决策的应用上下文迁移场景；
    所述多个第一EAS中除所述一个第一EAS以外的其他EAS支持的应用上下文迁移场景包括：由所述第二实体检测触发的应用上下文迁移场景。
  36. 如权利要求32-35中任一项所述的方法，其特征在于，所述第一实体根据所述第二实体的能力信息，为多个第一EAS中的至少一个第一EAS确定对应的目标应用上下文迁移场景，包括：
    在所述第二实体的能力信息指示所述第二实体具备处理所述关联的EAS中的应用上下文一起迁移的能力的情况下，确定所述目标应用上下文迁移场景中包括由所述至少一个第一EAS中的第一EAS决策的应用上下文迁移场景。
  37. 如权利要求32-36中任一项所述的方法，其特征在于，还包括：
    所述第一实体是EEC的情况下：若所述第二实体是AC，所述EEC从所述AC接收所述AC的能力信息；和/或，若所述第二实体是EES，所述EEC从所述EES接收所述EES的能力信息；
    所述第一实体是EES的情况下：若所述第二实体是EEC，所述EES从所述EEC接收所述EEC的能力信息；和/或，若所述第二实体是AC，所述EES从所述EEC接收由所述EEC转发的、所述AC的能力信息。
  38. 如权利要求32-37中任一项所述的方法，其特征在于，还包括：
    所述第一实体接收第一信息，所述第一信息指示所述多个第一EAS是关联的EAS。
  39. 如权利要求32-38中任一项所述的方法，其特征在于，所述多个第一EAS注册于多个EES中。
  40. 如权利要求39所述的方法，其特征在于，所述第二实体包括所述多个EES，第一 EES的能力信息指示所述第一EES是否支持如下能力中的一项或多项：
    获取所述多个第一EAS的标识的能力；
    获取所述第一EES中注册的至少一个第一EAS的标识的能力；
    获取所述多个EES的标识的能力；
    接收来自所述多个第一EAS中的一个第一EAS的触发迁移通知的指示，向所述多个第一EAS中的其他EAS发送迁移通知的能力；
    其中，所述迁移通知用于触发应用上下文迁移；
    所述第一EES是所述多个EES中的一个。
  41. 如权利要求39或40所述的方法，其特征在于，所述第一实体根据所述第二实体的能力信息，为多个第一EAS中的至少一个第一EAS确定对应的目标应用上下文迁移场景，包括：
    所述第一实体是第一EES的情况下，所述第一EES根据所述第二实体的能力信息，为所述多个第一EAS中注册于所述第一EES中的至少一个第一EAS确定对应的目标应用上下文迁移场景，所述第一EES是所述多个EES中的一个。
  42. 如权利要求39或40所述的方法，其特征在于，所述第一实体根据所述第二实体的能力信息，为多个第一EAS中的至少一个第一EAS确定对应的目标应用上下文迁移场景，包括：
    所述第一实体是第一EES的情况下，所述第一EES根据所述第二实体的能力信息，为所述多个第一EAS确定对应的目标应用上下文迁移场景；
    其中，所述第一EES是由AC或EEC指定的、所述多个EES中的一个EES；
    或，所述第一EES中预配置有第三指示，所述第三指示用于指示所述第一EES是所述多个EES中、用于为所述多个第一EAS确定对应的目标应用上下文迁移场景的EES；
    或，所述第一EES是所述多个EES中注册有主EAS的EES。
  43. 如权利要求39-42中任一项所述的方法，其特征在于，
    所述第一实体是第一EES、所述第二实体包括所述多个EES中的其他EES的情况下，所述第一EES从所述其他EES接收所述其他EES的能力信息；
    其中，所述第一EES是所述多个EES中的一个。
  44. 一种通信装置，其特征在于，包括用于执行如权利要求1至12中的任一项所述方法的模块；或包括用于执行如权利要求13至20中的任一项所述方法的模块；或包括用于执行如权利要求21至25中的任一项所述方法的模块；或包括用于执行如权利要求26至31中的任一项所述方法的模块；或包括用于执行如权利要求32至43中的任一项所述方法的模块。
  45. 一种通信装置，其特征在于，包括处理器，所述处理器与存储器相连，所述存储器用于存储计算机程序，所述处理器用于执行所述存储器中存储的计算机程序，以使得所述装置执行如权利要求1至12中的任一项所述方法，或执行如权利要求13至20中的任一项所述方法，或执行如权利要求21至25中的任一项所述方法，或执行如权利要求26至31中的任一项所述方法，或执行如权利要求32至43中的任一项所述方法。
  46. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机程序或指令，当所述计算机程序或指令被通信装置执行时，实现如权利要求1至12中的 任一项所述方法，或实现如权利要求13至20中的任一项所述方法，或实现如权利要求21至25中的任一项所述方法，或实现如权利要求26至31中的任一项所述方法，或实现如权利要求32至43中的任一项所述方法。
  47. 一种计算机程序产品，其特征在于，所述计算机程序产品包括计算机程序或指令，当所述计算机程序或指令被通信装置执行时，实现如权利要求1至12中的任一项所述方法，或实现如权利要求13至20中的任一项所述方法，或实现如权利要求21至25中的任一项所述方法，或实现如权利要求26至31中的任一项所述方法，或实现如权利要求32至43中的任一项所述方法。
PCT/CN2023/084010 2022-03-29 2023-03-27 一种应用上下文迁移场景的确定方法及通信装置 WO2023185710A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202210323867 2022-03-29
CN202210323867.5 2022-03-29
CN202210689587.6 2022-06-16
CN202210689587.6A CN116939746A (zh) 2022-03-29 2022-06-16 一种应用上下文迁移场景的确定方法及通信装置

Publications (1)

Publication Number Publication Date
WO2023185710A1 true WO2023185710A1 (zh) 2023-10-05

Family

ID=88199412

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/084010 WO2023185710A1 (zh) 2022-03-29 2023-03-27 一种应用上下文迁移场景的确定方法及通信装置

Country Status (1)

Country Link
WO (1) WO2023185710A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021137579A1 (ko) * 2020-01-03 2021-07-08 삼성전자 주식회사 에지 컴퓨팅 시스템에서 어플리케이션 컨텍스트 재배치 조정 방법 및 장치
KR20210087881A (ko) * 2020-01-03 2021-07-13 삼성전자주식회사 에지 컴퓨팅 시스템에서 어플리케이션 컨텍스트 재배치 조정 방법 및 장치
WO2021204510A1 (en) * 2020-04-06 2021-10-14 Sony Group Corporation Relocation of application context to edge data network
US20220015018A1 (en) * 2020-07-13 2022-01-13 Qualcomm Incorporated User equipment (ue) triggered edge computing application context relocation

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021137579A1 (ko) * 2020-01-03 2021-07-08 삼성전자 주식회사 에지 컴퓨팅 시스템에서 어플리케이션 컨텍스트 재배치 조정 방법 및 장치
KR20210087881A (ko) * 2020-01-03 2021-07-13 삼성전자주식회사 에지 컴퓨팅 시스템에서 어플리케이션 컨텍스트 재배치 조정 방법 및 장치
WO2021204510A1 (en) * 2020-04-06 2021-10-14 Sony Group Corporation Relocation of application context to edge data network
US20220015018A1 (en) * 2020-07-13 2022-01-13 Qualcomm Incorporated User equipment (ue) triggered edge computing application context relocation

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SAMSUNG ELECTRONICS: "Informing EES of the selected EAS", 3GPP TSG-SA WG6 MEETING #39-BIS-E, S6-201970, 17 October 2020 (2020-10-17), XP051940395 *

Similar Documents

Publication Publication Date Title
WO2020259509A1 (zh) 一种应用迁移方法及装置
CN114145054B (zh) 用于支持流量导向通过服务功能链的系统和方法
WO2022012310A1 (zh) 一种通信方法及装置
EP3836515B1 (en) Communication method and communication device for reducing complexity in processing of service instances.
CN112136294A (zh) 应用功能影响业务路由的消息和系统
US11729137B2 (en) Method and device for edge application server discovery
US20130176903A1 (en) Methods and Apparatus for Establishing a Tunneled Direct Link Setup (TDLS) Session Between Devices in a Wireless Network
US20230254364A1 (en) Method and apparatus for transferring an edge computing application
WO2021168714A1 (zh) 一种发现应用的方法、装置及系统
WO2021168715A1 (zh) 一种发现应用的方法、装置及系统
WO2021051420A1 (zh) 一种dns缓存记录的确定方法及装置
WO2018000202A1 (zh) 一种负载迁移方法、装置及系统
WO2023011217A1 (zh) 一种通信方法及装置
WO2018129665A1 (zh) 通信方法、网络开放功能网元和控制面网元
US20230164234A1 (en) Service continuity event notification method, and apparatus
WO2022022322A1 (zh) 访问本地网络的方法和装置
WO2023185710A1 (zh) 一种应用上下文迁移场景的确定方法及通信装置
WO2022099484A1 (zh) 标识发送方法和通信装置
US20200177675A1 (en) Communication device and method of controlling same
WO2023185654A1 (zh) 一种通信方法及装置
CN112383617A (zh) 进行长连接的方法、装置、终端设备以及介质
WO2022213824A1 (zh) 一种用于传输上下文的方法和通信装置
WO2023185567A1 (zh) 发现应用服务器的方法和装置
CN116939746A (zh) 一种应用上下文迁移场景的确定方法及通信装置
WO2023051581A1 (zh) 应用上下文重定位的方法和装置

Legal Events

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

Ref document number: 23778077

Country of ref document: EP

Kind code of ref document: A1