A communication method and communication device for edge computing

Abstract

The application provides a communication method and a communication device for edge computing. The method comprises the following steps: a second edge enabler server (EES) receives a first message sent by a first EES, wherein the first message carries the following information: an identifier of a UE group, first information of a first edge application server (EAS), and the first information comprises one or more of the following: a service area, data center information, and performance information; the first EAS is used by a first UE; and the UE group comprises the first UE and a second UE. Thus, the second UE can be connected to a more optimal EAS to obtain application services, so that the application services are more optimal.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and communication device for edge computing. Background Technology

[0002] The edge data network (EDN) includes an edge application server (EAS) and an edge enabler server (EES). The application client (AC) in the UE can connect to the EAS to obtain application services. Generally, an EAS registers with an EES, or the management system configures the information of an EAS on an EES; this EES is called the EES associated with that EAS, and the EES controls / manages the EAS registered / configured on it.

[0003] The UE needs to discover the EAS before it can establish a connection with the EAS to obtain application services. The EAS discovered by the UE through the existing EAS discovery process may not enable the UE to obtain better application services. Summary of the Invention

[0004] This application provides a communication method and device for edge computing, which helps UEs obtain better application services.

[0005] Firstly, this application provides a communication method for edge computing. This method can be executed by a second EES, by a module applied to the second EES (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the functions of the second EES. The method includes:

[0006] The second edge enabling server (EES) receives a first message sent by the first EES. The first message carries the following information: the identifier of the UE group, and the first information of the first edge application server (EAS). The first information includes one or more of the following: service area, data center information, and performance information. The first EAS is the EAS used by the first UE, and the UE group includes the first UE and the second UE.

[0007] As can be seen, based on the method described in the first aspect, the second EES can receive the service area and / or data center information and / or performance information corresponding to the first EAS used by the first UE sent by the first EES. Thus, the second EES can determine whether a second UE in the same UE group as the first UE is using the first EAS based on the service area and / or data center information and / or performance information corresponding to the first EAS used by the first UE, rather than directly determining the first EAS used by the first UE as the EAS used by the second UE. This is beneficial for the second UE to connect to a better EAS to obtain application services, thereby obtaining superior application services.

[0008] In one possible embodiment, the method further includes: a second EES receiving a second message sent by a second UE, the second message being used to request the discovery of an EAS, the second message carrying information about the second UE, the information about the second UE including location information and / or application information corresponding to the second UE; the second EES determining whether the second UE uses the first EAS based on the information about the second UE and the first information of the first EAS.

[0009] Based on this possible implementation, the second EES can determine whether a second UE in the same UE group as the first UE is using the first EAS based on the service area and / or data center information and / or performance information corresponding to the first EAS used by the first UE, instead of directly determining the first EAS used by the first UE as the EAS used by the second UE. This is beneficial for the second UE to connect to a better EAS to obtain application services and thus receive better application services.

[0010] In one possible embodiment, the specific implementation of the second EES determining whether the second UE uses the first EAS based on the information of the second UE and the first information of the first EAS is as follows: the second EES determines the second EAS based on the information of the second UE; the second EES determines whether the second UE uses the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS.

[0011] Based on this possible implementation, it is advantageous for the second UE to connect to a better EAS to obtain application services, thereby obtaining better application services.

[0012] In one possible embodiment, the second EES determines whether the second UE uses the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS. This includes: the second EES can determine whether the second UE uses the first EAS or the second EAS based on the first information of the second EAS and the first information of the first EAS, as well as the latency information or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES, or the latency information or response time information between the first EAS / first EES and the second EAS / second EES.

[0013] Optionally, the latency or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES can be pre-configured in the second EES and / or pre-configured in the first EES.

[0014] In one possible embodiment, the first message further carries second information of the first EAS, the second information of the first EAS including the identifier of the first EAS and / or the address information of the first EAS. The method further includes: the second EES sending a second response message corresponding to the second message to the second UE; if it is determined that the second UE uses the first EAS, the second response message carries the second information of the first EAS; if it is determined that the second UE uses the second EAS, the second response message carries the second information of the second EAS, the second information of the second EAS including the identifier of the second EAS and / or the address information of the second EAS.

[0015] Based on this possible embodiment, the address information and / or identifier of the EAS used by the second UE can be notified to the second UE so that the second UE can communicate with the EAS it uses.

[0016] In one possible embodiment, the method further includes: if it is determined that the second UE uses the second EAS, then the second EES sends the second information of the first EAS to the second EAS; if it is determined that the second UE uses the second EAS, then the second EES sends the second information of the second EAS to the first EES.

[0017] Based on this possible implementation, if the second UE uses the second EAS, the second EAS and the first EAS can perform application context synchronization to ensure data consistency between different UEs in the same UE group, so that the services of the UEs in the UE group can be carried out normally.

[0018] In one possible embodiment, if it is determined that the second UE uses the second EAS, the second response message also carries the second information of the first EAS; the method further includes: if it is determined that the second UE uses the second EAS, the second EES sends the second information of the second EAS to the first EES.

[0019] Based on this possible implementation, if the second UE uses the second EAS, the second EAS and the first EAS can perform application context synchronization to ensure data consistency among different UEs in the same UE group, thereby enabling the services of the UEs in the UE group to operate normally. Furthermore, by carrying the second information of the first EAS in the second response message, the second information of the first EAS can be sent from the application layer of the second UE to the second EAS.

[0020] In one possible embodiment, if it is determined that the second UE is using the second EAS, the second response message also carries indication information, which indicates that the second EAS needs to synchronize the application context with the first EAS.

[0021] In one possible embodiment, the method further includes: a second EES receiving a second message sent by a second UE, the second message being used to request the discovery of an EAS, the second message carrying information of the second UE, the information of the second UE including location information and / or application information corresponding to the second UE; the second EES determining a second EAS based on the information of the second UE; and the second EES sending a second response message corresponding to the second message to the second UE, the second response message carrying first information of the first EAS and the first information of the second EAS.

[0022] Based on this possible implementation, the second UE can determine whether it is using the first EAS based on the service area and / or data center information and / or performance information corresponding to the first EAS used by the first UE, rather than directly determining the first EAS used by the first UE as the EAS used by the second UE. This is beneficial for the second UE to connect to a better EAS to obtain application services, thereby obtaining better application services.

[0023] In one possible embodiment, the second response message may also carry latency information or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES, or latency information or response time information between the first EAS / first EES and the second EAS / second EES.

[0024] In one possible embodiment, the second response message also carries second information of the first EAS and second information of the second EAS. The second information of the first EAS includes the identifier of the first EAS and / or the address information of the first EAS, and the second information of the second EAS includes the identifier of the second EAS and / or the address information of the second EAS.

[0025] Based on this possible embodiment, the address information and / or identifier of the EAS used by the second UE can be notified to the second UE so that the second UE can communicate with the EAS it uses.

[0026] In one possible embodiment, the method further includes: the second EES receiving second information and / or indication information of the EAS used by the second UE sent by the second UE, the indication information indicating whether the second UE uses the first EAS or indicating whether application context synchronization is required; the EAS used by the second UE is one of the second EAS and the first EAS;

[0027] If the second EES determines, based on the information and / or indication information of the EAS used by the second UE, that context synchronization is required between the first EAS and the second EAS, the second EES sends the second information of the second EAS to the first EES.

[0028] Based on this possible implementation, if the second UE uses the second EAS, the second EAS and the first EAS can perform application context synchronization to ensure data consistency between different UEs in the same UE group, so that the services of the UEs in the UE group can be carried out normally.

[0029] In one possible embodiment, the method further includes: if the second EES determines, based on the information and / or indication information of the EAS selected by the second UE, that context synchronization is required between the first EAS and the second EAS, the second EES sends the second information of the first EAS to the second EAS.

[0030] Based on this possible implementation, if the second UE uses the second EAS, the second EAS and the first EAS can perform application context synchronization to ensure data consistency between different UEs in the same UE group, so that the services of the UEs in the UE group can be carried out normally.

[0031] Secondly, this application provides a communication method for edge computing. This method can be executed by a first EES, by a module applied to the first EES (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the functions of the first EES. The method includes:

[0032] The first edge enabling server (EES) sends a first message to the second EES. The first message carries the following information: the identifier of the UE group, and the first information of the first EAS, which includes one or more of the following: service area, data center information, and performance information; the first EAS is the EAS used by the first UE, and the UE group includes the first UE and the second UE.

[0033] In one possible embodiment, the method further includes: a first EES receiving second information of a second EAS sent by a second EES, the second information of the second EAS including the identifier of the second EAS and / or the address information of the second EAS, the second EAS being an EAS used by a second UE; the first EES sending the second information of the second EAS to the first EAS.

[0034] Thirdly, this application provides a communication method for edge computing. This method can be executed by a second UE, by a module applied to the second UE (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the functions of the second UE. The method includes:

[0035] The second user equipment (UE) sends a second message to the second edge enabling server (EES). This second message is used to request the discovery of an edge controller (EAS). The second message carries information about the second UE, including location information and / or application information corresponding to the second UE. The second UE receives a second response message corresponding to the second message sent by the second EES. This second response message carries first information about a first EAS and first information about a second EAS. The first information includes one or more of the following: service area, corresponding data center information, and performance information. The first EAS is the EAS used by the first UE. The UE group includes the first UE and the second UE. Based on the first information of the first EAS and the first information of the second EAS, the second UE determines whether it uses the first EAS or the second EAS.

[0036] Optionally, the second response message may also carry latency information or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES, or latency information or response time information between the first EAS / first EES and the second EAS / second EES. The second UE determines whether to use the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS, including: the second UE determines whether to use the first EAS or the second EAS based on the latency information or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES, or the latency information or response time information between the first EAS / first EES and the second EAS / second EES, and the first information of the first EAS and the first information of the second EAS.

[0037] Optionally, the latency or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES can be pre-configured in the second EES and / or pre-configured in the first EES.

[0038] In one possible embodiment, the second response message further carries second information of the first EAS and second information of the second EAS. The second information of the first EAS includes the identifier of the first EAS and / or the address information of the first EAS, and the second information of the second EAS includes the identifier of the second EAS and / or the address information of the second EAS. The method further includes: if it is determined that the second UE uses the first EAS, then the second UE communicates with the first EAS based on the second information of the first EAS; if it is determined that the second UE uses the second EAS, then the second UE communicates with the second EAS based on the second information of the second EAS.

[0039] In one possible embodiment, the method further includes: the second UE sending second information and / or indication information of the EAS used by the second UE to the second EES, the indication information indicating whether the second UE uses the first EAS or indicating whether application context synchronization is required.

[0040] In one possible embodiment, the method further includes: if it is determined that the second UE uses the second EAS, then the second UE sends the second information of the first EAS to the second EAS.

[0041] Fourthly, this application provides a communication method for edge computing. This method can be executed by a first EAS, by a module applied to the first EAS (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the functions of the first EAS. The method includes:

[0042] The first edge application server (EAS) receives second information from the second EAS sent by the first edge enabling server (EES). The second information of the second EAS includes the identifier and / or address information of the second EAS. The first EAS is the EAS used by the first UE, and the second EAS is the EAS used by the second UE. The first UE and the second UE are included in a UE group. The first EAS synchronizes the application context corresponding to the UE group with the second EAS based on the second information of the second EAS.

[0043] Fifthly, this application provides a communication method for edge computing. This method can be executed by a second UE, by a module applied to the second UE (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the functions of the second UE. The method includes:

[0044] The second user equipment (UE) sends a second message to the second edge enabling server (EES). This second message is used to request the discovery of an edge controller (EAS). The second message carries information about the second UE, including location information and / or application information corresponding to the second UE. The second UE receives a second response message corresponding to the second message sent by the second EES. This second response message carries second information about the second EAS and second information about the first EAS. The second EAS is the EAS used by the second UE, and the first EAS is the EAS used by the first UE. The first UE and the second UE are included in a UE group. The second information about the first EAS includes the identifier of the first EAS and / or the address information of the first EAS. The second UE sends the second information about the first EAS to the second EAS.

[0045] In one possible embodiment, the second response message also carries indication information that the second EAS needs to synchronize its application context with the first EAS.

[0046] Sixthly, this application provides a communication method for edge computing. This method can be executed by a second EAS, by a module applied to the second EAS (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the functions of the second EAS. The method includes:

[0047] The second edge application server (EAS) receives information from the second edge enable server (EES) or the second user equipment (UE) sent by the first EAS. The information of the first EAS includes the identifier and / or address information of the first EAS. The first EAS is the EAS used by the first UE, and the second EAS is the EAS used by the second UE. The first UE and the second UE are included in a UE group. The second EAS synchronizes the application context corresponding to the UE group with the first EAS based on the second information of the first EAS.

[0048] The beneficial effects of aspects two through six can be found in the beneficial effects of aspect one, and will not be repeated here.

[0049] Seventhly, this application provides a communication method for edge computing. This method can be executed by a first EES (Edge Execution System), by a module applied to the first EES (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the functions of the first EES. The method includes:

[0050] The first edge enabling server (EES) sends a first message to the second EES, the first message carrying second information of the first edge application server (EAS), the second information including identification and / or address information, the first EAS being the EAS used by the first UE; the first EES receives the second message sent by the second EES, the second message carrying the identification of the second UE and the first information of the second EAS, the first information including one or more of the following: service area, data center information, performance information; the first EES determines whether the second UE uses the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS, the first UE and the second UE being included in the same UE group.

[0051] As can be seen, based on the method described in aspect seven, the first EES can determine whether a second UE in the same UE group as the first UE uses the first EAS based on the service area and / or data center information and / or performance information corresponding to the first EAS used by the first UE, and the service area and / or data center information and / or performance information corresponding to the second EAS used by the second UE, rather than directly determining the first EAS used by the first UE as the EAS used by the second UE. This is beneficial for the second UE to connect to a better EAS to obtain application services, thereby obtaining better application services.

[0052] In one possible embodiment, the second message also carries information about the second UE, which includes location information and / or application information corresponding to the second UE; the first EES determines whether the second UE uses the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS, including: the first EES determines whether the second UE uses the first EAS or the second EAS based on the information of the second UE, the first information of the first EAS and the first information of the second EAS.

[0053] Based on this possible implementation, it is advantageous for the second UE to connect to a better EAS to obtain application services, thereby obtaining better application services.

[0054] In one possible embodiment, the first EES determines whether the second UE uses the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS, including: the first EES determines whether to use the first EAS or the second EAS based on the latency information or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES, or the latency information or response time information between the first EAS / first EES and the second EAS / second EES, as well as the first information of the first EAS and the first information of the second EAS.

[0055] Optionally, the latency or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES can be pre-configured in the first EES.

[0056] Optionally, the second message may also carry latency or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES, or latency or response time information between the first EAS / first EES and the second EAS / second EES. Optionally, the latency or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES may be pre-configured in the second EES. Optionally, the latency or response time information between the first EAS / first EES and the second EAS / second EES may be pre-configured in the second EES.

[0057] In one possible embodiment, the second message also carries second information of the second EAS; the method further includes: the first EES sending a second response message corresponding to the second message to the second EES; the second response message carries the identifier of the second UE and the second information of the EAS used by the second UE.

[0058] Based on this possible embodiment, the address information and / or identifier of the EAS used by the second UE can be notified to the second UE so that the second UE can communicate with the EAS it uses.

[0059] In one possible embodiment, the method further includes: if it is determined that the second UE uses the second EAS, then the first EES sends second information of the second EAS to the first EAS.

[0060] Based on this possible implementation, if the second UE uses the second EAS, the second EAS and the first EAS can perform application context synchronization to ensure data consistency between different UEs in the same UE group, so that the services of the UEs in the UE group can be carried out normally.

[0061] In one possible embodiment, if it is determined that the second UE uses the second EAS, the second response message also carries indication information indicating that the second EAS needs to synchronize its application context with the public EAS.

[0062] Eighthly, this application provides a communication method for edge computing. This method can be executed by a second EES, by a module applied to the second EES (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the functions of the second EES. The method includes:

[0063] The second edge enabling server (EES) receives a first message from the first EES. The first message carries second information of the first edge application server (EAS), including identification and / or address information. The first EAS is the EAS used by the first UE. The second EES receives a third message from the second UE. The third message is used to request the discovery of an EAS. The second message carries information of the second UE, including location information and / or application information corresponding to the second UE. The first UE and the second UE are included in the same UE group. The second EES determines the second EAS based on the information of the second UE. The second EES sends a second message to the first EES. The second message carries the identification of the second UE and the first information of the second EAS. The first information includes one or more of the following: service area, data center information, and performance information.

[0064] In one possible embodiment, the second message also carries information about the second UE, which includes location information and / or application information corresponding to the second UE.

[0065] In one possible embodiment, the second message may also carry latency information or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES, or latency information or response time information between the first EAS / first EES and the second EAS / second EES.

[0066] Optionally, the latency or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES can be pre-configured in the second EES.

[0067] In one possible embodiment, the second message also carries second information of the second EAS; the method further includes:

[0068] The second EES receives a second response message corresponding to the second message sent by the first EES. The second response message carries the identifier of the second UE and the second information of the EAS used by the second UE. The EAS used by the second UE is either the second EAS or the first EAS. The second EES sends a fourth message to the second UE. The fourth message carries the second information of the EAS used by the second UE.

[0069] In one possible embodiment, the EAS used by the second UE is the second EAS, and the method further includes: the second UE sending second information of the first EAS to the second EAS.

[0070] In one possible embodiment, the EAS used by the second UE is the second EAS, and the fourth message also carries the second information of the first EAS.

[0071] In one possible embodiment, the fourth message also carries an indication that the second EAS needs to synchronize its application context with the first EAS.

[0072] In one possible embodiment, the second response message also carries indication information that the second EAS needs to synchronize its application context with the first EAS.

[0073] Ninthly, this application provides a communication method for edge computing. This method can be executed by a second UE, by a module applied to the second UE (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the functions of the second UE. The method includes:

[0074] The second UE sends a third message to the second EES, which is used to request the discovery of an EAS. The second message carries information about the second UE, including location information and / or application information corresponding to the second UE. The second UE receives a fourth message sent by the second EES, which carries second information about the EAS used by the second UE and second information about the first EAS. The second information includes identification and / or address information. The EAS used by the second UE is the second EAS. The first EAS is the EAS used by the first UE. The first UE and the second UE are included in the same UE group. The second UE sends the second information of the first EAS to the second EAS.

[0075] In one possible embodiment, the fourth message also carries an instruction that indicates that the second EAS needs to synchronize its application context with the first EAS.

[0076] The beneficial effects of aspects eight and nine can be found in aspect seven, and will not be repeated here.

[0077] In a tenth aspect, this application provides a communication device, which may be a first EES or a module applied to the first EES, such as a processor, chip, or chip system, or may be a logic node, logic module, or software capable of implementing all or part of the functions of the first EES.

[0078] For example, the communication device can be a second EES or a module applied to the second EES, such as a processor, chip, or chip system, or it can be a logic node, logic module, or software that can implement all or part of the functions of the second EES.

[0079] For example, the communication device can be a second UE or a module applied to the second UE, such as a processor, chip, or chip system, or it can be a logical node, logical module, or software that can realize all or part of the functions of the second UE.

[0080] For example, the communication device can be the first EAS or a module applied to the first EAS, such as a processor, chip, or chip system, or it can be a logical node, logical module, or software that can implement all or part of the functions of the first EAS.

[0081] For example, the communication device can be a second EAS or a module applied to the second EAS, such as a processor, chip, or chip system, or it can be a logic node, logic module, or software that can implement all or part of the functions of the second EAS.

[0082] The communication device includes modules / units for performing any of the methods in the first to ninth aspects and their possible implementations.

[0083] In one aspect, this application provides a communication device including a processor coupled to a memory for storing programs or instructions, which, when executed by the processor, cause the device to perform the method described in any one of the first to ninth aspects above.

[0084] In a twelfth aspect, this application provides a chip including a processor and an interface, the processor and the interface being coupled; the interface is used to receive or output signals, and the processor is used to execute code instructions, causing the chip to perform the method described in any one of the first to ninth aspects above.

[0085] In a thirteenth aspect, this application provides a computer-readable storage medium storing computer-executable instructions, which, when invoked, cause any one of the first to ninth aspects described above to be executed.

[0086] In a fourteenth aspect, this application provides a computer program product comprising: computer program code, which, when run, causes any one of the first to ninth aspects described above to be executed.

[0087] In a fifteenth aspect, this application provides a communication system comprising a second EES for performing the method described in the first aspect, a first EES for performing the method described in the second aspect, a first EAS for performing the method described in the fourth aspect, and a second EAS for performing the method described in the sixth aspect.

[0088] Alternatively, the communication system may include a second EES for performing the method described in the first aspect above, a first EES for performing the method described in the second aspect above, a first EAS for performing the method described in the fourth aspect above, a second UE for performing the method described in the fifth aspect above, and a second EAS for performing the method described in the sixth aspect above.

[0089] Alternatively, the communication system may include a first EES for performing the method described in the first aspect above, a first EES for performing the method described in the eighth aspect above, a second UE for performing the method described in the third aspect above, a first EAS for performing the method described in the fourth aspect above, and a second EAS for performing the method described in the sixth aspect above.

[0090] Alternatively, the communication system may include a first EES for performing the method described in the seventh aspect above, a second EES for performing the method described in the eighth aspect above, a first EAS for performing the method described in the fourth aspect above, and a second EAS for performing the method described in the sixth aspect above.

[0091] Alternatively, the communication system may include a first EES for performing the method described in the seventh aspect above, a second EES for performing the method described in the eighth aspect above, a first EAS for performing the method described in the fourth aspect above, a second EAS for performing the method described in the sixth aspect above, and a second UE for performing the method described in the ninth aspect above. Attached Figure Description

[0092] Figure 1 A schematic diagram of a system architecture provided for this application;

[0093] Figure 2 A schematic diagram of a UE group connecting to an EAS provided in this application;

[0094] Figure 3 A schematic diagram illustrating another UE group connection to EAS provided in this application;

[0095] Figure 4 A flowchart illustrating a communication method for edge computing provided in this application;

[0096] Figure 5 A flowchart illustrating a communication method for edge computing provided in this application;

[0097] Figure 6 A flowchart illustrating a communication method for edge computing provided in this application;

[0098] Figure 7 A flowchart illustrating a communication method for edge computing provided in this application;

[0099] Figure 8 A flowchart illustrating a communication method for edge computing provided in this application;

[0100] Figure 9 A flowchart illustrating a communication method for edge computing provided in this application;

[0101] Figure 10 A flowchart illustrating a communication method for edge computing provided in this application;

[0102] Figure 11 A flowchart illustrating a communication method for edge computing provided in this application;

[0103] Figure 12 A flowchart illustrating a communication method for edge computing provided in this application;

[0104] Figure 13 A flowchart illustrating a communication method for edge computing provided in this application;

[0105] Figure 14A schematic diagram of the structure of a communication device provided in this application;

[0106] Figure 15 A schematic diagram of another communication device provided in this application. Detailed Implementation

[0107] The specific embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0108] The terms "first" and "second," etc., used in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0109] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0110] In this application, "at least one (item)" means one or more, "more than one" means two or more, "at least two (items)" means two or three or more, and "and / or" is used to describe the relationship between related objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0111] To enable UEs to obtain better application services, embodiments of this application provide a communication method and device for edge computing. To better understand these embodiments, the system architecture involved is first described below:

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

[0113] Please see Figure 1 , Figure 1 This is a schematic diagram of a system architecture provided in an embodiment of this application. For example... Figure 1 As shown, the system architecture includes user equipment (UE), the 3rd Generation Partnership Project core network (3GPPCN), the edge data network (EDN), and the edge configuration server (ECS). The UE includes an application client (AC) and an edge enabler client (EEC). The EDN includes an edge application server (EAS) and an edge enabler server (EES).

[0114] I. User Equipment

[0115] User equipment includes devices that provide voice and / or data connectivity to users. For example, a user equipment is a device with wireless transceiver capabilities that can be deployed on land, including indoors or outdoors, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as on ships); and it can be deployed in the air (such as on airplanes, balloons, and satellites). The user equipment can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, virtual reality (VR) user equipment, augmented reality (AR) user equipment, wireless terminals in industrial control, vehicle-mounted user equipment, wireless terminals in self-driving vehicles, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, wearable user equipment, etc. The embodiments in this application do not limit the application scenarios. A terminal may also be referred to as a terminal device, terminal, access user equipment, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station, remote station, remote user equipment, mobile device, UE user equipment, wireless communication equipment, UE agent, or UE device, etc. User equipment can be fixed or mobile. In this application, UE will be used to refer to user equipment.

[0116] 2. EDN

[0117] One common understanding is that an EDN corresponds to a data network, specifically a local data network (DN) containing edge-enabled functions. It can be identified using a data network access identifier (DNAI) and a data network name (DNN), and is a logical network concept. Another understanding of EDN is that it is a peer-to-peer concept of a central cloud, which can be understood as a local data center (geographical location concept). It can be identified using a DNAI and may contain multiple local data networks (DNs).

[0118] II. EAS

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

[0120] III. AC

[0121] It is the peer entity of EAS on the UE side. AC is used for application users to obtain application services from EAS. AC is a client program applied on the terminal side. AC can connect to EAS in the cloud to obtain application services, or it can connect to EAS deployed and running in one or more EDNs to obtain application services.

[0122] IV. EES

[0123] It can provide enabling capabilities for EAS deployed in EDN, better supporting application deployment in MEC. It can support edge application registration, UE authentication and authorization, and provide UEs with EAS IP address information. It can also further support obtaining EAS identifier and IP address information and sending this information to ECS. EES is deployed in EDN. Generally, an EAS registers with an EES, or an EAS's information is configured on an EES through the management system. This EES is called the EES associated with the EAS, and the EES controls / manages the EAS registered / configured on it.

[0124] V. EEC

[0125] It is the peer entity of EES on the UE side. EEC is used to register EEC information and AC information with EES, perform security authentication and authorization, obtain EAS IP address from EES, and provide edge computing enabling capabilities to AC, such as the EAS discovery service returning the EAS IP address to AC.

[0126] VI. ECS

[0127] It is responsible for EDN configuration, such as providing EES information to the UE. It can also directly provide EAS information to the UE, and obtain EAS information through DNS interaction with applications. Furthermore, it obtains and stores EAS and IP address information from other functional entities.

[0128] To facilitate understanding of the solutions provided in the embodiments of this application, some technical terms involved in this application will be introduced below:

[0129] I. EAS Discovery Service

[0130] In this process, application users sign service agreements with application providers to obtain services from them. Application users log into the Application Controller (AC) on their terminals and communicate with the Edge Controller (EAS) via the AC's connection. The Edge Controller (EEC) is a middleware layer, typically located within the operating system or between the AC and the operating system. The AC can obtain edge enabling services from the EEC via an Application Programming Interface (API). For example, edge enabling services may include EAS discovery services.

[0131] The 3GPP SA6 standard defines the discovery process for EES platforms and EASs, providing a mechanism for both. The architecture and functionality employ a two-tier discovery mechanism: first, the EES platform is discovered, and then EASs are discovered from the EES platform. For example, the EEC can send a request to the EES to discover EASs. Upon receiving the request, the EES matches the EAS that meets the user's request based on locally registered / online EAS information and user-provided discovery filtering parameters. The EES then returns the EAS information to the EEC. The EEC can then provide this information to the AC (Access Controller), allowing the AC to connect to the EAS.

[0132] II. A UE group connecting to EAS

[0133] A UE group is a group of UEs that use the same application. For example, multiple users playing a game together can form a UE group.

[0134] There are two scenarios where a UE group connects to EAS:

[0135] Scenario 1: A group of UEs can connect to the same EAS to reduce signaling interactions between EASs. For example, ... Figure 2As shown, EAS1 to EAS3 are different application instances of the same application. UE1 to UE3 are UEs in the same UE group. UE1 to UE3 are all connected to EAS2. This avoids synchronizing the application context of this UE group between different EASs, thereby reducing the overhead of EAS context synchronization. Furthermore, since a UE is connected to the same EAS, fairness among the group of UEs can be guaranteed.

[0136] Scenario 2: A group of UEs can connect to different EASs. Each UE can connect to the EAS that is closer to it to obtain better service performance. For example, if the EAS is a specific location, then the EASs need to synchronize application contexts to ensure that the services of the UEs in the group can operate normally. Figure 3 As shown, EAS1 to EAS3 are different application instances of the same application. EAS1-EAS3 share the same EASID / EAS domain name, but are different EAS instances. That is, the EAS server address, EAS IP address, and other address information corresponding to EAS1-EAS3 are different. The same application can be understood as a one-to-one correspondence between EASID and ACID, and the application services provided by that EAS and AC are the same. Considering different operating systems, the application ID in the EASID and ACID corresponds to the same application. EAS1 to EAS3 reside in different EDNs. UE1 to UE3 are UEs in the same UE group. UE1 connects to EAS1. UE2 connects to EAS2. UE3 connects to EAS3. Since different UEs in the same UE group connect to different EASs, to ensure data consistency, EAS1 to EAS3 can perform application context synchronization between each other. Alternatively, EAS1 to EAS3 can also reside in the same EDN. Figure 3 Taking EAS1 to EAS3 as examples, which are located in different EDNs.

[0137] The communication method and device for edge computing will be further described below with reference to the accompanying drawings. It is understood that this application uses a first UE, a first EES, a first EAS, a second UE, a second EES, and a second EAS as examples of the execution entities in the interaction illustration, but this application does not limit the execution entities in the interaction illustration. For example, the first UE in the method provided by this application can also be a chip, chip system, or processor applied to the first UE, or it can be a logical node, logical module, or software capable of implementing all or part of the first UE; the same applies to the first EES, the first EAS, the second UE, the second EES, and the second EAS.

[0138] Please see Figure 4 , Figure 4 This application provides a flowchart illustrating a communication method for edge computing, wherein:

[0139] 401. The first UE sends second information of the first EAS to the first EES, the second information including address information and / or identifier. The first EAS is the EAS used by the first UE. Alternatively, the first EAS may be an EAS used by multiple UEs in a group of UEs, including the first UE. Accordingly, the first EES can receive the second information of the first EAS.

[0140] The first UE is any UE in the UE group. This UE group includes multiple UEs. All UEs in this UE group use the same application. This application can correspond to multiple EASs. These multiple EASs include the first EAS and other EASs.

[0141] In this embodiment of the application, the second information of the first EAS includes the address information of the first EAS and / or the identifier of the first EAS. For example, the address information of the first EAS includes the IP address of the first EAS and / or endpoint information.

[0142] In one possible embodiment, the second information may be carried in an EAS infoprovisioning request.

[0143] For example, the first UE can first send an EAS discovery request to the first EES. This request is used to request the discovery of an EAS, and it may carry the identifier of the first UE, the identifier of the UE group, and information about the first UE. The information about the first UE may include the location information of the first UE and / or the application information corresponding to the first UE. Optionally, the application information corresponding to the first UE may be an application client profile (AC profile) or an EAS discovery requirement. For example, an AC profile may include one or more information elements in Table 1 below. For example, an EAS discovery requirement may include one or more information elements in Table 2 below. After receiving the EAS discovery request, the first EES determines the EAS that meets the AC requirement corresponding to the first UE based on the information of the first UE. If the first EES determines multiple EAS for the first UE, it sends an EAS discovery response to the first UE. This EAS discovery response carries the addresses and / or identifiers of the multiple EAS. After receiving the EAS discovery response, the first UE selects one EAS from the multiple EAS, and this EAS becomes the first EAS. The first UE sends an EAS information configuration request to the first EES, which carries the address information and / or identifier of the first EAS.

[0144] Table 1

[0145]

[0146] Step 401 can be optional. For example, if the first EES, after receiving the EAS discovery request, determines based on the first UE's information that there is only one EAS that meets the first UE's requirements, then that EAS is the first EAS. The first EES sends an EAS discovery response to the first UE, which carries the address and / or identifier of the first EAS, and then executes step 402. The first UE may choose not to send an EAS information configuration request to the first EES.

[0147] 402. The first EES sends a first message to the second EES, the first message carrying the following information: the identifier of the UE group, and first information of the first EES, the first information including one or more of the following: service area, data center information, and performance information. The UE group includes the first UE and the second UE. Accordingly, the second EES can receive the first message.

[0148] In one possible embodiment, the first message may be a common EAS announcement request, which is not limited in this patent.

[0149] In this embodiment, the first EES is the EES connected to the first UE, and the second EES is the EES connected to the second UE. That is, the first EES is the EES through which the first UE sends an EAS discovery request message or an EAS information configuration request. The second EES is the EES through which the second UE sends an EAS discovery request message or an EAS information configuration request. The first EES can send the first information of the first EAS to the second EES. After receiving the first information of the first EAS, the second EES can determine whether the second UE uses the first EAS based on this information. The second EES's determination of whether the second UE uses the first EAS based on the first information has two specific implementation methods. The first specific implementation method is that the second EES itself determines whether the second UE uses the first EAS based on the first information of the first EAS. For example, see [link to specific implementation]. Figures 5-7 The corresponding method implementation is as follows. A second specific implementation involves the second EES sending the first information of the first EAS to the second UE, and the second UE determining whether to use the first EAS based on the first information of the first EAS. For example, see [link to specific implementation details]. Figures 8-10 The corresponding method implementation.

[0150] In this embodiment of the application, the first EES can determine the first information of the first EAS based on the second information of the first EAS, and then send a first message to the second EES. The first information of the first EAS includes one or more of the following: the service area corresponding to the first EAS, the data center information corresponding to the first EAS, and the performance information corresponding to the first EAS.

[0151] In one possible embodiment, the service area corresponding to the first EAS refers to the service area where the first EAS can provide services. The UE can obtain services from the first EAS, connect to the first EAS, or obtain services based on certain KPIs provided by the first EAS within this service area. The service area can be a geographical service area or a network topology service area.

[0152] In one possible embodiment, the data center information of the first EAS can be the DNAI of the EDN where the first EAS is located and / or the EDN where the first EAS is located, or it can be the data center.

[0153] In one possible embodiment, the performance information corresponding to the first EAS may be the KPI information of the first EAS, and / or the response time information of the first EAS in the service area corresponding to the first EAS, and / or the latency between the UE and the first EAS, and / or the response time information between the first EAS and the AC. The response time information of the first EAS in the service area corresponding to the first EAS may indicate the response time for data transmission when the UE connects to the first EAS in the service area corresponding to the first EAS, that is, the duration from sending a data packet to receiving a data packet. The latency between the UE and the EAS may include uplink latency, that is, the latency from the UE to the EAS. The end-to-end latency may include downlink latency, that is, the latency from the EAS to the UE. The KPI information of the first EAS may include one or more information elements in Table 3 below.

[0154] Table 3

[0155]

[0156] In one possible embodiment, the first EES can use the first EAS as a public EAS, therefore, the first EAS in step 402 can also be called a public EAS.

[0157] It can be seen that, based on Figure 4The described method allows the first EES to send service area and / or data center information and / or performance information corresponding to the first EAS used by the first UE to the second EES. This enables the second EES to determine whether a second UE in the same UE group as the first UE is using the first EAS based on this information, rather than directly identifying the first EAS used by the first UE as the EAS used by the second UE. This facilitates the second UE connecting to a better EAS to obtain application services, thus achieving a superior service experience.

[0158] Please see Figure 5 , Figure 5 This application provides a flowchart illustrating a communication method for edge computing, wherein:

[0159] 501. The first UE sends second information of the first EAS to the first EES, the second information including address information and / or identifier. The first EAS is the EAS used by the first UE. Accordingly, the first EES can receive the second information of the first EAS.

[0160] 502. The first EES sends a first message to the second EES, the first message carrying the following information: the identifier of the UE group, and first information of the first EES, the first information including one or more of the following: service area, data center information, and performance information. The UE group includes the first UE and the second UE. Accordingly, the second EES can receive the first message.

[0161] For a detailed description of steps 501 and 502, please refer to the descriptions under steps 401 and 402, which will not be repeated here.

[0162] 503. The second UE sends a second message to the second EES, the second message being used to request the discovery of the EAS. The second message carries information about the second UE, including location information and / or application information corresponding to the second UE. Accordingly, the second EES can receive the second message.

[0163] In one possible embodiment, the second message may be an EAS discovery request.

[0164] In one possible embodiment, the application information corresponding to the second UE can be an AC profile or an EAS discovery requirement. For example, the AC profile may include one or more information elements from Table 1 above. For example, the EAS discovery requirement may include one or more information elements from Table 2 above.

[0165] 504. The second EES determines whether the second UE uses the first EAS based on the information of the second UE and the first information of the first EAS.

[0166] In one possible embodiment, the specific implementation of the second EES determining whether the second UE uses the first EAS based on the information of the second UE and the first information of the first EAS is as follows: the second EES determines the second EAS based on the information of the second UE; the second EES determines whether the second UE uses the first EAS or the second EAS based on the first information of the second EAS and the first information of the first EAS.

[0167] The first piece of information for the second EAS includes one or more of the following: the service area corresponding to the second EAS, the data center information corresponding to the second EAS, and the performance information corresponding to the second EAS. For descriptions of the service area, data center information, and performance information corresponding to the EAS, please refer to [link to relevant documentation]. Figure 4 The descriptions in the corresponding embodiments are not repeated here.

[0168] In this embodiment, the second EES can determine whether the second UE performs better using the first EAS or the second EAS based on the first information of the second EAS and the first EAS. If the second UE performs better using the first EAS, the second EES determines that the second UE uses the first EAS. If the second UE performs better using the second EAS, the second EES determines that the second UE uses the second EAS. "Performance better" refers to whether, for a group of UEs connected to multiple EASs, the interaction latency, interaction complexity, and latency / connection performance between the EASs are better than the latency / connection performance between each UE and the EAS, for a group of UEs connected to the same EAS.

[0169] For example, the second EES can determine whether the second UE uses the first EAS or the second EAS based on the service area corresponding to the second EAS, the service area corresponding to the first EAS, and the location information of the second UE.

[0170] For example, the second EES can determine whether the second UE uses the first EAS or the second EAS based on the DNAI information corresponding to the second EAS, the DNAI information corresponding to the first EAS, and the location information of the second UE.

[0171] For example, the second EES can determine whether the second UE uses the first EAS or the second EAS based on the KPI information of the second EAS and the KPI information of the first EAS.

[0172] For example, the second EES can determine whether the second UE uses the first EAS or the second EAS based on the response time information of the second EAS in the service area corresponding to the second EAS and the response time information of the first EAS in the service area corresponding to the first EAS.

[0173] For example, the second EES can determine whether the second UE uses the first EAS or the second EAS based on the response time information of the second EAS in the service area corresponding to the second EAS, the response time information of the first EAS in the service area corresponding to the first EAS, and the connection information between the first EES and the second EES. Optionally, the connection information between the first EES and the second EES can be the transmission delay between the first EES and the second EES.

[0174] In one possible embodiment, the second EES determines whether the second UE uses the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS. This includes: the second EES can determine whether the second UE uses the first EAS or the second EAS based on the first information of the second EAS and the first information of the first EAS, as well as the latency information or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES, or the latency information or response time information between the first EAS / first EES and the second EAS / second EES.

[0175] Optionally, the latency or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES can be pre-configured in the second EES and / or pre-configured in the first EES.

[0176] It can be seen that, based on Figure 5 The described method allows the second EES to determine whether a second UE in the same UE group as the first UE is using the first EAS, based on the service area and / or data center information and / or performance information corresponding to the first EAS used by the first UE, rather than directly determining the first EAS used by the first UE as the EAS used by the second UE. This facilitates the second UE connecting to a better EAS to obtain application services, thus achieving a superior application service experience.

[0177] Please see Figure 6 , Figure 6 This is a flowchart illustrating a communication method for edge computing provided in an embodiment of this application. Figure 6 The message names in the illustrated method flow are merely one specific example. Figure 6 The information transmitted in the illustrated method flow can also be carried in other messages for transmission; this application embodiment does not limit this. Wherein:

[0178] 601. The first UE sends an EAS information configuration request to the first EES. This EAS information configuration request carries second information about the first EAS, including address information and / or an identifier. The first EAS is the EAS used by the first UE. Accordingly, the first EES can receive the EAS information configuration request.

[0179] 602. The first EES sends an EAS information provisioning response to the first UE.

[0180] Steps 601 and 602 are optional. For example, the first UE sends an EAS discovery request message to the first EES. If, after receiving the EAS discovery request, the first EES determines, based on the information of the first UE, that there is only one EAS that meets the first UE's requirements, then that EAS is the first EAS. The first EES sends an EAS discovery response to the first UE, which carries the address and / or identifier of the first EAS, and then executes step 603. In this case, steps 601 and 602 do not need to be executed.

[0181] 603. The first EES sends a Public EAS Declaration Request to the second EES. This Public EAS Declaration Request carries the following information: the identifier of the first UE, the identifier of the UE group, first information of the first EAS, and second information of the first EAS. The first information includes one or more of the following: service area, data center information, and performance information. The UE group includes the first UE and the second UE. Accordingly, the second EES can receive this Public EAS Declaration Request.

[0182] 604. The second EES sends a common EAS announcement response to the first EES.

[0183] 605. The second UE sends an EAS discovery request to the second EES. This EAS discovery request is used to request the discovery of an EAS. The EAS discovery request carries the identifier of the second UE, the identifier of the UE group, and information about the second UE, including location information and / or application information corresponding to the second UE. Accordingly, the second EES can receive the EAS discovery request.

[0184] 606. The second EES determines the second EAS based on the information of the second UE.

[0185] Optionally, the second EES may be determined based on the information of the second UE and the information of the EAS managed by the second EES.

[0186] Optionally, the EAS can send a registration request message to the EES, carrying the EAS's information. Alternatively, the second EES can obtain the EAS's information through the network management system, or the second EES can obtain the EAS's information through pre-configuration.

[0187] Optionally, the information in EAS may include one or more of the information elements in Table 4 below.

[0188] Table 4

[0189]

[0190]

[0191] 607. The second EES determines whether the second UE uses the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS.

[0192] For specific implementation details of steps 601 and 603, please refer to [link to relevant documentation]. Figure 4 The descriptions of steps 401 and 402 are omitted here. For detailed implementations of steps 605 to 607, please refer to [link to relevant documentation]. Figure 5 The relevant descriptions of steps 503 to 504 are not repeated here.

[0193] 608. The second EES sends an EAS discovery response to the second UE. Accordingly, the second UE can receive the EAS discovery response.

[0194] If it is determined that the second UE is using the first EAS, the EAS discovery response carries the second information of the first EAS.

[0195] If it is determined that the second UE uses the second EAS, the EAS discovery response carries second information about the second EAS, which includes the identifier and / or address information of the second EAS. Figure 6 Take the second UE using the second EAS as an example.

[0196] In this embodiment of the application, if the EAS discovery response carries the second information of the first EAS, then after the second UE receives the EAS discovery response, it can communicate with the first EAS based on the second information of the first EAS.

[0197] If the EAS discovery response carries the second information of the second EAS, then after receiving the EAS discovery response, the second UE can communicate with the second EAS based on the second information of the second EAS.

[0198] 609. If it is determined that the second UE uses the second EAS, the second EES sends an EAS synchronization request to the second EAS. This EAS synchronization request carries the identifier of the first UE, the identifier of the UE group, and the second information of the first EAS. Accordingly, the second EAS can receive this EAS synchronization request.

[0199] In this embodiment of the application, after the second EAS receives the EAS synchronization request, step 614 can be executed.

[0200] 610. If it is determined that the second UE uses the second EAS, the second EES sends an EAS selection announcing request to the first EES. This EAS selection announcing request carries the identifier of the second UE, the identifier of the UE group, and the second information of the second EAS. Accordingly, the first EES can receive the EAS selection announcing request.

[0201] 611. The first EES sends an EAS synchronization request to the first EAS, which carries the identifier of the second UE, the identifier of the UE group, and the second information of the second EAS. Accordingly, the first EAS can receive the EAS synchronization request.

[0202] In this embodiment of the application, after the first EAS receives the EAS synchronization request, step 613 can be executed.

[0203] 612. The first EES sends an EAS selection announcement response to the second EES.

[0204] 613. The first EAS synchronizes the application context corresponding to the UE group with the second information of the second EAS.

[0205] 614. The second EAS synchronizes the application context corresponding to the UE group with the first EAS based on the second information of the first EAS.

[0206] In one possible embodiment, the identifier of the first UE and / or the identifier of the UE group carried in the public EAS announcement request in step 603, and the identifier of the first UE and / or the identifier of the UE group carried in the EAS synchronization request in step 609 are optional.

[0207] In one possible embodiment, the identification of the second UE and / or the identification of the UE group carried in the EAS discovery request in step 605, the identification of the second UE and / or the identification of the UE group carried in the EAS selection announcement request in step 610, and the identification of the second UE and / or the identification of the UE group carried in the EAS synchronization request in step 611 are optional.

[0208] It can be seen that, based on Figure 6 The described method allows the second EES to determine whether a second UE in the same UE group as the first UE is using the first EAS, based on the service area and / or data center information and / or performance information corresponding to the first EAS used by the first UE, rather than directly determining the first EAS used by the first UE as the EAS used by the second UE. This facilitates the second UE connecting to a better EAS to obtain application services, thus achieving a superior service experience. Furthermore, if the second UE is not using the first EAS, the second EAS and the first EAS can perform application context synchronization to ensure data consistency among different UEs in the same UE group, thereby enabling the services of UEs in the UE group to operate normally.

[0209] Please see Figure 7 , Figure 7 This is a flowchart illustrating a communication method for edge computing provided in an embodiment of this application. Figure 7 The message names in the illustrated method flow are merely one specific example. Figure 7 The information transmitted in the illustrated method flow can also be carried in other messages for transmission; this application embodiment does not limit this. Wherein:

[0210] 701. The first UE sends an EAS information configuration request to the first EES. This EAS information configuration request carries second information about the first EAS, including address information and / or an identifier. The first EAS is the EAS used by the first UE. Accordingly, the first EES can receive this EAS information configuration request.

[0211] 702. The first EES sends an EAS information configuration response to the first UE.

[0212] 703. The first EES sends a Public EAS Declaration Request to the second EES. This Public EAS Declaration Request carries the following information: the identifier of the first UE, the identifier of the UE group, first information of the first EAS, and second information of the first EAS. The first information includes one or more of the following: service area, data center information, and performance information. The UE group includes the first UE and the second UE. Accordingly, the second EES can receive this Public EAS Declaration Request.

[0213] 704. The second EES sends a public EAS declaration response to the first EES.

[0214] 705. The second UE sends an EAS discovery request to the second EES. This EAS discovery request is used to request the discovery of an EAS. The EAS discovery request carries the identifier of the second UE, the identifier of the UE group, and information about the second UE, including location information and / or application information corresponding to the second UE. Accordingly, the second EES can receive the EAS discovery request.

[0215] 706. The second EES determines the second EAS based on the information of the second UE.

[0216] 707. The second EES determines whether the second UE uses the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS.

[0217] The specific implementation methods for steps 701 to 707 can be found in the specific implementation methods for steps 601 to 607, and will not be repeated here.

[0218] 708. The second EES sends an EAS discovery response to the second UE. Accordingly, the second UE can receive the EAS discovery response.

[0219] If it is determined that the second UE is using the first EAS, the EAS discovery response carries the second information of the first EAS.

[0220] If it is determined that the second UE is using the second EAS, the EAS discovery response carries the identifier of the first UE, the identifier of the UE group, the second information of the second EAS, and the second information of the first EAS. The second information of the second EAS includes the identifier of the second EAS and / or the address information of the second EAS. Figure 7 Take the second UE using the second EAS as an example.

[0221] In this embodiment of the application, if the EAS discovery response carries the second information of the first EAS, then after the second UE receives the EAS discovery response, it can communicate with the first EAS based on the second information of the first EAS.

[0222] If the EAS discovery response carries the second information of both the second EAS and the first EAS, then after receiving the EAS discovery response, the second UE can communicate with the second EAS based on the second information of the second EAS. The second information of the first EAS is sent by the second UE to the second EAS so that the second EAS can perform application context synchronization with the first EAS based on the second information of the first EAS.

[0223] In one possible embodiment, if it is determined that the second UE is using the second EAS, the second response message also carries indication information, which indicates that the second EAS needs to synchronize the application context with the first EAS.

[0224] 709. The second UE sends the identifier of the first UE, the identifier of the UE group, and the second information of the first EAS to the second EAS. Correspondingly, the second EAS can receive the identifier of the first UE, the identifier of the UE group, and the second information of the first EAS.

[0225] Specifically, the EEC in the second UE can receive the EAS discovery response. The EEC in the second UE then sends this EAS discovery response to the AC in the second UE, and the AC in the second UE sends the identifier of the first UE, the identifier of the UE group, and the second information of the first EAS to the second EAS. In other words, in this embodiment, the application layer of the second UE can notify the second EAS to synchronize application context with the first EAS.

[0226] In this embodiment of the application, after the second EAS receives the identifier of the first UE, the identifier of the UE group, and the second information of the first EAS, it can execute step 714.

[0227] 710. If it is determined that the second UE uses the second EAS, the second EES sends an EAS selection announcement request to the first EES. The EAS selection announcement request carries the identifier of the second UE, the identifier of the UE group, and the second information of the second EAS. Accordingly, the first EES may receive the EAS selection announcement request.

[0228] 711. The first EES sends an EAS synchronization request to the first EAS. This EAS synchronization request carries the identifier of the second UE, the identifier of the UE group, and the second information of the second EAS. Accordingly, the first EAS can receive the EAS synchronization request.

[0229] In this embodiment of the application, after the first EAS receives the EAS synchronization request, step 713 can be executed.

[0230] 712. The first EES sends an EAS selection declaration response to the second EES.

[0231] 713. The first EAS synchronizes the application context corresponding to the UE group with the second information of the second EAS.

[0232] 714. The second EAS synchronizes the application context corresponding to the UE group with the information of the first EAS.

[0233] In one possible embodiment, the identifier of the first UE and / or the identifier of the UE group carried in the public EAS announcement request in step 703, and the identifier of the first UE and / or the identifier of the UE group carried in the EAS discovery response in step 708, are optional. The identifier of the first UE and / or the identifier of the UE group in step 709 are also optional.

[0234] In one possible embodiment, the identification of the second UE and / or the identification of the UE group carried in the EAS discovery request in step 705, the identification of the second UE and / or the identification of the UE group carried in the EAS selection announcement request in step 710, and the identification of the second UE and / or the identification of the UE group carried in the EAS synchronization request in step 711 are optional.

[0235] It can be seen that, based on Figure 7 The described method allows the second EES to determine whether a second UE in the same UE group as the first UE is using the first EAS, based on the service area and / or data center information and / or performance information corresponding to the first EAS used by the first UE, rather than directly determining the first EAS used by the first UE as the EAS used by the second UE. This facilitates the second UE connecting to a better EAS to obtain application services, thus achieving a superior service experience. Furthermore, if the second UE is not using the first EAS, the second EAS and the first EAS can perform application context synchronization to ensure data consistency among different UEs in the same UE group, thereby enabling the services of UEs in the UE group to operate normally.

[0236] Please see Figure 8 , Figure 8 This application provides a flowchart illustrating a communication method for edge computing, wherein:

[0237] 801. The first UE sends second information of the first EAS to the first EES, the second information including address information and / or identifier. The first EAS is the EAS used by the first UE. Correspondingly, the first EES can receive the second information of the first EAS.

[0238] 802. The first EES sends a first message to the second EES, the first message carrying the following information: the identifier of the UE group, and first information of the first EES, the first information including one or more of the following: service area, data center information, and performance information. The UE group includes the first UE and the second UE. Accordingly, the second EES can receive the first message.

[0239] 803. The second UE sends a second message to the second EES. This second message is used to request the discovery of the EAS. The second message carries information about the second UE, including location information and / or application information corresponding to the second UE. Accordingly, the second EES can receive this second message.

[0240] 804. The second EES determines the second EAS based on the information of the second UE.

[0241] The specific implementation methods of steps 801 to 804 can be found in the corresponding descriptions of steps 501 to 504, and will not be repeated here.

[0242] 805. The second EES sends a second response message corresponding to the second message to the second UE. The second response message carries the first information of the first EAS and the first information of the second EAS. Accordingly, the second UE can receive the second response message.

[0243] Optionally, the second response message may also carry latency information or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES, or latency information or response time information between the first EAS / first EES and the second EAS / second EES. Accordingly, the second UE can determine whether to use the first EAS or the second EAS based on the latency information or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES, or the latency information or response time information between the first EAS / first EES and the second EAS / second EES, as well as the first information of the first EAS and the first information of the second EAS.

[0244] Optionally, the latency or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES can be pre-configured in the second EES and / or pre-configured in the first EES.

[0245] 806. The second UE determines whether to use the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS.

[0246] The first piece of information for the second EAS includes one or more of the following: the service area corresponding to the second EAS, the data center information corresponding to the second EAS, and the performance information corresponding to the second EAS. For descriptions of the service area, data center information, and performance information of the second EAS, please refer to [link to relevant documentation]. Figure 4 The descriptions in the corresponding embodiments are not repeated here.

[0247] Among them, the second UE determines the specific implementation method of using the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS, and... Figure 5The specific implementation of the second EES in the corresponding embodiments, which determines whether the second UE uses the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS, is the same and will not be repeated here.

[0248] It can be seen that, based on Figure 8 The described method allows the second UE to determine whether it is using the first EAS based on the service area and / or data center information and / or performance information corresponding to the first EAS used by the first UE, rather than directly determining the first EAS used by the first UE as the EAS used by the second UE. This facilitates the second UE connecting to a better EAS to obtain application services, thus achieving a superior application service experience.

[0249] Please see Figure 9 , Figure 9 This is a flowchart illustrating a communication method for edge computing provided in an embodiment of this application. Figure 9 The message names in the illustrated method flow are merely one specific example. Figure 9 The information transmitted in the illustrated method flow can also be carried in other messages for transmission; this application embodiment does not limit this. Wherein:

[0250] 901. The first UE sends an EAS information configuration request to the first EES. This EAS information configuration request carries second information about the first EAS, including address information and / or an identifier. The first EAS is the EAS used by the first UE. Accordingly, the first EES can receive this EAS information configuration request.

[0251] 902. The first EES sends an EAS information configuration response to the first UE.

[0252] 903. The first EES sends a Public EAS Declaration Request to the second EES. This Public EAS Declaration Request carries the following information: the identifier of the first UE, the identifier of the UE group, first information of the first EAS, and second information of the first EAS. The first information includes one or more of the following: service area, data center information, and performance information. The UE group includes the first UE and the second UE. Accordingly, the second EES can receive this Public EAS Declaration Request.

[0253] 904. The second EES sends a public EAS declaration response to the first EES.

[0254] 905. The second UE sends an EAS discovery request to the second EES. This EAS discovery request is used to request the discovery of an EAS. The EAS discovery request carries the identifier of the second UE, the identifier of the UE group, and information about the second UE, including location information and / or application information corresponding to the second UE. Accordingly, the second EES can receive the EAS discovery request.

[0255] 906. The second EES determines the second EAS based on the information of the second UE.

[0256] The specific implementation methods for steps 901 to 906 can be found in the specific implementation methods for steps 601 to 607, and will not be repeated here.

[0257] 907. The second EES sends an EAS discovery response to the second UE. The EAS discovery response carries the UE group identifier, the first information of the first EAS, the first information of the second EAS, the second information of the first EAS, and the second information of the second EAS. The second information of the second EAS includes the identifier of the second EAS and / or the address information of the second EAS. Accordingly, the second UE can receive the EAS discovery response.

[0258] Optionally, the EAS discovery response may also carry latency information or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES, or latency information or response time information between the first EAS / first EES and the second EAS / second EES. Accordingly, the second UE can determine whether to use the first EAS or the second EAS based on the latency information or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES, or the latency information or response time information between the first EAS / first EES and the second EAS / second EES, as well as the first information of the first EAS and the first information of the second EAS.

[0259] Optionally, the latency or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES can be pre-configured in the second EES and / or pre-configured in the first EES.

[0260] 908. The second UE determines whether to use the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS.

[0261] For specific implementation methods of steps 907 to 908, please refer to the specific implementation methods of steps 805 and 806, which will not be repeated here.

[0262] In this embodiment of the application, if it is determined that the second UE uses the first EAS, the second UE communicates with the first EAS based on the second information of the first EAS; if it is determined that the second UE uses the second EAS, the second UE communicates with the second EAS based on the second information of the second EAS.

[0263] 909. The second UE sends an EAS information configuration message to the second EES. This message carries the identifier of the UE group and second information and / or indication information of the EAS used by the second UE. The indication information indicates whether the second UE uses the first EAS or whether application context synchronization is required. Accordingly, the second EES can receive the EAS information configuration message.

[0264] 910. If the second EES determines, based on the information and / or indication information of the EAS selected by the second UE, that context synchronization is required between the first EAS and the second EAS, then the second EES sends an EAS synchronization request to the second EAS. This EAS synchronization request carries the identifier of the first UE, the identifier of the UE group, and the second information of the first EAS. Accordingly, the second EAS can receive the EAS synchronization request.

[0265] After receiving the EAS synchronization request, the second EAS can execute step 915.

[0266] 911. If the second EES determines, based on the information and / or indication information of the EAS used by the second UE, that context synchronization is required between the first EAS and the second EAS, then the second EES sends an EAS selection announcement request to the first EES. This EAS selection announcement request carries the identifier of the second UE, the identifier of the UE group, and the second information of the second EAS. Accordingly, the first EES may receive the EAS selection announcement request.

[0267] 912. The first EES sends an EAS synchronization request to the first EAS. This EAS synchronization request carries the identifier of the second UE, the identifier of the UE group, and the second information of the second EAS. Accordingly, the first EAS can receive the EAS synchronization request.

[0268] After receiving the EAS synchronization request, the first EAS can execute step 914.

[0269] 913. The first EES sends an EAS selection declaration response to the second EES.

[0270] 914. The first EAS synchronizes the application context corresponding to the UE group with the second information of the second EAS.

[0271] 915. The second EAS synchronizes the application context corresponding to the UE group with the information of the first EAS.

[0272] In one possible embodiment, the identifier of the first UE and / or the identifier of the UE group carried in the public EAS announcement request in step 903, and the identifier of the first UE and / or the identifier of the UE group carried in the EAS synchronization request in step 910, are optional. The identifier of the UE group carried in the EAS discovery response in step 907 is optional.

[0273] In one possible embodiment, the identification of the second UE and / or the identification of the UE group carried in the EAS discovery request in step 905, the identification of the second UE and / or the identification of the UE group carried in the EAS selection announcement request in step 911, and the identification of the second UE and / or the identification of the UE group carried in the EAS synchronization request in step 912 are optional.

[0274] It can be seen that, based on Figure 9 The described method allows the second UE to determine whether it is using the first EAS based on the service area and / or data center information and / or performance information corresponding to the first EAS used by the first UE, rather than directly determining the first EAS used by the first UE as the EAS used by the second UE. This facilitates the second UE connecting to a better EAS to obtain application services, thus achieving a superior service experience. Furthermore, if the second UE is not using the first EAS, the second EAS and the first EAS can perform application context synchronization to ensure data consistency among different UEs within the same UE group, thereby enabling the normal operation of services for UEs within the UE group.

[0275] Please see Figure 10 , Figure 10 This is a flowchart illustrating a communication method for edge computing provided in an embodiment of this application. Figure 10 The message names in the illustrated method flow are merely a specific example. Figure 10 The information transmitted in the illustrated method flow can also be carried in other messages for transmission; this application embodiment does not limit this. Wherein:

[0276] 1001. The first UE sends an EAS information configuration request to the first EES. This EAS information configuration request carries second information about the first EAS, including address information and / or an identifier. The first EAS is the EAS used by the first UE. Accordingly, the first EES can receive this EAS information configuration request.

[0277] 1002. The first EES sends an EAS information configuration response to the first UE.

[0278] 1003. The first EES sends a Public EAS Declaration Request to the second EES. This Public EAS Declaration Request carries the following information: the identifier of the first UE, the identifier of the UE group, first information of the first EAS, and second information of the first EAS. The first information includes one or more of the following: service area, data center information, and performance information. The UE group includes the first UE and the second UE. Accordingly, the second EES can receive this Public EAS Declaration Request.

[0279] 1004. The second EES sends a public EAS declaration response to the first EES.

[0280] 1005. The second UE sends an EAS discovery request to the second EES. This EAS discovery request is used to request the discovery of an EAS. The EAS discovery request carries the identifier of the second UE, the identifier of the UE group, and information about the second UE, including location information and / or application information corresponding to the second UE. Accordingly, the second EES can receive the EAS discovery request.

[0281] 1006. The second EES determines the second EAS based on the information of the second UE.

[0282] The specific implementation methods for steps 901 to 906 can be found in the specific implementation methods for steps 601 to 607, and will not be repeated here.

[0283] 1007. The second EES sends an EAS discovery response to the second UE. The EAS discovery response carries the UE group identifier, the first information of the first EAS, the first information of the second EAS, the second information of the first EAS, and the second information of the second EAS. The second information of the second EAS includes the identifier of the second EAS and / or the address information of the second EAS. Accordingly, the second UE can receive the EAS discovery response.

[0284] Optionally, the EAS discovery response may also carry latency information or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES, or latency information or response time information between the first EAS / first EES and the second EAS / second EES. Accordingly, the second UE can determine whether to use the first EAS or the second EAS based on the latency information or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES, or the latency information or response time information between the first EAS / first EES and the second EAS / second EES, as well as the first information of the first EAS and the first information of the second EAS.

[0285] Optionally, the latency or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES can be pre-configured in the second EES and / or pre-configured in the first EES.

[0286] 1008. The second UE determines whether to use the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS.

[0287] For specific implementation methods of steps 1007 to 1008, please refer to the specific implementation methods of steps 805 and 806, which will not be repeated here.

[0288] In this embodiment of the application, if it is determined that the second UE uses the first EAS, the second UE communicates with the first EAS based on the second information of the first EAS; if it is determined that the second UE uses the second EAS, the second UE communicates with the second EAS based on the second information of the second EAS.

[0289] 1009. The second UE sends an EAS information configuration message to the second EES. This message carries the identifier of the UE group and the second information and / or indication information of the EAS used by the second UE. The indication information indicates whether the second UE uses the first EAS or whether application context synchronization is required. Accordingly, the second EES can receive the EAS information configuration message.

[0290] 1010. If the second EES determines, based on the information and / or indication information of the EAS used by the second UE, that context synchronization is required between the first EAS and the second EAS, then the second EES sends an EAS selection announcement request to the first EES. This EAS selection announcement request carries the identifier of the second UE, the identifier of the UE group, and the second information of the second EAS. Accordingly, the first EES may receive the EAS selection announcement request.

[0291] 1011. The first EES sends an EAS synchronization request to the first EAS. This EAS synchronization request carries the identifier of the second UE, the identifier of the UE group, and the second information of the second EAS. Accordingly, the first EAS can receive the EAS synchronization request.

[0292] In this embodiment of the application, after the first EAS receives the EAS synchronization request, it executes step 1014.

[0293] 1012. The first EES sends an EAS selection declaration response to the second EES.

[0294] 1013. If it is determined that the second UE uses the second EAS, then the second UE sends the identifier of the first UE, the identifier of the UE group, and the second information of the first EAS to the second EAS. Correspondingly, the second EAS can receive the identifier of the first UE, the identifier of the UE group, and the second information of the first EAS.

[0295] Specifically, the AC in the second UE can send the identifier of the first UE, the identifier of the UE group, and the second information of the first EAS to the second EAS. In other words, in this embodiment of the application, the application layer of the second UE can notify the second EAS to perform application context synchronization with the first EAS.

[0296] In this embodiment of the application, after the second EAS receives the identifier of the first UE, the identifier of the UE group, and the second information of the first EAS, it can execute step 1015.

[0297] 1014. The first EAS synchronizes the application context corresponding to the UE group with the second information of the second EAS.

[0298] 1015. The second EAS synchronizes the application context corresponding to the UE group with the information of the first EAS.

[0299] In one possible embodiment, the identifier of the first UE and / or the identifier of the UE group carried in the public EAS announcement request in step 1003, and the identifier of the first UE and / or the identifier of the UE group carried in the EAS discovery response in step 1007, are optional. The identifier of the first UE and / or the identifier of the UE group in step 1013 are also optional.

[0300] In one possible embodiment, the identifier of the second UE and / or the identifier of the UE group carried in the EAS discovery request in step 1005, the identifier of the second UE and / or the identifier of the UE group carried in the EAS selection announcement request in step 1010, and the identifier of the second UE and / or the identifier of the UE group carried in the EAS synchronization request in step 1011 are optional.

[0301] It can be seen that, based on Figure 10 The described method allows the second UE to determine whether it is using the first EAS based on the service area and / or data center information and / or performance information corresponding to the first EAS used by the first UE, rather than directly determining the first EAS used by the first UE as the EAS used by the second UE. This facilitates the second UE connecting to a better EAS to obtain application services, thus achieving a superior service experience. Furthermore, if the second UE is not using the first EAS, the second EAS and the first EAS can perform application context synchronization to ensure data consistency among different UEs within the same UE group, thereby enabling the normal operation of services for UEs within the UE group.

[0302] Please see Figure 11 , Figure 11 This application provides a flowchart illustrating a communication method for edge computing, wherein:

[0303] 1101. The first UE sends second information of the first EAS to the first EES. The second information includes address information and / or identifier. The first EAS is the EAS used by the first UE. Accordingly, the first EES can receive the second information of the first EAS.

[0304] The specific implementation of step 1101 can be found in the specific implementation of step 401, and will not be repeated here.

[0305] 1102. The first EES sends a first message to the second EES, the first message carrying the second information of the first EES. Accordingly, the second EES can receive the first message.

[0306] In one possible embodiment, the first message may be a public EAS declaration request.

[0307] 1103. The second UE sends a third message to the second EES. This third message is used to request the discovery of the EAS. The third message carries information about the second UE, including location information and / or application information corresponding to the second UE. The second UE is in the same UE group as the first UE. Accordingly, the second EES can receive this third message.

[0308] For information regarding the second UE, please refer to [link / reference]. Figure 5 The description of the information of the second UE in the corresponding embodiments will not be repeated here.

[0309] In one possible embodiment, the third message may be an EAS discovery request.

[0310] 1104. The second EES determines the second EAS based on the information of the second UE.

[0311] The second EES determines the second EAS based on the information of the second UE, and has the following two implementation methods:

[0312] Method 1: If the second EES determines an EAS that meets the requirements of the second UE based on the information of the second UE, then the EAS is the second EAS.

[0313] Method 2: If the second EES determines multiple EASs that meet the needs of the second UE based on the information of the second UE, the second EES can provide feedback on these multiple EASs to the second UE, and the second UE can select one EAS from these multiple EASs. The EAS selected by the second UE is the second EAS. The second UE then notifies the second EES of the second EAS.

[0314] 1105. The second EES sends a second message to the first EES. This second message carries the identifier of the second UE and the first information of the second EES. The first information includes one or more of the following: service area, data center information, and performance information. Accordingly, the first EES can receive this second message.

[0315] Optionally, the first EES may also determine whether to use the first EAS or the second EAS based on the latency information or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES, or the latency information or response time information between the first EAS / first EES and the second EAS / second EES, as well as the first information of the first EAS and the first information of the second EAS.

[0316] Optionally, the latency or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES can be pre-configured in the first EES.

[0317] Optionally, the second message may also carry latency or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES, or latency or response time information between the first EAS / first EES and the second EAS / second EES. Optionally, the latency or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES may be pre-configured in the second EES. Optionally, the latency or response time information between the first EAS / first EES and the second EAS / second EES may be pre-configured in the second EES.

[0318] 1106. The first EES determines whether the second UE uses the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS.

[0319] The first information of the first EAS includes one or more of the following: the service area corresponding to the first EAS, the data center information corresponding to the first EAS, and the performance information corresponding to the first EAS. For descriptions of the service area, data center information, and performance information of the first EAS, please refer to [link to relevant documentation]. Figure 4 The descriptions in the corresponding embodiments are not repeated here.

[0320] Specifically, the first EES determines the specific implementation method of the second UE using the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS. Figure 5 The specific implementation of the second EES in the corresponding embodiments, which determines whether the second UE uses the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS, is the same and will not be repeated here.

[0321] In one possible embodiment, the first message may also carry the identifier of the first UE and / or the identifier of the UE group to which the first UE belongs.

[0322] In one possible embodiment, the third message may also carry the identifier of the second UE and / or the identifier of the UE group to which the second UE belongs.

[0323] In one possible embodiment, the second message may also carry the identifier of the UE group to which the second UE belongs.

[0324] It can be seen that, based on Figure 11 The described method allows the first EES to determine whether the second UE uses the first EAS based on the service area and / or data center information and / or performance information corresponding to the first EAS used by the first UE, rather than directly determining the first EAS used by the first UE as the EAS used by the second UE. This facilitates the second UE connecting to a better EAS to obtain application services, thus achieving a superior application service experience.

[0325] Please see Figure 12 , Figure 12 This is a flowchart illustrating a communication method for edge computing provided in an embodiment of this application. Figure 12 The message names in the illustrated method flow are merely one specific example. Figure 12 The information transmitted in the illustrated method flow can also be carried in other messages for transmission; this application embodiment does not limit this. Wherein:

[0326] 1201. The first UE sends an EAS information configuration request to the first EES. This EAS information configuration request carries second information about the first EAS, including address information and / or an identifier. The first EAS is the EAS used by the first UE. Accordingly, the first EES can receive this EAS information configuration request.

[0327] 1202. The first EES sends an EAS information configuration response to the first UE.

[0328] The specific implementation methods for steps 1201 to 1202 can be found in the specific implementation methods for steps 601 to 602, and will not be repeated here.

[0329] 1203. The first EES sends a Public EAS Declaration Request to the second EES. This Public EAS Declaration Request carries the following information: the identifier of the first UE, the identifier of the UE group, and the second information of the first EAS. The UE group includes the first UE and the second UE. Accordingly, the second EES can receive this Public EAS Declaration Request.

[0330] 1204. The second EES sends a public EAS declaration response to the first EES.

[0331] 1205. The second UE sends an EAS discovery request to the second EES. This EAS discovery request is used to request the discovery of an EAS. The EAS discovery request carries the identifier of the second UE, the identifier of the UE group, and information about the second UE, including location information and / or application information corresponding to the second UE. Accordingly, the second EES can receive the EAS discovery request.

[0332] 1206. The second EES sends an EAS discovery response to the second UE, which carries secondary information about multiple EAS. Accordingly, the second UE can receive the EAS discovery response.

[0333] 1207. The second UE sends an EAS information configuration request to the second EES, which carries the second information of the second EAS. Accordingly, the second EES can receive the EAS information configuration request.

[0334] 1208. The second EES sends an EAS information configuration response to the second UE.

[0335] 1209. The second EES sends a public EAS announcement request to the first EES. This request carries the identifier of the second UE, the identifier of the UE group, the information of the second UE, the first information of the second EAS, and the second information of the second EAS. The first information includes one or more of the following: service area, data center information, and performance information. Accordingly, the first EES can receive the public EAS announcement request.

[0336] Optionally, the first EES may also determine whether to use the first EAS or the second EAS based on the latency information or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES, or the latency information or response time information between the first EAS / first EES and the second EAS / second EES, as well as the first information of the first EAS and the first information of the second EAS.

[0337] Optionally, the latency or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES can be pre-configured in the first EES.

[0338] Optionally, the public EAS declaration request may also carry latency or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES, or latency or response time information between the first EAS / first EES and the second EAS / second EES. Optionally, the latency or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES may be pre-configured in the second EES. Optionally, the latency or response time information between the first EAS / first EES and the second EAS / second EES may be pre-configured in the second EES.

[0339] 1210. The first EES determines whether the second UE uses the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS.

[0340] The specific implementation methods for steps 1203 to 1210 can be found in the specific implementation methods for steps 1101 to 1106, and will not be repeated here.

[0341] 1211. The first EES sends a public EAS announcement response to the second EES, which carries the identifier of the second UE, the identifier of the UE group, and the second information of the EAS used by the second UE. Accordingly, the second EES can receive the public EAS announcement response.

[0342] in, Figure 12 Taking the EAS used by the second UE as an example.

[0343] 1212. The second EES sends a fourth message to the second UE, which carries the second information of the EES used by the second UE. Accordingly, the second UE can receive the fourth message.

[0344] If the EAS used by the second UE is the first EAS, then after receiving the fourth message, the second UE can communicate with the first EAS based on the second information of the first EAS.

[0345] If the EAS used by the second UE is the second EAS, then after receiving the fourth message, the second UE can communicate with the second EAS based on the second information of the second EAS.

[0346] 1213. The second EES sends an EAS synchronization request to the second EAS. This EAS synchronization request carries the identifier of the first UE, the identifier of the UE group, and the second information of the first EAS. Accordingly, the second EAS can receive this EAS synchronization request.

[0347] In this embodiment of the application, after the second EAS receives the EAS synchronization request, step 1216 can be executed.

[0348] 1214. If it is determined that the second UE uses the second EAS, the first EES sends an EAS synchronization request to the first EAS. This EAS synchronization request carries the identifier of the second UE, the identifier of the UE group, and the second information of the second EAS. Accordingly, the first EAS can receive this EAS synchronization request.

[0349] In this embodiment of the application, after the first EAS receives the EAS synchronization request, step 1215 can be executed.

[0350] 1215. The first EAS synchronizes the application context corresponding to the UE group with the second information of the second EAS.

[0351] 1216. The second EAS synchronizes the application context corresponding to the UE group with the information of the first EAS.

[0352] For specific implementation methods of steps 1201 to 1210, please refer to [link to relevant documentation]. Figure 11 The relevant descriptions in the corresponding embodiments are not repeated here.

[0353] In one possible embodiment, the identifier of the first UE and / or the identifier of the UE group carried in the public EAS announcement request in step 1203, and the identifier of the first UE and / or the identifier of the UE group carried in the EAS synchronization request in step 1213 are optional.

[0354] In one possible embodiment, the identifier of the second UE and / or the identifier of the UE group carried in the EAS discovery request in step 1205, the identifier of the second UE and / or the identifier of the UE group carried in the EAS selection announcement request in step 1209, the EAS selection announcement response in step 1211, and the identifier of the second UE and / or the identifier of the UE group carried in the EAS synchronization request in step 1214 are optional.

[0355] It can be seen that, based on Figure 12 The described method allows the first EES to determine whether the second UE uses the first EAS based on the service area and / or data center information and / or performance information corresponding to the first EAS used by the first UE, rather than directly determining the first EAS used by the first UE as the EAS used by the second UE. This facilitates the second UE connecting to a better EAS to obtain application services, thus achieving a superior service experience. Furthermore, if the second UE does not use the first EAS, the second EAS and the first EAS can perform application context synchronization to ensure data consistency among different UEs within the same UE group, thereby enabling the normal operation of services for UEs within the UE group.

[0356] Please see Figure 13 , Figure 13 This is a flowchart illustrating a communication method for edge computing provided in an embodiment of this application. Figure 13 The message names in the illustrated method flow are merely one specific example. Figure 13 The information transmitted in the illustrated method flow can also be carried in other messages for transmission; this application embodiment does not limit this. Wherein:

[0357] 1301. The first UE sends an EAS information configuration request to the first EES. This EAS information configuration request carries second information about the first EAS, including address information and / or an identifier. The first EAS is the EAS used by the first UE. Accordingly, the first EES can receive this EAS information configuration request.

[0358] 1302. The first EES sends an EAS information configuration response to the first UE.

[0359] The specific implementation methods for steps 1301 to 1302 can be found in the specific implementation methods for steps 601 to 602, and will not be repeated here.

[0360] 1303. The first EES sends a Public EAS Declaration Request to the second EES. This Public EAS Declaration Request carries the following information: the identifier of the first UE, the identifier of the UE group, and the second information of the first EAS. The UE group includes the first UE and the second UE. Accordingly, the second EES can receive this Public EAS Declaration Request.

[0361] 1304. The second EES sends a public EAS declaration response to the first EES.

[0362] 1305. The second UE sends an EAS discovery request to the second EES. This EAS discovery request is used to request the discovery of an EAS. The EAS discovery request carries the identifier of the second UE, the identifier of the UE group, and information about the second UE, including location information and / or application information corresponding to the second UE. Accordingly, the second EES can receive the EAS discovery request.

[0363] 1306. The second EES sends an EAS discovery response to the second UE, which carries secondary information about multiple EAS. Accordingly, the second UE can receive the EAS discovery response.

[0364] 1307. The second UE sends an EAS information configuration request to the second EES, which carries the second information of the second EAS. Accordingly, the second EES can receive the EAS information configuration request.

[0365] 1308. The second EES sends an EAS information configuration response to the second UE.

[0366] 1309. The second EES sends a public EAS announcement request to the first EES. This request carries the identifier of the second UE, the identifier of the UE group, the information of the second UE, the first information of the second EAS, and the second information of the second EAS. The first information includes one or more of the following: service area, data center information, and performance information. Accordingly, the first EES may receive the public EAS announcement request.

[0367] Optionally, the first EES may also determine whether to use the first EAS or the second EAS based on the latency information or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES, or the latency information or response time information between the first EAS / first EES and the second EAS / second EES, as well as the first information of the first EAS and the first information of the second EAS.

[0368] Optionally, the latency or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES can be pre-configured in the first EES.

[0369] Optionally, the public EAS declaration request may also carry latency or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES, or latency or response time information between the first EAS / first EES and the second EAS / second EES. Optionally, the latency or response time information between the data center corresponding to the first EAS / first EES and the data center corresponding to the second EAS / second EES may be pre-configured in the second EES. Optionally, the latency or response time information between the first EAS / first EES and the second EAS / second EES may be pre-configured in the second EES.

[0370] 1310. The first EES determines whether the second UE uses the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS.

[0371] The specific implementation methods for steps 1303 to 1310 can be found in the specific implementation methods for steps 1101 to 1106, and will not be repeated here.

[0372] 1311. The first EES sends a public EAS announcement response to the second EES, which carries the identifier of the second UE, the identifier of the UE group, and the second information of the EAS used by the second UE. Accordingly, the second EES can receive the public EAS announcement response.

[0373] 1312. The second EES sends a fourth message to the second UE, which carries the second information of the EES used by the second UE. Accordingly, the second UE can receive the fourth message.

[0374] If the EAS used by the second UE is the first EAS, then after receiving the fourth message, the second UE can communicate with the first EAS based on the second information of the first EAS.

[0375] If the second UE uses the second EAS, then after receiving the fourth message, the second UE can communicate with the second EAS based on the second information of the second EAS. If the second UE uses the second EAS, then the fourth message also carries the identifier of the first UE, the identifier of the UE group, and the second information of the first EAS. Figure 13 Taking the EAS used by the second UE as an example.

[0376] 1313. The second UE sends the identifier of the first UE, the identifier of the UE group, and the second information of the first EAS to the second EAS. Correspondingly, the second EAS can receive the identifier of the first UE, the identifier of the UE group, and the second information of the first EAS.

[0377] Specifically, the AC in the second UE can send the identifier of the first UE, the identifier of the UE group, and the second information of the first EAS to the second EAS. In other words, in this embodiment of the application, the application layer of the second UE can notify the second EAS to perform application context synchronization with the first EAS.

[0378] In this embodiment of the application, after the second EAS receives the identifier of the first UE, the identifier of the UE group, and the second information of the first EAS, it can execute step 1316.

[0379] 1314. If it is determined that the second UE uses the second EAS, the first EES sends an EAS synchronization request to the first EAS. The EAS synchronization request carries the identifier of the second UE, the identifier of the UE group, and the second information of the second EAS. Accordingly, the first EAS can receive the EAS synchronization request.

[0380] In this embodiment of the application, after the first EAS receives the EAS synchronization request, step 1315 can be executed.

[0381] 1315. The first EAS synchronizes the application context corresponding to the UE group with the second information of the second EAS.

[0382] 1316. The second EAS synchronizes the application context corresponding to the UE group with the information of the first EAS.

[0383] In one possible embodiment, the fourth message also carries an instruction that indicates that the second EAS needs to synchronize its application context with the first EAS.

[0384] In one possible embodiment, the second response message also carries indication information that the second EAS needs to synchronize its application context with the first EAS.

[0385] In one possible embodiment, the identifier of the first UE and / or the identifier of the UE group carried in the public EAS declaration request in step 1303, and the identifier of the first UE and / or the identifier of the UE group carried in the fourth message in step 1312, are optional. The identifier of the first UE and / or the identifier of the UE group in step 1313 are also optional.

[0386] In one possible embodiment, the identifier of the second UE and / or the identifier of the UE group carried in the EAS discovery request in step 1305, the identifier of the second UE and / or the identifier of the UE group carried in the EAS selection announcement request in step 1309, the identifier of the second UE and / or the identifier of the UE group carried in the EAS selection announcement response in step 1311, and the identifier of the second UE and / or the identifier of the UE group carried in the EAS synchronization request in step 1314 are optional.

[0387] It can be seen that, based on Figure 13 The described method allows the first EES to determine whether the second UE uses the first EAS based on the service area and / or data center information and / or performance information corresponding to the first EAS used by the first UE, rather than directly determining the first EAS used by the first UE as the EAS used by the second UE. This facilitates the second UE connecting to a better EAS to obtain application services, thus achieving a superior service experience. Furthermore, if the second UE does not use the first EAS, the second EAS and the first EAS can perform application context synchronization to ensure data consistency among different UEs within the same UE group, thereby enabling the normal operation of services for UEs within the UE group.

[0388] This application provides a communication device that can be used to implement the functions of the second EES, first EES, second UE, first EAS, or second EAS described above. This communication device can be the second EES, first EES, second UE, first EAS, or second EAS. The communication device includes modules or units corresponding one-to-one with the methods / operations / steps / actions performed by the second EES, first EES, second UE, first EAS, or second EAS in the above method embodiments. These units can be hardware circuits, software, or a combination of hardware circuits and software implementation. Please refer to... Figure 14 , Figure 14 A schematic diagram of a communication device 1400 according to an embodiment of this application is shown. The communication device 1400 may include an interface unit 1401 and a processing unit 1402. Specifically, the processing unit 1402 is used to process signaling and / or data, which may be data received by the interface unit 1401, and the processed signaling and / or data may also be sent by the interface unit 1401.

[0389] In one embodiment, when the communication device 1400 is a second EES, wherein:

[0390] Interface unit 1401 is used to receive a first message sent by the first EES. The first message carries the following information: the identifier of the UE group, the first information of the first edge application server (EAS), and the first information includes one or more of the following: service area, data center information, and performance information; the first EAS is the EAS used by the first UE, and the UE group includes the first UE and the second UE.

[0391] In one possible embodiment, the interface unit 1401 is further configured to receive a second message sent by the second UE, the second message being used to request the discovery of EAS, the second message carrying information of the second UE, the information of the second UE including location information and / or application information corresponding to the second UE; the processing unit 1402 is configured to determine whether the second UE uses the first EAS based on the information of the second UE and the first information of the first EAS.

[0392] In one possible embodiment, the processing unit 1402 determines whether the second UE uses the first EAS based on the information of the second UE and the first information of the first EAS, including: the processing unit 1402 determines the second EAS based on the information of the second UE; the processing unit 1402 determines whether the second UE uses the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS.

[0393] In one possible embodiment, the first message also carries second information of the first EAS, the second information including identification and / or address information. The interface unit 1401 is also used to send a second response message corresponding to the second message to the second UE. If it is determined that the second UE uses the first EAS, the second response message carries the second information of the first EAS. If it is determined that the second UE uses the second EAS, the second response message carries the second information of the second EAS.

[0394] In one possible embodiment, if it is determined that the second UE uses the second EAS, then the interface unit 1401 is further configured to send the second information of the first EAS to the second EAS; if it is determined that the second UE uses the second EAS, then the interface unit 1401 is further configured to send the second information of the second EAS to the first EAS.

[0395] In one possible embodiment, if it is determined that the second UE uses the second EAS, the second response message also carries the second information of the first EAS; if it is determined that the second UE uses the second EAS, the interface unit 1401 is also used to send the second information of the second EAS to the first EES.

[0396] In one possible embodiment, if it is determined that the second UE uses the second EAS, the second response message also carries indication information, which indicates that the second EAS needs to synchronize the application context with the first EAS.

[0397] In one possible embodiment, the interface unit 1401 is further configured to receive a second message sent by the second UE, the second message being used to request the discovery of an EAS, the second message carrying information of the second UE, the information of the second UE including location information and / or application information corresponding to the second UE; the processing unit 1402 is configured to determine the second EAS based on the information of the second UE; the interface unit 1401 is further configured to send a second response message corresponding to the second message to the second UE, the second response message carrying first information of the first EAS and first information of the second EAS.

[0398] In one possible embodiment, the second response message also carries second information of the first EAS and second information of the second EAS, the second information including identification and / or address information.

[0399] In one possible embodiment, the interface unit 1401 is further configured to receive second information and / or indication information of the EAS used by the second UE sent by the second UE, wherein the indication information indicates whether the second UE uses the first EAS or indicates whether application context synchronization is required; the EAS used by the second UE is one of the second EAS and the first EAS; if the second EES determines that context synchronization is required between the first EAS and the second EAS based on the information and / or indication information of the EAS used by the second UE, the interface unit 1401 is further configured to send the second information of the second EAS to the first EES.

[0400] In one possible embodiment, if the second EES determines that context synchronization is required between the first EAS and the second EAS based on the information and / or indication information of the EAS selected by the second UE, the interface unit 1401 is further configured to send the second information of the first EAS to the second EAS.

[0401] In one embodiment, when the communication device 1400 is a first EES, wherein:

[0402] Interface unit 1401 is used to send a first message to the second EES. The first message carries the following information: the identifier of the UE group, the first information of the first EAS, and the first information includes one or more of the following: service area, data center information, and performance information; the first EAS is the EAS used by the first UE, and the UE group includes the first UE and the second UE.

[0403] In one possible embodiment, the interface unit 1401 is further configured to receive second information of the second EAS sent by the second EES, the second information including identification and / or address information, the second EAS being an EAS used by the second UE; and to send the second information of the second EAS to the first EAS.

[0404] In one embodiment, when the communication device 1400 is a second UE, wherein:

[0405] Interface unit 1401 is configured to send a second message to the second edge enabling server (EES), the second message being used to request the discovery of an EAS, the second message carrying information about the second UE, the information of the second UE including location information and / or application information corresponding to the second UE; interface unit 1401 is also configured to receive a second response message corresponding to the second message sent by the second EES, the second response message carrying first information of the first EAS, first information of the second EAS, the first information including one or more of the following: service area, corresponding data center information, performance information; the first EAS is the EAS used by the first UE, the UE group includes the first UE and the second UE; processing unit 1402 is configured to determine whether the second UE uses the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS.

[0406] In one possible embodiment, the second response message also carries second information of the first EAS and second information of the second EAS, the second information including identification and / or address information;

[0407] If it is determined that the second UE uses the first EAS, then the interface unit 1401 is also used to communicate with the first EAS based on the second information of the first EAS;

[0408] If it is determined that the second UE uses the second EAS, then the interface unit 1401 is also used to communicate with the second EAS based on the second information of the second EAS.

[0409] In one possible embodiment, the second UE sends second information and / or indication information of the EAS used by the second UE to the second EES. The indication information indicates whether the second UE uses the first EAS or whether application context synchronization is required.

[0410] In one possible embodiment, if it is determined that the second UE uses the second EAS, the second UE sends the second information of the first EAS to the second EAS.

[0411] In one embodiment, when the communication device 1400 is a first EAS, wherein:

[0412] Interface unit 1401 is used to receive second information of the second EAS sent by the first edge enabling server EES. The second information includes identification and / or address information. The first EAS is the EAS used by the first UE, and the second EAS is the EAS used by the second UE. The first UE and the second UE are included in a UE group.

[0413] Interface unit 1401 is also used to synchronize the application context corresponding to the UE group with the second information of the second EAS and the second EAS.

[0414] In one embodiment, when the communication device 1400 is a second UE, wherein:

[0415] Interface unit 1401 is used to send a second message to the second edge enable server (EES). The second message is used to request the discovery of EES. The second message carries information about the second UE, including location information and / or application information corresponding to the second UE.

[0416] Interface unit 1401 is further configured to receive a second response message corresponding to the second message sent by the second EES. The second response message carries second information of the second EAS and second information of the first EAS. The second EAS is the EAS used by the second UE, and the first EAS is the EAS used by the first UE. The first UE and the second UE are included in a UE group. The second information includes identification and / or address information.

[0417] Interface unit 1401 is used to send the second information of the first EAS to the second EAS.

[0418] In one possible embodiment, the second response message also carries indication information that the second EAS needs to synchronize its application context with the first EAS.

[0419] In one embodiment, when the communication device 1400 is a second EAS, wherein:

[0420] Interface unit 1401 is used to receive second information of the first EAS sent by the second edge enabling server EES or the second user equipment UE. The second information includes identification and / or address information. The first EAS is the EAS used by the first UE, and the second EAS is the EAS used by the second UE. The first UE and the second UE are included in a UE group.

[0421] Interface unit 1401 is also used to synchronize the application context corresponding to the UE group with the first EAS based on the second information of the first EAS.

[0422] In one embodiment, when the communication device 1400 is a first EES, wherein:

[0423] Interface unit 1401 is configured to send a first message to the second EES, the first message carrying second information of the first edge application server (EAS), the second information including identification and / or address information, the first EAS being the EAS used by the first UE; interface unit 1401 is configured to receive a second message sent by the second EES, the second message carrying the identification of the second UE and the first information of the second EAS, the first information including one or more of the following: service area, data center information, performance information; processing unit 1402 is configured to determine whether the second UE uses the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS, the first UE and the second UE being included in the same UE group.

[0424] In one possible embodiment, the second message also carries information about the second UE, which includes location information and / or application information corresponding to the second UE; the processing unit 1402 determines whether the second UE uses the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS, including: the processing unit 1402 determines whether the second UE uses the first EAS or the second EAS based on the information of the second UE, the first information of the first EAS and the first information of the second EAS.

[0425] In one possible embodiment, the second message also carries second information of the second EAS; the interface unit 1401 is further configured to send a second response message corresponding to the second message to the second EES; the second response message carries the identifier of the second UE and the second information of the EAS used by the second UE.

[0426] In one possible embodiment, if it is determined that the second UE uses the second EAS, the interface unit 1401 is further configured to send the second information of the second EAS to the first EAS.

[0427] In one possible embodiment, if it is determined that the second UE uses the second EAS, the second response message also carries indication information indicating that the second EAS needs to synchronize its application context with the public EAS.

[0428] In one embodiment, when the communication device 1400 is a second EES, wherein:

[0429] Interface unit 1401 is configured to receive a first message sent by a first EES, the first message carrying second information of a first edge application server (EAS), the second information including identification and / or address information, the first EAS being an EAS used by a first UE; interface unit 1401 is also configured to receive a third message sent by a second UE, the third message being used to request the discovery of an EAS, the second message carrying information of the second UE, the second UE information including location information and / or application information corresponding to the second UE; the first UE and the second UE are included in the same UE group; processing unit 1402 is configured to determine a second EAS based on the information of the second UE; interface unit 1401 is also configured to send a second message to the first EES, the second message carrying the identification of the second UE and the first information of the second EAS, the first information including one or more of the following: service area, data center information, performance information, the first information of the second EAS being used to determine whether the second UE uses the first EAS or the second EAS.

[0430] In one possible embodiment, the second message also carries information about the second UE, which includes location information and / or application information corresponding to the second UE.

[0431] In one possible embodiment, the second message also carries second information of the second EAS; the interface unit 1401 is further configured to receive a second response message corresponding to the second message sent by the first EES, the second response message carrying the identifier of the second UE and the second information of the EAS used by the second UE, the EAS used by the second UE being either the second EAS or the first EAS; the interface unit 1401 is further configured to send a fourth message to the second UE, the fourth message carrying the second information of the EAS used by the second UE.

[0432] In one possible embodiment, the EAS used by the second UE is the second EAS, and the interface unit 1401 is also used to send the second information of the first EAS to the second EAS.

[0433] In one possible embodiment, the EAS used by the second UE is the second EAS, and the fourth message also carries the second information of the first EAS.

[0434] In one possible embodiment, the fourth message also carries an indication that the second EAS needs to synchronize its application context with the first EAS.

[0435] In one possible embodiment, the second response message also carries indication information that the second EAS needs to synchronize its application context with the first EAS.

[0436] In one embodiment, when the communication device 1400 is a second UE, wherein:

[0437] Interface unit 1401 is configured to send a third message to the second EES, the third message being used to request the discovery of an EAS, and the second message carrying information about the second UE, including location information and / or application information corresponding to the second UE; interface unit 1401 is also configured to receive a fourth message sent by the second EES, the fourth message carrying second information of the EAS used by the second UE and second information of the first EAS, the second information including identification and / or address information; the EAS used by the second UE is the second EAS; the first EAS is the EAS used by the first UE; the first UE and the second UE are contained in the same UE group; the second UE sends the second information of the first EAS to the second EAS.

[0438] In one possible embodiment, the fourth message also carries an instruction that indicates that the second EAS needs to synchronize its application context with the first EAS.

[0439] like Figure 15 The illustration shows a communication device 1500 provided in an embodiment of this application, used to implement the functions of the aforementioned second EES, first EES, second UE, first EAS, or second EAS. This device can be a communication device or a device used within a communication device. The communication device can be a second EES, first EES, second UE, first EAS, or second EAS. The device used within the communication device can be a chip system or a chip within the communication device. The chip system can be composed of chips or can include chips and other discrete components.

[0440] The communication device 1500 includes at least one processor 1510 for implementing the processing functions of the device (e.g., a second EES, a first EES, a second UE, a first EAS, or a second EAS) in the methods provided in this application embodiment. The communication device 1500 may also include a communication interface 1520 for implementing the transmit and receive operations of the device (e.g., a second EES, a first EES, a second UE, a first EAS, or a second EAS) in the methods provided in this application embodiment. In this application embodiment, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface for communicating with other devices via a transmission medium. For example, the communication interface 1520 enables the device in the communication device 1500 to communicate with other devices. The processor 1510 uses the communication interface 1520 to transmit and receive data and is used to implement the methods described in the above method embodiments.

[0441] The communication device 1500 may further include at least one memory 1530 for storing program instructions and / or data. The memory 1530 is coupled to the processor 1510. The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, and may be electrical, mechanical, or other forms, for information exchange between devices, units, or modules. The processor 1510 may operate in conjunction with the memory 1530. The processor 1510 may execute program instructions stored in the memory 1530. At least one of the at least one memory may be included in the processor.

[0442] This application embodiment does not limit the specific connection medium between the communication interface 1520, processor 1510, and memory 1530. This application embodiment... Figure 15 The memory 1530, processor 1510, and communication interface 1520 are connected via a bus, and the bus is in... Figure 15 The connections between other components are shown in bold and are for illustrative purposes only, not as limiting information. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 15 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0443] When the communication device 1500 is specifically used for a device (e.g., a second EES, a first EES, a second UE, a first EAS, or a second EAS), for example, when the communication device 1500 is specifically a chip or a chip system, the communication interface 1520 can output or receive baseband signals. When the communication device 1500 is specifically a device (e.g., a second EES, a first EES, a second UE, a first EAS, or a second EAS), the communication interface 1520 can output or receive radio frequency signals. In the embodiments of this application, the processor can 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, or a discrete hardware component, capable of implementing or executing the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules in the processor.

[0444] It should be noted that the aforementioned communication interface 1520 can be used to execute the functions of the aforementioned interface unit 1401, and the aforementioned processor 1510 can be used to execute the functions of the aforementioned processing unit 1402, which will not be elaborated further here.

[0445] When the aforementioned communication device is a chip applied to the second EES, the first EES, the second UE, the first EAS, or the second EAS, the chip implements the functions of the second EES, the first EES, the second UE, the first EAS, or the second EAS in the above method embodiments. The chip receives information from other network elements; or, the chip sends information to other network elements.

[0446] It is understood that the processor in the embodiments of this application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0447] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Furthermore, the ASIC can reside in a core network device or terminal. Alternatively, the processor and storage medium can exist as discrete components in a terminal or access network device.

[0448] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer program or instructions can be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a DVD; or it can be a semiconductor medium, such as a solid-state disk (SSD).

[0449] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0450] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

[0451] This application also provides a computer-readable storage medium storing computer-executable instructions. When the computer-executable instructions are executed, the method executed by the terminal or access network device in the above method embodiments is implemented.

[0452] This application also provides a computer program product, which includes a computer program that, when executed, causes the method executed by the terminal or access network device in the above method embodiments to be implemented.

[0453] This application also provides a communication system, which includes a terminal or an access network device. The terminal is used to execute the method described in the above method embodiments. The access network device is used to execute the method described in the above method embodiments.

[0454] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0455] The descriptions of the various embodiments provided in this application can be referenced mutually. Each embodiment has its own emphasis, and parts not described in detail in a certain embodiment can be referred to the relevant descriptions of other embodiments. For the sake of convenience and brevity, for example, the functions and execution steps of the various devices and equipment provided in the embodiments of this application can be referred to the relevant descriptions of the method embodiments of this application. The method embodiments and the device embodiments can also be referenced, combined or cited from each other.

