A method and apparatus for migrating application context

Abstract

A method and apparatus for migrating application context, so as to delegate the migration of application context to edge enabler function entity, and the edge enabler function entity can make a decision on migrating the application context by itself, reduce signaling interaction, and shorten the latency of migrating the application context. The method comprises: receiving first information from an application function entity, the first information being used to indicate migration of application context associated with the application function entity (S201); and determining to migrate the application context according to the first information when a trigger event of migrating the application context occurs (S202).

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method and apparatus for transferring application context. Background Technology

[0002] In a multi-access edge computing (MEC) architecture, network services are provided to user equipment (UE) via an edge data network (EDN). Specifically, an edge application server (EAS) is deployed on the EDN, providing services to the application client (AC) on the UE side. An edge enabler server (EES) is deployed on the EDN to manage the EAS, and an edge enabler client (EEC) is also deployed on the UE side. The EEC manages the AC and can transmit AC information to the EES.

[0003] During the operation of edge applications, there may be instances where the UE with the AC deployed moves. When the UE moves outside the current service area, the EAS currently providing the service may not be able to continue providing services to the AC currently running on the moved UE. In this case, it is necessary to migrate the application context related to the EAS currently providing the service.

[0004] Currently, when an EEC or EES detects the need for application context migration, it typically relies on the MEC architecture's communication methods and discovery mechanisms to determine the target EAS for the application context migration and notify the currently serving EAS to perform the migration. This approach involves numerous signaling interactions, resulting in long latency and impacting application operation. Summary of the Invention

[0005] This application provides an application context migration method and apparatus, which aims to reduce signaling interactions and shorten the latency of application context migration by delegating the migration of application context to edge enabling functional entities such as EEC / EES.

[0006] In a first aspect, embodiments of this application provide an application context migration method, the method comprising: receiving first information from an application functional entity, the first information being used to indicate the migration of the application context associated with the application functional entity; and when a triggering event for the migration of the application context occurs, determining to migrate the application context based on the first information.

[0007] In this embodiment, the application function entity entrusts the migration of its associated application context to the edge enabling function entity. When the edge enabling function entity detects that the application context needs to be migrated, it can make its own decision to migrate the application context. This can reduce the signaling interaction of the application context migration, shorten the latency of the application context migration, help the normal operation of the business, and reduce the time when the business operation of the terminal application client is affected or interrupted.

[0008] In an optional implementation, the method further includes: performing one or more of the following operations based on the first information: detecting a trigger event for the migration of the application context; discovering a target application function entity, the target application function entity being used to receive the application context; transmitting the application context to an edge enabling function entity associated with the target application function entity; sending information of the target application function entity to a terminal device associated with the application function entity; and sending information about the migration of the application context to a core network element; wherein the application corresponding to the application function entity is the same as the application corresponding to the target application function entity.

[0009] In one optional implementation, receiving the first information from the application functional entity includes: receiving registration information from the application functional entity, wherein the registration information includes the first information.

[0010] In one alternative implementation, the method further includes: receiving first condition information from an application functional entity, the first condition information indicating a first effective condition of the first information.

[0011] In one optional implementation, the first effective condition includes any one or more of the following: the effective duration of the first information, the effective period of the first information, the application client to which the first information is applied, the migration duration of the application context being less than a preset time threshold, the size of the application context being less than a preset size threshold, or the application functional entity being overloaded.

[0012] In one optional implementation, the method further includes: receiving second condition information from the application functional entity, the second condition information indicating a second effective condition of the first information, the second effective condition being different from the first effective condition.

[0013] In one alternative implementation, the method further includes receiving the application context from the application functional entity.

[0014] In one alternative implementation, before receiving the application context from the application functional entity, the method further includes: sending the storage address of the application context to the application functional entity.

[0015] In one alternative implementation, the application context includes identification information, which is used to uniquely identify the application context.

[0016] Secondly, embodiments of this application provide an application context migration method, comprising: sending first information to an edge enabling function entity, the first information being used to instruct the migration of the application context associated with the application function entity; and receiving response information from the edge enabling function entity in response to the sending of the first information.

[0017] In this embodiment, the edge enabling function entity is responsible for the migration of application contexts. When the edge enabling function entity detects that the application context needs to be migrated, it can make its own decision to migrate the application context. This can reduce the signaling interaction of the application context migration, shorten the latency of the application context migration, help the normal operation of the business, and reduce the time when the business operation of the terminal application client is affected or interrupted.

[0018] In one optional implementation, the first information is further used to instruct the edge enabling function entity to perform one or more of the following operations: detect a trigger event for the migration of the application context; discover a target application function entity, the target application function entity being used to receive the application context; transmit the application context to the edge enabling function entity associated with the target application function entity; send the information of the target application function entity to the terminal device associated with the application function entity; and send the migration information of the application context to the core network element; wherein the application corresponding to the application function entity is the same as the application corresponding to the target application function entity.

[0019] In one optional implementation, sending the first information to the edge enabling function entity includes sending registration information to the edge enabling function entity, wherein the registration information includes the first information.

[0020] In an alternative implementation, the method further includes sending first condition information to the edge enabling function entity, the first condition information indicating a first activation condition of the first information.

[0021] In one optional implementation, the first condition information includes any one or more of the following: the effective duration of the first information, the effective period of the first information, the application client for which the first information is effective, the migration duration of the application context being less than a preset time threshold, the size of the application context being less than a preset size threshold, and the application functional entity being overloaded.

[0022] In one alternative implementation, the method further includes sending second condition information to the edge enabling function entity, the second condition information indicating a second activation condition of the first information, the second activation condition being different from the first activation condition.

[0023] In one alternative implementation, after sending the first information to the edge enabling entity, the method further includes sending the application context to the edge enabling entity.

[0024] In one alternative implementation, before sending the application context to the edge enabling entity, the method further includes: receiving the storage address of the application context from the edge enabling entity; and sending the application context to the edge enabling entity based on the storage address.

[0025] In one alternative implementation, the application context includes identification information, which is used to uniquely identify the application context.

[0026] Thirdly, embodiments of this application provide an application context migration apparatus, the apparatus comprising: a communication module, configured to receive first information from an application function entity, the first information being configured to instruct the migration of an application context associated with the application function entity; and a processing module, configured to determine, based on the first information, to migrate the application context when a triggering event for the migration of the application context occurs.

[0027] In this embodiment, the application function entity entrusts the migration of its associated application context to the edge enabling function entity. When the edge enabling function entity detects that the application context needs to be migrated, it can make its own decision to migrate the application context. This can reduce the signaling interaction of the application context migration, shorten the latency of the application context migration, help the normal operation of the business, and reduce the time when the business operation of the terminal application client is affected or interrupted.

[0028] In an optional implementation, the processing module is further configured to perform one or more of the following operations based on the first information: detect a trigger event for the migration of the application context; discover a target application function entity, the target application function entity being used to receive the application context; transmit the application context to an edge enabling function entity associated with the target application function entity; send information of the target application function entity to a terminal device related to the application function entity; and send the migration information of the application context to a core network element; wherein the application corresponding to the application function entity is the same as the application corresponding to the target application function entity.

[0029] In one optional implementation, the communication module is specifically configured to receive registration information from the application functional entity, the registration information including the first information.

[0030] In one alternative implementation, the communication module is further configured to receive first condition information from an application functional entity, the first condition information being used to indicate a first effective condition for the first information.

[0031] In one optional implementation, the first effective condition includes any one or more of the following: the effective duration of the first information, the effective period of the first information, the application client to which the first information is applied, the migration duration of the application context being less than a preset time threshold, the size of the application context being less than a preset size threshold, or the application functional entity being overloaded.

[0032] In one optional implementation, the communication module is further configured to receive second condition information from the application functional entity, the second condition information being used to indicate a second effective condition of the first information, the second effective condition being different from the first effective condition.

[0033] In one alternative implementation, the communication module is further configured to receive the application context from the application functional entity.

[0034] In one alternative implementation, before receiving the application context from the application functional entity, the communication module is further configured to send the storage address of the application context to the application functional entity.

[0035] In one alternative implementation, the application context includes identification information, which is used to uniquely identify the application context.

[0036] Fourthly, embodiments of this application provide an application context migration apparatus, comprising: a communication module, configured to send first information to an edge enabling function entity, the first information being used to indicate the application context associated with the migration application function entity; and a communication module further configured to receive response information from the edge enabling function entity in response to the sending of the first information.

[0037] In this embodiment, the edge enabling function entity is responsible for the migration of application contexts. When the edge enabling function entity detects that the application context needs to be migrated, it can make its own decision to migrate the application context. This can reduce the signaling interaction of the application context migration, shorten the latency of the application context migration, help the normal operation of the business, and reduce the time when the business operation of the terminal application client is affected or interrupted.

