Common edge application server bundling in a communications network

Abstract

This disclosure provides a method for common Edge Application Server, EAS, bundling in a communications network. The method comprises transmitting from an edge enabler server to an edge configuration server a first request, wherein the first request is an EAS information get 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; determining at the edge configuration server a first EAS information including at least one EAS serving the application group for at least one of the identifiers received in the first request; and transmitting from the edge configuration server to the edge enabler server an EAS information get response including an indication of the determined first EAS information. In some embodiments, the method further comprises transmitting from the edge enabler server to the edge configuration server a second request, wherein the second request is a Common EAS information store 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 a bundled EAS identifier and endpoint list, a main EAS identifier or an EAS bundle identifier; determining at the edge configuration server a second EAS information including 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 transmitting from the edge configuration server to the edge enabler server a Common EAS information store response including an indication of the second EAS information.

Description

[0001] COMMON EDGE APPLICATION SERVER BUNDLING IN A COMMUNICATIONS NETWORK

[0002] TECHNICAL FIELD

[0003] The present invention generally relates to edge computing in a communications network, and particularly to mechanisms for achieving common Edge Application Server (EAS) bundling by interaction between an Edge Enabler Server (EES) and an Edge Configuration Server (ECS).

[0004] BACKGROUND

[0005] Edge Computing (EC) is a concept that enables services to be hosted close to the service consumers and provides benefits such as efficient service delivery with significant reduction in end-to-end latency and decreased load on the transport network. The benefits of Edge Computing will strengthen the promise of Fifth Generation (5G) networks and expand the prospects for several new and enhanced use cases - including virtual and augmented reality, Internet of Things (loT), Industrial loT, autonomous driving, real-time multiplayer gaming etc.

[0006] The Third Generation Partnership Project (3GPP) aims to define an enabling layer to facilitate communication between the Application Clients (AC) running on the UE and the Edge Application Servers (EAS) deployed on the Edge Data Network (EDN). This includes aspects of service provisioning and EAS discovery. In addition, an aim is also to provide support services such as application context transfer between EASs for service continuity, service enablement and capability exposure APIs towards the EAS. More functions may be added, e.g., application roaming, edge computing federation, service continuity between edge and cloud.

[0007] Figure 2 shows the architecture for enabling edge applications as described in 3GPP TS 23.558 version 18.4.0. The EDN is a local Data Network (DN). EAS(s) and the EES (Edge Enabler Server) are contained within the EDN. The ECS (Edge Configuration Server) provides configurations related to the EES, including details of the EDN hosting the EES. The UE contains AC(s) and the EEC. The EAS(s), the EES and the ECS can interact with the 3GPP Core Network. When SEAL (Service Enabler Architecture Layer) notification management service is used, the EES and the ECS interacts with the SEAL notification management server and the SEAL EEC interacts with SEAL Notification management client.

[0008] Figure 3 shows common EAS (see 3GPP TR 23.700-98 version 18.1 .0), including several EASs (with same service) deployed in different locations in the same EDN. An application service may be deployed in an EDN in several EASs. A group of UEs can be anchored to consume the same application service to a common EAS to reduce the possibility of inter- EAS data synchronization. If a group of UEs are distributed in different EDNs, it is still possible to have inter-EAS data synchronization since a common EAS in each EDN is used to serve UEs within its EDN service area.

[0009] To support common EAS selection for a group of UEs, in addition to ECS functionalities, ECS with Central Repository supports storing and providing common EES and common EAS information.

[0010] Figure 4 shows the architecture for federation support while the ECS may contain a Repository function, ECS-ER (ECS - Edge Repository), as described in 3GPP TS 23.558 version 18.4.0.

[0011] An EAS bundle contains a list of EASs to serve UE application client. There are two types of EAS bundle: proxy type and direct type. Figure 5 shows the proxy type of EAS bundle.

[0012] Figure 6 shows the direct type of EAS bundle. The EASs in a bundle may be discovered or relocated together depending on EAS bundle requirement.

[0013] Figure 7 shows an EAS (with same service) deployed by the same ASP in different EDNs. The edge enabler layer supports for EAS synchronization. When UEs are connecting to the same EAS (i.e., common EAS) in their corresponding EDN, there is a need to synchronize information between common EASs. It is possible that common EAS in an EDN serves 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).

[0014] A problematic aspect is that both EAS bundle and common EAS are independent features. There is no support to combine them to have a common EAS bundle for a group of UEs.

[0015] A further problematic aspect is how to discover and select a common EAS bundle (i.e., a list of bundled EASs serving a group of UEs). A further problematic aspect is how to perform EAS synchronization between EAS bundles, i.e., how to synchronize data across EAS bundles, e.g., to enable applications where users from different locations need to interact in real-time.

[0016] A further problematic aspect is the inefficiencies of the existing solutions in anchoring multiple UEs to a single EAS.

[0017] SUMMARY

[0018] The invention is set out in the appended set of claims.

[0019] An object of the invention is to enable common Edge Application Server (EAS) bundling in a communications network.