[0456] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A communication method for edge computing, characterized in that, The method includes: The second edge enabling server (EES) receives a first message sent by the first EES. The first message carries the following information: the identifier of the UE group, and the first information of the first edge application server (EAS). The first information includes one or more of the following: service area, data center information, and performance information. The first EAS is the EAS used by the first UE. The UE group includes the first UE and the second UE. The first EES is the EES connected to the first UE, and the second EES is the EES connected to the second UE. The second EES receives a second message sent by the second UE. The second message is used to request the discovery of the EES. The second message carries information about the second UE, including location information and / or application information corresponding to the second UE. The second EES determines whether the second UE uses the first EAS based on the information of the second UE and the first information of the first EAS.

2. The method according to claim 1, characterized in that, The second EES determines whether the second UE uses the first EAS based on the information of the second UE and the first information of the first EAS, including: The second EES determines the second EAS based on the information of the second UE; The second EES determines whether the second UE uses the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS.

3. The method according to claim 2, characterized in that, The first message also carries second information about the first EAS, the second information including identification and / or address information, and the method further includes: The second EES sends a second response message corresponding to the second message to the second UE; If it is determined that the second UE is using the first EAS, then the second response message carries the second information of the first EAS; If it is determined that the second UE uses the second EAS, then the second response message carries the second information of the second EAS.

