Method and apparatus for migrating context

Abstract

The present application provides a method and apparatus for migrating context. The method for migrating context includes: obtaining application context migration (ACR) mode information, where the ACR mode information is used to determine the ACR method selected by at least one application, and performing an ACR process for a first application among the at least one application according to the ACR mode information. The method for migrating context performs the ACR process according to the ACR mode information, which can avoid repeated triggering of the ACR process on the premise of saving signaling overhead.

Description

[0001] This application claims the priority of the Chinese patent application with the application number 202110714098.7 and the application title "Method and Device for Migrating Context" filed with the Chinese Patent Office on June 25, 2021, the entire content of which is incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technologies, and more particularly, to a method and device for migrating context. Background Art

[0003] Multiple functional entities in an edge data network can all detect and initiate an application context relocation (ACR) process. To avoid multiple functional entities initiating the ACR process, which may result in multiple ACR processes being executed for the same application, currently, one solution is that an edge enabler server (EES) provides an in-progress indication, which is used to indicate to other detecting entities that an ACR is currently in progress, thereby avoiding multiple application context migrations.

[0004] However, this solution requires notifying each functional entity one by one that the application context is being migrated, resulting in a large signaling overhead. Therefore, how to avoid repeated triggering of the ACR process while saving signaling overhead has become an urgent problem to be solved. Summary of the Invention

[0005] This application provides a method and device for migrating context, enabling a certain functional entity to execute the ACR process, and avoiding repeated triggering of the ACR process while saving signaling overhead.

[0006] In a first aspect, a method for migrating context is provided. The method for migrating context can be executed by a terminal device, or alternatively, by a chip or circuit disposed in the terminal device. This application does not make any limitation in this regard.

[0007] Exemplarily, the terminal device involved in the first aspect may be an edge enabler client (EEC), that is, the terminal device in the first aspect can be replaced by an EEC.

[0008] The method for migrating context includes:

[0009] Obtain application context relocation (ACR) mode information; determine the ACR method selected by at least one application according to the ACR mode information.

[0010] The method for migrating context provided by the embodiments of the present application can execute the ACR process according to the ACR mode information, without indicating whether the ACR process of a certain application is currently being executed through indication information, and can avoid repeatedly triggering the ACR process of a certain application on the premise of saving signaling overhead.

[0011] In combination with the first aspect, in some implementation manners of the first aspect, the ACR mode information includes ACR rule information, and the ACR rule information includes condition information for triggering the ACR process of at least one application; when the first condition indicated by the condition information is satisfied, the ACR process for the first application among the at least one application is executed; the condition information also indicates at least one of the following conditions: a second condition, a third condition, and a fourth condition, where when the second condition is satisfied, it indicates that the application client AC executes the ACR process for the second application among the at least one application; when the third condition is satisfied, it indicates that the edge application server EAS executes the ACR process for the third application among the at least one application; when the fourth condition is satisfied, it indicates that the edge enabling server EES executes the ACR process for the fourth application among the at least one application.

[0012] The method for migrating context provided by the embodiments of the present application executes the ACR process according to the ACR rule information, without indicating whether the ACR process of the first application is currently being executed through indication information, and can avoid repeatedly triggering the ACR process of the first application on the premise of saving signaling overhead.

[0013] In combination with the first aspect, in some implementation manners of the first aspect, obtaining the ACR mode information includes: receiving the ACR mode information from the application client AC; or, receiving the ACR mode information from the edge enabling server EES and / or the edge configuration server ECS; or, formulating the ACR mode information according to the second information, the third information, and the fourth information.

[0014] The method for migrating context provided by the embodiments of the present application can obtain the above ACR mode information through different methods, improving the flexibility of the solution.

[0015] In combination with the first aspect, in some implementation manners of the first aspect,

[0016] Receiving the ACR mode information from the AC, the method further includes: sending the ACR mode information to the edge enabling server EES;

[0017] Receiving the ACR mode information from the EES and / or the ECS, the method further includes: sending the ACR mode information to the AC;

[0018] Formulate ACR mode information according to the second information, the third information, and the fourth information. The method further includes:

[0019] Receive the second information from the EAS. The second information includes the ACR capability information supported by the EAS and / or the second ACR method request information. The ACR capability information supported by the EAS indicates the capabilities of the EAS, and the second ACR method request information is used to request the allocation of an ACR method for the EAS.

[0020] Receive the third information from the AC. The third information includes the ACR capability information supported by the AC and / or the third ACR method request information. The ACR capability information supported by the AC indicates the capabilities of the AC, and the third ACR method request information is used to request the allocation of an ACR method for the AC.

[0021] Receive the fourth information from the EES. The fourth information includes the ACR capability information supported by the EES and / or the fourth ACR method request information. The ACR capability information supported by the EES indicates the capabilities of the EES, and the fourth ACR method request information is used to request the allocation of an ACR method for the EES.

[0022] Send the ACR mode information to the AC, the EES, or the ECS.

[0023] The method for migrating context provided by the embodiments of the present application can send the ACR mode information to other functional entities that require the ACR mode information, so that other functional entities can also execute the ACR process based on the ACR mode information, without the need to indicate whether the ACR process of a certain application is currently being executed through indication information, which can avoid repeated triggering of the ACR process while saving signaling overhead.

[0024] In combination with the first aspect, in some implementation manners of the first aspect, the ACR rule information includes: the correspondence between the application type and the device for executing the ACR process of the application belonging to the application type, and / or, the correspondence between the event information of the process for triggering the ACR and the device for executing the preset ACR process.

[0025] The above ACR rule information can specifically be for ACR events (such as UE mobility, EAS overload) or for application types, and allocate the events or application types that need to be detected and executed by each functional entity (such as AC, EAS, EES, or EEC). That is to say, the ACR rule information can specify different ACR trigger rules, improving the flexibility of the solution.

[0026] In combination with the first aspect, in some implementations of the first aspect, the ACR mode information indicates the identifier of the application client and the ACR method determined by the server for the application client, where the server is one of an edge-enabled client (EEC), an edge configuration server (ECS), an edge-enabled server (EES), or an edge application server (EAS). The above ACR mode information may specifically be the identifier of the application client and the ACR method selected by the server, and different ACR methods may be specified for different applications.

[0027] In combination with the first aspect, in some implementations of the first aspect, before obtaining the ACR mode information, the method further includes: sending a first message to the edge-enabled server (EES) or the edge configuration server (ECS), where the first message is used to indicate at least one of the following: ACR capability information supported by the application client for AC, ACR capability information supported by the edge-enabled client (EEC) for AC, a request to allocate an ACR method for the AC, and a request to allocate an ACR method for the EEC. In combination with the first aspect, in some implementations of the first aspect, the method further includes: receiving the ACR capability information supported by the AC from the AC, and / or, a third ACR method request message, where the first message further includes the ACR capability information supported by the AC, and / or, the third ACR method request message, where the ACR capability information supported by the AC indicates the capability of the AC, and the third ACR method request message is used to request to allocate an ACR method for the AC.

[0028] In a second aspect, a method for migrating context is provided. The method for migrating context may be executed by the EES, or may also be executed by a chip or circuit disposed in the EES. This application does not make any limitations in this regard.

[0029] The method for migrating context includes:

[0030] The edge-enabled server (EES) obtains application context migration ACR mode information, where the ACR mode information is used to determine the ACR method selected by at least one application; the EES sends the ACR mode information to the edge application server (EAS).

[0031] For the method for migrating context provided by the embodiments of this application, the EES executes the ACR process according to the ACR mode information, without the need to indicate whether the ACR process of a certain application is currently being executed through an indication message, and can avoid repeatedly triggering the ACR process of a certain application on the premise of saving signaling overhead.

[0032] In combination with the second aspect, in some implementations of the second aspect, the method further includes: the EES sends the ACR mode information to the edge-enabled client (EEC).

[0033] In combination with the second aspect, in some implementations of the second aspect, the ACR mode information includes ACR rule information, and the ACR rule information includes condition information for triggering the ACR process of at least one application; when the fourth condition indicated by the condition information is met, the EES executes the ACR process for a fourth application among the at least one application.

[0034] For the method for migrating context provided by the embodiments of the present application, the EES executes the ACR process according to the ACR rule information, without the need to indicate whether the ACR process of the fourth application is currently being executed by an indication message, which can avoid repeatedly triggering the ACR process of the fourth application on the premise of saving signaling overhead.

[0035] In combination with the second aspect, in some implementations of the second aspect, the EES obtaining the ACR mode information includes: the EES obtains the ACR mode information according to at least one of the following information: ACR capability information supported by the edge application server EAS, ACR capability information supported by the EEC, ACR capability information supported by the application client AC, and ACR capability information supported by the EES; or, the EES obtains the ACR mode information from the configuration file of the EES, and the configuration file of the EES includes the ACR mode information; or, the EES receives the ACR mode information from the ECS; wherein, the ACR capability information supported by the EAS is used to indicate the third condition corresponding to the ACR process supported by the EAS, the ACR capability information supported by the edge enabling client EEC is used to indicate the first condition corresponding to the ACR process supported by the edge enabling client EEC, the ACR capability information supported by the AC is used to indicate the second condition corresponding to the ACR process supported by the AC, the ACR capability information supported by the EES is used to indicate the fourth condition corresponding to the ACR process supported by the EES, and the condition information further indicates at least one of the following conditions: the second condition, the third condition, and the first condition, wherein when the second condition is met, it indicates that the AC executes the ACR process for a second application among at least one application; when the third condition is met, it indicates that the EAS executes the ACR process for a third application among at least one application; when the first condition is met, it indicates that the EEC executes the ACR process for a first application among at least one application.

[0036] In combination with the second aspect, in some implementations of the second aspect, the ACR mode information indicates the identity of the application client and the ACR method determined by the server for the application client, where the server is one of an edge-enabled client (EEC), an edge configuration server (ECS), an edge-enabled server (EES), or an edge application server (EAS). In combination with the second aspect, in some implementations of the second aspect, the EES obtaining the ACR mode information includes: the EES formulating the ACR mode information according to the second information and the first information, where the second information includes the ACR capability information supported by the EAS, and / or, the second ACR method request information; the first information includes at least one of the ACR capability information supported by the AC, the ACR capability information supported by the EEC, the first ACR method request information, or the third ACR method request information. The ACR capability information supported by the EAS indicates the capability of the EAS, the second ACR method request information is used to request an ACR method to be allocated to the EAS, the ACR capability information supported by the AC indicates the capability of the AC, the third ACR method request information is used to request an ACR method to be allocated to the AC, the ACR capability information supported by the EEC indicates the capability of the EEC, and the first ACR method request information is used to request an ACR method to be allocated to the EEC.

[0037] In combination with the second aspect, in some implementations of the second aspect, the method further includes: the EES receiving the second information from the EAS; the EES receiving the first information from the EEC.

[0038] In combination with the second aspect, in some implementations of the second aspect, the method further includes: the EES sending the ACR mode information to the EAS or the EEC.

[0039] In combination with the second aspect, in some implementations of the second aspect, the method further includes: the EES sending a fifth information to the ECS, where the fifth information includes at least one of the ACR capability information supported by the EES, the ACR capability information supported by the EAS, the fourth ACR method request information, or the second ACR method request information. The ACR capability information supported by the EES indicates the capability of the EES, the fourth ACR method request information is used to request an ACR method to be allocated to the EES, the ACR capability information supported by the EAS indicates the capability of the EAS, and the second ACR method request information is used to request an ACR method to be allocated to the EAS.

[0040] In combination with the second aspect, in some implementations of the second aspect, the method further includes: the EES sending a fourth information to the EEC, where the fourth information includes the ACR capability information supported by the EES, and / or, the fourth ACR method request information. The ACR capability information supported by the EES indicates the capability of the EES, and the fourth ACR method request information is used to request an ACR method to be allocated to the EES

[0041] In combination with the second aspect, in some implementations of the second aspect, the EES obtaining the ACR mode information includes: the EES receiving the ACR mode information from the edge application server EAS and / or the EEC.

[0042] For the method for migrating context provided by the embodiments of the present application, the EES can obtain the above-mentioned ACR mode information in different ways, improving the flexibility of the solution.

[0043] In combination with the second aspect, in some implementations of the second aspect, the method further includes: the EES sending the ACR mode information to the EAS and / or the EEC.

[0044] For the method for migrating context provided by the embodiments of the present application, the EEC can send the ACR mode information to other functional entities that need the ACR mode information, so that other functional entities can also execute the ACR process based on the ACR mode information, without the need to indicate whether the ACR process of a certain application is currently being executed through indication information, and can avoid repeatedly triggering the ACR process on the premise of saving signaling overhead.

[0045] In combination with the second aspect, in some implementations of the second aspect, the ACR rule information includes: the correspondence between the application type and the device for executing the ACR process of the application belonging to the application type, and / or, the correspondence between the event information of the process for triggering the ACR and the device for executing the preset ACR process.

[0046] The above-mentioned ACR rule information can specifically be for ACR events (such as UE mobility, EAS overload) or for application types, allocating the events or application types that each functional entity (such as AC, EAS, EES or EEC) needs to detect and execute ACR, or specifying different ACR methods for different applications. That is to say, the ACR rule information can stipulate different ACR triggering rules, improving the flexibility of the solution.

[0047] In combination with the second aspect, in some implementations of the second aspect, the ACR mode information includes the identification information of at least one application and the ACR method selected by the server, where the server is one of the edge configuration server ECS, the edge enabling server EES or the edge application server EAS.

[0048] The above-mentioned ACR mode information can specifically be the identification information of the application and the ACR method selected by the server, and different ACR methods can be specified for different applications.

[0049] In a third aspect, a method for migrating context is provided. The method for migrating context may be executed by an application client (AC), or may be executed by a chip or circuit disposed in the AC. This application does not make any limitations in this regard.

[0050] The method for migrating context includes:

[0051] The application client AC obtains application context migration ACR mode information; the application client AC determines an ACR method selected by at least one application according to the ACR mode information.

[0052] In the method for migrating context provided by the embodiments of this application, the AC executes the ACR process according to the ACR mode information, and there is no need to use indication information to indicate whether the ACR process of a certain application of the AC is currently being executed. It is possible to avoid repeatedly triggering the ACR process of a certain application while saving signaling overhead.

[0053] In combination with the third aspect, in some implementation manners of the third aspect, the ACR mode information includes ACR rule information, and the ACR rule information includes condition information for triggering the ACR process of at least one application; when a second condition indicated by the condition information is satisfied, the AC executes the ACR process for a second application among the at least one application.

[0054] In the method for migrating context provided by the embodiments of this application, the AC executes the ACR process according to the ACR rule information, and there is no need to use indication information to indicate whether the ACR process of the second application of the AC is currently being executed. It is possible to avoid repeatedly triggering the ACR process of the second application while saving signaling overhead.

[0055] In combination with the third aspect, in some implementation manners of the third aspect, the AC obtaining the ACR mode information includes: the AC obtains the ACR mode information from a configuration file of the AC, and the configuration file of the AC includes the ACR mode information; or the AC receives the ACR mode information from an edge enabling client (EEC); the condition information further indicates at least one of the following conditions: a first condition, a third condition, and a fourth condition, where when the first condition is satisfied, it indicates that the EEC executes the ACR process for a first application among at least one application; when the third condition is satisfied, it indicates that an edge application server (EAS) executes the ACR process for a third application among at least one application; when the fourth condition is satisfied, it indicates that an edge enabling server (EES) executes the ACR process for a fourth application among at least one application.

[0056] In the method for migrating context provided by the embodiments of this application, the AC can obtain the above ACR mode information through different methods, improving the flexibility of the solution.

[0057] In combination with the third aspect, in some implementation manners of the third aspect, when the AC obtains the ACR mode information from the configuration file of the AC, the method further includes: the AC sending the ACR mode information to the EEC.

[0058] In the method for migrating context provided by the embodiments of the present application, the AC can send the ACR mode information to other functional entities that need the ACR mode information, so that other functional entities can also execute the ACR process based on the ACR mode information, without the need to indicate whether the ACR process of a certain application is currently being executed through an indication message, which can avoid repeated triggering of the ACR process while saving signaling overhead.

[0059] In combination with the third aspect, in some implementation manners of the third aspect, the ACR rule information includes: the correspondence between the application type and the device for executing the ACR process of the application belonging to the application type, and / or, the correspondence between the event information of the process for triggering the ACR and the device for executing the preset ACR process.

[0060] The above ACR rule information can specifically be for ACR events (such as UE mobility, EAS overload) or for application types, and allocate the events or application types that need to be detected and executed by each functional entity (such as AC, EAS, EES or EEC). That is to say, the ACR rule information can specify different ACR triggering rules, improving the flexibility of the solution.

[0061] In combination with the third aspect, in some implementation manners of the third aspect, the ACR mode information indicates the identifier of the application client and the ACR method determined by the server for the application client, where the server is one of the edge enabled client EEC, the edge configuration server ECS, the edge enabled server EES or the edge application server EAS. The above ACR mode information can specifically be the identifier information of the application and the ACR method selected by the server, and different ACR methods can be specified for different applications.

[0062] In combination with the third aspect, in some implementation manners of the third aspect, the method further includes: the AC sending third information to the EEC, where the third information includes the ACR capability information supported by the AC, and / or, the third ACR method request information, where the ACR capability information supported by the AC indicates the capability of the AC, and the third ACR method request information is used to request an ACR method to be allocated to the AC.

[0063] Fourthly, a method for migrating context is provided. The method for migrating context can be executed by an edge application server (EAS), or can be executed by a chip or circuit disposed in the EAS. This application does not make any limitation in this regard.

[0064] The method for migrating context includes:

[0065] The edge application server EAS obtains application context migration (ACR) mode information; the edge application server EAS determines the ACR method and options selected by at least one application according to the ACR mode information.

[0066] In the method for migrating context provided by the embodiments of this application, the EAS executes the ACR process according to the ACR mode information, without using indication information to indicate whether the ACR process of a certain application is currently being executed by the EAS. It can avoid repeatedly triggering the ACR process of a certain application while saving signaling overhead.

[0067] In combination with the fourth aspect, in some implementation manners of the fourth aspect, the ACR mode information includes ACR rule information, and the ACR rule information includes condition information for triggering the ACR process of at least one application; when the third condition indicated by the condition information is satisfied, the EAS executes the ACR process for a third application among the at least one application.

[0068] In the method for migrating context provided by the embodiments of this application, the EAS executes the ACR process according to the ACR rule information, without using indication information to indicate whether the ACR process of the third application is currently being executed by the EAS. It can avoid repeatedly triggering the ACR process of the third application while saving signaling overhead.

[0069] In combination with the fourth aspect, in some implementation manners of the fourth aspect, the EAS obtaining the ACR mode information includes: the EAS obtains the ACR mode information from the configuration file of the EAS, and the ACR mode information is included in the configuration file of the EAS; or the EAS receives the ACR mode information from an edge enablement server (EES); the condition information further indicates at least one of the following conditions: a second condition, a first condition, and a fourth condition, where when the second condition is satisfied, it indicates that an application client (AC) executes the ACR process for a second application among the at least one application; when the first condition is satisfied, it indicates that an edge execution client (EEC) executes the ACR process for a first application among the at least one application; when the fourth condition is satisfied, it indicates that the EES executes the ACR process for a fourth application among the at least one application.

[0070] In combination with the fourth aspect, in some implementations of the fourth aspect, the EAS obtains the ACR mode information including: the EAS formulates the ACR mode information according to the first information, the third information, and the fifth information.

[0071] In combination with the fourth aspect, in some implementations of the fourth aspect, the method further includes:

[0072] Receiving first information from the EEC, the first information includes at least one of the ACR capabilities supported by the AC, the ACR capabilities supported by the EEC, the first ACR method request information, or the third ACR method request information. The ACR capabilities supported by the AC indicate the capabilities of the AC, and the third ACR method request information is used to request the allocation of an ACR method for the AC. The ACR capabilities supported by the EEC indicate the capabilities of the EEC, and the first ACR method request information is used to request the allocation of an ACR method for the EEC;

[0073] Receiving third information from the AC, the third information includes the ACR capabilities supported by the AC, and / or the third ACR method request information, where the ACR capabilities supported by the AC indicate the capabilities of the AC, and the third ACR method request information is used to request the allocation of an ACR method for the AC;

[0074] Receiving fifth information from the EES, the fifth information includes at least one of the ACR capabilities supported by the EES, the ACR capabilities supported by the EAS, the fourth ACR method request information, or the second ACR method request information. The ACR capabilities supported by the EES indicate the capabilities of the EES, the fourth ACR method request information is used to request the allocation of an ACR method for the EES, the ACR capabilities supported by the EAS indicate the capabilities of the EAS, and the second ACR method request information is used to request the allocation of an ACR method for the EAS;

[0075] Sending the ACR mode information to the AC, the EES, or the EEC.

[0076] For the method for migrating context provided by the embodiments of the present application, the EAS can obtain the above ACR mode information in different ways, improving the flexibility of the solution.

[0077] In combination with the fourth aspect, in some implementations of the fourth aspect, when the EAS obtains the ACR mode information from the configuration file of the EAS, the method further includes: the EAS sends the ACR mode information to the EES.

