Common edge application server bundling in communication networks
Patent Information
- Application Number
- JP2026519906
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-10-02
- Filing Date
- 2024-09-30
- Publication Date
- 2026-10-14
Smart Images
Figure 2026534308000001_ABST
Abstract
Description
Technical Field
[0001] The present invention relates generally to edge computing in communication networks, and in particular, to a mechanism for achieving common Edge Application Server (EAS) bundling through interaction between an Edge Enabler Server (EES) and an Edge Configuration Server (ECS).
Background Art
[0002] Edge Computing (EC) is a concept that allows services to be hosted close to service consumers, providing benefits such as efficient service delivery with significant reduction in end-to-end latency and reduced load on the transport network. The benefits of edge computing enhance the potential of fifth-generation (5G) networks and broaden the prospects for several new and extended use cases, including virtual reality and augmented reality, Internet of Things (IoT), industrial IoT, autonomous driving, real-time multiplayer gaming, and the like.
[0003] The 3rd Generation Partnership Project (3GPP) aims to define an enabling layer for facilitating communication between an Application Client (AC) running on a UE and an Edge Application Server (EAS) deployed on an Edge Data Network (EDN). This includes aspects of service provisioning and EAS discovery. It also aims to provide supporting services such as application context transfer between EASes for service continuity, service activation, and capability exposure APIs towards EASes. Further functions such as application roaming, edge computing federation, and service continuity between edge and cloud may be added.
[0004] Figure 2 shows the architecture for enabling edge applications, as described in 3GPP TS23.558 version 18.4.0. The EDN is the Local Data Network (DN). One or more EAS and EES (Edge Enabler Servers) are contained within the EDN. The ECS (Edge Configuration Server) provides EES-related configuration, including details of the EDN hosting the EES. The UE includes one or more ACs and EECs. One or more EASs, EESs, and ECSs can interact with the 3GPP core network. When the SEAL (Service Enabler Architecture Layer) notification management service is used, the EESs and ECSs interact with the SEAL notification management server, and the SEAL EECs interact with the SEAL notification management clients.
[0005] Figure 3 shows a common EAS (see 3GPP TR23.700-98 version 18.1.0) that includes several EASs (with the same services) deployed in different locations within the same EDN. Application services may be deployed within the EDN in several EASs. Groups of UEs may be anchored to the common EAS to consume the same application services in order to reduce the possibility of inter-EAS data synchronization. If groups of UEs are distributed across different EDNs, inter-EAS data synchronization is still possible because the common EAS in each EDN is used to serve the UEs within its EDN service area.
[0006] To support a common EAS selection for a group of UEs, in addition to ECS functionality, ECS with a central repository will support the storage and provision of common EES and common EAS information.
[0007] Figure 4 shows the architecture for federated support between ECS and ECS-ER (ECS-Edge Repository), which includes repository functionality, as described in 3GPP TS23.558 version 18.4.0.
[0008] An EAS bundle contains a list of EAS instances that should serve the UE application client. There are two types of EAS bundles: proxy type and direct type. Figure 5 shows a proxy type EAS bundle. Figure 6 shows a direct type EAS bundle. EAS instances within a bundle can be discovered or rearranged together depending on the EAS bundle requirements.
[0009] Figure 7 shows EAS deployed by the same ASP (having the same service) in different EDNs. The edge enabler layer supports EAS synchronization. When UEs are connected to the same EAS (i.e., a common EAS) in their corresponding EDNs, information needs to be synchronized between the common EASs. A common EAS in an EDN can serve only one UE. In a special case, one UE is connected to EAS-1X in EDN1 and another UE is connected to EAS-2X in EDN2, and EAS-1X and EAS-2X need to synchronize data (both UEs are in the same group).
[0010] The problematic aspect is that both EAS bundles and common EAS are independent features. There is no support for combining EAS bundles and common EAS to have a common EAS bundle for a group of UEs.
[0011] A further problematic aspect is how to discover and select a common EAS bundle (i.e., a list of bundled EAS that serve a group of UEs).
[0012] A further challenge is how to implement EAS synchronization between EAS bundles, i.e., how to synchronize data across EAS bundles, in order to enable applications where users from different locations need to interact in real time.
[0013] A further problematic aspect is the inefficiency of existing solutions in anchoring multiple UEs to a single EAS. [Overview of the project]
[0014] The present invention is described in the appended claims.
[0015] The objective of this invention is to enable common edge application server (EAS) bundling in communication networks.
[0016] One aspect of the present invention relates to a method implemented by an edge configuration server for common edge application server (EAS) bundling in a communication network. The method includes receiving a first request from an edge enabler server, wherein the first request is an EAS information retrieval request, the first request includes an EAS identifier and an application group identifier, and the first request includes a directive for at least one of a bundled EAS identifier list, a main EAS identifier, or an EAS bundle identifier; determining first EAS information for at least one of the identifiers received in the first request, including at least one EAS serving the application group; and transmitting an EAS information retrieval response from the edge configuration server to the edge enabler server, including a directive for the determined first EAS information. In some embodiments, the method includes receiving a second request from an edge enabler server, wherein the second request is a common EAS information storage request, and the second request includes at least one of EDN information, EES identifiers, EAS identifiers, EAS endpoints, and application group identifiers, and the second request includes instructions for at least one of bundled EAS identifiers and endpoint lists, main EAS identifiers, or EAS bundle identifiers; determining second EAS information in the same EDN, for at least one of the identifiers received in the second request, including at least one EAS serving an application group; and sending a common EAS information storage response from the edge enabler server to the edge enabler server, including instructions for the second EAS information. In some embodiments, the instructions for the bundled EAS identifier list are bundled EAS identifiers.In some embodiments, the method further includes, during EAS discovery, sending an EAS discovery request from the Edge Enabler Client (EEC) to the EES, which includes at least one of an EAS bundle identifier, a bundled EAS identifier list, or an application group identifier. In some embodiments, the method further includes, based on the received EAS discovery request, sending an EAS information storage request from the EES to the ECS-ER. In some embodiments, if the ECS-ER identifies existing common EAS information for an application group in the same EDN, the method further includes sending an instruction from the ECS-ER to the EES recommending the use of at least one common EAS. In some embodiments, the method further includes sending an instruction from the EEC to the Application Client (AC) regarding the received EAS information, thereby enabling the AC to connect to at least one EAS included in the EAS information. In some embodiments, the EAS information acquisition response includes a list of EAS endpoints and their associated EAS endpoints corresponding to the requested EAS identifiers. In some embodiments, the common EAS information storage response includes a common EAS endpoint and its associated EAS endpoints corresponding to the requested EAS identifier. In some embodiments, the edge enabler server is an edge enabler server (EES), and the edge configuration server is an edge configuration server (ECS-ER) with an edge repository.
[0017] One aspect of the present invention relates to a method implemented by an edge enabler server for common edge application server (EAS) bundling in a communication network. The method includes sending a first request from the edge enabler server to an edge configuration server, wherein the first request is an EAS information retrieval request, the first request includes an EAS identifier and an application group identifier, and the first request includes a directive for at least one of a bundled EAS identifier list, a main EAS identifier, or an EAS bundle identifier; and the edge enabler server receiving an EAS information retrieval response from the edge configuration server, which includes a directive for first EAS information, for at least one of the identifiers in the first request, including at least one EAS serving an application group. In some embodiments, the method further includes sending a second request from an edge enabler server to an edge configuration server, wherein the second request is a common EAS information storage request, and the second request includes at least one of EDN information, EES identifiers, EAS identifiers, EAS endpoints, and application group identifiers, and the second request includes instructions for at least one of bundled EAS identifiers and endpoint lists, main EAS identifiers, or EAS bundle identifiers; and the edge enabler server further includes receiving a common EAS information storage response from the edge configuration server, which includes instructions for a second EAS information including at least one EAS serving an application group for at least one of the identifiers in the second request, within the same EDN. In some embodiments, the instructions for bundled EAS identifier lists are bundled EAS identifiers. In some embodiments, the method further includes sending an EAS discovery request from an edge enabler client (EEC) to an EES, which includes at least one of EAS bundle identifiers, bundled EAS identifier lists, or application group identifiers. In some embodiments, the method further includes sending an EAS information storage request from the EES to the ECS-ER based on the received EAS discovery request.In some embodiments, the method further includes, if the ECS-ER identifies existing common EAS information for an application group in the same EDN, sending an instruction from the ECS-ER to the EES recommending the use of at least one common EAS. In some embodiments, the method further includes sending an instruction from the EEC to an application client (AC) regarding the received EAS information, thereby enabling the AC to connect to at least one EAS included in the EAS information. In some embodiments, the EAS information retrieval response includes a list of EAS endpoints and their associated EAS endpoints corresponding to the requested EAS identifier. In some embodiments, the common EAS information storage response includes common EAS endpoints and their associated EAS endpoints corresponding to the requested EAS identifier. In some embodiments, the edge enabler server is an edge enabler server (EES), and the edge configuration server is an edge configuration server (ECS-ER) with an edge repository.
[0018] Other aspects of the present invention relate to mobile network nodes, in particular edge enabler servers (116, 1400) and edge configuration servers (117, 1300) configured to implement the respective methods described herein. Other aspects of the present invention relate to computer programs and computer program products.
[0019] In some embodiments, the edge enabler server is an edge enabler server (EES). In some embodiments, the edge configuration server is an edge configuration server (ECS-ER) with an edge repository.
[0020] Advantageously, the solutions disclosed herein provide a method for facilitating interaction between an edge enabler server (EES) and an edge configuration server (ECS-ER) with an edge repository for common edge application server (EAS) bundling, which gives a more efficient way of managing edge computing resources in a communication network.
[0021] Furthermore, the solutions disclosed herein enable communication networks to achieve optimized utilization of network resources by bundling edge application servers (EAS) that serve the same group of applications.
[0022] Furthermore, the solutions disclosed herein enable reduced end-to-end latency by facilitating common EAS bundling closer to the service consumer, which is particularly beneficial for applications requiring real-time data processing, such as online gaming or autonomous driving.
[0023] Additional objectives, features, and advantages of the concepts disclosed herein may be apparent from the following description, claims, and drawings, or may be learned through the practice of the described art and concepts described herein.
[0024] To best illustrate the forms in which the disclosed concepts may be implemented, and to define other purposes, advantages, and features of this disclosure, a more detailed description is provided below and shown in the accompanying drawings. Understanding that these drawings merely illustrate exemplary embodiments of the invention and should not be considered limitations of scope, examples are described and illustrated with additional specificities and details by using the accompanying drawings. [Brief explanation of the drawing]
[0025] [Figure 1]FIG. 1 illustrates an exemplary networked system in accordance with certain embodiments of the solutions described herein. [Figure 2] FIG. 2 is an exemplary block diagram illustrating a network entity in a mobile communications network in accordance with certain embodiments of the solutions described herein. [Figure 3] FIG. 3 is an exemplary block diagram illustrating a network entity in a mobile communications network in accordance with certain embodiments of the solutions described herein. [Figure 4] FIG. 4 is an exemplary block diagram illustrating a network entity in a mobile communications network in accordance with certain embodiments of the solutions described herein. [Figure 5] FIG. 5 is an exemplary block diagram illustrating a network entity in a mobile communications network in accordance with certain embodiments of the solutions described herein. [Figure 6] FIG. 6 is an exemplary block diagram illustrating a network entity in a mobile communications network in accordance with certain embodiments of the solutions described herein. [Figure 7] FIG. 7 is an exemplary block diagram illustrating a network entity in a mobile communications network in accordance with certain embodiments of the solutions described herein. [Figure 8] FIG. 8 is an exemplary signaling diagram illustrating a procedure in accordance with certain embodiments of the solutions described herein. [Figure 9] FIG. 9 is an exemplary signaling diagram illustrating a procedure in accordance with certain embodiments of the solutions described herein. [Figure 10] FIG. 10 is an exemplary signaling diagram illustrating a procedure in accordance with certain embodiments of the solutions described herein. [Figure 11] FIG. 11 is an exemplary flowchart illustrating a method performed by a mobile network node in accordance with certain embodiments of the solutions described herein. [Figure 12]This is an exemplary flowchart illustrating how a particular embodiment of the solution described herein is implemented by a mobile network node. [Figure 13] This is an exemplary block diagram of a mobile network node configured according to a specific embodiment of the solution described herein. [Figure 14] This is an exemplary block diagram of a mobile network node configured according to a specific embodiment of the solution described herein. [Figure 15] This figure shows an example of a virtualized environment. [Modes for carrying out the invention]
[0026] Next, the present invention will be described in detail below with reference to the accompanying drawings illustrating examples of embodiments or implementations of the present invention. However, the present invention may be embodied or implemented in many different forms and should not be construed as being limited to the embodiments described herein. Rather, these embodiments are provided so as to ensure that this disclosure is thorough and complete and that the scope of the invention is fully conveyed to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. It can be implicitly assumed that components from one embodiment exist / are used in another embodiment. These embodiments of the disclosed subject matter are presented as teaching examples and should not be construed as limiting the scope of the disclosed subject matter. For example, some details of the embodiments described may be modified, omitted or expanded without departing from the scope of the described subject matter.
[0027] The exemplary embodiments described herein occur in the context of a communications network, including communications networks that conform to and / or optionally incorporate aspects of fifth-generation (5G) architectures, but are not limited thereto. Figure 1 shows an exemplary networked system 100 according to an exemplary embodiment of the present disclosure. In detail, Figure 1 shows a user equipment (UE) 101 which may communicate with a (radio) access network (RAN) 102, as well as an access and mobility management function (AMF) 106, and a user plane function (UPF) 103. The AMF 106 may communicate with core network services, including a session management function (SMF) 107 and a policy control function (PCF) 111. The core network services may also communicate with an application server / application function (AS / AF) 113. Other networked services also include a Network Slice Selection Function (NSSF) 108, an Authentication Server Function (AUSF) 105, a User Data Management (UDM) 112, a Network Exposure Function (NEF) 109, a Network Repository Function (NRF) 110, an Integrated Data Repository (UDR) 114, a Network Data Analysis Function (NWDAF) 115, and a Data Network (DN) 104. In some exemplary implementations of embodiments of this disclosure, each entity in the networked system 100 is considered a Network Function (NF). One or more additional instances of NFs may be incorporated into the networked system.
[0028] The solutions described herein are intended to enable common edge application server (EAS) bundling in communication networks.
[0029] This disclosure provides a method for common edge application server (EAS) bundling in a communication network. The method includes sending a first request from an edge enabler server to an edge configuration server, wherein the first request is an EAS information retrieval request, the first request includes an EAS identifier and an application group identifier, and the first request includes a directive for at least one of a bundled EAS identifier list, a main EAS identifier, or an EAS bundle identifier; the edge configuration server determines first EAS information for at least one of the identifiers received in the first request, including at least one EAS serving the application group; and the edge configuration server sends an EAS information retrieval response to the edge enabler server, including a directive for the determined first EAS information. In some embodiments, the method further includes sending a second request from an edge enabler server to an edge configuration server, wherein the second request is a common EAS information storage request, and the second request includes at least one of EDN information, EES identifiers, EAS identifiers, EAS endpoints, and application group identifiers, and the second request includes instructions for at least one of bundled EAS identifiers and endpoint lists, main EAS identifiers, or EAS bundle identifiers; determining, at the edge configuration server, second EAS information including at least one EAS serving an application group for at least one of the identifiers received in the second request, within the same EDN, in particular, determining that the at least one EAS serving the application group is a common EAS for bundling; and sending a common EAS information storage response from the edge configuration server to the edge enabler server, including instructions for the second EAS information. In some embodiments, the instructions for the bundled EAS identifier list are bundled EAS identifiers.In some embodiments, the method further includes, during EAS discovery, sending an EAS discovery request from the Edge Enabler Client (EEC) to the EES, which includes at least one of an EAS bundle identifier, a bundled EAS identifier list, or an application group identifier. In some embodiments, the method further includes, based on the received EAS discovery request, sending an EAS information storage request from the EES to the ECS-ER. In some embodiments, if the ECS-ER identifies existing common EAS information for an application group in the same EDN, the method further includes sending an instruction from the ECS-ER to the EES recommending the use of at least one common EAS. In some embodiments, the method further includes sending an instruction from the EEC to the Application Client (AC) regarding the received EAS information, thereby enabling the AC to connect to at least one EAS included in the EAS information. In some embodiments, the EAS information acquisition response includes a list of EAS endpoints and their associated EAS endpoints corresponding to the requested EAS identifiers. In some embodiments, the common EAS information storage response includes a common EAS endpoint and its associated EAS endpoints corresponding to the requested EAS identifier. In some embodiments, the edge enabler server is an edge enabler server (EES), and the edge configuration server is an edge configuration server (ECS-ER) with an edge repository.
[0030] This disclosure also provides mobile network nodes, in particular edge enabler servers (116, 1400) and edge configuration servers (117, 1300) configured to implement the respective methods described herein. In some embodiments, the edge enabler server is an edge enabler server (EES) 116. In some embodiments, the edge configuration server is an edge configuration server (ECS-ER) 117 having an edge repository.
[0031] This disclosure also provides a corresponding computer program, and a computer program product comprising code, for example in the form of a computer program, which, when run on the processing circuit of a mobile network node, causes the mobile network node to implement the disclosed method.
[0032] Advantageously, the solutions disclosed herein provide a method for facilitating interaction between an edge enabler server (EES) and an edge configuration server (ECS-ER) with an edge repository for common edge application server (EAS) bundling, which gives a more efficient way of managing edge computing resources in a communication network.
[0033] Furthermore, the solutions disclosed herein enable communication networks to achieve optimized utilization of network resources by bundling edge application servers (EAS) that serve the same group of applications.
[0034] Furthermore, the solutions disclosed herein enable reduced end-to-end latency by facilitating common EAS bundling closer to the service consumer, which is particularly beneficial for applications requiring real-time data processing, such as online gaming or autonomous driving.
[0035] The solutions and features included therein are further explained below.
[0036] During the initial selection of EAS bundles for group members, multiple EAS instances within the bundle may be pre-selected by the EES or EEC, and these bundled EAS instances, per EDN and per application group, need to be remembered when the EES interacts with the ECS-ER.
[0037] It is possible to have three options. a) Each related EAS service has its own application group. b) All related EAS services depend on the application group of the main EAS service. c) All related EAS services have an application group for the bundle.
[0038] To support options b and c, the main EAS ID or EAS bundle ID must be stored in ECS-ER along with other data.
[0039] When another application group member triggers EAS discovery for all EAS services in a bundle, the previously stored EAS bundle information is used during the interaction between EES and ECS-ER to anchor the group member to the same EAS instance (one or more) in the bundle.
[0040] The same is required in EAS synchronization. More query filters, such as EAS bundle IDs, may be supported.
[0041] This disclosure focuses on the dialogue between EES and ECS-ER regarding a common EAS bundle in order to do the following: 1. Support more query filters for common EAS bundles (e.g., EAS bundle ID). 2. The common EAS information storage procedure will support bundle relationship information (e.g., EAS bundle ID).
[0042] The following diagrams illustrating an example of a solution embodiment are described in detail.
[0043] Figure 8 is a signaling diagram showing an exemplary embodiment in which two UEs in a group are anchored to a common EAS in the EDN in order to select a common EAS for the UE application group. The procedure is carried out by edge enabler servers (116, 1400) and edge configuration servers (117, 1300), which are configured to carry out each of the methods described herein. In some embodiments, the edge enabler server is an edge enabler server (EES) 116. In some embodiments, the edge configuration server is an edge configuration server (ECS-ER) 117 with an edge repository.
[0044] Common EAS pre-selection can be performed by either the EES or the EEC. If the EEC is the one pre-selecting the common EAS, the EEC sends an EAS information provisioning request to the EES with the request type set in "EAS selection request". If the EES is the one pre-selecting the common EAS, the EEC sends an EAS discovery request to the EES.
[0045] The procedure includes the following steps: Step 1. During EAS discovery, EEC1 sends an EAS discovery request to EES1 that includes a list of EAS bundle IDs or EAS IDs in the bundle and an application group ID, or an EAS information provisioning request that includes (one or more) selected EAS endpoints and an application group ID. Step 2. EES1 either pre-selects an EAS or uses one or more received EAS endpoints, and then sends an EAS information storage request message to ECS-ER. The request message also includes the bundled EAS ID and endpoint list, the main EAS ID, or the EAS bundle ID. Step 3. No existing common EAS information is found, therefore ECS-ER creates new common EAS information for the application group. Step 4. The ECS-ER responds to the EAS information storage request with a result indicating OK to proceed with (one or more) requested EAS. Steps 5-7. Based on the received EAS information, EES1 responds to EEC1 with an EAS discovery request or EAS information provisioning request for the selected EAS, and as a result, AC1 connects to the (one or more) selected EAS after being informed by EEC1. Step 8. During EAS discovery, EEC2 sends an EAS discovery request to EES2 that includes a list of EAS bundle IDs or EAS IDs in the bundle and an application group ID, or an EAS information provisioning request to EES2 that includes (one or more) selected EAS endpoints and an application group ID. Step 9. EES2 either pre-selects an EAS or uses one or more received EAS endpoints, and then sends an EAS information storage request message to ECS-ER. The request message also includes the bundled EAS ID and endpoint list, the main EAS ID, or the EAS bundle ID. Step 10. ECS-ER finds existing common EAS information for application groups within the same EDN. Step 11. ECS-ER responds with a result indicating a recommendation to use one or more common EAS (including relevant EES information), which is one or more EAS selected by EES1. Steps 12-14. Based on the received EAS information, EES2 responds to EEC2 with an EAS discovery request or an EAS information provisioning request in one or more common EASs, and as a result, AC1 connects to one or more common EASs. EEC2 may then contact EES1 for subsequent procedures (e.g., EEC registration, ACR subscription).
[0046] Figure 9 is a signaling diagram showing the procedure for obtaining EAS information. The procedure is performed by edge enabler servers (116, 1400) and edge configuration servers (117, 1300), which are configured to perform each of the methods described herein. In some embodiments, the edge enabler server is an edge enabler server (EES) 116. In some embodiments, the edge configuration server is an edge configuration server (ECS-ER) 117 with an edge repository.
[0047] The procedure includes the following steps: Step 1. EES sends an EAS information request message to ECS-ER. The request message includes the EAS ID and application group ID, and may include a bundled EAS ID list and the main EAS ID or EAS bundle ID. Step 2. Upon receiving a request, the ECS-ER checks whether there are (one or more) stored EAS serving the application group for the EAS ID, bundled EAS ID list (if received), and main EAS ID (if received) or EAS bundle ID (if received). Step 3. If the request is processed successfully, the ECS-ER responds to the EES with the EAS information identified in Step 2.
[0048] Figure 10 is a signaling diagram showing the procedure for common EAS information storage. The procedure is performed by edge enabler servers (116, 1400) and edge configuration servers (117, 1300), which are configured to perform each of the methods described herein. In some embodiments, the edge enabler server is an edge enabler server (EES) 116. In some embodiments, the edge configuration server is an edge configuration server (ECS-ER) 117 with an edge repository.
[0049] The procedure includes the following steps: Step 1. EES sends a common EAS information storage request message to ECS-ER. The request message includes EDN information, EES ID, EAS ID, EAS endpoint, and application group ID, and may include a bundled EAS ID and endpoint list, main EAS ID, or EAS bundle ID. Step 2. Upon receiving a request, ECS-ER checks if there is a stored EAS serving the application group within the same EDN, for the EAS ID, bundled EAS ID list (if received), and main EAS ID (if received) or EAS bundle ID (if received). If no common EAS is identified, ECS-ER stores the received information for subsequent binding requests. Step 3. The ECS-ER responds to the EES with a common EAS information storage response message. The ECS-ER may reject or accept the request based on the common EAS information identified in Step 2.
[0050] Table 1 describes the information elements related to the request for EAS information from EES to ECS-ER. Table 1: EAS Information Acquisition Response TIFF2026534308000002.tif74170
[0051] Table 2 describes the information elements for the EAS information acquisition response from ECS-ER to EES. Table 2: EAS Information Acquisition Response TIFF2026534308000003.tif53170
[0052] Table 3 describes the information elements for common EAS information storage requests from EES to ECS-ER. Table 3: Common EAS information storage requirements TIFF2026534308000004.tif125170
[0053] Table 4 describes the information elements for the common EAS information memory response from ECS-ER to EES. Table 4: Common EAS Information Memory Response TIFF2026534308000005.tif38170
[0054] The following flowchart provides a detailed explanation of an example of a solution implementation.
[0055] The embodiments correspond to those implemented by edge enabler servers (116, 1400) and edge configuration servers (117, 1300), and methods involving them.
[0056] Figure 11 is a flowchart illustrating the method implemented by the edge configuration server for common edge application server (EAS) bundling in a communication network.
[0057] In step S-1101, the edge configuration server receives a first request from the edge enabler server, the first request being an EAS information retrieval request, the first request including an EAS identifier and an application group identifier, and the first request including an instruction for at least one of the following: a bundled EAS identifier list, a main EAS identifier, or an EAS bundle identifier.
[0058] In step S-1102, the edge configuration server determines first EAS information, which includes at least one EAS serving the application group, for at least one of the identifiers received in the first request.
[0059] In step S-1103, the edge configuration server sends an EAS information retrieval response to the edge enabler server, which includes instructions for the determined first EAS information.
[0060] In step S-1104, the edge configuration server receives a second request from the edge enabler server, the second request being a common EAS information storage request, the second request including at least one of EDN information, EES identifier, EAS identifier, EAS endpoint, and application group identifier, and the second request including instructions for at least one of bundled EAS identifiers and endpoint list, main EAS identifier, or EAS bundle identifier.
[0061] In step S-1105, the edge configuration server determines second EAS information, which includes at least one EAS serving an application group for at least one of the identifiers received in the second request within the same EDN.
[0062] In step S-1106, the edge configuration server sends a common EAS information storage response to the edge enabler server, which includes instructions for the second EAS information.
[0063] In some embodiments, the instruction for the bundled EAS identifier list is the bundled EAS identifier.
[0064] In some embodiments, the method further includes, during EAS discovery, sending an EAS discovery request from the Edge Enabler Client (EEC) to the EES, which includes at least one of the following: an EAS bundle identifier, a bundled EAS identifier list, or an application group identifier.
[0065] In some embodiments, the method further includes sending an EAS information storage request from the EES to the ECS-ER based on the received EAS discovery request.
[0066] In some embodiments, the method further includes, if ECS-ER identifies existing common EAS information for an application group in the same EDN, sending an instruction from ECS-ER to EES recommending the use of at least one common EAS.
[0067] In some embodiments, the method further includes transmitting instructions from the EEC to an application client (AC) for the received EAS information, thereby enabling the AC to connect to at least one EAS contained in the EAS information.
[0068] In some embodiments, the EAS information retrieval response includes a list of EAS endpoints and their associated EAS endpoints corresponding to the requested EAS identifier.
[0069] In some embodiments, the common EAS information storage response includes a common EAS endpoint and its associated EAS endpoints corresponding to the requested EAS identifier.
[0070] In some embodiments, the edge enabler server is an edge enabler server (EES), and the edge configuration server is an edge configuration server (ECS-ER) with an edge repository.
[0071] Figure 12 is a flowchart illustrating how common edge application server (EAS) bundling in a communication network is performed by an edge enabler server.
[0072] In step S-1201, the edge enabler server sends a first request to the edge configuration server, the first request being an EAS information retrieval request, the first request including an EAS identifier and an application group identifier, and the first request including a designation for at least one of the following: a bundled EAS identifier list, a main EAS identifier, or an EAS bundle identifier.
[0073] In step S-1202, the edge enabler server receives an EAS information retrieval response from the edge configuration server, which includes instructions for first EAS information, including at least one EAS that serves an application group for at least one of the identifiers in the first request.
[0074] In step S-1203, the edge enabler server sends a second request to the edge configuration server, the second request being a common EAS information storage request, the second request including at least one of EDN information, EES identifier, EAS identifier, EAS endpoint, and application group identifier, and the second request including at least one of bundled EAS identifier and endpoint list, main EAS identifier, or EAS bundle identifier.
[0075] In step S-1204, the edge enabler server receives a common EAS information storage response from the edge configuration server, which includes instructions for a second EAS information containing at least one EAS serving an application group for at least one of the identifiers in the second request, within the same EDN.
[0076] In some embodiments, the instruction for the bundled EAS identifier list is the bundled EAS identifier.
[0077] In some embodiments, the method further includes, during EAS discovery, sending an EAS discovery request from the Edge Enabler Client (EEC) to the EES, which includes at least one of the following: an EAS bundle identifier, a bundled EAS identifier list, or an application group identifier.
[0078] In some embodiments, the method further includes sending an EAS information storage request from the EES to the ECS-ER based on the received EAS discovery request.
[0079] In some embodiments, the method further includes, if ECS-ER identifies existing common EAS information for an application group in the same EDN, sending an instruction from ECS-ER to EES recommending the use of at least one common EAS.
[0080] In some embodiments, the method further includes transmitting instructions from the EEC to an application client (AC) for the received EAS information, thereby enabling the AC to connect to at least one EAS contained in the EAS information.
[0081] In some embodiments, the EAS information retrieval response includes a list of EAS endpoints and their associated EAS endpoints corresponding to the requested EAS identifier.
[0082] In some embodiments, the common EAS information storage response includes a common EAS endpoint and its associated EAS endpoints corresponding to the requested EAS identifier.
[0083] In some embodiments, the edge enabler server is an edge enabler server (EES), and the edge configuration server is an edge configuration server (ECS-ER) with an edge repository.
[0084] Figure 13 is a block diagram showing the elements of a mobile network node 1300 in a mobile communication network. In some embodiments, the mobile network node 1300 is an ECS-ER117. As shown, the mobile network node may include a network interface circuit 1301 (also called a network interface) configured to provide communication with the core network and / or other nodes in the network. The mobile network node may also include a processing circuit 1302 (also called a processor) coupled to the network interface circuit, and a memory circuit 1303 (also called memory) coupled to the processing circuit. The memory circuit 1303 may include computer-readable program code that, when executed by the processing circuit 1302, causes the processing circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, the processing circuit 1302 may be specified to include memory such that a separate memory circuit is not required. As described herein, the operation of the mobile network node may be performed by the processing circuit 1302 and / or the network interface circuit 1301. For example, the processing circuit 1302 may control the network interface circuit 1301 to send communications to one or more other network nodes through the network interface circuit 1301 and / or receive communications from one or more other network nodes through the network interface circuit. Furthermore, modules may be stored in memory 1303, and these modules may provide instructions such that when the module's instructions are executed by the processing circuit 1302, the processing circuit 1302 performs its respective operations (for example, operations described below with respect to exemplary embodiments relating to a core network node).
[0085] Figure 14 is a block diagram showing the elements of a mobile network node 1400 of a mobile communications network. In some embodiments, the mobile network node 1400 is an EES 116. As shown, the mobile network node may include a network interface circuit 1401 (also called a network interface) configured to provide communication with the core network and / or other nodes in the network. The mobile network node may also include a processing circuit 1402 (also called a processor) coupled to the network interface circuit, and a memory circuit 1403 (also called memory) coupled to the processing circuit. The memory circuit 1403 may include computer-readable program code that, when executed by the processing circuit 1402, causes the processing circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, the processing circuit 1402 may be specified to include memory such that a separate memory circuit is not required. As described herein, the operation of the mobile network node may be performed by the processing circuit 1402 and / or the network interface circuit 1401. For example, the processing circuit 1402 may control the network interface circuit 1401 to send communications to one or more other network nodes through the network interface circuit 1401 and / or receive communications from one or more other network nodes through the network interface circuit. Furthermore, modules may be stored in memory 1403, and these modules may provide instructions such that when the module's instructions are executed by the processing circuit 1402, the processing circuit 1402 performs its respective operations (for example, operations described below with respect to exemplary embodiments relating to a core network node).
[0086] Figure 15 is a block diagram showing a virtualized environment 1500 in which functions implemented by several embodiments may be virtualized. In this context, virtualization means creating a virtual version of a device or apparatus, which may include virtualizing hardware platforms, storage devices, and networking resources. The virtualization used herein may apply to any device or its components described herein and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components, executed by one or more virtual machines (VMs) implemented in one or more virtualized environments 1500 hosted by one or more hardware nodes, such as network nodes, UEs, core network nodes, or hardware computing devices acting as hosts. Furthermore, in embodiments in which the virtual nodes do not require wireless connectivity (e.g., core network nodes or hosts), the nodes may be fully virtualized. In some embodiments, the virtualized environment 1500 includes components defined by the O-RAN Alliance, such as an O-cloud environment organized by a service management and orchestration framework via an O-2 interface.
[0087] Application 1502 (which may alternatively be referred to as a software instance, virtual appliance, network function, virtual node, virtual network function, etc.) runs in the virtualized environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.
[0088] Hardware 1504 includes processing circuits, memory for storing software and / or instructions executable by the hardware processing circuits, and / or other hardware devices described herein, such as network interfaces and input / output interfaces. The software is executed by the processing circuits to instantiate one or more virtualization layers 1506 (also called a hypervisor or virtual machine monitor (VMM)), providing VM1508a and 1508b (one or more of which are commonly referred to as VM1508), and / or may implement any of the functions, features, and / or benefits described with respect to some embodiments described herein. The virtualization layer 1506 may present VM1508 with a virtual operating platform that looks like networking hardware.
[0089] VM1508 features virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be powered by the corresponding virtualization layer 1506. Different embodiments of instances of the virtual appliance 1502 may be implemented on one or more of the VM1508, and the implementation may be carried out in different ways. Hardware virtualization is referred to as network function virtualization (NFV) in several contexts. NFV can be used to consolidate many types of network equipment onto industry-standard high-volume server hardware, physical switches, and physical storage, which may reside in data centers and customer premises equipment.
[0090] In the context of NFV, VM1508 can be a software implementation of a physical machine, where programs run as if they were running on a physical, non-virtualized machine. Each VM1508 and its portion of the hardware 1504 on which it runs, whether that hardware is dedicated to that VM and / or shared by that VM with other VMs in the VM, form a separate virtual network element. Furthermore, in the context of NFV, the virtual network function is responsible for handling specific network functions running in one or more VM1508s on the hardware 1504, and corresponds to application 1502.
[0091] Hardware 1504 may be implemented in a standalone network node with general or specific components. Hardware 1504 may implement some functions through virtualization. Alternatively, hardware 1504 may be part of a larger cluster of hardware (such as in a data center or CPE) where many hardware nodes cooperate and are managed via management and orchestration 1510, which oversees the lifecycle management of applications 1502. In some embodiments, hardware 1504 is coupled to one or more radio units, each including one or more transmitters and one or more receivers, which may be coupled to one or more antennas. The radio units may communicate directly with other hardware nodes via one or more suitable network interfaces and may be used in combination with virtual components to provide a virtual node with radio capabilities, such as a radio access node or base station. In some embodiments, some signaling may be provided using a control system 1512, which may be used alternatively for communication between hardware nodes and radio units.
[0092] Embodiments within the scope of the present invention may also include computer-readable media for carrying computer-executable instructions or data structures, or on which computer-executable instructions or data structures are stored. Such computer-readable media may be any available medium accessible by a general-purpose or dedicated computer. Such tangible computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code means in the form of computer-executable instructions or data structures. When information is transferred to or provided to a computer via a network or another communication connection (either wired, wireless, or a combination thereof), the computer appropriately considers that connection as computer-readable media. Therefore, any such connection is appropriately referred to as computer-readable media. The above combinations should also be included within the scope of tangible computer-readable media.
[0093] Computer executable instructions include instructions and data that cause a general-purpose computer, a dedicated computer, or a dedicated processing device to perform a certain function or group of functions. Computer executable instructions also include program modules that are executed by computers, either standalone or in a networked environment. Generally, program modules include routines, programs, objects, components, and data structures that perform a particular task or implement a particular abstract data type. Computer executable instructions, associated data structures, and program modules represent examples of program code means for performing steps of the methods disclosed herein. A particular sequence of such executable instructions or associated data structures represents an example of a corresponding action for implementing the function described in such step.
[0094] Those skilled in the art will understand that other embodiments of the present invention can be practiced in network computing environments with many types of computer system configurations, including personal computers, handheld devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, and mainframe computers. Embodiments can also be practiced in distributed computing environments where tasks are performed by local and remote processing devices linked through a communication network (either by wired links, wireless links, or a combination thereof). In a distributed computing environment, program modules can reside in both local and remote memory storage devices.
[0095] Communication at various stages of the described system can be carried out through local area networks, token ring networks, the internet, corporate intranets, 802.11 series radio signals, fiber optic networks, radio or microwave transmissions, and the like. While the underlying communication technologies may change, the basic principles described herein remain applicable.
[0096] The various embodiments described above are provided as examples only and should not be construed as limiting the invention. For example, the principles herein can be applied to any remotely controlled device. Furthermore, those skilled in the art will recognize that communication between remotely controlled devices is not limited to communication over a local area network and may include communication over infrared channels, Bluetooth, or any other suitable communication interface. Those skilled in the art will readily recognize various modifications and changes that can be made to the invention without following the exemplary embodiments and applications shown and described herein, and without departing from the scope of this disclosure.
[0097] The terminology used herein is for illustrative purposes only and does not limit the exemplary embodiments. The singular forms “a,” “an,” and “the” used herein also include the plural form unless the context explicitly indicates otherwise. The terms “includes,” “including,” “comprises,” and “comprising” used herein specify the presence of a described feature, complete, step, operation, element, or component, and combinations thereof, but do not exclude the presence or addition of one or more other features, complete, step, operation, element, or component, and combinations thereof. Furthermore, all terms used in the claims should be interpreted according to their common meaning in the art unless otherwise expressly provided herein. All references to “one (a / an) / its (the) element, apparatus, component, means, module, step, etc.” should be openly interpreted as referring to at least one instance of that element, apparatus, component, means, module, step, etc., unless otherwise expressly stated. None of the steps of any method disclosed herein need to be performed in the exact order disclosed unless expressly stated otherwise.
[0098] acronym 3GPP Third Generation Partnership Project 5G (5th generation) AC Application Client API Application Programming Interface ASP Application Service Provider DN Data Network DNAI (Data Network Access Identifier) DNN Data Network Name EC edge computing EAS Edge Application Server ID identifier ECS Edge Configuration Server ECS-ER Edge Configuration Server - Edge Repository EDN (Edge Data Network) EEC Edge Enabler Client EES Edge Enabler Server IIoT (Industrial Internet of Things) IoT (Internet of Things) SEAL Service Enabler Architecture Layer TR technical report TS Technical Specifications UE User Equipment
Claims
1. A method for bundling common edge application servers (EAS) in a communication network, wherein the method is: Sending a first request from the edge enabler server to the edge configuration server (S-1201), wherein the first request is an EAS information retrieval request, the first request includes an EAS identifier and an application group identifier, and the first request includes an instruction for at least one of a bundled EAS identifier list, a main EAS identifier, or an EAS bundle identifier (S-1201), The edge configuration server determines first EAS information, which includes at least one EAS serving an application group, for at least one of the identifiers received in the first request (S-1102), The edge configuration server transmits an EAS information acquisition response to the edge enabler server, which includes an instruction for the determined first EAS information (S-1103). Methods that include...
2. Sending a second request from the edge enabler server to the edge configuration server (S-1203), wherein the second request is a common EAS information storage request, the second request includes at least one of EDN information, EES identifier, EAS identifier, EAS endpoint, and application group identifier, and the second request includes an instruction for at least one of bundled EAS identifier and endpoint list, main EAS identifier, or EAS bundle identifier (S-1203), The edge configuration server determines second EAS information (S-1105) which includes at least one EAS serving the application group for at least one of the identifiers received in the second request within the same EDN, and in particular determines second EAS information (S-1105) which includes at least one EAS serving the application group which is a common EAS for the bundle. The edge configuration server transmits a common EAS information storage response, including the instruction for the second EAS information, to the edge enabler server (S-1106). The method according to claim 1, further comprising:
3. The method according to claim 1 or 2, wherein the instruction for the bundled EAS identifier list is a bundled EAS identifier.
4. The method according to any one of claims 1 to 3, further comprising sending an EAS discovery request from an edge enabler client (EEC) to an EES, which includes at least one of an EAS bundle identifier, a bundled EAS identifier list, or an application group identifier, during EAS discovery.
5. The method according to any one of claims 1 to 4, further comprising transmitting an EAS information storage request from the EES to the ECS-ER based on the received EAS discovery request.
6. The method according to any one of claims 1 to 5, further comprising the ECS-ER sending an instruction to the EES recommending the use of at least one common EAS when the ECS-ER identifies existing common EAS information for the application group in the same EDN.
7. The method according to any one of claims 1 to 6, further comprising transmitting instructions for the received EAS information from the EEC to an application client (AC), thereby enabling the AC to connect to at least one EAS included in the EAS information.
8. The method according to any one of claims 1 to 7, wherein the EAS information retrieval response includes a list of EAS endpoints and associated EAS endpoints corresponding to the requested EAS identifier.
9. The method according to any one of claims 1 to 8, wherein the common EAS information storage response includes a common EAS endpoint and its associated EAS endpoints corresponding to the requested EAS identifier.
10. The method according to any one of claims 1 to 9, wherein the edge enabler server is an edge enabler server (EES) and the edge configuration server is an edge configuration server (ECS).
11. A method for common edge application server (EAS) bundling in a communication network, which is performed by an edge configuration server, wherein the method is: The edge configuration server receives a first request from the edge enabler server (S-1101), wherein the first request is an EAS information acquisition request, the first request includes an EAS identifier and an application group identifier, and the first request includes an instruction for at least one of a bundled EAS identifier list, a main EAS identifier, or an EAS bundle identifier (S-1101), The edge configuration server determines first EAS information, which includes at least one EAS serving an application group, for at least one of the identifiers received in the first request (S-1102), The edge configuration server transmits an EAS information acquisition response to the edge enabler server, which includes an instruction for the determined first EAS information (S-1103). Methods that include...
12. The edge configuration server receives a second request from the edge enabler server (S-1104), wherein the second request is a common EAS information storage request, and the second request includes at least one of EDN information, EES identifier, EAS identifier, EAS endpoint, and application group identifier, and the second request includes an instruction for at least one of bundled EAS identifier and endpoint list, main EAS identifier, or EAS bundle identifier (S-1104), The edge configuration server determines second EAS information (S-1105) which includes at least one EAS serving the application group for at least one of the identifiers received in the second request within the same EDN, and in particular determines second EAS information (S-1105) which includes at least one EAS serving the application group which is a common EAS for the bundle. The edge configuration server transmits a common EAS information storage response, including the instruction for the second EAS information, to the edge enabler server (S-1106). The method according to claim 11, further comprising:
13. The method according to claim 11 or 12, wherein the instruction for the bundled EAS identifier list is a bundled EAS identifier.
14. The method according to any one of claims 11 to 13, further comprising sending an EAS discovery request from an edge enabler client (EEC) to an EES, which includes at least one of an EAS bundle identifier, a bundled EAS identifier list, or an application group identifier, during EAS discovery.
15. The method according to any one of claims 11 to 14, further comprising transmitting an EAS information storage request from the EES to the ECS-ER based on the received EAS discovery request.
16. The method according to any one of claims 11 to 15, further comprising the ECS-ER sending an instruction to the EES recommending the use of at least one common EAS when the ECS-ER identifies existing common EAS information for the application group in the same EDN.
17. The method according to any one of claims 11 to 16, further comprising transmitting instructions for the received EAS information from the EEC to an application client (AC), thereby enabling the AC to connect to at least one EAS contained in the EAS information.
18. The method according to any one of claims 11 to 17, wherein the EAS information retrieval response includes a list of EAS endpoints and associated EAS endpoints corresponding to the requested EAS identifier.
19. The method according to any one of claims 11 to 18, wherein the common EAS information storage response includes a common EAS endpoint and its associated EAS endpoints corresponding to the requested EAS identifier.
20. The method according to any one of claims 11 to 19, wherein the edge enabler server is an edge enabler server (EES) and the edge configuration server is an edge configuration server (ECS).
21. A method for common edge application server (EAS) bundling in a communication network, which is implemented by an edge enabler server, wherein the method is: Sending a first request from the edge enabler server to the edge configuration server (S-1201), wherein the first request is an EAS information retrieval request, the first request includes an EAS identifier and an application group identifier, and the first request includes an instruction for at least one of a bundled EAS identifier list, a main EAS identifier, or an EAS bundle identifier (S-1201), The edge enabler server receives an EAS information retrieval response from the edge configuration server, which includes an instruction for first EAS information, including at least one EAS that serves an application group, for at least one of the identifiers in the first request (S-1202). Methods that include...
22. Sending a second request from the edge enabler server to the edge configuration server (S-1203), wherein the second request is a common EAS information storage request, the second request includes at least one of EDN information, EES identifier, EAS identifier, EAS endpoint, and application group identifier, and the second request includes an instruction for at least one of bundled EAS identifier and endpoint list, main EAS identifier, or EAS bundle identifier (S-1203), The edge enabler server receives a common EAS information storage response from the edge configuration server, which includes instructions for second EAS information, including at least one EAS serving the application group for at least one of the identifiers in the second request, within the same EDN (S-1204). The method according to claim 21, further comprising:
23. The method according to claim 21 or 22, wherein the instruction for the bundled EAS identifier list is a bundled EAS identifier.
24. The method according to any one of claims 21 to 23, further comprising sending an EAS discovery request from an edge enabler client (EEC) to an EES, which includes at least one of an EAS bundle identifier, a bundled EAS identifier list, or an application group identifier, during EAS discovery.
25. The method according to any one of claims 21 to 24, further comprising transmitting an EAS information storage request from the EES to the ECS-ER based on the received EAS discovery request.
26. The method according to any one of claims 21 to 25, further comprising the ECS-ER sending an instruction to the EES recommending the use of at least one common EAS when the ECS-ER identifies existing common EAS information for the application group in the same EDN.
27. The method according to any one of claims 21 to 26, further comprising transmitting instructions for the received EAS information from the EEC to an application client (AC), thereby enabling the AC to connect to at least one EAS contained in the EAS information.
28. The method according to any one of claims 21 to 27, wherein the EAS information retrieval response includes a list of EAS endpoints and associated EAS endpoints corresponding to the requested EAS identifier.
29. The method according to any one of claims 21 to 28, wherein the common EAS information storage response includes a common EAS endpoint and its associated EAS endpoints corresponding to the requested EAS identifier.
30. The method according to any one of claims 21 to 29, wherein the edge enabler server is an edge enabler server (EES) and the edge configuration server is an edge configuration server (ECS).
31. A device for common edge application server (EAS) bundling in a communication network, wherein the device comprises a processor and memory, the memory containing instructions executable by the processor such that the device is operable to perform the method according to any one of claims 11 to 20.
32. A device for common edge application server (EAS) bundling in a communication network, wherein the device comprises a processor and memory, the memory containing instructions executable by the processor such that the device is operable to perform the method according to any one of claims 21 to 30.
33. A system comprising the apparatus described in claim 31 and the apparatus described in claim 32.
34. A computer implementation system comprising one or more processors and one or more computer storage media for storing computer-usable instructions, wherein when the computer-usable instructions are used by the one or more processors, the one or more processors are instructed to carry out the method according to any one of claims 11 to 30.
35. A computer program that, when executed on at least one processor, includes an instruction causing the at least one processor to perform the method according to any one of claims 11 to 30.
36. A computer program product, embodied on a non-temporary machine-readable medium, comprising instructions executable by a processor, wherein the instructions cause the processor to perform the method according to any one of claims 11 to 30.