Application context relocation method, communication method, and related apparatus and system

Abstract

This application provides an application context relocation ACR method, a communication method, and a related apparatus and system, to relocate an application context between application instances EASs. The ACR method includes: determining a target edge enabler server EES, where the target EES is an EES that supports a first ACR scenario, and the first ACR scenario is a scenario in which the target EES executes ACR; and requesting the target EES to execute ACR. In the ACR method, the target EES that supports the first ACR scenario is determined and the target EES is requested to execute ACR, so that ACR can be completed via the target EES.

Description

Application context migration method, communication method, and related devices and systems

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on February 20, 2023, with application number 202310193234.1 and application name “Application context migration method, communication method and related devices and systems”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to an application context migration method, a communication method, and related devices and systems. Background Art

[0003] In edge computing scenarios, the same application is often deployed in multiple edge data networks (EDNs) at the same time. Application instances (edge ​​application servers, EAS) of the same application deployed in different EDNs can provide the same services. After accessing the network, the terminal device will select the nearest EAS to obtain application services. When the location of the terminal device changes, or the user plane path is updated, or the current EDN cannot provide services, the terminal device needs to reselect a new EAS to continue the service. The EAS reselected by the terminal device can be called the target EAS, and the EAS to which the terminal device is connected before switching to the target EAS can be called the source EAS.

[0004] When the service of a terminal device is switched from a source EAS to a target EAS, in order to ensure the continuity of the application service, the application context in the source EAS needs to be migrated to the target EAS. How to perform this application context migration is an urgent problem to be solved.

[0005] Summary of the Invention

[0006] The present application provides an application context migration method, a communication method, and related devices and systems, in order to migrate the application context between EASs.

[0007] In the first aspect, the present application provides an application context relocation (ACR) method, which can be applied to a terminal device and can be executed by the terminal device, or can be executed by a component configured in the terminal device (such as a chip, a chip system, a processor, etc.), or can be implemented by a logic module or software that can realize all or part of the terminal device functions. The present application does not limit this.

[0008] The method includes: determining a target edge enabler server (EES), where the target EES is an EES that supports a first ACR scenario, where the first ACR scenario is a scenario where ACR is performed by the target EES; and requesting the target EES to perform ACR.

[0009] Among them, ACR is the process of migrating the application context from the source EAS to the target EAS. In this application, the source EAS is the EAS that currently provides application services for the application of the terminal device, that is, the EAS that the terminal device is currently connected to, the source EES is the EAS associated with the source EAS, the source EAS is registered on the source EES, and the source EES manages the source EAS. The target EAS is the EAS that provides application services for the application of the terminal device after ACR, the target EES is the EES associated with the target EAS, the target EAS is registered on the target EES, and the target EES manages the target EAS. In the ACR process, it is necessary to first discover the target EES, and then discover the target EAS through the target EES, so as to perform ACR.

[0010] The first ACR scenario is where the target EES executes ACR. This ACR scenario includes ACR detection, ACR decision-making, ACR execution, and post-ACR cleanup. In the first ACR scenario, the terminal device performs ACR detection and ACR decision-making, the target EES executes ACR, and the target EES and target EAS perform post-ACR cleanup.

[0011] The execution of ACR by the target EES includes at least one of the following: the target EES performs user plane path modification, the target EES discovers the target EAS through the target EES, and the target EES triggers the target EAS to transmit the application context.

[0012] In this application, the determined target EES is an EES that supports the first ACR scenario, in other words, the EES is capable of performing ACR as a target EES. In this way, after requesting the target EES to perform ACR, the target EES is able to perform ACR.

[0013] Based on the above technical solution, the determined target EES supports ACR as the target EES. Therefore, when the EAS currently connected to the terminal device can no longer provide application services, the target EES can successfully complete the application context migration. This ensures a smooth EAS handover and guarantees the stability and continuity of application services.

[0014] In combination with the first aspect, in some possible implementations of the first aspect, determining the target EES includes: receiving EES information from an edge configuration server (ECS), where the EES information indicates at least one EES; and determining the target EES based on the EES information.

[0015] The ECS is responsible for configuring the EDN. EES information can be registered or configured on the ECS. The ECS can provide EES information to terminal devices, indicating the EES registered or configured on the ECS. The terminal device can determine the target EES based on the EES information from the ECS.

[0016] Optionally, the method further includes: the terminal device receiving first information from the ECS, where the first information indicates the ACR capability of the at least one EES.

[0017] Among them, the ACR capability of EES includes at least one of the following information: whether EES supports ACR, the ACR scenarios supported by EES, the ACR application programming interface (API) supported by EES, etc.

[0018] The ECS can send EES information to the terminal device, indicating at least one EES. The ECS can also send information indicating the ACR capabilities of these EESs to the terminal device. Accordingly, the terminal device can obtain the ACR capabilities of the EES.

[0019] In this way, the terminal device can select an EES that supports the first ACR scenario based on the ACR capability of the EES and use it as the target EES.

[0020] In some embodiments, the EES indicated by the EES information from the ECS is an EES that supports the first ACR scenario, that is, the ECS may filter out the EES that supports the first ACR scenario from the EESs registered or configured on the ECS and send the EES to the terminal device.

[0021] Therefore, when the terminal device selects a target EES from the EES indicated by the EES information, it does not need to perform further screening based on the ACR scenarios supported by the EES, which can reduce the burden on the terminal device.

[0022] Optionally, the method also includes: the terminal device sends second information to the ECS, and the second information is used to indicate at least one of the following: selecting a target EES that supports the first ACR scenario, or the currently connected EES or the currently connected EAS cannot perform ACR, or the current application has no corresponding ACR scenario, or requesting to obtain the ACR capability of the EES.

[0023] Before the ECS sends the EES information or the first information to the terminal device, the terminal device may send the second information to the ECS. In other words, based on the second information, the ECS may select an EES that supports the first ACR scenario and indicate it to the terminal device, or send information to the terminal device indicating at least one EES and the ACR capability of the at least one EES.

[0024] Based on the above technical solution, the ECS can filter out the EES that supports the first ACR scenario based on the ACR capability of the EES and indicate it to the terminal device, so that the terminal device can determine an EES as the target EES without having to filter based on the ACR capability of the EES. The task volume of the terminal device can be reduced, which can alleviate the burden on the terminal device. The ECS can also indicate the EES and the ACR capability of the EES to the terminal device, and the terminal device can filter out the EES that supports the first ACR scenario as the target EES, so that the ECS does not have to filter based on the ACR capability of the EES. The task volume of the ECS can be reduced, which can alleviate the burden on the ECS. The target EES determined by the terminal device supports the first ACR scenario, so that when requesting the target EES to perform ACR, the terminal device can successfully perform ACR, thereby enabling the EAS switching to be completed smoothly, which can ensure the continuity of the application business.

[0025] In combination with the first aspect, in some possible implementations of the first aspect, the method also includes: when the current application has no corresponding ACR scenario, or when the currently connected EES or the currently connected EAS cannot perform ACR, determining to perform ACR based on the first ACR scenario.

[0026] If the current application has no corresponding ACR scenario or the currently connected EES or the currently connected EAS cannot perform ACR, the application context cannot be migrated. At this time, the terminal device can determine to perform ACR based on the first ACR scenario, that is, to perform ACR through the target EES. After the terminal device determines to perform ACR based on the first ACR scenario, it can select the target EES and request it to perform ACR.

[0027] It should be understood that when the current application has a corresponding ACR scenario, or when the currently connected EES or the currently connected EAS is capable of performing ACR, the terminal device may also determine to perform ACR based on the first ACR scenario.

[0028] Optionally, the method further includes: the terminal device receiving third information from the currently connected EES, where the third information indicates that the current application has no corresponding ACR scenario, or indicates that the currently connected EES or the currently connected EAS cannot perform ACR.

[0029] The terminal device can determine, through information from the EES, that the current application has no corresponding ACR scenario, or determine that the currently connected EES or the currently connected EAS cannot perform ACR.

[0030] In combination with the first aspect, in some possible implementations of the first aspect, before determining the target EES, the method also includes: receiving fourth information from the currently connected EES, the fourth information being used to indicate the selection of a target EES that supports the first ACR scene, or to indicate that the first ACR scene is the ACR scene corresponding to the current application.

[0031] The currently connected EES can determine that ACR needs to be performed based on the first ACR scenario, and indicate to the terminal device that the ACR scenario corresponding to the current application is the first ACR scenario, or it can indicate to the terminal device that when determining the target EES, the target EES needs to support the first ACR scenario.

[0032] In combination with the first aspect, in some possible implementations of the first aspect, the method further includes: receiving EAS information from a target EES, where the EAS information indicates at least one EAS; and determining the target EAS based on the EAS information.

[0033] The target EES can send EAS information to the terminal device, indicating at least one EAS, from which the terminal device can determine the target EAS. The application service can be switched from the currently connected EAS to the target EAS, and ACR can be performed based on the target EAS.

[0034] Optionally, the method further includes: the terminal receives fifth information from the target EAS, where the fifth information indicates the ACR capability of the at least one EAS.

[0035] The ACR capabilities of EAS include whether EAS supports ACR, the ACR scenarios supported by EAS, and the ACR APIs supported by EAS.

[0036] The target EES can send information indicating the ACR capability of the EAS to the terminal device. Accordingly, the terminal device can obtain the ACR capability of at least one EAS indicated by the target EES, so that the terminal device can determine the EAS that supports the first ACR scenario based on the ACR capability of the EAS and use it as the target EAS.

[0037] In some embodiments, the at least one EAS supports a first ACR scenario.

[0038] The target EES may select an EAS that supports the first ACR scenario and indicate the EAS to the terminal device via EAS information sent to the terminal device. In this way, the terminal device may select one of the EASs as the target EAS.

[0039] Optionally, the method also includes: the terminal device sends sixth information to the target EES, and the sixth information is used to indicate at least one of the following: selecting a target EAS that supports the first ACR scenario, or the source EES or source EAS cannot perform ACR, or the current application has no corresponding ACR scenario, or requesting to obtain the ACR capability of the EAS.

[0040] Before the target EES sends the EAS information or the fifth information to the terminal device, the terminal device may send the sixth information to the target EES. In other words, the target EES may send the EAS information to the terminal device based on the sixth information and / or send the fifth information to the terminal device.

[0041] Based on the above technical solution, the target EES can filter out the EAS that supports the first ACR scenario based on the ACR capability of the EAS and indicate it to the terminal device, so that the terminal device can determine an EAS as the target EAS without having to filter based on the ACR capability of the EAS. The task load of the terminal device can be reduced, which can alleviate the burden on the terminal device. The target EES can also indicate the EAS and the ACR capability of the EAS to the terminal device, and the terminal device can filter out the EAS that supports the first ACR scenario as the target EAS. Therefore, the target EES does not have to filter based on the ACR capability of the EAS. The task load of the target EES can be reduced, which can alleviate the burden on the target EES.

[0042] The target EES and target EAS determined by the terminal device both support the first ACR scenario. When the terminal device requests the target EES to perform ACR, the target EES and target EAS are capable of performing ACR, thereby successfully completing the migration of the application context and ensuring the continuity of the application business.

[0043] On the second aspect, the present application provides a communication method, which can be applied to ECS and can be executed by ECS, or can be executed by components configured in ECS (such as chips, chip systems, processors, etc.), or can be implemented by logic modules or software that can implement all or part of the ECS functions. This application does not limit this.

[0044] The method includes: sending EES information to a terminal device, where the EES information indicates at least one EES; and sending first information to the terminal device, where the first information indicates an ACR capability of the at least one EES.

[0045] The ECS may send EES information and first information to the terminal device, indicating at least one EES and the ACR capability of the at least one EES, so that the terminal device can determine a target EES that supports the first ACR scenario based on the ACR capability of the EES.

[0046] Optionally, the method further includes: receiving second information from the terminal device, where the second information is used to indicate a request to obtain the ACR capability of the EES.

[0047] The ECS may send the EES information and the first information to the terminal device based on the second information from the terminal device.

[0048] In the third aspect, the present application provides a communication method, which can be applied to the ECS in the above-mentioned second aspect, and the method includes: determining at least one EES that supports a first ACR scenario, where the first ACR scenario is a scenario in which ACR is performed by a target EES; and sending EES information to a terminal device, where the EES information indicates the at least one EES.

[0049] The ECS may determine at least one EES that supports the first ACR scenario and indicate it to the terminal device, so that the terminal device may select any one of them as the target EES.

[0050] Optionally, the method also includes: receiving second information from the terminal device, the second information being used to indicate at least one of the following: selecting a target EES that supports the target ACR scene, or the currently connected EES or the currently connected EAS cannot perform ACR, or the current application has no corresponding ACR scene.

[0051] The ECS may determine, based on the second information from the terminal device, at least one EES that supports the first ACR scenario, and indicate the at least one EES to the terminal device.

[0052] Fourthly, the present application provides a communication method, which can be applied to EES, can be executed by EES, or can be executed by components configured in EES (such as chips, chip systems, processors, etc.), or can be implemented by logic modules or software that can realize all or part of the EES functions. This application does not limit this.

[0053] The method includes: determining that the current application has no corresponding ACR scenario; sending third information to the terminal device, the third information indicating that the current application has no corresponding ACR scenario, or indicating that the EES or the currently connected EAS cannot perform ACR.

[0054] When the current application has no corresponding ACR scenario, the EES may indicate to the terminal device that the current application has no corresponding ACR scenario.

[0055] In the fifth aspect, the present application provides a communication method, which can be applied to the EES in the above-mentioned fourth aspect, and the method includes: determining ACR based on a first ACR scenario, where the first ACR scenario is a scenario in which ACR is executed by a target EES; sending fourth information to a terminal device, where the fourth information is used to indicate the selection of a target EES that supports the first ACR scenario, or to indicate that the first ACR scenario is the ACR scenario corresponding to the current application.

[0056] Optionally, before determining to perform ACR based on the first ACR scenario, the method further includes: determining that the current application has no corresponding ACR scenario.

[0057] The EES may determine to perform ACR based on the first ACR scenario, and indicate to the terminal device that the first ACR scenario is the ACR scenario corresponding to the current application, that is, ACR needs to be performed based on the first ACR scenario when performing EAS switching.

[0058] EES can determine to perform ACR based on the first ACR scenario when the current application has no corresponding ACR scenario, and can also determine to perform ACR based on the first ACR scenario in other situations. For example, when the EES and EAS currently connected to the terminal device both support ACR, EES can also determine to perform ACR based on the first ACR scenario.

[0059] In the sixth aspect, the present application provides a communication method, which can be applied to the EES in the above-mentioned fourth aspect, and the method includes: sending EAS information to the terminal device, where the EAS information indicates at least one EAS; and sending fifth information to the terminal device, where the fifth information indicates the ACR capability of the at least one EAS.

[0060] The EES may send EAS information and fifth information to the terminal device, indicating at least one EAS and the ACR capability of the at least one EAS, so that the terminal device can determine a target EAS that supports the first ACR scenario based on the ACR capability of the EAS.

[0061] Optionally, the method further includes: receiving sixth information from the terminal device, where the sixth information is used to indicate a request to obtain the ACR capability of the EAS.

[0062] The EES may send the EAS information and the fifth information to the terminal device based on the sixth information from the terminal device.

[0063] In the seventh aspect, the present application provides a communication method, which can be applied to the EES in the fourth aspect above, and the method includes: determining at least one EAS that supports a first ACR scenario; the first ACR scenario is a scenario in which ACR is performed by the target EES; and sending EAS information to a terminal device, where the EAS information indicates the at least one EAS.

[0064] The EES may determine at least one EAS that supports the first ACR scenario and indicate it to the terminal device, so that the terminal device may select any one of them as a target EAS.

[0065] Optionally, the method further includes: receiving sixth information from the terminal device, the sixth information being used to indicate at least one of the following: selecting a target EAS that supports the first ACR scenario, or the source EES and source EAS are unable to perform ACR, or the current application has no corresponding ACR scenario.

[0066] The EES may determine at least one EAS that supports the first ACR scenario based on the sixth information from the terminal device, and indicate the at least one EAS information to the terminal device.

[0067] In an eighth aspect, the present application provides an EEC context transmission method, which can be applied to the terminal device in the aforementioned first aspect, and the method includes: obtaining the EEC context transmission capability of the source EES; determining the target EES, and the target EES is determined based on the EEC context transmission capability of the source EES.

[0068] The EEC context transmission capability includes whether the EES supports the transmission of the EEC context and the supported EEC context transmission process.

[0069] When performing EAS handover, the target EES needs to be determined first. The terminal device can determine the target EES based on whether the source EES supports EEC context transfer and the EEC context transfer process supported by the source EES.

[0070] In this way, the terminal device can determine the target EES that supports the corresponding EEC context transmission capability as the source EES, so that the EEC context can be transferred between the source EES and the target EES. The target EES can obtain the EEC context and, based on the EEC context, provide the terminal device with information that can be used in edge computing services, so that the terminal device's application services can proceed normally.

[0071] Optionally, acquiring the EEC context transmission capability of the source EES includes: receiving first capability information from the source EES, where the first capability information indicates the EEC context transmission capability of the source EES.

[0072] The terminal device may determine whether the source EES supports EEC context transfer based on the information obtained from the source EES. If the source EES supports EEC context transfer, the terminal device may also determine the EEC context transfer process supported by the source EES.

[0073] The EEC context transmission process may include an EEC context pull process and / or an EEC context push process.

