Generic edge application server bundle in a communication network

Abstract

The present disclosure provides a method for generic edge application server (EAS) bundling in a communication network. The method comprises: sending, from an edge enabling server to an edge configuration server, a first request, wherein the first request is an EAS information acquisition request, wherein the first request comprises an EAS identifier and an application group identifier, and wherein the first request comprises an indication of at least one of a bundled EAS identifier list, a primary EAS identifier, or an EAS bundle identifier; determining, at the edge configuration server, first EAS information comprising at least one EAS serving an application group targeted to at least one of the identifiers received in the first request; and sending, from the edge configuration server to the edge enabling server, an EAS information acquisition response comprising an indication of the determined first EAS information. In some embodiments, the method further comprises: sending, from the edge enabling server to the edge configuration server, a second request, wherein the second request is a generic EAS information storage request, wherein the second request comprises at least one of EDN information, an EES identifier, an EAS identifier, an EAS endpoint, and an application group identifier, and wherein the second request comprises an indication of at least one of a bundled EAS identifier and endpoint list, a primary EAS identifier, or an EAS bundle identifier; determining, at the

Description

Technical Field

[0001] This invention generally relates to edge computing in communication networks, and more specifically, to a mechanism for enabling the bundling of a generic edge application server (EAS) through interaction between an edge enabling server (EES) and an edge configuration server (ECS). Background Technology

[0002] Edge computing (EC) is a concept that enables services to be hosted closer to the service consumer and provides benefits such as efficient service delivery with significantly reduced end-to-end latency and reduced load on the transport network. The benefits of edge computing will enhance the prospects of fifth-generation (5G) networks and expand several new and enhanced use cases, including virtual and augmented reality, the Internet of Things (IoT), industrial IoT, autonomous driving, real-time multiplayer gaming, and more.

[0003] The 3rd Generation Partnership Project (3GPP) aims to define an enabling layer to facilitate communication between application clients (ACs) running on the UE and edge application servers (EASs) deployed on the edge data network (EDN). This includes aspects of service provisioning and EAS discovery. Additionally, it aims to provide support services such as application context transfer between EASs for service continuity, service enablement, and APIs that expose EAS capabilities. Further functionalities can be added, such as application roaming, edge computing alliances, and service continuity between the edge and the cloud.

[0004] Figure 2 This diagram illustrates the architecture for enabling edge applications described in 3GPP TS 23.558 Release 18.4.0. EDN stands for Local Data Network (DN). EAS and EES (Edge Enabler Server) are contained within the EDN. ECS (Edge Configuration Server) provides configuration related to the EES, including details of the EDN hosting the EES. The UE contains AC and EEC. EAS, EES, and ECS can interact with the 3GPP core network. When using SEAL (Service Enabler Architecture Layer) notification management services, the EES and ECS interact with the SEAL notification management server, and the SEAL EEC interacts with the SEAL notification management client.

[0005] Figure 3A generic EAS (see 3GPP TR 23.700-98 version 18.1.0) is illustrated, comprising several EASs (with the same services) deployed in different locations within the same EDN. Application services can be deployed across several EASs within an EDN. A group of UEs can be anchored to a generic EAS to consume the same application services, thereby reducing the likelihood of data synchronization between EASs. If a group of UEs is distributed across different EDNs, data synchronization between EASs can still be achieved because the generic EAS in each EDN is used to provide services to UEs within its EDN service area.

[0006] To support a common EAS selection for a set of UEs, in addition to ECS functionality, an ECS with a central repository also supports storing and providing common EES and common EAS information.

[0007] Figure 4 An architecture for supporting consortiums while allowing ECS ​​to include repository functionality (i.e., ECS-ER (ECS-Edge Repository)) is shown, as described in 3GPP TS 23.558 Release 18.4.0.

[0008] EAS bundles contain a list of EASs used to provide services to UE application clients. There are two types of EAS bundles: proxy type and direct type. Figure 5 The EAS bundle for the proxy type is shown. Figure 6 The direct type of EAS bundle is shown. Depending on the EAS bundle requirements, the EAS in the bundle can be discovered together or relocated.

[0009] Figure 7 This illustrates EASs (with identical services) deployed by the same ASP in different EDNs. The edge enablement layer supports EAS synchronization. When a UE connects to the same EAS (i.e., a generic EAS) in its corresponding EDN, information between the generic EASs needs to be synchronized. A generic EAS in an EDN can provide service to only one UE. In a special case, one UE connects to EAS-1X in EDN1, while another UE connects to EAS-2X in EDN2, and EAS-1X and EAS-2X need to synchronize data (the two UEs are in the same group).

[0010] One issue is that both EAS bundles and generic EAS are independent features. Combining them into a generic EAS bundle for a set of UEs is not supported.

[0011] Another aspect of the problem is how to discover and select a general EAS bundle (i.e., a list of bundled EAS that provide services to a group of UEs).

[0012] Another issue is how to perform EAS synchronization between EAS bundles, i.e., how to synchronize data between EAS bundles to enable applications where users from different locations need to interact in real time.

[0013] Another issue is the inefficiency of existing solutions in anchoring multiple UEs to a single EAS. Summary of the Invention

[0014] The invention is set forth in the appended claims.

[0015] The purpose of this invention is to enable the bundling of general edge application servers (EAS) in communication networks.