[0078] In the method for migrating context provided by the embodiments of the present application, the EAS can send the ACR mode information to other functional entities that require the ACR mode information, so that other functional entities can also execute the ACR process based on the ACR mode information, without indicating whether the ACR process of a certain application is currently being executed through indication information, which can avoid repeated triggering of the ACR process on the premise of saving signaling overhead.

[0079] In combination with the fourth aspect, in some implementation manners of the fourth aspect, the ACR rule information includes: the correspondence between the application type and the device for executing the ACR process of the application belonging to the application type, and / or, the correspondence between the event information of the process for triggering the ACR and the device for executing the preset ACR process.

[0080] The above ACR rule information can specifically be for ACR events (such as UE mobility, EAS overload) or for application types, and allocate the events or application types that each functional entity (such as AC, EAS, EES, or EEC) needs to detect and execute ACR. That is to say, the ACR rule information can specify different ACR triggering rules, improving the flexibility of the solution.

[0081] In combination with the fourth aspect, in some implementation manners of the fourth aspect, the ACR mode information indicates the identifier of the application client and the ACR method determined by the server for the application client, where the server is one of the edge-enabled client EEC, the edge configuration server ECS, the edge-enabled server EES, or the edge application server EAS. The above ACR mode information can specifically be the identifier information of the application and the ACR method selected by the server, and different ACR methods can be specified for different applications.

[0082] In combination with the fourth aspect, in some implementation manners of the fourth aspect, the method further includes: the EAS sends a second message to the EEC, and the second message includes the ACR capability information supported by the EAS, and / or, the second ACR method request information, where the ACR capability information supported by the EAS indicates the capability of the EAS, and the second ACR method request information is used to request to allocate an ACR method for the EAS.

[0083] In a fifth aspect, a method for migrating context is provided. The method for migrating context can be executed by the ECS, or can also be executed by a chip or circuit disposed in the ECS. The present application does not make any limitation in this regard.

[0084] The method for migrating context includes:

[0085] Obtain application context migration ACR mode information from the Edge Configuration Server (ECS); the ECS determines the ACR method selected by at least one application according to the ACR mode information.

[0086] In combination with the fifth aspect, in some implementation manners of the fifth aspect, the ACR mode information includes ACR rule information, and the ACR rule information includes condition information for triggering the ACR process of at least one application. The method further includes: the ECS formulates the application context migration ACR mode information, and the condition information indicates at least one of the following conditions: a first condition, a second condition, a third condition, and a fourth condition. When the first condition is satisfied, it indicates that the EEC executes the ACR process for a first application among at least one application; when the second condition is satisfied, it indicates that the application client AC executes the ACR process for a second application among at least one application; when the third condition is satisfied, it indicates that the Edge Application Server (EAS) executes the ACR process for a third application among at least one application; when the fourth condition is satisfied, it indicates that the Edge Enablement Server (EES) executes the ACR process for a fourth application among at least one application; the ECS sends the ACR mode information to the EEC and the EES respectively.

[0087] For the method for migrating context provided by the embodiments of the present application, the ECS can formulate and send the ACR mode information to the functional entity capable of executing the ACR process, so that the functional entity executes the ACR process according to the ACR mode information, without indicating whether the ACR process of a certain application is currently being executed through indication information, and can avoid repeatedly triggering the ACR process of the application while saving signaling overhead.

[0088] In combination with the fifth aspect, in some implementation manners of the fifth aspect, the ECS obtaining the ACR mode information includes: the ECS formulates the ACR mode information according to the first information, the second information, and the fifth information.

[0089] In combination with the fifth aspect, in some implementation manners of the fifth aspect, the method further includes:

[0090] The ECS receives the first information from the EEC, and the first information includes at least one of the ACR capabilities supported by the AC, the ACR capabilities supported by the EEC, the first ACR method request information, or the third ACR method request information. The ACR capabilities supported by the AC indicate the capabilities of the AC, the third ACR method request information is used to request an ACR method to be allocated to the AC, the ACR capabilities supported by the EEC indicate the capabilities of the EEC, and the first ACR method request information is used to request an ACR method to be allocated to the EEC;

[0091] The ECS receives second information from the EAS. The second information includes ACR capability information supported by the EAS and / or second ACR method request information. The ACR capability information supported by the EAS indicates the capabilities of the EAS, and the second ACR method request information is used to request the allocation of an ACR method for the EAS.

[0092] The ECS receives fifth information from the EES. The fifth information includes at least one of the following: ACR capability information supported by the EES, ACR capability information supported by the EAS, fourth ACR method request information, or second ACR method request information. The ACR capability information supported by the EES indicates the capabilities of the EES, the fourth ACR method request information is used to request the allocation of an ACR method for the EES, the ACR capability information supported by the EAS indicates the capabilities of the EAS, and the second ACR method request information is used to request the allocation of an ACR method for the EAS.

[0093] Send the ACR mode information to the EAS, the EES, or the EEC.

[0094] In a sixth aspect, a device for context migration is provided. The device for context migration includes a processor for implementing the functions of the terminal device (or the EEC) in the method described in the first aspect above.

[0095] In a possible implementation, the device for context migration may further include a memory coupled to the processor. The processor is used to implement the functions of the terminal device in the method described in the first aspect above.

[0096] In a possible implementation, the memory is used to store program instructions and data. The memory is coupled to the processor, and the processor can call and execute the program instructions stored in the memory to implement the functions of the terminal device in the method described in the first aspect above.

[0097] In a possible implementation, the device for context migration may further include a communication interface for communicating between the device for context migration and other devices. The communication interface can be a transceiver, an input / output interface, or a circuit, etc.

[0098] In a possible design, the device for context migration includes a processor and a communication interface.

[0099] The processor communicates with the outside using the communication interface.

[0100] The processor is used to run a computer program so that the device for context migration implements any of the methods described in the first aspect above.

[0101] It can be understood that the external entity can be an object other than the processor, or an object outside the device.

[0102] In another possible design, the device for context migration is a chip or a chip system. The communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The processor can also be embodied as a processing circuit or a logic circuit.

[0103] In a seventh aspect, a device for context migration is provided. The device for context migration includes a processor for implementing the function of AC in the method described in the above third aspect.

[0104] In a possible implementation, the device for context migration may further include a memory coupled to the processor, and the processor is used to implement the function of AC in the method described in the above third aspect.

[0105] In a possible implementation, the memory is used to store program instructions and data. The memory is coupled to the processor, and the processor can call and execute the program instructions stored in the memory to implement the function of AC in the method described in the above third aspect.

[0106] In a possible implementation, the device for context migration may further include a communication interface for the device for context migration to communicate with other devices. The communication interface can be a transceiver, input / output interface, or circuit, etc.

[0107] In a possible design, the device for context migration includes: a processor and a communication interface,

[0108] The processor communicates with the external entity using the communication interface;

[0109] The processor is used to run a computer program so that the device for context migration implements any of the methods described in the above third aspect.

[0110] It can be understood that the external entity can be an object other than the processor, or an object outside the device.

[0111] In another possible design, the device for context migration is a chip or a chip system. The communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The processor can also be embodied as a processing circuit or a logic circuit.

[0112] In an eighth aspect, a device for migrating context is provided. The device for migrating context includes a processor configured to implement the function of EAS in the method described in the fourth aspect above.

[0113] In a possible implementation, the device for migrating context may further include a memory coupled to the processor, and the processor is configured to implement the function of EAS in the method described in the fourth aspect above.

[0114] In a possible implementation, the memory is used to store program instructions and data. The memory is coupled to the processor, and the processor can call and execute the program instructions stored in the memory to implement the function of EAS in the method described in the fourth aspect above.

[0115] In a possible implementation, the device for migrating context may further include a communication interface configured to communicate the device for migrating context with other devices. The communication interface can be a transceiver, an input / output interface, or a circuit, etc.

[0116] In a possible design, the device for migrating context includes: a processor and a communication interface,

[0117] The processor communicates with the outside using the communication interface;

[0118] The processor is configured to run a computer program so that the device for migrating context implements any of the methods described in the fourth aspect above.

[0119] It can be understood that the outside can be an object other than the processor or an object outside the device.

[0120] In another possible design, the device for migrating context is a chip or a chip system. The communication interface can be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or a related circuit, etc. on the chip or chip system. The processor can also be embodied as a processing circuit or a logic circuit.

[0121] In a ninth aspect, a device for migrating context is provided. The device for migrating context includes a processor configured to implement the function of ECS in the method described in the fifth aspect above.

[0122] In a possible implementation, the device for migrating context may further include a memory coupled to the processor, and the processor is configured to implement the function of ECS in the method described in the fifth aspect above.

[0123] In a possible implementation, the memory is used to store program instructions and data. The memory is coupled to the processor, and the processor can call and execute the program instructions stored in the memory to implement the function of ECS in the method described in the fifth aspect above.

[0124] In a possible implementation manner, the apparatus for migrating context may further include a communication interface, and the communication interface is used for the apparatus for migrating context to communicate with other devices. The communication interface may be a transceiver, an input / output interface, a circuit, etc.

[0125] In a possible design, the apparatus for migrating context includes: a processor and a communication interface,

[0126] The processor communicates with the outside through the communication interface;

[0127] The processor is used to run a computer program so that the apparatus for migrating context implements any of the methods described in the fifth aspect above.

[0128] It can be understood that the outside may be an object other than the processor or an object outside the apparatus.

[0129] In another possible design, the apparatus for migrating context is a chip or a chip system. The communication interface may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or a related circuit, etc. on the chip or the chip system. The processor may also be embodied as a processing circuit or a logic circuit.

[0130] In a tenth aspect, the present application provides a computer-readable storage medium, and instructions are stored in the computer-readable storage medium. When it runs on a computer, it causes the computer to execute the methods in the above aspects.

[0131] In an eleventh aspect, the present application provides a computer program product containing instructions. When it runs on a computer, it causes the computer to execute the methods in the above aspects.

[0132] In a twelfth aspect, a communication system is provided, including the apparatus for migrating context shown in the sixth aspect to the apparatus for migrating context shown in the tenth aspect.

[0133] In a thirteenth aspect, a user equipment is provided, including the apparatus for migrating context shown in the sixth aspect and the apparatus for migrating context shown in the eighth aspect.

[0134] In a fourteenth aspect, a chip or a chip system is provided. The chip or the chip system includes at least one processor and a communication interface. The communication interface and the at least one processor are interconnected by a line. The at least one processor is configured to run a computer program or instruction to perform the method in any one of the possible implementation manners of the first aspect to the fifth aspect. Among them, the communication interface in the chip may be an input / output interface, a pin, a circuit, or the like.

[0135] In a possible implementation, the chip or the chip system described above in this application further includes at least one memory, and instructions are stored in the at least one memory. The memory may be a storage unit inside the chip, such as a register, a cache, etc., or may be a storage unit of the chip (such as a read-only memory, a random access memory, etc.). BRIEF DESCRIPTION OF THE DRAWINGS

[0136] Figure 1 is a schematic diagram of a system architecture applicable to an embodiment of this application.

[0137] Figure 2 is an implementation manner of application context migration.

[0138] Figure 3 In (a) is a schematic diagram of a service activation process; Figure 3 In (b) is a schematic diagram of an EEC registration process;

[0139] Figure 3 In (c) is a schematic diagram of an EAS registration process.

[0140] Figure 4 In (a) is a schematic diagram of a conventional EAS discovery process; Figure 4 In (b) is a schematic diagram of an AC information subscription process; Figure 4 In (c) is a schematic diagram of an AC information notification process.

[0141] Figure 5 is another implementation manner of application context migration.

[0142] Figure 6 is another implementation manner of application context migration.

[0143] Figure 7 is another implementation manner of application context migration.

[0144] Figure 8 is another implementation manner of application context migration.

[0145] Figure 9 is another implementation manner of application context migration.

[0146] Figure 10FIG. 0 is a schematic flowchart of a method for migrating context provided by the present application.

[0147] Figure 11 Among them, (a) in FIG. 4 is a schematic flowchart of another method for migrating context provided by the present application; Figure 11 Among them, (b) in FIG. 6 is a schematic flowchart of yet another method for migrating context provided by the present application.

[0148] Figure 12 FIG. 10 is a schematic flowchart of yet another method for migrating context provided by the present application.

[0149] Figure 13 FIG. 14 is a schematic flowchart of another method for migrating context provided by the present application.

[0150] Figure 14 FIG. 18 is a schematic diagram of an apparatus 1400 for migrating context provided by the present application.

[0151] Figure 15 FIG. 22 is a schematic structural diagram of an EEC 1500 applicable to an embodiment of the present application.

[0152] Figure 16 FIG. 26 is a schematic diagram of an apparatus 1600 for migrating context provided by the present application.

[0153] Figure 17 FIG. 30 is a schematic structural diagram of an EES 1700 applicable to an embodiment of the present application.

[0154] Figure 18 FIG. 34 is a schematic diagram of an apparatus 1800 for migrating context provided by the present application.

[0155] Figure 19 FIG. 38 is a schematic structural diagram of an AC 1900 applicable to an embodiment of the present application.

[0156] Figure 20 FIG. 42 is a schematic diagram of an apparatus 2000 for migrating context provided by the present application.

[0157] Figure 21 FIG. 46 is a schematic structural diagram of an EAS 2100 applicable to an embodiment of the present application.

[0158] Figure 22 FIG. 50 is a schematic diagram of an apparatus 2200 for migrating context provided by the present application.

[0159] Figure 23 FIG. 54 is a schematic structural diagram of an ECS 2300 applicable to an embodiment of the present application. DETAILED DESCRIPTION

[0160] The technical solutions in the present application will be described below with reference to the accompanying drawings.

[0161] Figure 1 is a schematic diagram of the system architecture applicable to the embodiments of the present application. The following will separately describe each part involved in the Figure 1 network architecture shown.

[0162] 1. Edge Data Network (EDN).

[0163] Generally understood, an EDN corresponds to only one data network and is a special local data network (LocalDN), which includes edge enabling functions and can use a data network access identifier (DNAI) and a DNN identifier. It is a network logical concept.

[0164] Another understanding of an EDN: An EDN is a peer concept of the central cloud and can be understood as a local data center (a geographical location concept). It can be identified by a DNAI and can include multiple local data networks (Local DN).

[0165] An EDN includes an Edge Enabler Server (EES) and multiple Edge Application Servers (EAS).

[0166] Among them, the EES can be a control network element or a management network element in a Mobile Edge Computing (MEC) node (MEC can also be referred to as Multi-Access Edge Computing). It is responsible for managing each EAS deployed in this EDN (or understood as providing services for each EAS deployed in this EDN), such as basic functions like registration, Domain Name System (DNS) resolution content routing selection, upper-layer application registration management, and wireless information interaction. In addition, the EES can invoke the capability open function network element in the 3GPP network. It should be understood that the EES network element can be co-located with other network elements or be an independent network element. The present application does not make any restrictions on the deployment of the EES network element in the network architecture. Generally, an EAS registers to an EES, or the information of an EAS is configured on an EES through a management system. This EES is called the EES associated with this EAS, and the EES controls / manages the EAS registered / configured on this EES.

[0167] An EAS can be an application deployed in an edge data network, which is called an application instance. Specifically, it refers to an instance in which a server application program (such as social media software, augmented reality (AR), virtual reality (VR)) is deployed and runs in the EDN. An application can deploy one or more EASs in one or more EDNs. The EASs deployed and running in different EDNs can be regarded as different EASs of an application. They can share a domain name, can use an anycast IP address, or can also use different IP addresses. An EAS can also be called an edge application (server), application instance, edge application instance, MEC application (server), EAS function, etc.

[0168] 2. Edge data network configuration server.

[0169] The edge data network configuration server can be a global management network element and can be called (edge data network configuration server, EDNCS) or edge configuration server (edge configuration server, ECS). For ease of description, in the embodiments of the present application, the edge data network configuration server is taken as an example of ECS for illustration.

[0170] The ECS maintains information about each EDN, including the service scope of the edge data network and the EES address, etc. Among them, the service scope of the edge data network can be topological address information (such as Cell ID, TAI (Trach area id), etc.) or geometric address information (such as province, city, district or longitude and latitude, etc. information), and the service scope can be a set of address information. In one implementation, the ECS network element is distributedly deployed, that is, each ECS can manage the edge data network in different regions. It should be understood that the ECS network element can be co-located with other network elements or can be an independent network element. The present application does not make any limitation on the deployment of the ECS network element in the network architecture.

[0171] 3. User equipment (UE): It can include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem with wireless communication functions, as well as various forms of terminals, mobile stations (mobile station, MS), terminals (terminal) or soft terminals, etc. For example, water meters, electricity meters, sensors, etc.

[0172] Specifically, in Figure 1Under the network architecture shown, the UE may include: an edge enabler client (EEC) and an application client (AC).

[0173] Among them, the application client is the peer entity of the edge application on the UE side. The application client is used for the application user to obtain application services from the application server. The application client is the client program of the application on the terminal side. The application client can connect to the application server in the cloud to obtain application services, or connect to the EAS deployed and running in one or more EDNs to obtain application services.

[0174] The EEC is the peer entity of the EES on the UE side. The EEC is used to register the information of the EEC and the application client with the EES, perform security authentication and authorization, obtain the IP address of the EAS from the EES, and provide edge computing enabling capabilities to the application client. For example, the EAS discovery service returns the IP address of the EAS to the application client.

[0175] The EEC provides necessary support for the application client on the UE. The functions of the EEC include: retrieving EDN information through EDGE-4, registering the UE to the EES, retrieving available EASs, EAS availability change, and notifying the EEC of EAS migration.

[0176] Among them, the application user signs a service agreement with the application provider to provide services for the application user. The application user communicates through the connection between the application client on the login terminal and the EAS. The enabling client is the middleware layer, generally located in the operating system or between the application client and the operating system. The application client can obtain edge enabling services from the enabling client in the form of an application program interface (API).

[0177] Exemplarily, the user equipment in the embodiments of the present application may refer to an access terminal, a user unit, a user station, a mobile station, a mobile device, a relay station, a remote station, a remote terminal, a mobile device, a user terminal (user terminal), a terminal device (terminal equipment), a wireless communication device, a user agent or a user device. The user equipment may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing devices connected to a wireless modem, a vehicle-mounted device, a wearable device, a user equipment in a 5G network, or a user equipment in a future evolved public land mobile network (PLMN), or a user equipment in a future vehicle-to-everything network, etc. The embodiments of the present application do not limit this.

[0178] As an example but not a limitation, in the embodiments of the present application, a wearable device may also be referred to as a wearable intelligent device, which is a general term for devices developed by applying wearable technology to the intelligent design of daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. A wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable intelligent devices include those with complete functions and large sizes that can realize complete or partial functions without relying on a smart phone, such as smart watches or smart glasses, etc., and those that only focus on a certain type of application function and need to cooperate with other devices such as smart phones, such as various smart bracelets and smart jewelry for physical sign monitoring.

[0179] In addition, in the embodiments of the present application, the user equipment may also be a user equipment in an Internet of Things (IoT) system. The IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, so as to realize an intelligent network of human-machine interconnection and thing-thing interconnection. In the embodiments of the present application, IoT technology can achieve massive connection, deep coverage, and low power consumption of terminals through, for example, narrow band (NB) technology. In addition, in the embodiments of the present application, the user equipment may also include sensors such as intelligent printers, train detectors, and gas stations. The main functions include collecting data (for some user equipment), receiving control information and downlink data from access network devices, and sending electromagnetic waves to transmit uplink data to access network devices.

[0180] 2. Fifth Generation (5G) mobile network.

[0181] In the embodiments of the present application, the structure of the 5G network is not limited, and the introduction of the current related technologies can be referred to, including radio access network ((R)AN) devices and 5G core network (5GC).

[0182] Among them, (R)AN is used to provide network access functions for authorized user equipment in a specific area, and can use transmission tunnels of different qualities according to the level of user equipment, service requirements, etc.

[0183] (R)AN can manage radio resources, provide access services for user equipment, and then complete the forwarding of control signals and user equipment data between the user equipment and the core network. (R)AN can also be understood as a base station in a traditional network.

[0184] Exemplarily, the access network device in the embodiments of the present application can be any communication device with wireless transceiver functions for communicating with user equipment. The access network device includes but is not limited to: evolved NodeB (eNB), baseband unit (BBU), access point (AP) in a wireless fidelity (WIFI) system, wireless relay node, wireless backhaul node, transmission point (TP), or transmission and reception point (TRP), etc. It can also be a gNB in a 5G system, such as an NR system, or a transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or it can also be a network node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit (DU), etc.

[0185] In some deployments, the gNB may include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (AAU). The CU implements some functions of the gNB, and the DU implements some functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services, implementing radio resource control (RRC), and the functions of the packet data convergence protocol (PDCP) layer. The DU is responsible for processing physical layer protocols and real-time services, implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer. The AAU implements some physical layer processing functions, radio frequency processing, and related functions of active antennas. Since the information of the RRC layer will ultimately become the information of the PHY layer, or is transformed from the information of the PHY layer, therefore, in this architecture, high-layer signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or sent by the DU + AAU. It can be understood that the access network device can be a device including one or more of the CU node, the DU node, and the AAU node. In addition, the CU can be classified as an access network device in the radio access network (RAN), or the CU can be classified as an access network device in the core network (CN), and this application does not make any limitations on this.

