Method and apparatus for context relocation

Abstract

The application provides a method and device for application context relocation, the method comprising: for an application context relocation (ACR) of service continuity planning, determining, by an edge enabling server, that a terminal device moves to a target position, and sending, by the edge enabling server, an ACR completion message to the terminal device. The method for application context relocation provided by the application can switch an application client to a target edge application server when it is determined that the terminal device moves to the target position, thereby avoiding service interruption of the application client caused by early switching.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a method and apparatus for application context relocation. Background Technology

[0002] In multi-access edge computing, when a terminal device moves outside its current service area during the operation of an edge application, the currently providing edge application server may no longer be able to provide services to the currently running application client, or the currently providing edge application server may no longer be the optimal application server to provide services to the terminal device. Other edge application servers may be more suitable to provide services to the application clients on the terminal device. Therefore, it is necessary to replace the currently providing edge application server with a new one. During this process, the application service may be temporarily suspended or interrupted. Therefore, the context information of the application client is migrated to the new edge application server in advance to minimize the impact of application interruption. Summary of the Invention

[0003] This application provides a method and apparatus for Application Context Relocation (ACR). The ACR method enables the terminal device to be disconnected from the source edge application server and connected to the target edge application server when the terminal device moves to the target location, thereby avoiding service interruption of the terminal device caused by premature switching.

[0004] Firstly, a method for application context relocation is provided, which includes: for application context relocation (ACR) of service continuity planning, when the edge enabling server determines that the terminal device has moved to the target location, the edge enabling server sends an ACR completion message to the terminal device.

[0005] Specifically, the target location is the service range of the target edge application server or the expected location of the terminal device.

[0006] It should be understood that the expected location of the terminal device may also be referred to as the predicted location, etc., and this application does not limit it in this way.

[0007] According to the ACR method provided in this application, when the terminal device moves to the target location, the edge enabling server sends an ACR completion message to the terminal device. After receiving the ACR completion message, the edge application client disconnects the terminal device from the source edge application server and connects to the target edge application server, thus avoiding service interruption of the terminal device caused by premature switching.

[0008] In conjunction with the first aspect, in some implementations of the first aspect, the edge enabling server receives first indication information from the terminal device, which instructs the edge enabling server to determine the mobility of the terminal device; or, the edge enabling server receives second indication information from the terminal device, which indicates that the edge enabling client of the terminal device does not support determining the mobility of the terminal device. This process involves the terminal device instructing the edge enabling server to determine the mobility of the terminal device, or the terminal device and the edge enabling server negotiating capabilities. This enables the edge enabling server to determine the mobility of the terminal device according to the indication, improving the reliability of communication.

[0009] In conjunction with the first aspect, in some implementations of the first aspect, the edge enabling server detects the event of the ACR, and the event type of the ACR is the ACR of service continuity planning;

[0010] Optionally, the edge enabling server stores at least one of the following: the event type of the ACR, the application client ID corresponding to the ACR, and the target location corresponding to the ACR;

[0011] The edge-enabled server determines when a terminal device moves to a target location, including:

[0012] The edge enabling server determines that the terminal device has moved to the target location based on the application client ID corresponding to the ACR and / or the target location corresponding to the ACR. Optionally, the edge enabling server also determines that the terminal device has moved to the target location based on the event type of the ACR.

[0013] In conjunction with the first aspect, in some implementations of the first aspect, the edge enabling server receives at least one of the following from the edge application server: the event type of the ACR, the application client ID corresponding to the ACR, and the target location corresponding to the ACR;

[0014] The edge-enabled server determines when a terminal device moves to a target location, including:

[0015] The edge enabling server determines that the terminal device has moved to the target location based on the application client ID corresponding to the ACR and / or the target location corresponding to the ACR. Optionally, the edge enabling server also determines that the terminal device has moved to the target location based on the event type of the ACR.

[0016] In conjunction with the first aspect, in some implementations of the first aspect, the edge enabling server obtains the current location of the terminal device;

[0017] The edge-enabled server determines when a terminal device moves to a target location, including:

[0018] The edge enabling server determines whether the terminal device moves to the target location based on the terminal device's current location, the application client ID corresponding to the ACR, and the target location corresponding to the ACR.

[0019] The edge-enabled server determines the target location of the terminal device based on the current location of the terminal device and the application client ID corresponding to the ACR.

[0020] Optionally, the edge enabling server can also determine the location where the terminal device has moved based on the event type of the ACR.

[0021] In conjunction with the first aspect, in certain implementations of the first aspect, the edge enabling server sends a subscription message to the core network. This subscription message is used to subscribe to the mobility of terminal devices. The subscription message includes the application client ID (or terminal device ID) corresponding to the ACR and / or the target location corresponding to the ACR. The edge enabling server determines that the terminal device has moved to the target location, including:

[0022] The edge enabling server receives a notification message sent by the core network, which instructs the terminal device to move to the target location.

[0023] It should be noted that before the edge enabling server sends the ACR completion message to the terminal device, it needs to determine that the application context transfer (ACT) is complete. ACT completion indicates that the application context has been transferred from the source edge application server to the target edge application server.

[0024] Secondly, corresponding to some implementations of the first aspect, when the edge application server detects the ACR event, the edge application server detects the ACR event, and the event type of the ACR is the ACR of service continuity planning; the edge application server sends at least one of the following to the edge enabling server: the event type of the ACR, the application client ID corresponding to the ACR, and the target location corresponding to the ACR.

[0025] Thirdly, corresponding to certain implementations of the first aspect, the terminal device sends a first indication message or a second indication message to the edge enabling server. The first indication message instructs the edge enabling server to determine the mobility of the terminal device. Alternatively, the terminal device sends a second indication message to the edge enabling server, indicating that the edge enabling client of the terminal device does not support determining the mobility of the terminal device. This process involves the terminal device instructing the edge enabling server to determine the mobility of the terminal device, or the terminal device and the edge enabling server negotiating capabilities. This enables the edge enabling server to determine the mobility of the terminal device based on the indication, improving the reliability of communication.

[0026] Fourthly, a method for application context relocation is provided, which includes: an edge-enabled client receiving an application context relocation (ACR) completion message sent by an edge-enabled server; and for service continuity planning (ACR), when the edge-enabled client determines that the terminal device has moved to the target location, switching the application client from the source edge application server to the target edge application server.

[0027] Specifically, the target location is the service range of the target edge application server or the expected location of the terminal device.

[0028] It should be understood that the expected location of the terminal device may also be referred to as the predicted location, etc., and this application does not limit it in this way.

[0029] According to the method provided in this application, when the edge-enabled client determines that the terminal device has moved to the target location, it disconnects the terminal device from the source edge application server and connects it to the target edge application server, thus avoiding service interruption of the terminal device caused by premature switching.

[0030] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the edge-enabled client detects the event of the ACR, and the type of the ACR event is the ACR of service continuity planning;

[0031] Optionally, the edge-enabled client stores at least one of the following: the type of the ACR event, the application client ID corresponding to the ACR event, and the target location corresponding to the ACR event;

[0032] Edge-enabled clients determine when a terminal device has moved to a target location, including:

[0033] The edge-enabled client determines that the terminal device has moved to the target location based on the application client ID corresponding to the ACR and / or the target location corresponding to the ACR. Optionally, the edge-enabled client also determines that the terminal device has moved to the target location based on the event type of the ACR.

[0034] It should be noted that before an edge-enabled client switches its application client from the source edge application server to the target edge application server, it needs to ensure that the Application Context Transfer (ACT) is completed.

[0035] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the edge-enabled client receives at least one of the following from the edge-enabled server: the event type of the ACR, the application client ID corresponding to the ACR, and the target location corresponding to the ACR;

[0036] Edge-enabled clients determine when a terminal device has moved to a target location, including:

[0037] The terminal device is moved to the target location based on the application client ID corresponding to the ACR and / or the target location corresponding to the ACR. Optionally, the edge-enabled client also determines that the terminal device has moved to the target location based on the event type of the ACR.

[0038] It should be noted that before an edge-enabled client switches its application client from the source edge application to the target edge application, it needs to confirm that the application context transfer (ACT) is complete. ACT completion indicates that the application context has been transferred from the source edge application server to the target edge application server.

[0039] Fifthly, corresponding to the fourth aspect, when the edge enabling server detects an ACR event, the edge enabling server detects the ACR event, and the event type of the ACR is Service Continuity Planning ACR.

[0040] The edge-enabled server sends at least one of the following to the edge-enabled client: the event type of the ACR, the application client ID corresponding to the ACR, and the target location corresponding to the ACR.

[0041] Sixthly, a method for application context relocation is provided, the method comprising: for application context relocation (ACR) of service continuity planning, an edge application server sending the application client ID corresponding to the ACR and / or the target location corresponding to the ACR to an edge enabling server; the edge application server receiving a first notification message from the edge enabling server, the first notification message instructing a terminal device to move to the target location; and the edge application server sending indication information to the edge enabling server according to the first notification message, the indication information instructing the application context transfer (ACT) to be completed.

[0042] According to the method provided in this application, the application client ID corresponding to the ACR and / or the target location corresponding to the ACR are sent from the edge application server to the edge enabling server. This allows the edge enabling server to determine that the terminal device has moved to the target location based on the information before sending the instruction information to the edge application server. This avoids the signaling waste caused by frequently sending the location information of the terminal device to the edge application server and saves signaling overhead.

[0043] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the edge application server sends a subscription message to the edge enabling server, which instructs the edge enabling server to send a first notification message to the edge application server when the terminal device moves to the target location.

[0044] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the edge application server detects the event of the ACR, and the time type of the ACR is Service Continuity Planning ACR.

[0045] In the seventh aspect, corresponding to the sixth aspect, the edge enabling server receives the application client ID corresponding to the ACR and / or the target location corresponding to the ACR sent by the edge application client;

[0046] The edge enable server sends a first notification message to the edge application server, which instructs the terminal device to move to the target location.

[0047] In conjunction with aspect seven, in some implementations of aspect seven, the edge enabling server receives a subscription message sent by the edge enabling client, which instructs the edge enabling server to send a first notification message to the edge application server when the terminal device moves to the target location.

[0048] Eighthly, an apparatus is provided, comprising units for performing steps of the communication method in any of the first to seventh aspects and their implementations.

[0049] In one design, the communication device is a communication chip, which may include input circuitry or interface for transmitting information or data, and output circuitry or interface for receiving information or data.