[0016] One aspect of the present invention relates to a method for general edge application server (EAS) bundling in a communication network, performed by an edge configuration server. The method includes: receiving a first request from an edge enabling server at the edge configuration server, wherein the first request is an EAS information retrieval request, wherein the first request includes an EAS identifier and an application group identifier, and wherein the first request includes an indication of at least one of a bundled EAS identifier list, a master EAS identifier, or an EAS bundle identifier; determining first EAS information at the edge configuration server, the first EAS information including at least one EAS serving an application group for at least one identifier received in the first request; and sending an EAS information retrieval response from the edge configuration server to the edge enabling server, the EAS information retrieval response including an indication of the determined first EAS information. In some embodiments, the method further includes: receiving a second request from an edge enabling server at an edge configuration server, wherein the second request is a generic EAS information storage request, wherein the second request includes at least one of EDN information, an EES identifier, an EAS identifier, an EAS endpoint, and an application group identifier, and wherein the second request includes an indication of at least one of a bundled EAS identifier and endpoint list, a primary EAS identifier, or an EAS bundle identifier; determining second EAS information at the edge configuration server, the 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; and sending a generic EAS information storage response from the edge configuration server to the edge enabling server, the generic EAS information storage response including an indication of the second EAS information. In some embodiments, the indication of the bundled EAS identifier list is a bundled EAS identifier. In some embodiments, the method further includes sending an EAS discovery request from an edge enabling client (EEC) to an EES during EAS discovery, the EAS discovery request including 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 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 generic EAS information for the application group in the same EDN, sending an indication from the ECS-ER to the EES suggesting the use of at least one generic EAS. In some embodiments, the method further includes sending an indication from the EEC to the application client (AC) to the received EAS information, allowing 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 identifier.In some embodiments, the generic EAS information storage response includes a generic EAS endpoint and its associated EAS endpoint corresponding to the requested EAS identifier. In some embodiments, the edge enabling server is an edge enabling 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 for bundling a generic edge application server (EAS) in a communication network, executed by an edge enabling server. The method includes: sending a first request from the edge enabling server to an edge configuration server, wherein the first request is an EAS information retrieval request, wherein the first request includes an EAS identifier and an application group identifier, and wherein the first request includes an indication of at least one of a bundled EAS identifier list, a primary EAS identifier, or an EAS bundle identifier; and receiving an EAS information retrieval response from the edge configuration server at the edge enabling server, the EAS information retrieval response including an indication of first EAS information, the first EAS information including at least one EAS serving an application group, the application group being for at least one identifier in the first request. In some embodiments, the method further includes: sending a second request from an edge enabling server to an edge configuration server, wherein the second request is a generic EAS information storage request, wherein the second request includes at least one of EDN information, an EES identifier, an EAS identifier, an EAS endpoint, and an application group identifier, and wherein the second request includes an indication of at least one of a bundled EAS identifier and endpoint list, a primary EAS identifier, or an EAS bundle identifier; and receiving a generic EAS information storage response from the edge configuration server at the edge enabling server, the generic EAS information storage response including an indication of second EAS information, the second EAS information including at least one EAS serving an application group, the application group being for at least one of the identifiers in the second request within the same EDN. In some embodiments, the indication of the bundled EAS identifier list is a bundled EAS identifier. In some embodiments, the method further includes sending an EAS discovery request from an edge enabling client (EEC) to an EES during EAS discovery, the EAS discovery request including 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 sending an EAS information storage request from an EES to an ECS-ER based on the received EAS discovery request. In some embodiments, the method further includes: if the ECS-ER identifies existing generic EAS information for the application group in the same EDN, sending an indication from the ECS-ER to the EES suggesting the use of at least one generic EAS. In some embodiments, the method further includes sending an indication from the EEC to the application client (AC) to receive the received EAS information, allowing 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 generic EAS information storage response includes generic EAS endpoints and their associated EAS endpoints corresponding to the requested EAS identifier.In some embodiments, the edge enabling server is an edge enabling server (EES), and the edge configuration server is an edge configuration server (ECS-ER) with an edge repository.

[0018] Other aspects of the invention relate to mobile network nodes configured to perform the corresponding methods described herein, specifically edge enabling servers (116, 1400) and edge configuration servers (117, 1300). Other aspects of the invention relate to computer programs and computer program products.

[0019] In some embodiments, the edge enabling server is an edge enabling server (EES). In some embodiments, the edge configuration server is an edge configuration server (ECS-ER) with an edge repository.

[0020] Advantageously, the solution disclosed herein provides a method for facilitating interaction between an Edge Enabled Server (EES) and an Edge Configuration Server (ECS-ER) with an edge repository for a generic Edge Application Server (EAS) bundle, which provides a more efficient way to manage edge computing resources in a communication network.

[0021] Furthermore, advantageously, the solution disclosed herein enables communication networks to optimize the use of network resources by bundling edge application servers (EAS) that serve the same application group.

[0022] Furthermore, the solution disclosed herein advantageously achieves reduced end-to-end latency by facilitating universal 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] Other objects, features, and advantages of the concepts disclosed herein will become apparent from the following description, claims, and drawings, or may be obtained by practicing the described techniques and the concepts set forth herein. Attached Figure Description

[0024] To better describe the implementation of the disclosed concepts and to define other objects, advantages, and features of this disclosure, a more detailed description is provided below and illustrated in the accompanying drawings. It should be understood that these drawings depict only exemplary embodiments of the invention and are therefore not intended to limit the scope of the invention. Examples are described and illustrated using the accompanying drawings and with the aid of additional specific description and details.

[0025] Figure 1 An example networking system based on a specific embodiment of the solution described herein is shown.

[0026] Figures 2 to 7An example block diagram of a network entity in a mobile communication network according to a specific embodiment of the solution described herein is shown.

[0027] Figure 8 An example signaling diagram is shown, illustrating a process according to a specific embodiment of the solution described herein.

[0028] Figure 9 An example signaling diagram is shown, illustrating a process according to a specific embodiment of the solution described herein.

[0029] Figure 10 An example signaling diagram is shown, illustrating a process according to a specific embodiment of the solution described herein.

[0030] Figure 11 An example flowchart is shown, illustrating a method performed by a mobile network node according to a specific embodiment of the solution described herein.

[0031] Figure 12 An example flowchart is shown, illustrating a method performed by a mobile network node according to a specific embodiment of the solution described herein.

[0032] Figure 13 An example block diagram of a mobile network node configured according to a specific embodiment of the solution described herein is shown.

[0033] Figure 14 An example block diagram of a mobile network node configured according to a specific embodiment of the solution described herein is shown.