[0074] In conjunction with the eighth aspect, in certain possible implementations of the eighth aspect, the source EES supports EEC context transfer. Determining a target EES based on the EEC context transfer capability of the source EES includes: receiving EES information from an ECS, the EES information indicating at least one EES; receiving second capability information from the ECS, the second capability information indicating the EEC context transfer capability of the at least one EES; and determining the target EES from the at least one EES.

[0075] When the source EES supports EEC context transfer, the terminal device may select an EES that supports the corresponding EEC context transfer process as the target EES from at least one EES indicated by the ECS.

[0076] In this way, the EEC context can be transmitted smoothly between the source EES and the target EES, and the target EES can successfully obtain the EEC context, thereby providing the terminal device with information that can be used in the edge computing service, so that the application business of the terminal device can proceed normally.

[0077] Optionally, before receiving the EES information from the ECS, the method further includes sending first request information to the ECS, where the first request information indicates at least one of the following: the source EES supports EEC context transfer, or requests to obtain the EEC context transfer capability of the EES.

[0078] The ECS may send the second capability information to the terminal device after receiving the first request information from the terminal device.

[0079] Optionally, the target EES and the source EES do not support the corresponding EEC context transfer process. The terminal device may select an EES from the at least one EES that does not support the corresponding EEC context transfer process with the source EES as the target EES.

[0080] Optionally, the method further includes determining that re-registration with the target EES is required.

[0081] When the target EES and the source EES do not support the corresponding EEC context transfer process, the terminal device can determine that it needs to re-register with the target EES, so that when the target EES and the source EES cannot perform EEC context transfer, the target EES can also obtain EEC information from the terminal device and generate EEC context based on the EEC information.

[0082] In combination with the eighth aspect, in some possible implementations of the eighth aspect, the source EES supports EEC context transfer; determining the target EES based on the EEC context transfer capability of the source EES includes: sending third capability information to the ECS, where the third capability information is used to indicate the EEC context transfer process supported by the source EES; receiving EES information from the ECS, where the EES information indicates at least one EES; and determining the target EES from the at least one EES.

[0083] The ECS can determine the EEC context transfer process supported by the source EES based on the third capability information from the terminal device, so that the ECS can select at least one EES based on the EEC context transfer process supported by the source EES, and send EES information to the terminal device to indicate the at least one EES, so that the terminal device can determine the target EES therefrom.

[0084] The at least one EES selected by the ECS may be an EES that supports the EEC context transmission capability corresponding to that of the source EES, or may be an EES that does not support the EEC context transmission capability corresponding to that of the source EES.

[0085] For example, if there is an EES managed by the ECS that supports the EEC context transfer capability corresponding to that of the source EES, the ECS may select at least one EES therefrom. If there is no EES managed by the ECS that supports the EEC context transfer capability corresponding to that of the source EES, the ECS may select at least one EES that does not support the EEC context transfer capability corresponding to that of the source EES.

[0086] Optionally, the method further includes receiving registration indication information from the ECS.

[0087] When the EES selected by the ECS does not support the corresponding EEC context transfer process with the source EES, the ECS may send a registration indication message to the terminal device, indicating that it needs to re-register with the target EES. The terminal device may determine that it needs to re-register with the target EES based on the registration indication message.

[0088] When the EES selected by the ECS supports the corresponding EEC context transfer process with the source EES, the ECS may send a registration indication message to the terminal device, indicating that it does not need to re-register with the target EES. The terminal device may determine that it does not need to re-register with the target EES based on the registration indication message.

[0089] In this way, when the target EES and the source EES cannot transfer the EEC context, the target EES can obtain EEC information from the terminal device through the EEC registration process to generate an EEC context. When the target EES and the source EES can transfer the EEC context, the terminal device does not need to register with the target EEC, thus avoiding redundant operations.

[0090] In the above solution, the step of selecting an EES with corresponding EEC context transmission capability to the source EES from the EES can be performed by the ECS. In this way, when the terminal device determines the target EES, it is not necessary to screen based on the EEC context transmission capability of the EES, which can reduce the burden on the terminal device.

[0091] In combination with the eighth aspect, in some possible implementations of the eighth aspect, the source EES supports EEC context transmission; after determining the target EES, the method further includes: sending fourth capability information to the target EES, the fourth capability information indicating the EEC context transmission capability of the source EES; receiving registration indication information from the target EES, the registration indication information indicating whether re-registration with the target EES is required.

[0092] When the source EES supports EEC context transfer, the terminal device can send information to the target EES indicating that the source EES supports the EEC context transfer process. After receiving the fourth capability information, the target EES can determine whether the target EES supports the corresponding EEC context transfer capability as the source EES.

[0093] When the target EES and the source EES support corresponding EEC context transmission capabilities, the target EES may send registration indication information to the terminal device, indicating that the terminal device does not need to re-register with the target EES.

[0094] When the target EES and the source EES do not support corresponding EEC context transmission capabilities, the target EES may send registration indication information to the terminal device, indicating that the terminal device needs to re-register with the target EES.

[0095] In this way, when the target EES and the source EES cannot transfer the EEC context, the target EES can instruct the terminal device to re-register with the target EES, so that the target EES can obtain EEC information, generate EEC context, and then provide the terminal device with information that can be used in edge computing services, so that the terminal device's application business can proceed normally. When the target EES and the source EES can transfer the EEC context, the target EES can instruct the terminal device not to register with the target EEC, thus avoiding redundant operations.

[0096] In combination with the eighth aspect, in some possible implementations of the eighth aspect, after determining the target EES, the method further includes: receiving fifth capability information from the target EES, the fifth capability information indicating the EEC context transmission capability of the target EES; and determining whether re-registration is required based on the EEC context transmission capability of the target EES.

[0097] The target EES may indicate the EEC context transmission capability of the target EES to the terminal device, so that the terminal device may determine whether the target EES supports the corresponding EEC context transmission capability as the source EES.

[0098] When the source EES supports EEC context transfer, and the target EES and the source EES support corresponding EEC context transfer capabilities, the terminal device may determine that it does not need to re-register with the target EES.

[0099] When the target EES and the source EES do not support corresponding EEC context transmission capabilities, or the source EES does not support EEC context transmission, the terminal device may determine that it needs to re-register with the target EES.

[0100] Optionally, the method further includes: sending second request information to the target EES, where the second request information indicates a request to obtain the EEC context transmission capability of the EES.

[0101] The target EES may send the fifth capability information to the terminal device after receiving the second request information from the terminal device.

[0102] In the above solution, the step of determining whether the target EES supports the corresponding EEC context transmission capability as the source EES can be performed by the terminal device, and the terminal device then determines whether it needs to re-register with the target EES. In this way, the target EES does not need to make any judgment, which can reduce the burden on the target EES.

[0103] In a ninth aspect, the present application provides a communication device that can implement the methods performed by the terminal device in the above aspects, or can implement the methods performed by the ECS in the above aspects, or can implement the methods performed by the EES in the above aspects. The device includes corresponding units or modules for performing the above methods. The units or modules included in the device can be implemented in software and / or hardware.

[0104] In a tenth aspect, the present application provides a communication device comprising a processor, which can implement the method executed by the terminal device in the above aspects, or can implement the method executed by the ECS in the above aspects, or can implement the method executed by the EES in the above aspects.

[0105] Optionally, the device may further include a memory for storing instructions and data. The memory is coupled to the processor, and when the processor executes the instructions stored in the memory, the methods described in the above aspects may be implemented.

[0106] Optionally, the apparatus may further include a communication interface, which is used for the apparatus to communicate with other devices. Exemplarily, the communication interface may be a transceiver, a circuit, a bus, a module, or other types of communication interfaces.

[0107] In the eleventh aspect, the present application provides a communication system comprising at least one of a source EES and a target EES, wherein the source EES is used to implement the method performed by the EES in the aforementioned fourth aspect or fifth aspect, and the target EES is used to implement the method performed by the EES in the aforementioned sixth aspect or seventh aspect.

[0108] Optionally, the communication system further includes an ECS, which is used to implement the methods performed by the ECS in the aforementioned aspects.

[0109] Optionally, the communication system further includes a terminal device, which is used to implement the methods executed by the terminal device in the aforementioned aspects.

[0110] In the twelfth aspect, the present application provides a chip system comprising at least one processor for supporting the functions involved in the methods executed by the terminal device in the above aspects, or for supporting the functions involved in the methods executed by the ECS in the above aspects, or for supporting the functions involved in the methods executed by the EES in the above aspects, for example, receiving or processing the data and / or information involved in the above methods.

[0111] In one possible design, the chip system further includes a memory, which is used to store program instructions and data, and the memory is located inside or outside the processor.

[0112] The chip system can be composed of chips, or can include chips and other discrete devices.

[0113] In the thirteenth aspect, the present application provides a computer-readable storage medium, including a computer program, which, when executed, enables the method executed by the terminal device in the above aspects to be implemented, or enables the method executed by the ECS in the above aspects to be implemented, or enables the method executed by the EES in the above aspects to be implemented.

[0114] In the fourteenth aspect, the present application provides a computer program product, which includes: a computer program (also referred to as code, or instructions), which, when run, enables the method executed by the terminal device in the above aspects to be implemented, or enables the method executed by the ECS in the above aspects to be implemented, or enables the method executed by the EES in the above aspects to be implemented.

[0115] It should be understood that the second to fourteenth aspects of the present application correspond to the technical solutions of the first aspect of the present application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation methods are similar and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0116] FIG1 is an architecture of a possible communication system applicable to the application context migration method provided in an embodiment of the present application;

[0117] FIG2 is a schematic diagram of a scenario applicable to the ACR method provided in an embodiment of the present application;

[0118] FIG3 is a schematic flow chart of the ACR method provided in an embodiment of the present application;

[0119] FIG4 is a schematic flow chart of a method for determining a target EES by an EEC according to an embodiment of the present application;

[0120] FIG5 is a schematic diagram of the process of EAS registering with EES and ECS respectively;

[0121] FIG6 is a schematic diagram of a process of an EEC requesting a target EES to perform ACR according to an embodiment of the present application;

[0122] FIG7 is a schematic diagram of a method for an EEC to determine a target EAS according to an embodiment of the present application;

[0123] FIG8 is a possible implementation of the application context migration method provided in an embodiment of the present application;

[0124] FIG9 is another possible implementation of the application context migration method provided in an embodiment of the present application;

[0125] FIG10 is another possible implementation of the application context migration method provided in an embodiment of the present application;

[0126] FIG11 is another possible implementation of the application context migration method provided in an embodiment of the present application;

[0127] FIG12 is a schematic diagram of the EEC registration process provided in an embodiment of the present application;

[0128] 13 is a schematic diagram of an EEC context pull process and an EEC context push process provided in an embodiment of the present application;

[0129] FIG14 is a schematic flowchart of an EEC context transmission method provided in an embodiment of the present application;

[0130] FIG15 is a schematic flowchart of a method for determining a target EES according to an embodiment of the present application;

[0131] FIG16 is a schematic flowchart of a method for determining whether to perform EEC context transfer according to an embodiment of the present application;

[0132] FIG17 is a possible implementation of the EEC context migration method provided in an embodiment of the present application;

[0133] FIG18 is another possible implementation of the EEC context migration method provided in an embodiment of the present application;

[0134] FIG19 is a schematic block diagram of a communication device provided in an embodiment of the present application;

[0135] Figure 20 is another schematic block diagram of the communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0136] The technical solution in this application will be described below with reference to the accompanying drawings.

[0137] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) mobile communication system, new radio access technology (NR) system, long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile telecommunication system (UMTS), or world-wide interoperability for microwave access (WiMAX) communication system. Among them, the mobile communication system may include non-standalone (NSA) and / or standalone (SA). The technical solutions provided in the present application can also be applied to future communication systems, such as the sixth generation mobile communication system. This application is not limited to this.

[0138] The technical solution provided in this application can also be applied to machine type communication (MTC), long term evolution technology for machine-to-machine communication (LTE-M), device-to-device (D2D) network, machine-to-machine (M2M) network, internet of things (IoT) network or other networks. Among them, IoT network can include, for example, Internet of Vehicles. Among them, the communication mode in the Internet of Vehicles system is collectively referred to as vehicle to other devices (vehicle to X, V2X, X can represent anything), for example, the V2X can include: vehicle to vehicle (V2V) communication, vehicle to infrastructure (V2I) communication, vehicle to pedestrian (V2P) communication or vehicle to network (V2N) communication, etc.

[0139] The technical solution of this application can be applied to various communication scenarios, such as service continuity scenarios, multi-access edge computing (MEC) scenarios, etc., and this application does not impose any restrictions on this.

[0140] FIG1 shows the architecture of a possible communication system applicable to the application context migration method provided in an embodiment of the present application.

[0141] In the MEC research of the service & system aspects (SA) working group of the 3rd generation partnership project (3GPP), the architecture shown in Figure 1 is defined.

[0142] As shown in Figure 1, the communication system includes terminal equipment, a core network, an EDN, and an ECS.

[0143] Among them, the terminal device can be configured with one or more application clients (AC) and one or more edge enabler clients (EEC), and the EDN can be deployed with one or more EAS and one or more EES.

[0144] The architecture of Figure 1 also includes reference points EDGE-1 to EDGE-9. The EDGE-1 reference point supports interaction between EES and EEC; the EDGE-2 reference point supports interaction between EES and the core network; the EDGE-3 reference point supports interaction between EES and EAS; the EDGE-4 reference point supports interaction between ECS and EEC; the EDGE-5 reference point supports interaction between AC and EEC; the EDGE-6 reference point supports interaction between ECS and EES; the EDGE-7 reference point supports interaction between EAS and the core network; the EDGE-8 reference point supports interaction between ECS and the core network; and the EDGE-9 reference point supports interaction between two EESs in the same or different MEC nodes.

[0145] It should be understood that FIG1 is for illustration only, and the communication system may further include other devices which are not shown in FIG1 .

[0146] It should be noted that the names of the various network elements and the communication interfaces between network elements involved in Figure 1 are simply described using the current protocol as an example, but do not limit the application of the embodiments of the present application to only currently known communication systems. Therefore, the standard names that appear when describing the current protocol as an example are all functional descriptions. This application does not limit the specific names of network elements, interfaces, information, messages, or signaling, but only represents the functions of network elements, interfaces, information, messages, or signaling, which can be correspondingly extended to other systems, such as 4G or future communication systems.

[0147] For ease of understanding, the following is a brief introduction to some network elements and terms involved in this application:

[0148] 1. Edge computing: This refers to an open platform integrating core networking, computing, storage, and application capabilities at the edge of the network, close to the source of objects or data. This platform provides local edge intelligence services to meet key industry digitalization needs in areas such as agile connectivity, real-time services, data optimization, application intelligence, and security and privacy protection. In other words, edge computing analyzes data collected from terminal devices directly on local devices or networks close to where the data is generated, eliminating the need to transmit the data to cloud-based data processing centers.

[0149] 2. Multi-access Edge Computing (MEC): Also known as mobile edge computing, it leverages wireless access networks to provide services and cloud computing capabilities locally, creating a carrier-grade service environment with high performance, low latency, and high bandwidth. This accelerates the download of content, services, and applications across the network, allowing consumers to enjoy an uninterrupted, high-quality network experience.

[0150] 3. Data network (DN): refers to the service network of operators or third parties, which can provide services to terminal devices, such as operator services, Internet services, etc.

[0151] 4. Local area data network (LADN): An access point to a data network that is very close to the user's attachment point.

[0152] 5. Edge Data Network (EDN): In one understanding, an EDN is a specialized local data network that includes edge-enabling capabilities. It can be identified using a data network access identifier (DNAI) and a data network name (DNN), and is a network logical concept. Another understanding is that an EDN is the equivalent of a central cloud, a local data center, identified using a DNAI, and can include multiple local data networks.

[0153] 6. Application Instance / Edge Application (EAS): This refers to an application deployed in an edge data network. Specifically, it can refer to a server application (for example, social media software, augmented reality (AR), virtual reality (VR)), or an instance deployed and running in an EDN. An application can deploy one or more EASs in one or more EDNs. EASs deployed and running in different EDNs can be considered different EASs for the same application. They can share a domain name and use a single Internet Protocol (IP) address or different IP addresses.

[0154] In addition, application instance / edge application can also be called edge application (server), application instance, edge application instance, MEC application (server), EAS function, etc.

[0155] 7. Application Client (AC): This refers to the peer entity of the edge application on the terminal device side. The application client is used by the application user to obtain application services from the application server. The application client is a client program applied on the terminal device side. 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.

[0156] 8. Edge Enabling Server (EES): This server provides enabling capabilities for EAS deployed in the EDN, better supporting the deployment of applications in the MEC. For example, the EES supports application registration, authentication and authorization of terminal devices, and provides EAS IP address information to terminal devices. The EES also supports obtaining EAS identification and IP address information and sending the EAS identification and IP address information to the ECS.

[0157] An EES is deployed in an EDN. Generally, an EAS is registered with an EES, or an EAS's information is configured on an EES through a management system. An EES can have one or more EASs registered with it or have information configured on it. This EES is called the EES associated with the one or more EASs. An EES can control, manage, register, or configure the EASs associated with it.

[0158] 9. Edge Enablement Client (EEC): Provides the support functions required by the AC and is the EES's counterpart on the terminal device side. The EEC is used to register EEC information and AC information with the EES, perform security authentication and authorization, obtain the EAS IP address from the EES, and provide edge computing capabilities to the AC. For example, if an EAS is available in the EDN, it will return the EAS IP address to the AC.

[0159] 10. Edge Configuration Server (ECS): Responsible for EDN configuration, such as providing EES information to end devices. It also provides application instance information directly to end devices and interacts with the application's DNS to obtain application instance information. It further obtains and stores application instance and IP address information from other functional entities.

