Information indication method, and apparatus

Abstract

Provided in the present application are an information indication method and a communication apparatus. The information indication method comprises: determining that there is a common area among service areas of at least two target edge application servers (EASs), wherein the at least two target EASs are EASs corresponding to a first application; sending first indication information, wherein the first indication information is used for indicating at least one of the following: the at least two target EASs requiring collaborative application context relocation; or there being the public area among the service areas of the at least two target EASs. By means of the present application, the collaborative application context relocation of a plurality of EASs of the same application can be realized, thereby saving on signaling overheads.

Description

Information indication method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on June 21, 2023, with application number 202310748120.9, and priority to the Chinese patent application entitled “Information Indication Method and Device”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to an information indication method and device. Background Art

[0003] Mobile edge computing (MEC) is a technology that sinks data processing and data computing to the edge of the network to achieve fast computing on the edge of the network, thereby achieving fast service response of applications. In MEC, an application can call multiple application instances / edge application servers (EAS) to obtain the required services. As the terminal device moves, the source EAS can perform application context relocation (ACR), that is, migrate the application context from the source EAS to the target EAS. In a scenario where an application calls multiple EASs, multiple EASs serving the same application can perform ACR collaboratively, that is, multiple EASs perform ACR together. How to achieve collaborative ACR of multiple EASs while saving signaling overhead has become a technical problem that needs to be solved urgently.

[0004] Summary of the Invention

[0005] The present application provides an information indication method and apparatus, which can realize the collaborative application context migration of multiple EASs of the same application, saving signaling overhead.

[0006] In a first aspect, an embodiment of the present application provides an information indication method, wherein the method can be performed by an edge-enabled client EEC, or by a component of the edge-enabled client EEC (e.g., a processor, a chip, or a chip system). The information indication method may include:

[0007] Determine that there is a common area in the service areas of at least two target EASs, and the at least two target EASs are EASs corresponding to the first application; send first indication information, and the first indication information is used to indicate at least one of the following: used to indicate that the at least two target EASs need to coordinate application context migration; or indicate that there is a common area in the service areas of the at least two target EASs.

[0008] Exemplarily, the above-mentioned at least two target EASs need to coordinate application context migration, which can be understood as the at least two target EASs need to perform application context migration together, or it can be understood as if there is an EAS among the at least two target EASs that needs to perform application context migration, then the at least two target EASs both need to perform application context migration.

[0009] By implementing the method described in the first aspect, when the EEC determines that at least two target EASs corresponding to the first application have a common area, it sends first indication information indicating at least one of the following: the at least two target EASs need to coordinate application context migration, or the service areas of the at least two target EASs have a common area. This facilitates subsequent triggering of coordinated application context migration between the at least two target EASs and the EESs associated with the at least two EASs when application context migration is required, avoiding interaction between EASs and corresponding EESs that do not have a common area, thereby saving signaling overhead.

[0010] In a possible implementation, the service key performance indicators (KPIs) required by the first application for the at least two target EASs belong to the same range, or the service KPIs required by the first application for the at least two target EASs are the same.

[0011] By implementing this method, at least two target EASs with the same KPI level are migrated together for application context, so that the migrated EAS can improve the KPI of the same level for the terminal device and meet the service KPI requirements of the application.

[0012] In a possible implementation, the method further includes:

[0013] A first request message is sent to the edge configuration server ECS, where the first request message is used to request information of the edge enabling server EES corresponding to the EAS identifier, the requested EAS identifier corresponds to the first application, and the requested EAS identifier includes identifiers of the at least two EASs.

[0014] By implementing this approach, the EEC can request the ECS for information on the EES corresponding to the EAS identifier, thereby obtaining information on the EES corresponding to the EAS in the public area of ​​the service area.

[0015] In a possible implementation, the method further includes:

[0016] Receive a first response message from the ECS, the first response message including at least one of the following: the second indication information, the service area of ​​at least one EES, and the service area of ​​at least one EAS corresponding to the at least one EES, wherein the second indication information is used to indicate that in at least one target EES, there is a common area in the service areas of the at least two target EASs.

[0017] By implementing this method, the ECS can determine that there is a common area in the service areas of at least two target EASs, or the ECS sends the service area of ​​the EES or the service area of ​​the EAS to the EEC to determine that there is a common area in the service areas of at least two target EASs, thereby facilitating the determination of at least two target EASs that need to collaborate in application context migration to meet application requirements.

[0018] In a possible implementation, the first response message includes a service area of ​​at least one EAS corresponding to the at least one EES, and the method further includes:

[0019] At least one target EES is determined according to the service area of ​​at least one EAS corresponding to the at least one EES, wherein, in the at least one target EES, service areas of the at least two target EASs have a common area.

[0020] In implementing this method, the EEC determines at least one target EES based on the service area of ​​at least one EAS returned by the ECS, thereby ensuring that in the at least one target EES, the service areas of at least two target EASs have a common area. The at least two target EASs can be collaboratively migrated for application context to meet the service key performance indicator (KPI) requirements of the application.

[0021] In a possible implementation, the first response message includes a service area of ​​the at least one EES, and the method further includes:

[0022] At least one target EES is determined according to the service area of ​​the at least one EES, where the service areas of the at least one target EES have a common area.

[0023] In this manner, the EEC determines at least one target EES based on the service area of ​​the at least one EES returned by the ECS, thereby ensuring that the service areas of the at least one target EES determined have a common area.

[0024] In a possible implementation, the service area of ​​the EES is the same as the service area of ​​the EAS corresponding to the EES.

[0025] By implementing this approach, the service area of ​​the EES is the same as the service area of ​​the EAS corresponding to the EES, thereby ensuring that the service areas of at least two target EASs in the determined at least one target EES have a common area.

[0026] In a possible implementation, the method further includes:

[0027] Obtaining, from the at least one target EES, a service area of ​​an EAS corresponding to the at least one target EES;

[0028] According to the service area of ​​the EAS corresponding to the at least one target EES, it is determined that the service areas of the at least two target EASs have a common area.

[0029] By implementing this method, the EEC can further obtain the service area of ​​the corresponding EAS from the determined target EES, thereby determining that the service areas of at least two target EASs have a common area, which facilitates the coordinated application context migration of the at least two target EASs to meet the service KPI requirements of the application.

[0030] In a possible implementation, the sending the first indication information includes:

[0031] The first indication information is sent to the at least one target EES respectively.

[0032] To implement this approach, when the EEC determines that there is a common area in the service areas of at least two target EASs, it needs to send indication information to at least one target EES, so that the target EES notifies the corresponding target EAS that a coordinated application context migration is required.

[0033] In a second aspect, an embodiment of the present application provides an information indication method, wherein the method can be performed by an edge enabling server EES, or by a component of the edge enabling server EES (such as a processor, chip, or chip system). The information indication method may include:

[0034] Receive first indication information from an edge enabling client EEC, where the first indication information is used to indicate at least one of the following: indicating that at least two target EASs cooperate with application context migration; or indicating that service areas of at least two target EASs have a common area, and the at least two target EASs are EASs corresponding to the first application;

[0035] The first indication information is sent to a first EAS corresponding to the EES, where the at least two target EASs include the first EAS.

[0036] By implementing the method described in the second aspect, when EES receives the indication information, it needs to send the indication information to the corresponding target EAS to indicate that at least two target EAS need to coordinate the application context migration, thereby facilitating the subsequent collaborative application context migration of the at least two target EAS to meet the service KPI requirements of the application.

[0037] In a third aspect, an embodiment of the present application provides an information indication method, wherein the method can be executed by an edge configuration server ECS, or by a component of the edge configuration server ECS (such as a processor, chip, or chip system). The information indication method may include:

[0038] Receive a first request message, where the first request message is used to request information of an edge enabling server (EES) corresponding to an EAS identifier, where the requested EAS identifier corresponds to the first application;

[0039] In response to the first request message, a first response message is sent, and the first response message includes at least one of the following: first indication information, the service area of ​​at least one EES, and the service area of ​​at least one EAS corresponding to at least one EES. The first indication information is used to indicate at least one of the following: used to indicate that at least two target EASs need to coordinate application context migration; or to indicate that there is a common area in the service areas of at least two target EASs, and the requested EAS identifier includes the identifiers of the at least two target EASs.

[0040] By implementing the method described in the third aspect, when receiving information requesting the EES to identify the corresponding EES, the ECS can determine that the service areas of at least two target EASs have a common area, and thus send indication information to indicate that the service areas of at least two target EASs have a common area, or the ECS can send the service area of ​​the EES or the service area of ​​the EAS to the EEC or the source EES, so that the EEC or the source EES can determine that the service areas of at least two target EASs have a common area, so that the at least two target EASs can perform collaborative application context migration to ensure the service KPIs of the at least two target EASs.

[0041] In a possible implementation, the first response message includes the first indication information, and the method further includes:

[0042] The ECS determines at least one target EES, in which service areas of the at least two target EASs have a common area;

[0043] The first response message further includes information of the at least one target EES.

[0044] By implementing this approach, the ECS can determine at least one target EES to ensure that in the at least one target EES, service areas of at least two target EASs have a common area, thereby facilitating subsequent collaborative application context migration by the at least two target EASs.

[0045] In a possible implementation, in the at least one target EES, service areas of the at least two target EASs have a common area, including:

[0046] The service area of ​​the at least one target EES has a common area, and the service area of ​​the target EES is the same as the service area of ​​the EAS corresponding to the target EES.

[0047] By implementing this method, the service area of ​​the EES is the same as the service area of ​​the corresponding EAS. Therefore, when there is a common area in the service area of ​​at least one target EES, there is also a common area in the service areas of at least two target EASs, thereby improving the efficiency of determining whether there is a common area in the service areas of at least two target EASs.

[0048] In a possible implementation, the first request message comes from an edge enabling client EEC, or at least one source EES.

[0049] By implementing this approach, the EEC or source EES can request EES information from the ECS and determine that the service areas of at least two target EASs have a common area, which can not only be adapted to initial EAS discovery, but also be applied to target EAS discovery during application context migration.

[0050] In a fourth aspect, an embodiment of the present application provides an information indication method, wherein the method can be performed by a source edge enabling server EES, or by a component of the source edge enabling server EES (such as a processor, chip, or chip system). The information indication method may include:

[0051] Sending a first request message to the edge configuration server ECS, where the first request message is used to request information of the edge enabling server EES corresponding to the EAS identifier, where the requested EAS identifier corresponds to the first application;

[0052] Receive a first response message from the ECS, the first response message including at least one of the following information: first indication information, a service area of ​​at least one EES, and a service area of ​​at least one EAS corresponding to at least one EES, the first indication information being used to indicate at least one of the following: used to indicate that at least two target EASs need to coordinate application context migration; or to indicate that there is a common area in the service areas of at least two target EASs, and the requested EAS identifier includes the identifiers of the at least two target EASs.

[0053] By implementing the method described in the fourth aspect, when the application context is migrated, the source EES can request the information of the target EES from the ECS and determine whether at least two target EASs need to collaborate in the application context migration, so that the source EES can use the at least two target EASs as EASs that need to collaborate in the application context migration later.

[0054] In a possible implementation, the first response message includes the first indication information; the first response message also includes a target EES corresponding to the source EES.

[0055] In this manner, when the ECS determines that at least two target EASs need to coordinate application context migration, the target EES corresponding to the source EES needs to be sent to the source EES, thereby facilitating the source EES to notify the corresponding target EES that at least two target EASs need to coordinate application context migration.

[0056] In a possible implementation, the first response message includes a service area of ​​the at least one EES or a service area of ​​at least one EAS corresponding to the at least one EES; and the method further includes:

[0057] A target EES corresponding to the source EES is determined according to a service area of ​​the at least one EES or a service area of ​​at least one EAS corresponding to the at least one EES.

[0058] By implementing this approach, the source EES can determine the target EES corresponding to the source EES based on the service area of ​​the EES or the service of the EAS returned by the ECS, thereby ensuring that the service areas of at least two target EASs have a common area, thereby meeting the service KPI requirements of the application.

[0059] In a possible implementation, the method further includes:

[0060] The first indication information is sent to the target EES.

[0061] By implementing this approach, the source EES can notify the target EES that at least two target EASs need to coordinate application context migration, so that subsequent target EESs can trigger each other with corresponding EESs to coordinate application context migration when application context migration is detected.

[0062] In a possible implementation, the method further includes:

[0063] The first indication information is sent to the edge enabling client EEC.

[0064] In this implementation, the source EES notifies the EEC that there is a common area in the service areas of at least two target EASs, so that when the EEC subsequently detects an application context migration event, it can trigger the corresponding EES to coordinate application context migration.

[0065] In a fifth aspect, an embodiment of the present application provides an information indication method, wherein the method can be performed by a first edge enabling server EES, or by a component of the first edge enabling server EES (such as a processor, chip, or chip system). The information indication method may include:

[0066] Determining that a service area of ​​a first target EAS and a service area of ​​a second target EAS have a common area, and that the first EAS and the second EAS correspond to a first application;

[0067] Sending first indication information to the second EES, wherein the first indication information is used to indicate at least one of the following: indicating that the first target EAS and the second target EAS need to coordinate application context migration; or indicating that the service areas of the first target EAS and the second target EAS have a common area.

[0068] By implementing the method described in the fifth aspect, the first EES can determine that there is a common area between the service area of ​​the first target EAS and the service area of ​​the second target EAS. The first EES further indicates to the second EES that the first target EAS and the second target EAS need to coordinate application context migration, thereby determining the target EAS that needs to coordinate application context migration through interaction between the first EES and the second EES. When an application context migration event is subsequently detected, the first target EAS, the second target EAS, the first target EES and the second target EES trigger each other to perform collaborative application context migration, thereby avoiding signaling waste caused by mutual triggering of collaborative application context migration between EASs and EESs that do not have a common area.

[0069] In a possible implementation, the method further includes:

[0070] receiving a first request message sent from the second EES, where the first request message is used to request the first EES to determine whether the EAS corresponding to the first application exists in a public area;

[0071] The sending the first indication information to the second EES includes:

[0072] A first response message is sent to the second EES, where the first response message includes the first indication information.

[0073] When implementing this method, the second EES can request the first EES to determine whether there is a common area in the EAS corresponding to the first application, thereby triggering the first EES to determine whether there is a common area in the service areas of at least two target EASs corresponding to the first application. The at least two target EASs need to coordinate application context migration to meet the service KPI requirements of the first application.

[0074] In a possible implementation, the first EES is a first source EES, and the second EES is a second source EES; the first request message includes a service area of ​​a second target EES corresponding to the second source EES;

[0075] The determining that a common area exists between the service area of ​​the first target EAS and the service area of ​​the second target EAS includes:

[0076] According to the service area of ​​the second target EES and the service area of ​​the first target EES, it is determined that there is a common area between the service area of ​​the first target EAS and the service area of ​​the second target EAS, the first target EES is the target EES selected by the first source EES, the service area of ​​the first target EES is the same as the service area of ​​the EAS corresponding to the first target EES, and the first target EAS is the EAS corresponding to the first target EES.

[0077] In implementing this method, the first EES and the second EES can be source EESs respectively. Through the interaction between at least two source EESs, it is determined that the service areas of at least two target EESs determined by the at least two source EESs have a common area. Since the service area of ​​the target EES is the same as the service area of ​​the corresponding EAS, the service areas of at least two target EASs among the at least two target EESs have a common area, which facilitates determination that the at least two target EASs can subsequently collaborate to perform application context migration.

[0078] In a possible implementation, the first EES is a first source EES, and the second EES is a second source EES; the first request message includes a service area of ​​the second target EAS corresponding to the second target EES selected by the second source EES;

[0079] The determining that a common area exists between the service area of ​​the first target EAS and the service area of ​​the second target EAS includes:

[0080] According to the service areas of the second target EAS and the first target EAS, it is determined that the service areas of the first target EAS and the second target EAS have a common area, and the first target EAS is the EAS corresponding to the first target EES selected by the first source EES.