[0050] In another design, the communication device is a communication equipment (e.g., an edge-enabled server), and the communication chip may include a transmitter for sending information and a receiver for receiving information or data.

[0051] A ninth aspect provides a communication device, including a processor and a memory for storing a computer program, the processor for calling and running the computer program from the memory, such that the communication device performs the communication method of any one of the first to seventh aspects and their respective implementations.

[0052] Optionally, the processor may be one or more, and the memory may be one or more.

[0053] Optionally, the memory may be integrated with the processor, or the memory may be separated from the processor.

[0054] Optionally, the communication device may also include a transmitter and a receiver.

[0055] In a tenth aspect, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code or instructions), which, when the computer program is run, causes a computer to execute any one of the first to seventh aspects and their respective implementations of the communication method.

[0056] Eleventhly, a communication system is provided, comprising: at least one means for performing the method of the first aspect and its implementations.

[0057] Optionally, the communication system further includes at least one means for performing the methods of the second aspect and its various implementations.

[0058] Optionally, the communication system further includes at least one means for performing the methods of the third aspect and its various implementations.

[0059] In a twelfth aspect, a communication system is provided, comprising: at least one means for performing the methods of the fourth aspect and its implementations.

[0060] Optionally, the communication system further includes at least one means for performing the methods of the fifth aspect and its various implementations.

[0061] In a thirteenth aspect, a communication system is provided, comprising: at least one means for performing the methods of the sixth aspect and its implementations.

[0062] Optionally, the communication system further includes at least one means for performing the methods of the seventh aspect and its various implementations.

[0063] In a fourteenth aspect, a chip system is provided, including a memory and a processor, the memory for storing a computer program and the processor for calling and running the computer program from the memory, such that a communication device equipped with the chip system performs the communication methods of any of the above aspects and their implementations.

[0064] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data. Attached Figure Description

[0065] Figure 1 This is a schematic diagram of the system architecture of an embodiment of this application.

[0066] Figure 2 This is a schematic diagram of the application context relocation process in an embodiment of this application.

[0067] Figure 3 This is a schematic diagram illustrating an example of an application context relocation method according to an embodiment of this application.

[0068] Figure 4 This is a schematic diagram illustrating another example of the application context relocation method in this application embodiment.

[0069] Figure 5 This is a schematic diagram illustrating another example of the application context relocation method in this application embodiment.

[0070] Figure 6 This is a schematic diagram illustrating another example of the application context relocation method in this application embodiment.

[0071] Figure 7 This is a schematic diagram illustrating another example of the application context relocation method in this application embodiment.

[0072] Figure 8 This is a schematic diagram illustrating another example of the application context relocation method in this application embodiment.

[0073] Figure 9 This is a schematic diagram illustrating another example of the application context relocation method in this application embodiment.

[0074] Figure 10 This is a schematic diagram illustrating another example of the application context relocation method in this application embodiment.

[0075] Figure 11 This is a schematic diagram illustrating another example of the application context relocation method in this application embodiment.

[0076] Figure 12 This is a schematic diagram of an example of a communication device for application context relocation according to an embodiment of this application.

[0077] Figure 13 This is a schematic diagram of another example of a communication device for application context relocation according to an embodiment of this application. Detailed Implementation

[0078] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0079] The technical solutions of this application embodiment can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) system, 5th Generation (5G) system, or New Radio (NR), etc.

[0080] In this application, the terminal device can refer to user equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user equipment. The terminal device can also be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal device in a 5G network, or terminal device in an evolved Public Land Mobile Network (PLMN), etc. This application does not limit the scope of the terminal device to these specific types.

[0081] The network device in this application embodiment can be a device for communicating with terminal devices. The network device can be a base station (BTS) in a Global System of Mobile communication (GSM) system or Code Division Multiple Access (CDMA), a base station (NodeB, NB) in a Wideband Code Division Multiple Access (WCDMA) system, an evolved NodeB (eNB or eNodeB) in an LTE system, or a radio controller in a Cloud Radio Access Network (CRAN) scenario. Alternatively, the network device can be a relay station, access point, vehicle-mounted device, wearable device, or a network device in a 5G network or an evolved PLMN network, etc. The embodiments of this application are not limited to these.

[0082] The following is a brief explanation of the relevant technical terms involved in the embodiments of this application.

[0083] 1. Multi-Access Edge Computing (MEC)

[0084] MEC can leverage wireless access networks to provide telecom users with the IT services and cloud computing capabilities they need, creating a high-performance, low-latency, and high-bandwidth carrier-grade service environment. This accelerates the download of various content, services, and applications on the network, allowing consumers to enjoy an uninterrupted, high-quality network experience.

[0085] 2. Data Network (DN)

[0086] Data networks refer to service networks provided by operators or third parties, which can provide services to terminal devices, such as operator services and internet services.

[0087] 3. Local Data Network (Local DN)

[0088] A local data network is an access point of a data network located very close to the user's attachment point.

[0089] 4. Application Context

[0090] This refers to runtime status information related to one or more users. Optionally, it may also include the context of the subscriptions of the one or more users to the source application instance or edge application EAS and the core network, such as the transaction identifier of the subscription. Optionally, it may also include the context of the one or more users on the edge enabling server EES, such as the transaction identifier of the subscription of the one or more users to the source EAS.

[0091] 5. Application Context Relocation (ACR)

[0092] During the operation of edge applications, when a terminal device moves outside its current service area, such as between edge data networks (EDNs) or between local area data networks (LADNs), the currently serving edge application server (EAS) may no longer be able to provide services for the currently running application, or the currently serving edge application server (EAS) may no longer be the optimal application server to serve the terminal device. Other EASs may be more suitable for serving the application clients on the terminal device. Therefore, a new edge application server (EAS) needs to be selected to serve the terminal device. This process will cause the application service to be temporarily suspended or interrupted. The application context needs to be migrated to the new EAS to minimize the impact of application interruption.

[0093] Figure 1 This is a schematic diagram of the system architecture according to an embodiment of this application. The following describes... Figure 1 A brief introduction to the functional entities and interfaces involved is provided.

[0094] 1. Edge Data Network (EDN)

[0095] In one possible implementation, an EDN corresponds to a data network, specifically a local data network (DN), which may include edge-enabled functions and can be identified using DNAI and DNN; it is a logical network concept. In another possible implementation, an EDN is a peer-to-peer concept of the central cloud, which can be understood as a local data center (geographical location concept), identified using DNAI, and may contain multiple local data networks.

[0096] 2. Application Example / Edge Application Server (EAS)

[0097] Edge applications are applications deployed in edge data networks. Specifically, an edge application can refer to an instance of a server application (e.g., social media software, augmented reality (AR), virtual reality (VR)) deployed and running on an EDN. An application can deploy one or more EASs in one or more ENDs. EASs deployed and running in different EDNs can be considered as different EASs of the same application; they can share a domain name, use the same IP address, or use different IP addresses. EAS can also be called edge application server, application instance, MEC application server, EAS functionality, etc.

[0098] 3. Application Client (AC)

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

[0100] 4. Edge Enabler Server (EES)

[0101] Edge Enabler Servers (EES) provide enabling capabilities for Edge Application Controllers (EAS) deployed in the Edge Data Network (EDN), better supporting edge application deployments within the MEC. They support EAS registration, authentication and authorization of terminal devices, and providing EAS IP address information to terminal devices. Furthermore, they support obtaining EAS identifiers and IP address information and sending this information to the EDN. EES are deployed within the EDN. Typically, an EAS registers with an EES, or an EAS's information is configured on an EES through a management system. This EES is called the EES associated with the EAS, and it controls / manages the EAS registered / configured on it.

[0102] 5. Edge Enabler Client (EEC):

[0103] EEC is the peer entity of EES on the terminal device side. EEC is used to register EEC information and application client information with EES, perform security authentication and authorization, obtain EAS IP address from EES, and provide edge computing enabling capabilities to application clients, such as EAS discovery service, returning EAS IP address to application clients, etc.

[0104] It should be noted that, in the embodiments of this application, a terminal device may include one or more EECs. It should be understood that, in the embodiments of this application, the EEC and the terminal device may be interchangeable in certain circumstances.

[0105] 6. Edge Configuration Server (ECS)

[0106] ECS is responsible for EDN configuration, such as providing EES information to terminal devices, and can also directly provide EAS information to terminal devices, as well as interacting with the application's DNS to obtain EAS information. Furthermore, it obtains and saves EAS and IP address information from other functional entities.

[0107] It's important to note that application users sign service agreements with application providers to obtain services. Application users communicate with the EAS (Edge Enablement System) by logging into the application client on their terminal device. The edge-enabled client is a middleware layer, typically located within the operating system or between the application client and the operating system. The application client can obtain edge-enabled services from the edge-enabled client via an application programming interface (API).

[0108] Figure 2 This is a schematic diagram of the Application Context Relocation (ACR) process according to an embodiment of this application.

[0109] ACR is mainly divided into four stages:

[0110] Phase 1: ACR detection.

[0111] ACR's detection and judgment may require context transfer. In this case, the detection entity usually detects some events, such as changes in the location of the terminal device or updates to the user plane path of the terminal device.

[0112] Phase Two: ACR Decision-Making.

[0113] The decision-making entity determines that ACR is required.

[0114] Phase 3: Execution of ACR.

[0115] The main function is to transfer the AC's context information from the source EAS to the predicted EAS or the EAS that has already been moved to. This step can further include sending information to the terminal devices notifying them of the predicted EAS, and sending network devices information related to the completion of the context migration and the predicted EAS, such as the predicted EAS address and its corresponding routing information.

[0116] It should be noted that before performing context migration, the target EES needs to be discovered. This process always follows a two-level discovery mechanism: first, the EES platform is discovered, and then the EAS is discovered from the EES platform.

[0117] As an example, and not a limitation, when the location of a terminal device changes, the detection entity of the ACR predicts that the EAS of the terminal device will change. The context information of the terminal device can be sent from the source EAS to the predicted target EAS in advance. This type of ACR that sends the context information to the target EAS in advance corresponds to the ACR of service continuity planning. By predicting and sending the context information of the terminal device in the source EAS to the target EAS in advance, the service terminal is avoided from being affected by the context migration after the terminal device moves to the target EAS.

[0118] As an example, and not a limitation, when the user plane path of a terminal device changes, and the terminal device has disconnected from the source EAS and connected to the target EAS, the ACR detection entity determines that the terminal device's EAS has changed and sends the context information of the source EAS to the target EAS. Because the context migration occurs after the terminal device switchover, it will cause service interruption. This ACR type can correspond to a normal ACR.