[0020] An aspect of the invention relates to a method performed by an edge configuration server for common Edge Application Server, EAS, bundling in a communications network. The method comprises receiving at an edge configuration server from an edge enabler server a first request, wherein the first request is an EAS information get 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; determining at the edge configuration server a first EAS information including at least one EAS serving the application group for at least one of the identifiers received in the first request; and transmitting from the edge configuration server to the edge enabler server an EAS information get response including an indication of the determined first EAS information. In some embodiments, the method further comprises receiving at the edge configuration server from the edge enabler server a second request, wherein the second request is a Common EAS information store 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 a bundled EAS identifier and endpoint list, a main EAS identifier or an EAS bundle identifier; determining at the edge configuration server a second EAS information including 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 transmitting from the edge configuration server to the edge enabler server a Common EAS information store response including an indication of the second EAS information. In some embodiments, the indication of a bundled EAS identifier list is a bundled EAS identifier. In some embodiments, the method further comprises transmitting from an Edge Enabler Client, EEC, to the EES during EAS discovery an 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 comprises transmitting from the EES to the ECS-ER an EAS information store request based on the received EAS discovery request. In some embodiments, the method further comprises transmitting from the ECS-ER to the EES an indication recommending the use of at least one common EAS if the ECS-ER identifies existing common EAS information for the Application group in the same EDN. In some embodiments, the method further comprises transmitting from the EEC to an Application Client, AC, an indication of 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 get response includes a list of EAS endpoints and its associated EAS endpoints corresponding to the requested EAS identifiers. In some embodiments, the Common EAS information store response includes a common EAS endpoint and its associated EAS endpoints corresponding to the requested EAS identifiers. In some embodiments, the edge enabler server is an Edge Enabler Server (EES), the edge configuration server is an Edge Configuration Server with an Edge Repository (ECS-ER).

[0021] An aspect of the invention relates to a method performed by an edge enabler server for common Edge Application Server, EAS, bundling in a communications network. The method comprises transmitting from an edge enabler server to an edge configuration server a first request, wherein the first request is an EAS information get 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 receiving at the edge enabler server from the edge configuration server an EAS information get response including an indication of a first EAS information including at least one EAS serving the application group for at least one of the identifiers in the first request. In some embodiments, the method further comprises transmitting from the edge enabler server to the edge configuration server a second request, wherein the second request is a Common EAS information store 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 a bundled EAS identifier and endpoint list, a main EAS identifier or an EAS bundle identifier; and receiving at the edge enabler server from the edge configuration server a Common EAS information store response including an indication of a 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. In some embodiments, the indication of a bundled EAS identifier list is a bundled EAS identifier. In some embodiments, the method further comprises transmitting from an Edge Enabler Client, EEC, to the EES during EAS discovery an 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 comprises transmitting from the EES to the ECS-ER an EAS information store request based on the received EAS discovery request. In some embodiments, the method further comprises transmitting from the ECS-ER to the EES an indication recommending the use of at least one common EAS if the ECS-ER identifies existing common EAS information for the Application group in the same EDN. In some embodiments, the method further comprises transmitting from the EEC to an Application Client, AC, an indication of 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 get response includes a list of EAS endpoints and its associated EAS endpoints corresponding to the requested EAS identifiers. In some embodiments, the Common EAS information store response includes a common EAS endpoint and its associated EAS endpoints corresponding to the requested EAS identifiers. In some embodiments, the edge enabler server is an Edge Enabler Server (EES), the edge configuration server is an Edge Configuration Server with an Edge Repository (ECS-ER).

[0022] Other aspects of the invention relate to mobile network nodes, particularly an edge enabler server (116, 1400), an edge configuration server (117, 1300) configured to perform the respective methods as described herein. Other aspects of the invention relate to computer program and computer program products.

[0023] 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 with an Edge Repository (ECS-ER).

[0024] Advantageously, the solution disclosed herein provides a method for facilitating interaction between an Edge Enabler Server (EES) and an Edge Configuration Server with an Edge Repository (ECS-ER) for common Edge Application Server (EAS) bundling, which offers a more efficient way of managing edge computing resources in a communications network.

[0025] Further advantageously, the solution disclosed herein enables communication networks to achieve optimized usage of network resources by bundling Edge Application Servers (EASs) serving the same application group. Further advantageously, the solution disclosed herein enables reduced end-to-end latency by facilitating common EAS bundling closer to the service consumers, which is especially beneficial for applications that require real-time data processing, such as online gaming or autonomous driving.

[0026] Additional objectives, features and advantages of the concepts disclosed herein will be apparent from the following description, claims and drawings, or may be learned by practice of the described technologies and concepts as set forth herein.

[0027] BRIEF DESCRIPTION OF THE DRAWINGS

[0028] In order to best describe the manner in which the disclosed concepts may be implemented, as well as define other objects, advantages and features of the disclosure, a more particular description is provided below and is illustrated in the appended drawings. Understanding that these drawings depict only exemplary embodiments of the invention and are not therefore to be considered to be limiting in scope, the examples will be described and explained with additional specificity and detail through the use of the accompanying drawings.