[0186] The 5GC at least includes the following network elements:

[0187] 1), User plane network element: Used for packet routing and forwarding, and quality of service (QoS) processing of user plane data, etc.

[0188] In a 5G communication system, the user plane network element can be a user plane function (UPF) network element. In future communication systems, the user plane network element can still be a UPF network element, or it can also have other names, and this application does not make any limitations on this.

[0189] 2), Access management network element: Mainly used for mobility management and access management, etc., and can be used to implement other functions of the mobility management entity (MME) function except session management, such as access authorization / authentication and other functions.

[0190] In a 5G communication system, the access management network element may be an access and mobility management function (AMF) network element. In future communication systems, the access management network element may still be an AMF network element, or it may have other names, which are not limited in this application.

[0191] 3) Session management network element: mainly used for session management, allocation and management of the Internet Protocol (IP) address of the terminal device, selection of manageable user plane functions, termination points of policy control and charging function interfaces, and downlink data notification, etc.

[0192] In a 5G communication system, the session management network element may be a session management function (SMF) network element. In future communication systems, the session management network element may still be an SMF network element, or it may have other names, which are not limited in this application.

[0193] 4) Policy control network element: a unified policy framework for guiding network behavior, providing policy rule information for network elements (such as AMF, SMF network elements, etc.) or terminal devices.

[0194] In a 4G communication system, the policy control network element may be a policy and charging rules function (PCRF) network element. In a 5G communication system, the policy control network element may be a policy control function (PCF) network element. In future communication systems, the policy control network element may still be a PCF network element, or it may have other names, which are not limited in this application.

[0195] 5) Application network element: used for data routing that affects applications, accessing network open function network elements, and interacting with the policy framework for policy control, etc.

[0196] In a 5G communication system, the application network element may be an application function (AF) network element. In future communication systems, the application network element may still be an AF network element, or it may have other names, which are not limited in this application.

[0197] 6) Network slice selection network element: used to select a network slice instance that serves the user equipment.

[0198] In a 5G communication system, the network slice selection network element may be a network slice selection function (NSSF) network element. In future communication systems, the network slice selection function network element may still be the NSSF network element, or it may have other names, which are not limited in this application.

[0199] 7) Authentication service network element: mainly used for user authentication, etc.

[0200] In a 5G communication system, the authentication service network element may be an authentication server function (AUSF) network element. In future communication systems, the authentication service function network element may still be the AUSF network element, or it may have other names, which are not limited in this application.

[0201] 8) Data management network element: used to process terminal device identification, access authentication, registration, and mobility management, etc.

[0202] In a 5G communication system, the data management network element may be a unified data management (UDM) network element. In future communication systems, the unified data management may still be the UDM network element, or it may have other names, which are not limited in this application.

[0203] It can be understood that the above network elements or functions can be either network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (such as a cloud platform).

[0204] It should be noted that in current standard protocols, such as technical specifications (TS) 23.501, TS 23.502, etc., the above EES network element, EAS network element, and ECS network element, etc. can all be called application function (AF) network elements, which will not be elaborated below.

[0205] In Figure 1 In the network architecture shown, the EDGE-8 reference point supports the interaction between the edge configuration server and the core network, such as supporting: (1) accessing core network functions and application programming interfaces (APIs) for retrieving network capability information; (2) providing service deployment notifications to the core network (such as: SMF). EDGE-1: The interface between the EES and the EEC, supporting the registration / deregistration of the EEC with the EES; discovery of edge application servers in the edge data network.

[0206] EDGE-2: The interface between the EES and the 3GPP core network, which is used for the EES to obtain the 3GPP network capabilities.

[0207] EDGE-3: The interface between the EES and the EAS, which supports the EES to register / deregister the EAS, including the availability information, service scope information, address information, etc. of the EAS; the EES provides the 3GPP network capability information (such as location information) to the EAS.

[0208] EDGE-4: The interface between the EEC and the ECS, which supports the ECS to provide / push configuration information to the EEC.

[0209] EDGE-5: The interface between the AC and the EEC, which supports the AC to obtain the information of the accessed EAS from the EEC.

[0210] EDGE-6: The interface between the ECS and the EES, which supports the configuration of the EES information on the ECS.

[0211] EDGE-7: The interface between the EAS and the 5GC, which supports the EAS to obtain the 5G network capabilities.

[0212] EDGE-8: The interface between the ECS and the 5GC, which supports the ECS to obtain the 5G network capabilities.

[0213] EDGE-9: The interface between different EESs across MEC nodes / within the same MEC node, which supports application migration.

[0214] It should be noted that Figure 1 The names of the various network elements and the communication interfaces between the network elements involved in [description] are simply described by taking the current protocol as an example, but it is not limited that the embodiments of the present application can only be applied to the currently known communication systems. Therefore, the standard names that appear when described by taking the current protocol as an example are all functional descriptions. The present application does not limit the specific names of the network elements, interfaces or signaling, etc., and only represents the functions of the network elements, interfaces or signaling, which can be correspondingly extended to other systems, such as 4G or future communication systems.

[0215] For the convenience of understanding the embodiments of the present application, several basic concepts involved in the embodiments of the present application are simply described. It should be understood that the basic concepts introduced below are simply described by taking the basic concepts specified in the current protocol as an example, but it is not limited that the embodiments of the present application can only be applied to the existing systems currently. Therefore, the names that appear when described by taking the existing systems currently as an example are all functional descriptions, and the specific names are not limited, and only represent the functions, which can be correspondingly extended to other systems, such as 4G or future communication systems.

[0216] 1. MEC.

[0217] The MEC can use the radio access network to provide the services required by the IT of telecom users and cloud computing functions nearby, thus creating a carrier-grade service environment with high performance, low latency, and high bandwidth, accelerating the rapid download of various contents, services, and applications in the network, and enabling consumers to enjoy an uninterrupted high-quality network experience.

[0218] 2. Data network.

[0219] A data network (DN) refers to the service network of an operator or a third party, which can provide services to terminals (such as operator services, Internet services, etc.).

[0220] 3. Local data network.

[0221] A local data network (local DN) can be an access point of a data network that is very close to the attachment point of the user.

[0222] 4. Application context.

[0223] An application context can refer to the running state information related to one or a group of users, such as game processes, historical data of ML, etc. Optionally, the application context can also include the subscription context of the one or more users in the EAS and the core network, such as subscription transaction identifiers, etc. Optionally, the application context can also include the context of the one or more users on the EES, such as the subscription transaction identifiers of the EAS for the one or more users.

[0224] 5. EEC context.

[0225] The EEC context can refer to the user-related data stored in the EES.

[0226] The EEC context can include EEC-side information and EAS-EES subscription information. Among them, the EEC-side information can include EEC registration information, EEC subscription information (such as EAS discovery subscription, EAS dynamic information subscription, etc.); the EAS-EES subscription information can include UE location API, application context relocation event, AC information open API, UE identifier API, and quality of service (QoS) session API, etc.

[0227] 6. Application context relocation (ACR).

[0228] Application context migration can also be referred to as application context relocation, and no distinction is made in this application.

[0229] During the operation of edge applications, when the terminal moves outside the current service area, the current EAS providing services may not be able to continue providing services for the currently running application, or the current EAS providing services is no longer the optimal EAS that can provide services for the terminal, and other EASs may be more suitable for serving the terminal. In this case, a new EAS can be selected to provide services for the terminal. However, during the process of replacing the currently serving edge application server with a new one, it will cause a temporary suspension or interruption of the application service, affecting the transmission of application services.

[0230] Specifically, based on Figure 1 the network architecture shown, application context relocation (ACR) can be performed.

[0231] For the convenience of description, hereinafter, the currently serving EAS will be referred to as the source EAS (S-EAS), and the new EAS will be referred to as the target EAS (T-EAS).

[0232] The application context migration process can be mainly divided into the following four stages.

[0233] Stage 1: Detection of application context migration.

[0234] In this stage, it can be determined that context migration may be required. The detection entity can detect the target event. The target event can include terminal location change, update of the terminal user plane path, etc.

[0235] Stage 2: Decision-making of application context migration.

[0236] In this stage, the decision-making entity determines that context migration is required.

[0237] Stage 3: Execution of application context migration.

[0238] In this stage, the execution entity transfers the context of the application from the source EAS to the target EAS. Further, it includes the discovery of the target EAS, and can also notify the terminal of the relevant information of the target EAS, notify the EAS (which can be the source EAS and the target EAS) to initiate the application context transmission, and the EES or EAS executes the application function (AF) traffic influence and carries the N6 routing information of the T-EAS

[0239] Stage 4: Clean-up work after application context migration.

[0240] Multiple entities are involved in this stage. EAS notifies EEC of the application context transfer result through EES, and AC initiates a new socket connection to the target EAS, etc.

[0241] It should be noted that the above entities can be the same entity or different entities, without limitation.

[0242] The following combines Figures 2 to 9 Describe several implementation methods of application context migration.

[0243] Figure 2 Is an implementation method of application context migration.

[0244] In this implementation method, EEC initiates ACR and adopts the conventional EAS discovery process.

[0245] This implementation method includes the following steps from step 201 to step 208:

[0246] Step 201, EEC detects the target event and decides to trigger the application context migration.

[0247] Among them, the target event may include UE location change, UE user plane path update, etc.

[0248] For example, EEC detects the location update of UE (UE location update). This step can also be triggered by AC by calling the ACR-related API provided by EEC, or AC detects the change of UE location and provides the new location to EEC, so that EEC knows that the location of UE has changed.

[0249] Step 202, EEC executes the service provisioning process to discover T-EES.

[0250] The following will combine Figure 3 in (a) to describe step 202 in detail.

[0251] It should be understood that the discovery process of the EES platform and the discovery process of EAS are defined in the current standard. This process provides the discovery of the EES platform and the application instances at the application layer. EES can function as a Local DNS server, and UE obtains the application instance address from the MEC platform. The architecture and function are designed to use a two-level discovery mechanism: first discover the EES platform, and then discover EAS from the EES platform.

[0252] The following will combine Figure 3 in (b) to describe the registration process of EEC in detail, and combine withFigure 3 Item (c) in [document] describes the EAS registration process in detail.

[0253] Step 203: The EEC executes a regular EAS discovery process to discover one or more EASs.

[0254] The following will describe Step 203 in detail in conjunction with Figure 4 Item (a) in [document].

[0255] Step 204: The AC selects a T-EAS from one or more EASs discovered by the EEC.

[0256] The following will describe the AC information subscription process in detail in conjunction with Figure 4 Item (b) in [document], and describe the AC information notification process in detail in conjunction with Figure 4 Item (c) in [document].

[0257] Step 205: The EEC sends an application context relocation request message to the S-EES.

[0258] Step 206: The S-EES sends an application context relocation response message to the EEC.

[0259] Step 207: The application context is transmitted between the S-EAS and the T-EAS.

[0260] The interaction between the AC and the S-EAS triggers the S-EAS to initiate the transfer of the application context.

[0261] Step 208: After the application context is transmitted, each entity executes a cleanup process.

[0262] It can be seen that in the implementation shown in Figure 2 the EEC performs detection, decision-making, determines the T-EES and T-EAS, requests the S-EES to initiate a user plane path modification, and initiates the transmission of the application context by the EEC or the AC.

[0263] Figure 3 Item (a) in [document] is a schematic diagram of the service activation process.

[0264] Prerequisite: The ECS configures the available edge computing service information related to the EEC according to the UE location, service requirements, service preferences, and connectivity for the EEC to discover the relevant available EESs.

[0265] The service provisioning process includes the following steps 301a to 303a:

[0266] Step 301a, the EEC sends a service provisioning request message to the ECS.

[0267] Among them, the service provisioning request message may include the EEC ID (identifier), security credentials, AC profile, UE identifier, connection information, and UE location, etc. Among them, the UE identifier may include the generic public subscription identifier (GPSI), etc.

[0268] As an example, Table 1a shows the cells that the service provisioning request message may include.

[0269] Table 1a

[0270]

[0271] Step 302a, after receiving the service provisioning request message, the ECS processes the service provisioning request.

[0272] Specifically, the ECS performs authentication and authorization, and matches the EES registered on the ECS according to the AC profile and UE location information provided by the EEC.

[0273] Step 303a, the ECS sends a service provisioning response message to the EEC.

[0274] If the ECS cannot determine the EEC information according to the service provisioning request message, the ECS shall reject the service provisioning request of the EEC and give the reason for failure.

[0275] If the ECS successfully processes the service provisioning request of the EEC, the ECS may provide EDN connection information, a list of EES that meet the EEC request information, and address identification information of the EES, etc.

[0276] As an example, Table 2a shows the cells that the service provisioning response message may include.

[0277] Table 2a

[0278]

[0279]

[0280] Figure 3 (b) in is a schematic diagram of the EEC registration process.

[0281] The EEC registration process includes the following steps from step 301b to step 304b:

[0282] Step 301b, the EEC sends an EEC registration request message to the EES.

[0283] The request from the client includes the security credentials received after successful authorization of the edge computing service and may include a proposed expiration time. The request may also optionally include information indicating to the EES how the EEC expects to use the services of the EES. If the EEC moves from the authority of another EES (referred to as the source EES) to this EES, the request from the EEC may include the identification and endpoints of the source EES, as well as the EEC context ID provided by the source EES to maintain the EEC context and authorize the relocation of the EEC context.

[0284] As an example, Table 1b shows the cells that an EEC registration request message may include.

[0285] Table 1b

[0286]

[0287] Step 302b, after the EES receives the request from the EEC, it verifies the registration request and the security credentials.

[0288] Specifically, the EES further determines whether the requirements indicated in the AC profile can be met.

[0289] Step 303b, after successfully verifying the request, if the received EEC registration request contains the EEC context ID, source EES ID, and EES endpoints, the EES retrieves the EEC's context from the source EES. Otherwise, this step is skipped.

[0290] Step 304b, the EES sends a registration response message to the EEC.

[0291] If the registration is successful, the EES sends a registration success response, which includes a registration ID and may include a newly assigned EEC context ID. The EEC stores the new EEC context ID and uses it when registering with another EES. The EES can also provide an expiration time to indicate to the EEC when the registration will automatically expire. To maintain the registration, the EEC should send a registration update request before the expiration. If no registration update request is received before the expiration time, the EES should consider the EEC as implicitly deregistered.

[0292] If the registration fails, the EES sends a registration failure response and gives the reason for the failure.

[0293] As an example, Table 2b shows the cells that a registration response message may include.

[0294] Table 2b

[0295]

[0296]

[0297] Figure 3 Among them, (c) is a schematic diagram of the EAS registration process.

[0298] This EAS registration process includes the following steps from step 301c to step 304c:

[0299] Step 301c, the EAS determines that it needs to be registered to the EES.

[0300] For example, the AS is instantiated and started

[0301] Step 302c, the EAS sends an EAS registration request message to the EES. The request should include the EAS configuration file and may include the proposed expiration time of the registration.

[0302] As an example, Table 1c shows the cells that the EAS registration request message can include.

[0303] Table 1c

[0304] Cell Status Description EAS Profile Required EAS Profile Security credentials Required Security credentials for EAS Proposed expiration time Optional Proposed expiration time for registration

[0305] As an example, Table 2c shows the cells that the EAS Profile can include.

[0306] Table 2c

[0307]

[0308]

[0309] Step 303c, the EES conducts a registration authorization check to verify whether the EAS has the authorization to register on the EES.

[0310] Step 304c, the EES sends an EAS registration response message to the EAS.

[0311] If the authorization is successful, the EES stores the EAS configuration file for future use (e.g., for servicing EAS discovery requests received from the EEC, etc.) and replies to the EAS using the EAS registration response. The EES can provide the expiration time to indicate to the EAS when the registration will automatically expire. To maintain the registration, the EAS should send a registration update request before the expiration time. If a registration update request is not received before the expiration time, the EES should consider the EAS as implicitly deregistered

[0312] If the registration fails, the EES sends a registration failure response and gives the reason for the failure.

[0313] As an example, Table 3c shows the cells that a registration response message can include.

[0314] Table 3c

[0315]

[0316] Figure 4 In (a) is a schematic diagram of the conventional EAS discovery process.

[0317] Prerequisites: 1) The EEC receives information from the EES, such as the URL, IP address, etc. of the EES; 2) The EAS discovery policy of the ECSP is configured on the EES.

[0318] This EAS discovery process includes the following steps 401a to 403a.

[0319] Step 401a, the EEC sends an EAS discovery request message to the EES.

[0320] Among them, the EAS discovery request message can include the EEC ID and security credentials. The EAS discovery request message can also include an EAS discovery filter to retrieve information about a specific EAS or a specific type of EAS (such as a game application).

[0321] As an example, Table 4a shows the cells that an EAS discovery request message can include.

[0322] Table 4a

[0323]

[0324] As an example, Table 5a shows the cells that an EAS discovery filter can include.

[0325] Table 5a

[0326]

[0327] As an example, Table 6a shows the cells that an AC configuration file can include.

[0328] Table 6a

[0329]

[0330]

[0331] Step 402a, after receiving the EAS discovery request sent by the EEC, the EES performs authorization verification and determines one or more EASs. Specifically, if the EES determines that the EEC is authorized to discover the requested EASs, the EES determines one or more EASs based on the provided EAS discovery filter and the location of the UE. If no EAS discovery filter is provided in the EAS discovery request message, the EES determines one or more EASs based on the UE-specific service information and UE location on the EES, or the EES determines one or more EASs by applying the ECSP policy (e.g., based only on the UE location). If the EES cannot determine one or more EASs through the information carried in the EAS discovery request message, the UE-specific service information and UE location on the EES, or the ECSP policy, the EES rejects the EAS discovery request of the EEC and gives the corresponding failure reason. If the UE is outside the geographical or topological service area of the EAS, the EES shall not include the EAS in the EAS discovery response message.

[0332] Step 403a, the EES sends an EAS discovery response message to the EEC.

[0333] Among them, if the EAS discovery request of the EEC is processed successfully, the EAS discovery response message includes the information of one or more discovered EASs and their endpoint information; if the EAS discovery request of the EEC is processed unsuccessfully, the EAS discovery response message includes a failure indication and the failure reason.

[0334] As an example, Table 7a shows the cells that the EAS discovery response message may include.

[0335] Table 7a

[0336]

[0337] Figure 4 In which, (b) is the schematic diagram of the AC information subscription process.

[0338] This AC information subscription process includes the following steps S401b to step S403b:

[0339] Step S401b, the EAS sends an AC information subscription request message to the EES.

[0340] The AC information subscription request message may contain a filter to retrieve information about a specific AC.

[0341] Step S402b, after receiving the request from the EAS, the EES processes the request, including:

[0342] Perform authorization check to verify whether EAS has the authorization to perform the operation. EES determines the matching AC information corresponding to the provided filter and synthesizes the result. EES stores the subscription information for future processing.

[0343] Step S403b, EES sends an AC information subscription response message to EAS.

[0344] As an example, Table 4b shows the cells that an AC information subscription request message can include.

[0345] Table 4b

[0346]

[0347] As an example, Table 5b shows the cells that a filter can include.

[0348] Table 5b

[0349]

[0350] Figure 4 (c) in it is the schematic diagram of the AC information notification process.

[0351] This AC information notification process includes the following steps S401c to S403c:

[0352] Step S401c, EES is triggered for AC information update.

[0353] For example, it receives an EEC registration request and determines whether it matches the filter provided by EAS; also for example, if the AC geographical service area is included in the geographical service area provided by EAS.

[0354] Step S402c, EES sends an AC information notification message to EAS.

[0355] As an example, Table 4c shows the cells that an AC information notification message can include.

[0356] Table 4c

[0357]

[0358]

[0359] Figure 5 is another implementation of application context migration.

[0360] In this implementation, EEC performs ACR through S-EES.

[0361] Step 501, EEC detects a target event.

[0362] Among them, the target event may include UE location change, UE user plane path update, etc. This step may be that the AC indicates to the EEC through the Edge-5 interface to detect whether ACR needs to be performed.

[0363] Step 502, the EEC decides to trigger application context migration.

[0364] Step 503, the EEC determines the T-EAS.

[0365] Step 504, the EEC sends an application context migration request to the S-EES, and this request is used to indicate that the S-EES further interacts with the S-EAS to trigger the S-EAS to perform context transfer.

[0366] Step 505, the S-EES indicates to the S-EAS to transfer the application context, and the application context is transferred between the S-EAS and the T-EAS.

[0367] Step 506, after the application context is transferred, the T-EAS sends an application context migration completion message to the T-EES, indicating that the application context transfer of the T-EES is completed and indicating the application context transfer result.

[0368] Step 507, after the application context is transferred, the S-EAS sends an application context migration completion message to the S-EES, indicating that the application context transfer of the T-EES is completed and indicating the application context transfer result.

[0369] Step 508, after receiving the application context migration completion message sent by the S-EAS, the S-EES sends an application context migration completion message to the EEC, indicating that the application context transfer of the EEC is completed.

