Communication method and communication apparatus

Through the edge configuration server selecting the appropriate edge enablement service and application server based on the indication information, the problems of business interruption and performance degradation during application context migration caused by terminal device movement are solved, and efficient edge computing services are achieved.

WO2024235055A1PCT designated stage expired Publication Date: 2024-11-21HUAWEI TECH CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/091450
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-16
Filing Date
2024-05-07
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

During edge application operation, when the terminal device moves to a new service area, it is difficult for the prior art to effectively select appropriate edge-enabled services and application servers, resulting in business interruptions or performance degradation during application context migration.

Method used

Receive instructions through the edge configuration server, determine the instantiation status of the target edge enable service and application server, and select the appropriate edge enable service and application server for application context migration to ensure service continuity and performance optimization.

Benefits of technology

It realizes reducing service interruption time during application context migration when terminal devices are moved and improving the performance and availability of edge computing services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024091450_21112024_PF_FP_ABST
    Figure CN2024091450_21112024_PF_FP_ABST
Patent Text Reader

Abstract

A communication method and a communication apparatus, applied to the technical field of communications. The method comprises: a second edge enabler server (EES) or an edge enabler client (EEC) sends first indication information, and correspondingly, an edge configuration server (ECS) receives the first indication information; and on the basis of the first indication information, the ECS determines an EES corresponding to a target EAS applying corresponding application context relocation (ACR). By means of embodiments of the present application, appropriate EES and EAS can be applied and selected, thereby providing better ACR service and edge computing service for applications.
Need to check novelty before this filing date? Find Prior Art

Description

Communication method and communication device

[0001] This application claims priority to the Chinese patent application with application number 202310553014.5 filed with the State Intellectual Property Office of China on May 16, 2023, and priority to the Chinese patent application with the invention name “Communication Method and Communication Device”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a communication method and a communication device. Background Art

[0003] During the operation of edge applications, when a terminal device moves outside the current service area, such as when a terminal device moves between edge data networks (EDNs) or local area data networks (LADNs), the current edge application server (EAS) may no longer be able to provide services for the currently running application, or the current EAS is no longer the optimal application server to provide services for the terminal device. Other EASs may be more suitable for serving the application client on the terminal device, so a new EAS needs to be selected to provide services for the terminal device. That is, the application context information of the terminal device needs to be migrated from the current EAS to the new EAS. This process can be called application context migration or application context relocation (ACR).

[0004] During the ACR process, the target EES and target EAS information of the ACR corresponding to the application can be obtained through the discovery process of the edge enabler server (EES) and EAS. For example, the source EES or EEC of the ACR corresponding to the application can first obtain the target EES information from the edge configuration server (ECS), and then obtain the target EAS information from the target EES.

[0005] Generally, an ECS can be associated with multiple EESs, and an EES can be associated with multiple EASs. Therefore, choosing the right EES or EAS for an application is an urgent issue.

[0006] Summary of the Invention

[0007] The embodiments of the present application disclose a communication method and a communication device, which can select appropriate EES and EAS, thereby providing better ACR services and edge computing services for applications.

[0008] In a first aspect, an embodiment of the present application provides a communication method, which is applied to an ECS, and includes:

[0009] The ECS receives first indication information, where the first indication information is used to determine a first EES corresponding to a first EAS, where the first EAS is a target EAS for an application context migration ACR corresponding to an application; the ECS determines the first EES based on the first indication information.

[0010] In an embodiment of the present application, the first EAS is the target EAS of the ACR corresponding to the application, that is, the first EAS is the EAS to which the context information of the application is to be migrated. The first EES is associated with an instantiated EAS or the first EES is associated with an EAS that can be instantiated but not instantiated. The first indication information may come from a second EES or EEC, where the second EES is the EES corresponding to the EAS currently providing services for the application, and the EEC is the EEC corresponding to the application. Based on the indication of the second EES or EEC, the ECS may determine whether the first EES is associated with an instantiated EAS or an instantiated but not instantiated EAS, thereby enabling the ECS to select a suitable EES for the application to perform application context migration, thereby providing better ACR services and edge computing services for the UE.

[0011] In combination with the first aspect, in a possible implementation method, the first indication information includes at least one of the following information: the ACR type corresponding to the application, indication information that the ACR corresponding to the application is a service continuity planning ACR or a common ACR, indication information of the instantiation status of the first EAS, and first time information; wherein, the first time information is used to indicate the time when the service continuity planning ACR is executed.

[0012] In an embodiment of the present application, ECS can determine whether the first EES needs to have an instantiable but uninstantiated EAS based on the ACR type corresponding to the application, the indication information of whether the ACR corresponding to the application is a service continuity planning ACR or a normal ACR, the indication information of the instantiation status of the first EAS, and the first time information, so as to select a suitable EES for the application to perform application context migration, thereby providing better ACR services and edge computing services for the application.

[0013] In combination with the first aspect, in a possible implementation, the ECS determines the first EES based on the first indication information, including: the ECS determines the first EES based on the first indication information and at least one of the following: the instantiation status of the EAS associated with at least one EES corresponding to the ECS, and second time information; wherein the second time information is used to indicate the time of instantiation of the first EAS.

[0014] In an embodiment of the present application, the ECS may determine the instantiation state of the target EAS (i.e., the first EAS) required for the ACR corresponding to the application based on the first indication information. Exemplarily, the first indication information includes the first time information, and the ECS may also determine the instantiation state of the first EAS based on the first time information and the second time information. The ECS may select an EES that matches the instantiation state of the first EAS from the at least one EES based on the instantiation state information of the EAS corresponding to at least one EES. For example, when the instantiation state of the first EAS is instantiated, the ECS selects the EES corresponding to the instantiated EAS as the first EES. For another example, when the instantiation state of the first EAS is instantiable but not instantiated, the ECS selects the EES corresponding to the instantiated but not instantiated EAS as the first EES. The ECS combines the first indication information, the instantiation state of the EAS associated with at least one EES corresponding to the ECS, and the second time information to select a suitable target EES for the application to perform ACR, thereby providing better ACR services and edge computing services for the terminal device.

[0015] In combination with the first aspect, in a possible implementation, when the ACR type includes an ordinary ACR type or the first indication information includes indication information that the ACR corresponding to the application is an ordinary ACR or the instantiation state of the first EAS includes an instantiated state, the first EES corresponds to an instantiated EAS; or, when the ACR type includes a service continuity planning ACR type or the first indication information includes indication information that the ACR corresponding to the application is a service continuity planning ACR or the instantiation state of the first EAS includes an instantiable but uninstantiated state, the first EES corresponds to an instantiable but uninstantiated EAS.

[0016] In an embodiment of the present application, when the ACR type includes a common ACR type or the first indication information includes indication information that the ACR corresponding to the application is a common ACR or the instantiation state of the first EAS includes an instantiated state, the ECS determines that the target EAS required by the ACR corresponding to the application is an instantiated EAS, and therefore the ECS selects the EES corresponding to the instantiated EAS as the first EES. When the ACR type includes a service continuity planning ACR type or the first indication information includes indication information that the ACR corresponding to the application is a service continuity planning ACR or the instantiation state of the first EAS includes an instantiable but uninstantiated state, the ECS determines that the target EAS required by the ACR corresponding to the application is an instantiable but uninstantiated EAS, and therefore the ECS selects the EES corresponding to the instantiable but uninstantiated EAS as the first EES.

[0017] In the embodiment of the present application, for ACRs of the common ACR type, an instantiated EAS can be selected to reduce the duration of service interruption. For ACRs of the service continuity planning ACR type, an instantiable but uninstantiated EAS can be selected, and a new EAS can be instantiated for the AC, which can provide an EAS with better key performance indicators (KPIs) for the application.

[0018] In combination with the first aspect, in a possible implementation, when the execution time of the service continuity planning ACR is less than the instantiation time of the first EAS, the first EES corresponds to the instantiated EAS; or, when the execution time of the service continuity planning ACR is greater than the instantiation time of the first EAS, the first EES is associated with an EAS that can be instantiated but has not been instantiated.

[0019] In an embodiment of the present application, the execution time of the service continuity planning ACR may also be referred to as the prediction expiration time, which is used to indicate the time when the terminal device corresponding to the application moves to the expected location or the service range of the target EAS. For example, the first time information includes a first duration, indicating that after the first duration, the terminal device moves to the expected location or the service range of the target EAS. The second time information is used to indicate the time when the first EAS is instantiated, that is, the second time information is used to indicate the time required for the first EAS to change from an uninstantiated state to an instantiated state. In the case that the execution time of the service continuity planning ACR is less than the instantiation time of the first EAS, the ECS selects the EES corresponding to the instantiated EAS, that is, the first EES corresponds to the instantiated EAS, which can avoid increasing the ACR latency and the time when the service performance is not optimal. When the execution time of the service continuity planning ACR is longer than the EAS instantiation time, ECS can select the EEES corresponding to the EAS that can be instantiated but not instantiated, that is, the first EES corresponds to the EAS that can be instantiated but not instantiated, and instantiate a new EAS for the application, thereby providing the application with an EAS with better KPIs, and providing the application with better ACR services and edge computing services.

[0020] In conjunction with the first aspect, in a possible implementation, the method further includes:

[0021] The ECS sends first information, which includes at least one of the following: information of at least one EES corresponding to the ECS, instantiation status information of an EAS associated with at least one EES corresponding to the ECS, and information of the first EES; wherein the at least one EES includes the first EES.

[0022] In an embodiment of the present application, after determining the first EES, the ECS can send the information of the first EES to the second EES or EEC, so that the second EES or EEC can quickly determine the target EES corresponding to the ACR and obtain the information of the target EAS corresponding to the ACR from the first EES.

[0023] In one possible implementation, after receiving the first indication information, the ECS can determine at least one EES that matches the application, and send the information of the at least one EES to the second EES or EEC, so that the second EES or EEC can determine the target EES of the ACE corresponding to the application based on the information of the at least one EES.

[0024] With reference to the first aspect, in a possible implementation manner, the first indication information comes from the second EES or the edge enabling client EEC.

[0025] In a second aspect, an embodiment of the present application provides a communication method, which is applied to a second EES, and includes:

[0026] The second EES sends a first message to the first EES, where the first message is used to obtain information of the first EAS, the first message includes first indication information, the first EAS is the target EAS for the application context migration ACR corresponding to the application, and the first indication information is used to determine the first EAS; the second EES receives a second message from the first EES, where the second message includes information of at least one EAS, and the at least one EAS includes the first EAS.

[0027] In an embodiment of the present application, the first EAS is the target EAS of the ACR corresponding to the application, that is, the first EAS is the EAS to which the context information of the application is to be migrated. The first EAS is an instantiated EAS, or the first EAS is an instantiated but uninstantiated EAS. The second EES is the EES corresponding to the EAS that currently provides services for the application, that is, the second EES is the source EES of the ACR corresponding to the application. The first EES is the target EES of the ACR corresponding to the application. The second EES can indicate the conditions that the target EAS (that is, the first EAS) required by the first EES (that is, the first EAS) must meet through the first indication information, so that the first EES can determine whether to select an instantiated but uninstantiated EAS for the application based on the first indication information, that is, it can enable the first EES to select a suitable EAS for the application to perform application context migration, thereby providing better ACR services and edge computing services for the application.

[0028] In combination with the second aspect, in a possible implementation method, the first indication information includes at least one of the following information: the application context migration ACR type corresponding to the application, indication information that the ACR corresponding to the application is a service continuity planning ACR or a common ACR, indication information of the instantiation status of the first EAS, and first time information; wherein, the first time information is used to indicate the time when the service continuity planning ACR is executed.

[0029] In an embodiment of the present application, the first indication information includes the ACR type corresponding to the application, indication information of whether the ACR corresponding to the application is a service continuity planning ACR or a common ACR, indication information of the instantiation status of the first EAS, and the first time information, so that the first EES can combine the ACR type corresponding to the application, indication information of whether the ACR corresponding to the application is a service continuity planning ACR or a common ACR, indication information of the instantiation status of the first EAS, and the first time information to select a suitable EAS for the application to perform application context migration, thereby providing better ACR services and edge computing services for the application.

[0030] In conjunction with the second aspect, in a possible implementation, the method further includes:

[0031] The second EES determines the first EAS from the at least one EAS based on at least one of the following information: a type of the ACR, instantiation state information of the first EAS, and the at least one EAS information.

[0032] In an embodiment of the present application, the second EES may determine the first EAS from at least one EAS based on the type of ACR and at least one EAS information, or the second EES may determine the first EAS from at least one EAS based on the instantiation status information of the first EAS and at least one EAS information. For example, the second EES may determine the instantiation status of the first EAS based on the type of ACR, and then select an EAS that matches the instantiation status of the first EAS from the at least one EAS. For example, if the instantiation status of the first EAS is instantiated, the second EES selects the instantiated EAS as the first EAS. For another example, if the instantiation status of the first EAS is instantiable but not instantiated, the second EES selects the instantiable but not instantiated EAS as the first EAS.

[0033] In an embodiment of the present application, the second EES combines the type of ACR, the instantiation status information of the first EAS, and at least one EAS information to select the target EAS corresponding to the ACR for the application, so as to select a suitable target EAS for the application for ACR, thereby providing better ACR services and edge computing services for the terminal device.

[0034] With reference to the second aspect, in a possible implementation, the first EAS information includes second time information, where the second time information is used to indicate a time when the first EAS is instantiated. The method further includes:

[0035] The second EES determines the first EAS from the at least one EAS based on the first time information and / or the second time information.

[0036] In an embodiment of the present application, the time for executing the service continuity plan ACR may also be referred to as the prediction expiration time, which is used to indicate the time when the terminal device corresponding to the application moves to the expected location or the service range of the target EAS. For example, the first time information includes a first duration, indicating that after the first duration, the terminal device moves to the expected location or the service range of the target EAS. The second time information is used to indicate the time when the first EAS is instantiated, that is, the second time information is used to indicate the time required for the first EAS to go from an uninstantiated state to an instantiated state. The second EES determines the first EAS in combination with the first time information and the second time information, and can select a suitable EAS for the application, reduce the service interruption time, and thus provide better ACR services and edge computing services for the terminal device.

[0037] For example, when the execution time of the service continuity planning ACR is less than the instantiation time of the first EAS, the second EES selects the instantiated EAS as the first EAS, that is, the first EES corresponds to the instantiated EAS, which can avoid increasing the ACR latency and the time of poor business performance. When the execution time of the service continuity planning ACR is greater than the instantiation time of the EAS, the second EES can select an instantiable but uninstantiated EAS as the first EAS, that is, the first EES corresponds to an instantiable but uninstantiated EAS, and instantiate a new EAS for the application, thereby providing the application with an EAS with better KPIs, and providing the application with better ACR services and edge computing services.

[0038] In conjunction with the second aspect, in a possible implementation, the method further includes:

[0039] The second EES sends a third message to the edge configuration server ECS, and the third message includes at least one of the following information: the first indication information and application information; the second EES receives the first information from the ECS, and the first information includes at least one of the following information: information of at least one EES, instantiation status information of the EAS corresponding to at least one EES, and time information of the EAS instantiation corresponding to at least one EES; the at least one EES includes the first EES.

[0040] In an embodiment of the present application, the first indication information or application information is used to determine whether the target EES (i.e., the first EES) of the ACR corresponding to the application needs to have an instantiable but uninstantiated EAS. Through this first indication information or application information, the ECS can be instructed to select a suitable target EES for the application, thereby providing better ACR services and edge computing services for the application.

[0041] In conjunction with the second aspect, in a possible implementation, the method further includes:

[0042] The second EES determines the first EES from the at least one EES based on at least one of the application information, the first indication information, information of the at least one EES, and instantiation state information of an EAS corresponding to the at least one EES.

[0043] In an embodiment of the present application, the second EES can select a suitable EES as the target EES of ACR by combining application information, first indication information, information of at least one EES, and instantiation status information of the EAS corresponding to at least one EES, thereby providing better ACR services and edge computing services for the application.

[0044] In conjunction with the second aspect, in a possible implementation, the method further includes:

[0045] The second EES determines an instantiation state corresponding to the first EAS based on the ACR type corresponding to the application, where the instantiation state of the first EAS includes an instantiated state, or the instantiation state of the first EAS includes an instantiable but uninstantiated state.

[0046] In an embodiment of the present application, the second EES determines the instantiation state of the first EAS based on the ACR type corresponding to the application, that is, the second EES determines that the first EAS is an instantiated EAS based on the ACR type, or that the first EAS is an instantiated but uninstantiated EAS. The second EES determines the instantiation state of the first EAS based on the ACR type so that the target EAS of the ACR corresponding to the application can match the ACR type, thereby providing better ACR services and edge computing services for the application.

[0047] In combination with the second aspect, in one possible implementation, the ACR type includes a common ACR type, and the instantiation state of the first EAS includes an instantiated state; or, the ACR type includes a service continuity planning ACR type, and the instantiation state of the first EAS includes an instantiable but uninstantiated state.

[0048] In the embodiment of the present application, for an ACR of the common ACR type, an instantiated EAS can be selected as the first EAS, which can reduce the duration of service interruption. For an ACR of the service continuity planning ACR type, an instantiable but uninstantiated EAS can be selected as the first EAS, and a new EAS can be instantiated for the AC, which can provide an EAS with better KPIs for the application.

[0049] With reference to the second aspect, in a possible implementation, the information of the first EAS includes at least one of the first EAS instantiation state information, the first EAS identification information, and the first EAS address information.

[0050] In a third aspect, an embodiment of the present application provides a communication method, which is applied to an EEC, and includes:

