WO2024174803A1 - 应用上下文迁移方法、通信方法及相关装置、系统 - Google Patents

应用上下文迁移方法、通信方法及相关装置、系统 Download PDF

Info

Publication number
WO2024174803A1
WO2024174803A1 PCT/CN2024/074052 CN2024074052W WO2024174803A1 WO 2024174803 A1 WO2024174803 A1 WO 2024174803A1 CN 2024074052 W CN2024074052 W CN 2024074052W WO 2024174803 A1 WO2024174803 A1 WO 2024174803A1
Authority
WO
WIPO (PCT)
Prior art keywords
ees
acr
target
eas
eec
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2024/074052
Other languages
English (en)
French (fr)
Inventor
胡雅婕
杨艳梅
李永翠
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to AU2024226522A priority Critical patent/AU2024226522A1/en
Priority to EP24759480.7A priority patent/EP4660801A4/en
Publication of WO2024174803A1 publication Critical patent/WO2024174803A1/zh
Priority to US19/303,838 priority patent/US20250385955A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/563—Data redirection of data network streams
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
    • G06F9/4856—Task life-cycle, e.g. stopping, restarting, resuming execution resumption being on a different machine, e.g. task migration, virtual machine migration
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5072—Grid computing
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5083—Techniques for rebalancing the load in a distributed system
    • G06F9/5088—Techniques for rebalancing the load in a distributed system involving task migration
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/546—Message passing systems or structures, e.g. queues
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/148—Migration or transfer of sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/289—Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/50—Indexing scheme relating to G06F9/50
    • G06F2209/5015—Service provider selection