[0038] In one optional implementation, the first information is further used to instruct the edge enabling function entity to perform one or more of the following operations: detect a trigger event for the migration of the application context; discover a target application function entity, the target application function entity being used to receive the application context; transmit the application context to the edge enabling function entity associated with the target application function entity; send the information of the target application function entity to the terminal device associated with the application function entity; and send the migration information of the application context to the core network element; wherein the application corresponding to the application function entity is the same as the application corresponding to the target application function entity.

[0039] In one alternative implementation, the communication module is further configured to send registration information to the edge enable function entity, the registration information including the first information.

[0040] In an alternative implementation, the communication module is further configured to send first condition information to the edge enable function entity, the first condition information being used to indicate a first effective condition of the first information.

[0041] In one optional implementation, the first condition information includes any one or more of the following: the effective duration of the first information, the effective period of the first information, the application client for which the first information is effective, the migration duration of the application context being less than a preset time threshold, the size of the application context being less than a preset size threshold, and the application functional entity being overloaded.

[0042] In one alternative implementation, the communication module is further configured to send second condition information to the edge enable function entity, the second condition information indicating a second effective condition of the first information, the second effective condition being different from the first effective condition.

[0043] In one alternative implementation, after sending the first information to the edge enabling entity, the communication module is further configured to send the application context to the edge enabling entity.

[0044] In one alternative implementation, before sending the application context to the edge enabling entity, the communication module is further configured to receive the storage address of the application context from the edge enabling entity; and send the application context to the edge enabling entity based on the storage address.

[0045] In one alternative implementation, the application context includes identification information, which is used to uniquely identify the application context.

[0046] Fifthly, embodiments of this application provide a communication device, including: a processor and a memory;

[0047] The memory is used to store computer programs;

[0048] The processor is configured to execute a computer program stored in the memory such that the method in any of the optional embodiments of the first to second aspects is performed.

[0049] Sixthly, a communication device includes: a processor and an interface circuit;

[0050] The interface circuit is used to receive code instructions and transmit them to the processor;

[0051] The processor is configured to execute the code instructions such that the method in any of the optional embodiments of any of the first to second aspects described above is performed.

[0052] A seventh aspect is a computer-readable storage medium storing instructions that, when executed, cause a method in any of the optional embodiments of any of the first to third aspects to be performed.

[0053] Eighthly, embodiments of this application provide a computer program product comprising: computer program code, which, when executed, causes the method in any of the optional implementations of any of the first to second aspects to be performed.

[0054] For the technical effects that can be achieved in aspects five through eight above, please refer to the description of the technical effects that can be achieved by the corresponding technical solutions in aspects one through two above, which will not be repeated here. Attached Figure Description

[0055] Figure 1A schematic diagram of an MEC architecture model provided in an embodiment of this application;

[0056] Figure 2 This is one of the schematic diagrams of the application context migration method provided in the embodiments of this application;

[0057] Figure 3 A schematic diagram illustrating the process of EAS registering with EES, provided for an embodiment of this application;

[0058] Figure 4 A schematic diagram illustrating the process of an AC registering with an EEC, provided for an embodiment of this application;

[0059] Figure 5 This application provides a schematic flowchart of a method for EAS to instruct EES to migrate application context.

[0060] Figure 6 This is the second schematic diagram of the application context migration method provided in the embodiments of this application;

[0061] Figure 7 A schematic diagram illustrating the process of EEC registering with EES, provided as an embodiment of this application;

[0062] Figure 8 A schematic diagram illustrating the process of an EEC discovering an EAS via an EES, provided as an embodiment of this application;

[0063] Figure 9 This is a flowchart illustrating a method for synchronizing application contexts, as provided in an embodiment of this application.

[0064] Figure 10 This application provides a schematic flowchart of a method for EAS to instruct EES to migrate application context.

[0065] Figure 11 A structural block diagram of an application context migration device provided in an embodiment of this application;

[0066] Figure 12 This is one of the structural schematic diagrams of a communication device provided in an embodiment of this application;

[0067] Figure 13 This is a second schematic diagram of a communication device provided in an embodiment of this application. Detailed Implementation

[0068] The embodiments of this application can be applied to 4G systems, 5G systems or future mobile communication systems, and specifically to multi-access edge computing (MEC) architectures.

[0069] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0070] like Figure 1 The diagram shows a MEC architecture model, illustrating the edge application server and edge enabling server on the edge data network side, and the application client and edge enabling client on the terminal device side.

[0071] An edge data network (EDN) corresponds to a data network deployed at the edge of the cloud. It can be a local data network (DN) or a local area data network (LADN). An edge data network includes edge-enabled features and can be identified using a data network access identifier (DNAI) and a data network name (DNN), or using a data network name and a data network service area. Alternatively, an edge data network can be understood as a data center deployed locally relative to the central cloud. DNAI can be used to identify an edge data network, and one edge data network can contain multiple local data networks (DNs).

[0072] An edge application server (EAS) refers to a server application deployed in an edge data network. It can also be called an application instance, edge application instance, MEC application (server), or EAS function. Examples include social media software, augmented reality (AR), and virtual reality (VR) applications deployed and running on EDN (Electronic Data Network). An application can deploy one or more EASs in one or more EDNs; EASs deployed and running in different EDNs can be considered different EASs of the same application. Different EASs of an application can share a domain name; different EASs of an application can use a single anycast IP address or different IP addresses. The edge application server (EAS) may also contain the application context of the application corresponding to that EAS. Optionally, this application context may also contain the context of one or more application users using the application on the EAS, such as the running status information of one or more application users using the application, and the transaction identifier of the subscription for those one or more application users by the EAS. Optionally, the application context may also contain the context of the subscription between the one or more application users using the application and the core network, such as the subscription transaction identifier.

[0073] Edge enabler servers (EES) are deployed within the EDN (Electronic Data Network) to provide edge computing enablement services for application instances (EAS) deployed within the EDN, thereby better supporting the deployment and operation of applications in the MEC (Multi-access Edge Computing). EES supports EAS registration, authentication and authorization of user equipment (UE), and authentication and authorization of edge-enabled clients, providing UEs with application instance information such as IP address information. Generally, an EAS can be registered to an EES, or an EAS's information can be configured on an EES through a management system. This EES is called the EES associated with that EAS, and it can control (manage) the registered or configured EAS or the service EES of that EAS. EES also supports obtaining application instance information, including application instance identifiers and address information (such as IP address information), and further sending this information, such as the application instance identifier, to the edge configuration server (ECS). The ECS is responsible for EDN configuration, such as providing EES information to the UE, providing EAS information to the UE, and interacting with the application's DNS to obtain EAS information. Furthermore, it can obtain and store application instance and IP address information from other functional entities. Figure 1 The illustrated MEC architecture model also illustrates the aforementioned ECS.

[0074] An application client (AC) is a client program for an application on the terminal device side. It is the peer entity of EAS on the terminal device side. The application client is used by application users to obtain application services from the application server. The application client can connect to the application server in the cloud to obtain application services, or it can connect to the EAS deployed and running in one or more EDNs to obtain application services.

[0075] The edge enabler client (EEC) is the peer entity of EES on the terminal device side. The EEC is used to register EEC information and application client AC information with EES, perform security authentication and authorization, obtain EAS information from EES, including EAS address information (such as IP address), and provide edge computing enabling capabilities to application clients. For example, the EEC discovery service can return the IP address of EAS to the application client.

[0076] like Figure 1As shown, a communication connection is established between the application client AC on the terminal device side and the edge application server EAS; a communication connection is also established between the edge-enabled client EEC on the terminal device side and the edge-enabled server EES. Application users sign service agreements with application providers and can use the application by logging into the application client AC deployed on the terminal device. Application data is exchanged and transmitted between the application client AC and EAS through the communication connection. Users can also obtain services provided by the edge-enabled server EES from the edge-enabled client EEC via the application programming interface (API) through the application client AC.

[0077] According to the current standard definition, such as Figure 1 The MEC architecture includes a two-level discovery mechanism: EEC discovers EES from ECS and EEC discovers EAS from EES. First, EEC discovers EES from ECS through the following process: EEC requests or subscribes to ECS to discover EES or EDNs of interest, obtaining information about one or more ESSs, such as the EES corresponding to the UE's location. Second, EEC discovers EAS from EES through the following process: EEC requests the target edge application instance (EAS) it wants to access from EES. Optionally, EEC may indicate the discovery filtering parameters provided by the application user in the request. EES matches one or more EAS that meet the request based on its locally registered or online EAS information and / or the discovery filtering parameters provided by the application user, and returns the information of one or more EAS that meet the request to EEC. Then, EEC can provide the information of one or more EAS received to the application client AC, enabling the AC to connect to the aforementioned EAS.

[0078] During the operation of edge applications, the terminal device (UE) with the deployed application client may move, for example, from one EDN-corresponding area to another. When the terminal device moves outside its current service area, the currently providing edge application server may no longer be able to provide services to the application client running on the moved UE, or the currently providing edge application server may no longer be the optimal edge application server to provide services to the application client on the UE, and there may be other edge application servers more suitable for serving the application client on the UE. In this case, a new edge application server needs to be selected to replace the currently providing edge application server (referred to as the source edge application server), and the new edge application server should be used to provide services to the application client on the UE. This process may cause a brief suspension or interruption of application services. Therefore, it is necessary to migrate the application context of the source edge application in the application client to the new edge application server so that the application client can quickly resume its business after connecting to the target edge application server, thereby reducing the impact of application operation interruption.