[0051] The EEC sends a first message to the first EES, where the first message is used to obtain information about the first EAS or report information about the first EAS. The first EAS is the target EAS for the application context migration ACR corresponding to the application. The first message includes first indication information, which is used to determine the first EAS. The EEC receives a second message from the first EES, where the second message includes information about at least one EAS, and the at least one EAS information includes the first EAS information.

[0052] In an embodiment of the present application, the first EAS is the target EAS of the ACR corresponding to the application, that is, the first EAS is the EAS to which the context information of the application is to be migrated. The first EAS is an instantiated EAS, or the first EAS is an EAS that can be instantiated but not instantiated. The EEC is the EEC corresponding to the application. The first EES is the target EES of the ACR corresponding to the application. The EEC can indicate the conditions that the target EAS (that is, the first EAS) required by the first EESACR (that is, the first EAS) must meet through the first indication information, so that the first EES can determine whether to select an EAS that can be instantiated but not instantiated for the application based on the first indication information, that is, it can enable the first EES to select a suitable EAS for the application to perform application context migration, thereby providing better ACR services and edge computing services for the application.

[0053] In combination with the third aspect, in a possible implementation method, the first indication information includes at least one of the following information: the application context migration ACR type corresponding to the application, indication information that the ACR corresponding to the application is a service continuity planning ACR or a common ACR, indication information of the instantiation status of the first EAS, and first time information; wherein, the first time information is used to indicate the time when the service continuity planning ACR is executed.

[0054] In an embodiment of the present application, the first indication information includes the ACR type corresponding to the application, indication information of whether the ACR corresponding to the application is a service continuity planning ACR or a common ACR, indication information of the instantiation status of the first EAS, and the first time information, so that the first EES can combine the ACR type corresponding to the application, indication information of whether the ACR corresponding to the application is a service continuity planning ACR or a common ACR, indication information of the instantiation status of the first EAS, and the first time information to select a suitable EAS for the application to perform application context migration, thereby providing better ACR services and edge computing services for the application.

[0055] In conjunction with the third aspect, in a possible implementation, the method further includes:

[0056] The EEC determines the first EAS from the at least one EAS based on at least one of the following information: a type of the ACR, instantiation state information of the first EAS, and the at least one EAS information.

[0057] In an embodiment of the present application, the EEC may determine the first EAS from at least one EAS based on the type of ACR and at least one EAS information, or the EEC may determine the first EAS from at least one EAS based on the instantiation status information of the first EAS and at least one EAS information. For example, the EEC may determine the instantiation status of the first EAS based on the type of ACR, and then select an EAS that matches the instantiation status of the first EAS from the at least one EAS. For example, if the instantiation status of the first EAS is instantiated, the EEC selects the instantiated EAS as the first EAS. For another example, if the instantiation status of the first EAS is instantiable but not instantiated, the EEC selects the instantiable but not instantiated EAS as the first EAS.

[0058] In an embodiment of the present application, the EEC combines the type of ACR, the instantiation status information of the first EAS, and at least one EAS information to select the target EAS corresponding to the ACR for the application, so as to select a suitable target EAS for the application for ACR, thereby providing better ACR services and edge computing services for the terminal device.

[0059] With reference to the third aspect, in a possible implementation, the first EAS information includes second time information, where the second time information is used to indicate a time when the first EAS is instantiated. The method further includes:

[0060] The EEC determines the first EAS from the at least one EAS based on the first time information and / or the second time information.

[0061] In an embodiment of the present application, the time for executing the service continuity plan ACR may also be referred to as the prediction expiration time, which is used to indicate the time when the terminal device corresponding to the application moves to the expected location or the service range of the target EAS. For example, the first time information includes a first duration, indicating that after the first duration, the terminal device moves to the expected location or the service range of the target EAS. The second time information is used to indicate the time when the first EAS is instantiated, that is, the second time information is used to indicate the time required for the first EAS to go from an uninstantiated state to an instantiated state. The EEC determines the first EAS in combination with the first time information and the second time information, and can select a suitable EAS for the application, reduce the service interruption time, and thus provide better ACR services and edge computing services for the terminal device.

[0062] For example, when the execution time of the service continuity planning ACR is less than the instantiation time of the first EAS, the EEC selects the instantiated EAS as the first EAS, that is, the first EES corresponds to the instantiated EAS, which can avoid increasing the ACR latency and the time of poor business performance. When the execution time of the service continuity planning ACR is greater than the instantiation time of the EAS, the EEC can select an instantiable but uninstantiated EAS as the first EAS, that is, the first EES corresponds to an instantiable but uninstantiated EAS, and instantiate a new EAS for the application, thereby providing the application with an EAS with better KPIs, and providing the application with better ACR services and edge computing services.

[0063] In conjunction with the third aspect, in one possible implementation, the method further includes:

[0064] The EEC sends a third message to the edge configuration server ECS, and the third message includes at least one of the following information: the first indication information and application information; the EEC receives first information from the ECS, and the first information includes at least one of the following information: information of at least one EES, instantiation status information of the EAS corresponding to at least one EES, and time information of the EAS instantiation corresponding to at least one EES; the at least one EES includes the first EES.

[0065] In an embodiment of the present application, the first indication information or application information is used to determine whether the target EES (i.e., the first EES) of the ACR corresponding to the application needs to have an instantiable but uninstantiated EAS. Through this first indication information or application information, the ECS can be instructed to select a suitable target EES for the application, thereby providing better ACR services and edge computing services for the application.

[0066] In conjunction with the third aspect, in a possible implementation, the method further includes:

[0067] The EEC determines the first EES from the at least one EES based on at least one of the application information, the first indication information, the information of the at least one EES, and the instantiation state information of the EAS corresponding to the at least one EES.

[0068] In an embodiment of the present application, the EEC combines application information, first indication information, information of at least one EES, and instantiation status information of the EAS corresponding to at least one EES to select a suitable EES as the target EES of ACR, thereby providing better ACR services and edge computing services for the application.

[0069] In conjunction with the third aspect, in a possible implementation, the method further includes:

[0070] The EEC determines an instantiation state corresponding to the first EAS based on the ACR type corresponding to the application, where the instantiation state of the first EAS includes an instantiated state or an instantiable but uninstantiated state.

[0071] In an embodiment of the present application, the EEC determines the instantiation state of the first EAS based on the ACR type corresponding to the application, that is, the EEC determines that the first EAS is an instantiated EAS based on the ACR type, or that the first EAS is an instantiated but uninstantiated EAS. The EEC determines the instantiation state of the first EAS based on the ACR type so that the target EAS of the ACR corresponding to the application can match the ACR type, thereby providing better ACR services and edge computing services for the application.

[0072] In combination with the third aspect, in one possible implementation, the ACR type includes a common ACR type, and the instantiation state of the first EAS includes an instantiated state; or, the ACR type includes a service continuity planning ACR type, and the instantiation state of the first EAS includes an instantiable but uninstantiated state.

[0073] In the embodiment of the present application, for an ACR of the common ACR type, an instantiated EAS can be selected as the first EAS, which can reduce the duration of service interruption. For an ACR of the service continuity planning ACR type, an instantiable but uninstantiated EAS can be selected as the first EAS, and a new EAS can be instantiated for the AC, which can provide an EAS with better KPIs for the application.

[0074] In a fourth aspect, an embodiment of the present application provides a communication method, which is applied to a first EES, and includes:

[0075] The first EES receives a first message, where the first message is used to request information of the first EAS, and the first message includes first indication information, where the first indication information is used to determine the first EAS, and the first EAS is the target EAS for the application context migration ACR corresponding to the application; the first EES sends a second message, where the second message includes information of at least one EAS, and the at least one EAS information includes the first EAS information.

[0076] In an embodiment of the present application, the first EES is the target EES of the ACR corresponding to the application, and the first EAS is the target EAS of the ACR corresponding to the application, that is, the first EAS is the EAS to which the context information of the application is to be migrated. The first EAS is an instantiated EAS, or the first EAS is an instantiated but uninstantiated EAS. The first EES can determine the conditions that the target EAS (that is, the first EAS) required by the ACR (that is, the first EAS) must meet through the first indication information, so that the first EES can determine whether to select an instantiated but uninstantiated EAS for the application based on the first indication information, that is, it can enable the first EES to select a suitable EAS for the application to migrate the application context, thereby providing better ACR services and edge computing services for the application.

[0077] In combination with the fourth aspect, in a possible implementation method, the first indication information includes at least one of the following information: the application context migration ACR type corresponding to the application, indication information that the ACR corresponding to the application is a service continuity planning ACR or a common ACR, indication information of the instantiation status of the first EAS, and first time information; wherein, the first time information is used to indicate the time when the service continuity planning ACR is executed.

[0078] In an embodiment of the present application, the first indication information includes the ACR type corresponding to the application, indication information of whether the ACR corresponding to the application is a service continuity planning ACR or a common ACR, indication information of the instantiation status of the first EAS, and the first time information, so that the first EES can combine the ACR type corresponding to the application, indication information of whether the ACR corresponding to the application is a service continuity planning ACR or a common ACR, indication information of the instantiation status of the first EAS, and the first time information to select a suitable EAS for the application to perform application context migration, thereby providing better ACR services and edge computing services for the application.

[0079] In combination with the fourth aspect, in a possible implementation, the first EES determines the first EAS based on the first indication information, and the instantiation state of the first EAS includes an instantiated state, or the instantiation state of the first EAS includes an instantiable but uninstantiated state.

[0080] In the embodiment of the present application, the first EES can determine, based on the first indication information, that the first EAS is an instantiated EAS or that the first EAS is an instantiated but uninstantiated EAS. That is, the first EES can determine, based on the first indication information, whether to select an instantiated but uninstantiated EAS for the application, i.e., the first EES can select an appropriate EAS for the application to perform application context migration, thereby providing better ACR services and edge computing services for the application.

[0081] In combination with the fourth aspect, in a possible implementation, when the ACR type includes a common ACR type or the first indication information includes indication information that the ACR corresponding to the application is a common ACR or the instantiation state of the first EAS includes an instantiated state, the first EAS includes an instantiated EAS; or, when the ACR type includes a service continuity planning ACR type or the first indication information includes indication information that the ACR corresponding to the application is a service continuity planning ACR or the instantiation state of the first EAS includes an instantiable but uninstantiated state, the first EAS includes an instantiable but uninstantiated EAS.

[0082] In an embodiment of the present application, when the ACR type includes a common ACR type or the first indication information includes indication information that the ACR corresponding to the application is a common ACR or the instantiation state of the first EAS includes an instantiated state, the first EES determines that the target EAS required by the ACR corresponding to the application is an instantiated EAS, that is, the first EAS includes an instantiated EAS. When the ACR type includes a service continuity planning ACR type or the first indication information includes indication information that the ACR corresponding to the application is a service continuity planning ACR or the instantiation state of the first EAS includes an instantiable but uninstantiated state, the first EES determines that the target EAS required by the ACR corresponding to the application is an instantiable but uninstantiated EAS, that is, the first EAS includes an instantiable but uninstantiated EAS. For an ACR of a common ACR type, an instantiated EAS can be selected, which can reduce the time of service interruption. For an ACR of a service continuity planning ACR type, an instantiable but uninstantiated EAS can be selected, and a new EAS can be instantiated for the AC, which can provide an EAS with a better KPI for the application.

[0083] With reference to the fourth aspect, in a possible implementation, the first indication information includes the first time information, and the first EES determines the first EAS based on the first indication information, including:

[0084] The first EES determines the first EAS based on the first time information and second time information, where the second time information is used to indicate the time when the first EAS is instantiated, and the instantiation state of the first EAS includes an instantiated state, or the instantiation state of the first EAS includes an instantiable but uninstantiated state.

[0085] In an embodiment of the present application, the time for executing the service continuity plan ACR may also be referred to as the prediction expiration time, which is used to indicate the time when the terminal device corresponding to the application moves to the expected location or the service range of the target EAS. For example, the first time information includes a first duration, indicating that after the first duration, the terminal device moves to the expected location or the service range of the target EAS. The second time information is used to indicate the time when the first EAS is instantiated, that is, the second time information is used to indicate the time required for the first EAS to go from an uninstantiated state to an instantiated state. The first EES determines the first EAS in combination with the first time information and the second time information, and can select a suitable EAS for the application, reduce the service interruption time, and thus provide better ACR services and edge computing services for the terminal device.

[0086] In combination with the fourth aspect, in a possible implementation method, when the execution time of the service continuity planning ACR is less than the instantiation time of the first EAS, the instantiation state of the first EAS includes an instantiated state; or, when the execution time of the service continuity planning ACR is greater than the instantiation time of the first EAS, the instantiation state of the first EAS includes an instantiable but not instantiated state.

[0087] In an embodiment of the present application, when the execution time of the service continuity planning ACR is less than the instantiation time of the first EAS, the first EES selects the instantiated EAS as the first EAS, that is, the instantiation state of the first EAS includes the instantiated state, which can avoid increasing the ACR latency and the time of poor business performance. When the execution time of the service continuity planning ACR is greater than the instantiation time of the EAS, the first EES can select an instantiable but uninstantiated EAS as the first EAS, that is, the instantiation state of the first EAS includes the instantiable but uninstantiated state, and instantiate a new EAS for the application, thereby being able to provide the application with an EAS with better KPIs, and being able to provide the application with better ACR services and edge computing services.

[0088] With reference to the fourth aspect, in a possible implementation, the first message comes from a second EES or an edge enabled client EEC; and the first EES sends the second message, including:

[0089] The first EES sends the second message to the second EES or the EEC.

[0090] In conjunction with the fourth aspect, in a possible implementation, the method further includes:

[0091] In a case where the instantiation state corresponding to the first EAS includes an instantiable but uninstantiated state, the first EES triggers an instantiation process of the first EAS to the network management system.

[0092] In an embodiment of the present application, when the instantiation state corresponding to the first EAS includes an instantiable but uninstantiated state, the first EES triggers the instantiation process for the first EAS to the network management system, instantiates a new EAS for the application, thereby providing the application with an EAS with better KPIs.

[0093] In a fifth aspect, an embodiment of the present application provides a communication device for executing the method in the first aspect or any possible implementation of the first aspect. The communication device includes a unit having the function of executing the method in the first aspect or any possible implementation of the first aspect.

[0094] In a sixth aspect, an embodiment of the present application provides a communication device for executing the method in the second aspect or any possible implementation of the second aspect. The communication device includes a unit having the function of executing the method in the second aspect or any possible implementation of the second aspect.

[0095] In a seventh aspect, an embodiment of the present application provides a communication device for executing the method in the third aspect or any possible implementation of the third aspect. The communication device includes a unit having the function of executing the method in the third aspect or any possible implementation of the third aspect.

[0096] In an eighth aspect, an embodiment of the present application provides a communication device for executing the method in the fourth aspect or any possible implementation of the fourth aspect. The communication device includes a unit having the function of executing the method in the fourth aspect or any possible implementation of the fourth aspect.

[0097] In the fifth aspect to the eighth aspect, the above-mentioned communication device and communication device may include a transceiver unit and a processing unit.

[0098] In a ninth aspect, an embodiment of the present application provides a communication device, comprising a processor configured to execute the method described in any one of the first to fourth aspects or any possible implementation thereof. Alternatively, the processor is configured to execute a program stored in a memory, and when the program is executed, the method described in any one of the first to fourth aspects or any possible implementation thereof is executed.

[0099] In a possible implementation, the memory is located outside the communication device.

[0100] In a possible implementation, the memory is located within the above-mentioned communication device.

[0101] In an embodiment of the present application, the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together.

[0102] In a possible implementation, the communication device further includes a transceiver, where the transceiver is configured to receive a signal or send a signal.

[0103] In a tenth aspect, an embodiment of the present application provides a communication device, which includes a logic circuit and an interface, wherein the logic circuit and the interface are coupled; the interface is used to receive first indication information; and the logic circuit is used to determine a first EES.

[0104] It can be understood that with respect to the communication device shown in the tenth aspect, reference can also be made to the first aspect or the specific implementation shown below.

[0105] In an eleventh aspect, an embodiment of the present application provides a communication device, which includes a logic circuit and an interface, wherein the logic circuit and the interface are coupled; the interface is used to output a first message and receive a second message.

[0106] It can be understood that, with respect to the communication device shown in the eleventh aspect, reference can also be made to the second aspect or the specific implementation shown below.

[0107] In a twelfth aspect, an embodiment of the present application provides a communication device, which includes a logic circuit and an interface, wherein the logic circuit and the interface are coupled; the interface is used to output a first message and receive a second message.

[0108] It can be understood that with respect to the communication device shown in the twelfth aspect, reference can also be made to the third aspect or the specific implementation shown below.

[0109] In a thirteenth aspect, an embodiment of the present application provides a communication device, which includes a logic circuit and an interface, wherein the logic circuit and the interface are coupled; the interface is used to input a first message and output a second message.

[0110] It can be understood that with respect to the communication device shown in the thirteenth aspect, reference can also be made to the fourth aspect or the specific implementation shown below.

[0111] In the fourteenth aspect, an embodiment of the present application provides a computer-readable storage medium, which is used to store a computer program. When the computer program is run on a computer, the method shown in any aspect of the first to fourth aspects or any possible implementation method is executed.

[0112] In the fifteenth aspect, an embodiment of the present application provides a computer program product, which includes a computer program. When the computer program is run on a computer, the method shown in any aspect of the first to fourth aspects or any possible implementation is executed.