[0081] In this implementation, the first EES and the second EES can be source EESs respectively. The interaction between the at least two source EESs determines that the service areas of the at least two target EASs have a common area, which facilitates the subsequent determination that the at least two target EASs can collaborate in application context migration.

[0082] In a possible implementation, the method further includes:

[0083] The first indication information is sent to the first target EES.

[0084] When implementing this method, when the source EES determines that there is a common area in the service areas of at least two target EASs, it is also necessary to send a first indication message to the corresponding target EES so that when an application context migration event is detected later, the target EESs can trigger each other to coordinate application context migration, thereby avoiding the signaling waste caused by mutual triggering in the scenario where there is no common area in the target EAS.

[0085] In one possible implementation, the first EES is a first target EES, and the second EES is a second target EES; the first target EES corresponds to the first target EAS, and the second target EES corresponds to the second target EAS; the first request message includes a service area of ​​the second target EES, and the service area of ​​the second target EES is the same as the service area of ​​the EAS corresponding to the second target EES;

[0086] The determining that a common area exists between the service area of ​​the first target EAS and the service area of ​​the second target EAS includes:

[0087] According to the service areas of the second target EES and the first target EES, it is determined that the service areas of the first target EAS and the second target EAS have a common area, and the service area of ​​the first target EES is the same as the service area of ​​the EAS corresponding to the first target EES.

[0088] In implementing this method, the first EES and the second EES can be target EESs respectively. Through the interaction between at least two target EESs, it is determined that there is a common area in the service areas of the at least two target EESs. Since the service area of ​​the target EES is the same as the service area of ​​the corresponding EAS, there is a common area in the service areas of at least two target EESs among the at least two target EESs, which facilitates determination that the at least two target EASs can subsequently collaborate to perform application context migration.

[0089] In one possible implementation, the first EES is a first target EES, and the second EES is a second target EES; the first target EES corresponds to the first target EAS, and the second target EES corresponds to the second target EAS, and the first request message includes a service area of ​​the second target EAS corresponding to the second target EES;

[0090] The determining that a common area exists between the service area of ​​the first target EAS and the service area of ​​the second target EAS includes:

[0091] According to the service areas of the second target EAS and the first target EAS, it is determined that the service areas of the first target EAS and the second target EAS have a common area, and the first target EAS is the EAS corresponding to the first target EES.

[0092] In this implementation, the first EES and the second EES can be target EESs respectively. By interaction between at least two target EESs, it is determined that the service areas of the at least two target EESs have a common area, which facilitates subsequent determination that the at least two target EASs can collaborate in application context migration.

[0093] In a possible implementation, the method further includes:

[0094] The first indication information is sent to the first target EAS.

[0095] In implementing this approach, when the target EES determines that the service areas of at least two target EASs have a common area, it needs to send first indication information to the corresponding target EASs to indicate that the at least two target EASs need to coordinate application context migration.

[0096] In a sixth aspect, the present application provides a communication device, applied to an edge-enabled client EEC, the device comprising:

[0097] A processing unit, configured to determine that service areas of at least two target edge application servers (EASs) have a common area, where the at least two target EASs are EASs corresponding to the first application;

[0098] The transceiver unit is configured to send first indication information, where the first indication information is used to indicate at least one of the following: indicating that the at least two target EASs need to coordinate application context migration; or indicating that service areas of the at least two target EASs have a common area.

[0099] In a possible implementation manner, the transceiver unit is configured to perform the receiving or sending operation of the EEC in various possible implementation manners of the first aspect, and the processing unit is configured to perform all operations except the receiving and sending operations.

[0100] In a seventh aspect, the present application provides a communication device, applied to an edge enabling server EES, comprising:

[0101] A transceiver unit is configured to receive first indication information from an edge enabling client EEC, where the first indication information is used to indicate at least one of the following: indicating that at least two target EASs cooperate with application context migration; or indicating that service areas of at least two target EASs have a common area, and the at least two target EASs are EASs corresponding to the first application;

[0102] The transceiver unit is further configured to send the first indication information to a first EAS corresponding to the EES, where the at least two target EASs include the first EAS.

[0103] In a possible implementation, the transceiver unit is configured to perform the receiving or sending operation of the EES in various possible implementations of the second aspect, and the processing unit is configured to perform all operations except the receiving and sending operations.

[0104] In an eighth aspect, the present application provides a communication device, applied to an edge configuration server ECS, comprising:

[0105] a transceiver unit configured to receive a first request message, wherein the first request message is used to request information of an edge enabling server EES corresponding to an EAS identifier, where the requested EAS identifier corresponds to the first application;

[0106] The transceiver unit is also used to send a first response message in response to the first request message, and the first response message includes at least one of the following: first indication information, the service area of ​​at least one EES, and the service area of ​​at least one EAS corresponding to at least one EES. The first indication information is used to indicate at least one of the following: used to indicate that at least two target EASs need to coordinate application context migration; or indicate that there is a common area in the service areas of at least two target EASs, and the requested EAS identifier includes the identifier of the at least two target EASs.

[0107] In a possible implementation, the transceiver unit is configured to perform the ECS receiving or sending operation in various possible implementations of the third aspect, and the processing unit is configured to perform all operations except the transceiver operation.

[0108] In a ninth aspect, the present application provides a communication device, applied to a source edge enabling server EES, comprising:

[0109] A transceiver unit, configured to send a first request message to an edge configuration server ECS, wherein the first request message is used to request information of an edge enabling server EES corresponding to an EAS identifier, and the requested EAS identifier corresponds to a first application;

[0110] The transceiver unit is further used to receive a first response message from the ECS, the first response message including at least one of the following information: first indication information, a service area of ​​at least one EES, and a service area of ​​at least one EAS corresponding to at least one EES, the first indication information being used to indicate at least one of the following: used to indicate that at least two target EASs need to coordinate application context migration; or to indicate that there is a common area in the service areas of at least two target EASs, and the requested EAS identifier includes the identifiers of the at least two target EASs.

[0111] In one possible implementation, the transceiver unit is used to perform the receiving or sending operation of the source EES in various possible implementations of the fourth aspect, and the processing unit is used to perform all operations except the transceiver operation.

[0112] In a tenth aspect, the present application provides a communication device, applied to a first edge enabling server EES, comprising:

[0113] a processing unit, configured to determine that a service area of ​​a first target EAS and a service area of ​​a second target EAS have a common area, and that the first EAS and the second EAS correspond to a first application;

[0114] The transceiver unit is used to send first indication information to the second EES, where the first indication information is used to indicate at least one of the following: indicating that the first target EAS and the second target EAS need to coordinate application context migration; or indicating that there is a common area in the service areas of the first target EAS and the second target EAS.

[0115] In one possible implementation, the transceiver unit is used to perform the receiving or sending operation of the first EES in various possible implementations of the fifth aspect, and the processing unit is used to perform all operations except the transceiver operation.

[0116] In an eleventh aspect, an embodiment of the present application provides a communication device, comprising a processor configured to execute the method of any possible implementation of any of the first to fifth aspects. Alternatively, the processor is configured to execute a program stored in a memory, and when the program is executed, the method of any possible implementation of any of the first to fifth aspects is executed.

[0117] In a possible implementation, the memory is located outside the communication device.

[0118] In a possible implementation, the memory is located within the above-mentioned communication device.

[0119] In an embodiment of the present application, the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together.

[0120] In a possible implementation, the communication device further includes a transceiver, where the transceiver is configured to receive a signal or send a signal.

[0121] In a twelfth aspect, an embodiment of the present application provides a communication device, which includes a logic circuit and an interface, wherein the logic circuit and the interface are coupled; the interface is used to receive information, and the logic circuit is used to perform processing operations.

[0122] In the thirteenth aspect, an embodiment of the present application provides a computer-readable storage medium for storing a computer program, which, when run on a computer, enables the method shown in any possible implementation of the first to fifth aspects above to be executed.

[0123] In the fourteenth aspect, an embodiment of the present application provides a computer program product, which includes a computer program or computer code, and when the computer program product is run on a computer, the method shown in any possible implementation of the above-mentioned first to fifth aspects is executed.

[0124] In a fifteenth aspect, an embodiment of the present application provides a computer program. When the computer program is run on a computer, the method shown in any possible implementation of the above-mentioned first to fifth aspects is executed.

[0125] In a sixteenth aspect, an embodiment of the present application provides a communication system, which includes at least two entities among EEC, ECS, EES, and EAS.

[0126] The technical effects achieved in the above-mentioned sixth to sixteenth aspects can refer to the technical effects of the first to fifth aspects or the beneficial effects in the method embodiments shown below, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0127] FIG1 is a schematic diagram of a system architecture provided by an embodiment of the present application;

[0128] FIG2 is a flowchart of an application context migration provided by an embodiment of the present application;

[0129] FIG3 is a schematic diagram of an AC calling multiple EASs according to an embodiment of the present application;

[0130] FIG4 is a schematic diagram of the service area of ​​the EAS provided in an embodiment of the present application;

[0131] FIG5 is a schematic diagram of an ACR collaborative triggering process provided in an embodiment of the present application;

[0132] FIG6a is a flowchart of an information indication method provided by an embodiment of the present application;

[0133] FIG6 b is an example of an information indication method provided by an embodiment of the present application;

[0134] FIG6c is an example of an information indication method provided by an embodiment of the present application;

[0135] FIG6 d is a flowchart of an information indication method provided by an embodiment of the present application;

[0136] FIG6e is an example of an information indication method provided by an embodiment of the present application;

[0137] FIG7a is a flowchart of another information indication method provided by an embodiment of the present application;

[0138] FIG7 b is an example of an information indication method provided by an embodiment of the present application;

[0139] FIG8a is a flowchart of another information indication method provided by an embodiment of the present application;

[0140] FIG8b is an example of an information indication method provided by an embodiment of the present application;

[0141] FIG8c is an example of an information indication method provided by an embodiment of the present application;

[0142] 9 to 11 are schematic structural diagrams of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0143] In order to make the purpose, technical solutions and advantages of this application clearer, this application will be further described below with reference to the accompanying drawings.

[0144] The terms "first" and "second" in the specification, claims, and drawings of this application are used only to distinguish different objects and are not used to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units that are not listed, or may optionally include other steps or units that are inherent to the process, method, product, or device.

[0145] References to "embodiments" herein mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it refer to independent or alternative embodiments that are mutually exclusive of other embodiments. It will be understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0146] In this application, "at least one (item)" means one or more, "more than one" means two or more, "at least two (items)" means two or three and more than three, and "and / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c".

[0147] Please refer to FIG1, which is a schematic diagram of a system architecture provided in an embodiment of the present application. The system architecture of the embodiment of the present application is introduced below in conjunction with FIG1:

[0148] Edge Data Network (EDN): In one possible implementation, an EDN corresponds to a data network, a specialized local data network (local DN) that includes edge-enabling capabilities and can be identified using a Data Network Access Identifier (DNAI) and a DNN. The EDN is a network logical concept. Another understanding of the EDN is that it is a peer-to-peer concept of the central cloud, and can be understood as a local data center (geographically identified), identified using a DNAI, and can include multiple local data networks (local DNs).

[0149] Application Instance / Edge Application Server (EAS): EAS is an application deployed in the edge data network, called an application instance. Specifically, it refers to a server application, such as social media software, augmented reality (AR), and virtual reality (VR), deployed and running on an EDN. An application can deploy one or more EASs in one or more EDNs. EASs deployed and running in different EDNs can be considered different EASs of the same application. They can share a domain name, use a single IP address, or use different IP addresses. EAS can also be called edge application (server), application instance, edge application instance, Multi-Access Edge Computing (MEC), EAS function, etc.

[0150] Application client (AC): The AC is the UE-side counterpart of edge applications. The AC allows users to access application services from the application server. The application client is a client program running on the terminal. It can connect to application servers in the cloud or to EAS deployed and running in one or more EDNs.

[0151] Edge Enabler Server (EES): EES can provide some enabling capabilities for application instances deployed in EDN, and can better support the deployment of applications in MEC. It can support the registration of edge applications, authentication and authorization of UE, and provide UE with IP address information of application instances. It can further support obtaining the identification and IP address information of application instances, and further send the identification and IP address information of application instances to the edge data network configuration server. EES is deployed in EDN. Generally, 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, or the EES is called the EES corresponding to the EAS. The EES controls / manages the EAS registered / configured on the EES.

[0152] Edge Enabler Client (EEC): The EEC is the UE-side counterpart of the EES. The EEC registers EEC information and application client information with the EES, performs security authentication and authorization, obtains the EAS IP address from the EES, and provides edge computing capabilities to the application client. For example, the EAS discovery service returns the EAS IP address to the application client.

[0153] Edge Configuration Server (ECS): The ECS is responsible for EDN configuration, such as providing EES information to the UE. It can also directly provide application instance information to the UE and interact with the application's DNS to obtain application instance information. It further obtains and stores application instance and IP address information from other functional entities.

[0154] Application users sign a service agreement with the application provider, which provides the service. Application users log in to the AC on their terminals and communicate with the EAS through the AC's connection. The EEC is a middleware layer, typically located within the operating system or between the AC and the operating system. The AC can access edge-enabling services from the EEC via an application programming interface (API).

[0155] It should be understood that the various network elements shown in the terminology of this application can be physical concepts, for example, it can be a single device physically, or at least two network elements can be integrated on the same physical device, or the network elements shown in this article can also be logical concepts, such as software modules or network functions corresponding to the services provided by each network element. The network function can be understood as a virtualization function under virtualization implementation, and can also be understood as a network function that provides services under a service-oriented architecture.

[0156] Before introducing the method embodiments of the present application, the conceptual terms involved in the present application are introduced.

[0157] 1. Application Context Migration (ACR)

[0158] Please refer to FIG2, which is a schematic diagram of a process flow of application context migration provided in an embodiment of the present application. The application context migration of an embodiment of the present application will be described below in conjunction with FIG2:

[0159] 101, Detection of application context migration.

[0160] The detection of application context migration is to determine whether context migration may be required. At this time, the detection entity usually detects some events, such as: a change in the location of the terminal device, an update of the user plane path of the terminal device, etc.

[0161] 102,Decision on Application Context Migration.

[0162] The decision-making entity determines that an application context migration is required.

[0163] 103, execution of application context migration.

[0164] This primarily involves transferring the AC's context information from the source EAS to the predicted EAS or the EAS to which the AC has already moved. This step may also include sending information to the terminal device informing it of the predicted EAS. Information regarding the completion of the context transfer and the predicted EAS, such as the address of the predicted EAS and routing information corresponding to the predicted EAS, may also be sent to the network device. For ease of description, the predicted EAS or the EAS to which the AC has already moved is referred to as the target EAS.

[0165] It should be noted that before performing application context migration, the target EES must be discovered. This process always follows a two-level discovery mechanism, that is, first discovering the EES, and then discovering the EAS from the EES. The EES discovery process and the EAS discovery process can be referred to the description of the subsequent embodiments and will not be repeated here. In some embodiments, the identifier of the target EAS (i.e., the EAS ID) can be the same as the identifier of the source EAS.

[0166] As an example and not a limitation, when the location of a terminal device changes, the detection entity that applies context migration predicts that the EAS of the terminal device will change, and can send the context information of the terminal device from the source EAS to the predicted target EAS in advance, thereby avoiding service interruption caused by context migration after the terminal device moves to the target EAS.

[0167] As an example and not a limitation, when the user plane path of the terminal device changes, the terminal device has been disconnected from the source EAS and connected to the target EAS. The application context migration detection entity determines that the EAS of the terminal device has changed and sends the context information of the source EAS to the target EAS. Since the application context migration is performed after the terminal device is switched, it will cause service interruption.

[0168] 104, clean up after application context migration.

[0169] This step involves multiple entities. For example, the application client initiates a new socket connection to the target EAS.

[0170] 2. EES discovery process and EAS discovery process