[0034] Figure 15 An example of a virtualized environment is shown. Detailed Implementation

[0035] The invention will now be described in detail below with reference to the accompanying drawings, in which examples of embodiments or implementations of the invention are illustrated. However, the invention may be embodied or practiced in many different forms and should not be construed as being limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be assumed by default to exist / be used in another embodiment. These embodiments of the disclosed subject matter are presented as illustrative examples and are not to be construed as limiting the scope of the disclosed subject matter. For example, certain details of the embodiments may be modified, omitted, or extended without departing from the scope of the subject matter.

[0036] The example embodiments described herein occur in the context of telecommunications networks, including but not limited to telecommunications networks that conform to and / or otherwise incorporate aspects of the fifth-generation (5G) architecture. Figure 1 This is an example networking system 100 according to an example embodiment of the present disclosure. Figure 1 Specifically, a User Equipment (UE) 101 is shown capable of communicating with the (Radio) Access Network (RAN) 102, Access and Mobility Management Function (AMF) 106, and User Plane Function (UPF) 103. AMF 106 can further communicate with core network services, including Session Management Function (SMF) 107 and Policy Control Function (PCF) 111. Core network services can also communicate with Application Server / Application Function (AS / AF) 113. Other networking services include Network Slice Selection Function (NSSF) 108, Authentication Server Function (AUSF) 105, User Data Management (UDM) 112, Network Open Function (NEF) 109, Network Repository Function (NRF) 110, Unified Data Repository (UDR) 114, Network Data Analysis Function (NWDAF) 115, and Data Network (DN) 104. In some example embodiments of this disclosure, each entity in the networking system 100 is considered a Network Function (NF). One or more additional NF instances may be incorporated into the networking system.

[0037] The solution described in this article aims to enable the bundling of general-purpose edge application servers (EAS) in communication networks.

[0038] This disclosure provides a method for bundling a generic edge application server (EAS) in a communication network. The method includes: sending a first request from an edge enabling server to an edge configuration server, wherein the first request is an EAS information retrieval request, wherein the first request includes an EAS identifier and an application group identifier, and wherein the first request includes an indication of at least one of a bundled EAS identifier list, a primary EAS identifier, or an EAS bundle identifier; determining first EAS information at the edge configuration server, the first EAS information including at least one EAS serving an application group, the application group being for at least one identifier received in the first request; and sending an EAS information retrieval response from the edge configuration server to the edge enabling server, the EAS information retrieval response including an indication of the determined first EAS information. In some embodiments, the method further includes: sending a second request from an edge enabling server to an edge configuration server, wherein the second request is a generic EAS information storage request, wherein the second request includes at least one of EDN information, an EES identifier, an EAS identifier, an EAS endpoint, and an application group identifier, and wherein the second request includes an indication of at least one of a bundled EAS identifier and endpoint list, a primary EAS identifier, or an EAS bundle identifier; determining second EAS information at the edge configuration server, the second EAS information including at least one EAS serving an application group for at least one identifier received in the second request within the same EDN, specifically wherein the at least one EAS serving the application group is the bundled generic EAS; and sending a generic EAS information storage response from the edge configuration server to the edge enabling server, the generic EAS information storage response including an indication of the second EAS information. In some embodiments, the indication of the bundled EAS identifier list is a bundled EAS identifier. In some embodiments, the method further includes sending an EAS discovery request from an Edge Enabled Client (EEC) to an EES during EAS discovery, the EAS discovery request including at least one of an EAS bundle identifier, a list of bundled EAS identifiers, or an application group identifier. In some embodiments, the method further includes sending an EAS information storage request from the EES to an ECS-ER based on the received EAS discovery request. In some embodiments, the method further includes: if the ECS-ER identifies existing generic EAS information for the application group in the same EDN, sending an indication from the ECS-ER to the EES suggesting the use of at least one generic EAS. In some embodiments, the method further includes sending an indication from the EEC to an Application Client (AC) to the received EAS information, allowing 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 identifier.In some embodiments, the generic EAS information storage response includes a generic EAS endpoint and its associated EAS endpoint corresponding to the requested EAS identifier. In some embodiments, the edge enabling server is an edge enabling server (EES), and the edge configuration server is an edge configuration server (ECS-ER) with an edge repository.

[0039] This disclosure also provides mobile network nodes configured to perform the corresponding methods described herein, specifically edge enabling servers (116, 1400) and edge configuration servers (117, 1300). In some embodiments, the edge enabling server is an edge enabling server (EES) 116. In some embodiments, the edge configuration server is an edge configuration server (ECS-ER) 117 with an edge repository.

[0040] This disclosure also provides a corresponding computer program and a computer program product including code (e.g., code in the form of a computer program) that, when run on the processing circuitry of a mobile network node, causes the mobile network node to perform the disclosed method.

[0041] Advantageously, the solution disclosed herein provides a method for facilitating interaction between an Edge Enabled Server (EES) and an Edge Configuration Server (ECS-ER) with an edge repository for a generic Edge Application Server (EAS) bundle, which provides a more efficient way to manage edge computing resources in a communication network.

[0042] Furthermore, advantageously, the solution disclosed herein enables communication networks to optimize the use of network resources by bundling edge application servers (EAS) that serve the same application group.

[0043] Furthermore, the solution disclosed herein advantageously achieves reduced end-to-end latency by facilitating universal 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.

[0044] The solution and its features will be described further below.

[0045] During the initial selection of EAS bundles for group members, when the EES interacts with the ECS-ER, the EES or EEC can pre-select multiple EAS in the bundle, and these bundled EAS need to be stored for each EDN and each application group.

[0046] It can have three options:

[0047] a) Each associated EAS service has its own application group.

[0048] b) All associated EAS services depend on the application group of the main EAS service.

[0049] c) All associated EAS services have bundled application groups.

[0050] To support options b and c, the primary EAS ID or EAS bundle ID needs to be stored in the ECS-ER along with other data.