[0113] In the sixteenth aspect, an embodiment of the present application provides a computer program. When the computer program is run on a computer, the method shown in any aspect or any possible implementation of the above-mentioned first to fourth aspects is executed.

[0114] In the seventeenth aspect, an embodiment of the present application provides a communication system, which includes at least two of the following: an ECS, a first EES, a second EES or an EEC, the ECS is used to execute the method shown in the above-mentioned first aspect or any possible implementation of the first aspect, the second EES is used to execute the method shown in the above-mentioned second aspect or any possible implementation of the second aspect, the EEC is used to execute the method shown in the above-mentioned third aspect or any possible implementation of the third aspect, and the first EES is used to execute the method shown in the above-mentioned fourth aspect or any possible implementation of the fourth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0115] The following is an introduction to the drawings related to the embodiments of this application.

[0116] FIG1 is a schematic diagram of a system architecture provided in an embodiment of the present application;

[0117] FIG2 is a schematic diagram of an ACR process provided in an embodiment of the present application;

[0118] FIG3 is a schematic diagram of a process of instantiating an EAS according to an embodiment of the present application;

[0119] FIG4A is an interactive diagram of a communication method provided in an embodiment of the present application;

[0120] FIG4B is an interactive diagram of another communication method provided in an embodiment of the present application;

[0121] FIG5A is an interactive diagram of another communication method provided in an embodiment of the present application;

[0122] FIG5B is an interactive diagram of another communication method provided in an embodiment of the present application;

[0123] FIG6 is an interactive diagram of another communication method provided in an embodiment of the present application;

[0124] FIG7 is an interactive diagram of another communication method provided in an embodiment of the present application;

[0125] FIG8 is an interactive diagram of another communication method provided in an embodiment of the present application;

[0126] FIG9 is an interactive diagram of another communication method provided in an embodiment of the present application;

[0127] FIG10 is an interactive diagram of another communication method provided in an embodiment of the present application;

[0128] FIG11 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0129] FIG12 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0130] FIG13 is a schematic structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0131] The terms "first" and "second" in the specification, claims and drawings of this application are only used to distinguish different objects, and are not used to limit the order, timing, priority or importance of multiple objects. In the embodiments of the present application, "multiple" refers to two or more. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes other steps or units inherent to these processes, methods, products or devices. In addition, the character " / ", unless otherwise specified, generally indicates that the objects associated before and after are in an "or" relationship.

[0132] References to "embodiments" herein mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it refer to independent or alternative embodiments that are mutually exclusive of other embodiments. It will be understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

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

[0134] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: global system of mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, fifth generation (5G) system or new radio (NR), etc.

[0135] The terminal device in the embodiments of the present application may refer to user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal device may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network or a terminal device in an evolved public land mobile network (PLMN), etc., and the embodiments of the present application are not limited to this.