[0079] Currently, when EEC / EES detects the need for application context migration, it typically relies on the MEC architecture's communication methods and discovery mechanisms to determine the target EAS for the application context migration and notify the currently serving EAS to perform the migration. This approach involves numerous signaling interactions, resulting in long latency and impacting application operation.

[0080] Based on this, embodiments of this application provide an application context migration method and apparatus. By authorizing (or, as can be described as "requesting" or "delegating") the migration of application contexts managed by the edge enabling function entity, as described above for EEC / EES, the edge enabling function entity is responsible for deciding on the migration of the application context, and may even fully delegate all operations of the application context migration, in order to reduce signaling interaction with EAS and shorten the latency of application context migration. Since the method and apparatus solve the same problem in principle, the method and apparatus embodiments can be referred to mutually, and repeated parts will not be described again.

[0081] In this application's embodiments, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship. Furthermore, it should be understood that although terms such as "first," "second," etc., may be used to describe various data in the embodiments of this invention, these data should not be limited to these terms. These terms are only used to distinguish the data from each other.

[0082] The application context migration method provided in the embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0083] like Figure 2 As shown, this application embodiment provides a method for migrating application contexts, which can be applied to the aforementioned MEC architecture model. The method includes the following steps.

[0084] S201, the application function entity sends first information, the first information being used to indicate the migration of the application context associated with the application function entity.

[0085] The first information can be a request message requesting the migration of the application context associated with the application functional entity. Alternatively, it can be a message that simultaneously requests and subscribes to the application context migration, requesting the migration of the application context and subscribing to migration notifications. The first information can be a service API provided by EES or EEC. Migration can be understood as relocation, and migrating the application context associated with the application functional entity can be understood as switching the service EAS of one, more, or all application users served by the application functional entity from the source EAS to the target EAS through a series of operations. Additionally, the first information can be a parameter in a message indicating the service or operation for migrating the application context. This parameter can be a combination of one or more of a set of enumerated values ​​such as {application context migration event detection, application context migration decision, application context migration execution, application context post-migration cleanup}. For example, if the parameter is "application context migration event detection & application context migration decision & application context migration execution & application context post-migration cleanup", it means that the edge enablement function entity performs the above services or operations. This first information can also be indicated using a specific bit of a parameter.

[0086] The application function entity can refer to either the application client or the edge application server in the aforementioned MEC architecture; the edge enabling function entity can refer to either the edge enabling client or the edge enabling function entity in the aforementioned MEC architecture. In one optional implementation, the application function entity can be the edge application server (EAS), and the edge enabling function entity can be the edge enabling server (EES); in another optional implementation, the application function entity can be the application client (AC), and the edge enabling function entity can be the edge enabling client (EEC).

[0087] The application context associated with an application function entity indicates the application context corresponding to that application function entity. Optionally, the application context may specifically include one or more application contexts related to application users associated with the application function entity. Optionally, the application context includes identification information used to uniquely identify the application context of an application user. For example, if it is necessary to distinguish the application contexts related to different application users, the aforementioned identification information may be a UE identifier such as an IP address, a subscription permanent identifier (SUPI), etc. In addition, the aforementioned identification information may also be the identifier of the application client, such as a uniform resource locator (URL) address.

[0088] Optionally, the edge-enabled functional entity may also respond to the aforementioned first information by sending response information of the first information to the application functional entity.

[0089] S202, when the application context migration trigger event occurs, the edge enable function entity determines to migrate the application context based on the first information.

[0090] Optionally, when the edge enabling function entity detects the movement of the terminal device related to the aforementioned application function entity, it can determine that a business continuity event has occurred, that is, it detects the triggering event of application context migration. This can be understood as the edge enabling function entity being able to detect some events and determine, based on these events, that application context migration may be necessary.

[0091] In this embodiment, the application function entity entrusts the migration of its associated application context to the edge enabling function entity. When the edge enabling function entity detects that the application context needs to be migrated, it can make its own decision to migrate the application context. This can reduce the signaling interaction of the application context migration, shorten the latency of the application context migration, help the normal operation of the business, and reduce the time when the business operation of the terminal application client is affected or interrupted.

[0092] In one optional implementation, the application function entity is the Edge Application Server (EAS), and the edge enabling function entity is the Edge Enabling Server (EES); the edge enabling function entity may also perform one or more of the following operations (1) to (5):

[0093] (1) Detect the triggering event of the migration of the application context.

[0094] (2) Discovering the target application functional entity, which is used to receive the application context; wherein, the target application functional entity may be an Edge Application Server (EAS). The EES can discover the target EAS and migrate the application context associated with the EAS that sent the first information to the target EAS. The application corresponding to the EAS that sent the first information is the same as the application corresponding to the target EAS, that is, the target EAS and the EAS that sent the first information are two different application instances of the same application.

[0095] (3) Transmit the application context to the edge enable function entity associated with the target application function entity; wherein the application corresponding to the application function entity is the same as the application corresponding to the target application function entity, that is, the target EAS and the EAS that sent the first information are two different application instances of the same application.

[0096] (4) Send the information of the target application function entity to the terminal device related to the application function entity; wherein, the application corresponding to the application function entity is the same as the application corresponding to the target application function entity (i.e., the target EAS and the EAS that sent the first information are two different application instances of the same application). Optionally, the information of the target application function entity includes the registration information of the target application function entity on its associated edge enable function entity, so that the application client of the aforementioned application deployed on the terminal device can reconnect to the target application function entity.

[0097] (5) Send the application context migration information to the core network element; wherein, the core network element may be a network expose function (NEF) element, a session management function (SMF) element, etc.

[0098] In one optional implementation, the application function entity is the application client AC, and the edge enabling function entity is the edge enabling client EEC; the edge enabling function entity may also perform one or more of the following operations (1) to (3):

[0099] (1) Detect the triggering event of the migration of the application context.

[0100] (2) Discovering the target application functional entity, which is used to receive the application context; wherein, the target application functional entity may be an Edge Application Server (EAS). The EES can discover the target EAS and migrate the application context associated with the EAS that sent the first information to the target EAS. The application corresponding to the EAS that sent the first information is the same as the application corresponding to the target EAS, that is, the target EAS and the EAS that sent the first information are two different application instances of the same application.

[0101] (3) Send the information of the target application function entity to the terminal device related to the application function entity; wherein, the application corresponding to the application function entity is the same as the application corresponding to the target application function entity (i.e., the target EAS and the EAS that sent the first information are two different application instances of the same application). Optionally, the information of the target application function entity includes the registration information of the target application function entity on its associated edge enable function entity, so that the application client of the aforementioned application deployed on the terminal device can reconnect to the target application function entity.

[0102] In one optional implementation, the first information may further specify the application context-related operation (or service) associated with the migration application function entity. Upon receiving the first information, the edge enabling function entity executes the operation indicated by the first information. This operation may indicate a standalone operation containing only one atomic function (also referred to as an atomic operation or atomic service); or it may indicate a composite operation comprising multiple atomic functions. Delegating some permissions related to migrating the application context to the edge enabling function entity provides greater flexibility. For example, taking the aforementioned EAS sending the first information to the EES as an example, the EAS can instruct the EES to perform one, more, or all of the following: detect the trigger event for application context migration, decide to migrate the application context, discover the target EAS, transfer the application context from the EAS to the target EAS or target EES, and send the target EAS information to the terminal device.

[0103] In one optional implementation, conditions that must be met for the edge-enabled functional entity to implement the indication of the first information can also be set. Optionally, the application functional entity can send first condition information to the edge-enabled functional entity, which is used to indicate the first effective condition of the first information. The application functional entity can send the first condition information together with the first information to the edge-enabled functional entity, or it can send the first information and the first condition information separately to the edge-enabled functional entity; this embodiment does not limit the specific approach.

[0104] Optionally, the first effective condition includes any one or more of the following: the effective duration of the first information, the effective period of the first information, the application client to which the first information applies, the migration duration of the application context being less than a preset time threshold, the size of the application context being less than a preset size threshold, or the application functional entity being overloaded.

[0105] The effective duration of the first information indicates that the edge enabling function entity can implement the instruction of the first information within a specified duration from the time the first information is received. The effective period of the first information indicates that the edge enabling function entity can implement the instruction of the first information within the aforementioned effective period. The application client to which the first information applies can be a UE identifier, a UE IP address, an application client identifier, or an edge enabling client identifier, etc. This parameter specifically indicates that the edge enabling function entity can implement the instruction of the first information for the application context of the application user using the application client on the terminal device corresponding to the UE identifier. Optionally, if the first valid condition does not include the application client to which the first information applies, it means that the edge enabling function entity can implement the instruction of the first information for the application context of all application users. The application context migration time being less than a preset time threshold indicates that the edge enabling function entity can only implement the instruction of the first information when the application context migration time is less than the preset time threshold. The application context size being less than a preset size threshold indicates that the edge enabling function entity can only implement the instruction of the first information when the application context size is less than the preset size threshold. The application function entity overload indicates that the application function entity can implement the instruction of the first information even when overloaded.

