CN115529641A

CN115529641A - Method and apparatus for migrating contexts

Info

Publication number: CN115529641A
Application number: CN202110999308.1A
Authority: CN
Inventors: 葛翠丽; 胡雅婕; 杨艳梅
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-06-25
Filing date: 2021-08-28
Publication date: 2022-12-27

Abstract

The application provides a method and a device for migrating a context, wherein the method for migrating the context comprises the following steps: acquiring application context migration ACR mode information, wherein the ACR mode information is used for determining an ACR method selected by at least one application, and performing an ACR process aiming at a first application in the at least one application according to the ACR mode information. The method for migrating the context executes the ACR flow according to the ACR mode information, and can avoid repeatedly triggering the ACR flow on the premise of saving signaling overhead.

Description

Method and apparatus for migrating contexts

The present application claims priority from the chinese patent application filed on 25/06/25/2021 with the chinese patent office having application number 202110714098.7 entitled "method and apparatus for migrating contexts", the entire contents of which are incorporated herein by reference.

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for migrating a context.

Background

In order to avoid that a plurality of functional entities initiate an ACR process, which results in multiple ACR processes being performed on the same application, an Edge Enable Server (EES) provides an in-progress indication (in-progress indication) for indicating that an ACR is currently in progress to other detection entities, thereby avoiding multiple application context migrations being performed.

However, the scheme needs to notify each functional entity that the application context is being migrated one by one, and the signaling overhead is large. Therefore, how to avoid repeatedly triggering the ACR flow becomes an urgent problem to be solved on the premise of saving signaling for county opening.

Disclosure of Invention

The application provides a method and a device for migrating contexts, so that a certain functional entity executes an ACR flow, and the ACR flow can be prevented from being repeatedly triggered on the premise of saving signaling overhead.

In a first aspect, a method for migrating a context is provided, where the method for migrating a context may be performed by a terminal device, or may also be performed by a chip or a circuit disposed in the terminal device, and this is not limited in this application.

Exemplarily, the terminal device in the first aspect may be an Edge Enabled Client (EEC), that is, the terminal device in the first aspect may be replaced with the EEC.

The method for migrating the context comprises the following steps:

acquiring application context migration ACR mode information; determining at least one ACR method selected by the application according to the ACR mode information.

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

With reference to the first aspect, in certain implementations of the first aspect, the ACR mode information includes ACR rule information including condition information that triggers at least one applied ACR procedure; when a first condition indicated by the condition information is satisfied, executing an ACR flow for a first application of the at least one application; the condition information further indicates at least one of the following conditions: a second condition, a third condition and a fourth condition, wherein when the second condition is satisfied, the application client AC is instructed to execute an ACR flow for a second application of the at least one application; instructing the edge application server EAS to perform an ACR procedure for a third application of the at least one application when the third condition is satisfied; when this fourth condition is satisfied, the edge-enabled server EES is instructed to execute the ACR flow for a fourth application of the at least one application.

According to the method for migrating the context, the ACR process is executed according to the ACR rule information, whether the ACR process of the first application is currently executed is not required to be indicated through the indication information, and the ACR process of the first application can be prevented from being repeatedly triggered on the premise of saving signaling overhead.

With reference to the first aspect, in certain implementations of the first aspect, the acquiring the ACR mode information includes: receiving the ACR mode information from an application client AC; or, receiving the ACR mode information from the edge-enabling server EES and/or the edge-configuration server ECS; or, formulating ACR mode information according to the second information, the third information and the fourth information.

The method for migrating the context provided by the embodiment of the application can acquire the ACR mode information in different modes, and the flexibility of the scheme is improved.

In combination with the first aspect, in certain implementations of the first aspect,

receiving the ACR mode information from the AC, the method further comprising: sending the ACR mode information to an edge enabling server EES;

receiving the ACR mode information from the EES and/or the ECS, the method further comprising: transmitting the ACR mode information to the AC;

formulating ACR mode information according to the second information, the third information and the fourth information, wherein the method further comprises the following steps:

receiving second information from the EAS, the second information including EAS-supported ACR capability information and/or second ACR method request information, wherein the EAS-supported ACR capability information indicates capabilities of the EAS, the second ACR method request information being for requesting allocation of an ACR method for the EAS;

receiving third information from the AC, the third information including ACR capability information supported by the AC, and/or third ACR method request information, wherein the ACR capability information supported by the AC indicates the capability of the AC, and the third ACR method request information is used for requesting allocation of an ACR method for the AC;

receiving fourth information from the EES, the fourth information including ACR capability information supported by the EES, and/or fourth ACR method request information, wherein the ACR capability information supported by the EES indicates a capability of the EES, and the fourth ACR method request information is used for requesting allocation of an ACR method for the EES;

sending the ACR mode information to the AC, the EES or the ECS.

The method for migrating the context provided by the embodiment of the application can send the ACR mode information to other functional entities needing the ACR mode information, so that the other functional entities can execute the ACR process based on the ACR mode information, whether the ACR process of a certain application is currently executed is not required to be indicated through the indication information, and the ACR process can be prevented from being repeatedly triggered on the premise of saving signaling overhead.

With reference to the first aspect, in certain implementations of the first aspect, the ACR rule information includes: a correspondence between an application type and a device that performs an ACR flow of the application belonging to the application type, and/or a correspondence between event information that triggers the flow of the ACR and a device that performs the flow of the preset ACR.

The ACR rule information may specifically be an event or an application type that allocates to each functional entity (e.g., AC, EAS, EES, or EEC) an ACR event (e.g., UE mobility, EAS overload) or an application type, where the ACR event or the application type needs to be detected and executed.

With reference to the first aspect, in certain implementations of the first aspect, the ACR mode information indicates an identity of the application client and an 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 ACR mode information may specifically be an identifier of the application client and an ACR method selected by the server, and different ACR methods may be specified for different applications.

With reference to the first aspect, in certain implementations of the first aspect, before acquiring the ACR pattern information, the method further includes: sending first information to the edge-enabled server EES or the edge-configuration server ECS, the first information indicating at least one of: the method comprises the steps of applying ACR capacity information supported by an AC (application client), enabling the ACR capacity information supported by an EEC (edge-enabled client), requesting to distribute an ACR method for the AC, and requesting to distribute the ACR method for the EEC. With reference to the first aspect, in certain implementations of the first aspect, the method further includes: receiving AC-supported ACR capability information from the AC, and/or third ACR method request information, the first information further including the AC-supported ACR capability information, and/or third ACR method request information, wherein the AC-supported ACR capability information indicates a capability of the AC, and the third ACR method request information is used for requesting allocation of an ACR method for the AC.

In a second aspect, a method for migrating a context is provided, where the method for migrating a context may be performed by an EES, or may also be performed by a chip or a circuit disposed in the EES, and this application is not limited thereto.

The method for migrating the context comprises the following steps:

an edge enabling server EES acquires application context migration ACR mode information, wherein the ACR mode information is used for determining at least one ACR method selected by an application; the EES sends the ACR pattern information to the edge application service EAS.

According to the method for migrating the context, the EES executes the ACR process according to the ACR mode information, whether the ACR process of a certain application of the EES is executed currently is not required to be indicated through the indication information, and the ACR process of the certain application can be prevented from being triggered repeatedly on the premise of saving signaling overhead.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the EES sends the ACR pattern information to the edge-enabled client EEC.

With reference to the second aspect, in certain implementations of the second aspect, the ACR mode information includes ACR rule information including condition information that triggers an ACR procedure of at least one application; when a fourth condition indicated by the condition information is satisfied, the EES executes an ACR procedure for a fourth application of the at least one application.

According to the method for migrating the context, the EES executes the ACR process according to the ACR rule information, and whether the ACR process of the EES fourth application is currently executed is not required to be indicated through the indication information, so that the repeated triggering of the ACR process of the fourth application can be avoided on the premise of saving signaling overhead.

With reference to the second aspect, in certain implementations of the second aspect, the acquiring, by the EES, the ACR mode information includes: the EES acquires the ACR pattern information according to at least one of the following information: ACR capability information supported by an Edge Application Server (EAS), ACR capability information supported by an EEC, ACR capability information supported by an Application Client (AC) and ACR capability information supported by the EES; or, the EES acquires the ACR mode information from a configuration file of the EES, where the configuration file of the EES includes the ACR mode information; alternatively, the EES receives the ACR mode information from the ECS; wherein, the EAS-supported ACR capability information is used to indicate a third condition corresponding to the EAS-supported ACR flow, the edge-enabled client EEC-supported ACR capability information is used to indicate a first condition corresponding to the edge-enabled client EEC-supported ACR flow, the AC-supported ACR capability information is used to indicate a second condition corresponding to the AC-supported ACR flow, the EES-supported ACR capability information is used to indicate the fourth condition corresponding to the EES-supported ACR flow, 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 satisfied, instructing the AC to perform an ACR flow for a second application of the at least one application; when the third condition is satisfied, instructing the EAS to perform an ACR flow for a third application of the at least one application; when the first condition is satisfied, instructing the EEC to execute an ACR flow for a first application of the at least one application.

With reference to the second aspect, in certain implementations of the second aspect, the ACR pattern information indicates an identity of the application client and an ACR method determined by the server for the application client, wherein 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. With reference to the second aspect, in certain implementations of the second aspect, the acquiring, by the EES, the ACR pattern information includes: the EES formulates ACR mode information according to second information and the first information, wherein the second information comprises ACR capability information supported by EAS and/or second ACR method request information; the first information includes at least one of AC-supported ACR capability information, EEC-supported ACR capability information, first ACR method request information, or third ACR method request information, the EAS-supported ACR capability information indicating an EAS capability, the second ACR method request information requesting allocation of an ACR method for EAS, the AC-supported ACR capability information indicating a capability of an AC, the third ACR method request information requesting allocation of an ACR method for the AC, the EEC-supported ACR capability information indicating a capability of an EEC, the first ACR method request information requesting allocation of an ACR method for the EEC.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the EES receives the second message from the EAS; the EES receives first information from the EEC.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the EES transmits the ACR mode information to the EAS or the EEC.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the EES sends fifth information to the ECS, where the fifth information includes: at least one of 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, wherein the ACR capability information supported by the EES indicates a capability of the EES, the fourth ACR method request information is for requesting allocation of an ACR method to the EES, the ACR capability information supported by the EAS indicates a capability of the EAS, and the second ACR method request information is for requesting allocation of an ACR method to the EAS.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the EES transmits fourth information to the EEC, the fourth information including ACR capability information supported by the EES, and/or fourth ACR method request information, wherein the ACR capability information supported by the EES indicates the capability of the EES, and the fourth ACR method request information is used for requesting allocation of ACR method for the EES

With reference to the second aspect, in certain implementations of the second aspect, the acquiring, by the EES, the ACR mode information includes: the EES receives the ACR pattern information from the edge application servers EAS and/or EEC.

According to the method for migrating the context, the EES can acquire the ACR mode information in different modes, and the flexibility of the scheme is improved.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the EES transmits the ACR mode information to the EAS and/or the EEC.

According to the method for migrating the context, the EEC can send the ACR mode information to other functional entities needing the ACR mode information, so that the other functional entities can execute the ACR process based on the ACR mode information, whether the ACR process of a certain application is executed currently is not required to be indicated through the indication information, and the ACR process can be prevented from being triggered repeatedly on the premise of saving signaling overhead.

With reference to the second aspect, in some implementations of the second aspect, the ACR rule information includes: a correspondence between an application type and a device that executes an ACR flow of an application belonging to the application type, and/or a correspondence between event information that triggers the flow of an ACR and a device that executes the flow of the preset ACR.

The ACR rule information may specifically be an event or application type that allocates an ACR to each functional entity (e.g., AC, EAS, EES, or EEC) for an ACR event (e.g., UE mobility, EAS overload) or for an application type, or specify different ACR methods for different applications, that is, the ACR rule information may specify different ACR trigger rules, thereby improving flexibility of the scheme.

With reference to the second aspect, in certain implementations of the second aspect, the ACR mode information includes identification information of at least one application and an ACR method selected by a server, wherein the server is one of an edge configuration server ECS, an edge enable server EES, or an edge application server EAS.

The ACR mode information may specifically be identification information of the application and an ACR method selected by the server, and different ACR methods may be specified for different applications.

In a third aspect, a method for migrating a context is provided, where the method for migrating a context may be performed by an Application Client (AC), or may be performed by a chip or a circuit disposed in the AC, and this application is not limited thereto.

The method for migrating the context comprises the following steps:

an application client AC acquires application context migration ACR mode information; the application client AC determines at least one ACR method selected by the application according to the ACR pattern information.

According to the method for migrating the context, the AC executes the ACR process according to the ACR mode information, whether the ACR process of a certain application of the AC is executed currently is not required to be indicated through the indication information, and the ACR process of a certain application can be prevented from being triggered repeatedly on the premise of saving signaling overhead.

With reference to the third aspect, in certain implementations of the third aspect, the ACR mode information includes ACR rule information including condition information that triggers an ACR procedure of at least one application; when a second condition indicated by the condition information is satisfied, the AC performs an ACR flow for a second application of the at least one application.

According to the method for migrating the context, the AC executes the ACR flow according to the ACR rule information without indicating whether the ACR flow of the second application of the AC is executed currently or not through the indication information, and the ACR flow of the second application can be prevented from being repeatedly triggered on the premise of saving signaling overhead.

With reference to the third aspect, in some implementations of the third aspect, the obtaining, by the AC, the ACR mode information includes: the AC acquires the ACR mode information from the configuration file of the AC, wherein the configuration file of the AC comprises the ACR mode information; alternatively, the AC receives the ACR mode information from the edge-enabled client EEC; the condition information further indicates at least one of the following conditions: a first condition, a third condition, and a fourth condition, wherein when the first condition is satisfied, the first condition instructs the EEC to execute an ACR flow for a first application of the at least one application; instructing the edge application server EAS to perform an ACR procedure for a third application of the at least one application when the third condition is satisfied; when this fourth condition is satisfied, the edge-enabled server EES is instructed to execute the ACR flow for a fourth application of the at least one application.

According to the method for migrating the context, the AC can acquire the ACR mode information in different modes, and the flexibility of the scheme is improved.

With reference to the third aspect, in some implementations of the third aspect, when the AC acquires the ACR mode information from the configuration file of the AC, the method further includes: the AC sends the ACR pattern information to the EEC.

According to the method for migrating the context, the AC can send the ACR mode information to other functional entities needing the ACR mode information, so that the other functional entities can execute the ACR process based on the ACR mode information, whether the ACR process of a certain application is executed currently is not required to be indicated through the indication information, and the ACR process can be prevented from being triggered repeatedly on the premise of saving signaling overhead.

With reference to the third aspect, in some implementations of the third aspect, the ACR rule information includes: a correspondence between an application type and a device that performs an ACR flow of the application belonging to the application type, and/or a correspondence between event information that triggers the flow of the ACR and a device that performs the flow of the preset ACR.

With reference to the third aspect, in certain implementations of the third aspect, the ACR mode information indicates an identity of the application client and an 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 ACR mode information may be identification information of an application and an ACR method selected by a server, and different ACR methods may be specified for different applications.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the AC transmits third information to the EEC, the third information including ACR capability information supported by the AC, and/or third ACR method request information, wherein the ACR capability information supported by the AC indicates a capability of the AC, and the third ACR method request information is used for requesting allocation of an ACR method for the AC.

In a fourth aspect, a method for migrating a context is provided, where the method for migrating a context may be performed by an Edge Application Server (EAS) or may be performed by a chip or a circuit disposed in the EAS, and the method is not limited in this application.

The method for migrating the context comprises the following steps:

an Edge Application Server (EAS) acquires information of an application context migration ACR mode; the edge application server EAS determines at least one ACR method and selected by the application according to the ACR pattern information.

According to the method for migrating the context, the EAS executes the ACR process according to the ACR mode information without indicating whether the ACR process of a certain application of the EAS is executed currently or not through the indication information, and the ACR process of a certain application can be prevented from being triggered repeatedly on the premise of saving signaling overhead.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the ACR mode information includes ACR rule information, the ACR rule information includes condition information that triggers an ACR procedure of at least one application; when a third condition indicated by the condition information is satisfied, the EAS executes an ACR procedure for a third application of the at least one application.

According to the method for migrating the context, the EAS executes the ACR flow according to the ACR rule information, whether the ACR flow of the EAS third application is executed currently is not required to be indicated through the indication information, and the ACR flow of the third application can be prevented from being triggered repeatedly on the premise of saving signaling overhead.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the EAS acquiring the ACR mode information includes: the EAS acquires the ACR mode information from a configuration file of the EAS, wherein the configuration file of the EAS comprises the ACR mode information; alternatively, the EAS receives the ACR mode information from an edge-enabled server EES; the condition information further indicates at least one of the following conditions: a second condition, a first condition and a fourth condition, wherein when the second condition is satisfied, the application client AC is instructed to execute an ACR flow for a second application of the at least one application; when the first condition is met, instructing the EEC to execute an ACR flow for a first application of the at least one application; when the fourth condition is satisfied, instructing the EES to execute an ACR procedure for a fourth application of the at least one application.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the EAS acquiring the ACR mode information includes: the EAS formulates ACR mode information according to the first information, the third information and the fifth information.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the method further includes:

receiving first information from the EEC, the first information including at least one of AC-supported ACR capability information, EEC-supported ACR capability information, first ACR method request information, or third ACR method request information, the AC-supported ACR capability information indicating a capability of the AC, the third ACR method request information requesting allocation of an ACR method to the AC, the EEC-supported ACR capability information indicating the capability of the EEC, the first ACR method request information requesting allocation of an ACR method to the EEC;

receiving third information from the AC, the third information including ACR capability information supported by the AC, and/or third ACR method request information, wherein the ACR capability information supported by the AC indicates a capability of the AC, and the third ACR method request information is used for requesting allocation of an ACR method for the AC;