4. The method according to claim 3, characterized in that, The method further includes: If it is determined that the second UE is using the second EAS, then the second EES sends the second information of the first EAS to the second EAS; If it is determined that the second UE uses the second EAS, then the second EES sends the second information of the second EAS to the first EES.

5. The method according to claim 3, characterized in that, If it is determined that the second UE uses the second EAS, the second response message also carries the second information of the first EAS; the method further includes: If it is determined that the second UE uses the second EAS, then the second EES sends the second information of the second EAS to the first EES.

6. The method according to claim 5, characterized in that, If it is determined that the second UE is using the second EAS, the second response message also carries indication information, which indicates that the second EAS needs to synchronize the application context with the first EAS.

7. A communication method for edge computing, characterized in that, The method includes: The second edge enabling server (EES) receives a first message sent by the first EES. The first message carries the following information: the identifier of the UE group, and the first information of the first edge application server (EAS). The first information includes one or more of the following: service area, data center information, and performance information. The first EAS is the EAS used by the first UE. The UE group includes the first UE and the second UE. The first EES is the EES connected to the first UE, and the second EES is the EES connected to the second UE. The second EES receives a second message sent by the second UE. The second message is used to request the discovery of the EES. The second message carries information about the second UE, including location information and / or application information corresponding to the second UE. The second EES determines the second EAS based on the information of the second UE; The second EES sends a second response message corresponding to the second message to the second UE. The second response message carries the first information of the first EAS and the first information of the second EAS. The first information of the first EAS and the first information of the second EAS are used to determine the EAS used by the second UE.