[0106] Optionally, conditions that must be met for the edge-enabled functional entity to implement the indication of the first information can also be set to support changes. In one exemplary manner, the application functional entity can also send second condition information to the edge-enabled functional entity. This second condition information indicates a second activation condition for the first information, which is different from the first activation condition. In one possible design, the second activation condition and the first activation condition contain the same parameters but have different values. For example, both the first and second activation conditions include the activation duration of the first information, but the specific activation durations differ. Another example is that the settings for preset time thresholds in the first and second activation conditions are different. In another possible design, the second activation condition and the first activation condition contain different parameters. For example, the second activation condition includes the application client to which the first information applies, while the first activation condition does not include the application client to which the first information applies.

[0107] In one alternative implementation, the edge-enabled functional entity can also obtain the application context associated with the application functional entity in order to perform operations such as determining the size of the application context, determining the migration duration of the application context, and performing the transfer of the application context.

[0108] Optionally, if EAS instructs EES to migrate the application context associated with EAS via the first information, EAS can send its associated application context to EES. Specifically, EAS can send the application context to EES based on a storage address (or managed address) accessible to EES. This storage address stores the application context, and optionally, the storage address accessible to EES can be implemented in one of the following two ways: First method: A managed address can be configured locally on EAS. This address is used by EAS to store the application contexts of one or more application users of its services that need to be migrated or synchronized. EAS stores the application contexts to be migrated at this managed address. Second method: EES can proactively or at EAS's request send the storage address to EAS, so that EAS can synchronize the application context to EES based on the aforementioned storage address. To distinguish the application contexts of multiple application users of the EAS service, EAS can assign an identifier to each user's application context. This identifier can be the application user's identifier, or it can be the IP address or identifier of the terminal device corresponding to the client used by the application user, or it can be other types of application context identifiers. To ensure that the application contexts to be migrated are up-to-date, EAS can periodically synchronize the latest application contexts to EES, for example, every 5 seconds. These application contexts can be stored either as overwrites or as appends. In append mode, if the application context exceeds a preset size, the oldest saved application context can be discarded, or each saved application context for relocation can carry a timestamp or checkpoint information.

[0109] Optionally, if the AC instructs the EEC to migrate the application context associated with the AC via the first information, and the application context associated with the AC is stored in the EAS where the application corresponding to the AC is deployed and running in the EDN, then the application context can be stored in the EES in the following two ways: First method: The AC interacts with the EAS, requesting the EAS to synchronize the application context to the EES. Second method: The EEC needs to request the EES associated with the aforementioned EAS to synchronize the application context, and the EES requests the EAS to synchronize the application context, then the EAS can synchronize the application context to the EES.

[0110] The following section provides a detailed explanation of the implementation process of the above application context migration method, taking into account different application characteristics.

[0111] For some applications, such as video applications with relatively stable operation, it is permissible to perform application context migration at any time. In an optional implementation, the above application context migration method can be implemented based on the registration process of application functional entities. Further optionally, the first information can be included in the registration information of the application functional entity and transmitted to the edge enabling functional entity.

[0112] For example, such as Figure 3 The process of EAS registering with EES, as shown, includes the following steps.

[0113] S301, EAS sends a registration request message or a registration update request message to EES. This registration request message or registration update request message carries registration information, which includes the aforementioned first information. Optionally, the registration information can be an EAS profile. The first information included in the EAS profile can be called an application migration delegate indication, application migration license, application migration agent, application migration decision license, application migration decision license, or application migration decision agent, etc. Optionally, the EAS profile includes the content shown in Table 1 below.

[0114] Table 1

[0115]

[0116]

[0117] S302, EES sends a registration response message or a registration update response message to EAS.

[0118] Optionally, EAS can include the application context's storage address (or managed address) in the registration response message or registration update response message, instructing EAS to send the application context to EES. This application context is the one that needs to be synchronized during migration. The storage address of the application context can be an IP address and port number, or a URL address. In an edge data network environment, EES and EAS are typically deployed in the same data center and may be deployed on the same storage resource. Sending the application context from EAS to EES can be understood as EAS storing the application context in a storage unit identified by a storage address. EES can then read the application context from the storage unit identified by that storage address. In other words, EAS and EES can be two logical functional modules within the same node. The aforementioned application context transfer can be achieved through sharing and managing the application context's storage space, unlike the traditional method of data exchange between two nodes via physical cables. The storage address and the corresponding storage unit can be managed by EES.

[0119] S303, when an application context migration trigger event occurs, if EES determines, based on the EAS registration information, that the application context migration has been delegated to EES, then it can be determined to migrate the application context.

[0120] Optionally, the EES can independently decide to migrate the application context and implement related operations. For example, when the first information indicates that the EES is migrating an application context that includes a transport application context, the related operations include one, more, or all of the following: the EES discovers the target EAS; the EES transfers the application context to the target EAS or the EES associated with the target EAS; the EES notifies the EEC that the application context handover is complete and sends the target EAS information to the EEC; the EES sends the application context migration information to the 3GPP core network elements, such as the target EAS information and the N6 information corresponding to the target EAS. When the first information indicates that the EES is migrating an application context that does not include a transport application context or the EES does not have an application context, the related operations include one, more, or all of the following: the EES discovers the target EAS; the EES notifies the source EAS of the target EAS address or requests the source EAS to transfer the application context to the target EAS; the EES notifies the EEC that the application context handover is complete and sends the target EAS information to the EEC; the EES sends the application context migration information to the 3GPP core network elements, such as the target EAS information and the N6 information corresponding to the target EAS. Additionally, an optional EES associated with the target EAS can replace the target EAS in determining whether to receive the aforementioned application context migration. In this case, the EES transmits the application context to the EES associated with the target EAS, and the EES associated with the target EAS can also replace the target EAS in determining whether to receive the application context. Furthermore, based on the first information in the EAS registration information, the EES can also execute: detecting the trigger event for the application context migration.

[0121] For example, such as Figure 4 The registration process from AC to EEC shown includes the following steps.

[0122] S401, the AC sends a registration request message or a registration update request message to the EEC. This registration request message or registration update request message carries registration information, which includes the aforementioned first information. Optionally, the registration information can be an AC profile. The first indication information included in the AC profile can be called an application migration delegation indication, application migration license, application migration agent, application migration decision license, application migration decision license, or application migration decision agent, etc. Optionally, the AC profile includes the content shown in Table 2 below.

[0123] Table 2

[0124]

[0125] S402, the EEC sends a registration response message or a registration update response message to the AC.

[0126] S403, when an application context migration trigger event occurs, if the EEC determines, based on the AC's registration information, that the application context migration has been delegated to the EEC, then the application context migration can be performed.

[0127] Optionally, the EEC can independently decide to migrate the application context and implement related operations. For example, the EEC obtains information about the target EES from the ECS, and then obtains information about the target EAS from that target EES, where the target EES and target EAS are associated. The EEC triggers the AC, the AC triggers the source EAS, and the source EAS sends the application context to the target EAS. After the application context migration, the AC switches the application data to the target EAS. Alternatively, the EEC may notify the target EES that application context relocation may be necessary; the target EES obtains information about the target EAS and sends an ACR request message to the target EAS; the target EAS initiates an application context transfer between the source EAS and the target EAS. After the context migration, the AC switches the application data to the target EAS. Another example is that the EEC obtains target EAS information from the source EES, and then notifies the source EAS through the source EES to perform an application context migration; the source EAS sends the application context to the target EAS. After the application context migration, the AC switches the application data to the target EAS.

[0128] For some applications, such as those with peak or off-peak business operations, i.e. busy or idle situations, the permissions related to the migration application context can be dynamically delegated to the edge enabling function entity. Optionally, the aforementioned method of setting the effective conditions of at least the first information can be used to set the edge enabling function entity to implement the permissions related to the migration application context under specific conditions.

[0129] For example, such as Figure 5 This paper illustrates a method flow for EAS to instruct EES to migrate the application context, which includes the following steps.

[0130] S501, EAS sends a first request message to EES. This first request message requests that the application context migration be managed (delegated) to EES, or it can be understood that the first request message requests the migration of the application context associated with the application functional entity. It can also be understood that the first request message can be a message that simultaneously requests and subscribes to the application context migration, i.e., requests the migration of the application context and subscribes to notifications of the application context migration. This first message can be a service API, which may be provided by EES; the first request message can also be described as a delegation of decision-making power for application context migration, a management request message, a context migration request, or a full-service context migration request, etc. The first request message contains instructions or requests for EES to make a decision on the application context migration.

[0131] Optionally, EAS can send a first request message to EES when the service is idle or when it is predicted that the service will be idle.