[0119] Phase 4: Post-ACR cleanup.

[0120] This step involves multiple entities. For example, it could involve the application client initiating a new socket connection to the target EAS.

[0121] The following section details the discovery process for the EES platform and EAS.

[0122] Step 1: The terminal device's EEC discovers the EES platform from the ECS.

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

[0124] 2. The ECS platform contains detailed information about EAS. Based on the location of the terminal device, the data network access identifier (DN Access Identifier, DNAI) is obtained. Combining the DNAI, the fully qualified domain name (FQDN), and the EES profile filter, a suitable EES is selected for each AC. The location of the terminal device is taken into account when selecting the EES platform.

[0125] 3. Obtain current or potential DNAI.

[0126] 4. The EEC obtains information about one or more EES from the ECS.

[0127] Step 2: EEC discovers EAS from the EES platform.

[0128] 1. The EEC sends an EAS discovery request message to the EES, carrying the EAS discovery request including the EEC ID and security credentials, and may include an EAS discovery filter to retrieve information about a specific EAS or a specific type of EAS (such as game applications).

[0129] 2. EES matches registered AC information. Based on locally registered or online EAS information and user-provided discovery filtering parameters, EES matches EAS that meet the user's request. If multiple EAS are satisfied, multiple EAS can be returned.

[0130] 3. The EES returns EAS information to the EEC. The EEC can then provide this information to the AC, which can then connect to the EAS.

[0131] It should be noted that the detection, decision-making, execution, and cleanup of ACR can be performed by different functional entities. The following examples illustrate the specific processes of ACR execution by different functional entities. It should also be noted that when the type of ACR event corresponds to a Service Continuity Planning (SCP) ACR, since the target EES and target EAS have not yet been discovered, the ACR detection is performed by the EEC, the source EES, or the source EAS.

[0132] Option 1: The EEC initiates an ACR and uses the regular EAS for discovery.

[0133] ACR detection: EEC may need to perform context migration, for example, when EEC detects a change in the location of the terminal device.

[0134] ACR decision: The EEC decided that an ACR was necessary.

[0135] The execution of ACR: EEC discovers the target EES and target EAS; EEC requests the source EES to initiate user plane path modification; EEC and AC initiate application context migration.

[0136] Cleaning up ACR.

[0137] Option 2: EEC executes ACR through the source EES.

[0138] ACR detection: EEC may need to perform context migration, for example, when EEC detects a change in the location of the terminal device.

[0139] ACR decision: The EEC decided that an ACR was necessary.

[0140] ACR execution: EEC discovers the target EES and target EAS; EEC requests the source EES to initiate user plane path modification; source EES notifies source EAS to initiate application context migration.

[0141] Cleaning up ACR.

[0142] Option 3: The EEC executes ACR through the target EES.

[0143] ACR detection: EEC may need to perform context migration, for example, when EEC detects a change in the location of the terminal device.

[0144] ACR decision: The EEC decided that an ACR was necessary.

[0145] ACR execution: EEC discovers the target EES and target EAS; EEC requests the target EES to initiate user plane path modification; target EES notifies target EAS to initiate application context migration.

[0146] Cleaning up ACR.

[0147] Option 4: The source EAS initiates the ACR process.

[0148] ACR detection: The source EES detects and notifies the source EAS of an ACR requirement, or the source EAS detects an ACR requirement; or the terminal device uses the expected or predicted location to trigger service continuity planning.

[0149] ACR decision: The source EAS determines that ACR is required.

[0150] Execution of ACR: The source EAS discovers the target EES and the target EAS, or the source EAS uses the terminal device's expected or predicted location to execute the target EES and the target EAS at the terminal's predicted location, and initiates user plane path modification and performs application context transfer.

[0151] Cleaning up ACR.

[0152] Option 5: Execute ACR on the source EES.

[0153] ACR detection: Source EES, source EAS, and source EEC can all determine if context transfer may be necessary.

[0154] ACR's decision: The detected entity notifies the source EES, and the source EES makes the decision to perform application context migration.

[0155] The execution of ACR is as follows: the source EES discovers the target EES and the target EAS; the source EES initiates a user plane path modification; the source EES notifies the source EAS to initiate an application context migration.

[0156] Cleaning up ACR.

[0157] Option 6: Automatic ACR.

[0158] ACR detection: Source EES.

[0159] ACR's decision: The source EES decision performs application context migration.

[0160] ACR execution: The source EES discovers the target EES and the target EAS; the source EES initiates user plane path modification; the source EES initiates application context migration.

[0161] Cleaning up ACR.

[0162] Figure 3 This is an example of an application context relocation method according to an embodiment of this application. Figure 3 In the method shown, the EES determines the type of ACR, and the EES performs mobility determination of the terminal device. The method 300 includes:

[0163] S310, the EEC sends a first instruction message or a second instruction message to the EES. The first instruction message instructs the EES to determine the mobility of the terminal device, and the second instruction message instructs the EEC not to determine the mobility of the terminal device.

[0164] Specifically, the first instruction information instructs the EES to determine the mobility of the terminal device. It should be understood that determining the mobility of the terminal device can be done by determining whether the terminal device is located at the target location.

[0165] Specifically, the target location can be the service area of ​​the target EAS or the expected location of the terminal equipment.

[0166] It should be understood that the service range of the target EAS can be: the area covered by the data network corresponding to the DNAI of the target EAS, or the geographical location of the target EAS, etc.

[0167] It should be understood that the expected location of the terminal device can be: the DNAI corresponding to the target EAS that the terminal device will access, or the expected geographical location of the terminal device, or the cell that the terminal device is expected to access, or the expected tracking area (TA) of the terminal device, etc.

[0168] It should be noted that the expected location of the terminal device can also be named the predicted location of the terminal device, the location that the terminal device is about to move to, etc. This application embodiment does not impose any special restrictions on the name.

[0169] It should be understood that the first indication information can be a cell instructing the EES to determine the mobility of the terminal device. Optionally, the first indication information may also include a cell instructing the EES to determine the timing of sending the ACR completion message. Optionally, the timing of sending the ACR completion message may be the completion of the Application Context Transmission (ACT) or the terminal device moving to the target location, where ACT completion indicates that the application context information has been sent from the source EAS to the target EAS. The above indication method containing specific cells can be considered explicit.

[0170] It should be understood that the first indication information can also be an indication information that instructs the EES to detect an ACR event, instructs the EES to trigger an ACR procedure, and / or instructs the EES to execute an ACR procedure. That is, the indication information that instructs the EES to detect an ACR event, instructs the EES to trigger an ACR procedure, and / or instructs the EES to execute an ACR procedure also instructs the EES to determine the mobility of the terminal device. This indication method can be considered implicit. Upon receiving the first indication information, the EES determines that it will execute the ACR detection procedure and / or trigger the ACR procedure, and the EES itself determines the mobility of the terminal device. Optionally, the EES also determines the timing of sending the ACR completion message. Optionally, this sending timing can be the same as described in the previous paragraph, and will not be repeated here.

[0171] It should be understood that the EEC instructs the EES to determine the mobility of the terminal device through the first indication information. The EEC may support determining the mobility of the terminal device but may not determine the mobility of the terminal device itself, or the EEC may not support determining the mobility of the terminal device.

[0172] It should be noted that before or during ACR, EES can negotiate capabilities with EEC. For example, EES can send a signaling message to EEC indicating that EES supports determining the mobility of terminal devices, in which case EEC will determine that EES is responsible for determining the mobility of terminal devices. Alternatively, EES may not need to send a signaling message, and EEC will assume that EES supports determining the mobility of terminal devices.

[0173] It should be noted that the EEC may choose not to send the first indication information to the EES. That is, the EEC can default to letting the EES determine the mobility of the terminal device. Optionally, when selecting the ACR method, the EEC and EES may confirm or configure the terminal device's mobility detection entity as the EES. In other words, the terminal device's mobility detection entity has already been confirmed or configured as the EES during the ACR configuration phase. Therefore, the EES, EEC, EAS, and other entities will perform the mobility detection of the terminal device according to the confirmed or configured scheme, with the EES determining the mobility. Optionally, the EES will determine the timing of sending the ACR completion message by default.

[0174] Specifically, the second instruction indicates that the EEC does not support determining the mobility of the terminal device. It should be understood that the EEC's lack of support for determining the mobility of the terminal device can specifically mean that the EEC does not support obtaining the location of the terminal device, and / or the EEC does not support determining the type of ACR, and / or the EEC does not support determining whether the terminal device is located at the target location.

[0175] It should be understood that after receiving the second indication information, the EES determines that the EEC's capability does not support determining the mobility of the terminal device, and thus determines that the EES itself should determine the mobility of the terminal device. Optionally, the EES itself determines when to send the ACR completion message.

[0176] It should be noted that the second indication information carries EEC capability information, that is, it carries a cell indicating that the EEC does not support determining the mobility of the terminal device, and this indication method can be considered to be explicit.

[0177] It should be noted that the second indication information can also be an indication that the EEC does not support detecting ACR events, or an indication that the EEC does not support triggering the ACR procedure. In other words, it indicates that the EEC does not support detecting ACR events, or that the EEC does not support triggering the ACR procedure, and also indicates that the EEC does not support determining the mobility of the terminal device. This indication method can be considered implicit. Upon receiving the second indication information, the EES determines whether to execute the ACR detection procedure or trigger the ACR procedure, and determines the mobility of the terminal device. Optionally, the EES also determines the timing of sending the ACR completion message. Optionally, this sending timing can be the same as described above.

[0178] It should be noted that the EEC may also choose not to send the second instruction information to the EES. The EES may determine the mobility of the terminal device by itself, based on its local configuration information or by requesting EEC capabilities from other network elements.

[0179] The first or second indication information may be included in an existing request message, such as an ACR information subscription request message. Alternatively, the first or second indication information may be sent via a new signaling message, such as an ACR mobility capability message. This application does not limit this approach.

[0180] It should be noted that for EES to determine the mobility of terminal devices, it must first obtain and determine the target location of the terminal devices.

[0181] Specifically, EES can obtain the target location of terminal devices through the capabilities of the 3GPP core network.

[0182] For example, EES can obtain the target location of terminal devices by subscribing to UPPM (user plane path management) event notifications from the 3GPP core network.