receiving fifth information from the EES, the fifth information comprising: at least one of 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, wherein the ACR capability information supported by the EES indicates a capability of the EES, the fourth ACR method request information is for requesting allocation of an ACR method to the EES, the ACR capability information supported by the EAS indicates a capability of the EAS, and the second ACR method request information is for requesting allocation of an ACR method to the EAS;

sending the ACR mode information to the AC, the EES or the EEC.

According to the method for migrating the context, the EAS can acquire the ACR mode information in different modes, and the flexibility of a scheme is improved.

With reference to the fourth aspect, in certain implementations of the fourth aspect, when the EAS acquires the ACR mode information from a configuration file of the EAS, the method further comprises: the EAS transmits the ACR mode information to the EES.

According to the method for migrating the context, the EAS can send the ACR mode information to other functional entities needing the ACR mode information, so that the other functional entities can execute the ACR process based on the ACR mode information, whether the ACR process of an application is currently executed is not required to be indicated through the indication information, and the ACR process can be prevented from being triggered repeatedly on the premise of saving signaling overhead.

With reference to the fourth aspect, in some implementations of the fourth aspect, the ACR rule information includes: a correspondence between an application type and a device that performs an ACR flow of the application belonging to the application type, and/or a correspondence between event information that triggers the flow of the ACR and a device that performs the flow of the preset ACR.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the ACR mode information indicates an identity of the application client and an ACR method determined by the server for the application client, wherein 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 ACR mode information may be identification information of an application and an ACR method selected by a server, and different ACR methods may be specified for different applications.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the method further includes: the EAS transmits second information including EAS-supported ACR capability information indicating capabilities of the EAS and/or second ACR method request information for requesting allocation of an ACR method for the EAS to the EEC.

In a fifth aspect, a method for migrating a context is provided, where the method for migrating a context may be performed by an ECS, or may be performed by a chip or a circuit disposed in the ECS, and this is not limited in this application.

The method for migrating the context comprises the following steps:

acquiring application context migration ACR mode information from an edge configuration server ECS; the self-edge configuration server ECS determines at least one ACR method selected by the application according to the ACR mode information.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the ACR mode information includes ACR rule information including condition information that triggers an ACR procedure of at least one application, the method further includes: the application context migration ACR pattern information is formulated from the edge configuration server ECS, the condition information indicating at least one of the following conditions: a first condition, a second condition, a third condition, and a fourth condition, wherein when the first condition is satisfied, the first condition instructs the EEC to execute an ACR flow for a first application of the at least one application; when the second condition is met, instructing the application client AC to execute an ACR flow for a second application of the at least one application; when the third condition is satisfied, instructing an edge application server EAS to execute an ACR flow for a third application of the at least one application; when the fourth condition is satisfied, instructing the edge-enabled server EES to execute an ACR flow for a fourth application of the at least one application; the ECS sends the ACR mode information to the EEC and the EES, respectively.

According to the method for migrating the context, 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 executed currently or not through the indication information, and the ACR process of the application can be prevented from being triggered repeatedly on the premise of saving signaling overhead.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the acquiring, by the ECS, the ACR mode information includes: and the ECS formulates ACR mode information according to the first information, the second information and the fifth information.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the method further comprises:

the ECS receiving first information from the EEC, the first information including at least one of AC-supported ACR capability information, EEC-supported ACR capability information, first ACR method request information, or third ACR method request information, the AC-supported ACR capability information indicating a capability of the AC, the third ACR method request information requesting allocation of an ACR method to the AC, the EEC-supported ACR capability information indicating the capability of the EEC, the first ACR method request information requesting allocation of an ACR method to the EEC;

the ECS receiving second information from the EAS, the second information including EAS-supported ACR capability information, and/or second ACR method request information, wherein the EAS-supported ACR capability information indicates capabilities of the EAS, the second ACR method request information being for requesting allocation of an ACR method for the EAS;

the ECS receives the fifth information from the EES, wherein the fifth information comprises: at least one of 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, wherein the ACR capability information supported by the EES indicates a capability of the EES, the fourth ACR method request information is for requesting allocation of an ACR method to the EES, the ACR capability information supported by the EAS indicates a capability of the EAS, and the second ACR method request information is for requesting allocation of an ACR method to the EAS;

transmitting the ACR mode information to the EAS, the EES or the EEC.

In a sixth aspect, an apparatus for migrating a context is provided, where the apparatus for migrating a context includes a processor, and is configured to implement the function of the terminal apparatus (or the EEC) in the method described in the first aspect.

In a possible implementation manner, the apparatus for migrating a context may further include a memory, which is coupled to the processor, and the processor is configured to implement the function of the terminal apparatus in the method described in the first aspect.

In one 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, so as to implement the functions of the terminal device in the method described in the first aspect.

In one possible implementation, the apparatus for migrating a context may further include a communication interface for the apparatus for migrating a context to communicate with other devices. The communication interface may be a transceiver, an input/output interface, or a circuit, etc.

In one possible design, the means for migrating contexts includes: a processor and a communication interface, wherein the processor is connected with the communication interface,

the processor communicates with the outside by using the communication interface;

the processor is configured to run a computer program to cause the apparatus for migrating contexts to implement any of the methods described in the first aspect above.

It will be appreciated that the external may be an object other than a processor, or an object other than the apparatus.

In another possible design, the means for migrating contexts is a chip or a system-on-chip. The communication interface may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit, etc. on the chip or system of chips. The processor may also be embodied as a processing circuit or a logic circuit.

In a seventh aspect, an apparatus for migrating a context is provided, where the apparatus for migrating a context includes a processor configured to implement a function of an AC in the method described in the third aspect.

In a possible implementation manner, the apparatus for migrating a context may further include a memory, which is coupled to the processor, and the processor is configured to implement the function of the AC in the method described in the third aspect.

In one 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 for implementing the functions of the AC in the method described in the third aspect.

In one possible implementation, the means for migrating a context may further include a communication interface for the means for migrating a context to communicate with other devices. The communication interface may be a transceiver, an input/output interface, or a circuit, etc.

the processor is configured to run the computer program to cause the apparatus for migrating contexts to implement any of the methods described in the third aspect above.

In an eighth aspect, an apparatus for migrating a context is provided, where the apparatus for migrating a context includes a processor configured to implement the function of EAS in the method described in the fourth aspect.

In a possible implementation manner, the apparatus for migrating a context may further include a memory, the memory being coupled with the processor, and the processor being configured to implement the function of EAS in the method described in the fourth aspect.

In one possible implementation, the memory is used to store program instructions and data. The memory is coupled to the processor, and the processor may invoke and execute program instructions stored in the memory for implementing EAS functionality in the method described in the fourth aspect.

the processor is configured to run the computer program, so that the apparatus for migrating contexts implements any one of the methods described in the fourth aspect above.

It will be appreciated that the external portion may be an object other than a processor, or an object other than the apparatus.

In a ninth aspect, there is provided an apparatus for migrating a context, the apparatus for migrating a context comprising a processor for implementing the functions of the ECS in the method described in the fifth aspect.

In a possible implementation manner, the apparatus for migrating a context may further include a memory, which is coupled with the processor, and the processor is configured to implement the function of the ECS in the method described in the fifth aspect.

In one 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 for implementing the functions of the ECS in the method described in the fifth aspect.

the processor is configured to run a computer program to cause the apparatus for migrating contexts to implement any of the methods described in the fifth aspect above.

In a tenth aspect, the present application provides a computer-readable storage medium having stored therein instructions, which when run on a computer, cause the computer to perform the method of the above aspects.

In an eleventh aspect, the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the above aspects.

In a twelfth aspect, there is provided a communication system comprising the apparatus for migrating a context of the sixth aspect to the apparatus for migrating a context of the tenth aspect.

In a thirteenth aspect, a user equipment is provided, which includes the apparatus for migrating a context shown in the sixth aspect and the apparatus for migrating a context shown in the eighth aspect.

In a fourteenth aspect, a chip or a chip system is provided, where 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, and the at least one processor is configured to execute a computer program or instructions to perform the method in any one of the possible implementation manners of the first aspect to the fifth aspect. The communication interface in the chip may be an input/output interface, a pin, a circuit, or the like.

In one possible implementation, the chip or chip system described above in this application further comprises at least one memory having instructions stored therein. 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 (e.g., a read-only memory, a random access memory, etc.).

Drawings

Fig. 1 is a schematic diagram of a system architecture to which an embodiment of the present application is applicable.

FIG. 2 is an implementation of application context migration.

Fig. 3 (a) is a schematic diagram of a service provisioning procedure; fig. 3 (b) is a schematic diagram of the EEC registration flow;

fig. 3 (c) is a schematic diagram of an EAS registration procedure.

FIG. 4 (a) is a schematic diagram of a conventional EAS discovery procedure; fig. 4 (b) is a schematic diagram illustrating an AC information subscription flow; fig. 4 (c) is a schematic diagram of an AC information notification flow.

FIG. 5 is another implementation of application context migration.

FIG. 6 is another implementation of application context migration.

FIG. 7 is another implementation of application context migration.

FIG. 8 is another implementation of application context migration.

FIG. 9 is another implementation of application context migration.

FIG. 10 is a schematic flow chart diagram illustrating a method for migrating contexts provided herein.

FIG. 11 (a) is a schematic flow chart diagram of another method for migrating contexts provided by the present application; FIG. 11 (b) is a schematic flow chart diagram illustrating yet another method for migrating contexts provided herein.

FIG. 12 is a schematic flow chart diagram illustrating yet another method for migrating contexts provided herein.

FIG. 13 is a schematic flow chart diagram illustrating another method for migrating contexts provided herein.

Fig. 14 is a schematic diagram of an apparatus 1400 for migrating a context provided herein.

Fig. 15 is a schematic structural diagram of an EEC 1500 suitable for use in embodiments of the present application.

Fig. 16 is a schematic diagram of an apparatus 1600 for migrating contexts provided herein.

Fig. 17 is a schematic structural diagram of an EES 1700 suitable for use in embodiments of the present application.

Fig. 18 is a schematic diagram of an apparatus 1800 for migrating contexts provided herein.

Fig. 19 is a schematic structural diagram of AC 1900 suitable for use in embodiments of the present application.

Fig. 20 is a schematic diagram of an apparatus 2000 for migrating contexts provided herein.

Fig. 21 is a schematic diagram of an EAS 2100 suitable for use in embodiments of the application.

FIG. 22 is a diagram illustrating an apparatus 2200 for migrating contexts provided herein.

Fig. 23 is a schematic diagram of an ECS 2300 configuration suitable for use in embodiments of the present application.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

Fig. 1 is a schematic diagram of a system architecture to which an embodiment of the present application is applicable. The following describes each part involved in the network architecture shown in fig. 1.

1. Edge Data Network (EDN).

In a general understanding, the EDN corresponds to only one data network, is a special local data network (local DN), includes an edge-enabled function, can use a data network Access Identifier (DN Access Identifier, DNAI) and a DNN Identifier, and is a network logical concept.

Another understanding of EDN: the EDN is a peer-to-peer concept of a central cloud, which may be understood as a local data center (concept of geographical location), may be identified using DNAI, and may contain a plurality of local data networks (local DNs).

The EDN includes an Edge Enable Server (EES) and a plurality of Edge Application Servers (EAS).

The EES may be a control network element or a management network element in a Mobile Edge Computing (MEC) node (the MEC may also be referred to as a multi-access edge computing (multi-access edge computing)), and is responsible for managing each EAS deployed in the EDN (or understood to provide services for each EAS deployed in the EDN), such as basic functions of registration, domain Name System (DNS) resolution content routing, upper-layer application registration management, wireless information interaction, and the like. In addition, the EES may invoke a capability openness function network element in the 3GPP network. It should be understood that the EES network element may be co-located with other network elements or may be an independent network element, and the present application does not limit the deployment situation of the EES network element in the network architecture. Typically, the EAS is registered to an EES, or information about an EAS is configured by the management system to an EES, which is called the EAS associated EES, which controls/manages the EAS registered/configured on the EES.

EAS may be an application deployed in an edge data network referred to as an application instance. In particular, a server application (e.g., social media software, augmented Reality (AR), virtual Reality (VR)) deploys an instance (instance) running on the EDN. An application may deploy one or more EAS in one or more EDNs, and the EAS deployed to run in different EDNs may be considered different EAS of an application, which may share a domain name, may use an anycast IP address, or may use different IP addresses. EAS may also be referred to as edge application (server), application instance, edge application instance, MEC application (server), EAS function, and the like.

2. An edge data network configuration server.

The edge data network configuration server may be a global management network element, and may be referred to as an (edge data network configuration server, EDNCS) or an Edge Configuration Server (ECS). For convenience of description, in the embodiment of the present application, an edge data network configuration server is taken as an ECS for example.

The ECS maintains information about each EDN, including the service scope and EES address of the edge data network. The service scope of the edge data network may be topological address information (e.g., cell ID, TAI (trace area ID), etc.) or geometric address information (e.g., information about province, city, district, or longitude and latitude), and the service scope may be a set of address information. In one implementation, the ECS network elements are deployed in a distributed manner, i.e., each ECS may manage edge data networks of different areas. It should be understood that the ECS network element may be co-located with other network elements or may be an independent network element, and the present application does not limit the deployment of the ECS network element in the network architecture.

3. User Equipment (UE): may include various handheld devices, vehicle mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem, as well as various forms of terminals, mobile Stations (MSs), terminals (terminals) or soft terminals, etc. having wireless communication capabilities. Such as water meters, electricity meters, sensors, etc.

Specifically, under the network architecture shown in fig. 1, the UE may include: edge Enabled Client (EEC) and Application Client (AC).

Wherein, the application client is a peer entity of the edge application on the UE side. The application client is used for an application user (user) to obtain application services from the application server. The application client is a client program applied on the terminal side, and the application client can be connected to an application server on the cloud to acquire application services, and can also be connected to an EAS (electronic article surveillance) deployed and operated in one or more EDNs to acquire the application services.

The EEC is a peer entity of the EES at the UE side. The EEC is used to register information of the EEC and information of the application client with the EES, perform security authentication and authorization, obtain an IP address of the EAS from the EES, and provide an edge computing enabling capability to the application client, such as the EAS discovery service returns the IP address of the EAS to the application client.

The EEC provides necessary support for an application client on the UE, and the functions of the EEC include: retrieve EDN information via EDGE-4, register UE with EES, retrieve available EAS, EAS availability change, EAS migration notification to EEC.

The application user signs a service agreement with an application provider so as to provide services for the application user, and the application user logs in an application client on the terminal and communicates with the EAS through the connection of the application client. The enabling client is a middleware layer, and is generally located in the operating system, or is located between the application client and the operating system. The application client may obtain the edge-enabled service from the enabling client in the form of an Application Programming Interface (API).

Illustratively, the user equipment in the embodiments of the present application may refer to an access terminal, a subscriber unit, a subscriber station, a mobile station, a relay 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 equipment. 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 a wireless communication function, a computing device or other processing device 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 Public Land Mobile Network (PLMN) for future evolution, or a user equipment in a future vehicle networking, and the like, which is not limited in this embodiment of the present application.

By way of example and not limitation, in the embodiments of the present application, a wearable device may also be referred to as a wearable smart device, which is a generic term for intelligently designing daily wearing by applying wearable technology, developing wearable devices, such as glasses, gloves, watches, clothes, shoes, and the like. A wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction and cloud interaction. The generalized wearable smart device has full functions and large size, and can realize complete or partial functions without depending on a smart phone, for example: smart watches or smart glasses and the like, and only focus on a certain type of application functions, and need to be used in cooperation with other devices such as smart phones, such as various smart bracelets for physical sign monitoring, smart jewelry and the like.

In addition, in the embodiment of the present application, the user equipment may also be user equipment in an internet of Things (IoT) system, where IoT is an important component of future information technology development, and a main technical feature of the present application is to connect an article with a network through a communication technology, so as to implement an intelligent network with interconnected human-computer and interconnected objects. In the embodiment of the present application, the IOT technology may achieve massive connection, deep coverage, and power saving for the terminal through a Narrowband (NB) technology, for example. In addition, in this embodiment of the application, the user equipment may further include sensors such as an intelligent printer, a train detector, and a gas station, and the main functions include collecting data (part of the user equipment), receiving control information and downlink data of the access network equipment, and sending electromagnetic waves to transmit uplink data to the access network equipment.

2. The fifth generation (5th Generation, 5G) moves the network.

In the embodiment of the present application, the structure of the 5G network is not limited, and reference may be made to the introduction of the related art, including a (radio) access network device (R) AN) and a 5G core network (5G core, 5gc).

Wherein, (R) AN is used to provide a network access function for authorized user equipment in a specific area, and can use transmission tunnels of different qualities according to the level of the user equipment, the service requirement, and the like.

The (R) AN can manage radio resources and provide access services for the ue, thereby completing forwarding of control signals and ue data between the ue and the core network, and the (R) AN can also be understood as a base station in a conventional network.

The access network device in the embodiment of the present application may be any communication device with a wireless transceiving function for communicating with the user equipment. The access network devices include, but are not limited to: an evolved Node B (eNB), a baseBand unit (BBU), an Access Point (AP), a wireless relay Node, a wireless backhaul Node, a Transmission Point (TP), a Transmission and Reception Point (TRP) in a wireless fidelity (WIFI) system, and the like, and may also be 5G, such as NR, a gNB in the system, or a transmission point (TRP or TP), one or a set (including multiple antenna panels) of base stations in the 5G system, or may also be a network Node forming the gNB or the transmission point, such as a baseBand unit (BBU), or a Distributed Unit (DU), and the like.

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 part of the function of the gNB and the DU implements part of the function of the gNB. For example, the CU is responsible for processing non-real-time protocols and services, and implements functions of a Radio Resource Control (RRC) layer and a Packet Data Convergence Protocol (PDCP) layer. The DU is responsible for processing a physical layer protocol and a real-time service, and implements functions of a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer. The AAU implements part of the physical layer processing functions, radio frequency processing and active antenna related functions. Since the information of the RRC layer eventually becomes or is converted from the information of the PHY layer, the higher layer signaling, such as the RRC layer signaling, may also be considered to be transmitted by the DU or by the DU + AAU under this architecture. It is to be understood that the access network device may be a device comprising one or more of a CU node, a DU node, an AAU node. In addition, the CU may be divided into access network devices in an access network (RAN), or may be divided into access network devices in a Core Network (CN), which is not limited in this application.