[0051] When another application group member triggers EAS discovery for all EAS services in the bundle, the group member is anchored to the same EAS instance in the bundle using the previously stored EAS bundle information during the interaction between EES and ECS-ER.

[0052] EAS synchronization requires the same operations. It can support more query filtering, such as EAS-bound IDs.

[0053] This disclosure focuses on the interaction between EES and ECS-ER to achieve a universal EAS bundle so that:

[0054] 1. Supports more query filtering for general EAS bundles (e.g., EAS bundle ID).

[0055] 2. Supports bundling related information (e.g., EAS bundling ID) in the general EAS information storage process.

[0056] The accompanying drawings, which illustrate an example of an embodiment of the solution, are described in detail below.

[0057] Figure 8 This is a signaling diagram illustrating an example embodiment of anchoring two UEs in a group to a common EAS in the EDN to select the common EAS for the UE application group. This process is performed by an edge enabling server (116, 1400) and an edge configuration server (117, 1300) configured to perform the corresponding methods described herein. In some embodiments, the edge enabling server is an edge enabling server (EES) 116. In some embodiments, the edge configuration server is an edge configuration server (ECS-ER) 117 with an edge repository.

[0058] The pre-selection of a general EAS can be performed by either the EES or the EEC. If the EEC pre-selects a general EAS, the EEC sends an EAS information provision request to the EES, where the request type is set to "EAS selection request". If the EES pre-selects a general EAS, the EEC sends an EAS discovery request to the EES.

[0059] The process includes the following steps.

[0060] Step 1. During EAS discovery, EEC 1 sends an EAS discovery request to EES 1, which includes the EAS bundle ID or a list of EAS IDs in the bundle, and the application group ID; or EEC 1 sends an EAS information provision request to EES 1, which includes the selected EAS endpoint and the application group ID.

[0061] Step 2. EES 1 pre-selects an EAS or uses a received EAS endpoint, and then sends an EAS information storage request message to the ECS-ER. This request message also includes the bundled EAS ID and endpoint list, the primary EAS ID or the EAS bundle ID.

[0062] Step 3. No existing generic EAS information was found, so ECS-ER created a new generic EAS information for the application group.

[0063] Step 4. ECS-ER responds to the EAS information storage request by indicating that the processing of the requested EAS results can continue.

[0064] Steps 5 to 7. Based on the received EAS information, EES 1 responds to EEC 1 with an EAS discovery request or EAS information provision request using the selected EAS. Subsequently, AC1 connects to the selected EAS after being informed by EEC 1.

[0065] Step 8. During EAS discovery, EEC 1 sends an EAS discovery request to EES 2, which includes the EAS bundle ID or a list of EAS IDs in the bundle, and the application group ID; or EEC 1 sends an EAS information provision request to EES 2, which includes the selected EAS endpoint and the application group ID.

[0066] Step 9. EES2 pre-selects an EAS or uses the received EAS endpoint, and then sends an EAS information storage request message to ECS-ER. This request message also includes the bundled EAS ID and endpoint list, the primary EAS ID or the EAS bundle ID.

[0067] Step 10. ECS-ER searches for existing generic EAS information for the application group in the same EDN.

[0068] Step 11. ECS-ER responds with the result indicating that the recommended use is the general EAS (including associated EES information) selected as EES 1.

[0069] Steps 12 to 14. Based on the received EAS information, EES2 responds to EEC2 with an EAS discovery request or EAS information provision request using the generic EAS, and then AC1 connects to the generic EAS. EEC2 can then contact EES1 for further procedures (e.g., EEC registration, ACR subscription).

[0070] Figure 9 This is a signaling diagram illustrating the process for obtaining EAS information. This process is performed by an edge enabling server (116, 1400) and an edge configuration server (117, 1300) configured to perform the corresponding methods described herein. In some embodiments, the edge enabling server is an edge enabling server (EES) 116. In some embodiments, the edge configuration server is an edge configuration server (ECS-ER) 117 with an edge repository.

[0071] The process includes the following steps.

[0072] Step 1. The EES sends an EAS information retrieval request message to the ECS-ER. This request message includes the EAS ID and application group ID, and may include a list of bundled EAS IDs and the primary EAS ID or EAS bundle ID.

[0073] Step 2. Upon receiving the request, ECS-ER checks whether there are any stored EAS serving the application group for that EAS ID, the list of bundled EAS IDs (if received), and the primary EAS ID (if received) or the EAS bundle ID (if received).

[0074] Step 3. If the request is successfully processed, the ECS-ER responds to the EES with the EAS information identified in Step 2.

[0075] Figure 10 This is a signaling diagram illustrating the process for general EAS information storage. The process is performed by an edge enabling server (116, 1400) and an edge configuration server (117, 1300) configured to perform the corresponding methods described herein. In some embodiments, the edge enabling server is an edge enabling server (EES) 116. In some embodiments, the edge configuration server is an edge configuration server (ECS-ER) 117 with an edge repository.

[0076] The process includes the following steps.

[0077] Step 1. The EES sends a generic EAS information storage request message to the ECS-ER. This request message includes EDN information, EESID, EAS ID, EAS endpoint and application group ID, and may include bundled EAS IDs and endpoint lists, primary EAS ID or EAS bundle IDs.

[0078] Step 2. Upon receiving the request, the ECS-ER checks within the same EDN whether any stored EAS exists that serves an application group for that EAS ID, the list of bundled EAS IDs (if received), and the primary EAS ID (if received) or the EAS bundle ID (if received). If no generic EAS is identified, the ECS-ER stores the received information for subsequent bundling requests.

[0079] Step 3. The ECS-ER responds to the EES with a response message stored in the generic EAS information. The ECS-ER can reject or accept the request using the generic EAS information identified in Step 2.

[0080] Table 1 describes the information elements of an EAS information retrieval request from EES to ECS-ER.

[0081] Table 1: EAS Information Acquisition Response

[0082]

[0083] Table 2 describes the information elements of the EAS information acquisition response from ECS-ER to EES.