[0136] The network device in the embodiment of the present application can be a device for communicating with a terminal device. The network device can be a base station (base transceiver station, BTS) in a global system of mobile communication (GSM) system or code division multiple access (CDMA), or a base station (NodeB, NB) in a wideband code division multiple access (WCDMA) system, or an evolved base station (eNB or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (CRAN) scenario, or the network device can be a relay station, an access point, an on-board device, a wearable device, a network device in a 5G network, or a network device in an evolved PLMN network, etc., and the embodiment of the present application is not limited.

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

[0138] Multi-access edge computing (MEC): MEC refers to cloud computing at the edge of the network. It deploys computing power closer to users, reducing network latency and providing them with computing power and applications close to their location, significantly improving the service experience. MEC leverages wireless access networks to provide telecom users with information technology (IT) services and cloud computing capabilities close to their location. This creates a carrier-grade service environment with high performance, low latency, and high bandwidth, accelerating the download of content, services, and applications across the network, ensuring users enjoy an uninterrupted, high-quality network experience.

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

[0140] Local Data Network (local DN): A local data network is an access point to a data network that is very close to the user's attachment point.

[0141] Application context: Application context refers to the operational status information associated with a user or group of users. Optionally, the application context may also include the subscription context of the user or users in the source application instance or edge application server (EAS) and the core network, such as the subscription transaction identifier. Optionally, the application context may also include the subscription context of the user or users on the edge enabler server (EES), such as the transaction identifier of the source EAS subscription to the user or users.

[0142] Figure 1 is a schematic diagram of a system architecture provided by an embodiment of the present application. The following briefly introduces the functional entities and interfaces involved in Figure 1.

[0143] Edge Data Network (EDN): In one possible implementation, an EDN corresponds to a data network, a special local data network (local DN), which can include edge-enabling functions and can be identified using a data network access identifier (DNAI) and a data network name (DNN). It is a network logical concept. In another possible implementation, the EDN is a peer-to-peer concept of the central cloud, which can be understood as a local data center (geographical concept), can be identified using a DNAI, and can include multiple local data networks.

[0144] Application instance or edge application server (EAS): An edge application is an application deployed in an edge data network. Specifically, an edge application may refer to an instance of a server application (e.g., social media software, augmented reality (AR), virtual reality (VR)) deployed and running on an EDN. An application may deploy one or more EASs in one or more ENDs. EASs deployed and running in different EDNs may be considered as different EASs of an application. They may share a domain name, use an IP address, or use different IP addresses. For example, EAS may also be referred to as an edge application server, application instance, edge application instance, MEC application server, EAS function, etc.

[0145] Application Client (AC): The application client is the peer entity of the edge application on the terminal device side. The application client is used by the application user to obtain application services from the edge application EAS. The application client is a client program applied on the terminal device side. The application client can connect to the application server in the cloud to obtain application services, or it can connect to the edge application EAS deployed and running in one or more EDNs to obtain application services.

[0146] Edge enabler server (EES): The edge enabler server EES can provide some enabling capabilities for the edge application EAS deployed in the EDN, which can better support the deployment of edge applications in the MEC. For example, the EES can support EAS registration, authentication and authorization of terminal devices, and provide EAS IP address information for terminal devices. For example, the EES can further support obtaining the EAS identification and IP address information, and further send the EAS identification and IP address information to the edge data network configuration server. For example, the EES can be deployed in the EDN. Generally, the EAS is registered on an EES, or the information of an EAS is configured on an EES through the management system. The EES is called the EES associated with the EAS, and the EES controls or manages the EAS registered or configured on the EES. That is, the EAS associated with the EES indicates the EAS registered on the EES, or the EAS managed by the EES. The EES can obtain EAS information from the network management system or through pre-configuration.

[0147] Edge Enabler Client (EEC): The EEC is the EES's counterpart on the terminal device side. The EEC is responsible for registering EEC information and application client information with the EES, performing security authentication and authorization, obtaining the EAS IP address from the EES, and providing edge computing capabilities to the application client. Examples include EAS discovery services and returning the EAS IP address to the application client.

[0148] In the embodiment of the present application, a terminal device may include one or more EECs or ACs. It should be understood that in the embodiment of the present application, the EEC and the terminal device may be replaced with each other in some cases.

[0149] Edge Configuration Server (ECS): The ECS is responsible for configuring the EDN. For example, the ECS can provide EES information to terminal devices, provide EAS information to terminal devices, and interact with the application's DNS to obtain EAS information. For example, the ECS can also obtain and store EAS and IP address information from other functional entities.

[0150] For example, an application user signs a service agreement with the application provider to provide services to the application user. The application user logs in to the application client on the terminal device and communicates with the EAS through the connection between the application client and the EAS. The edge enabling client is a middleware layer that can be located in the operating system or between the application client and the operating system. The application client can obtain edge enabling services from the edge enabling client in the form of an application programming interface (API).

[0151] For example, during the operation of an edge application, when a terminal device moves outside the current service area, such as when a terminal device moves between edge data networks (EDNs) or local area data networks (LADNs), the edge application server EAS currently providing services may not be able to continue to provide services for the currently running application, or the edge application server EAS currently providing services is no longer the optimal application server that can provide services for the terminal device. Other EASs may be more suitable for serving the application client on the terminal device, so a new edge application server EAS needs to be selected to provide services for the terminal device. That is, the application context information of the terminal device needs to be migrated from the current EAS to the new EAS. This process can be called application context migration or application context relocation (ACR).

[0152] FIG2 is a schematic diagram of the ACR process according to an embodiment of the present application. ACR may include the following stages:

[0153] 1. Application context migration detection: Application context migration detection is to determine whether context migration may be required. The detection entity can detect some events, such as: terminal device location change, terminal device user plane path update, etc. The detection entity may include EEC, EAS, EES, etc.

[0154] 2. Decision on application context migration: The need for ACR is determined by a decision-making entity, which may include EEC, EAS, EES, etc.

[0155] 3. Execution of Application Context Migration: Execution of application context migration primarily involves transferring the AC's context information from the source EAS to the target EAS, which can be a predicted EAS or an EAS already moved to. This step can be performed by an execution entity, including an EES or EAS. For example, the execution entity can also notify the terminal device of the target EAS information, or notify the network of the completion of the context migration or relevant information about the target EAS (such as the address of the target EAS, the N6 routing information corresponding to the target EAS, etc.).

[0156] As an example and not a limitation, when the location of a terminal device changes, the ACR detection entity predicts that the EAS of the terminal device will change, and can send the context information of the terminal device from the source EAS to the predicted target EAS in advance. This type of ACR that transmits context information to the target EAS in advance corresponds to the ACR for service continuity planning. The ACR for service continuity planning can transmit the context information of the terminal device in the source EAS to the target EAS in advance through prediction, avoiding service interruption caused by context migration after the terminal device moves to the target EAS.

[0157] As an example and not a limitation, when the user plane path of a terminal device changes, the terminal device has been disconnected from the source EAS and connected to the target EAS, the ACR detection entity determines that the EAS of the terminal device has changed and sends the context information of the source EAS to the target EAS. This ACR type may correspond to a normal ACR.

[0158] 4. Cleanup after application context migration: This step involves multiple entities (such as AC, EEC, EAS, EES, etc.). For example, AC initiates a new socket connection to the target EAS.

[0159] It is understood that the detection, decision-making, execution, and cleanup of ACRs can be performed by different functional entities. For example, when the type of ACR event corresponds to an ACR for service continuity planning, since the target EES and target EAS have not yet been discovered, the ACR detection is performed by the EEC or the source EES or source EAS.

[0160] For example, before performing application context migration, it is necessary to perform EES discovery and EAS discovery processes to discover the target EES and target EAS. For example, the EES discovery and EAS discovery processes can follow a two-level discovery mechanism, that is, first discovering the EES platform, and then discovering the EAS from the EES platform. The EES platform discovery and EAS discovery processes may include the following steps:

[0161] S1: The EEC of the terminal device discovers the EES platform from the ECS.

[0162] Exemplarily, the EEC requests or subscribes to the EES platform corresponding to the terminal device location from the ECS. The EEC then discovers the EES-enabled platform or EDN of interest from the ECS. The ECS platform contains detailed information about the EAS. The ECS can obtain the DNAI based on the terminal device's location, and combine the DNAI with the fully qualified domain name (FQDN) and the EES profile to select the appropriate EES for each AC or EEC. Exemplarily, the ECS can combine the terminal device location and other optional filters when selecting the EES platform for the AC or EEC.

[0163] The EEC or ECS obtains the current or potential DNAI, which may represent the location information of the terminal device, and may select an EES that is closer to the terminal device based on the DNAI.

[0164] For example, the EEC may obtain information of one or more EESs from the ECS.

[0165] S2: EEC discovers EAS from the EES platform.

[0166] Exemplarily, the EEC sends a discovery request message to the EES to discover the application to be accessed.

[0167] EES matches the information of registered applications. For example, EES matches EASs that meet the user's request based on the information of locally registered or online EASs and the discovery filter parameters provided by the user. If multiple EASs meet the user's request, EES can return information for multiple EASs to EEC.

[0168] The EES returns the EAS information to the EEC. For example, after receiving the EAS information, the EEC may also provide the EAS information to the AC so that the AC can connect to the EAS.

[0169] In some possible implementations, when an EEC or AC requests an available EAS, but there is no EAS available on the current EES or EDN, the EES can trigger EAS instantiation to the edge computing service provider (ECSP) management system based on the needs of the terminal device. Alternatively, during the initial EAS discovery and target EAS discovery process, the EES or target EES (T-EES) can trigger the ECSP management system to perform EAS instantiation. The process of instantiating an EAS is shown in Figure 3:

[0170] 301. The application service provider (ASP) creates a managed object instance (MOI) required by EAS to request the ECSP to deploy EAS.

[0171] 302. The ECSP creates an MOI response to indicate to the ASP that the request to deploy the EAS has been received and that the EAS deployment is in progress.

[0172] 303, the ECSP analyzes EAS requirements (eg, required EAS KPIs, deployment location, etc.) to determine the operation of the EAS virtual network function (VNF).

[0173] 304. ECSP requests the NFV management network element to instantiate the EAS VNF.

[0174] 305 , the NFV management system indicates the result of the EAS instantiation to the ECSP.

[0175] 306. When the EAS is instantiated successfully, the ECSP creates an MOI for the EAS information managed object (IOC).

[0176] 307, if the EAS is instantiated successfully, the ECSP creates an MOI for the EAS requirement IOC.

[0177] 308. The ESCP indicates the EAS instantiation result to the ASP.

[0178] As can be seen from Figure 3, it takes a certain amount of time and process for the ECSP management system to execute EAS instantiation. For ordinary ACR (for example, when the UE cannot obtain services on the source EAS (source EAS, S-EAS), or when the service performance obtained by the terminal device on the source EAS degrades, the terminal device needs to immediately migrate from the source EAS to the target EAS), executing EAS instantiation in this type of application context process will further increase the service interruption time or increase the time for the service performance obtained by the terminal device to degrade. For service continuity planning (service continuity planning) ACR, the service continuity planning ACR can perform target EAS discovery and application context transmission (application context transmission, ACT) in advance based on the predicted location of the terminal device. At this time, the terminal device does not need to connect to the target EAS immediately, so when there is no available EAS on the EES or EDN, the EES can trigger EAS instantiation for the EEC or AC. At this time, the instantiated EAS can be used as the target EAS. At this time, the terminal device can obtain better service performance from the instantiated EAS without increasing the service interruption time or the time of service performance degradation.

[0179] Generally, in the target EES discovery process, the ECS selects a target EES for the terminal device based on the EAS discovery filter and application information. In the target EAS discovery process, the target EES can select a target EAS for the terminal device based on the EAS discovery filter and application information. Then, in the above-mentioned target EAS or target EES discovery process, when there is no available EAS on the target EES, the EAS instantiation process needs to be triggered. In some cases (such as ordinary ACR), this will lead to an increase in service interruption time or an increase in the time that the service performance obtained by the terminal device degrades.

[0180] In view of this, an embodiment of the present application provides a communication method that can select a suitable EES or EAS for an application during the ACR process. Through the method provided in the embodiment of the present application, a target EES with the required EAS can be discovered, thereby avoiding an increase in service interruption time or an increase in the time of service performance degradation obtained by the terminal device due to EAS instantiation in the ordinary ACR process. Alternatively, through the method provided in the embodiment of the present application, a suitable EAS can be discovered for the terminal device, which can provide better performance based on the ACR type or avoid an increase in service interruption time, thereby providing better ACR services and edge computing services for the application. The method provided in the embodiment of the present application can be applied to the communication method shown in Figure 1.

[0181] It can be understood that the information involved in the embodiments of the present application can be carried in different messages. The information-carrying messages shown in the embodiments of the present application are only examples, and the present application does not limit the information-carrying messages.

[0182] It is understood that the various methods provided in the embodiments of this application can be combined with each other to form new embodiments. The order of combination can be determined based on the specific implementation, and the embodiments of this application will not be listed one by one.

[0183] Please refer to Figure 4A, which is an interactive diagram of a communication method provided by an embodiment of the present application. As shown in Figure 4A, the EES, EAS, ECS, etc. involved in the method can refer to the relevant description above and will not be described in detail here. It is understandable that although the method shown below does not involve a relay node, those skilled in the art will know that when the sender and receiver communicate, the forwarding operation can be performed through the relay node. As shown in Figure 4A, the method includes but is not limited to the following steps:

[0184] 401, the EEC or the second EES sends a first indication message, and the ECS receives the indication message accordingly. The first indication message is used to determine the first EES, which is the target EAS of the ACR corresponding to the application, that is, the first EAS is the EAS to which the application context is to be migrated.

[0185] Exemplarily, the application can be identified by one or more of an AC identifier (AC identifier, ACID), an application identifier (application ID), and an EAS identifier (EAS identifier, EASID). The first indication information includes at least one of the following information: the ACR type corresponding to the application, indication information that the ACR corresponding to the application is a service continuity planning ACR or a common ACR, indication information of the instantiation state of the first EAS, and the first time information. The first time information is used to indicate the time when the service continuity planning ACR is executed. The time when the service continuity planning ACR is executed can also be called the prediction expiration time, which is used to indicate the time when the terminal device corresponding to the application moves to the expected location or the service range of the target EAS. For example, the first time information includes a first duration, indicating that after the first duration, the terminal device moves to the expected location or the service range of the target EAS.

[0186] Exemplarily, the ACR type (ACR type) corresponding to the application may include a service continuity planning ACR or a normal ACR. Service continuity planning ACR means initiating application context migration in advance based on the predicted location of the terminal device corresponding to the application, so that after the terminal device moves to the predicted location, the AC can be directly connected to the target EAS. Normal ACR means that based on the current location of the terminal device corresponding to the application, the terminal device cannot obtain application context migration at the current location.

[0187] Exemplarily, the above-mentioned indication information of the instantiation state of the first EAS may indicate that the instantiation state of the first EAS is an instantiated state, or the indication information of the instantiation state of the first EAS may indicate that the instantiation state of the first EAS is an instantiable but uninstantiated state, which may be used to indicate the need for the instantiation state of the first EAS.

[0188] As an example, the first indication information includes an ACR type field, which indicates the ACR type corresponding to the application. For example, if the ACR type field is x, it indicates that the ACR type corresponding to the application is a service continuity planning ACR; if the ACR type field is y, it indicates that the ACR type corresponding to the application is a normal ACR. It can be understood that x and y represent different values ​​of the ACR type field, and x and y can be different values. For example, x can be 0, y can be 1, or x and y can also take other values, which are not limited in this application.

[0189] Exemplarily, the second EES may be the EES corresponding to the source EAS currently providing services for the application. The second EES may obtain the ACR type corresponding to the application from the source EAS, or the second EES may determine the ACR type corresponding to the application based on the business requirements of the application. The EEC may be the EEC corresponding to the application. The EEC may determine the ACR type corresponding to the application based on the business requirements of the application.

[0190] It is understood that the EEC can be an entity on the terminal device. In the embodiments of the present application, the EEC, AC, and terminal device can be interchangeable. That is, the steps or functions performed by the EEC in the embodiments of the present application can be replaced by those performed by the terminal device or AC.

[0191] As an example, the first indication information may be carried in a third message, and the third message may also include application information. The application information may include at least one of ACID, application identifier, and EASID. The application information is used to indicate the application for which ACR is to be performed.

[0192] Exemplarily, the third message may include a retrieve T-EES request or a service provisioning request message, and the retrieval T-EES request message or the service provisioning request message may also include at least one of the following: an EAS discovery filter, a UE identifier (UEID), an AC identifier (ACID), and an EAS identifier. The EAS discovery filter is used to indicate the conditions satisfied by the target EAS (i.e., the first EAS) required for the application, and the EAS identifier is used to indicate the required target EAS.

[0193] It can be understood that the retrieval T-EES request message or service configuration request message is only an example, and the third message can also include other messages, that is, the first indication information can also be carried in other messages, which is not limited in this application.

[0194] 402. The ECS determines a first EES based on the first indication information.

[0195] For example, the ECS may determine the first EES based on the first indication information and at least one of the following: the instantiation state of the EAS associated with at least one EES corresponding to the ECS, and second time information. The second time information is used to indicate the time when the first EAS was instantiated, or the time required for the EAS to change from an uninstantiated state to an instantiated state, or the time required for the EAS to be instantiated.

[0196] For example, the second time information may be applicable to one EAS (e.g., the first EAS), that is, the second time information is used to indicate the time when the first EAS is instantiated. Alternatively, the second time information may be applicable to multiple EASs (e.g., a certain type of EAS), and the second time information is used to indicate the time required for EAS instantiation.

[0197] Exemplarily, the second time information may be based on historical time information or predicted time information. The ECS may obtain the second time information from a network management system or may configure the second time information locally.

[0198] Exemplarily, the ECS may be associated with at least one EES, and the ECS maintains information of at least one EES, and the information of at least one EES includes instantiation status information of the EAS corresponding to each EES. The instantiation status information of the EAS may include instantiated or instantiable but not instantiated, or the EAS instantiation status information may include at least one of information of an instantiable but not instantiated EAS, an EAS identifier (EASID) of an instantiable but not instantiated EAS, information of an instantiated EAS, and an EASID of an instantiated EAS. Exemplarily, the ECS may obtain information of at least one EES through a registration request message from at least one EES. Each EES corresponds to at least one EAS, and each EAS corresponds to instantiation status information; or the EAS instantiation types corresponding to the EES include: instantiable but not instantiated, instantiated, wherein the instantiable but not instantiated state corresponds to at least one EAS, and the instantiated state corresponds to at least one EAS.

[0199] For example, regarding the ECS determining the first EES based on the first indication information, the embodiment of the present application further provides the following implementation methods:

[0200] Implementation Method 1: The ECS may determine the first EES from the at least one EES based on the instantiation status of the EAS associated with the at least one EES corresponding to the ECS based on the first indication information. Exemplarily, the ECS determines based on the first indication information whether to select the EES corresponding to the instantiated EAS or the EES corresponding to the EAS that is instantiable but not instantiated.

[0201] As an example, the first indication information includes an ACR type corresponding to the application, or the first indication information includes indication information for indicating whether the corresponding ACR is a service continuity ACR or a common ACR.

[0202] In the case where the ACR type is a common ACR type, or the first indication information includes indication information that the ACR corresponding to the application is a common ACR, if EAS instantiation is performed during the application context process, it will further lead to an increase in service interruption time or an increase in the time during which the service performance obtained by the terminal device decreases. Therefore, the ECS determines to select the EES corresponding to the instantiated EAS, which can avoid an increase in service interruption time or an increase in the time during which the service performance obtained by the terminal device decreases. Exemplarily, the ECS selects an EES associated with the instantiated EAS from the at least one EES as the first EES based on the instantiation state of the EAS corresponding to the at least one EES, that is, the first EES corresponds to the instantiated EAS.

[0203] In the case of the above-mentioned ACR type service continuity planning ACR type, or the first indication information includes indication information that the ACR corresponding to the application is a service continuity planning ACR, the discovery and ACT of the target EAS can be performed in advance based on the predicted location of the terminal device, and the terminal device does not need to connect to the target EAS immediately. In this case, the ECS can select the EES corresponding to the instantiated but uninstantiated EAS, so that the EES triggers EAS instantiation for the terminal device, thereby enabling the terminal device to obtain better service performance from the instantiated EAS without increasing the service interruption time or the service performance degradation time. Exemplarily, the ECS selects an EES associated with an instantiated but uninstantiated EAS from the at least one EES as the first EES based on the instantiation status of the EAS corresponding to the at least one EES, that is, the above-mentioned first EES corresponds to an instantiated but uninstantiated EAS.

[0204] As another example, the first indication information includes indication information of the instantiation state of the first EAS. The ECS determines an EES that matches the instantiation state of the first EAS from at least one EES as the first EES. For example, when the instantiation state of the first EAS is an instantiated state, the ECS selects an EES associated with an instantiated EAS from at least one EES based on the instantiation state of the EAS corresponding to at least one EES as the first EES, that is, the first EES corresponds to an instantiated EAS. For another example, when the instantiation state of the first EAS is an instantiable but uninstantiated state, the ECS selects an EES associated with an instantiable but uninstantiated EAS from at least one EES based on the instantiation state of the EAS corresponding to at least one EES as the first EES, that is, the first EES corresponds to an instantiable but uninstantiated EAS.

[0205] As another example, the first indication information includes first time information. In this case, the ACR corresponding to the application may be a service continuity ACR. The ECS may determine whether to select the EES corresponding to the instantiated EAS or the EES corresponding to the instantiated but uninstantiated EAS based on the execution time of the service continuity planning ACR. For example, the first time information includes a first duration. If the first duration is greater than or equal to a first threshold, it indicates that the terminal device corresponding to the application will move to the expected location after a long time. Executing the EAS instantiation process during the ACR process will not increase the service interruption time. Therefore, the ECS determines to select the EES corresponding to the instantiated but uninstantiated EAS as the first EES, that is, the first EES corresponds to the instantiated but uninstantiated EAS. If the first duration is less than or equal to the first threshold, it indicates that the terminal device corresponding to the application moves to the expected location within a short time. Executing the EAS instantiation process during the ACR process will increase the service interruption time. Therefore, the ECS determines to select the EES corresponding to the instantiated EAS as the first EES, that is, the first EES corresponds to the instantiated EAS.

[0206] It is understood that the first threshold can be configured by the ECS based on the business needs of the application, or the first threshold can be obtained by the ECS from the operations, administration, and maintenance (OAM) system, or the first threshold can be obtained by the EES from the OAM system and sent to the ECS. The first threshold can apply to one EAS or multiple EASs. The first threshold can be determined by historical values ​​or predicted values.

[0207] Implementation method 2: The ECS may determine the first EES from the at least one EES based on the first indication information, the instantiation state of the EAS associated with the at least one EES corresponding to the ECS, and the second time information.

[0208] For example, the ECS can obtain information about at least one EES via a registration request message from at least one EES. Each EES corresponds to at least one EAS, and each EAS corresponds to instantiation status information and time information required for instantiation. Specifically, the registration request message sent by the first EES to the ECS carries the second time information, indicating the time required for instantiation of the first EAS.

[0209] As an example, the above-mentioned first indication information includes first time information, and the ECS can determine the first EES from the at least one EES based on the first time information, the second time information and the instantiation status of the EAS associated with the at least one EES. Exemplarily, the ECS can determine to select the EES corresponding to the instantiated EAS as the first EES based on the comparison result of the execution time of the ACR and the time required for the instantiation of the first EAS, or to select the EES corresponding to the EAS that can be instantiated but not instantiated as the first EES. For example, when the execution time of the service continuity planning ACR is less than the instantiation time of the first EAS, the ECS determines to select the EES corresponding to the instantiated EAS as the first EES, that is, the first EES corresponds to the instantiated EAS. For another example, when the execution time of the service continuity planning ACR is greater than or equal to the instantiation time of the first EAS, the ECS determines to select the EES corresponding to the EAS that can be instantiated but not instantiated as the first EES, that is, the first EES is associated with the EAS that can be instantiated but not instantiated.

[0210] It is understandable that when the execution time of the service continuity plan ACR is equal to the instantiation time of the first EAS, the ECS can select the EES corresponding to the instantiated EAS, or select the EES corresponding to the EAS that can be instantiated but has not been instantiated.

[0211] In some possible implementations, the method shown in FIG4A further includes step 403 .

[0212] 403. The ECS sends first information, and the second EES or EEC receives the first information accordingly. The first information includes at least one of the following: information about at least one EES, instantiation status information of an EAS associated with at least one EES, and information about the first EES. The at least one EES includes the first EES.

[0213] Exemplarily, the information of the at least one EES may include identification information of each EES in the at least one EES, EES address information, etc. The instantiation state information of the EAS associated with the at least one EES may include the instantiation state of the EAS corresponding to the EES.

[0214] It is understood that, when the first indication information comes from the second EES, the ECS sends the first information to the second EES. When the first indication information comes from the EEC, the ECS sends the first information to the EEC.

[0215] Exemplarily, the first information may be carried in a retrieve T-EES response or a service provisioning response message.

[0216] In one possible implementation, the first information includes information of the first EES. After the ECS determines the first EES from at least one EES based on the first indication information, it can send the information of the first EES to the second EES or EEC by retrieving a T-EES response message or a service configuration response message.

[0217] In an embodiment of the present application, the ECS can discover the target EES with the required EAS based on at least one of the ACR type, the first time information, and the EAS instantiation status information. For example, the ECS determines whether to select the EES corresponding to the EAS that can be instantiated but not instantiated based on at least one of the ACR type, the first time information, and the EAS instantiation status information. For example, when the ACR corresponding to the application is a normal ACR, or the ACR corresponding to the application is a service continuity planning ACR and the execution time of the service continuity planning ACR is longer than the time of EAS instantiation, selecting the EES corresponding to the instantiated EAS can reduce the time of service interruption. When the ACR corresponding to the application is a service continuity planning ACR, or the execution time of the service continuity planning ACR is longer than the time of EAS instantiation, selecting the EES corresponding to the EAS that can be instantiated but not instantiated. In this case, when the instantiated EAS cannot provide a better KPI, the EES can trigger the OAM system to trigger the EAS instantiation, which can provide the UE with an EAS with a better KPI, thereby providing the UE with better ACR services and edge computing services.

[0218] Please refer to Figure 4B, which is an interactive diagram of another communication method provided by an embodiment of the present application. As shown in Figure 4B, the EES, EAS, ECS, etc. involved in this method can refer to the relevant description above and will not be described in detail here. It is understandable that although the method shown below does not involve a relay node, those skilled in the art will know that when the sender and receiver communicate, the forwarding operation can be performed through the relay node. As shown in Figure 4B, the method includes but is not limited to the following steps:

[0219] Optionally, the method shown in FIG4B may include step 404 .

[0220] 404 , the second EES or EEC sends a third message. Accordingly, the ECS receives the third message, where the third message is used to obtain information of at least one EES.

[0221] Optionally, the third message includes at least one of the following information: first indication information, application information, identification information of the second EES, UE identification, and EEC identification.

[0222] It is understandable that for the specific description of the first indication information and application information, reference can be made to the relevant description in step 401, which will not be described in detail here.

[0223] 405 , the ECS sends first information, and correspondingly, the second EES or EEC receives the first information, where the first information includes information of at least one EES and instantiation status information of an EAS associated with at least one EES.

[0224] Exemplarily, the at least one EES is an EES that matches the application. The second EES or EEC may send application information to the ECS, and the ECS determines at least one EES that matches the application based on the application information.

[0225] Exemplarily, the first information may be carried in a retrieve T-EES response or a service configuration response message.

[0226] 406 , the second EES or EEC determines the first EES based on the first indication and the first information.

[0227] In one possible implementation, the first information may further include second time information, which is used to indicate the time information required for instantiation of the EAS corresponding to the at least one EES. The second EES or EEC determines the first EES from the at least one EES based on at least one of the application information, the first indication information, the second time information, and the instantiation status information of the EAS corresponding to the at least one EES. For example, the second EES or EEC may determine the first EES that matches the application from the at least one EES based on the application information, or the second EES or EEC may determine the first EES from the at least one EES based on the first indication information and the second time information, or the second EES or EEC may determine the first EES from the at least one EES based on the first indication information and the instantiation status information of the EAS corresponding to the at least one EES.

[0228] It is understandable that the specific implementation manner in which the second EES or EEC determines the first EES may refer to the specific implementation manner in which the ECS determines the first EES in step 402, which will not be described in detail here.

[0229] In an embodiment of the present application, the ECS may send information of at least one EES to the second EES or ECS, and then the second EES or EEC may determine the first EES from the at least one EES. The second EES or EEC may be able to discover the target EES with the required EAS based on at least one of the ACR type, the first time information, and the EAS instantiation status information. For example, the second EES or EEC determines whether to select the EES corresponding to the EAS that can be instantiated but not instantiated based on at least one of the ACR type, the first time information, and the EAS instantiation status information. For example, when the ACR corresponding to the application is a normal ACR, or the ACR corresponding to the application is a service continuity planning ACR and the execution time of the service continuity planning ACR is greater than the EAS instantiation time, selecting the EES corresponding to the instantiated EAS can reduce the service interruption time. When the ACR corresponding to the application is a service continuity planning ACR, or the execution time of the service continuity planning ACR is greater than the EAS instantiation time, selecting the EES corresponding to the EAS that can be instantiated but not instantiated. In this case, when the instantiated EAS cannot provide better KPIs, the EES can trigger the OAM system to trigger EAS instantiation, thereby providing the UE with an EAS with better KPIs, thereby providing the UE with better ACR services and edge computing services.

[0230] Please refer to Figure 5A, which is an interactive diagram of another communication method provided by an embodiment of the present application. As shown in Figure 5A, the EES, EAS, ECS, etc. involved in this method can refer to the relevant description above and will not be described in detail here. It is understandable that although the method shown below does not involve relay nodes, those skilled in the art will know that when the sender and receiver communicate, forwarding operations can be performed through relay nodes. As shown in Figure 5A, this method includes but is not limited to the following steps:

[0231] 501. The second EES or EEC sends a first message to the first EES. Accordingly, the first EES receives the first message. The first message is used to obtain information about the first EAS or report information about the first EAS. The first message includes first indication information. The first EAS is the target EAS of the ACR corresponding to the application. The first indication information is used to determine the first EAS.

[0232] Exemplarily, the first indication information includes at least one of the following information: an ACR type corresponding to the application, indication information of whether the ACR corresponding to the application is a service continuity planning ACR or a common ACR, indication information of the instantiation state of the first EAS, and first time information. The first time information is used to indicate the time when the service continuity planning ACR is executed.

[0233] Exemplarily, the information of the first EAS may include an identifier of the first EAS, and the first message is used to report the identifier of the first EAS to indicate the first EAS.

[0234] Exemplarily, the first message may include an EAS discovery request message or an EAS information provisioning message, configured to request information about the first EAS from the second EES. The first message may also include an EAS discovery filter, configured to indicate conditions that the first EAS must meet.

[0235] It is understandable that for the specific description of the second EES, EEC, first indication information, etc., reference can be made to the relevant description in step 401 in FIG. 4A , which will not be described in detail here.

[0236] In an embodiment of the present application, the first indication information includes at least one of the ACR type corresponding to the application, indication information that the ACR corresponding to the application is a service continuity planning ACR or a common ACR, indication information of the instantiation state of the first EAS, and the first time information, and is used to determine the name of the information of the first EES or the first EAS. The present application does not limit the name of the information. The first indication information can be carried in different messages. For example, the first indication information in step 401 can be carried in a retrieval T-EES request message, and the first indication information in step 501 can be carried in the first message. The present application does not limit the message that carries the first indication information.

[0237] 502. The first EES sends a second message to the second EES or EEC. Correspondingly, the second EES or EEC receives the second message. The second message includes information of at least one EAS, and the at least one EAS includes the first EAS.

[0238] Optionally, the at least one EAS is an EAS that matches the application and satisfies an EAS discovery filter.

[0239] Exemplarily, the at least one EAS includes a first EAS, that is, the information of the at least one EAS includes information of the first EAS. The information of the at least one EAS includes at least one of instantiation status information, identification information, and address information of each EAS. That is, the information of the first EAS includes at least one of first EAS instantiation status information, first EAS identification information, and first EAS address information.

[0240] Exemplarily, when the first message comes from the second EES, the first EES sends the second message to the second EES. When the first message comes from the EEC, the first EES sends the second message to the EEC.

[0241] Exemplarily, the second message may include an EAS discovery response message, and the second message includes information of at least one EAS, where the at least one EAS is an EAS that satisfies an EAS discovery filter.

[0242] 503 : The second EES or EEC determines a first EAS from at least one EAS based on the first indication information.

[0243] For example, after determining the first EAS, the second EES or EEC may send the information of the first EAS to the first EES. If the first EAS is an instantiable but uninstantiated EAS, the first EES triggers an EAS instantiation process for the first EAS to the OAM system.

[0244] As an example, the information of the at least one EAS includes the instantiation status information of each EAS. The second EES or EEC determines the first EAS from the at least one EAS based on the type of the ACR corresponding to the application, the instantiation status information of the first EAS, and at least one of the EAS information. Exemplarily, the second EES or EEC can obtain the instantiation status information of the first EAS from the source EAS of the ACR corresponding to the application, or the second EES or EEC can determine the instantiation status information of the first EAS based on the type of the ACR corresponding to the application. For example, in the case where the ACR type is a service continuity planning ACR, the second EES or EEC determines that the target EAS of the ACR corresponding to the application is an instantiated but not instantiated EAS, that is, the instantiation status of the first EAS is an instantiated but not instantiated state. In the case where the ACR type is a normal ACR, the second EES or EEC determines that the target EAS of the ACR corresponding to the application is an instantiated EAS, that is, the instantiation status of the first EAS is an instantiated but not instantiated state.

[0245] The second EES or EEC may select an EAS from the at least one EAS that matches the instantiation state of the first EAS as the first EAS. For example, if the instantiation state of the first EAS is Instantiated, the second EES selects an Instantiated EAS from the at least one EAS. For another example, if the instantiation state of the first EAS is Instantiated but Not Instantiated, the second EES or EEC selects an Instantiated but Not Instantiated EAS from the at least one EAS.

[0246] As another example, the information of the at least one EAS includes the time required for instantiation of each EAS that can be instantiated but has not been instantiated, and the information of the first EAS includes second time information, and the second time information is used to indicate the time when the first EAS is instantiated. The second EES or EEC determines the first EAS from the at least one EAS based on the first time information and the second time information. Exemplarily, the second EES or EEC can obtain the first time information from the source EAS to which the corresponding ACR is applied. The second EES or EEC can determine the first EAS based on a comparison result of the time when the service continuity planning ACR is executed and the time when the first EAS is instantiated.

[0247] For example, the second EES or EEC may compare the execution time of the service continuity planning ACR with the time required to instantiate an EAS that can be instantiated but has not been instantiated in the at least one EAS. In the case that there is an EAS in the at least one EAS whose instantiation time is less than the execution time of the service continuity planning ACR, the second EES selects an EAS that can be instantiated but has not been instantiated from the at least one EAS as the first EAS, and the time required to instantiate the first EAS is less than or equal to the execution time of the service continuity planning ACR. In the case that the time required to instantiate any EAS in the at least one EAS is greater than the execution time of the service continuity planning ACR, the second EES or EEC selects an EAS that has been instantiated from the at least one EAS as the first EAS.

[0248] In an embodiment of the present application, after the first EES receives the first message, it sends information of at least one EAS to the second EES or EEC through a second message, so that the second EES or EEC can determine the target EAS (i.e., the first EAS) of the ACR corresponding to the application from the at least one EAS based on the information of the at least one EAS. The second EES or EEC can find the required target EAS based on at least one of the ACR type, the first time information, and the EAS instantiation status information. For example, the second EES or EEC determines whether to select an EAS that can be instantiated but not instantiated based on at least one of the ACR type, the first time information, and the EAS instantiation status information. For example, when the ACR corresponding to the application is a normal ACR, or the ACR corresponding to the application is a service continuity planning ACR and the execution time of the service continuity planning ACR is greater than the time of EAS instantiation, selecting the instantiated EAS can reduce the time of business interruption. When the ACR corresponding to the application is a service continuity planning ACR, or the execution time of the service continuity planning ACR is greater than the time of EAS instantiation, select an EAS that can be instantiated but not instantiated. In this case, when the instantiated EAS cannot provide better KPIs, the EES can trigger the OAM system to trigger EAS instantiation, thereby providing the UE with an EAS with better KPIs, thereby providing the UE with better ACR services and edge computing services.

[0249] Please refer to Figure 5B, which is an interactive diagram of another communication method provided by an embodiment of the present application. As shown in Figure 5B, the EES, EAS, ECS, etc. involved in this method can refer to the relevant description above and will not be described in detail here. It is understandable that although the method shown below does not involve a relay node, those skilled in the art will know that when the sender and receiver communicate, the forwarding operation can be performed through the relay node. As shown in Figure 5B, the method includes but is not limited to the following steps:

[0250] 504. The second EES or EEC sends a first message to the first EES. Accordingly, the first EES receives the first message. The first message is used to obtain information about the first EAS or report information about the first EAS. The first message includes first indication information. The first EAS is the target EAS of the ACR corresponding to the application. The first indication information is used to determine the first EAS.

[0251] 505 , the first EES determines the first EES based on the first indication information.

[0252] Exemplarily, the first EES may determine the first EAS from the at least one EAS associated with the first EES according to the first indication information, the instantiation status of the at least one EAS, and the time information required for instantiation of the at least one EAS.

[0253] As an example, when the ACR type corresponding to the application includes a common ACR type, or the first indication information includes indication information that the ACR corresponding to the application is a common ACR, or the instantiation state of the first EAS includes an instantiated state, the first EAS includes an instantiated EAS.

[0254] As another example, when the ACR type corresponding to the application includes a service continuity planning ACR type or the first indication information includes indication information that the ACR corresponding to the application is a service continuity planning ACR or the instantiation state of the first EAS includes an instantiable but uninstantiated state, the first EAS includes an instantiable but uninstantiated EAS.

[0255] As another example, when the time when the service continuity planning ACR is executed is less than the time when the first EAS is instantiated, the instantiation state of the first EAS includes an instantiated state.

[0256] As another example, when the time when the service continuity planning ACR is executed is greater than or equal to the time when the first EAS is instantiated, the instantiation state of the first EAS includes an instantiable but uninstantiated state.

[0257] It is understandable that when the execution time of the service continuity plan ACR is equal to the instantiation time of the first EAS, the first EES can select an EAS that can be instantiated but not instantiated as the first EAS, or select an EAS that has been instantiated as the first EAS.

[0258] It is understandable that the specific implementation of the first EES determining the first EAS based on the first indication information can refer to the specific implementation of the first EES or EEC determining the first EAS in step 503, which will not be described in detail here.

[0259] In a possible implementation, when the first EAS is an EAS that can be instantiated but has not been instantiated, the first EAS may further trigger an instantiation process for the first EAS to the network management system.

[0260] 506 , the first EES sends a second message to the second EES or EEC. Correspondingly, the second EES or EEC receives the second message, where the second message includes information of the first EAS.

[0261] In an embodiment of the present application, after the first EES receives the first message, it determines the first EAS based on the first indication information, and sends the information of the first EAS to the second EES or EEC through the second message. The first EES can discover the required target EAS based on at least one of the ACR type, the first time information, and the EAS instantiation status information. For example, the first EES determines whether to select an EAS that can be instantiated but not instantiated based on at least one of the ACR type, the first time information, and the EAS instantiation status information. For example, when the ACR corresponding to the application is an ordinary ACR, or the ACR corresponding to the application is a service continuity planning ACR and the execution time of the service continuity planning ACR is greater than the instantiation time of the EAS, selecting the instantiated EAS can reduce the time of business interruption. When the ACR corresponding to the application is a service continuity planning ACR, or the execution time of the service continuity planning ACR is greater than the instantiation time of the EAS, select an EAS that can be instantiated but not instantiated. In this case, when the instantiated EAS cannot provide better KPIs, the EES can trigger the OAM system to trigger EAS instantiation, thereby providing the UE with an EAS with better KPIs, thereby providing the UE with better ACR services and edge computing services.

[0262] It is understandable that the various methods provided in the embodiments of the present application can be combined with each other. The order of combination can be determined based on the specific implementation, and the embodiments of the present application will not be listed one by one. For example, Figure 4A can be combined with the method shown in Figure 5A or Figure 5B, and Figure 4B can be combined with the method shown in Figure 5A or Figure 5B. That is, the second EES or EEC or ECS determines the first EES based on the first indication information. The second EES or EEC sends a first message to the first EES to request information about the first EAS or report information about the first EAS, and the first EES returns information about at least one EAS or information about the first EAS through the second message.

[0263] Please refer to Figure 6, which is an interactive diagram of another communication method provided in an embodiment of the present application. As shown in Figure 6, this method can be applied to the communication system shown in Figure 1, or the method can be applied to a source EAS or AC, a source EES or EEC, an ECS, a target EES, or a target EAS. Exemplarily, the source EES can be the second EES shown above, the target EES can be the first EES shown above, and the target EAS can be the first EAS shown above.

[0264] It is understood that although the method shown below does not involve relay nodes, those skilled in the art will know that when the sender and receiver communicate, the forwarding operation can be performed through the relay node. As shown in Figure 6, the method includes but is not limited to the following steps:

[0265] In some implementations, the method shown in FIG6 may include step 601 and step 602 .

[0266] 601. The target EAS sends a first registration request message. Correspondingly, the target EES receives the first registration request message, where the first registration request message includes EAS information.

[0267] Exemplarily, after receiving the first registration request message, the target EES may also send a corresponding response message to the target EES.

[0268] 602. The target EES sends a second registration request message to the ECS. The ECS receives the second registration request message. The second registration request message carries EAS instantiation information, i.e., instantiation status information corresponding to the EASID, including at least one of instantiated but not instantiated and instantiated. Alternatively, the EAS instantiation information may include instantiated but not instantiated yet EAS information and its corresponding EASID, or instantiated EAS and its corresponding EASID.

[0269] Exemplarily, after receiving the second registration request message, the ECS may also send a corresponding response message to the target EES.

[0270] Optionally, the ECS may also obtain EAS information (including EAS instantiation information) in a pre-configured manner.

[0271] Exemplarily, the target EES maintains an EAS list that can be instantiated but not instantiated or has been instantiated. The EAS list can be stored in the target EES, for example, the EAS list can be stored in a target EES profile.

[0272] As an example, the EAS list may be as shown in Table 1. The EES profile includes information about each EAS, which may be identified by an EAS ID. The information about each EAS includes the instantiation status of the corresponding EAS. The instantiation status of an EAS may be instantiated or instantiable but not instantiated.

[0273] Table 1

[0274] As another example, the EAS list may be as shown in Table 2. The EES profile may include information about instantiated EASs and information about EASs that can be instantiated but not yet instantiated. The information about instantiated EASs includes identifiers of instantiated EASs. The information about EASs that can be instantiated but not yet instantiated includes identifiers of EASs that can be instantiated but not yet instantiated.

[0275] Table 2

[0276] It is understandable that the target EES may obtain the EAS list through a network management system or through pre-configuration. This application does not limit the method in which the target EES obtains the EAS list.

[0277] Optionally, the method shown in FIG6 may include step 603 .

[0278] 603. The source EAS sends a fourth message, and correspondingly, the source EES receives the fourth message. The fourth message includes the EAS discovery filter, UEID, ACR type, or indication information indicating whether the ACR corresponding to the application is a service continuity planning ACR or a common ACR.

[0279] Exemplarily, the fourth message may include an EAS discovery request message.

[0280] The source EAS is the EAS currently providing services for the application, that is, the source EAS of the ACR corresponding to the application, or the source EAS can also be called the EAS to which the application context is to be migrated, or the EAS currently connected to the terminal device.

[0281] It can be understood that a corresponding EAS list is maintained on the source EES, and the EAS list includes information of the source EAS.

[0282] 604. The source EES sends a third message. Correspondingly, the ECS receives the third message, where the third message includes the first indication information.

[0283] It is understandable that the specific description of step 604 can refer to the specific description of step 401 in Figure 4A, which will not be described in detail here.

[0284] 605, the ECS determines the target EES according to the first indication information. That is, the ECS may select the EES corresponding to the instantiable but uninstantiated EAS as the target EES based on the first indication information, or select the EES corresponding to the instantiated EAS as the target EES.

[0285] For example, if the ACR type corresponding to the application is a common ACR, the ECS determines to select the EES corresponding to the instantiated EAS. If the ACR type corresponding to the application is a service continuity planning ACR, the ECS determines to select the EES corresponding to the instantiable but uninstantiated EAS.

[0286] It is understandable that the specific implementation of the ECS determining the target EES can refer to the relevant description in step 402, which will not be detailed here.

[0287] 606, the ECS sends first information, and correspondingly, the source EES receives the first information, wherein the first information includes information of the target EES.

[0288] Exemplarily, the first information may be carried in a T-EES retrieval response message, and the T-EES retrieval response message includes information of a target EES, wherein the information of the target EES includes an EASID of an EAS corresponding to the target EES.

[0289] Optionally, the information of the target EES may further include instantiation status information of the EAS corresponding to the target EES, for example, whether the EAS corresponding to the target EES is an instantiated EAS or whether the EAS corresponding to the target EES is an instantiable but uninstantiated EAS.

[0290] Exemplarily, the target EES information further includes identification information (EES ID) and EES address information (endpoint) of the target EES.

[0291] It is understandable that the specific description of step 606 can refer to the specific description of step 403 in Figure 4A, which will not be described in detail here.

[0292] 607 , the source EES sends a first message, and correspondingly, the target EES receives the first message, where the first message is used to obtain information of the target EES, and the first message includes first indication information.

[0293] Exemplarily, the first message may include an EAS discovery request message, and the EAS discovery request message may further include an EAS discovery filter.

[0294] It is understandable that the specific description of step 607 can refer to the specific description of step 504 in Figure 5B, which will not be described in detail here.

[0295] 608: The target EES determines a target EAS according to the first indication information. In other words, the target EES determines whether to select an EAS that can be instantiated but has not been instantiated as the target EAS according to the first indication information.

[0296] For example, if the ACR type corresponding to the application is a common ACR, the target EES determines to select an instantiated EAS as the target EAS. If the ACR type corresponding to the application is a service continuity planning ACR, the target EES may select an instantiable but uninstantiated EAS and trigger the EAS instantiation process to the OAM system.

[0297] It is understandable that the specific implementation of the target EES determining the target EAS can refer to the specific implementation of step 505 in the method shown in FIG. 5B , which will not be described in detail here.

[0298] 609. The target EES sends a second message, and the source EES receives the second message accordingly. The second message includes information about the target EAS. Optionally, the information about the target EAS may include instantiation state information of the target EAS.

[0299] Exemplarily, the target EAS information may further include an EAS configuration file, which includes an EAS ID and EAS address information (endpoint).

[0300] It is understandable that, in the case that the target EAS is an EAS that can be instantiated but has not been instantiated, the target EES may send the instantiated EAS information to the source EES after the instantiation of the target EAS is completed.

[0301] It is understandable that the specific description of step 604 can refer to the specific description of step 506 in Figure 5B, which will not be described in detail here.

[0302] Optionally, the method shown in FIG6 may further include step 610 .

[0303] 610. The source EES sends a fifth message, and the source EAS receives the fifth message accordingly. The fifth message includes information about the target EAS. Optionally, the information about the target EAS may include instantiation state information of the target EAS.

[0304] Exemplarily, the fifth message may include an EAS discovery response message.

[0305] It can be understood that the parameters involved in the method shown in Figure 6 (such as the first indication information, the first message, the second message, the first information, etc.) can refer to the relevant descriptions in Figure 4A or Figure 4B or Figure 5A or Figure 5B, and will not be repeated here.

[0306] In some possible implementations, in the method shown in FIG6 , the source EAS can be replaced by an AC, and the source EES can be replaced by an EEC. Specifically, the AC can perform the steps or functions performed by the source EAS in the method embodiment shown in FIG6 , and the EEC can perform the steps or functions performed by the source EES in the method embodiment shown in FIG6 . For example, the AC can perform the sending step in step 603 and the receiving step in step 610. The EEC can perform the receiving steps in steps 603, 606, and 609, and the sending steps in steps 605, 607, and 610.

[0307] In an embodiment of the present application, the source EES may send the first indication information to the ECS through a third message, so that the ECS can select a suitable target EES for the terminal device based on the indication information that the ACR type or the ACR corresponding to the application is a service continuity ACR or a normal ACR. In addition, the source EES sends the first indication information to the target EES through the first message, so that the target EES can select a suitable target EAS for the terminal device based on the indication information that the ACR type or the ACR corresponding to the application is a service continuity ACR or a normal ACR. That is, the ECS and the target EES can determine whether to select an instantiated but uninstantiated EAS based on the ACR type. For an ACR of the normal ACR type, an instantiated EAS can be selected, which can reduce the time of service interruption. For an ACR of the service continuity planning ACR type, an instantiated but uninstantiated EAS can be selected. When the instantiated EAS cannot provide a better KPI, a new EAS can be instantiated for the AC, which can provide the UE with an EAS with a better KPI.

[0308] Please refer to Figure 7, which is an interactive diagram of another communication method provided in an embodiment of the present application. As shown in Figure 7, this method can be applied to the communication system shown in Figure 1, or the method can be applied to a source EAS or AC, a source EES or EEC, an ECS, a target EES, or a target EAS. Exemplarily, the source EES can be the second EES shown above, the target EES can be the first EES shown above, and the target EAS can be the first EAS shown above.

[0309] It is understood that although the method shown below does not involve relay nodes, those skilled in the art will know that when the sender and receiver communicate, the forwarding operation can be performed through the relay node. As shown in Figure 7, the method includes but is not limited to the following steps:

[0310] In some implementations, the method shown in FIG. 7 may include step 701 and step 702 .

[0311] 701. The target EAS sends a first registration request message. Correspondingly, the target EES receives the first registration request message, where the first registration request message includes EAS information.

[0312] Exemplarily, after receiving the first registration request message, the target EES may also send a corresponding response message to the target EES.

[0313] 702. The target EES sends a second registration request message to the ECS. Correspondingly, the ECS receives the second registration request message. The second registration request message carries the instantiation information of the EAS corresponding to the target EES.

[0314] Exemplarily, after receiving the second registration request message, the ECS may also send a corresponding response message to the target EES.

[0315] Optionally, the ECS may also obtain EAS information (including EAS instantiation information) in a pre-configured manner.

[0316] Exemplarily, the target EES maintains a list of EASs that can be instantiated but have not been instantiated or have been instantiated.

[0317] Optionally, the method shown in FIG7 may include step 703 .

[0318] 703. The source EAS sends a fourth message, and correspondingly, the source EES receives the fourth message. The fourth message includes the EAS discovery filter, UEID, ACR type, or indication information indicating whether the ACR corresponding to the application is a service continuity planning ACR or a common ACR.

[0319] Exemplarily, the fourth message may include an EAS discovery request message.

[0320] At 704, the source EES determines the instantiation status of the target EAS based on the first indication information. Specifically, the source EES determines whether the target EES for the application's corresponding ACR needs to have an instantiated EAS or has an instantiable but uninstantiated EAS based on the ACR type or the indication that the ACR corresponding to the application is a service continuity planning ACR or a common ACR. Specifically, the source EES determines whether a new EAS needs to be instantiated for the AC as the target EAS and provide subsequent services for the AC.

[0321] For example, when the ACR type is a common ACR, the target EES has an instantiated EAS. When the ACR type is a service continuity planning ACR, the target EE has an instantiable but uninstantiated EAS.

[0322] 705 , the source EES sends a third message, and correspondingly, the ECS receives the third message.

[0323] Exemplarily, the third message may include a T-EES retrieval request message or a service provisioning request message, the third message including an EASID and information indicating the instantiation state of the target EAS. The instantiation state of the target EAS may include instantiable but not instantiated or instantiated.

[0324] 706 , the ECS determines the target EES according to the indication information and the EAS instantiation status information corresponding to the EES, that is, determines whether the target EES has an EAS that can be instantiated but has not been instantiated, or determines whether the target EES has an EAS that has been instantiated.

[0325] If the indication information indicates that the instantiation state of the target EAS is instantiable but not instantiated, the ECS determines that the target EES has an instantiable but not instantiated EAS. If the indication information indicates that the instantiation state of the target EAS is instantiated, the ECS determines that the target EES has an instantiated EAS.

[0326] It is understandable that the specific implementation of the ECS determining the target EES in step 706 can be referred to the specific description of step 402 in FIG. 4A , which will not be described in detail here.

[0327] 707, the ECS sends first information, and correspondingly, the source EES receives the first information, which includes information of the target EES.

[0328] Exemplarily, the first information may be carried in a retrieve T-EES response message or a service provisioning response message.

[0329] It is understandable that the specific description of step 707 can refer to the specific description of step 403 in Figure 4A, which will not be described in detail here.

[0330] 708. The source EES sends a first message, and correspondingly, the target EES receives the first message. The first request message includes the EASID of the target EAS and information indicating the instantiation status of the target EAS.

[0331] It is understandable that the specific description of step 708 can refer to the specific description of step 504 in Figure 5B, which will not be described in detail here.

[0332] 709. The target EES determines the target EAS based on the target EAS instantiation status indication information and the EAS instantiation status information corresponding to the target EES. In other words, the target EES determines whether to select an EAS that can be instantiated but has not yet been instantiated as the target EAS based on the target EAS instantiation status indication information and the EAS instantiation status information corresponding to the target EES.

[0333] For example, when the target EES determines to select an EAS that can be instantiated but has not been instantiated, the target EES may trigger the EAS instantiation to the OAM system.

[0334] It is understandable that the specific implementation method of the target EES determining the target EAS can refer to the relevant description in step 505 of Figure 5B, which will not be detailed here.

[0335] 710. The target EES sends a second message, and the source EES receives the second message accordingly. The second message includes information about the target EAS. Optionally, the information about the target EAS may include instantiation state information of the target EAS.

[0336] It is understandable that, in the case that the target EAS is an EAS that can be instantiated but has not been instantiated, the target EES may send the instantiated EAS information to the source EES after the EAS instantiation is completed.

[0337] It is understandable that for the specific description of step 710, reference can be made to the specific description of step 506 in FIG. 5B, which will not be described in detail here.

[0338] Optionally, the method shown in FIG7 may further include step 711 .

[0339] 711. The source EES sends a fifth message, and the source EAS receives the fifth message accordingly. The fifth message includes information about the target EAS. Optionally, the information about the target EAS may include instantiation state information of the target EAS.

[0340] Exemplarily, the fifth message may include an EAS discovery response message.

[0341] It can be understood that the parameters involved in the method shown in Figure 7 (such as the first indication information, the first message, the second message, the first information, etc.) can refer to the relevant descriptions in Figure 4A or Figure 4B or Figure 5A or Figure 5B, and will not be repeated here.

[0342] In some possible implementations, in the method shown in FIG7 , the source EAS may be replaced by an AC, and the source EES may be replaced by an EEC. That is, the AC may perform the steps or functions performed by the source EAS in the method embodiment shown in FIG7 , and the EEC may perform the steps or functions performed by the source EES in the method embodiment shown in FIG7 .

[0343] In this embodiment of the present application, the source EES or EEC determines whether to select an EAS that can be instantiated but has not yet been instantiated based on the EAS instantiation status information and the ACR type corresponding to the application. When the instantiated EAS cannot provide a good KPI, a new EAS can be instantiated for the AC, which can provide the UE with an EAS with a better KPI without increasing the ACR latency.

[0344] Please refer to Figure 8, which is an interactive diagram of another communication method provided in an embodiment of the present application. As shown in Figure 8, this method can be applied to the communication system shown in Figure 1, or the method can be applied to a source EAS or AC, a source EES or EEC, an ECS, or a target EES. Exemplarily, the source EES can be the second EES shown above, and the target EES can be the first EES shown above.

[0345] It is understood that although the method shown below does not involve relay nodes, those skilled in the art will know that when the sender and receiver communicate, the forwarding operation can be performed through the relay node. As shown in Figure 8, the method includes but is not limited to the following steps:

[0346] In some implementations, the method shown in FIG. 8 may include step 801 and step 802 .

[0347] 801. The target EAS sends a first registration request message. Correspondingly, the target EES receives the first registration request message, where the first registration request message includes EAS information.

[0348] Exemplarily, after receiving the first registration request message, the target EES may also send a corresponding response message to the target EES.

[0349] 802. The target EES sends a second registration request message to the ECS. Correspondingly, the ECS receives the second registration request message. The registration request message carries the instantiation information of the EAS corresponding to the target EES.

[0350] Optionally, the method shown in FIG8 may include step 803 .

[0351] 803. The source EAS sends a fourth message, and correspondingly, the source EES receives the fourth message. The fourth message includes the EAS discovery filter, UEID, ACR type, or indication information indicating whether the ACR corresponding to the application is a service continuity planning ACR or a common ACR.

[0352] Exemplarily, the fourth message may include an EAS discovery request message.

[0353] 804 , the source EES sends a third message, and correspondingly, the ECS receives the third message.

[0354] The third message may include a T-EES retrieval request message. Optionally, the third message includes indication information of the target EAS instantiation state to be obtained.

[0355] 805, the ECS sends first information, and correspondingly, the source EES receives the first information, where the first information includes information of at least one EES, including identification and address information of the at least one EES.

[0356] Exemplarily, the information of the at least one EES further includes instantiation status information of an EAS associated with the at least one EES. The instantiation status information of the EAS includes whether the EAS is in an instantiated state or in an instantiable but uninstantiated state.

[0357] Exemplarily, the first information may be carried in a retrieval T-EES response message.

[0358] It is understandable that for the specific description of step 805, reference can be made to the specific description of step 405 in FIG. 4B, which will not be described in detail here.

[0359] 806. The source EES determines a target EES from at least one EES according to the first indication information.

[0360] Exemplarily, the source EES determines whether to select the EES corresponding to the instantiable but uninstantiated EAS as the target EES based on the indication information that the ACR type or the ACR corresponding to the application is a service continuity planning ACR or a common ACR.

[0361] Exemplarily, the source EES may determine whether an instantiable but uninstantiated EAS is required on the source EES based on the indication information that the ACR type or the ACR corresponding to the application is a service continuity planning ACR or a common ACR and the instantiation status information of at least one EES associated EAS.

[0362] It is understandable that the specific implementation of the source EES determining the target EES can refer to the specific implementation of the ECS determining the first EES in step 402, which will not be repeated here.

[0363] It is understandable that for the specific description of step 806, reference can be made to the specific description of step 406 in FIG. 4B, which will not be described in detail here.

[0364] 807. The source EES sends a first message, and correspondingly, the target EES receives the first message, which includes information such as EASID.

[0365] Exemplarily, the first message may further include indication information of the target EAS instantiation state that needs to be obtained.

[0366] It is understandable that the specific description of step 807 can refer to the specific description of step 501 in Figure 5A, and will not be described in detail here.

[0367] 808. The target EES sends a second message, and the source EES receives the second message accordingly. The second message may include information about at least one EAS associated with the target EES, including instantiation state information of the at least one EAS.

[0368] It is understandable that the specific description of step 808 can refer to the specific description of step 502 in Figure 5A, which will not be described in detail here.

[0369] 809 , the source EES determines a target EAS from the at least one EAS according to the information of the at least one EAS and the ACR type corresponding to the application.

[0370] Exemplarily, the source EES determines whether to select an instantiable but uninstantiated EAS based on the ACR type corresponding to the application or the indication information that the ACR corresponding to the application is a service continuity planning ACR or a common ACR, and determines the target EAS from the at least one EAS based on the instantiation status information of the at least one EAS.

[0371] It is understandable that the specific implementation of the source EES determining the target EAS can refer to the specific implementation of step 503 in FIG. 5A , which will not be described in detail here.

[0372] Optionally, the method described in FIG8 may further include step 811 .

[0373] 810. The source EES sends a fifth message, and the source EAS receives the fifth message accordingly. The fifth message includes information about the target EAS, which may include instantiation state information of the target EAS.

[0374] Exemplarily, the fifth message may include an EAS response message.

[0375] 811. When the source EES determines to select an EAS that is instantiable but not yet instantiated as the target EAS, the source EES sends information about the target EAS to the target EES and instructs the target EES to trigger the target EAS instantiation process. For example, the source EES may trigger the target EAS instantiation through a selected EAS announcement process.

[0376] It can be understood that the parameters involved in the method shown in Figure 8 (such as the first indication information, the first message, the second message, the first information, etc.) can refer to the relevant descriptions in Figure 4A or Figure 4B or Figure 5A or Figure 5B, and will not be repeated here.

[0377] In some possible implementations, in the method shown in FIG8 , the source EAS may be replaced by an AC, and the source EES may be replaced by an EEC. That is, the AC may perform the steps or functions performed by the source EAS in the method embodiment shown in FIG8 , and the EEC may perform the steps or functions performed by the source EES in the method embodiment shown in FIG8 .

[0378] In this embodiment of the present application, the source EES or EEC determines whether to select an EAS that can be instantiated but has not yet been instantiated based on the EAS instantiation status information and the ACR type corresponding to the application. When the instantiated EAS cannot provide a good KPI, a new EAS can be instantiated for the AC, which can provide the UE with an EAS with a better KPI without increasing the ACR latency.

[0379] Please refer to Figure 9, which is an interactive schematic diagram of another communication method provided by an embodiment of the present application. As shown in Figure 9, the method can be applied to the communication system shown in Figure 1, or the method is applied to the source EAS or AC, the source EES or EEC, the ECS, and the target EES. Exemplarily, the source EES can be the second EES shown above, and the target EES can be the first EES shown above. It is understandable that although the method shown below does not involve a relay node, those skilled in the art can know that when the sender and receiver communicate, the forwarding operation can be performed through the relay node. As shown in Figure 9, the method includes but is not limited to the following steps:

[0380] In some implementations, the method shown in FIG. 9 may include step 901 and step 902 .

[0381] 901. The target EAS sends a first registration request message. Correspondingly, the target EES receives the first registration request message, where the first registration request message includes EAS information.

[0382] Exemplarily, after receiving the first registration request message, the target EES may also send a corresponding response message to the target EES.

[0383] 902. The target EES sends a second registration request message to the ECS. Correspondingly, the ECS receives the second registration request message. The registration request message carries the instantiation information of the EAS corresponding to the target EES and the time required for the EAS instantiation.

[0384] Exemplarily, a list of EASs that can be instantiated but have not been instantiated is maintained on the target EES, and the list of EASs that can be instantiated but have not been instantiated includes the time required to instantiate the EASs that can be instantiated but have not been instantiated.

[0385] Optionally, the method shown in FIG9 may include step 903 .

[0386] 903. The source EAS sends a fourth message, and the source EES receives the fourth message accordingly. The fourth message includes the EAS discovery filter, the UEID, the ACID, and the first time information. The first time information is used to indicate the execution time of the service continuity plan ACR, that is, the first time information is used to indicate the expected expiration time, which indicates the time when the terminal device corresponding to the application is expected to arrive at the predicted or expected location or the target EAS service area at the latest.

[0387] Optionally, the fourth message may further include indication information of applying the corresponding ACR as the service continuity planning ACR.

[0388] Exemplarily, the fourth message may include an EAS discovery request message.

[0389] 904. The source EES sends a third message, and the ECS receives the third message accordingly. The third message includes the EAS discovery filter, UEID, ACID, and first time information.

[0390] Optionally, the third message may further include indication information of applying the corresponding ACR as the service continuity planning ACR.

[0391] It is understandable that the specific description of step 904 can refer to the specific description of step 401 in Figure 4A, and will not be described in detail here.

[0392] 905, the ECS determines the target EES based on the first time information and the second time information, that is, the ECS determines whether to select the EES corresponding to the EAS that can be instantiated but not instantiated as the target EES based on the execution time of the service continuity ACR and the time information required for EAS instantiation.

[0393] Exemplarily, the ECS may determine whether to select the EES corresponding to the instantiable but uninstantiated EAS as the target EES based on the indication information of the ACR corresponding to the application as the service continuity planning ACR, the first time information, and the time information required for EAS instantiation.

[0394] When the execution time of the service continuity planning ACR indicated by the first time information is less than the time required for EAS instantiation, instantiating EAS during the ACR process will cause the ACR delay to increase further, and then cause the service interruption delay or the time of poor service performance to increase further. Therefore, in this case, ECS selects the EES corresponding to the instantiated EAS as the target EES.

[0395] When the execution time of the service continuity planning ACR indicated by the first time information is greater than the time required for EAS instantiation, instantiating EAS during the ACR process will not cause an increase in ACR latency. Therefore, in this case, ECS can select the EES corresponding to the EAS that can be instantiated but not instantiated as the target EES.

[0396] It is understandable that when the execution time of the service continuity plan ACR is equal to the time required for EAS instantiation, the ECS can select the EES corresponding to the EAS that can be instantiated but has not been instantiated, or select the EES corresponding to the EAS that has been instantiated.

[0397] It is understandable that the specific description of step 905 can refer to the specific description of step 402 in Figure 4A, and will not be described in detail here.

[0398] 906, the ECS sends a first message, and the source EES receives the first message accordingly. The first message includes information of the target EES, wherein the information of the target EES includes the EASID of the EAS corresponding to the target EES.

[0399] Optionally, the information of the target EES may further include instantiation status information of the EAS corresponding to the target EES, for example, whether the EAS corresponding to the target EES is an instantiated EAS or whether the EAS corresponding to the target EES is an instantiable but uninstantiated EAS.

[0400] Exemplarily, the target EES information also includes identification information (EES ID) and EES address information of the target EES.

[0401] It is understandable that the specific description of step 906 can refer to the specific description of step 403 in Figure 4A, which will not be described in detail here.

[0402] 907, the source EES sends a first message, and correspondingly, the target EES receives the first message, wherein the first message includes the EAS discovery filter and the first time information.

[0403] Optionally, the first message may further include indication information of applying the corresponding ACR as the service continuity planning ACR.

[0404] It is understandable that the specific description of step 907 can refer to the specific description of step 504 in Figure 5B, which will not be described in detail here.

[0405] 908, the target EES determines the target EAS based on the first time information and the second time information. That is, the target EES determines whether to select an EAS that can be instantiated but has not been instantiated as the target EAS based on the first time information and the time when the EAS corresponding to the target EES is instantiated.

[0406] Exemplarily, the target EES may determine whether to select an EAS that is instantiable but not instantiated based on the indication information of the ACR corresponding to the application for service continuity planning ACR, the first time information, and the time when the EAS corresponding to the target EES is instantiated.

[0407] Exemplarily, in a case where the target EES can select an EAS that can be instantiated but has not been instantiated, the target EES triggers the EAS instantiation process to the OAM system.

[0408] It is understandable that the specific implementation of the target EES determining the target EAS can refer to the specific implementation of step 505 in the method shown in FIG5B , which will not be described in detail here.

[0409] 909. The target EES sends a second message, and the source EES receives the second message accordingly. The second message includes information about the target EAS. The target EAS information may include instantiation status information of the target EAS. Exemplarily, the target EAS information may also include an EAS configuration file. The EAS configuration file includes an EAS ID and EAS address information.

[0410] It is understandable that, in the case that the target EAS is an EAS that can be instantiated but has not been instantiated, the target EES may send the instantiated target EAS information to the source EES after the instantiation of the target EAS is completed.

[0411] It is understandable that the specific description of step 909 can refer to the specific description of step 506 in Figure 5B, which will not be described in detail here.

[0412] Optionally, the method shown in FIG9 further includes step 910 .

[0413] 910. The source EES sends a fifth message, and the source EAS receives the fifth message accordingly. The fifth message includes information about the target EAS, which may include instantiation state information of the target EAS.

[0414] Exemplarily, the fifth message may include an EAS discovery response message.

[0415] It can be understood that the specific description of the parameters involved in the method shown in Figure 9 (such as the first indication information, the first time information, the second time information, the first message, the second message, the first information, etc.) can refer to the relevant description in Figure 4A or Figure 4B or Figure 5A or Figure 5B, and will not be repeated here.

[0416] In some possible implementations, in the method shown in FIG9 , the source EAS may be replaced by an AC, and the source EES may be replaced by an EEC. That is, the AC may perform the steps or functions performed by the source EAS in the method embodiment shown in FIG9 , and the EEC may perform the steps or functions performed by the source EES in the method embodiment shown in FIG9 .

[0417] In an embodiment of the present application, the ECS and the target EES can select an instantiated EAS or an instantiated but uninstantiated EAS based on the execution time of the service continuity ACR (expected expiration time) and the delay of EAS instantiation. When the execution time of the service continuity planning ACR is greater than the instantiation time of the EAS, selecting an instantiated EAS can avoid increasing the delay of the ACR and the time of poor service performance. When the execution time of the service continuity planning ACR is less than the instantiation time of the EAS, selecting an instantiated but uninstantiated EAS is, that is, instantiating a new EAS for the AC, thereby being able to provide the AC with an EAS with better KPIs and providing the UE with better ACR services and edge computing services.

[0418] Please refer to Figure 10, which is an interactive diagram of another communication method provided in an embodiment of the present application. As shown in Figure 10, this method can be applied to the communication system shown in Figure 1, or the method can be applied to a source EAS or AC, a source EES or EEC, an ECS, or a target EES. Exemplarily, the source EES can be the second EES shown above, and the target EES can be the first EES shown above.

[0419] It is understood that although the method shown below does not involve relay nodes, those skilled in the art will know that when the sender and receiver communicate, the forwarding operation can be performed through the relay node. As shown in Figure 10, the method includes but is not limited to the following steps:

[0420] In some implementations, the method shown in FIG. 10 may include step 1001 and step 1002 .

[0421] 1001. The target EAS sends a first registration request message. Correspondingly, the target EES receives the first registration request message, where the first registration request message includes EAS information.

[0422] Exemplarily, after receiving the first registration request message, the target EES may also send a corresponding response message to the target EES.

[0423] 1002. The target EES sends a second registration request message to the ECS. Correspondingly, the ECS receives the second registration request message. The second registration request message carries the instantiation information of the EAS corresponding to the target EES and the time required for the EAS instantiation.

[0424] Exemplarily, a list of EASs that can be instantiated but have not been instantiated is maintained on the target EES, and the list of EASs that can be instantiated but have not been instantiated includes the time required to instantiate the EASs that can be instantiated but have not been instantiated.

[0425] Optionally, the method shown in FIG10 may include step 1003 .

[0426] 1003. The source EAS sends a fourth message, and the source EES receives the fourth message accordingly. The fourth message includes an EAS discovery filter, a UEID, an ACID, and first time information. The first time information is used to indicate the execution time of the service continuity plan ACR, that is, the first time information is used to indicate the expected expiration time, which indicates the time when the terminal device corresponding to the application is expected to arrive at the predicted or expected location or the target EAS service area at the latest.

[0427] Optionally, the fourth message may further include indication information of applying the corresponding ACR as the service continuity planning ACR.

[0428] Exemplarily, the fourth message may include an EAS discovery request message.

[0429] 1004 : The source EES sends a third message, and correspondingly, the ECS receives the third message.

[0430] 1005. The ECS sends first information, and the source EES receives the first information. The first information includes second time information and information about at least one EES. The second time information indicates the time required for instantiation of the EAS corresponding to the at least one EES. The information about the at least one EES includes identification information (e.g., EASID) and instantiation status information of the EAS corresponding to the at least one EES.

[0431] It is understandable that for the specific description of step 1005, reference can be made to the specific description of step 405 in FIG. 4B, which will not be described in detail here.

[0432] 1006. The source EES determines a target EES based on the first time information and the second time information. That is, the source EES determines whether to select an EES corresponding to an instantiable but uninstantiated EAS as the target EES based on the first time information and the time information required for instantiation of the EAS corresponding to at least one EES.

[0433] Exemplarily, the source EES may determine whether to select the EES corresponding to the instantiable but uninstantiated EAS as the target EES based on the indication information of the ACR corresponding to the application as the service continuity planning ACR, the first time information, and the time information required for EAS instantiation.

[0434] When the execution time of the service continuity planning ACR indicated by the first time information is less than the time required for EAS instantiation, instantiating EAS during the ACR process will cause the ACR delay to further increase, and thus cause a further increase in the service interruption delay or the time of poor service performance. Therefore, in this case, the source EES selects the EES corresponding to the instantiated EAS as the target EES.

[0435] When the time for executing the service continuity planning ACR indicated by the first time information is greater than the time required for EAS instantiation, instantiating EAS during the ACR process will not cause an increase in ACR latency. Therefore, in this case, the source EES can select the EES corresponding to the EAS that can be instantiated but not instantiated as the target EES.

[0436] It is understandable that when the execution time of the service continuity plan ACR is equal to the time required for EAS instantiation, the source EES can select the EES corresponding to the EAS that can be instantiated but has not been instantiated, or the EES corresponding to the EAS that has been instantiated.

[0437] It is understandable that for the specific description of step 1006, reference can be made to the specific description of step 406 in FIG. 4B, which will not be described in detail here.

[0438] 1007. The source EES sends a first message, and correspondingly, the target EES receives the first message, wherein the first message includes an EAS discovery filter.

[0439] It is understandable that the specific description of step 1007 can refer to the specific description of step 501 in Figure 5A, and will not be described in detail here.

[0440] 1008. The target EES sends a second message, and the source EES receives the second message accordingly. The second message includes information about at least one EAS corresponding to the target EES, including instantiation information of the at least one EAS and time information required for instantiation.

[0441] It is understandable that the specific description of step 1008 can refer to the specific description of step 502 in Figure 5A, which will not be described in detail here.

[0442] 1009. The source EES determines a target EAS based on the first time information and the time information required for instantiation of at least one EAS corresponding to the target EES. That is, the source EES determines whether to select an EAS that can be instantiated but has not yet been instantiated as the target EAS based on the first time information and the time information required for instantiation of at least one EAS corresponding to the target EES.

[0443] Exemplarily, the source EES may determine whether to select an EAS that can be instantiated but not instantiated based on the indication information of the ACR corresponding to the application for service continuity planning ACR, the first time information, and the time when the EAS corresponding to the target EES is instantiated.

[0444] When the execution time of the service continuity planning ACR indicated by the first time information is less than the time required to instantiate each EAS that can be instantiated but has not been instantiated in the at least one EAS, instantiating the EAS during the ACR process will cause the ACR delay to further increase, and thus cause a further increase in the service interruption delay or the time of poor service performance. Therefore, in this case, the source EES selects the instantiated EAS.

[0445] When the time for executing the service continuity planning ACR indicated by the first time information is greater than the time required for instantiation of any EAS in at least one EAS, instantiating the EAS during the ACR process will not cause an increase in the ACR latency. Therefore, in this case, the source EES can select an EAS that can be instantiated but has not been instantiated.

[0446] Exemplarily, after determining the target EAS, the source EES may send information about the target EAS to the target EES. In the case that the target EAS is an EAS that can be instantiated but has not been instantiated, the target EES triggers an EAS instantiation process to the OAM system.

[0447] It is understandable that the specific implementation of the source EES determining the target EAS can refer to the specific implementation of step 503 in FIG. 5A , which will not be described in detail here.

[0448] Optionally, the method shown in FIG10 further includes step 1010 .

[0449] 1010. The source EES sends a fifth message, and the source EAS receives the fifth message. The fifth message includes information about the target EAS, which may include instantiation state information of the target EAS.

[0450] Exemplarily, the fifth message may include an EAS response message.

[0451] It can be understood that the specific description of the parameters involved in the method shown in Figure 10 (such as the first indication information, the first time information, the second time information, the first message, the second message, the first information, etc.) can refer to the relevant description in Figure 4A or Figure 4B or Figure 5A or Figure 5B, and will not be repeated here.

[0452] In some possible implementations, in the method shown in FIG10 , the source EAS may be replaced by an AC, and the source EES may be replaced by an EEC. That is, the AC may perform the steps or functions performed by the source EAS in the method embodiment shown in FIG10 , and the EEC may perform the steps or functions performed by the source EES in the method embodiment shown in FIG10 .

[0453] In an embodiment of the present application, the source EES or EEC selects an instantiated EAS or an instantiated but uninstantiated EAS based on the execution time of the service continuity planning ACR and the instantiation time of the EAS. In the case that the execution time of the service continuity planning ACR is less than the instantiation time of the EAS, selecting the instantiated EAS can avoid increasing the ACR latency and the time of poor service performance. In the case that the execution time of the service continuity planning ACR is greater than the instantiation time of the EAS, selecting an instantiated but uninstantiated EAS is, that is, instantiating a new EAS for the AC, thereby being able to provide the AC with an EAS with better KPIs and providing the UE with better ACR services and edge computing services.

[0454] It should be understood that the parameters involved in the embodiments of the present application (for example, including but not limited to the first indication information, the first information, the first time information, the second time information, etc.) are not limited to a specific embodiment, but are applicable to all embodiments of the present application, and this application will not go into details about this.

[0455] The following describes a communication device according to an embodiment of the present application.

[0456] The present application divides the functional modules of the communication device according to the above-mentioned method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in this application is schematic and is only a logical functional division. There may be other division methods in actual implementation. The communication device of the embodiment of the present application will be described in detail below with reference to Figures 11 to 13.

[0457] Figure 11 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. As shown in Figure 11, the communication device includes a processing unit 1101 and a transceiver unit 1102. The transceiver unit 1102 can implement corresponding communication functions, and the processing unit 1101 is used to process data. For example, the transceiver unit 1102 can also be referred to as a communication interface or a communication unit.

[0458] In some embodiments of the present application, the communication device can be used to execute the actions performed by the ECS in the above method embodiments. In this case, the communication device can be an ECS or a component that can be configured in the ECS (such as a chip or system, etc.), the transceiver unit 1102 is used to execute the ECS transmission and reception related operations in the above method embodiments, and the processing unit 1101 is used to execute the ECS processing related operations in the above method embodiments.

[0459] Exemplarily, the transceiver unit 1102 is configured to receive first indication information; and the processing unit 1101 is configured to determine a first EES based on the first indication information.

[0460] Optionally, the transceiver unit 1102 is further configured to send the first information.

[0461] In other embodiments of the present application, the communication device can be used to execute the actions performed by the second EES in the above method embodiments. In this case, the communication device can be the second EES or a component that can be configured in the second EES, such as a chip or system, etc.), the transceiver unit 1102 is used to execute the transceiver-related operations of the second EES in the above method embodiments, and the processing unit 1101 is used to execute the processing-related operations of the second EES in the above method embodiments.