[0183] For example, EES can also obtain the target location of the terminal device through APIs (application programming interfaces) exposed to the 3GPP core network, such as SCEF (service capability exposure function) / NEF (network exposure function) / SCEF+NEF (network exposure function) or LCS (Location Service).

[0184] For example, EES can also analyze the expected behavior of terminal devices and obtain the target location of terminal devices based on the NEF (Network Exposure Function) or NWDAF (Network Data Analytics Function) opened by the 3GPP core network.

[0185] Specifically, EES can obtain relevant information from AC through EEC to obtain the target location of terminal devices. This relevant information includes at least one of the following: AC plan / schedule, expected AC geographic service area, expected service KPI, and a list of preferred ECSPs (Edgecomputing service providers).

[0186] It should be noted that the EEC can do so through the above-mentioned methods. Figure 1 The EDGE-5 interface in the described system architecture can obtain the above-mentioned relevant information, but it can also obtain the above-mentioned relevant information through other paths. This application embodiment does not limit this.

[0187] It should be noted that, as mentioned above, step S310 is optional. It can also be that the EES determines the mobility of the terminal device by default, or that the EES determines the mobility of the terminal device without sending the first indication information or the second indication information during the configuration phase.

[0188] S320, EES determines the event type of the ACR.

[0189] It should be understood that, if the EES detects the event of the ACR, the EES will further determine the event type of the ACR.

[0190] It should be noted that the events for this ACR can be, for example, EAS overload, terminal device movement, prediction that the terminal device will move, or source EAS being unable to provide service.

[0191] Specifically, the event type of this ACR can include ordinary ACR and service continuity planning ACR. It should be understood that the event type of the ACR in this application can also be referred to as the type of ACR, and therefore, the event type of ACR in the following text can be directly replaced by the type of ACR.

[0192] Among them, the ordinary ACR is an ACR that does not need to determine whether the terminal device has reached the target location. In other words, the ACR completion message of the ordinary ACR can be sent when the ACT is completed. After receiving the ACR completion message, the EEC can switch the AC from the source EAS to the target EAS.

[0193] As an example of a typical ACR (Active Response Code) rather than a limitation, if a terminal device has moved to the service range of another EAS, the detection entity, such as the EES, detects an ACR event, indicating that the terminal device has moved to the service range of another EAS. Further, the EES initiates the ACR process, sending the corresponding context information to the target EAS (which could be the EAS to which the terminal device has moved). When the ACT (Active Response Code) is completed, the EEC (Electronic Control Center) receives the ACR completion notification and switches the AC (Active Response Center) from the source EAS to the target EAS, without needing to determine the mobility of the terminal device.

[0194] Service continuity planning (ACR), also known as predictive ACR, can be an ACR that anticipates a potential change in the EAS serving the AC and proactively transmits context information to the target EAS. This application does not impose any specific limitations on this. For example, it could be an ACR that predicts the terminal will reach a target location and begins before the terminal device arrives at that location. As a service continuity planning ACR, it needs to determine the mobility of the terminal device, i.e., whether to switch the AC from the source EAS to the target EAS after the terminal device reaches the target location. Alternatively, it could be that the EEC switches the AC from the source EAS to the target EAS after receiving the ACR completion message. It should be noted that the ACR completion message is sent when the ACT (Activity Execution Control) is completed and the terminal device has moved to the target location.

[0195] As an example, and not a limitation, of Service Continuity Planning (ACR), the detection entity detects a potential change in the location of an end device, initiates an ACR process, determines the target EAS, transmits context information to the target EAS in advance, and confirms the target location of the end device. When the end device reaches the target location and the Action Process (ACT) is completed, the Equipment Controller (EEC) receives the ACR completion message and switches the Access Control Center (AC) from the source EAS to the target EAS. This process can also be initiated when an EAS is predicted to be overloaded. It should be understood that Service Continuity Planning (ACR) can be an ACR that predicts a potential change in the service EAS and transmits context information to the target EAS in advance; this application does not impose any particular limitation on this.

[0196] It should be noted that among the ACR events listed above, some ACR events correspond to ordinary ACR event types, such as EAS overload; while others correspond to service continuity planning ACR event types, such as terminal device movement or prediction that terminal device movement is imminent.

[0197] Based on the above description, it should be understood that Service Continuity Planning (ACR) is a predictive behavior. When relevant entities provide information about planned, anticipated, or expected behaviors, ACR planning in advance can provide seamless continuity of services to application clients when the predicted behaviors actually occur, avoiding service interruptions.

[0198] It should be understood that EES determines the event type of the ACR. When the event type of the ACR is a Service Continuity Planning ACR, EES can store the event type of the ACR and / or the AC ID and / or the target location corresponding to the ACR for subsequent processes.

[0199] It should be noted that when the event type of the ACR is a normal ACR, EES can also store the event type of the ACR and / or the AC ID corresponding to the ACR.

[0200] Specifically, EES can store the ACR event type corresponding to the ACR event and / or the AC ID corresponding to the ACR event and / or the target location corresponding to the ACR event. Alternatively, EES can store the ACR event type corresponding to the AC ID and / or the AC ID and / or the target location corresponding to the AC ID. In other words, EES can store data based on ACR events or based on AC IDs.

[0201] In this application embodiment, the case where the event type of ACR is Service Continuity Planning ACR is mainly described, but this application embodiment does not limit this, and the method provided in this application embodiment may also be used for other ACR event types.

[0202] S330, EES determines whether the terminal device has moved to the target location.

[0203] Specifically, EES determines whether the terminal device has moved to the target location based on the AC ID corresponding to the ACR and the target location corresponding to the ACR, that is, it judges the mobility of the terminal device.

[0204] It should be understood that the EES can determine the mobility of the terminal device either after the ACT is completed or before the ACT is completed.

[0205] Specifically, the EES determines ACT completion by receiving the ACR status update request (ACR statusupdate response) message.

[0206] Specifically, the EES can receive an ACR status update request upon determining that the ACT is complete. Optionally, the status update request may include indication information indicating ACT completion, and the EES determines ACT completion based on this indication information. Optionally, the status update request message may also include an ACT result and reason message, which may include ACT success or ACT failure and the reason for failure. If the message content indicates ACT success, the EES considers the ACT complete.

[0207] It should be noted that ACT completion indicates that the application context of the AC corresponding to the ACR has been transferred from the source EAS to the target EAS.

[0208] It should be noted that the carrier message of the ACR completion message is not limited in this embodiment of the application.

[0209] Furthermore, the EES determines whether the terminal has moved to the target location based on at least one of the following: the ACID corresponding to the ACR, the target location corresponding to the ACR, and the current location of the terminal device. Below are some specific examples of how the EES may determine whether the terminal device has moved to the target location.

[0210] For example, when EES determines the event type of an ACR, it only stores the AC ID corresponding to the ACR whose event type is Service Continuity Planning (i.e., it does not store the IDs of ordinary ACRs). When EES determines whether the terminal device has moved to the target location, EES compares the target location corresponding to the AC ID with the current location of the terminal device to determine whether the terminal device has moved to the target location.

[0211] It should be noted that the target location of the terminal device can be obtained by EES or obtained by EES from other entities.

[0212] For example, when EES determines the event type of an ACR, it stores the event type of the ACR and the corresponding ACID. When EES determines whether a terminal device has moved to a target location, it finds the event type of the ACR based on the ACID. If the event type of the ACR is determined to be a Service Continuity Planning ACR, EES compares the target location corresponding to the ACR with the current location of the terminal device to determine whether the terminal device has moved to the target location.

[0213] It should be noted that the target location corresponding to this ACR can be obtained by EES or obtained by EES from other entities.

[0214] For example, when determining the event type of an ACR, if the event type of the ACR is a Service Continuity Planning ACR, the EES sends the AC ID and the target location corresponding to the ACR to the 3GPP core network and subscribes to a notification message from the 3GPP core network. This notification message is sent to the EES when the 3GPP core network determines that the terminal device has moved to the target location corresponding to the ACR. The EES determines whether the terminal device has moved to the target location based on whether it has received this notification message. For a detailed description of this notification message and the subscription mechanism, please refer to the description below.

[0215] It should be noted that the specific process by which EES determines whether the terminal device has moved to the target location based on the AC ID corresponding to the ACR, the target location corresponding to the ACR, and the current location of the terminal device can be a combination of the above examples or a recombination of individual steps in the above examples. This application does not limit this.

[0216] It should be noted that the terminal device can obtain its current location from the 3GPP core network, and the terminal device can also obtain its mobility information directly from the 3GPP core network. That is, when the 3GPP core network determines that the terminal device has moved to the target location, it will notify the terminal device.

[0217] For example, EES can obtain the current location of the terminal device from the 3GPP core network. One possible implementation is that EES subscribes to UPPM events from the 3GPP core network. These UPPM events are triggered when the data network access identifier (DNAccess Identifier, DNAI) of the terminal device changes, at which point the core network sends the corresponding DNAI of the terminal device to the EES.

[0218] It should be understood that, corresponding to the above example, the EES determines whether the terminal device has moved to the target location by checking whether the DNAI of the terminal device at that moment matches the DNAI of the target EAS. When the DNAI of the terminal device at that moment matches the DNAI of the target EAS, the EES determines that the terminal device has moved to the target location.

[0219] It should be noted that the 3GPP core network can notify the terminal device of the corresponding DNAI through an EESDNAI change notification (EESDNAI change). Optionally, this change notification includes the DNAI information corresponding to the terminal device at this time.

[0220] For example, the EES can directly subscribe to the mobility of terminal devices from the 3GPP core network. One possible implementation is that the EES subscribes to UPPM events from the 3GPP core network. These UPPM events are notification messages sent by the 3GPP core network to the EES when the terminal device moves to a target location (which could be the same as the DNAI of the target EAS). Optionally, when subscribing to UPPM events, the EES carries the target location of the terminal device (which could be the DNAI information of the target EAS or the expected location of the terminal device, such as geographic coordinates) in the subscription message so that the core network can determine whether the terminal device has moved to its target location.

[0221] It should be understood that, corresponding to the above example, when the EES receives a notification message from the core network, the EES determines that the terminal device has moved to the target location of the terminal device.

[0222] S340, EES sends an ACR completion message to EEC.

[0223] When the terminal device moves to the target location, the EES sends an ACR completion message to the terminal device. This ACR completion message can be sent via ACR information notification; optionally, it can be an ACR complete notify. Optionally, the ACR completion message may include the ACR event type described in the above steps and / or the AC ID corresponding to the ACR, indicating that the terminal device has moved to the target location corresponding to that AC ID. Optionally, this ACR completion message is sent after the ACT (Activity Control Execution) is completed.