[0084] Table 2: EAS Information Acquisition Response

[0085]

[0086] Table 3 describes the information elements of a general EAS information storage request from EES to ECS-ER.

[0087] Table 3: General EAS Information Storage Requests

[0088]

[0089] Table 4 describes the information elements of the general EAS information storage response from ECS-ER to EES.

[0090] Table 4: General EAS Information Storage Response

[0091]

[0092] The following describes in detail a flowchart illustrating an example of an embodiment of the solution.

[0093] The embodiments correspond to the methods performed and involved by the edge enabling servers (116, 1400) and the edge configuration servers (117, 1300).

[0094] Figure 11 This is a flowchart illustrating a method for bundling a generic edge application server (EAS) in a communication network, performed by an edge configuration server.

[0095] In step S-1101, the edge configuration server receives a first request from the edge enable server, wherein the first request is an EAS information acquisition request, wherein the first request includes an EAS identifier and an application group identifier, and wherein the first request includes an indication of at least one of a bundled EAS identifier list, a main EAS identifier, or an EAS bundle identifier.

[0096] In step S-1102, the edge configuration server determines first EAS information, which includes at least one EAS that provides services to an application group for at least one identifier received in the first request.

[0097] In step S-1103, the edge configuration server sends an EAS information acquisition response to the edge enable server, the EAS information acquisition response including an indication of the determined first EAS information.

[0098] In step S-1104, the edge configuration server receives a second request from the edge enable server, wherein the second request is a general EAS information storage request, wherein the second request includes at least one of EDN information, EES identifier, EAS identifier, EAS endpoint and application group identifier, and wherein the second request includes an indication of at least one of bundled EAS identifier and endpoint list, main EAS identifier or EAS bundle identifier.

[0099] 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 identifier received in a second request within the same EDN.

[0100] In step S-1106, the edge configuration server sends a generic EAS information storage response to the edge enable server, the generic EAS information storage response including an indication of second EAS information.

[0101] In some embodiments, the indication of the bundled EAS identifier list is the bundled EAS identifier.

[0102] In some embodiments, the method further includes sending an EAS discovery request from an edge-enabled client (EEC) to an EES during EAS discovery, the EAS discovery request including at least one of an EAS bundle identifier, a list of bundled EAS identifiers, or an application group identifier.

[0103] 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.

[0104] In some embodiments, the method further includes: if the ECS-ER identifies existing generic EAS information for the application group in the same EDN, sending an indication from the ECS-ER to the EES to suggest using at least one generic EAS.

[0105] In some embodiments, the method further includes an instruction from the EEC to the application client (AC) to send the received EAS information, allowing the AC to connect to at least one EAS included in the EAS information.

[0106] 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.

[0107] In some embodiments, the generic EAS information storage response includes a generic EAS endpoint and its associated EAS endpoint corresponding to the requested EAS identifier.

[0108] In some embodiments, the edge enabling server is an edge enabling server (EES), and the edge configuration server is an edge configuration server (ECS-ER) with an edge repository.

[0109] Figure 12 This is a flowchart illustrating a method for bundling a generic edge application server (EAS) in a communication network, performed by an edge enabler server.

[0110] In step S-1201, the edge enabling server sends a first request to the edge configuration server, wherein the first request is an EAS information acquisition request, wherein the first request includes an EAS identifier and an application group identifier, and wherein the first request includes an indication of at least one of a bundled EAS identifier list, a main EAS identifier, or an EAS bundle identifier.

[0111] In step S-1202, the edge enable server receives an EAS information acquisition response from the edge configuration server. The EAS information acquisition response includes an indication of first EAS information, which includes at least one EAS that provides services to an application group, the application group being for at least one identifier in the identifier in the first request.

[0112] In step S-1203, the edge enable server sends a second request to the edge configuration server, wherein the second request is a general EAS information storage request, wherein the second request includes at least one of EDN information, EES identifier, EAS identifier, EAS endpoint and application group identifier, and wherein the second request includes an indication of at least one of bundled EAS identifier and endpoint list, main EAS identifier or EAS bundle identifier.

[0113] In step S-1204, the edge enable server receives a generic EAS information storage response from the edge configuration server. The generic EAS information storage response includes an indication of second EAS information, which includes at least one EAS that provides services to an application group, the application group being for at least one identifier in a second request within the same EDN.

[0114] In some embodiments, the indication of the bundled EAS identifier list is the bundled EAS identifier.

[0115] In some embodiments, the method further includes sending an EAS discovery request from an edge-enabled client (EEC) to an EES during EAS discovery, the EAS discovery request including at least one of an EAS bundle identifier, a list of bundled EAS identifiers, or an application group identifier.

[0116] 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.

[0117] In some embodiments, the method further includes: if the ECS-ER identifies existing generic EAS information for the application group in the same EDN, sending an indication from the ECS-ER to the EES to suggest using at least one generic EAS.

[0118] In some embodiments, the method further includes an instruction from the EEC to the application client (AC) to send the received EAS information, allowing the AC to connect to at least one EAS included in the EAS information.

[0119] 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.

[0120] In some embodiments, the generic EAS information storage response includes a generic EAS endpoint and its associated EAS endpoint corresponding to the requested EAS identifier.

[0121] In some embodiments, the edge enabling server is an edge enabling server (EES), and the edge configuration server is an edge configuration server (ECS-ER) with an edge repository.

[0122] Figure 13 This is a block diagram illustrating the elements of a mobile network node 1300 in a mobile communication network. In some embodiments, the mobile network node 1300 is an ECS-ER 117. As shown, the mobile network node may include network interface circuitry 1301 (also referred to as a network interface) configured to communicate with the core network and / or other nodes in the network. The mobile network node may also include: processing circuitry 1302 (also referred to as a processor) coupled to the network interface circuitry; and memory circuitry 1303 (also referred to as a memory) coupled to the processing circuitry. The memory circuitry 1303 may include computer-readable program code that, when executed by the processing circuitry 1302, causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, the processing circuitry 1302 may be defined to include memory, thereby eliminating the need for a separate memory circuitry. As discussed herein, the operation of the mobile network node may be performed by the processing circuitry 1302 and / or the network interface circuitry 1301. For example, processing circuitry 1302 can control network interface circuitry 1301 to send communications to or receive communications from one or more other network nodes via network interface circuitry 1301. Furthermore, modules can be stored in memory 1303, and these modules can provide instructions such that when the instructions of the modules are executed by processing circuitry 1302, processing circuitry 1302 performs corresponding operations (e.g., the operations discussed below with respect to example embodiments related to core network nodes).