The 5GC at least comprises the following network elements:

1) And a user plane network element: for packet routing and forwarding, quality of service (QoS) handling of user plane data, etc.

In the 5G communication system, the user plane network element may be a User Plane Function (UPF) network element. In a future communication system, the user plane network element may still be a UPF network element, or may also have another name, which is not limited in this application.

2) And the access management network element: the present invention is mainly used for mobility management, access management, and the like, and may be used to implement other functions besides session management in a Mobility Management Entity (MME) function, for example, functions such as access authorization/authentication.

In the 5G communication system, the access management network element may be an access and mobility management function (AMF) network element. In the future communication system, the access management network element may still be an AMF network element, or may also have another name, which is not limited in this application.

3) And the session management network element: the method is mainly used for session management, internet Protocol (IP) address allocation and management of terminal equipment, selection of a termination point capable of managing a user plane function and a policy control and charging function interface, downlink data notification and the like.

In the 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 may also have another name, which is not limited in this application.

4) And the strategy control network element: the unified policy framework is used for guiding network behavior, and providing policy rule information for network elements (such as AMF, SMF network elements and the like) or terminal equipment.

In the 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 a future communication system, the policy control network element may still be a PCF network element, or may also have another name, which is not limited in this application.

5) And the application network element: the method is used for carrying out data routing of application influence, accessing to a network open function network element, carrying out strategy control by interacting with a strategy framework and the like.

In the 5G communication system, the application network element may be an Application Function (AF) network element. In a future communication system, the application network element may still be an AF network element, or may also have another name, which is not limited in this application.

6) Network slice selection network element: for selecting a network slice instance to serve the user equipment.

In the 5G communication system, the network slice selection element may be a Network Slice Selection Function (NSSF) element. In a future communication system, the network slice selection function network element may still be an NSSF network element, or may also have another name, which is not limited in this application.

7) And authenticating the service network element: the method is mainly used for user authentication and the like.

In the 5G communication system, the authentication service network element may be an authentication service function (AUSF) network element. In a future communication system, the authentication service function network element may still be an AUSF network element, or may also have another name, which is not limited in this application.

8) And the data management network element: the method is used for processing terminal equipment identification, access authentication, registration, mobility management and the like.

In the 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 a UDM network element, or may also have other names, which is not limited in this application.

It is to be understood that the network element or the function may be a network element in a hardware device, or may be a software function running on dedicated hardware, or a virtualization function instantiated on a platform (e.g., a cloud platform).

It should be noted that, in the current standard protocol, for example, technical Specification (TS) 23.501, TS23.502, and the like, the EES network element, the EAS network element, the ECS network element, and the like may all be referred to as an Application Function (AF) network element, and details are not described below.

In the network architecture shown in fig. 1, the EDGE-8 reference point supports interaction between the EDGE configuration server and the core network, for example, supporting: (1) Accessing core network functions and Application Programming Interfaces (APIs) for retrieving network capability information; (2) And providing service release notification to a core network (such as SMF). EDGE-1: the interface between the EES and the EEC supports the registration/deregistration of the EEC in the EES; edge application server discovery in an edge data network.

EDGE-2: and the interface between the EES and the 3GPP core network is used for acquiring the 3GPP network capability by the EES.

EDGE-3: the interface between the EES and the EAS supports EES registration/deregistration of the EAS, and comprises availability information, service range information, address information and the like of the EAS; the EES provides 3GPP network capability information (e.g., location information) to the EAS.

EDGE-4: the interface between the EEC and the ECS supports the ECS to provide/push configuration information to the EEC.

EDGE-5: and the interface between the AC and the EEC supports the AC to acquire accessed EAS information from the EEC.

EDGE-6: and the interface between the ECS and the EES supports the configuration of EES information on the ECS.

EDGE-7: and an interface between the EAS and the 5GC supports the EAS to acquire 5G network capability.

EDGE-8: and an interface between the ECS and the 5GC supports the ECS to acquire the 5G network capability.

EDGE-9: and the interfaces between different EESs in the same MEC node/across MEC nodes support application migration.

It should be noted that the names of the network elements and the communication interfaces between the network elements referred to in fig. 1 are simply described by taking the example specified in the current protocol as an example, but the embodiments of the present application are not limited to be applicable only to currently known communication systems. Therefore, the standard names appearing when the current protocol is described as an example are all functional descriptions, and the specific names of the network elements, interfaces, signaling and the like in the present application are not limited, and only indicate the functions of the network elements, interfaces or signaling, and can be correspondingly extended to other systems, such as 4G or future communication systems.

In order to facilitate understanding of the embodiments of the present application, a brief description is given of several basic concepts involved in the embodiments of the present application. It should be understood that the basic concepts described below are provided as examples of basic concepts defined in the current protocol, and are not intended to limit the application of the embodiments to only currently available systems. Therefore, the names appearing when the existing system is taken as an example for description are functional descriptions, and the specific names are not limited, only indicate functions, and can be correspondingly extended to other systems, such as 4G or future communication systems.

1、MEC。

The MEC can provide services and cloud computing functions required by the telecommunication user IT nearby by using the wireless access network, so as to create a telecommunication-level service environment with high performance, low delay and high bandwidth, accelerate the rapid downloading of various contents, services and applications in the network, and enable consumers to enjoy uninterrupted high-quality network experience.

2. A data network.

A Data Network (DN) refers to a service network of an operator or a third party, and may provide services (e.g., operator services, internet services, etc.) to a terminal.

3. A local data network.

The local DN may be an access point (access point) of a data network that is in close proximity to the user's point of attachment (attachment point).

4. Application context (application context).

An application context may refer to running state information associated with one or a group of users, e.g., game progress, historical data of ML, etc. Optionally, the application context may further include a context of a subscription of the one or more users in the EAS with the core network, such as a transaction identifier of the subscription. Optionally, the application context may also include a context of the one or more users on the EES, e.g., a transaction identification of the EAS subscription to the one or more users.

5. EEC context (EEC context).

The EEC context may refer to data related to the subscriber stored in the EES.

The EEC context may include EEC side information and EAS-EES subscription information. The EEC side information may include EEC registration information, EEC subscription information (e.g., EAS discovery subscription, EAS dynamic information subscription, etc.); the EAS-EES subscription information may include a UE location API, an application context relocation event, an AC information opening API, a UE identity API, and a quality of service (QoS) session API, etc.

6. Application context migration (ACR).

Application context migration may also be referred to as application context relocation, which is not differentiated in this application.

In the process of running the edge application, when the terminal moves out of the current service area, the currently-served EAS may not be able to continue to serve the currently-running application, or the currently-served EAS is not the optimal EAS for serving the terminal, and other EAS may be more suitable for serving the terminal, at which point a new EAS may be selected to serve the terminal. However, a temporary suspension or interruption of application service may be caused during the process of replacing the currently serving edge application server with a new edge application server, which may affect the transmission of application traffic.

Specifically, application context migration (ACR) may be performed based on the network architecture shown in fig. 1.

For convenience of description, the currently provided EAS is hereinafter referred to as source EAS (S-EAS), and the new EAS is hereinafter referred to as target EAS (T-EAS).

The application context migration flow can be mainly divided into the following four stages.

Stage 1: detection of application context migration.

At this stage, it may be determined that a context migration may be required. The target event may be detected by a detection entity. The target event may include a change in terminal location, an update in the end-user plane path, etc.

And (2) stage: a decision to apply context migration.

At this stage, the decision entity determines that a context migration is required.

And (3) stage: execution of application context migration.

At this stage, the context of the application is transferred from the source EAS to the target EAS by the executing entity. Further, the method includes discovery of the target EAS, and may further notify the terminal of information related to the target EAS, notify the EAS (which may be the source EAS and the target EAS) to initiate application context transfer, and cause the EES or the EAS to execute Application Function (AF) traffic impact (AF traffic) and carry N6 routing information of the T-EAS

And (4) stage: clean up work after context migration is applied.

At this stage, multiple entities are involved, the EAS informs the EEC via the EES of the application context transfer result, the AC initiates a new socket connection to the target EAS, etc.

It should be noted that the entities may be the same entity or different entities, and are not limited.

Several implementations of applying context migration are described below in conjunction with fig. 2-9.

FIG. 2 is an implementation of application context migration.

In this implementation, ACR is initiated by the EEC and a conventional EAS discovery procedure is employed.

The implementation includes the following steps 201 to 208:

in step 201, the eec detects a target event and decides to trigger application context migration.

The target event may include a UE location change, a UE user plane path update, and the like.

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

In step 202, the eec executes a service provisioning procedure (service provisioning) procedure to discover the T-EES.

Step 202 will be described in detail below with reference to (a) in fig. 3.

It should be understood that the discovery of the EES platform and the discovery process of the EAS are defined in the current standard, and the procedures provide the discovery of the EES platform and the discovery of the application instance in the application layer, the EES can be used as a Local DNS server function, and the UE obtains the address of the application instance from the MEC platform. Architectural and functional design uses a two-level discovery mechanism: the EES platform is discovered first and then the EAS is discovered from the EES platform.

Hereinafter, the registration procedure of the EEC will be described in detail with reference to (b) of fig. 3, and the registration procedure of the EAS will be described in detail with reference to (c) of fig. 3.

In step 203, the EEC performs a conventional EAS discovery (EAS discovery) procedure to discover one or more EAS's.

Step 203 will be described in detail below with reference to (a) in fig. 4.

In step 204, the AC selects T-EAS from the one or more EAS found by the EEC.

The AC information subscription flow will be described in detail below in conjunction with (b) in fig. 4, and the AC information notification flow will be described in detail in conjunction with (c) in fig. 4.

In step 205, the EEC sends an application context migration request message (application context location request) to the S-EES.

In step 206, S-EES sends application context migration response message (application context location response) to EEC.

Step 207, transfer of application context between S-EAS and T-EAS.

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

In step 208, after the application context is transferred, each entity performs a cleanup procedure.

It can be seen that in the implementation shown in fig. 2, the EEC detects, decides, determines T-EES and T-EAS, requests from the EEC to the S-EES to initiate user plane path modification, and initiates the transfer of application context by the EEC or AC.

Fig. 3 (a) is a schematic diagram of a service provisioning process.

The precondition is as follows: the ECS configures available edge computing service information about the EEC based on the UE location, service requirements, service preferences and connectivity for the EEC to discover about available EES.

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

in step 301a, the eec sends a service provisioning request message to the ECS.

The service provisioning request message may include an EEC ID (identifier), a security credential, an AC profile (AC profile), a UE identity, connection information, a UE location, and the like. The UE identity may include a Generic Public Subscription Identifier (GPSI) and the like.

As an example, table 1a shows an information element that the provisioning request message may include.

TABLE 1a

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

Specifically, the ECS performs authentication and authorization, and matches the EES registered on the ECS according to the AC configuration file and the UE location information provided by the EEC.

In step 303a, the ECS sends a service open response message to the EEC.

If the ECS can not determine the EEC information according to the service opening request message, the ECS should reject the service opening request of the EEC and give a failure reason.

If the ECS successfully processes the service activation request of the EEC, the ECS may provide the EDN connection information, the EES list satisfying the EEC request information, and the address identification information of the EES.

As an example, table 2a shows an information element that the service provisioning response message may include.

TABLE 2a

Fig. 3 (b) is a schematic diagram of the EEC registration flow.

The EEC registration procedure includes the following steps 301b to 304b:

in step 301b, the EEC sends an EEC registration (EEC registration) request message to the EES.

The request from the client includes the security credentials received after successful authorization of the edge computing service and may include a suggested expiration time. The request may also optionally include information indicating to the EES how the EEC desires to use the services of the EES. If an EEC is moved to another EES (referred to as a source EES) from its authority, the request from the EEC may include the identity and endpoint of the source EES, as well as the EEC context ID provided by the source EES, to maintain the EEC context and authorize EEC context relocation.

As an example, table 1b shows information elements that the EEC registration request message may include.

TABLE 1b

In step 302b, the ees receives the request from the EEC, verifies the registration request and verifies the security credentials.

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

In step 303b, after successful authentication of the request, if the received EEC registration request contains the EEC context ID, the source EESID and the EES endpoint, the EES will retrieve the EEC context from the source EES. Otherwise, this step is skipped.

In step 304b, the ees sends a registration response message to the EEC.

If the registration is successful, the EES sends a registration success response including the registration ID and possibly the newly allocated EEC context ID. The EEC stores the new EEC context ID and uses it when registering with another EES. The EES may also provide an expiration time to indicate to the EEC when the registration is automatically expired. To maintain registration, the EEC should send a registration update request before expiration. The EES shall treat the EEC as implicit deregistration if no registration update request is received before the expiry time.

And if the registration fails, the EES sends a registration failure response and gives a failure reason.

As an example, table 2b shows information elements that the registration response message may include.

TABLE 2b

Fig. 3 (c) is a schematic diagram of an EAS registration procedure.

The EAS registration process includes the following steps 301c to 304c:

in step 301c, the EAS determines that registration with the EES is required.

For example, an AS is instantiated and started

Step 302c, the EAS sends an EAS registration (EAS registration) request message to the EES. The request should include the EAS configuration file and possibly the recommended expiration time for the registration.

As an example, table 1c shows information elements that an EAS registration request message may include.

TABLE 1c

Cell	Status of state	Description of the invention
			EAS configuration file (EAS Profile)	Must choose	EAS configuration files
Security certificate (Security credentials)	Must choose	Security credentials for EAS
			Suggested expiration time (deployed expiration time)	Optionally	Recommended expiration time for registration

As an example, table 2c shows information elements that an EAS Profile may include.

TABLE 2c

In step 303c, the EES performs a registration authorization check to verify that the EAS has authorization to register with the EES.

In step 304c, the ees transmits an EAS registration response message to the EAS.

If the authorization is successful, the EES stores the EAS configuration file for later use (e.g., to service EAS discovery requests received from the EEC, etc.) and replies to the EAS with an EAS registration response. The EES may provide an expiration time to indicate to the EAS when registration is to be automatically expired. To maintain registration, the EAS should send a registration update request before the expiration time. The EES should treat the EAS as an implicit de-registration if a registration update request is not received before the expiration time

And if the registration failure EES sends a registration failure response, and a failure reason is given.

As an example, table 3c shows information elements that the registration response message may include.

TABLE 3c

Fig. 4 (a) is a schematic diagram of a conventional EAS discovery procedure.

The preconditions are as follows: 1) The EEC receives the information of the EES, such as the URL, IP address and the like of the EES; 2) The EES configures the ECSP EAS discovery policy.

The EAS discovery procedure includes the following steps 401a through 403a.

In step 401a, the EEC sends an EAS discovery request message to the EES.

The EAS discovery request message may include, among other things, the EEC ID and the security credentials. The EAS discovery request message may also include an EAS discovery filter (EAS discovery filter) to retrieve information about a particular EAS or a particular class of EAS (e.g., gaming applications).

As an example, table 4a shows information elements that an EAS discovery request message may include.

TABLE 4a

As an example, table 5a shows information elements that an EAS discovery filter may include.

TABLE 5a

As an example, table 6a shows the cells that an AC profile may include.

TABLE 6a

After receiving the EAS discovery request sent by the EEC, the EES performs an authorization check and determines one or more EAS, step 402 a. Specifically, if the EES determines that the EEC is authorized to discover the requested EAS, the EES determines one or more EAS based on the provided EAS discovery filter and the location of the UE. If the EAS discovery filter is not provided in the EAS discovery request message, the EES determines one or more EAS based on the UE specific traffic information on the EES and the UE location, or the EES determines one or more EAS by applying the ECSP policy (e.g., based only on the UE location). If the EES can not determine one or more EAS through the information carried in the EAS discovery request message, the UE specific service information and the UE location on the EES, or the ECSP policy, the EES rejects the EAS discovery request of the EEC and gives a corresponding failure reason. If the UE is located outside the geographical or topological service area of the EAS, the EES should not include the EAS in the EAS discovery response message.

In step 403a, the EES sends an EAS discovery response message to the EEC.

Wherein, if the processing of the EAS discovery request of the EEC is successful, the EAS discovery response message includes information of one or more discovered EAS and endpoint information thereof; if the EAS discovery request processing by the EEC fails, the EAS discovery response message includes a failure indication and a failure reason.

As an example, table 7a shows information elements that an EAS discovery response message may include.

TABLE 7a

Fig. 4 (b) is a schematic diagram of an AC information subscription flow.

The AC information subscription flow includes the following steps S401b to S403b:

in step S401b, the EAS transmits an AC information subscription request message to the EES.

The AC information subscription request message may contain a filter to retrieve information about a particular AC.

Step S402b, after receiving the EAS request, the EES processes the request, including:

an authorization check is performed to verify that the EAS is authorized to perform the operation. The EES determines matching AC information corresponding to the provided filters and synthesizes results. The EES stores the subscription information for future processing.

In step S403b, the EES sends an AC information subscription response message to the EAS.

As an example, table 4b shows an information element that the AC information subscription request message may include.

TABLE 4b

As an example, table 5b shows the cells that a filter may comprise.

TABLE 5b

Fig. 4 (c) is a schematic diagram of an AC information notification flow.

The AC information notification flow includes the following steps S401c to S403c:

in step S401c, the EES is triggered for AC information update.

For example, it receives an EEC registration request, it determines if it matches the filter provided by the EAS; also for example, if the AC geographic service area is included in the EAS-provided geographic service area.

Step S402c, the EES transmits an AC information notification message to the EAS.

As an example, table 4c shows information elements that the AC information notification message may include.

TABLE 4c

FIG. 5 is another implementation of application context migration.

In this implementation, ACRs are performed by the EEC over S-EES.

In step 501, the EEC detects a target event.

The target event may include a UE location change, a UE user plane path update, and the like. This step may be that the AC indicates via the Edge-5 interface whether the EEC needs to perform ACR detection.