[0370] It can be seen that in Figure 5 the implementation shown, the EEC performs detection, decision-making, determines the T-EES and the T-EAS, the EEC requests the S-EES to initiate user plane path modification, and the S-EES initiates the transfer of the application context. Figure 5 For a more specific description of each stage shown, reference can be made to Figure 2 the relevant description in, which will not be elaborated here. Different from Figure 2 the implementation shown is that the S-EES initiates the transfer of the application context.

[0371] Figure 6 is another implementation of application context migration.

[0372] In this implementation, the EEC performs ACR through the T-EES.

[0373] Step 601, the EEC detects a target event.

[0374] Among them, the target event may include UE location change, UE user plane path update, etc.

[0375] Step 602, the EEC decides to trigger application context migration.

[0376] Step 603, the EEC determines the T-EAS.

[0377] Step 604, the EEC sends an application context migration request to the T-EES. This request is used to trigger the transfer of the application context and the update of the user plane path.

[0378] Step 605, the T-EES instructs the T-EAS to request the application context from the S-EAS, and the application context is transmitted between the S-EAS and the T-EAS.

[0379] Step 606, after the application context is transmitted, the T-EAS sends an application context migration completion message to the T-EES, indicating that the T-EES has completed the application context transmission and indicating the application context transmission result.

[0380] Step 607, after receiving the application context migration completion message sent by the T-EAS, the T-EES sends an application context migration completion message to the EEC, indicating that the EEC has completed the application context transmission.

[0381] It can be seen that in Figure 6 the implementation shown, the EEC performs detection, decision-making, determines the T-EES and the T-EAS, the EEC requests the T-EES to initiate the user plane path modification, and the T-EES notifies the T-EAS to initiate the transmission of the application context. Figure 6 For a more specific description of each stage shown, reference can be made to Figure 5 the relevant description in, which will not be elaborated here. Different from Figure 5 the implementation shown, the transmission of the application context is initiated by the T-EES.

[0382] Figure 7 is another implementation of application context migration.

[0383] In this implementation, the S-EAS decides to initiate the ACR.

[0384] Step 701, the S-EAS detects a target event, or the S-EES detects a target event and notifies the S-EAS.

[0385] Among them, the target event may include UE location change, UE user plane path update, etc.

[0386] Step 702, S-EAS determines to initiate application context migration.

[0387] Step 703, S-EAS determines T-EAS.

[0388] Step 704, S-EES notifies the target EAS information.

[0389] Step 705, the application context is transmitted between S-EAS and T-EAS.

[0390] Step 706, after the application context is transmitted, each entity executes the cleanup process.

[0391] It can be seen that in Figure 7 the implementation shown, it is detected by S-EAS or S-EES, the decision is made by S-EAS, T-EES and T-EAS are determined, the user plane path is modified by S-EAS, and the application context is transmitted by S-EES.

[0392] Figure 8 is another implementation of application context migration.

[0393] In this implementation, S-EES executes ACR.

[0394] Step 801, EEC, S-EAS or S-EES detects a target event.

[0395] Among them, the target event may include UE location change, UE user plane path update, etc.

[0396] Step 802, EEC or S-EAS notifies S-EES that a target event has been detected.

[0397] This step is an optional step. If the target event is detected by EEC or S-EAS, then EEC or S-EAS needs to notify S-EES that a target event has been detected.

[0398] Step 803, S-EES determines to initiate application context migration.

[0399] Step 804, S-EES determines T-EAS.

[0400] Step 805, S-EES notifies the target EAS information.

[0401] Step 806, S-EES notifies S-EAS to perform context migration.

[0402] Step 807, the application context is transmitted between S-EAS and T-EAS.

[0403] Step 808, after the application context is transmitted, T-EAS sends an application context migration completion message to T-EES, indicating that the application context transmission of T-EES is completed and indicating the application context transmission result.

[0404] Step 809, after the application context is transmitted, S-EAS sends an application context migration completion message to S-EES, indicating that the application context transmission of T-EES is completed and indicating the application context transmission result.

[0405] Step 810, after receiving the application context migration completion message sent by S-EAS, S-EES sends an application context migration completion message to EEC, indicating that the application context transmission of EEC is completed.

[0406] It can be seen that in Figure 8 the implementation shown, EEC, S-EAS or S-EES performs detection, S-EES makes decisions to determine T-EES and T-EAS, S-EES initiates the user plane path modification, and S-EES notifies S-EAS to initiate the transmission of the application context.

[0407] Figure 9 This is another implementation of the application context migration.

[0408] Figure 9 The ACR method shown is automatic ACR, and this automatic ACR can also be called full ACR, or full service ACR, or full operation ACR.

[0409] Step 901, S-EAS or S-EES initiates automatic ACR.

[0410] Step 902, EEC, S-EAS or S-EES detects a target event.

[0411] Among them, the target event may include UE location change, UE user plane path update, etc.

[0412] Step 903, EEC or S-EAS notifies S-EES that the target event is detected.

[0413] This step is an optional step. If EEC or S-EAS detects the target event, then EEC or S-EAS needs to notify S-EES that the target event is detected.

[0414] Step 904, S-EES determines to initiate the application context migration.

[0415] Step 905, S-EES determines T-EAS.

[0416] Step 906, S-EES notifies the target-side information.

[0417] Step 907, S-EES notifies S-EAS to perform context migration.

[0418] Step 908, S-EES executes the application traffic impact process.

[0419] Step 909, S-EES initiates the transfer of the application context. Before this, the application context is stored by S-EAS at a storage address that allows S-EES to access it. The same is true on the target side, where the target EES and target EAS share a storage address for the application context.

[0420] Step 910, after the application context is transmitted, T-EAS sends an application context migration completion message to T-EES, indicating that the application context transmission to T-EES is completed and indicating the application context transmission result.

[0421] Step 911, after the application context is transmitted, S-EAS sends an application context migration completion message to S-EES, indicating that the application context transmission to T-EES is completed and indicating the application context transmission result.

[0422] Step 912, after receiving the application context migration completion message sent by S-EAS, S-EES sends an application context migration completion message to EEC, indicating that the application context transmission to EEC is completed.

[0423] It can be seen that in Figure 9 the implementation shown, EEC, S-EAS or S-EES performs detection, S-EES makes decisions to determine T-EES and T-EAS, S-EES initiates the modification of the user plane path, and S-EES notifies S-EAS to initiate the transmission of the application context.

[0424] From Figure 2 and Figures 5 to 9 the processes shown, it can be seen that EEC, AC, EES, and EAS can all detect ACR events, and after a specific entity detects an ACR event, multiple ACR methods can be used for application context migration. However, the above ACR methods may cause multiple functional entities to repeatedly detect the ACR requirements for the same application and cause conflicts brought about by executing multiple application context migrations.

[0425] To avoid the defect that multiple functional entities repeatedly detect the ACR requirements for the same application caused by the current ACR methods, the present application provides a method for migrating context, which avoids multiple functional entities from repeatedly triggering the ACR process by enabling a certain functional entity to execute the ACR process.

[0426] The following will combine with Figure 11 the figures to introduce in detail the method for migrating context provided by this application.

[0427] The technical solutions of the embodiments of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Worldwide Interoperability for Microwave Access (WiMAX) communication systems, 5G systems, New Radio (NR) or future networks, etc. The technical solutions provided by this application can also be applied to future communication systems, such as the sixth-generation mobile communication system. The communication system can also be a Public Land Mobile Network (PLMN) network, a Device-to-Device (D2D) communication system, a Machine-to-Machine (M2M) communication system, an Internet of Things (IoT) communication system, or other communication systems.

[0428] The specific structure of the execution subject of the method provided by the embodiments of this application is not particularly limited by the embodiments shown below. As long as it can communicate according to the method provided by the embodiments of this application by running a program recording the code of the method provided by the embodiments of this application. For example, the execution subject of the method provided by the embodiments of this application can be a terminal device or a device in the edge network, or a functional module in the terminal device or the device in the edge network that can call and execute the program function.

[0429] For the convenience of understanding the embodiments of this application, the following points are explained.

[0430] First, the first, second, and various numerical numbers (for example, "#1", "#2", etc.) shown in this application are only for convenience of description and are used to distinguish objects, and do not limit the scope of the embodiments of this application. For example, to distinguish different messages, etc., rather than for describing a specific order or sequence. It should be understood that the objects described in this way can be interchanged under appropriate circumstances so as to be able to describe the solutions other than the embodiments of this application.

[0431] Second, in this application, "preset" may include predefined, for example, protocol definition. Among them, "predefined" can be implemented by pre-saving corresponding codes, tables or other ways that can be used to indicate relevant information in a device (for example, including a user equipment or a core network equipment), and this application does not limit its specific implementation method.

[0432] Third, the "saving" involved in the embodiments of this application may refer to saving in one or more memories. The one or more memories may be separately provided, or may be integrated in an encoder or a decoder, a processor, or a communication device. The one or more memories may also be partially separately provided and partially integrated in a decoder, a processor, or a communication device. The type of the memory may be any form of storage medium, and this application does not limit this.

[0433] Fourth, the "protocol" involved in the embodiments of this application may refer to a standard protocol in the communication field. For example, it may include a 5G protocol, a new radio (NR) protocol, and related protocols applied to future communication systems. This application does not limit this.

[0434] Hereinafter, without loss of generality, taking the interaction between devices as an example, the method for information transmission provided by the embodiments of this application will be described in detail.

[0435] Figure 10 is a schematic flowchart of a method for migrating context provided by this application.

[0436] The method for migrating context includes the following steps:

[0437] Step 1010, the AC obtains ACR mode information.

[0438] The ACR mode information is information for determining the ACR method. Among them, the ACR method may also be called an ACR scenario or an ACR execution method, etc. For the convenience of description, the ACR method will be used as an example for description hereinafter.

[0439] Exemplarily, determining the ACR method may be embodied as determining the device for executing the ACR process. For example, if the device for executing the ACR process is the EEC, it can be understood that the ACR method is the ACR method #1.

[0440] Exemplarily, the ACR methods involved in the embodiments of this application include at least one of the following:

[0441] The EEC uses regular EAS discovery (Initiation by EEC using regular EAS Discovery) (such as Figure 2in the manner shown), the EEC executes ACR via S-EES (EEC executed ACR via S-EES) (as Figure 5 shown), S-EAS determines the ACR scenario, S-EES executes ACR (S-EES executed ACR) (as Figure 7 shown), the EEC executes ACR via T-EES (EEC executed ACR via T-EES) (as Figure 6 shown), or automated ACR (which can also be referred to as full ACR / EES management, ACR / EEL layer manages ACR / Automated ACR) (as Figure 9 shown), etc.

[0442] The ACR mode information can specifically be the rule for determining the ACR method, and can also be called the selection rule of the ACR method, the determination rule of the ACR method, or the ACR rule information, etc. This application takes the ACR rule information as an example for illustration. First, the ACR rule information will be specifically introduced below. The ACR rule information includes condition information for triggering the ACR process of at least one application.

[0443] As a possible implementation, the ACR rule information includes the correspondence between the application type and the device for executing the ACR process of the application belonging to the application type;

[0444] As another possible implementation, the ACR rule information includes the correspondence between the event information of the process for triggering ACR and the device for executing the preset ACR process.

[0445] Exemplarily, the ACR rule information can be represented by a correspondence, and this correspondence includes the correspondence between the ACR trigger event and the preset ACR execution manner (for example, including the six manners as shown in Figure 2 , Figures 5 to 9 shown), and / or the correspondence between the application type and the preset ACR execution manner; or,

[0446] The corresponding relationship includes the corresponding relationship between ACR trigger events and the functional entities that execute ACR (including at least functional entities such as AC, EAS, EES, and EEC as described above), and / or the corresponding relationship between application types and the functional entities that execute ACR. Here, executing ACR can be understood as, after deciding to perform ACR, sending an application context relocation request or triggering a context transfer or requesting a user plane path update. In the embodiments of the present application, the ACR rule information is used to indicate the ACR trigger events and / or application types for the ACR processes executed by at least one of AC, EAS, EES, and EEC.

[0447] For example, if the ACR trigger event is UE movement, the functional entity that executes the ACR process is EES or EAS;

[0448] Also for example, if the ACR trigger event is server overload, the functional entity that executes the ACR process is EAS;

[0449] Also for example, if the ACR trigger event is a change in DNAI, the functional entity that executes the ACR process is EES;

[0450] Also for example, when the application type is Application A, the functional entity that executes the ACR process is EES;

[0451] Also for example, when the QoE quality deteriorates, the functional entity that executes the ACR process is AC.

[0452] The condition information can be understood as ACR trigger condition information, which is used to indicate the ACR trigger conditions. For example, the ACR trigger conditions include ACR trigger events (such as UE movement, EAS overload, etc.); also for example, the ACR trigger conditions include application types (such as information applications, call applications, etc.).

[0453] The above-mentioned condition information indicates at least one of the following conditions:

[0454] The first condition, the second condition, the third condition, and the fourth condition,

[0455] Among them, when the first condition is satisfied, it indicates that EEC executes the ACR process for the first application among at least one application; when the second condition is satisfied, it indicates that AC executes the ACR process for the second application among at least one application; when the third condition is satisfied, it indicates that EAS executes the ACR process for the third application among at least one application; when the fourth condition is satisfied, it indicates that EES executes the ACR process for the fourth application among at least one application.

[0456] It should be noted that the "first application" involved in the embodiments of the present application can be one or more. It can be understood that when the first condition is met, all applications corresponding to the ACR processes that the EEC can execute are called the first application. For example, when the EEC executes the ACR process for an application of application type #1, the application of application type #1 can be one or more; similarly, the "second application" can also be one or more, the "third application" can also be one or more, and the "fourth application" can also be one or more. For the same reason as above, it will not be elaborated here.

[0457] In addition, it should be noted that the above-mentioned "first application", "second application", "third application" and "fourth application" can be the same application, that is, the application corresponding to this AC. For example, when different conditions are met, the above-mentioned functional entity executes the ACR process for a certain application.

[0458] Specifically, the ACR mode information can also be an indication of the identity of the application client and the ACR method determined by the server for this application client identity.

[0459] Wherein, the server is one of an edge enabling client EEC, an edge configuration server ECS, an edge enabling server EES or an edge application server EAS.

[0460] Specifically, the ACR mode information can be the correspondence between the identity (ID) of this AC and the ACR method determined for this AC.

[0461] The correspondence between the application client identity and the ACR method for executing the application corresponding to the application client identity specifically includes:

[0462] Pre-configure an ACR method for the application corresponding to each client identity; or, select an ACR method for the application corresponding to each client identity.

[0463] For example, when the identity of the application client is AC ID#1, the ACR method for executing the application App#1 corresponding to this AC ID#1 is that the EEC uses the conventional EAS discovery.

[0464] Specifically, in the embodiments of the present application, the AC obtaining the ACR mode information includes the following two situations:

[0465] Situation 1: The AC obtains the ACR mode information from the AC configuration file (AC profile) in the AC; or it can be said that the AC determines the ACR mode information from the AC profile.

[0466] For example, the ACR mode information is pre-configured in the AC profile.

[0467] In Scenario 1, the above-mentioned step 1010 is understood as Figure 10 step S1011 shown in Figure 10 , where AC obtains ACR mode information from the AC configuration file in AC.

[0468] It can be understood that the ACR mode information is predefined in the AC profile. In Scenario 1, the cells that can be included in the AC profile are shown in Table 8 below:

[0469] Table 8

[0470]

[0471] In Scenario 1, AC can send the ACR mode information to the EEC. Figure 10 The method flow shown can further include:

[0472] Step 1012, where AC sends the ACR mode information to the EEC.

[0473] Exemplarily, AC sending the ACR mode information to the EEC can be the ACR rule information or the ACR method corresponding to the AC ID.

[0474] Exemplarily, AC sends the AC profile containing the ACR mode information to the EEC through the EDGE-5 interface.

[0475] It should be noted that AC sending the ACR mode information to the EEC can be achieved by AC actively sending a message carrying the ACR mode information (e.g., an EDGE-5 interface message) to the EEC, or the EEC implicitly or explicitly subscribing to the ACR mode information. After AC obtains the ACR mode information, it can send a notification message to the EEC.

[0476] Another possible implementation method is that when the EEC does not implicitly or explicitly subscribe to the above notification message, after AC obtains the ACR mode information, it can notify the EEC to implicitly or explicitly subscribe to the ACR mode information. After the EEC subscribes to the ACR mode information, it sends an ACR mode information notification to the EEC.

[0477] Exemplarily, as an implementation method for the above EEC to explicitly subscribe to the ACR mode information: The EEC subscribes to the ACR mode information and requests AC to send the ACR mode information to the EEC after obtaining the ACR mode information;

[0478] Exemplarily, as an implementation method for the above EEC to implicitly subscribe to the ACR mode information: When the EEC subscribes to ACR information notifications and other ACR-related notification information from AC, it requests AC to send the ACR mode information in the ACR information notifications and other ACR-related information notifications to the EEC after obtaining the ACR mode information.

[0479] Scenario 2: The AC receives the ACR mode information from the EEC.

[0480] Exemplarily, the AC receives the ACR mode information from the EEC through the EDGE-5 interface.

[0481] Exemplarily, the ACR mode information received by the AC from the EEC through the EDGE-5 interface may be ACR rule information or the ACR method corresponding to the AC ID. In Scenario 2, step 1010 described above is understood as Figure 10 step 1021 shown in, where the AC receives the ACR mode information from the EEC.

[0482] It should be noted that when the EEC sends the ACR mode information to the AC, it can actively send a message carrying the ACR mode information (e.g., an EDGE-5 interface message) to the AC, or implicitly or explicitly subscribe to the ACR mode information in the process of the AC reporting information. After the EEC obtains the ACR mode information, it can send a notification message to the AC.

[0483] In another possible implementation method, when the AC does not implicitly or explicitly subscribe to the above notification message, after the EEC obtains the ACR mode information, it can notify the AC to implicitly or explicitly subscribe to the ACR mode information. After the AC subscribes to the ACR mode information, the EEC sends an ACR mode information notification to the AC.

[0484] Exemplarily, as an implementation method for the AC to explicitly subscribe to the ACR mode information: The AC subscribes to the ACR mode information and requests the EEC to send the ACR mode information to the AC after obtaining the ACR mode information;

[0485] Exemplarily, as an implementation method for the AC to implicitly subscribe to the ACR mode information: When the AC subscribes to ACR information notifications and other ACR-related notification information from the EES, it requests the EEC to send the ACR mode information in the ACR information notifications and other ACR-related information notifications after obtaining the ACR mode information.

[0486] In Scenario 2, the EEC obtains the ACR mode information. Different from step 1012 shown in Scenario 1 above, in Scenario 2, the EEC does not obtain the ACR mode information from the AC (it can be understood that if it is obtained from the AC, there is no need to send it to the AC again). Below, it will be combined with Figure 11 in (a) to detail the possible ways for the EEC to obtain the ACR mode information, which will not be elaborated here.

[0487] Further, when the second condition is satisfied, the AC executes the ACR process for the second application in at least one application.Figure 10 The method flow shown may further include:

[0488] Step 1020, the AC executes the ACR process for the second application in at least one application.