[0160] It is also responsible for maintaining information about each EDN, including the EDN's service area and EES address. The EDN's service area can be topological address information (such as cell identity, tracking area identity (TAI)), or geometric address information (such as province, city, district, or longitude and latitude). The service area can be a collection of address information.

[0161] ECS can be deployed in the mobile network operator (MNO) domain or in a third-party domain by a service provider. In one implementation, ECS network elements are deployed in a distributed manner, that is, each ECS can manage edge data networks in different regions. It should be understood that ECS network elements can be co-located with other network elements or can be independent network elements. This application does not impose any restrictions on the deployment of ECS network elements in the network architecture.

[0162] 11. Terminal device: Also known as user equipment (UE), mobile station (MS), or mobile terminal (MT), this device provides voice or data services to users and can also be an IoT device. Examples of terminal devices include handheld devices and vehicle-mounted devices with wireless transceiver capabilities. At present, terminal devices can be: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices (such as smart watches, smart bracelets, smart glasses, etc.), vehicle-mounted devices (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed railways, etc.), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, smart home devices (such as refrigerators, TVs, air conditioners, electric meters, etc.), intelligent robots, workshop equipment, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, flight equipment (such as intelligent robots, hot air balloons, drones, airplanes), etc. In addition, the terminal device can also be a chip. This application does not limit the specific form of the terminal device.

[0163] 12. Core Network: Mainly used to manage terminal devices and provide communication with external networks. The core network may include at least one of the following network elements: user plane function (UPF), access and mobility management function (AMF), session management function module (SMF), unified data management (UDM), or policy control function (PCF). For the functions of the network elements included in the core network, reference may be made to the standards defined by 3GPP (e.g., TS 23.501).

[0164] 13. Application context: This refers to operational status information related to one or a group of users, such as game progress and historical data. Optionally, the application context may also include the subscription context of the one or more users in the EAS and the core network, such as the subscription transaction identifier. Optionally, the application context may also include the context of the one or more users on the EES, such as the transaction identifier of the EAS subscription to the one or more users.

[0165] 14. EEC Context: EEC context refers to user-related data stored in the EES. EEC context may include EEC-side information and EAS-EES subscription information. EEC-side information may include EEC registration information and EEC subscription information (e.g., EAS discovery subscription, EAS dynamic information subscription, etc.); EAS-EES subscription information may include terminal device location API, application context migration events, AC information exposure API, terminal device identification API, and quality of service (QoS) session API, etc.

[0166] 15. Application Context Migration (ACR): Also known as application migration or application context relocation, it is the process of migrating application contexts between EASs.

[0167] The ACR process can be divided into the following four stages:

[0168] Phase 1: Detection of ACR.

[0169] At this stage, it can be determined whether context migration is required. The detection entity can detect events that require ACR, such as changes in terminal location and updates to the terminal user plane path.

[0170] Phase 2: ACR decision-making.

[0171] During this phase, the decision-making entity determines that a context transfer is required.

[0172] Phase 3: Execution of ACR.

[0173] In this phase, the execution entity transfers the application context from the source EAS to the target EAS. Furthermore, including the discovery of the target EAS, the terminal device can be notified of relevant information about the target EAS, the EAS (which can be the source EAS or the target EAS) can be notified to initiate application context transfer (ACT), the EES or EAS performs application function (AF) traffic influence and carries the N6 routing information of the target EAS.

[0174] Phase 4: Cleanup after ACR.

[0175] At this stage, multiple entities are involved, including the EAS notifying the EEC of the ACT result through the EES, and the AC initiating a new socket connection to the target EAS.

[0176] 16. ACR Scenario: A specific solution for detecting and executing ACRs, including steps such as ACR detection, ACR decision-making, ACR execution, and post-ACR cleanup. The ACR scenario involves the entities that perform each step. Currently, there are multiple ACR scenarios. Table 1 shows the corresponding ACR solutions for these scenarios.

[0177] Table 1

[0178] It should be understood that the five ACR scenarios shown in Table 1 are only examples of ACR scenarios, and the names of the scenarios are only given for reference and cannot be a limitation to this application. For the specific content of the ACR scenarios, please refer to the standards defined by 3GPP (for example, TS23.588).

[0179] 17. ACR Capabilities: The ACR capabilities in the embodiments of this application may include, but are not limited to, whether ACR is supported, whether the first ACR scenario is supported, supported ACR scenarios, and supported ACR APIs. Based on the ACR capabilities of EES, the ACR scenarios supported by EES can be determined, and based on the ACR capabilities of EAS, the ACR scenarios supported by EAS can be determined.

[0180] In some embodiments of the present application, the ACR capability of an EES may also include the EEC context transmission capability of the EES. The EEC context transmission capability of the EES includes whether the EES supports EEC context transmission, whether the EES supports the EEC context pull process, and whether the EES supports the EEC context push process. When the EES supports EEC context transmission, the EEC context transmission capability corresponding to the EES also includes the EEC context transmission process supported by the EES. The EEC context transmission capability can be indicated by the API information supported by the EES.

[0181] In the embodiments of this application, an AC and EEC can be configured on a terminal device. Application users sign a service agreement with the application provider and can log in to the AC corresponding to the application on the terminal device. Through the AC's connection with the EAS, communication is established to access the application's services. The EEC is a middleware layer, typically located within the operating system or between the AC and the operating system. The AC can obtain edge-enabled services from the EEC via an API.

[0182] In edge computing, the EAS that provides application services can be deployed in an EDN near the terminal device. Application data in the terminal device can be processed in real time in the EAS close to the terminal device, without having to transmit the data to the central cloud for processing, thus reducing the latency caused by data transmission.

[0183] The same application can be deployed in multiple EDNs. EAS for the same application deployed in different EDNs can provide the same services and have functional equivalence.

[0184] For example, the server for application a can be deployed in EDN-1 in location A and EDN-2 in location B. The terminal device in location A can be configured with the AC for application a and can obtain application services through the EAS in the nearby EDN-1. The terminal device in location B can also be configured with the AC for application a and can obtain application services through the EAS in the nearby EDN-2.

[0185] After accessing the network, a terminal device will select an EAS deployed in the nearest EDN to perform services. If a terminal device moves from one EDN's service area to another, or the EAS to which the terminal device is currently connected is fully loaded, the EAS to which the terminal device is currently connected may no longer be able to provide adequate services for the terminal device. To meet the application's business continuity requirements, a new EAS must be selected for the terminal device to continue providing services.

[0186] When the application service of the terminal device is switched between EASs, the context of the application of the terminal device needs to be migrated between EASs.

[0187] FIG2 is a schematic diagram of a scenario applicable to the ACR method provided in an embodiment of the present application.

[0188] As shown in Figure 2, EES1, EAS1, and EAS2 can be deployed in EDN1, and EES2 and EAS2 can be deployed in EDN2. EAS2 in EDN1 and EDN2 can provide services for the current application to the terminal device. The EAS currently providing services to the terminal device is EAS2 in EDN1. When the terminal device moves from the service area of ​​EDN1 to the service area of ​​EDN2, or when EAS2 in EDN1 is fully loaded, EAS2 in EDN1 will no longer be able to provide application services to the terminal device. In this case, the application business of the current application can be switched to EAS2 in EDN2, and the context of the current application of the terminal device needs to be synchronously migrated from EAS2 in EDN1 to EAS2 in EDN2.

[0189] It should be understood that the scenario shown in Figure 2 is merely an example and does not constitute any limitation to this application. An application can deploy EAS in more or fewer EDNs, each with its own service area. An EDN can also deploy EAS for multiple applications.

[0190] For the convenience of description, in the embodiments of the present application, the EAS currently providing application services to the terminal device is referred to as the source EAS (source EAS, S-EAS), or the currently connected EAS, such as EAS2 in EDN1 in Figure 2; the EES associated with the source EAS is referred to as the source EES (source EES, S-EES), or the currently connected EES, such as EES1 in Figure 2; after the application service of the terminal device is switched, the new EAS that provides application services to the terminal device is referred to as the target EAS (target EAS, T-EAS), such as EAS2 in EDN2 in Figure 2, and the EES associated with the target EAS is referred to as the target EES (target EES, T-EES), such as EES2 in Figure 2.

[0191] After the terminal device is connected to the EAS, it needs to negotiate with the EAS and the EES associated with the EAS to determine the ACR scenario of the application, so that the application can perform ACR detection, decision-making and execution processes based on the determined ACR scenario, so as to complete the switching process when the application's business needs to switch between EASs.

[0192] When the terminal device, the EAS currently connected to the terminal device (or selected by the terminal device), and the EES associated with the EAS do not have a commonly supported ACR scenario, for example, the EEC, EAS, or EES do not support the execution of ACR, it is impossible to negotiate and determine the ACR scenario of the current application. Therefore, when the EAS currently providing application services to the terminal device is fully loaded, or the terminal device leaves the service area of ​​the EDN where the EAS is located, the current application cannot implement ACR, and the smooth switching of the EAS cannot be completed.

[0193] To this end, the present application provides an ACR method, which determines a target EES that supports executing ACR and executes ACR based on the target EES, thereby completing the migration of the context of the current application.

[0194] In this way, the context of the current application can be migrated through the target EES. When the current application has no corresponding ACR scenario, for example, when the terminal device, the EAS currently connected to the terminal device (or selected by the terminal device), and the EES associated with the EAS do not have a commonly supported ACR scenario, the context of the current application can also be migrated. When the EAS currently connected to the terminal device can no longer provide application services, the smooth switching of the EAS can be guaranteed, thereby ensuring the stability and continuity of the application business.

[0195] The application context migration method provided by this application is described below with reference to FIG. 3 to FIG. 11 .

[0196] In order to better understand the embodiments of the present application, the following points are first explained:

[0197] First, to facilitate a clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. For example, the first information and the second information are merely used to distinguish different information and do not limit their order. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity or execution order, and words such as "first" and "second" do not necessarily mean that they are different.

[0198] Second, in the embodiments of this application, various terms and abbreviations, such as edge application server, edge enabling server, application context migration, EEC, EES, source EES, target EES, EAS, source EAS, target EAS, ACR, etc., are provided for convenience of description and should not limit this application in any way. This application does not exclude the possibility of defining other terms in existing or future protocols that can achieve the same or similar functions.

[0199] Third, "at least one" means one or more, and "more" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c, where a, b, c can be single or multiple.

[0200] Fourth, the tables in the embodiments of the present application are only examples and do not limit the scope of protection of the present application. For example, the values ​​of the information in the table are only examples and can be configured as other values, which are not limited by the present application. For another example, appropriate deformation adjustments can be made based on the tables in the text, such as splitting, merging, etc. For another example, the parameter names shown in the titles of the tables can also adopt other names that can be understood by the communication device, and the values ​​or representations of the parameters can also adopt other values ​​or representations that can be understood by the communication device. For another example, when implementing the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables.

[0201] Fifth, "pre-definition" or "pre-configuration" can be achieved by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and an ECS), and this application does not limit its specific implementation method. Among them, "saving" can mean saving in one or more memories. The one or more memories can be set separately or integrated in an encoder or decoder, a processor, or a communication device. The one or more memories can also be partially set separately and partially integrated in a decoder, a processor, or a communication device. The type of memory can be any form of storage medium, which is not limited by this application.

[0202] Sixth, in the embodiments of the present application, descriptions such as "when...", "in the case of...", "if" and "if" all mean that the device (such as the terminal device or EES described below) will perform corresponding processing under certain objective circumstances. It does not limit the time, and does not require the device (such as the terminal device or EES described below) to perform a judgment action when implementing it, nor does it mean that there are other limitations.

[0203] Seventh, in this application, "sending information to... (terminal)" can be understood as the destination of the information being the terminal. This can include sending information to the terminal directly or indirectly. "Receiving information from... (terminal)" can be understood as the source of the information being the terminal, which can include receiving information from the terminal directly or indirectly. The information may undergo necessary processing between the source and destination of the information, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be understood similarly and will not be repeated here.

[0204] Eighth, the examples of messages carrying information in this application are for illustrative purposes only. For example, the phrase "the second information may be carried in the aforementioned service activation request message" below should be understood to mean that the second information may be carried in the service activation request message or in other messages. Similar expressions in this application should be interpreted similarly. This application does not limit the type of message used to carry information, and the names of the messages carrying information are provided for illustrative purposes only and are not intended to be limiting.

[0205] Ninth, the various embodiments in this application can be implemented individually or in combination, and this application does not limit this.

[0206] FIG3 is a schematic flow chart of the ACR method provided in an embodiment of the present application.

[0207] The method shown in Figure 3 illustrates the ACR method provided by an embodiment of the present application from the perspective of a terminal device. The method can be executed by the terminal device or by a component (such as a circuit, chip, chip system, etc.) in the terminal device, and can be implemented in software and / or hardware. This application is not limited to this. The following description takes the EEC configured in the terminal device as an example.

[0208] 3 , method 300 includes step 310 and step 320 .

[0209] In step 310 , the EEC determines a target EES, where the target EES is an EES that supports a first ACR scenario, where the first ACR scenario is a scenario in which ACR is performed by the target EES.

[0210] The first ACR scenario is a scenario where the target EES executes ACR, for example, the scenario "EEC executed ACR via T-EES". In the first ACR scenario, the ACR process may be that the EEC detects an event requiring ACR, decides whether to perform ACR, and the target EES performs ACR.

[0211] It should be understood that the description of the "first ACR scene" in this application is only a schematic for distinction and does not mean a limitation on the name of the ACR scene.

[0212] In the embodiment of the present application, if the EES supports the first ACR scenario, it means that the EES can serve as the target EES to support the execution of the ACR. Correspondingly, if the EAS supports the first ACR scenario, it means that the EAS can serve as the target EAS to support the execution of the ACR.

[0213] The EEC may determine a target EES that supports the first ACR scenario, so that when the EEC requests the target EES to perform ACR, the target EES is capable of performing ACR.

[0214] The EEC can determine the target EES through the service provisioning process or the EES discovery process.

[0215] The following will describe step 310 in detail from the perspective of interaction between network elements in conjunction with FIG. 4 (a) and FIG. 4 (b).

[0216] Figure 4(a) is a schematic diagram of a method for an EEC to determine a target EES through an ECS according to an embodiment of the present application. In method 400a, the EEC determines a target EES that supports a first ACR scenario based on the ACR scenarios supported by the EES. Method 400a may include steps 410a to 440a.

[0217] In step 410a, the EEC sends a service provisioning request message to the ECS.

[0218] The service activation request message may also be called a service configuration request message, which may include an EEC identifier (EEC ID), security credentials, AC configuration information (AC profile), terminal device identification, connection information, and terminal device location, etc. The terminal device identification may include a generic public subscription identifier (GPSI), etc.

[0219] In an embodiment of the present application, the EEC may also send information to the ECS to indicate a request to obtain the ACR capabilities of the EES. For ease of description, in the embodiment of the present application, this information is referred to as second information, but it should be understood that this does not limit the present application. The second information may, for example, be carried in the above-mentioned service activation request message.

[0220] For example, when the current application has no corresponding ACR scene, or the terminal device and EES have not determined an ACR scene through negotiation, the EEC may send the second information to the ECS. When the ACR scene corresponding to the current application is the first ACR scene, the second information may also indicate that the selected ACR scene is the first ACR scene.

[0221] In step 420a, after receiving the service activation request message, the ECS processes the service activation request and determines or identifies one or more EESs.

[0222] In some embodiments, the ECS may perform an authorization check to verify whether the EEC has authorization to perform the operation.

[0223] The ECS can match the EES registered with the ECS based on the AC configuration information and / or the terminal device location information.

[0224] For example, if the check passes, the ECS may select one or more EESs based on the service provisioning request. The ECS may select an EES whose service area includes the location of the terminal device, an EES whose registered EAS list includes an EAS identifier (EAS ID) that matches the AC configuration information, etc.

[0225] In an embodiment of the present application, the ECS may obtain relevant information of one or more EESs. The relevant information of the EES may include information indicating at least one EES, such as a list of EESs, and the relevant information of the EES may also include information indicating the ACR capability of the at least one EES, and may also include information indicating at least one EAS associated with the EES, and information indicating the ACR capability of the at least one EAS.

[0226] EES information can be obtained by ECS when EES registers with it. EES can be registered with ECS, and ECS can store EES information. When EAS determines it needs to register with EES, such as when EAS is configured and started, EAS can also register with EES, and EES can store EAS information.

[0227] In some embodiments, the EES may obtain EAS information through the network management system, and the ECS may also obtain EES-related information through the network management system without performing a registration process. In some embodiments, the ECS may store information about one or more EESs, which may be pre-configured, and the EES may store information about one or more EASs, which may also be pre-configured. This application does not limit this.

[0228] As an example, the process of EAS registering on EES is described below with reference to FIG. 5 (a), and the process of EES registering on ECS is described below with reference to FIG. 5 (b).

[0229] FIG5( a ) is a schematic diagram of the process of EAS registering with EES.

[0230] The EAS registration process may include steps 510a to 530a.

[0231] In step 510a, the EAS sends an EAS registration request message to the EES.

[0232] The EAS registration request message may carry EAS configuration information (EAS profile) and EAS security credentials, and may also include a recommended expiration time for the registration, or the registration validity period.

[0233] In an embodiment of the present application, the EAS may also send information to the EES indicating the ACR capability of the EAS, such as whether the EAS supports ACR or the ACR scenarios supported by the EAS. This information may be carried in the EAS registration request message, for example, it may be included in the EAS configuration information. This information may be represented, for example, by a "service continuity support" parameter.