Step 502, eec decides to trigger application context migration.

In step 503, EEC determines T-EAS.

In step 504, the EEC sends an application context migration request to the S-EES, which indicates that the S-EES further interacts with the S-EAS, triggering the S-EAS to perform a context transfer (transfer).

Step 505, S-EES transfers application context to S-EAS indication and between S-EAS and T-EAS.

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 transfer of the application context of the T-EES is completed, and indicating the result of the transfer of the application context.

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

Step 508, after receiving the application context migration completion message sent by S-EAS, the S-EES sends the application context migration completion message to the EEC to indicate that the EEC application context transfer is completed.

It can be seen that in the implementation shown in fig. 5, the EEC detects, decides, and determines the T-EES and the T-EAS, the EEC requests the S-EES to initiate the user plane path modification, and the S-EES initiates the transmission of the application context. A more detailed description of the stages shown in fig. 5 may refer to the related description in fig. 2, and will not be described again here. Unlike in the implementation shown in fig. 2, the transfer of the application context is initiated by the S-EES.

FIG. 6 is another implementation of application context migration.

In this implementation, ACR is performed by the EEC through the T-EES.

In step 601, the eec detects a target event.

In step 602, eec decides to trigger application context migration.

Step 603, EEC determines T-EAS.

In step 604, the EEC sends an application context migration request to the T-EES. The request is used to trigger the transfer of the application context, and the updating of the user plane path.

Step 605, T-EES indicates to T-EAS to request application context from S-EAS, application context is transferred between S-EAS and T-EAS.

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

Step 607, after receiving the application context migration completion message sent by the T-EAS, the T-EES sends the application context migration completion message to the EEC to indicate that the EEC application context transfer is completed.

It can be seen that in the implementation shown in fig. 6, the EEC detects, decides, determines T-EES and T-EAS, requests initiation of user plane path modification from the T-EES, and notifies the T-EAS of the transmission of the initiation application context. More detailed description of the stages shown in fig. 6 can refer to the related description in fig. 5, and will not be repeated here. Unlike in the implementation shown in fig. 5, the transfer of the application context is initiated by the T-EES.

FIG. 7 is another implementation of application context migration.

In this implementation, ACR is initiated by the S-EAS decision.

Step 701, S-EAS detects the target event, or S-EES detects the target event and notifies the S-EAS.

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

Step 703, S-EAS determines T-EAS.

Step 704, S-EES makes a notification of the target EAS information.

Step 705, transfer application context between S-EAS and T-EAS.

In step 706, after the application context is transferred, each entity executes a cleanup flow.

It can be seen that in the implementation shown in FIG. 7, detection is performed by S-EAS or S-EES, decision is made by S-EAS, T-EES and T-EAS are determined, user plane path modification is initiated by S-EAS, and transmission of application context is initiated by S-EES.

FIG. 8 is another implementation of application context migration.

In this implementation, ACR is performed by the S-EES.

In step 801, an EEC, S-EAS, or S-EES detects a target event.

Step 802, EEC or S-EAS notifies the S-EES of the detection of the target event.

This step is optional and if the EEC or S-EAS detects the target event, the EEC or S-EAS notifies the S-EES of the detection of the target event.

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

In step 804, the S-EES determines the T-EAS.

Step 805, S-EES makes notification of target EAS information.

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

Step 807, transfer of application context between S-EAS and T-EAS.

Step 808, after the application context is transferred, the T-EAS sends an application context migration complete message to the T-EES, indicating that the transfer of the application context of the T-EES is complete, and indicating the result of the transfer of the application context.

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

Step 810, after receiving the application context migration completion message sent by the S-EAS, the S-EES sends the application context migration completion message to the EEC to indicate that the EEC application context transfer is completed.

It will be appreciated that in the implementation shown in FIG. 8, detection is performed by EEC, S-EAS or S-EES, decision is made by S-EES, T-EES and T-EAS are determined, user plane path modification is initiated by S-EES, and S-EAS is notified of the transfer of the originating application context.

FIG. 9 is another implementation of application context migration.

The ACR mode shown in fig. 9 is an automatic ACR, which may also be referred to as a full ACR, or a full service ACR, or a full operation ACR.

In step 901, an automatic ACR is initiated by the S-EAS or S-EES.

In step 902, an EEC, S-EAS, or S-EES detects a target event.

Step 903, EEC or S-EAS notifies the S-EES of the detection of the target event.

Step 904, S-EES determines to initiate application context migration.

Step 905, S-EES determines T-EAS.

In step 906, the S-EES performs notification of destination-side information.

Step 907, S-EES informs S-EAS to perform context migration.

Step 908, S-EES executes the application flow impact process.

Step 909, S-EES initiates the transfer of the application context. Before this the application context is stored by the S-EAS to a fault address that allows access by the S-EES, also on the target side, the target EES and the target EAS sharing the memory address of one application context.

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

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

Step 912, after receiving the application context migration completion message sent from S-EAS, S-EES sends the application context migration completion message to EEC to indicate that the EEC application context transfer is completed.

It will be appreciated that in the implementation shown in FIG. 9, detection is performed by EEC, S-EAS or S-EES, decision is made by S-EES, T-EES and T-EAS are determined, user plane path modification is initiated by S-EES, and S-EAS is notified of the transfer of the originating application context.

As can be seen from the processes shown in fig. 2 and fig. 5 to 9, the EEC, AC, EES, and EAS can detect the ACR event, and after the ACR event is detected by a specific entity, the application context can be migrated by using a plurality of ACR manners. However, the ACR method described above may cause multiple functional entities to repeatedly detect ACR requirements of the same application, and cause conflicts in performing migration of multiple application contexts.

In order to avoid the defect that a plurality of functional entities repeatedly detect the ACR requirement of the same application in the current ACR mode, the application provides a method for migrating contexts.

The method for migrating contexts provided in the present application will be described in detail below with reference to fig. 11 to fig..

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD) system, a Worldwide Interoperability for Microwave Access (WiMAX) communication system, a 5G system, a New Radio (NR) or future network, and the like. The technical scheme provided by the application can also be applied to future communication systems, such as a sixth generation mobile communication system. The communication system may 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.

The embodiments shown below do not particularly limit the specific structure of the execution subject of the method provided by the embodiments of the present application, as long as the communication can be performed according to the method provided by the embodiments of the present application by running the program recorded with the code of the method provided by the embodiments of the present application, for example, the execution subject of the method provided by the embodiments of the present application may be a terminal device or a device in an edge network, or a functional module capable of calling the program and executing the program in the terminal device or the device in the edge network.

To facilitate understanding of the embodiments of the present application, the following description is made.

First, second, and various numerical numbers (e.g., "#1", "#2", etc.) shown in the present application are merely for convenience of description, and are not intended to limit the scope of the embodiments of the present application. E.g., to distinguish between different messages, etc. Rather than to describe a particular order or sequence. It should be understood that the objects so described are interchangeable under appropriate circumstances to enable description of aspects other than those of the embodiments of the application.

Second, in the present application, "preset" may include a predefined definition, for example, a protocol definition. The "predefined" may be implemented by saving a corresponding code, table, or other means that can be used to indicate related information in a device (for example, including a user device or a core network device) in advance, and the specific implementation manner of the present application is not limited thereto.

Third, the term "store" referred to in the embodiments of the present application may refer to a store in one or more memories. The one or more memories may be provided separately or integrated in the encoder or decoder, the processor, or the communication device. The one or more memories may also be provided separately, with a portion of the one or more memories being integrated into the decoder, the processor, or the communication device. The type of memory may be any type of storage medium, and the application is not limited thereto.

Fourth, the "protocol" referred to in this embodiment may refer to a standard protocol in the communication field, and may include, for example, a 5G protocol, a New Radio (NR) protocol, and a related protocol applied in a future communication system, which is not limited in this application.

Hereinafter, the method for information transmission provided by the embodiment of the present application is described in detail by taking interaction between various devices as an example without loss of generality.

The method for migrating the context comprises the following steps:

in step 1010, the ac acquires ACR pattern information.

The ACR mode information is information for determining an ACR method. The ACR method may also be called an ACR scenario or an ACR execution mode, and for convenience of description, the ACR method is described as an example hereinafter.

Illustratively, the ACR determining method may be embodied as an apparatus for determining to perform an ACR procedure. For example, it is determined that the device performing the ACR flow is the EEC, and it can be understood that it is determined that the ACR method is the ACR method #1.

Exemplarily, the ACR method in the embodiments of the present application includes at least one of:

the EEC uses conventional EAS Discovery (initialization by EEC using regular EAS Discovery) (as shown in fig. 2), EEC performs ACR through S-EES (as shown in fig. 5), S-EAS decides ACR scenario (S-EAS defined ACR scenario), S-EES performs ACR (S-EES defined ACR) (as shown in fig. 7), EEC performs ACR through T-EES (as shown in fig. 6), or automatic ACR (also called full/EES management, ACR/EEL layer management ACR/Automated ACR) (as shown in fig. 9), etc.

The ACR mode information may be a rule for determining the ACR method, and may also be called a selection rule of the ACR method, a determination rule of the ACR method, or ACR rule information, and the ACR rule information is taken as an example in the present application for explanation. The ACR rule information is described in detail below. The ACR rule information includes condition information that triggers an ACR procedure of at least one application.

As one possible implementation, the ACR rule information includes a correspondence between an application type and a device that executes an ACR procedure of an application belonging to the application type;

as another possible implementation manner, the ACR rule information includes a correspondence between event information of a procedure of triggering an ACR and a device executing the procedure of the preset ACR.

Illustratively, the ACR rule information may be represented by a correspondence relationship including a correspondence relationship between an ACR trigger event and a preset ACR execution manner (for example, including six manners as shown in fig. 2, 5 to 9 described above), and/or a correspondence relationship between an application type and a preset ACR execution manner; or,

the correspondence relationship includes a correspondence relationship between an ACR trigger event and a functional entity performing the ACR (at least including functional entities such as the AC, EAS, EES, EEC, etc. described above), and/or a correspondence relationship between an application type and a functional entity performing the ACR. Where performing an ACR may be understood as deciding after an ACR is to be made, sending an application context migration request (application context location) or triggering a context transfer or requesting a user plane path update. The ACR rule information is used in the embodiment of the present application to indicate an ACR trigger event and/or an application type for which an ACR procedure performed by at least one of AC, EAS, EES, and EEC.

For example, if the ACR triggering event is UE movement, the functional entity executing the ACR procedure is EES or EAS;

for example, if the ACR triggering event is server overload, the functional entity executing the ACR process is EAS;

for example, if the ACR trigger event is that DNAI changes, the functional entity executing the ACR process is EES;

for example, when the application type is an a application, the functional entity executing the ACR process is an EES;

also for example, when QoE quality degradation occurs, the functional entity performing the ACR procedure is an AC.

The condition information may be understood as ACR trigger condition information for indicating an ACR trigger condition, for example, the ACR trigger condition includes an ACR trigger event (e.g., UE movement, EAS overload, etc.); also for example, the ACR trigger condition includes an application type (e.g., an information application, a call application, etc.).

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

a first condition, a second condition, a third condition, and a fourth condition,

wherein when the first condition is satisfied, instructing the EEC to execute an ACR flow for a first application of the at least one application; when the second condition is satisfied, instructing the AC to perform an ACR flow for a second application of the at least one application; when the third condition is satisfied, instructing the EAS to perform an ACR procedure for a third application of the at least one application; when the fourth condition is satisfied, instructing the EES to execute an ACR flow for a fourth application of the at least one application.

It should be noted that, in the embodiment of the present application, one or more "first applications" may be referred to, and it is understood that when the first condition is satisfied, all the applications corresponding to the ACR flow that the EEC can execute are referred to as first applications, for example, the EEC executes the ACR flow for an application with an application type #1, and the application with the application type #1 may be one or more; similarly, one or more "second applications" may be provided, one or more "third applications" may be provided, and one or more "fourth applications" may be provided, for the same reason, which is not described herein again.

In addition, it should be noted that the "first application", "second application", "third application", and "fourth application" may be the same application, that is, an application corresponding to the AC. For example, when different conditions are satisfied, the functional entity executes an ACR procedure for a certain application.

The ACR mode information may specifically be an ACR method indicating the identity of the application client and the identity of the application client determined by the server,

wherein 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.

Specifically, the ACR mode information may be a correspondence between an Identity (ID) of the AC and an ACR method determined for the AC.

The correspondence between the application client identifier and the ACR method for executing the application corresponding to the application client identifier specifically includes:

an ACR method is pre-configured for the application corresponding to each client identifier; or, an ACR method is selected for each application corresponding to the client identifier.

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

Specifically, the AC acquiring the ACR mode information in the embodiment of the present application includes the following two cases:

in the first case, the AC acquires ACR mode information from an AC configuration file (AC profile) in the AC; or the AC determines the ACR pattern information from the AC profile.

For example, the AC profile is preconfigured with ACR mode information.

Step 1010 described above in case one is understood as step S1011 shown in fig. 10, the AC acquires ACR pattern information from an AC profile in the AC.

It can be understood that the ACR mode information is predefined in the AC profile, in case one the cells that can be included in the AC profile are as shown in table 8 below:

TABLE 8

In this case, the AC may send ACR mode information to the EEC, and the method flow shown in fig. 10 may further include:

in step 1012, the ac sends ACR mode information to the EEC.

For example, the AC sending the ACR pattern information to the EEC may be ACR rule information or an ACR method corresponding to the AC ID.

Illustratively, the AC sends an AC profile containing ACR mode information to the EEC over the EDGE-5 interface.

It should be noted that the AC sends the ACR mode information to the EEC, and may actively send a message (e.g., EDGE-5 interface message) carrying the ACR mode information to the EEC through the AC, or the EEC implicitly or explicitly subscribes to the ACR mode information, and after acquiring the ACR mode information, the AC may send a notification message to the EEC.

Another possible implementation method is that when the EEC does not subscribe implicitly or explicitly to the notification message, the AC may notify the EEC to subscribe implicitly or explicitly to the ACR mode information after acquiring the ACR mode information, and after the EEC subscribes to the ACR mode information, the AC sends the ACR mode information notification to the EEC.

Exemplarily, one implementation way for displaying the subscription ACR mode information as the EEC is as follows: the EEC subscribes ACR mode information, and requests the AC to send the ACR mode information to the EEC after acquiring the ACR mode information;

exemplarily, one implementation manner of implicitly subscribing to ACR mode information by the EEC is as follows: when the EEC subscribes notification information related to ACRs such as ACR information notification and the like to the AC, after requesting the AC to acquire ACR mode information, the AC sends the ACR mode information to the EEC in the information notification information related to ACRs such as ACR information notification and the like.

In case two, the AC receives ACR mode information from the EEC.

Illustratively, the AC receives ACR mode information from the EEC over the EDGE-5 interface.

Illustratively, the ACR pattern information received by the AC from the EEC through the EDGE-5 interface may be ACR rule information or an ACR method corresponding to the AC ID. Step 1010 above in case two is understood to be step 1021 shown in fig. 10, where the ac receives ACR mode information from the EEC.

It should be noted that the EEC sends the ACR mode information to the AC, and may actively send a message (e.g., EDGE-5 interface message) carrying the ACR mode information to the AC through the EEC, or implicitly or explicitly subscribe to the ACR mode information in the process of reporting information by the AC, and after acquiring the ACR mode information, the EEC may send a notification message to the AC.

Another possible implementation method is that when the AC does not subscribe implicitly or explicitly to the notification message, the EEC may notify the AC to subscribe implicitly or explicitly to the ACR mode information after acquiring the ACR mode information, and send the ACR mode information notification to the AC after the AC subscribes to the ACR mode information.

Illustratively, one implementation of displaying the subscription ACR mode information as the AC is as follows: the AC subscribes ACR mode information, and requests the EEC to send the ACR mode information to the AC after acquiring the ACR mode information;

exemplarily, one implementation manner of implicitly subscribing to ACR mode information as the AC described above is: when the AC subscribes to the notification information related to ACR, such as ACR information notification, to the EES, the EEC requests the EEC to acquire ACR mode information, and then the EEC sends and transmits ACR mode information to the AC in the information notification information related to ACR, such as ACR information notification.

In case two, the EEC acquires ACR pattern information, unlike step 1012 shown in case one above, in case two the EEC acquires ACR pattern information not from the AC (it is understood that it does not need to be sent to the AC if it is acquired from the AC). The following will describe in detail the possible manner of acquiring the ACR mode information by the EEC with reference to (a) in fig. 11, and details are not repeated here.

Further, when the second condition is satisfied, the AC performs an ACR flow for a second application of the at least one application, and the method flow shown in fig. 10 may further include:

step 1020, the ac performs an ACR flow for a second application of the at least one application.