[0132] Optional, such as Figure 5 As shown, the first request message carries the aforementioned first information and first condition information; specifically, the first information may be a relocation delegate indication. Optionally, the application context migration delegate indication includes delegating the decision-making power for application context migration to the EES. The first condition information is used to indicate the first effective condition of the first information, and the content included in the first effective condition can be referred to the foregoing embodiments, which will not be repeated in this application embodiment. Optionally, the EES may save the received first information and first condition information.

[0133] S502, EES responds to the first request message by sending a first response message to EAS.

[0134] Optionally, the first response message may carry a transaction ID, which is used by EAS to perform subsequent operations on the aforementioned first information, or to mark the aforementioned first information and first condition information stored by EES. This facilitates subsequent updates or cancellations of managed transactions by EAS.

[0135] Optionally, the first response message may carry the storage address of the application context, instructing EAS to synchronize the application context to EES based on the aforementioned storage address.

[0136] S503, when an application context migration trigger event occurs, if the EES determines, based on the EAS sending a first request message, that the application context migration has been delegated to the EES and the first condition information is met, then it can be determined to migrate the application context.

[0137] Optionally, the EES can independently decide to migrate the application context and perform related operations, such as: the EES discovering the target EAS; the EES notifying the source EAS of the target EAS's address, or the EES requesting the source EAS to transfer the application context to the target EAS; the EES notifying the EEC that the application context handover is complete and sending the target EAS's information to the EEC; and the EES sending the application context migration information to the 3GPP core network elements, such as the target EAS's information and the N6 information corresponding to the target EAS. Additionally, the EES associated with the target EAS can optionally determine, on behalf of the target EAS, whether to accept the aforementioned application context migration.

[0138] S504, EAS sends a managed update request message to EES. The managed update request message is used to request an update to the aforementioned first information and / or first condition information. It should be noted that the managed update request message can also be called an application context migration delegation or managed request message, or a second request message, or other messages, as long as its function is to request an update to the aforementioned first information and / or first condition information. This application embodiment does not limit this.

[0139] Optionally, the managed update request message carries second condition information, which indicates the second effective condition of the first information. Optionally, the managed update request message also carries the aforementioned transaction identifier, so that EES can determine the managed transaction to be updated by EAS based on the transaction identifier. The difference between the second effective condition and the first effective condition can be referred to in the foregoing embodiments, and will not be repeated in this application embodiment.

[0140] For example, if EAS needs to update the duration of hosting, i.e., update the validity period of the first information, it can carry second condition information in the hosting update request message. This second condition information includes the validity period of the aforementioned updated first information. Upon receiving the hosting update request message carrying this second condition information, if the saved first condition information includes the validity period of the first information, it replaces this with the updated validity period of the first information; if the original saved first condition information does not include the validity period of the first information, it adds the updated validity period of the first information to the first condition information.

[0141] S505, in response to the managed update request message, EES sends a second response message to EAS.

[0142] Optionally, the second response message may carry a transaction ID, which is used to mark a managed transaction in which EAS delegates or entrusts the decision-making power for application context migration to EES, or the transaction ID is used to mark the aforementioned first information and first condition information stored by EES. This facilitates subsequent updates or cancellations of managed transactions by EAS.

[0143] Optionally, the second response message may carry the storage address of the application context, instructing EAS to synchronize the application context to EES based on the aforementioned storage address.

[0144] S506, EAS sends a managed cancellation request message to EES. The managed cancellation request message is used to request the cancellation of the delegation or management of the application context migration to EES. It should be noted that the managed cancellation request message can also be called an application context migration delegation, an application context migration managed cancellation request message, a third request message, or other messages, as long as its function is to request the cancellation of EES's management of the application context migration. This embodiment of the application does not limit this to any particular type.

[0145] Optionally, the managed cancellation request message may also carry the aforementioned transaction identifier and / or first information, so that EES can determine the managed transaction that EAS wants to cancel based on the transaction identifier and / or first information. Optionally, EAS may send a managed cancellation request message to EES when business enters a peak period or when it is predicted that business will enter a peak period.

[0146] S507, in response to the managed cancellation request message, the EES sends a third response message to the EAS. The third response message is used to indicate that the EES agrees to the managed cancellation request message, that is, the EES agrees to relinquish its decision-making power over the application context migration.

[0147] In addition, embodiments of this application also provide a method for indicating the migration application context between edge-enabled functional entities.

[0148] like Figure 6 As shown, this application embodiment provides another method for migrating application contexts, which can be applied to the aforementioned MEC architecture model. The method includes the following steps.

[0149] S601, the first edge enabling function entity sends first information to the second edge enabling function entity, the first information being used to indicate the application context associated with the migration application function entity. This application function entity is the application function entity registered on the first edge enabling function entity.

[0150] The first edge enabling function entity can be an edge enabling server in the aforementioned MEC architecture, and the second edge enabling function entity can be an edge enabling client in the aforementioned MEC architecture. The application function entity can be an edge application server registered on the edge enabling server. This first information can be carried in the EEC registration response message sent by the EES to the EEC, or it can be carried in other messages sent by the EES to the EEC. The first information can be called a relocation delegate indication, which can also include delegating the decision-making power for application migration to the EEC.

[0151] S602, when the application context migration trigger event occurs, the second edge enable function entity determines to migrate the application context based on the first information.

[0152] Optionally, when the second edge enabling function entity detects the movement of the terminal device related to the aforementioned application function entity, it can determine that a business continuity event has occurred, that is, a trigger event for the migration of the application context has been detected.

[0153] In this embodiment, the edge-enabled server delegates the application context migration to the edge-enabled client. When the edge-enabled client detects that the application context needs to be migrated, it can make its own decision to migrate the application context, which can reduce the signaling interaction of the application context migration, shorten the latency, and help the normal operation of the business.

[0154] In one optional implementation, the edge-enabled server may be pre-configured with first information. Optionally, the above-described application context migration method can be implemented based on the registration process of the edge-enabled client to the edge-enabled server.

[0155] For example, such as Figure 7 The process shown includes the following steps for an EEC to register with or update its registration with the EES.

[0156] S701, the EEC sends a registration request message or a registration update request message to the EES. This registration request message or registration update request message carries registration information, which may be an EEC profile. Specifically, the EEC profile includes the information described in Table 3 below.

[0157] Table 3

[0158]

[0159]

[0160] S702, EES sends a registration response message or a registration update response message to EEC.

[0161] Optionally, the EAS may include pre-configured first information in the registration response message or registration update response message to instruct the EEC to migrate the application context. This first information may come from the EAS or be pre-configured in the EES.

[0162] S703, when the EEC detects a trigger event for application context migration, if the EEC determines that the application context migration has been delegated to the EEC based on the registration response message or registration update response message sent by the EES, then it can be determined to migrate the application context.

[0163] In another alternative implementation, the above application context migration method can be implemented based on the process of the edge-enabled client requesting the edge-enabled server to discover the edge application server.

[0164] For example, such as Figure 8 The process shown is one in which an EEC discovers an EAS through an EES, and includes the following steps.

[0165] S801, EEC sends an EAS discovery request message to EES.

[0166] Optionally, the EAS discovery request message may include the EEC ID and security credentials. Optionally, the EAS discovery request message may include EAS discovery filtering parameters, which indicate the target EAS or the category of the target EAS (e.g., game applications).

[0167] S802, EES sends an EAS discovery response message to EEC.

[0168] The EAS discovery response message carries information about the discovered EAS. This EAS information includes the EAS's registration information, which contains the aforementioned first information. Specifically, for example, the EAS discovery response message carries an EAS profile, which includes a relocation delegate indication. Optionally, if the EAS discovery request message carries EAS discovery filter parameters, the EES can determine the discovered EAS based on these parameters, and thus carry the discovered EAS's information in the EAS discovery response message.

[0169] S803, when an application context migration trigger event occurs, if the EEC determines that the application context migration has been delegated to the EES based on the EAS discovery response message sent by the EES, then it can be determined that the application context migration will be performed.

[0170] Furthermore, embodiments of this application also provide a scheme for pre-configuring the migration of application contexts for some applications for edge-enabled functional entities.

[0171] In one optional implementation, a list of applications can be configured on the Edge Enabled Server (EES). The migration of the application context of any application in this list is delegated to the EES; in other words, the EES has the authority to migrate the application context of any application in the list. Optionally, the application list contains one or more EAS identifiers. Each EAS identifier indicates that the migration of the application context of the application corresponding to that EAS identifier is delegated to the EES. The application corresponding to the EAS identifier refers to the application deployed and running on the EAS indicated by the EAS identifier. For example, the application list configured on the EES may contain EAS#ID1 and EAS#ID2. EAS#ID1 indicates that the migration of the application context of the application deployed and running on the EAS with identifier ID1 is delegated to the EES, and EAS#ID2 indicates that the migration of the application context of the application deployed and running on the EAS with identifier ID2 is delegated to the EES.