[0029] Figure 1 illustrates an example networked system in accordance with particular embodiments of the solution described herein.

[0030] Figures 2-7 illustrate example block diagrams showing network entities in a mobile communications network according to particular embodiments of the solution described herein.

[0031] Figure 8 illustrates an example signaling diagram showing a procedure according to particular embodiments of the solution described herein.

[0032] Figure 9 illustrates an example signaling diagram showing a procedure according to particular embodiments of the solution described herein.

[0033] Figure 10 illustrates an example signaling diagram showing a procedure according to particular embodiments of the solution described herein.

[0034] Figure 11 illustrates an example flowchart showing a method performed by a mobile network node according to particular embodiments of the solution described herein. Figure 12 illustrates an example flowchart showing a method performed by a mobile network node according to particular embodiments of the solution described herein.

[0035] Figure 13 illustrates an example block diagram of a mobile network node configured in accordance with particular embodiments of the solution described herein.

[0036] Figure 14 illustrates an example block diagram of a mobile network node configured in accordance with particular embodiments of the solution described herein.

[0037] Figure 15 illustrates an example of a virtualized environment.

[0038] DETAILED DESCRIPTION

[0039] The invention will now be described in detail hereinafter with reference to the accompanying drawings, in which examples of embodiments or implementations of the invention are shown. The invention may, however, be embodied or implemented in many different forms and should not be construed as 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 present 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 tacitly assumed to be present / used in another embodiment. These embodiments of the disclosed subject matter are presented as teaching examples and are not to be construed as limiting the scope of the disclosed subject matter. For example, certain details of the described embodiments may be modified, omitted, or expanded upon without departing from the scope of the described subject matter.

[0040] The example embodiments described herein arise in the context of a telecommunications network, including but not limited to a telecommunications network that conforms to and / or otherwise incorporates aspects of a fifth generation (5G) architecture. Figure 1 is an example networked system 100 in accordance with example embodiments of the present disclosure. Figure 1 specifically illustrates User Equipment (UE) 101 , which may be in communication with a (Radio) Access Network (RAN) 102 and Access and Mobility Management Function (AMF) 106 and User Plane Function (UPF) 103. The AMF 106 may, in turn, be in communication with core network services including Session Management Function (SMF) 107 and Policy Control Function (PCF) 111. The core network services may also be in communication with an Application Server / Application Function (AS / AF) 113. Other networked services also include Network Slice Selection Function (NSSF) 108, Authentication Server Function (ALISF) 105, User Data Management (UDM) 112, Network Exposure Function (NEF) 109, Network Repository Function (NRF) 110, Unified Data Repository (UDR) 114, Network Data Analytics Function (NWDAF) 115, and Data Network (DN) 104. In some example implementations of embodiments of the present disclosure, each one of the entities in the networked system 100 are considered to be a Network Function (NF). One or more additional instances of the NFs may be incorporated into the networked system.

[0041] The solution described herein aims to enable common Edge Application Server (EAS) bundling in a communications network.

[0042] This disclosure provides a method for common Edge Application Server, EAS, bundling in a communications network. The method comprises transmitting from an edge enabler server to an edge configuration server a first request, wherein the first request is an EAS information get 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; determining at the edge configuration server a first EAS information including at least one EAS serving the application group for at least one of the identifiers received in the first request; and transmitting from the edge configuration server to the edge enabler server an EAS information get response including an indication of the determined first EAS information. In some embodiments, the method further comprises transmitting from the edge enabler server to the edge configuration server a second request, wherein the second request is a Common EAS information store 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 a bundled EAS identifier and endpoint list, a main EAS identifier or an EAS bundle identifier; determining at the edge configuration server a second EAS information including at least one EAS serving the application group for at least one of the identifiers received in the second request within the same EDN, particularly wherein the at least one EAS serving the application group is a common EAS for the bundle; and transmitting from the edge configuration server to the edge enabler server a Common EAS information store response including an indication of the second EAS information. In some embodiments, the indication of a bundled EAS identifier list is a bundled EAS identifier. In some embodiments, the method further comprises transmitting from an Edge Enabler Client, EEC, to the EES during EAS discovery an 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 comprises transmitting from the EES to the ECS-ER an EAS information store request based on the received EAS discovery request. In some embodiments, the method further comprises transmitting from the ECS-ER to the EES an indication recommending the use of at least one common EAS if the ECS-ER identifies existing common EAS information for the Application group in the same EDN. In some embodiments, the method further comprises transmitting from the EEC to an Application Client, AC, an indication of 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 get response includes a list of EAS endpoints and its associated EAS endpoints corresponding to the requested EAS identifiers. In some embodiments, the Common EAS information store response includes a common EAS endpoint and its associated EAS endpoints corresponding to the requested EAS identifiers. In some embodiments, the edge enabler server is an Edge Enabler Server (EES), the edge configuration server is an Edge Configuration Server with an Edge Repository (ECS-ER).