Definitions

  • the present application relates to the field of communication technology, and in particular to an application context migration method, a communication method, and related devices and systems.
  • EAS edge application server
  • EDN edge data networks
  • EAS edge application server
  • the terminal device After accessing the network, the terminal device will select the nearest EAS to obtain application services.
  • the terminal device needs to reselect a new EAS to continue the service.
  • the EAS reselected by the terminal device can be called the target EAS, and the EAS to which the terminal device is connected before switching to the target EAS can be called the source EAS.
  • the present application provides an application context migration method, a communication method, and related devices and systems, in order to migrate the application context between EASs.
  • the present application provides an application context relocation (ACR) method, which can be applied to a terminal device, and can be executed by the terminal device, or can be executed by a component configured in the terminal device (such as a chip, a chip system, a processor, etc.), or can be implemented by a logic module or software that can realize all or part of the terminal device functions, and the present application does not limit this.
  • ACR application context relocation
  • the method includes: determining a target edge enabler server (EES), the target EES being an EES supporting a first ACR scenario, the first ACR scenario being a scenario in which ACR is executed by the target EES; and requesting the target EES to execute ACR.
  • EES target edge enabler server
  • ACR is the process of migrating the application context from the source EAS to the target EAS.
  • the source EAS is the EAS that currently provides application services for the application of the terminal device, that is, the EAS to which the terminal device is currently connected
  • the source EES is the EAS associated with the source EAS.
  • the source EAS is registered on the source EES, and the source EES manages the source EAS.
  • the target EAS is the EAS that provides application services for the application of the terminal device after ACR.
  • the target EES is the EES associated with the target EAS.
  • the target EAS is registered on the target EES, and the target EES manages the target EAS.
  • the first ACR scenario is a scenario where the target EES executes ACR, and the ACR scenario includes ACR detection, ACR decision, ACR execution, and post-ACR cleanup.
  • the terminal device performs ACR detection and ACR decision
  • the target EES executes ACR
  • the target EES and target EAS perform post-ACR cleanup.
  • the execution of ACR by the target EES includes at least one of the following: the target EES performs user plane path modification, the target EES discovers the target EAS through the target EES, and the target EES triggers the target EAS to transmit the application context.
  • the determined target EES is an EES that supports the first ACR scenario, in other words, the EES is capable of performing ACR as a target EES. In this way, after requesting the target EES to perform ACR, the target EES can perform ACR.
  • the determined target EES supports executing ACR as the target EES, so that when the EAS currently connected to the terminal device can no longer provide application services, the application context migration can be successfully completed through the target EES. In this way, the smooth switching of the EAS can be guaranteed, and the stability and continuity of the application business can be guaranteed.
  • determining the target EES includes: receiving EES information from an edge configuration server (ECS), the EES information indicating at least one EES; and determining the target EES according to the EES information. Identify target EES.
  • EES edge configuration server
  • ECS is responsible for the configuration of EDN.
  • EES related information can be registered or configured on ECS.
  • ECS can provide EES information to terminal devices, indicating the EES registered or configured on the ECS.
  • the terminal device can determine the target EES based on the EES information from the ECS.
  • the method further includes: the terminal device receiving first information from the ECS, the first information indicating the ACR capability of the at least one EES.
  • the ACR capability of EES includes at least one of the following information: whether EES supports ACR, the ACR scenarios supported by EES, and the ACR application programming interface (API) supported by EES.
  • API application programming interface
  • the ECS may send EES information to the terminal device, indicating at least one EES.
  • the ECS may also send information indicating the ACR capabilities of these EES to the terminal device. Accordingly, the terminal device can obtain the ACR capabilities of the EES.
  • the terminal device can select an EES that supports the first ACR scenario based on the ACR capability of the EES and use it as the target EES.
  • the EES indicated by the EES information from the ECS is an EES that supports the first ACR scenario, that is, the ECS can filter out the EES that supports the first ACR scenario from the EES registered or configured on the ECS, and send it to the terminal device.
  • the terminal device selects a target EES from the EES indicated by the EES information, it does not need to perform further screening based on the ACR scenarios supported by the EES, which can reduce the burden on the terminal device.
  • the method also includes: the terminal device sends second information to the ECS, and the second information is used to indicate at least one of the following: selecting a target EES that supports the first ACR scenario, or the currently connected EES or the currently connected EAS cannot execute ACR, or the current application has no corresponding ACR scene, or requesting to obtain the ACR capability of the EES.
  • the terminal device may send the second information to the ECS.
  • the ECS may select an EES that supports the first ACR scenario based on the second information and indicate it to the terminal device, or send information to the terminal device indicating at least one EES and the ACR capability of the at least one EES.
  • the ECS can filter out the EES that supports the first ACR scenario based on the ACR capability of the EES, and indicate it to the terminal device, so that the terminal device can determine an EES as the target EES without having to filter based on the ACR capability of the EES, and the task volume of the terminal device can be reduced, which can reduce the burden on the terminal device.
  • the ECS can also indicate the EES and the ACR capability of the EES to the terminal device, and the terminal device filters out the EES that supports the first ACR scenario as the target EES, so that the ECS does not have to filter based on the ACR capability of the EES, and the task volume of the ECS can be reduced, which can reduce the burden on the ECS.
  • the target EES determined by the terminal device supports the first ACR scenario, so that when requesting the target EES to execute ACR, the terminal device can successfully execute ACR, thereby enabling the EAS switching to be completed smoothly, which can ensure the continuity of the application service.
  • the method also includes: when the current application has no corresponding ACR scenario, or when the currently connected EES or the currently connected EAS cannot perform ACR, determining to perform ACR based on the first ACR scenario.
  • the terminal device can determine to perform ACR based on the first ACR scenario, that is, to perform ACR through the target EES. After the terminal device determines to perform ACR based on the first ACR scenario, it can select the target EES and request it to perform ACR.
  • the terminal device may also determine to perform ACR based on the first ACR scenario.
  • the method further includes: the terminal device receives third information from the currently connected EES, the third information indicating that the current application has no corresponding ACR scene, or indicating that the currently connected EES or the currently connected EAS cannot perform ACR.
  • the terminal device can determine, through information from the EES, that the current application has no corresponding ACR scenario, or determine that the currently connected EES or the currently connected EAS cannot perform ACR.
  • the method before determining the target EES, the method also includes: receiving fourth information from the currently connected EES, the fourth information being used to indicate selection of a target EES that supports the first ACR scene, or to indicate that the first ACR scene is the ACR scene corresponding to the current application.
  • the currently connected EES may determine that ACR needs to be performed based on the first ACR scenario, and indicate to the terminal device that the ACR scenario corresponding to the current application is the first ACR scenario, or may indicate to the terminal device that when determining the target EES, the target EES needs to Supports the first ACR scenario.
  • the method further includes: receiving EAS information from a target EES, the EAS information indicating at least one EAS; and determining the target EAS according to the EAS information.
  • the target EES may send EAS information to the terminal device, indicating at least one EAS, from which the terminal device may determine the target EAS.
  • the application service may be switched from the currently connected EAS to the target EAS, and ACR may be performed based on the target EAS.
  • the method further includes: the terminal is configured to receive fifth information from the target EAS, where the fifth information indicates an ACR capability of the at least one EAS.
  • the ACR capabilities of EAS include whether EAS supports ACR, the ACR scenarios supported by EAS, and the ACR APIs supported by EAS.
  • the target EES can send information indicating the ACR capability of the EAS to the terminal device. Accordingly, the terminal device can obtain the ACR capability of at least one EAS indicated by the target EES, so that the terminal device can determine the EAS that supports the first ACR scenario based on the ACR capability of the EAS and use it as the target EAS.
  • the at least one EAS supports a first ACR scenario.
  • the target EES can select an EAS that supports the first ACR scenario, and indicate the EAS to the terminal device through the EAS information sent to the terminal device. In this way, the terminal device can select one of them as the target EAS.
  • the method also includes: the terminal device sends sixth information to the target EES, and the sixth information is used to indicate at least one of the following: selecting a target EAS that supports the first ACR scenario, or the source EES or source EAS cannot execute ACR, or the current application has no corresponding ACR scene, or requesting to obtain the ACR capability of the EAS.
  • the terminal device may send the sixth information to the target EES.
  • the target EES may send the EAS information to the terminal device based on the sixth information, and/or send the fifth information to the terminal device.
  • the target EES can filter out the EAS that supports the first ACR scenario based on the ACR capability of the EAS, and indicate it to the terminal device, so that the terminal device can determine an EAS as the target EAS without having to filter based on the ACR capability of the EAS, and the task volume of the terminal device can be reduced, which can reduce the burden on the terminal device.
  • the target EES can also indicate the EAS and the ACR capability of the EAS to the terminal device, and the terminal device filters out the EAS that supports the first ACR scenario as the target EAS, so that the target EES does not have to filter based on the ACR capability of the EAS, and the task volume of the target EES can be reduced, which can reduce the burden on the target EES.
  • the target EES and target EAS determined by the terminal device both support the first ACR scenario.
  • the target EES and target EAS are capable of performing ACR, thereby successfully completing the migration of the application context and ensuring the continuity of the application service.
  • the present application provides a communication method, which can be applied to ECS, can be executed by ECS, or can be executed by components configured in ECS (such as chips, chip systems, processors, etc.), or can be implemented by logic modules or software that can implement all or part of the ECS functions, and the present application does not limit this.
  • the method includes: sending EES information to a terminal device, the EES information indicating at least one EES; sending first information to the terminal device, the first information indicating an ACR capability of the at least one EES.
  • the ECS may send the EES information and the first information to the terminal device, indicating at least one EES and the ACR capability of the at least one EES, so that the terminal device can determine the target EES supporting the first ACR scenario based on the ACR capability of the EES.
  • the method further includes: receiving second information from the terminal device, where the second information is used to indicate a request to obtain the ACR capability of the EES.
  • the ECS may send the EES information and the first information to the terminal device based on the second information from the terminal device.
  • the present application provides a communication method, which can be applied to the ECS in the above-mentioned second aspect, and the method includes: determining at least one EES that supports a first ACR scenario, the first ACR scenario being a scenario in which ACR is executed by a target EES; sending EES information to a terminal device, the EES information indicating the at least one EES.
  • the ECS After the ECS determines at least one EES that supports the first ACR scenario, it may indicate it to the terminal device, so that the terminal device may select any one of them as the target EES.
  • the method further includes: receiving second information from the terminal device, the second information being used to indicate at least the following: One: Select a target EES that supports the target ACR scenario, or the currently connected EES or the currently connected EAS cannot perform ACR, or the current application has no corresponding ACR scenario.
  • the ECS may determine, based on the second information from the terminal device, at least one EES that supports the first ACR scenario, and indicate the at least one EES to the terminal device.
  • the present application provides a communication method, which can be applied to EES, and can be executed by EES, or can be executed by components configured in EES (such as chips, chip systems, processors, etc.), or can be implemented by logic modules or software that can implement all or part of the EES functions, and the present application does not limit this.
  • the method includes: determining that the current application has no corresponding ACR scenario; sending third information to the terminal device, the third information indicating that the current application has no corresponding ACR scenario, or indicating that the EES or the currently connected EAS cannot perform ACR.
  • the EES may indicate to the terminal device that the current application has no corresponding ACR scenario.
  • the present application provides a communication method, which can be applied to the EES in the fourth aspect above, and the method includes: determining to perform ACR based on a first ACR scenario, and the first ACR scenario is a scenario in which ACR is executed by a target EES; sending fourth information to a terminal device, and the fourth information is used to indicate the selection of a target EES that supports the first ACR scenario, or to indicate that the first ACR scene is the ACR scene corresponding to the current application.
  • the method before determining to perform ACR based on the first ACR scenario, the method further includes: determining that the current application has no corresponding ACR scenario.
  • EES can determine to perform ACR based on the first ACR scenario, and indicate to the terminal device that the first ACR scenario is the ACR scenario corresponding to the current application, that is, ACR needs to be performed based on the first ACR scenario when EAS switching is performed.
  • EES can determine to perform ACR based on the first ACR scenario when the current application has no corresponding ACR scenario, and can also determine to perform ACR based on the first ACR scenario in other situations. For example, when the EES and EAS currently connected to the terminal device both support ACR, EES can also determine to perform ACR based on the first ACR scenario.
  • the present application provides a communication method, which can be applied to the EES in the fourth aspect above, and the method includes: sending EAS information to a terminal device, the EAS information indicating at least one EAS; sending fifth information to the terminal device, the fifth information indicating the ACR capability of the at least one EAS.
  • the EES may send the EAS information and the fifth information to the terminal device, indicating at least one EAS and the ACR capability of the at least one EAS, so that the terminal device can determine the target EAS supporting the first ACR scenario based on the ACR capability of the EAS.
  • the method further includes: receiving sixth information from the terminal device, where the sixth information is used to indicate a request to obtain the ACR capability of the EAS.
  • the EES may send the EAS information and the fifth information to the terminal device based on the sixth information from the terminal device.
  • the present application provides a communication method, which can be applied to the EES in the fourth aspect above, and the method includes: determining at least one EAS that supports a first ACR scenario; the first ACR scenario is a scenario in which ACR is performed by a target EES; and sending EAS information to a terminal device, the EAS information indicating the at least one EAS.
  • the EES determines at least one EAS that supports the first ACR scenario, it may indicate it to the terminal device, so that the terminal device may select any one of them as the target EAS.
  • the method also includes: receiving sixth information from the terminal device, the sixth information being used to indicate at least one of the following: selecting a target EAS that supports the first ACR scenario, or the source EES and source EAS are unable to perform ACR, or the current application has no corresponding ACR scenario.
  • the EES may determine at least one EAS supporting the first ACR scenario based on the sixth information from the terminal device, and indicate the at least one EAS information to the terminal device.
  • the present application provides an EEC context transmission method, which can be applied to the terminal device in the aforementioned first aspect, and the method includes: obtaining the EEC context transmission capability of the source EES; determining the target EES, and the target EES is determined based on the EEC context transmission capability of the source EES.
  • the EEC context transmission capability includes whether the EES supports the transmission of the EEC context and the supported EEC context transmission process.
  • the target EES When performing EAS switching, the target EES needs to be determined first.
  • the terminal device can determine the target EES based on whether the source EES supports EEC context transmission and the EEC context transmission process supported by the source EES.
  • the terminal device can determine the target EES that supports the corresponding EEC context transmission capability as the source EES, so that the EEC context can be transmitted between the source EES and the target EES.
  • the target EES can obtain the EEC context, and based on the EEC context, the target EES can provide the terminal device with information that can be used in the edge computing service, so that the application business of the terminal device can proceed normally.
  • acquiring the EEC context transmission capability of the source EES includes: receiving first capability information from the source EES, where the first capability information indicates the EEC context transmission capability of the source EES.
  • the terminal device may determine whether the source EES supports EEC context transmission based on the information obtained from the source EES. If the source EES supports EEC context transmission, the terminal device may also determine the EEC context transmission process supported by the source EES.
  • the EEC context transmission process may include an EEC context pull process and/or an EEC context push process.
  • the source EES supports EEC context transmission.
  • the determining the target EES based on the EEC context transmission capability of the source EES includes: receiving EES information from an ECS, the EES information indicating at least one EES; receiving second capability information from the ECS, the second capability information indicating the EEC context transmission capability of the at least one EES; and determining the target EES from the at least one EES.
  • the terminal device can select an EES that supports the corresponding EEC context transmission process as the target EES from at least one EES indicated by the ECS.
  • the EEC context can be transmitted smoothly between the source EES and the target EES, and the target EES can successfully obtain the EEC context, thereby providing the terminal device with information that can be used in the edge computing service, so that the application business of the terminal device can proceed normally.
  • the method before receiving the EES information from the ECS, the method further includes sending first request information to the ECS, where the first request information indicates at least one of the following: the source EES supports EEC context transmission, or requests to obtain the EEC context transmission capability of the EES.
  • the ECS may send the second capability information to the terminal device after receiving the first request information from the terminal device.
  • the target EES and the source EES do not support the corresponding EEC context transfer process.
  • the terminal device may select an EES from the at least one EES that does not support the corresponding EEC context transfer process with the source EES as the target EES.
  • the method further comprises determining that re-registration with the target EES is required.
  • the terminal device can determine that it needs to re-register with the target EES, so that when the target EES and the source EES cannot perform EEC context transfer, the target EES can also obtain EEC information from the terminal device and generate EEC context based on the EEC information.
  • the source EES supports EEC context transmission; the target EES is determined based on the EEC context transmission capability of the source EES, including: sending third capability information to the ECS, the third capability information is used to indicate the EEC context transmission process supported by the source EES; receiving EES information from the ECS, the EES information indicating at least one EES; and determining the target EES from the at least one EES.
  • the ECS can determine the EEC context transmission process supported by the source EES based on the third capability information from the terminal device, so that the ECS can select at least one EES based on the EEC context transmission process supported by the source EES, and send EES information to the terminal device to indicate the at least one EES, so that the terminal device can determine the target EES therefrom.
  • the at least one EES selected by the ECS may be an EES that supports the EEC context transmission capability corresponding to that of the source EES, or may be an EES that does not support the EEC context transmission capability corresponding to that of the source EES.
  • the ECS when there is an EES with EEC context transmission capability corresponding to the source EES support among the EES managed by the ECS, the ECS can select at least one EES therefrom. When there is no EES with EEC context transmission capability corresponding to the source EES support among the EES managed by the ECS, the ECS can select at least one EES with EEC context transmission capability corresponding to the source EES not support.
  • the method further includes receiving registration indication information from the ECS.
  • the ECS may send a registration indication message to the terminal device, indicating that it needs to re-register with the target EES.
  • the terminal device may determine that it needs to re-register with the target EES based on the registration indication message.
  • the ECS can send a registration indication message to the terminal device, indicating that it is not necessary to re-register with the target EES.
  • the terminal device can determine that it does not need to re-register with the target EES based on the registration indication message. To re-register with the target EES.
  • the target EES can obtain the EEC information from the terminal device through the EEC registration process to generate the EEC context.
  • the terminal device does not need to register with the target EEC, which can avoid redundant operations.
  • the step of selecting an EES from the EES that has the corresponding EEC context transmission capability as the source EES can be executed by the ECS. In this way, when the terminal device determines the target EES, it is not necessary to screen based on the EEC context transmission capability of the EES, which can reduce the burden on the terminal device.
  • the source EES supports EEC context transmission; after determining the target EES, the method also includes: sending fourth capability information to the target EES, the fourth capability information indicating the EEC context transmission capability of the source EES; receiving registration indication information from the target EES, the registration indication information indicating whether re-registration with the target EES is required.
  • the terminal device can send information to the target EES to indicate that the source EES supports the EEC context transfer process.
  • the target EES can determine whether the target EES supports the corresponding EEC context transfer capability as the source EES.
  • the target EES may send registration indication information to the terminal device, indicating that the terminal device does not need to re-register with the target EES.
  • the target EES may send registration indication information to the terminal device, indicating that the terminal device needs to re-register with the target EES.
  • the target EES can instruct the terminal device to re-register with the target EES, so that the target EES can obtain the EEC information and generate the EEC context, and then provide the terminal device with information that can be used in the edge computing service, so that the application business of the terminal device can proceed normally.
  • the target EES and the source EES can transfer the EEC context, the target EES can instruct the terminal device not to register with the target EEC, which can avoid redundant operations.
  • the method after determining the target EES, the method also includes: receiving fifth capability information from the target EES, the fifth capability information indicating the EEC context transmission capability of the target EES; and determining whether re-registration is required based on the EEC context transmission capability of the target EES.
  • the target EES may indicate the EEC context transmission capability of the target EES to the terminal device, so that the terminal device may determine whether the target EES supports the corresponding EEC context transmission capability as the source EES.
  • the terminal device may determine that it does not need to re-register with the target EES.
  • the terminal device may determine that it needs to re-register with the target EES.
  • the method further includes: sending second request information to the target EES, where the second request information indicates a request to obtain the EEC context transmission capability of the EES.
  • the target EES may send the fifth capability information to the terminal device after receiving the second request information from the terminal device.
  • the step of determining whether the target EES supports the corresponding EEC context transmission capability as the source EES can be performed by the terminal device, and the terminal device further determines whether it needs to re-register with the target EES. In this way, the target EES does not need to make a judgment, which can reduce the burden on the target EES.
  • the present application provides a communication device that can implement the method performed by the terminal device in the above aspects, or can implement the method performed by the ECS in the above aspects, or can implement the method performed by the EES in the above aspects.
  • the device includes corresponding units or modules for performing the above methods.
  • the units or modules included in the device can be implemented by software and/or hardware.
  • the present application provides a communication device comprising a processor, wherein the processor can implement the method executed by the terminal device in the above aspects, or can implement the method executed by the ECS in the above aspects, or can implement the method executed by the EES in the above aspects.
  • the device may further include a memory for storing instructions and data.
  • the memory is coupled to the processor, and when the processor executes the instructions stored in the memory, the methods described in the above aspects may be implemented.
  • the apparatus may further include a communication interface, and the communication interface is used for the apparatus to communicate with other devices.
  • the communication interface may be a transceiver, circuit, bus, module or other types of communication interfaces.
  • the present application provides a communication system comprising at least one of a source EES and a target EES, wherein the source EES is used to implement the method performed by the EES in the fourth or fifth aspect, and the target EES is used to implement the method performed by the EES in the sixth or seventh aspect.
  • the communication system further includes an ECS, and the ECS is used to implement the methods executed by the ECS in the aforementioned aspects.
  • the communication system further includes a terminal device, which is used to implement the methods executed by the terminal device in the aforementioned aspects.
  • the present application provides a chip system, which includes at least one processor for supporting the functions involved in the methods executed by the terminal device in the above aspects, or for supporting the functions involved in the methods executed by the ECS in the above aspects, or for supporting the functions involved in the methods executed by the EES in the above aspects, for example, receiving or processing the data and/or information involved in the above methods.
  • the chip system also includes a memory, which is used to store program instructions and data, and the memory is located inside or outside the processor.
  • the chip system may be composed of the chip, or may include the chip and other discrete devices.
  • the present application provides a computer-readable storage medium, including a computer program, which, when executed, enables the method executed by the terminal device in the above-mentioned aspects to be implemented, or enables the method executed by the ECS in the above-mentioned aspects to be implemented, or enables the method executed by the EES in the above-mentioned aspects to be implemented.
  • the present application provides a computer program product, which includes: a computer program (also referred to as code, or instruction), which, when executed, enables the method executed by the terminal device in the above-mentioned aspects to be implemented, or enables the method executed by the ECS in the above-mentioned aspects to be implemented, or enables the method executed by the EES in the above-mentioned aspects to be implemented.
  • a computer program also referred to as code, or instruction
  • FIG1 is an architecture of a possible communication system applicable to the application context migration method provided in an embodiment of the present application
  • FIG2 is a schematic diagram of a scenario applicable to the ACR method provided in an embodiment of the present application.
  • FIG3 is a schematic flow chart of an ACR method provided in an embodiment of the present application.
  • FIG4 is a schematic flow chart of a method for an EEC to determine a target EES provided in an embodiment of the present application
  • FIG5 is a schematic diagram of the process of EAS registering with EES and ECS respectively;
  • FIG. 6 is a schematic diagram of a process of an EEC requesting a target EES to perform an ACR according to an embodiment of the present application
  • FIG. 7 is a schematic diagram of a method for an EEC to determine a target EAS provided in an embodiment of the present application
  • FIG8 is a possible implementation of the application context migration method provided in an embodiment of the present application.
  • FIG. 9 is another possible implementation of the application context migration method provided in an embodiment of the present application.
  • FIG10 is another possible implementation of the application context migration method provided in an embodiment of the present application.
  • FIG11 is another possible implementation of the application context migration method provided in an embodiment of the present application.
  • FIG12 is a schematic diagram of the EEC registration process provided in an embodiment of the present application.
  • FIG. 13 is a schematic diagram of an EEC context pull process and an EEC context push process provided in an embodiment of the present application;
  • FIG14 is a schematic flow chart of an EEC context transmission method provided in an embodiment of the present application.
  • FIG15 is a schematic flow chart of a method for determining a target EES according to an embodiment of the present application.
  • 16 is a schematic flowchart of a method for determining whether to perform EEC context transmission according to an embodiment of the present application
  • FIG17 is a possible implementation of the EEC context migration method provided in an embodiment of the present application.
  • FIG18 is another possible implementation of the EEC context migration method provided in an embodiment of the present application.
  • FIG19 is a schematic block diagram of a communication device provided in an embodiment of the present application.
  • FIG. 20 is another schematic block diagram of a communication device provided in an embodiment of the present application.
  • the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) mobile communication system, the new radio access technology (new radio access technology, NR) system, the long term evolution (long term evolution, LTE) system, the LTE frequency division duplex (frequency division duplex, FDD) system, the LTE time division duplex (time division duplex, TDD), the universal mobile telecommunication system (universal mobile telecommunication system, UMTS), or the world-wide interoperability for microwave access (worldwide interoperability for microwave access, WiMAX) communication system.
  • the mobile communication system may include non-standalone (NSA) and/or standalone (SA).
  • SA standalone
  • the technical solutions provided in the present application can also be applied to future communication systems, such as the sixth generation mobile communication system, etc. This application is not limited to this.
  • the technical solution provided in the present application can also be applied to machine type communication (MTC), Long Term Evolution-machine (LTE-M), device-to-device (D2D) network, machine-to-machine (M2M) network, Internet of Things (IoT) network or other networks.
  • IoT network can include vehicle networking, for example.
  • vehicle to X, V2X, X can represent anything
  • the V2X can include: vehicle to vehicle (V2V) communication, vehicle to infrastructure (V2I) communication, vehicle to pedestrian (V2P) communication or vehicle to network (V2N) communication, etc.
  • the technical solution of the present application can be applied to various communication scenarios, such as service continuity scenarios, multi-access edge computing (MEC) scenarios, etc., and the present application does not impose any restrictions on this.
  • MEC multi-access edge computing
  • FIG1 shows the architecture of a possible communication system applicable to the application context migration method provided in an embodiment of the present application.
  • the communication system includes terminal equipment, a core network, an EDN and an ECS.
  • one or more application clients (AC) and one or more edge enabler clients (EEC) can be configured in the terminal device, and one or more EAS and one or more EES can be deployed in the EDN.
  • AC application clients
  • EEC edge enabler clients
  • the architecture of Figure 1 also includes reference points EDGE-1 to EDGE-9.
  • the EDGE-1 reference point supports the interaction between EES and EEC;
  • the EDGE-2 reference point supports the interaction between EES and the core network;
  • the EDGE-3 reference point supports the interaction between EES and EAS;
  • the EDGE-4 reference point supports the interaction between ECS and EEC;
  • the EDGE-5 reference point supports the interaction between AC and EEC;
  • the EDGE-6 reference point supports the interaction between ECS and EES;
  • the EDGE-7 reference point supports the interaction between EAS and the core network;
  • the EDGE-8 reference point supports the interaction between ECS and the core network;
  • the EDGE-9 reference point supports the interaction between two EESs in the same or different MEC nodes.
  • FIG. 1 is for illustration only, and the communication system may also include other devices which are not shown in FIG. 1 .
  • the names of the various network elements and the communication interfaces between network elements involved in FIG. 1 are briefly described by taking the current protocol as an example, but the embodiments of the present application are not limited to being applicable only to currently known communication systems. Therefore, the standard names that appear when describing the current protocol as an example are all functional descriptions.
  • the present application does not limit the specific names of network elements, interfaces, information, messages, or signaling, but only indicates the functions of network elements, interfaces, information, messages, or signaling, which can be correspondingly extended to other systems, such as 4G or future communication systems.
  • Edge computing refers to an open platform that integrates network, computing, storage, and application core capabilities at the edge of the network close to the source of objects or data, providing edge intelligence services nearby to meet the key needs of industry digitalization in terms of agile connection, real-time business, data optimization, application intelligence, security and privacy protection, etc.
  • edge computing is to analyze the data collected from the terminal device directly in the local device or network close to the data generation, without the need to transmit the data to the cloud data processing center.
  • Multi-access edge computing also known as mobile edge computing, can use wireless access networks to provide services and cloud computing functions nearby, thereby creating a telecommunications-grade service environment with high performance, low latency and high bandwidth, accelerating the rapid download of various content, services and applications in the network, allowing consumers to enjoy an uninterrupted high-quality network experience.
  • Data network refers to the service network of operators or third parties, which can provide services to terminal devices, such as operator services, Internet services, etc.
  • LADN Local area data network
  • EDN Edge Data Network
  • DNAI data network access identifier
  • DNN data network name
  • Another understanding is that EDN is a peer-to-peer concept of the central cloud. It can be understood as a local data center that can be identified by DNAI and can include multiple local data networks.
  • Application instance/edge application refers to an application deployed in the edge data network, which can specifically refer to an application on a server (for example, social media software, augmented reality (AR), virtual reality (VR)), or an instance deployed and running in an EDN.
  • An application can deploy one or more EAS in one or more EDNs.
  • EASs deployed and running in different EDNs can be considered different EASs of an application. They can share a domain name, use an Internet protocol (IP) address, or use different IP addresses.
  • IP Internet protocol
  • application instance/edge application can also be called edge application (server), application instance, edge application instance, MEC application (server), EAS function, etc.
  • Application Client refers to the peer entity of edge application on the terminal device side.
  • Application client is used by application users to obtain application services from application servers.
  • Application client is a client program applied on the terminal device side.
  • Application client can connect to application servers on the cloud to obtain application services, or it can connect to EAS deployed in one or more EDNs to obtain application services.
  • EES Edge Enablement Server It can provide enabling capabilities for EAS deployed in EDN and can better support the deployment of applications in MEC. For example, EES can support application registration, authentication and authorization of terminal devices, and provide EAS IP address information for terminal devices. EES can also support obtaining EAS identification and IP address information, and send EAS identification and IP address information to ECS.
  • EES is deployed in EDN.
  • an EAS is registered to an EES, or the information of an EAS is configured on an EES through the management system.
  • An EES can be registered with one or more EASs, or configured with the information of one or more EASs.
  • the EES is called the EES associated with the one or more EASs.
  • EES can control, manage, register or configure the EASs associated with the EES.
  • Edge Enablement Client It is used to provide the support functions required by AC and is the peer entity of EES on the terminal device side. EEC is used to register EEC information and AC information with EES, perform security authentication and authorization, obtain the IP address of EAS from EES, and provide edge computing enabling capabilities to AC, such as discovering EAS available in EDN and returning the IP address of EAS to AC.
  • ECS Edge Configuration Server
  • the service area of the EDN can be topological address information (such as cell identity, tracking area identity (TAI), etc.) or geometric address information (such as province, city, district or longitude and latitude, etc.), and the service area can be a collection of address information.
  • topological address information such as cell identity, tracking area identity (TAI), etc.
  • geometric address information such as province, city, district or longitude and latitude, etc.
  • ECS can be deployed in the mobile network operator (MNO) domain or in a third-party domain by a service provider.
  • ECS network elements are deployed in a distributed manner, that is, each ECS can manage edge data networks in different regions. It should be understood that ECS network elements can be co-located with other network elements or can be independent network elements. This application does not impose any restrictions on the deployment of ECS network elements in the network architecture.
  • Terminal equipment also known as user equipment (UE), mobile station (MS), mobile terminal (MT), etc.
  • UE user equipment
  • MS mobile station
  • MT mobile terminal
  • terminal equipment includes handheld devices with wireless transceiver functions, vehicle-mounted devices, etc.
  • terminal devices can be: mobile phones, tablet computers, laptops, PDAs, mobile Internet devices (MID), wearable devices (such as smart watches, smart bracelets, smart glasses, etc.), vehicle-mounted devices (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), virtual reality (VR) devices, augmented reality devices, etc.
  • MID mobile Internet devices
  • wearable devices such as smart watches, smart bracelets, smart glasses, etc.
  • vehicle-mounted devices such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.
  • VR virtual reality
  • the terminal device can also be a chip. This application does not limit the specific form of the terminal device.
  • Core network mainly used to manage terminal devices and provide the function of communicating with the external network.
  • the core network may include at least one of the user plane function (UPF) network element, the access and mobility management function (AMF) network element, the session management function module (SMF) network element, the unified data management (UDM) network element or the policy control function (PCF) network element.
  • UPF user plane function
  • AMF access and mobility management function
  • SMF session management function module
  • UDM unified data management
  • PCF policy control function
  • Application context may refer to the running status information related to one or a group of users, such as game progress, historical data, etc.
  • the application context may also include the subscription context of the one or more users in the EAS and the core network, such as the transaction identifier of the subscription, etc.
  • the application context may also include the context of the one or more users on the EES, such as the transaction identifier of the subscription of the one or more users by the EAS.
  • EEC context may refer to user-related data stored in EES.
  • EEC context may include EEC side information and EAS-EES subscription information.
  • EEC side information may include EEC registration information, EEC subscription information (for example, EAS discovery subscription, EAS dynamic information subscription, etc.);
  • EAS-EES subscription information may include terminal device location API, application context migration events, AC information open API, terminal device identification API, and quality of service (QoS) session API, etc.
  • QoS quality of service
  • Application Context Migration It can also be called application migration or application context relocation. It is the process of migrating application context between EAS.
  • the ACR process can be divided into the following four stages:
  • the detection entity can detect events that require ACR, such as a change in terminal location, an update to the terminal user plane path, and the like.
  • Phase 2 ACR decision making.
  • the execution entity transfers the application context from the source EAS to the target EAS. Further, including the discovery of the target EAS, the terminal device can be notified of relevant information of the target EAS, the EAS (which can be the source EAS and the target EAS) can be notified to initiate application context transfer (ACT), EES or EAS executes application function (AF) traffic influence (AF traffic influence) and carries the N6 routing information of the target EAS.
  • the EAS which can be the source EAS and the target EAS
  • ACT application context transfer
  • EES or EAS executes application function (AF) traffic influence (AF traffic influence) and carries the N6 routing information of the target EAS.
  • ACR scenario A specific solution for detecting and executing ACR, including ACR detection, ACR decision, ACR execution and post-ACR cleanup.
  • the ACR scenario involves entities that execute each step.
  • the ACR capability in the embodiments of the present application may include but is not limited to whether ACR is supported, whether the first ACR scenario is supported, supported ACR scenarios, and supported ACR APIs. Based on the ACR capability of EES, the ACR scenarios supported by EES can be determined, and based on the ACR capability of EAS, the ACR scenarios supported by EAS can be determined.
  • the ACR capability of the EES may also include the EEC context transmission capability of the EES.
  • the EEC context transmission capability of the EES includes whether the EES supports EEC context transmission, whether the EES supports the EEC context pull process, and whether the EES supports the EEC context push process.
  • the EEC context transmission capability corresponding to the EES also includes the EEC context transmission process supported by the EES.
  • the EEC context transmission capability can be indicated by the API information supported by the EES.
  • AC and EEC may be configured on the terminal device.
  • the user of the application signs a service agreement with the provider of the application, logs in to the AC corresponding to the application on the terminal device, and communicates through the connection between AC and EAS, so as to obtain the service of the application.
  • EEC is a middleware layer, generally located in the operating system, or between AC and the operating system. AC can obtain edge enabling services from EEC in the form of API.
  • EAS that provides application services can be configured in EDN near the terminal device.
  • the application data in the terminal device can be processed in real time in the EAS close to the terminal device, without transmitting the data to the central cloud for processing, so as to reduce the delay caused by data transmission.
  • the same application can deploy EAS in multiple EDNs.
  • the EAS of the same application deployed in different EDNs can provide the same services and have functional equivalence.
  • the server of application a can be deployed in EDN-1 located in location A and in EDN-2 located in location B.
  • the terminal device located in location A can be configured with the AC of application a and can obtain application services through the EAS in the nearby EDN-1.
  • the terminal device located in location B can also be configured with the AC of application a and can obtain application services through the EAS in the nearby EDN-2.
  • the terminal device After accessing the network, the terminal device will select the EAS deployed in the nearest EDN to execute services. When the terminal device moves from the service area of one EDN to the service area of another EDN, or the EAS currently connected to the terminal device is fully loaded, the EAS currently connected to the terminal device cannot continue to provide services for the terminal device well. In order to meet the business continuity requirements of the application, it is necessary to re-select a new EAS for the terminal device so that it can continue to provide services for the terminal device.
  • FIG2 is a schematic diagram of a scenario applicable to the ACR method provided in an embodiment of the present application.
  • EES1, EAS1 and EAS2 can be deployed in EDN1, and EES2 and EAS2 can be deployed in EDN2.
  • EAS2 in EDN1 and EDN2 can provide the current application service for the terminal device.
  • the EAS currently providing services to the terminal device is EAS2 in EDN1.
  • EAS2 in EDN1 When the terminal device moves from the service area of EDN1 to the service area of EDN2, or when EAS2 in EDN1 is fully loaded, EAS2 in EDN1 will no longer be able to provide application services to the terminal device.
  • the application service of the current application can be switched to EAS2 in EDN2, and the context of the current application of the terminal device needs to be synchronously migrated from EAS2 in EDN1 to EAS2 in EDN2.
  • An application can deploy EAS in more or fewer EDNs, and each EDN can have its own service area. EAS of multiple applications can also be deployed in one EDN.
  • the EAS that currently provides application services to the terminal device is referred to as the source EAS (source EAS, S-EAS), or the currently connected EAS, such as EAS2 in EDN1 in Figure 2;
  • the EES associated with the source EAS is referred to as the source EES (source EES, S-EES), or the currently connected EES, such as EES1 in Figure 2;
  • the new EAS that provides application services to the terminal device is referred to as the target EAS (target EAS, T-EAS), such as EAS2 in EDN2 in Figure 2
  • the EES associated with the target EAS is referred to as the target EES (target EES, T-EES), such as EES2 in Figure 2.
  • the terminal device After the terminal device is connected to the EAS, it needs to negotiate with the EAS and the EES associated with the EAS to determine the ACR scenario of the application, so that the application can perform ACR detection, decision-making and execution processes based on the determined ACR scenario, so as to complete the switching process when the application's business needs to switch between EASs.
  • the terminal device When the terminal device, the EAS currently connected to the terminal device (or selected by the terminal device), and the EES associated with the EAS do not have a commonly supported ACR scenario, for example, the EEC, EAS or EES do not support the execution of ACR, it is impossible to negotiate and determine the ACR scenario of the current application. Therefore, when the EAS currently providing application services to the terminal device is fully loaded, or the terminal device leaves the service area of the EDN where the EAS is located, the current application cannot implement ACR, and the smooth switching of the EAS cannot be completed.
  • the present application provides an ACR method, which completes the migration of the context of the current application by determining a target EES that supports the execution of ACR and executing ACR based on the target EES.
  • the context migration of the current application can be achieved through the target EES.
  • the current application has no corresponding ACR scenario, for example, when the terminal device, the EAS currently connected to the terminal device (or selected by the terminal device), and the EES associated with the EAS do not have a commonly supported ACR scenario
  • the context migration of the current application can also be achieved.
  • the EAS currently connected to the terminal device can no longer provide application services, the smooth switching of the EAS can be guaranteed, thereby ensuring the stability and continuity of the application business.
  • the words “first” and “second” are used to distinguish the same items or similar items with basically the same functions and effects.
  • the first information and the second information are only used to distinguish different information, and their order is not limited.
  • the words “first” and “second” do not limit the quantity and execution order, and the words “first” and “second” do not limit a certain different.
  • edge application server edge enabling server
  • application context migration EEC, EES, source EES, target EES, EAS, source EAS, target EAS, ACR, etc.
  • EEC edge application server
  • EES application context migration
  • source EES target EES
  • EAS source EAS
  • target EAS target EAS
  • ACR application context migration
  • At least one means one or more, and “more than one” means two or more.
  • “And/or” describes the association relationship of associated objects, indicating that three relationships may exist.
  • a and/or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.
  • the character “/” generally indicates that the associated objects before and after are in an “or” relationship.
  • “At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items.
  • At least one of a, b and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c, where a, b, c can be single or multiple.
  • the tables in the embodiments of the present application are only examples and do not limit the scope of protection of the present application.
  • the values of the information in the table are only examples and can be configured as other values, which are not limited by the present application.
  • appropriate deformation adjustments can be made based on the tables in the text, such as splitting, merging, etc.
  • the parameter names shown in the titles of the tables can also use other names that can be understood by the communication device, and the values or representations of the parameters can also use other values or representations that can be understood by the communication device.
  • other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables.
  • pre-definition or “pre-configuration” can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and an ECS), and the present application does not limit its specific implementation method.
  • "saving” may mean saving in one or more memories.
  • the one or more memories may be separately set or integrated in an encoder or decoder, a processor, or a communication device.
  • the one or more memories may also be partially separately set and partially integrated in a decoder, a processor, or a communication device.
  • the type of memory may be any form of storage medium, which is not limited by the present application.
  • sending information to...(terminal) can be understood as the destination of the information being the terminal. It can include sending information to the terminal directly or indirectly.
  • receiving information from...(terminal) can be understood as the source of the information being the terminal, which can include receiving information from the terminal directly or indirectly.
  • the information may be processed as necessary between the source and destination of the information, such as format changes, etc., but the destination can understand the valid information from the source. Similar expressions in this application can be understood similarly and will not be repeated here.
  • FIG3 is a schematic flow chart of the ACR method provided in an embodiment of the present application.
  • the method shown in FIG3 illustrates the ACR method provided by an embodiment of the present application from the perspective of a terminal device.
  • the method can be executed by a terminal device, or by a component (such as a circuit, a chip, a chip system, etc.) in the terminal device, and can be implemented by software and/or hardware.
  • the present application does not limit this.
  • the following description is taken as an example of an EEC configured in a terminal device.
  • method 300 includes step 310 and step 320 .
  • the EEC determines a target EES, where the target EES is an EES that supports a first ACR scenario, where the first ACR scenario is a scenario in which ACR is performed by the target EES.
  • the first ACR scenario is a scenario where the target EES executes ACR, for example, it can be a scenario "EEC executed ACR via T-EES".
  • the ACR process can be that the EEC detects an event that requires ACR and decides whether to If no ACR is performed, the target EES will perform ACR.
  • the EES supports the first ACR scenario, which means that the EES can be used as a target EES to support the execution of the ACR.
  • the EAS supports the first ACR scenario, which means that the EAS can be used as a target EAS to support the execution of the ACR.
  • the EEC may determine a target EES that supports the first ACR scenario, and then when the EEC requests it to perform ACR, the target EES is capable of performing ACR.
  • EEC can determine the target EES through the service provisioning process or the EES discovery process.
  • step 310 in detail from the perspective of interaction between network elements in combination with FIG. 4 (a) and FIG. 4 (b).
  • Fig. 4 (a) is a schematic diagram of a method for determining a target EES by an EEC through an ECS provided by an embodiment of the present application.
  • the EEC determines a target EES supporting a first ACR scenario based on the ACR scenarios supported by the EES.
  • Method 400a may include steps 410a to 440a.
  • step 410a the EEC sends a service provisioning request message (service provisioning request) to the ECS.
  • the service activation request message may also be called a service configuration request message, which may include an EEC identifier (EEC ID), security credentials, AC configuration information (AC profile), terminal device identification, connection information, and terminal device location, etc.
  • EEC ID EEC identifier
  • AC profile AC configuration information
  • terminal device identification may include a generic public subscription identifier (GPSI), etc.
  • the EEC may also send information to the ECS to indicate a request to obtain the ACR capability of the EES.
  • the information is referred to as the second information, and it should be understood that this cannot be a limitation of the present application.
  • the second information may be carried in the above-mentioned service activation request message, for example.
  • the EEC may send the second information to the ECS.
  • the second information may also indicate that the selected ACR scene is the first ACR scene.
  • step 420a after receiving the service activation request message, the ECS processes the service activation request and determines or identifies one or more EESs.
  • the ECS may perform an authorization check to verify whether the EEC has authorization to perform the operation.
  • the ECS can match the EES registered on the ECS according to the AC configuration information and/or the terminal device location information.
  • the ECS can select one or more EESs according to the service activation request.
  • the ECS can select an EES whose service area contains the location of the terminal device, an EES whose EAS identifier (EAS ID) matches the AC configuration information in the registered EAS list, etc.
  • the ECS may obtain relevant information of one or more EESs.
  • the relevant information of the EES may include information indicating at least one EES, such as a list of EESs, and the relevant information of the EES may also include information indicating the ACR capability of the at least one EES, and may also include information indicating at least one EAS associated with the EES, and information indicating the ACR capability of the at least one EAS.
  • the relevant information of EES can be obtained by ECS when EES registers with ECS.
  • EES can be registered with ECS, and ECS can save the relevant information of EES.
  • EAS determines that it needs to be registered with EES, such as when EAS is configured and started, EAS can also be registered with EES, and EES can save the information of EAS.
  • the EES may obtain the information of the EAS through the network management system, and the ECS may also obtain the relevant information of the EES through the network management system without performing the registration process.
  • the ECS may store the relevant information of one or more EESs, and the relevant information of the EESs may be pre-configured, and the EES may also store the information of one or more EASs, and the information of the EASs may also be pre-configured, which is not limited in this application.
  • FIG5( a ) is a schematic diagram of the process of EAS registering with EES.
  • the EAS registration process may include steps 510a to 530a.
  • step 510a EAS sends an EAS registration request message to EES.
  • the EAS registration request message can carry EAS configuration information (EAS profile) and EAS security credentials, and can also include registration The recommended expiration date of the registration, or the effective date of the registration.
  • EAS profile EAS configuration information
  • EAS security credentials EAS security credentials
  • the EAS may also send information to the EES indicating the ACR capability of the EAS, such as whether the EAS supports ACR, or the ACR scenarios supported by the EAS.
  • the information may be carried in the EAS registration request message, for example, may be included in the EAS configuration information.
  • the information may be represented, for example, by the "service continuity support" parameter.
  • step 520a the EES processes the registration request.
  • EES performs a registration authorization check based on the EAS registration request message to verify whether EAS has the authorization to register on EES.
  • the EES After successful authorization, the EES stores the EAS configuration information for later use (eg, to service EAS discovery requests received from the EEC, etc.) The EES may also save the ACR capabilities of the EAS.
  • step 530a the EES sends an EAS registration response message to the EAS.
  • EES replies to EAS with an EAS Registration Response message. If the registration is successful, the EAS Response message may carry information indicating that the registration is successful. EES may also provide an expiration time to indicate to EAS when the registration automatically expires. If the registration fails, the EAS Response message may carry information indicating that the registration failed and the reason for the failure. (b) in Figure 5 is a schematic diagram of the process of EES registering with ECS.
  • the registration process of EES may include steps 510b to 530b.
  • step 510b the EES sends an EES registration request message to the ECS.
  • the EES registration request message may carry the configuration information of the EES.
  • the configuration information of the EES may include at least one of the following information: the EES identifier, the endpoint information of the EES, the identifier list of the EAS registered to the EES, etc.
  • the configuration information of the EES also includes the security credentials of the EES.
  • the configuration information of the EES may also include the effective time of the registration.
  • the EES may also send information to the ECS to indicate the ACR capability of the EES, such as the ACR scenarios supported by the EES.
  • the information may be carried in an EES registration request message, such as included in the configuration information of the EES.
  • the EES may also send information to the ECS indicating the ACR capabilities of the EAS registered with the EES, such as the ACR scenarios supported by the EAS. This information may also be carried in the EES registration request message.
  • step 520b the ECS processes the registration request.
  • the ECS After receiving the EES registration request message, the ECS can save the configuration information of the EES locally. The ECS can also save the ACR capability of the EES and the ACR capability of the EAS registered on the EES.
  • step 530b the ECS sends an EES registration response message to the EES.
  • the ECS may also send a corresponding response message.
  • the registration process of EES and the registration process of EAS may not be executed continuously in time.
  • An EAS may register with the EES at any time interval after the EES registers with the ECS, and after the EAS registers with the EES, the EES may perform the process of registering with the ECS at any time interval.
  • step 430a the ECS sends a service activation response message to the EEC.
  • the service activation response message may also be referred to as a service configuration response message. If the ECS cannot determine the EEC information based on the service activation request message, the service activation response message carries an information element indicating that the ECS rejects the service activation request of the EEC and gives the reason for the failure. If the ECS successfully processes the service activation request of the EEC, the service activation response message may carry EDN connection information, EES information (which may include a list of one or more EESs determined or identified by the ECS, as well as the addresses of the one or more EESs, identification information of the one or more EESs, etc.). The service activation response message may also carry information about the EAS associated with each EES in the one or more EESs determined or identified by the ECS.
  • the ECS may also send information to the EEC, indicating the ACR capabilities of each EES in one or more EESs identified or determined by the ECS, such as the ACR scenarios supported by the EES.
  • the information is referred to as first information, and it should be understood that this cannot be a limitation of the present application.
  • the first information may be carried in the above-mentioned service activation response message, for example, included in the EES information.
  • the first information may also indicate the ACR capability of the EAS associated with each EES in one or more EESs determined or identified by the ECS.
  • the ECS may store the information of all EESs registered or configured on the ECS. All the information is sent to EEC. At this time, the above step 420a is optional.
  • step 440a the EEC determines a target EES that supports the first ACR scenario from among one or more EESs.
  • the information received by the EEC may indicate one or more EESs and the ACR capabilities of the one or more EESs, and the EEC may select an EES that supports the first ACR scenario as a target EES.
  • the EEC also receives information indicating the EAS to which the EES is associated and the ACR scenarios supported by the EAS, from which the EEC may select an EES associated with the EAS supporting the first ACR scenario as a target EES.
  • the target EES determined by the EEC supports the first ACR scenario, and at least one of the EASs associated with the target EES also supports the first ACR scenario.
  • the EES information from the ECS does not include an EES that supports the first ACR scenario, and the EEC cannot determine the target EES.
  • FIG4 is another schematic diagram of a method for determining a target EES through an ECS provided by an embodiment of the present application.
  • the ECS selects an EES supporting a first ACR scenario based on the ACR scenarios supported by the EES and sends the EES to the EEC.
  • Method 400b may include steps 410b to 440b.
  • step 410b the EEC sends a service activation request message to the ECS.
  • the description of the service activation request message can be found in the aforementioned step 410a, which will not be repeated here.
  • the EEC may also send second information to the ECS, where the second information may indicate at least one of the following: selecting an EES that supports the first ACR scenario, or preferably an EES that supports the first ACR scenario, or the source EES and/or source EAS cannot perform ACR, or the current application has no corresponding ACR scenario.
  • the second information may be carried in the above-mentioned service activation request message, for example.
  • the EEC may send the second information to the ECS.
  • the second information may also indicate that the selected ACR scene is the first ACR scene.
  • step 420b after receiving the service activation request message, the ECS processes the service activation request and selects an EES that supports the first ACR scenario.
  • the ECS may optionally perform an authorization check to verify whether the EEC has the authorization to perform the operation.
  • the ECS may determine that an EES supporting the first ACR scenario needs to be selected. For example, it may be determined that an EES supporting the first ACR scenario needs to be selected based on second information from the ECS.
  • the ECS may match the EES registered with the ECS according to the AC configuration information and/or the terminal device location information, and select the EES supporting the first ACR scenario based on the ACR scenarios supported by the EES.
  • the ECS may select an EES whose service area includes the location of the terminal device, or an EES whose registered EAS list includes an EAS identifier (EAS ID) matching the AC configuration information, or an EES whose service area includes the location of the terminal device and whose registered EAS list includes an EAS ID matching the AC configuration information.
  • the ECS may further determine one or more EESs that support the first ACR scenario.
  • the ECS may add a condition when selecting an EES, that is, the EES needs to support the first ACR scenario.
  • the ECS may select an EES associated with an EAS supporting the first ACR scenario.
  • one or more EESs selected by the ECS support the first ACR scenario, wherein at least one of the EASs associated with each EES also supports the first ACR scenario.
  • step 430b the ECS sends a service activation response message to the EEC.
  • step 430a For a detailed description of the corresponding message for service activation, please refer to the aforementioned step 430a.
  • the ECS After the ECS selects, determines or identifies one or more EESs that support the first ACR scenario, it may indicate the one or more EESs through EES information in a service activation response message sent to the EEC.
  • step 440b the EEC determines the target EES.
  • the information received by the EEC indicates an EES, and the EEC may determine it as the target EES. In some embodiments, the information received by the EEC indicates multiple EESs that support the first ACR scenario, and the EEC may determine an EES as the target EES.
  • the present application does not limit the specific determination method, for example, it may be randomly determined or determined based on a local policy.
  • step 440b is an optional step.
  • (a) in Figure 4 and (b) in Figure 4 provide a method for determining the target EES.
  • the step of determining the EES that supports the first ACR scenario from the EES can be executed by the ECS, so that the terminal device does not have to perform screening, which can reduce the burden on the terminal device; this step can also be executed by the EEC, so that the ECS does not have to perform screening based on the ACR capability of the EES, which can reduce the burden on the ECS.
  • the target EES determined by the EEC supports the first ACR scenario.
  • the EES has the ability to perform ACR as a target EES.
  • the EEC can successfully complete the migration of the application context through the target EES, thereby ensuring the continuity of the current application's business.
  • step 320 the EEC requests the target EES to perform ACR.
  • the EEC After determining the target EES, the EEC can establish a communication connection with the target EES through the address of the target EES obtained from the ECS, and request it to perform ACR.
  • the method of the EEC requesting the target EES to perform ACR includes discovering the target EAS, transmitting application context between the target EAS and the source EAS, and other processes.
  • step 320 in detail from the perspective of interaction between network elements in conjunction with FIG. 6 .
  • step 320 may further include steps 610 to 650 .
  • the EEC may perform an EAS discovery process to determine a target EAS that supports the first ACR scenario.
  • the process of the EEC determining the target EAS may be as shown in FIG. 7( a ) or FIG. 7( b ).
  • FIG7 (a) is a schematic diagram of a method for determining a target EAS by an EEC according to an embodiment of the present application.
  • the EEC determines a target EAS supporting a first ACR scenario based on the ACR scenarios supported by the EAS.
  • Method 700a may include steps 710a to 740a.
  • step 710a the EEC sends an EAS discovery request message to the target EES.
  • the EAS discovery request message may include an EEC ID and security credentials.
  • the EAS discovery request message may also include an EAS discovery filter, which may include filter parameters of the EAS to retrieve information about a specific EAS or a specific type of EAS (e.g., a gaming application).
  • the EEC may also send information to the target EES to request the acquisition of the ACR capability of the EAS.
  • the information is referred to as the sixth information, but it should be understood that this cannot be a limitation to the present application.
  • the sixth information may be carried in the above-mentioned EAS discovery request message, for example, included in the EAS discovery filter.
  • the sixth information may also indicate that the selected ACR scene is the first ACR scene.
  • step 720a the target EES processes the EAS discovery request and determines or identifies one or more EASs.
  • the target EES after receiving the EAS discovery request sent by the EEC, the target EES performs an authorization check and selects one or more EASs.
  • the target EES may select one or more EASs based on the provided EAS discovery filter and the location of the terminal device. If the EAS discovery filter is not provided in the EAS discovery request message, the target EES may select one or more EASs based on the terminal device-specific service information and the terminal device location on the target EES, or the target EES selects one or more EASs by applying an edge computing service provider (ECSP) policy (e.g., based only on the terminal device location).
  • ECSP edge computing service provider
  • the target EES may reject the EAS discovery request of the EEC and give the corresponding failure reason.
  • step 730a the target EES sends an EAS discovery response message to the EEC.
  • the EAS discovery response message may include EAS information (which may include a list of EASs determined or identified by the EES, and EAS configuration information, etc.), and the EAS information may indicate one or more EASs determined or identified by the target EES. If the target EES cannot determine or identify one or more EAS, the EAS discovery response message may include a failure indication and the reason for the failure.
  • the target EES may also send information to the EEC, indicating the ACR capability of each EAS in one or more EASs determined or identified by the target EES, such as the ACR scenarios supported by the EAS.
  • the information is referred to as the fifth information, and it should be understood that this cannot be a limitation of the present application.
  • the fifth information may be carried in the above-mentioned EAS discovery response message, for example, included in the EAS information.
  • the target EES may send all the information of all EASs registered or configured on the target EES to the target EES.
  • the aforementioned step 720a is optional.
  • step 740a the EEC determines a target EAS that supports the first ACR scenario from among the one or more EASs.
  • the information received by the EEC may indicate one or more EASs and the ACR capabilities of the one or more EASs, and the EEC may select an EAS that supports the first ACR scenario as a target EAS.
  • FIG7( b ) is another schematic diagram of a method for an EEC to determine a target EAS provided by an embodiment of the present application.
  • the target EES selects an EAS supporting a first ACR scenario based on the ACR scenarios supported by the EAS, and sends the EAS to the EEC.
  • Method 700b may include steps 710b to 740b .
  • step 710b the EEC sends an EAS discovery request message to the target EES.
  • the EEC may also send sixth information to the target EES, where the sixth information may indicate at least one of the following: selecting an EAS that supports the first ACR scenario, or preferably an EAS that supports the first ACR scenario, or the source EES and/or the source EAS cannot perform ACR, or the current application has no corresponding ACR scenario.
  • the sixth information may be carried in the above-mentioned service activation request message, for example.
  • the second information may further indicate that the selected ACR scenario is the first ACR scenario.
  • the target EES processes the EAS discovery request and selects an EAS that supports the first ACR scenario.
  • the target EES may determine that it is necessary to select an EAS that supports the first ACR scenario. For example, it may determine that it is necessary to select an EAS that supports the first ACR scenario based on the sixth information from the EEC.
  • the target EES may select one or more EASs that support the first ACR scenario. For example, the target EES may select one or more EASs based on the method in the aforementioned step 720a, and determine one or more EASs that support the first ACR scenario based on the ACR capabilities of the one or more EASs. Alternatively, when selecting an EAS based on the method in the aforementioned step 720a, a condition may be added, that is, the EAS needs to support the first ACR scenario.
  • step 730b the target EES sends an EAS discovery response message to the EEC.
  • the target EES may indicate the one or more EASs through EAS information in the EAS discovery response message sent to the EEC.
  • step 740b the EEC determines the target EAS.
  • the information received by the EEC indicates an EAS, and the EEC may determine it as the target EAS. In some embodiments, the information received by the EEC indicates multiple EASs that support the first ACR scenario, and the EEC may determine one EAS as the target EES.
  • the present application does not limit the specific determination method, for example, it may be randomly determined or determined based on local policies.
  • step 740b is an optional step.
  • Step 740a in method 700a or step 740b in method 700b may also be performed by the AC.
  • the EEC may pass the EAS information to the AC through inter-layer interaction, and the AC may determine the target EAS from one or more EASs received by the EEC.
  • (a) in Figure 7 and (b) in Figure 7 provide a method for determining the target EAS.
  • the step of determining the EAS that supports the first ACR scenario from the EAS can be executed by the target EES, so that the terminal device does not have to perform screening, which can reduce the burden on the terminal device; this step can also be executed by the terminal device, so that the target EES does not have to perform screening based on the ACR capability of the EAS, which can reduce the burden on the target EES.
  • the EEC can find an EAS associated with the target EES and supporting the first ACR scenario, and use it as the target EAS.
  • the EAS has the ability to complete the ACR as the target EAS, and the migration of the application context can be successfully completed through the target EAS.
  • step 620 the EEC sends an ACR request message to the target EES, requesting the target EES to perform at least one of the following actions: interacting with the target EAS to trigger the target EAS to perform context transfer, or updating the user plane path.
  • the ACR request can also be called an application relocation request.
  • the ACR request message can carry information about the terminal device, such as the terminal device identifier, the terminal device location, the AC identifier, etc.
  • the ACR request message can also carry the address of the source EAS (such as an IP address or a URL address), and the identifier of the current application (such as the domain name (fully qualified domain name, FQDN) or uniform resource locator (uniform resource locator, URL) of the application).
  • the target EES may obtain the address of the source EES and the address of the source EAS based on the ACR request message.
  • step 630 the target EES instructs the target EAS to request the application context from the source EAS, and the application context is transmitted between the source EAS and the target EAS.
  • the target EES may send a message to the target EAS to request migration of the context of the current application on the terminal device where the EEC is located. Accordingly, the target EAS may obtain information of the source EAS from the target EES, such as the address of the source EAS and information of the terminal device.
  • the target EAS may notify the source EAS to send the context of the current application, and accordingly, the target EAS receives the context of the current application.
  • the source EAS may transmit the context of the current application to the target EES through the source EES, and the target EES transfers the received application context to the target EAS.
  • step 640 the target EAS sends an ACR completion message to the target EES.
  • the target EAS After receiving the context of the current application of the terminal device, the target EAS determines that the application context is received successfully, that is, the context of the current application can be reconstructed in the target EAS to form an application context that can be used by the client of the current application of the terminal device.
  • the target EAS may send a message to the target EES indicating the completion of the ACT and indicating the results of the ACT.
  • the source EAS may also send a notification message of successful application context migration to the source EES.
  • step 650 after receiving the ACR completion message sent from the target EAS, the target EES sends an ACR completion message to the EEC, indicating that the ACT is completed.
  • the target EES can also trigger the update of the user plane path of the current application.
  • the target EES can trigger the SMF to insert a new user plane path for the current application of the terminal device, as well as insert an uplink classifier (UL CL) or a branch anchor point (BP). This step can also be triggered by the target EAS.
  • UL CL uplink classifier
  • BP branch anchor point
  • the step of triggering the user plane path update of the current application can also be executed synchronously with the aforementioned step 630 or 640, for example, it can be executed after the target EES sends a message to the target EAS to request the migration of the application context, or after the ACT is completed. This application does not impose any restrictions on this.
  • step 620 to step 650 Regarding the specific method of executing step 620 to step 650, reference may be made to the prior art and will not be described in detail.
  • the terminal device when determining the target EES, can instruct the ECS to select an EES that supports the first ACR scenario, so that the target EES determined by the terminal device can support the first ACR scenario; the ECS can also send the ACR capability of the EES to the terminal device, so that the terminal device can select the target EES that supports the first ACR scenario, so that the terminal device can smoothly execute ACR through the target EES.
  • the terminal device can instruct the target EES to select an EAS that supports the first ACR scenario, so that the EAS determined by the terminal device can support the first ACR scenario; the target EES can also indicate the ACR capability of the EAS to the terminal device, and the terminal device selects the target EAS that supports the first ACR scenario, so that the EAS can complete the transmission of the application context as the target EAS.
  • the ACR process based on the target EES can be executed smoothly, and when the service of the current application is switched between EASs, the application context can be successfully migrated, which can ensure the continuity of the service of the current application.
  • the terminal device may execute method 300 when detecting an event requiring ACR.
  • events requiring ACR may include one or more of the following:
  • the location of the terminal device moves out of the service area of the currently connected EAS
  • the EEC receives a request to migrate the application context from the AC;
  • the terminal device detects that the quality of the current application in the currently connected EAS is low, for example, the connection quality with the currently connected EAS is not good, such as large delay or large packet loss rate;
  • EEC receives a message about a new session from SMF, or EEC receives a new IP prefix, etc.
  • the event that makes the source EAS unable to provide application services to the terminal device corresponds to the event that requires ACR.
  • the EEC may perform ACR through the method 300 when determining to perform ACR based on the first ACR scenario.
  • the currently connected EES may determine that the first ACR scene is the selected ACR scene, that is, when there is an ACR demand, ACR needs to be performed based on the first ACR scene.
  • the currently connected EES may send information to the EEC to indicate that ACR is performed based on the first ACR scene, or to indicate that an EES supporting the first ACR scene is selected, or to indicate that the ACR scene corresponding to the current application is the first ACR scene.
  • the first ACR scene is referred to as the ACR scene.
  • This information is the fourth information, and it should be understood that this cannot be a limitation on the present application.
  • the fourth information can be carried in an ACR scenario selection notification message sent by the EES to the EEC.
  • the EES currently connected to the terminal device can obtain information indicating the ACR capability of the terminal device (including the ACR capability of the EEC and the ACR capability of the AC) from the terminal device, and the EES can determine the ACR scene corresponding to the current application based on the ACR capability of AC, EEC, the EES currently connected to the terminal device, and the EAS currently connected to the terminal device (or the EAS selected by the terminal device). For example, the first ACR scene is determined as the ACR scene corresponding to the current application.
  • the EES currently connected to the terminal device can determine the first ACR scene as the selected ACR scene when the terminal device (including AC and EEC), the EAS currently connected to the terminal device (or the terminal selected) and the EES currently connected to the terminal device do not have a commonly supported ACR scene, and send the fourth information to the EEC. It is also possible that the EES currently connected to the terminal device can determine the first ACR scene as the selected ACR scene when the terminal device (including AC and EEC), the EAS currently connected to the terminal device (or the terminal selected) and the EES currently connected to the terminal device associated with the EAS have a commonly supported ACR scene, and send the fourth information to the EEC.
  • the EEC can determine to perform ACR based on the first ACR scenario through the fourth information from the EES.
  • the EES may also send information to the EEC to indicate that the current application has no corresponding ACR scenario, or indicates that the determined ACR scenario is empty, or indicates that the currently connected EES or the EAS associated with the EES cannot perform ACR.
  • this information is referred to as the third information. It should be understood that this cannot be a limitation of the present application.
  • the third information can be carried in an ACR scenario selection notification message or an EAS information provisioning response message sent by the EES to the EEC.
  • the EES currently connected to the terminal device can send third information to the EEC when the terminal device (including AC and EEC), the EAS currently connected to the terminal device (or selected by the terminal device), and the EES associated with the EAS do not have a commonly supported ACR scenario.
  • the EEC may determine that the current application has no corresponding ACR scene, and determine that the first ACR scene is the selected ACR scene, that is, ACR needs to be performed based on the first ACR scene when there is an ACR demand.
  • the EEC may receive information from the EES to which the terminal device is currently connected, obtain the ACR scenarios supported by the EES and the EAS to which the terminal device is currently connected (or selected by the terminal device), and the terminal device may also determine the ACR scenarios supported by the EEC and AC. The terminal device may determine the ACR scenario corresponding to the current application accordingly.
  • the EEC may determine that the first ACR scene is the ACR scene corresponding to the current application when the terminal device (including AC and EEC), the EAS currently connected to the terminal device (or selected by the terminal device), and the EES associated with the EAS do not have a commonly supported ACR scene.
  • the EEC may also determine that the first ACR scene is the ACR scene corresponding to the current application when the terminal device (including AC and EEC), the EAS currently connected to the terminal device (or selected by the terminal device), and the EES associated with the EAS do not have a commonly supported ACR scene.
  • FIG. 8 is a possible implementation of the application context migration method provided in an embodiment of the present application.
  • the EEC determines that the selected ACR scene is the first ACR scene
  • the ECS determines the EES that supports the first ACR scene
  • the target EES determines the EAS that supports the first ACR scene.
  • the implementation shown in FIG. 8 includes steps 801 to 814 .
  • Step 801 The target EAS sends an EAS registration request message to the target EES.
  • the EAS registration request message carries the EAS configuration information (including the ACR scenarios supported by the EAS).
  • Step 802 The target EES sends an EAS registration response message to the target EAS.
  • step 801 and step 802 The specific method of registering the target EAS with the target EES shown in step 801 and step 802 can be performed with reference to the method shown in (a) of FIG. 5 , and will not be described in detail here.
  • Step 803 The target EES sends an EES registration request message to the ECS.
  • the EES registration request message carries information indicating the ACR scenarios supported by the EES and the ACR scenarios supported by the EAS associated with the EES.
  • Step 804 The ECS sends an EES registration response message to the target EES.
  • the specific method of registering the target EES with the ECS shown in steps 803 to 804 can refer to the method shown in (b) of FIG. 5 above. Steps 801 to 804 are optional steps.
  • the source EAS can also be registered on the source EES, and the source EES can also be registered on the ECS.
  • Step 805 The source EES determines that the ACR scenario supported by the current application is empty.
  • the source EES can obtain the ACR scenarios supported by the terminal device, such as the ACR scenarios supported by AC and EEC, by connecting to the terminal device.
  • the source EES can determine that the ACR scenarios supported by the current application are empty when the terminal device, the source EES, and the source EAS do not have ACR scenarios supported in common.
  • Step 806 The source EES sends an ACR scheme selection notification message to the EEC.
  • the message may carry the AC ID and EAS ID of the current application and information indicating that the ACR scenarios supported by the current application are empty.
  • Step 807 The EEC determines that the selected ACR scene is the first ACR scene.
  • the EEC may determine that the current application has no available ACR scene, and the EEC may determine to use the first ACR scene as the ACR scene of the current application.
  • step 805 to step 807 are optional steps.
  • Step 808 EEC sends a service activation request message to ECS, which carries second information and can indicate at least one of the following: selecting an EES that supports the first ACR scenario, or, preferably an EES that supports the first ACR scenario, or, the source EES and/or source EAS cannot execute ACR, or, the current application has no corresponding ACR scenario.
  • the EEC may execute step 808 when an event requiring ACR is detected, for example, when the location of the terminal device moves out of the service area of the currently connected EAS.
  • step 808 can refer to the aforementioned step 410b, which will not be repeated here.
  • Step 809 the ECS determines one or more EESs that support the first ACR scenario.
  • step 809 can refer to the aforementioned step 420b, which will not be repeated here.
  • Step 810 The ECS sends a service activation response message to the EEC.
  • the EES information carried in the message indicates one or more EESs that are determined or identified by the ECS and support the first ACR scenario.
  • the EEC can select a target EES from them.
  • step 810 can refer to the aforementioned steps 430b and 440b, which will not be repeated here.
  • Step 811 the EEC sends an EAS discovery request message to the target EES, which carries sixth information, which can indicate at least one of the following: selecting an EAS that supports the first ACR scenario, or the source EES and/or source EAS cannot perform ACR, or the current application has no corresponding ACR scenario.
  • step 811 may refer to the aforementioned step 710b, which will not be repeated here.
  • Step 812 the target EES determines one or more EASs that support the first ACR scenario.
  • Step 813 The target EES sends an EAS discovery response message to the EEC.
  • the EAS information carried in the message indicates one or more EASs that support the first ACR scenario determined by the target EES.
  • the EEC can select the target EAS from them.
  • step 811 may refer to the aforementioned steps 730b and 740b, which will not be repeated here.
  • Step 814 the EEC transmits the application context of the current application from the source EAS to the target EAS through the target EES and the target EAS.
  • step 814 can refer to the aforementioned steps 620 to 650, which will not be repeated here.
  • the source EES can indicate to the EEC that the ACR scene of the current application is empty, and then the EEC can determine to perform ACR based on the first ACR scene.
  • the source EAS cannot provide application services for the terminal device, an EES that supports the first ACR scene can be selected as the target EES, and an EAS that supports the first ACR scene can be selected as the target EAS, and ACR can be performed through the target EES, thereby successfully completing the migration of the application context and ensuring the continuity of the application service.
  • FIG. 9 is another possible implementation of the application context migration method provided in an embodiment of the present application.
  • the source EES determines that the selected ACR scene is the first ACR scene
  • the ECS determines the EES that supports the first ACR scene
  • the target EES determines the EAS that supports the first ACR scene.
  • the implementation shown in FIG. 9 includes steps 901 to 913 .
  • Steps 901 to 904 are the same as the aforementioned steps 801 to 804 and will not be repeated here.
  • Step 905 The source EES determines that the selected ACR scene is the first ACR scene.
  • the source EES may determine the first ACR scene as the ACR scene corresponding to the current application.
  • the selected ACR scene is determined to be the first ACR scene.
  • Step 906 The source EES sends an ACR scheme selection notification message to the EEC.
  • the message carries information indicating the selection of the EES supporting the first ACR scenario.
  • Steps 907 to 913 are the same as the aforementioned steps 808 to 814 and will not be repeated here.
  • the step of determining that the selected ACR scene is the first ACR scene is performed by the source EES
  • the step of determining the EES that supports the first ACR scene is performed by the ECS
  • the step of determining the EAS that supports the first ACR scene is performed by the target EES, so that the terminal device does not need to perform these steps, which can reduce the burden on the terminal device.
  • FIG. 10 is another possible implementation of the application context migration method provided in the present application.
  • the EEC determines that the selected ACR scene is the first ACR scene, the EEC determines the target EES that supports the first ACR scene, and the EEC determines the target EAS that supports the first ACR scene.
  • the implementation shown in FIG. 10 includes steps 1001 to 1014 .
  • Steps 1001 to 1007 are the same as the aforementioned steps 801 to 807 and will not be repeated here.
  • Step 1008 EEC sends a service activation request message to ECS.
  • Step 1009 in response to the service activation request, the ECS sends a service activation response message to the EEC.
  • the EES information carried in the message indicates one or more EESs.
  • the message also carries information indicating the ACR scenarios supported by the one or more EESs.
  • the information carried in the message also indicates the ACR scenarios supported by the EAS associated with the EES.
  • Step 1010 The EEC determines an EES supporting the first ACR scenario as a target EES from one or more EESs based on the information carried in the service activation response message.
  • steps 1008 to 1010 please refer to the aforementioned steps 410 to 440 , which will not be repeated here.
  • Step 1011 the EEC sends an EAS discovery request message to the target EES.
  • Step 1012 In response to the EAS discovery request message, the target EES sends an EAS discovery response message to the EEC.
  • the EAS information carried in the message indicates one or more EASs, and the message also carries information indicating the ACR scenarios supported by the one or more EASs.
  • Step 1013 The EEC determines an EAS supporting the first ACR scenario from one or more EASs as a target EAS based on the information carried in the EAS discovery response message.
  • steps 1011 to 1013 can be found in the aforementioned steps 710 to 740, which will not be repeated here.
  • Step 1014 the EEC transmits the application context of the current application from the source EAS to the target EAS through the target EES and the target EAS.
  • step 1014 can refer to the aforementioned steps 620 to 650, which will not be repeated here.
  • the step of determining that the selected ACR scene is the first ACR scene, the step of determining the target EES that supports the first ACR scene, and the step of determining the EAS that supports the first ACR scene are all performed by the EEC, so that the source EES, ECS, and target EES do not need to perform these steps, which can reduce the burden on the source EES, ECS, and target EES.
  • FIG. 11 is another possible implementation of the application context migration method provided in the present application.
  • the source EES determines that the selected ACR scene is the first ACR scene, the EES determines the target EES that supports the first ACR scene, and the EEC determines the target EAS that supports the first ACR scene.
  • the implementation method shown in FIG. 11 includes steps 1101 to 1113 .
  • steps 1101 to 1106 are the same as the aforementioned steps 901 to 906, and steps 1107 to 1113 are the same as the aforementioned steps 1008 to 1014, which will not be repeated here.
  • the effect achieved by the implementation shown in FIG11 is similar to the effect achieved by the implementation shown in FIG8 .
  • the step of determining that the selected ACR scene is the first ACR scene can be performed by the source EES or by the EEC.
  • the step of determining the EES that supports the first ACR scene can be performed by the EEC or by the ECS.
  • the step of determining the EAS that supports the first ACR scene can be performed by the EEC or by the target EES.
  • the entity that specifically performs the above steps can be determined based on the load capacity of each entity, so that the system load is balanced to smoothly realize the transmission of the application context.
  • FIGS. 8 to 11 are only examples of the methods provided in the embodiments of the present application and cannot constitute an embodiment of the present application.
  • the limitations of the application are that any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in this application, which should be included in the protection scope of this application.
  • an EEC context may also be stored on the EES.
  • the EEC context may be acquired, generated or created by the EES when the EEC registers with the EES, or it may be pre-configured, or it may be acquired by the EES from another EES through the EEC context transmission process (for example, the target EES may acquire the EEC context from the source EES).
  • the present application does not limit this.
  • the EEC registration process is described below in conjunction with FIG. 12 .
  • the EEC registration process may include steps 1210 to 1240 .
  • step 1210 the EEC sends an EEC registration request message to the EES.
  • the EEC registration request includes security credentials received after successful authorization of the edge computing service, and may also include a recommended expiration time.
  • the request may also include information indicating to the EES how the EEC expects to use the services of the EES. If the EEC is moved to this EES from the authority of another EES (taking the source EES as an example), the request from the EEC may include the identity and endpoint of the source EES, as well as the EEC context ID provided by the source EES to maintain the EEC context and authorize the relocation of the EEC context.
  • step 1220 after receiving the registration request from the EEC, the EES verifies the registration request and verifies the security credentials.
  • EES can determine whether the requirements indicated in the AC profile can be met.
  • step 1230 after successfully validating the request, if the received EEC registration request contains the EEC context ID, the EES ID of the source EES, and the EES endpoint, the EES can retrieve the context of the EEC from the source EES. Otherwise, this step is skipped.
  • step 1240 the EES sends a registration response message to the EEC.
  • the EES sends a registration success response, which includes the registration ID and may include a newly assigned EEC context ID.
  • the EEC stores the new EEC context ID and uses it when registering with another EES.
  • the EES can also provide an expiration time to indicate to the EEC when the registration automatically expires.
  • the EEC should send a registration update request before the expiration. If a registration update request is not received before the expiration time, the EES should treat the EEC as implicitly deregistered.
  • EES sends a registration failure response and gives the reason for the failure.
  • the source EES and the target EES can also transmit the EEC context.
  • EEC context The transmission of EEC context can be performed through the EEC context pull (EEC context push) process or the EEC context push (EEC context pull) process.
  • the EEC context transmission process is schematically illustrated below in conjunction with FIG. 13 (a) and FIG. 13 (b).
  • FIG 13 (a) is a schematic diagram of an EEC context pulling process provided by an embodiment of the present application.
  • the EEC context pulling process may include steps 1310a to 1330a.
  • the target EES sends an EEC context pull request message to the source EES to request the EEC context from the source EES.
  • the request message may include an EEC context ID.
  • step 1320a after receiving the EEC context pull request message from the target EES, the source EES verifies the request and verifies the security credentials of the requester.
  • the source EES uses the EEC context ID in the request message to identify and authorize the EEC context to be relocated.
  • step 1330a the source EES sends an EEC context pull response message to the target EES.
  • the target EES receives the EEC context from the source EES and stores the EEC context.
  • FIG13( b ) is a schematic diagram of an EEC context push process provided by an embodiment of the present application.
  • the EEC context push process may include steps 1310 b to 1330 b.
  • step 1310b the source EES decides to forward the EEC context to the target EES for relocation.
  • the source EES determines the target EES and EEC context to be forwarded.
  • step 1320b the source EES sends an EEC context push request message to the target EES, where the request message includes the determined EEC context.
  • step 1330b after receiving the request from the source EES, the target EES verifies the request and verifies the security credentials.
  • the target EES uses the provided EEC context ID to authorize the storage and management of the EEC context. Afterwards, the target EES sends an EEC context push response message to the source EES, indicating that the EEC context has been successfully received.
  • the source EES and the target EES may transfer the EEC context.
  • the EEC context pull process shown in (a) of FIG. 13 or the EEC context push process shown in (b) of FIG. 13 may be performed while executing the aforementioned step 630. It should be understood that the present application does not limit the specific time for performing the EEC context transfer process, and the EEC context transfer between the source EES and the target EES may also be performed before the aforementioned step 630 or after the aforementioned step 630.
  • the source EES and the target EES need to have the EEC context transfer capability, that is, the EEC context transfer can be performed through the corresponding process only when the source EES and the target EES have a commonly supported EEC context transfer process.
  • the EEC context transfer can be performed between the source EES and the target EES through the process shown in (b) of Figure 13; when the source EES supports the EEC context push process but the target EES does not support the EEC context push process, the EEC context transfer cannot be performed between the source EES and the target EES through the EEC context push process.
  • the target EES has (or supports) an EEC context transmission capability corresponding to the source EES, or the target EES and the source EEC have (or support) corresponding EEC context transmission capabilities, which means that the same EEC context transmission process exists in the EEC context transmission process supported by the target EES and the context transmission process supported by the source EES.
  • the target EES and the source EES both support the EEC context push process (the target EES and the source EES support the EEC context push API), or the target EES and the source EES both support the EEC context pull process (the target EES and the source EES support the EEC context push API).
  • Both the target EES and the source EES support the EEC context push process, including the source EES supporting the sending of an EEC context push request message and the target EES supporting the sending of an EEC context push response message.
  • Both the target EES and the source EES support the EEC context pull process, including the target EES supporting the sending of the EEC context pull request message and the source EES supporting the sending of the EEC context pull response message.
  • the EEC context transmission cannot be performed in the ACR process, which may affect the continuity of the service.
  • an embodiment of the present application also provides an EEC context transmission method.
  • a target EES that supports the corresponding EEC context transmission process with the source EES is selected, so that EEC context transmission can be implemented based on the corresponding EEC context transmission process during the ACR process; when the source EES does not support EEC context transmission, or the target EES does not have the EEC context transmission capability corresponding to the source EES, the EEC re-registers with the target EES after the ACR is completed.
  • the target EES can obtain the context of the EEC, thereby providing the EEC with information that can be used in edge computing services.
  • the target EES can then provide subsequent edge computing services to the terminal device, thereby ensuring business continuity.
  • FIG14 is a schematic flow chart of the EEC context transmission method provided in an embodiment of the present application.
  • the method shown in FIG14 illustrates the method provided in an embodiment of the present application from the perspective of a terminal device.
  • the method can be executed by a terminal device, or by a component (such as a circuit, a chip, a chip system, etc.) in the terminal device, and can be implemented by software and/or hardware.
  • the present application does not limit this. The following description is given by taking the EEC configured in the terminal device as an example.
  • the EEC context transmission method 1400 may include step 1410 and step 1420 .
  • step 1410 the EEC context transmission capability of the source EES is obtained.
  • the EEC may obtain the context transmission capability of the source EES from the source EES. For example, when the source EES is connected to the EEC, the source EES may carry the API information supported by the source EES in the ACR scheme selection notification message sent to the EEC, indicating the EEC context transmission capability of the source EES.
  • it may indicate whether the source EES supports EEC context transmission, or whether the source EES supports the EEC context pull process, or whether the source EES supports the EEC context push process.
  • a target EES is determined, the target EES being determined based on the EEC context transfer capability of the source EES.
  • the source EES may send information to the EEC to instruct the EEC that when performing ACR, it is necessary to select a target EES that supports the corresponding EEC context transmission capability. For example, if the source EES supports the EEC context pull process, the source EES may indicate to the EEC that when performing ACR, it is necessary to select a target EES that supports the EEC context pull process.
  • the EEC may determine the need to select a target EES that supports the corresponding EEC context transmission capability based on the information from the source EES.
  • the EEC can select a target EES that supports the same EEC context transfer process based on the EEC context transfer process supported by the source EES through the ECS.
  • the source EES can send information to the EEC to instruct the EEC to select a target EES that does not support EEC context transfer when performing ACR.
  • the source EES can also indicate to the EEC that it needs to re-register with the target EES after performing ACR.
  • the EEC may determine to select a target EES that does not support EEC context transfer based on information from the source EES.
  • the EEC may also determine that it needs to re-register with the target EES after the ACR.
  • the EEC can select a target EES through the ECS, and the target EES does not have to support EEC context transmission.
  • the target EES can be determined through the service provisioning process or the EES discovery process.
  • the method of selecting a target EES may be as shown in (a) of FIG. 15 or (b) of FIG. 15 .
  • the EEC selects a target EES based on the EEC context transfer process supported by the source EES.
  • the method 1500 a may include steps 1510 a to 1540 a .
  • the EEC may send a service activation request message to the ECS.
  • step 1510a can refer to the aforementioned step 410a or the aforementioned step 410b.
  • the EEC may also send first request information to the EES, where the first request information is used to indicate at least one of the following: requesting to obtain the EEC context transmission capability of the EES, or the source EES supports EEC context transmission.
  • the EEC determines that ACR needs to be performed based on the first ACR scenario.
  • the EEC can send a first request message to the ECS to request the ECS to send the API capabilities supported by the EES, or to request the ECS to send the EEC context transmission capabilities supported by the EES, or to request the ECS to send whether the EES supports the EEC context pull process, or to request the ECS to send whether the EES supports the EEC context push process.
  • the ECS processes the service provisioning request and identifies one or more EESs.
  • step 1520a may refer to the aforementioned step 420a, or may refer to the aforementioned step 420b.
  • the one or more EESs identified by the ECS may be EESs that support the first ACR scenario.
  • the ECS sends a service activation response message to the EEC, as well as information indicating the EEC context transmission capability of the EES, such as the API capability supported by the EES, or whether the EES supports EEC context transmission, or the EEC context transmission process supported by the EES, or whether the EES supports the EEC context pull process, or whether the EES supports the EEC context push process.
  • This information can be carried in the service activation request response message, for example.
  • ECS can obtain information indicating the EEC context transmission capability of EES, which can be obtained by ECS when EES registers with ECS, or obtained by ECS through the gateway system, or pre-configured.
  • EES can send API information supported by EES to ECS, for example, indicating the EEC context transmission capability of EES. This information can be carried in the EES registration request message.
  • step 1530a can refer to the aforementioned step 430a, and can also refer to the aforementioned step 430b.
  • the ECS may send all information of all EESs registered or configured on the ECS to the EEC.
  • the aforementioned step 1520a is optional.
  • step 1540a the EEC determines a target EES from one or more EESs that has an EEC context transfer capability corresponding to the source EES.
  • the information received by the EEC may indicate the EEC context transfer capabilities of the EES.
  • the EEC can select an EES that supports the corresponding EEC context transfer process as the target EES. For example, if the source EES only supports the EEC context pull process, the target EES needs to support the EEC context pull process; if the source EES only supports the EEC context push process, the target EES needs to support the EEC context push process; if If the source EES supports both the EEC context pull process and the EEC context push process, the target EES may only support the EEC context pull process or only support the EEC context push process.
  • the EEC may not consider the EEC context transmission capability of the EES when selecting the EES.
  • the target EES selected by the EEC may have a different EEC context transmission capability from the source EES, or the target EES selected by the EEC may not have the EEC context transmission capability.
  • the EEC may determine that it needs to re-register with the target EES after the ACR.
  • FIG15 is a schematic diagram of another method for determining the target EES provided in an embodiment of the present application.
  • Method 1500 b in method 1500 b , the ECS selects an EES supporting the corresponding EEC context transmission capability based on the EEC context transmission capability supported by the source EES.
  • Method 1500 b may include steps 1510 b to 1540 b .
  • step 1510b the EEC sends a service activation request message to the ECS.
  • the EEC may send information to the ECS indicating the EEC context transmission capability of the source EES.
  • the information may be carried in a service activation request message, for example.
  • the EEC can send information to the ECS to indicate that the source EES supports the EEC context pull process; if the source EES supports the EEC context push process, the EEC can send information to the ECS to indicate that the source EES supports the EEC context push process.
  • the EEC may also send information to the ECS, indicating at least one of the following: the need to select an EES with EEC context transmission capability, or the need to select an EES with EEC context transmission capability corresponding to the source EES, or the preference is to select an EES with EEC context transmission capability corresponding to the source EES.
  • the EEC can send information to the ECS to indicate that an EES that supports the EEC context pull process needs to be selected. If the source EES only supports the EEC context push process, the EEC can send information to the ECS to indicate that an EES that supports the EEC context push process needs to be selected; if the source EES supports both the EEC context pull process and the EEC context push process, the EEC can send information to the ECS to indicate that an EES that supports the EEC context pull process or an EES that only supports the EEC context push process can be selected.
  • the specific implementation of the EEC sending the service activation request message to the ECS may refer to the aforementioned step 410a or the aforementioned step 410b.
  • step 1520b the ECS processes the service provisioning request and selects an EES having the same EEC context transfer capability as the source EES.
  • Step 1520b may be performed with reference to the aforementioned step 420a or 420b.
  • the ECS may select an EES that supports an EEC context transfer process corresponding to the source EES.
  • ECS selects an EES that supports the EEC context pull process. If the information source EES from EEC only supports the EEC context push process, ECS selects an EES that supports the EEC context push process; if the information source EES from EEC supports both the EEC context pull process and the EEC context push process, ECS can select an EES that supports the EEC context pull process or an EES that only supports the EEC context push process.
  • an EES with an EEC context transmission capability corresponding to that supported by the source EES may be selected based on the EEC context transmission capability supported by the one or more EES.
  • a condition is added, namely, the selected EES needs to support an EEC context transmission capability corresponding to that supported by the source EES. It should be understood that the present application does not limit the order of selection.
  • the ECS may not consider the EEC context transmission capability supported by the EES when selecting the EES.
  • step 1530b the ECS sends a service activation response message to the EEC.
  • the ECS determines one or more EESs that have EEC context transfer capabilities corresponding to the source EES.
  • the ECS may send information to the EEC indicating the one or more EESs, and the information may be carried in a service activation response message.
  • the ECS may send information to the EEC, indicating that it is not necessary to re-register with the target EES after the ACR. This information may be carried in a service activation response message.
  • no EES supports the corresponding EEC context transfer process with the source EES, or no EES has the EEC context transfer capability, or the information from the EEC indicates that the source EES does not have the EEC context transfer capability.
  • the ECS may send information to the EEC indicating that it is necessary to re-register with the target EES after the ACR. This information may be carried in a service activation response message.
  • the specific implementation method of step 1530b may refer to the aforementioned steps 430a or 430b.
  • step 1540b the EEC determines a target EES from one or more EESs indicated by the ECS.
  • the EEC may determine that it needs to re-register with the target EES after the ACR.
  • step 1540b you can refer to the aforementioned step 440a or 440b and will not repeat it here.
  • step 1540b is an optional step.
  • (a) in Figure 15 and (b) in Figure 15 provide a method for determining the target EES in step 1420.
  • the step of selecting an EES from the EES that has the same EEC context transmission capability as the source EES can be executed by the ECS, so that the terminal device does not have to perform screening, which can reduce the burden on the terminal device; this step can also be executed by the EEC, so that the ECS does not have to perform screening based on the EEC context transmission capability of the EES, which can reduce the burden on the ECS.
  • a target EES having the same EEC context transmission capability as the source EES can be determined, and during the ACR process, the source EES can complete the EEC context transmission with the target EES.
  • the EEC can obtain an instruction to re-register with the target EES, and the EEC can re-register with the target EES based on the instruction after the ACR is completed, so that the target EES obtains the EEC context.
  • the method 1400 may further include: determining whether to perform EEC context transfer.
  • FIG. 16( a ) and FIG. 16( b ) show two methods of determining whether to perform EEC context transfer.
  • Method 1600a the target EES determines whether the EEC context transfer can be performed.
  • Method 1600a includes steps 1610a to 1630a.
  • the EEC may send information to the target EES to indicate the EEC context transmission capability of the source EES. For example, at least one of the following may be indicated: the API capability supported by the source EES, or the source EES supports the EEC context transmission process, or whether the source EES supports the EEC context pull process, or whether the source EES supports the EEC context push process. It should be understood that this application does not limit this.
  • the target EES may determine whether the EEC context transfer can be performed based on the information.
  • the target EES and the source EES support the corresponding EEC context transfer process
  • the source EES and the target EES both support the EEC context pull process and/or the source EES and the target EES both support the EEC context push process. It can be determined that the EEC context transfer can be performed with the source EES.
  • the target EES can also determine that the EEC does not need to re-register with the target EES after ACR.
  • the target EES may also determine that the EEC needs to re-register with the target EES after ACR.
  • step 1630a the target EES sends an indication message to the EEC, indicating whether the EEC needs to re-register with the target EES after the ACR.
  • the target EES may send an indication message to the EEC, indicating that it is not necessary to re-register with the target EES after the ACR.
  • the target EES can send an indication message to the EEC to indicate that the ACR You need to re-register with the target EES afterwards.
  • the EEC and the target EES may perform method 1600a when performing the EAS discovery process in the aforementioned step 610.
  • the information sent by the EEC to the target EES may be carried in an EAS discovery request message, and the indication information in step 1630a may be carried in an EAS discovery response message.
  • Method 1600b the EEC determines whether the EEC context transfer can be performed.
  • Method 1600b includes steps 1610b to 1630b.
  • the EEC sends a request message to the target EES, where the request message may indicate at least one of the following: a request to obtain the EEC context transmission capability of the target EES, or the source EES supports EEC context transmission.
  • the target EES in response to the request from the EEC, sends information to the EEC to indicate the EEC context transmission capability of the target EES. For example, when the target EES supports the EEC context pull process, it can be indicated that the target EES supports the EEC context pull process; when the target EES supports the EEC context push process, it can be indicated that the target EES supports the EEC context push process; when the target EES does not support the EEC context transmission capability, it can be indicated that the target EES does not support the EEC context transmission capability; when the target EES has the EEC context transmission capability, it can be indicated that the target EES has the EEC context transmission capability.
  • step 1630b the EEC determines whether the EEC context transfer capability can be executed based on the EEC context transfer capability of the target EES.
  • the target EES and the source EES support corresponding EEC context transfer capabilities, it can be determined that the target EES can perform EEC context transfer with the source EES.
  • the EEC can determine that it does not need to re-register with the target EES after the ACR.
  • the EEC can determine that the target EES cannot perform EEC context transmission with the source EES.
  • the EEC can also determine that it needs to re-register with the target EES after ACR.
  • the EEC and the target EES may perform method 1600b when performing the EAS discovery process in the aforementioned step 610.
  • the information sent by the EEC to the target EES may be carried in an EAS discovery request message
  • the information sent by the target EES to the EEC may be carried in an EAS discovery response message.
  • the aforementioned step 1420 is optional, that is, the target EES can be determined by the method of the aforementioned step 1420, or by the method in the aforementioned step 310, or by a method in the prior art.
  • the terminal device may determine the target EES and perform ACR through the method 1400.
  • the source EES and the target EES may perform EEC context transmission, or the EEC may re-register with the target EES after the ACR.
  • the source EES and the target EES support the same EEC context transmission capability, and the EEC context transmission can be performed between the source EES and the target EES during the ACR process, for example, when executing the aforementioned step 630.
  • the source EES and the target EES jointly support the EEC context push process, and the EEC context can be transferred between the source EES and the target EES through the process shown in (b) of Figure 13.
  • the source EES and the target EES jointly support the EEC context pull process, and the EEC context can be transferred between the source EES and the target EES through the process shown in (a) of Figure 13.
  • the source EES and/or the target EES do not support EEC context transmission, or the source EES and the target EES do not have corresponding EEC context transmission capabilities.
  • the EEC can register with the target EES after the ACR.
  • the method for the EEC to register with the target EES can refer to the method in Figure 12 above, which will not be repeated here.
  • the EEC when determining the target EES, can instruct the ECS to select an EES with an EEC context transmission capability corresponding to the source EES support, so that the target EES determined by the EEC can transmit the EEC context with the source EES; the ECS can also indicate the EEC context transmission capability of the EES to the EEC, so that the EEC can select a target EES with an EEC context transmission capability corresponding to the source EES support, so that during the ACR process, the source EES and the target EES can smoothly perform EEC context transmission.
  • the EEC can re-register with the target EES based on the instruction, so that the target EES can obtain the context of the EEC and can provide the EEC with information that can be used in edge computing services. Then the target EES It can provide subsequent edge computing services for terminal devices and ensure business continuity.
  • FIG17 is a possible implementation of the EEC context migration method provided by an embodiment of the present application.
  • the step of determining an EES that supports the EEC context transmission capability corresponding to the source EES can be performed by the ECS, and the step of determining whether the source EES and the target EES have corresponding EEC context transmission capabilities can be performed by the target EES.
  • the method includes steps 1701 to 1710.
  • Step 1701 The target EES sends an EES registration request message to the ECS.
  • the EES registration request message carries information indicating the EEC context transmission capability of the EES.
  • Step 1702 The ECS sends an EES registration response message to the target EES.
  • step 1701 and step 1702 The specific method of registering the target EES with the ECS shown in step 1701 and step 1702 can be executed with reference to the method shown in (b) of the aforementioned FIG. 5 , and will not be described in detail here.
  • Step 1701 and step 1702 are optional steps.
  • the source EES may also be registered with the ECS. Based on the registration process, the ECS may determine the EEC context transfer capability of the source EES and/or the target EES.
  • Step 1703 The source EES sends an ACR scheme selection notification message to the EEC, which may carry the currently applied AC ID, EAS ID, and information indicating the EEC context transmission capability of the source EES.
  • the EEC or source EES may determine the ACR scenario.
  • step 1703 The specific method for executing step 1703 can refer to the aforementioned step 1410, which will not be repeated here.
  • Step 1704 the EEC sends a service activation request message to the ECS, and the message carries information that can indicate at least one of the following: the need to select an EES with EEC context transmission capability, or the need to select an EES with an EEC context transmission capability corresponding to the source EES, preferably an EES with an EEC context transmission capability corresponding to the source EES.
  • Step 1705 the ECS determines an EES that supports the EEC context transfer capability corresponding to the source EES.
  • step 1705 refers to the aforementioned step 1520b, which will not be repeated here.
  • Step 1706 the ECS sends a service activation response message to the EEC, which may carry information indicating one or more EESs that have EEC context transmission capabilities corresponding to the source EES, from which the EEC may determine the target EES.
  • the message may carry information indicating the need to re-register with the target EES.
  • step 1706 can refer to the aforementioned step 1530b, which will not be repeated here.
  • Step 1707 the EEC sends information to the target EES to indicate the EEC context transmission capability of the source EES.
  • step 1707 can refer to the aforementioned step 1610a, which will not be repeated here.
  • Step 1708 the target EES determines whether the source EES and the target EES have corresponding EEC context transmission capabilities.
  • step 1708 can refer to the aforementioned step 1620a, which will not be repeated here.
  • Step 1709 The target EES sends a registration instruction message to the EEC, indicating whether it is necessary to re-register with the target EES.
  • step 1708 can refer to the aforementioned step 1630a, which will not be repeated here.
  • step 1710 the target EES transfers the EEC context with the source EES, or the EEC registers with the target EES.
  • the target EES and the source EES support corresponding EEC context transmission capabilities
  • the target EES can perform EEC context transmission with the source EES through a commonly supported EEC context transmission process.
  • the specific implementation method can be carried out with reference to (a) in Figure 13 or (b) in Figure 13, which will not be repeated here.
  • the EEC can re-register with the target EES so that the target EES can obtain the EEC context.
  • the specific implementation method can be carried out with reference to Figure 12 and will not be repeated here.
  • steps 1707 to 1709 are optional steps.
  • steps 1704 to 1706 are optional steps, that is, other methods can be used to determine the target EES, such as determining the target EES based on the method in the aforementioned step 310, or determining the target EES based on the prior art.
  • step 1703 if the information sent by the source EES to the EEC indicates that the source EES does not support EEC context transmission, If the EEC is input, the EEC may determine that it needs to re-register with the target EES. In this case, steps 1704 to 1709 are optional steps. In step 1710, the EEC registers with the target EES, and the target EES obtains the EEC context.
  • the target EES can obtain the EEC context, thereby providing the EEC with information that can be used in edge computing services.
  • the target EES can then provide subsequent edge computing services to the terminal device, thereby ensuring business continuity.
  • FIG18 is another possible implementation of the application context migration method provided by an embodiment of the present application.
  • the step of determining a target EES that supports the EEC context transmission capability corresponding to the source EES can be performed by the EEC, and the step of determining whether the source EES and the target EES have corresponding EEC context transmission capabilities can be performed by the target EEC.
  • the method includes steps 1801 to 1810.
  • step 1801 to step 1803 is the same as the implementation method of the aforementioned step 1701 to step 1703, which will not be repeated here.
  • Step 1804 the EEC sends a service activation request message to the ECS, the message carrying information indicating at least one of the following: requesting to obtain the EEC context transmission capability of the EES, or the source EES supporting EEC context transmission.
  • step 1804 can refer to the aforementioned step 1510a, which will not be repeated here.
  • Step 1805 the ECS sends a service activation response message to the EEC, and the message may carry information indicating one or more EESs and the EEC context transmission capabilities of the one or more EESs.
  • step 1805 can refer to the aforementioned step 1520a and the aforementioned step 1530a, which will not be repeated here.
  • Step 1806 The EEC determines a target EES that supports the EEC context transmission capability corresponding to the source EES.
  • the EEC can select an EES that supports the EEC context transmission capability corresponding to the source EES from one or more EESs indicated by the ECS based on the EEC context transmission capability of the EES, and use it as the target EES.
  • step 1805 can refer to the aforementioned step 1540a, which will not be repeated here.
  • Step 1807 the EEC sends a request message to the target EES, indicating at least one of the following: requesting to obtain the EEC context transmission capability of the target EES, or the source EES supports EEC context transmission.
  • Step 1808 The target EES sends information to the EES, indicating the EEC context transmission capability of the target EES.
  • step 1808 can refer to the aforementioned step 1620b, which will not be repeated here.
  • Step 1809 the EEC determines whether the source EES and the target EES have corresponding EEC context transmission capabilities.
  • step 1809 can refer to the aforementioned step 1630b, which will not be repeated here.
  • Step 1810 the target EES transfers the EEC context with the source EES, or the EEC registers with the target EES.
  • the target EES and the source EES support corresponding EEC context transmission capabilities
  • the target EES can perform EEC context transmission with the source EES through a commonly supported EEC context transmission process.
  • the specific implementation method can be carried out with reference to (a) in Figure 13 or (b) in Figure 13, which will not be repeated here.
  • the EEC can re-register with the target EES so that the target EES can obtain the EEC context.
  • the specific implementation method can be carried out with reference to Figure 12 and will not be repeated here.
  • steps 1807 to 1809 are optional steps.
  • steps 1804 to 1806 are optional steps, that is, other methods can be used to determine the target EES, such as determining the target EES based on the method in the aforementioned step 310, or determining the target EES based on the prior art.
  • step 1803 if the information sent by the source EES to the EEC indicates that the source EES does not support EEC context transmission, the EEC may determine that it needs to re-register with the target EES. At this time, steps 1804 to 1809 are optional steps. In step 1810, the EEC registers with the target EES, and the target EES obtains the EEC context.
  • the target EES can obtain the EEC context, thereby providing the EEC with information that can be used in edge computing services.
  • the target EES can then provide subsequent edge computing services to the terminal device, thereby ensuring business continuity.
  • steps in FIG. 17 and FIG. 18 can be implemented in combination. For example, after executing steps 1704 to 1706, steps 1807 to 1809 can be executed; or, after executing steps 1804 to 1806, steps 1707 to 1709 can be executed. This application does not limit this.
  • EEC context transmission method provided in the embodiment of the present application can be implemented in combination with the ACR method described in the aforementioned Figures 3 to 11.
  • the specific steps can be referred to the description in the aforementioned Figures 3 to 11, and the present application does not limit this.
  • the communication device may include a processing unit 1910 and a transceiver unit 1920.
  • the communication device 1900 may correspond to the terminal device (including EEC or AC) in the above method embodiment, for example, it may be a terminal device, or a component configured in the terminal device (such as a chip, a chip system, a processor, etc.), or it may also be a logic module or software that can realize all or part of the functions of the terminal device.
  • the terminal device including EEC or AC
  • the communication device 1900 may correspond to the terminal device (including EEC or AC) in the above method embodiment, for example, it may be a terminal device, or a component configured in the terminal device (such as a chip, a chip system, a processor, etc.), or it may also be a logic module or software that can realize all or part of the functions of the terminal device.
  • This embodiment of the application is not limited to this.
  • the device 1900 When the device 1900 corresponds to a terminal device, it can be used to execute the steps performed by the terminal device in the method shown in Figures 3 to 18 above, such as the steps performed by the EEC.
  • the communication device 1900 may include a unit for executing the method performed by the terminal device (including the EEC) in the method shown in Figures 3 to 18 above.
  • each unit in the communication device 1900 and the above-mentioned other operations and/or functions are respectively for implementing the corresponding processes in the methods shown in Figures 3 to 18.
  • the processing unit 1910 is used to determine a target EES, where the target EES is an EES that supports a first ACR scenario, where the first ACR scenario is a scenario where the target EES performs ACR.
  • the transceiver unit 1920 is used to request the target EES to perform ACR.
  • the transceiver unit 1920 is further configured to receive EES information from the ECS, where the EES information indicates at least one EES.
  • the processing unit 1910 is specifically configured to determine a target EES according to the EES information.
  • the transceiver unit 1920 is further used to receive first information from the ECS, where the first information indicates the ACR capability of the at least one EES.
  • the at least one EES supports a first ACR scenario.
  • the transceiver unit 1920 is also used to send second information to the ECS, where the second information is used to indicate at least one of the following: selecting a target EES that supports the first ACR scenario, or the currently connected EES or the currently connected application instance EAS cannot execute ACR, or the current application has no corresponding ACR scenario, or requesting to obtain the ACR capability of the EES.
  • the processing unit 1910 is further used to determine to perform ACR based on the first ACR scenario when the current application has no corresponding ACR scenario, or when the currently connected EES or the currently connected EAS cannot perform ACR.
  • the transceiver unit 1920 is further configured to receive third information from the currently connected EES, where the third information indicates that the current application has no corresponding ACR scenario, or indicates that the currently connected EES or the currently connected EAS cannot perform ACR.
  • the transceiver unit 1920 is further used to receive fourth information from the currently connected EES, where the fourth information is used to indicate the selection of a target EES that supports the first ACR scene, or to indicate that the first ACR scene is the ACR scene corresponding to the current application.
  • the transceiver unit 1920 is further configured to receive EAS information from a target EES, where the EAS information indicates at least one EAS.
  • the processing unit 1910 is further configured to determine a target EAS according to the EAS information.
  • the transceiver unit 1920 is further configured to receive fifth information from the target EES, where the fifth information indicates the ACR capability of the at least one EAS.
  • the at least one EAS supports the first ACR scenario.
  • the transceiver unit 1920 is also used to send sixth information to the target EES, and the sixth information is used to indicate at least one of the following: selecting a target EAS that supports the first ACR scenario, or the source EES or source EAS cannot perform ACR, or the current application has no corresponding ACR scene, or requesting to obtain the ACR capability of the EAS.
  • the transceiver unit 1920 in the communication device 1900 can be implemented by a communication interface, for example, it can correspond to the communication interface 2030 in the communication device 2000 shown in Figure 20.
  • the processing unit 1910 in the communication device 1900 can be implemented by at least one processor, for example, it can correspond to the processor 2010 in the communication device 2000 shown in Figure 20.
  • the communication device 1900 may correspond to the ECS in the foregoing method embodiment, for example, it may be an ECS, or a component configured in the ECS (such as a chip, a chip system, a processor, etc.), or it may also be a logic module or software capable of implementing all or part of the ECS functions. This embodiment of the application is not limited to this.
  • the communication device 1900 may include a unit for executing the method executed by the ECS in the methods shown in Figures 3 to 18 above. Furthermore, each unit in the communication device 1900 and the above-mentioned other operations and/or functions are respectively for implementing the corresponding processes in the methods shown in Figures 3 to 18.
  • the transceiver unit 1920 is used to send EES information to the terminal device, where the EES information indicates at least one EES.
  • the transceiver unit 1920 is also used to send first information to the terminal device, where the first information indicates the ACR capability of the at least one EES.
  • the transceiver unit 1920 is further used to receive second information from the terminal device, where the second information is used to indicate a request to obtain the ACR capability of the EES.
  • the processing unit 1910 is configured to determine at least one EES supporting a first ACR scenario, where the first ACR scenario is a scenario where ACR is performed by the target EES.
  • the transceiver unit 1920 is configured to send EES information to the terminal device, where the EES information indicates the at least one EES.
  • the transceiver unit 1920 is also used to receive second information from the terminal device, and the second information is used to indicate at least one of the following: selecting a target EES that supports the target ACR scene, or the currently connected EES or the currently connected EAS cannot perform ACR, or the current application has no corresponding ACR scene.
  • the transceiver unit 1920 in the communication device 1900 can be implemented by a communication interface, for example, it can correspond to the communication interface 2030 in the communication device 2000 shown in Figure 20.
  • the processing unit 1910 in the communication device 1900 can be implemented by at least one processor, for example, it can correspond to the processor 2010 in the communication device 2000 shown in Figure 20.
  • the communication device 1900 may correspond to the EES (including the source EES or the target EES) in the foregoing method embodiment, for example, it may be an EES, or a component configured in the EES (such as a chip, a chip system, a processor, etc.), or it may also be a logic module or software capable of implementing all or part of the EES functions.
  • EES including the source EES or the target EES
  • the communication device 1900 may correspond to the EES (including the source EES or the target EES) in the foregoing method embodiment, for example, it may be an EES, or a component configured in the EES (such as a chip, a chip system, a processor, etc.), or it may also be a logic module or software capable of implementing all or part of the EES functions.
  • the present application embodiment does not limit this.
  • the device 1900 When the device 1900 corresponds to the EES, it can be used to execute the steps executed by the EES in the methods shown in Figures 3 to 18 above, such as executing the steps executed by the source EES, or executing the steps executed by the target EES.
  • the communication device 1900 may include a unit for executing the method executed by the EES in the methods shown in Figures 3 to 18 above.
  • each unit in the communication device 1900 and the above-mentioned other operations and/or functions are respectively for implementing the corresponding processes in the methods shown in Figures 3 to 18.
  • the processing unit 1910 is used to determine that the current application has no corresponding ACR scenario.
  • the transceiver unit 1920 is used to send third information to the terminal device, the third information indicating that the current application has no corresponding ACR scenario, or indicating that the EES or the EAS associated with the EES cannot perform ACR.
  • the processing unit 1910 is used to determine to perform ACR based on the first ACR scenario, where the first ACR scenario is a scenario in which the target EES performs ACR.
  • the transceiver unit 1920 is used to send fourth information to the terminal device, where the fourth information is used to indicate the selection of a target EES that supports the first ACR scenario, or to indicate that the first ACR scenario is the ACR scenario corresponding to the current application.
  • the processing unit 1910 is further configured to determine that the current application has no corresponding ACR scenario.
  • the transceiver unit 1920 is used to send EAS information to the terminal device, where the EAS information indicates at least one EAS; the transceiver unit 1920 is also used to send fifth information to the terminal device, where the fifth information indicates the ACR capability of the at least one EAS.
  • the transceiver unit 1920 is further used to receive sixth information from the terminal device, where the sixth information is used to indicate a request to obtain the ACR capability of the EAS.
  • the processing unit 1910 is configured to determine at least one EAS supporting a first ACR scenario, where the first ACR scenario is a scenario where ACR is performed by a target EES.
  • the transceiver unit 1920 is configured to send EAS information to a terminal device, where the EAS information indicates the at least one EAS.
  • the transceiver unit 1920 is also used to receive sixth information from the terminal device, and the sixth information is used to indicate at least one of the following: selecting a target EAS that supports the first ACR scenario, or the source EES and source EAS cannot perform ACR, or the current application has no corresponding ACR scenario.
  • the transceiver unit 1920 in the communication device 1900 can be implemented by a communication interface, for example, it can correspond to the communication interface 2030 in the communication device 2000 shown in Figure 20.
  • the processing unit 1910 in the communication device 1900 can be implemented by at least one processor, for example, it can correspond to the processor 2010 in the communication device 2000 shown in Figure 20.
  • FIG20 is another schematic block diagram of a communication device provided in an embodiment of the present application.
  • the device 2000 may include at least one processor 2010.
  • the at least one processor 2010 may be used to implement the functions of a terminal device (including an EEC, etc.), an ECS, or an EES (including a source EES or a target EES) in the method provided in an embodiment of the present application.
  • the communication device 2000 may also include at least one memory 2020 for storing program instructions and/or data.
  • the memory 2020 is coupled to the processor 2010.
  • the coupling in the embodiment of the present application is an indirect coupling or communication connection between devices, units or modules, which may be electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the processor 2010 may operate in conjunction with the memory 2020.
  • the processor 2010 may execute program instructions stored in the memory 2020. At least one of the at least one memory may be included in the processor.
  • the communication device 2000 may also include a communication interface 2030 for communicating with other devices via a transmission medium, so that the device in the communication device 2000 can communicate with other devices.
  • the other device may include ECS and EES.
  • the communication interface 2030 may be, for example, a transceiver, an interface, a bus, a circuit, or a device capable of implementing a transceiver function.
  • the processor 2010 may use the communication interface 2030 to send and receive data and/or information, and is used to implement the method performed by the terminal device, ECS or EES in the embodiments corresponding to Figures 3 to 18.
  • the processor 2010 can be used to determine the target EES, which is an EES that supports the first ACR scenario, and the first ACR scenario is a scenario in which ACR is executed by the target EES; the processor is also used to control the communication interface 2030 to request the target EES to execute ACR.
  • the processor 2010 may be used to control the communication interface 2030 to send EES information to a terminal device, where the EES information indicates at least one EES.
  • the processor 2010 can be used to determine that the current application has no corresponding ACR scene, and can also be used to control the communication interface 2030 to send third information to the terminal device, wherein the third information indicates that the current application has no corresponding ACR scene, or indicates that the EES or the EAS associated with the EES cannot execute ACR.
  • connection medium between the processor 2010, the memory 2020 and the communication interface 2030 is not limited in the embodiment of the present application.
  • the above method embodiments can be applied to a processor or implemented by a processor.
  • the processor may be an integrated circuit chip with signal processing capabilities.
  • each step of the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software.
  • the above processor may be a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component.
  • the methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.
  • the steps of the method disclosed in the embodiments of the present application can be directly embodied as a hardware decoding processor to be executed, or a combination of hardware and software modules in the decoding processor to be executed.
  • the software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc.
  • the storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a ROM, a PROM, an EPROM, an EEPROM or a flash memory.
  • the volatile memory may be a RAM, which is used as an external cache.
  • RAM random access memory
  • static RAM static random access memory
  • dynamic RAM dynamic random access memory
  • DRAM dynamic random access memory
  • synchronous dynamic random access memory synchronous DRAM, SDRAM
  • double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • serial link DRAM SLDRAM
  • direct memory bus random access memory direct rambus RAM, DR RAM
  • the present application also provides a chip system, which includes at least one processor for implementing the above-mentioned FIG. 3 to FIG.
  • the chip system also includes a memory, which is used to store program instructions and data, and the memory is located inside or outside the processor.
  • the chip system may be composed of the chip, or may include the chip and other discrete devices.
  • the present application also provides a communication system, including at least one of the aforementioned source EES and target EES, wherein the source EES can implement the functions involved in the source EES in the aforementioned method embodiment; the target EES can implement the functions involved in the target EES in the aforementioned method embodiment.
  • the communication system further includes an ECS, which can implement the functions involved in the ECS in the aforementioned method embodiment.
  • the communication system further includes a terminal device, which can implement the functions involved in the terminal device in the aforementioned method embodiment, for example, can implement the functions involved in the EEC.
  • the present application also provides a computer program product, which includes: a computer program (also referred to as code, or instruction), which, when executed, enables a computer to execute the method executed by a terminal device, ECS or EES (including a source EES or a target EES) in the embodiments shown in FIGS. 3 to 16 .
  • a computer program also referred to as code, or instruction
  • ECS or EES including a source EES or a target EES
  • the present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program (also referred to as code or instruction).
  • a computer program also referred to as code or instruction.
  • the computer program executes the method executed by the terminal device, ECS or EES (including source EES or target EES) in the embodiments shown in FIGS. 3 to 16 .
  • the method provided in the above embodiment can be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software When implemented by software, it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product may include one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network or other programmable device.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from one website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated.
  • the available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic disk), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)).
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.
  • Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of this application essentially or in other words contributes to the prior art.
  • Part of the invention or part of the technical solution may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the invention.
  • the aforementioned storage medium includes: a USB flash drive, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk, or an optical disk, etc., various media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Hardware Redundancy (AREA)
  • Stored Programmes (AREA)