[0171] Step 1: The EEC of the terminal device discovers the EES from the ECS (i.e., the EES discovery process).

[0172] 1. The EEC requests or subscribes to the EES platform corresponding to the terminal device location from the ECS. The EEC discovers the EES-enabled platform or EDN of interest from the ECS.

[0173] 2. Detailed information about EAS is registered on the ECS. The DNAI is obtained based on the location of the terminal device. The DNAI, the fully qualified domain name (FQDN), and the EES configuration file filter are combined to select the appropriate EES for each AC. The terminal device location is taken into consideration when selecting the EES.

[0174] 3. Obtain current or potential DNAI.

[0175] 4. The EEC obtains information about one or more EESs from the ECS.

[0176] Step 2: EEC discovers EAS from EES (ie, EAS discovery process).

[0177] 1. The EEC sends an EAS discovery request message to the EES. The EAS discovery request message includes the EEC ID and security credentials, and may include an EAS discovery filter parameter to retrieve information about a specific EAS or a specific type of EAS (such as a gaming application).

[0178] 2. EES matches the registered AC information. Based on the information of locally registered or online EASs and the discovery filter parameters provided by the user, EES matches the EAS that meets the user's request. If multiple EASs meet the requirements, multiple EASs can be returned.

[0179] 3. The EES returns the EAS information to the EEC, which can then provide it to the AC for the AC to connect to the EAS.

[0180] 3. Bundle EAS

[0181] Bundle EAS means that an AC can call multiple EASs (i.e., bundle EASs) to obtain the required services. Based on the needs of the AC, the AC determines whether at least one EAS in the bundle EAS needs to perform application context migration together (also known as collaborative application context migration) when an application context migration event occurs, and / or whether it needs to provide the same service KPI (such as latency, connection bandwidth, response time, request rate, etc.), or determines whether to perform collaborative application context migration based on whether the EASs in the bundle EAS provide the same service KPI. For example, the EASs in the bundle EAS called by an AC that need to provide the same or the same range of service KPIs can be regarded as EASs that need to perform application context migration together.

[0182] As shown in Figure 3, the AC can invoke EAS1, EAS2, and EAS3. If the service KPIs required by the AC for EAS1 and EAS2 are the same or within the same range, EAS1 and EAS2 are considered EASs requiring application context migration together. When EAS1 and EAS2 are deployed in different EDNs, the EAS service areas are different. As shown in Figure 4, the dotted circle represents the service area of ​​EAS1, and the solid circle represents the service area of ​​EAS2. The intersection of the dotted and solid circles represents the common area of ​​the service areas of EAS1 and EAS2.

[0183] When a UE is located in the common service area of ​​EAS1 and EAS2, it can obtain the same service KPI or the same range of service KPIs. In this case, EAS1 and EAS2 can apply context migration together. For example, as shown in Figure 4, when the UE is located in position A, the UE can obtain the same service KPI from EAS1 and EAS2. When the UE is located in position B, the UE cannot obtain the same service KPI. Exemplarily, the service KPI provided by EAS1 to the UE in the service area of ​​EAS1 is the same as the service KPI provided by EAS2 to the UE in the service area of ​​EAS2. When the UE is in a common area, it can obtain the same service KPI from EAS1 and EAS2.

[0184] In the following embodiments, the EAS IDs of multiple EASs invoked by an AC are referred to as bundle EAS IDs.

[0185] 4. Collaborative Application Context Migration

[0186] In the embodiment of the present application, "collaborative application context migration" and "apply context migration together" can be interchanged. The at least two EASs that need to collaborate in application context migration can be understood as when one of the EASs has a need for application context migration, the at least two EASs need to perform application context migration. In the embodiment of the present application, the at least two EASs that need to collaborate in application context migration are the bundle EAS corresponding to an application (i.e., an AC). Exemplarily, the at least two EASs that need to collaborate in application context migration may be some or all of the EASs in the bundle EAS, which is not limited in the present application.

[0187] In the scenario of bundle EAS performing application context migration, the source EAS can be referred to as bundle S-EAS, the source EES can be referred to as bundle S-EES, the target EAS can be referred to as bundle T-EAS, and the target EES can be referred to as bundle T-EES.

[0188] The following is a flowchart of an application context migration in an embodiment of the present application, described in conjunction with Figure 5. When the application context migration is triggered or executed by the network side (source S-EES, source S-EAS), the target EAS (i.e., T-EAS) discovery process is correspondingly also triggered by S-EES, S-EAS. The following example illustrates this, and in Figure 5, bundle EAS includes EAS1 and EAS2 as an example.

[0189] 1. ACR detection: For example, S-EAS1 or S-EES1 may detect that an ACR is required.

[0190] 2. S-EAS1 sends an ACR request to S-EES1. The ACR request includes the bundle EAS ID. In response, S-EES1 sends an ACR request to S-EES2.

[0191] 3. S-EES2 exchanges ACR requests with S-EAS2.

[0192] 4. S-EES2 sends an ACR response to S-EES1. In response, S-EES1 sends an ACR response to S-EAS1.

[0193] 5. S-EAS1 sends an EAS discovery request to S-EES1. S-EAS2 sends an EAS discovery request to S-EES2.

[0194] 6. S-EES1 obtains T-EES from ECS.

[0195] 7. S-EES1 sends a target EHE announcement request to S-EES2. The target EHE announcement request is used to send the selected data center information.

[0196] 8. S-EES2 sends a target EHE announcement response to S-EES1. The target EHE announcement response is used to confirm the selected data center information.

[0197] Perform steps 7 and 8 to allow S-EES1 and S-EES2 to select T-EES in the same data center.

[0198] 9. S-EES1 obtains T-EES from ECS.

[0199] 10. T-EAS discovery: S-EES1 and S-EES2 discover T-EAS from the selected T-EES.

[0200] 11. EAS discovery response.

[0201] 12. Application context transfer.

[0202] In some embodiments, steps 2-4 and 7-8 above may be optional steps. If steps 2-4 and 7-8 are not performed, S-EES1 discovers all bundle T-EASs and bundle T-EESs (bundle T-EASs and bundle T-EESs are in the same EDN, or DNAI, or data center), and S-EES1 notifies the corresponding S-EES of the selected bundle T-EAS and bundle T-EES information. In this way, the selected bundle T-EESs and bundle T-EASs may also belong to the same data center.

[0203] As can be seen from the flowchart shown in Figure 5, when the bundle EAS to which the UE is connected does not have a common service area, the bundle EAS to which the UE is connected does not need to perform ACR together. Therefore, whether the bundle EAS needs to perform ACR together needs to be determined based on whether the bundle EAS has a common service area. If the bundle EAS no longer has a common service area, EAS1 and EAS2 do not need to be migrated at the same time, that is, steps 2-4 and steps 7-8 in Figure 5 do not need to be executed, that is, the ACR of EAS1 and EAS2 can be triggered separately based on demand. Therefore, using the ACR migration process shown in Figure 5 may result in unnecessary ACR collaborative triggering processes (i.e., steps 2-4 and steps 7-8).

[0204] In order to avoid unnecessary ACR collaborative triggering process in the ACR process shown in Figure 5, in an embodiment of the present application, if the bundle EAS has a common area, an indication information is sent to indicate that there is a common area for at least two target EASs in the bundle EAS, so as to determine whether context migration needs to be applied together in subsequent ACR, thereby avoiding unnecessary ACR collaborative triggering process.

[0205] The following describes the information indication method in the embodiments of the present application. It should be noted that the various technical solutions (or embodiments) of the present application can be implemented independently or in combination based on certain internal connections. This application is not limited thereto. Furthermore, the various terms and definitions between the various embodiments can be referenced to each other. In each embodiment of the present application, different implementation methods can also be implemented in combination or independently.

[0206] It should be noted that the EEC in this application is an entity on the terminal device. In this application, the EEC and the terminal device can be replaced with each other without limitation.

[0207] Please refer to Figure 6a, which is a flowchart of an information indication method provided in an embodiment of the present application. The information indication method shown in Figure 6a includes but is not limited to the following steps. It is understood that the following steps are for example only, and the information indication method may also include some of the following steps, but not all of them. This application does not limit this. It should be noted that the following steps are not limited to the order in which they are executed.

[0208] 201. The EEC sends a first request message to the ECS. The first request message may be used to request information about an EES corresponding to an EAS ID. The requested EAS IDs may include at least two EAS IDs corresponding to a first application. In some implementations, the requested EAS IDs may also include other requested EAS IDs.

[0209] In the embodiment of the present application, the EEC may be included in a terminal device. In addition to the EEC, the terminal device may also include a first application, which may also be called an AC.

[0210] Exemplarily, the first request message may be a service provisioning request message, and the specific bearer message is not limited. The first request message may include at least two EAS IDs corresponding to the first application. For ease of description, this application refers to the at least two EAS IDs corresponding to the first application included in the first request message as n EAS IDs, where n is an integer greater than or equal to 2. In some embodiments, the n EAS IDs may be all EAS IDs in the bundle EAS ID corresponding to the first application. For example, the bundle EAS ID includes m EAS IDs, where m is equal to n, and m is an integer greater than or equal to 2. In some embodiments, the n EAS IDs may be part of the EAS IDs in the bundle EAS ID corresponding to the first application, that is, n is less than m. For example, the first application has the same service KPIs for the n EASs corresponding to the n EAS IDs, or some parameters in the service KPIs are the same, or the service KPI levels are similar (for example, the first application has the same service KPIs for the n EASs corresponding to the n EAS IDs), etc. In some implementations, the n EAS IDs to which context migration needs to be applied together and included in the first request message may be configured in the AC.

[0211] In an embodiment of the present application, if the terminal device is located in a common area of ​​the service areas of at least two EASs corresponding to the at least two EAS IDs, the same service KPI or similar service KPI level can be obtained. It can be understood that the at least two EASs have similar service KPIs or similar service KPI levels in their respective service areas.

[0212] In some embodiments, the first request message may also include the service KPIs required by the first application for each of the n EAS IDs. The service KPIs may include, but are not limited to, connection bandwidth, request rate, response time, compute availability, graphical compute, memory, storage, latency, etc.

[0213] 202 , the ECS determines at least one EES.

[0214] Among them, step 202 is an optional step.

[0215] In a first possible implementation, the ECS may determine at least one EES based on the service area of ​​the EES managed / corresponding to the ECS or the service area of ​​the EAS. In the at least one EES, the service areas of at least two EASs have a common area. For ease of description, in the embodiment of the present application, the number of EASs with a common area is defined as p, where p is an integer greater than or equal to 2, and p is an integer less than or equal to n. The n EAS IDs mentioned above include the p EAS IDs. The EES managed by the ECS may be understood as the EES registered on the ECS, the EAS managed by the ECS may be understood as the EAS corresponding to the EES registered on the ECS, and the EAS corresponding to the EES may be understood as the EAS registered on the EES.

[0216] Method 1: Based on the service area of ​​the EAS, the service areas of the p EASs corresponding to the p EAS IDs have a common area. It is understood that if p is less than n, then the np EAS IDs that do not have a common area can trigger application context migration based on demand.

[0217] For example, the ECS determines at least one EES based on the service areas of each EAS registered on the EES managed by the ECS, to ensure that the service areas of the p EASs corresponding to the p EAS IDs in the determined at least one EES have a common area.

[0218] Method 2: Among the at least one EES determined based on the service area of ​​the EES, the service area of ​​the at least one EES has a common area. For example, the ECS determines at least one EES based on the service area of ​​the EES managed by the ECS to ensure that the service area of ​​the at least one EES determined has a common area. Exemplarily, the service area of ​​the EES may be the same as the service area of ​​the EAS registered on the EES. In other words, if the service area of ​​the at least one EES mentioned above has a common area, then the service areas of the p EASs corresponding to the p EAS IDs registered on the at least one EES have a common area. Exemplarily, the service area of ​​the EES may also be different from the service area of ​​the EAS registered on the EES. In this case, the EEC needs to further determine, based on the service area of ​​the EAS registered on the at least one EES, whether the service areas of the p target EASs corresponding to the p EAS IDs have a common area. The way for the EEC to obtain the service area of ​​the EAS registered on the at least one EES may be that the ECS sends it to the EEC, or the EEC may obtain the service area of ​​the EAS from the corresponding EES through the EAS discovery process. This is not limited in this application.

[0219] In a second possible implementation, the ECS may determine at least one EES. The specific selection process may refer to the EES discovery process in the aforementioned embodiment.

[0220] 203. ECS sends a first response message to EEC, wherein the first response message may include at least one of the following: second indication information, a service area of ​​at least one EES, and a service area of ​​at least one EAS corresponding to at least one EES; the above-mentioned second indication information may be used to indicate that in at least one EES, the service areas of at least two EASs have a common area.

[0221] Exemplarily, the first response message includes information of at least one EES determined by the ECS.

[0222] If at least one EES is determined in step 202 using the first possible implementation method, that is, at least one EES is determined based on the service area of ​​the EES or the service area of ​​the EAS to ensure that the service areas of the p EASs in the at least one EES have a common area, then the first response message may include second indication information, used to indicate at least one of the following: in the determined at least one EES, the service areas of the p EASs corresponding to the above-mentioned p EAS IDs have a common area; or the p EASs corresponding to the above-mentioned p EAS IDs need to perform application context migration together or collaboratively perform application context migration.

[0223] If the second possible implementation method is adopted in step 202 to determine at least one EES, that is, at least one EES is determined through the EES discovery process (that is, the EES is not determined based on the service area of ​​the EES and / or the service area of ​​the EAS), the ECS sends a first response message, which includes the service area of ​​at least one EAS corresponding to the at least one EES or includes the service areas corresponding to the at least one EES respectively.

[0224] Exemplarily, the first response message may include the service areas corresponding to at least one EAS ID. In some embodiments, the at least one EAS ID may be the service areas of all EASs registered on the EES, or may be the n EAS IDs included in the first request message, which is not limited in this application. The EEC may determine the EES based on the service area of ​​at least one EAS corresponding to the at least one EES to ensure that the service areas of at least two EASs have a common area.

[0225] In a third possible implementation, the first response message may include the service areas corresponding to the at least one EES. The EEC selects an EES with a public area based on the service areas corresponding to the at least one EES. In this implementation, the service area of ​​the EES may be the same as or different from the service area of ​​the EAS registered on the EES, and this application does not limit this.

[0226] Exemplarily, the first response message may be a service provisioning response message, and the specific bearer message is not limited.

[0227] 204. The EEC determines that there is a common area between the service areas of at least two EASs.

[0228] Among them, step 204 is an optional step.

[0229] In some embodiments, for ease of description, this application refers to the at least two EASs with a common area as p EASs. The EEC receives the first response message and, based on the first response message, determines that a common area exists within the service areas of the p EASs. It should be noted that the number p of EASs with a common area may be the same as or different from the number n of EAS IDs requested in the first request message, and this application does not impose any limitation thereon.

[0230] In a possible implementation, the first response message includes the second indication information, and the EEC may determine, based on the second indication information, that a common area exists among the service areas of the p EASs.

[0231] In one possible implementation, the first response message includes the service area of ​​at least one EAS corresponding to at least one EES. The EEC can determine at least one EES based on the service area of ​​at least one EAS corresponding to the at least one EES, and on the determined at least one EES, there is a common area among the service areas of p EASs.

[0232] In one possible implementation, the first response message includes the service areas corresponding to the at least one EES, and the EEC determines the EES with a common area based on the service areas corresponding to the at least one EES. For example, if the service area of ​​the EES is the same as the service area of ​​the EAS registered on the EES, it is guaranteed that the service areas of the p EASs on the EES with a common area exist in a common area. If the service area of ​​the EES is different from the service area of ​​the EAS registered on the EES, the EEC may further obtain the service area of ​​the EAS from the determined EES, thereby determining that the service areas of the p EASs have a common area.

[0233] 205 , the EEC sends an EAS discovery request message to the EES.