[0043] This disclosure also provides mobile network nodes, particularly an edge enabler server (116, 1400), an edge configuration server (117, 1300) configured to perform the respective methods as 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 with an Edge Repository (ECS-ER) 117.

[0044] This disclosure also provides the corresponding computer program and computer program products comprising code, for example in the form of a computer program, that when run on processing circuitry of the mobile network nodes causes the mobile network nodes to perform the disclosed methods.

[0045] Advantageously, the solution disclosed herein provides a method for facilitating interaction between an Edge Enabler Server (EES) and an Edge Configuration Server with an Edge Repository (ECS-ER) for common Edge Application Server (EAS) bundling, which offers a more efficient way of managing edge computing resources in a communications network.

[0046] Further advantageously, the solution disclosed herein enables communication networks to achieve optimized usage of network resources by bundling Edge Application Servers (EASs) serving the same application group. Further advantageously, the solution disclosed herein enables reduced end-to-end latency by facilitating common EAS bundling closer to the service consumers, which is especially beneficial for applications that require real-time data processing, such as online gaming or autonomous driving.

[0047] The solution and the features comprised therein are further described in what follows.

[0048] During initial selection of EAS bundle for a group member, multiple EASs in a bundle may be pre-selected by an EES or EEC, when EES interacts with ECS-ER, these bundled EASs per EDN and per application group needs to be stored.

[0049] It is possible to have three options: a) Each associated EAS service has its own application group. b) All associated EAS services rely on main EAS service’s application group. c) All associated EAS services have an application group for a bundle.

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

[0051] When another application group member triggers EAS discovery for all EAS services in a bundle, during interaction between EES and ECS-ER, the previously stored EAS bundle information are used to anchor group member to the same EAS instance(s) in the bundle.

[0052] The same is required in the EAS synchronization. More query filters like EAS bundle ID can be supported.

[0053] This disclosure focuses on the interaction between the EES and the ECS-ER for common EAS bundle to:

[0054] 1 . Support more query filters (e.g., EAS bundle ID) for common EAS bundle.

[0055] 2. Support bundle related info (e.g., EAS bundle ID) in the common EAS info storage procedure.

[0056] Hereinafter, drawings showing examples of embodiments of the solution are described in detail.

[0057] Figure 8 is a signaling diagram illustrating an example embodiment with two UEs in a group being anchored to a common EAS in an EDN for selecting a common EAS for LIE application group. The procedure is performed by an edge enabler server (116, 1400), an edge configuration server (117, 1300) configured to perform the respective methods as 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 with an Edge Repository (ECS-ER) 117.

[0058] The common EAS pre-selection can be done either by EES or EEC. If it is EEC to pre-select common EASs, EEC sends EAS info provisioning request to EES with request type set to "EAS selection request". If it is EES to pre-select common EAS, EEC sends EAS discovery request to EES.

[0059] The procedure comprises the following steps.

[0060] Step 1 . During EAS discovery, EEC 1 sends EAS discovery request to EES 1 including EAS bundle ID or a list of EAS IDs in a bundle, and Application Group ID; or EAS info provisioning request including selected EAS endpoint(s) and Application Group ID to EES1.

[0061] Step 2. The EES 1 either pre-selects an EAS or uses the received EAS endpoint(s) and then sends EAS info store request message to ECS-ER. The request message also includes bundled EAS ID and endpoint list, main EAS ID or EAS bundle ID.

[0062] Step 3. There is no existing common EAS information found so that the ECS-ER creates a new common EAS information for the Application group.

[0063] Step 4. The ECS-ER responds to the EAS info store request with a result indicating OK to proceed with the requested EAS(s).

[0064] Step 5-7. With the received EAS information, the EES 1 responds the EAS discovery request or EAS info provisioning request with the selected EAS to the EEC 1 and consequently AC1 connects to the selected EAS(s) after being informed by EEC 1 .

[0065] Step 8. During EAS discovery, EEC 2 sends EAS discovery request to EES 2 including EAS bundle ID or a list of EAS IDs in a bundle, and Application Group ID; or EAS info provisioning request including selected EAS endpoint(s) and Application Group ID to EES 2.

[0066] Step 9. The EES 2 either pre-selects an EAS or uses the received EAS endpoint(s) and then sends EAS info store request message to ECS-ER. The request message also includes bundled EAS ID and endpoint list, main EAS ID or EAS bundle ID. Step 10. The ECS-ER finds existing common EAS information for the Application group in the same EDN.

[0067] Step 11 . The ECS-ER responds with a result indicating recommendation to use common EAS(s) (including the associated EES info) which is EES 1 selected EAS(s).

[0068] Step 12-14. With the received EAS information, the EES 2 responds the EAS discovery request or EAS info provisioning request with the common EAS(s) to the EEC 2 and consequently AC1 connects to the common EAS(s). EEC 2 may contact EES 1 for subsequent procedures (e.g., EEC registration, ACR subscription).