[0224] It should be understood that the order in which the EES determines the terminal device to move to the target location and the order in which the EES determines the ACT to be completed is not limited in the embodiments of this application.

[0225] S350, upon receiving the ACR completion message, the EEC disconnects the AC from the source EAS and connects to the target EAS.

[0226] Optionally, the EEC receives the ACR completion message and forwards it to the AC. The AC then disconnects from the source EAS and connects to the target EAS based on the ACR completion message.

[0227] Optionally, after receiving the ACR completion message, the EEC generates a notification message based on the ACR completion message and sends the notification message to the AC. The notification message instructs the AC to disconnect from the source EAS and / or connect to the target EAS. Upon receiving the notification message, the AC disconnects from the source EAS and / or connects to the target EAS based on the notification message.

[0228] It should be noted that the forwarded ACR completion message or notification message can be sent by the EEC via, for example... Figure 1 The EDGE-5 interface in the described system architecture can send data to the AC, but it can also send data to the AC through other interfaces. In this embodiment, no special restrictions are placed on the sending method.

[0229] It should be noted that when the EEC receives an ACR completion message, it can determine that the ACT is complete and the terminal device has moved to the target location, and then proceed with subsequent communication procedures. Alternatively, the EEC can receive an ACR completion message, which indicates that it has received an instruction to proceed with subsequent communication procedures.

[0230] It should be noted that in the embodiments of this application, the AC ID can also be the UE ID of the terminal device, etc., and this application does not limit it.

[0231] The method provided in this application determines the mobility of the terminal device through the EES and switches the AC on the terminal device from the source EAS to the target EAS after the terminal device moves to the target location. This avoids service interruption caused by switching the AC from the source EAS to the target EAS too early (e.g., the ACT is completed, but the terminal device has not yet moved to the target location, resulting in service interruption), thus ensuring service continuity.

[0232] Figure 4 This is a schematic diagram illustrating another example of the application context relocation method according to embodiments of this application. Figure 4 In the method shown, the type of ACR is determined by EAS, and the mobility of the terminal device is determined by EES, such as... Figure 4 As shown, the method 400 includes:

[0233] S410, the EEC sends a first instruction message or a second instruction message to the EES. The first instruction message instructs the EES to determine the mobility of the terminal device, and the second instruction message instructs the EEC not to determine the mobility of the terminal device.

[0234] The specific meanings of the first and second instruction information are similar to those of step S310 in method 300, and can be found in the relevant description in S310.

[0235] S420, EAS determines the event type of the ACR.

[0236] The EAS determines the event type of ACR in a similar way to the EES in step S320 of method 300. For details, please refer to the relevant description in S320. You only need to replace EES in step S320 with EAS.

[0237] Optionally, the EAS can determine the event type of the ACR by sending an indication message.

[0238] Specifically, EES sends an instruction message to EAS, instructing EAS to determine the event type of ACR.

[0239] Optionally, this indication information can be obtained through, for example... Figure 1 The system architecture described uses the EDGE-3 interface for transmission.

[0240] Specifically, the relevant message may be an ACR monitoring event in the ACR management event notification message, or an UPPM event notification, or an ACR facilitation event notification, or a separate newly added signaling message. This application embodiment does not limit this.

[0241] EAS can determine the event type of ACR without sending indication information through EES.

[0242] Optionally, EAS can determine the event type of ACR using the EAS default.

[0243] Optionally, EAS can determine the event type of ACR by selecting an ACR scenario / solution when the relevant entity (e.g., AC, EEC, EES.EAS) chooses an ACR scenario triggered / executed by EAS.

[0244] It should be noted that after EAS determines the event type of ACR, EAS can cache the event type of ACR and / or the AC ID and / or the target location corresponding to ACR.

[0245] Specifically, the method by which EAS obtains the target location corresponding to the ACR is similar to the method by which EES obtains the target location of the terminal device in step S310 of method 300. Please refer to the relevant description in step S310, only EES needs to be replaced with EAS.

[0246] S430, EAS sends the event type of the ACR and / or the AC ID corresponding to the ACR and / or the target location corresponding to the ACR to EES.

[0247] Optionally, the event type of the ACR and / or the AC ID and / or the target location of the ACR sent by the EAS to the EES can be included in existing messages such as the ACR status update request sent by the EAS to the EES. Alternatively, the event type of the ACR and / or the AC ID and / or the target location of the ACR sent by the EAS to the EES can be included in a newly added separate signaling message. This application does not limit this.

[0248] It should be noted that the EAS can send the event type of the ACR and / or the AC ID and / or the target location of the ACR to the EES at any time, either after the ACT is completed or before the ACT is completed.

[0249] It should be understood that after receiving information such as the event type of the ACR and / or the AC ID and / or the target location of the ACR sent by the EAS, the EES can store the event type of the ACR and / or the AC ID and / or the target location of the ACR in order to determine the mobility of the terminal device.

[0250] S440, EES determines whether the terminal device has moved to the target location.

[0251] This step is similar to step S330 in method 300, and can be found in the relevant description in S330.

[0252] S450, EES sends an ACR completion message to EEC.

[0253] This step is similar to step S340 in method 300, and can be found in the relevant description in S340.

[0254] It should be noted that in this step, the timing of the EES sending the ACR completion message to the EEC may differ slightly from that in step S340. This difference is related to the timing of the EAS sending the event type of the ACR and / or the AC ID and / or the target location information corresponding to the ACR to the EES in step S430.

[0255] Specifically, if the EAS sends the above information to the EES after confirming the completion of the ACT, the EES can be unaware of whether the ACT is completed. By default, once it receives the above information and confirms that the terminal device has moved to the target location, it will send an ACR completion message to the EEC. If the EAS can send the above information to the EES whether the ACT is completed or not, then the EES will send an ACR completion message to the EEC after confirming that the terminal device has moved to the target location and that the ACT is completed.

[0256] S460, upon receiving the ACR completion message, the EEC disconnects the AC from the source EAS and connects to the target EAS.

[0257] This step is similar to step S350 in method 300, and can be found in the relevant description in S350.

[0258] The method provided in this application embodiment determines the type of ACR by the EAS and sends certain relevant information needed to determine the mobility of the terminal device to the EES. The EES then determines the mobility of the terminal device, ensuring that the AC on the terminal device is switched from the source EAS to the target EAS only after the terminal device moves to the target location. This avoids service interruption caused by prematurely switching the AC from the source EAS to the target EAS and ensures service continuity.

[0259] Figure 5 This is a schematic diagram illustrating another example of the application context relocation method according to an embodiment of this application. Figure 5 The method shown is a specific embodiment corresponding to method 300, such as... Figure 5 As shown, the method 500 includes:

[0260] S510, the source EES detects the ACR event and initiates the ACR process.

[0261] It should be noted that prior to this step, the terminal device's AC is connected to the source EAS, and the application corresponding to the AC is running.

[0262] Specifically, the source EES detects an ACR event and initiates the ACR process. It should be noted that the ACR event can be, for example, EAS overload, the terminal device being moved, the terminal device about to be moved, or the source EES being unable to provide service.

[0263] For example, an event that the source EES detects an ACR could be that the source EES has detected a change in the location of the terminal device.

[0264] For example, an event where the source EES detects an ACR could be that the source EES has detected that the terminal device has moved out of the service range of the current EAS or the source EAS.

[0265] For example, an event that triggers an ACR can be that the source EES receives a UPPM notification from the 3GPP core network, or that the source EES receives a notification from the EAS or EEC that informs the source EES that an ACR event has occurred.

[0266] For example, the source EES may need to notify the source EES of the location of the terminal device based on the predicted location of the terminal device.

[0267] S520, the source EES determines the event type of the ACR.

[0268] It should be noted that this step is similar to step S320 in method 300. Please refer to the relevant description in step S320. The only difference is that EES in step S320 is replaced with the source EES.

[0269] Optionally, the source EES can also receive a first indication message or a second indication message sent by the EEC. The first indication message instructs the source EES to determine the mobility of the terminal device, and the second indication message instructs the EEC of the terminal device not to determine the mobility of the terminal device. The specific meanings of the first and second indication messages are similar to those in step S310 of method 300, and can be found in the relevant description in step S310.

[0270] S530, the discovery process of the source EES executing the target EAS.

[0271] Specifically, the source EES sends a Retrieve EES request to the ECS. This request includes one or more of the following: the location information or identifier of the terminal device, the EAS ID of the source EAS, the target DNAI, and the AC profile, in order to identify candidate target EES with an EAS that can be used to serve a given AC in the terminal device.

[0272] The ECS determines candidate target EES based on parameters in the request (such as EAS ID, target DNAI, etc.) and the expected location information of the terminal device. It should be understood that if the expected location of the terminal device is not included in the request, the ECS does not know the expected location of the terminal device. The ECS can interact with the 3GPP core network to retrieve the expected location of the terminal device. The specific method is similar to obtaining the expected location of the terminal device from the EES, as described in step S310; simply replace the EES with the ECS.

[0273] Furthermore, the ECS sends a "Retrieve EES" response to the source EES. This response message may include the EAS ID of the source EAS, a list of candidate target EES information, etc. The candidate target EES information list may include one or more target EES, and this list includes the endpoints of each candidate target EES, such as the IP addresses of the candidate target EES.

[0274] Furthermore, the source EES executes the target EAS discovery process.

[0275] Specifically, the source EES sends a target EAS discovery request to the candidate target EES retrieved by the ECS. This discovery request may include the source EES's identifier (EES ID) and security credentials, and may also include a target EAS discovery filter, which may include parameters or other requirements of the target EES desired by the source EES. It should be noted that the source EES may send this discovery request to one or more EES in the candidate target EES list.

[0276] Furthermore, the candidate target EES receives the discovery request and, based on the request, discovers the target EAS, then feeds back the relevant information of the target EAS to the source EES. Specifically, the candidate target EES can filter other EASs using the discovery filter to ultimately select the target EAS.

[0277] It should be noted that the expected location of the terminal device can help the source EES discover the target EAS. Once the source EES determines the target EAS, it can determine the service range of the target EAS. In some embodiments, the expected location of the terminal device and the service range of the target EAS can be equivalent. The expected location of the terminal device can also be a location point within the service range of the target EAS. This application does not impose any special limitations on this.