[0489] Exemplarily, when the AC determines that the second condition is satisfied (for example, when the ACR rule information indicates that the application type is type #1 and the functional entity executing the ACR is the AC; also for example, when the ACR mode information indicates that the application identifier is AC ID #1 and the method of executing the ACR is that the EEC uses the conventional EAS discovery), the AC executes the ACR process for the second application in at least one application (for example, the second application is an application of type #1).

[0490] Exemplarily, the AC executes the ACR process according to the selected ACR method.

[0491] Specifically, for the AC to determine whether the second condition is satisfied, it may be that the AC monitors the application type to which the application that needs to perform context migration belongs, or the event type that triggers context migration, or monitors the identifier of the application that needs to perform context migration. For example, when the second condition is that a quality of experience (QoE) degradation event occurs and the ACR is triggered by the AC, then when the AC detects the QoE degradation event, the AC executes the ACR. Specifically, the AC may call the application programming interface (API) provided by the EES to complete the ACR, for example Figure 2 The corresponding process.

[0492] Exemplarily, the AC executes the ACR process according to the ACR method corresponding to the AC ID, and / or executes the corresponding ACR method corresponding to the AC ID, and further executes the relevant steps in the above ACR method.

[0493] It should be noted that in the embodiments of the present application, there is no limitation on how the functional entity (AC, EAS, EES or EEC) executes the ACR process, and reference can be made to the descriptions in the current related technologies (such as the Figure 2 , Figures 5 to 9 shown process). The embodiments of the present application mainly involve how to determine the ACR process that needs to be executed by itself or the ACR method corresponding to the executed ACR according to the ACR mode information. After determination, the current execution method can be referred to.

[0494] In addition, it should be noted that the execution of the ACR process involved in the embodiments of the present application can be understood as initiating the ACR process.

[0495] For ease of understanding, the following combines Figure 11(a) therein illustrates the way for the EEC to obtain the ACR mode information. Figure 11 (a) therein is a schematic flowchart of another method provided by this application for migrating context.

[0496] Specifically, from Figure 11 it can be seen from (a) therein that the EEC obtaining the ACR mode information includes the following situations:

[0497] Situation 1: The EEC receives the ACR mode information from the AC. It includes the following steps:

[0498] Step 1110, the EEC receives the ACR mode information from the AC.

[0499] Referring to Figure 10 the description of step 1012 shown in, it will not be elaborated here.

[0500] Situation 2: The EEC receives the ACR mode information from the EES. It includes the following steps:

[0501] Step 1120, the EES obtains the ACR mode information.

[0502] Below will combine with Figure 12 to describe in detail the possible ways for the EES to obtain the ACR mode information. It will not be elaborated here.

[0503] Step 1130, the EES sends the ACR mode information to the EEC.

[0504] Exemplarily, the EES sending the ACR mode information to the EEC can be the ACR rule information, or the ACR method corresponding to the AC ID.

[0505] It should be noted that for the EES to send the ACR mode information to the EEC, it can actively send a message carrying the ACR mode information (such as, the EAS discovery response message or the EAS discovery update response message, the EEC registration response message or the EEC registration update response message or the EAS discovery notification message, or the EDGE-1 related message) to the EEC, or implicitly or explicitly subscribe to the ACR mode information in the process of the EEC reporting information. After the EES obtains the ACR mode information, it can send a notification message to the EEC.

[0506] Another possible implementation method is that when the EEC does not implicitly or explicitly subscribe to the above notification message, after the EES obtains the ACR mode information, it can notify the EEC to implicitly or explicitly subscribe to the ACR mode information. After the EEC subscribes to the ACR mode information, it sends an ACR mode information notification to the EEC.

[0507] Exemplarily, as an implementation manner for the above EEC to display and subscribe to ACR mode information: The EEC subscribes to the ACR mode information, and requests the EES to send the ACR mode information to the EEC after obtaining the ACR mode information;

[0508] Exemplarily, as an implementation manner for the above EEC to implicitly subscribe to ACR mode information: When the EEC subscribes to ACR-related notification information such as ACR information notification from the EES, it requests the EES to send the ACR mode information to the EEC in the ACR information notification and other ACR-related information notification messages after obtaining the ACR mode information.

[0509] As a possible implementation manner, as shown in (b) of Figure 3 the EEC registration process shown, the ACR mode information can be sent to the EEC during the EEC registration process.

[0510] For example, the EES sends an EEC registration response message or an EEC registration update response message to the EEC, and the ACR mode information is carried in the EEC registration response message or the EEC registration update response message. The cells carried in the EEC registration response message or the EEC registration update response message are shown in Table 9 below:

[0511] Table 9

[0512]

[0513] Optionally, before the EES sends an EEC registration response message to the EEC, the EEC sends an EEC registration request message to the EES; or,

[0514] before the EES sends an EEC registration update response message to the EEC, the EEC sends an EEC registration update request message to the EES.

[0515] As another possible implementation manner, as shown in (a) of Figure 4 the conventional EAS discovery process shown, the ACR mode information can be sent to the EEC during the conventional EAS discovery process.

[0516] For example, the EES sends an EAS discovery response message or an EAS discovery update response message to the EEC, and the ACR mode information is carried in the EAS discovery response message or the EAS discovery update response message. The cells carried in the EAS discovery response message are shown in Table 10 below:

[0517] Table 10

[0518]

[0519] Optionally, before the EES sends an EAS discovery response message to the EEC, the EEC sends an EAS discovery subscription update request message to the EES.

[0520] Optionally, before the EES sends an EAS discovery update response message to the EEC, the EEC sends an EAS discovery subscription update request message to the EES.

[0521] Scenario 3: The EEC receives ACR mode information from the ECS. It includes the following steps:

[0522] Step 1140: The ECS obtains the ACR mode information.

[0523] The following will combine Figure 11 in (b) to detail the possible ways for the ECS to obtain the ACR mode information, which will not be elaborated here.

[0524] Step 1150: The ECS sends the ACR mode information to the EEC.

[0525] It should be noted that when the ECS sends the ACR mode information to the EEC, it can actively send a message carrying the ACR mode information (such as a service activation (update) response message) to the EEC, or implicitly or explicitly subscribe to the ACR mode information in the process of the EEC reporting information. After the ECS obtains the ACR mode information, it can send a notification message to the EEC.

[0526] Another possible implementation method is that when the EEC does not implicitly or explicitly subscribe to the above notification message, after the ECS obtains the ACR mode information, it can notify the EEC to implicitly or explicitly subscribe to the ACR mode information. After the EEC subscribes to the ACR mode information, it sends an ACR mode information notification to the EEC.

[0527] Exemplarily, as an implementation method of the above EEC explicitly subscribing to the ACR mode information: The EEC subscribes to the ACR mode information and requests the ECS to send the ACR mode information to the EEC after obtaining the ACR mode information;

[0528] Exemplarily, as an implementation method of the above EEC implicitly subscribing to the ACR mode information: When the EEC subscribes to ACR information notifications and other ACR-related notification information from the ECS, it requests the ECS to send the ACR mode information in the ACR information notifications and other ACR-related information notification messages after obtaining the ACR mode information.

[0529] As a possible implementation method, such as Figure 3 shown in (a) of the service activation process, the ACR mode information can be sent to the EEC in the service activation process.

[0530] For example, the ECS sends a service activation response message to the EEC, and the ACR mode information is carried in the service activation response message. The cells carried in the service activation response message are shown in Table 11 below:

[0531] Table 11

[0532]

[0533]

[0534] Case 4: The EEC formulates the ACR mode information.

[0535] Exemplarily, in the embodiments of the present application, the ECS formulating the ACR mode information may also be formulating the ACR mode information according to the information reported by the AC, EEC, EAS, and EES. Specifically, it includes:

[0536] Step 1161, the EEC receives the second information from the EAS.

[0537] The second information includes the ACR capability information supported by the EAS, and / or the second ACR method request information.

[0538] Among them, the ACR capability information supported by the EAS indicates the ACR trigger event or application type corresponding to the ACR process that the EAS can execute (or detect), or the ACR event that the EAS can detect, or the application where the EAS can detect the occurrence of ACR, or the ACR method supported or preferred by the EAS, or the priority of the ACR method corresponding to each AC ID;

[0539] The second ACR method request information (referred to as request ACR method, or referred to as request ACR scenario) is used to request the allocation of an ACR method, and can request the allocation of an ACR method for the EAS or suggest an ACR method for each AC, or the EAS carries AC-related information (such as, AC ID) in the ACR method request information, and requests the allocation of an ACR method for the EAS or suggests an ACR method for the required AC.

[0540] The specific sending process of the second information in this embodiment includes:

[0541] EAS to EES (e.g., via an EAS registration request, an EAS registration update request, a UE location request message, a subscription request message, an ACR management request message, a subscription request message, an AC information subscription request message, a subscription request message, a UE identifier API request message, a subscription request message, a QoS session creation response request message, a subscription request message, an ACR management event request message, a subscription request message, etc., corresponding request messages and subscription requests related to EDGE-3 subscriptions); EES to EEC (e.g., via processes related to EDGE-1 such as EAS discovery of EEC registration, EAS discovery subscription).

[0542] As a possible implementation, EAS may implicitly report the above-mentioned second information.

[0543] EAS subscribes to ACR management events from EES, including user plane path change (-user plane pathchange), ACR monitoring (-ACR monitoring), and ACR facilitation (-ACR facilitation).

[0544] When EAS subscribes to -user plane path change and / or -ACR monitoring events, it implicitly indicates that EAS has selected the ACR method of EAS executing ACR (S-EAS decided ACR scenario).

[0545] When EAS subscribes to ACR facilitation, it implicitly indicates that EAS has selected the ACR method of EES executing ACR (S-EESexecuted ACR).

[0546] Exemplarily, when EAS subscribes to ACR management events such as -user plane path change and / or -ACR monitoring to subscribe to ACR events from EES or to notify EAS of ACR requirements, and EAS decides whether to execute the ACR process based on the above events, this situation belongs to one implementation of the above implicit indication.

[0547] Exemplarily, when EAS subscribes to ACR management events such as ACR facilitation to subscribe to relevant notifications in the ACR process from EES and notify EAS, and EAS can receive relevant events in the ACR process, this situation belongs to one implementation of the above implicit indication.

[0548] Further, when the EAS subscribes to the ACR management event from the EES, it optionally carries the AC ID, which is used to implicitly indicate whether the ACR method selected by the EES for each AC is the ACR method of the EES executed ACR (S-EES executed ACR) or the ACR method of the S-EAS decided ACR scenario (S-EAS decided ACR scenario).

[0549] Step 1162, the EEC receives the third information from the AC.

[0550] The third information includes the ACR capability information supported by the AC and / or the third ACR method request information.

[0551] Among them, the ACR capability information supported by the AC indicates the ACR trigger event or application type corresponding to the ACR process that the AC can execute (or detect), or the ACR event that the AC can detect, or the application in which the AC can detect the occurrence of ACR, or the ACR method supported or preferred by the AC, or the priority of the ACR method corresponding to each AC ID;

[0552] The third ACR method request information (referred to as request ACR method, or referred to as request ACR scenario) is used to request the allocation of an ACR method. It can request the allocation of an ACR method for each AC or suggest an ACR method, or the AC carries AC-related information (such as AC ID) in the ACR method request information to request the allocation of an ACR method or suggest an ACR method for the required AC.

[0553] The specific sending process of the third information in this embodiment includes:

[0554] AC to EEC (such as through the EDGE-5 interface).

[0555] Step 1163, the EEC receives the fourth information from the EES.

[0556] The fourth information includes the ACR capability information supported by the EES and / or the fourth ACR method request information.

[0557] Among them, the ACR capability information supported by the EES indicates the ACR trigger event or application type corresponding to the ACR process that the EES can execute (or detect), or the ACR event that the EES can detect, or the application in which the EES can detect the occurrence of ACR, or the ACR method supported or preferred by the EES, or the priority of the ACR method corresponding to each AC ID;

[0558] The fourth ACR method request information (referred to as request ACR method or request ACR scenario) is used to request the allocation of ACR methods. It can allocate or recommend ACR methods for the EES for each AC request. Alternatively, the AC carries AC-related information (such as AC ID) in the ACR method request information, and allocates or recommends ACR methods for the EES for the required AC requests.

[0559] The specific sending process of the fourth information in this embodiment includes:

[0560] From EES to EEC (such as through processes related to EDGE-1 like EAS discovery of EEC registration and EAS discovery subscription).

[0561] Step 1164, the EEC formulates ACR mode information.

[0562] The EEC sets the ACR trigger rules according to the information reported by the AC, EES, and EAS, that is, for ACR events (UE mobility, EAS overload) or for application types, it allocates the events or application types that each functional entity (AC, EAS, EEC, EES) needs to detect and execute ACR;

[0563] And / or, the EEC sets the ACR method corresponding to each AC according to the ACR methods supported by the AC, EEC, EES, and EAS (optionally, the ACR methods supported for each AC).

[0564] Exemplarily, for the ACR event types reported by each entity, for example, for AC#1, the AC supports detecting UE mobility events, the EEC supports detecting UE mobility events, the EES supports detecting UE mobility events and EAS overload events, and the EAS supports detecting UE overload events. Then the EEC can set the ACR method for the application corresponding to this AC to be executed by the EES, S-EES executed ACR. After each entity receives the ACR method for the application corresponding to the AC, the EES performs the detection and determination of ACR, and the remaining entities perform the relevant required steps in the ACR process (subsequent steps will be called and executed by the relevant entities). For example, the EES notifies the EAS to perform the transmission of the application context, etc.

[0565] For the information of the application type or application-related information (e.g., AC ID) reported by each entity, such as AC ID #1, AC supports ACR method #1 and ACR method #2, EEC #1 supports ACR method #2 and ACR method #3, EES supports ACR method #1 and ACR method #2, and EAS supports ACR method #2 and ACR method #3. Then, EEC can set the ACR method of the application corresponding to the AC ID #1 to ACR method #2, and the remaining entities execute the relevant required steps in the ACR process (the subsequent steps will be called and executed by the relevant entities).

[0566] If the ACR methods supported by each entity are contradictory and conflicting, when the ACR mode information is sent, a failure indication message can be returned, and the failure reason carried in the failure indication message is that the ACR methods supported by each entity are contradictory and conflicting, or further includes the information re-reported by each entity (e.g., the updated second information, the updated third information, etc.).

[0567] Figure 11 In the cases shown in Case 2, Case 3, and Case 4 shown in (a) in, after EEC obtains the ACR mode information, it can send the ACR mode information to AC, Figure 11 The method flow shown in (a) in also includes:

[0568] Step 1160, EEC sends the ACR mode information to AC.

[0569] Refer to Figure 10 the description of Step 1021 shown in, which will not be elaborated here.

[0570] Step 1171, EEC sends the ACR mode information to EES.

[0571] It should be noted that when EEC sends the ACR mode information to EES, it can actively send a message carrying the ACR mode information (e.g., service activation (update) response message) to EES, or implicitly or explicitly subscribes to the ACR mode information in the process of EES reporting information. After EEC obtains the ACR mode information, it can send a notification message to EES.

[0572] Another possible implementation method is that when EES does not implicitly or explicitly subscribe to the above notification message, after EEC obtains the ACR mode information, it can notify EES to implicitly or explicitly subscribe to the ACR mode information. After EES subscribes to the ACR mode information, it sends an ACR mode information notification to EES.

[0573] Exemplarily, as an implementation manner for the above-mentioned EES to subscribe to ACR mode information: The EES subscribes to the ACR mode information and requests the EEC to send the ACR mode information to the EES after obtaining the ACR mode information;

[0574] Exemplarily, as an implementation manner for the above-mentioned EES to implicitly subscribe to ACR mode information: When the EES subscribes to ACR-related notification information such as ACR information notification from the EEC, the EES requests the EEC to send the ACR mode information to the EES in the ACR information notification and other ACR-related information notification messages after obtaining the ACR mode information.

[0575] Exemplarily, the ACR mode information sent by the EEC to the EES can be ACR rule information or the ACR method corresponding to the AC ID.

[0576] Optionally, the EEC sends the ACR mode information to the EES through at least one of the EEC registration update request message, the EAS discovery request message, and the EDGE-1 subscription request message.

[0577] As a possible implementation manner, such as Figure 3 shown in (b) of [reference], the ACR mode information can be sent to the EES during the EEC registration process.

[0578] For example, the EEC sends an EEC registration request message to the EES. The EEC registration request message carries AC-related information (such as the AC ID) (the cells carried in the EEC registration request message are as described in Table 1b above), and the AC profile includes the ACR mode information (the cells carried in the AC profile are as described in Table 8 above).

[0579] As another possible implementation manner, such as Figure 4 shown in (a) of [reference], the ACR mode information can be sent to the EES during the conventional EAS discovery process.

[0580] For example, the EEC sends an EAS discovery request message to the EES. The EAS discovery request message carries an EAS discovery filter (the cells carried in the EAS discovery request message are as described in Table 4a above), the EAS discovery filter carries an AC profile (the cells carried in the EAS discovery filter are as described in Table 5a above), and the AC profile includes the ACR mode information (the cells carried in the AC profile are as described in Table 8 above).

[0581] It should be understood that after determining the ACR mode information, the EEC may actively initiate at least one of an EEC registration update request message, an EAS discovery request message, and an EDGE-1 subscription request message to send the ACR mode information to the EES, or carry the above messages in a separate request or subscription message, and the specific bearer message is not limited.

[0582] As can be seen from the above, the conditional information included in the ACR mode information can be used to indicate a first condition. When the first condition is met, the EEC executes the ACR process for the first application among at least one application. Figure 11 The method flow shown in (a) in [] may further include:

[0583] Step 1170, the EEC executes the ACR process for the first application among at least one application.

[0584] Exemplarily, when the EEC determines that the first condition is met (for example, when the ACR mode information indicates that the ACR trigger event is UE movement and the functional entity executing the ACR is the EEC; also for example, when the ACR mode information indicates that the application identifier is AC ID#2 and the method for executing the ACR is that the EEC executes the ACR through the T-EES), the EEC executes the ACR process for the first application among at least one application (for example, the ACR process of the first application is the ACR process when the ACR trigger event is UE movement).

[0585] Specifically, the EEC determining whether the first condition is met may be that the EEC monitors the application type to which the application that needs to perform context migration belongs, or the event type that triggers context migration, or the identifier of the application that needs to perform context migration.

[0586] Exemplarily, the EEC executes the ACR process according to the ACR method corresponding to the AC ID, and / or executes the corresponding ACR method corresponding to the AC ID, and further executes the relevant steps in the above ACR method.

[0587] For ease of understanding, the following combines [] Figure 11 in (b) to illustrate the manner in which the ECS obtains the ACR mode information. Figure 11 (b) in [] is a schematic flowchart of another method for migrating context provided by this application.

[0588] Specifically, from [] Figure 11 in (b), it can be seen that the ECS obtaining the ACR mode information includes the following situations:

[0589] Situation 1, the ECS formulates the ACR mode information.

[0590] Exemplarily, in the embodiments of the present application, the ACR mode information formulated by the ECS may also be the ACR mode information set according to the capabilities of the AC, EEC, EAS, and EES. Specifically, it includes:

[0591] Step 1141, the ECS receives second information from the EAS.

[0592] The second information includes the ACR capability information supported by the EAS, and / or the ACR method request information.

[0593] Among them, the ACR capability information supported by the EAS indicates the ACR trigger event or application type corresponding to the ACR process that the EAS can execute (or detect), or the ACR event that the EAS can detect, or the application in which the EAS can detect the occurrence of ACR, or the ACR method supported or preferred by the EAS, or the priority of the ACR method corresponding to each AC ID;

[0594] The ACR method request information (referred to as request ACR method, or referred to as request ACR scenario) is used to request the allocation of an ACR method. It can request the EES to allocate an ACR method or recommend an ACR method for each AC, or the EAS carries an AC profile in the ACR method request information to request the EES to allocate an ACR method or recommend an ACR method for the required AC.

[0595] The specific sending process of the second information in this embodiment includes:

[0596] From the EAS to the EES (e.g., through the EAS registration request, EAS registration update request, UE location request message, subscription request message, ACR management request message, subscription request message, AC information subscription request message, subscription request message, UE identification API request message, subscription request message, QoS session creation response request message, subscription request message, etc., EDGE-3 related subscription corresponding request messages, subscription request messages); from the EES to the ECS (e.g., service activation process).

[0597] Step 1142, the ECS receives first information from the EEC.

[0598] The first information includes at least one of the ACR capability information supported by the AC, the ACR capability information supported by the EEC, the first ACR method request information, or the third ACR method request information.

[0599] Among them, the ACR capability information supported by the AC indicates the ACR trigger event or application type corresponding to the ACR process that the AC can execute (or detect), or the ACR event that the AC can detect, or the application in which the AC can detect the occurrence of ACR, or the ACR method supported or preferred by the AC, or the priority of the ACR method corresponding to each AC ID;

[0600] The third ACR method request information (referred to as request ACR method, or referred to as request ACR scenario) is used to request the allocation of an ACR method, and can allocate an ACR method for each AC or suggest an ACR method, or the AC carries AC-related information (such as, AC ID) in the ACR method request information, and requests the allocation of an ACR method or suggests an ACR method for the required AC;

[0601] The ACR capability information supported by the EEC indicates the ACR trigger event or application type corresponding to the ACR process that the EEC can execute (or detect), or the ACR event that the EEC can detect, or the application in which the EEC can detect the occurrence of ACR, or the ACR method supported or preferred by the EEC, or the priority of the ACR method corresponding to each AC ID;

[0602] The first ACR method request information (referred to as request ACR method, or referred to as request ACR scenario) is used to request the allocation of an ACR method, and can allocate an ACR method for the EEC for each AC request or suggest an ACR method, or the AC carries AC-related information (such as, AC ID) in the ACR method request information, and requests the allocation of an ACR method for the EEC or suggests an ACR method for the required AC.

[0603] When the first information includes the ACR capability information supported by the AC, and / or, the third ACR method request information, the AC sends an AC profile to the EEC through the EDGE-5 interface, and the AC profile includes the ACR capability information supported by the AC, and / or, the third ACR method request information.

[0604] The specific sending process of the first information in this embodiment includes:

[0605] From the EEC to the ECS (such as, the first information is carried in a service provisioning request message).

[0606] As a possible implementation, the EEC can implicitly report the above first information.

[0607] For example, the two types of events included in the first ACR method request information subscribed by the EEC from the EES can be understood as the EEC subscribing to two types of ACR events from the EES (e.g., target information notification and ACR complete notify).

[0608] Among them, subscribing to the target information notification applies to ACR methods initiated by the EAS or the EES (including the S-EAS decided ACR scenario, the S-EES executed ACR, and the Automated ACR), that is, ACR methods initiated by the network side.

[0609] When the EES or the EAS executes the T-EAS discovery process, that is, the target EAS discovery process initiated by the EAS or the EES, the EES or the EAS needs to send the discovered target information notification to the EEC. The target information notification includes the information related to the selected target EES and the information related to the selected target EAS.

[0610] The ACR complete notify applies to all ACR methods. The EEC subscribes to the ACR complete information from the EES (or when the EEC does not subscribe to notifications related to the execution of the ACR process such as the target information notification, it implicitly indicates that the EEC does not initiate the ACR process actively), which is used for the network side to notify the completion of the ACR (the completion of the application context relocation, and further can include the completion of the application context transmission and / or the completion of the EEC context transmission). According to the different ACR information subscribed by the EEC, the EES can determine whether the EEC has selected one of the three ACR processes for the EEC to execute (e.g., Initiation by EEC using regular EAS Discovery, EEC executed ACR via S-EES, EEC executed ACR via T-EES).

[0611] Furthermore, the EEC carries the AC ID, and its corresponding ACR event target information notification and / or ACR complete notify in the ACR information request message, for implicitly indicating that the ACR method selected by the EES for each AC is the ACR method initiated by the network side (S-EAS decided ACR scenario, S-EES executed ACR, Automated ACR) or the ACR method initiated by the EEC side (Initiation by EEC using regular EAS Discovery, EEC executed ACR via S-EES, EEC executed ACR via T-EES).

[0612] Step 1143, the ECS receives the fifth information from the EES.

[0613] The fifth information includes at least one of the ACR capability information supported by the EES, the ACR capability information supported by the EAS, the fourth ACR method request information, or the second ACR method request information.

[0614] Among them, the ACR capability information supported by the EAS indicates the ACR trigger event or application type corresponding to the ACR process that the EAS can execute (or detect), or the ACR event that the EAS can detect, or the application where the EAS can detect the occurrence of ACR, or the ACR method supported or preferred by the EAS, or the priority of the ACR method corresponding to each AC ID;

[0615] The second ACR method request information (referred to as request ACR method, or referred to as request ACR scenario) is used to request the allocation of an ACR method, and can request the EES to allocate an ACR method or suggest an ACR method for the EAS for each AC, or the EAS carries AC-related information (such as, AC ID) in the ACR method request information, and requests the EES to allocate an ACR method or suggest an ACR method for the EAS for the required AC;

[0616] The ACR capability information supported by the EES indicates the ACR trigger event or application type corresponding to the ACR process that the EES can execute (or detect), or the ACR event that the EES can detect, or the application where the EES can detect the occurrence of ACR, or the ACR method supported or preferred by the EES, or the priority of the ACR method corresponding to each AC ID;

[0617] The fourth ACR method request information (referred to as request ACR method or request ACR scenario) is used to request the allocation of ACR methods, and can allocate or recommend ACR methods for the EES for each AC request. Alternatively, the AC carries AC-related information (e.g., AC ID) in the ACR method request information, and allocates or recommends ACR methods for the EES for the required AC requests.

[0618] In the case where the fifth information includes the ACR capabilities information supported by the EAS and / or the second ACR method request information, the EAS sends a message to the EES (e.g., through an EAS registration response message, an EAS registration update response message, a UE location response message, a notification message, an ACR management response message, a notification message, an AC information subscription response message, a notification message, a UE identifier API response message, a notification message, a QoS session creation response message, a notification message, an ACR management event response message, a notification message, etc., corresponding response messages and notification messages related to EDGE-3 subscriptions). The message includes the ACR capabilities information supported by the EAS and / or the second ACR method request information.

[0619] The specific sending process of the fifth information in this embodiment includes:

[0620] From the EES to the ECS (e.g., in the service activation process).

[0621] Step 1144, the ECS formulates ACR mode information.

[0622] The ECS sets the ACR trigger rules according to the information reported by the AC, EAS, EEC, and EES, that is, for ACR events (UE mobility, EAS overload) or for application types, it allocates the events or application types that each functional entity (AC, EAS, EEC, EES) needs to detect and execute ACR.

[0623] And / or, the ECS sets the ACR method corresponding to each AC according to the supported ACR methods or preferred ACR methods reported by the AC, EAS, EEC, and EES.

[0624] Exemplarily, for the ACR event types reported by each entity, for example, for AC#1, AC supports detecting UE mobility events, EEC supports detecting UE mobility events, EES supports detecting UE mobility events and EAS overload events, and EAS supports detecting UE overload events. Then, ECS can set the ACR method of the application corresponding to this AC to be executed by EES, S-EESexecuted ACR. After each entity receives the ACR method of the application corresponding to the AC, EES performs the detection and determination of ACR, and the remaining entities perform the relevant required steps in the ACR process (subsequent steps will be called and executed by the relevant entities). For example, EES notifies EAS to perform the transmission of the application context, etc.

[0625] For the information of the application type or application-related information (such as, AC ID) reported by each entity, for example, for AC ID#1, AC supports ACR method#1 and ACR method#2, EEC#1 supports ACR method#2 and ACR method#3, EES supports ACR method#1 and ACR method#2, and EAS supports ACR method#2 and ACR method#3. Then, ECS can set the ACR method of the application corresponding to this AC ID#1 to be ACR method#2, and the remaining entities perform the relevant required steps in the ACR process (subsequent steps will be called and executed by the relevant entities).

[0626] If the ACR methods supported by each entity are contrary and conflicting, then when the ACR mode information is sent down, a failure indication message can be returned, and the failure reason carried in the failure indication message is that the ACR methods supported by each entity are contrary and conflicting, or further includes the re-reported information of each entity (such as, updated first information, updated fifth information, etc.).

[0627] Case 2: ECS sets the ACR trigger rule.

[0628] Step 1145, ECS assigns the events or application types that need to be detected and executed for ACR to each functional entity (AC, EAS, EES, EEC) for the ACR event (such as, UE mobility, EAS overload) or for the application type.

[0629] Exemplarily, ECS sets the ACR method corresponding to each AC (such as AC ID).

[0630] In the embodiments of the present application, there is no limitation on how ECS sets the ACR mode information. It can be set according to the historical ACR process or can also be set according to the capabilities of each functional entity.

[0631] Specifically, after ECS obtains the ACR mode information, it needs to send the ACR mode information to other functional entities. Figure 11The (b) in

[0632] Step 1146, the ECS sends ACR mode information to the EEC.

[0633] Referring to the above Step 1150, it will not be elaborated here.

[0634] Step 1147, the ECS sends ACR mode information to the EES.

[0635] It should be noted that the ECS sends ACR mode information to the EES. It can actively send a message carrying ACR mode information (such as an EES registration (update) response message) to the EES, or implicitly or explicitly subscribe to ACR mode information in the process of the EES reporting information. After the ECS obtains the ACR mode information, it can send a notification message to the EES.

[0636] Another possible implementation method is that when the EES does not implicitly or explicitly subscribe to the above notification message, after the ECS obtains the ACR mode information, it can notify the EES to implicitly or explicitly subscribe to the ACR mode information. After the EES subscribes to the ACR mode information, it sends an ACR mode information notification to the EES.

[0637] Exemplarily, as an implementation method of the above EES explicitly subscribing to ACR mode information: the EES subscribes to ACR mode information and requests the ECS to send ACR mode information to the EES after obtaining the ACR mode information;

[0638] Exemplarily, as an implementation method of the above EES implicitly subscribing to ACR mode information: when the EES subscribes to ACR information notifications and other ACR-related notification information from the ECS, it requests the ECS to send ACR mode information in the ACR information notifications and other ACR-related information notification information after obtaining the ACR mode information.

[0639] Exemplarily, the ECS sends an EES registration response message to the EES, and the EES registration response message includes the ACR mode information.

[0640] Step 1148, the EES sends ACR mode information to the EAS.

[0641] It should be noted that for the EES to send ACR mode information to the EAS, it can be achieved by the EES actively sending a message carrying the ACR mode information (such as, EAS registration (update) response message, EAS registration response message, EAS registration update response message, UE location response message, notification message, ACR management response message, notification message, AC information subscription response message, notification message, UE identifier API response message, notification message, QoS session creation response message, notification message, ACR management event response message, notification message, etc., corresponding response messages and notification messages related to EDGE-3 subscriptions) to the EAS, or the EAS implicitly or explicitly subscribes to the ACR mode information during the process of reporting information. After the EES obtains the ACR mode information, it can send a notification message to the EAS.

[0642] Another possible implementation method is that when the EAS does not implicitly or explicitly subscribe to the above notification message, after the EES obtains the ACR mode information, it can notify the EAS to subscribe to the ACR mode information. After the EAS subscribes to the mode information, it sends an ACR mode information notification to the EAS.

[0643] Exemplarily, as an implementation manner of the above EAS explicitly subscribing to the ACR mode information: the EAS subscribes to the ACR mode information and requests the EES to send the ACR mode information to the EAS after obtaining the ACR mode information;

[0644] Exemplarily, as an implementation manner of the above EAS implicitly subscribing to the ACR mode information: when the EAS subscribes to ACR-related notification information such as ACR information notification from the EES, it requests the EES to send the ACR mode information in the ACR information notification and other ACR-related information notification messages after obtaining the ACR mode information.

[0645] Figure 12 It is a schematic flowchart of another method for migrating context provided by the present application.

[0646] Specifically, from Figure 12 it can be seen that the EES obtaining the ACR mode information includes the following situations:

[0647] Situation 1: The EES receives the ACR mode information from the EEC. It includes the following steps:

[0648] Step 1210, the EES receives the ACR mode information from the EEC.

[0649] Referring to the above step 1171, it will not be elaborated here.

[0650] In Figure 12In the first case shown, after the EES obtains the ACR mode information, it can send the ACR mode information to the EAS. Figure 12 The method flow shown also includes:

[0651] Step 1211, the EES sends the ACR mode information to the EAS.

[0652] Exemplarily, the EES sending the ACR mode information to the EAS can be the ACR rule information or the ACR method corresponding to the AC ID.

[0653] It should be noted that the EES sending the ACR mode information to the EAS can actively send a message carrying the ACR mode information by the EES (such as, EAS registration response message, EAS registration update response message, UE location response message, notification message, ACR management response message, notification message, AC information subscription response message, notification message, UE identifier API response message, notification message, QoS session creation response message, notification message, ACR management event response message, notification message, etc., response messages and notification messages corresponding to EDGE-3 related subscriptions such as service activation (update) response message) to the EAS, or implicitly or explicitly subscribes to the ACR mode information in the process of the EAS reporting information. After the EES obtains the ACR mode information, it can send a notification message to the EAS.

[0654] Another possible implementation method is that when the EAS does not implicitly or explicitly subscribe to the above notification message, after the EES obtains the ACR mode information, it can notify the EEC to implicitly or explicitly subscribe to the ACR mode information. After the EAS subscribes to the ACR mode information, it sends an ACR mode information notification to the EAS.

[0655] Exemplarily, as an implementation manner of the above EAS explicitly subscribing to the ACR mode information: The EAS subscribes to the ACR mode information and requests the EES to send the ACR mode information to the EAS after obtaining the ACR mode information;

[0656] Exemplarily, as an implementation manner of the above EAS implicitly subscribing to the ACR mode information: When the EAS subscribes to ACR information notifications and other ACR-related notification information from the EES, it requests the EES to send the ACR mode information in the ACR information notifications and other ACR-related information notifications after obtaining the ACR mode information.

[0657] As a possible implementation manner, such as Figure 3 shown in (c) of the EAS registration process, the ACR mode information can be sent to the EAS in the EAS registration process.

[0658] For example, the EES sends an EAS registration response message or an EAS registration update response message to the EAS, and the ACR mode information is carried in the EAS registration response message or the EAS registration update response message. The cells carried in the EAS registration response message or the EAS registration update response message are shown in Table 12 below:

[0659] Table 12

[0660]

[0661] Optionally, before the EES sends an EAS registration response message to the EAS, the EAS sends an EAS registration request message to the EES; or,

[0662] before the EES sends an EAS registration update response message to the EAS, the EAS sends an EAS registration update request message to the EES.

[0663] As another possible implementation, as shown in (b) of Figure 4 the AC information subscription process, the ACR mode information can be sent to the EAS during the AC information subscription process.

[0664] For example, the EES sends an AC information subscription response message to the EAS, and the AC information subscription response message includes the ACR mode information.

[0665] As yet another possible implementation, as shown in (c) of Figure 4 the AC information notification process, the ACR mode information can be sent to the EAS during the AC information notification process.

[0666] For example, the EES sends an AC information notification message to the EAS, the AC information notification message carries AC-related information (such as, ACID) (the cells carried in the AC information notification message are as described in Table 4c above), and the AC profile includes the ACR mode information (the cells carried in the AC profile are as described in Table 8 above).

[0667] Still for example, the EES sends an AC information notification message to the EAS, and the cells carried in the AC information notification message are shown in the following table:

[0668]

[0669] Case 2: The EES obtains the ACR mode information from the EES configuration file (EES profile) in the EES; or rather, the EES determines the ACR mode information from the EES profile.

[0670] For example, the ACR mode information is pre-configured in the EES profile.

[0671] In Case 2, the EES obtains the ACR mode information, including Figure 12 the step S1220 shown in Figure 12 , where the EES obtains the ACR mode information from the EES configuration file in the EES.

[0672] It can be understood that the ACR mode information is predefined in the EES profile. In Case 2, the cells that can be included in the EES profile are shown in Table 13 below:

[0673] Table 13

[0674]

[0675]

[0676] In Figure 12 Case 2 shown in Figure 12 , after the EES obtains the ACR mode information, it can send the ACR mode information to the EAS and / or the EEC. Specifically, it can send the determined ACR method to the EAS and / or the EEC. Figure 12 The method flow shown in Figure 12 further includes:

[0677] Step 1221, the EES sends the ACR mode information to the EAS.

[0678] Referring to the description of Step 1211 above, it will not be elaborated here.

[0679] Step 1222, the EES sends the ACR mode information to the EEC.

[0680] Referring to Figure 11 the description of Step 1130 shown in Figure 11 , it will not be elaborated here.

[0681] Case 3: The EES receives the ACR mode information from the ECS. It includes the following steps:

[0682] Step 1230, the ECS obtains the ACR mode information.

[0683] Referring to Figure 11 the description of Step 1140 shown in (a) in Figure 11 , it will not be elaborated here.

[0684] Step 1240, the ECS sends the ACR mode information to the EES.

[0685] Referring to Figure 11 the description of Step 1147 shown in (b) in Figure 11 , it will not be elaborated here.

[0686] In Figure 12 Case 3 shown in Figure 12 , after the EES obtains the ACR mode information, it can send the ACR mode information to the EAS and / or the EEC.Figure 12 The method flow shown also includes:

[0687] Step 1241, the EES sends ACR mode information to the EAS.

[0688] Referring to the description of step 1211 above, it will not be elaborated here.

[0689] Step 1242, the EES sends ACR mode information to the EEC.

[0690] Referring to Figure 11 the description of step 1130 shown therein, it will not be elaborated here.

[0691] Case 4: The EES receives ACR mode information from the EAS. It includes the following steps:

[0692] Step 1250, the EAS obtains ACR mode information.

[0693] The following will combine Figure 13 to describe in detail the possible ways for the EAS to obtain ACR mode information. It will not be elaborated here.

[0694] Step 1260, the EAS sends ACR mode information to the EES.

[0695] It should be noted that: when the EAS sends ACR mode information to the EES, it can actively send a message carrying ACR mode information (such as, EAS registration request, EAS registration update request, UE location request message, subscription request message, ACR management request message, subscription request message, AC information subscription request message, subscription request message, UE identifier API request message, subscription request message, QoS session creation response request message, subscription request message, ACR management event request message, subscription request message, etc., corresponding request messages for EDGE-3 related subscriptions, corresponding request messages for EDGE-3 related subscriptions or subscription requests) to the EES, or implicitly or explicitly subscribes to ACR mode information in the process of the EES reporting information. After the EAS obtains ACR mode information, it can send a notification message to the EES.

[0696] Another possible implementation method is that when the EES does not implicitly or explicitly subscribe to the above notification message, after the EAS obtains ACR mode information, it can notify the EES to implicitly or explicitly subscribe to ACR mode information. After the EES subscribes to ACR mode information, it sends an ACR mode information notification to the EES.

[0697] Exemplarily, as an implementation manner for the above EES to subscribe to ACR mode information: the EES subscribes to the ACR mode information, and requests the EAS to send the ACR mode information to the EES after obtaining the ACR mode information;

[0698] Exemplarily, as an implementation manner for the above EES to implicitly subscribe to ACR mode information: when the EES subscribes to ACR-related notification information such as ACR information notification from the EAS, it requests the EAS to send the ACR mode information to the EES in the ACR information notification and other ACR-related information notification messages after obtaining the ACR mode information.

[0699] As a possible implementation manner, as shown in (c) of Figure 3 the EAS registration process shown, the ACR mode information can be sent to the EES during the EAS registration process.

[0700] For example, the EAS sends an EAS registration request message to the EES, and the ACR mode information is carried in the EAS registration request message.

[0701] As another possible implementation manner, as shown in (b) of Figure 4 the AC information subscription process shown, the ACR mode information can be sent to the EES during the AC information subscription process.

[0702] For example, the EAS sends an AC information subscription request message to the EES, and the ACR mode information is included in the AC information subscription request message.

[0703] In Figure 12 Case 4 shown, after the EES obtains the ACR mode information, it can send the ACR mode information to the EEC, Figure 12 the method flow shown further includes:

[0704] Step 1261, the EES sends the ACR mode information to the EEC.

[0705] Referring to the description of step 1130 shown in Figure 11 it will not be elaborated here.

[0706] Case 5: The EES formulates the ACR mode information.

[0707] Exemplarily, in the embodiments of the present application, the EES formulating the ACR mode information may also be formulating the ACR mode information according to the information reported by the AC, EEC, and EAS. Specifically, it includes:

[0708] Step 1270, the EES receives the second information from the EAS.

[0709] The second information includes ACR capability information supported by EAS, and / or second ACR method request information.

[0710] Among them, the ACR capability information supported by EAS indicates the ACR trigger event or application type corresponding to the ACR process that EAS can execute (or detect), or the ACR event that EAS can detect, or the application where EAS can detect the occurrence of ACR, or the ACR method supported or preferred by EAS, or the priority of the ACR method corresponding to each AC ID;

[0711] The second ACR method request information (referred to as request ACR method, or referred to as request ACR scenario) is used to request the allocation of an ACR method, and can allocate an ACR method for EAS or suggest an ACR method for each AC request, or EAS carries AC-related information (such as AC ID) in the ACR method request information, and allocates an ACR method for EAS or suggests an ACR method for the required AC request.

[0712] The specific sending process of the second information in this embodiment includes:

[0713] EAS to EES (such as, through EAS registration request, EAS registration update request, UE location request message, subscription request message, ACR management request message, subscription request message, AC information subscription request message, subscription request message, UE identification API request message, subscription request message, QoS session creation response request message, subscription request message, ACR management event request message, subscription request message, etc., request messages and subscription requests corresponding to EDGE-3 related subscriptions).

[0714] As a possible implementation, as Figure 3 shown in (c) of, the ACR capability information supported by EAS can be sent to EES during the EAS registration process.

[0715] For example, EAS sends an EAS registration request message or an EAS registration update request message to EES, and the EAS registration request message or the EAS registration update request message carries the ACR capability information supported by EAS.

[0716] As another possible implementation, as Figure 4 shown in (b) of, the ACR capability information supported by EAS can be sent to EES during the AC information subscription process.

[0717] For example, EAS sends an AC information subscription request message to EES, and the AC information subscription request message includes the ACR capability information supported by EAS.

[0718] Step 1271, the EES receives the first information from the EEC.

[0719] The first information includes at least one of ACR capability information supported by the AC, ACR capability information supported by the EEC, first ACR method request information, or third ACR method request information.

[0720] Among them, the ACR capability information supported by the AC indicates the ACR trigger event or application type corresponding to the ACR process that the AC can execute (or detect), or the ACR event that the AC can detect, or the application in which the AC can detect the occurrence of ACR, or the ACR method supported or preferred by the AC, or the priority of the ACR method corresponding to each AC ID;

[0721] The third ACR method request information (referred to as request ACR method, or referred to as request ACR scenario) is used to request the allocation of an ACR method, and can allocate an ACR method for each AC or suggest an ACR method, or the AC carries AC-related information (such as AC ID) in the ACR method request information, and requests the allocation of an ACR method or suggests an ACR method for the required AC;

[0722] The ACR capability information supported by the EEC indicates the ACR trigger event or application type corresponding to the ACR process that the EEC can execute (or detect), or the ACR event that the EEC can detect, or the application in which the EEC can detect the occurrence of ACR, or the ACR method supported or preferred by the EEC, or the priority of the ACR method corresponding to each AC ID;

[0723] The first ACR method request information (referred to as request ACR method, or referred to as request ACR scenario) is used to request the allocation of an ACR method, and can allocate an ACR method for the EEC for each AC or suggest an ACR method, or the AC carries AC-related information (such as AC ID) in the ACR method request information, and requests the allocation of an ACR method for the EEC for the required AC or suggests an ACR method.

[0724] When the first information includes the ACR capability information supported by the AC and / or the third ACR method request information, the AC sends an AC profile to the EEC through the EDGE-5 interface, and the AC profile includes the ACR capability information supported by the AC and / or the third ACR method request information.

[0725] The specific sending process of the first information in this embodiment includes:

[0726] From EES to EEC (e.g., processes related to EDGE-1 such as discovering EEC registration by EAS, subscribing to EAS discovery, etc.).

[0727] As a possible implementation, such as Figure 3 In the EEC registration process shown in (b) of , the first information can be sent to EES during the EEC registration process.

[0728] For example, the EEC sends an EEC registration request message to the EES, and the first information is carried in the EEC registration request message.

[0729] As another possible implementation, such as Figure 4 In the conventional EAS discovery process shown in (a) of , the first information can be sent to the EES during the conventional EAS discovery process.

[0730] As another possible implementation, such as Figure 4 In the EAS discovery subscription process shown in (a) of , the first information can be sent to the EES in the EAS discovery subscription request.

[0731] For example, the EEC sends an EAS discovery request message to the EES, and the first information is carried in the EAS discovery request message.

[0732] Among them, the ACR capability information supported by the AC, and / or the third ACR method request information is obtained from the AC through step 1272.

[0733] Step 1272, the EEC receives the third information from the AC.

[0734] The third information includes the ACR capability information supported by the AC, and / or the third ACR method request information.

[0735] Exemplarily, the AC sends the third information to the EEC through the EDGE-5 interface.

[0736] Step 1280, the EES formulates the ACR mode information.

[0737] The EES sets the ACR trigger rule according to the information reported by the AC, EEC, EES, and EAS, that is, for ACR events (UE mobility, EAS overload) or for application types, assigns the events or application types that each functional entity (AC, EAS, EES, EEC) needs to detect and execute ACR.

[0738] And / or, the EES sets the ACR method corresponding to each AC according to the supported ACR methods or preferred ACR methods reported by the AC, EAS, and EEC.

[0739] Exemplarily, for the ACR event types reported by each entity, for example, for AC#1, the AC supports detecting UE mobility events, the EEC supports detecting UE mobility events, the EES supports detecting UE mobility events and EAS overload events, and the EAS supports detecting UE overload events. Then, the EES can set the ACR method of the application corresponding to this AC to be executed by the EES, S-EESexecuted ACR. After each entity receives the ACR method of the application corresponding to the AC, the EES performs the detection and determination of the ACR, and the remaining entities perform the relevant required steps in the ACR process (subsequent steps will be called and executed by the relevant entities). For example, the EES notifies the EAS to perform the transmission of the application context, etc.

[0740] For the information of the application type or application-related information (such as, AC ID) reported by each entity, for example, for AC ID#1, the AC supports ACR method#1 and ACR method#2, EEC#1 supports ACR method#2 and ACR method#3, the EES supports ACR method#1 and ACR method#2, and the EAS supports ACR method#2 and ACR method#3. Then, the EES can set the ACR method of the application corresponding to this AC ID#1 to ACR method#2, and the remaining entities perform the relevant required steps in the ACR process (subsequent steps will be called and executed by the relevant entities).

[0741] If the ACR methods supported by each entity are contrary and conflicting, when the ACR mode information is sent down, a failure indication message can be returned, and the failure reason carried in the failure indication message is that the ACR methods supported by each entity are contrary and conflicting, or further includes the re-reported information of each entity (such as, the updated second information, the updated fifth information, etc.).

[0742] In Figure 12 In case five shown, after the EES obtains the ACR mode information, it can send the ACR mode information to the EAS and / or the EEC. Figure 12 The method flow shown further includes:

[0743] Step 1281, the EES sends the ACR mode information to the EAS.

[0744] Referring to the description of step 1211 above, it will not be elaborated here.

[0745] Step 1282, the EES sends the ACR mode information to the EEC.

[0746] Referring to Figure 11 the description of step 1130 shown, it will not be elaborated here.

[0747] Figure 12In the cases shown in Case 1 to Case 5 as shown, after the EEC obtains the ACR mode information, it can send the ACR mode information to the AC. Figure 12 The method flow shown also includes:

[0748] Step 1283, the EEC sends the ACR mode information to the AC.

[0749] Reference Figure 10 For the description of step 1021 shown in, it will not be elaborated here.

[0750] As can be seen from the above, the conditional information included in the ACR mode information can be used to indicate the fourth condition. When the fourth condition is met, the EES executes the ACR process for the fourth application in at least one application. Figure 12 The method flow shown may also include:

[0751] Step 1290, the EES executes the ACR process for the fourth application in at least one application.

[0752] Exemplarily, when the EES determines that the fourth condition is met (for example, when the ACR information indicates that the ACR trigger event is UE movement and the functional entity executing the ACR is the EES; also for example, when the ACR mode information indicates that the application identifier is AC ID#4 and the method for executing the ACR is that the EEC executes the ACR through the S-EES), the EES executes the ACR process for the fourth application in at least one application (for example, the ACR process for the fourth application is the ACR process when the ACR trigger event is UE movement).

[0753] Specifically, for the EES to determine whether the fourth condition is met, it can be that the EES monitors the application type to which the application that needs to perform context migration belongs, or the event type that triggers context migration, or the identifier of the application that needs to perform context migration.

[0754] Exemplarily, the EES executes the ACR process according to the selected ACR method.

[0755] Exemplarily, the EES executes the ACR process according to the ACR method corresponding to the AC ID, and / or executes the corresponding ACR method corresponding to the AC ID, and further executes the relevant steps in the above ACR method.

[0756] Figure 13 It is a schematic flowchart of another method for context migration provided by the present application.

[0757] Specifically, from Figure 13 it can be seen that the EAS obtaining the ACR mode information includes the following situations:

[0758] Case 1: The EAS receives the ACR mode information from the EES. It includes the following steps:

[0759] Step 1310, the EAS receives the ACR mode information from the EES.

[0760] Referring to the description of step 1211 above, it will not be elaborated here.

[0761] Case 2: The EAS obtains the ACR mode information from the EAS configuration file (EAS profile) in the EAS; or rather, the EAS determines the ACR mode information from the EAS profile.

[0762] For example, the ACR mode information is pre-configured in the EAS profile.

[0763] As a possible implementation, the ACR mode information pre-configured in the EAS profile is formulated by the EAS according to the information reported by each entity. Specifically, it includes:

[0764] Step S1321, the EAS receives the third information from the AC.

[0765] The third information includes the ACR capability information supported by the AC, and / or the third ACR method request information.

[0766] Among them, the ACR capability information supported by the AC indicates the ACR trigger event or application type corresponding to the ACR process that the AC can execute (or detect), or the ACR event that the AC can detect, or the application where the AC can detect the occurrence of ACR, or the ACR method supported or preferred by the AC, or the priority of the ACR method corresponding to each AC ID;

[0767] The third ACR method request information (referred to as request ACR method, or referred to as request ACR scenario) is used to request the allocation of ACR methods, and can allocate ACR methods for each AC or suggest ACR methods, or the AC carries AC-related information (such as, AC ID) in the ACR method request information to request the allocation of ACR methods or suggest ACR methods for the required AC.

[0768] The specific sending process of the third information in this embodiment includes:

[0769] AC to EEC (e.g., via the EDGE-5 interface); EEC to EES (e.g., via EDGE-1 related processes such as EAS discovery of EEC registration, EAS discovery subscription, etc.); EES to EAS (e.g., ACR management response messages, notification messages, AC information subscription response messages, notification messages, UE identification API response messages, notification messages, QoS session creation response messages, notification messages, ACR management event response messages, notification messages, etc., corresponding to subscriptions related to EDGE-3).

[0770] Step S1322, the EAS receives first information from the EEC.

[0771] The first information includes at least one of ACR capability information supported by the AC, ACR capability information supported by the EEC, first ACR method request information, or third ACR method request information.

[0772] Among them, the ACR capability information supported by the EEC indicates the ACR trigger event or application type corresponding to the ACR process that the EEC can execute (or detect), or the ACR event that the EEC can detect, or the application for which the EEC can detect the occurrence of ACR, or the ACR method supported or preferred by the EEC, or the priority of the ACR method corresponding to each AC ID;

[0773] The first ACR method request information (referred to as request ACR method, or referred to as request ACR scenario) is used to request the allocation of an ACR method, and can allocate an ACR method for the EEC or suggest an ACR method for each AC request, or the AC carries AC-related information (e.g., AC ID) in the ACR method request information, and allocates an ACR method for the EEC or suggests an ACR method for the required AC request.

[0774] In the case where the first information includes ACR capability information supported by the AC, and / or, third ACR method request information, the AC sends an AC profile to the EEC via the EDGE-5 interface, and the AC profile includes ACR capability information supported by the AC, and / or, third ACR method request information.

[0775] The specific sending process of the first information in this embodiment includes:

[0776] EEC to EES (e.g., EDGE-1 related processes such as EEC registration discovery via EAS, EAS discovery subscription, etc.); EES to EAS (e.g., response messages corresponding to EDGE-3 related subscriptions in EAS registration (update) response messages, EAS registration response messages, EAS registration update response messages, UE location response messages, notification messages, ACR management response messages, notification messages, AC information subscription response messages, notification messages, UE identification API response messages, notification messages, QoS session creation response messages, notification messages, ACR management event response messages, notification messages, etc.).

[0777] Step S1323, EAS receives the fifth information from EES.

[0778] The fifth information includes at least one of ACR capability information supported by EES, ACR capability information supported by EAS, fourth ACR method request information, or second ACR method request information.

[0779] Among them, the ACR capability information supported by EAS indicates the ACR trigger event or application type corresponding to the ACR process that EAS can execute (or detect), or the ACR event that EAS can detect, or the application where ACR can occur that EAS can detect, or the ACR method supported or preferred by EAS, or the priority of the ACR method corresponding to each AC ID;

[0780] The second ACR method request information (referred to as request ACR method, or referred to as request ACR scenario) is used to request the allocation of an ACR method, and can request EES to allocate an ACR method or recommend an ACR method for EAS for each AC, or EAS carries AC-related information (such as AC ID) in the ACR method request information, and requests EES to allocate an ACR method or recommend an ACR method for EAS for the required AC.

[0781] When the fifth information includes the ACR capability information supported by EAS, and / or, the second ACR method request information, EAS sends a message to EES (e.g., via EAS registration response messages, EAS registration update response messages, UE location response messages, notification messages, ACR management response messages, notification messages, AC information subscription response messages, notification messages, UE identification API response messages, notification messages, QoS session creation response messages, notification messages, ACR management event response messages, notification messages, etc. corresponding to EDGE-3 related subscriptions) and the message includes the ACR capability information supported by EAS, and / or, the second ACR method request information.

[0782] The specific sending process of the fifth piece of information in this embodiment includes:

[0783] From EES to EAS (such as, in response messages for EAS registration (update), EAS registration, EAS registration update, UE location response messages, notification messages, ACR management response messages, notification messages, AC information subscription response messages, notification messages, UE identifier API response messages, notification messages, QoS session creation response messages, notification messages, ACR management event response messages, notification messages, etc., corresponding response messages for subscriptions related to EDGE-3).

[0784] In case two, the ACR mode information obtained by EAS includes Figure 13 Step S1320 as shown, where EAS obtains the ACR mode information from the EAS configuration file in EAS.

[0785] It can be understood that the ACR mode information is predefined in the EAS profile. In case two, the cells that can be included in the EAS profile are shown in Table 14 below:

[0786] Table 14

[0787]

[0788]

[0789] In Figure 13 In case two as shown, after EAS obtains the ACR mode information, it can send the ACR mode information to EES. Figure 13 The method process shown also includes:

[0790] Step 1330, EAS sends the ACR mode information to EES.

[0791] Refer to Figure 12 the description of Step 1260 as shown, which will not be elaborated here.

[0792] After EES obtains the ACR mode information, it can send the ACR rule information to EEC. Figure 13 The method process shown also includes:

[0793] Step 1340, EES sends the ACR mode information to EEC.

[0794] Refer to Figure 11 the description of Step 1130 as shown, which will not be elaborated here.

[0795] Step 1350, EEC sends the ACR mode information to AC.

[0796] Refer toFigure 10 The description of step 1021 shown herein will not be elaborated further here.

[0797] As can be seen from the above, the conditional information included in the ACR mode information can be used to indicate a third condition. When the third condition is met, the EAS executes the ACR process for a third application in at least one application. Figure 13 The method flow shown may further include:

[0798] Step 1360, the EAS executes the ACR process for a third application in at least one application.

[0799] Specifically, for the EAS to determine whether the fourth condition is met, it can be that the EAS monitors the application type to which the application that needs to perform context migration belongs, or the event type that triggers context migration, or monitors the identifier of the application that needs to perform context migration.

[0800] Exemplarily, the EAS executes the ACR process for the third application according to the ACR method corresponding to the identifier (AC ID) of the third application, and / or executes the ACR method corresponding to the third application, and further executes the relevant steps in the above ACR method.

[0801] This application also considers the situation where the ACR method for an AC does not match: for example, there is no negotiation of the ACR method in the embodiments shown above, or the negotiation of the above ACR method is executed but an error occurs in the negotiation. Furthermore, this application also provides a method for migrating context, which specifically includes the following steps: Figures 11 - 13 Step 1: The EEC initiates the ACR process. The EEC initiating the ACR process specifically corresponds to the EEC using regular EAS Discovery (Initiation by EEC using regular EAS Discovery) (in the manner shown above), the EEC executing the ACR via S-EES (EEC executed ACR via S-EES) (in the manner shown above), the EEC executing the ACR via T-EES (EEC executed ACR via T-EES) (in the manner shown above).

[0802] Step 2: The EEC sends a first message to the EES. The first message includes the AC ID, and / or, the EEC ID. Figure 2 Optionally, the first message is an ACR request message. Figure 5 Figure 6

[0803]

[0804]

[0805] ​​​​Exemplarily, in the three ACR scenarios initiated by the EEC, after the T-EAS is discovered and before the application context is transmitted, the EEC sends an ACR request message to the EES, carrying the AC ID, and / or, the EEC ID.

[0806] It should be understood that in step one, the ACR initiated by the EEC is for the ACR corresponding to this AC ID and / or EEC ID, that is, the ACR of this AC.

[0807] After the EEC receives the above first message, the steps to be executed include the following two cases:

[0808] Case one: Execute step three and step four below.

[0809] Step three: The EES receives this first message and determines whether the ACR process has been initiated on the EES side.

[0810] Specifically, in response to receiving this first information, the EES determines whether the ACR process corresponding to this AC ID and / or EEC ID has been initiated on the EES side.

[0811] Step four: The EES sends a second message to the EEC.

[0812] The second message includes indication information, and the indication information is used to indicate success or failure.

[0813] Optionally, the second message is an ACR response message.

[0814] As a possible implementation, if the EES determines that the EES has not initiated an application context migration for this AC, the EES returns an ACR response message to the EEC, carrying an indication information of success.

[0815] As another possible implementation, if the EES determines that the EES has initiated an application context migration for this AC, the EES returns an ACR response message to the EEC, and the ACR response message indicates that the ACR fails. For example, the ACR response message carries an indication information of ACR failure, and / or, the reason for failure.

[0816] The reason for the failure specifically indicates that the ACR methods do not match (or are inconsistent, conflicting, etc.), or the ACR method on the EEC side does not match the ACR method on the EES side, or the ACR method is for the EES to execute the ACR (S-EES executed ACR). This ACR response message can also carry the AC ID. Then this ACR response message can specifically also indicate that the ACR method of this AC does not match (or is inconsistent, conflicting, etc.), or the ACR method on the EEC side of this AC does not match the ACR method on the EES side, or the ACR method determined by the EES side for this AC is for the EES to execute the ACR (S-EES executed ACR), etc.

[0817] Case 2: Perform the following Step 5 and Step 6.

[0818] Step 5: The EES receives this first message and determines whether the ACR process has been initiated on the EAS side.

[0819] Specifically, in response to receiving this first information, the EES determines whether the ACR process corresponding to this AC ID and / or EEC ID has been initiated on the EAS side.

[0820] Step 6: The EES sends a second message to the EEC.

[0821] This second message includes indication information, and the indication information is used to indicate success or failure.

[0822] Optionally, this second message is an ACR response message.

[0823] As a possible implementation, if the EES determines that the EAS has not initiated an application context migration for this AC, the EES returns an ACR response message to the EEC and carries indication information of success.

[0824] As another possible implementation, if the EES determines that the EAS has initiated an application context migration for this AC, the EES returns an ACR response message to the EEC, and this ACR response message indicates that the ACR fails. For example, this ACR response message carries indication information of ACR failure, and / or, the reason for the failure.

[0825] The reason for the failure specifically indicates that the ACR methods do not match (or are inconsistent, conflicting, etc.), or the ACR method on the EEC side does not match the ACR method on the EES side, or the ACR method for the ACR scenario where the ACR method is for the EAS to execute the ACR (S-EAS decided ACRscenario).

[0826] The ACR response message may also carry the AC ID. Specifically, the ACR response message may also indicate that the ACR method of the AC does not match (or is inconsistent, in conflict, etc.), or that the ACR method on the EEC side of the AC does not match the ACR method on the EAS side, or that the ACR method determined by the EES side for the AC is the ACR method for the EAS to perform ACR (S-EAS decided ACR scenario), etc.

[0827] As another possible implementation, the EES may indicate ACR failure in the ACR information subscription response or ACR information notification message. For example, the ACR information subscription response or ACR information notification message carries an indication of ACR failure and / or the reason for the failure.

[0828] The reason for the failure specifically indicates that the ACR method does not match (or is inconsistent, in conflict, etc.), or that the ACR method on the EEC side does not match the ACR method on the EES side, or that the ACR method is the ACR method for the EAS to perform ACR (S-EAS decided ACR scenario).

[0829] The ACR information subscription response or ACR information notification message may also carry the AC ID. Specifically, the ACR information subscription response or ACR information notification message may also indicate that the ACR method of the AC does not match (or is inconsistent, in conflict, etc.), or that the ACR method on the EEC side of the AC does not match the ACR method on the EAS side, or that the ACR method determined by the EES side for the AC is the ACR method for the EAS to perform ACR (S-EAS decided ACR scenario), etc.

[0830] In the above method embodiments, the magnitudes of the sequence numbers of the above processes do not imply the order of execution. The order of execution of each process should be determined by its function and internal logic, and should not impose any limitation on the implementation process of the embodiments of the present application. And it is possible that not all the operations in the above method embodiments need to be executed.

[0831] It should be understood that in the above method embodiments, each functional entity may execute some or all of the steps in the embodiments. These steps or operations are only examples, and the embodiments of the present application may also include performing other operations or various deformations of the operations.

[0832] It can be understood that in the above method embodiments, the methods implemented by the AC, EEC, EAS, EES, or ECS can also be implemented by components (such as chips or circuits, etc.) available for the AC, EEC, EAS, EES, or ECS.

[0833] It should also be understood that in various embodiments of the present application, without special instructions and logical conflicts, the terms and / or descriptions between different embodiments can be consistent and can refer to each other. The technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.

[0834] The method for migrating context in the embodiments of the present application has been introduced in detail above in conjunction with Figures 10 to 13 The device for migrating context provided in the embodiments of the present application will be introduced in detail below in conjunction with Figures 14 - 23 Referring to

[0835] See Figure 14 , Figure 14 FIG. 14 is a schematic diagram of a device 1400 for migrating context provided by the present application. As Figure 14 shown, the device 1400 includes a processing unit 1410, an acquisition unit 1420, and a sending unit 1430.

[0836] The acquisition unit 1420 is configured to acquire application context migration (ACR) mode information;

[0837] The processing unit 1410 is configured to determine an ACR method selected for at least one application according to the ACR mode information.

[0838] Exemplarily, the acquisition unit 1420 acquiring the ACR mode information includes:

[0839] The acquisition unit 1420 receives the ACR mode information from an application client (AC); or,

[0840] The acquisition unit 1420 receives the ACR mode information from an edge enabling server (EES) and / or an edge configuration server (ECS).

[0841] Exemplarily, when the acquisition unit 1420 receives the ACR mode information from the AC, the device 1400 further includes:

[0842] The sending unit 1430 is configured to send the ACR mode information to the edge enabling server EES;

[0843] When the acquisition unit 1420 receives the ACR mode information from the EES and / or the ECS, the device 1400 further includes:

[0844] The sending unit 1430 is configured to send the ACR mode information to the AC.

[0845] The EEC in the device 1400 corresponds to that in the method embodiment. The device 1400 can be the EEC in the method embodiment, or a chip or functional module inside the EEC in the method embodiment. The corresponding units of the device 1400 are used to executeFigures 10 to 13 The corresponding steps executed by the EEC in the method embodiments shown.

[0846] Among them, the processing unit 1410 in the device 1400 is used to execute the steps related to processing corresponding to the EEC in the method embodiments. The acquisition unit 1420 in the device 1400 executes the acquisition steps of the EEC in the method embodiments. The sending unit 1430 in the device 1400 is used to execute the steps sent by the EEC.

[0847] The acquisition unit 1420 and the sending unit can form a transceiver unit, which has both acquisition and sending functions. Among them, the processing unit 1410 can be at least one processor. The sending unit 1430 can be a transmitter or an interface circuit, and the acquisition unit 1420 can be a receiver or an interface circuit. The receiver and the transmitter can be integrated together to form a transceiver or an interface circuit.

[0848] Optionally, the device 1400 may further include a storage unit, which is used to store data and / or signaling. The processing unit 1410, the acquisition unit 1420, and the sending unit 1430 can interact with or be coupled to the storage unit, for example, read or call the data and / or signaling in the storage unit, so that the methods in the above embodiments can be executed.

[0849] Each of the above units can exist independently, or can be integrated in whole or in part.

[0850] See Figure 15 , Figure 15 is a schematic structural diagram of the EEC 1500 applicable to the embodiments of the present application, which can be used to implement the functions of the above EEC.

[0851] The EEC 1500 includes a processor 1501, a memory 1502, and a transceiver 1503. Among them, instructions or programs are stored in the memory 1502. The processor 1502 and the transceiver 1503 are used to execute or call the instructions or programs stored in the memory 1502, so that the EEC 1500 realizes the functions of the EEC in the above method for migrating context. When the instructions or programs stored in the memory 1502 are executed, the transceiver 1503 is used to execute Figure 14 the operations executed by the sending unit 1430 and the acquisition unit 1420 in the embodiments shown, and the processor 1502 is used to execute Figure 14 the operations executed by the processing unit 1410 in the embodiments shown.

[0852] Those skilled in the art can understand that for the sake of convenience of description, Figure 15Only one memory and one processor are shown. In an actual user device, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, etc., and the embodiments of the present application do not limit this.

[0853] See Figure 16 , Figure 16 which is a schematic diagram of the device 1600 for migrating context provided by the present application. As Figure 16 shown, the device 1600 includes a processing unit 1610, an obtaining unit 1620, and a sending unit 1630.

[0854] The obtaining unit 1620 is configured to obtain application context migration (ACR) mode information, where the ACR mode information is used to determine the ACR method selected by at least one application;

[0855] The sending unit 1630 is configured to send the ACR mode information to an edge application service (EAS).

[0856] The ACR mode information includes ACR rule information, and the ACR rule information includes condition information for triggering the ACR process of at least one application;

[0857] The processing unit 1610 is configured to, when a fourth condition indicated by the condition information is satisfied, perform the ACR process for a fourth application among the at least one application.

[0858] Exemplarily, the obtaining unit 1620 obtaining the ACR mode information includes:

[0859] The obtaining unit 1620 obtains the ACR mode information according to at least one of the following information:

[0860] the ACR capability information supported by an edge application server (EAS), the ACR capability information supported by an EEC, the ACR capability information supported by an application client AC, and the ACR capability information supported by the device; or,

[0861] The obtaining unit 1620 obtains the ACR mode information from a configuration file of the device 1600, where the configuration file of the device 1600 includes the ACR mode information; or,

[0862] The obtaining unit 1620 receives the ACR mode information from the ECS; or,

[0863] The obtaining unit 1620 receives the ACR mode information from the edge application server (EAS) and / or the EEC.

[0864] Exemplarily, the device further includes:

[0865] A sending unit 1630, configured to send the ACR mode information to the EAS and / or the EEC.

[0866] The EES in the apparatus 1600 corresponds to that in the method embodiments. The apparatus 1600 may be the EES in the method embodiments, or a chip or functional module inside the EES in the method embodiments. The corresponding units of the apparatus 1600 are configured to execute Figures 10 to 13 the corresponding steps executed by the EES in the method embodiments shown.

[0867] Among them, the processing unit 1610 in the apparatus 1600 is configured to execute the steps related to processing corresponding to the EES in the method embodiments. The obtaining unit 1620 in the apparatus 1600 executes the steps of obtaining by the EES in the method embodiments. The sending unit 1630 in the apparatus 1600 is configured to execute the steps of sending by the EES.

[0868] The obtaining unit 1620 and the sending unit may form a transceiver unit, which has both the functions of obtaining and sending. Among them, the processing unit 1610 may be at least one processor. The sending unit 1630 may be a transmitter or an interface circuit, and the obtaining unit 1620 may be a receiver or an interface circuit. The receiver and the transmitter may be integrated together to form a transceiver or an interface circuit.

[0869] Optionally, the apparatus 1600 may further include a storage unit, which is configured to store data and / or signaling. The processing unit 1610, the obtaining unit 1620, and the sending unit 1630 may interact with or be coupled to the storage unit, for example, read or call the data and / or signaling in the storage unit, so that the methods in the above embodiments are executed.

[0870] The above units may exist independently, or may be integrated in whole or in part.

[0871] Refer to Figure 17 , Figure 17 is a schematic structural diagram of the EES 1700 applicable to the embodiments of the present application, which may be used to implement the functions of the above EES.

[0872] The EES 1700 includes a processor 1701, a memory 1702, and a transceiver 1703. Among them, instructions or programs are stored in the memory 1702. The processor 1702 and the transceiver 1703 are configured to execute or call the instructions or programs stored in the memory 1702, so that the EES 1700 realizes the functions of the EES in the method for migrating context above. When the instructions or programs stored in the memory 1702 are executed, the transceiver 1703 is configured to execute Figure 16 the operations executed by the sending unit 1630 and the obtaining unit 1620 in the embodiments shown, and the processor 1702 is configured to execute Figure 16The operations performed by the processing unit 1610 in the illustrated embodiment.

[0873] Those skilled in the art can understand that, for ease of explanation, Figure 17 only one memory and one processor are shown. In an actual user device, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, etc., and the embodiments of the present application do not limit this.

[0874] Refer to Figure 18 , Figure 18 is a schematic diagram of the device 1800 for migrating context provided by the present application. As Figure 18 shown, the device 1800 includes a processing unit 1810, an obtaining unit 1820, and a sending unit 1830.

[0875] The obtaining unit 1820 is configured to obtain application context migration (ACR) mode information, where the ACR mode information includes condition information for triggering the ACR process of at least one application;

[0876] The processing unit 1810 is configured to, when a second condition indicated by the condition information is satisfied, the AC execute the ACR process for a second application in the at least one application.

[0877] Exemplarily, the obtaining unit 1820 obtaining the ACR mode information includes:

[0878] The obtaining unit 1820 obtains the ACR mode information from the configuration file of the device 1800, and the configuration file of the device 1800 includes the ACR mode information; or,

[0879] The obtaining unit 1820 receives the ACR mode information from an edge enabling client (EEC).

[0880] Exemplarily, when the obtaining unit obtains the ACR mode information from the configuration file of the device 1800, the device further includes:

[0881] The sending unit 1830 is configured to send the ACR mode information to the EEC.

[0882] The AC in the device 1800 corresponds to the AC in the method embodiment. The device 1800 may be the AC in the method embodiment, or a chip or a functional module inside the AC in the method embodiment. The corresponding units of the device 1800 are configured to execute Figures 10 to 13 the corresponding steps executed by the AC in the illustrated method embodiment.

[0883] Among them, the processing unit 1810 in the device 1800 is used to execute the steps related to AC corresponding processing in the method embodiments. The acquisition unit 1820 in the device 1800 executes the steps of AC acquisition in the method embodiments. The sending unit 1830 in the device 1800 is used to execute the steps of AC sending.

[0884] The acquisition unit 1820 and the sending unit can form a transceiver unit, which has both the functions of acquisition and sending. Among them, the processing unit 1810 can be at least one processor. The sending unit 1830 can be a transmitter or an interface circuit, and the acquisition unit 1820 can be a receiver or an interface circuit. The receiver and the transmitter can be integrated together to form a transceiver or an interface circuit.

[0885] Optionally, the device 1800 may further include a storage unit, which is used to store data and / or signaling. The processing unit 1810, the acquisition unit 1820, and the sending unit 1830 can interact with or be coupled to the storage unit, for example, reading or calling the data and / or signaling in the storage unit, so that the methods in the above embodiments can be executed.

[0886] Each of the above units can exist independently, or can be integrated in whole or in part.

[0887] See Figure 19 , Figure 19 is a schematic structural diagram of the AC 1900 applicable to the embodiments of the present application, which can be used to implement the functions of the above AC.

[0888] The AC 1900 includes a processor 1901, a memory 1902, and a transceiver 1903. Among them, instructions or programs are stored in the memory 1902. The processor 1902 and the transceiver 1903 are used to execute or call the instructions or programs stored in the memory 1902, so that the AC 1900 can implement the functions of the AC in the above method for migrating context. When the instructions or programs stored in the memory 1902 are executed, the transceiver 1903 is used to execute Figure 18 the operations performed by the sending unit 1830 and the acquisition unit 1820 in the embodiments shown, and the processor 1902 is used to execute Figure 18 the operations performed by the processing unit 1810 in the embodiments shown.

[0889] Those skilled in the art can understand that, for the sake of convenience of description, Figure 19 only one memory and one processor are shown. In an actual user device, there may be multiple processors and memories. The memory can also be referred to as a storage medium or a storage device, etc., and the embodiments of the present application do not limit this.

[0890] See Figure 20 , Figure 20It is a schematic diagram of the device 2000 for migrating context provided by this application. As Figure 20 shown, the device 2000 includes a processing unit 2010, an acquisition unit 2020, and a sending unit 2030.

[0891] The acquisition unit 2020 acquires application context migration (ACR) mode information, and the ACR mode information includes condition information for triggering the ACR process of at least one application;

[0892] The processing unit 2010 is configured to, when a third condition indicated by the condition information is satisfied, the EAS executes the ACR process for a third application in the at least one application.

[0893] Exemplarily, the acquisition unit 2020 acquiring the EASR rule information includes:

[0894] The acquisition unit 2020 acquires the ACR mode information from the configuration file of the device 2000, and the ACR mode information is included in the configuration file of the device 2000; or,

[0895] The acquisition unit 2020 receives the ACR mode information from the edge enablement server (EES).

[0896] Exemplarily, when the acquisition unit 2020 acquires the ACR mode information from the configuration file of the device 2000, the device further includes:

[0897] The sending unit 2030 is configured to send the ACR mode information to the EES.

[0898] The EAS in the device 2000 corresponds to that in the method embodiment. The device 2000 may be the EAS in the method embodiment, or a chip or functional module inside the EAS in the method embodiment. The corresponding units of the device 2000 are used to execute Figures 10 to 13 the corresponding steps executed by the EAS in the shown method embodiment.

[0899] Among them, the processing unit 2010 in the device 2000 is used to execute the steps related to processing corresponding to the EAS in the method embodiment. The acquisition unit 2020 in the device 2000 executes the acquisition steps of the EAS in the method embodiment. The sending unit 2030 in the device 2000 is used to execute the sending steps of the EAS.

[0900] The acquisition unit 2020 and the sending unit may form a transceiver unit, which has both acquisition and sending functions. Among them, the processing unit 2010 may be at least one processor. The sending unit 2030 may be a transmitter or an interface circuit, and the acquisition unit 2020 may be a receiver or an interface circuit. The receiver and the transmitter may be integrated together to form a transceiver or an interface circuit.

[0901] Optionally, the apparatus 2000 may further include a storage unit for storing data and / or signaling. The processing unit 2010, the obtaining unit 2020, and the sending unit 2030 may interact with or be coupled to the storage unit, for example, read or call the data and / or signaling in the storage unit, so that the methods in the above embodiments are executed.

[0902] Each of the above units may exist independently, or may be integrated in whole or in part.

[0903] See Figure 21 , Figure 21 is a schematic structural diagram of the EAS 2100 applicable to the embodiments of the present application, which may be used to implement the functions of the above EAS.

[0904] The EAS 2100 includes a processor 2101, a memory 2102, and a transceiver 2103. Among them, instructions or programs are stored in the memory 2102. The processor 2102 and the transceiver 2103 are used to execute or call the instructions or programs stored in the memory 2102, so that the EAS 2100 implements the functions of the EAS in the above method for migrating context. When the instructions or programs stored in the memory 2102 are executed, the transceiver 2103 is used to execute Figure 20 the operations performed by the sending unit 2030 and the obtaining unit 2020 in the embodiments shown in Figure 20 the operations performed by the processing unit 2010 in the embodiments shown in

[0905] Those skilled in the art can understand that for the sake of convenience of description, Figure 21 only one memory and one processor are shown. In an actual user device, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, etc., and the embodiments of the present application do not limit this.

[0906] See Figure 22 , Figure 22 is a schematic diagram of the apparatus 2200 for migrating context provided by the present application. As Figure 22 shown, the apparatus 2200 includes a processing unit 2210 and a sending unit 2220.

[0907] The processing unit 2210 is used to formulate application context migration ACR mode information, and the ACR mode information includes condition information for triggering the ACR process of at least one application;

[0908] The sending unit 2220 is used to send the ACR mode information to the EEC and the EES respectively.

[0909] The ECS in the apparatus 2200 corresponds to that in the method embodiments. The apparatus 2200 may be the ECS in the method embodiments, or a chip or functional module inside the ECS in the method embodiments. The corresponding units of the apparatus 2200 are used to execute Figures 10 to 13 the corresponding steps executed by the ECS in the method embodiments shown.

[0910] Among them, the processing unit 2210 in the apparatus 2200 is used to execute the steps related to processing corresponding to the ECS in the method embodiments. The sending unit 2220 in the apparatus 2200 is used to execute the steps of sending by the ECS.

[0911] Optionally, the apparatus 2200 may further include a storage unit, which is used to store data and / or signaling. The processing unit 2210 and the sending unit 2220 may interact with or be coupled to the storage unit, for example, read or call the data and / or signaling in the storage unit, so that the methods in the above embodiments are executed.

[0912] Each of the above units may exist independently, or may be integrated in whole or in part.

[0913] See Figure 23 , Figure 23 which is a schematic structural diagram of the ECS 2300 applicable to the embodiments of the present application and can be used to implement the functions of the above ECS.

[0914] The ECS 2300 includes a processor 2301, a memory 2302 and a transceiver 2303. Among them, instructions or programs are stored in the memory 2302. The processor 2302 and the transceiver 2303 are used to execute or call the instructions or programs stored in the memory 2302, so that the ECS 2300 realizes the functions of the ECS in the method for migrating context above. When the instructions or programs stored in the memory 2302 are executed, the transceiver 2303 is used to execute Figure 22 the operations executed by the sending unit 2220 in the embodiments shown, and the processor 2302 is used to execute Figure 22 the operations executed by the processing unit 2210 in the embodiments shown.

[0915] Those skilled in the art can understand that, for the sake of convenience of description, Figure 23 only one memory and one processor are shown. In an actual user device, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, etc., and the embodiments of the present application do not limit this.

[0916] The embodiments of the present application further provide a communication system, which includes the foregoing EEC, EES, AC, EAS and ECS.

[0917] The embodiment of the present application further provides a user equipment, which includes the aforementioned EEC and AC.

[0918] The present application also provides a computer-readable storage medium, in which instructions are stored. When the instructions run on a computer, the computer is caused to execute each step performed by EEC, EES, AC, EAS or ECS in the method as Figures 10 to 13 shown.

[0919] The present application also provides a computer program product containing instructions. When the computer program product runs on a computer, the computer is caused to execute each step performed by EEC, EES, AC, EAS or ECS in the method as Figures 10 to 13 shown.

[0920] The present application also provides a chip, including a processor. The processor is configured to read and run a computer program stored in a memory to execute the corresponding operations and / or processes performed by EEC, EES, AC, EAS or ECS in the method for migrating context provided by the present application as Figures 10 to 13 shown. In a possible implementation, the chip further includes a memory, and the memory is connected to the processor through a circuit or wire. The processor is configured to read and execute the computer program in the memory. Further in a possible implementation, the chip further includes a communication interface, and the processor is connected to the communication interface. The communication interface is configured to receive the processed data and / or information. The processor obtains the data and / or information from the communication interface and processes the data and / or information. The communication interface may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip, etc. The processor may also be embodied as a processing circuit or a logic circuit.

[0921] The aforementioned chip may also be replaced with a chip system, which will not be elaborated here.

[0922] The terms "include" and "have" and any variations thereof in the present application are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units does not necessarily have to be limited to those clearly listed steps or units, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0923] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in connection with the embodiments disclosed herein can be implemented in electronic hardware, or in a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled professionals may use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0924] Those skilled in the art can clearly understand that for the sake of convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments, and will not be elaborated herein.

[0925] In 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 merely illustrative. For example, the division of the units is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces, and the indirect couplings or communication connections of the devices or units can be in electrical, mechanical, or other forms.

[0926] The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0927] In addition, the functional units in each embodiment of this application can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.