[0123] Figure 14This is a block diagram illustrating the elements of a mobile network node 1400 in a mobile communication network. In some embodiments, the mobile network node 1400 is an EES 116. As shown, the mobile network node may include network interface circuitry 1401 (also referred to as a network interface) configured to communicate with the core network and / or other nodes in the network. The mobile network node may also include: processing circuitry 1402 (also referred to as a processor) coupled to the network interface circuitry; and memory circuitry 1403 (also referred to as memory) coupled to the processing circuitry. The memory circuitry 1403 may include computer-readable program code that, when executed by the processing circuitry 1402, causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, the processing circuitry 1402 may be defined to include memory, thereby eliminating the need for a separate memory circuitry. As discussed herein, the operation of the mobile network node may be performed by the processing circuitry 1402 and / or the network interface circuitry 1401. For example, processing circuitry 1402 can control network interface circuitry 1401 to send communications to or receive communications from one or more other network nodes via network interface circuitry 1401. Furthermore, modules can be stored in memory 1403, and these modules can provide instructions such that when the instructions of the modules are executed by processing circuitry 1402, processing circuitry 1402 performs corresponding operations (e.g., the operations discussed below with respect to example embodiments related to core network nodes).

[0124] Figure 15 This is a block diagram illustrating a virtualization environment 1500 in which functionality implemented by some embodiments can be virtualized. In this context, virtualization means creating a virtual version of an apparatus or device that may include a virtualization hardware platform, storage devices, and networking resources. As used herein, virtualization can be applied to any device or component thereof described herein, and involves at least a portion of its functionality being implemented as an implementation of one or more virtual components. Some or all of the functionality described herein can be implemented as virtual components executed by one or more virtual machines (VMs) in one or more virtual environments 1500 hosted by one or more hardware nodes (e.g., hardware computing devices operating as network nodes, UEs, core network nodes, or hosts). Furthermore, in embodiments where virtual nodes do not require radio connectivity (e.g., core network nodes or hosts), the nodes can be fully virtualized. In some embodiments, the virtualization environment 1500 includes components defined by the O-RAN Alliance, such as an open cloud environment orchestrated via an O-2 interface by a service management and orchestration framework.

[0125] Application 1502 (which may alternatively be referred to as a software instance, virtual device, network function, virtual node, virtual network function, etc.) operates in a virtualized environment Q400 to implement some of the features, functions, and / or benefits of some embodiments disclosed herein.

[0126] Hardware 1504 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices described herein (e.g., network interfaces, input / output interfaces, etc.). The software can be executed by the processing circuitry to instantiate one or more virtualization layers 1506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1508a and 1508b (one or more of which may generally be referred to as VM 1508), and / or perform any functions, features, and / or benefits described in relation to some embodiments described herein. Virtualization layer 1506 can present a virtual operating platform to VM 1508, which appears as network hardware.

[0127] VM 1508 includes virtual processing, virtual memory, virtual network or interface, and virtual storage, and can be operated by a corresponding virtualization layer 1506. Different embodiments of instances of virtual device 1502 can be implemented on one or more VMs 1508, and these implementations can be carried out in different ways. In some contexts, hardware virtualization is referred to as Network Functions Virtualization (NFV). NFV can be used to unify many network device types into industry-standard high-capacity server hardware, physical switches, and physical storage, which can reside in data center and customer residential equipment.

[0128] In the context of NFV, VM 1508 can be a software implementation of a physical machine, whose operating procedures are executed as if on a physical, non-virtualized machine. Each VM 1508, along with the hardware portion of hardware 1504 that executes that VM (whether it is dedicated hardware for that VM and / or hardware shared by that VM with other VMs), forms a separate virtual network element. Still within the context of NFV, the virtual network function is responsible for handling the operation of one or more VMs 1508 on top of hardware 1504 and corresponds to the specific network function of application 1502.

[0129] Hardware 1504 can be implemented in a standalone network node with general or specific components. Hardware 1504 may implement some functions via virtualization. Alternatively, hardware 1504 may be part of a larger hardware cluster (e.g., in a data center or CPE) where many hardware nodes work together and are managed by management and orchestration 1510, which in particular oversees the lifecycle management of application 1502. In some embodiments, hardware 1504 is coupled to one or more radio units, each radio unit including one or more transmitters and one or more receivers that can 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 conjunction with virtual components to provide radio capabilities to virtual nodes (e.g., radio access nodes or base stations). In some embodiments, some signaling may be provided using a control system 1512, which may alternatively be used for communication between hardware nodes and radio units.

[0130] Embodiments within the scope of this invention may also include computer-readable media for carrying or having computer-executable instructions or data structures stored thereon. Such a computer-readable medium can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, such tangible computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of computer-executable instructions or data structures. When information is transmitted or provided to a computer via a network or other communication connection (wired, wireless, or a combination thereof), the computer correctly considers that connection as a computer-readable medium. Therefore, any such connection may be appropriately named a computer-readable medium. Combinations of the above should also be included within the scope of tangible computer-readable media.

[0131] Computer-executable instructions include, for example, instructions and data that cause a general-purpose computer, a special-purpose computer, or a special-purpose processing device to perform a specific function or a set of functions. Computer-executable instructions also include program modules that are executed by a computer in a standalone or networked environment. Typically, program modules include routines, programs, objects, components, and data structures that perform a specific task or implement a specific abstract data type. The computer-executable instructions, associated data structures, and program modules represent examples of program code means for performing the steps of the methods disclosed herein. Specific sequences of these executable instructions or associated data structures represent examples of corresponding actions for performing the functions described in these steps.