[0069] Figure 9 is a signaling diagram illustrating a procedure for obtaining EAS information. The procedure is performed by an edge enabler server (116, 1400), an edge configuration server (117, 1300) configured to perform the respective methods as 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 with an Edge Repository (ECS-ER) 117.

[0070] The procedure comprises the following steps.

[0071] Step 1 . The EES sends EAS information get request message to the ECS-ER. The request message includes EAS ID and Application Group ID, and may include bundled EAS ID list and main EAS ID or EAS bundle ID.

[0072] Step 2. Upon receiving the request, the ECS-ER checks if there are any stored EAS(s) 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).

[0073] Step 3. If the processing of the request was successful, the ECS-ER responds the EES with EAS information identified in step 2.

[0074] Figure 10 is a signaling diagram illustrating a procedure for common EAS information storage. The procedure is performed by an edge enabler server (116, 1400), an edge configuration server (117, 1300) configured to perform the respective methods as 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 with an Edge Repository (ECS-ER) 117.

[0075] The procedure comprises the following steps. Step 1 . The EES sends Common EAS information store request message to the ECS-ER. The request message includes EDN information, EES ID, EAS ID, EAS endpoint and Application Group ID, and may include bundled EAS ID and endpoint list, main EAS ID or EAS bundle ID. Step 2. Upon receiving the request, the ECS-ER checks if there is any 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) within the same EDN. If no common EAS is identified, the ECS-ER stores the received information for subsequent binding requests.

[0076] Step 3. The ECS-ER responds the EES with Common EAS information store response message. The ECS-ER may reject the request with common EAS information identified in step 2 or accept the request.

[0077] Table 1 describes the information elements for EAS information get request from the EES to the ECS-ER. Table 1 : EAS information get response Table 2 describes the information elements for EAS information get response from the ECS- ER to the EES.

[0078] Table 2: EAS information get response

[0079] Table 3 describes the information elements for common EAS information store request from the EES to the ECS-ER.

[0080] Table 3: Common EAS information store request Table 4 describes the information elements for common EAS information store response from the ECS-ER to the EES.

[0081] Table 4: Common EAS information store response

[0082] Hereinafter, flowcharts showing examples of embodiments of the solution are described in detail.

[0083] The embodiments correspond to methods performed by and involving an edge enabler server (1 16, 1400), an edge configuration server (1 17, 1300). Figure 11 is a flowchart illustrating a method performed by the edge configuration server for common Edge Application Server, EAS, bundling in a communications network.

[0084] In step S-1101 , the edge configuration server receives from an edge enabler server a first request, wherein the first request is an EAS information get 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.

[0085] In step S-1102, the edge configuration server determines a first EAS information including at least one EAS serving the application group for at least one of the identifiers received in the first request. In step S-1103, the edge configuration server transmits to the edge enabler server an EAS information get response including an indication of the determined first EAS information.

[0086] In step S-1104, the edge configuration server receives from the edge enabler server a second request, wherein the second request is a Common EAS information store 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 a bundled EAS identifier and endpoint list, a main EAS identifier or an EAS bundle identifier.

[0087] In step S-1105, the edge configuration server determines a second EAS information including at least one EAS serving the application group for at least one of the identifiers received in the second request within the same EDN.

[0088] In step S-1106, the edge configuration server transmits to the edge enabler server a Common EAS information store response including an indication of the second EAS information.

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

[0090] In some embodiments, the method further comprises transmitting from an Edge Enabler Client, EEC, to the EES during EAS discovery an EAS discovery request including at least one of an EAS bundle identifier, a bundled EAS identifier list, or an Application Group identifier.

[0091] In some embodiments, the method further comprises transmitting from the EES to the ECS- ER an EAS information store request based on the received EAS discovery request.

[0092] In some embodiments, the method further comprises transmitting from the ECS-ER to the EES an indication recommending the use of at least one common EAS if the ECS-ER identifies existing common EAS information for the Application group in the same EDN.

[0093] In some embodiments, the method further comprises transmitting from the EEC to an Application Client, AC, an indication of the received EAS information, allowing the AC to connect to at least one EAS included in the EAS information.

[0094] In some embodiments, the EAS information get response includes a list of EAS endpoints and its associated EAS endpoints corresponding to the requested EAS identifiers. In some embodiments, the Common EAS information store response includes a common EAS endpoint and its associated EAS endpoints corresponding to the requested EAS identifiers.

[0095] In some embodiments, the edge enabler server is an Edge Enabler Server (EES), the edge configuration server is an Edge Configuration Server with an Edge Repository (ECS-ER).

[0096] Figure 12 is a flowchart illustrating a method performed by the edge enabler server for common Edge Application Server, EAS, bundling in a communications network.

[0097] In step S-1201 , the edge enabler server transmits to an edge configuration server a first request, wherein the first request is an EAS information get 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.

[0098] In step S-1202, the edge enabler server receives from the edge configuration server an EAS information get response including an indication of a first EAS information including at least one EAS serving the application group for at least one of the identifiers in the first request.