[0462] Exemplarily, the transceiver unit 1102 is configured to output a first message and input a second message.

[0463] Optionally, the processing unit 1101 is configured to determine a first EAS.

[0464] Optionally, the transceiver unit 1102 is further configured to output a third message and receive the first message.

[0465] Optionally, the processing unit 1101 is further configured to determine a first EES.

[0466] It is understandable that the specific description of the processing unit 1101 determining the first EAS or the first EES can be referred to the method embodiment shown above, and will not be described in detail here.

[0467] In some other embodiments of the present application, the communication device can be used to execute the actions performed by the EEC in the above method embodiments. In this case, the communication device can be an EEC or a component that can be configured in the EEC, such as a chip or system, etc.), the transceiver unit 1102 is used to execute the transceiver-related operations of the EEC in the above method embodiments, and the processing unit 1101 is used to execute the EEC processing-related operations in the above method embodiments.

[0468] Exemplarily, the transceiver unit 1102 is configured to output a first message and input a second message.

[0469] Optionally, the processing unit 1101 is configured to determine a first EAS.

[0470] Optionally, the transceiver unit 1102 is further configured to output a third message and receive the first message.

[0471] Optionally, the processing unit 1101 is further configured to determine a first EES.

[0472] It is understandable that the specific description of the processing unit 1101 determining the first EAS or the first EES can be referred to the method embodiment shown above, and will not be described in detail here.