[0132] Those skilled in the art will understand that other embodiments of the present invention can be implemented 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, mainframes, etc. Embodiments can also be implemented in distributed computing environments, where tasks are performed by local and remote processing devices linked via a communication network (via wired links, wireless links, or a combination thereof). In a distributed computing environment, program modules can reside in local and remote memory storage devices.

[0133] Communication at each stage of the system can be performed via local area networks, token ring networks, the Internet, corporate intranets, 802.11 wireless signals, fiber optic networks, radio or microwave transmission, etc. Although the underlying communication technology may change, the basic principles described herein remain applicable.

[0134] The various embodiments described above are provided by way of illustration only and should not be construed as limiting the invention. For example, the principles described herein can be applied to any remote control device. Furthermore, those skilled in the art will recognize that communication between the remote device and the remote control device is not limited to communication over a local area network, but may include communication over an infrared channel, Bluetooth, or any other suitable communication interface. Those skilled in the art will readily recognize that various modifications and changes can be made to the invention without following the exemplary embodiments and applications described and illustrated herein, and without departing from the scope of this disclosure.

[0135] The terminology used herein is for the purpose of describing various embodiments only and is not intended to limit the exemplary embodiments. The singular forms “a,” “an,” and “the” as used herein are intended to also include the plural forms unless the context clearly indicates otherwise. It will also be understood that the terms “having,” “containing,” “comprising,” and “including” as used in this specification indicate the presence of the described features, integrals, steps, operations, elements, components, and combinations thereof, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components, and combinations thereof. Furthermore, unless expressly stated otherwise herein, all terms used in the claims are to be interpreted according to their ordinary meaning in the art. Unless expressly stated otherwise, all references to “a / an / the said element, device, component, apparatus, module, step, etc.” should be openly interpreted as referring to at least one instance of an element, device, component, apparatus, module, step, etc. Unless expressly stated otherwise, the steps of any method disclosed herein need not be performed in the exact order disclosed.

[0136] acronyms

[0137] 3GPP Third Generation Partnership Project

[0138] 5G (Fifth Generation)

[0139] AC Application Client

[0140] API (Application Programming Interface)

[0141] ASP application service provider

[0142] DN Data Network

[0143] DNAI Data Network Access Identifier

[0144] DNN Data Network Name

[0145] EC edge computing

[0146] EAS Edge Application Server

[0147] ID identifier

[0148] ECS Edge Configuration Server

[0149] ECS-ER Edge Configuration Server - Edge Repository

[0150] EDN Edge Data Network

[0151] EEC Edge Enabled Clients

[0152] EES Edge Enabled Server

[0153] IIoT (Industrial Internet of Things)

[0154] IoT (Internet of Things)

[0155] SEAL Service Enablement Architecture Layer

[0156] TR Technical Report

[0157] TS Technical Specifications

[0158] UE (User Equipment)

Claims

1. A method for bundling a generic edge application server (EAS) in a communication network, the method comprising: A first request (S-1201) is sent from the edge enable server to the edge configuration server, wherein the first request is an EAS information acquisition request, wherein the first request includes an EAS identifier and an application group identifier, and wherein the first request includes an indication of at least one of a bundled EAS identifier list, a main EAS identifier, or an EAS bundle identifier. At the edge configuration server, first EAS information is determined (S-1102), the first EAS information including at least one EAS for serving an application group, the application group being for at least one identifier among the identifiers received in the first request; and The edge configuration server sends an EAS information acquisition response (S-1103) to the edge enable server, the EAS information acquisition response including an indication of the determined first EAS information.

2. The method according to claim 1, further comprising: A second request (S-1203) is sent from the edge enable server to the edge configuration server, wherein the second request is a general EAS information storage request, wherein the second request includes at least one of EDN information, EES identifier, EAS identifier, EAS endpoint and application group identifier, and wherein the second request includes an indication of at least one of bundled EAS identifier and endpoint list, main EAS identifier or EAS bundle identifier. At the edge configuration server, second EAS information is determined (S-1105), the second EAS information including at least one EAS serving an application group, the application group being for at least one identifier received in a second request within the same EDN, specifically wherein the at least one EAS serving the application group is the bundled generic EAS; and The edge configuration server sends a (S-1106) generic EAS information storage response to the edge enable server, the generic EAS information storage response including an indication of the second EAS information.

3. The method according to any one of claims 1 to 2, wherein, The list of bundled EAS identifiers indicates which EAS identifiers are bundled.

4. The method according to any one of claims 1 to 3, wherein, The method further includes sending an EAS discovery request from the edge-enabled client (EEC) to the EES during EAS discovery, the EAS discovery request including at least one of an EAS bundle identifier, a list of bundled EAS identifiers, or an application group identifier.

5. The method according to any one of claims 1 to 4, wherein, The method further includes sending 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, wherein, The method further includes: if the ECS-ER identifies existing generic EAS information for the application group in the same EDN, then sending an indication from the ECS-ER to the EES to suggest using at least one generic EAS.

7. The method according to any one of claims 1 to 6, wherein, The method further includes sending an instruction from the EEC to the application client AC to receive EAS information, allowing 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 their associated EAS endpoints corresponding to the requested EAS identifier.

9. The method according to any one of claims 1 to 8, wherein, The generic EAS information storage response includes a generic EAS endpoint and its associated EAS endpoint corresponding to the requested EAS identifier.

10. The method according to any one of claims 1 to 9, wherein, The edge enabling server is an edge enabling server (EES), and the edge configuration server is an edge configuration server (ECS).