Abstract

本申请提供了应用上下文迁移ACR方法、通信方法及相关装置、系统，可以在应用实例EAS间迁移应用的上下文，该ACR方法包括：确定目标边缘使能服务器EES，该目标EES为支持第一ACR场景的EES，该第一ACR场景为由目标EES执行ACR的场景；请求目标EES执行ACR。该ACR方法通过确定支持第一ACR场景的目标EES并请求其进行ACR，能够通过目标EES完成ACR。

Description

应用上下文迁移方法、通信方法及相关装置、系统
本申请要求于2023年2月20日提交中国专利局、申请号为202310193234.1、申请名称为“应用上下文迁移方法、通信方法及相关装置、系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及应用上下文迁移方法、通信方法及相关装置、系统。
背景技术
在边缘计算场景中，同一应用往往同时部署于多个边缘数据网络(edge data network，EDN)中。部署在不同的EDN的同一应用的应用实例(edge application server，EAS)可以提供相同的业务。终端设备在接入网络后，会就近选择EAS获取应用业务。当终端设备位置变化时，或用户面路径发生更新时，或者当前的EDN不能提供服务的时候，终端设备需要重新选择一个新的EAS继续进行业务。终端设备重新选择的EAS可称为目标EAS，终端设备在切换到目标EAS之前连接的EAS可称为源EAS。
在终端设备的业务从源EAS切换到目标EAS时，为了保证应用业务的连续性，需要将源EAS中的应用上下文迁移至目标EAS，如何进行这种应用上下文的迁移，是一个亟待解决的问题。
发明内容
本申请提供了应用上下文迁移方法、通信方法及相关装置、系统，以期将应用的上下文在EAS间进行迁移。
第一方面，本申请提供了一种应用上下文迁移(application context relocation，ACR)方法，该方法可以应用于终端设备，可以由终端设备执行，或者，也可以由配置在终端设备中的部件(如芯片、芯片系统、处理器等)执行，或者，还可以由能实现全部或部分终端设备功能的逻辑模块或软件实现，本申请对此不作限定。
该方法包括：确定目标边缘使能服务器(edge enabler server，EES)，该目标EES为支持第一ACR场景的EES，该第一ACR场景为由目标EES执行ACR的场景；请求该目标EES执行ACR。
其中，ACR是应用的上下文从源EAS迁移到目标EAS的过程。在本申请中，源EAS是当前为终端设备的应用提供应用服务的EAS，即终端设备当前连接的EAS，源EES是源EAS所关联的EAS，源EAS注册在源EES上，源EES对源EAS进行管理。目标EAS是在ACR后为终端设备的应用提供应用服务的EAS，目标EES为目标EAS所关联的EES，目标EAS注册在目标EES上，目标EES对目标EAS进行管理。在ACR过程中，需要先发现目标EES，再通过目标EES发现目标EAS，从而进行ACR。
第一ACR场景为由目标EES执行ACR的场景，ACR场景中包括ACR的检测，ACR的决策，ACR的执行和ACR后的清理等阶段。在第一ACR场景中，由终端设备进行ACR的检测和ACR的决策，由目标EES进行ACR的执行，由目标EES和目标EAS进行ACR后的清理。
其中，由目标EES进行ACR的执行，包括以下内容中的至少一项：目标EES进行用户面路径修改，目标EES通过目标EES发现目标EAS，目标EES触发目标EAS进行应用上下文的传输。
在本申请中，确定的目标EES是支持第一ACR场景的EES，换言之，该EES有能力作为目标EES执行ACR。如此，请求目标EES执行ACR后，目标EES能够执行ACR。
基于上述技术方案，确定出的目标EES支持作为目标EES执行ACR，从而在当前与终端设备连接的EAS不能继续提供应用服务时，通过目标EES能够顺利完成应用的上下文的迁移。如此，能够保证EAS的顺利切换，保障应用业务的稳定性和连续性。
结合第一方面，在第一方面的某些可能的实现方式中，所述确定目标EES，包括：从边缘配置服务器(edge configuration server，ECS)接收EES信息，该EES信息指示至少一个EES；根据该EES信息 确定目标EES。
ECS负责EDN的配置，在ECS上，可以注册或配置有EES的相关信息，ECS可以向终端设备提供EES信息，指示注册或配置在该ECS上的EES，终端设备可以基于来自ECS的EES信息，确定目标EES。
可选地，该方法还包括：终端设备从ECS接收第一信息，该第一信息指示所述至少一个EES的ACR能力。
其中，EES的ACR能力包括以下信息的至少一项EES是否支持ACR，EES支持的ACR场景，EES支持的ACR应用编程接口(appilcation program interface，API)等。
ECS可以向终端设备发送EES信息，指示至少一个EES。ECS还可以向终端设备发送指示这些EES的ACR能力的信息。相应地，终端设备能够获取到EES的ACR能力。
如此，终端设备能够基于EES的ACR能力，选择出支持第一ACR场景的EES，将其作为目标EES。
在一些实施例中，来自于ECS的EES信息指示的EES是支持第一ACR场景的EES。即ECS可以从注册或配置在该ECS上的EES中筛选出支持第一ACR场景的EES，并发送给终端设备。
从而终端设备在从EES信息所指示的EES中选择目标EES时，不必基于EES支持的ACR场景而进行进一步筛选，可以减小终端设备的负担。
可选地，该方法还包括：终端设备向ECS发送第二信息，该第二信息用于指示以下至少一项：选择支持第一ACR场景的目标EES，或者，当前连接的EES或当前连接的EAS无法执行ACR，或者，当前应用无对应的ACR场景，或者，请求获取EES的ACR能力。
在ECS向终端设备发送EES信息或第一信息之前，终端设备可以向ECS发送第二信息。换言之，ECS可以基于第二信息，选择支持第一ACR场景的EES并指示给终端设备，或向终端设备发送信息指示至少一个EES以及该至少一个EES的ACR能力。
基于上述技术方案，可以由ECS基于EES的ACR能力筛选出支持第一ACR场景的EES，并指示给终端设备，从而终端设备可以从中确定一个EES作为目标EES，而不必基于EES的ACR能力进行筛选，终端设备的任务量得以减少，可以减轻终端设备的负担。ECS也可以向终端设备指示EES以及EES的ACR能力，由终端设备筛选出支持第一ACR场景的EES作为目标EES，从而ECS不必基于EES的ACR能力进行筛选，ECS的任务量得以减少，可以减轻ECS的负担。终端设备确定出的目标EES支持第一ACR场景，从而在请求目标EES执行ACR时，该终端设备能够顺利执行ACR，进而使EAS的切换能够顺利完成，可以保障应用业务的连续性。
结合第一方面，在第一方面的某些可能的实现方式中，所述方法还包括：在当前应用无对应的ACR场景的情况下，或者，在当前连接的EES或当前连接的EAS无法执行ACR的情况下，确定基于第一ACR场景进行ACR。
在当前应用无对应的ACR场景的情况下或者在当前连接的EES或当前连接的EAS无法执行ACR的情况下，无法实现应用上下文的迁移。此时，终端设备可以确定基于第一ACR场景进行ACR，即通过目标EES执行ACR。终端设备确定基于第一ACR场景进行ACR后，可以选择目标EES并请求其执行ACR。
应理解，在当前应用有对应的ACR场景的情况下，或者在当前连接的EES或当前连接的EAS能够执行ACR的情况下，终端设备也可以确定基于第一ACR场景进行ACR。
可选地，该方法还包括：终端设备从当前连接的EES接收第三信息，该第三信息指示当前应用无对应的ACR场景，或者，指示当前连接的EES或当前连接的EAS无法执行ACR。
终端设备可以通过来自EES的信息，确定当前应用无对应的ACR场景，或者，确定当前连接的EES或当前连接的EAS无法执行ACR。
结合第一方面，在第一方面的某些可能的实现方式中，在确定目标EES之前，所述方法还包括：从当前连接的EES接收第四信息，该第四信息用于指示选择支持第一ACR场景的目标EES，或用于指示第一ACR场景为当前应用对应的ACR场景。
当前连接的EES可以确定需要基于第一ACR场景进行ACR，并向终端设备指示当前应用对应的ACR场景是第一ACR场景，或者，可以指示终端设备，在确定目标EES时，目标EES需要 支持第一ACR场景。
结合第一方面，在第一方面的某些可能的实现方式中，所述方法还包括：从目标EES接收EAS信息，该EAS信息指示至少一个EAS；根据EAS信息确定目标EAS。
目标EES可以向终端设备发送EAS信息，指示至少一个EAS，终端设备可以从中确定出目标EAS。应用业务可以从当前连接的EAS上切换至该目标EAS上，基于该目标EAS，可以进行ACR。
可选地，该方法还包括：终端设从目标EAS接收第五信息，该第五信息指示所述至少一个EAS的ACR能力。
EAS的ACR能力包括EAS是否支持ACR，EAS所支持的ACR场景，以及EAS支持的ACR API等。
目标EES可以向终端设备发送指示EAS的ACR能力的信息，相应地，终端设备可以获取到目标EES所指示的至少一个EAS的ACR能力，从而终端设备能够基于EAS的ACR能力，确定支持第一ACR场景的EAS，将其作为目标EAS。
在一些实施例中，所述至少一个EAS支持第一ACR场景。
目标EES可以选择出支持第一ACR场景的EAS，并通过发送给终端设备的EAS信息向终端设备指示该EAS。如此，终端设备可以从中任选一个作为目标EAS。
可选地，该方法还包括：终端设备向目标EES发送第六信息，该六信息用于指示以下至少一项：选择支持所述第一ACR场景的目标EAS，或者，源EES或源EAS无法执行ACR，或者，当前应用无对应的ACR场景，或者，请求获取EAS的ACR能力。
在目标EES向终端设备发送EAS信息或第五信息之前，终端设备可以向目标EES发送第六信息。换言之，目标EES可以基于第六信息，向终端设备发送EAS信息，和/或向终端设备发送第五信息。
基于上述技术方案，可以由目标EES基于EAS的ACR能力筛选出支持第一ACR场景的EAS，并指示给终端设备，从而终端设备可以从中确定一个EAS作为目标EAS，而不必基于EAS的ACR能力进行筛选，终端设备的任务量得以减少，可以减轻终端设备的负担。目标EES也可以向终端设备指示EAS以及EAS的ACR能力，由终端设备筛选出支持第一ACR场景的EAS作为目标EAS，从而目标EES不必基于EAS的ACR能力进行筛选，目标EES的任务量得以减少，可以减轻目标EES的负担。
终端设备确定出的目标EES和目标EAS都支持第一ACR场景，在终端设备请求目标EES执行ACR时，目标EES和目标EAS有能力执行ACR，从而能够顺利完成应用上下文的迁移，进而能够保障应用业务的连续性。
第二方面，本申请提供一种通信方法，该方法可以应用于ECS，可以由ECS执行，或者，也可以由配置在ECS中的部件(如芯片、芯片系统、处理器等)执行，或者，还可以由能实现全部或部分ECS功能的逻辑模块或软件实现，本申请对此不作限定。
该方法包括：向终端设备发送EES信息，该EES信息指示至少一个EES；向终端设备发送第一信息，该第一信息指示所述至少一个EES的ACR能力。
ECS可以向终端设备发送EES信息和第一信息，指示至少一个EES，以及该至少一个EES的ACR能力。如此终端设备能够基于EES的ACR能力，从中确定出支持第一ACR场景的目标EES。
可选地，该方法还包括：接收来自所述终端设备的第二信息，该第二信息用于指示请求获取EES的ACR能力。
ECS可以基于来自终端设备的第二信息，向终端设备发送EES信息和第一信息。
第三方面，本申请提供一种通信方法，该方法可以应用于上述第二方面中的ECS，该方法包括：确定支持第一ACR场景的至少一个EES，第一ACR场景为由目标EES执行ACR的场景；向终端设备发送EES信息，该EES信息指示所述至少一个EES。
ECS可以确定出支持第一ACR场景的至少一个EES后，将其指示给终端设备，如此，终端设备可以从中任选一个作为目标EES。
可选地，该方法还包括：接收来自所述终端设备的第二信息，该第二信息用于指示以下至少 一项：选择支持目标ACR场景的目标EES，或者，当前连接的EES或当前连接的EAS无法执行ACR，或者，当前应用无对应的ACR场景。
ECS可以基于来自终端设备的第二信息，确定支持第一ACR场景的至少一个EES，并向终端设备指示该至少一个EES。
第四方面，本申请提供一种通信方法，该方法可以应用于EES，可以由EES执行，或者，也可以由配置在EES中的部件(如芯片、芯片系统、处理器等)执行，或者，还可以由能实现全部或部分EES功能的逻辑模块或软件实现，本申请对此不作限定。
该方法包括：确定当前应用无对应的ACR场景；向终端设备发送第三信息，该第三信息指示当前应用无对应的ACR场景，或者，指示所述EES或者当前连接的EAS无法执行ACR。
在当前应用无对应的ACR场景时，EES可以向终端设备指示当前应用无对应的ACR场景。
第五方面，本申请提供一种通信方法，该方法可以应用于上述第四方面中的EES，该方法包括：确定基于第一ACR场景进行ACR，该第一ACR场景为由目标EES执行ACR的场景；向终端设备发送第四信息，该第四信息用于指示选择支持第一ACR场景的目标EES，或用于指示第一ACR场景为当前应用对应的ACR场景。
可选地，在确定基于第一ACR场景进行ACR之前，该方法还包括：确定当前应用无对应的ACR场景。
EES可以确定基于第一ACR场景进行ACR，并向终端设备指示第一ACR场景为当前应用对应的ACR场景，即，在进行EAS切换时需要基于第一ACR场景进行ACR。
EES可以在当前应用无对应的ACR场景的情况下，确定基于第一ACR场景进行ACR，也可以在其他情况下，确定基于第一ACR场景进行ACR，例如，在终端设备当前连接的EES和EAS都支持ACR时，EES也可以确定基于第一ACR场景进行ACR。
第六方面，本申请提供一种通信方法，该方法可以应用于上述第四方面中的EES，该方法包括：向终端设备发送EAS信息，该EAS信息指示至少一个EAS；向终端设备发送第五信息，该第五信息指示所述至少一个EAS的ACR能力。
EES可以向终端设备发送EAS信息和第五信息，指示至少一个EAS，以及该至少一个EAS的ACR能力。如此终端设备能够基于EAS的ACR能力，从中确定出支持第一ACR场景的目标EAS。
可选地，该方法还包括：接收来自终端设备的第六信息，该第六信息用于指示请求获取EAS的ACR能力。
EES可以基于来自于终端设备的第六信息，向终端设备发送EAS信息和第五信息。
第七方面，本申请提供一种通信方法，该方法可以应用于上述第四方面中的EES，该方法包括：确定支持第一ACR场景的至少一个EAS；该第一ACR场景为由目标EES执行ACR的场景；向终端设备发送EAS信息，该EAS信息指示所述至少一个EAS。
EES可以确定出支持第一ACR场景的至少一个EAS后，将其指示给终端设备，如此，终端设备可以从中任选一个作为目标EAS。
可选地，该方法还包括：接收来自终端设备的第六信息，该第六信息用于指示以下至少一项：选择支持第一ACR场景的目标EAS，或者，源EES和源EAS无法执行ACR，或者，当前应用无对应的ACR场景。
EES可以基于来自于终端设备的第六信息，确定出支持第一ACR场景的至少一个EAS，并向终端设备指示该至少一个EAS信息。
第八方面，本申请提供了一种EEC上下文传输方法，该方法可以应用于前述第一方面中的终端设备，该方法包括：获取源EES的EEC上下文传输能力；确定目标EES，所述目标EES基于源EES的EEC上下文传输能力确定。
其中，EEC上下文传输能力包括EES是否支持传输EEC上下文，以及所支持的EEC上下文传输流程。
在进行EAS切换时，需要先确定目标EES。终端设备可以基于源EES是否支持EEC上下文传输，以及源EES支持的EEC上下文传输流程，确定目标EES。
如此，终端设备可以确定出与源EES支持对应EEC上下文传输能力的目标EES，从而源EES与目标EES之间能够进行EEC上下文的传输。目标EES能够获取到EEC上下文，基于EEC上下文，目标EES能够为终端设备提供可在边缘计算服务中使用的信息，以使终端设备的应用业务得以正常进行。
可选地，所述获取源EES的EEC上下文传输能力，包括：从源EES接收第一能力信息，该第一能力信息指示源EES的EEC上下文传输能力。
终端设备可以基于从源EES获取的信息，确定源EES是否支持EEC上下文传输。若源EES支持EEC上下文传输，还可以确定该源EES所支持的EEC上下文传输流程。
EEC上下文传输流程可以包括EEC上下文拉取流程和/或EEC上下文推送流程。
结合第八方面，在第八方面的某些可能的实现方式中，源EES支持EEC上下文传输。；所述基于源EES的EEC上下文传输能力，确定目标EES，包括：从ECS接收EES信息，该EES信息指示至少一个EES；从ECS接收第二能力信息，该第二能力信息指示所述至少一个EES的EEC上下文传输能力；从所述至少一个EES中确定目标EES。
在源EES支持EEC上下文从传输时，终端设备可以从ECS指示的至少一个EES中选择与源EES支持对应EEC上下文传输流程的EES作为目标EES。
如此，源EES与目标EES之间能够顺利进行EEC上下文传输，目标EES能够成功获取到EEC上下文，从而能够为终端设备提供可在边缘计算服务中使用的信息，以使终端设备的应用业务得以正常进行。
可选地，在从ECS接收EES信息之前，该方法还包括，向ECS发送第一请求信息，该第一请求信息指示以下至少一项：源EES支持EEC上下文传输，或者，请求获取EES的EEC上下文传输能力。
ECS可以在接收到来自于终端设备的第一请求信息后，再向终端设备发送上述第二能力信息。
可选地，目标EES与源EES不支持对应EEC上下文传输流程。终端设备可以从所述至少一个EES中选择不与源EES支持对应EEC上下文传输流程的EES作为目标EES。
可选地，该方法还包括，确定需要向目标EES重新注册。
在目标EES与源EES不支持对应EEC上下文传输流程时，终端设备可以确定需要向目标EES重新注册，从而在目标EES与源EES不能进行EEC上下文传输时，目标EES也能从终端设备处获取到EEC的信息，并基于EEC的信息生成EEC的上下文。
结合第八方面，在第八方面的某些可能的实现方式中，源EES支持EEC上下文传输；所述基于源EES的EEC上下文传输能力，确定目标EES，包括：向ECS发送第三能力信息，该第三能力信息用于指示源EES所支持的EEC上下文传输流程；从ECS接收EES信息，该EES信息指示至少一个EES；从所述至少一个EES中确定目标EES。
ECS可以基于来自终端设备的第三能力信息，确定源EES所支持的EEC上下文传输流程，从而ECS可以基于源EES所支持的EEC上下文传输流程，选择至少一个EES，并向终端设备发送EES信息指示该至少一个EES，终端设备从而可以从中确定目标EES。
ECS选择的至少一个EES可以是和源EES支持对应的EEC上下文传输能力的EES，也可以是和源EES不支持对应的EEC上下文传输能力的EES。
例如，在ECS所管理的EES中存在与源EES支持对应的EEC上下文传输能力的EES时，ECS可以从中选择出至少一个EES。在ECS所管理的EES中不存在与源EES支持对应的EEC上下文传输能力的EES时，ECS可以选择出与源EES不支持对应的EEC上下文传输能力的至少一个EES。
可选地，所述方法还包括，从ECS接收注册指示信息。
在ECS选择出的EES不与源EES支持对应EEC上下文传输流程时，ECS可以向终端设备发送注册指示信息，指示需要重新向目标EES注册。终端设备可以基于该注册指示信息，确定需要重新向目标EES注册。
在ECS选择出的EES与源EES支持对应EEC上下文传输流程时，ECS可以向终端设备发送注册指示信息，指示不需要重新向目标EES注册。终端设备可以基于该注册指示信息，确定不需 要重新向目标EES注册。
如此，在目标EES与源EES不能进行EEC上下文传输时，目标EES可以通过EEC注册过程，从终端设备处获取到EEC的信息，从而生成EEC上下文。在目标EES与源EES可以进行EEC上下文传输时，终端设备不必向目标EEC进行注册，能够避免冗余操作。
在上述方案中，从EES中选择与源EES具有对应EEC上下文传输能力的EES的步骤可以由ECS执行，如此，在终端设备确定目标EES时，不必基于EES的EEC上下文传输能力进行筛选，可以减少终端设备的负担。
结合第八方面，在第八方面的某些可能的实现方式中，源EES支持EEC上下文传输；在确定目标EES后，所述方法还包括：向目标EES发送第四能力信息，该第四能力信息指示源EES的EEC上下文传输能力；接收来自目标EES的注册指示信息，该注册指示信息指示是否需要向目标EES重新注册。
在源EES支持EEC上下文传输时，终端设备可以向目标EES发送信息指示源EES支持EEC上下文传输流程。目标EES接收到第四能力信息后，可以判断目标EES是否与源EES支持对应的EEC上下文传输能力。
在目标EES与源EES支持对应的EEC上下文传输能力时，目标EES可以向终端设备发送注册指示信息，指示终端设备不需要重新向目标EES注册。
在目标EES与源EES不支持对应的EEC上下文传输能力时，目标EES可以向终端设备发送注册指示信息，指示终端设备需要重新向目标EES注册。
如此，在目标EES与源EES不能进行EEC上下文传输时，目标EES可以指示终端设备重新向目标EES注册，从而目标EES能够获取到EEC的信息，生成EEC上下文，进而可以为终端设备提供可在边缘计算服务中使用的信息，以使终端设备的应用业务得以正常进行。在目标EES与源EES能够进行EEC上下文传输时，目标EES可以指示终端设备不必向目标EEC进行注册，能够避免冗余操作。
结合第八方面，在第八方面的某些可能的实现方式中，在确定目标EES后，所述方法还包括：接收来自目标EES的第五能力信息，该第五能力信息指示目标EES的EEC上下文传输能力；基于目标EES的EEC上下文传输能力，确定是否需要重新注册。
目标EES可以向终端设备指示目标EES的EEC上下文传输能力，从而终端设备可以判断目标EES是否与源EES支持对应的EEC上下文传输能力。
在源EES支持EEC上下文传输，且目标EES与源EES支持对应的EEC上下文传输能力时，终端设备可以确定不需要重新向目标EES注册。
在目标EES与源EES不支持对应的EEC上下文传输能力，或源EES不支持EEC上下文传输时，终端设备可以确定需要重新向目标EES注册。
可选地，该方法还包括：向目标EES发送第二请求信息，该第二请求信息指示请求获取EES的EEC上下文传输能力。
目标EES可以在接收到来自于终端设备的第二请求信息后，再向终端设备发送上述第五能力信息。
在上述方案中，判断目标EES是否与源EES支持对应的EEC上下文传输能力的步骤可以由终端设备执行，终端设备进而确定是否需要重新向目标EES注册，如此，目标EES不必进行判断，可以减少目标EES的负担。
第九方面，本申请提供了一种通信装置，可以实现上述各方面中终端设备执行的方法，或可以实现上述各方面中ECS执行的方法，或可以实现上述各方面中EES执行的方法。该装置包括用于执行上述方法的相应的单元或模块。该装置包括的单元或模块可以通过软件和/或硬件方式实现。
第十方面，本申请提供了一种通信装置，包括处理器，所述处理器可以实现上述各方面中终端设备执行的方法，或可以实现上述各方面中ECS执行的方法，或可以实现上述各方面中EES执行的方法。
可选地，该装置还可以包括存储器，用于存储指令和数据。所述存储器与所述处理器耦合，所述处理器执行所述存储器中存储的指令时，可以实现上述各方面中描述的方法。
可选地，所述装置还可以包括通信接口，所述通信接口用于该装置与其它设备进行通信，示例性地，通信接口可以是收发器、电路、总线、模块或其它类型的通信接口。
第十一方面，本申请提供了一种通信系统，包括源EES和目标EES中的至少一个，其中，源EES用于实现前述第四方面或第五方面中EES所执行的方法，目标EES用于实现前述第六方面或第七方面中EES所执行的方法。
可选地，该通信系统中还包括ECS，该ECS用于实现前述各方面中ECS所执行的方法。
可选地，该通信系统中还包括终端设备，该终端设备用于实现前述各方面中终端设备所执行的方法。
第十二方面，本申请提供了一种芯片系统，该芯片系统包括至少一个处理器，用于支持实现上述各方面中终端设备执行的方法所涉及的功能，或用于支持实现上述各方面中ECS执行的方法所涉及的功能，或用于支持实现上述各方面中EES执行的方法所涉及的功能，例如，接收或处理上述方法中所涉及的数据和/或信息。
在一种可能的设计中，所述芯片系统还包括存储器，所述存储器用于保存程序指令和数据，存储器位于处理器之内或处理器之外。
该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
第十三方面，本申请提供了一种计算机可读存储介质，包括计算机程序，当其被运行时，使得上述各方面中终端设备执行的方法被实现，或使得上述各方面中ECS执行的方法被实现，或使得上述各方面中EES执行的方法被实现。
第十四方面，本申请提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当所述计算机程序被运行时，使得上述各方面中终端设备执行的方法被实现，或使得上述各方面中ECS执行的方法被实现，或使得上述各方面中EES执行的方法被实现。
应当理解的是，本申请的第二方面至第十四方面与本申请的第一方面的技术方案相对应，各方面及对应的可行实施方式所取得的有益效果相似，不再赘述。
附图说明
图1是适用于本申请实施例提供的应用上下文迁移方法的一种可能的通信系统的架构；
图2是适用于本申请实施例提供的ACR方法的场景示意图；
图3是本申请实施例提供的ACR方法的示意性流程图；
图4是本申请实施例提供的EEC确定目标EES的方法的示意性流程图；
图5是EAS分别向EES注册和ECS注册的流程的示意图；
图6是本申请实施例提供的EEC请求目标EES执行ACR的流程的示意图；
图7是本申请实施例提供的EEC确定目标EAS的方法的示意图；
图8是本申请实施例提供的应用上下文迁移方法的一种可能的实现方式；
图9是本申请实施例提供的应用上下文迁移方法的又一种可能的实现方式；
图10是本申请实施例提供的应用上下文迁移方法的又一种可能的实现方式；
图11是本申请实施例提供的应用上下文迁移方法的又一种可能的实现方式；
图12是本申请实施例提供的EEC注册流程的示意图；
图13是本申请实施例提供的EEC上下文拉取流程和EEC上下文推送流程的示意图；
图14是本申请实施例提供的EEC上下文传输方法的示意性流程图；
图15是本申请实施例提供的确定目标EES的方法的示意性流程图；
图16是本申请实施例提供的确定是否执行EEC上下文传输的方法的示意性流程图；
图17是本申请实施例提供的EEC上下文迁移方法的一种可能的实现方式；
图18是本申请实施例提供的EEC上下文迁移方法的又一种可能的实现方式；
图19是本申请实施例提供的通信装置的示意性框图；
图20是本申请实施例提供的通信装置的另一示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：第五代(5thgeneration，5G)移动通信系统、新无线接入技术(new radio access technology，NR)系统、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、或者全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统。其中，移动通信系统可以包括非独立组网(non-standalone，NSA)和/或独立组网(standalone，SA)。本申请提供的技术方案还可以应用于未来的通信系统，如第六代移动通信系统等。本申请对此不作限定。
本申请提供的技术方案还可以应用于机器类通信(machine type communication，MTC)、机器间通信长期演进技术(Long Term Evolution-machine，LTE-M)、设备到设备(device-to device，D2D)网络、机器到机器(machine to machine，M2M)网络、物联网(internet of things，IoT)网络或者其他网络。其中，IoT网络例如可以包括车联网。其中，车联网系统中的通信方式统称为车到其他设备(vehicle to X，V2X，X可以代表任何事物)，例如，该V2X可以包括：车辆到车辆(vehicle to vehicle，V2V)通信，车辆与基础设施(vehicle to infrastructure，V2I)通信、车辆与行人之间的通信(vehicle to pedestrian，V2P)或车辆与网络(vehicle to network，V2N)通信等。
本申请的技术方案可以应用于各种通信场景中，例如服务连续性场景、多接入边缘计算(multi-access edge computing，MEC)场景等，本申请对此不作限制。
图1示出了适用于本申请实施例提供的应用上下文迁移方法的一种可能的通信系统的架构。
在第三代合作伙伴计划(3rd generation partnership project，3GPP)的服务与系统(service&system aspects，SA)工作组的MEC研究中，定义了如图1所示的架构。
如图1所示，该通信系统包括终端设备、核心网、EDN和ECS。
其中，终端设备中可以配置有一个或多个应用客户端(application client，AC)和一个或多个边缘使能客户端(edge enabler client，EEC)，EDN中可以部署有一个或多个EAS和一个或多个EES。
图1的架构还包括参考点EDGE-1到EDGE-9。EDGE-1参考点支持EES和EEC之间的交互；EDGE-2参考点支持EES和核心网之间的交互；EDGE-3参考点支持EES和EAS之间的交互；EDGE-4参考点支持ECS和EEC之间的交互；EDGE-5参考点支持AC和EEC之间的交互；EDGE-6参考点支持ECS和EES之间的交互；EDGE-7参考点支持EAS和核心网之间的交互；EDGE-8参考点支持ECS和核心网之间的交互；EDGE-9参考点支持两个处于相同或不同MEC节点的EES之间的交互。
应理解，图1仅为示意，该通信系统中还可以包括其它设备，在图1中未画出。
需要说明的是，图1中所涉及的各个网元以及网元之间的通信接口的名称是以目前协议中规定的为例进行简单说明的，但并不限定本申请实施例只能够应用于目前已知的通信系统。因此，以目前协议为例描述时出现的标准名称，都是功能性描述，本申请对于网元、接口、信息、消息或信令等的具体名称并不限定，仅表示网元、接口、信息、消息或者信令的功能，可以对应的扩展到其它系统，比如4G或未来通信系统中。
为了方便理解，下面对本申请涉及的一些网元、术语等进行简单介绍：
1、边缘计算：是指在靠近物或数据源头的网络边缘侧，融合网络、计算、存储、应用核心能力的开放平台，就近提供边缘智能服务，满足行业数字化在敏捷连接、实时业务、数据优化、应用智能、安全与隐私保护等方面的关键需求。换言之，边缘计算是将从终端设备采集到的数据，直接在靠近数据产生的本地设备或网络中进行分析，无需再将数据传输至云端数据处理中心。
2、多接入边缘计算(MEC)：也可以称为移动边缘计算(mobile edge computing)，可利用无线接入网络就近提供服务和云端计算功能，从而创造出一个具备高性能、低延迟与高带宽的电信级服务环境，加速网络中各项内容、服务及应用的快速下载，让消费者享有不间断的高质量网络体验。
3、数据网络(data network，DN)：指运营商或第三方的服务网络，可以向终端设备提供服务，例如运营商业务、互联网业务等。
4、本地数据网络(local area data network，LADN)：距离用户的附着点(attachment point)很近的一个数据网络的接入点(access point)。
5、边缘数据网络(EDN)：在一种理解中，EDN是一个特别的本地数据网络，包含边缘使能功能，可以使用数据网络接入标识符(data network access identifier，DNAI)和数据网络名称(data network name，DNN)来标识，是网络逻辑概念。另一种理解为，EDN是中心云的对等概念，可以理解为是一个本地的数据中心，可以使用DNAI来标识，可以包含多个本地数据网络。
6、应用实例/边缘应用(EAS)：是指部署在边缘数据网络中的应用，具体可以指一个服务器的应用程序(例如，社交媒体软件、增强现实(augmented reality，AR)、虚拟现实(virtual reality，VR))，或部署在EDN中运行的实例(instance)。一个应用可在一个或多个EDN中部署一个或多个EAS，部署在不同EDN运行的EAS可以认为是一个应用的不同的EAS，它们可以共享一个域名，可以使用一个互联网协议(internet protocol，IP)地址，也可以使用不同的IP地址。
此外，应用实例/边缘应用也可以称为边缘应用(服务器)、应用实例、边缘应用实例、MEC应用(服务器)、EAS功能等。
7、应用客户端(AC)：是指边缘应用在终端设备侧的对等实体，应用客户端用于应用用户(user)从应用服务器获取应用业务。应用客户端是应用在终端设备侧的客户端程序，应用客户端可以连接到云上的应用服务器获取应用业务，也可以连接到部署在一个或多个EDN中运行的EAS以获取应用业务。
8、边缘使能服务器(EES)：可以为部署在EDN中的EAS提供使能能力，可以更好地支持应用在MEC的部署情况。例如，EES可以支持应用的注册，对终端设备的认证和鉴权，为终端设备提供EAS的IP地址信息等。EES还可以支持获取EAS的标识和IP地址信息，并将EAS的标识和IP地址信息发送给ECS。
EES部署在EDN中。一般情况下，一个EAS注册到一个EES上，或者，通过管理系统将一个EAS的信息配置在一个EES上，一个EES上可以注册有一个或多个EAS，或者配置有一个或多个EAS的信息，该EES称为该一个或多个EAS所关联的EES。EES可以控制、管理、注册或配置与该EES关联的EAS。
9、边缘使能客户端(EEC)：用于提供AC所需的支持功能，是EES在终端设备侧的对等实体。EEC用于向EES注册EEC的信息及AC的信息、执行安全认证和鉴权、从EES获取EAS的IP地址、向AC提供边缘计算使能能力，如发现EDN中可用的EAS，将EAS的IP地址返回给AC等。
10、边缘配置服务器(ECS)：负责EDN的配置，如向终端设备提供EES的信息。还可以直接向终端设备提供应用实例的信息，以及和应用的DNS交互获取应用实例的信息。进一步从其他功能实体获取并保存应用实例和IP地址的信息。
还负责维护各个EDN的信息，包括EDN的服务区域和EES地址等。其中，EDN的服务区域可以是拓扑地址信息(例如小区标识(cell identity)、跟踪区标识(tracking area identity，TAI)等)或几何地址信息(例如，省、市、区或经纬度等信息)，服务区域可以是地址信息的集合。
ECS可以被部署在移动网络运营商(mobile network operator，MNO)域中，也可以由服务提供商部署在第三方域中。在一种实现方式中，ECS网元是分布式部署的，即每个ECS可以管理不同区域的边缘数据网络。应该理解，ECS网元可以与其它网元合设也可以是独立的网元，本申请对ECS网元在网络架构中的部署情况并不做任何限定。
11、终端设备：又称为用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)等，是一种向用户提供语音或数据服务的设备，也可以是物联网设备。示例性地，终端设备包括具有无线收发功能的手持式设备、车载设备等。目前，终端设备可以是：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备(例如智能手表、智能手环、智能眼镜等)，车载设备(例如，汽车、自行车、电动车、飞机、船舶、火车、高铁等)、虚拟现实(virtual reality，VR)设备、增强现实 (augmented reality，AR)设备、工业控制(industrial control)中的无线终端、智能家居设备(例如，冰箱、电视、空调、电表等)、智能机器人、车间设备、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端，或智慧家庭(smart home)中的无线终端、飞行设备(例如，智能机器人、热气球、无人机、飞机)等。此外，终端设备还可以为一种芯片。本申请对于终端设备的具体形式不做限定。
12、核心网：主要用于对终端设备进行管理，并提供与外网通信的功能。核心网可以包括用户平面功能(user plane function，UPF)网元、接入与移动性管理功能(access and mobility management function，AMF)网元、会话管理功能模块(session management function，SMF)网元、统一数据管理(unified data management，UDM)网元或策略控制功能(policy control function，PCF)网元中的至少一个。对于核心网中包括的网元的功能，可以参考3GPP定义的标准(例如，TS 23.501)。
13、应用上下文(application context)：可以指和一个或一组用户相关的运行状态信息，例如，游戏进程、历史数据等。可选地，应用上下文还可以包含该一个或多个用户在EAS与核心网的订阅的上下文，例如订阅的事务标识等。可选地，应用上下文还可以包括该一个或多个用户在EES上的上下文，例如，EAS对该一个或多个用户的订阅的事务标识。
14、EEC上下文：EEC上下文可以指存储在EES中的与用户相关的数据。EEC上下文可以包括EEC侧信息和EAS‐EES订阅信息。其中，EEC侧信息可以包括EEC注册信息、EEC订阅信息(例如，EAS发现订阅、EAS动态信息订阅等)；EAS‐EES订阅信息可以包括终端设备位置API、应用上下文迁移事件、AC信息开放API、终端设备标识API、以及服务质量(quality of service，QoS)会话API等。
15、应用上下文迁移(ACR)：也可以称为应用迁移或应用上下文重定位，是应用上下文在EAS间进行迁移的过程。
ACR流程主要可以分为以下四个阶段：
阶段1：ACR的检测。
在此阶段，可以判断是否需要进行上下文迁移。可以由检测实体检测需要进行ACR的事件，例如终端位置变化、终端用户面路径发生更新等。
阶段2：ACR的决策。
在此阶段，由决策实体确定需要进行上下文迁移。
阶段3：ACR的执行。
在此阶段，由执行实体将应用的上下文从源EAS传送至目标EAS。进一步地，包括目标EAS的发现，还可以向终端设备通知目标EAS的相关信息、通知EAS(可以是源EAS和目标EAS)发起应用上下文传输(application context transfer，ACT)，EES或EAS执行应用功能(application function，AF)流量影响(AF traffic influence)并携带目标EAS的N6路由信息
阶段4：ACR后的清理工作。
在此阶段会涉及到多个实体，包括EAS通过EES向EEC通知ACT结果，AC发起一个新的套接字(socket)连接到目标EAS等。
16、ACR场景：检测并执行ACR的具体方案，包括ACR的检测，ACR的决策，ACR的执行和ACR后的清理等步骤，ACR场景中涉及执行各个步骤的实体。目前存在多种ACR场景，ACR场景所对应的ACR方案如表1所示。
表1