8. The method according to claim 7, characterized in that, The second response message also carries second information of the first EAS and second information of the second EAS, the second information including identification and / or address information.

9. The method according to claim 8, characterized in that, The method further includes: The second EES receives second information and / or indication information from the second UE regarding the EAS used by the second UE. The indication information indicates whether the second UE uses the first EAS or whether application context synchronization is required. The EAS used by the second UE is either the second EAS or the first EAS. If the second EES determines, based on the information and / or indication information of the EAS used by the second UE, that context synchronization is required between the first EAS and the second EAS, then the second EES sends the second information of the second EAS to the first EES.

10. The method according to claim 9, characterized in that, The method further includes: If the second EES determines, based on the information and / or indication information of the EAS selected by the second UE, that context synchronization is required between the first EAS and the second EAS, then the second EES sends the second information of the first EAS to the second EAS.

11. A communication method for edge computing, characterized in that, The method includes: The first edge enabling server (EES) sends a first message to the second EES. The first message carries the following information: the identifier of the UE group, and the first information of the first EAS. The first information includes one or more of the following: service area, data center information, and performance information. The first EAS is the EAS used by the first UE. The UE group includes the first UE and the second UE. The first EES is the EES connected to the first UE, and the second EES is the EES connected to the second UE. The first information of the first EAS is used by the second EES to determine whether the second UE uses the first EAS in combination with the information of the second UE. The information of the second UE includes location information and / or application information corresponding to the second UE.