[0473] In some other embodiments of the present application, the communication device can be used to execute the actions performed by the first EES in the above method embodiments. In this case, the communication device can be the first EES or a component that can be configured in the first EES (such as a chip or system, etc.), the transceiver unit 1102 is used to execute the transceiver-related operations of the first EES in the above method embodiments, and the processing unit 1101 is used to execute the processing-related operations of the first EES in the above method embodiments.

[0474] Exemplarily, the transceiver unit 1102 is configured to input a first message and output a second message.

[0475] Optionally, the processing unit 1101 is configured to determine a first EAS.

[0476] Optionally, the processing unit 1101 is further configured to trigger an instantiation process of the first EAS.

[0477] Optionally, the above-mentioned communication device may further include a storage unit, which may be used to store instructions and / or data. The processing unit 1101 may read the instructions and / or data in the storage unit so that the communication device implements the above-mentioned method embodiment.

[0478] It can be understood that the specific description of the transceiver unit and the processing unit shown in the embodiment of the present application is only an example. For the specific functions or execution steps of the transceiver unit and the processing unit, please refer to the above-mentioned method embodiment and will not be described in detail here.

[0479] In the above embodiments, the descriptions of the first indication information, the first EES, the first EAS, the first information, the first message, the second message, the third message, etc. can also be referred to the introduction in the above method embodiments, and will not be described in detail here.