应理解，表1中示出的5种ACR场景仅为ACR场景的示例，各场景的名称也仅是示意性的给出，不能成为对本申请的限制，关于ACR场景的具体内容，可以参照3GPP定义的标准(例如，TS23.588)。
17、ACR能力：本申请实施例中的ACR能力，可以包括但不限于是否支持ACR，是否支持第一ACR场景，所支持的ACR场景，以及，所支持的ACR API。基于EES的ACR能力，可以确定EES所支持的ACR场景，基于EAS的ACR能力，可以确定EAS所支持的ACR场景。
在本申请的一些实施例中，EES的ACR能力还可以包括EES的EEC上下文传输能力。EES的EEC上下文传输能力包括该EES是否支持EEC上下文传输，该EES是否支持EEC上下文拉取流程，该EES是否支持EEC上下文推送流程。在EES支持EEC上下文传输时，EES对应的EEC上下文传输能力还包括EES所支持的EEC上下文传输流程。EEC上下文传输能力可以通过EES支持的API信息指示。
在本申请的实施例中，终端设备上可以配置有AC和EEC。应用的用户与应用的提供商签订服务协议，可以登录终端设备上的与该应用对应的AC，通过AC与EAS的连接进行通信，从而可以获取应用的服务。EEC为中间件层，一般位于操作系统中，或者位于AC与操作系统中间。AC可以以API的方式从EEC获取边缘使能服务。
在边缘计算技术中，提供应用服务的EAS可以配置在终端设备附近的EDN中。终端设备中的应用数据可以在靠近终端设备的EAS中实时处理，而不用将数据传输到中心云中进行处理，以降低因数据传输造成的时延。
同一应用可以在多个EDN中部署EAS。部署在不同的EDN的同一应用的EAS可以提供相同的业务，具有功能上的等价性。
示例性地，应用a的服务器可以部署在位于A地的EDN-1中，以及位于B地的EDN-2中。位于A地的终端设备上可以配置有应用a的AC，可以通过位于其附近的EDN-1中的EAS获取应用业务，位于B地的终端设备上也可以配置有的应用a的AC，可以通过位于其附近的EDN-2中的EAS获取应用业务。
终端设备在接入网络后，会选择部署在就近的EDN中的EAS执行业务。当发生终端设备从一个EDN的服务区域移动到另一个EDN的服务区域，或终端设备当前连接的EAS满载等情况时，终端设备当前连接的EAS不能很好的为该终端设备继续提供服务，为了适应应用的业务连续性需求，需要为终端设备重新就近选择一个新的EAS，从而为终端设备继续提供服务。
当终端设备的应用业务在EAS间切换时，需要将终端设备的应用的上下文在EAS间进行迁移。
图2是适用于本申请实施例提供的ACR方法的场景示意图。
如图2所示，EDN1中可以部署有EES1、EAS1和EAS2，EDN2中可以部署有EES2和EAS2。EDN1和EDN2中的EAS2可以为终端设备提供当前应用的服务。当前为终端设备提供服务的EAS是EDN1中的EAS2，在终端设备从EDN1的服务区域移动到EDN2的服务区域，或EDN1中的EAS2满载时，EDN1中的EAS2将无法继续为终端设备提供应用服务，这时可以将当前应用的应用业务切换至EDN2中的EAS2，并需要将终端设备的当前应用的上下文从EDN1中的EAS2同步迁移到EDN2中的EAS2中。
应理解，图2所示的场景仅为示例，这不应对本申请构成任何限定。一个应用可以在更多个或更少个多个EDN中部署EAS，各个EDN可以有各自的服务区域。一个EDN中也可以部署有多个应用的EAS。
为了方便描述，在本申请的实施例中，将当前为终端设备提供应用服务的EAS称为源EAS(source EAS，S-EAS)，或当前连接的EAS，例如图2中的EDN1中的EAS2；与源EAS关联的EES称为源EES(source EES，S-EES)，或当前连接的EES，例如图2中的EES1；将终端设备的应用业务切换后，为终端设备提供应用服务的新的EAS称为目标EAS(target EAS，T-EAS)，例如图2中的EDN2中的EAS2，与目标EAS关联的EES称为目标EES(target EES，T-EES)，例如图2中的EES2。
在终端设备与EAS连接后，需要与该EAS，以及该EAS所关联的EES协商确定应用的ACR场景，从而应用可以基于确定的ACR场景，进行ACR的检测、决策和执行的流程，以便在应用的业务需要在EAS间切换时完成该切换过程。
当终端设备、与终端设备当前连接的(或者终端设备选择的)EAS以及该EAS所关联的EES没有共同支持的ACR场景，例如EEC、EAS或EES不支持执行ACR时，无法协商确定出当前应用的ACR场景，因此，在当前为终端设备提供应用服务的EAS满载，或终端设备离开该EAS所在的EDN的服务区域时，当前应用无法实现ACR，也就不能完成EAS的顺利切换。
为此，本申请提供了一种ACR方法，通过确定支持执行ACR的目标EES，基于该目标EES执行ACR，从而完成当前应用的上下文的迁移。
如此，能够通过目标EES实现当前应用的上下文的迁移。在当前应用无对应的ACR场景时，例如终端设备、与终端设备当前连接的(或者终端设备选择)EAS以及该EAS所关联的EES没有共同支持的ACR场景时，也可以实现当前应用的上下文迁移。在当前与终端设备连接的EAS不能继续提供应用服务时，能够保证EAS的顺利切换，进而能够保障应用业务的稳定性和连续性。
下面结合图3至图11对本申请提供的应用上下文迁移方法进行描述。
为了更好地理解本申请的实施例，首先做出如下几点说明：
第一，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。例如，第一信息和第二信息仅仅是为了区分不同的信息，并不对其先后顺序进行限定。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定 不同。
第二，在本申请实施例中，各术语及英文缩略语，如边缘应用服务器、边缘使能服务器、应用上下文迁移、EEC、EES、源EES、目标EES、EAS、源EAS、目标EAS、ACR等均为方便描述而给出的示例性举例，不应对本申请构成任何限定。本申请并不排除在已有或未来的协议中定义其它能够实现相同或相似功能的术语的可能。
第三，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a、b和c中的至少一项(个)，可以表示：a，或b，或c，或a和b，或a和c，或b和c，或a、b和c，其中a，b，c可以是单个，也可以是多个。
第四，本申请实施例中的表格仅为示例，并不对本申请的保护范围构成限定。例如，表格中的信息的取值仅仅是举例，可以配置为其他值，本申请并不限定。又例如，可以基于文中各表做适当的变形调整，例如，拆分，合并等等。再例如，各表中标题示出的参数名称也可以采用通信装置可理解的其他名称，其参数的取值或表示方式也可以采用通信装置可理解的其他取值或表示方式。再例如，上述各表在实现时，也可以采用其他的数据结构，例如可以采用数组、队列、容器、栈、线性表、指针、链表、树、图、结构体、类、堆、散列表或哈希表等。
第五，“预定义”或“预配置”可以通过在设备(例如，包括终端设备和ECS)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现，本申请对于其具体的实现方式不做限定。其中，“保存”可以是指，保存在一个或者多个存储器中。所述一个或者多个存储器可以是单独的设置，也可以是集成在编码器或者译码器，处理器、或通信装置中。所述一个或者多个存储器也可以是一部分单独设置，一部分集成在译码器、处理器、或通信装置中。存储器的类型可以是任意形式的存储介质，本申请并不对此限定。
第六，在本申请实施例中，“当……时”、“在……的情况下”、“若”以及“如果”等描述均指在某种客观情况下设备(如，下文所述的终端设备或者EES)会做出相应的处理，并非是限定时间，且也不要求设备(如，下文所述的终端设备或者EES)在实现时一定要有判断的动作，也不意味着存在其它限定。
第七、本申请中“向…(终端)发送信息”可以理解为该信息的目的端是终端。可以包括直接或间接的向终端发送信息。“从…(终端)接收信息”可以理解为该信息的源端是终端，可以包括直接或间接的从终端接收信息。信息在信息发送的源端和目的端之间可能会被进行必要的处理，例如格式变化等，但目的端可以理解来自源端的有效信息。本申请中类似的表述可以做类似的理解，在此不再赘述。
第八、本申请中对承载信息的消息的举例仅为示意，如下文中的“第二信息例如可以承载在上述服务开通请求消息中”可以理解为第二信息可以承载在服务开通请求消息中，也可以承载在其他消息中。本申请中类似的表述可以作类似的理解。本申请不限定用于承载信息的消息的类型，对承载信息的消息的名称也仅是示意性地给出，不作限定。
第九、本申请中的各个实施例可以单独的实施，也可以组合实施，本申请对此不作限定。
图3是本申请实施例提供的ACR方法的示意性流程图。
图3所示的方法从终端设备的角度示出了本申请实施例提供的ACR方法。该方法可以由终端设备执行，也可以由终端设备在中的部件(如电路、芯片、芯片系统等)执行，可以通过软件和/或硬件的方式实现。本申请对此不作限定。下面以配置于终端设备的EEC为例进行描述。
参看图3，方法300包括步骤310和步骤320。
在步骤310中，EEC确定目标EES，该目标EES为支持第一ACR场景的EES，该第一ACR场景为由目标EES执行ACR的场景。
第一ACR场景是由目标EES执行ACR的场景，例如可以是场景“EEC executed ACR via T-EES”。在第一ACR场景中，ACR的流程可以为，由EEC检测需要进行ACR的事件，并决策是 否进行ACR，由目标EES执行ACR。
应理解，本申请中的“第一ACR场景”的描述，仅是为了区分而给出的示意，并不意味着对ACR场景的名称的限定。
在本申请的实施例中，EES支持第一ACR场景，代表该EES可以作为目标EES支持完成ACR的执行。相应地，EAS支持第一ACR场景，代表该EAS可以作为目标EAS支持完成ACR的执行。
EEC可以确定支持第一ACR场景的目标EES，进而在EEC请求其执行ACR时，目标EES有能力执行ACR。
EEC可以通过服务开通流程(service provisioning)或者EES发现流程，确定目标EES。
下文将结合图4中的(a)和图4中的(b)，从网元间交互的角度对步骤310进行详细描述。
图4中的(a)是本申请实施例提供的EEC通过ECS确定目标EES的方法的示意图。在方法400a中，由EEC基于EES支持的ACR场景，确定出支持第一ACR场景的目标EES。方法400a可以包括步骤410a至步骤440a。
在步骤410a中，EEC向ECS发送服务开通请求消息(service provisioning request)。
服务开通请求消息也可以称为服务配置请求消息，该消息中可以包括EEC标识符(EEC ID)、安全凭据、AC配置信息(AC profile)、终端设备标识、连接信息、和终端设备位置等。其中，终端设备标识可以包括通用公共订阅标识符(generic public subscription identifier，GPSI)等。
在本申请的实施例中，EEC还可以向ECS发送信息，指示请求获取EES的ACR能力。为了便于描述，在本申请的实施例中，称该信息为第二信息，应理解，这不能成为对本申请的限定。该第二信息例如可以承载在上述服务开通请求消息中。
示例性地，在当前应用无对应的ACR场景，或终端设备与EES协商未确定出ACR场景时，EEC可以向ECS发送第二信息。在当前应用对应的ACR场景为第一ACR场景时，第二信息还可以指示选定的ACR场景为第一ACR场景。
在步骤420a中，在接收到服务开通请求消息后，ECS处理服务开通请求，确定或识别一个或多个EES。
在一些实施例中，ECS可以进行授权检查，以验证EEC是否具有执行操作的授权。
ECS可以根据AC配置信息和/或终端设备位置信息，匹配注册到ECS上的EES。
示例性地，如果检查通过，ECS可以根据服务开通请求选择一个或多个EES。ECS可以选择服务区域中包含该终端设备的位置的EES、注册的EAS列表中包括匹配AC配置信息的EAS标识符(EAS ID)的EES等。
在本申请的实施例中，ECS可以获取一个或多个EES的相关信息。EES的相关信息中可以包括指示至少一个EES的信息，例如EES的列表，EES的相关信息中还可以包括指示该至少一个EES的ACR能力的信息，还可以包括指示与EES所关联的至少一个EAS的信息，以及指示该至少一个EAS的ACR能力的信息。
EES的相关信息可以是EES向ECS注册时ECS获取的。EES可以注册到ECS上，ECS可以保存EES的相关信息。在EAS确定需要注册到EES时，例如EAS被配置并启动时，EAS也可以注册到EES上，EES可以保存EAS的信息。
在一些实施例中，EES可以通过网管系统获取EAS的信息，ECS也可以通过网管系统获取EES的相关信息，而无需进行执行注册流程。在一些实施例中，ECS上可以存储有一个或多个EES的相关信息，该EES的相关信息可以是预配置的，EES上也可以存储有一个或多个EAS的信息，该EAS的信息也可以是预配置的，本申请对此不作限定。
作为示例，下面结合图5中的(a)说明EAS注册到EES上的流程，结合图5中的(b)说明EES注册到ECS上的流程。
图5中的(a)是EAS向EES注册的流程的示意图。
EAS的注册流程可以包括步骤510a至步骤530a。
在步骤510a中，EAS向EES发送EAS注册(EAS registration)请求消息。
EAS注册请求消息可以携带EAS配置信息(EAS profile)和EAS安全凭据，还可以包括注 册的建议到期时间，或称为注册的有效时间。
在本申请的实施例中，EAS还可以向EES发送信息指示该EAS的ACR能力，例如该EAS是否支持ACR，或者该EAS支持的ACR场景。该信息可以承载在EAS注册请求消息中，例如可以包括在EAS配置信息中。该信息例如可以用“service continuity support”参数表示。
在步骤520a中，EES处理注册请求。
EES基于EAS的注册请求消息，进行注册授权检查，验证EAS是否具有在EES上注册的授权。
在授权成功后，EES存储EAS配置信息供以后使用(例如，用于服务从EEC收到的EAS发现请求等)。EES也可以保存EAS的ACR能力。
在步骤530a中，EES向EAS发送EAS注册响应消息。
EES使用EAS注册响应消息回复EAS。若注册成功，在EAS响应消息中可以携带指示注册成功的信息。EES还可以提供到期时间，以向EAS指示注册何时自动到期。若注册失败，在EAS响应消息中可以携带信息指示注册失败，并给出失败原因。图5中的(b)是EES向ECS注册的流程的示意图。
EES的注册流程可以包括步骤510b至步骤530b。
在步骤510b中，EES向ECS发送EES注册请求消息。
EES注册请求消息中可以携带该EES的配置信息。EES的配置信息可以包括以下信息中的至少一项：该EES标识、该EES的端点(endpoint)信息、注册到该EES的EAS的标识列表等等。EES的配置信息中还包含该EES的安全凭据。EES的配置信息中还可以包含注册的有效时间。
在本申请的实施例中，EES还可以向ECS发送信息指示该EES的ACR能力，例如该EES支持的ACR场景，该信息可以承载在EES注册请求消息中，例如包括在EES的配置信息中。
EES还可以向ECS发送信息指示注册到该EES的EAS的ACR能力，例如EAS支持的ACR场景，该信息也可以承载在EES注册请求消息中。
在步骤520b中，ECS处理注册请求。
ECS接收到EES注册请求消息后，可以将EES的配置信息保存在本地。ECS也可以保存EES的ACR能力，以及注册到EES上的EAS的ACR能力。
在步骤530b中，ECS向EES发送EES注册响应消息。
接收到来自EES的EES注册请求消息后，ECS还可以发送相应的响应消息。
需要说明的是，图5中的(a)和图5中的(b)所示的注册过程可以是单独的实施例，EAS向EES注册的过程，以及EES向ECS注册的过程，可以一次或多次发生在方法300的被执行时，或方法300被执行之前的任意时间，或方法300被执行之后的任意时间。
EES的注册过程和EAS的注册过程在时间上可以不是连续执行的。在EES向ECS注册后的任意时间间隔内可以有EAS注册到该EES上，EAS注册到EES上后该EES可以在任意时间间隔内执行注册到ECS上的过程。
在步骤430a中，ECS向EEC发送服务开通响应消息。
服务开通响应消息也可以称为服务配置响应消息。若ECS无法根据服务开通请求消息确定EEC信息，则服务开通响应消息中携带信元指示ECS拒绝该EEC的服务开通请求，并给出失败原因。若ECS成功处理该EEC的服务开通请求，则服务开通响应消息中可以携带EDN连接信息、EES信息(可以包括ECS确定或识别出的一个或多个EES的列表、以及该一个或多个EES的地址、该一个或多个EES的标识信息等)。在服务开通响应消息中还可以携带ECS确定或识别的一个或多个EES中各个EES所关联的EAS的信息。
在本申请的实施例中，ECS还可以向EEC发送信息，指示由ECS识别或确定的一个或多个EES中各个EES的ACR能力，例如EES所支持的ACR场景。为了便于描述，在本申请的实施例中，称该信息为第一信息，应理解，这不能成为对本申请的限定。该第一信息例如可以承载在上述服务开通响应消息中，例如包括在EES信息中。
在一些实施例中，第一信息还可以指示由ECS确定或识别的一个或多个EES中，各个EES所关联的EAS的ACR能力。在一些实施例中，ECS可以将所有注册或配置在ECS上的EES的信 息全部发送给EEC。此时，前述步骤420a是可选地。
在步骤440a中，EEC从一个或多个EES中确定支持第一ACR场景的目标EES。
EEC接收到的信息可以指示一个或多个EES以及该一个或多个EES的ACR能力，EEC可以选择支持第一ACR场景的EES作为目标EES。
在一些实施例中，EEC还接收到信息，指示EES所关联的EAS，以及EAS所支持的ACR场景，EEC可以从中选择一个与支持第一ACR场景的EAS所关联的EES作为目标EES。
例如，EEC确定的目标EES支持第一ACR场景，该目标EES所关联的EAS中的至少一个也支持第一ACR场景。
在一些实施例中，来自于ECS的EES信息中没有支持第一ACR场景的EES，EEC无法确定出目标EES。
图4中的(b)是本申请实施例提供的EEC通过ECS确定目标EES的方法的又一示意图。在方法400b中，由ECS基于EES支持的ACR场景，选择出支持第一ACR场景的EES，并发送给EEC。方法400b可以包括步骤410b至步骤440b。
在步骤410b中，EEC向ECS发送服务开通请求消息。关于服务开通请求消息的描述可以参见前述步骤410a，此处不再赘述。
可选地，EEC还可以向ECS发送第二信息，该第二信息可以指示以下内容中的至少一项：选择支持第一ACR场景的EES，或者，优选支持第一ACR场景的EES，或者，源EES和/或源EAS无法执行ACR，或者，当前应用无对应的ACR场景。该第二信息例如可以承载在上述服务开通请求消息中。
示例性地，在当前应用无对应的ACR场景，或终端设备与EES协商未确定出ACR场景时，EEC可以向ECS发送第二信息。在当前应用对应的ACR场景为第一ACR场景时，第二信息还可以指示选定的ACR场景为第一ACR场景。
在步骤420b中，在接收到服务开通请求消息后，ECS处理服务开通请求，选择支持第一ACR场景的EES。
收到请求后，可选地，ECS可以进行授权检查，以验证EEC是否具有执行操作的授权。
根据接收到的信息，ECS可以确定需要选择支持第一ACR场景的EES，例如，可以基于来自ECS的第二信息确定需要选择支持第一ACR场景的EES。
可选地，ECS可以根据AC配置信息和/或终端设备位置信息，匹配注册到ECS上的EES，并基于EES所支持的ACR场景，选择支持第一ACR场景的EES。
示例性地，ECS可以选择服务区域中包含该终端设备的位置的EES，或注册的EAS列表中包括匹配AC配置信息中的EAS标识符(EAS ID)的EES，或服务区域中包含该终端设备的位置且注册的EAS列表中包括匹配AC配置信息的EAS ID的EES。在选择出一个或多个EES之后，ECS可以进一步从中确定出支持第一ACR场景的一个或多个EES。或者，ECS可以在选择EES时，增加一个条件，即EES需要支持第一ACR场景。
可选地，ECS可以选择与支持第一ACR场景的EAS所关联的EES，换言之，ECS选择的一个或多个EES支持第一ACR场景，其中各EES所关联的EAS中的至少一个也支持第一ACR场景。
在步骤430b中，ECS向EEC发送服务开通响应消息。
关于服务开通相应消息的具体描述参见前述步骤430a。
ECS选择、确定或识别出支持第一ACR场景的一个或多个EES后，可以在向EEC发送的服务开通响应消息中，通过EES信息指示该一个或多个EES。
在步骤440b中，EEC确定目标EES。
在一些实施例中，EEC接收到的信息指示一个EES，EEC可以将其确定为目标EES。在一些实施例中，EEC接收到的信息指示多个支持第一ACR场景的EES，EEC可以从中确定一个EES作为目标EES。本申请对具体的确定方法不做限定，例如可以是随机确定，或者是基于本地策略确定。
在方法400b中，步骤440b是可选的步骤。
图4中的(a)和图4中的(b)提供了确定目标EES的方法，从EES中确定支持第一ACR场景的EES的步骤可以由ECS执行，从而终端设备不必再进行筛选，可以减少终端设备的负担；该步骤也可以由EEC执行，从而ECS不必基于EES的ACR能力进行筛选，能够减少ECS的负担。
通过步骤310，EEC确定出的目标EES支持第一ACR场景，该EES具有作为目标EES执行ACR的能力，在当前应用的EAS切换时，EEC可以通过该目标EES，顺利完成应用上下文的迁移，从而保证当前应用的业务的连续性。
在步骤320中，EEC请求目标EES执行ACR。
EEC确定目标EES后，可以通过从ECS获取的目标EES的地址，与目标EES建立通信连接，并请求其执行ACR。EEC请求目标EES执行ACR的方法包括发现目标EAS，目标EAS与源EAS之间传输应用上下文等过程。
下文将结合图6，从网元间交互的角度对步骤320进行详细描述。
参看图6，步骤320可以进一步包括步骤610至步骤650。
在步骤610中，EEC可以执行EAS发现流程，确定支持第一ACR场景的目标EAS。
示例性地，EEC确定目标EAS的流程可以如图7中的(a)或图7中的(b)所示。
图7中的(a)是本申请实施例提供的EEC确定目标EAS的方法的示意图。在方法700a中，由EEC基于EAS支持的ACR场景，确定出支持第一ACR场景的目标EAS。方法700a可以包括步骤710a至步骤740a。
在步骤710a中，EEC向目标EES发送EAS发现请求消息。
其中，可选地，EAS发现请求消息可以包括EEC ID以及安全凭据。EAS发现请求消息还可以包括EAS发现过滤器(EAS discovery filter)，EAS发现过滤器可以包括EAS的过滤参数，以便检索有关特定EAS或特定某类EAS(例如，游戏应用程序)的信息。
可选地，EEC还可以向目标EES发送信息指示请求获取EAS的ACR能力。为了便于描述，在本申请的实施例中，称该信息为第六信息，应理解，这不能成为对本申请的限定。
第六信息可以承载在上述EAS发现请求消息中，例如包括在EAS发现过滤器中。在当前应用对应的ACR场景为第一ACR场景时，第六信息还可以指示选定的ACR场景为第一ACR场景。
在步骤720a中，目标EES处理EAS发现请求，确定或识别一个或多个EAS。
在一些实施例中，在接收到EEC发送的EAS发现请求后，目标EES进行授权检验并选择一个或多个EAS。
示例性地，若目标EES确定该EEC被授权可以发现所请求的EAS，则目标EES可以根据提供的EAS发现过滤器和终端设备的位置选择一个或多个EAS。若在EAS发现请求消息中未提供EAS发现过滤器，则目标EES可以基于该目标EES上的终端设备特定业务信息和终端设备位置选择一个或多个EAS，或者，目标EES通过应用边缘计算服务提供商(edge computing service provider，ECSP)策略(例如，仅基于终端设备位置)，选择一个或多个EAS。若目标EES无法通过EAS发现请求消息中携带的信息、目标EES上的终端设备特定业务信息和终端设备的位置、或ECSP策略选择一个或多个EAS，则目标EES可以拒绝该EEC的EAS发现请求，并给出相应的失败原因。
在步骤730a中，目标EES向EEC发送EAS发现响应消息。
若目标EES成功确定或识别一个或多个EAS，则EAS发现响应消息中可以包括EAS信息(可以包括EES确定或识别的EAS的列表，以及EAS配置信息等)，EAS信息可以指示目标EES确定或识别的一个或多个EAS。若目标EES无法确定或识别一个或多个EAS，则EAS发现响应消息可以包括失败指示以及失败原因。
在本申请的实施例中，目标EES还可以向EEC发送信息，指示由目标EES确定或识别的一个或多个EAS中每个EAS的ACR能力，例如EAS所支持的ACR场景。为了便于描述，在本申请的实施例中，称该信息为第五信息，应理解，这不能成为对本申请的限定。该第五信息例如可以承载在上述EAS发现响应消息中，例如包括在EAS信息中。
在一些实施例中，目标EES可以将所有注册或配置在该目标EES上的EAS的信息全部发送 给EEC。此时，前述步骤720a是可选地。
在步骤740a中，EEC从一个或多个EAS中确定支持第一ACR场景的目标EAS。
EEC接收到的信息可以指示一个或多个EAS以及该一个或多个EAS的ACR能力，EEC可以选择支持第一ACR场景的EAS作为目标EAS。
图7中的(b)是本申请实施例提供的EEC确定目标EAS的方法的又一示意图。在方法700b中，由目标EES基于EAS支持的ACR场景，选择出支持第一ACR场景的EAS，并发送给EEC。方法700b可以包括步骤710b至步骤740b。
在步骤710b中，EEC向目标EES发送EAS发现请求消息。
关于EAS发现请求消息的描述可以参见前述步骤710a，此处不再赘述。
可选地，EEC还可以向目标EES发送第六信息，该第六信息可以指示以下内容中的至少一项：选择支持第一ACR场景的EAS，或者，优选支持第一ACR场景的EAS，或者，源EES和/或源EAS无法执行ACR，或者，当前应用无对应的ACR场景。该第六信息例如可以承载在上述服务开通请求消息中。
在当前应用对应的ACR场景为第一ACR场景时，第二信息还可以指示选定的ACR场景为第一ACR场景。在步骤720b中，目标EES处理EAS发现请求，选择支持第一ACR场景的EAS。
目标EES可以确定需要选择支持第一ACR场景的EAS，例如，可以基于来自EEC的第六信息确定需要选择支持第一ACR场景的EAS。
目标EES可以选择出支持第一ACR场景的一个或多个EAS。示例性地，目标EES可以基于前述步骤720a中的方法，选择出一个或多个EAS，并基于该一个或多个EAS的ACR能力，从中确定出支持第一ACR场景的一个或多个EAS。或者，可以在基于前述步骤720a中的方法选择EAS时，增加一个条件，即EAS需要支持第一ACR场景。
在步骤730b中，目标EES向EEC发送EAS发现响应消息。
关于EAS发现响应消息的具体描述参见前述步骤730a。目标EES选择出支持第一ACR场景的一个或多个EAS后，可以在向EEC发送的EAS发现响应消息中，通过EAS信息指示该一个或多个EAS。
在步骤740b中，EEC确定目标EAS。
在一些实施例中，EEC接收到的信息指示一个EAS，EEC可以将其确定为目标EAS。在一些实施例中，EEC接收到的信息指示多个支持第一ACR场景的EAS，EEC可以从中确定一个EAS作为目标EES。本申请对具体的确定方法不做限定，例如可以是随机确定，或者是基于本地策略确定。
在方法700b中，步骤740b是可选的步骤。
方法700a中的步骤740a或方法700b中的步骤740b也可以由AC执行，例如，EEC可以通过层间交互将EAS信息上递给AC，AC可以从EEC接收到的一个或多个EAS中确定目标EAS。
图7中的(a)和图7中的(b)提供了确定目标EAS的方法，从EAS中确定支持第一ACR场景的EAS的步骤可以由目标EES执行，从而终端设备不必再进行筛选，可以减少终端设备的负担；该步骤也可以由终端设备执行，从而目标EES不必基于EAS的ACR能力进行筛选，能够减少目标EES的负担。
通过步骤610，EEC可以发现与目标EES关联的且支持第一ACR场景的EAS，并将其作为目标EAS。该EAS具有作为目标EAS完成ACR的能力，通过该目标EAS，可以顺利完成应用上下文的迁移。
在步骤620中，EEC向目标EES发送ACR请求消息，用于请求目标EES执行以下动作中的至少一项：与目标EAS交互触发目标EAS执行上下文传输，或者，更新用户面路径。
其中，ACR请求也可以称为应用迁移请求(application relocation request)。ACR请求消息中可以携带终端设备的信息，例如终端设备标识、终端设备位置、AC标识等，ACR请求消息还可以携带源EAS的地址(如IP地址或URL地址)，以及当前应用的标识(如应用的域名(fully qualified domain name，FQDN)或统一资源定位符(uniform resource locator，URL))。
目标EES可以基于ACR请求消息，获取源EES的地址以及源EAS的地址。
在步骤630中，目标EES向目标EAS指示向源EAS请求应用上下文，源EAS和目标EAS之间传输应用上下文
目标EES可以向目标EAS发送消息，用于请求迁移EEC所在的终端设备上的当前应用的上下文。相应地，目标EAS可以从目标EES获取源EAS的信息，例如源EAS的地址，以及终端设备的信息。
目标EAS可以通知源EAS发送当前应用的上下文，相应地，目标EAS接收当前应用的上下文。
在一种实现方式中，源EAS可以通过源EES向目标EES传输当前应用的上下文，目标EES将接收到的应用上下文再转给目标EAS。
在步骤640中，目标EAS向目标EES发送ACR完成消息。
目标EAS在完成对终端设备的当前应用的上下文的接收后，确定该应用上下文接收成功，即当前应用的上下文可以在目标EAS重建形成该终端设备的当前应用的客户端可以使用的应用上下文。
目标EAS可以向目标EES发送消息，指示ACT完成，并指示ACT结果。
可选地，源EAS在完成ACT后，也可以向源EES发送应用上下文迁移成功的通知消息。
在步骤650中，在接收到来自目标EAS发送的ACR完成消息后，目标EES向EEC发送ACR完成消息，指示ACT完成。
在接收到来自目标EAS发送的ACR完成消息后，目标EES还可以触发当前应用的用户面路径的更新。目标EES可以触发SMF为终端设备的当前应用插入一条新的用户面路径，以及插入上行数据分流(uplink classifier，UL CL)或分支锚点(branch point，BP)。该步骤也可以由目标EAS触发。
触发当前应用的用户面路径更新的步骤也可以和前述步骤630或640同步执行，例如，可以在目标EES向目标EAS发送用于请求迁移应用上下文的消息之后，或在ACT完成后执行，本申请对此不作限制。
关于执行步骤620至步骤650的具体方法，还可以参照现有技术进行，不再赘述。
基于上述技术方案，在确定目标EES时，终端设备可以指示ECS选择支持第一ACR场景的EES，进而终端设备确定的目标EES能够支持第一ACR场景；ECS也可以将EES的ACR能力发送给终端设备，从而终端设备能选择出支持第一ACR场景的目标EES，如此，终端设备可以通过目标EES顺利执行ACR。终端设备可以指示目标EES选择出支持第一ACR场景的EAS，进而终端设备确定的EAS能够支持第一ACR场景；目标EES也可以向终端设备指示EAS的ACR能力，由终端设备选择出支持第一ACR场景的目标EAS，如此，该EAS能够作为目标EAS完成应用上下文的传输。如此，基于目标EES的ACR流程能够顺利执行，在当前应用的业务在EAS间切换时，应用上下文得以成功迁移，能够保证当前应用的业务的连续性。
终端设备可以在检测到需要进行ACR的事件时，执行方法300。
示例性地，需要进行ACR的事件可以包括以下一项或多项：
终端设备的位置移动出当前连接的EAS的服务区域；
EEC从AC接收到迁移应用上下文的请求；
终端设备检测到当前应用在当前连接的EAS的质量低，例如与当前连接的EAS的连接质量不好，比如延迟大或丢包率大；
EEC接收到来自SMF的新建会话的消息，或EEC收到一个新的IP前缀等。
在本申请的实施例中，使源EAS无法为终端设备提供应用服务的事件，即对应于需要进行ACR的事件。
可选地，EEC可以在确定基于第一ACR场景执行ACR的情况下，通过方法300进行ACR。
在一些实施例中，在终端设备连接至EES时，可以由当前连接的EES确定第一ACR场景为选定的ACR场景，即在有ACR需求时需要基于第一ACR场景进行ACR。当前连接的EES可以向EEC发送信息，指示基于第一ACR场景进行ACR，或者指示选择支持第一ACR场景的EES，或者指示当前应用对应的ACR场景为第一ACR场景。为了便于描述，在本申请的实施例中，称 该信息为第四信息，应理解，这不能成为对本申请的限定。作为一个示例，第四信息可以承载在EES向EEC发送的ACR方案选择通知(ACR scenario selection notification)消息中。
在本申请的实施例中，与终端设备当前连接的EES可以从终端设备获取示终端设备的ACR能力(包括EEC的ACR能力和AC的ACR能力)的信息，该EES可以基于AC，EEC，终端设备当前连接的EES，以及终端设当前连接的EAS(或者终端设备选择的EAS)的ACR能力，确定当前应用所对应的ACR场景。例如确定第一ACR场景作为当前应用对应的ACR场景。与终端设备当前连接的EES可以在终端设备(包括AC和EEC)、与终端设备当前连接的(或者终端选择的)EAS以及与终端设当前连接的EES没有共同支持的ACR场景时，确定第一ACR场景为选定的ACR场景，并向EEC发送第四信息。也可以在与终端设备当前连接的EES可以在终端设备(包括AC和EEC)、与终端设备当前连接的(或者终端选择的)EAS以及该EAS所关联的与终端设当前连接的EES有共同支持的ACR场景时，确定第一ACR场景为选定的ACR场景，并向EEC发送第四信息。
EEC可以通过来自EES的第四信息，确定基于第一ACR场景进行ACR。在一些实施例中，EES也可以向EEC发送信息，指示当前应用无对应的ACR场景，或者指示确定的ACR场景为空，或者指示当前连接的EES或该EES所关联的EAS无法执行ACR。了便于描述，在本申请的实施例中，称该信息为第三信息，应理解，这不能成为对本申请的限定。作为一个示例，第三信息可以承载在EES向EEC发送的ACR方案选择通知(ACR scenario selection notification)消息或EAS信息提供响应(EAS information provisioning response)消息中。
与终端设备当前连接的EES可以在终端设备(包括AC和EEC)、与终端设备当前连接的(或者终端设备选择的)EAS以及该EAS所关联的EES没有共同支持的ACR场景时，向EEC发送第三信息。
EEC可以在接收到来自EES的第三信息后，确定当前应用无对应的ACR场景，并确定第一ACR场景为选定的ACR场景，即在有ACR需求时需要基于第一ACR场景进行ACR。
在一些实施例中，EEC可以从终端设备当前连接的EES接收信息，获取该EES、终端设备当前连接的(或终端设备选择的)EAS所支持的ACR场景，终端设备也可以确定EEC和AC所支持的ACR场景。终端设备可以据此确定当前应用对应的ACR场景。
例如EEC可以在终端设备(包括AC和EEC)、与终端设备当前连接的(或者终端设备选择的)EAS以及该EAS所关联的EES没有共同支持的ACR场景时，确定第一ACR场景为当前应用所对应的ACR场景。或者，EEC也可以在终端设备(包括AC和EEC)、与终端设备当前连接的(或者终端设备选择的)EAS以及该EAS所关联的EES没有共同支持的ACR场景时，确定第一ACR场景为当前应用所对应的ACR场景。
以上内容结合图3至图7详细说明了本申请实施例所提供的应用上下文迁移方法。
下面，结合图8至图11对本申请提供的应用上下文迁移方法的几种可能的实现方式进行描述。
图8是本申请实施例提供的应用上下文迁移方法的一种可能的实现方式。
在本实现方式中，由EEC确定选定的ACR场景为第一ACR场景，由ECS确定支持第一ACR场景的EES，由目标EES确定支持第一ACR场景的EAS。
图8所示的实现方式包括步骤801至步骤814。
步骤801，目标EAS向目标EES发送EAS注册请求消息，EAS注册请求消息中携带该EAS配置信息(包括该EAS支持的ACR场景)。
步骤802，目标EES向目标EAS发送EAS注册响应消息。
步骤801和步骤802所示的目标EAS向目标EES注册的具体方法可以参照图5中的(a)所示的方法执行，此处不再赘述。
步骤803，目标EES向ECS发送发送EES注册请求消息，EES注册请求消息中携带信息指示该EES支持的ACR场景以及该EES所关联的EAS支持的ACR场景。
步骤804，ECS向目标EES发送EES注册响应消息。
步骤803至步骤804所示的目标EES向ECS注册的具体方法可以参照前述图5中的(b)所 示的方法执行，这里不再赘述。步骤801至步骤804是可选的步骤。
应理解，基于上述步骤，源EAS也可以注册到源EES上，源EES也可以注册到ECS上。
步骤805，源EES确定当前应用支持的ACR场景为空。
源EES可以通过与终端设备的连接，获取终端设备支持的ACR场景，例如AC和EEC支持的ACR场景。源EES可以在终端设备、源EES以及源EAS没有共同支持的ACR场景时，确定当前应用支持的ACR场景为空。
步骤806，源EES向EEC发送ACR方案选择通知消息，该消息中可以携带当前应用的AC ID、EAS ID和指示当前应用支持的ACR场景为空的信息。
步骤807，EEC确定选定的ACR场景为第一ACR场景。
EEC基于从源EES接收到的指示当前应用支持的ACR场景为空的信息，可以确定当前应用没有可用的ACR场景，EEC可以确定将第一ACR场景作为当前应用的ACR场景。
其中，步骤805至步骤807是可选的步骤。
步骤808，EEC向ECS发送服务开通请求消息，该消息中携带第二信息，可以指示以下内容中的至少一项：选择支持第一ACR场景的EES，或者，优选支持第一ACR场景的EES，或者，源EES和/或源EAS无法执行ACR，或者，当前应用无对应的ACR场景。
EEC可以在检测到需要进行ACR的事件时，例如，终端设备的位置移动出当前连接的EAS的服务区域时，执行步骤808。
执行步骤808的具体方法可以参照前述步骤410b，这里不再赘述。
步骤809，ECS确定支持第一ACR场景的一个或多个EES。
执行步骤809的具体方法可以参照前述步骤420b，这里不再赘述。
步骤810，ECS向EEC发送服务开通响应消息，该消息中携带的EES信息指示由ECS确定或识别的支持第一ACR场景的一个或多个EES。EEC可以从中选择出目标EES。
执行步骤810的具体方法可以参见前述步骤430b和步骤440b，这里不再赘述。
步骤811，EEC向目标EES发送EAS发现请求消息，该消息中携带第六信息，可以指示以下内容中的至少一项：选择支持第一ACR场景的EAS，或者，源EES和/或源EAS无法执行ACR，或者，当前应用无对应的ACR场景。
执行步骤811的具体方法可以参照前述步骤710b，这里不再赘述。
步骤812，目标EES确定支持第一ACR场景的一个或多个EAS。
执行步骤812的具体方法可以参照前述步骤720b，这里不再赘述。步骤813，目标EES向EEC发送EAS发现响应消息，该消息中携带的EAS信息指示由目标EES确定的支持第一ACR场景的一个或多个EAS。EEC可以从中选择出目标EAS。
执行步骤811的具体方法可以参照前述步骤730b和步骤740b，这里不再赘述。
步骤814，EEC通过目标EES和目标EAS，将当前应用的应用上下文从源EAS传输至目标EAS。
步骤814的具体流程可以参见前述步骤620至步骤650，这里不再赘述。
通过图8所示的方法，在当前应用的ACR场景为空时，源EES可以向EEC指示当前应用的ACR场景为空，进而EEC可以确定基于第一ACR场景进行ACR。在源EAS无法为终端设备提供应用服务时，可以选择出支持第一ACR场景的EES作为目标EES，选择出支持第一ACR场景的EAS作为目标EAS，并通过目标EES执行ACR，从而成功完成应用上下文的迁移，保证应用服务的连续性。
图9是本申请实施例提供的应用上下文迁移方法的又一种可能的实现方式。
在本实现方式中，由源EES确定选定的ACR场景为第一ACR场景，由ECS确定支持第一ACR场景的EES，由目标EES确定支持第一ACR场景的EAS。
图9所示的实现方式包括步骤901至步骤913。
步骤901至步骤904与前述步骤801至步骤804相同，这里不再赘述。
步骤905，源EES确定选定的ACR场景为第一ACR场景。
源EES可以将第一ACR场景确定为当前应用所对应的ACR场景。例如可以在终端设备、源 EES以及源EAS没有共同支持的ACR场景时，确定选定的ACR场景为第一ACR场景。
步骤906，源EES向EEC发送ACR方案选择通知消息，该消息中携带信息指示选择支持第一ACR场景的EES。
步骤907至步骤913与前述步骤808至步骤814相同，这里不再赘述。
图9所示的实现方式取得的效果和图8所示的实现方式取得的效果类似。此外，在图9所示的实现方式中，确定选定的ACR场景为第一ACR场景的步骤由源EES执行，确定支持第一ACR场景的EES的步骤由ECS执行，确定支持第一ACR场景的EAS的步骤由目标EES执行，如此，终端设备不用执行这些步骤，可以减轻终端设备的负担。
图10是本申请提供的应用上下文迁移方法的又一种可能的实现方式。
在本实现方式中，由EEC确定选定的ACR场景为第一ACR场景，由EEC确定支持第一ACR场景的目标EES，由EEC确定支持第一ACR场景的目标EAS。
图10所示的实现方式包括步骤1001至步骤1014。
步骤1001至步骤1007与前述步骤801至步骤807相同，这里不再赘述。
步骤1008，EEC向ECS发送服务开通请求消息。
步骤1009，响应于服务开通请求，ECS向EEC发送服务开通响应消息，该消息中携带的EES信息指示一个或多个EES，该消息中还携带信息指示该一个或多个EES所支持的ACR场景，该消息中携带的信息还指示与EES关联的EAS所支持的ACR场景。
步骤1010，EEC基于服务开通响应消息中携带的信息，从一个或多个EES中确定出支持第一ACR场景的EES作为目标EES。
步骤1008至步骤1010的更具体的描述可以参见前述步骤410至步骤440，这里不再赘述。
步骤1011，EEC向目标EES发送EAS发现请求消息。
步骤1012，响应于EAS发现请求消息，目标EES向EEC发送EAS发现响应消息，该消息中携带的EAS信息指示一个或多个EAS，该消息中还携带指示该一个或多个EAS支持的ACR场景的信息。
步骤1013，EEC基于EAS发现响应消息中携带的信息，从一个或多个EAS中确定出支持第一ACR场景的EAS作为目标EAS。
步骤1011至步骤1013的更具体的描述可以参加前述步骤710至步骤740，这里不再赘述。
步骤1014，EEC通过目标EES和目标EAS，将当前应用的应用上下文从源EAS传输至目标EAS。
步骤1014的具体流程可以参见前述步骤620至步骤650，这里不再赘述。
图10所示的实现方式取得的效果和图8所示的实现方式取得的效果类似。此外，在图10所示的实现方式中，确定选定的ACR场景为第一ACR场景的步骤，确定支持第一ACR场景的目标EES的步骤，以及确定支持第一ACR场景的EAS的步骤均由EEC执行，如此，源EES、ECS和目标EES不用执行这些步骤，可以减轻源EES、ECS和目标EES的负担。
图11是本申请提供的应用上下文迁移方法的又一种可能的实现方式。
在本实现方式中，由源EES确定选定的ACR场景为第一ACR场景，由EES确定支持第一ACR场景的目标EES，由EEC确定支持第一ACR场景的目标EAS。
图11所示的实现方式包括步骤1101至步骤1113。
其中，步骤1101至步骤1106与前述步骤901至步骤906相同，步骤1107至步骤1113与前述步骤1008至步骤1014相同，这里不再赘述。
图11所示的实现方式取得的效果和图8所示的实现方式取得的效果类似。
在本申请的实施例中，确定选定的ACR场景为第一ACR场景的步骤可以由源EES执行，也可以由EEC执行。确定支持第一ACR场景的EES的步骤可以由EEC执行，也可以由ECS执行。确定支持第一ACR场景的EAS的步骤可以由EEC执行，也可以由目标EES执行。可以根据各实体的负载能力，确定具体执行上述步骤的实体，从而使系统负载均衡，以顺利实现应用上下文的传输。
应理解，图8至图11所示的实现方式仅为本申请实施例所提供的方法的示例，不能成为对本 申请的限制，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。
在本申请的实施例中，EES上还可以保存有EEC上下文，该EEC上下文可以是EEC向EES注册时EES获取、生成或创建的，也可以是预配置的，也可以是EES通过EEC上下文传输流程从另一个EES上获取的(例如目标EES可以从源EES获取EEC上下文)，本申请对此不作限定。
作为示例，下面结合图12对EEC注册流程进行说明。
参看图12，EEC注册流程可以包括步骤1210至步骤1240。
在步骤1210中，EEC向EES发送EEC注册请求消息。
EEC注册请求包括在边缘计算服务成功授权后接收的安全凭据，还可以包括建议的到期时间。可选地，该请求还可以包括向EES指示EEC期望如何使用EES的服务的信息。如果EEC从另一个EES(以源EES为例)的权限移动到此EES，则来自EEC的请求可以包括源EES的标识和端点，以及由源EES提供的EEC上下文ID，以保持EEC上下文并授权EEC上下文的重新定位。
在步骤1220中，EES接收到EEC的注册请求后，验证注册请求并验证安全凭据。
EES可以确定是否可以满足AC配置文件中指出的要求。
在步骤1230中，在成功验证请求后，如果接收到的EEC注册请求包含EEC上下文ID、源EES的EES ID和EES端点，EES可以从源EES检索EEC的上下文。否则，跳过此步骤。
在步骤1240中，EES向EEC发送注册响应消息。
若注册成功，EES发送注册成功响应，其中包括注册ID，并可能包括新分配的EEC上下文ID。EEC存储新的EEC上下文ID，并在向另一个EES注册时使用它。EES还可以提供到期时间，以向EEC指示注册何时自动到期。为维持注册，EEC应在到期前发送注册更新请求。如果在到期时间之前没有收到注册更新请求，EES应将EEC视为隐式注销。
若注册失败，EES发送注册失败响应，并给出失败原因。
图12所示的流程的具体步骤还可以参照现有技术进行，不再赘述。
在本申请实施例所提供的方法中，在ACR过程中，源EES和目标EES还可以进行EEC上下文的传输。
EEC上下文的传输可以通过EEC上下文拉取(EEC context push)流程或EEC上下文推送(EEC context pull)流程进行。
下面结合图13中的(a)和图13中的(b)，对EEC上下文传输流程进行示意性地说明。
图13中的(a)是本申请实施例提供的EEC上下文拉取流程的示意图。参看图13中的(a)，EEC上下文拉取流程可以包括步骤1310a至步骤1330a。
在步骤1310a中，目标EES向源EES发送EEC上下文拉取请求消息，向源EES请求EEC上下文。该请求消息中可以包括EEC上下文ID。
在步骤1320a中，源EES接收到来自目标EES的EEC上下文拉取请求消息后，验证请求并验证请求者的安全凭据。源EES使用请求消息中的EEC上下文ID来标识和授权要重新定位的EEC上下文。
在步骤1330a中，源EES向目标EES发送EEC上下文拉取响应消息。目标EES从源EES接收EEC上下文并存储该EEC上下文。
图13中的(b)是本申请实施例提供的EEC上下文推送流程的示意图。参看图13中的(b)，EEC上下文推送流程可以包括步骤1310b至步骤1330b。
在步骤1310b中，源EES决定将EEC上下文转发到目标EES以进行重定位。源EES确定要转发的目标EES和EEC上下文。
在步骤1320b中，源EES向目标EES发送EEC上下文推送请求消息，该请求消息中包括确定的EEC上下文。
在步骤1330b中，目标EES收到源EES的请求后，验证请求并验证安全凭据。目标EES使用提供的EEC上下文ID来授权存储和管理EEC上下文。之后，目标EES向源EES发送EEC上下文推送响应消息，指示成功接收EEC上下文。
关于图13中的(a)和图13中的(b)所示的流程的具体步骤可以参照现有技术进行，不再 赘述。
在ACR过程中，源EES和目标EES可以进行EEC上下文的传输，示例性地，可以在执行前述步骤630的同时执行如图13中的(a)所示的EEC上下文拉取流程或如图13中的(b)所示的EEC上下文推送流程。应理解，本申请不限定进行EEC上下文传输流程的具体时间，源EES和目标EES之间的EEC上下文传输也可以在前述步骤630之前执行，或在前述步骤630之后执行。
为了能够实现EEC的上下文传输，需要源EES和目标EES具有EEC上下文传输能力，即在源EES和目标EES具有共同支持的EEC上下文传输流程时，才能通过相应的流程进行EEC上下文传输。例如，当源EES和目标EES共同支持EEC上下文推送流程时，源EES和目标EES之间可以通过如图13中的(b)所示的流程进行EEC上下文传输；当源EES支持EEC上下文推送流程但目标EES不支持EEC上下文推送流程时，源EES和目标EES之间不能通过EEC上下文推送流程进行EEC上下文传输。
在本申请的实施例中，目标EES具有(或支持)与源EES对应的EEC上下文传输能力，或目标EES与源EEC具有(或支持)对应的EEC上下文传输能力，是指，在目标EES支持的EEC上下文传输流程与源EES支持的上下文传输流程中，存在相同的EEC上下文传输流程。例如，目标EES与源EES均支持EEC上下文推送流程(目标EES与源EES支持EEC上下文推送的API)，或，目标EES与源EES均支持EEC上下文拉取流程(目标EES与源EES支持EEC上下文推送的API)。
目标EES与源EES均支持EEC上下文推送流程，包括源EES支持发送EEC上下文推送请求消息，目标EES支持发送EEC上下文推送响应消息。
目标EES与源EES均支持EEC上下文拉取流程，包括目标EES支持发送EEC上下文拉取请求消息，源EES支持发送EEC上下文拉取响应消息。
在ACR过程中，若确定出的目标EES与源EES没有共同支持的EEC上下文传输方案，就不能在ACR过程中进行EEC上下文传输。从而可能会影响业务的连续性。
在当应用对应的ACR场景为空时，且终端设备通过ECS获取到的目标EES不支持第一ACR场景时，仍然需要应用上下文迁移，用于保证应用的连续性，然而可能目标EES并不具备与源EES对应的EEC上下文传输能力，此时目标EES上没有EEC的相关信息，可能会导致目标EES无法为终端设备提供后续的边缘计算服务。
为此，本申请实施例还提供了一种EEC上下文传输方法，在ACR过程中，在源EES支持EEC上下文传输时，选择出与源EES支持相应EEC上下文传输流程的目标EES，从而在ACR过程中能够基相应的EEC上下文传输流程实现EEC上下文传输；在源EES不支持EEC上下文传输，或目标EES不具有与源EES对应的EEC上下文传输能力时，EEC在ACR完成后向目标EES重新注册。
如此，目标EES能够获取到EEC的上下文，从而能够为该EEC提供可在边缘计算服务中使用的信息。进而目标EES能够为终端设备提供后续的边缘计算服务，能够保障业务的连续性。
下面结合图14至图16说明本申请实施例提供的EEC上下文传输方法。
图14是本申请实施例提供的EEC上下文传输方法的示意性流程图。图14所示的方法从终端设备的角度示出了本申请实施例提供的方法。该方法可以由终端设备执行，也可以由终端设备在中的部件(如电路、芯片、芯片系统等)执行，可以通过软件和/或硬件的方式实现。本申请对此不作限定。下面以配置于终端设备的EEC为例进行描述。
示例性地，如图14所示，EEC上下文传输方法1400可以包括步骤1410和步骤1420。
在步骤1410中，获取源EES的EEC上下文传输能力。
EEC可以从源EES获取源EES的上下文传输能力。例如，在源EES与EEC连接时，源EES可以在向EEC发送的ACR方案选择通知消息中携带源EES支持的API信息，指示源EES的EEC上下文传输能力。
示例性地，可以指示源EES是否支持EEC上下文传输，或指示源EES是否支持EEC上下文拉取流程，或指示源EES是否支持EEC上下文推送流程。
在步骤1420中，确定目标EES，该目标EES基于源EES的EEC上下文传输能力确定。
源EES支持EEC上下文传输时，
源EES可以向EEC发送信息，指示EEC，在进行ACR时，需要选择支持相应EEC上下文传输能力的目标EES。示例性地，若源EES支持EEC上下文拉取流程，源EES可以向EEC指示，在进行ACR时，需要选择支持EEC上下文拉取流程的目标EES。
相应地，EEC可以基于来自于源EES的信息，确定需要选择支持相应的EEC上下文传输能力的目标EES。
EEC可以通过ECS，基于源EES支持的EEC上下文传输流程，选择支持相同EEC上下文传输流程的目标EES。
源EES不支持EEC上下文传输时，源EES可以向EEC发送信息，指示EEC，在进行ACR时，可以选择不支持EEC上下文传输的目标EES。源EES还可以向EEC指示，在进行ACR后需要重新向目标EES注册。
相应地，EEC可以基于来自于源EES的信息，确定可以选择不支持EEC上下文传输的目标EES。EEC也可以确定在ACR后需要重新向目标EES注册。
EEC可以通过ECS，选择出目标EES，该目标EES不必支持EEC上下文传输。可以通过服务开通流程或者EES发现流程，确定目标EES。
示例性地，选择目标EES的方法可以如图15中的(a)或如图15中的(b)所示。
参看图15中的(a)，在方法1500a中，由EEC基于源EES支持的EEC上下文传输流程，选择出目标EES。方法1500a可以包括步骤1510a至步骤1540a。
在步骤1510a中，EEC可以向ECS发送服务开通请求消息。
步骤1510a的具体实施方法可以参见前述步骤410a或前述步骤410b。
在本申请的实施例中，EEC还可以向EES发送第一请求信息，该第一请求信息用于指示以下至少一项：请求获取EES的EEC上下文传输能力，或者，源EES支持EEC上下文传输。
示例性的，当EEC确定应用对应的ACR场景为空(以及其他的情况)，EEC确定需要基于第一ACR场景执行ACR。EEC可以向ECS发送第一请求信息，用于请求ECS发送EES支持的API能力，或者用于请求ECS发送EES支持的EEC上下文传输能力，或者用于请求ECS发送EES是否支持EEC上下文拉取流程，或者用于请求ECS发送EES是否支持EEC上下文推送流程。
可选地，在步骤1520a中，ECS处理服务开通请求，识别一个或多个EES。
步骤1520a的具体实施方法可以参见前述步骤420a，也可以参见前述步骤420b。例如，ECS识别的一个或多个EES可以是支持第一ACR场景的EES。
在步骤1530a中，ECS向EEC发送服务开通响应消息，以及指示EES的EEC上下文传输能力的信息，例如EES支持的API能力，或者，EES是否支持EEC上下文传输，或者，EES支持的EEC上下文传输流程，或者，EES是否支持EEC上下文拉取流程，或者，EES是否支持EEC上下文推送流程。该信息例如可以承载在服务开通请求响应消息中。
ECS可以获取指示EES的EEC上下文传输能力的信息，该信息可以是EES向ECS注册时ECS获取的，也可以是ECS通过网关系统获取的，也可以是预配置的。示例性地，在前述图5中的(b)所示的EES向ECS注册的流程中，EES可以向ECS发送EES支持的API信息，例如可以指示EES的EEC上下文传输能力。该信息可以携带在EES注册请求消息中。
步骤1530a的具体实施方法可以参见前述步骤430a，也可以参见前述步骤430b。
在一些实施例中，ECS可以将所有注册或配置在ECS上的EES的信息全部发送给EEC。此时，前述步骤1520a是可选地。
在步骤1540a中，EEC从一个或多个EES中确定具有与源EES对应的EEC上下文传输能力的目标EES。
EEC接收到的信息可以指示EES的EEC上下文传输能力。
当源EES支持EEC上下文传输时，EEC可以选择支持对应的EEC上下文传输流程的EES作为目标EES。例如，若源EES仅支持EEC上下文拉取流程，则目标EES需要支持EEC上下文拉取流程；若源EES仅支持EEC上下文推送流程，则目标EES需要支持EEC上下文推送流程；若 源EES既支持EEC上下文拉取流程，又支持EEC上下文推送流程，则目标EES可以仅支持EEC上下文拉取流程，也可以仅支持EEC上下文推送流程。
当源EES不支持EEC上下文传输时，EEC在选择EES时可以不考虑EES的EEC上下文传输能力。
在一些实施例中，源EES支持EEC上下文传输，ECS向EEC指示的一个或多个EES中没有与源EES支持对应的EEC上下文传输能力的EES，或者，ECS向EEC指示的一个或多个EES不具备EEC上下文传输能力，则EEC选择的目标EES可以与源EES具有不同的EEC上下文传输能力，或EEC选择的目标EES可以不具备EEC上下文传输能力。EEC可以确定在ACR后需要重新向目标EES注册。
图15中的(b)是本申请实施例提供的确定目标EES的又一方法的示意图。
参看图15中的(b)，在方法1500b中，由ECS基于源EES支持的EEC上下文传输能力，选择出支持对应EEC上下文传输能力的EES。方法1500b可以包括步骤1510b至步骤1540b。
在步骤1510b中，EEC向ECS发送服务开通请求消息。
EEC可以向ECS发送信息指示源EES的EEC上下文传输能力，该信息例如可以承载在服务开通请求消息中。
例如，若源EES支持EEC上下文拉取流程，EEC可以向ECS发送信息指示源EES支持EEC上下文拉取流程；若源EES支持EEC上下文推送流程，EEC可以向ECS发送信息指示源EES支持EEC上下文推送流程。
EEC还可以向ECS发送信息，指示以下至少一项：需要选择具有EEC上下文传输能力的EES，或者，需要选择具有与源EES对应的EEC上下文传输能力的EES，或者，优选具有与源EES对应的EEC上下文传输能力的EES。
例如，若源EES仅支持EEC上下文拉取流程，则EEC可以向ECS发送信息，指示需要选择支持EEC上下文拉取流程的EES。若源EES仅支持EEC上下文推送流程，则EEC可以向ECS发送信息，指示需要选择支持EEC上下文推送流程的EES；若源EES既支持EEC上下文拉取流程，又支持EEC上下文推送流程，则EEC可以向ECS发送信息，指示可以选择支持EEC上下文拉取流程的EES，也可以选择仅支持EEC上下文推送流程的EES。
EEC向ECS发送服务开通请求消息的具体实施方式可以参见前述步骤410a，也可以参见前述步骤410b。
在步骤1520b中，ECS处理服务开通请求，选择具有与源EES相同的EEC上下文传输能力的EES。
步骤1520b可以参照前述步骤420a或420b进行。
在本申请的实施例中，若源EES支持EEC上下文传输，ECS可以选择与源EES支持对应的EEC上下文传输流程的EES。
例如，若来自EEC的信息指示源EES仅支持EEC上下文拉取流程，则ECS选择支持EEC上下文拉取流程的EES。若来自EEC的信息源EES仅支持EEC上下文推送流程，则ECS选择支持EEC上下文推送流程的EES；若来自EEC的信息源EES既支持EEC上下文拉取流程，又支持EEC上下文推送流程，则ECS可以选择支持EEC上下文拉取流程的EES，也可以选择仅支持EEC上下文推送流程的EES。
可选地，可以在执行前述步骤420a或在执行前述步骤420b，选择出一个或多个EES后，基于该一个或多个EES所支持的EEC上下文传输能力，选择出与源EES支持对应的EEC上下文传输能力的EES。或者，在执行前述步骤420a或步骤420b，选择一个或多个EES时，增加一个条件，即选择的EES需要与源EES支持对应的EEC上下文传输能力。应理解，本申请对选择的顺序不作限制。在一些实施例中，注册在ECS上或配置在ECS上的EES中，没有EES与源EES支持相同的EEC上下文传输流程，或者，来自EEC的信息指示源EES没有EEC上下文传输能力，则ECS在选择EES时可以不考虑EES所支持的EEC上下文传输能力。
在步骤1530b中，ECS向EEC发送服务开通响应消息。
在一些实施例中，ECS确定出一个或多个具有与源EES对应的EEC上下文传输能力的EES， ECS可以向EEC发送信息指示该一个或多个EES，该信息可以承载在服务开通响应消息中。
可选地，ECS可以向EEC发送信息，指示不需要在ACR后重新向目标EES注册。该信息可以承载在服务开通响应消息中。
在一些实施例中，注册在ECS上或配置在ECS上的EES中，没有EES与源EES支持对应的EEC上下文传输流程，或者没有EES具有EEC上下文传输能力，或者，来自EEC的信息指示源EES没有EEC上下文传输能力。ECS可以向EEC发送信息，指示需要在ACR后重新向目标EES注册。该信息可以承载在服务开通响应消息中。步骤1530b的具体实施方法可以参照前述步骤430a或430b。
步骤1540b，EEC从ECS指示的一个或多个EES中确定目标EES。
在一些实施例中，ECS指示的一个或多个EES不具有与源EES对应的EEC上下文传输能力，或指示的一个或多个EES不具有EEC上下文传输能力，EEC可以确定在ACR后需要重新向目标EES注册。
关于步骤1540b的具体实施方法，可以参照前述步骤440a或440b进行，不再赘述。
在方法1500b中，步骤1540b是可选的步骤。
图15中的(a)和图15中的(b)提供了步骤1420中确定目标EES的方法，从EES中选择与源EES具有相同EEC上下文传输能力的EES的步骤可以由ECS执行，从而终端设备不必再进行筛选，可以减少终端设备的负担；该步骤也可以由EEC执行，从而ECS不必基于EES的EEC上下文传输能力进行筛选，能够减少ECS的负担。
通过步骤1420，可以确定出确定出与源EES具有相同EEC上下文传输能力的目标EES，在ACR的过程中，源EES可以和该目标EES完成EEC上下文的传输。在确定出的目标EES与源EES不具有相同EEC上下文传输能力，或源EES不支持EEC上下文传输时，EEC能够获得向目标EES重新注册的指示，EEC可以基于该指示，在ACR完成后向目标EES重新注册，从而使目标EES获得EEC上下文。
可选地，方法1400还可以包括：确定是否执行EEC上下文传输。
示例性地，图16中的(a)和图16中的(b)给出了确定是否执行EEC上下文传输的两种方法。
在方法1600a中，由目标EES确定是否可以执行EEC上下文传输。方法1600a包括步骤1610a至步骤1630a。
在步骤1610a中，EEC可以向目标EES发送信息，指示源EES的EEC上下文传输能力。例如，可以指示以下内容中的至少一种：源EES支持的API能力，或者，源EES支持EEC上下文传输流程，或者，源EES是否支持EEC上下文拉取流程，或者，源EES是否支持EEC上下文推送流程。应理解，本申请对此不作限定。
在步骤1620a中，目标EES接收到来自EEC的信息后，可以基于该信息确定是否可以执行EEC上下文传输。
若确定目标EES与源EES支持相应的EEC上下文传输流程，例如，源EES与目标EES均支持EEC上下文拉取流程和/或源EES与目标EES均支持EEC上下文推送流程。则可以确定能够与源EES进行EEC上下文传输。目标EES还可以确定，EEC在ACR后不需要重新向目标EES注册。
若确定目标EES与源EES不支持相应的EEC上下文传输流程，或源EES不支持EEC上下文传输，或目标EES不支持EEC上下文传输，目标EES还可以确定，EEC在ACR后需要重新向目标EES注册。
在步骤1630a中，目标EES向EEC发送指示信息，指示在ACR后EEC是否需要重新向目标EES注册。
若确定目标EES与源EES支持对应的EEC上下文传输能力，目标EES可以向EEC发送指示信息，指示在ACR后不需要重新向目标EES注册。
若确定目标EES与源EES不支持相同的EEC上下文传输流程，或源EES不支持EEC上下文传输，或目标EES不支持EEC上下文传输，目标EES可以向EEC发送指示信息，指示在ACR 后需要重新向目标EES注册。
EEC和目标EES可以在执行前述步骤610中的EAS发现流程时，执行方法1600a。示例性地，步骤1610a中，EEC向目标EES发送的信息可以承载在EAS发现请求消息中，步骤1630a中的指示信息可以承载在EAS发现响应消息中。
在方法1600b中，由EEC确定是否可以执行EEC上下文传输。方法1600b包括步骤1610b至步骤1630b。
在步骤1610b中，EEC向目标EES发送请求信息，该请求信息可以指示以下至少一项：请求获取目标EES的EEC上下文传输能力，或者，源EES支持EEC上下文传输。
在步骤1620b中，响应于来自EEC的请求，目标EES向EEC发送信息，指示目标EES的EEC上下文传输能力。例如，在目标EES支持EEC上下文拉取流程时，可以指示目标EES支持EEC上下文拉取流程；在目标EES支持EEC上下文推送流程时，可以指示目标EES支持EEC上下文推送流程；在目标EES不支持EEC上下文传输能力时，可以指示目标EES不支持EEC上下文传输能力；在目标EES具有EEC上下文传输能力时，可以指示目标EES具有EEC上下文传输能力。
在步骤1630b中，EEC基于目标EES的EEC上下文传输能力，确定是否可以执行EEC上下文传输能力。
若目标EES与源EES支持对应的EEC上下文传输能力，则可以确定目标EES能够与源EES进行EEC上下文传输。EEC可以确定在ACR后不需要重新向目标EES注册。
若确定目标EES与源EES不支持对应的EEC上下文传输能力，或源EES不支持EEC上下文传输，或目标EES不支持EEC上下文传输，则EEC可以确定目标EES不能够与源EES进行EEC上下文传输，EEC还可以确定在ACR后需要重新向目标EES注册。
EEC和目标EES可以在执行前述步骤610中的EAS发现流程时，执行方法1600b。示例性地，步骤1610b中，EEC向目标EES发送的信息可以承载在EAS发现请求消息中，步骤1620b中目标EES向EEC发送的信息可以承载在EAS发现响应消息中。
应理解，本申请不限制在ACR过程中执行方法1400中各步骤的具体时间。
在执行步骤方法1600a或方法1600b时，前述步骤1420是可选地，也就是说，可以通过前述步骤1420的方法确定目标EES，也可以通过前述步骤310中的方法确定目标EES，也可以通过现有技术中的方法确定目标EES。
终端设备可以通过方法1400确定出目标EES，并进行ACR。在ACR过程中，源EES和目标EES可以进行EEC上下文传输，或者，EEC可以在ACR后向目标EES重新注册。
在一些实施例中，源EES和目标EES支持相同的EEC上下文传输能力，源EES和目标EES之间可以在ACR过程中进行EEC上下文传输，例如在执行前述步骤630时进行EEC上下文传输。
示例性地，源EES和目标EES共同支持EEC上下文推送流程，源EES和目标EES之间可以通过如图13中的(b)所示的过程进行EEC上下文传输。源EES和目标EES共同支持EEC上下文拉取过程，源EES和目标EES之间可以通过如图13中的(a)所示的过程进行EEC上下文传输。
在一些实施例中，源EES和/或目标EES不支持EEC上下文传输，或者源EES与目标EES不具有对应的EEC上下文传输能力。EEC可以在ACR后向目标EES注册，EEC向目标EES注册的方法可以参见前述图12中的方法，此处不再赘述。
基于上述技术方案，在确定目标EES时，EEC可以指示ECS选择与源EES支持对应的EEC上下文传输能力的EES，进而EEC确定的目标EES能够与源EES传输EEC上下文；ECS也可以将EES的EEC上下文传输能力指示给EEC，从而EEC能选择出与源EES支持对应的EEC上下文传输能力的目标EES，如此，在ACR过程中，源EES与目标EES能够顺利进行EEC上下文传输。在源EES不支持EEC上下文传输，或目标EES不支持EEC上下文传输，或源EES与目标EES不具有对应的EEC上下文传输能力时，EEC可以基于指示重新向目标EES注册，从而目标EES够获取到EEC的上下文，能够为该EEC提供可在边缘计算服务中使用的信息。进而目标EES 能够为终端设备提供后续的边缘计算服务，能够保障业务的连续性。
作为示例，下面结合图17和图18对本申请实施例提供的EEC上下文传输的方法的几种可能的实现方式进行描述。
图17是本申请实施例提供的EEC上下文迁移方法的一种可能的实现方式。在图17所示的方法中，确定支持与源EES对应的EEC上下文传输能力的EES的步骤可以由ECS执行，确定源EES与目标EES是否具有对应的EEC上下文传输能力的步骤可以由目标EES执行。参看图17，该方法包括步骤1701至步骤1710。
步骤1701，目标EES向ECS发送EES注册请求消息，EES注册请求消息中携带信息指示该EES的EEC上下文传输能力。
步骤1702，ECS向目标EES发送EES注册响应消息。
步骤1701和步骤1702所示的目标EES向ECS注册的具体方法可以参照前述图5中的(b)所示的方法执行，这里不再赘述。
步骤1701和步骤1702是可选的步骤。
应理解，基于上述步骤，源EES也可以注册到ECS上。基于注册过程，ECS可以确定源EES和/或目标EES的EEC上下文传输能力。
步骤1703，源EES向EEC发送ACR方案选择通知消息，该消息中可以携带当前应用的AC ID、EAS ID和指示源EES的EEC上下文传输能力的信息。
可选地，EEC或源EES可以确定ACR场景。
执行步骤1703的具体方法可以参见前述步骤1410，这里不再赘述。
步骤1704，EEC向ECS发送服务开通请求消息，该消息中携带信息，可以指示以下内容中的至少一项：需要选择具有EEC上下文传输能力的EES，或者，需要选择具有与源EES对应的EEC上下文传输能力的EES，优选具有与源EES对应的EEC上下文传输能力的EES。
步骤1705，ECS确定支持与源EES对应的EEC上下文传输能力的EES。
步骤1705的具体实现方式参见前述步骤1520b，这里不再赘述。
步骤1706，ECS向EEC发送服务开通响应消息，该消息中可以携带信息，指示一个或多个具有与源EES对应的EEC上下文传输能力的EES。EEC可以从中确定出目标EES。
可选地，若ECS确定出的EES不具有与原EES对应的EEC上下文传输能力，该消息中可以携带信息指示需要重新向目标EES注册。
步骤1706的具体实现方式可以参见前述步骤1530b，这里不再赘述。
步骤1707，EEC向目标EES发送信息指示源EES的EEC上下文传输能力。
步骤1707的具体实现方式可以参见前述步骤1610a，这里不再赘述。
步骤1708，目标EES确定源EES与目标EES是否具有对应的EEC上下文传输能力。
步骤1708的具体实现方式可以参见前述步骤1620a，这里不再赘述。
步骤1709，目标EES向EEC发送注册指示信息，指示是否需要重新向目标EES注册。
步骤1708的具体实现方式可以参见前述步骤1630a，这里不再赘述。
步骤1710中，目标EES与源EES传输EEC上下文，或EEC向目标EES注册。
若目标EES与源EES支持对应的EEC上下文传输能力，目标EES可以与源EES通过共同支持的EEC上下文传输流程进行EEC上下文传输，具体实现方式可以参照图13中的(a)或图13中的(b)进行，这里不再赘述。
若目标EES与源EES不支持对应的EEC上下文传输能力，或源EES不支持EEC上下文传输，或目标EES不支持EEC上下文传输，则EEC可以重新向目标EES注册，从而目标EES可以获取EEC上下文，具体实现方式可以参照图12进行，这里不再赘述。
应理解，在通过步骤1704至步骤1706的方法确定目标EES时，步骤1707至步骤1709是可选地步骤。在执行步骤1707至步骤1709时，步骤1704至步骤1706是可选的步骤，也就是说，可以采用其他方法确定目标EES，例如基于前述步骤310中的方法确定目标EES，或基于现有技术确定目标EES。
还应理解，在步骤1703中，若源EES向EEC发送的信息指示源EES不支持EEC上下文传 输，则EEC可以确定需要重新向目标EES注册，此时步骤1704至步骤1709是可选的步骤，在步骤1710中，EEC向目标EES注册，目标EES获取EEC上下文。
如此，目标EES能够获取到EEC上下文，从而能够为该EEC提供可在边缘计算服务中使用的信息。进而目标EES能够为终端设备提供后续的边缘计算服务，能够保障业务的连续性。
图18是本申请实施例提供的应用上下文迁移方法的又一种可能的实现方式。在图18所示的方法中，确定支持与源EES对应的EEC上下文传输能力的目标EES的步骤可以由EEC执行，确定源EES与目标EES是否具有对应的EEC上下文传输能力的步骤可以由目标EEC执行。参看图18，该方法包括步骤1801至步骤1810。
步骤1801至步骤1803的实现方式与前述步骤1701至步骤1703的实现方式相同，这里不再赘述。
步骤1804，EEC向ECS发送服务开通请求消息，该消息中携带信息，指示以下至少一项：请求获取EES的EEC上下文传输能力，或者，源EES支持EEC上下文传输。
步骤1804的具体实现方式可以参照前述步骤1510a，这里不再赘述。
步骤1805，ECS向EEC发送服务开通响应消息，该消息中可以携带信息，指示一个或多个EES以及该一个或多个EES的EEC上下文传输能力。
步骤1805的具体实现方式可以参照前述步骤1520a和前述步骤1530a，这里不再赘述。
步骤1806，EEC确定支持与源EES对应的EEC上下文传输能力的目标EES。EEC可以基于EES的EEC上下文传输能力，从ECS所指示的一个或多个EES中选择与源EES支持对应EEC上下文传输能力的EES，将其作为目标EES。
步骤1805的具体实现方式可以参照前述步骤1540a，这里不再赘述。
步骤1807，EEC向目标EES发送请求信息，指示以下至少一项：请求获取目标EES的EEC上下文传输能力，或者，源EES支持EEC上下文传输。
步骤1808，目标EES向EES发送信息，指示目标EES的EEC上下文传输能力。
步骤1808的具体实现方式可以参照前述步骤1620b，这里不再赘述。
步骤1809，EEC确定源EES与目标EES是否具有对应的EEC上下文传输能力。
步骤1809的具体实现方式可以参照前述步骤1630b，这里不再赘述。
步骤1810，目标EES与源EES传输EEC上下文，或EEC向目标EES注册。
若目标EES与源EES支持对应的EEC上下文传输能力，目标EES可以与源EES通过共同支持的EEC上下文传输流程进行EEC上下文传输，具体实现方式可以参照图13中的(a)或图13中的(b)进行，这里不再赘述。
若目标EES与源EES不支持对应的EEC上下文传输能力，或源EES不支持EEC上下文传输，或目标EES不支持EEC上下文传输，则EEC可以重新向目标EES注册，从而目标EES可以获取EEC上下文，具体实现方式可以参照图12进行，这里不再赘述。
应理解，在通过步骤1804至步骤1806的方法确定目标EES时，步骤1807至步骤1809是可选地步骤。在执行步骤1807至步骤1809时，步骤1804至步骤1806是可选的步骤，也就是说，可以采用其他方法确定目标EES，例如基于前述步骤310中的方法确定目标EES，或基于现有技术确定目标EES。
还应理解，在步骤1803中，若源EES向EEC发送的信息指示源EES不支持EEC上下文传输，则EEC可以确定需要重新向目标EES注册，此时步骤1804至步骤1809是可选的步骤，在步骤1810中，EEC向目标EES注册，目标EES获取EEC上下文。
如此，目标EES能够获取到EEC上下文，从而能够为该EEC提供可在边缘计算服务中使用的信息。进而目标EES能够为终端设备提供后续的边缘计算服务，能够保障业务的连续性。
应理解，图17和图18中的各步骤可以组合实施，示例性地，在执行步骤1704至步骤1706之后，可以执行步骤1807至步骤1809；或者，在执行步骤1804至步骤1806之后，可以执行步骤1707至步骤1709。本申请对此不作限制。
还应理解，本申请实施例所提供的EEC上下文传输方法可以结合前述图3至图11中所述的ACR方法进行实施，具体步骤可以参见前述图3至图11中的描述，本申请对此不作限定。
以上内容，结合图3至图18详细说明了本申请实施例所提供的方法，接下来，结合图19和图20说明本申请实施例提供的装置。
参看图19，图19是本申请实施例提供的通信装置的示意性框图，如图19所示，该通信装置可以包括处理单元1910和收发单元1920。
可选地，上述通信装置1900可以对应于前文方法实施例中的终端设备(包括EEC或AC)，例如，可以为终端设备，或配置在终端设备中的部件(如芯片、芯片系统、处理器等)，或者，还可以为能够实现全部或部分终端设备功能的逻辑模块或软件。本申请实施例对此不作限定。
该装置1900与终端设备对应时，可用于执行前文图3至图18所示的方法中终端设备所执行的步骤，例如执行EEC所执行的步骤。该通信装置1900可以包括用于执行前文图3至图18所示出的方法中的终端设备(包括EEC)执行的方法的单元。并且，该通信装置1900中的各单元和上述其他操作和/或功能分别为了实现图3至图18所示的方法中的相应流程。
作为一个示例，处理单元1910用于确定目标EES，该目标EES为支持为支持第一ACR场景的EES，第一ACR场景为由目标EES执行ACR的场景。收发单元1920用于请求目标EES执行ACR。
在一些实施例中，收发单元1920还用于从ECS接收EES信息，该EES信息指示至少一个EES。处理单元1910具体用于，根据该EES信息确定目标EES。
可选地，收发单元1920还用于从ECS接收第一信息，该第一信息指示所述至少一个EES的ACR能力。
可选地，所述至少一个EES支持第一ACR场景。
可选地，收发单元1920还用于向所述ECS发送第二信息，该第二信息用于指示以下至少一项：选择支持所述第一ACR场景的目标EES，或者，当前连接的EES或当前连接的应用实例EAS无法执行ACR，或者，当前应用无对应的ACR场景，或者，请求获取EES的ACR能力。
在一些实施例中，处理单元1910还用于，在当前应用无对应的ACR场景的情况下，或者，在当前连接的EES或当前连接的EAS无法执行ACR的情况下，确定基于第一ACR场景进行ACR。
可选地，收发单元1920还用于从当前连接的EES接收第三信息，该第三信息指示当前应用无对应的ACR场景，或者，指示当前连接的EES或当前连接的EAS无法执行ACR。
在一些实施例中，收发单元1920还用于从当前连接的EES接收第四信息，该第四信息用于指示选择支持第一ACR场景的目标EES，或用于指示第一ACR场景为当前应用对应的ACR场景。
在一些实施例中，收发单元1920还用于从目标EES接收EAS信息，该EAS信息指示至少一个EAS。处理单元1910还用于，根据EAS信息确定目标EAS。
可选地，收发单元1920还用于从目标EES接收第五信息，该第五信息指示所述至少一个EAS的ACR能力。
可选地，所述至少一个EAS支持所述第一ACR场景。
可选地，收发单元1920还用于向目标EES发送第六信息，该第六信息用于指示以下至少一项：选择支持所述第一ACR场景的目标EAS，或者，源EES或源EAS无法执行ACR，或者，当前应用无对应的ACR场景，或者，请求获取EAS的ACR能力。
应理解，该通信装置1900为终端设备时，该通信装置1900中的收发单元1920可以通过通信接口实现，例如可对应于图20中示出的通信装置2000中的通信接口2030。该通信装置1900中的处理单元1910可通过至少一个处理器实现，例如可对应于图20中示出的通信装置2000中的处理器2010。
可选地，上述通信装置1900可以对应于前文方法实施例中的ECS，例如，可以为ECS，或配置在ECS中的部件(如芯片、芯片系统、处理器等)，或者，还可以为能够实现全部或部分ECS功能的逻辑模块或软件。本申请实施例对此不作限定。
该装置1900与ECS对应时，可用于执行前文图3至图18所示的方法中ECS所执行的步骤。该通信装置1900可以包括用于执行前文图3至图18所示出的方法中的ECS执行的方法的单元。 并且，该通信装置1900中的各单元和上述其他操作和/或功能分别为了实现图3至图18所示的方法中的相应流程。
作为一个示例，收发单元1920用于向终端设备发送EES信息，该EES信息指示至少一个EES。收发单元1920还用于向终端设备发送第一信息，该第一信息指示所述至少一个EES的ACR能力。
可选地，收发单元1920还用于接收来自所述终端设备的第二信息，该第二信息用于指示请求获取EES的ACR能力。
作为又一个示例，处理单元1910用于确定支持第一ACR场景的至少一个EES，该第一ACR场景为由目标EES执行ACR的场景。收发单元1920用于向终端设备发送EES信息，该EES信息指示所述至少一个EES。
可选地，收发单元1920还用于接收来自终端设备的第二信息，该第二信息用于指示以下至少一项：选择支持目标ACR场景的目标EES，或者，当前连接的EES或当前连接的EAS无法执行ACR，或者，当前应用无对应的ACR场景。
应理解，该通信装置为ECS时，该通信装置1900中的收发单元1920可以通过通信接口实现，例如可对应于图20中示出的通信装置2000中的通信接口2030。该通信装置1900中的处理单元1910可通过至少一个处理器实现，例如可对应于图20中示出的通信装置2000中的处理器2010。
可选地，上述通信装置1900可以对应于前文方法实施例中的EES(包括源EES或目标EES)，例如，可以为EES，或配置在EES中的部件(如芯片、芯片系统、处理器等)，或者，还可以为能够实现全部或部分EES功能的逻辑模块或软件。本申请实施例对此不作限定。
该装置1900与EES对应时，可用于执行前文图3至图18所示的方法中EES所执行的步骤，例如执行源EES所执行的步骤，或执行目标EES所执行的步骤。该通信装置1900可以包括用于执行前文图3至图18所示出的方法中的EES执行的方法的单元。并且，该通信装置1900中的各单元和上述其他操作和/或功能分别为了实现图3至图18所示的方法中的相应流程。
作为一个示例，处理单元1910用于确定当前应用无对应的ACR场景。收发单元1920用于向终端设备发送第三信息，该第三信息指示当前应用无对应的ACR场景，或者，指示EES或者该EES所关联的EAS无法执行ACR。
作为又一个示例，处理单元1910用于确定基于第一ACR场景进行ACR，该第一ACR场景为由目标EES执行ACR的场景。收发单元1920用于向终端设备发送第四信息，该第四信息用于指示选择支持第一ACR场景的目标EES，或用于指示第一ACR场景为当前应用对应的ACR场景。
可选地，在处理单元1910确定基于第一ACR场景进行ACR之前，处理单元1910还用于确定当前应用无对应的ACR场景。
作为又一个示例，收发单元1920用于向终端设备发送EAS信息，该EAS信息指示至少一个EAS；收发单元1920还用于向终端设备发送第五信息，该第五信息指示所述至少一个EAS的ACR能力。
可选地，收发单元1920用于还用于接收来自所述终端设备的第六信息，该第六信息用于指示请求获取EAS的ACR能力。
作为又一个示例，处理单元1910用于确定支持第一ACR场景的至少一个EAS，该第一ACR场景为由目标EES执行ACR的场景。收发单元1920用于向终端设备发送EAS信息，该EAS信息指示所述至少一个EAS。
可选地，收发单元1920还用于接收来自终端设备的第六信息，该第六信息用于指示以下至少一项：选择支持第一ACR场景的目标EAS，或者，源EES和源EAS无法执行ACR，或者，当前应用无对应的ACR场景。
应理解，该通信装置为EES时，该通信装置1900中的收发单元1920可以通过通信接口实现，例如可对应于图20中示出的通信装置2000中的通信接口2030。该通信装置1900中的处理单元1910可通过至少一个处理器实现，例如可对应于图20中示出的通信装置2000中的处理器2010。
图20是本申请实施例提供的通信装置的另一示意性框图。如图20所示，该装置2000可以包括至少一个处理器2010。该至少一个处理器2010可用于实现本申请实施例提供的方法中终端设备(包括EEC等)、ECS、或EES(包括源EES或目标EES)的功能。
该通信装置2000还可以包括至少一个存储器2020，用于存储程序指令和/或数据。存储器2020和处理器2010耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器2010可能和存储器2020协同操作。处理器2010可能执行存储器2020中存储的程序指令。所述至少一个存储器中的至少一个可以包括于处理器中。
该通信装置2000还可以包括通信接口2030，用于通过传输介质和其它设备进行通信，从而用于通信装置2000中的装置可以和其它设备进行通信。示例性地，当该通信装置2000用于实现本申请实施例提供的方法中终端设备的功能时，该其他设备可以包括ECS和EES。通信接口2030例如可以是收发器、接口、总线、电路或者能够实现收发功能的装置。处理器2010可利用通信接口2030收发数据和/或信息，并用于实现图3至图18对应的实施例中的终端设备、ECS或EES所执行的方法。
例如，当该装置2000用于实现本申请实施例提供的方法中终端设备的功能时，处理器2010可用于确定目标EES，该目标EES为支持为支持第一ACR场景的EES，第一ACR场景为由目标EES执行ACR的场景；处理器还用于控制通信接口2030，请求目标EES执行ACR。
又例如，当该装置2000用于实现本申请实施例提供的方法中ECS的功能时，处理器2010可用于控制控制通信接口2030向终端设备发送EES信息，该EES信息指示至少一个EES。
再例如，当该装置2000用于实现本申请实施例提供的方法中EES的功能时，处理器2010可用于确定当前应用无对应的ACR场景，还可用于控制通信接口2030向终端设备发送第三信息，该第三信息指示当前应用无对应的ACR场景，或者，指示EES或者该EES所关联的EAS无法执行ACR。
应理解，各单元执行相应步骤的具体过程在前述方法实施例中已经详细说明，为了简洁，在此不再赘述。
本申请实施例中不限定上述处理器2010、存储器2020以及通信接口2030之间的具体连接介质。
应注意，上述的方法实施例可以应用于处理器中，或者由处理器实现。处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是ROM、PROM、EPROM、EEPROM或闪存。易失性存储器可以是RAM，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请还提供了一种芯片系统，所述芯片系统包括至少一个处理器，用于实现上述图3至图 16所示实施例中终端设备、ECS或EES(包括源EES或目标EES)执行的方法中所涉及的功能，例如，接收或处理上述方法中所涉及的数据和/或信息。
在一种可能的设计中，所述芯片系统还包括存储器，所述存储器用于保存程序指令和数据，存储器位于处理器之内或处理器之外。
该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
本申请还提供了一种通信系统，包括前述的源EES和目标EES中的至少一个。其中，源EES可以实现前述方法实施例中源EES所涉及的功能；目标EES可以实现前述方法实施例中目标EES所涉及的功能。
可选地，该通信系统中还包括ECS，该ECS可以实现前述方法实施例中ECS所涉及的功能。
可选地，该通信系统中还包括终端设备，该终端设备可以实现前述方法实施例中终端设备所涉及的功能，例如可以实现EEC所涉及的功能。
本申请还提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当所述计算机程序被运行时，使得计算机执行图3至图16所示实施例中终端设备、ECS或EES(包括源EES或目标EES)执行的方法。
本申请还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序(也可以称为代码，或指令)。当所述计算机程序被运行时，使得计算机执行图3至图16所示实施例中终端设备、ECS或EES(包括源EES或目标EES)执行的方法。
上述实施例所提供的方法，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品可以包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁盘)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘solid state disk(SSD))等。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡 献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (33)

  1. 一种应用上下文迁移的方法，其特征在于，应用于终端设备，所述方法包括：
    向边缘配置服务器ECS发送第二信息，所述第二信息用于指示选择支持应用上下文迁移ACR场景的边缘使能服务器EES；
    从所述ECS接收EES信息，所述EES信息指示至少一个支持ACR场景的EES；
    根据所述EES信息确定目标EES，所述目标EES为所述至少一个支持ACR场景的EES中的一个EES；
    请求所述目标EES执行ACR，以使得所述终端设备通过所述目标EES将所述终端设备的应用上下文从所述终端设备的源边缘应用服务器EAS迁移到所述终端设备的目标EAS。
  2. 如权利要求1所述的方法，其特征在于，所述ACR场景为：所述终端设备通过支持ACR场景的EES执行将所述终端设备的应用上下文从所述终端设备的源EAS迁移到所述终端设备的目标EAS的场景。
  3. 如权利要求2所述的方法，其特征在于，所述方法还包括：
    从所述ECS接收第一信息，所述第一信息指示所述至少一个EES的ACR能力。
  4. 如权利要求1至3中任一项所述的方法，其特征在于，所述方法还包括：
    在当前应用无对应的ACR场景的情况下，或者，在当前连接的EES或当前连接的EAS无法执行ACR的情况下，确定基于所述ACR场景进行ACR。
  5. 如权利要求4所述的方法，其特征在于，所述方法还包括：
    从当前连接的EES接收第三信息，所述第三信息指示当前应用无对应的ACR场景，或者，指示所述当前连接的EES或所述当前连接的EAS无法执行ACR。
  6. 如权利要求1至3中任一项所述的方法，其特征在于，在所述确定目标EES之前，所述方法还包括：
    从当前连接的EES接收第四信息，所述第四信息用于指示选择支持所述ACR场景的目标EES，或用于指示所述ACR场景为当前应用对应的ACR场景。
  7. 如权利要求1至6中任一项所述的方法，其特征在于，所述方法还包括：
    从所述目标EES接收EAS信息，所述EAS信息指示至少一个EAS；
    根据所述EAS信息确定目标EAS。
  8. 如权利要求7所述的方法，其特征在于，所述方法还包括：
    从所述目标EES接收第五信息，所述第五信息指示所述至少一个EAS的ACR能力。
  9. 如权利要求7或8所述的方法，其特征在于，所述至少一个EAS支持所述ACR场景。
  10. 如权利要求7至9中任一项所述的方法，其特征在于，所述方法还包括：
    向所述目标EES发送第六信息，所述第六信息用于指示以下至少一项：
    选择支持所述ACR场景的目标EAS，
    源EES或源EAS无法执行ACR，
    当前应用无对应的ACR场景，或者
    请求获取EAS的ACR能力。
  11. 一种通信方法，其特征在于，应用于边缘配置服务器ECS，所述方法包括：
    接收来自终端设备的第二信息，所述第二信息用于指示选择支持应用上下文迁移ACR场景的边缘使能服务器EES；
    向所述终端设备发送EES信息，所述EES信息指示至少一个支持ACR场景的EES。
  12. 如权利要求11所述的方法，其特征在于，所述ACR场景为：所述终端设备通过支持应用上下文迁移场景的EES执行将所述终端设备的应用上下文从所述终端设备的源边缘应用服务器EAS迁移到所述终端设备的目标EAS的场景。
  13. 如权利要求12所述的方法，其特征在于，所述方法还包括：
    向所述终端设备发送第一信息，所述第一信息指示所述至少一个EES的ACR能力。
  14. 一种通信方法，其特征在于，应用于边缘配置服务器ECS，所述方法包括：
    确定支持应用上下文迁移ACR场景的至少一个边缘使能服务器EES，所述ACR场景为由目标EES执行ACR的场景；
    向终端设备发送EES信息，所述EES信息指示所述至少一个EES。
  15. 如权利要求14所述的方法，其特征在于，所述方法还包括：向所述终端设备发送第一信息，所述第一信息指示所述至少一个EES的ACR能力。
  16. 如权利要求14或15所述的方法，其特征在于，所述方法还包括：
    接收来自所述终端设备的第二信息，所述第二信息用于指示以下至少一项：
    选择支持目标ACR场景的目标EES，
    当前连接的EES或当前连接的边缘应用服务器EAS无法执行ACR，或者
    当前应用无对应的ACR场景。
  17. 一种通信方法，其特征在于，应用于边缘使能服务器EES，所述方法包括：
    确定当前应用无对应的应用上下文迁移ACR场景；
    向终端设备发送第三信息，所述第三信息指示当前应用无对应的ACR场景，或者，指示所述EES或者当前连接的边缘应用服务器EAS无法执行ACR。
  18. 一种通信方法，其特征在于，应用于边缘使能服务器EES，所述方法包括：
    确定基于应用上下文迁移ACR场景进行ACR，所述ACR场景为由目标EES执行ACR的场景；
    向终端设备发送第四信息，所述第四信息用于指示选择支持所述ACR场景的目标EES，或用于指示所述ACR场景为当前应用对应的ACR场景。
  19. 如权利要求18所述的方法，其特征在于，在所述确定基于ACR场景进行ACR之前，所述方法还包括：
    确定当前应用无对应的ACR场景。
  20. 一种通信方法，其特征在于，应用于边缘使能服务器EES，所述方法包括：
    向终端设备发送边缘应用服务器EAS信息，所述EAS信息指示至少一个EAS；
    向终端设备发送第五信息，所述第五信息指示所述至少一个EAS的应用上下文迁移ACR能力。
  21. 如权利要求20所述的方法，其特征在于，所述方法还包括：
    接收来自所述终端设备的第六信息，所述第六信息用于指示请求获取EAS的ACR能力。
  22. 一种通信方法，其特征在于，应用于边缘使能服务器EES，所述方法包括：
    确定支持应用上下文迁移ACR场景的至少一个边缘应用服务器EAS；所述ACR场景为由目标EES执行ACR的场景；
    向终端设备发送EAS信息，所述EAS信息指示所述至少一个EAS。
  23. 如权利要求22所述的方法，其特征在于，所述方法还包括：向所述终端设备发送第五信息，所述第五信息指示所述至少一个EAS的ACR能力。
  24. 如权利要求22或23所述的方法，其特征在于，所述方法还包括：
    接收来自终端设备的第六信息，所述第六信息用于指示以下至少一项：
    选择支持ACR场景的目标EAS，
    源EES和源EAS无法执行ACR，或者
    当前应用无对应的ACR场景。
  25. 一种通信装置，其特征在于，用于实现如权利要求1至10中任一项所述的方法，或，用于实现如权利要求11至16中任一项所述的方法，或，用于实现如权利要求17至19中任一项所述的方法，或，用于实现如权利要求20至24中任一项所述的方法。
  26. 一种通信装置，其特征在于，包括处理器，所述处理器用于执行程序代码，以使得所述通信装置实现如权利要求1至10中任一项所述的方法，或，实现如权利要求11至16中任一项所述的方法，或，实现如权利要求17至19中任一项所述的方法，或，实现如权利要求20至24中任一项所述的方法。
  27. 一种通信系统，包括源边缘使能服务器EES和目标EES中的至少一个，其中，所述源EES 用于实现如权利要求17至19中任一项所述的方法，所述目标EES用于实现如权利要求20至24中任一项所述的方法。
  28. 如权利要求27所述的通信系统，其特征在于，所述通信系统还包括边缘配置服务器ECS，所述ECS用于实现如权利要求11至16中任一项所述的方法。
  29. 如权利要求27或28所述的通信系统，其特征在于，所述通信系统还包括终端设备，所述终端设备用于实现如权利要求1至10中任一项所述的方法。
  30. 一种方法，其特征在于，所述方法包括：
    终端向边缘配置服务器ECS发送第二信息，所述第二信息用于指示选择支持应用上下文迁移ACR场景的边缘使能服务器EES；
    所述ECS向所述终端发送EES信息，所述EES信息指示至少一个支持ACR场景的EES；
    所述终端根据所述EES信息确定目标EES，所述目标EES为所述至少一个支持ACR场景的EES中的一个EES；
    所述终端请求所述目标EES执行ACR，以使得所述终端设备通过所述目标EES将所述终端设备的应用上下文从所述终端设备的源边缘应用服务器EAS迁移到所述终端设备的目标EAS。
  31. 如权利要求30所述的方法，其特征在于，所述ACR场景为：所述终端设备通过支持ACR场景的EES执行将所述终端设备的应用上下文从所述终端设备的源EAS迁移到所述终端设备的目标EAS的场景。
  32. 一种通信系统，其特征在于，所述通信系统包括：
    终端设备，用于实现如权利要求1至10中任一项所述的方法；
    网络侧设备，用于与所述终端设备通信。
  33. 如权利要求32所述的通信系统，其特征在于，所述网络侧设备包括边缘配置服务器ECS和边缘使能服务器EES中的至少一个。