[0234] In some embodiments, the EEC may send an EAS discovery request message to the determined EES. The EAS discovery request message may include EAS information. For example, the EAS information may include but is not limited to EAS ID, EAS FQDN, and other information.

[0235] In some implementations, the EES may be an EES among at least one EES determined by the EEC.

[0236] 206 , the EES sends an EAS discovery response message to the EEC.

[0237] The EAS discovery response message may include information about the EAS corresponding to the EAS ID in the EES, for example, may include a service area of ​​the EAS.

[0238] In some embodiments, the EEC may determine, based on the service area of ​​the EAS in the EAS discovery response message, that there are p EASs in a common area in the service area of ​​the EAS.

[0239] 207. The EEC sends first instruction information to the EES.

[0240] After the EEC determines the EES, it can discover the p EASs corresponding to the p EAS IDs from the EES. The EEC can further send a first indication message to the EES, where the first indication message indicates at least one of the following: that the p EASs need to coordinate application context migration; or that the service areas of the p EASs have a common area. The request message also includes information about the EAS ID selected by the EEC.

[0241] Illustratively, the first indication information may be carried in a Selected EAS announcement request message. Furthermore, the Selected EAS announcement request message may include information about the public area. For example, the Selected EAS announcement request message may include a correspondence between the identifiers of the p EASs and the public area, indicating that the p EASs have a public area. It is understood that the message carrying the first indication information is not limited and may also be carried in other messages.

[0242] 208. The EES sends first instruction information to the EAS.

[0243] Step 207 is an optional step.

[0244] The EES may further send the above-mentioned first indication information to the EAS, which is the EAS among the above-mentioned p EASs. The first indication information may be carried in the EAS selected subscription notification message Selected EAS subscription notification, or may be carried in other messages, without limitation to the carried message. Furthermore, the EAS selected subscription notification message may also carry information about the public area. For example, the EAS selected subscription notification message includes the correspondence between the identifiers of the p EASs and the public area, and the correspondence is used to indicate that the at least two EASs have a public area. When the subsequent terminal device moves out of the public area, it is necessary to trigger the application context migration. In other words, the condition for application context migration is added with "determining whether to move out of the public area". When it is subsequently determined that application context migration is required, the p EASs and the EESs corresponding to the p EASs may be cooperatively triggered. For details, please refer to the process shown in Figure 5.

[0245] In an embodiment of the present application, when the EEC determines that there is a common area in the service areas of at least two EASs, it sends a first indication message to indicate that the at least two EASs need to collaboratively trigger ACR subsequently, thereby avoiding the signaling waste caused by the ACR collaborative triggering process in a scenario where there is no common area for at least two EASs (i.e., a scenario where collaborative triggering is not required).

[0246] The following illustrates Figure 6a with reference to Figures 6b and 6c. In Figure 6b, the EEC determines the presence of at least two EASs in a public area. In Figure 6c, the ECS determines the presence of at least two EASs in a public area. In Figures 6b and 6c, the first request message is a service provisioning request, and the first application is an AC.

[0247] As shown in FIG6b , an example of an information indication method provided in an embodiment of the present application is provided. As shown in FIG6b , the information indication method includes but is not limited to the following steps. It is understood that the information indication method may include some, but not all, of the steps in FIG6b . For example, it may include only step 303. The following is explained in conjunction with FIG6b :

[0248] 301. EAS1 sends a subscription request to EES1. The subscription request is used to subscribe to the bundle EAS in which EAS1 is selected as the first application.

[0249] The subscription request Selected EAS subscription request (EAS) is mainly used for EES1 to subsequently notify EAS1 whether application context migration is required.

[0250] 302. EES1 sends a subscription response to EAS1. The subscription response is used to indicate whether the subscription is successful or failed.

[0251] The subscription response Selected EAS subscription response may include indication information for indicating whether the subscription is successful or failed.

[0252] 303. EES1 sends an EES registration request to ECS.

[0253] The EES registration request carries the EAS ID and the service area corresponding to the EAS. For example, the EES registration request may also carry the service KPIs that the EAS can provide (e.g., latency information that the EAS can provide in its service area). The corresponding ECS ​​sends an EES registration response message to the EES, carrying an indication of whether the subscription is successful or unsuccessful.

[0254] Among them, the EAS ID carried in the above-mentioned EES registration request EES registration request can be the EAS registered on the EES. It should be noted that it can also be called the EAS managed by the EES, or the EAS associated with the EES, or the EAS corresponding to the EES, etc. In the embodiment of the present application, the four naming methods are interchangeable.

[0255] 304. EEC sends a service activation request to ECS.

[0256] The service provisioning request message carries the AC profile and the information of the bundle EAS required by the AC. The information of the bundle EAS required by the AC may also be carried in the AC profile. The information of the bundle EAS may, for example, include the EAS ID information of each EAS in the bundle EAS. Exemplarily, the information of the bundle EAS may also carry the service KPI required by the AC. When the EEC / AC requires the same service KPI for at least one EAS in the bundle EAS, or certain parameters in the service KPI are the same, or the KPI levels are similar, the EEC / AC may regard at least two EASs with the same or similar service KPIs as EASs that need to migrate application contexts together. In some embodiments, the AC may configure the information of the bundle EASs that need to collaborate in application context migration in the AC based on the service KPI requirements of the bundle EAS. When the service areas of the at least two EASs have a common area, the UE can obtain the same or similar service KPIs in the common area of ​​the at least two EASs.

[0257] For example, the AC requires an EAS bundle that includes EAS1, EAS2, and EAS3. The AC sets the same or similar service KPIs for EAS1 and EAS2. The EEC / AC determines that context migration is best applied to EAS1 and EAS2, and that the terminal device can obtain similar or identical service KPIs for EAS1 and EAS2 in the common service area of ​​EAS1 and EAS2. In this embodiment, the EEC / AC determines that at least one corresponding EES must be selected to ensure that EAS1 and EAS2 are registered on at least one EES and that the common service area exists for EAS1 and EAS2.

[0258] 305 , the ECS sends a service activation response, where the service activation response includes the service area of ​​the EAS or the service area of ​​the EES.

[0259] The service provisioning response carries information about at least one EES.

[0260] In a first implementation, the service activation response may include the EAS service area, for example, a correspondence between the EAS ID and the service area of ​​the corresponding EAS, i.e., the service area of ​​the EAS registered or managed on the EES. Exemplarily, the service activation response may also include the EES service area. Exemplarily, the ECS may also send service KPI information that the EAS can provide within the EAS service area.

[0261] In a second implementation manner, the service activation response may include the service area of ​​the EES, and illustratively, may further include indication information for indicating that the service area of ​​the EES is the same as the service area of ​​the EAS corresponding to the EES.

[0262] 306, EEC determines EES.

[0263] If the service provisioning response includes the information described in the first implementation in step 305, the EEC can determine the EES based on the service area of ​​the EAS corresponding to the at least one EES to ensure that the service area of ​​the requested EAS bundle exists in common. For example, the determined EESs include EES1 and EES2, and the requested EAS bundle includes EAS1 and EAS2. In other words, EAS1 registered with EES1 and EAS2 registered with EES2 exist in common.

[0264] If the service provisioning response includes the information in the second implementation in step 305 , the EEC may determine that the service area of ​​at least one EES is in a public area, thereby ensuring that the service area of ​​the bundle EAS registered on the at least one EES is in a public area.

[0265] For example, in this embodiment, the determined EES includes EES1 and EES2. EAS1 is registered on EES1, and EAS2 is registered on EES2. EAS1 and EAS2 are bundle EAS. If the service areas of EES1 and EES2 have a common area, then the service areas of EAS1 and EAS2 have a common area.

[0266] In some implementations, if the service activation response includes the service area of ​​the EES, and the service area of ​​the EES is different from the service area of ​​the EAS registered on the EES, the EEC may determine that there is at least one EES with a common service area, and obtain the service area of ​​the EAS from the at least one EES with a common service area (for example, the service area of ​​the EAS may be obtained through the EAS discovery process of steps 307 and 308), thereby determining that there is a common service area in the bundle EAS based on the service areas of the EAS corresponding to the at least one EES.

[0267] 307, EEC sends an EAS discovery request.

[0268] The EAS discovery request message EAS discovery response carries information about the bundle EAS, such as the EAS ID of each EAS, and optionally carries required EAS service KPIs, etc. It is understood that the EEC can send an EAS discovery request message to EES1 and send an EAS discovery request message to EES2.

[0269] 308 , EES1 sends an EAS discovery response.

[0270] The EAS Discovery Response message carries information about the discovered EAS, namely the EAS profile. The EAS profile includes at least one of the following: the EAS Geographical Service Area, the EAS Topological Service Area, and the EAS DNAI, which can be used to indicate the EAS location. It is understood that EES2 can also send an EAS Discovery Response to the EEC.

[0271] 309. The EEC determines, based on the service areas of the EASs, that at least two EASs have a common area.

[0272] If it is not determined whether the EASs have a common area in step 306 , it may be determined in step 309 whether the service areas of at least two EASs have a common area.

[0273] The EEC may determine whether at least two EASs have a common area based on the service area corresponding to each EAS in the bundle EAS received in step 308 .

[0274] If at least two EASs have a common area, the at least two EASs need to apply context migration together.

[0275] 310. The EEC sends a request message, where the request message includes first indication information, where the first indication information is used to indicate at least one of the following: service areas of at least two EASs have a common area; or at least two EASs need to coordinate application context migration.

[0276] EEC sends a request message to EES1 and EES2 (i.e., the EES corresponding to EAS1 and EAS2 in the public area respectively). The request message carries AC ID, EAS ID, and application context coordination indication, such as ACR coordinate required (i.e., the first indication information) or no requirement for ACR coordinate.

[0277] In some embodiments, the request message may indicate that the bundle EAS needs to apply context migration together (i.e., the first indication information is used to indicate that the bundle EAS needs to apply context migration together). In some embodiments, the request message includes at least two EAS IDs in which a public service area exists. Exemplarily, the request message may also include a public area. Further, the request message may include a correspondence between the public area and the at least two EAS IDs, i.e., at least two EASs corresponding to the at least two EAS IDs have a common area.

[0278] 311. EES1 sends a notification message to EAS1, where the notification message includes first indication information.

[0279] EES1 sends a notification message Selected EAS subscription notification, which carries an AC ID and an application context coordination indication, such as ACR coordinate required (i.e., the first indication information) or no requirement for ACR coordinate. In some embodiments, the notification message may also indicate that the bundle EAS needs to apply context migration together (i.e., the first indication information is used to indicate that the bundle EAS needs to apply context migration together). In some embodiments, the notification message includes at least two EAS IDs in which a public service area exists. Exemplarily, the notification message may also include a public area. Further, the notification message may include a correspondence between a public area and at least two EAS IDs, that is, at least two EASs corresponding to the at least two EAS IDs have a public area.

[0280] It is understandable that EES2 may also send a notification message to EAS2, where the notification message includes the first indication information.

[0281] 312. EES1 sends a response message to EEC. The response message is used to indicate success or failure.

[0282] The response message may include information indicating whether notification to the corresponding EAS is successful or failed.

[0283] It is understandable that EES2 may also send a response message to EEC.

[0284] FIG6c is an example of an information indication method provided in an embodiment of the present application. As shown in FIG6c , the information indication method includes but is not limited to the following steps. It is understood that the information indication method may include some, but not all, of the steps in FIG6c . The following is described in conjunction with FIG6c :

[0285] 401 : Send a subscription request, where the subscription request is used to subscribe to the bundle EAS in which EAS1 is selected as the first application.

[0286] 402: Send a subscription response, which is used to indicate whether the subscription is successful or failed.

[0287] 403. EES1 sends an EES registration request, wherein the EES registration request includes the EAS ID registered on EES1.

[0288] 404: EEC sends a service activation request to ECS.

[0289] For step 404 in the embodiment of the present application, please refer to step 304 in the embodiment shown in FIG6 b , which will not be described in detail here.

[0290] 405 , the ECS determines at least one EES according to the service area of ​​the EES or the service area of ​​the EAS.

[0291] The ECS may determine at least one EES according to the service areas of the EESs or EASs managed / corresponding to the ECS, wherein service areas of at least two EASs have a common area in the at least one EES.

[0292] In one implementation, the ECS determines at least one EES based on the service areas of each EAS registered on the EES managed by the ECS, to ensure that the service areas of the bundle EAS have a common area.

[0293] In another implementation, the service area of ​​at least one EES determined by the ECS based on the service area of ​​the EES has a common area. The service area of ​​the EES may be the same as the service area of ​​the corresponding EAS. If the service area of ​​the at least one EES has a common area, then the service area of ​​the bundle EAS registered on the at least one EES has a common area.

[0294] 406 , the ECS sends a service activation response to the EEC, where the service activation response includes information of at least one EES.

[0295] In the embodiment of the present application, it is taken as an example that the at least one EES includes EES1 and EES2.

[0296] 407, EEC sends an EAS discovery request to EES1. Similarly, EEC sends an EAS discovery request to EES2.

[0297] 408. EES1 sends an EAS discovery response to EEC. Similarly, EES2 sends an EAS discovery response to EEC.

[0298] For steps 407-408 of the embodiment of the present application, please refer to steps 307-308 of the embodiment shown in Figure 6b, and will not be repeated here.

[0299] 409 , the EEC sends a request message to EES1 and EES2 respectively, where the request message includes the first indication information.

[0300] 410. EES1 sends a notification message to EAS1, where the notification message includes first indication information.

[0301] 411. EES1 and EES2 send response messages to EEC respectively.

[0302] Please refer to steps 409-411 of the embodiment of this application for steps 310-312 of the embodiment shown in Figure 6b, and will not be repeated here.

[0303] It should be noted that the contents of the embodiment of FIG. 6 c and the embodiment of FIG. 6 b can be referenced to each other.

[0304] Please refer to Figure 6d, which is a flowchart of an information indication method provided in an embodiment of the present application. The information indication method shown in Figure 6d includes but is not limited to the following steps. It is understood that the following steps are for example only, and the information indication method may also include some of the following steps, but not all of them. This application does not limit this. It should be noted that the following steps are not limited to the order in which they are executed.

[0305] 501. The EEC sends a first request message to the EES. The first request message is used to request to obtain at least two EASs corresponding to at least two EAS IDs.

[0306] Exemplarily, the first request message may be an EAS discovery request. The first request message includes at least two EAS IDs. The at least two EAS IDs correspond to the first application. For ease of description, this application refers to the at least two EAS IDs corresponding to the first application included in the first request message as n EAS IDs. For a description of the n EAS IDs, reference can be made to the description of the embodiment shown in FIG. 6a , and further details are omitted here. The first request message may also include service KPIs required by the first application for each of the n EAS IDs.

[0307] 502. The EES determines, based on service areas of at least two EASs, that the service areas of the at least two EASs have a common area.

[0308] In some embodiments, the EES may determine that the service areas of the p EASs corresponding to the p EASs among the n EAS IDs have a common area based on the service areas of the EASs registered on the EES, where p is an integer greater than or equal to 2 and less than or equal to n.

[0309] 503. The EES sends information of at least two EASs and first indication information to the EEC. The first indication information is used to indicate at least one of the following: indicating that the at least two EASs need to coordinate application context migration; or indicating that service areas of the at least two EASs have a common area.

[0310] In some embodiments, the EES sends information about the at least two EASs identified and the first indication information to the EEC. In some implementations, the EES may also send the public area to the EEC. In some implementations, the EES sends the EEC the p EAS IDs where the public area exists, indicating that the service areas of the p EASs corresponding to the p EAS IDs contain the public area. For example, the EES may send a correspondence between the p EAS IDs and the public area. The information about the at least two EASs and the first indication information may be included in an EAS discovery response message.

[0311] 504. The EES sends first indication information to the EAS.

[0312] The EES may also send first indication information to the corresponding EAS. For a detailed description of the first indication information, refer to the description of step 503 and are not repeated here. The EES may also send the public area to the EAS. In some implementations, the EES sends the p EAS IDs where the public area exists to the EAS, indicating that the service areas of the p EASs corresponding to the p EAS IDs contain the public area. For example, the correspondence between the p EAS IDs and the public area may be sent.