11. A method for bundling a generic edge application server (EAS) in a communication network, performed by an edge configuration server, the method comprising: At the edge configuration server, a first request is received from the edge enable server (S-1101), wherein the first request is an EAS information acquisition request, wherein the first request includes an EAS identifier and an application group identifier, and wherein the first request includes an indication of at least one of a bundled EAS identifier list, a main EAS identifier, or an EAS bundle identifier. At the edge configuration server, first EAS information is determined (S-1102), the first EAS information including at least one EAS for serving an application group, the application group being for at least one identifier among the identifiers received in the first request; and The edge configuration server sends an EAS information acquisition response (S-1103) to the edge enable server, the EAS information acquisition response including an indication of the determined first EAS information.

12. The method of claim 11, further comprising: At the edge configuration server, a second request (S-1104) is received from the edge enable server, wherein the second request is a general EAS information storage request, wherein the second request includes at least one of EDN information, EES identifier, EAS identifier, EAS endpoint and application group identifier, and wherein the second request includes an indication of at least one of bundled EAS identifier and endpoint list, main EAS identifier or EAS bundle identifier. At the edge configuration server, second EAS information is determined (S-1105), the second EAS information including at least one EAS serving an application group, the application group being for at least one identifier received in a second request within the same EDN, specifically wherein the at least one EAS serving the application group is the bundled generic EAS; and The edge configuration server sends a (S-1106) generic EAS information storage response to the edge enable server, the generic EAS information storage response including an indication of the second EAS information.

13. The method according to any one of claims 11 to 12, wherein, The list of bundled EAS identifiers indicates which EAS identifiers are bundled.

14. The method according to any one of claims 11 to 13, wherein, The method further includes sending an EAS discovery request from the edge-enabled client (EEC) to the EES during EAS discovery, the EAS discovery request including at least one of an EAS bundle identifier, a list of bundled EAS identifiers, or an application group identifier.

15. The method according to any one of claims 11 to 14, wherein, The method further includes sending 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, wherein, The method further includes: if the ECS-ER identifies existing generic EAS information for the application group in the same EDN, then sending an indication from the ECS-ER to the EES to suggest using at least one generic EAS.

17. The method according to any one of claims 11 to 16, wherein, The method further includes sending an instruction from the EEC to the application client AC to receive EAS information, allowing the AC to connect to at least one EAS included 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 their associated EAS endpoints corresponding to the requested EAS identifier.

19. The method according to any one of claims 11 to 18, wherein, The generic EAS information storage response includes a generic EAS endpoint and its associated EAS endpoint corresponding to the requested EAS identifier.

20. The method according to any one of claims 11 to 19, wherein, The edge enabling server is an edge enabling server (EES), and the edge configuration server is an edge configuration server (ECS).

21. A method for bundling a generic edge application server (EAS) for use in a communication network, performed by an edge enabling server, the method comprising: A first request (S-1201) is sent from the edge enable server to the edge configuration server, wherein the first request is an EAS information retrieval request, wherein the first request includes an EAS identifier and an application group identifier, and wherein the first request includes an indication of at least one of a bundled EAS identifier list, a main EAS identifier, or an EAS bundle identifier; and At the edge enable server, an EAS information acquisition response (S-1202) is received from the edge configuration server. The EAS information acquisition response includes an indication of first EAS information, which includes at least one EAS that provides services to an application group, the application group being for at least one identifier in the first request.

22. The method of claim 21, further comprising: A second request (S-1203) is sent from the edge enabling server to the edge configuration server, wherein the second request is a general EAS information storage request, wherein the second request includes at least one of EDN information, EES identifier, EAS identifier, EAS endpoint and application group identifier, and wherein the second request includes an indication of at least one of bundled EAS identifiers and endpoint lists, main EAS identifier or EAS bundle identifier; and At the edge enable server, a generic EAS information storage response (S-1204) is received from the edge configuration server. The generic EAS information storage response includes an indication of second EAS information, which includes at least one EAS that serves an application group, the application group being for at least one identifier in a second request within the same EDN.

23. The method according to any one of claims 21 to 22, wherein, The list of bundled EAS identifiers indicates which EAS identifiers are bundled.

24. The method according to any one of claims 21 to 23, wherein, The method further includes sending an EAS discovery request from the edge-enabled client (EEC) to the EES during EAS discovery, the EAS discovery request including at least one of an EAS bundle identifier, a list of bundled EAS identifiers, or an application group identifier.

25. The method according to any one of claims 21 to 24, wherein, The method further includes sending 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, wherein, The method further includes: if the ECS-ER identifies existing generic EAS information for the application group in the same EDN, then sending an indication from the ECS-ER to the EES to suggest using at least one generic EAS.

27. The method according to any one of claims 21 to 26, wherein, The method further includes sending an instruction from the EEC to the application client AC to receive EAS information, allowing the AC to connect to at least one EAS included 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 their associated EAS endpoints corresponding to the requested EAS identifier.

29. The method according to any one of claims 21 to 28, wherein, The generic EAS information storage response includes a generic EAS endpoint and its associated EAS endpoint corresponding to the requested EAS identifier.

30. The method according to any one of claims 21 to 29, wherein, The edge enabling server is an edge enabling server (EES), and the edge configuration server is an edge configuration server (ECS).

31. An apparatus for bundling a Universal Edge Application Server (EAS) in a communication network, the apparatus comprising a processor and a memory, the memory containing instructions executable by the processor, such that the apparatus is operable to perform the method according to any one of claims 11 to 20.

32. An apparatus for bundling a Universal Edge Application Server (EAS) in a communication network, the apparatus comprising a processor and a memory containing instructions executable by the processor, such that the apparatus is operable to perform the method according to any one of claims 21 to 30.

33. A system comprising the apparatus of claim 31 and the apparatus of claim 32.

34. A computer-implemented system comprising one or more processors and one or more computer storage media storing computer-usable instructions that, when used by the one or more processors, cause the one or more processors to perform the method according to any one of claims 11 to 30.

35. A computer program comprising instructions that, when executed on at least one processor, cause 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-transitory machine-readable medium, comprising instructions executable by a processor to cause the processor to perform the method according to any one of claims 11 to 30.

Images