[0278] S540, the source EAS sends the context information of the AC corresponding to the ACR to the target EAS.

[0279] Specifically, the source EAS sends the context information corresponding to the AC of the ACR to the target EAS. This can be done by the source EAS sending the context information corresponding to the AC to the target EAS, or by the source EES assisting the source EAS in sending the context information corresponding to the AC to the target EES via the EDGE-9 interface, and then the target EAS obtains the application context information from the target EES.

[0280] S550, the source EAS sends an ACR status update request to the source EES.

[0281] It should be noted that this status update request is sent after the application context information has been transmitted from the source EAS to the target EAS, i.e., after the ACT is completed. It should also be noted that this ACR status update request can indicate ACT completion and proceed with subsequent communication procedures, or it can include a separate information cell indicating ACT completion and proceeding with subsequent communication procedures. For details, please refer to the relevant descriptions of the ACT completion message and status update request message in step S330 of method 300, which will not be repeated here.

[0282] S560, the source EES sends an ACR status update response to the source EAS.

[0283] S570, the source EES determines whether the terminal device has moved to the target location.

[0284] This step is similar to step S330 in method 300, as can be found in the relevant description in step S330, except that EES is replaced with the source EES.

[0285] It should be noted that the step of determining whether the terminal device has moved to the target location can also be performed by the target EES. Before determining whether the terminal device has moved to the target location, the target EES receives information such as the event type of the ACR and / or the AC ID and / or the target location corresponding to the ACR from the source EES. Optionally, the target EES can store the event type of the ACR and / or the AC ID and / or the target location corresponding to the ACR.

[0286] The method for determining whether the terminal device has moved to the target location using the target EES is similar to step S330 in method 300. Please refer to the relevant description in step S330. Simply replace the EES with the target EES.

[0287] S580, the source EES sends an ACR completion notification to the EEC.

[0288] This step is similar to step S340 in method 300. For details, please refer to the relevant description in S340. Simply replace EES with the source EES.

[0289] It should be understood that when the target EES performs the mobility determination of the terminal device, this step involves the target EES sending an ACR completion notification to the EEC. This step is similar to step S340 in method 300. For details, please refer to the relevant description in S340. You only need to replace the EES with the target EES.

[0290] S590, the EEC receives the ACR completion message and switches the AC from the source EAS to the target EAS.

[0291] This step is similar to step S350 in method 300, and you can refer to the relevant description in S350 for details.

[0292] Figure 6 This is a schematic diagram illustrating another example of the application context relocation method according to an embodiment of this application. Figure 6 The method shown is a specific embodiment of method 400, such as Figure 6 As shown, the method 600 includes:

[0293] S610, the source EES detects the ACR event and initiates the ACR process.

[0294] This step is similar to step S510 in method 500, and you can refer to the relevant description of step S510.

[0295] S620, the source EAS determines the event type of the ACR.

[0296] It should be noted that this step is similar to step S420 of method 400. Please refer to the relevant description in method S420. You only need to replace EAS with the source EAS.

[0297] S630, the source EAS sends the event type of the ACR and / or the AC ID corresponding to the ACR and / or the target location corresponding to the ACR to the source EES.

[0298] It should be noted that this step is similar to step S430 in method 400. Please refer to the relevant description in method S430. Simply replace EAS with the source EAS and EES with the source EES.

[0299] S640, the discovery process of the source EES executing the target EAS.

[0300] The discovery process is similar to step S530 in method 500, and the relevant description in S530 can be found for details.

[0301] S650, the source EAS sends the context information of the AC corresponding to the ACR to the target EAS.

[0302] This step is similar to step S540 in method 500, and you can refer to the relevant description in step S540 for details.

[0303] S660, the source EAS sends an ACR status update request to the source EES.

[0304] This step is similar to step S550 in method 500, and you can refer to the relevant description in step S550 for details.

[0305] S670, the source EES sends an ACR status update response to the source EAS.

[0306] S680, the source EES determines whether the terminal device has moved to the target location.

[0307] This step is similar to step S560 in method 500, and you can refer to the relevant description in step S560 for details.

[0308] S690, the source EES sends an ACR completion notification to the EEC.

[0309] This step is similar to step S570 in method 500, and you can refer to the relevant description in step S570 for details.

[0310] S6100: Upon receiving the ACR completion message, the EEC switches the AC from the source EAS to the target EAS.

[0311] This step is similar to step S580 in method 500, and you can refer to the relevant description in step S580 for details.

[0312] Figure 7 This is a schematic diagram illustrating another example of the application context relocation method according to embodiments of this application. Figure 7 In the method shown, the EEC determines the type of ACR event and the mobility of the terminal device. For example... Figure 7 As shown, the method 700 includes:

[0313] S710, EES determines the mobility of the terminal equipment determined by EEC.

[0314] Optionally, EES defaults to EEC determining the mobility of terminal devices.

[0315] Optionally, when determining the ACR method, the EEC is used to determine the mobility of the terminal device.

[0316] For a detailed description of determining the mobility of the terminal device, please refer to the relevant description of step S310 in method 300, which will not be repeated here.

[0317] It should be noted that this step is optional.

[0318] S720, EEC determines the event type of the ACR.

[0319] It should be noted that this step is similar to the description of step S320 in method 300. Please refer to the relevant description in step S320, only replace EES with EEC.

[0320] It should be noted that when the EEC obtains the target location of the terminal device, in addition to obtaining the target location of the terminal device from the method described in step S320, it can also obtain the target location of the terminal device from itself, that is, from the terminal devices to which the EEC belongs.

[0321] S730, EEC receives ACR completion message sent by EES.

[0322] The ACR completion message can be sent via ACR information notification. Optionally, the ACR completion message can specifically be an ACR complete notify. This ACR completion message indicates that the ACT is complete, meaning that the context information of the AC corresponding to the ACR has been transferred from the source EAS to the target EAS. Optionally, the ACT completion message can be a specific information cell, which can be included in the ACR status update request or a separate newly added information cell. The ACT completion message can also be a default message, meaning that the EES receives an ACT completion message by default upon receiving, for example, an ACR status update request. The information cell of the ACT completion message or the default ACT completion message can be sent from the EAS to the EES, and then forwarded by the EES to the EEC; or it can be sent from the EAS to the EES, and then the EES generates a separate signaling message to forward to the EEC; or the EES can send an ACR completion notification to the EEC, which signifies that the ACT is complete.

[0323] It should be noted that the order of step S730 and the following step S740 is not limited; S730 can precede S740, or S740 can precede S730.

[0324] S740, EEC determines whether the terminal equipment has moved to the target location.

[0325] Specifically, the method by which EEC determines whether the terminal device has moved to the target location is roughly the same as the method in step S330 of method 300, where EES determines whether the terminal device has moved to the target location; only EES needs to be replaced with EEC.

[0326] It should be noted that, in addition to obtaining the location information of terminal devices from the 3GPP core network information like the EES, the EEC itself, i.e., the terminal devices to which the EEC belongs, can also obtain the location information of terminal devices.

[0327] It should be noted that the order of steps S740 and S730 is not limited.

[0328] S750 switches the AC from the source EAS to the target EAS when the terminal device moves to the target location.

[0329] In some embodiments, the EEC determines that the terminal device has moved to the target location. Optionally, the EEC determines that the ACT is completed. For example, the EEC receives an ACR completion message to determine that the ACT is completed, and the EEC switches the AC from the source EAS to the target EAS.

[0330] It should be noted that the mechanism by which the EEC notifies the AC to switch is the same as that described in step S340 of method 300, and the relevant description in step S340 can be found.

[0331] The method provided in this application determines the mobility of the terminal device through the EEC, ensuring that the AC corresponding to the ACR is switched from the source EAS to the target EAS only after the terminal device moves to the target location. This avoids service interruption caused by prematurely switching the AC from the source EAS to the target EAS, thus ensuring service continuity. Furthermore, since the EEC belongs to the terminal device, the method of obtaining the location of the terminal device by the EEC for mobility determination is simpler and can save signaling overhead for obtaining location information to a certain extent.

[0332] like Figure 8 This is a schematic diagram illustrating another example of the application context relocation method according to embodiments of this application. Figure 8 In the method shown, the EES determines the event type of the ACR, and the EEC determines the mobility of the terminal device. For example... Figure 8 As shown, the method 800 includes:

[0333] S810, EES determines the mobility of the terminal equipment determined by EEC.

[0334] S820, EES determines the event type of the ACR.

[0335] It should be noted that this step is similar to step S420 in method 400. For details, please refer to the description of step S420. You only need to replace EAS with EES.

[0336] S830, EES sends the event type of the ACR and / or the AC ID corresponding to the ACR and / or the target location corresponding to the ACR to EEC.

[0337] It should be noted that this step is similar to step S430 in method 400. For details, please refer to the relevant description of step S430. Simply replace EAS with EES and EES with EEC.

[0338] In some embodiments, step S810 or the configuration phase may not instruct the EEC to determine the mobility of the terminal device. By default, in this step, when the EES sends certain information to the EEC, the EEC determines the mobility of the terminal device. As an example and not a limitation, when the EES determines the event type of the ACR, if it is determined to be an ACR related to service continuity planning, the EES sends the event type of the ACR and / or the AC ID and / or the target location corresponding to the ACR to the EEC. In this case, the EEC is required by default to determine the mobility of the terminal device corresponding to the ACR. In other words, when the AC corresponding to the ACR is switched, the mobility of the terminal device needs to be determined first.

[0339] S840, EEC receives the ACR completion message sent by EES.

[0340] It should be noted that this step is similar to step S730 in method 700, and the relevant description of S730 can be found in the description.

[0341] S850, EEC determines whether the terminal device has moved to the target location.

[0342] Specifically, the method by which the EEC determines whether the terminal device has moved to the target location is largely the same as the method used by the EES in step S330 of method 300 to determine whether the terminal device has moved to the target location; only the EES is replaced with the EEC. It should be noted that, unlike step S330, the EEC does not receive ACR status update requests or ACT completion notifications.

[0343] It should be noted that, in addition to obtaining the location information of terminal devices from the 3GPP core network information like the EES, the EEC itself, i.e., the terminal devices to which the EEC belongs, can also obtain the location information of terminal devices.

[0344] It should be noted that the order of steps S850 and S860 is not limited.

[0345] S860, when the EEC determines that the terminal device has moved to the target location, switches the AC to the target EAS.