[0234] In step 520a, the EES processes the registration request.

[0235] EES performs a registration authorization check based on the EAS registration request message to verify whether EAS has the authorization to register on EES.

[0236] After successful authorization, the EES stores the EAS configuration information for future use (eg, to service EAS discovery requests received from the EEC, etc.) The EES may also save the ACR capabilities of the EAS.

[0237] In step 530a, the EES sends an EAS registration response message to the EAS.

[0238] EES responds to EAS with an EAS Registration Response message. If the registration is successful, the EAS Response message may include information indicating the successful registration. EES may also provide an expiration time to indicate to EAS when the registration automatically expires. If the registration fails, the EAS Response message may include information indicating the registration failure and the reason for the failure. Figure 5 (b) shows the process of EES registering with ECS.

[0239] The EES registration process may include steps 510b to 530b.

[0240] In step 510b, the EES sends an EES registration request message to the ECS.

[0241] The EES registration request message may carry the EES configuration information. The EES configuration information may include at least one of the following: the EES identifier, the EES endpoint information, a list of EAS identifiers registered with the EES, and so on. The EES configuration information may also include the EES's security credentials. The EES configuration information may also include the registration expiration date.

[0242] In an embodiment of the present application, the EES may also send information to the ECS to indicate the ACR capability of the EES, such as the ACR scenarios supported by the EES. The information may be carried in an EES registration request message, such as included in the configuration information of the EES.

[0243] The EES may also send information to the ECS indicating the ACR capabilities of the EAS registered with the EES, such as the ACR scenarios supported by the EAS. This information may also be carried in the EES registration request message.

[0244] In step 520b, the ECS processes the registration request.

[0245] After receiving the EES registration request message, the ECS can save the EES configuration information locally. The ECS can also save the ACR capabilities of the EES and the ACR capabilities of the EAS registered with the EES.

[0246] In step 530b, the ECS sends an EES registration response message to the EES.

[0247] After receiving the EES registration request message from EES, ECS can also send a corresponding response message.

[0248] It should be noted that the registration processes shown in (a) of Figure 5 and (b) of Figure 5 may be separate embodiments, and the process of EAS registering with EES, and the process of EES registering with ECS may occur once or multiple times when method 300 is executed, or at any time before method 300 is executed, or at any time after method 300 is executed.

[0249] The EES registration process and the EAS registration process may not be performed consecutively. An EAS can register with the EES at any time interval after the EES registers with the ECS. After the EAS registers with the EES, the EES can register with the ECS at any time interval.

[0250] In step 430a, the ECS sends a service activation response message to the EEC.

[0251] The service activation response message can also be called a service configuration response message. If the ECS cannot determine the EEC information based on the service activation request message, the service activation response message carries an information element instructing the ECS to reject the service activation request of the EEC and give the reason for the failure. If the ECS successfully processes the service activation request of the EEC, the service activation response message can carry EDN connection information, EES information (which may include a list of one or more EESs determined or identified by the ECS, as well as the addresses of the one or more EESs, identification information of the one or more EESs, etc.). The service activation response message can also carry information about the EAS associated with each EES in the one or more EESs determined or identified by the ECS.

[0252] In an embodiment of the present application, the ECS may also send information to the EEC, indicating the ACR capabilities of each EES in one or more EESs identified or determined by the ECS, such as the ACR scenarios supported by the EES. For ease of description, in an embodiment of the present application, this information is referred to as first information, but it should be understood that this does not limit the present application. The first information may be carried in the above-mentioned service activation response message, for example, included in the EES information.

[0253] In some embodiments, the first information may also indicate the ACR capability of the EAS associated with each of the one or more EESs determined or identified by the ECS. In some embodiments, the ECS may send all information about all EESs registered or configured on the ECS to the EEC. In this case, the aforementioned step 420a is optional.

[0254] In step 440a, the EEC determines a target EES that supports the first ACR scenario from one or more EESs.

[0255] The information received by the EEC may indicate one or more EESs and the ACR capabilities of the one or more EESs, and the EEC may select an EES that supports the first ACR scenario as a target EES.

[0256] In some embodiments, the EEC also receives information indicating the EAS associated with the EES and the ACR scenarios supported by the EAS, and the EEC can select an EES associated with the EAS supporting the first ACR scenario as the target EES.

[0257] For example, the target EES determined by the EEC supports the first ACR scenario, and at least one of the EASs associated with the target EES also supports the first ACR scenario.

[0258] In some embodiments, the EES information from the ECS does not include an EES that supports the first ACR scenario, and the EEC cannot determine the target EES.

[0259] Figure 4(b) is another schematic diagram of a method provided by an embodiment of the present application for an EEC to determine a target EES through an ECS. In method 400b, the ECS selects an EES that supports a first ACR scenario based on the ACR scenarios supported by the EES and sends the selected EES to the EEC. Method 400b may include steps 410b to 440b.

[0260] In step 410b, the EEC sends a service activation request message to the ECS. The description of the service activation request message can be found in the aforementioned step 410a and will not be repeated here.

[0261] Optionally, the EEC may further send second information to the ECS, where the second information may indicate at least one of the following: selecting an EES that supports the first ACR scenario, or preferably an EES that supports the first ACR scenario, or the source EES and / or source EAS cannot perform ACR, or the current application has no corresponding ACR scenario. This second information may be carried in the above-mentioned service activation request message, for example.

[0262] For example, when the current application has no corresponding ACR scene, or the terminal device and EES have not determined an ACR scene through negotiation, the EEC may send the second information to the ECS. When the ACR scene corresponding to the current application is the first ACR scene, the second information may also indicate that the selected ACR scene is the first ACR scene.

[0263] In step 420b, after receiving the service activation request message, the ECS processes the service activation request and selects an EES that supports the first ACR scenario.

[0264] Upon receiving the request, the ECS may optionally perform an authorization check to verify whether the EEC has the authorization to perform the operation.

[0265] According to the received information, the ECS may determine that an EES supporting the first ACR scenario needs to be selected. For example, it may be determined that an EES supporting the first ACR scenario needs to be selected based on second information from the ECS.

[0266] Optionally, the ECS may match the EES registered with the ECS according to the AC configuration information and / or the terminal device location information, and select an EES that supports the first ACR scenario based on the ACR scenarios supported by the EES.

[0267] For example, the ECS may select an EES whose service area includes the location of the terminal device, or an EES whose registered EAS list includes an EAS identifier (EAS ID) that matches the AC configuration information, or an EES whose service area includes the location of the terminal device and whose registered EAS list includes an EAS ID that matches the AC configuration information. After selecting one or more EESs, the ECS may further determine one or more EESs that support the first ACR scenario. Alternatively, the ECS may add a condition when selecting an EES, namely, the EES needs to support the first ACR scenario.

[0268] Optionally, the ECS may select an EES associated with an EAS that supports the first ACR scenario. In other words, one or more EESs selected by the ECS support the first ACR scenario, wherein at least one of the EASs associated with each EES also supports the first ACR scenario.

[0269] In step 430b, the ECS sends a service activation response message to the EEC.

[0270] For a detailed description of the corresponding service activation message, please refer to the aforementioned step 430a.

[0271] After the ECS selects, determines or identifies one or more EESs that support the first ACR scenario, it may indicate the one or more EESs through EES information in a service activation response message sent to the EEC.

[0272] In step 440b, the EEC determines the target EES.

[0273] In some embodiments, the information received by the EEC indicates an EES, which the EEC may determine as the target EES. In some embodiments, the information received by the EEC indicates multiple EESs that support the first ACR scenario, from which the EEC may determine an EES as the target EES. This application does not limit the specific determination method, for example, it may be random determination or determination based on local policy.

[0274] In method 400b, step 440b is an optional step.

[0275] (a) in Figure 4 and (b) in Figure 4 provide a method for determining the target EES. The step of determining the EES that supports the first ACR scenario from the EES can be performed by the ECS, so that the terminal device does not have to perform screening, which can reduce the burden on the terminal device; this step can also be performed by the EEC, so that the ECS does not have to perform screening based on the ACR capability of the EES, which can reduce the burden on the ECS.

[0276] Through step 310, the target EES determined by the EEC supports the first ACR scenario. The EES has the ability to perform ACR as a target EES. When the EAS of the current application is switched, the EEC can successfully complete the migration of the application context through the target EES, thereby ensuring the continuity of the current application's business.

[0277] In step 320 , the EEC requests the target EES to perform ACR.

[0278] After the EEC determines the target EES, it can establish a communication connection with the target EES through the address of the target EES obtained from the ECS and request it to perform ACR. The method of the EEC requesting the target EES to perform ACR includes discovering the target EAS and transferring the application context between the target EAS and the source EAS.

[0279] The following will describe step 320 in detail from the perspective of interaction between network elements in conjunction with FIG. 6 .

[0280] 6 , step 320 may further include steps 610 to 650 .

[0281] In step 610 , the EEC may perform an EAS discovery process to determine a target EAS that supports the first ACR scenario.

[0282] Exemplarily, the process of the EEC determining the target EAS may be as shown in FIG. 7( a ) or FIG. 7( b ).

[0283] Figure 7(a) is a schematic diagram of a method for an EEC to determine a target EAS according to an embodiment of the present application. In method 700a, the EEC determines a target EAS that supports a first ACR scenario based on the ACR scenarios supported by the EAS. Method 700a may include steps 710a to 740a.

[0284] In step 710a, the EEC sends an EAS discovery request message to the target EES.

[0285] Optionally, the EAS discovery request message may include the EEC ID and security credentials. The EAS discovery request message may also include an EAS discovery filter. The EAS discovery filter may include EAS filter parameters to retrieve information about a specific EAS or a specific type of EAS (e.g., a gaming application).

[0286] Optionally, the EEC may also send information to the target EES to request the ACR capability of the EAS. For ease of description, in the embodiment of the present application, this information is referred to as sixth information, but it should be understood that this is not a limitation to the present application.

[0287] The sixth information may be carried in the above-mentioned EAS discovery request message, for example, included in the EAS discovery filter. When the ACR scene corresponding to the current application is the first ACR scene, the sixth information may further indicate that the selected ACR scene is the first ACR scene.

[0288] In step 720a, the target EES processes the EAS discovery request and determines or identifies one or more EASs.

[0289] In some embodiments, after receiving the EAS discovery request sent by the EEC, the target EES performs an authorization check and selects one or more EASs.

[0290] Exemplarily, if the target EES determines that the EEC is authorized to discover the requested EAS, the target EES may select one or more EASs based on the provided EAS discovery filter and the location of the terminal device. If no EAS discovery filter is provided in the EAS discovery request message, the target EES may select one or more EASs based on the terminal device-specific service information and the terminal device location on the target EES, or the target EES may select one or more EASs by applying an edge computing service provider (ECSP) policy (for example, based only on the terminal device location). If the target EES cannot select one or more EASs based on the information carried in the EAS discovery request message, the terminal device-specific service information and the terminal device location on the target EES, or the ECSP policy, the target EES may reject the EAS discovery request of the EEC and give the corresponding failure reason.

[0291] In step 730a, the target EES sends an EAS discovery response message to the EEC.

[0292] If the target EES successfully determines or identifies one or more EASs, the EAS discovery response message may include EAS information (which may include a list of EASs determined or identified by the EES, as well as EAS configuration information, etc.). The EAS information may indicate the one or more EASs determined or identified by the target EES. If the target EES cannot determine or identify one or more EASs, the EAS discovery response message may include a failure indication and the reason for the failure.

[0293] In an embodiment of the present application, the target EES may also send information to the EEC indicating the ACR capabilities of each of the one or more EASs determined or identified by the target EES, such as the ACR scenarios supported by the EAS. For ease of description, in an embodiment of the present application, this information is referred to as fifth information, but it should be understood that this does not limit the present application. The fifth information may be carried in the above-mentioned EAS discovery response message, for example, included in the EAS information.

[0294] In some embodiments, the target EES may send all information of the EAS registered or configured on the target EES to the EEC. In this case, the aforementioned step 720a is optional.

[0295] In step 740a, the EEC determines a target EAS that supports the first ACR scenario from among one or more EASs.

[0296] The information received by the EEC may indicate one or more EASs and the ACR capabilities of the one or more EASs, and the EEC may select an EAS that supports the first ACR scenario as a target EAS.

[0297] Figure 7(b) is another schematic diagram of a method for an EEC to determine a target EAS according to an embodiment of the present application. In method 700b, the target EES selects an EAS that supports a first ACR scenario based on the ACR scenarios supported by the EAS and sends the selected EAS to the EEC. Method 700b may include steps 710b to 740b.

[0298] In step 710b, the EEC sends an EAS discovery request message to the target EES.

[0299] For the description of the EAS discovery request message, please refer to the aforementioned step 710a, which will not be repeated here.

[0300] Optionally, the EEC may further send sixth information to the target EES, where the sixth information may indicate at least one of the following: selecting an EAS that supports the first ACR scenario, or preferably an EAS that supports the first ACR scenario, or the source EES and / or source EAS cannot perform ACR, or the current application has no corresponding ACR scenario. The sixth information may be carried in the above-mentioned service activation request message, for example.

[0301] When the ACR scenario corresponding to the current application is the first ACR scenario, the second information may further indicate that the selected ACR scenario is the first ACR scenario. In step 720b, the target EES processes the EAS discovery request and selects an EAS that supports the first ACR scenario.

[0302] The target EES may determine that it is necessary to select an EAS that supports the first ACR scenario. For example, the target EES may determine that it is necessary to select an EAS that supports the first ACR scenario based on the sixth information from the EEC.

[0303] The target EES may select one or more EASs that support the first ACR scenario. For example, the target EES may select one or more EASs based on the method in step 720a above, and determine one or more EASs that support the first ACR scenario based on the ACR capabilities of the one or more EASs. Alternatively, when selecting an EAS based on the method in step 720a above, a condition may be added, namely, that the EAS needs to support the first ACR scenario.

[0304] In step 730b, the target EES sends an EAS discovery response message to the EEC.

[0305] For a detailed description of the EAS discovery response message, see the aforementioned step 730a. After the target EES selects one or more EASs that support the first ACR scenario, it may indicate the one or more EASs through EAS information in the EAS discovery response message sent to the EEC.

[0306] In step 740b, the EEC determines the target EAS.

[0307] In some embodiments, the information received by the EEC indicates an EAS, which the EEC may determine as the target EAS. In some embodiments, the information received by the EEC indicates multiple EASs that support the first ACR scenario, from which the EEC may determine an EAS as the target EAS. This application does not limit the specific determination method, for example, it may be random determination or determination based on local policy.

[0308] In method 700b, step 740b is an optional step.

[0309] Step 740a in method 700a or step 740b in method 700b may also be performed by the AC. For example, the EEC may pass the EAS information to the AC through inter-layer interaction, and the AC may determine the target EAS from one or more EASs received by the EEC.

[0310] (a) in Figure 7 and (b) in Figure 7 provide a method for determining the target EAS. The step of determining the EAS that supports the first ACR scenario from the EAS can be performed by the target EES, so that the terminal device does not have to perform screening, which can reduce the burden on the terminal device; this step can also be performed by the terminal device, so that the target EES does not have to perform screening based on the ACR capability of the EAS, which can reduce the burden on the target EES.

[0311] In step 610, the EEC may find an EAS associated with the target EES and supporting the first ACR scenario, and use it as the target EAS. The EAS has the ability to complete ACR as the target EAS, and the application context can be successfully migrated through the target EAS.

[0312] In step 620 , the EEC sends an ACR request message to the target EES, requesting the target EES to perform at least one of the following actions: interacting with the target EAS to trigger the target EAS to perform context transfer, or updating the user plane path.