Illustratively, when the AC determines that the second condition is satisfied (e.g., the ACR rule information indicates that the application type is type #1, the functional entity performing the ACR is the AC; further, for example, the ACR pattern information indicates that the application identification is AC ID #1, the method of performing the ACR is EEC using conventional EAS discovery), the AC performs an ACR flow for a second application of the at least one application (e.g., the second application is an application of type # 1).

Illustratively, the AC performs the ACR procedures in accordance with the selected ACR method.

Specifically, the AC determining whether the second condition is satisfied may be that the AC monitors a type of an application to which the application requiring context migration belongs, or triggers a type of an event for context migration, or monitors an identification of the application requiring context migration. For example, when the second condition is that a quality of experience (QoE) degradation event occurs, the AC triggers execution of the ACR, and then the AC executes the ACR after detecting the QoE degradation event, specifically, the AC may call an Application Programming Interface (API) provided by the EES to complete the ACR, for example, the flow corresponding to fig. 2.

Illustratively, the AC performs the ACR procedure according to the ACR method corresponding to the AC ID, and/or performs the corresponding ACR method corresponding to the AC ID, and further performs the related steps in the ACR method.

It should be noted that, in the embodiment of the present application, there is no limitation on how the functional entity (AC, EAS, EES or EEC) performs the ACR process, and reference may be made to the description in the related art (the processes shown in fig. 2, fig. 5 to fig. 9 described above). The embodiment of the application mainly relates to how to determine an ACR flow required to be executed by the user or an ACR method corresponding to the executed ACR according to the ACR mode information, and the current execution mode can be referred to after the determination.

In addition, it should be noted that the ACR execution flow referred to in the embodiments of the present application may be understood as an ACR initiation flow.

For ease of understanding, the manner in which the EEC obtains ACR mode information is described below in conjunction with (a) in fig. 11, which is a schematic flow chart of another method for migrating contexts provided herein.

Specifically, it can be seen from (a) in fig. 11 that the EEC acquires the ACR mode information includes the following cases:

case one, the EEC receives ACR mode information from the AC. The method comprises the following steps:

at step 1110, the eec receives ACR pattern information from the AC.

Reference is made to the description of step 1012 shown in fig. 10, which is not repeated here.

In case two, the EEC receives ACR mode information from the EES. The method comprises the following steps:

in step 1120, the ees acquires ACR mode information.

The manner in which the EES may obtain the ACR mode information will be described in detail below with reference to fig. 12. And are not described in detail herein.

In step 1130, the ees sends ACR pattern information to the EEC.

Exemplarily, the EES sending the ACR pattern information to the EEC may be ACR rule information, or an ACR method corresponding to the AC ID.

It should be noted that the EES sends the ACR mode information to the EEC, and may actively send a message (e.g., an EAS discovery response message or an EAS discovery update response message, an EEC registration response message or an EEC registration update response message or an EAS discovery notification message, or an EDGE-1 related message) carrying the ACR mode information to the EEC through the EES, or implicitly or explicitly subscribe to the ACR mode information in a process of reporting the information by the EEC, and after acquiring the ACR mode information, the EES may send the notification message to the EEC.

Another possible implementation method is that when the EEC does not subscribe implicitly or explicitly to the notification message, the EES may notify the EEC to subscribe implicitly or explicitly to the ACR mode information after acquiring the ACR mode information, and send the ACR mode information notification to the EEC after the EEC subscribes to the ACR mode information.

Exemplarily, one implementation of displaying the subscription ACR mode information as the EEC described above is: the EEC subscribes ACR mode information, requests the EES to send the ACR mode information to the EEC after acquiring the ACR mode information;

exemplarily, one implementation manner of implicitly subscribing to ACR mode information as the above EEC is: when subscribing the notification information related to ACR such as ACR information notification to the EES, the EEC requests the EES to acquire ACR mode information, and then the EES sends and sends ACR mode information to the EEC in the information notification information related to ACR such as ACR information notification.

As a possible implementation manner, as the EEC registration flow shown in (b) of fig. 3, the ACR mode information may be sent to the EEC in the EEC registration flow.

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

TABLE 9

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

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

As another possible implementation, as shown in (a) of fig. 4, in a conventional EAS discovery procedure, the ACR mode information may be transmitted to the EEC in the conventional EAS discovery procedure.

For example, the EES sends an EAS discovery response message or an EAS discovery update response message to the EEC, and the EAS discovery response message or the EAS discovery update response message carries the ACR mode information. The information elements carried in the EAS discovery response message are shown in table 10 below:

TABLE 10

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

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

Case three, EEC receives ACR pattern information from ECS. The method comprises the following steps:

in step 1140, the ecs obtains ACR mode information.

The following will describe in detail the possible manner of acquiring the ACR mode information by the ECS with reference to (b) in fig. 11, and details are not repeated here.

In step 1150, the ecs sends ACR mode information to the EEC.

It should be noted that the ECS sends the ACR mode information to the EEC, and may actively send a message (for example, a service activation (update) response message) carrying the ACR mode information to the EEC through the ECS, or implicitly or explicitly subscribe to the ACR mode information in the process of reporting the information by the EEC, and after acquiring the ACR mode information, the ECS may send a notification message to the EEC.

Another possible implementation method is that when the EEC does not subscribe implicitly or explicitly to the notification message, the ECS may notify the EEC to subscribe implicitly or explicitly to the ACR mode information after acquiring the ACR mode information, and send the ACR mode information notification to the EEC after the EEC subscribes to the ACR mode information.

Exemplarily, one implementation way for displaying the subscription ACR mode information as the EEC is as follows: the EEC subscribes the ACR mode information, and requests the ECS to send the ACR mode information to the EEC after acquiring the ACR mode information;

exemplarily, one implementation manner of implicitly subscribing to ACR mode information by the EEC is as follows: when the EEC subscribes to the ECS for the ACR-related notification information such as ACR information notification, the ECS is requested to acquire the ACR mode information, and then sends and sends the ACR mode information to the EEC in the ACR-related information notification information such as ACR information notification.

As a possible implementation manner, the service provisioning procedure shown in (a) in fig. 3 may send ACR mode information to the EEC in the service provisioning procedure.

For example, the ECS sends a service provisioning response message to the EEC, where the service provisioning response message carries the ACR mode information. The information element carried in the service activation response message is shown in table 11 below:

TABLE 11

And fourthly, the EEC formulates ACR mode information.

For example, in the embodiment of the present application, the ECS may formulate the ACR mode information according to information reported by the AC, the EEC, the EAS, and the EES. Specifically, the method comprises the following steps:

in step 1161, the EEC receives the second message from the EAS.

The second information includes EAS-supported ACR capability information and/or second ACR method request information.

Wherein the EAS-supported ACR capability information indicates an ACR trigger event or an application type corresponding to an ACR procedure that the EAS can perform (or detect), or an ACR event that the EAS can detect, or an application that the EAS can detect that an ACR occurs, or an EAS-supported or preferred ACR method, or a priority of the ACR method corresponding to each AC ID;

the second ACR method request information (referred to as request ACR method, or referred to as request ACR security) is used to request allocation of an ACR method, and may be EAS allocation of an ACR method or recommendation of an ACR method for each AC request, or EAS carries AC related information (e.g., AC ID) in the ACR method request information, and EAS allocation of an ACR method or recommendation of an ACR method for a required AC request.

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

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 UE identity 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, and other request messages and subscription request messages corresponding to EDGE-3 related subscriptions); EES to EEC (e.g., EDGE-1 related flows through EAS discovery EEC registration, EAS discovery subscription, etc.).

As a possible implementation, the EAS may implicitly report the second information.

The EAS subscribes to the EES for ACR management events including user plane path change (-user plane path change), ACR monitoring (-ACR monitoring), and ACR facilitation (-ACR authentication).

When the EAS subscribes to a user plane path change and/or an ACR monitoring event, implicitly indicating that the EAS selects an ACR method of an EAS execution ACR (S-EAS determined ACR security);

when the EAS subscribes to ACR facility, the EAS is implicitly instructed to select an ACR method in which the EES performs ACR (S-EES executed ACR).

Exemplarily, when the EAS subscribes to an ACR management event such as a user plane path change and/or an ACR monitoring, the EAS is notified when the EES subscribes to the ACR event or the ACR needs, and the EAS determines whether to execute an ACR procedure according to the event, which belongs to an implementation manner of the above implicit indication.

Illustratively, when the EAS subscribes to an ACR event management event such as ACR failure, for subscribing to the EES for the relevant notification in the ACR process, the EAS is notified, and the EAS may receive the relevant event in the ACR process, which belongs to one implementation of the implicit indication described above.

Further, when the EAS subscribes to the ACR management event from the EES, the EAS optionally carries an AC ID, and the ACR method for implicitly indicating that the EES selects for each AC is an ACR method for the EES to perform ACR (S-EES executed ACR) or an ACR method for the EAS to perform ACR (S-EAS determined ACR scientific).

Step 1162, the EEC receives the third message from the AC.

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

Wherein, the ACR capability information supported by the AC indicates an ACR trigger event or an application type corresponding to an ACR procedure that the AC can perform (or detect), or an ACR event that the AC can detect, or an application that the AC can detect an ACR occurs, or an ACR method supported or preferred by the AC, or a priority of the ACR method corresponding to each AC ID;

the third ACR method request information (referred to as request ACR method, or referred to as request ACR scenario) is used to request allocation of an ACR method, and may allocate an ACR method or suggest an ACR method for an AC for each AC request, or the AC carries AC related information (e.g., AC ID) in the ACR method request information, and allocate an ACR method or suggest an ACR method for a required AC request.

The specific third information sending process in this embodiment includes:

AC to EEC (e.g., via EDGE-5 interface).

In step 1163, the EEC receives 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.

Wherein, the ACR capability information supported by the EES indicates an ACR trigger event or an application type corresponding to an ACR procedure that the EES can perform (or detect), or an ACR event that the EES can detect, or an application that the EES can detect an ACR occurs, or an ACR method supported or preferred by the EES, or a priority of the ACR method corresponding to each AC ID;

the fourth ACR method request information (referred to as request ACR method or request ACR discovery) is used for requesting allocation of the ACR method, and may allocate the ACR method or suggest the ACR method for the EES for each AC request, or the AC carries AC related information (e.g., AC ID) in the ACR method request information, and allocates the ACR method or suggests the ACR method for the EES for the required AC request.

The fourth information specific sending process in this embodiment includes:

EES to EEC (e.g., EDGE-1 related flows through EAS discovery EEC registration, EAS discovery subscription, etc.).

In step 1164, the eec formulates ACR pattern information.

The EEC sets an ACR triggering rule according to information reported by the AC, the EES and the EAS, namely aiming at an ACR event (UE mobility and EAS overload) or an application type, distributing the event or the application type of the ACR to be detected and executed for each functional entity (AC, EAS, EEC and EES);

and/or the EEC sets the ACR method corresponding to each AC according to the supported ACR methods of the AC, EEC, EES, and EAS (optionally, the supported ACR method for each AC).

Illustratively, 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, EAS supports detecting UE overload class events, the EEC may set the ACR method of the application corresponding to the AC as EES executing ACR, S-EES executed ACR, after each entity receives the ACR method of the application corresponding to the AC, the EES executes detection and determination of ACR, and the remaining entities execute the steps required for correlation in the ACR flow (the subsequent steps may be called and executed by the related entities), for example, the EES notifies the EAS to execute transmission of application context, and the like.

For information of application types or application related information (e.g., AC ID) reported by each entity, such as AC ID #1, AC supported ACR method #1 and ACR method #2, EEC #1 supported ACR method #2 and ACR method #3, ees supported ACR method #1 and ACR method #2, eas supported ACR method #2 and ACR method #3, the EEC may set the ACR method of the application corresponding to the AC ID #1 as ACR method #2, and the remaining entities perform steps required for correlation in the ACR flow (subsequent steps may be called to be performed by the related entities).

If the ACR methods supported by the entities are violated and collided, when the ACR mode information is issued, failure indication information may be returned, and the failure indication information carries the failure reason, which is the ACR method violation and collision supported by the entities, or further includes information (e.g., updated second information, updated third information, etc.) re-reported by the entities.

In the case shown in the second, third, and fourth cases shown in (a) in fig. 11, after the EEC acquires the ACR mode information, the EEC may send the ACR mode information to the AC, and the method flow shown in (a) in fig. 11 further includes:

step 1160, eec sends ACR pattern information to AC.

The description of step 1021 shown in fig. 10 is referred to, and will not be repeated here.

In step 1171, the eec sends ACR mode information to the EES.

It should be noted that the EEC sends the ACR mode information to the EES, and may actively send a message (e.g., a service activation (update) response message) carrying the ACR mode information to the EES through the EEC, or implicitly or explicitly subscribe to the ACR mode information in a process of reporting the information by the EES, and after acquiring the ACR mode information, the EEC may send a notification message to the EES.

Another possible implementation method is that when the EES does not subscribe implicitly or explicitly to the notification message, the EEC may notify the EES to subscribe implicitly or explicitly to the ACR mode information after acquiring the ACR mode information, and after the EES subscribes to the ACR mode information, the EES sends the ACR mode information notification to the EES.

Exemplarily, one implementation of displaying the subscription ACR mode information as the EES is as follows: the EES subscribes ACR mode information, requests the EEC to send the ACR mode information to the EES after acquiring the ACR mode information;

exemplarily, one implementation manner of implicitly subscribing to ACR mode information as the EES described above is: when subscribing the notification information related to ACR such as ACR information notification to the EEC, the EES requests the EEC to acquire the ACR mode information, and then the EEC sends and sends the ACR mode information to the EES in the information notification information related to ACR such as ACR information notification.

Illustratively, the sending of the ACR mode information to the EES by the EEC may be ACR rule information, or an ACR method corresponding to the AC ID.

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

As a possible implementation manner, as the EEC registration flow shown in (b) of fig. 3, the ACR mode information may be sent to the EES in the EEC registration flow.

For example, the EEC sends an EEC registration request message to the EES, where the EEC registration request message carries AC related information (e.g., AC ID) (cells carried in the EEC registration request message are described in table 1b above), and the AC profile includes ACR mode information (cells carried in the AC profile are described in table 8 above).

As another possible implementation, as shown in (a) of fig. 4, the ACR mode information may be sent to the EES in a conventional EAS discovery procedure.

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

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 a single request or subscription message carries the ACR mode information, and the specific bearer message is not limited.

The condition information included by the above-described known ACR mode information may be used to indicate a first condition, and when the first condition is satisfied, the EEC performs an ACR procedure for a first application of the at least one application. The method flow shown in fig. 11 (a) may further include:

step 1170, the eec performs an ACR flow for a first application of the at least one application.

Illustratively, when the EEC determines that the first condition is satisfied (e.g., the ACR mode information indicates that the ACR triggering event is UE movement, the functional entity performing ACR is the EEC; further, for example, when the ACR mode information indicates that the application identification is AC ID #2, the method performing ACR is that the EEC performs ACR through T-EES), the EEC performs an ACR procedure for a first application of the at least one application (e.g., the ACR procedure for the first application is an ACR procedure when the ACR triggering event is UE movement).

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

Illustratively, the EEC executes the ACR procedure according to the ACR method corresponding to the AC ID, and/or executes the corresponding ACR method corresponding to the AC ID, further executing the relevant steps in the ACR method.

For ease of understanding, the manner in which the ECS obtains ACR mode information is described below in conjunction with (b) in fig. 11, which is a schematic flow chart of the present application providing yet another method for migrating contexts.

Specifically, it can be seen from (b) in fig. 11 that the ECS acquires the ACR mode information includes the following cases:

in case one, the ECS formulates ACR mode information.

For example, in the embodiment of the present application, the ECS may set the ACR mode information according to the capabilities of the AC, the EEC, the EAS, and the EES. Specifically, the method comprises the following steps:

step 1141, the ecs receives the second information from the EAS.

The second information includes EAS supported ACR capability information and/or ACR method request information.

the ACR method request information (referred to as request ACR method or request ACR scenario) is used to request allocation of the ACR method, and may allocate the ACR method or suggest the ACR method for each AC request EES, or EAS carries AC profile in the ACR method request information, and allocates the ACR method or suggests the ACR method for the required AC request EES.

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 UE identity 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, and other request messages, subscription request messages corresponding to EDGE-3 related subscriptions, such as an EAS registration request, an EAS registration update request, a UE location request message, a subscription request message, an ACR management 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, and the like); EES to ECS (e.g., service provisioning procedures).

In step 1142, the ECS receives the first message from the EEC.

The first information includes at least one of AC-supported ACR capability information, EEC-supported ACR capability information, first ACR method request information, or third ACR method request information.

Wherein, the AC-supported ACR capability information indicates an ACR trigger event or an application type corresponding to an ACR procedure that the AC can perform (or detect), or an ACR event that the AC can detect, or an application that the AC can detect an ACR occurs, or an ACR method that the AC supports or prefers, or a priority of the ACR method corresponding to each AC ID;

the third ACR method request information (referred to as request ACR method, or referred to as request ACR scenario) is used for requesting allocation of an ACR method, and may allocate an ACR method or suggest an ACR method for an AC for each AC request, or an AC carries AC related information (e.g., AC ID) in the ACR method request information, and allocate an ACR method or suggest an ACR method for a required AC request;

the ACR capability information supported by the EEC indicates an ACR trigger event or an application type corresponding to an ACR procedure that the EEC can perform (or detect), or an ACR event that the EEC can detect, or an application in which an ACR occurs, or an ACR method supported or preferred by the EEC, or a priority of the ACR method corresponding to each AC ID;

the first ACR method request information (referred to as request ACR method or request ACR discovery) is used for requesting allocation of the ACR method, and may allocate the ACR method or suggest the ACR method for the EEC for each AC request, or the AC carries AC related information (e.g., AC ID) in the ACR method request information, and allocate the ACR method or suggest the ACR method for the EEC for the required AC request.

In case that 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 through the EDGE-5 interface, the AC profile including the ACR capability information supported by the AC, and/or the third ACR method request information.

The specific first information sending process in this embodiment includes:

EEC to ECS (e.g., service provisioning request message carrying the first information).

As a possible implementation manner, the EEC may implicitly report the first information.

For example, the EEC subscribes to the EES for the first ACR method request information including two types of events, which may be understood as that the EEC subscribes to two types of ACR events (e.g., target information notification (target information notification) and ACR completion notification (ACR completion notification)) to the EES.

The subscription target information notification is applicable to an EAS or EES initiated ACR method (including S-EAS determined ACR scenario, S-EES executed ACR, and Automated ACR), that is, an ACR method initiated by a network side.

When the EES or EAS performs a T-EAS discovery procedure, i.e., an EAS or EES-initiated target EAS discovery procedure, the EES or EAS needs to send a discovered target information notification to the EEC, the target information notification including selected target EES related information and selected target EAS related information.

The ACR completion notification is applicable to all ACR methods. The EEC subscribes ACR completion information to the EES (or when the EEC unsubscribes target information notification and other notifications related to ACR flow execution, the EEC is implicitly instructed not to initiate the ACR flow) for notifying the ACR completion (application context relocation completion, which may further include application context transmission completion and/or EEC context transmission completion) by the network side. The EES may determine whether the EEC has selected the EEC to execute one of three ACR procedures (e.g., initiation by EEC using regular EAS Discovery, EEC executed ACR via S-EES, and EEC executed ACR via T-EES) according to the difference of the EEC subscription ACR information.