[0313] 6e is used as an example to illustrate FIG6d. In FIG6d , the first request message is an EAS discovery request, and the first application is AC as an example.

[0314] FIG6e shows an example of an information indication method provided in an embodiment of the present application. As shown in FIG6e , the information indication method includes but is not limited to the following steps. It is understood that the information indication method may include some, but not all, of the steps in FIG6e . The following is described in conjunction with FIG6e :

[0315] 601 , sending a subscription request, where the subscription request is used to subscribe to the bundle EAS where the EAS is selected as the first application.

[0316] 602. Send a subscription response, where the subscription response is used to indicate whether the subscription is successful or failed.

[0317] 603. The EES sends an EES registration request to the ECS, wherein the EES registration request includes the EAS ID registered on the EES1.

[0318] 604. The EEC sends a service activation request to the ECS.

[0319] For step 604 in the embodiment of the present application, please refer to step 304 in the embodiment shown in FIG6 b , which will not be described in detail here.

[0320] 605 , the ECS sends a service activation response to the EEC, where the service activation response includes information of at least one EES.

[0321] The ECS may determine at least one EES through an EES discovery process. For details about the EES discovery process, please refer to the description of the aforementioned embodiment, which will not be repeated here.

[0322] 606. The EEC sends an EAS discovery request to the EES. The EAS discovery request includes bundle EAS information. The bundle EAS information includes a bundle EAS ID. The bundle EAS ID includes at least two EAS IDs. For ease of description, the bundle EAS ID may include n EAS IDs.

[0323] 607 , the EES determines that the service areas of at least two EASs have a common area.

[0324] The EES can determine at least two EASs in the bundle EAS that have a common area based on the service areas of the EASs registered on the EES. For ease of description, the at least two EASs in the bundle EAS that have a common area in their service areas are p EASs, where p is an integer less than or equal to n.

[0325] 608 , the EES sends an EAS discovery response to the EEC, where the EAS discovery response includes EAS information and first indication information.

[0326] The first indication information is used to indicate at least one of the following: there is a common area among the service areas of the p EASs; or the p EASs need to coordinate application context migration.

[0327] 609. The EES sends first instruction information to the EAS.

[0328] The EES may also send the public area to the EAS. In some implementations, the EES sends the p EAS IDs where the public area exists to the EAS, indicating that the service areas of the p EASs corresponding to the p EAS IDs contain the public area. For example, the EES may send the corresponding relationship between the p EAS IDs and the public area.

[0329] It should be noted that the processes shown in Figures 6a-6e above can be applied to the initial EAS discovery process or to the target EAS discovery process during application context migration, and this application does not limit this. If applied to the target EAS discovery process, the p EASs mentioned above can be replaced with p target EASs.

[0330] Please refer to Figure 7a, which is a flowchart of another information indication method provided in an embodiment of the present application. The information indication method shown in Figure 7a includes but is not limited to the following steps. It is understood that the following steps are for example only, and the information indication method may also include some of the following steps, but not all of them. This application does not limit this. It should be noted that the following steps are not limited to the order in which they are executed.

[0331] 701. The source EES sends a first request message to the ECS. The first request message may be used to request information of the target EES corresponding to the EAS ID.

[0332] Exemplarily, the first request message may be a Retrieve T-EES request message for obtaining the target EES, or may be other messages. This application does not limit the bearer message.

[0333] When the source EAS or source EES detects the need for application context migration, it sends a first request message to the ECS. Exemplarily, the first request message includes at least two EAS IDs. These at least two EAS IDs may be the EAS IDs determined to require application context migration during the last application context migration. For ease of description, the EAS IDs determined to require application context migration during the last migration are referred to as p EAS IDs. For example, the p EAS IDs may be the EAS IDs determined to require application context migration by the EEC as illustrated in Figures 6a-6e. As the terminal device moves, the need for application context migration may be detected again. Exemplarily, the condition for application context migration may be that the terminal device moves out of the common area determined during the last application context migration.

[0334] If the p EAS IDs correspond to at least one source EES, the source EESs can trigger each other to obtain information about the target EESs corresponding to their respective EAS IDs from the ECS. It is understood that the p EAS IDs can be bundle EAS IDs corresponding to the first application.

[0335] 702, the ECS determines at least one EES.

[0336] The ECS receives a target EES acquisition request from at least one source EES, where the target EES acquisition request includes an EAS ID.

[0337] In a first possible implementation, the ECS may determine at least one target EES based on the service area of ​​the EES managed / corresponding to the ECS or the service area of ​​the EAS. In the at least one target EES, the service areas of at least two target EASs have a common area. For ease of description, in the embodiment of the present application, the number of EASs with a common area is q, where q is an integer greater than or equal to 2, and q is an integer less than or equal to p.

[0338] Method 1: Based on the service area of ​​the EAS, among the at least one target EES determined, the service areas of the q target EASs corresponding to the q EAS IDs have a common area. It is understood that if q is less than p, then the pq EAS IDs that do not have a common area can trigger application context migration individually based on demand.

[0339] For example, the ECS determines at least one target EES based on the service areas of each EAS registered on the EES managed by the ECS, to ensure that the service areas of the q target EASs corresponding to the q EAS IDs in the determined at least one target EES have a common area.

[0340] Mode 2: Among the at least one target EES determined based on the service area of ​​the EES, the service area of ​​the at least one target EES has a common area. For example, the ECS determines at least one target EES based on the service area of ​​the EES managed by the ECS to ensure that the service area of ​​the at least one target EES determined has a common area. Exemplarily, the service area of ​​the EES can be the same as the service area of ​​the EAS registered on the EES. In other words, if the service area of ​​the at least one target EES has a common area, then the service areas of the q target EASs corresponding to the q EAS IDs registered on the at least one target EES have a common area. Exemplarily, the service area of ​​the EES can also be different from the service area of ​​the EAS registered on the EES. In this case, the source EES needs to further determine, based on the service area of ​​the EAS registered on the at least one target EES, whether the service areas of the q target EASs corresponding to the q EAS IDs have a common area. The way in which the source EES obtains the service area of ​​the EAS registered on the at least one target EES can be that the ECS sends it to the source EES, or the source EES can obtain the service area of ​​the target EAS from the corresponding EES through the EAS discovery process, which is not limited in this application.

[0341] In a second possible implementation, the ECS may determine at least one EES according to the EES discovery process. The specific selection process may refer to the EES discovery process in the aforementioned embodiment.

[0342] 703. The ECS sends a first response message to the source EES. The first response message may include at least one of the following: second indication information, the service area of ​​at least one EES, and the service area of ​​at least one EAS corresponding to the at least one EES. The second indication information may be used to indicate that the service areas of at least two target EASs in at least one target EES have a common area.

[0343] Exemplarily, the first response message includes information of the EES determined by the ECS.

[0344] Illustratively, the first response message may be a Retrieve T-EES response message for obtaining a target EES. This embodiment of the present application does not limit the bearer message, and may also be other messages.

[0345] If the first possible implementation method is adopted in step 502 to determine at least one target EES, that is, at least one target EES is determined based on the service area of ​​the EES or the service area of ​​the EAS to ensure that there is a common area in the service areas of q EASs in the at least one EES, then the first response message includes second indication information, and the second indication information is used to indicate that in the at least one target EES, there is a common area in the service areas of at least two target EASs, and the identifiers of the at least two target EASs are included in the above-mentioned p EAS IDs. For the convenience of description, this application refers to the at least two target EASs with a common area as q target EASs, and the p EAS IDs include the q target EAS IDs, where p is greater than or equal to q.

[0346] If the second possible implementation method is used in step 502 to determine at least one EES, that is, to determine at least one EES through the EES discovery process (that is, the EES is not determined based on the service area of ​​the EES and / or the service area of ​​the EAS), the first response message may include the service area of ​​the at least one EAS corresponding to the at least one EES, or include the service areas corresponding to the at least one EES. For example, the first response message may include the service areas of all EASs registered in the EES, or the first response message may include the service area of ​​the EAS corresponding to the requested EAS ID registered in the EES, which is not limited in this application.

[0347] In some embodiments, the source EES may determine the target EES corresponding to the source EES according to the service area of ​​the EAS in the first response message to ensure that the service areas of the q target EASs in the p EAS IDs have a common area.

[0348] In some embodiments, the first response message may include the service area of ​​at least one EES, where the at least one EES is the EES corresponding to p EAS IDs, i.e., the EASs corresponding to the p EAS IDs are registered in the at least one EES. Exemplarily, if the service area of ​​the EES is the same as the service area of ​​the EAS registered on the EES, the source EES may determine the target EES corresponding to the source EES based on the service area of ​​the at least one EES in the first response message, to ensure that the service areas of the q target EASs among the p EAS IDs have a common area. Exemplarily, if the service area of ​​the EES is different from the service area of ​​the EAS registered on the EES, the source EES may further obtain the service areas of the EASs corresponding to the p EAS IDs in the at least one EES, and select the corresponding target EES based on the service areas of the EASs corresponding to the p EAS IDs, to ensure that the service areas of the q target EASs among the p EAS IDs have a common area.

[0349] 704 , the source EES determines that the service areas of at least two target EASs have a common area.

[0350] Among them, step 704 is an optional step.

[0351] For ease of description, the number of target EASs that will exist in the common area is q.

[0352] In a possible implementation, the first response message includes second indication information, and the source EES may determine that the service areas of the q target EASs have a common area according to the second indication information. The first response message also includes information of at least one target EES.

[0353] In one possible implementation, the first response message includes the service area of ​​at least one EAS corresponding to at least one EES. The source EES can determine at least one target EES based on the service area of ​​at least one EAS corresponding to the at least one EES. On the determined at least one target EES, the service areas of p EAS have a common area.

[0354] In one possible implementation, the first response message includes the service areas corresponding to the at least one EES, and the source EES determines at least one target EES with a common area based on the service areas corresponding to the at least one EES. For example, if the service area of ​​the EES is the same as the service area of ​​the EAS registered on the EES, it is guaranteed that the service areas of the q EASs on the EES with a common area exist in a common area. If the service area of ​​the EES is different from the service area of ​​the EAS registered on the EES, the source EES may further obtain the service area of ​​the EAS from the determined EES, thereby determining that the service areas of the q EASs have a common area.

[0355] In one possible implementation, the first response message includes information of at least one EES. The source EES may send an EAS discovery request message to the EES carried in the first response message. The EAS discovery request message includes information such as EAS ID and EAS FQDN. The EES returns an EAS discovery response message. The EAS discovery response message includes the service area corresponding to the EAS ID. The source EES may determine that there is a common area in the service areas of q EASs based on the service area corresponding to the EAS ID included in the EAS discovery response message.

[0356] In one possible implementation, the first response message includes the service area of ​​at least one EES. The source EES determines, based on the service area of ​​the at least one EES, that there is at least one EES in a public area in the service area of ​​the EES, and sends an EAS discovery request message to the at least one EES in the service area of ​​the EES where there is a public area. The EAS discovery request message includes information such as the EAS ID and the EAS FQDN. The EES returns an EAS discovery response message. If the service area of ​​the EES is the same as the service area of ​​the corresponding EAS, the EAS service area corresponding to the EAS ID included in the EAS discovery response message also has a public area.

[0357] For example, if the service area of ​​the EES is different from the service area of ​​the corresponding EAS, the source EES may further determine that the service areas of the q EASs have a common area according to the service area corresponding to the EAS ID included in the EAS discovery response message.

[0358] 705 , the source EES sends an EAS discovery request message to the target EES.

[0359] The EAS discovery request message carries information such as the EAS ID and EAS FQDN corresponding to the S-EES, and at least two EAS IDs corresponding to the same application (for example, a bundle EAS ID list).

[0360] In one possible implementation, the EAS discovery request message may also carry third indication information, and the third indication information is used to indicate that a common area is required between at least two target EASs in the EAS ID corresponding to the same application. After the target EES receives the above-mentioned EAS discovery request message, it determines at least two target EASs based on the service area information of the EAS managed / registered on the target EES, and determines that the service areas of the above-mentioned at least two target EASs have a common area (for example, there is a common area between the service areas of q target EASs), that is, determines the first indication information.

[0361] In one possible implementation, the request message does not carry the indication information. In this case, the target EES only determines the EAS based on the EAS ID, EAS FQDN, bundle EAS ID list, etc., or the target EES does not make a determination and sends all EASs managed / registered on the target EES and the corresponding service areas to the S-EES.

[0362] 706 , the target EES sends an EAS discovery response message to the source EES.

[0363] The EAS discovery response message carries information of the target EAS, including endpoint information of the target EAS, EAS address information, and the like.

[0364] In a possible implementation, if the target EES determines that the service areas of at least two target EASs have a common area, the EAS discovery response message may further carry first indication information.

[0365] In a possible implementation, the EAS discovery response message may include information of at least one EAS and a service area corresponding to the EAS.

[0366] 707, the source EES determines the target EAS based on the service area of ​​the EAS.

[0367] Step 707 is an optional step.

[0368] The source EES may determine the target EAS based on the service area of ​​the EAS carried in the EAS discovery response message to ensure that the service areas of at least two target EASs have a common area (eg, the service areas of q target EASs have a common area), that is, the source EES determines the first indication information.

[0369] 708. The source EES sends first indication information to the target EES, wherein the first indication information is used to indicate at least one of the following: indicating that the at least two target EASs need to coordinate application context migration; or indicating that the service areas of the at least two target EASs have a common area.

[0370] The source EES determines that the service areas of the q target EASs have a common area, and the source EES sends first indication information to the target EES, where the target EES is the EES corresponding to the target EAS. Exemplarily, the first indication information may be carried in a second request message, which may be an EAS discovery request message. It is understood that this application does not limit the bearer message.

[0371] In some embodiments, the second request message may further include EAS IDs of the q target EASs and a common area of ​​the service areas of the q target EASs.

[0372] 709. The target EES sends first instruction information to the target EAS.

[0373] In some embodiments, step 706 is optional.

[0374] After receiving the first indication information, the target EES further sends the first indication information to the target EAS. In some embodiments, the target EES sends the EAS IDs of the q target EASs and the common area of ​​the service areas of the q target EASs to the target EAS, so that the subsequent application context migration condition includes detecting whether the terminal device has moved out of the common area. If it is detected that the terminal device has moved out of the common area, the q target EASs and at least one target EES corresponding to the q target EASs can trigger each other to collaboratively perform application context migration.

[0375] 710. The source EES sends first indication information to the EEC.

[0376] The first indication information sent by the source EES to the EEC may be carried in a notification message, which may be a Target Information Notification. Furthermore, the notification message may also include the EAS IDs of the q target EASs and the common area of ​​the service areas of the q target EASs.

[0377] The following is an example of Figure 7a in conjunction with Figure 7b. In Figure 7b, the first request message is the target EES Retrieve T-EES request, the first application is AC, the source EES includes S-EES1 and S-EES2, the source EAS includes S-EAS1 and S-EAS2, and the target EES is T-EES as an example.

[0378] As shown in FIG7b , an example of an information indication method provided in an embodiment of the present application is shown. As shown in FIG7b , the information indication method includes but is not limited to the following steps. It is understandable that the information indication method may include some, but not all, of the steps in FIG7b . The following is explained in conjunction with FIG7b :

[0379] 800, EEC, S-EAS1, S-EAS2, S-EES1, and S-EES2 store the first indication information. When the terminal device moves and requires coordinated application context migration, S-EAS1, S-EAS2, S-EES1, and S-EES2 trigger ACR with each other according to the existing technology. For details, please refer to steps 1-8 of the embodiment shown in Figure 5.

[0380] Step 800 is an optional step.