[0099] In step S-1203, the edge enabler server transmits to the edge configuration server a second request, wherein the second request is a Common EAS information store 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 a bundled EAS identifier and endpoint list, a main EAS identifier or an EAS bundle identifier.

[0100] In step S-1204, the edge enabler server receives from the edge configuration server a Common EAS information store response including an indication of a 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.

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

[0102] In some embodiments, the method further comprises transmitting from an Edge Enabler Client, EEC, to the EES during EAS discovery an 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 comprises transmitting from the EES to the ECS- ER an EAS information store request based on the received EAS discovery request.

[0103] In some embodiments, the method further comprises transmitting from the ECS-ER to the EES an indication recommending the use of at least one common EAS if the ECS-ER identifies existing common EAS information for the Application group in the same EDN.

[0104] In some embodiments, the method further comprises transmitting from the EEC to an Application Client, AC, an indication of the received EAS information, allowing the AC to connect to at least one EAS included in the EAS information.

[0105] In some embodiments, the EAS information get response includes a list of EAS endpoints and its associated EAS endpoints corresponding to the requested EAS identifiers.

[0106] In some embodiments, the Common EAS information store response includes a common EAS endpoint and its associated EAS endpoints corresponding to the requested EAS identifiers.

[0107] In some embodiments, the edge enabler server is an Edge Enabler Server (EES), the edge configuration server is an Edge Configuration Server with an Edge Repository (ECS-ER).

[0108] Figure 13 is a block diagram illustrating elements of a mobile network node 1300 of a mobile communications 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 provide communications with other nodes of the core network and / or the network. The mobile network node may also include a processing circuitry 1302 (also referred to as a processor) coupled to the network interface circuitry, and memory circuitry 1303 (also referred to as 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, processing circuitry 1302 may be defined to include memory so that a separate memory circuitry is not required. As discussed herein, operations of the mobile network node may be performed by processing circuitry 1302 and / or network interface circuitry 1301 . For example, processing circuitry 1302 may control network interface circuitry 1301 to transmit communications through network interface circuitry 1301 to one or more other network nodes and / or to receive communications through network interface circuitry from one or more other network nodes. Moreover, modules may be stored in memory 1303, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 1302, processing circuitry 1302 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to core network nodes).

[0109] Figure 14 is a block diagram illustrating 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 network interface circuitry 1401 (also referred to as a network interface) configured to provide communications with other nodes of the core network and / or the network. The mobile network node may also include a 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, processing circuitry 1402 may be defined to include memory so that a separate memory circuitry is not required. As discussed herein, operations of the mobile network node may be performed by processing circuitry 1402 and / or network interface circuitry 1401 . For example, processing circuitry 1402 may control network interface circuitry 1401 to transmit communications through network interface circuitry 1401 to one or more other network nodes and / or to receive communications through network interface circuitry from one or more other network nodes. Moreover, modules may be stored in memory 1403, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 1402, processing circuitry 1402 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to core network nodes).

[0110] Figure 15 is a block diagram illustrating a virtualization environment 1500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, 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 virtual environments 1500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0111] Applications 1502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0112] Hardware 1504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may 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 be generally referred to as VMs 1508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1506 may present a virtual operating platform that appears like networking hardware to the VMs 1508.

[0113] The VMs 1508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1506. Different embodiments of the instance of a virtual appliance 1502 may be implemented on one or more of VMs 1508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0114] In the context of NFV, a VM 1508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1508, and that part of hardware 1504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1508 on top of the hardware 1504 and corresponds to the application 1502. Hardware 1504 may be implemented in a standalone network node with generic or specific components. Hardware 1504 may implement some functions via virtualization. Alternatively, hardware 1504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1510, which, among others, oversees lifecycle management of applications 1502. In some embodiments, hardware 1504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1512 which may alternatively be used for communication between hardware nodes and radio units.

[0115] Embodiments within the scope of the present invention may also include computer-readable media for carrying or having computer-executable instructions or data structures stored thereon. Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such tangible computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which 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 or provided over a network or another communications connection (either hardwired, wireless, or combination thereof) to a computer, the computer properly views the connection as a computer-readable medium. Thus, any such connection is properly termed a computer- readable medium. Combinations of the above should also be included within the scope of the tangible computer-readable media.

[0116] Computer-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Computer-executable instructions also include program modules that are executed by computers in standalone or network environments. Generally, program modules include routines, programs, objects, components, and data structures that perform particular tasks or implement particular abstract data types. Computer executable instructions, associated data structures, and program modules represent examples of the program code means for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represent examples of corresponding acts for implementing the functions described in such steps.

[0117] Those of skill in the art will appreciate that other embodiments of the invention may be practiced in network computing environments with many types of computer system configurations, including personal computers, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. Embodiments may also be practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or by a combination thereof) through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