[0928] When the above-mentioned functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs.

[0929] In addition, the term "and / or" in this application is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship; the term "at least one" in this application may represent "one" and "two or more". For example, at least one of A, B, and C may represent: A exists alone, B exists alone, C exists alone, A and B exist simultaneously, A and C exist simultaneously, C and B exist simultaneously, and A, B, and C exist simultaneously, these seven situations.

[0930] As described above, this is only the specific implementation manner of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art in the technical field disclosed in this application can easily think of changes or substitutions, which should all be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

1. A method for migrating context, characterized in that, Including: Obtaining at least one of the ACR capability information supported by the Edge Application Service (EAS), the ACR capability information supported by the Edge Enablement Client (EEC), the ACR capability information supported by the Application Client (AC), or the ACR capability information supported by the Edge Enablement Server (EES); Obtaining Application Context Migration (ACR) mode information according to the at least one piece of information obtained, wherein the ACR mode information specifies different ACR methods for different applications.

2. The method according to claim 1, wherein The method is executed by the EES.

3. The method according to claim 2, wherein The method further includes: The EES sends the ACR mode information to the EEC and / or the EAS.

4. The method according to claim 2 or 3, characterized in that, The obtaining of the ACR capability information supported by the EAS includes: The EES receives the ACR capability information supported by the EAS from the EAS.