[0313] Among them, the ACR request can also be called an application relocation request. The ACR request message can carry information about the terminal device, such as the terminal device identifier, terminal device location, AC identifier, etc. The ACR request message can also carry the address of the source EAS (such as an IP address or URL address) and the identifier of the current application (such as the application's fully qualified domain name (FQDN) or uniform resource locator (URL)).

[0314] The target EES may obtain the address of the source EES and the address of the source EAS based on the ACR request message.

[0315] In step 630, the target EES instructs the target EAS to request the application context from the source EAS, and the application context is transmitted between the source EAS and the target EAS.

[0316] The target EES can send a message to the target EAS to request the migration of the current application context on the terminal device where the EEC is located. Accordingly, the target EAS can obtain the source EAS information from the target EES, such as the source EAS address and the terminal device information.

[0317] The target EAS may notify the source EAS to send the context of the current application, and accordingly, the target EAS receives the context of the current application.

[0318] In one implementation, the source EAS may transmit the context of the current application to the target EES via the source EES, and the target EES then transfers the received application context to the target EAS.

[0319] In step 640, the target EAS sends an ACR completion message to the target EES.

[0320] After receiving the context of the current application of the terminal device, the target EAS determines that the application context is received successfully, that is, the context of the current application can be reconstructed in the target EAS to form an application context that can be used by the client of the current application of the terminal device.

[0321] The target EAS may send a message to the target EES indicating that the ACT is complete and indicating the result of the ACT.

[0322] Optionally, after completing the ACT, the source EAS may also send a notification message of successful application context migration to the source EES.

[0323] In step 650, after receiving the ACR completion message sent from the target EAS, the target EES sends an ACR completion message to the EEC to indicate that the ACT is completed.

[0324] After receiving the ACR completion message from the target EAS, the target EES can also trigger an update of the user plane path of the current application. The target EES can trigger the SMF to insert a new user plane path for the current application of the terminal device, as well as insert an uplink classifier (UL CL) or branch anchor point (BP). This step can also be triggered by the target EAS.

[0325] The step of triggering the user plane path update of the current application can also be executed synchronously with the aforementioned step 630 or 640. For example, it can be executed after the target EES sends a message to the target EAS to request the migration of the application context, or after the ACT is completed. This application does not impose any restrictions on this.

[0326] Regarding the specific method of executing steps 620 to 650, reference may be made to the prior art and will not be repeated here.

[0327] Based on the above technical solution, when determining the target EES, the terminal device can instruct the ECS to select an EES that supports the first ACR scenario, so that the target EES determined by the terminal device can support the first ACR scenario; the ECS can also send the ACR capability of the EES to the terminal device, so that the terminal device can select the target EES that supports the first ACR scenario, so that the terminal device can smoothly execute ACR through the target EES. The terminal device can instruct the target EES to select an EAS that supports the first ACR scenario, so that the EAS determined by the terminal device can support the first ACR scenario; the target EES can also indicate the ACR capability of the EAS to the terminal device, and the terminal device selects the target EAS that supports the first ACR scenario, so that the EAS can complete the transmission of the application context as the target EAS. In this way, the ACR process based on the target EES can be executed smoothly, and when the current application's business switches between EASs, the application context can be successfully migrated, which can ensure the continuity of the current application's business.

[0328] The terminal device may execute method 300 when detecting an event requiring ACR.

[0329] For example, events requiring ACR may include one or more of the following:

[0330] The terminal device moves out of the service area of ​​the currently connected EAS;

[0331] The EEC receives a request from the AC to migrate the application context;

[0332] The terminal device detects that the quality of the currently applied EAS to which it is currently connected is low, for example, the connection quality to the currently connected EAS is poor, such as high latency or high packet loss rate;

[0333] The EEC receives a message about a new session from the SMF, or the EEC receives a new IP prefix, etc.

[0334] In the embodiment of the present application, the event that makes the source EAS unable to provide application services to the terminal device corresponds to the event that requires ACR.

[0335] Optionally, the EEC may perform ACR through the method 300 when determining to perform ACR based on the first ACR scenario.

[0336] In some embodiments, when the terminal device is connected to the EES, the currently connected EES can determine that the first ACR scene is the selected ACR scene, that is, when there is an ACR demand, ACR needs to be performed based on the first ACR scene. The currently connected EES can send information to the EEC, indicating that ACR is performed based on the first ACR scene, or indicating that the EES that supports the first ACR scene is selected, or indicating that the ACR scene corresponding to the current application is the first ACR scene. For ease of description, in the embodiments of the present application, this information is referred to as the fourth information. It should be understood that this cannot be a limitation of the present application. As an example, the fourth information can be carried in an ACR scenario selection notification message sent by the EES to the EEC.

[0337] In an embodiment of the present application, the EES currently connected to the terminal device can obtain information indicating the ACR capability of the terminal device (including the ACR capability of the EEC and the ACR capability of the AC) from the terminal device. The EES can determine the ACR scene corresponding to the current application based on the AC, EEC, the EES currently connected to the terminal device, and the ACR capability of the EAS currently connected to the terminal device (or the EAS selected by the terminal device). For example, the first ACR scene is determined as the ACR scene corresponding to the current application. The EES currently connected to the terminal device can determine that the first ACR scene is the selected ACR scene when the terminal device (including AC and EEC), the EAS currently connected to the terminal device (or the terminal selected) and the EES currently connected to the terminal device do not have a commonly supported ACR scene, and send a fourth information to the EEC. The EES currently connected to the terminal device can also determine that the first ACR scene is the selected ACR scene when the terminal device (including AC and EEC), the EAS currently connected to the terminal device (or the terminal selected) and the EES currently connected to the terminal device associated with the EAS have a commonly supported ACR scene, and send a fourth information to the EEC.

[0338] The EEC can determine to perform ACR based on the first ACR scenario through the fourth information from the EES. In some embodiments, the EES may also send information to the EEC to indicate that the current application has no corresponding ACR scenario, or to indicate that the determined ACR scenario is empty, or to indicate that the currently connected EES or the EAS associated with the EES cannot perform ACR. For ease of description, in the embodiments of the present application, this information is referred to as the third information. It should be understood that this cannot be a limitation of the present application. As an example, the third information can be carried in an ACR scenario selection notification message or an EAS information provisioning response message sent by the EES to the EEC.

[0339] The EES currently connected to the terminal device can send third information to the EEC when the terminal device (including AC and EEC), the EAS currently connected to the terminal device (or selected by the terminal device) and the EES associated with the EAS do not have a commonly supported ACR scenario.

[0340] After receiving the third information from the EES, the EEC may determine that the current application has no corresponding ACR scenario, and determine that the first ACR scenario is the selected ACR scenario, that is, ACR needs to be performed based on the first ACR scenario when there is an ACR requirement.

[0341] In some embodiments, the EEC can receive information from the EES to which the terminal device is currently connected, and obtain the ACR scenarios supported by the EES and the EAS to which the terminal device is currently connected (or selected by the terminal device). The terminal device can also determine the ACR scenarios supported by the EEC and AC. The terminal device can then determine the ACR scenario corresponding to the current application based on this information.

[0342] For example, the EEC may determine that the first ACR scene is the ACR scene corresponding to the current application when the terminal device (including AC and EEC), the EAS currently connected to the terminal device (or selected by the terminal device), and the EES associated with the EAS do not have a commonly supported ACR scene. Alternatively, the EEC may also determine that the first ACR scene is the ACR scene corresponding to the current application when the terminal device (including AC and EEC), the EAS currently connected to the terminal device (or selected by the terminal device), and the EES associated with the EAS do not have a commonly supported ACR scene.

[0343] The above content, combined with Figures 3 to 7, details the application context migration method provided in the embodiment of the present application.

[0344] Below, several possible implementations of the application context migration method provided in this application are described in conjunction with Figures 8 to 11.

[0345] FIG8 is a possible implementation of the application context migration method provided in an embodiment of the present application.

[0346] In this implementation, the EEC determines that the selected ACR scene is the first ACR scene, the ECS determines the EES that supports the first ACR scene, and the target EES determines the EAS that supports the first ACR scene.

[0347] The implementation shown in FIG8 includes steps 801 to 814 .

[0348] Step 801: The target EAS sends an EAS registration request message to the target EES. The EAS registration request message carries the EAS configuration information (including the ACR scenarios supported by the EAS).

[0349] Step 802: The target EES sends an EAS registration response message to the target EAS.

[0350] The specific method of registering the target EAS with the target EES shown in steps 801 and 802 can be performed with reference to the method shown in (a) of FIG. 5 , and will not be described in detail here.

[0351] Step 803: The target EES sends an EES registration request message to the ECS. The EES registration request message carries information indicating the ACR scenarios supported by the EES and the ACR scenarios supported by the EAS associated with the EES.

[0352] Step 804: The ECS sends an EES registration response message to the target EES.

[0353] The specific method of registering the target EES with the ECS shown in steps 803 to 804 can be performed with reference to the method shown in (b) of Figure 5 above, and will not be repeated here. Steps 801 to 804 are optional steps.

[0354] It should be understood that, based on the above steps, the source EAS can also be registered on the source EES, and the source EES can also be registered on the ECS.

[0355] Step 805: The source EES determines that the ACR scenario supported by the current application is empty.

[0356] The source EES can obtain the ACR scenarios supported by the terminal device, such as the ACR scenarios supported by AC and EEC, by connecting to the terminal device. The source EES can determine that the ACR scenarios supported by the current application are empty when the terminal device, the source EES, and the source EAS do not have ACR scenarios supported by both.

[0357] Step 806: The source EES sends an ACR scheme selection notification message to the EEC. The message may carry the AC ID and EAS ID of the current application and information indicating that the ACR scenarios supported by the current application are empty.

[0358] Step 807 : The EEC determines that the selected ACR scene is the first ACR scene.

[0359] Based on the information received from the source EES indicating that the ACR scenarios supported by the current application are empty, the EEC may determine that the current application has no available ACR scenarios, and the EEC may determine to use the first ACR scenario as the ACR scenario of the current application.

[0360] Among them, steps 805 to 807 are optional steps.

[0361] In step 808, the EEC sends a service activation request message to the ECS, which carries second information and may indicate at least one of the following: selecting an EES that supports the first ACR scenario, or preferably an EES that supports the first ACR scenario, or the source EES and / or source EAS cannot execute ACR, or the current application has no corresponding ACR scenario.

[0362] The EEC may execute step 808 when an event requiring ACR is detected, for example, when the terminal device moves out of the service area of ​​the currently connected EAS.

[0363] The specific method for executing step 808 may refer to the aforementioned step 410b and will not be repeated here.

[0364] In step 809 , the ECS determines one or more EESs that support the first ACR scenario.

[0365] The specific method of executing step 809 can refer to the aforementioned step 420b and will not be repeated here.

[0366] In step 810, the ECS sends a service activation response message to the EEC. The EES information carried in the message indicates one or more EESs determined or identified by the ECS that support the first ACR scenario. The EEC can select a target EES from them.

[0367] The specific method for executing step 810 can be found in the aforementioned steps 430b and 440b, which will not be repeated here.

[0368] In step 811, the EEC sends an EAS discovery request message to the target EES, which carries sixth information and may indicate at least one of the following: selecting an EAS that supports the first ACR scenario, or the source EES and / or source EAS cannot perform ACR, or the current application has no corresponding ACR scenario.

[0369] The specific method for executing step 811 can refer to the aforementioned step 710b and will not be repeated here.

[0370] In step 812 , the target EES determines one or more EASs that support the first ACR scenario.

[0371] The specific method for executing step 812 can refer to the aforementioned step 720b and will not be repeated here. In step 813, the target EES sends an EAS discovery response message to the EEC. The EAS information carried in the message indicates one or more EASs that support the first ACR scenario determined by the target EES. The EEC can select the target EAS from them.

[0372] The specific method for executing step 811 may refer to the aforementioned steps 730b and 740b, which will not be repeated here.

[0373] In step 814 , the EEC transfers the application context of the current application from the source EAS to the target EAS via the target EES and the target EAS.

[0374] The specific process of step 814 can be found in the aforementioned steps 620 to 650 and will not be repeated here.

[0375] Through the method shown in Figure 8, when the ACR scenario of the current application is empty, the source EES can indicate to the EEC that the ACR scenario of the current application is empty, and then the EEC can determine to perform ACR based on the first ACR scenario. When the source EAS cannot provide application services for the terminal device, an EES that supports the first ACR scenario can be selected as the target EES, and an EAS that supports the first ACR scenario can be selected as the target EAS. ACR is performed through the target EES, thereby successfully completing the migration of the application context and ensuring the continuity of the application service.

[0376] FIG9 is another possible implementation of the application context migration method provided in an embodiment of the present application.

[0377] In this implementation, the source EES determines that the selected ACR scene is the first ACR scene, the ECS determines the EES that supports the first ACR scene, and the target EES determines the EAS that supports the first ACR scene.

[0378] The implementation shown in FIG9 includes steps 901 to 913 .

[0379] Steps 901 to 904 are the same as the aforementioned steps 801 to 804 and will not be repeated here.

[0380] Step 905 : The source EES determines that the selected ACR scene is the first ACR scene.

[0381] The source EES may determine the first ACR scene as the ACR scene corresponding to the current application. For example, when the terminal device, the source EES, and the source EAS do not have a commonly supported ACR scene, the selected ACR scene may be determined as the first ACR scene.

[0382] Step 906: The source EES sends an ACR solution selection notification message to the EEC. The message carries information indicating the selection of the EES that supports the first ACR scenario.

[0383] Steps 907 to 913 are the same as the aforementioned steps 808 to 814 and will not be repeated here.

[0384] The effect achieved by the implementation shown in Figure 9 is similar to that achieved by the implementation shown in Figure 8. In addition, in the implementation shown in Figure 9, the step of determining that the selected ACR scene is the first ACR scene is performed by the source EES, the step of determining the EES that supports the first ACR scene is performed by the ECS, and the step of determining the EAS that supports the first ACR scene is performed by the target EES. In this way, the terminal device does not need to perform these steps, which can reduce the burden on the terminal device.

[0385] FIG10 is another possible implementation of the application context migration method provided in this application.

[0386] In this implementation, the EEC determines that the selected ACR scene is the first ACR scene, the EEC determines a target EES that supports the first ACR scene, and the EEC determines a target EAS that supports the first ACR scene.

[0387] The implementation shown in FIG10 includes steps 1001 to 1014 .

[0388] Steps 1001 to 1007 are the same as the aforementioned steps 801 to 807 and will not be repeated here.

[0389] Step 1008: The EEC sends a service activation request message to the ECS.

[0390] Step 1009, in response to the service activation request, the ECS sends a service activation response message to the EEC. The EES information carried in the message indicates one or more EESs. The message also carries information indicating the ACR scenarios supported by the one or more EESs. The information carried in the message also indicates the ACR scenarios supported by the EAS associated with the EES.

[0391] Step 1010 : The EEC determines an EES supporting the first ACR scenario from one or more EESs as a target EES based on the information carried in the service activation response message.

[0392] For a more detailed description of steps 1008 to 1010 , please refer to the aforementioned steps 410 to 440 , which will not be repeated here.

[0393] Step 1011: The EEC sends an EAS discovery request message to the target EES.

[0394] Step 1012: In response to the EAS discovery request message, the target EES sends an EAS discovery response message to the EEC. The EAS information carried in the message indicates one or more EASs, and the message also carries information indicating the ACR scenarios supported by the one or more EASs.

[0395] Step 1013 : The EEC determines an EAS supporting the first ACR scenario from one or more EASs as a target EAS based on the information carried in the EAS discovery response message.

[0396] A more detailed description of steps 1011 to 1013 can be found in the aforementioned steps 710 to 740 and will not be repeated here.

[0397] In step 1014 , the EEC transfers the application context of the current application from the source EAS to the target EAS via the target EES and the target EAS.

[0398] The specific process of step 1014 can be found in the aforementioned steps 620 to 650, which will not be repeated here.

[0399] The effect achieved by the implementation shown in Figure 10 is similar to that achieved by the implementation shown in Figure 8. In addition, in the implementation shown in Figure 10, the steps of determining that the selected ACR scene is the first ACR scene, determining the target EES that supports the first ACR scene, and determining the EAS that supports the first ACR scene are all performed by the EEC. In this way, the source EES, ECS, and target EES do not need to perform these steps, which can reduce the burden on the source EES, ECS, and target EES.

[0400] FIG11 is another possible implementation of the application context migration method provided in this application.

[0401] In this implementation, the source EES determines that the selected ACR scene is the first ACR scene, the EES determines the target EES that supports the first ACR scene, and the EEC determines the target EAS that supports the first ACR scene.

[0402] The implementation shown in FIG11 includes steps 1101 to 1113 .

[0403] Among them, steps 1101 to 1106 are the same as the aforementioned steps 901 to 906, and steps 1107 to 1113 are the same as the aforementioned steps 1008 to 1014, and are not repeated here.

[0404] The effect achieved by the implementation shown in FIG11 is similar to the effect achieved by the implementation shown in FIG8 .

[0405] In an embodiment of the present application, the step of determining that the selected ACR scene is the first ACR scene can be performed by the source EES or by the EEC. The step of determining the EES that supports the first ACR scene can be performed by the EEC or by the ECS. The step of determining the EAS that supports the first ACR scene can be performed by the EEC or by the target EES. The entity that specifically performs the above steps can be determined based on the load capacity of each entity, so that the system load is balanced to smoothly realize the transmission of application context.

[0406] It should be understood that the implementation methods shown in Figures 8 to 11 are merely examples of the methods provided in the embodiments of the present application and cannot constitute a limitation to the present application. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope disclosed in this application, and they should all be covered by the scope of protection of this application.

[0407] In an embodiment of the present application, an EEC context may also be stored on the EES. The EEC context may be acquired, generated or created by the EES when the EEC registers with the EES, or it may be pre-configured, or it may be acquired by the EES from another EES through the EEC context transmission process (for example, the target EES may acquire the EEC context from the source EES). This application does not limit this.

[0408] As an example, the EEC registration process is described below with reference to FIG12 .

[0409] 12 , the EEC registration process may include steps 1210 to 1240 .

[0410] In step 1210 , the EEC sends an EEC registration request message to the EES.

[0411] The EEC registration request includes the security credentials received after successful authorization of the edge computing service, and may also include a recommended expiration time. Optionally, the request may also include information indicating to the EES how the EEC expects to use the services of the EES. If the EEC is moved to this EES from the authority of another EES (for example, the source EES), the request from the EEC may include the identity and endpoint of the source EES, as well as the EEC context ID provided by the source EES to maintain the EEC context and authorize the relocation of the EEC context.

[0412] In step 1220, after receiving the registration request from the EEC, the EES verifies the registration request and the security credentials.

[0413] EES can determine whether the requirements indicated in the AC profile can be met.

[0414] In step 1230, after successfully verifying the request, if the received EEC registration request contains the EEC context ID, the EES ID of the source EES, and the EES endpoint, the EES can retrieve the EEC context from the source EES. Otherwise, this step is skipped.

[0415] In step 1240, the EES sends a registration response message to the EEC.

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

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

[0418] The specific steps of the process shown in FIG12 can also be performed with reference to the prior art and will not be described in detail.

[0419] In the method provided in the embodiment of the present application, during the ACR process, the source EES and the target EES can also transmit the EEC context.

[0420] The transmission of the EEC context may be performed through an EEC context push process or an EEC context pull process.

[0421] The EEC context transmission process is schematically described below with reference to FIG. 13 (a) and FIG. 13 (b).

[0422] FIG13( a ) is a schematic diagram of an EEC context pulling process according to an embodiment of the present application. Referring to FIG13( a ), the EEC context pulling process may include steps 1310 a to 1330 a .

[0423] In step 1310a, the target EES sends an EEC context pull request message to the source EES, requesting the EEC context from the source EES. The request message may include an EEC context ID.

[0424] In step 1320a, after receiving the EEC context pull request message from the target EES, the source EES verifies the request and verifies the security credentials of the requester. The source EES uses the EEC context ID in the request message to identify and authorize the EEC context to be relocated.

[0425] In step 1330a, the source EES sends an EEC context pull response message to the target EES. The target EES receives the EEC context from the source EES and stores the EEC context.

[0426] FIG13( b ) is a schematic diagram of an EEC context push process according to an embodiment of the present application. Referring to FIG13( b ), the EEC context push process may include steps 1310 b to 1330 b .

[0427] In step 1310b, the source EES decides to forward the EEC context to the target EES for relocation. The source EES determines the target EES and EEC context to be forwarded.

[0428] In step 1320b, the source EES sends an EEC context push request message to the target EES, where the request message includes the determined EEC context.

[0429] In step 1330b, upon receiving the request from the source EES, the target EES verifies the request and validates the security credentials. The target EES uses the provided EEC context ID to authorize the storage and management of the EEC context. The target EES then sends an EEC context push response message to the source EES, indicating successful receipt of the EEC context.

[0430] The specific steps of the process shown in (a) of FIG. 13 and (b) of FIG. 13 can be performed with reference to the prior art and will not be described in detail.

[0431] During the ACR process, the source EES and the target EES may transfer the EEC context. For example, the EEC context pull process shown in (a) of FIG. 13 or the EEC context push process shown in (b) of FIG. 13 may be performed simultaneously with the execution of the aforementioned step 630. It should be understood that the present application does not limit the specific time for performing the EEC context transfer process, and the EEC context transfer between the source EES and the target EES may also be performed before or after the aforementioned step 630.

[0432] To enable EEC context transfer, both the source and target EESs must have EEC context transfer capabilities. This means that EEC context transfer can only be performed through the corresponding process when both the source and target EESs support the EEC context push process. For example, when both the source and target EESs support the EEC context push process, EEC context transfer can be performed between the source and target EESs using the process shown in Figure 13 (b). However, when the source EES supports the EEC context push process but the target EES does not, EEC context transfer cannot be performed between the source and target EESs using the EEC context push process.

[0433] In the embodiments of the present application, the target EES has (or supports) the EEC context transfer capability corresponding to the source EES, or the target EES and the source EEC have (or support) the corresponding EEC context transfer capability, which means that the EEC context transfer process supported by the target EES and the context transfer process supported by the source EES have the same EEC context transfer process. For example, the target EES and the source EES both support the EEC context push process (the target EES and the source EES support the EEC context push API), or the target EES and the source EES both support the EEC context pull process (the target EES and the source EES support the EEC context push API).

[0434] Both the target EES and the source EES support the EEC context push process, including the source EES supporting the sending of an EEC context push request message and the target EES supporting the sending of an EEC context push response message.

[0435] Both the target EES and the source EES support the EEC context pull process, including the target EES supporting the sending of EEC context pull request messages and the source EES supporting the sending of EEC context pull response messages.

[0436] During the ACR process, if the determined target EES and source EES do not have a commonly supported EEC context transfer solution, EEC context transfer cannot be performed during the ACR process, which may affect service continuity.

[0437] When the ACR scenario corresponding to the application is empty and the target EES obtained by the terminal device through ECS does not support the first ACR scenario, application context migration is still required to ensure the continuity of the application. However, the target EES may not have the EEC context transmission capability corresponding to the source EES. At this time, there is no EEC-related information on the target EES, which may cause the target EES to be unable to provide subsequent edge computing services for the terminal device.

[0438] To this end, an embodiment of the present application also provides an EEC context transmission method. During the ACR process, when the source EES supports EEC context transmission, a target EES that supports the corresponding EEC context transmission process with the source EES is selected, so that EEC context transmission can be implemented based on the corresponding EEC context transmission process during the ACR process; when the source EES does not support EEC context transmission, or the target EES does not have the EEC context transmission capability corresponding to the source EES, the EEC re-registers with the target EES after the ACR is completed.

[0439] In this way, the target EES can obtain the context of the EEC and provide the EEC with information that can be used in edge computing services. The target EES can then provide subsequent edge computing services to the terminal device, ensuring business continuity.

[0440] The following describes the EEC context transmission method provided in an embodiment of the present application with reference to FIG. 14 to FIG. 16 .

[0441] Figure 14 is a schematic flow chart of the EEC context transmission method provided in an embodiment of the present application. The method shown in Figure 14 illustrates the method provided in an embodiment of the present application from the perspective of a terminal device. The method can be executed by the terminal device or by components within the terminal device (such as circuits, chips, chip systems, etc.), and can be implemented in software and / or hardware. This application is not limited to this. The following description uses the EEC configured in the terminal device as an example.

[0442] Exemplarily, as shown in FIG. 14 , the EEC context transmission method 1400 may include step 1410 and step 1420 .

[0443] In step 1410 , the EEC context transmission capability of the source EES is obtained.

[0444] The EEC can obtain the context transfer capability of the source EES from the source EES. For example, when the source EES is connected to the EEC, the source EES can send an ACR solution selection notification message to the EEC containing API information supported by the source EES, indicating the EEC context transfer capability of the source EES.

[0445] Exemplarily, it may indicate whether the source EES supports EEC context transmission, or whether the source EES supports the EEC context pull process, or whether the source EES supports the EEC context push process.

[0446] In step 1420, a target EES is determined, where the target EES is determined based on the EEC context transfer capability of the source EES.

[0447] When the source EES supports EEC context transfer,

[0448] The source EES may send information to the EEC, instructing the EEC to select a target EES that supports the corresponding EEC context transfer capability when performing an ACR. For example, if the source EES supports the EEC context pull process, the source EES may indicate to the EEC that it needs to select a target EES that supports the EEC context pull process when performing an ACR.

[0449] Accordingly, the EEC may determine that it needs to select a target EES that supports the corresponding EEC context transmission capability based on the information from the source EES.

[0450] The EEC can select a target EES that supports the same EEC context transfer process based on the EEC context transfer process supported by the source EES through the ECS.

[0451] When the source EES does not support EEC context transfer, the source EES can send information to the EEC to instruct the EEC to select a target EES that does not support EEC context transfer when performing ACR. The source EES can also indicate to the EEC that it needs to re-register with the target EES after performing ACR.

[0452] Accordingly, the EEC may determine, based on information from the source EES, to select a target EES that does not support EEC context transfer. The EEC may also determine that re-registration with the target EES is required after the ACR.

[0453] The EEC can select a target EES through the ECS. The target EES does not have to support EEC context transfer. The target EES can be determined through the service provisioning process or the EES discovery process.

[0454] Illustratively, the method of selecting a target EES may be as shown in FIG. 15( a ) or FIG. 15( b ).

[0455] 15( a ), in method 1500 a , the EEC selects a target EES based on the EEC context transfer process supported by the source EES. Method 1500 a may include steps 1510 a to 1540 a .

[0456] In step 1510a, the EEC may send a service activation request message to the ECS.

[0457] The specific implementation method of step 1510a can refer to the aforementioned step 410a or the aforementioned step 410b.

[0458] In an embodiment of the present application, the EEC may further send first request information to the EES, where the first request information is used to indicate at least one of the following: requesting to obtain the EEC context transmission capability of the EES, or the source EES supporting EEC context transmission.

[0459] For example, when the EEC determines that the ACR scenario corresponding to the application is empty (or in other situations), the EEC determines that ACR needs to be performed based on the first ACR scenario. The EEC may send a first request message to the ECS, requesting the ECS to send the API capabilities supported by the EES, or requesting the ECS to send the EEC context transmission capabilities supported by the EES, or requesting the ECS to send whether the EES supports the EEC context pull process, or requesting the ECS to send whether the EES supports the EEC context push process.

[0460] Optionally, in step 1520a, the ECS processes the service provisioning request and identifies one or more EESs.

[0461] The specific implementation method of step 1520a may refer to the aforementioned step 420a or the aforementioned step 420b. For example, the one or more EESs identified by the ECS may be EESs that support the first ACR scenario.

[0462] In step 1530a, the ECS sends a service provisioning response message to the EEC, along with information indicating the EEC context transfer capabilities of the EES, such as the API capabilities supported by the EES, whether the EES supports EEC context transfer, the EEC context transfer processes supported by the EES, whether the EES supports the EEC context pull process, or whether the EES supports the EEC context push process. This information can be carried in the service provisioning request response message, for example.

[0463] The ECS can obtain information indicating the EES's EEC context transmission capabilities. This information can be obtained by the ECS when the EES registers with the ECS, obtained by the ECS through a gateway system, or pre-configured. For example, in the EES registration process shown in (b) of Figure 5 , the EES can send information about the APIs supported by the EES to the ECS, such as information indicating the EES's EEC context transmission capabilities. This information can be carried in the EES registration request message.

[0464] The specific implementation method of step 1530a can refer to the aforementioned step 430a, and can also refer to the aforementioned step 430b.

[0465] In some embodiments, the ECS may send all information of all EESs registered or configured on the ECS to the EEC. In this case, the aforementioned step 1520a is optional.

[0466] In step 1540a, the EEC determines a target EES from one or more EESs that has an EEC context transfer capability corresponding to the source EES.

[0467] The information received by the EEC may indicate the EEC context transfer capability of the EES.

[0468] When the source EES supports EEC context transfer, the EEC can select an EES that supports the corresponding EEC context transfer process as the target EES. For example, if the source EES only supports the EEC context pull process, the target EES must support the EEC context pull process; if the source EES only supports the EEC context push process, the target EES must support the EEC context push process; if the source EES supports both the EEC context pull process and the EEC context push process, the target EES can support only the EEC context pull process or only the EEC context push process.

[0469] When the source EES does not support EEC context transfer, the EEC may not consider the EEC context transfer capability of the EES when selecting the EES.

[0470] In some embodiments, if the source EES supports EEC context transfer, and none of the one or more EESs indicated by the ECS to the EEC has the EEC context transfer capability corresponding to that supported by the source EES, or if the one or more EESs indicated by the ECS to the EEC do not have the EEC context transfer capability, the target EES selected by the EEC may have a different EEC context transfer capability than the source EES, or may not have the EEC context transfer capability. The EEC may determine that re-registration with the target EES is required after the ACR.

[0471] FIG15( b ) is a schematic diagram of another method for determining a target EES provided in an embodiment of the present application.

[0472] 15( b ), in method 1500 b , the ECS selects an EES that supports the corresponding EEC context transmission capability based on the EEC context transmission capability supported by the source EES. Method 1500 b may include steps 1510 b to 1540 b .

[0473] In step 1510b, the EEC sends a service activation request message to the ECS.

[0474] The EEC may send information to the ECS indicating the EEC context transmission capability of the source EES. For example, the information may be carried in a service activation request message.

[0475] For example, if the source EES supports the EEC context pull process, the EEC can send information to the ECS to indicate that the source EES supports the EEC context pull process; if the source EES supports the EEC context push process, the EEC can send information to the ECS to indicate that the source EES supports the EEC context push process.

[0476] The EEC may also send information to the ECS, indicating at least one of the following: the need to select an EES with EEC context transmission capability, or the need to select an EES with EEC context transmission capability corresponding to the source EES, or the preference for an EES with EEC context transmission capability corresponding to the source EES.

[0477] For example, if the source EES only supports the EEC context pull process, the EEC can send information to the ECS to indicate that an EES that supports the EEC context pull process needs to be selected. If the source EES only supports the EEC context push process, the EEC can send information to the ECS to indicate that an EES that supports the EEC context push process needs to be selected. If the source EES supports both the EEC context pull process and the EEC context push process, the EEC can send information to the ECS to indicate that an EES that supports the EEC context pull process or an EES that only supports the EEC context push process can be selected.

[0478] The specific implementation of the EEC sending the service activation request message to the ECS can refer to the aforementioned step 410a, and can also refer to the aforementioned step 410b.

[0479] In step 1520b, the ECS processes the service provisioning request and selects an EES with the same EEC context transfer capability as the source EES.

[0480] Step 1520b may be performed with reference to the aforementioned step 420a or 420b.

[0481] In an embodiment of the present application, if the source EES supports EEC context transfer, the ECS may select an EES that supports an EEC context transfer process corresponding to that supported by the source EES.

[0482] For example, if the information from the EEC indicates that the source EES only supports the EEC context pull process, the ECS selects an EES that supports the EEC context pull process. If the information from the EEC indicates that the source EES only supports the EEC context push process, the ECS selects an EES that supports the EEC context push process. If the information from the EEC indicates that the source EES supports both the EEC context pull process and the EEC context push process, the ECS can select an EES that supports the EEC context pull process or an EES that only supports the EEC context push process.

[0483] Optionally, after executing the aforementioned step 420a or executing the aforementioned step 420b and selecting one or more EESs, an EES with an EEC context transmission capability corresponding to that supported by the source EES may be selected based on the EEC context transmission capability supported by the one or more EESs. Alternatively, when executing the aforementioned step 420a or step 420b and selecting one or more EESs, a condition is added, namely, the selected EES needs to support an EEC context transmission capability corresponding to that supported by the source EES. It should be understood that this application does not limit the order of selection. In some embodiments, among the EESs registered on or configured on the ECS, no EES supports the same EEC context transmission process as the source EES, or information from the EEC indicates that the source EES does not have EEC context transmission capability, then the ECS may not consider the EEC context transmission capability supported by the EES when selecting the EES.

[0484] In step 1530b, the ECS sends a service activation response message to the EEC.

[0485] In some embodiments, the ECS determines one or more EESs that have EEC context transfer capabilities corresponding to the source EES. The ECS may send information indicating the one or more EESs to the EEC. The information may be carried in a service activation response message.

[0486] Optionally, the ECS may send information to the EEC, indicating that it is not necessary to re-register with the target EES after the ACR. This information may be carried in the service activation response message.

[0487] In some embodiments, among the EESs registered or configured on the ECS, no EES supports the corresponding EEC context transfer process as the source EES, or no EES has the EEC context transfer capability, or information from the EEC indicates that the source EES does not have the EEC context transfer capability. The ECS may send information to the EEC indicating that re-registration with the target EES is required after the ACR. This information may be carried in a service provisioning response message. The specific implementation method of step 1530b may refer to the aforementioned steps 430a or 430b.

[0488] In step 1540b, the EEC determines a target EES from one or more EESs indicated by the ECS.

[0489] In some embodiments, if the ECS indicates that one or more EESs do not have the EEC context transfer capability corresponding to the source EES, or indicates that one or more EESs do not have the EEC context transfer capability, the EEC may determine that it needs to re-register with the target EES after the ACR.

[0490] Regarding the specific implementation method of step 1540b, you can refer to the aforementioned step 440a or 440b and will not repeat it here.

[0491] In method 1500b, step 1540b is an optional step.

[0492] (a) in Figure 15 and (b) in Figure 15 provide a method for determining the target EES in step 1420. The step of selecting an EES from the EES that has the same EEC context transmission capability as the source EES can be performed by the ECS, so that the terminal device does not have to perform screening, which can reduce the burden on the terminal device; this step can also be performed by the EEC, so that the ECS does not have to perform screening based on the EEC context transmission capability of the EES, which can reduce the burden on the ECS.

[0493] Through step 1420, a target EES having the same EEC context transfer capability as the source EES can be determined. During the ACR process, the source EES can complete the EEC context transfer with the target EES. If the target EES does not have the same EEC context transfer capability as the source EES, or the source EES does not support EEC context transfer, the EEC can obtain an instruction to re-register with the target EES. Based on the instruction, the EEC can re-register with the target EES after the ACR is completed, thereby allowing the target EES to obtain the EEC context.

[0494] Optionally, the method 1400 may further include: determining whether to perform EEC context transfer.

[0495] Exemplarily, FIG. 16( a ) and FIG. 16 ( b ) provide two methods of determining whether to perform EEC context transfer.

[0496] In method 1600a, the target EES determines whether an EEC context transfer can be performed. Method 1600a includes steps 1610a to 1630a.

[0497] In step 1610a, the EEC may send information to the target EES, indicating the EEC context transfer capabilities of the source EES. For example, the information may indicate at least one of the following: API capabilities supported by the source EES, whether the source EES supports the EEC context transfer process, whether the source EES supports the EEC context pull process, or whether the source EES supports the EEC context push process. It should be understood that this application is not limited to this.

[0498] In step 1620a, after receiving the information from the EEC, the target EES may determine whether the EEC context transfer can be performed based on the information.

[0499] If it is determined that the target EES and the source EES support the corresponding EEC context transfer process, for example, both the source EES and the target EES support the EEC context pull process and / or both the source EES and the target EES support the EEC context push process, then it can be determined that EEC context transfer with the source EES is possible. The target EES can also determine that the EEC does not need to re-register with the target EES after ACR.

[0500] If it is determined that the target EES and the source EES do not support the corresponding EEC context transfer process, or the source EES does not support EEC context transfer, or the target EES does not support EEC context transfer, the target EES may also determine that the EEC needs to re-register with the target EES after ACR.

[0501] In step 1630a, the target EES sends an indication message to the EEC, indicating whether the EEC needs to re-register with the target EES after the ACR.

[0502] If it is determined that the target EES and the source EES support corresponding EEC context transfer capabilities, the target EES may send an indication message to the EEC, indicating that it is not necessary to re-register with the target EES after the ACR.

[0503] If it is determined that the target EES and the source EES do not support the same EEC context transfer process, or the source EES does not support EEC context transfer, or the target EES does not support EEC context transfer, the target EES can send an indication message to the EEC, indicating that it needs to re-register with the target EES after ACR.

[0504] The EEC and the target EES may perform method 1600a when executing the EAS discovery process in step 610. For example, in step 1610a, the information sent by the EEC to the target EES may be carried in an EAS discovery request message, and the indication information in step 1630a may be carried in an EAS discovery response message.

[0505] In method 1600b, the EEC determines whether the EEC context transfer can be performed. Method 1600b includes steps 1610b to 1630b.

[0506] In step 1610b, the EEC sends a request message to the target EES. The request message may indicate at least one of the following: a request to obtain the EEC context transfer capability of the target EES, or the source EES supports EEC context transfer.

[0507] In step 1620b, in response to the request from the EEC, the target EES sends information to the EEC, indicating the EEC context transfer capability of the target EES. For example, if the target EES supports the EEC context pull process, the information may indicate that the target EES supports the EEC context pull process; if the target EES supports the EEC context push process, the information may indicate that the target EES supports the EEC context push process; if the target EES does not support the EEC context transfer capability, the information may indicate that the target EES does not support the EEC context transfer capability; if the target EES has the EEC context transfer capability, the information may indicate that the target EES has the EEC context transfer capability.

[0508] In step 1630b, the EEC determines whether the EEC context transfer capability can be executed based on the EEC context transfer capability of the target EES.

[0509] If the target EES and the source EES support corresponding EEC context transfer capabilities, it can be determined that the target EES can transfer the EEC context with the source EES. The EEC can determine that it does not need to re-register with the target EES after the ACR.

[0510] If it is determined that the target EES and the source EES do not support corresponding EEC context transmission capabilities, or the source EES does not support EEC context transmission, or the target EES does not support EEC context transmission, then the EEC can determine that the target EES cannot perform EEC context transmission with the source EES. The EEC can also determine that it needs to re-register with the target EES after ACR.

[0511] The EEC and the target EES may perform method 1600b when executing the EAS discovery process in step 610. For example, in step 1610b, the information sent by the EEC to the target EES may be carried in an EAS discovery request message, and in step 1620b, the information sent by the target EES to the EEC may be carried in an EAS discovery response message.

[0512] It should be understood that the present application does not limit the specific time for executing each step in method 1400 during the ACR process.

[0513] When executing step method 1600a or method 1600b, the aforementioned step 1420 is optional, that is, the target EES can be determined by the method of the aforementioned step 1420, the target EES can be determined by the method in the aforementioned step 310, or the target EES can be determined by a method in the prior art.

[0514] The terminal device may determine the target EES and perform ACR through the method 1400. During the ACR process, the source EES and the target EES may perform EEC context transfer, or the EEC may re-register with the target EES after the ACR.

[0515] In some embodiments, the source EES and the target EES support the same EEC context transmission capability, and the EEC context can be transmitted between the source EES and the target EES during the ACR process, for example, when executing the aforementioned step 630 .

[0516] For example, the source EES and the target EES jointly support the EEC context push process, and the EEC context can be transferred between the source EES and the target EES through the process shown in (b) of Figure 13. The source EES and the target EES jointly support the EEC context pull process, and the EEC context can be transferred between the source EES and the target EES through the process shown in (a) of Figure 13.

[0517] In some embodiments, the source EES and / or the target EES do not support EEC context transfer, or the source EES and the target EES do not have corresponding EEC context transfer capabilities. The EEC can register with the target EES after the ACR. The method for the EEC to register with the target EES can be referred to the method in Figure 12 above and will not be repeated here.

[0518] Based on the above technical solution, when determining the target EES, the EEC can instruct the ECS to select an EES with EEC context transmission capabilities corresponding to those supported by the source EES, so that the target EES determined by the EEC can transmit the EEC context to the source EES. The ECS can also indicate the EEC's EEC context transmission capabilities to the EEC, so that the EEC can select a target EES with EEC context transmission capabilities corresponding to those supported by the source EES. In this way, during the ACR process, the source EES and the target EES can smoothly transfer the EEC context. If the source EES does not support EEC context transmission, or the target EES does not support EEC context transmission, or the source EES and the target EES do not have corresponding EEC context transmission capabilities, the EEC can re-register with the target EES based on the instructions, so that the target EES can obtain the EEC context and provide the EEC with information that can be used in edge computing services. The target EES can then provide subsequent edge computing services to the terminal device, ensuring business continuity.

[0519] As an example, several possible implementations of the method for EEC context transmission provided in an embodiment of the present application are described below in conjunction with FIG. 17 and FIG. 18 .

[0520] Figure 17 illustrates a possible implementation of the EEC context migration method provided in an embodiment of the present application. In the method illustrated in Figure 17 , the step of determining an EES that supports the EEC context transfer capability corresponding to the source EES may be performed by the ECS, and the step of determining whether the source EES and the target EES have corresponding EEC context transfer capabilities may be performed by the target EES. Referring to Figure 17 , the method includes steps 1701 through 1710.

[0521] Step 1701: The target EES sends an EES registration request message to the ECS. The EES registration request message carries information indicating the EEC context transmission capability of the EES.

[0522] Step 1702: The ECS sends an EES registration response message to the target EES.

[0523] The specific method of registering the target EES with the ECS shown in steps 1701 and 1702 can be performed with reference to the method shown in (b) of FIG. 5 , and will not be described in detail here.

[0524] Step 1701 and step 1702 are optional steps.

[0525] It should be understood that, based on the above steps, the source EES may also be registered with the ECS. Based on the registration process, the ECS may determine the EEC context transfer capability of the source EES and / or the target EES.

[0526] Step 1703 : The source EES sends an ACR scheme selection notification message to the EEC. The message may carry the currently applied AC ID, EAS ID, and information indicating the EEC context transmission capability of the source EES.

[0527] Optionally, the EEC or source EES may determine the ACR scenario.

[0528] The specific method for executing step 1703 can be found in the aforementioned step 1410 and will not be repeated here.

[0529] In step 1704, the EEC sends a service activation request message to the ECS. The message carries information that may indicate at least one of the following: the need to select an EES with EEC context transmission capability, or the need to select an EES with EEC context transmission capability corresponding to the source EES, preferably an EES with EEC context transmission capability corresponding to the source EES.

[0530] Step 1705 , the ECS determines an EES that supports the EEC context transfer capability corresponding to the source EES.

[0531] The specific implementation method of step 1705 can be found in the aforementioned step 1520b and will not be repeated here.

[0532] Step 1706: The ECS sends a service activation response message to the EEC. The message may carry information indicating one or more EESs that have the EEC context transfer capability corresponding to the source EES. The EEC may determine the target EES from the information.

[0533] Optionally, if the EES determined by the ECS does not have the EEC context transmission capability corresponding to the original EES, the message may carry information indicating that re-registration with the target EES is required.

[0534] The specific implementation of step 1706 can be found in the aforementioned step 1530b, which will not be repeated here.

[0535] Step 1707 : The EEC sends information to the target EES to indicate the EEC context transfer capability of the source EES.

[0536] The specific implementation of step 1707 can be found in the aforementioned step 1610a, which will not be repeated here.

[0537] Step 1708 : The target EES determines whether the source EES and the target EES have corresponding EEC context transmission capabilities.

[0538] The specific implementation of step 1708 can be found in the aforementioned step 1620a, which will not be repeated here.

[0539] Step 1709: The target EES sends a registration instruction message to the EEC, indicating whether it is necessary to re-register with the target EES.

[0540] The specific implementation of step 1708 can be found in the aforementioned step 1630a, which will not be repeated here.

[0541] In step 1710 , the target EES transfers the EEC context with the source EES, or the EEC registers with the target EES.

[0542] If the target EES and the source EES support corresponding EEC context transmission capabilities, the target EES can perform EEC context transmission with the source EES through the EEC context transmission process that they both support. The specific implementation method can be referred to (a) or (b) in Figure 13, which will not be repeated here.

[0543] If the target EES and the source EES do not support corresponding EEC context transmission capabilities, or the source EES does not support EEC context transmission, or the target EES does not support EEC context transmission, the EEC can re-register with the target EES so that the target EES can obtain the EEC context. The specific implementation method can be referred to Figure 12 and will not be repeated here.

[0544] It should be understood that when the target EES is determined using the method of steps 1704 to 1706, steps 1707 to 1709 are optional. When steps 1707 to 1709 are performed, steps 1704 to 1706 are optional. That is, other methods can be used to determine the target EES, such as determining the target EES based on the method in step 310 above, or determining the target EES based on existing technologies.

[0545] It should also be understood that in step 1703, if the information sent by the source EES to the EEC indicates that the source EES does not support EEC context transmission, the EEC may determine that it needs to re-register with the target EES. At this time, steps 1704 to 1709 are optional steps. In step 1710, the EEC registers with the target EES, and the target EES obtains the EEC context.

[0546] In this way, the target EES can obtain the EEC context and provide the EEC with information that can be used in edge computing services. The target EES can then provide subsequent edge computing services to the terminal device, ensuring business continuity.

[0547] Figure 18 illustrates another possible implementation of the application context migration method provided in an embodiment of the present application. In the method illustrated in Figure 18 , the step of determining a target EES that supports the EEC context transfer capability corresponding to the source EES may be performed by the EEC, and the step of determining whether the source EES and the target EES have corresponding EEC context transfer capabilities may be performed by the target EEC. Referring to Figure 18 , the method includes steps 1801 through 1810.

[0548] The implementation method of steps 1801 to 1803 is the same as the implementation method of the aforementioned steps 1701 to 1703, and will not be repeated here.

[0549] Step 1804 , the EEC sends a service activation request message to the ECS. The message carries information indicating at least one of the following: a request to obtain the EEC context transfer capability of the EES, or whether the source EES supports EEC context transfer.

[0550] The specific implementation of step 1804 can refer to the aforementioned step 1510a and will not be repeated here.

[0551] Step 1805 : The ECS sends a service activation response message to the EEC. The message may carry information indicating one or more EESs and the EEC context transmission capabilities of the one or more EESs.

[0552] The specific implementation of step 1805 can refer to the aforementioned step 1520a and the aforementioned step 1530a, which will not be repeated here.

[0553] In step 1806, the EEC determines a target EES that supports the EEC context transfer capability corresponding to the source EES. Based on the EEC context transfer capability of the EES, the EEC may select an EES that supports the EEC context transfer capability corresponding to the source EES from one or more EESs indicated by the ECS as the target EES.

[0554] The specific implementation of step 1805 can refer to the aforementioned step 1540a and will not be repeated here.

[0555] Step 1807 : The EEC sends a request message to the target EES, indicating at least one of the following: requesting to obtain the EEC context transfer capability of the target EES, or the source EES supporting EEC context transfer.

[0556] Step 1808: The target EES sends information to the EES, indicating the EEC context transmission capability of the target EES.

[0557] The specific implementation method of step 1808 can refer to the aforementioned step 1620b and will not be repeated here.

[0558] Step 1809 , the EEC determines whether the source EES and the target EES have corresponding EEC context transmission capabilities.

[0559] The specific implementation of step 1809 can refer to the aforementioned step 1630b and will not be repeated here.

[0560] Step 1810 : The target EES transfers the EEC context to the source EES, or the EEC registers with the target EES.

[0561] If the target EES and the source EES support corresponding EEC context transmission capabilities, the target EES can perform EEC context transmission with the source EES through the EEC context transmission process that they both support. The specific implementation method can be referred to (a) or (b) in Figure 13, which will not be repeated here.

[0562] If the target EES and the source EES do not support corresponding EEC context transmission capabilities, or the source EES does not support EEC context transmission, or the target EES does not support EEC context transmission, the EEC can re-register with the target EES so that the target EES can obtain the EEC context. The specific implementation method can be referred to Figure 12 and will not be repeated here.

[0563] It should be understood that when the target EES is determined using the method of steps 1804 to 1806, steps 1807 to 1809 are optional. When steps 1807 to 1809 are performed, steps 1804 to 1806 are optional. That is, other methods can be used to determine the target EES, such as determining the target EES based on the method in step 310 above, or determining the target EES based on existing technologies.

[0564] It should also be understood that in step 1803, if the information sent by the source EES to the EEC indicates that the source EES does not support EEC context transmission, the EEC may determine that it needs to re-register with the target EES. At this time, steps 1804 to 1809 are optional steps. In step 1810, the EEC registers with the target EES, and the target EES obtains the EEC context.

[0565] In this way, the target EES can obtain the EEC context and provide the EEC with information that can be used in edge computing services. The target EES can then provide subsequent edge computing services to the terminal device, ensuring business continuity.

[0566] It should be understood that the steps in Figures 17 and 18 can be implemented in combination. For example, after executing steps 1704 to 1706, steps 1807 to 1809 can be executed; or after executing steps 1804 to 1806, steps 1707 to 1709 can be executed. This application does not limit this.

[0567] It should also be understood that the EEC context transmission method provided in the embodiment of the present application can be implemented in combination with the ACR method described in Figures 3 to 11 above. The specific steps can be found in the description in Figures 3 to 11 above. This application does not limit this.

[0568] The above content, combined with Figures 3 to 18, details the method provided in the embodiment of the present application. Next, the device provided in the embodiment of the present application is described in combination with Figures 19 and 20.

[0569] Refer to Figure 19, which is a schematic block diagram of a communication device provided in an embodiment of the present application. As shown in Figure 19, the communication device may include a processing unit 1910 and a transceiver unit 1920.

[0570] Optionally, the communication device 1900 may correspond to the terminal device (including the EEC or AC) in the above method embodiment. For example, it may be a terminal device, or a component configured in the terminal device (such as a chip, a chip system, a processor, etc.), or it may be a logic module or software that can implement all or part of the functions of the terminal device. This embodiment of the present application is not limited to this.

[0571] When the apparatus 1900 corresponds to a terminal device, it can be used to execute the steps performed by the terminal device in the methods shown in Figures 3 to 18 above, such as the steps performed by the EEC. The communication apparatus 1900 may include units for executing the methods performed by the terminal device (including the EEC) in the methods shown in Figures 3 to 18 above. Furthermore, each unit in the communication apparatus 1900 and the other operations and / or functions described above are respectively for implementing the corresponding processes in the methods shown in Figures 3 to 18.

[0572] As an example, the processing unit 1910 is configured to determine a target EES, where the target EES is an EES that supports a first ACR scenario, where the first ACR scenario is a scenario where the target EES performs ACR. The transceiver unit 1920 is configured to request the target EES to perform ACR.

[0573] In some embodiments, the transceiver unit 1920 is further configured to receive EES information from the ECS, where the EES information indicates at least one EES. The processing unit 1910 is specifically configured to determine a target EES based on the EES information.

[0574] Optionally, the transceiver unit 1920 is further configured to receive first information from the ECS, where the first information indicates the ACR capability of the at least one EES.

[0575] Optionally, the at least one EES supports a first ACR scenario.

[0576] Optionally, the transceiver unit 1920 is also used to send second information to the ECS, where the second information is used to indicate at least one of the following: selecting a target EES that supports the first ACR scenario, or the currently connected EES or the currently connected application instance EAS cannot perform ACR, or the current application has no corresponding ACR scenario, or requesting to obtain the ACR capability of the EES.

[0577] In some embodiments, the processing unit 1910 is further configured to determine to perform ACR based on the first ACR scenario when the current application has no corresponding ACR scenario, or when the currently connected EES or the currently connected EAS cannot perform ACR.

[0578] Optionally, the transceiver unit 1920 is further configured to receive third information from the currently connected EES, where the third information indicates that the current application has no corresponding ACR scenario, or indicates that the currently connected EES or the currently connected EAS cannot perform ACR.

[0579] In some embodiments, the transceiver unit 1920 is further used to receive fourth information from the currently connected EES, where the fourth information is used to indicate the selection of a target EES that supports the first ACR scene, or to indicate that the first ACR scene is the ACR scene corresponding to the current application.

[0580] In some embodiments, the transceiver unit 1920 is further configured to receive EAS information from a target EES, where the EAS information indicates at least one EAS. The processing unit 1910 is further configured to determine a target EAS based on the EAS information.

[0581] Optionally, the transceiver unit 1920 is further configured to receive fifth information from the target EES, where the fifth information indicates the ACR capability of the at least one EAS.

[0582] Optionally, the at least one EAS supports the first ACR scenario.

[0583] Optionally, the transceiver unit 1920 is also used to send sixth information to the target EES, where the sixth information is used to indicate at least one of the following: selecting a target EAS that supports the first ACR scenario, or the source EES or source EAS cannot perform ACR, or the current application has no corresponding ACR scenario, or requesting to obtain the ACR capability of the EAS.

[0584] It should be understood that when the communication device 1900 is a terminal device, the transceiver unit 1920 in the communication device 1900 can be implemented by a communication interface, for example, it can correspond to the communication interface 2030 in the communication device 2000 shown in Figure 20. The processing unit 1910 in the communication device 1900 can be implemented by at least one processor, for example, it can correspond to the processor 2010 in the communication device 2000 shown in Figure 20.

[0585] Optionally, the communication device 1900 may correspond to the ECS in the aforementioned method embodiment, for example, an ECS, or a component configured in an ECS (such as a chip, a chip system, a processor, etc.), or a logic module or software capable of implementing all or part of the ECS functions. This embodiment of the present application is not limited to this.

[0586] When the device 1900 corresponds to an ECS, it can be used to execute the steps performed by the ECS in the methods shown in Figures 3 to 18 above. The communication device 1900 may include units for executing the methods performed by the ECS in the methods shown in Figures 3 to 18 above. Furthermore, each unit in the communication device 1900 and the other operations and / or functions described above are respectively for implementing the corresponding processes in the methods shown in Figures 3 to 18.

[0587] As an example, the transceiver unit 1920 is configured to send EES information to the terminal device, where the EES information indicates at least one EES. The transceiver unit 1920 is further configured to send first information to the terminal device, where the first information indicates the ACR capability of the at least one EES.

[0588] Optionally, the transceiver unit 1920 is further configured to receive second information from the terminal device, where the second information is used to indicate a request to obtain the ACR capability of the EES.

[0589] As another example, the processing unit 1910 is configured to determine at least one EES that supports a first ACR scenario, where the first ACR scenario is a scenario where ACR is performed by a target EES. The transceiver unit 1920 is configured to send EES information to the terminal device, where the EES information indicates the at least one EES.

[0590] Optionally, the transceiver unit 1920 is also used to receive second information from the terminal device, and the second information is used to indicate at least one of the following: selecting a target EES that supports the target ACR scene, or the currently connected EES or the currently connected EAS cannot perform ACR, or the current application has no corresponding ACR scene.

[0591] It should be understood that when the communication device is an ECS, the transceiver unit 1920 in the communication device 1900 can be implemented by a communication interface, for example, it can correspond to the communication interface 2030 in the communication device 2000 shown in Figure 20. The processing unit 1910 in the communication device 1900 can be implemented by at least one processor, for example, it can correspond to the processor 2010 in the communication device 2000 shown in Figure 20.

[0592] Optionally, the communication device 1900 may correspond to the EES (including the source EES or the target EES) in the above method embodiments, for example, an EES, or a component configured in an EES (such as a chip, a chip system, a processor, etc.), or a logic module or software capable of implementing all or part of the EES functions. This embodiment of the present application is not limited to this.

[0593] When the device 1900 corresponds to an EES, it can be used to execute the steps performed by the EES in the methods shown in Figures 3 to 18 above, such as executing the steps performed by the source EES or executing the steps performed by the target EES. The communication device 1900 may include units for executing the methods performed by the EES in the methods shown in Figures 3 to 18 above. Furthermore, each unit in the communication device 1900 and the other operations and / or functions described above are respectively for implementing the corresponding processes in the methods shown in Figures 3 to 18.

[0594] As an example, the processing unit 1910 is configured to determine that the current application has no corresponding ACR scenario. The transceiver unit 1920 is configured to send third information to the terminal device, where the third information indicates that the current application has no corresponding ACR scenario, or indicates that the EES or the EAS associated with the EES cannot perform ACR.

[0595] As another example, the processing unit 1910 is configured to determine to perform ACR based on a first ACR scenario, where the first ACR scenario is a scenario in which ACR is performed by a target EES. The transceiver unit 1920 is configured to send fourth information to the terminal device, where the fourth information is used to indicate the selection of a target EES that supports the first ACR scenario, or to indicate that the first ACR scenario is the ACR scenario corresponding to the current application.

[0596] Optionally, before the processing unit 1910 determines to perform ACR based on the first ACR scenario, the processing unit 1910 is further configured to determine that the current application has no corresponding ACR scenario.

[0597] As another example, the transceiver unit 1920 is used to send EAS information to the terminal device, where the EAS information indicates at least one EAS; the transceiver unit 1920 is also used to send fifth information to the terminal device, where the fifth information indicates the ACR capability of the at least one EAS.

[0598] Optionally, the transceiver unit 1920 is further configured to receive sixth information from the terminal device, where the sixth information is used to indicate a request to obtain the ACR capability of the EAS.

[0599] As another example, the processing unit 1910 is configured to determine at least one EAS supporting a first ACR scenario, where the first ACR scenario is a scenario where ACR is performed by a target EES. The transceiver unit 1920 is configured to send EAS information to the terminal device, where the EAS information indicates the at least one EAS.

[0600] Optionally, the transceiver unit 1920 is also used to receive sixth information from the terminal device, and the sixth information is used to indicate at least one of the following: selecting a target EAS that supports the first ACR scenario, or the source EES and source EAS cannot perform ACR, or the current application has no corresponding ACR scenario.

[0601] It should be understood that when the communication device is an EES, the transceiver unit 1920 in the communication device 1900 can be implemented by a communication interface, for example, it can correspond to the communication interface 2030 in the communication device 2000 shown in Figure 20. The processing unit 1910 in the communication device 1900 can be implemented by at least one processor, for example, it can correspond to the processor 2010 in the communication device 2000 shown in Figure 20.

[0602] Figure 20 is another schematic block diagram of a communication device provided in an embodiment of the present application. As shown in Figure 20, the device 2000 may include at least one processor 2010. The at least one processor 2010 may be used to implement the functions of a terminal device (including an EEC, etc.), an ECS, or an EES (including a source EES or a target EES) in the method provided in an embodiment of the present application.

[0603] The communication device 2000 may also include at least one memory 2020 for storing program instructions and / or data. The memory 2020 is coupled to the processor 2010. Coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which may be electrical, mechanical, or other forms, and is used for information exchange between the devices, units, or modules. The processor 2010 may operate in conjunction with the memory 2020. The processor 2010 may execute program instructions stored in the memory 2020. At least one of the at least one memory may be included in the processor.

[0604] The communication device 2000 may also include a communication interface 2030 for communicating with other devices via a transmission medium, so that the device in the communication device 2000 can communicate with other devices. Exemplarily, when the communication device 2000 is used to implement the function of the terminal device in the method provided in the embodiment of the present application, the other devices may include ECS and EES. The communication interface 2030 can be, for example, a transceiver, an interface, a bus, a circuit or a device capable of implementing the transceiver function. The processor 2010 can use the communication interface 2030 to send and receive data and / or information, and is used to implement the method performed by the terminal device, ECS or EES in the embodiments corresponding to Figures 3 to 18.

[0605] For example, when the device 2000 is used to implement the function of the terminal device in the method provided in an embodiment of the present application, the processor 2010 can be used to determine the target EES, which is an EES that supports the first ACR scenario, and the first ACR scenario is a scenario in which ACR is executed by the target EES; the processor is also used to control the communication interface 2030 to request the target EES to execute ACR.

[0606] For another example, when the apparatus 2000 is used to implement the ECS function in the method provided in an embodiment of the present application, the processor 2010 may be used to control the communication interface 2030 to send EES information to the terminal device, where the EES information indicates at least one EES.

[0607] For another example, when the device 2000 is used to implement the function of EES in the method provided in an embodiment of the present application, the processor 2010 can be used to determine that the current application has no corresponding ACR scene, and can also be used to control the communication interface 2030 to send a third information to the terminal device, where the third information indicates that the current application has no corresponding ACR scene, or indicates that the EES or the EAS associated with the EES cannot execute ACR.

[0608] It should be understood that the specific process of each unit executing the corresponding step has been described in detail in the aforementioned method embodiment, and for the sake of brevity, it will not be repeated here.

[0609] The specific connection medium between the processor 2010, the memory 2020 and the communication interface 2030 is not limited in the embodiment of the present application.

[0610] It should be noted that the above-described method embodiments can be applied to or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above-described method embodiments can be completed by hardware integrated logic circuits within the processor or by software instructions. The above-described processor may be a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The methods, steps, and logic block diagrams disclosed in the embodiments of this application can be implemented or executed. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in conjunction with the embodiments of this application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules within the decoding processor. The software modules can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. The storage medium is located in a memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above-described method.

[0611] The memory in the embodiment of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Wherein, the non-volatile memory can be a ROM, PROM, EPROM, EEPROM or flash memory. The volatile memory can be a RAM, which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM) and direct rambus random access memory (direct rambus RAM, DR RAM). It should be noted that the memory of the system and method described herein is intended to include but is not limited to these and any other suitable types of memory.

