Communication method and communication apparatus using edge computing
The second EES determines that the second UE is connected to a better EAS based on the information of the first EAS used by the first UE, which solves the problem that the UE cannot obtain better application services, and achieves better service performance and data consistency.
Patent Information
- Application Number
- PCT/CN2024/121545
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-09-28
- Filing Date
- 2024-09-26
- Publication Date
- 2025-04-03
AI Technical Summary
In the prior art, when UE discovers an edge application server (EAS), it may not be able to obtain better application services, resulting in poor service performance.
The second edge enable server (EES) receives a message sent by the first EES, including the identification of the UE group and the information of the first EAS, to determine whether the second UE uses the first EAS. The second EES determines that the second UE connects to a better EAS to obtain application services based on the service area, data center information and performance information of the first EAS used by the first UE.
The second UE is connected to a better EAS, thereby obtaining better application services, improving service performance, and ensuring consistency of data within the UE group through application context synchronization.
Smart Images

Figure CN2024121545_03042025_PF_FP_ABST
Abstract
Description
Communication method and communication device for edge computing
[0001] This application claims priority to the Chinese patent application with application number 202311283557.6 filed with the State Intellectual Property Office of China on September 28, 2023, and priority to the Chinese patent application with the invention name “A communication method and communication device for edge computing”, all contents of which are incorporated by reference into this application. Technical Field
[0002] The present application relates to the field of communication technology, and in particular to a communication method and communication device for edge computing. Background Art
[0003] 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 is registered with an EES, or an EAS's information is configured on an EES through a management system. This EES is called the EES associated with the EAS. The EES controls / manages the EASs registered / configured on it.
[0004] The UE needs to discover EAS first before it can establish a connection with EAS to obtain application services. The EAS discovered for the UE through the existing EAS discovery process may not enable the UE to obtain better application services.
[0005] Summary of the Invention
[0006] The present application provides an edge computing communication method and communication device, which is conducive to enabling UE to obtain better application services.
[0007] In the first aspect, the present application provides a communication method for edge computing, which can be performed by a second EES, or by a module (such as a processor, chip, or chip system) applied to the second EES, or by a logical node, logical module, or software that can implement all or part of the second EES function. The method includes:
[0008] The second edge enabling server EES receives the first message sent by the first EES, which carries the following information: the identifier of the UE group, the first information of the first edge application server EAS, the first information including one or more of the following: service area, data center information, 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.
[0009] It can be seen that 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, which is sent by the first EES. In this way, the second EES can determine whether the 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, rather than directly determining the first EAS used by the first UE as the EAS used by the second UE. This helps the second UE connect to a better EAS to obtain application services, thereby obtaining better application services.
[0010] In a possible embodiment, the method also includes: the second EES receives a second message sent by the second UE, the second message is used to request discovery of the EAS, the second message carries information of the second UE, the information of the second UE includes 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.
[0011] Based on this possible embodiment, the second 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, 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 more optimal EAS to obtain application services, thereby obtaining better application services.
[0012] In a possible embodiment, the specific implementation method 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: 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.
[0013] Based on this possible embodiment, it is helpful for the second UE to connect to a better EAS to obtain application services, so as to obtain better application services.
[0014] In a 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, including: 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 delay 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 delay information or response time information between the first EAS / first EES and the second EAS / second EES.
[0015] Optionally, 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 may be preconfigured in the second EES and / or preconfigured in the first EES. Optionally, the latency information or response time information between the first EAS / first EES and the second EAS / second EES may be preconfigured in the second EES and / or preconfigured in the first EES.
[0016] In a possible embodiment, the first message also carries second information of the first EAS, and the second information of the first EAS includes the identifier of the first EAS and / or the address information of the first EAS. The method also 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 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 second information of the second 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.
[0017] 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 used by the second UE.
[0018] In a possible embodiment, 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 first EAS to the second EAS; 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 embodiment, if the second UE uses the second EAS, the second EAS and the first EAS may perform application context synchronization to ensure data consistency between different UEs in the same UE group, thereby allowing services of the UEs in the UE group to proceed normally.
[0020] In a 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 also 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.
[0021] Based on this possible embodiment, if the second UE uses the second EAS, the second EAS and the first EAS can synchronize application contexts to ensure data consistency between different UEs in the same UE group, thereby allowing services for the UEs in the UE group to proceed normally. Furthermore, by also including the second information of the first EAS in the second response message, the second information of the first EAS can be sent to the second EAS via the application layer of the second UE.
[0022] In a possible embodiment, if it is determined that the second UE uses the second EAS, the second response message further carries indication information, where the indication information indicates that the second EAS needs to synchronize application context with the first EAS.
[0023] In a possible embodiment, the method also includes: the second EES receives a second message sent by the second UE, the second message is used to request the discovery of the EAS, the second message carries information of the second UE, the information of the second UE includes 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.
[0024] Based on this possible embodiment, the second UE can determine whether to use 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 helps the second UE connect to a more optimal EAS to obtain application services, thereby obtaining better application services.
[0025] In a possible embodiment, the second response message may also carry the delay 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 delay information or response time information between the first EAS / first EES and the second EAS / second EES.
[0026] In a possible embodiment, the second response message also carries the second information of the first EAS and the 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.
[0027] 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 used by the second UE.
[0028] In a possible embodiment, the method further includes: receiving, by the second EES, second information and / or indication information of an EAS used by the second UE, sent by the second UE, the indication information indicating whether the second UE uses the first EAS or whether application context synchronization is required; the EAS used by the second UE is one of the second EAS and the first EAS;
[0029] If the second EES determines that context synchronization needs to be performed 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 second EES sends second information of the second EAS to the first EES.
[0030] Based on this possible embodiment, if the second UE uses the second EAS, the second EAS and the first EAS may perform application context synchronization to ensure data consistency between different UEs in the same UE group, thereby allowing services of the UEs in the UE group to proceed normally.
[0031] In a possible embodiment, the method further includes: 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 second EES sends second information of the first EAS to the second EAS.
[0032] Based on this possible embodiment, if the second UE uses the second EAS, the second EAS and the first EAS may perform application context synchronization to ensure data consistency between different UEs in the same UE group, thereby allowing services of the UEs in the UE group to proceed normally.
[0033] In a second aspect, the present application provides a communication method for edge computing, which can be performed by a first EES, or by a module (such as a processor, chip, or chip system) applied to the first EES, or by a logical node, logical module, or software that can implement all or part of the functions of the first EES. The method includes:
[0034] The first edge enabling server EES sends a first message to the second EES, which 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.
[0035] In a possible embodiment, the method further includes: the first EES receives second information of the second EAS sent by the second EES, the second information of the second EAS includes an identifier of the second EAS and / or address information of the second EAS, and the second EAS is the EAS used by the second UE; and the first EES sends the second information of the second EAS to the first EAS.
[0036] In a third aspect, the present application provides a communication method for edge computing, which can be performed by a second UE, or by a module (such as a processor, chip, or chip system) applied to the second UE, or by a logical node, logical module, or software that can implement all or part of the second UE function. The method includes:
[0037] The second user equipment UE sends a second message to the second edge enabling server EES, where the second message is used to request discovery of the EAS. The second message carries information of the second UE, where the information of the second UE includes 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, where the second response message carries first information of the first EAS and first information of the second EAS, where 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 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.
[0038] Optionally, the second response message may also carry the delay 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 delay information or response time information between the first EAS / first EES and the second EAS / second EES. The second UE 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 second UE determines whether to use the first EAS or the second EAS based on the delay 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 delay 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.
[0039] Optionally, 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 may be preconfigured in the second EES and / or preconfigured in the first EES. Optionally, the latency information or response time information between the first EAS / first EES and the second EAS / second EES may be preconfigured in the second EES and / or preconfigured in the first EES.
[0040] In a possible embodiment, the second response message also carries the second information of the first EAS and the 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 also includes: 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.
[0041] In a 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, where the indication information indicates whether the second UE uses the first EAS or whether application context synchronization is required.
[0042] In a possible embodiment, the method further includes: if it is determined that the second UE uses the second EAS, the second UE sending second information of the first EAS to the second EAS.
[0043] In a fourth aspect, the present application provides an edge computing communication method, which can be executed by a first EAS, or by a module (such as a processor, chip, or chip system) applied to the first EAS, or by a logical node, logical module, or software that can implement all or part of the first EAS function. The method includes:
[0044] The first edge application server EAS receives the second information of the second EAS sent by the first edge enabling server EES, where the second information of the second EAS includes the identifier of the second EAS and / or the 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 the 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.
[0045] In a fifth aspect, the present application provides a communication method for edge computing, which can be executed by a second UE, or by a module applied to the second UE (such as a processor, chip, or chip system, etc.), or by a logical node, logical module, or software that can implement all or part of the second UE function. The method includes:
[0046] The second user equipment UE sends a second message to the second edge enabling server EES, where the second message is used to request the discovery of EAS. The second message carries information of the second UE, where the information of the second UE includes 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, where 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 the UE group; the second information of the first EAS includes the identifier of the first EAS and / or the address information of the first EAS; the information of the second EAS includes the identifier of the second EAS and / or the address information of the second EAS; the second UE sends the second information of the first EAS to the second EAS.
[0047] In a possible embodiment, the second response message further carries indication information, where the indication information indicates that the second EAS needs to synchronize application context with the first EAS.
[0048] In a sixth aspect, the present application provides an edge computing communication method, which can be executed by a second EAS, or by a module (such as a processor, chip, or chip system) applied to the second EAS, or by a logical node, logical module, or software that can implement all or part of the second EAS function. The method includes:
[0049] The second edge application server EAS receives the information of the first EAS sent by the second edge enabling server EES or the second user equipment UE, where the information of the first EAS includes the identifier of the first EAS and / or the 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 the 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.
[0050] The beneficial effects of the second to sixth aspects can be found in the beneficial effects of the first aspect and will not be repeated here.
[0051] In a seventh aspect, the present application provides a communication method for edge computing, which can be performed by a first EES, or by a module (such as a processor, chip, or chip system) applied to the first EES, or by a logical node, logical module, or software that can implement all or part of the functions of the first EES. The method includes:
[0052] The first edge enabling server EES sends a first message to the second EES, where the first message carries second information of the first edge application server EAS, where the second information includes identification and / or address information, and the first EAS is the EAS used by the first UE; the first EES receives a second message sent by the second EES, where the second message carries the identification of the second UE and first information of the second EAS, where the first information includes one or more of the following: service area, data center information, and 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, and the first UE and the second UE are included in the same UE group.
[0053] It can be seen that based on the method described in the seventh aspect, the first EES can determine whether the 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 helps the second UE connect to a better EAS to obtain application services, so as to obtain better application services.
[0054] In a possible embodiment, the second message also carries information of the second UE, and the information of the second UE 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.
[0055] Based on this possible embodiment, it is helpful for the second UE to connect to a better EAS to obtain application services, so as to obtain better application services.
[0056] In a 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 delay 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 delay 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.
[0057] Optionally, 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 may be pre-configured in the first EES. Optionally, the latency information or response time information between the first EAS / first EES and the second EAS / second EES may be pre-configured in the first EES.
[0058] Optionally, 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. Optionally, 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 may be preconfigured in the second EES. Optionally, the latency information or response time information between the first EAS / first EES and the second EAS / second EES may be preconfigured in the second EES.
[0059] In a possible embodiment, the second message also carries second information of the second EAS; the method also includes: the first EES sends 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.
[0060] 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 used by the second UE.
[0061] In a possible embodiment, the method further includes: if it is determined that the second UE uses the second EAS, the first EES sending second information of the second EAS to the first EAS.
[0062] Based on this possible embodiment, if the second UE uses the second EAS, the second EAS and the first EAS may perform application context synchronization to ensure data consistency between different UEs in the same UE group, thereby allowing services of the UEs in the UE group to proceed normally.
[0063] In a possible embodiment, if it is determined that the second UE uses the second EAS, the second response message further carries indication information, where the indication information indicates that the second EAS needs to synchronize application context with the public EAS.
[0064] In an eighth aspect, the present application provides a communication method for edge computing, which can be performed by a second EES, or by a module (such as a processor, chip, or chip system) applied to the second EES, or by a logical node, logical module, or software that can implement all or part of the functions of the second EES. The method includes:
[0065] The second edge enabling server EES receives a first message sent by the first EES, the first message carries second information of the first edge application server EAS, the second information includes identification and / or address information, and the first EAS is the EAS used by the first UE; the second EES receives a third message sent by the second UE, the third message is used to request discovery of the EAS, the second message carries information of the second UE, the information of the second UE includes 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, and the first information includes one or more of the following: service area, data center information, and performance information.
[0066] In a possible embodiment, the second message further carries information of the second UE, where the information of the second UE includes location information and / or application information corresponding to the second UE.
[0067] In a possible embodiment, the second message may also carry delay 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 delay information or response time information between the first EAS / first EES and the second EAS / second EES.
[0068] Optionally, 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 may be preconfigured in the second EES. Optionally, the latency information or response time information between the first EAS / first EES and the second EAS / second EES may be preconfigured in the second EES.
[0069] In a possible embodiment, the second message further carries second information of a second EAS; and the method further includes:
[0070] 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 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.
[0071] In a possible embodiment, the EAS used by the second UE is a second EAS, and the method further includes: the second EAS sending second information of the first EAS to the second EAS.
[0072] In a possible embodiment, the EAS used by the second UE is the second EAS, and the fourth message further carries second information of the first EAS.
[0073] In a possible embodiment, the fourth message further carries indication information, where the indication information indicates that the second EAS needs to synchronize application context with the first EAS.
[0074] In a possible embodiment, the second response message further carries indication information, where the indication information indicates that the second EAS needs to synchronize application context with the first EAS.
[0075] In a ninth aspect, the present application provides a communication method for edge computing, which can be performed by a second UE, or by a module (such as a processor, chip, or chip system) applied to the second UE, or by a logical node, logical module, or software that can implement all or part of the second UE function. The method includes:
[0076] The second UE sends a third message to the second EES, where the third message is used to request discovery of the EAS. The second message carries information of the second UE, where the information of the second UE includes location information and / or application information corresponding to the second UE. The second UE receives a fourth message sent by the second EES, where the fourth message carries second information of the EAS used by the second UE and second information of the first EAS, where 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.
[0077] In a possible embodiment, the fourth message further carries indication information, where the indication information indicates that the second EAS needs to synchronize application context with the first EAS.
[0078] The beneficial effects of the eighth to ninth aspects can be found in the beneficial effects of the seventh aspect and will not be described in detail here.
[0079] In the tenth aspect, the present application provides a communication device, for example, the communication device can be a first EES or a module applied to the first EES 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 EES.
[0080] For another example, the communication device may be a second EES or a module applied to the second EES, such as a processor, a chip, or a chip system, or a logical node, a logical module, or software that can implement all or part of the functions of the second EES.
[0081] For example, the communication device may be a second UE or a module applied to the second UE, such as a processor, a chip, or a chip system, or may be a logical node, a logical module, or software that can implement all or part of the functions of the second UE.
[0082] For another example, the communication device may be the first EAS or a module applied to the first EAS, such as a processor, a chip, or a chip system, or may be a logical node, a logical module, or software that can implement all or part of the first EAS functions.
[0083] For another example, the communication device may be a second EAS or a module applied to the second EAS, such as a processor, a chip, or a chip system, or may be a logical node, a logical module, or software that can implement all or part of the second EAS functions.
[0084] The communication device includes a module / unit for executing any one of the methods in the first aspect to the ninth aspect and possible implementations thereof.
[0085] In the eleventh aspect, the present application provides a communication device, including a processor, the processor and a memory are coupled, the memory is used to store programs or instructions, when the program or instructions are executed by the processor, the device executes the method described in any one of the above-mentioned aspects 1 to 9.
[0086] In the twelfth aspect, the present application provides a chip, which includes a processor and an interface, and the processor and the interface are coupled; the interface is used to receive or output signals, and the processor is used to execute code instructions, so that the chip executes the method described in any one of the above-mentioned aspects 1 to 9.
[0087] In a thirteenth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are called, any one of the above-mentioned first to ninth aspects is executed.
[0088] In a fourteenth aspect, the present application provides a computer program product, comprising: a computer program code, wherein when the computer program code is executed, any one of the above-mentioned first to ninth aspects is executed.
[0089] In the fifteenth aspect, the present application provides a communication system, which includes a second EES for executing the method described in the first aspect and a first EES for executing the second aspect, a first EAS for executing the fourth aspect, and a second EAS for executing the sixth aspect.
[0090] Alternatively, the communication system includes a second EES for executing the method described in the first aspect above and a first EES for executing the method described in the second aspect above, a first EAS for executing the method described in the fourth aspect above, a second UE for executing the method described in the fifth aspect above, and a second EAS for executing the method described in the sixth aspect above.
[0091] Alternatively, the communication system includes a first EES for executing the method described in the first aspect above and a first EES for executing the method described in the eighth aspect above, a second UE for executing the method described in the third aspect above, a first EAS for executing the method described in the fourth aspect above, and a second EAS for executing the method described in the sixth aspect above.
[0092] Alternatively, the communication system includes a first EES for executing the method described in the seventh aspect, a second EES for executing the method described in the eighth aspect, a first EAS for executing the method described in the fourth aspect, and a second EAS for executing the method described in the sixth aspect.
[0093] Alternatively, the communication system includes a first EES for executing the method described in the seventh aspect and a second EES for executing the method described in the eighth aspect, a first EAS for executing the method described in the fourth aspect, a second EAS for executing the method described in the sixth aspect, and a second UE for executing the method described in the ninth aspect. BRIEF DESCRIPTION OF THE DRAWINGS
[0094] FIG1 is a schematic diagram of a system architecture provided by this application;
[0095] FIG2 is a schematic diagram of a UE group connected to an EAS provided by the present application;
[0096] FIG3 is a schematic diagram of another UE group connected to EAS provided by the present application;
[0097] FIG4 is a flow chart of an edge computing communication method provided by the present application;
[0098] FIG5 is a flow chart of an edge computing communication method provided by the present application;
[0099] FIG6 is a flow chart of an edge computing communication method provided by the present application;
[0100] FIG7 is a flow chart of an edge computing communication method provided by the present application;
[0101] FIG8 is a flow chart of an edge computing communication method provided by the present application;
[0102] FIG9 is a flow chart of an edge computing communication method provided by the present application;
[0103] FIG10 is a flow chart of an edge computing communication method provided by the present application;
[0104] FIG11 is a flow chart of an edge computing communication method provided by the present application;
[0105] FIG12 is a flow chart of an edge computing communication method provided by the present application;
[0106] FIG13 is a flow chart of an edge computing communication method provided by the present application;
[0107] FIG14 is a schematic structural diagram of a communication device provided by the present application;
[0108] FIG15 is a schematic structural diagram of another communication device provided in this application. DETAILED DESCRIPTION
[0109] The specific embodiments of the present application are further described in detail below with reference to the accompanying drawings.
[0110] The terms "first" and "second" and the like in the specification, claims, and drawings of this application are used to distinguish between different objects, not to describe a particular order. Furthermore, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or elements is not limited to the listed steps or elements, but may optionally include steps or elements not listed, or may optionally include other steps or elements inherent to the process, method, product, or apparatus.
[0111] References herein to "embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.
[0112] In this application, "at least one (item)" refers to one or more, "more than one" refers to two or more, "at least two (items)" refers to two or three and more than three, and "and / or" is used to describe the association relationship of associated 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 at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b 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, c can be single or multiple.
[0113] In order to enable UE to obtain better application services, the embodiment of the present application provides a communication method and communication device for edge computing. In order to better understand the embodiment of the present application, the system architecture involved in the embodiment of the present application is first introduced below:
[0114] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: global system of mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, fifth generation (5G) system or new radio (NR) and future communication systems.
[0115] Please refer to Figure 1, which is a schematic diagram of a system architecture provided by an embodiment of the present application. As shown in Figure 1, the system architecture includes user equipment (UE), a third generation partnership project core network (3GPP CN), an edge data network (EDN) and an edge configuration server (ECS). Among them, 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).
[0116] 1. User Equipment
[0117] 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 the water (such as a ship, etc.); it can also be deployed in the air (such as an airplane, balloon and satellite, etc.). The user equipment can be a mobile phone, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) user equipment, an augmented reality (AR) user equipment, a wireless terminal in industrial control, a vehicle-mounted user equipment, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a wearable user equipment, etc. The embodiments of the present 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 device, UE agent, or UE device. User equipment may also be fixed or mobile. In this application, UE is used to refer to user equipment.
[0118] 2. EDN
[0119] A common understanding is that an EDN corresponds to a data network, a special local data network (local DN) that includes edge-enabling functions and can be identified using a data network access identifier (DNAI) and a data network name (DNN). It is a network logical concept. Another understanding of EDN is that EDN is a peer-to-peer concept of the central cloud, which can be understood as a local data center (geographical concept), which can be identified using a DNAI and can include multiple local data networks (local DNs).
[0120] 2. EAS
[0121] An application deployed in an edge data network is called an application instance. EAS can also be referred to as an edge application (server), application instance, edge application instance, MEC application (server), EAS function, etc. Specifically, it refers to an instance of a server application (for example, social media software, augmented reality (AR), virtual reality (VR)) deployed and running on an EDN. An application can deploy one or more EASs in one or more EDNs. EASs deployed and running in different EDNs can be considered different EASs of the same application. They can share a domain name, use a single IP address, or use different IP addresses.
[0122] AC
[0123] The AC is the UE-side counterpart of the EAS. It allows users to access application services from the EAS. The AC is a client application running on the terminal. It can connect to the EAS in the cloud or to an EAS deployed and running in one or more EDNs.
[0124] 4. EES
[0125] It can provide some enabling capabilities for the EAS deployed in the EDN, which can better support the deployment of applications in the MEC. It can support the registration of edge applications, authentication and authorization of UEs, and provide the UE with the IP address information of the EAS. It can also further support the acquisition of the EAS identification and IP address information, and further send the EAS identification and IP address information to the ECS. The EES is deployed in the EDN. Generally, the EAS is registered with an EES, or the information of an EAS 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 the EES.
[0126] 5. EEC
[0127] The EES is the UE-side counterpart of the EES. The EEC is used to register EEC and AC information with the EES, perform security authentication and authorization, obtain the EAS IP address from the EES, and provide edge computing capabilities to the AC. For example, the EAS discovery service returns the EAS IP address to the AC.
[0128] 6. ECS
[0129] Responsible for EDN configuration, such as providing EES information to the UE. It can also directly provide EAS information to the UE and interact with the application's DNS to obtain EAS information. It further obtains and stores EAS and IP address information from other functional entities.
[0130] To facilitate understanding of the solutions provided by the embodiments of this application, some professional terms involved in this application are introduced below:
[0131] 1. EAS Discovery Service
[0132] Application users sign a service agreement with the application provider, which provides services to the application users. Application users log in to the AC on their terminals and communicate through the connection between the AC and the EAS. The EEC is a middleware layer, generally located in the operating system or between the AC and the operating system. The AC can obtain edge-enabling services from the EEC in the form of an application programming interface (API). For example, edge-enabling services may include EAS discovery services.
[0133] The 3GPP SA6 standard defines the EES platform discovery and EAS discovery processes, which provide EES platform discovery and EAS discovery. The architecture and functionality are designed to use a two-level discovery mechanism: first, discover the EES platform, and then discover the EAS from the EES platform. For example, the EEC can send a request to the EES to discover the EAS. After receiving the request, the EES matches the EAS that meets the user's request based on the information of the locally registered / online EAS and the discovery filter parameters provided by the user. The EES returns the EAS information to the EEC. The EEC can then provide it to the AC for the AC to connect to the EAS.
[0134] 2. A UE group connected to EAS
[0135] A UE group is a group of UEs that use the same application. For example, multiple users team up to play a game, and the UEs of these multiple users can form a UE group.
[0136] There are two situations in which a UE group is connected to EAS:
[0137] Case 1: A group of UEs can be connected to the same EAS to reduce signaling interactions between EASs. For example, as shown in Figure 2, EAS1 through EAS3 are different instances of the same application. UE1 through UE3 are UEs in the same UE group. UE1 through UE3 are all connected to EAS2. This avoids synchronizing the UE group's application context between different EASs, thereby reducing EAS context synchronization overhead. Furthermore, since a UE is connected to the same EAS, fairness is ensured for the group of UEs.
[0138] Scenario 2: A group of UEs can connect to different EASs. Each UE can connect to a closer EAS to achieve better service performance, such as the EAS that is available. In this case, EASs must synchronize application contexts to ensure normal service for UEs in the group. For example, as shown in Figure 3, EAS1 through EAS3 are different application instances of the same application. EAS1-EAS3 share the same EASID / EAS domain name, but are different EAS instances. This means that EAS1-EAS3 have different address information, such as the EAS server address and EAS IP address. The same application can be understood as having a one-to-one correspondence between the EASID and ACID, and the application services provided by the EAS and AC are the same. Considering different operating systems, the application ID in the EASID and ACID corresponds to the same application. EAS1-EAS3 are located in different EDNs. UE1-UE3 are UEs in the same UE group. UE1 is connected to EAS1. UE2 is connected to EAS2. UE3 is connected to EAS3. Since different UEs in the same UE group are connected to different EASs, to ensure data consistency, application context synchronization can be performed between EAS1 to EAS3. EAS1 to EAS3 can also be located in the same EDN. Figure 3 takes EAS1 to EAS3 located in different EDNs as an example.
[0139] The following is a further introduction to the communication method and communication device for edge computing with reference to the accompanying drawings. It can be understood that the present application uses the first UE, the first EES, the first EAS, the second UE, the second EES and the second EAS as examples of the execution subjects of the interaction diagram, but the present application does not limit the execution subjects of the interaction diagram. For example, the first UE in the method provided in the present application may also be a chip, a chip system, or a processor applied to the first UE, or a logical node, a logical module or software that can implement 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.
[0140] Please refer to Figure 4, which is a flow chart of a communication method for edge computing provided in an embodiment of the present application, wherein:
[0141] 401. A first UE sends second information of a first EAS to a first EES. The second information includes address information and / or an identifier. The first EAS is an 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 may receive the second information of the first EAS.
[0142] The first UE is any one UE in a UE group. The UE group includes multiple UEs. All UEs in the UE group use the same application. The application may correspond to multiple EASs. The multiple EASs include the first EAS and other EASs.
[0143] In the embodiment of the present 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 and / or endpoint information of the first EAS.
[0144] In a possible embodiment, the second information may be carried in an EAS information provisioning request.
[0145] For example, the first UE may first send an EAS discovery request to the first EES. The request is used to request the discovery of the EAS. The request may carry the identifier of the first UE, the identifier of the UE group, and the information of the first UE. The information of 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, the AC profile may include one or more information elements in Table 1 below. For example, the EAS discovery requirement may include one or more information elements in Table 2 below. After receiving the EAS discovery request, the first EES determines an EAS that meets the AC requirements corresponding to the first UE based on the information of the first UE. If the first EES determines multiple EASs for the first UE, it sends an EAS discovery response to the first UE. The EAS discovery response carries the addresses and / or identifiers of the multiple EASs. After receiving the EAS discovery response, the first UE selects an EAS from the multiple EASs, and the EAS is the first EAS. The first UE sends an EAS information configuration request to the first EES, where the request carries the address information and / or identifier of the first EAS.
[0146] Table 1
[0147] Table 2
[0148] Step 401 may be optional. For example, if, after receiving the EAS discovery request, the first EES 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 not send an EAS information configuration request to the first EES.
[0149] 402. The first EES sends a first message to the second EES. The first message carries the following information: an identifier of a UE group and 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 UE group includes the first UE and the second UE. Accordingly, the second EES may receive the first message.
[0150] In a possible embodiment, the first message may be a common EAS announcement request, which is not limited in this patent.
[0151] In an embodiment of the present application, 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 to which the first UE sends an EAS discovery request message or an EAS information configuration request. The second EES is the EES to 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. In this way, after the second EES receives the first information of the first EAS, it can determine whether the second UE uses the first EAS based on the first information of the first EAS. The second EES determines whether the second UE uses the first EAS based on the first information of the first EAS in the following two specific implementation methods. The first specific implementation method is that the second EES determines whether the second UE uses the first EAS based on the first information of the first EAS. For example, please refer to the method embodiments corresponding to Figures 5 to 7 for details. The second specific implementation method is that the second EES sends the first information of the first EAS to the second UE, and the second UE determines whether the second UE uses the first EAS based on the first information of the first EAS. For example, please refer to the method embodiments corresponding to Figures 8 to 10 for details.
[0152] In an embodiment of the present application, the first EES may 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 may include 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.
[0153] In a possible embodiment, the service area corresponding to the first EAS refers to a service area in which the first EAS can provide services. The UE can obtain services of the first EAS within the service area, or connect to the first EAS, or obtain services of a certain KPI provided by the first EAS. The service area can be a geographical service area or a network topology service area.
[0154] In a possible embodiment, the data center information of the first EAS may be the DNAI of the EDN where the first EAS is located and / or the EDN where the first EAS is located, or may be a data center.
[0155] In a 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 corresponding to the first EAS in the service area corresponding to the first EAS, and / or the delay between the UE and the first EAS, and / or the response time information between the first EAS and the AC. The response time information corresponding to the first EAS in the service area corresponding to the first EAS may indicate the response time of data transmission when the UE is connected to the first EAS in the service area corresponding to the first EAS, that is, the time length from sending a data packet to receiving a data packet. The delay between the UE and the EAS may include an uplink delay, that is, the delay from the UE to the EAS. The end-to-end delay may include a downlink delay, that is, the delay from the EAS to the UE. The KPI information of the first EAS may include one or more information elements in Table 3 below.
[0156] Table 3
[0157] In a possible embodiment, the first EES may use the first EAS as a public EAS. Therefore, the first EAS in step 402 may also be referred to as a public EAS.
[0158] It can be seen that based on the method described in Figure 4, the first EES can send the 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, so that the second EES can determine whether the 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, rather than directly determining the first EAS used by the first UE as the EAS used by the second UE. This helps the second UE connect to a more optimal EAS to obtain application services, thereby obtaining better application services.
[0159] Please refer to Figure 5, which is a flow chart of a communication method for edge computing provided in an embodiment of the present application, wherein:
[0160] 501. A first UE sends second information of a first EAS to a first EES, where the second information includes address information and / or an identifier. The first EAS is the EAS used by the first UE. Accordingly, the first EES may receive the second information of the first EAS.
[0161] 502. The first EES sends a first message to the second EES. The first message carries the following information: an identifier of a UE group and 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 UE group includes the first UE and the second UE. Accordingly, the second EES may receive the first message.
[0162] The detailed description of step 501 and step 502 can be found in the description of step 401 and step 402, which will not be repeated here.
[0163] 503. The second UE sends a second message to the second EES, where the second message is used to request EAS discovery. 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 may receive the second message.
[0164] In a possible embodiment, the second message may be an EAS discovery request.
[0165] In a possible embodiment, the application information corresponding to the second UE may be an AC profile or an EAS discovery requirement. For example, the AC profile may include one or more information elements in Table 1 above. For example, the EAS discovery requirement may include one or more information elements in Table 2 above.
[0166] 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.
[0167] In a possible embodiment, the specific implementation method 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: 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.
[0168] The first information of 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 corresponding to the EAS, the data center information corresponding to the EAS, and the performance information corresponding to the EAS, please refer to the description of the embodiment corresponding to FIG4 and are not repeated here.
[0169] In an embodiment of the present application, the second EES can determine whether the second UE has better performance using the first EAS or the second UE has better performance using the second EAS based on the first information of the second EAS and the first information of the first EAS. If the second UE has better performance using the first EAS, the second EES determines that the second UE uses the first EAS. If the second UE has better performance using the second EAS, the second EES determines that the second UE uses the second EAS. Good performance means: for a group of UEs connected to multiple EASs, the interaction delay between EASs, the interaction complexity, and the delay / connection performance between the UE and the corresponding EAS, compared to a group of UEs connected to the same EAS, the delay / connection performance between each UE and the EAS, whether a group of UEs has better performance connecting to multiple EASs or a group of UEs has better performance connecting to the same EAS.
[0170] For example, the second EES may 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.
[0171] For another example, the second EES may 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.
[0172] For another example, the second EES may 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.
[0173] For another example, the second EES may determine whether the second UE uses the first EAS or the second EAS based on the response time information corresponding to the second EAS in the service area corresponding to the second EAS and the response time information corresponding to the first EAS in the service area corresponding to the first EAS.
[0174] For another example, the second EES may determine whether the second UE uses the first EAS or the second EAS based on response time information corresponding to the second EAS in the service area corresponding to the second EAS, response time information corresponding to the first EAS in the service area corresponding to the first EAS, and connection information between the first EES and the second EES. Optionally, the connection information between the first EES and the second EES may be a transmission delay between the first EES and the second EES.
[0175] In a 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, including: 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 delay 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 delay information or response time information between the first EAS / first EES and the second EAS / second EES.
[0176] Optionally, 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 may be preconfigured in the second EES and / or preconfigured in the first EES. Optionally, the latency information or response time information between the first EAS / first EES and the second EAS / second EES may be preconfigured in the second EES and / or preconfigured in the first EES.
[0177] As can be seen, based on the method described in Figure 5, the second 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, rather than directly determining the first EAS used by the first UE as the EAS used by the second UE. This helps the second UE connect to a more optimal EAS to obtain application services, thereby obtaining better application services.
[0178] Please refer to Figure 6, which is a flow chart of a communication method for edge computing provided by an embodiment of the present application. The message name in the method flow shown in Figure 6 is only a specific example. The information transmitted in the method flow shown in Figure 6 can also be carried in other messages for transmission, which is not limited by the embodiment of the present application.
[0179] 601. A first UE sends an EAS information configuration request to a first EES. The EAS information configuration request carries second information of a first EAS, the second information including address information and / or an identifier. The first EAS is the EAS used by the first UE. Accordingly, the first EES may receive the EAS information configuration request.
[0180] 602. The first EES sends an EAS information provisioning response to the first UE.
[0181] 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 requirements of the first UE, 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 are not required.
[0182] 603. The first EES sends a public EAS announcement request to the second EES. The public EAS announcement request carries the following information: an identifier of the first UE, an 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 may receive the public EAS announcement request.
[0183] 604. The second EES sends a common EAS announcement response to the first EES.
[0184] 605. The second UE sends an EAS discovery request to the second EES. The EAS discovery request is used to request EAS discovery. The EAS discovery request carries an identifier of the second UE, an identifier of the UE group, and information about the second UE. The information about the second UE includes location information and / or application information corresponding to the second UE. Accordingly, the second EES may receive the EAS discovery request.
[0185] 606. The second EES determines a second EAS based on the information of the second UE.
[0186] Optionally, the second EES determines the second EAS based on information about the second UE and information about the EAS managed by the second EES.
[0187] Optionally, the EAS may send a registration request message to the EES, carrying the EAS information. Alternatively, the second EES may obtain the EAS information through a network management system, or the second EES may obtain the EAS information through pre-configuration.
[0188] Optionally, the EAS information may include one or more information elements listed in Table 4 below.
[0189] Table 4
[0190] 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.
[0191] The specific implementation of steps 601 and 603 can be found in the description of steps 401 and 402 in FIG4 , which are not repeated here. The specific implementation of steps 605 to 607 can be found in the description of steps 503 to 504 in FIG5 , which are not repeated here.
[0192] 608. The second EES sends an EAS discovery response to the second UE. Correspondingly, the second UE may receive the EAS discovery response.
[0193] If it is determined that the second UE uses the first EAS, the EAS discovery response carries second information of the first EAS;
[0194] If it is determined that the second UE uses the second EAS, the EAS discovery response carries second information of the second 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.
[0195] In the embodiment of the present application, if the EAS discovery response carries the second information of the first EAS, the second UE may communicate with the first EAS based on the second information of the first EAS after receiving the EAS discovery response.
[0196] If the EAS discovery response carries the second information of the second EAS, the second UE may communicate with the second EAS based on the second information of the second EAS after receiving the EAS discovery response.
[0197] 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. The 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 may receive the EAS synchronization request.
[0198] In the embodiment of the present application, after the second EAS receives the EAS synchronization request, step 614 may be executed.
[0199] 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. The 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 may receive the EAS selection announcing request.
[0200] 611. 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 may receive the EAS synchronization request.
[0201] In the embodiment of the present application, after the first EAS receives the EAS synchronization request, step 613 may be executed.
[0202] 612. The first EES sends an EAS selection announcing response to the second EES.
[0203] 613. 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.
[0204] 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.
[0205] In a possible embodiment, the first UE identifier and / or UE group identifier carried in the public EAS announcement request in step 603 and the first UE identifier and / or UE group identifier carried in the EAS synchronization request in step 609 are optional.
[0206] In a possible embodiment, the identifier of the second UE and / or the identifier of the UE group carried by the EAS discovery request in step 605, the identifier of the second UE and / or the identifier of the UE group carried by the EAS selection declaration request in step 610, and the identifier of the second UE and / or the identifier of the UE group carried by the EAS synchronization request in step 611 are optional.
[0207] It can be seen that based on the method described in Figure 6, the second EES can determine whether the 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, rather than directly determining the first EAS used by the first UE as the EAS used by the second UE. This is conducive to the second UE connecting to a better EAS to obtain application services, so as to obtain better application services. And if the second UE does not use the first EAS, the second EAS and the first EAS can synchronize the application context to ensure data consistency between different UEs in the same UE group, so that the services of the UEs in the UE group can proceed normally.
[0208] Please refer to Figure 7, which is a flow chart of a communication method for edge computing provided by an embodiment of the present application. The message name in the method flow shown in Figure 7 is only a specific example. The information transmitted in the method flow shown in Figure 7 can also be carried in other messages for transmission, and this embodiment of the present application does not limit it. Among them:
[0209] 701. A first UE sends an EAS information configuration request to a first EES. The EAS information configuration request carries second information of a first EAS, the second information including address information and / or an identifier. The first EAS is the EAS used by the first UE. Accordingly, the first EES may receive the EAS information configuration request.
[0210] 702. The first EES sends an EAS information configuration response to the first UE.
[0211] 703. The first EES sends a public EAS announcement request to the second EES. The public EAS announcement request carries the following information: an identifier of the first UE, an 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 may receive the public EAS announcement request.
[0212] 704. The second EES sends a public EAS announcement response to the first EES.
[0213] 705. The second UE sends an EAS discovery request to the second EES. The EAS discovery request is used to request EAS discovery. The EAS discovery request carries an identifier of the second UE, an identifier of the UE group, and information about the second UE. The information about the second UE includes location information and / or application information corresponding to the second UE. Accordingly, the second EES may receive the EAS discovery request.
[0214] 706. The second EES determines a second EAS based on the information of the second UE.
[0215] 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.
[0216] The specific implementation of steps 701 to 707 may refer to the specific implementation of steps 601 to 607, which will not be described in detail here.
[0217] 708. The second EES sends an EAS discovery response to the second UE. Correspondingly, the second UE may receive the EAS discovery response.
[0218] If it is determined that the second UE uses the first EAS, the EAS discovery response carries second information of the first EAS;
[0219] If it is determined that the second UE uses 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 takes the use of the second EAS by the second UE as an example.
[0220] In the embodiment of the present application, if the EAS discovery response carries the second information of the first EAS, the second UE may communicate with the first EAS based on the second information of the first EAS after receiving the EAS discovery response.
[0221] If the EAS discovery response carries the second information of the second EAS and the second information of the first EAS, then after receiving the EAS discovery response, the second UE may 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 synchronizes the application context with the first EAS based on the second information of the first EAS.
[0222] In a possible embodiment, if it is determined that the second UE uses the second EAS, the second response message further carries indication information, where the indication information indicates that the second EAS needs to synchronize application context with the first EAS.
[0223] 709. The second UE sends the first UE identifier, the UE group identifier, and the second information of the first EAS to the second EAS. Correspondingly, the second EAS may receive the first UE identifier, the UE group identifier, and the second information of the first EAS.
[0224] Specifically, the EEC in the second UE may receive the EAS discovery response. The EEC in the second UE may then send the EAS discovery response to the AC in the second UE, which in turn may send the first UE's identifier, the UE group identifier, and the second information of the first EAS to the second EAS. In other words, in this embodiment of the present application, the second UE's application layer may notify the second EAS to synchronize application contexts with the first EAS.
[0225] In the embodiment of the present 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, step 714 may be executed.
[0226] 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.
[0227] 711. 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 may receive the EAS synchronization request.
[0228] In the embodiment of the present application, after the first EAS receives the EAS synchronization request, step 713 may be executed.
[0229] 712. The first EES sends an EAS selection announcement response to the second EES.
[0230] 713. 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.
[0231] 714. The second EAS synchronizes the application context corresponding to the UE group with the first EAS based on the information of the first EAS.
[0232] 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.
[0233] In a possible embodiment, the identifier of the second UE and / or the identifier of the UE group carried by the EAS discovery request in step 705, the identifier of the second UE and / or the identifier of the UE group carried by the EAS selection declaration request in step 710, and the identifier of the second UE and / or the identifier of the UE group carried by the EAS synchronization request in step 711 are optional.
[0234] It can be seen that based on the method described in Figure 7, the second EES can determine whether the 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, rather than directly determining the first EAS used by the first UE as the EAS used by the second UE. This is conducive to the second UE connecting to a better EAS to obtain application services, so as to obtain better application services. And if the second UE does not use the first EAS, the second EAS and the first EAS can synchronize the application context to ensure data consistency between different UEs in the same UE group, so that the services of the UEs in the UE group can proceed normally.
[0235] Please refer to Figure 8, which is a flow chart of a communication method for edge computing provided in an embodiment of the present application, wherein:
[0236] 801. A first UE sends second information of a first EAS to a first EES, where the second information includes address information and / or an identifier. The first EAS is the EAS used by the first UE. Accordingly, the first EES may receive the second information of the first EAS.
[0237] 802. A first EES sends a first message to a second EES. The first message carries the following information: an identifier of a UE group and first information of the first EAS. The first information includes one or more of the following: a service area, data center information, and performance information. The UE group includes the first UE and the second UE. Accordingly, the second EES may receive the first message.
[0238] 803. The second UE sends a second message to the second EES, where the second message is used to request EAS discovery. 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 may receive the second message.
[0239] 804. The second EES determines a second EAS based on the information of the second UE.
[0240] The specific implementation of steps 801 to 804 can be found in the corresponding descriptions of steps 501 to 504 and will not be repeated here.
[0241] 805. The second EES sends a second response message corresponding to the second message to the second UE, where the second response message carries the first information of the first EAS and the first information of the second EAS. Accordingly, the second UE may receive the second response message.
[0242] Optionally, the second response message may also carry the delay 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 delay 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 delay 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 delay 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.
[0243] Optionally, 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 may be preconfigured in the second EES and / or preconfigured in the first EES. Optionally, the latency information or response time information between the first EAS / first EES and the second EAS / second EES may be preconfigured in the second EES and / or preconfigured in the first EES.
[0244] 806. The second UE 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.
[0245] The first information of 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 corresponding to the second EAS, the data center information corresponding to the EAS, and the performance information corresponding to the EAS, please refer to the description of the embodiment corresponding to FIG4 and are not repeated here.
[0246] Among them, the specific implementation method in which the second UE 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 as the specific implementation method in which 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 described in the embodiment corresponding to Figure 5, and will not be repeated here.
[0247] As can be seen, based on the method described in FIG8 , the second UE can determine whether to use 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 to connect to a more optimal EAS to obtain application services, thereby obtaining better application services.
[0248] Please refer to Figure 9, which is a flow chart of a communication method for edge computing provided by an embodiment of the present application. The message name in the method flow shown in Figure 9 is only a specific example. The information transmitted in the method flow shown in Figure 9 can also be carried in other messages for transmission, which is not limited by the embodiment of the present application.
[0249] 901. A first UE sends an EAS information configuration request to a first EES. The EAS information configuration request carries second information of a first EAS, the second information including address information and / or an identifier. The first EAS is the EAS used by the first UE. Accordingly, the first EES may receive the EAS information configuration request.
[0250] 902. The first EES sends an EAS information configuration response to the first UE.
[0251] 903. The first EES sends a public EAS announcement request to the second EES. The public EAS announcement request carries the following information: an identifier of the first UE, an 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 may receive the public EAS announcement request.
[0252] 904. The second EES sends a public EAS announcement response to the first EES.
[0253] 905. The second UE sends an EAS discovery request to the second EES. The EAS discovery request is used to request EAS discovery. The EAS discovery request carries an identifier of the second UE, an identifier of the UE group, and information about the second UE. The information about the second UE includes location information and / or application information corresponding to the second UE. Accordingly, the second EES may receive the EAS discovery request.
[0254] 906. The second EES determines a second EAS based on the information of the second UE.
[0255] The specific implementation of steps 901 to 906 can refer to the specific implementation of steps 601 to 607, which will not be repeated here.
[0256] 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 may receive the EAS discovery response.
[0257] Optionally, the EAS discovery response may also carry 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. Accordingly, the second UE may 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.
[0258] Optionally, 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 may be preconfigured in the second EES and / or preconfigured in the first EES. Optionally, the latency information or response time information between the first EAS / first EES and the second EAS / second EES may be preconfigured in the second EES and / or preconfigured in the first EES.
[0259] 908. The second UE 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.
[0260] The specific implementation of steps 907 to 908 can refer to the specific implementation of steps 805 and 806, which will not be repeated here.
[0261] In an embodiment of the present 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.
[0262] 909. The second UE sends an EAS information configuration message to the second EES. The message carries an identifier of the UE group, second information about the EAS used by the second UE, and / or indication information. The indication information indicates whether the second UE uses the first EAS or whether application context synchronization is required. Accordingly, the second EES may receive the EAS information configuration message.
[0263] 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, the second EES sends an EAS synchronization request to the second EAS. The 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 may receive the EAS synchronization request.
[0264] After the second EAS receives the EAS synchronization request, step 915 may be executed.
[0265] 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, the second EES sends an EAS selection announcement request to the first EES. The EAS selection announcement request carries an identifier of the second UE, an identifier of the UE group, and second information of the second EAS. Accordingly, the first EES may receive the EAS selection announcement request.
[0266] 912. 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 may receive the EAS synchronization request.
[0267] After the first EAS receives the EAS synchronization request, step 914 may be executed.
[0268] 913. The first EES sends an EAS selection announcement response to the second EES.
[0269] 914. 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.
[0270] 915. The second EAS synchronizes the application context corresponding to the UE group with the first EAS based on the information of the first EAS.
[0271] 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 also optional.
[0272] In a possible embodiment, the identifier of the second UE and / or the identifier of the UE group carried by the EAS discovery request in step 905, the identifier of the second UE and / or the identifier of the UE group carried by the EAS selection declaration request in step 911, and the identifier of the second UE and / or the identifier of the UE group carried by the EAS synchronization request in step 912 are optional.
[0273] It can be seen that based on the method described in Figure 9, the second UE can determine whether to use the first EAS with the second UE 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 conducive to the second UE connecting to a better EAS to obtain application services, so as to obtain better application services. And 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 between different UEs in the same UE group, so that the services of the UEs in the UE group can proceed normally.
[0274] Please refer to Figure 10, which is a flow chart of a communication method for edge computing provided by an embodiment of the present application. The message name in the method flow shown in Figure 10 is only a specific example. The information transmitted in the method flow shown in Figure 10 can also be carried in other messages for transmission, which is not limited by the embodiment of the present application.
[0275] 1001. A first UE sends an EAS information configuration request to a first EES. The EAS information configuration request carries second information of a first EAS, the second information including address information and / or an identifier. The first EAS is the EAS used by the first UE. Accordingly, the first EES may receive the EAS information configuration request.
[0276] 1002. The first EES sends an EAS information configuration response to the first UE.
[0277] 1003. The first EES sends a public EAS announcement request to the second EES. The public EAS announcement request carries the following information: an identifier of the first UE, an 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 may receive the public EAS announcement request.
[0278] 1004. The second EES sends a public EAS announcement response to the first EES.
[0279] 1005. The second UE sends an EAS discovery request to the second EES. The EAS discovery request is used to request EAS discovery. The EAS discovery request carries an identifier of the second UE, an identifier of the UE group, and information about the second UE. The information about the second UE includes location information and / or application information corresponding to the second UE. Accordingly, the second EES may receive the EAS discovery request.
[0280] 1006. The second EES determines a second EAS based on the information of the second UE.
[0281] The specific implementation of steps 901 to 906 can refer to the specific implementation of steps 601 to 607, which will not be repeated here.
[0282] 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 may receive the EAS discovery response.
[0283] Optionally, the EAS discovery response may also carry 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. Accordingly, the second UE may 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.
[0284] Optionally, 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 may be preconfigured in the second EES and / or preconfigured in the first EES. Optionally, the latency information or response time information between the first EAS / first EES and the second EAS / second EES may be preconfigured in the second EES and / or preconfigured in the first EES.
[0285] 1008. The second UE 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.
[0286] The specific implementation of steps 1007 to 1008 can refer to the specific implementation of steps 805 and 806, which will not be repeated here.
[0287] In an embodiment of the present 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.
[0288] 1009. The second UE sends an EAS information configuration message to the second EES. The message carries an identifier of the UE group, second information about the EAS used by the second UE, and / or indication information, wherein the indication information indicates whether the second UE uses the first EAS or whether application context synchronization is required. Accordingly, the second EES may receive the EAS information configuration message.
[0289] 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, the second EES sends an EAS selection announcement request to the first EES. The EAS selection announcement request carries an identifier of the second UE, an identifier of the UE group, and second information of the second EAS. Accordingly, the first EES may receive the EAS selection announcement request.
[0290] 1011. 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 may receive the EAS synchronization request.
[0291] In the embodiment of the present application, after the first EAS receives the EAS synchronization request, step 1014 is executed.
[0292] 1012. The first EES sends an EAS selection announcement response to the second EES.
[0293] 1013. If it is determined that the second UE uses the second EAS, the second UE sends the first UE identifier, the UE group identifier, and the second information of the first EAS to the second EAS. Correspondingly, the second EAS may receive the first UE identifier, the UE group identifier, and the second information of the first EAS.
[0294] Specifically, the AC in the second UE may send the first UE identifier, the UE group identifier, and the second information of the first EAS to the second EAS. In other words, in this embodiment of the present application, the application layer of the second UE may notify the second EAS to synchronize application contexts with the first EAS.
[0295] In the embodiment of the present 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, step 1015 may be executed.
[0296] 1014. 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.
[0297] 1015. The second EAS synchronizes the application context corresponding to the UE group with the first EAS based on the information of the first EAS.
[0298] 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.
[0299] In a possible embodiment, the identifier of the second UE and / or the identifier of the UE group carried by the EAS discovery request in step 1005, the identifier of the second UE and / or the identifier of the UE group carried by the EAS selection declaration request in step 1010, and the identifier of the second UE and / or the identifier of the UE group carried by the EAS synchronization request in step 1011 are optional.
[0300] It can be seen that based on the method described in Figure 10, the second UE can determine whether to use the first EAS with the second UE 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 conducive to the second UE connecting to a better EAS to obtain application services, so as to obtain better application services. And 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 between different UEs in the same UE group, so that the services of the UEs in the UE group can proceed normally.
[0301] Please refer to Figure 11, which is a flow chart of a communication method for edge computing provided in an embodiment of the present application, wherein:
[0302] 1101. A first UE sends second information of a first EAS to a first EES, where the second information includes address information and / or an identifier. The first EAS is the EAS used by the first UE. Accordingly, the first EES may receive the second information of the first EAS.
[0303] The specific implementation of step 1101 can refer to the specific implementation of step 401 and will not be repeated here.
[0304] 1102. The first EES sends a first message to the second EES, where the first message carries second information of the first EAS. Correspondingly, the second EES may receive the first message.
[0305] In a possible embodiment, the first message may be a public EAS announcement request.
[0306] 1103. The second UE sends a third message to the second EES, requesting EAS discovery. The third message carries information about the second UE, including location information and / or application information corresponding to the second UE. The second UE and the first UE are in the same UE group. Accordingly, the second EES may receive the third message.
[0307] For an explanation of the information of the second UE, please refer to the description of the information of the second UE in the embodiment corresponding to FIG5 , which will not be repeated here.
[0308] In a possible embodiment, the third message may be an EAS discovery request.
[0309] 1104. The second EES determines a second EAS based on the information of the second UE.
[0310] The second EES determines the second EAS based on the information of the second UE in the following two implementations:
[0311] 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.
[0312] Method 2: If the second EES determines multiple EASs that meet the second UE's requirements based on the second UE's information, the second EES may provide the multiple EASs back to the second UE, and the second UE selects one of the multiple EASs. The EAS selected by the second UE is the second EAS. The second UE notifies the second EES of the second EAS.
[0313] 1105. The second EES sends a second message to the first EES. The second message carries the identifier of the second UE and first 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 second message.
[0314] Optionally, the first EES can also determine whether to use the first EAS or the second EAS based on the delay 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 delay 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.
[0315] Optionally, 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 may be pre-configured in the first EES. Optionally, the latency information or response time information between the first EAS / first EES and the second EAS / second EES may be pre-configured in the first EES.
[0316] Optionally, 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. Optionally, 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 may be preconfigured in the second EES. Optionally, the latency information or response time information between the first EAS / first EES and the second EAS / second EES may be preconfigured in the second EES.
[0317] 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.
[0318] 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 corresponding to the first EAS, the data center information corresponding to the EAS, and the performance information corresponding to the EAS, please refer to the description of the embodiment corresponding to FIG4 and are not repeated here.
[0319] Among them, the specific implementation method of the first EES determining 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 as the specific implementation method of the second EES determining 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 described in the embodiment corresponding to Figure 5, and will not be repeated here.
[0320] In a possible embodiment, the first message may further carry an identifier of the first UE and / or an identifier of the UE group to which the first UE belongs.
[0321] In a possible embodiment, the third message may further carry the identifier of the second UE and / or the identifier of the UE group to which the second UE belongs.
[0322] In a possible embodiment, the second message may further carry an identifier of the UE group to which the second UE belongs.
[0323] As can be seen, based on the method described in Figure 11, the first EES can 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 helps the second UE connect to a more optimal EAS to obtain application services, thereby obtaining better application services.
[0324] Please refer to Figure 12, which is a flow chart of a communication method for edge computing provided by an embodiment of the present application. The message name in the method flow shown in Figure 12 is only a specific example. The information transmitted in the method flow shown in Figure 12 can also be carried in other messages for transmission, which is not limited by the embodiment of the present application. Among them:
[0325] 1201. A first UE sends an EAS information configuration request to a first EES. The EAS information configuration request carries second information of a first EAS, the second information including address information and / or an identifier. The first EAS is the EAS used by the first UE. Accordingly, the first EES may receive the EAS information configuration request.
[0326] 1202. The first EES sends an EAS information configuration response to the first UE.
[0327] The specific implementation of steps 1201 to 1202 may refer to the specific implementation of steps 601 to 602, which will not be described in detail here.
[0328] 1203. The first EES sends a public EAS announcement request to the second EES. The public EAS announcement request carries the following information: an identifier of the first UE, an identifier of the UE group, and second information of the first EAS. The UE group includes the first UE and the second UE. Accordingly, the second EES may receive the public EAS announcement request.
[0329] 1204. The second EES sends a public EAS announcement response to the first EES.
[0330] 1205. The second UE sends an EAS discovery request to the second EES. The EAS discovery request is used to request EAS discovery. The EAS discovery request carries an identifier of the second UE, an identifier of the UE group, and information about the second UE. The information about the second UE includes location information and / or application information corresponding to the second UE. Accordingly, the second EES may receive the EAS discovery request.
[0331] 1206. The second EES sends an EAS discovery response to the second UE, where the EAS discovery response carries second information of multiple EASs. Accordingly, the second UE may receive the EAS discovery response.
[0332] 1207. The second UE sends an EAS information configuration request to the second EES, where the EAS information configuration request carries the second information of the second EAS. Correspondingly, the second EES may receive the EAS information configuration request.
[0333] 1208. The second EES sends an EAS information configuration response to the second UE.
[0334] 1209. The second EES sends a public EAS announcement request to the first EES. The request carries the identifier of the second UE, the identifier of the UE group, information about the second UE, first information about the second EAS, and second information about 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.
[0335] Optionally, the first EES can also determine whether to use the first EAS or the second EAS based on the delay 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 delay 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.
[0336] Optionally, 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 may be pre-configured in the first EES. Optionally, the latency information or response time information between the first EAS / first EES and the second EAS / second EES may be pre-configured in the first EES.
[0337] Optionally, the public EAS announcement request 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. Optionally, 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 may be preconfigured in the second EES. Optionally, the latency information or response time information between the first EAS / first EES and the second EAS / second EES may be preconfigured in the second EES.
[0338] 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.
[0339] The specific implementation of steps 1203 to 1210 may refer to the specific implementation of steps 1101 to 1106 and will not be described in detail here.
[0340] 1211. The first EES sends a public EAS announcement response to the second EES, where the response carries the identifier of the second UE, the identifier of the UE group, and second information of the EAS used by the second UE. Accordingly, the second EES may receive the public EAS announcement response.
[0341] 12 takes the EAS used by the second UE as the second EAS as an example.
[0342] 1212. The second EES sends a fourth message to the second UE, where the fourth message carries second information of the EAS used by the second UE. Accordingly, the second UE may receive the fourth message.
[0343] If the EAS used by the second UE is the first EAS, after receiving the fourth message, the second UE may communicate with the first EAS based on the second information of the first EAS.
[0344] If the EAS used by the second UE is the second EAS, after receiving the fourth message, the second UE may communicate with the second EAS based on the second information of the second EAS.
[0345] 1213. The second EES sends an EAS synchronization request to the second EAS. The EAS synchronization request carries the identifier of the first UE, the identifier of the UE group, and the second information of the first EAS. Correspondingly, the second EAS may receive the EAS synchronization request.
[0346] In the embodiment of the present application, after the second EAS receives the EAS synchronization request, step 1216 may be executed.
[0347] 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. 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 may receive the EAS synchronization request.
[0348] In the embodiment of the present application, after the first EAS receives the EAS synchronization request, step 1215 may be executed.
[0349] 1215. 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.
[0350] 1216. The second EAS synchronizes the application context corresponding to the UE group with the first EAS based on the information of the first EAS.
[0351] The specific implementation of steps 1201 to 1210 can be found in the relevant description of the embodiment corresponding to FIG11 , which will not be repeated here.
[0352] In a 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.
[0353] In a 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 declaration request in step 1209, the EAS selection declaration 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.
[0354] It can be seen that based on the method described in Figure 12, the first EES can 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 is conducive to the second UE connecting to a better EAS to obtain application services, so as to obtain better application services. And if the second UE does not use the first EAS, the second EAS and the first EAS can synchronize the application context to ensure data consistency between different UEs in the same UE group, so that the services of the UEs in the UE group can proceed normally.
[0355] Please refer to Figure 13, which is a flow chart of a communication method for edge computing provided by an embodiment of the present application. The message name in the method flow shown in Figure 13 is only a specific example. The information transmitted in the method flow shown in Figure 13 can also be carried in other messages for transmission, which is not limited by the embodiment of the present application. Among them:
[0356] 1301. A first UE sends an EAS information configuration request to a first EES. The EAS information configuration request carries second information of a first EAS, the second information including address information and / or an identifier. The first EAS is the EAS used by the first UE. Accordingly, the first EES may receive the EAS information configuration request.
[0357] 1302. The first EES sends an EAS information configuration response to the first UE.
[0358] The specific implementation of steps 1301 to 1302 may refer to the specific implementation of steps 601 to 602, which will not be described in detail here.
[0359] 1303. The first EES sends a public EAS announcement request to the second EES. The public EAS announcement request carries the following information: an identifier of the first UE, an identifier of the UE group, and second information of the first EAS. The UE group includes the first UE and the second UE. Accordingly, the second EES may receive the public EAS announcement request.
[0360] 1304. The second EES sends a public EAS announcement response to the first EES.
[0361] 1305. The second UE sends an EAS discovery request to the second EES. The EAS discovery request is used to request EAS discovery. The EAS discovery request carries an identifier of the second UE, an identifier of the UE group, and information about the second UE. The information about the second UE includes location information and / or application information corresponding to the second UE. Accordingly, the second EES may receive the EAS discovery request.
[0362] 1306. The second EES sends an EAS discovery response to the second UE, where the EAS discovery response carries second information of multiple EASs. Accordingly, the second UE may receive the EAS discovery response.
[0363] 1307. The second UE sends an EAS information configuration request to the second EES, where the EAS information configuration request carries the second information of the second EAS. Correspondingly, the second EES may receive the EAS information configuration request.
[0364] 1308. The second EES sends an EAS information configuration response to the second UE.
[0365] 1309. The second EES sends a public EAS announcement request to the first EES. The request carries the identifier of the second UE, the identifier of the UE group, information about the second UE, first information about the second EAS, and second information about 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.
[0366] Optionally, the first EES can also determine whether to use the first EAS or the second EAS based on the delay 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 delay 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.
[0367] Optionally, 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 may be pre-configured in the first EES. Optionally, the latency information or response time information between the first EAS / first EES and the second EAS / second EES may be pre-configured in the first EES.
[0368] Optionally, the public EAS announcement request 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. Optionally, 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 may be preconfigured in the second EES. Optionally, the latency information or response time information between the first EAS / first EES and the second EAS / second EES may be preconfigured in the second EES.
[0369] 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.
[0370] The specific implementation of steps 1303 to 1310 may refer to the specific implementation of steps 1101 to 1106 and will not be described in detail here.
[0371] 1311. The first EES sends a public EAS announcement response to the second EES, where the response carries the identifier of the second UE, the identifier of the UE group, and second information of the EAS used by the second UE. Accordingly, the second EES may receive the public EAS announcement response.
[0372] 1312. The second EES sends a fourth message to the second UE, where the fourth message carries second information of the EAS used by the second UE. Accordingly, the second UE may receive the fourth message.
[0373] If the EAS used by the second UE is the first EAS, after receiving the fourth message, the second UE may communicate with the first EAS based on the second information of the first EAS.
[0374] If the EAS used by the second UE is the second EAS, then after receiving the fourth message, the second UE may communicate with the second EAS based on the second information of the second EAS. If the EAS used by the second UE is the second EAS, 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 uses the second EAS as an example.
[0375] 1313. The second UE sends the first UE identifier, the UE group identifier, and the second information of the first EAS to the second EAS. Correspondingly, the second EAS may receive the first UE identifier, the UE group identifier, and the second information of the first EAS.
[0376] Specifically, the AC in the second UE may send the first UE identifier, the UE group identifier, and the second information of the first EAS to the second EAS. In other words, in this embodiment of the present application, the application layer of the second UE may notify the second EAS to synchronize application contexts with the first EAS.
[0377] In the embodiment of the present 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, step 1316 may be executed.
[0378] 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 may receive the EAS synchronization request.
[0379] In the embodiment of the present application, after the first EAS receives the EAS synchronization request, step 1315 may be executed.
[0380] 1315. 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.
[0381] 1316. The second EAS synchronizes the application context corresponding to the UE group with the first EAS based on the information of the first EAS.
[0382] In a possible embodiment, the fourth message further carries indication information, where the indication information indicates that the second EAS needs to synchronize application context with the first EAS.
[0383] In a possible embodiment, the second response message further carries indication information, where the indication information indicates that the second EAS needs to synchronize application context with the first EAS.
[0384] In a 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 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.
[0385] In a possible embodiment, the identifier of the second UE and / or the identifier of the UE group carried by the EAS discovery request in step 1305, the identifier of the second UE and / or the identifier of the UE group carried by the EAS selection declaration request in step 1309, the identifier of the second UE and / or the identifier of the UE group carried by the EAS selection declaration response in step 1311, and the identifier of the second UE and / or the identifier of the UE group carried by the EAS synchronization request in step 1314 are optional.
[0386] It can be seen that based on the method described in Figure 13, the first EES can 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 is conducive to the second UE connecting to a better EAS to obtain application services, so as to obtain better application services. And if the second UE does not use the first EAS, the second EAS and the first EAS can synchronize the application context to ensure data consistency between different UEs in the same UE group, so that the services of the UEs in the UE group can proceed normally.
[0387] The present application provides a communication device that can be used to implement the functions of the above-mentioned second EES or first EES or second UE or first EAS or second EAS. The communication device can be the second EES or the first EES or the second UE or the first EAS or the second EAS. The communication device includes a module or unit that corresponds one-to-one to the method / operation / step / action performed by the second EES or the first EES or the second UE or the first EAS or the second EAS in the above-mentioned method embodiment. The unit can be a hardware circuit, or software, or a combination of a hardware circuit and software. Please refer to Figure 14, which shows a structural diagram of a communication device 1400 of an embodiment of the present application. 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, and the signaling and / or data 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;
[0388] In one embodiment, when the communication device 1400 is a second EES, wherein:
[0389] Interface unit 1401 is used to receive a first message sent by a first EES, where the first message carries the following information: an identifier of a UE group, first information of a first edge application server EAS, where the first information includes one or more of the following: service area, data center information, and performance information; the first EAS is an EAS used by a first UE, and the UE group includes a first UE and a second UE.
[0390] In a possible embodiment, the interface unit 1401 is further used to receive a second message sent by the second UE, where the second message is used to request discovery of the EAS, and the second message carries information of the second UE, where the information of the second UE includes location information and / or application information corresponding to the second UE; the processing unit 1402 is used 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.
[0391] In a 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.
[0392] In a possible embodiment, the first message also carries second information of the first EAS, and the second information includes 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.
[0393] In a possible embodiment, if it is determined that the second UE uses the second EAS, the interface unit 1401 is further used 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, the interface unit 1401 is further used to send the second information of the second EAS to the first EES.
[0394] In a 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.
[0395] In a possible embodiment, if it is determined that the second UE uses the second EAS, the second response message further carries indication information, where the indication information indicates that the second EAS needs to synchronize application context with the first EAS.
[0396] In a possible embodiment, the interface unit 1401 is also used to receive a second message sent by the second UE, where the second message is used to request the discovery of the EAS, and the second message carries information of the second UE, where the information of the second UE includes location information and / or application information corresponding to the second UE; the processing unit 1402 is used to determine the second EAS based on the information of the second UE; the interface unit 1401 is also used to send a second response message corresponding to the second message to the second UE, where the second response message carries the first information of the first EAS and the first information of the second EAS.
[0397] In a possible embodiment, the second response message further carries second information of the first EAS and second information of the second EAS, where the second information includes identification and / or address information.
[0398] In a possible embodiment, the interface unit 1401 is further used to receive 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 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 used to send the second information of the second EAS to the first EES.
[0399] In a 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 second information of the first EAS to the second EAS.
[0400] In one embodiment, when the communication device 1400 is a first EES, wherein:
[0401] Interface unit 1401 is used to send a first message to the second EES, where the first message carries the following information: an identifier of the UE group, first information of the first EAS, where 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.
[0402] In a possible embodiment, the interface unit 1401 is further configured to receive second information of a second EAS sent by a second EES, where the second information includes identification and / or address information, and the second EAS is the EAS used by the second UE; and send the second information of the second EAS to the first EAS.
[0403] In one embodiment, when the communication device 1400 is a second UE, wherein:
[0404] Interface unit 1401 is used to send a second message to the second edge enabling server EES, where the second message is used to request the discovery of EAS, and the second message carries information of the second UE, where the information of the second UE includes location information and / or application information corresponding to the second UE; interface unit 1401 is also used to receive a second response message corresponding to the second message sent by the second EES, where the second response message carries first information of the first EAS, first information of the second EAS, and 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; processing unit 1402 is used 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.
[0405] In a possible embodiment, the second response message further carries second information of the first EAS and second information of the second EAS, where the second information includes identification and / or address information;
[0406] If it is determined that the second UE uses the first EAS, the interface unit 1401 is further configured to communicate with the first EAS based on the second information of the first EAS;
[0407] If it is determined that the second UE uses the second EAS, the interface unit 1401 is further configured to communicate with the second EAS based on the second information of the second EAS.
[0408] In a possible embodiment, the second UE sends second information and / or indication information of the EAS used by the second UE to the second EES, where the indication information indicates whether the second UE uses the first EAS or whether application context synchronization is required.
[0409] In a 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.
[0410] In one embodiment, when the communication device 1400 is a first EAS, wherein:
[0411] The interface unit 1401 is configured to receive second information of a second EAS sent by the first edge enabling server EES, where the second information includes identification and / or address information; the first EAS is an EAS used by the first UE, and the second EAS is an EAS used by the second UE; the first UE and the second UE are included in a UE group;
[0412] The interface unit 1401 is further configured to synchronize the application context corresponding to the UE group with the second EAS based on the second information of the second EAS.
[0413] In one embodiment, when the communication device 1400 is a second UE, wherein:
[0414] The interface unit 1401 is configured to send a second message to the second edge enabling server EES, where the second message is used to request discovery of the EAS, and the second message carries information about the second UE, where the information about the second UE includes location information and / or application information corresponding to the second UE;
[0415] The interface unit 1401 is further configured to receive a second response message corresponding to the second message sent by the second EES, where the second response message carries second information of the second EAS and second information of the first EAS, where the second EAS is the EAS used by the second UE, the first EAS is the EAS used by the first UE, and the first UE and the second UE are included in the UE group; the second information includes identification and / or address information;
[0416] The interface unit 1401 is configured to send second information of the first EAS to the second EAS.
[0417] In a possible embodiment, the second response message further carries indication information, where the indication information indicates that the second EAS needs to synchronize application context with the first EAS.
[0418] In one embodiment, when the communication device 1400 is a second EAS, wherein:
[0419] The interface unit 1401 is configured to receive second information of a first EAS sent by a second edge enabling server EES or a second user equipment UE, where the second information includes identification and / or address information; the first EAS is an EAS used by the first UE, and the second EAS is an EAS used by the second UE; the first UE and the second UE are included in a UE group;
[0420] The interface unit 1401 is further configured to synchronize the application context corresponding to the UE group with the first EAS based on the second information of the first EAS.
[0421] In one embodiment, when the communication device 1400 is a first EES, wherein:
[0422] Interface unit 1401 is used to send a first message to the second EES, where the first message carries second information of the first edge application server EAS, where the second information includes identification and / or address information, and the first EAS is the EAS used by the first UE; interface unit 1401 is used to receive a second message sent by the second EES, where the second message carries the identification of the second UE and first information of the second EAS, and the first information includes one or more of the following: service area, data center information, and performance information; processing unit 1402 is used 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, and the first UE and the second UE are included in the same UE group.
[0423] In a possible embodiment, the second message also carries information of the second UE, and the information of the second UE 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.
[0424] In a possible embodiment, the second message also carries second information of the second EAS; the interface unit 1401 is also used 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.
[0425] In a possible embodiment, if it is determined that the second UE uses the second EAS, the interface unit 1401 is further configured to send second information of the second EAS to the first EAS.
[0426] In a possible embodiment, if it is determined that the second UE uses the second EAS, the second response message further carries indication information, where the indication information indicates that the second EAS needs to synchronize application context with the public EAS.
[0427] In one embodiment, when the communication device 1400 is a second EES, wherein:
[0428] Interface unit 1401 is used to receive a first message sent by a first EES, the first message carries second information of a first edge application server EAS, the second information includes an identification and / or address information, and the first EAS is the EAS used by the first UE; interface unit 1401 is also used to receive a third message sent by a second UE, the third message is used to request discovery of the EAS, the second message carries information of the second UE, the information of the second UE includes 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 used to determine the second EAS based on the information of the second UE; interface unit 1401 is also used to send a second message to the first EES, the second message carries an identification of the second UE and first information of the second EAS, the first information includes one or more of the following: service area, data center information, performance information, the first information of the second EAS is used to determine whether the second UE uses the first EAS or the second EAS.
[0429] In a possible embodiment, the second message further carries information of the second UE, where the information of the second UE includes location information and / or application information corresponding to the second UE.
[0430] In a possible embodiment, the second message also carries second information of the second EAS; the interface unit 1401 is also used to receive 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, and the EAS used by the second UE is the second EAS or the first EAS; the interface unit 1401 is also used to send a fourth message to the second UE, and the fourth message carries the second information of the EAS used by the second UE.
[0431] In a possible embodiment, the EAS used by the second UE is a second EAS, and the interface unit 1401 is further configured to send the second information of the first EAS to the second EAS.
[0432] In a possible embodiment, the EAS used by the second UE is the second EAS, and the fourth message further carries second information of the first EAS.
[0433] In a possible embodiment, the fourth message further carries indication information, where the indication information indicates that the second EAS needs to synchronize application context with the first EAS.
[0434] In a possible embodiment, the second response message further carries indication information, where the indication information indicates that the second EAS needs to synchronize application context with the first EAS.
[0435] In one embodiment, when the communication device 1400 is a second UE, wherein:
[0436] Interface unit 1401 is used to send a third message to the second EES, where the third message is used to request the discovery of EAS, and the second message carries information of the second UE, where the information of the second UE includes location information and / or application information corresponding to the second UE; interface unit 1401 is also used to receive a fourth message sent by the second EES, where the fourth message carries second information of the EAS used by the second UE and second information of the first EAS, where 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.
[0437] In a possible embodiment, the fourth message further carries indication information, where the indication information indicates that the second EAS needs to synchronize application context with the first EAS.
[0438] As shown in FIG15 , a communication device 1500 provided in an embodiment of the present application is configured to implement the functions of the second EES, the first EES, the second UE, the first EAS, or the second EAS. The device may be a communication device or a device used in a communication device. The communication device may be the second EES, the first EES, the second UE, the first EAS, or the second EAS. The device used in the communication device may be a chip system or a chip within the communication device. The chip system may be composed of a chip or may include a chip and other discrete components.
[0439] The communication device 1500 includes at least one processor 1510 for implementing the processing function of the device (e.g., the second EES or the first EES or the second UE or the first EAS or the second EAS) in the method provided in the embodiment of the present application. The communication device 1500 may also include a communication interface 1520 for implementing the transceiver operation of the device (e.g., the second EES or the first EES or the second UE or the first EAS or the second EAS) in the method provided in the embodiment of the present application. In an embodiment of the present application, the communication interface may be a transceiver, a circuit, a bus, a module or other type of communication interface for communicating with other devices via a transmission medium. For example, the communication interface 1520 is used for the device in the communication device 1500 to communicate with other devices. The processor 1510 uses the communication interface 1520 to send and receive data, and is used to implement the method described in the above method embodiment.
[0440] The communication device 1500 may also include at least one memory 1530 for storing program instructions and / or data. The memory 1530 is coupled to the processor 1510. Coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, and is used for information exchange between devices, units, or modules. The processor 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.
[0441] The specific connection medium between the communication interface 1520, processor 1510, and memory 1530 is not limited in the embodiments of the present application. In Figure 15, the embodiment of the present application shows that the memory 1530, processor 1510, and communication interface 1520 are connected via a bus. The bus is represented by a bold line in Figure 15. The connection method between other components is only for schematic illustration and is not limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one bold line is used in Figure 15, but this does not mean that there is only one bus or one type of bus.
[0442] When the communication device 1500 is specifically a device for a device (e.g., a second EES or a first EES or a second UE or 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 may output or receive a baseband signal. When the communication device 1500 is specifically a device (e.g., a second EES or a first EES or a second UE or a first EAS or a second EAS), the communication interface 1520 may output or receive a radio frequency signal. In an embodiment of the present application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.
[0443] It should be noted that the above-mentioned communication interface 1520 can be used to execute the functions of the above-mentioned interface unit 1401, and the above-mentioned processor 1510 can be used to execute the functions of the above-mentioned processing unit 1402, which will not be repeated here.
[0444] When the above-mentioned communication device is a chip applied to the second EES or the first EES or the second UE or the first EAS or the second EAS, the chip implements the function of the second EES or the first EES or the second UE or the first EAS or the second EAS in the above-mentioned method embodiment, and the chip receives information from other network elements; or, the chip sends information to other network elements.
[0445] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.
[0446] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed 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, mobile hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and storage medium can be located in an ASIC. In addition, the ASIC can be located in a core network device or a terminal. Of course, the processor and storage medium can also exist as discrete components in a terminal or access network device.
[0447] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part 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 instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is executed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program or instruction may be stored in a computer-readable storage medium or transmitted via the computer-readable storage medium. The computer-readable storage medium may 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 may be a magnetic medium, such as a floppy disk, a hard disk, or a tape; it may also be an optical medium, such as a DVD; it may also be a semiconductor medium, such as a solid state disk (SSD).
[0448] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.
[0449] It is understood that the various numbers used in the embodiments of this application are merely for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not necessarily imply a specific order of execution; the order of execution of the processes should be determined by their functions and inherent logic.
[0450] An embodiment of the present application further provides a computer-readable storage medium, which stores computer-executable instructions. When the computer-executable instructions are executed, the method executed by the terminal or access network device in the above method embodiment is implemented.
[0451] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed, the method executed by the terminal or access network device in the above method embodiment is implemented.
[0452] The present application also provides a communication system including a terminal or an access network device, wherein the terminal is configured to execute the method executed by the terminal in the above method embodiment, and the access network device is configured to execute the method executed by the access network device in the above method embodiment.
[0453] It should be noted that for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.
[0454] The descriptions of the various embodiments provided in this application can refer to each other. The descriptions of each embodiment have their own focus. For parts not described in detail in a particular embodiment, please refer to the relevant descriptions of other embodiments. For the convenience and brevity of description, for example, the functions and execution steps of the various devices and equipment provided in the embodiments of this application can refer to the relevant descriptions of the method embodiments of this application. The various method embodiments and the various device embodiments can also refer to, be combined with, or quote each other.
[0455] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some or all of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.
Claims
1. A communication method for edge computing, characterized in that: The method comprises: The second edge enabling server EES receives a first message sent by the first EES, and the first message carries the following information: an identifier of a UE group, first information of a first edge application server EAS, the first information including one or more of the following: service area, data center information, performance information; the first EAS is an EAS used by a first UE, and the UE group includes a first UE and a second UE.
2. The method according to claim 1, characterized in that The method further comprises: The second EES receives a second message sent by a second UE, where the second message is used to request to discover the EAS, and the second message carries information about the second UE, where the information about the second UE includes 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.
3. The method according to claim 2, characterized in that The second EES determines, based on the information of the second UE and the first information of the first EAS, whether the second UE uses the first EAS, including: The second EES determines a second EAS based on the information of the second UE; The second EES determines that 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.
4. The method according to claim 3, characterized in that: The first message also carries second information of the first EAS, where the second information includes identification and / or address information. 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 uses the first EAS, the second response message carries second information of the first EAS; If it is determined that the second UE uses the second EAS, the second response message carries second information of the second EAS.
5. The method according to claim 4, characterized in that The method further comprises: If it is determined that the second UE uses the second EAS, the second EES sends second information of the first EAS to the second EAS; If it is determined that the second UE uses the second EAS, the second EES sends second information of the second EAS to the first EES.
6. The method according to claim 4, characterized in that If it is determined that the second UE uses the second EAS, the second response message also carries second information of the first EAS; and the method further includes: If it is determined that the second UE uses the second EAS, the second EES sends second information of the second EAS to the first EES.
7. The method according to claim 6, characterized in that If it is determined that the second UE uses the second EAS, the second response message further carries indication information, where the indication information indicates that the second EAS needs to synchronize application context with the first EAS.
8. The method according to claim 1, characterized in that The method further comprises: The second EES receives a second message sent by a second UE, where the second message is used to request to discover the EAS, and the second message carries information about the second UE, where the information about the second UE includes location information and / or application information corresponding to the second UE; The second EES determines a 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, where the second response message carries the first information of the first EAS and the first information of the second EAS.
9. The method according to claim 8, characterized in that The second response message also carries second information of the first EAS and second information of the second EAS, where the second information includes identification and / or address information.
10. The method according to claim 9, characterized in that The method further comprises: The second EES receives 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 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 second EES sends second information of the second EAS to the first EES.
11. The method according to claim 10, characterized in that The method further comprises: 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 second EES sends second information of the first EAS to the second EAS.
12. A communication method for edge computing, characterized in that: The method comprises: The first edge enabling server EES sends a first message to the second EES, and the first message carries the following information: an identifier of a UE group, first information of a first EAS, the first information including one or more of the following: a service area, data center information, and performance information; the first EAS is an EAS used by a first UE, and the UE group includes a first UE and a second UE.
13. The method according to claim 12, characterized in that The method further comprises: The first EES receives second information of a second EAS sent by the second EES, where the second information includes identification and / or address information, and the second EAS is an EAS used by a second UE; The first EES sends second information of the second EAS to the first EAS.
14. An edge application server EAS discovery method, characterized in that: The method is applied to a second user equipment UE or a chip of the second UE, and the method includes: Sending a second message to a second edge enabling server EES, where the second message is used to request discovery of the EAS, and the second message carries information about the second UE, where the information about the second UE includes location information and / or application information corresponding to the second UE; receiving a second response message corresponding to the second message sent by the second EES, where the second response message carries first information of the first EAS and first information of the second EAS, where the first information includes one or more of the following: a service area, corresponding data center information, and performance information; the first EAS is an EAS used by a first UE, and 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, it is determined that the second UE uses the first EAS or the second EAS.
15. The method according to claim 14, characterized in that The second response message also carries second information of the first EAS and second information of the second EAS, wherein the second information includes identification and / or address information; and the method further includes: If it is determined that the second UE uses the first EAS, communicating with the first EAS based on second information of the first EAS; If it is determined that the second UE uses the second EAS, communication is performed with the second EAS based on second information of the second EAS.
16. The method according to claim 15, characterized in that The method further comprises: Second information and / or indication information of the EAS used by the second UE is sent to the second EES, where the indication information indicates whether the second UE uses the first EAS or whether application context synchronization is required.
17. The method according to claim 16, characterized in that The method further comprises: If it is determined that the second UE uses the second EAS, second information of the first EAS is sent to the second EAS.
18. An edge application server EAS discovery method, characterized in that: The method comprises: The first edge application server EAS receives second information of the second EAS sent by the first edge enabling server EES, where 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 the 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.
19. An edge application server EAS discovery method, characterized in that: The method is applied to a second user equipment UE or a chip of the second UE, and the method includes: Sending a second message to a second edge enabling server EES, where the second message is used to request discovery of the EAS, and the second message carries information about the second UE, where the information about the second UE includes location information and / or application information corresponding to the second UE; receiving a second response message corresponding to the second message sent by the second EES, wherein the second response message carries second information of the second EAS and second information of the first EAS, wherein the second EAS is the EAS used by the second UE, the first EAS is the EAS used by the first UE, and the first UE and the second UE are included in a UE group; and the second information includes identification and / or address information; Second information of the first EAS is sent to the second EAS.
20. The method according to claim 19, characterized in that The second response message also carries indication information, where the indication information indicates that the second EAS needs to synchronize application context with the first EAS.
21. An edge application server EAS discovery method, characterized in that: The method comprises: The second edge application server EAS receives second information of the first EAS sent by the second edge enabling server EES or the second user equipment UE, where 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 the 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.
22. A communication device, characterized in that: Comprising units for executing the method according to any one of claims 1 to 21.
23. A communication device, characterized in that: The method comprises a processor and a memory, wherein the processor and the memory are coupled, and the processor is used to implement the method according to any one of claims 1 to 21.
24. A chip, characterized in that: The method comprises a processor and an interface, wherein the processor and the interface are coupled; the interface is used to receive or output signals, and the processor is used to execute code instructions so that the method described in any one of claims 1 to 21 is executed.
25. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are called by the computer, the computer executes the method according to any one of claims 1 to 21.
26. A communication system, characterized in that: The communication system comprises a first edge enabling server EES and a second EES, wherein: The second EES is used to perform the method of any one of claims 1-11; The first EES is used to perform the method of any one of claims 12-13.
27. The communication system according to claim 26, characterized in that The communication system further comprises a first edge application server EAS and / or a second EAS, wherein: The first EAS is used to perform the method of claim 18; The second EAS is used to perform the method of claim 21.
28. The communication system according to claim 26 or 27, characterized in that: The communication system also includes a second UE, and the second UE is used to execute the method of any one of claims 14-17, or the second UE is used to execute the method of claim 19 or 20.
Citation Information
Patent Citations
Communication method and communication device for edge computing
CN119728677A
Equipment selection method and device
CN114599022A
Method and apparatus for managing information related to edge computing services
CN115486053A
Method and device for selecting edge application server
CN116260795A