PCT/CN2024/074052 2023-02-20 2024-01-25 应用上下文迁移方法、通信方法及相关装置、系统 Ceased WO2024174803A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
AU2024226522A AU2024226522A1 (en) 2023-02-20 2024-01-25 Application context relocation method, communication method, and related apparatus and system
EP24759480.7A EP4660801A4 (en) 2023-02-20 2024-01-25 METHOD FOR RELOCATING APPLICATION CONTEXT, COMMUNICATION METHOD, ASSOCIATED DEVICE AND SYSTEM
US19/303,838 US20250385955A1 (en) 2023-02-20 2025-08-19 Application context relocation method, communication method, and related apparatus and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202310193234.1 2023-02-20
CN202310193234.1A CN118519732A (zh) 2023-02-20 2023-02-20 应用上下文迁移方法、通信方法及相关装置、系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US19/303,838 Continuation US20250385955A1 (en) 2023-02-20 2025-08-19 Application context relocation method, communication method, and related apparatus and system

Publications (1)

Publication Number Publication Date
WO2024174803A1 true WO2024174803A1 (zh) 2024-08-29

Family

ID=92281596

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/074052 Ceased WO2024174803A1 (zh) 2023-02-20 2024-01-25 应用上下文迁移方法、通信方法及相关装置、系统