[0346] In some embodiments, the EEC determines that the terminal device has moved to the target location. Optionally, the EEC determines that the ACT is completed. For example, the EEC receives an ACR completion message to determine that the ACT is completed, and the EEC switches the AC from the source EAS to the target EAS.

[0347] It should be noted that the mechanism by which the EEC notifies the AC to switch is the same as that described in step S340 of method 300, and the relevant description in step S340 can be found.

[0348] like Figure 9 This is a schematic diagram illustrating yet another example of the application context relocation method according to an embodiment of this application. Figure 9 The method shown is a specific embodiment of method 700. For example... Figure 9 As shown, the method 900 includes:

[0349] S910, EEC detects the ACR event and initiates the ACR process.

[0350] It should be noted that this step is similar to step S510 in method 500. Please refer to the description of step S510. Simply replace the source EES with EEC.

[0351] S920, EEC determines the event type of the ACR.

[0352] It should be noted that this step is similar to step S320 in method 300. Please refer to the relevant description in step S320. You only need to replace EES with EEC.

[0353] S930, the EEC performs the discovery process for the target EAS.

[0354] Specifically, the EEC sends an EAS discovery request to the EES. This EAS discovery request may include the EEC ID, security credentials, and an EAS discovery filter, which is used to retrieve information about a specific EAS or a specific type of EAS (such as game applications).

[0355] Furthermore, after receiving the EAS discovery request from the EEC, the EES checks whether the EEC is authorized to discover the requested EAS. If the EEC is authorized, the EES identifies the EAS based on the EAS discovery filter provided by the EEC and the location of the terminal device (which can be obtained from the 3GPP core network).

[0356] It should be noted that if the EEC does not provide an EAS discovery filter, the EES can identify the EAS based on the specific service information of the terminal device on the EES and the location of the terminal device. The EES can also identify the EAS by applying ECSP policies. If the EES cannot determine the EAS information through the information in the EAS discovery request, the specific service information of the terminal device on the EES, or the ECSP policies, the EES can refuse to provide services to the EEC and provide the corresponding reason.

[0357] Furthermore, if EES determines that it can provide services to EEC, EES sends an EAS discovery response to EEC, which includes the discovered EAS information and its endpoint information.

[0358] Correspondingly, after receiving the response from the EEC, the EEC routes the application data traffic to the EAS according to the endpoint information required.

[0359] It should be noted that the EAS in this step is the target EAS.

[0360] It should be noted that the EES can be either the source EES or the target EES.

[0361] S940, the source EAS sends the context information of the AC corresponding to the ACR to the target EAS.

[0362] Specifically, this step is similar to step S540 in method 500, and you can refer to the relevant description of step S540 for details.

[0363] S950, the target EAS sends an ACR status update request to the target EES.

[0364] It should be noted that this step is similar to step S550 in method 500, and the relevant description in S550 can be found therein. The only difference is that the source EAS is replaced with the target EAS, and the source EES is replaced with the target EES. It should also be noted that in this step, the target EAS can also send an ACR status update request to either the source EES or the source EAS.

[0365] S960, the target EES sends an ACR status update response to the target EAS.

[0366] S970, the target EES sends an ACR completion notification to the EEC.

[0367] This step is similar to step S730 in method 700, and you can refer to the description of S730 for details. The only difference is that the EES is replaced with the target EES.

[0368] S980, EEC determines whether the terminal equipment has moved to the target location.

[0369] Specifically, the method by which EEC determines whether the terminal device has moved to the target location is roughly the same as the method by which EES determines whether the terminal device has moved to the target location in step S330 of method 300; only EES needs to be replaced with EEC.

[0370] It should be noted that, in addition to obtaining the location information of terminal devices from the 3GPP core network information like the EES, the EEC itself, i.e., the terminal devices to which the EEC belongs, can also obtain the location information of terminal devices.

[0371] It should be noted that the order of steps S970 and S980 is not limited.

[0372] S990 switches the AC from the source EAS to the target EAS when the terminal device moves to the target location.

[0373] In some embodiments, the EEC determines that the terminal device has moved to the target location. Optionally, the EEC determines that the ACT is completed. For example, the EEC receives an ACR completion message to determine that the ACT is completed, and the EEC switches the AC from the source EAS to the target EAS.

[0374] It should be noted that the mechanism by which the EEC notifies the AC to switch is the same as that described in step S340 of method 300, and the relevant description in step S340 can be found.

[0375] like Figure 10 This is a schematic diagram illustrating another example of the application context relocation method according to an embodiment of this application. Figure 10 The method shown is a specific embodiment of method 800. For example... Figure 10 As shown, the method 1000 includes:

[0376] S1010, EEC detected the ACR event and initiated the ACR process.

[0377] It should be noted that this step is similar to step S510 in method 500. Please refer to the description of step S510. Simply replace the source EES with EEC.

[0378] S1020, EES determines the event type of the ACR.

[0379] It should be noted that this step is similar to step S420 in method 400. For details, please refer to the description of step S420. You only need to replace EAS with EES.

[0380] S1030, EES sends the event type of the ACR and / or the AC ID corresponding to the ACR and / or the target location corresponding to the ACR to EEC.

[0381] It should be noted that this step is similar to step S430 in method 400. For details, please refer to the relevant description of step S430. Simply replace EAS with EES and EES with EEC.

[0382] In some embodiments, step S810 or the configuration phase may not instruct the EEC to determine the mobility of the terminal device. By default, in this step, when the EES sends certain information to the EEC, the EEC determines the mobility of the terminal device. As an example and not a limitation, when the EES determines the event type of the ACR, if it is determined to be an ACR related to service continuity planning, the EES sends the event type of the ACR and / or the AC ID and / or the target ID corresponding to the ACR to the EEC. In this case, the EEC needs to determine the mobility of the terminal device corresponding to the ACR by default. In other words, when the AC corresponding to the ACR is switched, the mobility of the terminal device needs to be determined first.

[0383] S1040, EEC executes the discovery process for target EAS.

[0384] Specifically, this process is similar to step S930 in method 900, and the relevant description in step S930 can be found for details.

[0385] S1050, the source EAS sends the context information of the AC corresponding to the ACR to the target EAS.

[0386] Specifically, this step is similar to step S540 in method 500, and you can refer to the relevant description of step S540 for details.

[0387] Specifically, the source EAS sends the context information corresponding to the AC on the terminal device to the target EAS.

[0388] S1060, the target EAS sends an ACR status update request to the target EES.

[0389] It should be noted that this step is similar to step S550 in method 500. Please refer to the relevant description in S550. The only difference is that the source EAS is replaced with the target EAS and the source EES is replaced with the target EES.

[0390] S1070, the target EES sends an ACR status update response to the target EAS.

[0391] S1080, the target EES sends an ACR completion notification to the EEC.

[0392] This step is similar to step S730 in method 700, and you can refer to the description of S730 for details. The only difference is that the EES is replaced with the target EES.

[0393] S1090, EEC determines whether the terminal device has moved to the target location.

[0394] Specifically, the method by which EEC determines whether the terminal device has moved to the target location is roughly the same as the method in step S330 of method 300, where EES determines whether the terminal device has moved to the target location; only EES needs to be replaced with EEC.

[0395] It should be noted that, in addition to obtaining the location information of terminal devices from the 3GPP core network information like the EES, the EEC itself, i.e., the terminal devices to which the EEC belongs, can also obtain the location information of terminal devices.

[0396] It should be noted that the order of steps S970 and S980 is not limited.

[0397] S1100, when the terminal device moves to the target location, switches the AC from the source EAS to the target EAS.

[0398] In some embodiments, the EEC determines that the terminal device has moved to the target location. Optionally, the EEC determines that the ACT is completed. For example, the EEC receives an ACR completion message to determine that the ACT is completed, and the EEC switches the AC from the source EAS to the target EAS.

[0399] It should be noted that the mechanism by which the EEC notifies the AC to switch is the same as that described in step S340 of method 300, and the relevant description in step S340 can be found.

[0400] like Figure 11 This is a schematic diagram illustrating another example of the application context relocation method according to embodiments of this application. Figure 11 In the method shown, the EAS subscribes to the mobility of the terminal device from the EES. When the EAS receives a notification message and determines that the terminal device has moved to the target location, it continues the subsequent communication process. Figure 11 As shown, the method 1100 includes:

[0401] S1110, EAS sends the AC ID and target location corresponding to the ACR to EES.

[0402] It should be noted that the EES determines whether the terminal device has reached the target location based on the AC ID corresponding to the ACR sent by the EAS, the target location corresponding to the ACR, and the current location of the terminal device. This determination process and specific examples are similar to step S330 in method 300. Refer to the description in step S330 regarding receiving the terminal device's location information from the 3GPP core network for judgment or directly obtaining a notification message from the 3GPP core network to determine if the terminal device has moved to the target location.

[0403] It should be noted that the method for EAS to obtain the target location of the terminal device is similar to step S310 in method 300, except that EES is replaced with EAS. For details, please refer to the relevant description of step S310.

[0404] S1120, when the EES determines that the terminal device has moved to the target location, it sends a first notification message to the EAS.

[0405] Specifically, the first notification message instructs the terminal device to move to the target location.

[0406] It should be noted that, optionally, EAS can send a subscription message to EES in advance. This subscription message instructs EES to send a first notification message to EAS when it receives the AC ID and target location corresponding to the ACR and needs to determine that the terminal device has moved to the target location. Optionally, EAS can send a subscription message to EES, instructing EES to send a first notification message to EAS when it determines that the terminal device has moved to the target location. This subscription message carries the AC ID and target location corresponding to the ACR. Optionally, EES can default to sending a first notification message to EAS only after receiving the AC ID and target location corresponding to the ACR from EAS and needing to determine that the terminal device has moved to the target location.

[0407] S1130, EAS receives the first notification message and sends an ACT completion message to EES based on the first notification message.

[0408] It should be noted that after the EAS receives the first notification message and determines that the context information of the AC corresponding to the ACR has been sent from the source EAS to the target EAS, the EAS sends an ACT completion message to the EES. This ACT completion message can be included in the ACR status update notification as a separate information cell, or it can be the EES receiving the ACR status update notification, i.e., confirming that the ACT is complete.

[0409] Optionally, the EAS can set a timer. If the EAS does not receive the first notification message after the timer expires, the EAS can send an ACT result and reason message to the EES. This message can also be included in the ACR status update request. This message can indicate that the ACT failed because the timer expired but the terminal device did not move to the target location. It should be noted that this ACT failure does not necessarily mean that the application context transmission failed; it can also implicitly indicate that the terminal device did not move to the target location.