[0480] The above describes the communication device according to the embodiment of the present application. The following describes possible product forms of the communication device. It should be understood that any product having the functions of the communication device described in FIG. 11 falls within the scope of protection of the embodiment of the present application. It should also be understood that the following description is merely illustrative and does not limit the product forms of the communication device according to the embodiment of the present application to these examples.

[0481] In one possible implementation, in the communication device shown in Figure 11, the processing unit 1101 can be one or more processors, the transceiver unit 1102 can be a transceiver, or the transceiver unit 1102 can also be a sending unit and a receiving unit, the sending unit can be a transmitter, the receiving unit can be a receiver, and the sending unit and the receiving unit are integrated into a device, such as a transceiver. In the embodiment of the present application, the processor and the transceiver can be coupled, etc., and the embodiment of the present application does not limit the connection method between the processor and the transceiver. During the execution of the above method, the process of sending information in the above method can be understood as the process of the processor outputting the above information. When outputting the above information, the processor outputs the above information to the transceiver so that it can be transmitted by the transceiver. After being output by the processor, the above information may also need to undergo other processing before reaching the transceiver. Similarly, the process of receiving information in the above method can be understood as the process of the processor receiving the input information. When the processor receives the input information, the transceiver receives the above information and inputs it into the processor. Furthermore, after the transceiver receives the above information, the above information may need to be processed further before being received by the processor.

[0482] As shown in FIG. 12 , the communication device 120 includes one or more processors 1220 and a transceiver 1210 .

[0483] In some embodiments of the present application, the communication device may be used to execute the steps or functions performed by the ECS in the above method embodiments.

[0484] The transceiver 1210 is configured to receive first indication information; the processor 1220 is configured to determine a first EES based on the first indication information.

[0485] Optionally, the transceiver 1210 is further configured to send the first information.

[0486] In other embodiments of the present application, the communication device can be used to execute the steps or functions performed by the second EES in the above method embodiments.

[0487] The transceiver 1210 is configured to output a first message and input a second message.

[0488] Optionally, the processor 1220 is configured to determine a first EAS.

[0489] Optionally, the transceiver 1210 is further configured to output a third message and receive the first message.

[0490] Optionally, the processor 1220 is further configured to determine a first EES.

[0491] It will be understood that the specific descriptions of the transceiver and processor shown in the embodiments of the present application are merely examples. For the specific functions or execution steps of the transceiver and processor, reference may be made to the above-mentioned method embodiments, which will not be described in detail here.

[0492] In some other embodiments of the present application, the communication device may be an EEC or a component that may be configured in the EEC, such as the transceiver 1210, which may be used to output the first message and input the second message.

[0493] In some other embodiments of the present application, the communication device may be the first EES or a component that may be configured in the first EES, such as the transceiver 1210 , which may be configured to receive the first message and send the second message.

[0494] In the above embodiments, the descriptions of the first indication information, the first EES, the first EAS, the first information, the first message, the second message, the third message, etc. can also be referred to the introduction in the above method embodiments, and will not be described in detail here.