[0381] EEC, S-EAS1, S-EAS2, S-EES1, S-EES2 store at least two EAS IDs that need to perform application context migration together. When the terminal device moves and it is determined that application context migration is required together, for example, when the terminal device moves out of a public area, S-EAS1, S-EAS2, S-EES1, S-EES2 can trigger each other to perform application context migration.

[0382] 801. S-EES1 and S-EES2 send a T-EES acquisition request to the ECS.

[0383] 802. The ECS determines at least one T-EES.

[0384] The T-EES acquisition request includes an EAS ID and bundle EAS information (e.g., a bundle EAS ID list). The ECS determines at least one T-EES based on the service areas of the EASs or EESs managed on the ECS, where the bundle EAS IDs of at least two T-EESs share a common service area.

[0385] 803, ECS sends a Retrieve T-EES response to S-EES1 and S-EES2.

[0386] The T-EES acquisition response includes the EAS ID, T-EES information, and first indication information, which indicates that the service areas of the two T-EASs share a common area and require application context migration. It is understood that the number of T-EESs determined can be one or more. Figure 7b uses one T-EES as an example.

[0387] The specific description of steps 802 to 803 can be found in the relevant description of FIG. 7 a , which will not be repeated here.

[0388] In some embodiments, if the at least one T-EES determined in step 802 is not determined based on the service area of ​​the EAS or the service area of ​​the EES, and the T-EES acquisition response in step 803 includes the service area of ​​the at least one T-EES or the service area of ​​the EAS corresponding to the at least one T-EES, step 804 may also be included.

[0389] 804 , S-EES1 and S-EES2 determine that the service areas of at least two T-EASs have a common area based on the service area of ​​the T-EES or the service area of ​​the EAS corresponding to the T-EES.

[0390] For a detailed description of step 804, please refer to the relevant description of step 704 in the embodiment of FIG. 7a, which will not be repeated here.

[0391] 805 , S-EES1 and S-EES2 send an EAS discovery request to T-EES, where the EAS discovery request includes first indication information.

[0392] The EAS discovery request EAS discovery request includes EAS ID, T-EES information, and first indication information ACR coordinate indication (ACR coordinate required or no requirement for ACR coordinate) for indicating whether T-EAS1 and T-EAS2 need to perform application context migration together, where there can be only one T-EES, or S-EES1 and S-EES2 correspond to different T-EESs respectively.

[0393] 806. T-EES sends first indication information to T-EAS1 and T-EAS2 respectively.

[0394] T-EES may respectively notify T-EAS1 and T-EAS2 of the first indication information.

[0395] For a detailed description of step 806, please refer to step 706 in the embodiment shown in FIG. 7a, which will not be repeated here.

[0396] 807 , T-EES sends an EAS discovery response to S-EES1 and S-EES2.

[0397] The EAS discovery response may be used to indicate the success or failure of the T-EAS discovery.

[0398] 808. S-EES1 or S-EES2 sends first indication information to EEC.

[0399] For a detailed description of step 808, please refer to step 707 of the embodiment shown in FIG. 7a, which will not be repeated here.

[0400] Please refer to Figure 8a, which is a flowchart of another information indication method provided in an embodiment of the present application. The information indication method shown in Figure 8a includes but is not limited to the following steps. It is understood that the following steps are for example only, and the information indication method may also include some of the following steps, but not all of them. This application does not limit this. It should be noted that the following steps are not limited to the order in which they are executed.

[0401] 901, a second EES sends a first request message to a first EES. The first request message may be used to request whether a service area of ​​the EAS corresponding to the first application includes a public area. Correspondingly, the first EES receives the first request message.

[0402] Exemplarily, the first EES is a first source EES, the second EES is a second source EES, and the first request message may include a service area of ​​a second target EES selected by the second source EES and / or a service area of ​​an EAS corresponding to the second target EES.

[0403] Exemplarily, the first EES is the first target EES determined by the first source EES, and the second EES is the second target EES determined by the second source EES. The first request message may include the service area of ​​the second EES and / or the service area of ​​the EAS corresponding to the second EES.

[0404] 902 , the first EES determines that a service area of ​​the first target EAS and a service area of ​​the second target EAS have a common area.

[0405] For example, the EAS corresponding to the first application may be at least two target EASs selected for the first application during application context migration, where the at least two target EASs are bundle EASs of the first application. For ease of description, this application uses two target EASs as an example, namely the first target EAS and the second target EAS.

[0406] In a first possible implementation, the first EES is the first source EES, and the second EES is the second source EES. The first source EES corresponds to the first source EAS, and the second source EES corresponds to the second source EAS. The first source EAS and the first target EAS have the same EAS ID, and the second source EAS and the second target EAS have the same EAS ID. The first target EAS can be understood as the target EAS selected for the first source EAS, and the second target EAS can be understood as the target EAS selected for the second source EAS.

[0407] Prior to step 701, when the first source EAS and the second source EAS need to perform application context migration together, the first source EES, the second source EES, the first source EAS, and the second source EAS trigger each other to perform application context migration. Specifically, optionally, the first source EES obtains information about at least one EES for the first source EAS from the ECS, selects a first target EES from the at least one EES, and discovers the first target EAS from the first target EES through the EAS discovery process. The second source EES obtains information about at least one EES for the second source EAS from the ECS, selects a second target EES from the at least one EES, and discovers the second target EAS from the second target EES through the EAS discovery process.

[0408] In order to determine whether the service areas of the first target EAS and the second target EAS have a common area, two examples are given below:

[0409] Method 1: determining whether the service areas of the first target EAS and the second target EAS have a common area based on the service areas of the first target EES and the second target EES, wherein the service area of ​​the EES is the same as the service area of ​​the EAS registered with the EES.

[0410] Exemplarily, the second source EES sends a first request message to the first source EES, where the first request message carries the service area of ​​the second target EES selected by the second source EES. The first source EES determines whether there is a common area between the service area of ​​the first target EES and the service area of ​​the second target EES. If there is a common area between the service area of ​​the first target EES and the service area of ​​the second target EES, it is determined that there is a common area between the service area of ​​the first target EES and the service area of ​​the second target EES. It is understandable that the first source EES may also send a first request message to the second source EES to request the second source EES to determine whether there is a common area between the service area of ​​the first target EES and the service area of ​​the second target EES, which is not limited in this application.

[0411] Method 2: determining whether the service areas of the first target EAS and the second target EAS have a common area based on the service area of ​​the first target EAS and the service area of ​​the second target EAS.

[0412] Exemplarily, the second source EES sends a first request message to the first source EES, where the first request message includes the service area of ​​the second target EAS corresponding to the second target EES selected by the second source EES. The first source EES determines whether the first target EAS and the second target EAS share a common area based on the service area of ​​the first target EAS and the service area of ​​the second target EAS. It is understood that the first source EES may also send a first request message to the second source EES to request the second source EES to determine whether the service area of ​​the first target EES and the service area of ​​the second target EES share a common area, which is not limited in this application.

[0413] In a second possible implementation, the first EES is the first target EES selected by the first source EES, and the second EES is the second target EES selected by the second source EES. The first target EES corresponds to the first target EAS, and the second target EES corresponds to the second target EAS. The first source EES corresponds to the first source EAS, and the second source EES corresponds to the second source EAS. The first source EAS and the first target EAS have the same EAS ID, and the second source EAS and the second target EAS have the same EAS ID. The first target EAS can be understood as the target EAS selected for the first source EAS, and the second target EAS can be understood as the target EAS selected for the second source EAS.

[0414] Prior to step 701, when the first source EAS and the second source EAS need to perform application context migration together, the first source EES, the second source EES, the first source EAS, and the second source EAS trigger each other to perform application context migration. Specifically, optionally, the first source EES obtains information about at least one EES for the first source EAS from the ECS, selects a first target EES from the at least one EES, and discovers the first target EAS from the first target EES through the EAS discovery process. The second source EES obtains information about at least one EES for the second source EAS from the ECS, selects a second target EES from the at least one EES, and discovers the second target EAS from the second target EES through the EAS discovery process.

[0415] In order to determine whether the service areas of the first target EAS and the second target EAS have a common area, two examples are given below:

[0416] Method 1: determining whether the service areas of the first target EAS and the second target EAS have a common area based on the service areas of the first target EES and the second target EES, wherein the service area of ​​the EES is the same as the service area of ​​the EAS registered with the EES.

[0417] Exemplarily, the second target EES sends a first request message to the first target EES, and the first request message carries the service area of ​​the second target EES. The first target EES determines whether there is a common area between the service area of ​​the first target EES and the service area of ​​the second target EES. If there is a common area between the service area of ​​the first target EES and the service area of ​​the second target EES, it is determined that there is a common area between the service area of ​​the first target EES and the service area of ​​the second target EES. It is understandable that the first target EES may also send a first request message to the second target EES to request the second target EES to determine whether there is a common area between the service area of ​​the first target EES and the service area of ​​the second target EES, which is not limited in this application.

[0418] Method 2: determining whether the service areas of the first target EAS and the second target EAS have a common area based on the service area of ​​the first target EAS and the service area of ​​the second target EAS.

[0419] Exemplarily, the second target EES sends a first request message to the first target EES, where the first request message includes the service area of ​​the second target EAS corresponding to the second target EES. The first target EES determines whether the first target EAS and the second target EAS have a common area based on the service area of ​​the first target EAS and the service area of ​​the second target EAS. It is understandable that the first target EES may also send a first request message to the second target EES to request the second target EES to determine whether the service area of ​​the first target EES and the service area of ​​the second target EES have a common area, which is not limited in this application.

[0420] 903. The first EES sends a first response message to the second EES, where the first response message includes first indication information. The first indication information is used to indicate at least one of the following: indicating that the first target EAS and the second target EAS need to coordinate application context migration; or indicating that the first target EAS and the second target EAS have a common service area.

[0421] In some embodiments, the first response message may further include a common area between the first target EAS and the second target EAS.

[0422] Exemplarily, if the first EES is the first source EES and the second EES is the second source EES, the second source EES receives the first response message and sends the first indication information to the second target EES. The second source EES may also send the common area of ​​the first target EAS and the second target EAS to the second target EES. After receiving the first indication information, the second target EES may send the first indication information to the second target EAS. Exemplarily, the second target EES may also send the common area to the second target EAS. Similarly, the first source EES may send the first indication information to the first target EES. In some embodiments, the first source EES may also send the common area of ​​the first target EAS and the second target EAS to the first target EES. The first target EES may send the first indication information to the first target EAS. In some embodiments, the first target EES may also send the common area of ​​the first target EAS and the second target EAS to the first target EES. It is understood that the number of target EES may be one, and both the first source EES and the second source EES send the first indication information to the target EES.

[0423] For example, if the first EES is the first target EES and the second EES is the second target EES, the second target EES receives the first response message and sends the first indication information to the second target EAS. In some embodiments, the second target EES may send the common area of ​​the first target EAS and the second target EAS to the second target EAS. Similarly, the first target EES may send the first indication information to the first target EAS. In some embodiments, the first target EES may send the common area to the first target EAS.

[0424] FIG8a is illustrated below with reference to FIG8b and FIG8c. FIG8b illustrates an example in which the first EES is S-EES1 and the second EES is S-EES2. FIG8c illustrates an example in which the first EES is T-EES1 and the second EES is T-EES2. FIG8b and FIG8c illustrate an example in which the service area of ​​an EES is the same as the service area of ​​the EAS registered on the EES.

[0425] As shown in FIG8b , an example of an information indication method provided in an embodiment of the present application is shown. As shown in FIG8b , the information indication method includes but is not limited to the following steps. It is understandable that the information indication method may include some, but not all, of the steps in FIG8b . The following is explained in conjunction with FIG8b :

[0426] 1000, EEC, S-EAS1, S-EAS2, S-EES1, and S-EES2 store the first indication information. When the terminal device moves and requires coordinated application context migration, S-EAS1, S-EAS2, S-EES1, and S-EES2 trigger ACR with each other according to the existing technology. For details, please refer to steps 1-8 of the embodiment shown in Figure 5.

[0427] 1001, S-EES1 and S-EES2 send a T-EES acquisition request.

[0428] For steps 1000 to 1001 of the embodiment of the present application, please refer to steps 800 to 801 of the embodiment shown in FIG7 b , which will not be repeated here.

[0429] 1002. The ECS sends a T-EES acquisition response to S-EES1 and S-EES2. The T-EES acquisition response includes the service area of ​​the T-EES.

[0430] The ECS sends a Retrieve T-EES response to S-EES1 and S-EES2 respectively. The T-EES Retrieve T-EES response includes the EAS ID of the corresponding S-EES, information of at least one T-EES, and the service area of ​​the T-EES or the service area of ​​the EAS corresponding to the T-EES.

[0431] 1003, S-EES1 and S-EES2 determine T-EES respectively.

[0432] In one implementation, the T-EES determined by S-EES1 and S-EES2 may be the same, that is, the T-EES determined by S-EES1 and S-EES2 is the same.

[0433] In one implementation, the T-EESs determined by S-EES1 and S-EES2 may be different. For example, the T-EES determined by S-EES1 is T-EES1, and the T-EES determined by S-EES2 is T-EES2. This application does not limit this.

[0434] 1004. S-EES1 sends a request message to S-EES2, where the request message is used to request S-EES2 to determine whether there is a public area in the service area of ​​the target EAS corresponding to the first application. The request message includes the service area of ​​T-EES1 selected by S-EES1, or the service area of ​​the EAS corresponding to T-EES1 selected by S-EES1.

[0435] Exemplarily, the request message may be an ACR coordinate determination request.

[0436] 1005. S-EES2 sends a response message to S-EES1. The response message includes first indication information. The first indication information is used to indicate that T-EAS1 and T-EAS2 have a common area.

[0437] In some embodiments, the service area of ​​the T-EES is the same as the service area of ​​the EAS registered with the T-EES, and the request message includes the service area of ​​T-EES1. Specifically, S-EES2 optionally determines whether T-EES1 and T-EES2 have a common area based on the received service area of ​​T-EES1 and the service area of ​​T-EES2 selected by S-EES2. If T-EES1 and T-EES2 have a common area, then T-EAS1 and T-EAS2 have a common area.

[0438] In some embodiments, the service area of ​​the T-EES is different from the service area of ​​the EAS registered with the T-EES, and the request message includes the service area of ​​the EAS corresponding to T-EES1. Specifically, S-EES2 optionally determines whether T-EAS1 and T-EAS2 have a common area based on the service area of ​​T-EAS1 and the service area of ​​T-EAS2.

[0439] Exemplarily, the response message may be an ACR coordinate determination response, and the first indication information may be an application context coordinated migration indication ACR coordinate indication.

[0440] In some embodiments, the response message also includes a public area.

[0441] 1006 , S-EES1 and S-EES2 send an EAS discovery request to T-EES, where the EAS discovery request includes first indication information.

[0442] Exemplarily, S-EES1 sends an EAS discovery request to T-EES1, and S-EES2 sends an EAS discovery request to T-EES2. The EAS discovery request includes the first indication information. In some embodiments, the EAS discovery request also includes a public area.

[0443] 1007. T-EES sends first indication information to T-EAS1 and T-EAS2 respectively.

[0444] Exemplarily, T-EES1 sends first indication information to T-EAS1, and T-EES2 sends first indication information to T-EAS2. In some embodiments, T-EES1 further sends a public area to T-EAS1, and T-EES2 further sends a public area to T-EAS2, and the condition for subsequent application context migration may include the terminal device moving out of the public area.

[0445] 1008 , T-EES sends an EAS discovery response to S-EES1 and S-EES2 .

[0446] 1009. S-EES1 sends first indication information to EEC.

[0447] S-EES#1 or S-EES#2 sends first indication information to the EEC, to indicate whether the subsequent bundle EAS of the UE needs to apply context migration together.

[0448] FIG8c is an example of an information indication method provided in an embodiment of the present application. As shown in FIG8c , the information indication method includes but is not limited to the following steps. It is understandable that the information indication method may include some, but not all, of the steps in FIG8c . The following is explained in conjunction with FIG8c :