Country Status (6)

Country Link
US (1) US20250385955A1 (zh)
EP (1) EP4660801A4 (zh)
CN (1) CN118519732A (zh)
AU (1) AU2024226522A1 (zh)
TW (1) TW202437785A (zh)
WO (1) WO2024174803A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN119012310A (zh) * 2023-05-16 2024-11-22 华为技术有限公司 通信方法及通信装置

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190342797A1 (en) * 2016-12-07 2019-11-07 Telefonaktiebolaget Lm Ericsson (Publ) Method and migration managing module for managing a migration of a service
US20210352156A1 (en) * 2020-05-08 2021-11-11 Samsung Electronics Co., Ltd. Method and apparatus for managing information related to edge computing service
CN114599022A (zh) * 2022-01-30 2022-06-07 华为技术有限公司 设备选择的方法以及装置
CN114980223A (zh) * 2021-02-24 2022-08-30 华为技术有限公司 一种通信方法及装置
CN115167991A (zh) * 2021-04-07 2022-10-11 华为技术有限公司 一种业务迁移的方法和装置
CN115190169A (zh) * 2021-04-02 2022-10-14 华为技术有限公司 一种通信方法、装置及系统
CN115529641A (zh) * 2021-06-25 2022-12-27 华为技术有限公司 用于迁移上下文的方法和装置
CN115552867A (zh) * 2020-07-23 2022-12-30 三星电子株式会社 用于在边缘计算环境中选择目标边缘应用服务器的方法和装置

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190342797A1 (en) * 2016-12-07 2019-11-07 Telefonaktiebolaget Lm Ericsson (Publ) Method and migration managing module for managing a migration of a service
US20210352156A1 (en) * 2020-05-08 2021-11-11 Samsung Electronics Co., Ltd. Method and apparatus for managing information related to edge computing service
CN115486053A (zh) * 2020-05-08 2022-12-16 三星电子株式会社 用于管理与边缘计算服务相关的信息的方法和装置
CN115552867A (zh) * 2020-07-23 2022-12-30 三星电子株式会社 用于在边缘计算环境中选择目标边缘应用服务器的方法和装置
CN114980223A (zh) * 2021-02-24 2022-08-30 华为技术有限公司 一种通信方法及装置
CN115190169A (zh) * 2021-04-02 2022-10-14 华为技术有限公司 一种通信方法、装置及系统
CN115167991A (zh) * 2021-04-07 2022-10-11 华为技术有限公司 一种业务迁移的方法和装置
CN115529641A (zh) * 2021-06-25 2022-12-27 华为技术有限公司 用于迁移上下文的方法和装置
CN114599022A (zh) * 2022-01-30 2022-06-07 华为技术有限公司 设备选择的方法以及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4660801A1 *