[0495] In various implementations of the communication device shown in FIG12 , the transceiver may include a receiver and a transmitter, wherein the receiver is configured to perform a receiving function (or operation) and the transmitter is configured to perform a transmitting function (or operation). The transceiver is configured to communicate with other devices / devices via a transmission medium.

[0496] Optionally, the communication device 120 may further include one or more memories 1230 for storing program instructions and / or data, etc. The memory 1230 is coupled to the processor 1220. The coupling in the embodiment of the present application is an indirect coupling or communication connection between devices, units or modules, which can be electrical, mechanical or other forms, and is used for information exchange between devices, units or modules. The processor 1220 may operate in conjunction with the memory 1230. The processor 1220 may execute program instructions stored in the memory 1230. Optionally, at least one of the one or more memories may be included in the processor.

[0497] The specific connection medium between the transceiver 1210, processor 1220, and memory 1230 is not limited in the embodiments of the present application. In Figure 12, the memory 1230, processor 1220, and transceiver 1210 are connected via a bus 1240. The bus is represented by a bold line in Figure 12. The connection methods between other components are merely schematic and are not limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, Figure 12 only uses a single bold line, but this does not mean that there is only one bus or only one type of bus.

[0498] In the embodiments of the present application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc., and may implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of the present application may be directly implemented as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor, etc.

[0499] In the embodiment of the present application, memory may include but is not limited to non-volatile memories such as hard disk drive (HDD) or solid-state drive (SSD), random access memory (RAM), erasable programmable read-only memory (EPROM), read-only memory (ROM) or portable read-only memory (CD-ROM), etc. Memory is any storage medium that can be used to carry or store program code in the form of instructions or data structures, and can be read and / or written by a computer (such as the communication device shown in the present application), but is not limited thereto. The memory in the embodiment of the present application can also be a circuit or other arbitrarily capable of realizing a storage function, for storing program instructions and / or data.

[0500] Exemplarily, the processor 1220 is primarily used to process communication protocols and communication data, control the entire communication device, execute software programs, and process software program data. The memory 1230 is primarily used to store software programs and data. The transceiver 1210 may include a control circuit and an antenna. The control circuit is primarily used to convert baseband signals into radio frequency signals and process radio frequency signals. The antenna is primarily used to transmit and receive radio frequency signals in the form of electromagnetic waves. Input / output devices, such as a touch screen, display, and keyboard, are primarily used to receive user input and output data to the user.

[0501] When the communication device is powered on, the processor 1220 can read the software program in the memory 1230, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor 1220 performs baseband processing on the data to be sent and outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal to the outside in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor 1220. The processor 1220 converts the baseband signal into data and processes the data.

[0502] In another implementation, the RF circuit and antenna may be provided independently of the processor performing baseband processing. For example, in a distributed scenario, the RF circuit and antenna may be remotely arranged independent of the communication device.

[0503] It is understood that the communication device shown in the embodiment of the present application may also have more components than those in Figure 12, and the embodiment of the present application is not limited to this. The method performed by the processor and transceiver shown above is only an example. For the specific steps performed by the processor and transceiver, please refer to the method described above.

[0504] In another possible implementation, in the communication device shown in Figure 11, the processing unit 1101 can be one or more logic circuits, and the transceiver unit 1102 can be an input / output interface, or also called a communication interface, or an interface circuit, or an interface, etc. Alternatively, the transceiver unit 1102 can also be a sending unit and a receiving unit, the sending unit can be an output interface, and the receiving unit can be an input interface, and the sending unit and the receiving unit are integrated into one unit, such as an input / output interface. As shown in Figure 13, the communication device shown in Figure 13 includes a logic circuit 1301 and an interface 1302. That is, the above-mentioned processing unit 1101 can be implemented with a logic circuit 1301, and the transceiver unit 1102 can be implemented with an interface 1302. Among them, the logic circuit 1301 can be a chip, a processing circuit, an integrated circuit or a system on chip (SoC) chip, etc., and the interface 1302 can be a communication interface, an input / output interface, a pin, etc. For example, Figure 13 is illustrated using the above-mentioned communication device as a chip, and the chip includes a logic circuit 1301 and an interface 1302.

[0505] In the embodiment of the present application, the logic circuit and the interface may also be coupled to each other. The embodiment of the present application does not limit the specific connection method between the logic circuit and the interface.

[0506] In some embodiments of the present application, the communication device may be used to execute the steps or functions performed by the ECS in the above method embodiments.

[0507] Illustratively, the interface 1302 is used to input first indication information; the logic circuit 1301 is used to determine the first EES based on the first indication information.

[0508] In other embodiments of the present application, the communication device can be used to execute the steps or functions performed by the second EES in the above method embodiments.

[0509] Illustratively, the interface 1302 is used to output a first message and input a second message.

[0510] In some other embodiments of the present application, the communication device can be used to execute the steps or functions performed by the EEC in the above method embodiments.

[0511] Illustratively, the interface 1302 is used to output a first message and input a second message.

[0512] In some other embodiments of the present application, the communication device can be used to execute the steps or functions performed by the first EES in the above method embodiments.

[0513] Illustratively, the interface 1302 is used to input a first message and output a second message.

[0514] It can be understood that the specific description of the logic circuit and interface shown in the embodiments of the present application is only an example. For the specific functions or execution steps of the logic circuit and interface, please refer to the above-mentioned method embodiment and will not be described in detail here.

[0515] In the above embodiments, the descriptions of the first indication information, the first EES, the first EAS, the first information, the first message, the second message, the third message, etc. can also be referred to the introduction in the above method embodiments, and will not be described in detail here.

[0516] It can be understood that the communication device shown in the embodiment of the present application can implement the method provided in the embodiment of the present application in the form of hardware, or can implement the method provided in the embodiment of the present application in the form of software, etc., and the embodiment of the present application is not limited to this.

[0517] An embodiment of the present application further provides a communication system, which includes at least two of the following: an ECS, a first EES, a second EES, or an EEC. The ECS, the first EES, the second EES, or the EEC can be used to execute the method in any of the aforementioned embodiments.

[0518] In addition, the present application also provides a computer program, which is used to implement the operations and / or processes performed by the ECS in the method provided in the present application.

[0519] The present application also provides a computer program, which is used to implement the operations and / or processing performed by the first EES in the method provided by the present application.

[0520] The present application also provides a computer program, which is used to implement the operations and / or processing performed by the second EES in the method provided by the present application.

[0521] The present application also provides a computer program, which is used to implement the operations and / or processes performed by the EEC in the method provided in the present application.

[0522] The present application also provides a computer-readable storage medium having computer code stored therein. When the computer code is executed on a computer, the computer executes the operations and / or processes performed by the ECS in the method provided in the present application.

[0523] The present application also provides a computer-readable storage medium having computer code stored therein. When the computer code is run on a computer, the computer is enabled to execute the operations and / or processes performed by the first EES in the method provided in the present application.

[0524] The present application also provides a computer-readable storage medium having computer code stored therein. When the computer code is run on a computer, the computer is enabled to execute the operations and / or processing performed by the second EES in the method provided by the present application.

[0525] The present application also provides a computer-readable storage medium having computer codes stored therein. When the computer codes are executed on a computer, the computer executes the operations and / or processes performed by the EEC in the method provided in the present application.

[0526] The present application also provides a computer program product, which includes computer code or computer program. When the computer code or computer program is run on a computer, the operations and / or processes performed by the ECS in the method provided by the present application are executed.

[0527] The present application also provides a computer program product, which includes computer code or computer program. When the computer code or computer program is run on a computer, the operations and / or processing performed by the first EES in the method provided by the present application are executed.

[0528] The present application also provides a computer program product, which includes computer code or computer program. When the computer code or computer program is run on a computer, the operations and / or processing performed by the second EES in the method provided by the present application are executed.

[0529] The present application also provides a computer program product, which includes computer code or computer program. When the computer code or computer program runs on a computer, the operations and / or processes performed by the EEC in the method provided by the present application are executed.

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

[0531] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual needs to achieve the technical effects of the solutions provided in the embodiments of the present application.

[0532] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0533] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a readable storage medium, including a number of instructions for enabling a computer device (which can 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 present application. The aforementioned readable storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

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

Claims

1. A communication method, characterized in that: include: The edge configuration server ECS receives first indication information, where the first indication information is used to determine a first edge enabling server EES corresponding to a first edge application server EAS, where the first EAS is a target EAS for an application context migration ACR corresponding to an application; The ECS determines the first EES based on the first indication information.

2. The method according to claim 1, characterized in that The first indication information includes at least one of the following information: the ACR type corresponding to the application, indication information that the ACR corresponding to the application is a service continuity planning ACR or a common ACR, indication information of the instantiation status of the first EAS, and first time information; wherein the first time information is used to indicate the execution time of the service continuity planning ACR.

3. The method according to claim 1 or 2, characterized in that: The ECS determines a first edge enabling server EES based on the first indication information, including: The ECS determines the first EES based on the first indication information and at least one of the following: an instantiation state of an EAS associated with at least one EES corresponding to the ECS, and second time information; wherein the second time information is used to indicate the instantiation time of the first EAS.

4. The method according to claim 3, characterized in that In the case where the ACR type includes a common ACR type or the first indication information includes indication information that the ACR corresponding to the application is a common ACR or the instantiation state of the first EAS includes an instantiated state, the first EES corresponds to an instantiated EAS; or, When the ACR type includes a service continuity planning ACR type or the first indication information includes indication information that the ACR corresponding to the application is a service continuity planning ACR or the instantiation state of the first EAS includes an instantiable but uninstantiated state, the first EES corresponds to an instantiable but uninstantiated EAS.

5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: The ECS sends first information, which includes at least one of the following: information of at least one EES corresponding to the ECS, instantiation status information of an EAS associated with at least one EES corresponding to the ECS, and information of the first EES; wherein the at least one EES includes the first EES.

6. The method according to any one of claims 1 to 5, characterized in that: The first indication information comes from the second EES or the edge enabled client EEC.

7. A communication method, characterized in that: include: The second edge enabling server EES sends a first message to the first EES, where the first message is used to obtain information about the first edge application server EAS, the first message includes first indication information, the first EAS is a target EAS for application context migration ACR corresponding to the application, and the first indication information is used to determine the first EAS; The second EES receives a second message from the first EES, the second message including information of at least one EAS, the at least one EAS including the first EAS.

8. The method according to claim 7, characterized in that The first indication information includes at least one of the following information: the application context migration ACR type corresponding to the application, indication information that the ACR corresponding to the application is a service continuity planning ACR or a common ACR, indication information of the instantiation status of the first EAS, and first time information; wherein the first time information is used to indicate the execution time of the service continuity planning ACR.

9. The method according to claim 7 or 8, characterized in that: The method further comprises: The second EES determines the first EAS from the at least one EAS based on at least one of the following information: a type of the ACR, instantiation state information of the first EAS, and the at least one EAS information.

10. The method according to claim 7 or 8, characterized in that: The first EAS information includes second time information, where the second time information is used to indicate a time when the first EAS is instantiated. The method further includes: The second EES determines the first EAS from among the at least one EAS based on the first time information and / or the second time information.

11. The method according to any one of claims 7 to 10, characterized in that: The method further comprises: The second EES sends a third message to the edge configuration server ECS, where the third message includes at least one of the following information: the first indication information and application information; The second EES receives first information from the ECS, the first information including at least one of the following information: information of at least one EES, instantiation status information of the EAS corresponding to at least one EES, and time information of the EAS instantiation corresponding to at least one EES; the at least one EES includes the first EES.

12. The method according to claim 11, characterized in that The method further comprises: The second EES determines the first EES from the at least one EES based on at least one of the application information, the first indication information, information of the at least one EES, and instantiation status information of the EAS corresponding to the at least one EES.

13. The method according to any one of claims 7 to 12, characterized in that: The method further comprises: The second EES determines an instantiation state corresponding to the first EAS based on the ACR type corresponding to the application, where the instantiation state of the first EAS includes an instantiated state, or the instantiation state of the first EAS includes an instantiable but uninstantiated state.

14. The method according to claim 13, characterized in that The ACR type includes a common ACR type, and the instantiation state of the first EAS includes an instantiated state; or, The ACR type includes a service continuity planning ACR type, and the instantiation state of the first EAS includes an instantiable but uninstantiated state.

15. The method according to any one of claims 7 to 14, characterized in that: The information of the first EAS includes at least one of the first EAS instantiation state information, the first EAS identification information, and the first EAS address information.

16. A communication method, characterized in that: include: The edge enabling client EEC sends a first message to the first EES, where the first message is used to obtain information about the first edge application server EAS or report information about the first EAS, where the first EAS is the target EAS for the application context migration ACR corresponding to the application, and the first message includes first indication information, where the first indication information is used to determine the first EAS; The EEC receives a second message from the first EES, the second message including information of at least one EAS, the at least one EAS information including the first EAS information.

17. The method according to claim 16, characterized in that The first indication information includes at least one of the following information: the application context migration ACR type corresponding to the application, indication information that the ACR corresponding to the application is a service continuity planning ACR or a common ACR, indication information of the instantiation status of the first EAS, and first time information; wherein the first time information is used to indicate the execution time of the service continuity planning ACR.

18. The method according to claim 16 or 17, characterized in that The method further comprises: The EEC determines the first EAS from the at least one EAS based on at least one of the following information: a type of the ACR, instantiation state information of the first EAS, and the at least one EAS information.

19. The method according to claim 16 or 17, characterized in that The first EAS information includes second time information, where the second time information is used to indicate a time when the first EAS is instantiated. The method further includes: The EEC determines the first EAS from among the at least one EAS based on the first time information and / or the second time information.

20. The method according to any one of claims 16 to 19, characterized in that: The method further comprises: The EEC sends a third message to the edge configuration server ECS, wherein the third message includes at least one of the following information: - instruction information and application information; The EEC receives first information from the ECS, the first information including at least one of the following information: information of at least one EES, instantiation status information of the EAS corresponding to at least one EES, and time information of the EAS instantiation corresponding to at least one EES; the at least one EES includes the first EES.

21. The method according to claim 20, characterized in that The method further comprises: The EEC determines the first EES from the at least one EES based on at least one of the application information, the first indication information, the information of the at least one EES, and the instantiation state information of the EAS corresponding to the at least one EES.

22. The method according to any one of claims 16 to 21, characterized in that: The method further comprises: The EEC determines an instantiation state corresponding to the first EAS based on the ACR type corresponding to the application, where the instantiation state of the first EAS includes an instantiated state, or the instantiation state of the first EAS includes an instantiable but uninstantiated state.

23. The method according to claim 22, characterized in that The ACR type includes a common ACR type, and the instantiation state of the first EAS includes an instantiated state; or, The ACR type includes a service continuity planning ACR type, and the instantiation state of the first EAS includes an instantiable but uninstantiated state.

24. A communication method, characterized in that: include: The first edge enabling server EES receives a first message, where the first message is used to request information of a first edge application server EAS, and the first message includes first indication information, where the first indication information is used to determine the first EAS, where the first EAS is a target EAS for an application context migration ACR corresponding to an application; The first EES sends a second message, where the second message includes information of at least one EAS, and the at least one EAS information includes the first EAS information.

25. The method according to claim 24, characterized in that The first indication information includes at least one of the following information: the application context migration ACR type corresponding to the application, indication information that the ACR corresponding to the application is a service continuity planning ACR or a common ACR, indication information of the instantiation status of the first EAS, and first time information; wherein the first time information is used to indicate the execution time of the service continuity planning ACR.

26. The method according to claim 25, characterized in that The method further comprises: The first EES determines the first EAS based on the first indication information, the instantiation state of the first EAS includes an instantiated state, or the instantiation state of the first EAS includes an instantiable but uninstantiated state.

27. The method according to claim 26, characterized in that In a case where the ACR type includes a common ACR type or the first indication information includes indication information that the ACR corresponding to the application is a common ACR or the instantiation state of the first EAS includes an instantiated state, the first EAS includes an instantiated EAS; or, When the ACR type includes a service continuity planning ACR type or the first indication information includes indication information that the ACR corresponding to the application is a service continuity planning ACR or the instantiation state of the first EAS includes an instantiable but uninstantiated state, the first EAS includes an instantiable but uninstantiated EAS.

28. The method according to claim 26, characterized in that The first indication information includes the first time information, and the first EES determines the first EAS based on the first indication information, including: The first EES determines the first EAS based on the first time information and second time information, where the second time information is used to indicate the time when the first EAS is instantiated, and the instantiation state of the first EAS includes an instantiated state, or the instantiation state of the first EAS includes an instantiable but uninstantiated state.

29. The method according to any one of claims 24 to 28, characterized in that: The first message comes from the second EES or the edge enabled client EEC; the first EES sends the second message, including: The first EES sends the second message to the second EES or the EEC.

30. A communication device, characterized in that: Comprising units for performing the method according to any one of claims 1 to 29.

31. A communication system, characterized in that: The method comprises at least one communication device for executing the method according to any one of claims 1 to 29.

32. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store a computer program, which, when executed on a computer or a processor, enables the computer or the processor to execute the method according to any one of claims 1 to 29.

33. A computer program product, characterized in that The computer program product comprises a computer program, which, when executed on a computer or a processor, causes the computer or the processor to execute the method according to any one of claims 1 to 29.

Citation Information

Patent Citations

  • Communication method and communication device

    CN119012310A

  • Communication method and device

    CN114980223A

  • Service migration method and device

    CN115167991A

  • Communication method and device

    CN116896558A

  • Methods and systems for managing relocation of an edge enabler client context information

    WO2022019724A1