[0449] 1100, EEC, S-EAS1, S-EAS2, S-EES1, and S-EES2 store the first indication information. When the terminal device moves and requires coordinated application context migration, S-EAS1, S-EAS2, S-EES1, and S-EES2 trigger ACR with each other according to the existing technology. For details, please refer to steps 1-8 of the embodiment shown in Figure 5.

[0450] 1101, S-EES1 and S-EES2 send a T-EES acquisition request.

[0451] For steps 1100 to 1101 of the embodiment of the present application, please refer to steps 800 to 801 of the embodiment shown in FIG7 b , which will not be repeated here.

[0452] 1102. The ECS sends a T-EES acquisition response to S-EES1 and S-EES2. The T-EES acquisition response includes the service area of ​​the T-EES.

[0453] 1103 , S-EES1 and S-EES2 respectively determine T-EES, for example, S-EES1 determines T-EES1, and S-EES2 determines T-EES2.

[0454] For steps 1102-1103 of the embodiment of this application, please refer to the description of steps 1002-1003 in the embodiment of Figure 8b, which will not be repeated here.

[0455] 1104 , S-EES1 sends an EAS discovery request to T-EES1 , where the EAS discovery request includes information about T-EES2 .

[0456] The information of T-EES2 may include address information of T-EES2, so that T-EES1 can send a request message to T-EES2.

[0457] 1105 , S-EES2 sends an EAS discovery request to T-EES2 , where the EAS discovery request includes information of T-EES1 .

[0458] The information of T-EES2 may include the address information of T-EES1, so that T-EES2 can send a response message to T-EES1.

[0459] 1106 , T-EES1 and T-EES2 send EAS discovery responses respectively.

[0460] 1107. T-EES1 sends a request message to T-EES2, where the request message is used to request T-EES2 to determine whether there is a public area in the service area of ​​the target EAS corresponding to the first application. The request message includes the service area of ​​T-EES1; or the service area of ​​the EAS corresponding to T-EES1 selected by S-EES1.

[0461] 1108. T-EES2 sends a response message to T-EES1, where the response message includes first indication information.

[0462] In some embodiments, the service area of ​​the T-EES is the same as the service area of ​​the EAS registered with the T-EES, and the request message includes the service area of ​​T-EES1. Specifically, T-EES2 optionally determines whether T-EES1 and T-EES2 have a common area based on the received service area of ​​T-EES1 and the service area of ​​T-EES2. If T-EES1 and T-EES2 have a common area, then T-EAS1 and T-EAS2 have a common area.

[0463] In some embodiments, the service area of ​​the T-EES is different from the service area of ​​the EAS registered with the T-EES, and the request message includes the service area of ​​the EAS corresponding to T-EES1. Specifically, T-EES2 optionally determines whether T-EAS1 and T-EAS2 have a common area based on the service area of ​​T-EAS1 and the service area of ​​T-EAS2.

[0464] 1109. T-EES1 and T-EES2 send first indication information to T-EAS1 and T-EAS2 respectively.

[0465] Please refer to step 1007 in the embodiment of Figure 8b for step 1109 of this application embodiment, and will not be repeated here.

[0466] 1110. T-EES1 sends first indication information to S-EES1.

[0467] In some implementations, T-EES 2 may also send the first indication information to S-EES 2. In some embodiments, T-EES may also send the public area to S-EES.

[0468] 1111. S-EES1 sends first indication information to EEC.

[0469] Please refer to step 1009 in the embodiment of Figure 8b for step 1111 of this application embodiment, and will not be repeated here.

[0470] The following describes a communication device according to an embodiment of the present application.

[0471] The present application divides the functional modules of the communication device according to the above-mentioned method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in this application is schematic and is only a logical functional division. There may be other division methods in actual implementation. The communication device of the embodiment of the present application will be described in detail below with reference to Figures 9 to 11.

[0472] Figure 9 is a structural diagram of a communication device provided in an embodiment of the present application. As shown in Figure 9, the communication device 1000 can correspond to the functions or steps implemented by the communication device (e.g., EEC or EES or ECS or source EES or first EES) in the above-mentioned various method embodiments. The communication device may include a processing unit 1200 and a transceiver unit 1100. Optionally, it may also include a storage unit, which can be used to store instructions (code or program) and / or data. The processing unit 1200 and the transceiver unit 1100 can be coupled with the storage unit. For example, the processing unit 1200 can read the instructions (code or program) and / or data in the storage unit to implement the corresponding method. The above-mentioned units can be set independently or partially or fully integrated. For example, the transceiver unit 1100 may include a sending unit and a receiving unit. The sending unit may be a transmitter and the receiving unit may be a receiver. The entity corresponding to the transceiver unit 1100 may be a transceiver.

[0473] In some possible implementations, the communication device 1000 can implement the corresponding behaviors and functions of the EEC in the above-mentioned method embodiments. For example, the communication device 1000 can be an EEC, or it can be a component (such as a chip or circuit) used in a terminal device. The transceiver unit 1100 can be used to perform all receiving or sending operations performed by the EEC in the embodiments of Figures 6a to 8c. The processing unit 1200 is used to perform all operations performed by the EEC except for the receiving and sending operations. The following describes the communication device used in the EEC:

[0474] The communication device 1000 includes a processing unit 1200 and a transceiver unit 1100 .

[0475] The processing unit 1200 is configured to determine that service areas of at least two target edge application servers (EASs) have a common area, where the at least two target EASs are EASs corresponding to a first application.

[0476] The transceiver unit 1100 is configured to send first indication information, where the first indication information is used to indicate at least one of the following: indicating that the at least two target EASs need to coordinate application context migration; or indicating that service areas of the at least two target EASs have a common area.

[0477] Exemplarily, the transceiver unit 1100 is also used to send a first request message to the edge configuration server ECS, wherein the first request message is used to request information of the edge enabling server EES corresponding to the EAS identifier, the requested EAS identifier corresponds to the first application, and the requested EAS identifier includes the identifiers of the at least two EASs.

[0478] Exemplarily, the transceiver unit 1100 is also used to receive a first response message from the ECS, the first response message including at least one of the following: the second indication information, the service area of ​​at least one EES, and the service area of ​​at least one EAS corresponding to at least one EES, the second indication information being used to indicate that in at least one target EES, there is a common area in the service areas of the at least two target EASs.

[0479] Exemplarily, the first response message includes a service area of ​​at least one EAS corresponding to the at least one EES;

[0480] The processing unit 1200 is further configured to determine at least one target EES according to the service area of ​​at least one EAS corresponding to the at least one EES, wherein, in the at least one target EES, the service areas of the at least two target EASs have a common area.

[0481] Exemplarily, the first response message includes a service area of ​​the at least one EES;

[0482] The processing unit 1200 is further configured to determine at least one target EES according to the service area of ​​the at least one EES, where the service area of ​​the at least one target EES has a common area.

[0483] Illustratively, the service area of ​​the EES is the same as the service area of ​​the EAS corresponding to the EES.

[0484] Exemplarily, the processing unit 1200 is further configured to obtain, from the at least one target EES, a service area of ​​an EAS corresponding to the at least one target EES;

[0485] According to the service area of ​​the EAS corresponding to the at least one target EES, it is determined that the service areas of the at least two target EASs have a common area.

[0486] Exemplarily, the transceiver unit 1100 is specifically configured to send the first indication information to the at least one target EES respectively.

[0487] In some possible implementations, the communication device 1000 can implement the behaviors and functions of the edge enabling server EES in the above-mentioned method embodiments. For example, the communication device 1000 can be an edge enabling server EES, or a component (such as a chip or circuit) in the EES. The transceiver unit 1100 can be used to perform all receiving or sending operations performed by the EES in the embodiments of Figures 6a to 8c. The processing unit 1200 is used to perform all operations performed by the EES except for the sending and receiving operations.

[0488] The communication device 1000 includes a processing unit 1200 and a transceiver unit 1100 .

[0489] The transceiver unit 1100 is configured to receive first indication information from the edge enabling client EEC, where the first indication information is used to indicate at least one of the following: indicating that at least two target EASs cooperate with application context migration; or indicating that service areas of at least two target EASs have a common area, and the at least two target EASs are EASs corresponding to the first application;

[0490] The processing unit 1200 is configured to send the first indication information to a first EAS corresponding to the EES through the transceiver unit 1100 , where the at least two target EASs include the first EAS.

[0491] In some possible implementations, the communication device 1000 can implement the behaviors and functions of the edge configuration server ECS in the above-mentioned method embodiment. For example, the communication device 1000 can be an ECS, or a component (such as a chip or circuit) in the ECS. The transceiver unit 1100 can be used to perform all receiving or sending operations performed by the ECS in the embodiments of Figures 6a to 8c. The processing unit 1200 is used to perform all operations performed by the ECS except for the sending and receiving operations.

[0492] The communication device 1000 includes a processing unit 1200 and a transceiver unit 1100 .

[0493] The transceiver unit 1100 is configured to receive a first request message, where the first request message is used to request information of an edge enabling server EES corresponding to an EAS identifier, where the requested EAS identifier corresponds to the first application;

[0494] The transceiver unit 1100 is also used to send a first response message in response to the first request message, and the first response message includes at least one of the following: first indication information, the service area of ​​at least one EES, and the service area of ​​at least one EAS corresponding to at least one EES. The first indication information is used to indicate at least one of the following: used to indicate that at least two target EASs need to coordinate application context migration; or to indicate that there is a common area in the service areas of at least two target EASs, and the requested EAS identifier includes the identifiers of the at least two target EASs.

[0495] Exemplarily, the first response message includes the first indication information;

[0496] The processing unit 1200 is configured to determine at least one target EES, wherein the service areas of the at least two target EASs have a common area;

[0497] The first response message further includes information of the at least one target EES.

[0498] Exemplarily, in the at least one target EES, the service areas of the at least two target EASs have a common area, including:

[0499] The service area of ​​the at least one target EES has a common area, and the service area of ​​the target EES is the same as the service area of ​​the EAS corresponding to the target EES.

[0500] Exemplarily, the first request message comes from an edge enabling client EEC, or at least one source EES.

[0501] In some possible implementations, the communication device 1000 can implement the behaviors and functions of the source EES in the above-described method embodiments. For example, the communication device 1000 can be a source EES or a component (e.g., a chip or circuit) within the source EES. The transceiver unit 1100 can, for example, be configured to perform all receiving or transmitting operations performed by the source EES in the embodiments of Figures 6a to 8c. The processing unit 1200 is configured to perform all operations performed by the source EES except for the transmitting and receiving operations.

[0502] The communication device 1000 includes a processing unit 1200 and a transceiver unit 1100 .

[0503] The transceiver unit 1100 is configured to send a first request message to the edge configuration server ECS, where the first request message is used to request information of the edge enabling server EES corresponding to the EAS identifier, where the requested EAS identifier corresponds to the first application;

[0504] The transceiver unit 1100 is also used to receive a first response message from the ECS, where the first response message includes at least one of the following information: first indication information, a service area of ​​at least one EES, and a service area of ​​at least one EAS corresponding to at least one EES. The first indication information is used to indicate at least one of the following: used to indicate that at least two target EASs need to coordinate application context migration; or to indicate that there is a common area in the service areas of at least two target EASs, and the requested EAS identifier includes the identifiers of the at least two target EASs.

[0505] Exemplarily, the first response message includes the first indication information; the first response message also includes the target EES corresponding to the source EES.

[0506] Exemplarily, the first response message includes a service area of ​​the at least one EES or a service area of ​​at least one EAS corresponding to the at least one EES;

[0507] The processing unit 1200 is configured to determine a target EES corresponding to the source EES according to a service area of ​​the at least one EES or a service area of ​​at least one EAS corresponding to the at least one EES.

[0508] Exemplarily, the transceiver unit 1100 is further configured to send the first indication information to the target EES.

[0509] Exemplarily, the transceiver unit 1100 is further configured to send the first indication information to the edge enablement client EEC.

[0510] In some possible implementations, the communication device 1000 can implement the corresponding behaviors and functions of the first EES in the above-described method embodiments. For example, the communication device 1000 can be the first EES or a component (e.g., a chip or circuit) within the first EES. The transceiver unit 1100 can, for example, be configured to perform all receiving or transmitting operations performed by the first EES in the embodiments of Figures 6a to 8c. The processing unit 1200 is configured to perform all operations performed by the first EES except for the receiving and transmitting operations.

[0511] The communication device 1000 includes a processing unit 1200 and a transceiver unit 1100 .

[0512] The processing unit 1200 is configured to determine that a service area of ​​a first target EAS and a service area of ​​a second target EAS have a common area, and the first EAS and the second EAS correspond to a first application;

[0513] The transceiver unit 1100 is used to send first indication information to the second EES, where the first indication information is used to indicate at least one of the following: indicating that the first target EAS and the second target EAS need to coordinate application context migration; or indicating that there is a common area in the service areas of the first target EAS and the second target EAS.

[0514] Exemplarily, the transceiver unit 1100 is further configured to receive a first request message sent from the second EES, where the first request message is used to request the first EES to determine whether the EAS corresponding to the first application has a public area;

[0515] The transceiver unit 1100 is specifically configured to send a first response message to the second EES, where the first response message includes the first indication information.

[0516] Exemplarily, the first EES is a first source EES, and the second EES is a second source EES; the first request message includes a service area of ​​a second target EES corresponding to the second source EES;

[0517] The processing unit 1200 is specifically used to determine, based on the service areas of the second target EES and the service areas of the first target EES, that there is a common area between the service areas of the first target EAS and the service areas of the second target EAS, the first target EES is the target EES selected by the first source EES, the service area of ​​the first target EES is the same as the service area of ​​the EAS corresponding to the first target EES, and the first target EAS is the EAS corresponding to the first target EES.

[0518] Exemplarily, the first EES is a first source EES, and the second EES is a second source EES; the first request message includes a service area of ​​the second target EAS corresponding to the second target EES selected by the second source EES;

[0519] The processing unit 1200 is specifically configured to determine that a common area exists between the service areas of the first target EAS and the second target EAS according to the service areas of the second target EAS and the first target EAS, wherein the first target EAS is the EAS corresponding to the first target EES selected by the first source EES.

[0520] Exemplarily, the transceiver unit 1100 is further configured to send the first indication information to the first target EES.

[0521] Exemplarily, the first EES is a first target EES, and the second EES is a second target EES; the first target EES corresponds to the first target EAS, and the second target EES corresponds to the second target EAS; the first request message includes a service area of ​​the second target EES, and the service area of ​​the second target EES is the same as the service area of ​​the EAS corresponding to the second target EES;

[0522] The processing unit 1200 is specifically configured to determine, based on the service areas of the second target EES and the first target EES, that a common area exists between the service areas of the first target EAS and the second target EAS, and that the service area of ​​the first target EES is the same as the service area of ​​the EAS corresponding to the first target EES.

[0523] Exemplarily, the first EES is a first target EES, and the second EES is a second target EES; the first target EES corresponds to the first target EAS, and the second target EES corresponds to the second target EAS, and the first request message includes a service area of ​​the second target EAS corresponding to the second target EES;

[0524] The processing unit 1200 is specifically configured to determine that a common area exists between the service areas of the first target EAS and the second target EAS according to the service areas of the second target EAS and the first target EAS, wherein the first target EAS is the EAS corresponding to the first target EES.

[0525] Exemplarily, the transceiver unit 1100 is further configured to send the first indication information to the first target EAS.

[0526] For the description of the device embodiment shown in FIG9 , please refer to the detailed description of the method embodiment shown in FIG6 a to FIG8 c , which will not be repeated here.

[0527] The above describes the EEC, EES, ECS, source EES, or first EES according to the embodiments of the present application. The following describes possible product forms of the EEC, EES, ECS, source EES, or first EES. It should be understood that any product having the functions described in FIG. 9 falls within the scope of protection of the embodiments of the present application. It should also be understood that the following description is merely illustrative and does not limit the product forms of the EEC, EES, ECS, source EES, or first EES according to the embodiments of the present application to these examples.