[0118] Communication at various stages of the described system can be performed through a local area network, a token ring network, the Internet, a corporate intranet, 802.11 series wireless signals, fiber-optic network, radio or microwave transmission, etc. Although the underlying communication technology may change, the fundamental principles described herein are still applicable.

[0119] The various embodiments described above are provided by way of illustration only and should not be construed to limit the invention. For example, the principles herein may be applied to any remotely controlled device. Further, those of skill in the art will recognize that communication between the remote the remotely controlled device need not be limited to communication over a local area network but can 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 may be made to the present invention without following the example embodiments and applications illustrated and described herein, and without departing from the scope of the present disclosure.

[0120] The terminology used herein is for the purpose of describing various embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "includes," "including," "comprises," and "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, or components, and combinations thereof, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, or components, and combinations thereof. Further, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field, unless explicitly defined otherwise herein. All references to ""a / an / the element, apparatus, component, means, module, step, etc."" are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, module, step, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated.

[0121] ACRONYMS

[0122] 3GPP Third Generation Partnership Project

[0123] 5G Fifth Generation

[0124] AC Application Client

[0125] APIs Application Programming Interfaces

[0126] ASP Application Service Provider

[0127] DN Data Network

[0128] DNAI Data Network Access Identifier

[0129] DNN Data Network Name

[0130] EC Edge Computing

[0131] EAS Edge Application Server

[0132] ID Identifier

[0133] ECS Edge Configuration Server

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

[0135] EDN Edge Data Network

[0136] EEC Edge Enabler Client

[0137] EES Edge Enabler Server

[0138] I loT Industrial Internet of Things loT Internet of Things SEAL Service Enabler Architecture Layer

[0139] TR Technical Report

[0140] TS Technical Specification

[0141] UE User Equipment

Claims

CLAIMS1 . A method for common Edge Application Server, EAS, bundling in a communications network, the method comprising: transmitting (S-1201) from an edge enabler server to an edge configuration server a first request, wherein the first request is an EAS information get 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; determining (S-1102) at the edge configuration server a first EAS information including at least one EAS serving the application group for at least one of the identifiers received in the first request; and transmitting (S-1103) from the edge configuration server to the edge enabler server an EAS information get response including an indication of the determined first EAS information.

2. The method of claim 1 , further comprising: transmitting (S-1203) from the edge enabler server to the edge configuration server a second request, wherein the second request is a Common EAS information store 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 a bundled EAS identifier and endpoint list, a main EAS identifier or an EAS bundle identifier; determining (S-1105) at the edge configuration server a second EAS information including at least one EAS serving the application group for at least one of the identifiers received in the second request within the same EDN, particularly wherein the at least one EAS serving the application group is a common EAS for the bundle; and transmitting (S-1106) from the edge configuration server to the edge enabler server a Common EAS information store response including an indication of the second EAS information.

3. The method of any one of claims from claim 1 to claim 2, wherein the indication of a bundled EAS identifier list is a bundled EAS identifier.

4. The method of any one of claims from claim 1 to claim 3, wherein the method further comprises transmitting from an Edge Enabler Client, EEC, to the EES during EAS discovery an EAS discovery request including at least one of an EAS bundle identifier, a bundled EAS identifier list, or an Application Group identifier.

5. The method of any one of claims from claim 1 to claim 4, wherein the method further comprises transmitting from the EES to the ECS-ER an EAS information store request based on the received EAS discovery request.

6. The method of any one of claims from claim 1 to claim 5, wherein the method further comprises transmitting from the ECS-ER to the EES an indication recommending the use of at least one common EAS if the ECS-ER identifies existing common EAS information for the Application group in the same EDN.

7. The method of any one of claims from claim 1 to claim 6, wherein the method further comprises transmitting from the EEC to an Application Client, AC, an indication of the received EAS information, allowing the AC to connect to at least one EAS included in the EAS information.

8. The method of any one of claims from claim 1 to claim 7, wherein the EAS information get response includes a list of EAS endpoints and its associated EAS endpoints corresponding to the requested EAS identifiers.

9. The method of any one of claims from claim 1 to claim 8, wherein the Common EAS information store response includes a common EAS endpoint and its associated EAS endpoints corresponding to the requested EAS identifiers.

10. The method of any one of claims from claim 1 to claim 9, wherein the edge enabler server is an Edge Enabler Server, EES, the edge configuration server is an Edge Configuration Server, ECS.

11. A method performed by an edge configuration server for common Edge Application Server, EAS, bundling in a communications network, the method comprising: receiving (S-1101 ) at an edge configuration server from an edge enabler server a first request, wherein the first request is an EAS information get 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;determining (S-1102) at the edge configuration server a first EAS information including at least one EAS serving the application group for at least one of the identifiers received in the first request; and transmitting (S-1103) from the edge configuration server to the edge enabler server an EAS information get response including an indication of the determined first EAS information.