[0612] The present application also provides a chip system, which includes at least one processor for implementing the functions involved in the methods executed by the terminal device, ECS or EES (including source EES or target EES) in the embodiments shown in Figures 3 to 16 above, for example, receiving or processing the data and / or information involved in the above methods.

[0613] In one possible design, the chip system further includes a memory, which is used to store program instructions and data, and the memory is located inside or outside the processor.

[0614] The chip system can be composed of chips, or can include chips and other discrete devices.

[0615] The present application also provides a communication system, including at least one of the aforementioned source EES and target EES, wherein the source EES can implement the functions involved in the source EES in the aforementioned method embodiment; the target EES can implement the functions involved in the target EES in the aforementioned method embodiment.

[0616] Optionally, the communication system further includes an ECS, which can implement the functions involved in the ECS in the aforementioned method embodiment.

[0617] Optionally, the communication system further includes a terminal device, which can implement the functions involved in the terminal device in the aforementioned method embodiment, for example, can implement the functions involved in the EEC.

[0618] The present application also provides a computer program product, which includes: a computer program (also referred to as code, or instructions), which, when executed, enables a computer to execute the method executed by the terminal device, ECS or EES (including source EES or target EES) in the embodiments shown in Figures 3 to 16.

[0619] The present application also provides a computer-readable storage medium storing a computer program (also referred to as code or instructions). When the computer program is executed, the computer executes the method executed by the terminal device, ECS, or EES (including the source EES or the target EES) in the embodiments shown in Figures 3 to 16.