[0528] In one possible implementation, in the communication device shown in FIG9 , the processing unit 1200 may be one or more processors, the transceiver unit 1100 may be a transceiver, or the transceiver unit 1100 may be a transmitting unit and a receiving unit, the transmitting unit may be a transmitter, the receiving unit may be a receiver, and the transmitting unit and the receiving unit are integrated into a single device, such as a transceiver. In the embodiment of the present application, the processor and the transceiver may be coupled, etc., and the embodiment of the present application does not limit the connection method between the processor and the transceiver.

[0529] Fig. 10 is a schematic diagram of the structure of another communication device 2000 provided in an embodiment of the present application. The communication device in Fig. 10 can be the above-mentioned EEC, EES, ECS, source EES or first EES.

[0530] As shown in FIG10 , the communication device 2000 includes one or more processors 2200 and a transceiver 2100. The transceiver 2100 can implement the function of the transceiver unit 1100, and the processor 2200 can implement the function of the processing unit 1200.

[0531] In various implementations of the communication device shown in FIG10 , the transceiver may include a receiver and a transmitter, wherein the receiver is configured to perform a receiving function (or operation) and the transmitter is configured to perform a transmitting function (or operation). The transceiver is configured to communicate with other devices / apparatuses via a transmission medium.

[0532] Optionally, the communication device 2000 may further include one or more memories 2300 for storing program instructions and / or data. The memories 2300 are coupled to the processor 2200. Coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which may be electrical, mechanical, or other forms, and is used for information exchange between the devices, units, or modules. The processor 2200 may operate in conjunction with the memories 2300. The processor 2200 may execute program instructions stored in the memories 2300.

[0533] The specific connection medium between the transceiver 2100, processor 2200, and memory 2300 is not limited in the embodiments of the present application. In Figure 10, the embodiment of the present application shows that the transceiver 2100, processor 2200, and memory 2300 are connected via bus 2400. The bus is represented by a bold line in Figure 10. The connection methods between other components are only for schematic illustration and are not limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, Figure 10 only uses a single bold line, but this does not mean that there is only one bus or only one type of bus.

[0534] In the embodiments of the present application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc., and may implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of the present application may be directly implemented as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor, etc.

[0535] In the embodiment of the present application, memory may include but is not limited to non-volatile memories such as hard disk drive (HDD) or solid-state drive (SSD), random access memory (RAM), erasable programmable read-only memory (EPROM), read-only memory (ROM) or portable read-only memory (CD-ROM), etc. Memory is any storage medium that can be used to carry or store program code in the form of instructions or data structures, and can be read and / or written by a computer (such as the communication device shown in the present application), but is not limited thereto. The memory in the embodiment of the present application can also be a circuit or other arbitrarily capable of realizing a storage function, for storing program instructions and / or data.

[0536] The processor 2200 is primarily used to process communication protocols and communication data, control the entire communication device, execute software programs, and process software program data. The memory 2300 is primarily used to store software programs and data. The transceiver 2100 may include a control circuit and an antenna. The control circuit is primarily used to convert baseband signals into radio frequency signals and process radio frequency signals. The antenna is primarily used to transmit and receive radio frequency signals in the form of electromagnetic waves. Input and output devices, such as a touch screen, display, and keyboard, are primarily used to receive user input and output data to the user.

[0537] When the communication device is turned on, the processor 2200 can read the software program in the memory 2300, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor 2200 performs baseband processing on the data to be sent and outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal to the outside in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor 2200. The processor 2200 converts the baseband signal into data and processes the data.

[0538] In another implementation, the RF circuit and antenna may be provided independently of the processor performing baseband processing. For example, in a distributed scenario, the RF circuit and antenna may be remotely arranged independent of the communication device.

[0539] It is understood that the communication device shown in the embodiment of the present application may also have more components than those in Figure 10, and the embodiment of the present application is not limited to this. The method performed by the processor and transceiver shown above is only an example. For the specific steps performed by the processor and transceiver, please refer to the method described above.

[0540] In another possible implementation, in the communication device shown in FIG9 , the processing unit 1200 may be one or more logic circuits, and the transceiver unit 1100 may be an input / output interface, or may be called a communication interface, or an interface circuit, or an interface, etc. Alternatively, the transceiver unit 1100 may also be a sending unit and a receiving unit, the sending unit may be an output interface, the receiving unit may be an input interface, and the sending unit and the receiving unit are integrated into one unit, such as an input / output interface. As shown in FIG11 , the communication device shown in FIG11 includes a logic circuit 3001 and an interface 3002. That is, the above-mentioned processing unit 1200 can be implemented using a logic circuit 3001, and the transceiver unit 1100 can be implemented using an interface 3002. The logic circuit 3001 may be a chip, a processing circuit, an integrated circuit, or a system on chip (SoC) chip, etc., and the interface 3002 may be a communication interface, an input / output interface, a pin, etc. For example, FIG11 is illustrated using the above-mentioned communication device as a chip, and the chip includes a logic circuit 3001 and an interface 3002.

[0541] In the embodiment of the present application, the logic circuit and the interface may also be coupled to each other. The embodiment of the present application does not limit the specific connection method between the logic circuit and the interface.

[0542] It can be understood that the communication device shown in the embodiment of the present application can implement the method provided in the embodiment of the present application in the form of hardware, or can implement the method provided in the embodiment of the present application in the form of software, etc., and the embodiment of the present application is not limited to this.

[0543] An embodiment of the present application also provides a wireless communication system, which includes at least two network entities among AC, EEC, EES, ECS, and EAS. The AC, EEC, EES, ECS, and EAS can be used to execute the method in any of the aforementioned embodiments.

[0544] In addition, the present application also provides a computer-readable storage medium, which stores computer code. When the computer code runs on a computer, the computer executes the operations and / or processing performed by EEC, EES, and ECS in the method provided by the present application.

[0545] The present application also provides a computer program product, which includes computer code or computer program. When the computer code or computer program is run on a computer, the operations and / or processing performed by the EEC, EES, and ECS in the method provided by the present application are executed.

[0546] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or can be electrical, mechanical or other forms of connection.

[0547] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual needs to achieve the technical effects of the solutions provided in the embodiments of the present application.

[0548] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0549] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a readable storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned readable storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, and other media that can store program code.

[0550] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. An information indication method, applied to an edge enabled client EEC, characterized in that: include: Determine that service areas of at least two target edge application servers EAS have a common area, and the at least two target EASs are EASs corresponding to the first application; Sending first indication information, where the first indication information is used to indicate at least one of the following: indicating that the at least two target EASs need to coordinate application context migration; or indicating that service areas of the at least two target EASs have a common area.

2. The method according to claim 1, characterized in that The method further comprises: A first request message is sent to the edge configuration server ECS, where the first request message is used to request information of the edge enabling server EES corresponding to the EAS identifier, the requested EAS identifier corresponds to the first application, and the requested EAS identifier includes identifiers of the at least two EASs.

3. The method according to claim 2, characterized in that The method further comprises: Receive a first response message from the ECS, the first response message including at least one of the following: the second indication information, the service area of ​​at least one EES, and the service area of ​​at least one EAS corresponding to at least one EES, wherein the second indication information is used to indicate that in at least one target EES, there is a common area in the service areas of the at least two target EASs.

4. The method according to claim 3, characterized in that The first response message includes a service area of ​​at least one EAS corresponding to the at least one EES, and the method further includes: At least one target EES is determined according to the service area of ​​at least one EAS corresponding to the at least one EES, wherein, in the at least one target EES, service areas of the at least two target EASs have a common area.

5. The method according to claim 3, characterized in that The first response message includes a service area of ​​the at least one EES, and the method further includes: At least one target EES is determined according to the service area of ​​the at least one EES, and the service area of ​​the at least one target EES has a common area.

6. The method according to claim 5, characterized in that The service area of ​​the EES is the same as the service area of ​​the EAS corresponding to the EES.

7. The method according to claim 5, characterized in that The method further comprises: Obtaining, from the at least one target EES, a service area of ​​an EAS corresponding to the at least one target EES; According to the service area of ​​the EAS corresponding to the at least one target EES, it is determined that the service areas of the at least two target EASs have a common area.

8. The method according to any one of claims 4 to 7, characterized in that: The sending of the first indication information includes: The first indication information is sent to the at least one target EES respectively.

9. An information indication method, applied to an edge enabling server EES, characterized in that: include: receiving first indication information from an edge enabling client EEC, wherein the first indication information is used to indicate at least one of the following: used to indicate that at least two target EASs both coordinate application context migration; or indicating that there is a common area in the service areas of at least two target EASs, where the at least two target EASs are EASs corresponding to the first application; The first indication information is sent to a first EAS corresponding to the EES, and the at least two target EASs include the first EAS.

10. An information indication method, applied to an edge configuration server ECS, characterized in that: include: Receive a first request message, where the first request message is used to request information of an edge enabling server EES corresponding to an EAS identifier, where the requested EAS identifier corresponds to the first application; In response to the first request message, a first response message is sent, where the first response message includes at least one of the following: first indication information, The service area of ​​at least one EES and the service area of ​​at least one EAS corresponding to the at least one EES, wherein the first indication information is used to indicate at least one of the following: used to indicate that at least two target EASs need to coordinate application context migration; Or it indicates that there is a common area in the service areas of at least two target EASs, and the requested EAS identifiers include the identifiers of the at least two target EASs.

11. The method according to claim 10, characterized in that The first response message includes the first indication information, and the method further includes: The ECS determines at least one target EES, in which service areas of the at least two target EASs have a common area; The first response message also includes information of the at least one target EES.

12. The method according to claim 11, characterized in that The service areas of the at least two target EASs in the at least one target EES have a common area, including: The service area of ​​the at least one target EES has a common area, and the service area of ​​the target EES is the same as the service area of ​​the EAS corresponding to the target EES.

13. The method according to any one of claims 10 to 12, characterized in that: The first request message comes from an edge enabling client EEC, or at least one source EES.

14. An information indication method, applied to a source edge enabling server EES, characterized in that: include: Sending a first request message to the edge configuration server ECS, where the first request message is used to request information of the edge enabling server EES corresponding to the EAS identifier, where the requested EAS identifier corresponds to the first application; receiving a first response message from the ECS, the first response message including at least one of the following information: first indication information, a service area of ​​at least one EES, and a service area of ​​at least one EAS corresponding to at least one EES, the first indication information being used to indicate at least one of the following: being used to indicate that at least two target EASs need to coordinate application context migration; Or it indicates that there is a common area in the service areas of at least two target EASs, and the requested EAS identifiers include the identifiers of the at least two target EASs.

15. The method according to claim 14, characterized in that The first response message includes the first indication information; the first response message also includes the target EES corresponding to the source EES.

16. The method according to claim 14, characterized in that The first response message includes the service area of ​​the at least one EES or the service area of ​​at least one EAS corresponding to the at least one EES; the method further includes: A target EES corresponding to the source EES is determined according to a service area of ​​the at least one EES or a service area of ​​at least one EAS corresponding to the at least one EES.

17. The method according to claim 15 or 16, characterized in that The method further comprises: The first indication information is sent to the target EES.

18. The method according to any one of claims 15 to 17, characterized in that: The method further comprises: The first indication information is sent to the edge enabling client EEC.

19. An information indication method, applied to a first edge enabling server EES, characterized in that: include: Determine that a service area of ​​a first target EAS and a service area of ​​a second target EAS have a common area, and the first EAS and the second EAS correspond to a first application; Sending first indication information to the second EES, wherein the first indication information is used to indicate at least one of the following: indicating that the first target EAS and the second target EAS need to coordinate application context migration; or indicating that there is a common area between the service areas of the first target EAS and the second target EAS.

20. The method of claim 19, wherein: The method further comprises: receiving a first request message sent from the second EES, where the first request message is used to request the first EES to determine whether the EAS corresponding to the first application exists in a public area; The sending the first indication information to the second EES includes: A first response message is sent to the second EES, where the first response message includes the first indication information.

21. The method according to claim 19 or 20, characterized in that The first EES is a first source EES, and the second EES is a second source EES; the first request message includes a service area of ​​a second target EES corresponding to the second source EES; The determining that a service area of ​​the first target EAS and a service area of ​​the second target EAS have a common area includes: According to the service area of ​​the second target EES and the service area of ​​the first target EES, it is determined that there is a common area between the service area of ​​the first target EAS and the service area of ​​the second target EAS, the first target EES is the target EES selected by the first source EES, the service area of ​​the first target EES is the same as the service area of ​​the EAS corresponding to the first target EES, and the first target EAS is the EAS corresponding to the first target EES.

22. The method according to claim 19 or 20, characterized in that The first EES is a first source EES, and the second EES is a second source EES; the first request message includes a service area of ​​the second target EAS corresponding to the second target EES selected by the second source EES; The determining that a service area of ​​the first target EAS and a service area of ​​the second target EAS have a common area includes: According to the service area of ​​the second target EAS and the service area of ​​the first target EAS, it is determined that there is a common area between the service area of ​​the first target EAS and the service area of ​​the second target EAS, and the first target EAS is the EAS corresponding to the first target EES selected by the first source EES.

23. The method according to claim 21 or 22, characterized in that The method further comprises: The first indication information is sent to the first target EES.

24. The method according to claim 19 or 20, characterized in that The first EES is a first target EES, and the second EES is a second target EES; the first target EES corresponds to the first target EAS, and the second target EES corresponds to the second target EAS, the first request message includes a service area of ​​the second target EES, and the service area of ​​the second target EES is the same as the service area of ​​the EAS corresponding to the second target EES; The determining that a service area of ​​the first target EAS and a service area of ​​the second target EAS have a common area includes: According to the service areas of the second target EES and the first target EES, it is determined that there is a common area between the service areas of the first target EAS and the second target EAS, and the service area of ​​the first target EES is the same as the service area of ​​the EAS corresponding to the first target EES.

25. The method according to claim 19 or 20, characterized in that The first EES is a first target EES, and the second EES is a second target EES; the first target EES corresponds to the first target EAS, and the second target EES corresponds to the second target EAS, and the first request message includes a service area of ​​the second target EAS corresponding to the second target EES; The determining that a service area of ​​the first target EAS and a service area of ​​the second target EAS have a common area includes: According to the service area of ​​the second target EAS and the service area of ​​the first target EAS, it is determined that there is a common area between the service area of ​​the first target EAS and the service area of ​​the second target EAS, and the first target EAS is the EAS corresponding to the first target EES.

26. The method according to claim 24 or 25, characterized in that The method further comprises: The first indication information is sent to the first target EAS.

27. A communication device, applied to an edge enabled client EEC, characterized in that: include: A processing unit, configured to determine that service areas of at least two target edge application servers EAS have a common area, wherein the at least two target EAS are EASs corresponding to the first application; The transceiver unit is used to send first indication information, where the first indication information is used to indicate at least one of the following: used to indicate that the at least two target EASs need to coordinate application context migration; or to indicate that there is a common area in the service areas of the at least two target EASs.

28. A communication device, characterized in that: Including processors; The processor is coupled to a memory; The memory is used to store instructions; The processor is used to execute the instruction so that the method according to any one of claims 1 to 8 is executed; or, The processor is configured to execute the instructions so that the method according to claim 9 is performed; or The processor is used to execute the instruction so that the method according to any one of claims 10 to 13 is executed; or The processor is used to execute the instruction so that the method according to any one of claims 14 to 18 is executed; or The processor is configured to execute the instructions so that the method according to any one of claims 19 to 26 is performed.

29. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store a computer program, and when the computer program is executed, the method described in any one of claims 1 to 8 is executed; or, when the computer program is executed, the method described in claim 9 is executed; or, when the computer program is executed, the method described in any one of claims 10 to 13 is executed; or, when the computer program is executed, the method described in any one of claims 14 to 18 is executed; or, when the computer program is executed, the method described in any one of claims 19 to 26 is executed.

Images