[0172] Based on this, when EES detects a trigger event for application context migration, EES can query the pre-configured application list to determine that the application context is the application context of a certain application in the application list. In other words, it can determine that the decision-making power for the application context migration has been delegated to EES, and thus EES can determine to migrate the application context.

[0173] Optionally, for any application in the aforementioned application list, managed indication information can be configured on the Edge Application Server (EAS) deployed and running on the EDN for that application. This managed indication information is used to indicate that the decision-making authority for application context migration of that application is delegated to the EES. Optionally, this managed indication information can be the aforementioned first information, specifically configured in the EAS profile.

[0174] Optionally, for the Edge Application Server (EAS), if managed instructions are configured in the EAS, the EAS can synchronize the application context to the ESS. For example... Figure 9 As shown in the figure, this application embodiment also provides a flowchart of a method for synchronizing application context.

[0175] S901, EAS determines whether a managed address is configured locally on EAS. This includes managed address information configured within EAS.

[0176] S902, if an available hosting address (or storage address) is available locally on EAS, the application context to be migrated will be stored on that hosting address. This hosting address can be obtained by EAS from EES during registration.

[0177] S903, if no available hosting address exists locally on EAS, EAS sends a request message to EES to request a storage address. This request message may carry the identifier of the application user whose application context needs to be migrated. This identifier can be the IP address of the terminal device corresponding to the client used by the application user, or the identifier of the terminal device.

[0178] S904, in response to the aforementioned request message from EAS, EES sends a response message to EAS. This response message carries the storage address allocated by EES to EAS. Optionally, the response message also carries an identifier of the application context to be migrated, which is specified by EES. This identifier can be the identifier of the application user, or it can be the IP address or identifier of the terminal device corresponding to the client used by the application user, or it can be other types of application context identifiers.

[0179] S905, EAS synchronizes the application context to be migrated to EES based on a locally available hosting address or a storage address indicated by EES. Optionally, the application context contains an identifier to identify the application context, which can be an application context identifier received from EES or an application context identifier specified by EAS.

[0180] In another alternative implementation, a list of applications can be configured on the Edge Enabled Client (EEC). The migration of the application context of any application in this list is delegated to the EEC; in other words, the EEC has the capability to migrate the application context of any application in this list. Optionally, the application list contains one or more EAS identifiers. Each EAS identifier indicates that the migration of the application context of the application corresponding to that EAS identifier is delegated to the EEC. The application corresponding to the EAS identifier refers to the application deployed and running on the EAS indicated by the EAS identifier. For example, a list of applications configured on the EEC may contain EAS#ID1 and EAS#ID2. EAS#ID1 indicates that the migration of the application context of the application deployed and running on the EAS with identifier ID1 is delegated to the EEC, and EAS#ID2 indicates that the migration of the application context of the application deployed and running on the EAS with identifier ID2 is delegated to the EEC.

[0181] Based on this, when the EEC detects a trigger event for application context migration, the EEC can query the pre-configured application list to determine that the application context is the application context of a certain application in the application list. In other words, it can determine that the decision-making power for the application context migration has been delegated to the EEC, and thus the EEC can decide to migrate the application context.

[0182] For example, such as Figure 10 This paper illustrates a method flow for EAS to instruct EES to migrate the application context, which includes the following steps.