[0620] The methods provided in the above embodiments can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, they can be implemented in whole or in part in the form of a computer program product. The computer program product may include one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic disk), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state disk (SSD)).

[0621] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0622] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

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

[0624] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0625] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0626] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk, or an optical disk.

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

Claims

1. A method for application context migration, characterized in that: Applied to a terminal device, the method comprises: Sending second information to the edge configuration server ECS, where the second information is used to indicate the selection of an edge enabling server EES that supports the application context migration ACR scenario; receiving EES information from the ECS, the EES information indicating at least one EES supporting an ACR scenario; Determine a target EES according to the EES information, where the target EES is one of the at least one EES supporting the ACR scenario; The target EES is requested to perform ACR, so that the terminal device migrates the application context of the terminal device from the source edge application server EAS of the terminal device to the target EAS of the terminal device through the target EES.

2. The method according to claim 1, characterized in that The ACR scenario is a scenario in which the terminal device executes, through an EES supporting the ACR scenario, migration of the application context of the terminal device from a source EAS of the terminal device to a target EAS of the terminal device.

3. The method according to claim 2, characterized in that The method further comprises: First information is received from the ECS, the first information indicating an ACR capability of the at least one EES.

4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: In the case that the current application has no corresponding ACR scenario, or in the case that the currently connected EES or the currently connected EAS cannot perform ACR, it is determined to perform ACR based on the ACR scenario.