Further, the EEC carries the AC ID in the ACR information request message, and an ACR event object information notification (target information notification) and/or an ACR completion notification (ACR complete notification) corresponding to the AC ID, where the ACR method for implicitly indicating the EES to select for each AC is an ACR method (S-EAS determined ACR Discovery, S-EES executed ACR, automated ACR) initiated by the network side or an ACR method (Initiation by EEC using regulated EAS Discovery, EEC executed ACR view S-EES, EEC executed ACR view T-EES) initiated by the EEC side.

In step 1143, the ECS receives the fifth information from the EES.

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

Wherein, the EAS-supported ACR capability information indicates an ACR trigger event or an application type corresponding to an ACR procedure that the EAS can perform (or detect), or an ACR event that the EAS can detect, or an application that the EAS can detect an ACR occurring, or an EAS-supported or preferred ACR method, or a priority of the ACR method corresponding to each AC ID;

the second ACR method request information (referred to as request ACR method, or referred to as request ACR security) is used for requesting allocation of the ACR method, and may request an EES for each AC to allocate the ACR method for the EAS or suggest the ACR method, or the EAS carries AC related information (e.g., AC ID) in the ACR method request information, and requests the EES for the EAS to allocate the ACR method for the required AC or suggest the ACR method;

the ACR capability information supported by the EES indicates an ACR trigger event or an application type corresponding to an ACR procedure that the EES can perform (or detect), or an ACR event that the EES can detect, or an application that the EES can detect an ACR occurs, or an ACR method supported or preferred by the EES, or a priority of the ACR method corresponding to each AC ID;

the fourth ACR method request information (referred to as request ACR method, or referred to as request ACR scenario) is used to request allocation of an ACR method, and may allocate an ACR method or suggest an ACR method for an EES for each AC request, or the AC carries AC related information (e.g., AC ID) in the ACR method request information, and allocate an ACR method or suggest an ACR method for an EES for a required AC request.

In a case where the fifth information includes EAS-supported ACR capability information, and/or the second ACR method request information, the EAS includes the EAS-supported ACR capability information by sending a message (e.g., by 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 identity API response message, a notification message, a QoS session creation response message, a notification message, an ACR management event response message, an EDGE-3 related subscription-corresponding response message in a notification message, a notification message) to the EES, and/or the second ACR method request information.

The fifth specific information sending process in this embodiment includes:

EES to ECS (e.g., service open procedures).

In step 1144, the ecs formulates ACR mode information.

The ECS sets an ACR trigger rule according to the information reported by the AC, EAS, EEC, and EES, that is, allocates an event or an application type for each functional entity (AC, EAS, EEC, EES) to be detected and perform ACR for an ACR event (UE mobility, EAS overload) or for an application type.

And/or the ECS sets the ACR method corresponding to each AC according to the supported ACR method reported by the AC, EAS, EEC and EES or the optimized ACR method.

Illustratively, 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, EAS supports detecting UE overload class events, the ECS sets the ACR method of the application corresponding to the AC as an EES executing ACR, S-EES executed ACR, after each entity receives the ACR method of the application corresponding to the AC, the EES executes detection and determination of the ACR, and the remaining entities execute the steps required for association in the ACR flow (the subsequent steps are called and executed by the related entities), for example, the EES notifies EAS to execute transmission of the application context, and the like.

For information of application types or application related information (e.g., AC IDs) reported by each entity, for example, AC ID #1, AC supporting ACR method #1 and ACR method #2, eec #1 supporting ACR method #2 and ACR method #3, ees supporting ACR method #1 and ACR method #2, eas supporting ACR method #2 and ACR method #3, the ECS may set the ACR method of the application corresponding to the AC ID #1 as ACR method #2, and the remaining entities perform steps required for correlation in the ACR flow (subsequent steps may be called by the related entities).

If the ACR methods supported by the entities are violated and collided, when the ACR mode information is issued, failure indication information may be returned, and the failure indication information carries the failure reason, which is the ACR method violation and collision supported by the entities, or further includes information (e.g., updated first information, updated fifth information, etc.) re-reported by the entities.

And in case two, the ECS sets an ACR triggering rule.

Step 1145, the ecs assigns each functional entity (AC, EAS, EES, EEC) the event or application type that needs to detect and perform ACR for ACR event (e.g., UE mobility, EAS overload) or for application type.

Illustratively, the ECS sets the ACR method for each AC (e.g., AC ID).

In the embodiment of the present application, how the ECS sets the ACR mode information is not limited, and the setting may be performed according to a historical ACR procedure or may also be performed according to the capability of each functional entity.

Specifically, after the ECS acquires the ACR mode information, the ECS needs to send the ACR mode information to another functional entity, and (b) in fig. 11 further includes:

in step 1146, the ecs sends ACR mode information to the EEC.

Referring to step 1150, the description is omitted here.

In step 1147, the ecs sends ACR mode information to the EES.

It should be noted that the ECS sends the ACR mode information to the EES, and may actively send a message carrying the ACR mode information (for example, an EES registration (update) response message) to the EES through the ECS, or implicitly or explicitly subscribe to the ACR mode information in a process of reporting the information by the EES, and after acquiring the ACR mode information, the ECS may send a notification message to the EES.

Another possible implementation method is that when the EES does not subscribe implicitly or explicitly to the notification message, the ECS may notify the EES to subscribe implicitly or explicitly to the ACR mode information after acquiring the ACR mode information, and after the EES subscribes to the ACR mode information, the ECS sends the ACR mode information notification to the EES.

Exemplarily, one implementation of displaying the subscription ACR mode information as the EES is as follows: the EES subscribes the ACR mode information and requests the ECS to send the ACR mode information to the EES after acquiring the ACR mode information;

exemplarily, one implementation manner of implicitly subscribing to ACR mode information by the EES is as follows: when subscribing ACR related notification information such as ACR information notification to the ECS, the EES requests the ECS to acquire ACR mode information, and then the ECS sends and sends the ACR mode information to the EES in the ACR related information notification information such as ACR information notification.

Illustratively, the ECS sends EES registration response information to the EES, where the EES registration response information includes the ACR mode information.

In step 1148, the ees transmits ACR mode information to the EAS.

It should be noted that, the EES sends the ACR mode information to the EAS, and may actively send a message (e.g., an EAS registration (update) 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, and a response message, a notification message corresponding to an EDGE-3 related subscription in the ACR management message) carrying the ACR mode information to the EAS, or implicitly or explicitly subscribe the ACR mode information in a process of reporting the information, and after acquiring the ACR mode information, the EES may send the notification message to the EAS.

Another possible implementation method is that when the EAS does not implicitly or explicitly subscribe to the notification message, the EES may notify the EAS of subscribing to the ACR mode information after acquiring the ACR mode information, and send the ACR mode information notification to the EAS after waiting for the EAS of subscribing to the ACR mode information.

Illustratively, one implementation of subscribing to ACR mode information as the above EAS display is: the EAS subscribes to the ACR mode information, requests the EES to send the ACR mode information to the EAS after acquiring the ACR mode information;

illustratively, one implementation of the above EAS implicit subscription ACR mode information is: when the EAS subscribes to notification information related to ACR such as ACR information notification to the EES, the EES is requested to acquire ACR mode information, and then the EES sends and sends ACR mode information to the EAS in the information notification information related to ACR such as ACR information notification.

Specifically, it can be seen from fig. 12 that the EES acquires the ACR pattern information includes the following cases:

in case one, the EES receives ACR mode information from the EEC. The method comprises the following steps:

in step 1210, the ees receives ACR pattern information from the EEC.

Reference is made to step 1171 above and will not be described further herein.

In the first case shown in fig. 12, after the EES acquires the ACR mode information, the EES may send the ACR mode information to the EAS, and the method flow shown in fig. 12 further includes:

in step 1211, the ees transmits ACR mode information to the EAS.

Illustratively, the EES transmitting the ACR mode information to the EAS may be ACR rule information, or an ACR method corresponding to the AC ID.

It should be noted that the EES sends the ACR mode information to the EAS, and may actively send a message carrying the ACR mode information (e.g., 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, a response message corresponding to an EDGE-3 related subscription in the notification message, a notification message service provisioning (update) response message) to the EAS, or implicitly or explicitly subscribe the ACR mode information in a process of reporting the EAS information, and after obtaining the ACR mode information, the EES may send the notification message to the EAS.

Another possible implementation method is that when the EAS does not implicitly or explicitly subscribe to the notification message, the EES may notify the EEC to implicitly or explicitly subscribe to the ACR mode information after acquiring the ACR mode information, and after waiting for the EAS to subscribe to the ACR mode information, the EES sends the ACR mode information notification to the EAS.

As a possible implementation, as shown in (c) of fig. 3, the EAS registration procedure may be performed in which the ACR mode information is transmitted to the EAS.

For example, the EES transmits an EAS registration response message or an EAS registration update response message to the EAS, and the EAS registration response message or the EAS registration update response message carries the ACR mode information. The information element carried in the EAS registration response message or the EAS registration update response message is shown in table 12 below:

TABLE 12

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

the EAS transmits an EAS registration update request message to the EES before the EES transmits an EAS registration update response message to the EAS.

As another possible implementation, as shown in (b) of fig. 4, the AC information subscription procedure may send the ACR mode information to the EAS in the AC information subscription procedure.

For example, the EES transmits an AC information subscription response message including ACR mode information to the EAS.

As still another possible implementation, as an AC information notification procedure shown in (c) of fig. 4, the ACR mode information may be transmitted to the EAS in the AC information notification procedure.

For example, the EES sends an AC information notification message to the EAS, where the AC information notification message carries AC related information (e.g., AC ID) (cells carried in the AC information notification message are described in table 4c above), and the AC profile includes ACR mode information (cells carried in the AC profile are described in table 8 above).

For example, the EES sends an AC information notification message to the EAS, and the cells carried in the AC information notification message are as follows:

in the second case, the EES acquires ACR mode information from an EES configuration file (EES profile) in the EES; or the EES determines the ACR mode information from the EES profile.

For example, the EES profile is preconfigured with ACR mode information.

The acquiring of the ACR mode information by the EES in case two includes step S1220 shown in fig. 12, and the EES acquires the ACR mode information from the EES configuration file in the EES.

It can be understood that the ACR mode information is predefined in the EES profile, and the cells that can be included in the EES profile in case two are shown in table 13 below:

watch 13

In the second case shown in fig. 12, after the EES acquires the ACR mode information, the EES may send the ACR mode information to the EAS and/or the EEC, and specifically may send the determined ACR method to the EAS and/or the EEC, where the method flow shown in fig. 12 further includes:

in step 1221, the ees transmits ACR pattern information to the EAS.

Reference is made to the above description of step 1211, which is not repeated here.

Step 1222, ees sends ACR mode information to EEC.

Reference is made to the description of step 1130 shown in FIG. 11, which is not repeated here.

Case three, the EES receives ACR mode information from the ECS. The method comprises the following steps:

in step 1230, the ecs acquires ACR mode information.

Reference is made to the description of step 1140 shown in (a) in fig. 11, which is not described herein again.

In step 1240, the ecs sends ACR pattern information to the EES.

Refer to the description of step 1147 shown in (b) in fig. 11, which is not repeated here.

In the third case shown in fig. 12, after the EES acquires the ACR mode information, the EES may send the ACR mode information to the EAS and/or the EEC, and the method flow shown in fig. 12 further includes:

in step 1241, the ees transmits ACR mode information to the EAS.

The description of step 1211 mentioned above is not repeated herein.

In step 1242, the ees sends ACR mode information to the EEC.

Reference is made to the description of step 1130 shown in fig. 11, which is not repeated herein.

Case four, the EES receives ACR pattern information from the EAS. The method comprises the following steps:

in step 1250, the eas acquires ACR mode information.

A detailed description of a possible manner of EAS acquisition of ACR pattern information will be given below with reference to fig. 13. And will not be described in detail herein.

Step 1260, eas sends ACR mode information to EES.

It should be noted that: the EAS sends ACR mode information to the EES, and may actively send a message carrying the ACR mode information (e.g., 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 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, and other EDGE-3 related subscription corresponding request messages, subscription request messages, and other EDGE-3 related subscription corresponding request messages or subscription requests) to the EES through the EAS, or implicitly or explicitly subscribe the ACR mode information in a process of reporting information by the EES, and the EAS may send a notification message to the EES after acquiring the ACR mode information.

Another possible implementation method is that when the EES does not subscribe implicitly or explicitly to the notification message, the EAS may notify the EES to subscribe implicitly or explicitly to the ACR mode information after acquiring the ACR mode information, and after the EES subscribes to the ACR mode information, the EAS sends the ACR mode information notification to the EES.

Exemplarily, one implementation of displaying the subscription ACR mode information as the EES is as follows: the EES subscribes the ACR mode information, requests the EAS to send the ACR mode information to the EES after acquiring the ACR mode information;

exemplarily, one implementation manner of implicitly subscribing to ACR mode information by the EES is as follows: when subscribing the notification information related to ACR such as ACR information notification to the EAS, the EES requests the EAS to acquire the ACR mode information, and then the EAS transmits and transmits the ACR mode information to the EES in the information notification information related to ACR such as ACR information notification.

As a possible implementation manner, as shown in (c) of fig. 3, the EAS registration procedure may be used to send ACR mode information to the EES.

For example, the EAS sends an EAS registration request message to the EES, where the EAS registration request message carries ACR mode information.

As another possible implementation manner, as shown in (b) of fig. 4, in the AC information subscription procedure, the ACR mode information may be sent to the EES.

For example, the EAS sends an AC information subscription request message to the EES, where the AC information subscription request message includes ACR mode information.

In a fourth case shown in fig. 12, after acquiring the ACR mode information, the EES may send the ACR mode information to the EEC, and the method flow shown in fig. 12 further includes:

in step 1261, the ees sends ACR mode information to the EEC.

And fifthly, the EES formulates ACR mode information.

For example, in the embodiment of the present application, the setting of the ACR mode information by the EES may also be setting of the ACR mode information according to information reported by the AC, the EEC, and the EAS. Specifically, the method comprises the following steps:

in step 1270, the ees receives the second information from the EAS.

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 UE identity 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, and other EDGE-3 related subscription-corresponding request messages, subscription request messages).

As a possible implementation manner, as shown in (c) of fig. 3, the EAS registration procedure may send ACR capability information supported by EAS detection to the EES.

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

As another possible implementation, as shown in (b) of fig. 4, the AC information subscription procedure may send EAS-supported ACR capability information to the EES in the AC information subscription procedure.

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

In step 1271, the EES receives the first information from the EEC.

In case that the first information includes ACR capability information supported by the AC, and/or third ACR method request information, the AC sends AC profile including the ACR capability information supported by the AC, and/or the third ACR method request information to the EEC through the EDGE-5 interface.

The specific first information sending process in this embodiment includes:

As a possible implementation manner, as shown in (b) of fig. 3, the first information may be sent to the EES in the EEC registration procedure.

For example, the EEC sends an EEC registration request message to the EES, where the EEC registration request message carries the first information.

As another possible implementation, as shown in fig. 4 (a), the first information may be sent to the EES in a conventional EAS discovery procedure.

As another possible implementation, in the EAS discovery subscription procedure as shown in (a) of fig. 4, the first information may be sent to the EES in the EAS discovery subscription request.

For example, the EEC sends an EAS discovery request message to the EES, where the EAS discovery request message carries the first information.

Wherein the ACR capability information supported by the AC, and/or the third ACR method request information is obtained from the AC through step 1272.

In step 1272, the EEC receives AC third information from the AC.

Illustratively, the AC sends the third information to the EEC over the EDGE-5 interface.

In step 1280, the ees formulates ACR mode information.

The EES sets an ACR trigger rule according to the information reported by the AC, the EEC, the EES and the EAS, that is, for an ACR event (UE mobility, EAS overload) or for an application type, each functional entity (AC, EAS, EES and EEC) is allocated with an event or an application type which needs to detect and execute ACR.

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

Illustratively, 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 class events, the EES may set the ACR method of the application corresponding to the AC as an EES executing ACR and an S-EES executed ACR, after each entity receives the ACR method of the application corresponding to the AC, the EES executes detection and determination of the ACR, and the remaining entities execute the steps required for association in the ACR flow (the subsequent steps may be called and executed by the related entities), for example, the EES notifies EAS to execute transmission of the application context, and the like.

For information of application types or application related information (e.g., AC IDs) reported by each entity, for example, AC ID #1, AC supporting ACR method #1 and ACR method #2, eec #1 supporting ACR method #2 and ACR method #3, EES supporting ACR method #1 and ACR method #2, eas supporting ACR method #2 and ACR method #3, the EES may set the ACR method of the application corresponding to the AC ID #1 as ACR method #2, and the remaining entities perform steps required for correlation in the ACR flow (subsequent steps may be called by the related entities to be performed).

If the ACR methods supported by the respective entities are violated and collided, when the ACR mode information is issued, failure indication information may be returned, and the failure indication information carries the failure reason that the ACR methods supported by the respective entities are violated and collided, or further includes information (e.g., updated second information, updated fifth information, etc.) re-reported by the respective entities.

In case five shown in fig. 12, after acquiring the ACR mode information, the EES may send the ACR mode information to the EAS and/or the EEC, and the method flow shown in fig. 12 further includes:

in step 1281, the ees transmits ACR mode information to the EAS.

In step 1282, the ees sends ACR mode information to the EEC.

In the cases shown in the first to fifth cases shown in fig. 12, after the EEC acquires the ACR mode information, the EEC may send the ACR mode information to the AC, and the method flow shown in fig. 12 further includes:

in step 1283, the eec sends ACR mode information to the AC.

The condition information included by the above-described known ACR pattern information may be used to indicate a fourth condition, and when the fourth condition is satisfied, the EES performs an ACR flow for a fourth application of the at least one application. The method flow shown in fig. 12 may further include:

in step 1290, the ees executes an ACR flow for a fourth application of the at least one application.

Illustratively, when the EES determines that the fourth condition is satisfied (e.g., the ACR information indicates that the ACR triggering event is UE movement, the functional entity performing ACR is the EES; further, for example, when the ACR mode information indicates that the application identification is AC ID #4, the method of performing ACR is that the ecc performs ACR through S-EES), the EES performs an ACR procedure for a fourth application of the at least one application (e.g., the ACR procedure for the fourth application is the ACR procedure when the ACR triggering event is UE movement).

Specifically, the determination of whether the fourth condition is met by the EES may be that the EES monitors an application type to which an application that needs to perform context migration belongs, or an event type that triggers the context migration, or monitors an identifier of the application that needs to perform context migration.

Illustratively, the EES performs the ACR procedure in accordance with the selected ACR method.

Illustratively, the EES executes the ACR procedure according to the ACR method corresponding to the AC ID, and/or executes the ACR method corresponding to the AC ID, and further executes the related steps in the ACR method.

Specifically, it can be seen from fig. 13 that the EAS acquisition ACR mode information includes the following cases:

case one, the EAS receives ACR mode information from the EES. The method comprises the following steps:

in step 1310, the eas receives ACR pattern information from the EES.

In the second case, the EAS acquires ACR mode information from an EAS configuration file (EAS profile) in the EAS; or EAS, determines ACR pattern information from the EAS profile.

For example, the EAS profile is preconfigured with ACR mode information.

As a possible implementation manner, the EAS profile is pre-configured with the ACR mode information, which is formulated by the EAS according to the reported information of each entity. Specifically, the method comprises the following steps:

at step S1321, the EAS receives the third information from the AC.

The specific third information sending process in this embodiment includes:

AC to EEC (e.g., via EDGE-5 interface); EEC to EES (e.g., EDGE-1 related procedures such as registration through EAS discovery EEC, EAS discovery subscription, etc.); EES to EAS (e.g., EAS registration (update) 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 identity API response message, notification message, qoS session creation response message, notification message, ACR management event response message, notification message, etc., EDGE-3 related subscription-corresponding response message).

At step S1322, the EAS receives the first information from the EEC.

Wherein, the ACR capability information supported by the EEC indicates an ACR trigger event or an application type corresponding to an ACR procedure that the EEC can execute (or detect), or an ACR event that the EEC can detect, or an application that the EEC can detect an ACR occurs, or an ACR method supported or preferred by the EEC, or a priority of the ACR method corresponding to each AC ID;

the first ACR method request information (referred to as request ACR method, or referred to as request ACR scenario) is used to request allocation of an ACR method, and may allocate an ACR method 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 allocate an ACR method or suggest an ACR method for the EEC for a required AC request.

The specific first information sending process in this embodiment includes:

EEC to EES (e.g., EDGE-1 related procedures such as registration through EAS discovery EEC, EAS discovery subscription, etc.); EES to EAS (e.g., via an EAS registration (update) 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 identity 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., EDGE-3 related subscription-corresponding response message).

In step S1323, the EAS receives the fifth information from the EES.

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

the second ACR method request information (referred to as request ACR method, or referred to as request ACR discovery) is used to request allocation of an ACR method, an ACR method may be allocated or suggested for EAS for each AC request EES, or AC related information (e.g., AC ID) is carried in the EAS request information, and an ACR method is allocated or suggested for EAS for required AC request EES.

The fifth information specific sending process in this embodiment includes:

an EES-to-EAS (e.g., an EAS registration (update) 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 identity API response message, a notification message, a QoS session creation response message, a notification message, an ACR management event response message, a notification message, and a response message corresponding to an EDGE-3 related subscription, such as an EAS registration (update) response message, an EAS registration update response message, a UE location response message, a notification message, an ACR management response message, a notification message, and the like).

The EAS acquisition of the ACR mode information in case two includes step S1320 shown in fig. 13, the EAS acquires the ACR mode information from an EAS configuration file in the EAS.

It can be understood that the ACR pattern information is predefined in the EAS profile, and the cells that can be included in the EAS profile in case two are shown in table 14 below:

TABLE 14

In the second case shown in fig. 13, after the EAS acquires the ACR mode information, the EAS may send the ACR mode information to the EES, and the method flow shown in fig. 13 further includes:

step 1330, the eas sends ACR pattern information to the EES.

Reference is made to the description of step 1260 shown in fig. 12, which is not repeated here.

After acquiring the ACR mode information, the EES may send the ACR rule information to the EEC, and the method flow shown in fig. 13 further includes:

step 1340, the ees transmits ACR mode information to the EEC.

In step 1350, the eec sends ACR mode information to the AC.

The condition information included by the above-described known ACR mode information may be used to indicate a third condition, and when the third condition is satisfied, the EAS performs an ACR procedure for a third application of the at least one application. The method flow shown in fig. 13 may further include:

in step 1360, the eas executes an ACR flow for a third application of the at least one application.

In particular, the EAS determining whether the fourth condition is satisfied may be the EAS monitoring a type of application to which the application requiring context migration belongs or a type of event triggering the context migration or an identification of the application requiring context migration.

Illustratively, the EAS executes the ACR procedure of the third application according to an ACR method corresponding to an identification (AC ID) of the third application, and/or executes the ACR method corresponding to the third application, further executing the related steps in the ACR method described above.

The present application also considers the case where the ACR method for one AC does not match: for example, the negotiation of the ACR method in the above-described embodiments shown in fig. 11 to 13 is not performed, or the negotiation of the ACR method described above is performed but an error occurs in the negotiation. Further, the present application provides a method for migrating a context, specifically including the following steps:

the method comprises the following steps: the EEC initiates an ACR flow. The EEC initiated ACR flow specifically corresponds to the EEC using conventional EAS Discovery (initialization by EEC using standardized EAS Discovery) (in the manner shown in fig. 2), the EEC performing ACR (EEC executed ACR via S-EES) (in the manner shown in fig. 5) through S-EES, and the EEC performing ACR (EEC executed ACR via T-EES) (in the manner shown in fig. 6).

Step two: the EEC sends a first message to the EES. The first message includes the AC ID, and/or the EEC ID.

Optionally, the first message is an ACR request message.

Illustratively, in three ACR scenarios initiated by the EEC, after the T-EAS discovery and before applying the context transfer, the EEC sends an ACR request message to the EES and carries the AC ID, and/or the EEC ID.

It should be understood that, in step one, the EEC initiates the ACR corresponding to the AC ID and/or the EEC ID, that is, the ACR of the AC.

After the EEC receives the first message, the steps to be performed include the following two cases:

the first condition is as follows: the following third and fourth steps are performed.

Step three: the EES receives the first message and determines whether the EES side has initiated the ACR procedure.

Specifically, in response to receiving the first information, the EES determines whether the EES side has initiated an ACR procedure corresponding to the AC ID and/or the EEC ID.

Step four: the EES sends a second message to the EEC.

The second message includes indication information, and the indication information is used for indicating success or failure.

Optionally, the second message is an ACR response message.

As a possible implementation manner, if the EES determines that the EES does not initiate application context migration for the AC, the EES returns an ACR response message to the EEC and carries success indication information.

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

The reason for the failure specifically indicates that the ACR method does not match (or is called as inconsistent, conflicting, etc.), or the ACR method on the EEC side does not match with the ACR method on the EES side, or the ACR method performs ACR for the EES (S-EES executed ACR). The ACR response message may also carry an AC ID. The ACR response message may specifically indicate that the ACR method of the AC does not match (or is called as inconsistent, conflicting, etc.), or the ACR method on the EEC side of the AC does not match the ACR method on the EES side, or the ACR method determined by the EES side for the AC performs ACR for the EES (S-EES executed ACR), and so on.

Case two: the following steps five and six are performed.

Step five: the EES receives the first message and determines whether the EAS side has initiated an ACR procedure.

Specifically, in response to receiving the first information, the EES determines whether the EAS side has initiated an ACR procedure corresponding to the AC ID and/or the EEC ID.

Step six: the EES sends a second message to the EEC.

Optionally, the second message is an ACR response message.

As a possible implementation manner, if the EES determines that the EAS has not initiated application context migration for the AC, the EES returns an ACR response message to the EEC and carries successful indication information.

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

The reason for the failure specifically indicates that the ACR method does not match (or is called as inconsistent, conflicting, etc.), or the ACR method on the EEC side does not match with the ACR method on the EES side, or the ACR method is an ACR method for EAS executing ACR (S-EAS determined ACR security).

The ACR response message may also carry an AC ID. The ACR response message may specifically further indicate that the ACR method of the AC does not match (or is called as inconsistent, conflicting, etc.), or the ACR method of the EEC side of the AC does not match the ACR method of the EAS side, or the ACR method determined by the EES side for the AC is the ACR method of the EAS execution ACR (S-EAS determined ACR scientific), etc.

As another possible implementation manner, the EES may indicate that an ACR fails in an ACR information subscription response or an ACR information notification message, for example, the ACR information subscription response or the ACR information notification message carries indication information of the ACR failure, and/or a reason of the failure.

The message in the ACR information subscription response or ACR information notification message may also carry an AC ID. The ACR information subscription response or the ACR information notification message may specifically indicate that the ACR methods of the AC do not match (or are called as inconsistent, conflicting, etc.), or the ACR method on the EEC side of the AC does not match the ACR method on the EAS side, or the ACR method determined by the EES side for the AC is an ACR method for EAS execution ACR (S-EAS determined ACR security), and so on.

In the method embodiment, the sequence number of each process does not mean the execution sequence, and the execution sequence of each process should be determined by the function and the internal logic of the process, and should not limit the implementation process of the embodiment of the present application. And possibly not all operations in the above method embodiments.

It should be understood that each functional entity in the above method embodiments may perform part or all of the steps in the embodiments, and these steps or operations are merely examples, and the embodiments of the present application may also include performing other operations or variations of various operations.

It is understood that in the above method embodiments, the method implemented by AC, EEC, EAS, EES, or ECS may also be implemented by a component (e.g., a chip or a circuit, etc.) that is available for AC, EEC, EAS, EES, or ECS.

It is also to be understood that the terminology and/or the description of different embodiments may be in the nature of words and/or phrases and may be referred to one another or any other embodiment herein without specifically indicating or implying any logical conflict between such embodiments, wherein technical features of different embodiments may be combined to form new embodiments based on their inherent logical relationships.

The method for migrating contexts in the embodiment of the present application is described in detail above with reference to fig. 10 to 13, and the apparatus for migrating contexts provided in the embodiment of the present application is described in detail below with reference to fig. 14 to 23.

Referring to fig. 14, fig. 14 is a schematic diagram of an apparatus 1400 for migrating a context provided by the present application. As shown in fig. 14, the apparatus 1400 includes a processing unit 1410, an obtaining unit 1420, and a transmitting unit 1430.

An obtaining unit 1420, configured to obtain application context migration ACR mode information;

a processing unit 1410 for determining an ACR method selected for at least one application according to the ACR mode information.

Illustratively, the acquiring unit 1420 acquires the ACR mode information includes:

the acquisition unit 1420 receives the ACR pattern information from the application client AC; or,

the acquisition unit 1420 receives the ACR pattern information from the edge-enabling server EES and/or the edge-configuring server ECS.

Illustratively, when the acquiring unit 1420 receives the ACR pattern information from the AC, the apparatus 1400 further comprises:

a sending unit 1430, configured to send the ACR pattern information to an edge-enabled server EES;

when the acquiring unit 1420 receives the ACR mode information from the EES and/or the ECS, the apparatus 1400 further includes:

a transmitting unit 1430 configured to transmit the ACR mode information to the AC.

The apparatus 1400 corresponds to the EEC in the method embodiment. The apparatus 1400 may be the EEC in the method embodiment, or a chip or a functional block inside the EEC in the method embodiment. The corresponding units of the device 1400 are used to execute the corresponding steps performed by the EEC in the method embodiments shown in fig. 10 to 13.

Processing unit 1410 in apparatus 1400 is configured to perform steps related to processing corresponding to the EEC in the method embodiment. An acquisition unit 1420 in the apparatus 1400 performs the steps of EEC acquisition in the method embodiment. A sending unit 1430 in the apparatus 1400 for performing the step of EEC sending.

The acquiring unit 1420 and the transmitting unit may constitute a transceiving unit, and have both acquiring and transmitting functions. Wherein processing unit 1410 can be at least one processor. The transmitting unit 1430 may be a transmitter or an interface circuit, and the acquiring unit 1420 may be a receiver or an interface circuit. The receiver and transmitter may be integrated together to form a transceiver or interface circuit.

Optionally, the apparatus 1400 may further include a storage unit, and the processing unit 1410, the obtaining unit 1420, and the sending unit 1430 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 as to enable the method of the foregoing embodiment to be performed.

The above units may exist independently, or may be wholly or partially integrated.

Referring to fig. 15, fig. 15 is a schematic structural diagram of an EEC 1500 suitable for use in the embodiment of the present application, which may be used to implement the functions of the EEC.

The EEC 1500 includes a processor 1501, a memory 1502 and a transceiver 1503, wherein the memory 1502 stores instructions or programs, and the processor 1502 and the transceiver 1503 are configured to execute or call the instructions or programs stored in the memory 1502, so that the EEC 1500 implements the functions of the EEC in the method for migrating contexts. When the instructions or programs stored in the memory 1502 are executed, the transceiver 1503 is configured to perform the operations performed by the sending unit 1430 and the obtaining unit 1420 in the embodiment shown in fig. 14, and the processor 1502 is configured to perform the operations performed by the processing unit 1410 in the embodiment shown in fig. 14.

Those skilled in the art will appreciate that fig. 15 shows only one memory and processor for ease of illustration. In an actual user equipment, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, and the like, which is not limited in this application.

Referring to fig. 16, fig. 16 is a schematic diagram of an apparatus 1600 for migrating contexts provided herein. As shown in fig. 16, the apparatus 1600 includes a processing unit 1610, an obtaining unit 1620, and a transmitting unit 1630.

An obtaining unit 1620 configured to obtain application context migration ACR mode information, where the ACR mode information is used to determine at least one ACR method selected by an application;

a transmitting unit 1630, configured to transmit the ACR mode information to an edge application service EAS.

The ACR mode information includes ACR rule information including condition information triggering an ACR procedure of at least one application;

a processing unit 1610, configured to perform an ACR procedure for a fourth application of the at least one application when a fourth condition indicated by the condition information is satisfied.

Illustratively, the acquiring unit 1620 acquires the ACR mode information includes:

the acquisition unit 1620 acquires the ACR pattern information according to at least one of the following information:

ACR capability information supported by an edge application server EAS, ACR capability information supported by an EEC, ACR capability information supported by an application client AC, and ACR capability information supported by the device; or,

the acquiring unit 1620 acquires the ACR mode information from a configuration file of the device 1600, wherein the configuration file of the device 1600 includes the ACR mode information; or,

the acquiring unit 1620 receives the ACR mode information from the ECS; or,

the acquisition unit 1620 receives the ACR mode information from the edge application server EAS and/or the EEC.

Illustratively, the apparatus further comprises:

a transmitting unit 1630, configured to transmit the ACR mode information to the EAS and/or the EEC.

The apparatus 1600 corresponds to the EES in the method embodiment. The apparatus 1600 may be an EES in a method embodiment, or a chip or functional block within an EES in a method embodiment. The corresponding units of the apparatus 1600 are used to perform the corresponding steps performed by the EES in the method embodiments shown in fig. 10 to 13.

The processing unit 1610 in the apparatus 1600 is configured to execute steps related to the EES correspondence in the method embodiment. The acquisition unit 1620 in the apparatus 1600 performs the steps of EES acquisition in the method embodiment. A transmitting unit 1630 in the apparatus 1600, configured to perform the step of EES transmitting.

The acquiring unit 1620 and the transmitting unit may constitute a transceiving unit, and have both acquiring and transmitting functions. The processing unit 1610 may be at least one processor, among others. 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 transmitter may be integrated together to form a transceiver or interface circuit.

Optionally, the apparatus 1600 may further include a storage unit, and 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 method of the foregoing embodiment is executed.

The above units may exist independently, or may be integrated wholly or partially.

Referring to fig. 17, fig. 17 is a schematic structural diagram of an EES 1700 suitable for the embodiment of the present application, and may be used to implement the functions of the EES.

The EES 1700 includes a processor 1701, a memory 1702 and a transceiver 1703, wherein the memory 1702 stores instructions or programs therein, and the processor 1702 and the transceiver 1703 are used for executing or calling the instructions or programs stored in the memory 1702, so that the EES 1700 implements the functions of the EES in the method for migrating contexts. When the instructions or programs stored in the memory 1702 are executed, the transceiver 1703 is configured to perform the operations performed by the sending unit 1630 and the obtaining unit 1620 in the embodiment shown in fig. 16, and the processor 1702 is configured to perform the operations performed by the processing unit 1610 in the embodiment shown in fig. 16.

Those skilled in the art will appreciate that fig. 17 shows only one memory and processor for ease of illustration. In an actual user equipment, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, and the like, which is not limited in this application.

Referring to fig. 18, fig. 18 is a schematic diagram of an apparatus 1800 for migrating contexts provided in the present application. As shown in fig. 18, the apparatus 1800 includes a processing unit 1810, an obtaining unit 1820, and a sending unit 1830.

An obtaining unit 1820, configured to obtain application context migration ACR mode information, where the ACR mode information includes condition information for triggering an ACR procedure of at least one application;

a processing unit 1810, configured to, when a second condition indicated by the condition information is satisfied, execute, by the AC, an ACR procedure for a second application of the at least one application.

Illustratively, the acquiring unit 1820 acquires the ACR pattern information includes:

the acquiring unit 1820 acquires the ACR mode information from a profile of the device 1800, the profile of the device 1800 including the ACR mode information; or,

the acquisition unit 1820 receives the ACR pattern information from the edge-enabled client EEC.

Illustratively, when the acquiring unit acquires the ACR mode information from the profile of the apparatus 1800, the apparatus further includes:

a transmitting unit 1830, configured to transmit the ACR pattern information to the EEC.

The apparatus 1800 corresponds to the AC in the method embodiments. The apparatus 1800 may be an AC in a method embodiment, or a chip or functional block within an AC in a method embodiment. Corresponding elements of the apparatus 1800 are adapted to carry out the corresponding steps performed by the AC in the method embodiments shown in fig. 10 to 13.

The processing unit 1810 of the apparatus 1800 is configured to perform the steps related to AC mapping and processing in the method embodiment. An acquisition unit 1820 in the apparatus 1800 performs the steps of AC acquisition in the method embodiments. A sending unit 1830 in the apparatus 1800, configured to perform the step of AC sending.

The obtaining unit 1820 and the transmitting unit may constitute a transceiving unit, and have both obtaining and transmitting functions. The processing unit 1810 may be at least one processor, among others. The transmitting unit 1830 may be a transmitter or an interface circuit, and the obtaining unit 1820 may be a receiver or an interface circuit. The receiver and transmitter may be integrated together to form a transceiver or interface circuit.

Optionally, the apparatus 1800 may further include a storage unit, and the processing unit 1810, the obtaining unit 1820, and the sending unit 1830 may interact with or be coupled to the storage unit, for example, to read or call the data and/or the signaling in the storage unit, so as to implement the method of the foregoing embodiments.

Referring to fig. 19, fig. 19 is a schematic structural diagram of an AC 1900 suitable for the embodiment of the present application, which may be used to implement the functions of the AC.

The AC 1900 includes a processor 1901, a memory 1902 and a transceiver 1903, wherein the memory 1902 stores therein instructions or programs, and the processor 1902 and the transceiver 1903 are configured to execute or call the instructions or programs stored in the memory 1902, so that the AC 1900 implements the functions of the AC in the method for migrating contexts. When the instructions or programs stored in the memory 1902 are executed, the transceiver 1903 is configured to perform the operations performed by the sending unit 1830 and the obtaining unit 1820 in the embodiment shown in fig. 18, and the processor 1902 is configured to perform the operations performed by the processing unit 1810 in the embodiment shown in fig. 18.

Those skilled in the art will appreciate that fig. 19 shows only one memory and processor for ease of illustration. In an actual user equipment, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, and the like, which is not limited in this application.

Referring to fig. 20, fig. 20 is a schematic diagram of an apparatus 2000 for migrating a context provided by the present application. As shown in fig. 20, the apparatus 2000 includes a processing unit 2010, an obtaining unit 2020, and a sending unit 2030.

An acquisition unit 2020 that acquires application context migration ACR mode information including condition information that triggers an ACR flow of at least one application;

a processing unit 2010, configured to execute an ACR procedure for a third application of the at least one application by the EAS when a third condition indicated by the condition information is satisfied.

Illustratively, the obtaining unit 2020 obtaining the EASR rule information includes:

the acquisition unit 2020 acquires the ACR mode information from a profile of the device 2000, the profile of the device 2000 including the ACR mode information; or,

the acquisition unit 2020 receives the ACR mode information from the edge-enable server EES.

Illustratively, when the acquisition unit 2020 acquires the ACR pattern information from a profile of the device 2000, the device further includes:

a sending unit 2030, configured to send the ACR mode information to the EES.

The device 2000 corresponds to EAS in the method embodiments. The device 2000 may be an EAS in a method embodiment, or a chip or functional module internal to an EAS in a method embodiment. The corresponding elements of apparatus 2000 are adapted to perform the corresponding steps performed by EAS in the method embodiments shown in fig. 10-13.

Processing unit 2010 of apparatus 2000 is configured to perform, among other things, EAS-related and process-related steps of the method embodiments. Acquisition unit 2020 in device 2000 performs the steps of EAS acquisition in method embodiments. A transmitting unit 2030 in the apparatus 2000 is configured to perform the step of EAS transmission.

The acquiring unit 2020 and the transmitting unit may constitute a transceiving unit, and have both acquiring and transmitting functions. Processing unit 2010 may be at least one processor, among others. The sending unit 2030 may be a transmitter or an interface circuit, and the obtaining unit 2020 may be a receiver or an interface circuit. The receiver and transmitter may be integrated together to form a transceiver or interface circuit.

Optionally, the apparatus 2000 may further include a storage unit, and 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 as to enable the method of the above-described embodiment to be performed.

Referring to fig. 21, fig. 21 is a schematic structural diagram of an EAS 2100 suitable for use in embodiments of the present application and may be used to implement the EAS functionality described above.

The EAS 2100 comprises a processor 2101, a memory 2102 and a transceiver 2103, wherein the memory 2102 stores instructions or programs therein, and the processor 2102 and the transceiver 2103 are configured to execute or invoke the instructions or programs stored in the memory 2102, so that the EAS 2100 implements the functions of the EAS in the above-described method for migrating contexts. When the instructions or programs stored in the memory 2102 are executed, the transceiver 2103 is configured to perform the operations performed by the transmitting unit 2030 and the obtaining unit 2020 in the embodiment shown in fig. 20, and the processor 2102 is configured to perform the operations performed by the processing unit 2010 in the embodiment shown in fig. 20.

Those skilled in the art will appreciate that fig. 21 shows only one memory and processor for the sake of illustration. In an actual user equipment, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, and the like, which is not limited in this application.

Referring to fig. 22, fig. 22 is a schematic diagram of an apparatus 2200 for migrating contexts provided in this application. As shown in fig. 22, the apparatus 2200 includes a processing unit 2210 and a transmitting unit 2220.

A processing unit 2210, configured to formulate application context migration ACR mode information, where the ACR mode information includes condition information for triggering an ACR procedure of at least one application;

a sending unit 2220, configured to send the ACR mode information to the EEC and the EES, respectively.

The apparatus 2200 corresponds to the ECS in the method embodiment. The apparatus 2200 may be the ECS in the method embodiment, or a chip or functional module inside the ECS in the method embodiment. The corresponding elements of apparatus 2200 are for performing the corresponding steps performed by the ECS in the method embodiments shown in fig. 10-13.

The processing unit 2210 in the apparatus 2200 is configured to perform the steps related to the ECS mapping in the method embodiment. A sending unit 2220 in the apparatus 2200, configured to execute the step of ECS sending.

Optionally, the apparatus 2200 may further include a storage unit, and the storage unit is configured to store data and/or signaling, and 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 as to execute the method of the foregoing embodiment.

Referring to fig. 23, fig. 23 is a schematic diagram of a structure of an ECS 2300 suitable for use in embodiments of the present application, which may be used to implement the functions of the ECS described above.

The ECS 2300 includes a processor 2301, a memory 2302, and a transceiver 2303, wherein the memory 2302 stores instructions or programs therein, and the processor 2302 and the transceiver 2303 are configured to execute or call the instructions or programs stored in the memory 2302 to enable the ECS 2300 to implement the functions of the ECS in the method for migrating contexts. When the instructions or programs stored in the memory 2302 are executed, the transceiver 2303 is configured to perform the operations performed by the transmission unit 2220 in the embodiment shown in fig. 22, and the processor 2302 is configured to perform the operations performed by the processing unit 2210 in the embodiment shown in fig. 22.

Those skilled in the art will appreciate that fig. 23 shows only one memory and processor for the sake of illustration. In an actual user equipment, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, and the like, which is not limited in this application.

Embodiments of the present application also provide a communication system, which includes the aforesaid EEC, EES, AC, EAS and ECS.

The embodiment of the present application further provides a user equipment, which includes the foregoing EEC and AC.

The present application also provides a computer-readable storage medium having stored therein instructions which, when executed on a computer, cause the computer to perform the steps performed by the EEC, EES, AC, EAS, or ECS of the above-described method as shown in fig. 10-13.

The present application also provides a computer program product containing instructions which, when run on a computer, cause the computer to perform the steps performed by the EEC, EES, AC, EAS or ECS in the method shown in figures 10 to 13.

The application also provides a chip comprising a processor. The processor is configured to read and execute the computer program stored in the memory to perform the corresponding operations and/or processes performed by the EEC, the EES, the AC, the EAS or the ECS in the method for migrating contexts provided in the present application, as shown in fig. 10 to 13. In a possible implementation, the chip further comprises a memory, the memory is connected with the processor through a circuit or a wire, and the processor is used for reading and executing 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 used for receiving the processed data and/or information, and the processor acquires 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, interface circuit, output circuit, input circuit, pin or related circuit on the chip, etc. The processor may also be embodied as a processing circuit or a logic circuit.

The chip can be replaced by a chip system, which is not described herein again.

The terms "comprises," "comprising," and "having," and any variations thereof, in this application are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual conditions to achieve the purpose of the scheme of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions may be stored in a computer-readable storage medium if they are implemented in the form of software functional units and sold or used as separate products. Based on such understanding, the technical solutions of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product, which 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) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a portable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, an optical disk, or other various media capable of storing program codes.