[0183] S1001, the EAS sends an application context migration (subscription) request to the source EES. Optionally, the application context migration (subscription) request includes an application context migration service mode, which can be a full-service mode. The application context migration (subscription) request is used to request the EES to perform all operations related to the application context. These operations include detecting application context migration trigger events, deciding whether the application context needs to be migrated, performing the application context migration, and performing cleanup operations after the migration. Further, these operations also include notifying the EEC of information about the target EAS (specifically, the target EAS's access address, such as its IP address) and notifying the mobile communication network of application migration information. The request message may optionally include the identifiers of one or more application users, which can be the identifier or IP address of the terminal where the client used by the application user is located. If the request does not include application user identifiers, it can be understood that the EAS requests the EES to perform the aforementioned application context migration operations for all application users served by that EAS. The application context migration (subscription) request or the application context migration service mode can be considered as the aforementioned first information.

[0184] S1002, the source EES sends an application context migration (subscription) response to the EAS. This response message may contain an address for application context synchronization, which can be an IP address and port number, or a URL. This address is used by the EAS to store and update the application contexts that need to be migrated. The application context can be the context of one or more users of the EAS service that needs to be migrated. The EES can access and read the application contexts that need to be migrated from this address. A detailed description of this address can be found in the corresponding description in the foregoing embodiments.

[0185] S1003, the source EES detects the application context triggering event. Optionally, after receiving the request message in S1001, the source EES may subscribe to user plane path management event notifications from the core network element and receive user plane path management event notification messages from the core network element. These messages carry a target DNAI, which indicates the potential location where the EAS may be deployed. Optionally, the source EES may also subscribe to the location and changes of the UE from one or more application users' corresponding terminal devices, thereby obtaining the latest location of those one or more terminal devices. Optionally, the source EES may also subscribe to the location and changes of the UE from one or more application users' corresponding terminal devices from the core network element, thereby obtaining the latest location of those one or more terminal devices. The source EES can determine, based on the user plane path management event notifications and their target DNAIs or the UE's location, that one or more application users may require application context migration.

[0186] S1004, the source EES decides whether the application context needs to be migrated for one or more application users. For example, the source EES can move the UE out of the service area (or the best service area) corresponding to the current source EES based on the UE's location, thereby determining whether an application context migration is needed.

[0187] S1005, Optionally, when the source EES determines that an application context needs to be migrated for one or more application users, it may send an application context migration notification message to the source EAS, informing the source EAS that the application context for the one or more users needs to be migrated. Further, it may also include notifying the EAS to prepare the application context that needs to be migrated.

[0188] S1006, the source EES sends an EES request message to the edge configuration server ECS to obtain information about a target EES that matches the location or target DNAI of the one or more users and can provide services for the application. After obtaining the target EES from the ECS, the source EES sends an EAS request message to the target EES to request the transfer of the application context for the one or more users. After the target EES determines the target EES and the target EES can accept the application context, the target EES sends a response message to the source EES, indicating acceptance of the application context. Furthermore, the request message sent by the source EES to the target EES can also be used to obtain information about the target EES that provides services for the application. Optionally, the source EES obtains the target EES information from the target EES.

[0189] S1007, after step S1002 and before step S1008, the source EAS synchronizes the application context to be migrated to the source EES. For a description of the synchronization of the application context from the source EAS to the source EES, please refer to the corresponding description in the foregoing embodiments.

[0190] S1008, when the source EES determines that the target EES can accept the application context, the source EES reads the application context to be migrated from the aforementioned address and transmits the application context to the target EES. The target EES saves the received application context to a specific storage address identifying the storage area.

[0191] S1009, the target EES sends an application context migration notification message to the target EAS to notify the target EAS that there is an application context to receive. This message may contain address information for reading the application context, corresponding to the storage address where the target EES stores the application context in S1008. This step is optional.

[0192] S1010, the target EAS sends an application context acquisition request to the target EES. This request message is a user request to obtain the application context. This step is optional.

[0193] S1011, the target EES sends an application context acquisition response to the target EAS, indicating that the request message is accepted.

[0194] S1012, after receiving the application context, the target EES sends the application context to the target EAS. This can be understood as the target EAS and target EES processing the application context in ways such as mapping storage addresses or copying or cutting the application context across different storage spaces on the same physical storage device. This is similar to the aforementioned methods used by the source EAS and source EES to process the application context, and can also be referenced to the corresponding descriptions in the preceding embodiments.

[0195] S1013, Optionally, after the application context transfer is completed, the source EES sends an application context migration notification message to the EEC. This message indicates that the application context transfer is complete and may contain information about the target EAS, specifically the EAS's IP address and port number. Further, the EEC sends a notification message to the AC, notifying the AC that the application context transfer is complete, and this message also includes information about the target EAS.

[0196] S1014, Optionally, after the application context transfer is completed, the source EES sends an application context migration notification message to the source EAS, which indicates that the application context transfer is complete.

[0197] S1015, optionally, the source EES sends an application migration message to the core network elements. Specifically, this includes the address information of the target EAS, the routing information of the target N6, etc. Figure 10 S1015 is not shown in the diagram.

[0198] Based on the same concept, see [link / reference] Figure 10 This application provides an application context migration device 1100, which includes a communication module 1101 and a processing module 1102.

[0199] (i) The application context migration device 1100 can be applied to an edge-enabled functional entity. Specifically, the application context migration device 1100 can be an edge-enabled functional entity, or it can be applied to an edge-enabled functional entity, or it can be a device that supports the edge-enabled functional entity in executing a data transmission method. The following describes in detail the functions or execution processes of the modules in the application context migration device 1100 applied to an edge-enabled functional entity.

[0200] Communication module 1101 is configured to receive first information from an application function entity, the first information being configured to indicate the migration of the application context associated with the application function entity;

[0201] The processing module 1102 is used to determine, based on the first information, to migrate the application context when a trigger event for the migration of the application context occurs.

[0202] In this embodiment, the application function entity entrusts the migration of its associated application context to the edge enabling function entity. When the edge enabling function entity detects that the application context needs to be migrated, it can make its own decision to migrate the application context. This can reduce the signaling interaction of the application context migration, shorten the latency of the application context migration, help the normal operation of the business, and reduce the time when the business operation of the terminal application client is affected or interrupted.

[0203] In an optional implementation, the processing module 1102 is further configured to perform one or more of the following operations based on the first information: detect a trigger event for the migration of the application context; discover a target application function entity, the target application function entity being used to receive the application context; transmit the application context to an edge enabling function entity associated with the target application function entity; send information of the target application function entity to a terminal device associated with the application function entity; and send information about the migration of the application context to a core network element; wherein the application corresponding to the application function entity is the same as the application corresponding to the target application function entity.

[0204] In one optional implementation, the communication module 1101 is specifically used to receive registration information from the application function entity, the registration information including the first information.

[0205] In an optional implementation, the communication module 1101 is further configured to receive first condition information from an application function entity, the first condition information being used to indicate a first effective condition for the first information.

[0206] In one optional implementation, the first effective condition includes any one or more of the following: the effective duration of the first information, the effective period of the first information, the application client to which the first information is applied, the migration duration of the application context being less than a preset time threshold, the size of the application context being less than a preset size threshold, or the application functional entity being overloaded.

[0207] In an optional implementation, the communication module 1101 is further configured to receive second condition information from the application function entity, the second condition information being used to indicate a second effective condition of the first information, the second effective condition being different from the first effective condition.

[0208] In an optional implementation, the communication module 1101 is further configured to receive the application context from the application functional entity.

[0209] In an optional implementation, before receiving the application context from the application function entity, the communication module 1101 is further configured to send the storage address of the application context to the application function entity.

[0210] In one alternative implementation, the application context includes identification information, which is used to uniquely identify the application context.

[0211] (ii) The application context migration device 1100 can be applied to an application functional entity. Specifically, the application context migration device 1100 can be an application functional entity, or it can be applied to an application functional entity, or it can be a device that supports the application functional entity in executing a data transmission method. The following describes in detail the functions or execution processes of the modules in the application context migration device 1100 applied to an application functional entity.

[0212] Processing module 1102 is used to determine the first information.

[0213] The communication module 1101 is configured to send first information to the edge enabling function entity, the first information being used to indicate the application context associated with the migration application function entity; the communication module 1101 is also configured to receive response information from the edge enabling function entity in response to the sending of the first information.

[0214] In this embodiment, the edge enabling function entity is responsible for the migration of application contexts. When the edge enabling function entity detects that the application context needs to be migrated, it can make its own decision to migrate the application context. This can reduce the signaling interaction of the application context migration, shorten the latency of the application context migration, help the normal operation of the business, and reduce the time when the business operation of the terminal application client is affected or interrupted.

[0215] In an optional implementation, the first information is further used to instruct the edge enabling function entity to perform one or more of the following operations: detect a trigger event for the migration of the application context; discover a target application function entity, the target application function entity being used to receive the application context; transmit the application context to the edge enabling function entity associated with the target application function entity; send information of the target application function entity to the terminal device associated with the application function entity; and send the migration information of the application context to the core network element; wherein the application corresponding to the application function entity is the same as the application corresponding to the target application function entity.

[0216] In an optional implementation, the communication module 1101 is further configured to send registration information to the edge enable function entity, the registration information including the first information.

[0217] In an optional implementation, the processing module 1102 is further configured to determine first condition information; the communication module 1101 is further configured to send the first condition information to the edge enabling function entity, wherein the first condition information is used to indicate the first effective condition of the first information.

[0218] In one optional implementation, the first condition information includes any one or more of the following: the effective duration of the first information, the effective period of the first information, the application client for which the first information is effective, the migration duration of the application context being less than a preset time threshold, the size of the application context being less than a preset size threshold, and the application functional entity being overloaded.

[0219] In an optional implementation, the processing module 1102 is further configured to determine second condition information; the communication module 1101 is further configured to send the second condition information to the edge enabling function entity, the second condition information being used to indicate a second effective condition of the first information, the second effective condition being different from the first effective condition.

[0220] In one alternative implementation, after sending the first information to the edge enabling function entity, the communication module 1101 is further configured to send the application context to the edge enabling function entity.

[0221] In one optional implementation, before sending the application context to the edge enabling entity, the communication module 1101 is further configured to receive the storage address of the application context from the edge enabling entity; and send the application context to the edge enabling entity based on the storage address.

[0222] In one alternative implementation, the application context includes identification information, which is used to uniquely identify the application context.

[0223] Based on the same concept, such as Figure 12 As shown, this application embodiment provides a communication device 1200. Exemplarily, the communication device 1200 may be a chip or a chip system. Optionally, in this application embodiment, the chip system may be composed of chips, or may include chips and other discrete devices.

[0224] The communication device 1200 may include at least one processor 1210, and may also include at least one memory 1220 for storing computer programs, program instructions and / or data. The memory 1220 and the processor 1210 are coupled.

[0225] The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, used for information interaction between devices, units, or modules. The processor 1210 may operate in conjunction with the memory 1220. The memory 1220 stores the computer programs, program instructions, and / or data necessary for implementing any of the above embodiments; the processor 1210 may execute the computer programs stored in the memory 1220 to complete the methods in any of the above embodiments. Optionally, at least one of the memories 1220 may be included in the processor 1210.

[0226] The communication device 1200 may also include a transceiver 1230, through which the communication device 1200 can exchange information with other devices. The transceiver 1230 may be a circuit, a bus, a transceiver, or any other device that can be used for information exchange.

[0227] In one possible implementation, the communication device 1200 can be applied to an edge-enabled functional entity. Specifically, the communication device 1200 can be an edge-enabled functional entity, or it can be a device capable of supporting the edge-enabled functional entity and implementing the functions of the edge-enabled functional entity in any of the above embodiments. The memory 1220 stores the necessary computer programs, program instructions, and / or data for implementing the functions of the edge-enabled functional entity in any of the above embodiments. The processor 1210 can execute the computer program stored in the memory 1220 to complete the method executed by the edge-enabled functional entity in any of the above embodiments.

[0228] In another possible implementation, the communication device 1200 can be applied to an application functional entity. Specifically, the communication device 1200 can be an application functional entity or an apparatus capable of supporting the application functional entity and implementing the functions of the application functional entity in any of the above embodiments. The memory 1220 stores the necessary computer programs, program instructions, and / or data for implementing the functions of the application functional entity in any of the above embodiments. The processor 1210 can execute the computer program stored in the memory 1220 to complete the method executed by the application functional entity in any of the above embodiments.

[0229] This application embodiment does not limit the specific connection medium between the transceiver 1230, processor 1210, and memory 1220. This application embodiment... Figure 12 The memory 1220, processor 1210, and transceiver 1230 are connected via a bus, and the bus is in... Figure 12 The connections between other components are shown in bold lines only and are not intended to be limiting. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, Figure 12The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0230] In the embodiments of this application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, and may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0231] In the embodiments of this application, the memory can be non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it can be volatile memory, such as random-access memory (RAM). The memory can also be any other medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited thereto. The memory in the embodiments of this application can also be a circuit or any other device capable of implementing storage functions, used to store computer programs, program instructions, and / or data.

[0232] Based on the above embodiments, see Figure 13 This application also provides another communication device 1300, including: an interface circuit 1310 and a processor 1320; the interface circuit 1310 is used to receive code instructions and transmit them to the processor; the processor 1320 is used to run the code instructions to execute the method executed by the edge enabling function entity or the application function entity in any of the above embodiments.

[0233] Based on the above embodiments, this application also provides a computer-readable storage medium storing instructions that, when executed, cause the method executed by the edge-enabled functional entity or the method executed by the application functional entity in any of the above embodiments to be implemented. The computer-readable storage medium may include various media capable of storing program code, such as a USB flash drive, portable hard drive, read-only memory, random access memory, magnetic disk, or optical disk.

[0234] To achieve the above Figures 11-13In addition to the functions of the communication device, this application also provides a chip, including a processor, for supporting the communication device in implementing the functions involved in the edge enabling function entity or application function entity in the above method embodiments. In one possible design, the chip is connected to a memory or the chip includes a memory for storing necessary program instructions and data of the communication device.

[0235] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0236] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0237] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0238] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0239] Obviously, those skilled in the art can make various modifications and variations to the embodiments of this application without departing from the scope of the embodiments of this application. Therefore, if these modifications and variations to the embodiments of this application fall within the scope of the claims of this application and their equivalents, this application also intends to include these modifications and variations.

Claims

1. A method for transferring application context, characterized in that, Applied to edge-enabled servers, the method includes: Receive first information from an application function entity, the first information being used to instruct the migration of the application context associated with the application function entity; Based on the first information, perform the following operations: Detect the trigger event for the migration of the application context; when the trigger event occurs, determine to migrate the application context; Discover the target application function entity, which is used to receive the application context; The application context is transmitted to the edge-enabled server associated with the target application functional entity; Send the information of the target application function entity to the terminal device related to the application function entity; The application context migration information is sent to the core network element; The application corresponding to the application function entity is the same as the application corresponding to the target application function entity.