5. The method according to claim 2 or 3, wherein The obtaining of the ACR capability information supported by the EEC and the ACR capability information supported by the AC includes: The EES receives the ACR capability information supported by the EEC and the ACR capability information supported by the AC from the EEC.

6. The method according to claim 2 or 3, characterized in that, The method further includes: The EES receives ACR method request information from the EEC, wherein the ACR method request information is used to request allocation of an ACR method.

7. The method according to claim 1, wherein The method is executed by the EEC.

8. The method according to claim 7, characterized in that, The method further includes: The EEC sends the ACR mode information to the AC and / or the EES.

9. The method according to claim 7 or 8, characterized in that, The obtaining of the ACR capability information supported by the AC includes: The EEC receives the ACR capability information supported by the AC from the AC.

10. The method according to claim 7 or 8, characterized in that, The obtaining of the ACR capability information supported by the EES includes: The EEC receives the ACR capability information supported by the EES and the ACR capability information supported by the EAS from the EES.

11. The method according to claim 7 or 8, characterized in that, The obtaining of the ACR capability information supported by the EAS includes: The EEC receives the ACR capability information supported by the EAS from the EAS.

12. An apparatus for migrating context, characterized in that, Including: An obtaining unit for obtaining at least one of the ACR capability information supported by the Edge Application Service (EAS), the ACR capability information supported by the Edge Enablement Client (EEC), the ACR capability information supported by the Application Client (AC), or the ACR capability information supported by the Edge Enablement Server (EES); A processing unit for obtaining Application Context Migration (ACR) mode information according to the at least one piece of information obtained, wherein the ACR mode information specifies different ACR methods for different applications.