In addition, the term "and/or" in the present application is only one kind of association relationship describing the associated object, and means that three kinds of relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter associated objects are in an "or" relationship; the term "at least one" in this application may mean "one" and "two or more", e.g. at least one of a, B and C may mean: a exists alone, B exists alone, C exists alone, A and B exist together, A and C exist together, C and B exist together, A and B exist together, and A, B and C exist together, which are seven cases.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for migrating contexts, comprising:

acquiring application context migration ACR mode information;

determining at least one ACR method selected by an application according to the ACR mode information.

2. The method of claim 1, wherein the ACR mode information comprises ACR rule information, the ACR rule information comprising condition information for triggering at least one applied ACR procedure;

when a first condition indicated by the condition information is satisfied, executing an ACR flow for a first application of the at least one application;

the condition information further indicates at least one of the following conditions:

a second condition, a third condition, and a fourth condition,

wherein the second condition, when satisfied, instructs the application client AC to perform an ACR flow for a second application of the at least one application; instructing an edge application server EAS to execute an ACR flow for a third application of the at least one application when the third condition is satisfied; when the fourth condition is satisfied, instructing the edge-enabled server EES to execute an ACR flow for a fourth application of the at least one application.

3. The method of claim 2, wherein the ACR rule information comprises:

a correspondence between an application type and a device that executes an ACR flow of an application belonging to the application type, and/or a correspondence between event information that triggers the flow of the ACR and a device that executes the flow of the preset ACR.

4. The method of claim 1, wherein the ACR mode information indicates an identity of an application client and an ACR method determined by a server for the application client,

5. The method according to any of claims 1-4, wherein the obtaining the ACR mode information comprises:

receiving the ACR mode information from an application client AC; or,

receiving the ACR mode information from an edge-enabled server EES and/or an edge configuration server ECS.

6. The method of claim 5, wherein the receiving the ACR mode information from the AC further comprises:

and sending the ACR mode information to an edge enabling server EES.

7. The method of claim 5, wherein the receiving the ACR mode information from the EES and/or the ECS, the method further comprises:

transmitting the ACR mode information to the AC.

8. The method according to any of claims 1-7, wherein prior to the obtaining the ACR mode information, the method further comprises:

sending first information to an edge-enabled server EES or an edge configuration server ECS, the first information indicating at least one of:

the method comprises the steps of applying ACR capacity information supported by a client AC, enabling the ACR capacity information supported by an EEC of an edge-enabled client, requesting to distribute ACR methods for the AC and requesting to distribute ACR methods for the EEC.

9. A method for migrating contexts, comprising:

an Edge Enabling Server (EES) acquires application context migration (ACR) mode information, wherein the ACR mode information is used for determining an ACR method selected by at least one application;

the EES transmits the ACR mode information to an edge application service EAS.

10. The method of claim 9, further comprising:

and the EES sends the ACR mode information to an edge enabling client EEC.

11. The method according to claim 9 or 10, wherein the ACR mode information includes ACR rule information, the ACR rule information including condition information that triggers at least one applied ACR procedure;

when a fourth condition indicated by the condition information is satisfied, the EES performs an ACR flow for a fourth application of the at least one application.

12. The method of claim 11, wherein the ACR rule information comprises:

13. The method according to claim 9 or 10, wherein the ACR mode information indicates an identity of an application client and an ACR method determined by a server for the application client,

14. The method according to any of claims 9 to 13, wherein the EES acquiring the ACR mode information comprises:

the EES acquires the ACR mode information according to at least one of the following information:

ACR capability information supported by an Edge Application Server (EAS), ACR capability information supported by an edge-enabled client (EEC), ACR capability information supported by an Application Client (AC) or ACR capability information supported by the EES; or,

the EES acquires the ACR mode information from a configuration file of the EES, wherein the configuration file of the EES comprises the ACR mode information; or,

the EES receives the ACR mode information from the ECS.

15. The method of claim 14, further comprising:

the EES transmits the ACR mode information to the EAS and/or the EEC.

16. The method of claim 14, wherein the EES obtaining the ACR mode information comprises:

the EES receives the ACR pattern information from the edge application servers EAS and/or EEC.

17. An apparatus for migrating contexts, comprising:

an acquisition unit configured to acquire application context migration ACR mode information;

a processing unit for determining at least one ACR method selected by an application according to the ACR mode information.

18. An apparatus according to claim 17, wherein the ACR mode information comprises ACR rule information, the ACR rule information comprising condition information that triggers at least one applied ACR procedure;

the processing unit is further used for executing an ACR flow aiming at a first application in the at least one application when a first condition indicated by the condition information is met;

a second condition, a third condition, and a fourth condition,

wherein the second condition, when satisfied, instructs the AC to perform an ACR flow for a second application of the at least one application; when the third condition is satisfied, instructing an edge application server EAS to perform an ACR flow for a third application of the at least one application; when the fourth condition is satisfied, instructing the edge-enabled server EES to execute an ACR flow for a fourth application of the at least one application.

19. The apparatus of claim 18, wherein the ACR rule information comprises:

a correspondence between an application type and a device that performs an ACR flow of an application belonging to the application type, and/or a correspondence between event information that triggers a flow of an ACR and a device that performs a flow of the preset ACR.

20. The apparatus of claim 17, wherein the ACR mode information indicates an identity of an application client and an ACR method determined by a server for the application client,

21. The apparatus according to any one of claims 17 to 20, wherein the acquiring unit acquires the ACR mode information comprises:

the acquisition unit receives the ACR mode information from an application client AC; or,

the acquisition unit receives the ACR mode information from an edge-enabling server EES and/or an edge-configuration server ECS.

22. The apparatus of claim 21, wherein the acquisition unit receives the ACR mode information from the AC, and wherein the apparatus further comprises:

a sending unit, configured to send the ACR pattern information to an edge-enabled server EES.

23. The apparatus according to claim 21, wherein the acquiring unit receives the ACR mode information from the EES and/or the ECS, the apparatus further comprising:

a transmitting unit configured to transmit the ACR mode information to the AC.

24. The apparatus according to any of claims 17 to 23, wherein before the acquisition unit acquires the ACR mode information, the apparatus further comprises:

a sending unit, configured to send first information to an edge-enabling server EES or an edge-configuration server ECS, where the first information is used to indicate at least one of the following:

the method comprises the steps of applying ACR capability information supported by a client AC, enabling the ACR capability information supported by an EEC of an edge-enabled client, requesting to distribute an ACR method for the AC, and requesting to distribute the ACR method for the EEC.

25. An apparatus for migrating contexts, comprising:

an acquiring unit, configured to acquire application context migration ACR mode information, where the ACR mode information is used to determine an ACR method selected by at least one application;

a sending unit, configured to send the ACR mode information to an edge application service EAS.

26. The apparatus of claim 25, wherein the sending unit is further configured to send the ACR mode information to an edge-enabled client EEC.

27. The apparatus according to claim 25 or 26, wherein the ACR mode information comprises ACR rule information, the ACR rule information comprising condition information that triggers at least one applied ACR procedure;

a processing unit configured to perform an ACR procedure for a fourth application among the at least one application when a fourth condition indicated by the condition information is satisfied,

the second condition, the third condition, and the first condition,

wherein the second condition, when satisfied, instructs the AC to perform ACR procedures for a second application of the at least one application; when the third condition is satisfied, instructing the EAS to perform an ACR procedure for a third application of the at least one application; when the first condition is satisfied, instructing the EEC to execute an ACR procedure for a first application of the at least one application.

28. The apparatus of claim 27, wherein the ACR rule information comprises:

29. The apparatus of claim 25 or 26, wherein the ACR rule information indicates an identity of an application client and an ACR method determined by a server for the application client,

30. The apparatus according to any of claims 25 to 29, wherein the acquiring unit acquires the ACR mode information comprises:

the acquisition unit acquires the ACR mode information according to at least one of the following information:

ACR capability information supported by an edge application server EAS, ACR capability information supported by an edge-enabled client EEC, ACR capability information supported by an application client AC, and ACR capability information supported by the device; or,

the acquisition unit acquires the ACR mode information from a configuration file of the device, wherein the configuration file of the device comprises the ACR mode information; or,

the acquisition unit receives the ACR mode information from the ECS.

31. The apparatus of claim 30, further comprising:

a sending unit, configured to send the ACR mode information to the EAS and/or the EEC.

32. The apparatus according to claim 30, wherein the acquiring unit acquires the ACR mode information comprises:

the acquisition unit receives the ACR pattern information from an edge application server EAS and/or the EEC.

33. A computer-readable storage medium, having stored thereon a computer program which, when run, causes an apparatus to perform the method of any of claims 1-8 or causes an apparatus to perform the method of any of claims 9-16.

34. A chip system, comprising: a processor for calling and running a computer program from a memory so that a communication device in which the system-on-chip is installed performs the method of any one of claims 1 to 8; or causing a communication device in which the system-on-chip is installed to perform the method of any one of claims 9 to 16.

35. A communications apparatus, comprising:

a memory for storing a computer program;

a processor for executing a computer program stored in the memory to cause the communication device to perform the method of any of claims 1 to 8 or to cause the communication device to perform the method of any of claims 9 to 16.

36. A communication system, characterized in that it comprises at least one means for migrating contexts according to any one of claims 17 to 24 and at least one means for migrating contexts according to any one of claims 25 to 32.