12. The method according to claim 11, characterized in that, The method further includes: The first EES receives second information of the second EAS sent by the second EES. The second information includes identification and / or address information. The second EAS is the EAS used by the second UE. The first EES sends the second information of the second EAS to the first EAS.

13. A method for discovering Edge Application Servers (EAS), characterized in that, The method includes: The second user equipment (UE) sends a second message to the second edge enable server (EES). The second message is used to request the discovery of the EAS. The second message carries information about the second UE, including location information and / or application information corresponding to the second UE. The second UE receives a second response message corresponding to the second message sent by the second EES. The second response message carries first information of the first EAS and first information of the second EAS. The first information includes one or more of the following: service area, corresponding data center information, and performance information. The first EAS is the EAS used by the first UE, and the UE group includes the first UE and the second UE. The second UE determines whether to use the first EAS or the second EAS based on the first information of the first EAS and the first information of the second EAS.

14. The method according to claim 13, characterized in that, The second response message also carries second information of the first EAS and second information of the second EAS, the second information including identification and / or address information; the method further includes: If it is determined that the second UE uses the first EAS, then the second UE communicates with the first EAS based on the second information of the first EAS; If it is determined that the second UE uses the second EAS, then the second UE communicates with the second EAS based on the second information of the second EAS.

15. The method according to claim 14, characterized in that, The method further includes: The second UE sends second information and / or indication information of the EAS used by the second UE to the second EES. The indication information indicates whether the second UE uses the first EAS or whether application context synchronization is required.

16. The method according to claim 15, characterized in that, The method further includes: If it is determined that the second UE is using the second EAS, then the second UE sends the second information of the first EAS to the second EAS.

17. A communication device, characterized in that, Includes units for performing the method as described in any one of claims 1 to 16.

18. A communication device, characterized in that, It includes a processor and a memory, the processor and the memory being coupled, the processor being used to implement the method as described in any one of claims 1 to 16.

19. A chip, characterized in that, It includes a processor and an interface, the processor and the interface being coupled; the interface is used to receive or output signals, and the processor is used to execute code instructions to cause the method of any one of claims 1 to 16 to be performed.

20. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when invoked by the computer, cause the computer to perform the method described in any one of claims 1-16.

Images