[0410] It should be noted that after receiving the first notification message, EAS can perform subsequent steps according to the existing process, such as sending an ACR completion notification to the EEC.

[0411] In the method provided in this application embodiment, compared with other methods in this specification, the EES itself does not perceive the event type of the ACR. The EES only determines whether the terminal device has moved to the target location based on the subscription message of the EAS or the AC ID and target location corresponding to the ACR provided by the EAS. The EAS will only proceed with the subsequent communication process after receiving the first notification message. This method makes minimal changes to the existing protocol, avoids the signaling overhead caused by the EES continuously sending the location information of the terminal device to the EAS in the existing process, saves signaling overhead, and reduces changes to the existing protocol.

[0412] Figure 12 This is an example of the application context relocation device provided in this application. For example... Figure 12 As shown, the device 1200 includes a transceiver unit 1210 and a processing unit 1220.

[0413] In some embodiments, the application context relocation device 1200 can be used to implement the functionality of the EES (including the source EES and the target EES) involved in any of the above method embodiments. For example, the application context relocation device 1200 can correspond to an EES.

[0414] The application context relocation device can be an EES, and it executes the steps performed by the EES in the above method embodiments. The transceiver unit 1210 can be used to support the context relocation device 1200 in communication, for example, to perform the sending and / or receiving actions performed by the EES in the above method embodiments. The processing unit 1220 can be used to support the application context transmission device 1200 in performing the processing actions in the above method embodiments, for example, to perform the processing actions performed by the EES in the above method embodiments.

[0415] Optionally, the application context relocation device may further include a storage unit 1230. Figure 12 (Not shown in the image), used to store the device's program code and data.

[0416] For details, please refer to the following description:

[0417] The processing unit 1220 is used to determine that the terminal device has moved to the target location.

[0418] The transceiver unit 1210 is used to send an ACR completion message to the terminal device when the processing unit 1220 determines that the terminal device has moved to the target location.

[0419] The transceiver unit 1210 is also configured to receive first indication information from the terminal device, the first indication information indicating that the edge-enabled server determines the mobility of the terminal device, or to receive second indication information from the terminal device, the second indication information indicating that the edge-enabled client of the terminal device does not support determining the mobility of the terminal device.

[0420] The processing unit 1220 is also used to detect ACR events, where the event type of the ACR is a Service Continuity Planning ACR.

[0421] The processing unit 1220 is also used to determine the target location of the terminal device based on the application client ID corresponding to the ACR and / or the target location corresponding to the ACR.

[0422] The transceiver unit 1210 is also used to receive at least one of the following from the edge application server: the event type of the ACR, the application client ID corresponding to the ACR, and the target location corresponding to the ACR;

[0423] The processing unit 1220 is also used to determine the target location of the terminal device based on the application client ID corresponding to the ACR and / or the target location corresponding to the ACR.

[0424] The transceiver unit 1210 is also used to obtain the current location of the terminal device.

[0425] The processing unit 1220 is also used to determine the target location of the terminal device based on the current location of the terminal device, the application client ID corresponding to the ACR, and the target location corresponding to the ACR.

[0426] In some embodiments, the application context relocation device 1200 can be used to implement the EEC functionality involved in any of the above method embodiments. For example, the application context relocation device 1200 can correspond to the EEC.

[0427] The application context relocation device can be an EEC (Enterprise Controller), and it executes the steps performed by the EEC in the above method embodiments. The transceiver unit 1210 can be used to support the context relocation device 1200 in communication, for example, to perform the sending and / or receiving actions performed by the EEC in the above method embodiments. The processing unit 1220 can be used to support the application context transmission device 1200 in performing the processing actions in the above method embodiments, for example, to perform the processing actions performed by the EEC in the above method embodiments.

[0428] Optionally, the application context relocation device may further include a storage unit 1230. Figure 12 (Not shown in the image), used to store the device's program code and data.

[0429] For details, please refer to the following description:

[0430] The transceiver unit 1210 is used to receive the Application Context Relocation (ACR) completion message.

[0431] The processing unit 1220 is used to switch the application client from the source edge application server to the target edge application server when it is determined that the terminal device has moved to the target location.

[0432] The processing unit 1220 is also used to detect ACR events, where the event type of the ACR is a Service Continuity Planning ACR.

[0433] The processing unit 1220 is also used to determine the target location of the terminal device based on the application client ID corresponding to the ACR and / or the target location corresponding to the ACR.

[0434] The transceiver unit 1210 is also configured to receive at least one of the following: the event type of the ACR and / or the application client ID corresponding to the ACR and / or the target location corresponding to the ACR;

[0435] The processing unit 1220 is also used to determine the target location of the terminal device based on the application client ID corresponding to the ACR and / or the target location corresponding to the ACR.

[0436] In some embodiments, the application context relocation device 1200 can be used to implement the functionality of the EAS (including the source EAS and the target EAS) involved in any of the above method embodiments. For example, the application context relocation device 1200 can correspond to the EEC.

[0437] The application context relocation device can be an EAS, and it executes the steps performed by the EAS in the above method embodiments. The transceiver unit 1210 can be used to support the context relocation device 1200 in communication, for example, to perform the sending and / or receiving actions performed by the EAS in the above method embodiments. The processing unit 1220 can be used to support the application context transmission device 1200 in performing the processing actions in the above method embodiments, for example, to perform the processing actions performed by the EAS in the above method embodiments.

[0438] Optionally, the application context relocation device may further include a storage unit 1230. Figure 12 (Not shown in the image), used to store the device's program code and data.

[0439] For details, please refer to the following description:

[0440] The transceiver unit 1210 is used to send the application client ID corresponding to the ACR and / or the target location corresponding to the ACR to the edge enabling server.

[0441] The transceiver unit 1210 is also used to receive a first notification message from the edge enable server, which instructs the terminal device to move to the target location.

[0442] The transceiver unit 1210 is also configured to send indication information to the edge enable server according to the first notification message, the indication information indicating that the application context transmission ACT is completed.

[0443] The transceiver unit 1210 is also used to send a subscription message to the edge enabling server. The subscription message instructs the edge enabling server to send a first notification message to the edge application server when the terminal device moves to the target location.

[0444] The processing unit 1220 is used to detect the event of the ACR, wherein the event type of the ACR is the ACR of service continuity planning.

[0445] Figure 13 This is an example of the signal transmission apparatus 1300 provided in the embodiments of this application. For example... Figure 13 As shown, the device 1300 includes a transceiver 1310, a processor 1320, and a memory 1330. The memory 1330 is used to store instructions. The processor 1320 is coupled to the memory 1330 and is used to execute the instructions stored in the memory to perform the methods provided in the embodiments of this application described above.

[0446] Specifically, the transceiver 1310 in the device 1300 can correspond to the transceiver unit 1210 in the device 1200, and the processor 1320 in the communication device 1300 can correspond to the processing unit 1220 in the communication device 1200.

[0447] It should be understood that the memory 1330 and processor 1320 described above can be combined into a single processing device, with the processor 1320 executing the program code stored in the memory 1330 to achieve the aforementioned functions. In specific implementations, the memory 1330 can be integrated into the processor 1320 or independent of the processor 1320.

[0448] Those skilled in the art will recognize that the units and algorithm steps of the various examples 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 implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art 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.

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

[0450] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

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

[0452] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0453] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0454] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for application context relocation, characterized in that, include: The edge-enabled server detected an event that triggered the Application Context Relocation (ACR). When the event type of the ACR is a Service Continuity Planning ACR, and it is determined that the terminal device has moved to the target location, the edge enabling server sends an ACR completion message to the terminal device. The step of determining that the terminal device has moved to the target location includes: the edge enabling server determining that the terminal device has moved to the target location based on the application client ID corresponding to the ACR, the target location corresponding to the ACR, and the current location of the terminal device.

2. The method according to claim 1, characterized in that, The target location is either within the service range of the target edge application server or the expected location of the terminal device.

3. The method according to claim 1 or 2, characterized in that, The method further includes: The edge-enabled server receives first indication information from the terminal device, which instructs the edge-enabled server to determine the mobility of the terminal device.

4. The method according to claim 1 or 2, characterized in that, The method further includes: The edge-enabled server receives a second indication from the terminal device, the second indication indicating that the edge-enabled client of the terminal device does not support determining the mobility of the terminal device.

5. The method according to claim 1 or 2, characterized in that, The method further includes: The edge enabling server receives at least one of the following from the edge application server: the event type of the ACR and the application client ID corresponding to the ACR.

6. The method according to claim 1 or 2, characterized in that, Before the edge enabling server sends an ACR completion message to the terminal device, the method further includes: The edge-enabled server determines that the application context transfer (ACT) is complete.

7. An apparatus for application context relocation, characterized in that, The apparatus is used for Application Context Relocation (ACR) in service continuity planning, and the apparatus includes: A processing unit for detecting events in the ACR; The transceiver unit is configured to send an ACR completion message to the terminal device when the event type of the ACR is a service continuity planning ACR and it is determined that the terminal device has moved to the target location. The step of determining that the terminal device has moved to the target location includes: the transceiver unit is used to determine that the terminal device has moved to the target location based on the application client ID corresponding to the ACR, the target location corresponding to the ACR, and the current location of the terminal device.

8. The apparatus according to claim 7, characterized in that, The target location is either within the service range of the target edge application server or the expected location of the terminal device.

9. The apparatus according to claim 7 or 8, characterized in that, The transceiver unit is also used for: The device receives a first instruction from a terminal device, which instructs the device to determine the mobility of the terminal device.

10. The apparatus according to claim 7 or 8, characterized in that, The transceiver unit is also used for: The terminal device receives a second indication message, which indicates that the edge-enabled client of the terminal device does not support determining the mobility of the terminal device.

11. The apparatus according to claim 7 or 8, characterized in that, The transceiver unit is also used for: Receive at least one of the following from the edge application server: the event type of the ACR, and the application client ID corresponding to the ACR.

12. The apparatus according to claim 7 or 8, characterized in that, The processing unit is also used for: The application context transfer (ACT) has been completed.

13. A computer-readable storage medium, characterized in that, The computer-readable medium stores computer instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1 to 6.

14. A chip, characterized in that, It includes a processor and a memory, the memory being used to store computer programs, and the processor being used to invoke and run computer media stored in the memory to perform the method as described in any one of claims 1 to 6.

Images