12. The method of claim 11 , further comprising: receiving (S-1104) at the edge configuration server from the edge enabler server a second request, wherein the second request is a Common EAS information store 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 a bundled EAS identifier and endpoint list, a main EAS identifier or an EAS bundle identifier; determining (S-1105) at the edge configuration server a second EAS information including at least one EAS serving the application group for at least one of the identifiers received in the second request within the same EDN, particularly wherein the at least one EAS serving the application group is a common EAS for the bundle; and transmitting (S-1106) from the edge configuration server to the edge enabler server a Common EAS information store response including an indication of the second EAS information.

13. The method of any one of claims from claim 11 to claim 12, wherein the indication of a bundled EAS identifier list is a bundled EAS identifier.

14. The method of any one of claims from claim 11 to claim 13, wherein the method further comprises transmitting from an Edge Enabler Client, EEC, to the EES during EAS discovery an EAS discovery request including at least one of an EAS bundle identifier, a bundled EAS identifier list, or an Application Group identifier.

15. The method of any one of claims from claim 11 to claim 14, wherein the method further comprises transmitting from the EES to the ECS-ER an EAS information store request based on the received EAS discovery request.

16. The method of any one of claims from claim 11 to claim 15, wherein the method further comprises transmitting from the ECS-ER to the EES an indication recommending theuse of at least one common EAS if the ECS-ER identifies existing common EAS information for the Application group in the same EDN.

17. The method of any one of claims from claim 11 to claim 16, wherein the method further comprises transmitting from the EEC to an Application Client, AC, an indication of the received EAS information, allowing the AC to connect to at least one EAS included in the EAS information.

18. The method of any one of claims from claim 11 to claim 17, wherein the EAS information get response includes a list of EAS endpoints and its associated EAS endpoints corresponding to the requested EAS identifiers.

19. The method of any one of claims from claim 11 to claim 18, wherein the Common EAS information store response includes a common EAS endpoint and its associated EAS endpoints corresponding to the requested EAS identifiers.

20. The method of any one of claims from claim 11 to claim 19, wherein the edge enabler server is an Edge Enabler Server, EES, the edge configuration server is an Edge Configuration Server, ECS.21 . A method performed by an edge enabler server for common Edge Application Server, EAS, bundling in a communications network, the method comprising: transmitting (S-1201) from an edge enabler server to an edge configuration server a first request, wherein the first request is an EAS information get 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 receiving (S-1202) at the edge enabler server from the edge configuration server an EAS information get response including an indication of a first EAS information including at least one EAS serving the application group for at least one of the identifiers in the first request.

22. The method of claim 21 , further comprising: transmitting (S-1203) from the edge enabler server to the edge configuration server a second request, wherein the second request is a Common EAS information store 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 requestincludes an indication of at least one of a bundled EAS identifier and endpoint list, a main EAS identifier or an EAS bundle identifier; and receiving (S-1204) at the edge enabler server from the edge configuration server a Common EAS information store response including an indication of a 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.

23. The method of any one of claims from claim 21 to claim 22, wherein the indication of a bundled EAS identifier list is a bundled EAS identifier.

24. The method of any one of claims from claim 21 to claim 23, wherein the method further comprises transmitting from an Edge Enabler Client, EEC, to the EES during EAS discovery an EAS discovery request including at least one of an EAS bundle identifier, a bundled EAS identifier list, or an Application Group identifier.

25. The method of any one of claims from claim 21 to claim 24, wherein the method further comprises transmitting from the EES to the ECS-ER an EAS information store request based on the received EAS discovery request.

26. The method of any one of claims from claim 21 to claim 25, wherein the method further comprises transmitting from the ECS-ER to the EES an indication recommending the use of at least one common EAS if the ECS-ER identifies existing common EAS information for the Application group in the same EDN.

27. The method of any one of claims from claim 21 to claim 26, wherein the method further comprises transmitting from the EEC to an Application Client, AC, an indication of the received EAS information, allowing the AC to connect to at least one EAS included in the EAS information.

28. The method of any one of claims from claim 21 to claim 27, wherein the EAS information get response includes a list of EAS endpoints and its associated EAS endpoints corresponding to the requested EAS identifiers.

29. The method of any one of claims from claim 21 to claim 28, wherein the Common EAS information store response includes a common EAS endpoint and its associated EAS endpoints corresponding to the requested EAS identifiers.

30. The method of any one of claims from claim 21 to claim 29, wherein the edge enabler server is an Edge Enabler Server, EES, the edge configuration server is an Edge Configuration Server, ECS.31 . Apparatus for common Edge Application Server, EAS, bundling in a communications 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 of any one of claims from claim 11 to claim 20.

32. Apparatus for common Edge Application Server, EAS, bundling in a communications 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 of any one of claims from claim 21 to claim 30.

33. A system comprising an apparatus as claimed in claim 31 , and an apparatus as claimed in 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 a method according to any one of claims from claim 11 to claim 30.

35. A computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to perform a method according to any of claims from claim 11 to claim 30.

36. A computer program product, embodied on a non-transitory machine-readable medium, comprising instructions which are executable by a processor, causing the processor to perform the method according to any of claims from claim 11 to claim 30.

Images