2. The method as described in claim 1, characterized in that, The receipt of the first information from the application functional entity includes: Receive registration information from the application function entity, the registration information including the first information.

3. The method as described in claim 1 or 2, characterized in that, The method further includes: Receive first condition information from the application function entity, the first condition information being used to indicate the first effective condition of the first information.

4. The method as described in claim 3, characterized in that, The first effective condition includes any one or more of the following: the effective duration of the first information, the effective period of the first information, the application client to which the first information is applied, the migration duration of the application context is less than a preset time threshold, the size of the application context is less than a preset size threshold, or the application functional entity is overloaded.

5. The method as described in claim 3 or 4, characterized in that, The method further includes: Receive second condition information from the application functional entity, the second condition information being used to indicate a second effective condition of the first information, the second effective condition being different from the first effective condition.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: Receive the application context from the application function entity.

7. The method as described in claim 6, characterized in that, Before receiving the application context from the application functional entity, the method further includes: Send the storage address of the application context to the application function entity.

8. The method according to any one of claims 1-7, characterized in that: The application context contains identification information, which is used to uniquely identify the application context.

9. A method for transferring application context, characterized in that, Applied to application functional entities, the method includes: Send a first message to the edge enabling server, the first message being used to instruct the edge enabling server to perform one or more of the following operations: Detect the trigger events for the migration of application context associated with application functional entities; When the triggering event occurs, the application context is determined to be migrated; Discover the target application function entity, which is used to receive the application context; The application context is transmitted to the edge-enabled server associated with the target application functional entity; Send the information of the target application function entity to the terminal device related to the application function entity; The application context migration information is sent to the core network element; Wherein, the application corresponding to the application function entity is the same as the application corresponding to the target application function entity; Receive the response from the edge-enabled server in response to the first information sent.

10. The method as described in claim 9, characterized in that, Sending the first information to the edge-enabled server includes: Send registration information to the edge-enabled server, the registration information including the first information.

11. The method as described in claim 9 or 10, characterized in that, The method further includes: Send first condition information to the edge enabling server, the first condition information being used to indicate the first effective condition of the first information.

12. The method as described in claim 11, characterized in that, The first condition information includes any one or more of the following: the effective duration of the first information, the effective period of the first information, the application client for which the first information is effective, the migration duration of the application context being less than a preset time threshold, the size of the application context being less than a preset size threshold, and the application function entity being overloaded.

13. The method as described in claim 11 or 12, characterized in that, The method further includes: Send a second condition information to the edge enabling server. The second condition information is used to indicate a second effective condition of the first information. The second effective condition is different from the first effective condition.

14. The method according to any one of claims 9-13, characterized in that, After sending the first information to the edge enabling server, the method further includes: Send the application context to the edge enable server.

15. The method as described in claim 14, characterized in that, The response information includes the storage address of the application context; Sending the application context to the edge enabling server includes: Based on the storage address, the application context is sent to the edge enable server.

16. The method according to any one of claims 9-15, characterized in that: The application context contains identification information, which is used to uniquely identify the application context.

17. An application context migration device, characterized in that, The device includes: A communication module is configured to receive first information from an application function entity, the first information being used to indicate the migration of the application context associated with the application function entity; The processing module is configured to perform the following operations based on the first information: Detect the triggering event of the application context migration; When a trigger event for the migration of the application context occurs, determine to migrate the application context; Discover the target application function entity, which is used to receive the application context; The application context is transmitted to the edge-enabled server associated with the target application functional entity; Send the information of the target application function entity to the terminal device related to the application function entity; The application context migration information is sent to the core network element; The application corresponding to the application function entity is the same as the application corresponding to the target application function entity.

18. The apparatus as claimed in claim 17, characterized in that, The communication module is specifically used to receive registration information from the application function entity, and the registration information includes the first information.

19. The apparatus as claimed in claim 17 or 18, characterized in that, The communication module is further configured to receive first condition information from the application function entity, wherein the first condition information is used to indicate the first effective condition of the first information.

20. The apparatus as claimed in claim 18, characterized in that, The first effective condition includes any one or more of the following: the effective duration of the first information, the effective period of the first information, the application client to which the first information is applied, the migration duration of the application context is less than a preset time threshold, the size of the application context is less than a preset size threshold, or the application functional entity is overloaded.

21. The apparatus as claimed in claim 19 or 20, characterized in that, The communication module is further configured to receive second condition information from the application function entity, the second condition information being used to indicate a second effective condition of the first information, the second effective condition being different from the first effective condition.

22. The apparatus according to any one of claims 17-21, characterized in that, The communication module is also configured to receive the application context from the application functional entity.

23. The apparatus as claimed in claim 22, characterized in that, Before receiving the application context from the application function entity, the communication module is further configured to send the storage address of the application context to the application function entity.

24. The apparatus according to any one of claims 17-23, characterized in that: The application context contains identification information, which is used to uniquely identify the application context.

25. An application context migration device, characterized in that, include: The communication module is used to send first information to the edge-enabled server, the first information being used to instruct the edge-enabled server to perform the following operation: Detect the trigger events for the migration of application context associated with application functional entities; When the triggering event occurs, the application context is determined to be migrated; Discover the target application function entity, which is used to receive the application context; The application context is transmitted to the edge-enabled server associated with the target application functional entity; Send the information of the target application function entity to the terminal device related to the application function entity; The application context migration information is sent to the core network element; Wherein, the application corresponding to the application function entity is the same as the application corresponding to the target application function entity; The communication module is also used to receive response information from the edge-enabled server in response to the first information sent.

26. The apparatus as claimed in claim 25, characterized in that, The communication module is also used to send registration information to the edge enabling server, the registration information including the first information.

27. The apparatus as claimed in claim 25 or 26, characterized in that, The communication module is further configured to send first condition information to the edge enabling server, the first condition information being used to indicate a first effective condition for the first information.

28. The apparatus as claimed in claim 27, characterized in that, The first condition information includes any one or more of the following: the effective duration of the first information, the effective period of the first information, the application client for which the first information is effective, the migration duration of the application context being less than a preset time threshold, the size of the application context being less than a preset size threshold, and the application function entity being overloaded.

29. The apparatus as claimed in claim 27 or 28, characterized in that, The communication module is further configured to send second condition information to the edge enabling server, the second condition information being used to indicate a second effective condition of the first information, the second effective condition being different from the first effective condition.

30. The apparatus according to any one of claims 25-29, characterized in that, After sending the first information to the edge enabling server, the communication module is also used to send the application context to the edge enabling server.

31. The apparatus as claimed in claim 30, characterized in that, The response information includes the storage address of the application context; When the communication module sends the application context to the edge enabling server, it is specifically used to send the application context to the edge enabling server based on the storage address.

32. The apparatus according to any one of claims 25-31, characterized in that: The application context contains identification information, which is used to uniquely identify the application context.

33. A communication device, characterized in that, include: Processor and memory; The memory is used to store computer programs; The processor is configured to execute a computer program stored in the memory to cause the method as described in any one of claims 1 to 8 or the method as described in any one of claims 9 to 16 to be performed.

34. A communication device, characterized in that, include: Processor and interface circuitry; The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to execute the code instructions to cause the method as described in any one of claims 1 to 8 or the method as described in any one of claims 9 to 16 to be performed.

35. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed, cause the method as claimed in any one of claims 1 to 8 or the method as claimed in any one of claims 9 to 16 to be implemented.

36. A computer program product, characterized in that, Includes computer program code, which, when executed, causes the method as described in any one of claims 1-16 to be performed.

37. A communication system, characterized in that, It includes a first communication device for performing the method of any one of claims 1 to 8, and a second communication device for performing the method of any one of claims 9 to 16.

38. A method for transferring application context, characterized in that, include: The application function entity sends the first information to the edge enable server. The edge-enabled server receives the first information; The edge-enabled server performs the following operations based on the first information: Detect the trigger event for the migration of the application context associated with the application function entity; When the triggered event occurs, the application context is determined to be migrated; Discover the target application function entity, which is used to receive the application context; The application context is transmitted to the edge-enabled server associated with the target application functional entity; Send the information of the target application function entity to the terminal device related to the application function entity; The application context migration information is sent to the core network element; The application corresponding to the application function entity is the same as the application corresponding to the target application function entity.

39. The method as described in claim 38, characterized in that, Also includes: The edge enabling server responds to the first information by sending response information to the application function entity; The application function entity receives the response information.

40. The method as described in claim 39, characterized in that, Also includes: The application function entity sends the application context to the edge enable server; The edge-enabled server receives the application context.

41. The method as described in claim 40, characterized in that, The response information includes the storage address of the application context; The application function entity sends the application context to the edge enabling server, including: the application function entity sending the application context to the edge enabling server based on the storage address.

Images