13. The device according to claim 12, wherein The device is the EES.

14. The device according to claim 13, characterized in that, The EES includes a sending unit, The sending unit for sending the ACR mode information to the EEC and / or the EAS.

15. The device according to claim 12 or 13, characterized in that, The obtaining of the ACR capability information supported by the EAS by the obtaining unit includes: The EES receives the ACR capability information supported by the EAS from the EAS.

16. The device according to claim 12 or 13, characterized in that The obtaining of the ACR capability information supported by the EEC and the ACR capability information supported by the AC by the obtaining unit includes: The EES receives the ACR capability information supported by the EEC and the ACR capability information supported by the AC from the EEC.

17. The device according to claim 12 or 13, characterized in that, The EES includes a receiving unit. The receiving unit is configured to receive ACR method request information from the EEC, where the ACR method request information is used to request allocation of an ACR method.

18. The device according to claim 12, characterized in that, The device is executed for the EEC.

19. The device according to claim 18, characterized in that, The EEC includes a sending unit. The sending unit is configured to send the ACR mode information to the AC and / or the EES.

20. The device according to claim 18 or 19, characterized in that, The obtaining unit obtaining the ACR capability information supported by the AC includes: The EEC receives the ACR capability information supported by the AC from the AC.

21. The device according to claim 18 or 19, characterized in that, The obtaining unit obtaining the ACR capability information supported by the EES includes: The EEC receives the ACR capability information supported by the EES and the ACR capability information supported by the EAS from the EES.

22. The device according to claim 18 or 19, characterized in that, The obtaining unit obtaining the ACR capability information supported by the EAS includes: The EEC receives the ACR capability information supported by the EAS from the EAS.

23. A computer-readable storage medium, characterized in that, A computer program is stored on the computer-readable storage medium. When the computer program runs, it causes the device to execute the method according to any one of claims 1 to 11.

24. A chip system, characterized in that, Including: A processor, configured to call and run the computer program from the memory, so that the communication device installed with the chip system executes the method according to any one of claims 1 to 11.

25. A communication device, characterized in that, Including: A memory, configured to store the computer program; A processor, configured to execute the computer program stored in the memory, so that the communication device executes the method according to any one of claims 1 to 11.

26. A communication system, characterized in that, The communication system includes at least one device for migrating context according to any one of claims 12 to 22.

Images