5. The method according to claim 4, characterized in that The method further comprises: Third information is received from the currently connected EES, where the third information indicates that the current application has no corresponding ACR scenario, or indicates that the currently connected EES or the currently connected EAS cannot perform ACR.

6. The method according to any one of claims 1 to 3, characterized in that Before determining the target EES, the method further includes: Fourth information is received from the currently connected EES, where the fourth information is used to indicate selection of a target EES that supports the ACR scene, or to indicate that the ACR scene is an ACR scene corresponding to a current application.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: receiving EAS information from the target EES, the EAS information indicating at least one EAS; The target EAS is determined according to the EAS information.

8. The method according to claim 7, characterized in that The method further comprises: Fifth information is received from the target EES, the fifth information indicating an ACR capability of the at least one EAS.

9. The method according to claim 7 or 8, characterized in that The at least one EAS supports the ACR scenario.

10. The method according to any one of claims 7 to 9, characterized in that The method further comprises: Sending sixth information to the target EES, where the sixth information is used to indicate at least one of the following: Select the target EAS that supports the ACR scenario. The source EES or source EAS cannot perform ACR, The current application has no corresponding ACR scene, or Request to obtain the ACR capability of EAS.

11. A communication method, characterized in that: Applied to edge configuration server ECS, the method includes: receiving second information from a terminal device, where the second information is used to indicate selection of an edge enabling server EES supporting an application context migration ACR scenario; EES information is sent to the terminal device, where the EES information indicates at least one EES that supports the ACR scenario.

12. The method according to claim 11, characterized in that The ACR scenario is a scenario in which the terminal device executes migration of the application context of the terminal device from the source edge application server EAS of the terminal device to the target EAS of the terminal device through the EES supporting the application context migration scenario.

13. The method according to claim 12, characterized in that The method further comprises: Sending first information to the terminal device, wherein the first information indicates the ACR capability of the at least one EES.

14. A communication method, characterized in that: Applied to edge configuration server ECS, the method includes: Determine at least one edge enabling server EES that supports an application context migration ACR scenario, wherein the ACR scenario is a scenario in which ACR is performed by a target EES; EES information is sent to the terminal device, where the EES information indicates the at least one EES.

15. The method according to claim 14, characterized in that The method further includes: sending first information to the terminal device, wherein the first information indicates the ACR capability of the at least one EES.

16. The method according to claim 14 or 15, characterized in that The method further comprises: receiving second information from the terminal device, where the second information is used to indicate at least one of the following: Select the target EES that supports the target ACR scenario, The currently connected EES or the currently connected edge application server EAS cannot perform ACR, or The current application has no corresponding ACR scenario.

17. A communication method, characterized in that: Applied to an edge enabling server EES, the method comprises: Determine that the current application has no corresponding application context migration ACR scenario; The third information is sent to the terminal device, where the third information indicates that the current application has no corresponding ACR scenario, or indicates that the EES or the currently connected edge application server EAS cannot perform ACR.

18. A communication method, characterized in that: Applied to an edge enabling server EES, the method comprises: Determine to perform ACR based on an application context migration ACR scenario, where the ACR scenario is a scenario in which ACR is performed by a target EES; Send fourth information to the terminal device, where the fourth information is used to indicate the selection of a target EES that supports the ACR scene, or to indicate that the ACR scene is the ACR scene corresponding to the current application.

19. The method according to claim 18, characterized in that Before determining to perform ACR based on the ACR scenario, the method further includes: Make sure that the current application has no corresponding ACR scenario.

20. A communication method, characterized in that: Applied to an edge enabling server EES, the method comprises: Sending edge application server EAS information to the terminal device, wherein the EAS information indicates at least one EAS; Fifth information is sent to the terminal device, where the fifth information indicates the application context migration ACR capability of the at least one EAS.

21. The method of claim 20, wherein: The method further comprises: Receive sixth information from the terminal device, where the sixth information is used to indicate a request to obtain the ACR capability of the EAS.

22. A communication method, characterized in that: Applied to an edge enabling server EES, the method comprises: Determine at least one edge application server EAS that supports an application context migration ACR scenario; the ACR scenario is a scenario in which ACR is executed by a target EES; EAS information is sent to the terminal device, where the EAS information indicates the at least one EAS.

23. The method of claim 22, wherein: The method further includes: sending fifth information to the terminal device, wherein the fifth information indicates the ACR capability of the at least one EAS.

24. The method according to claim 22 or 23, characterized in that The method further comprises: Receive sixth information from a terminal device, where the sixth information is used to indicate at least one of the following: Select the target EAS that supports the ACR scenario. The source EES and source EAS cannot perform ACR, or The current application has no corresponding ACR scenario.

25. A communication device, characterized in that: Used to implement the method as claimed in any one of claims 1 to 10, or, used to implement the method as claimed in any one of claims 11 to 16, or, used to implement the method as claimed in any one of claims 17 to 19, or, used to implement the method as claimed in any one of claims 20 to 24.

26. A communication device, characterized in that: Comprising a processor, the processor is used to execute program code so that the communication device implements the method as described in any one of claims 1 to 10, or, implements the method as described in any one of claims 11 to 16, or, implements the method as described in any one of claims 17 to 19, or, implements the method as described in any one of claims 20 to 24.

27. A communication system comprising at least one of a source edge enabling server (EES) and a target EES, wherein: The source EES is used to implement the method according to any one of claims 17 to 19, and the target EES is used to implement the method according to any one of claims 20 to 24.

28. The communication system according to claim 27, characterized in that The communication system further comprises an edge configuration server ECS, wherein the ECS is configured to implement the method according to any one of claims 11 to 16.

29. The communication system according to claim 27 or 28, characterized in that: The communication system further comprises a terminal device, wherein the terminal device is configured to implement the method according to any one of claims 1 to 10.

30. A method, characterized in that The method comprises: The terminal sends second information to the edge configuration server ECS, where the second information is used to indicate the selection of an edge enabling server EES that supports the application context migration ACR scenario; The ECS sends EES information to the terminal, where the EES information indicates at least one EES that supports the ACR scenario; The terminal determines a target EES according to the EES information, where the target EES is one of the at least one EES supporting the ACR scenario; The terminal requests the target EES to perform ACR, so that the terminal device migrates the application context of the terminal device from the source edge application server EAS of the terminal device to the target EAS of the terminal device through the target EES.

31. The method of claim 30, wherein: The ACR scenario is a scenario in which the terminal device executes, through an EES supporting the ACR scenario, migration of the application context of the terminal device from a source EAS of the terminal device to a target EAS of the terminal device.

32. A communication system, characterized in that: The communication system comprises: A terminal device, configured to implement the method according to any one of claims 1 to 10; A network side device is used to communicate with the terminal device.

33. The communication system according to claim 32, characterized in that The network side device includes at least one of an edge configuration server ECS and an edge enabling server EES.