Also Published As

Publication number Publication date
EP4660801A4 (en) 2026-03-11
TW202437785A (zh) 2024-09-16
CN118519732A (zh) 2024-08-20
US20250385955A1 (en) 2025-12-18
EP4660801A1 (en) 2025-12-10
AU2024226522A1 (en) 2025-09-11

Similar Documents

Publication Publication Date Title
CN114980223B (zh) 一种通信方法及装置
EP3977792B1 (en) Supporting traffic steering through a service function chain
US11558911B2 (en) Communication method and device for edge computing system
CN109922472B (zh) 用户策略的获取
CN104255046B (zh) 可定制的移动宽带网络系统和定制移动宽带网络的方法
WO2022012310A1 (zh) 一种通信方法及装置
CN113630749B (zh) 一种获取边缘服务的方法和装置
TWI854211B (zh) 一種用於傳輸上下文的方法和通信裝置
CN112491944A (zh) 边缘应用发现方法及装置、边缘应用服务支持方法及装置
WO2023143574A1 (zh) 设备选择的方法以及装置
JP2023052808A (ja) ３ｇｐｐ・セルラー外のアクセスのための、５ｇネットワークにおけるアクセスノードの選択、及び、合法的な傍受に従う地域的要件の表示傍受を意識したアクセスノードの選択
CN111770538A (zh) 通信方法、设备及系统
US20240098806A1 (en) Service data flow continuity for a ue in a system involving a gateway device
CN102801800A (zh) 多无线终端之间的资源共享处理方法及系统
WO2023143212A1 (zh) 一种通信方法及装置
CN108701278A (zh) 用于经由第二运营商网络向连接到第一运营商网络的用户设备提供服务的方法
US11916805B2 (en) Network device provisioning based on device type
US20250385955A1 (en) Application context relocation method, communication method, and related apparatus and system
CN116671137B (zh) 一种确定mec接入点的方法及装置
WO2023143560A1 (zh) 设备选择的方法以及装置
JP2025519249A (ja) 通信装置の方法および通信装置
CN113676903B (zh) 切片认证授权管理方法、装置和系统
CN118785136A (zh) 通信方法、通信装置及通信系统
CN120730541A (zh) 一种通信方法及装置
WO2026040619A1 (zh) 通信方法和通信装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24759480

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202527077992

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: AU2024226522

Country of ref document: AU

WWP Wipo information: published in national office

Ref document number: 202527077992

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 2024226522

Country of ref document: AU

Date of ref document: 20240125

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 2024759480

Country of ref document: EP