Techniques for controlling a service in a communication system

Abstract

The disclosure relates to a method (100) for controlling a service (112) in a communication system (110) based on at least one characteristic parameter of the communication system for serving at least one User Equipment, UE (131). A plurality of edge application servers (181, 182, 183) are arranged in the communication system (110) for controlling the service. The method comprises: receiving a request for instantiating one or more services on the plurality of edge application servers (181, 182, 183); upon receiving the request, instantiating the one or more services on a first edge application server (181); obtaining information about the at least one characteristic parameter of the communication system (110) for serving the at least one UE (131); and instantiating the one or more services on at least one second edge application server (182) based on the information about the at least one characteristic parameter of the communication system (110).

Description

[0001] TECHNIQUES FOR CONTROLLING A SERVICE IN A COMMUNICATION SYSTEM

[0002] TECHNICAL FIELD

[0003] The disclosure relates to the field of controlling services in communication systems, in particular communication networks such as 5G and 6G systems and beyond and edge computing or on demand provisioning of compute services very close to end-users. In particular, the disclosure relates to joint network and compute mechanisms for optimal provisioning of third-party services in mobile networks.

[0004] BACKGROUND

[0005] In current 3GPP networks, users can access edge applications from any location within the network. So, to realize the benefits of edge computing, edge nodes for a specific application have to be deployed near all possible network locations. Since this can be in the order of hundreds for a certain large city and tens of thousands or more for a certain country, deploying edge applications at all possible locations is not feasible and very costly at best. A more logical approach is to deploy edge nodes specifically at those locations where the service is needed. Therefore, to deploy services closer to end users and for an optimal service placement it is required to have some information of the users consuming the service. A main challenge in this context is that third party services are not aware of the connectivity nuances at the operator networks. Only operators have the capabilities to gather network-based location information about users consuming a particular service. Operators can identify which users are consuming a service solely based on the service description. Further, using current technology, it is not possible for the operator to infer the location information of users consuming a service using a scalable and efficient method. Further, it is not possible for the edge compute operator and the network operator to interact in order to instantiate the services. Further, it is not possible to target the instantiation to a certain location close to a cluster of users.

[0006] SUMMARY

[0007] This disclosure provides a solution for an efficient and targeted instantiation of services for a certain application in a certain region.

[0008] In particular, a solution is provided for an efficient instantiation of edge compute services according to the location of the users using the applications. The foregoing and other objects are achieved by the features of the independent claims. Further implementation forms are apparent from the dependent claims, the description and the figures.

[0009] The disclosure presents mechanisms to extend the current technology with architectural enhancements in order to realize user-close (optimal) placement of edge services.

[0010] This disclosure provides introduction of mechanisms and entities that are able to realize efficient and scalable instantiation and control of edge services. They rely on novel network functions for optimization of the location of resources, enhancements to the ECM so that it is able to coordinate instantiation and monitoring of compute and networking resources. Five phases for the instantiation procedures to enable the optimal service provisioning are defined as presented hereinafter.

[0011] The above-described problem is solved by defining and enhancing the following functions or procedures.

[0012] A) Definition of a new network function Placement Optimization Function (POF). This new POF handles data collection (from network and compute resources). It handles EAS (edge app) placement that is optimal for the user application and it provides a novel Npof interface to trigger edge location optimization near end users.

[0013] B) Enhancement of the Edge Computing Manager (ECM) with Edge Exposure API, i.e., methods and parameters for service providers to request deploying and optimizing their edge compute services; Interaction with the POF (Npof) to make use of the optimized EAS deployment strategy (service deployment near end users); and use of monitoring parameters from the edge nodes.

[0014] C) Definition of five phases of operator / 3rdparty interaction for optimized service delivery as described below with respect to Figure 4.

[0015] In order to describe the disclosure in detail, the following terms, abbreviations and notations will be used:

[0016] 3GPP third generation partnership project

[0017] UE user equipment

[0018] AF application function, application function entity PCF policy control function, policy control function entity

[0019] SMF session management function; session management function entity

[0020] AMF access and mobility management function; access and mobility management function entity

[0021] UPF user plane function; user plane function entity

[0022] SP service provider

[0023] POF placement optimization function

[0024] ECM edge computing manager

[0025] EAS edge application server

[0026] EES edge enabler server

[0027] S-EES source edge enabler server

[0028] T-EES target edge enabler server

[0029] EEC edge enabler client

[0030] ECS edge configuration server

[0031] API application programming interface

[0032] KPI Key Performance Indicator

[0033] SLA Service Level Agreement

[0034] A service-level agreement (SLA) is a contract between a service provider and its customers that documents what services the provider will furnish and defines the service standards the provider is obligated to meet. Service providers need SLAs to help them manage customer expectations and define the severity levels and circumstances under which they are not liable for outages or performance issues. Customers can also benefit from SLAs because the contract describes the performance characteristics of the service - which can be compared with other vendors' SLAs -- and sets forth the means for redressing service issues.

[0035] The term KPI (key performance indicator) refers to general key figures that relate to the success, performance or utilization of a company, its individual organizational units or a machine. KPIs serve management and controlling to control company processes, individual projects or departments and to evaluate them accordingly. Depending on the perspective, different parameters are used as KPIs.

[0036] In this disclosure, edge computing, edge nodes in mobile communication systems for performing edge computing and deployment and control of services in 5G and 6G mobile communication systems and 5G network functions are described. Edge computing, or on demand provisioning of compute services very close to end-users, enables next generation applications especially in 6G mobile communication systems. The main advantage of deep (meaning as close to the user as possible) edge computing is its ability to offer services with very low latencies and high throughput. Which is very important for applications with stringent requirements such as: video conferencing, virtual reality, and drone control. Since the edge nodes are deployed close to end users it is possible to realize the best service delivery conditions. Generally, the growing scale and advancement of virtualization of network functions (the basic logical mobile network building blocks) have led to more radical changes in the data and control components of mobile communication systems. Indeed, many operators are looking into how to make use of untapped resources (virtualization-enabled data centers and servers), deployed with the RAN, transit, and core networks.

[0037] In an edge computing scenario, the service provider provides the applications and usually deploys those compute instances in centralized clouds. The network operators on the other hand are responsible for creating and managing the mobile network as well as handling the connectivity between the user devices and the service providers. Evidently, the operator networks are the best place to deploy services near end users. This is mainly due to the proximity of RAN access points to the end users they are serving. This actually enables SLA guarantees.

[0038] One major issue of the current edge computing approach is the architectural split between network (represented by the operators) and compute (represented by service providers). Due to this split, the service providers are not aware of the operator network architecture, while the operators have no knowledge about the service / application internals. This creates a gap in interaction mechanisms between edge service providers and operators.

[0039] This disclosure presents embodiments for exploring the interaction between third party service providers and operators in order to increase the flexibility in deploying computing closer to the end user as well as reducing service latency and providing increased QoS & QoE. In addition, the amount of information exchanged outside the operator’s network can be reduced.

[0040] The concept can be illustrated by the following steps.

[0041] 1) A Service Provider detects many users coming from the same operator network / location.

[0042] 2) The Service Provider requests from the operator the instantiation of a service (or a subpart of it) at the operator's edge nodes.

[0043] 3) The operator finds the optimal place(s) for deploying the service(s).

[0044] 4) Service(s) are deployed and the network traffic is steered accordingly. 5) Service(s) life-cycle is managed by the operator, but can be influenced at any time by the service provider.

[0045] According to a first aspect, the disclosure relates to a method for controlling a service in a communication system based on at least one characteristic parameter of the communication system for serving at least one User Equipment (UE), wherein a plurality of edge application servers are arranged in the communication system for controlling the service to serve at least one UE, the method comprising: receiving, by a network entity of the communication system, a request issued by a service provider entity for instantiating one or more services on the plurality of edge application servers of the communication system and controlling the one or more services; upon receiving the request, instantiating the one or more services on a first edge application server of the plurality of edge application servers and controlling the one or more services via the first edge application server to serve the at least one UE; obtaining information about the at least one characteristic parameter of the communication system for serving the at least one UE; and instantiating the one or more services on at least one second edge application server of the plurality of edge application servers based on the information about the at least one characteristic parameter of the communication system for serving the at least one UE and controlling the one or more services via the at least one second edge application server to serve the at least one UE.

[0046] Such a method provides the advantage that the interaction between third party service providers and operators can be explored. The method increases the flexibility in deploying computing closer to the end user as well as reducing service latency and providing increased QoS & QoE. In addition, by applying such method, the amount of information exchanged outside the operator’s network can be reduced.

[0047] The service can be any kind of service, e.g., a communication service, a computation service, a location service, a storage service, a gaming service, or any other service.

[0048] Instantiating the one or more services on the edge application servers may include determining or identifying the one or more services, e.g., based on the service description, and actuating these services on the respective edge application servers. Instantiating may include mapping an identified, determined or advertised service to a reservable physical entity such as the edge application server on which this service is served. Upon receiving the request, the one or more services are instantiated on the first edge application server. This request is the request issued by the service provider entity which is received by the network entity.

[0049] Controlling the one or more services via the first edge application server to serve the at least one UE may include a respective signaling between the first edge application server, the network entity, and / or the at least one UE, e.g., the UE and / or the network entity transmits a respective service description to the first edge application server and the first edge application server provides the service to the UE according to the service description. The controlling may be performed according to any of the implementations of the method described below.

[0050] Controlling the one or more services via the at least one second edge application server to serve the at least one UE may include a respective signaling between the at least one second edge application server, the network entity, and / or the at least one UE, e.g., the UE and / or the network entity transmits a respective service description to the at least one second edge application server and the at least one second edge application server provides the service to the UE according to the service description. The controlling may be performed according to any of the implementations of the method described below.

[0051] The information about the at least one characteristic parameter may be obtained from the network, e.g., any network entity in the communication system. Such a network entity for obtaining or determining the at least one characteristic parameter may be, for example, a placement optimization function network entity as described below in more detail.

[0052] Obtaining information about the at least one characteristic parameter of the communication system for serving the at least one UE means here that the at least one UE is served with the one or more services based on the information about the at least one characteristic parameter. For example, if the characteristic parameter is a geographic location of the UE, the UE is served with the service running on the edge application server which is closest to the location of the UE. For example, if the characteristic parameter is an energy consumption of the edge application servers, the UE is served with the service running on the edge application server which has the lowest energy consumption. Further implementation examples are described below.

[0053] In an exemplary implementation of the method, the at least one characteristic parameter of the communication system for serving at least one UE comprises at least one of the following: a location of the at least one UE, a communication latency for a communication with the at least one UE, a bandwidth or throughput of a communication channel to the at least one UE, an energy consumption of each of the plurality of edge application servers.

[0054] This provides the advantage that various characteristic parameters of the communication system can be exploited to increase the flexibility in deploying computing closer to the end user as well as reducing service latency and providing increased QoS & QoE.

[0055] In an exemplary implementation of the method, the first edge application server is a default application server of the communication system; and a location of the at least one second edge application server is closer to a location of the at least one UE than a location of the first edge application server.

[0056] This provides the advantage that the method allows to reduce latency in the communication with the UE, when the second application server is located closer to the location of the UE.

[0057] In an exemplary implementation of the method, the request comprises a service descriptor for identifying the service, the method further comprises: identifying the service based on the service descriptor.

[0058] This provides the advantage that the service can be efficiently identified and a service-specific solution can be provided to the UE.

[0059] In an exemplary implementation of the method, the request comprises information about at least one Key Performance Indicator (KPI), to be fulfilled by the communication system in accordance with a predetermined Service Level Agreement (SLA).

[0060] This provides the advantage that the optimal placement strategy considers KPIs in accordance with a given SLA.

[0061] In an exemplary implementation of the method, the method comprises: monitoring data traffic between the at least one UE and the service to obtain the at least one characteristic parameter of the communication system for serving the at least one UE.

[0062] This provides the advantage that the characteristic parameter of the communication system can be efficiently determined just by monitoring the data traffic between UE and the service. In an exemplary implementation of the method, the method comprises: monitoring data traffic between the at least one UE and a central server to obtain the at least one characteristic parameter of the communication system for serving the at least one UE.

[0063] This provides the advantage that the characteristic parameter of the communication system can be efficiently determined by monitoring the data traffic between the UE and a central server.

[0064] In this scenario, the traffic can first be flowing to the central server (e.g., Internet) and not to a first edge server. The optimization then handles deploying the new edge server close to the UEs.

[0065] The central server can be for example a central application server outside the communication network, for example at the service provider.

[0066] In an exemplary implementation of the method, the method comprises: determining the at least one second edge application server from the plurality of edge application servers based on an optimal placement criterion with respect to the at least one UE and the plurality of edge application servers.

[0067] This provides the advantage that the second edge application server can be easily determined just by evaluating the optimal placement criterion with respect to the monitored data.

[0068] In an exemplary implementation of the method, the optimal placement criterion is based on at least one or any combination of the following: a minimum geographical distance between the at least one UE and the at least one second edge application server, a minimum latency for communication between the at least one UE and the at least one second edge application server, a maximum bandwidth or a maximum throughput for communication between the at least one UE and the at least one second edge application server, a minimum energy consumption of the at least one second edge application server with respect to the other edge application servers, fulfillment of at least one Key Performance Indicator (KPI) by the communication system in accordance with a predetermined Service Level Agreement (SLA), at least one second edge application server fulfilling a predefined SLA.

[0069] This provides the advantage that the optimal placement criterion can be flexible selected, i.e., not just the location of the UE but also parameters like bandwidth and throughput of the communication can be considered. The optimal placement criterion may include SLAs that are agreed upon beforehand; this means that we may choose a server (i.e., at least one second EAS) with a higher latency as long as it satisfies the SI_As.

[0070] In an exemplary implementation of the method, controlling the service via the at least one second edge application server to serve the at least one UE comprises: relocating an application context of the service utilized by the at least one UE from the first edge application server to the at least one second edge application server.

[0071] This provides the advantage that the UE can always be connected with the optimal edge application server, e.g., by relocating the context to another edge application server, for example when the UE has moved to another location or when bandwidth and / or throughput parameters of the network have changed.

[0072] In an exemplary implementation of the method, the method comprises: continuous monitoring of user status and / or and resource utilization of the at least one UE utilizing the service via the at least one second edge application server; and relocating an application context of the service towards another edge application server of the plurality of edge application servers based on the monitored user status and / or resource utilization.

[0073] This provides the advantage that the UE can always be connected with the optimal edge application server, e.g., by relocating the context to another edge application server, for example when user status and / or and resource utilization of the at least one UE have changed.

[0074] In an exemplary implementation of the method, the network entity of the communication system comprises an interface to a service provider entity for receiving the request for instantiating the one or more services.

[0075] This provides the advantage that the service provider can have easy access to the network entity for communicating his request for service instantiation.

[0076] In an exemplary implementation of the method, the method comprises: updating the service controlled via the at least one second edge application server and / or the first edge application server based on a service scale request received via the interface to the service provider entity; or deleting the service controlled via the at least one second edge application server and / or the first edge application server based on a service delete request received via the interface to the service provider entity.

[0077] This provides the advantage that the service can be easily updated based on the current situation.

[0078] In an exemplary implementation of the method, the network entity of the communication system comprises an Edge Computing Management (ECM) network entity according to 3GPP TS 28.538 specification.

[0079] This provides the advantage that the method can be applied with ECM according to 3GPP TS 28.538 specification.

[0080] In an exemplary implementation of the method, the ECM network entity comprises an Application Programmable Interface for exposing methods and parameters for service providers to request controlling and optimizing their services and for receiving monitoring parameters from the edge application servers.

[0081] This provides the advantage that the API can be easily used by service providers to request controlling and optimizing their services and for receiving monitoring parameters from the edge application servers.

[0082] In an exemplary implementation of the method, the communication system comprises a Placement Optimization Function (POF) network entity for determining placement criteria for placement of services based on the information about the at least one characteristic parameter of the communication system for serving the at least one UE.

[0083] This provides the advantage that based on this new network function (POF), the optimal placement criterion can be efficiently applied in the communication system.

[0084] In an exemplary implementation of the method, the method comprises: collecting data, by the POF network entity, from the communication system, the at least one UE, and from compute resources of the plurality of edge application servers; and determining the placement criteria, by the POF entity, based on the collected data and based on fulfillment of a predetermined Service Level Agreement (SLA). This provides the advantage that respective data can be easily monitored and collected for computing the optimal placement criterion.

[0085] In an exemplary implementation of the method, the POF network entity comprises an interface towards the network entity configured to initiate relocation of services from one edge application server to another edge application server of the plurality of edge application servers.

[0086] This provides the advantage that the POF network entity can initiate relocation of services based on his optimal placement strategy.

[0087] According to a second aspect, the disclosure relates to a network entity for controlling a service based on at least one characteristic parameter of a communication system for serving at least one User Equipment, UE, wherein the network entity is configured to: receive a request from a service provider entity for instantiating one or more services on a plurality of edge application servers of the communication system and controlling the one or more services; upon receiving the request, instantiate the one or more services on a first edge application server of the plurality of edge application servers and control the one or more services via the first edge application server to serve the at least one UE; obtain information about the at least one characteristic parameter of the communication system for serving the at least one UE; and instantiate the one or more services on at least one second edge application server of the plurality of edge application servers based on the information about the at least one characteristic parameter of the communication system and control the one or more services via the at least one second edge application server to serve the at least one UE.

[0088] Such a network entity, that may be an Edge Computing Management (ECM) network entity as described below in more detail, provides the advantage that the interaction between third party service providers and operators can be explored. The network entity increases the flexibility in deploying computing closer to the end user as well as reducing service latency and providing increased QoS & QoE. In addition, by applying such a network entity, the amount of information exchanged outside the operator’s network can be reduced.

[0089] The service can be any kind of service, e.g., a communication service, a computation service, a location service, a storage service, a gaming service, or any other service.

[0090] In an exemplary implementation of the network entity, the at least one characteristic parameter of the communication system for serving at least one UE comprises at least one of the following: a location of the at least one UE, a communication latency for a communication with the at least one UE, a bandwidth or throughput of a communication channel to the at least one UE, an energy consumption of each of the plurality of edge application servers.

[0091] This provides the advantage that various characteristic parameters of the communication system can be exploited to increase the flexibility in deploying computing closer to the end user as well as reducing service latency and providing increased QoS & QoE.

[0092] According to a third aspect, the disclosure relates to a Placement Optimization Function, POF, network entity for determining a placement criterion for placement of at least one service based on at least one characteristic parameter of a communication system, wherein the POF network entity is configured to: receive, from a network entity of the communication system, a placement optimization request for determining a placement criterion for placement of at least one service in the communication system; obtain at least one characteristic parameter of the communication system from the communication system; determine the placement criterion based on the at least one characteristic parameter of the communication system; and provide the placement criterion to the network entity of the communication system.

[0093] Such a POF network entity provides the advantage that an optimal placement strategy can be determined which saves resources in the communication system.

[0094] In an exemplary implementation of the POF network entity, the at least one characteristic parameter of the communication system comprises at least one of the following: a location of the at least one UE served by the at least one service, a communication latency for a communication with the at least one UE, a bandwidth or throughput of a communication channel to the at least one UE, an energy consumption of each of a plurality of edge application servers controlling the at least one service to serve the at least one UE.

[0095] This provides the advantage that various characteristic parameters of the communication system can be exploited to increase the flexibility in deploying computing closer to the end user as well as reducing service latency and providing increased QoS & QoE.

[0096] In an exemplary implementation of the POF network entity, the POF network entity is configured to determine the placement criterion based on at least one of the following: a minimum distance of the at least one UE to a respective edge application server of the plurality of edge application servers, a minimum communication latency of a communication between the at least one UE and a respective edge application server of the plurality of edge application servers, a maximum bandwidth or maximum throughput of a communication channel between the at least one UE and a respective edge application server of the plurality of edge application servers, a minimum energy consumption of a respective edge application server of the plurality of edge application servers.

[0097] By such POF network entity an optimal placement criterion can be advantageously determined which saves resources in the communication system and provides efficient service placement.

[0098] According to a fourth aspect, the disclosure relates to a communication system for controlling a service based on at least one characteristic parameter of the communication system for serving at least one User Equipment, UE, the communication system comprising: a plurality of edge application servers for controlling one or more services to serve at least one UE; an Edge Computing Management, ECM, network entity configured to receive a request issued by a service provider entity for instantiating one or more services on the plurality of edge application servers and controlling the one or more services; wherein the ECM network entity is configured, upon receiving the request, to instantiate the one or more services on a first edge application server of the plurality of edge application servers and to control the one or more services via the first edge application server to serve the at least one UE; and a Placement Optimization Function, POF, network entity for determining a placement criterion for placement of the service based on at least one characteristic parameter of the communication system for serving the at least one UE; wherein the ECM network entity is configured to instantiate the one or more services on at least one second edge application server of the plurality of edge application servers based on the placement criterion determined by the POF network entity and to control the one or more services via the at least one second edge application server to serve the at least one UE.

[0099] Such a communication system provides the advantage that the interaction between third party service providers and operators can be explored. This increases the flexibility in deploying computing closer to the end user as well as reducing service latency and providing increased QoS & QoE. In addition, the amount of information exchanged outside the operator’s network can be reduced.

[0100] In an exemplary implementation of the communication system, the at least one second edge application server is configured to initiate sending of a notification to an Edge Enabler Client, EEC, of the at least one UE or to a network entity of the communication system, the notification indicating the controlling of the one or more services via the at least one second edge application server. This provides the advantage that the EEC in a UE can be efficiently informed about the optimal services and controlled to use these optimal services.

[0101] According to a fifth aspect, the disclosure relates to a computer program product including computer executable code or computer executable instructions that, when executed, causes at least one computer to execute the method according to the first aspect described above.

[0102] The computer program product may run on a controller or processor for controlling the abovedescribed service in a communication system, e.g., one of the components of the communication system described in Figure 1 or Figure 2.

[0103] According to a sixth aspect, the disclosure relates to a computer-readable medium, storing instructions that, when executed by a computer, cause the computer to execute the method according to the first aspect described above. Such a computer readable medium may be a non-transient readable storage medium. The instructions stored on the computer-readable medium may be executed by a controller or processor for controlling the above-described service in a communication system, e.g., one of the components of the communication system described in Figure 1 or Figure 2.

[0104] BRIEF DESCRIPTION OF THE DRAWINGS

[0105] Further embodiments of the disclosure will be described with respect to the following figures, in which:

[0106] Figure 1 shows a schematic diagram illustrating a method 100 for controlling a service 112 in a communication system 110 according to an example of the disclosure;

[0107] Figure 2 shows a block diagram illustrating a communication system 200 for controlling a service based on a at least one characteristic parameter of the communication system according to an example of the disclosure;

[0108] Figure 3 shows an exemplary block diagram of a communication system 300 using an edge data network 181 , 182, 183 for provisioning of compute services close to end-users;

[0109] Figure 4 shows an exemplary message flow chart 400 illustrating the five phases of optimized service deployment according to an example of the disclosure;

[0110] Figure 5 shows an exemplary message flow chart 500 illustrating implementation of the first phase of optimized service deployment based on a first embodiment;

[0111] Figure 6 shows an exemplary message flow chart 600 illustrating implementation of the second phase of optimized service deployment based on the first embodiment; Figure 7 shows an exemplary message flow chart 700 illustrating implementation of the third phase of optimized service deployment based on the first embodiment;

[0112] Figure 8 shows an exemplary message flow chart 800 illustrating implementation of the fourth phase of optimized service deployment based on the first embodiment;

[0113] Figure 9 shows an exemplary message flow chart 900 illustrating implementation of the fifth phase of optimized service deployment based on the first embodiment;

[0114] Figure 10 shows an exemplary message flow chart 1000 illustrating implementation of the first phase of optimized service deployment based on a second embodiment;

[0115] Figure 11 shows an exemplary message flow chart 1100 illustrating implementation of the second phase of optimized service deployment based on the second embodiment;

[0116] Figure 12 shows an exemplary message flow chart 1200 illustrating implementation of the third phase of optimized service deployment based on the second embodiment;

[0117] Figure 13 shows an exemplary message flow chart 1300 illustrating implementation of the fourth phase of optimized service deployment based on the second embodiment; and

[0118] Figure 14 shows an exemplary message flow chart 1400 illustrating implementation of the fifth phase of optimized service deployment based on the second embodiment.

[0119] DETAILED DESCRIPTION OF EMBODIMENTS

[0120] In the following detailed description, reference is made to the accompanying drawings, which form a part thereof, and in which is shown by way of illustration specific aspects in which the disclosure may be practiced. It is understood that other aspects may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure. The following detailed description, therefore, is not to be taken in a limiting sense, and the scope of the present disclosure is defined by the appended claims.

[0121] It is understood that comments made in connection with a described method may also hold true for a corresponding device or system configured to perform the method and vice versa. For example, if a specific method step is described, a corresponding device may include a unit to perform the described method step, even if such unit is not explicitly described or illustrated in the figures. Further, it is understood that the features of the various exemplary aspects described herein may be combined with each other, unless specifically noted otherwise.

[0122] Figure 1 shows a schematic diagram illustrating a method 100 for controlling a service 112 in a communication system 110 according to the disclosure. Figure 1 also illustrates the architecture of an end-to-end data delivery network representing the communication system 110 and the method steps according to the disclosure for controlling a service 112 in the communication system 110.

[0123] The service provider 121 provides the applications and usually deploys those compute instances in centralized clouds. The network operators 111 on the other hand are responsible for creating and managing the mobile network as well as handling the connectivity between the user devices 131 , 132, 133 and the service providers 121.

[0124] The communication system 110 (corresponding to the communication system 200 in Figure 2) may be based on 3GPP standardization but is not restricted to that. In particular, the communication system 110 may comprise the following 5G network functions of the 5G reference point architecture (see also Figure 2) as specified in 3GPP TS 38.300 and 3GPP TS 23.501 specifications: UPF, SMF, PCF, AMF and the following edge functionalities as specified in 3GPP TS 23.558 and TS 28.538: EES, EEC, ECS, EAS, ECM.

[0125] UPF stands for User plane function. The functions of 5G NR UPF node or UPF entity are: Anchor point for lntra- / lnter-RAT mobility (when applicable); External PDU Session point of interconnect to Data Network; Packet routing & forwarding; Packet inspection; User Plane part of policy rule enforcement, e.g. Gating, Redirection, Traffic steering; Lawful intercept (UP collection); Traffic usage reporting; QoS handling for user plane, e.g. UL / DL rate enforcement, Reflective QoS marking in DL; Uplink Traffic verification (SDF to QoS Flow mapping); Transport level packet marking in the uplink and downlink; Downlink packet buffering and downlink data notification triggering; Sending and forwarding of one or more "end marker" to the source NG-RAN node.

[0126] SMF stands for Session Management Function. The functions of 5G NR SMF node or SMF entity are: Session Management; UE IP address allocation and management; Selection and control of UP function; Configures traffic steering at UPF to route traffic to proper destination; Control part of policy enforcement and QoS; Downlink Data Notification.

[0127] PCF stands for Policy Control Function. The functions of 5G NR PCF node or PCF entity are: Support of unified policy framework to govern network behavior; Providing policy rules to Control Plane function(s) to enforce them; Accessing subscription information relevant for policy decisions in a Unified Data Repository (UDR). AMF stands for Access and Mobility Management Function. AMF is part of the 3GPP 5G Architecture. Its primary tasks includes: Registration Management, Connection Management, Reachability Management, Mobility Management and various function relating to security and access management and authorization.

[0128] The edge architecture according to 3GPP TS 23.558 is provided for enabling Edge Applications. It includes Edge enabler server (EES) that represents the network-side edge control plane; Edge enabler client (EEC) that represents the UE-side edge control plane; Edge configuration server (ECS) that provides edge configuration support for EEC and EES. The edge application server (EAS) represents the actual edge server. The edge architecture can be applied to enable UEs to consume edge applications.

[0129] Edge Computing Management (ECM) according to 3GPP TS 28.538 focuses on life cycle management for edge services in 3GPP networks, EAS, EES, ECS deployment and termination. Enhancements to the ECM as presented in this disclosure can be applied to handle third-party service request in the operator’s domain, to handle targeted EAS (edge server) placement near end users consuming a service; and to use monitoring information from the mobile and edge nodes.

[0130] In this disclosure, a new network function Placement Optimization Function (POF) is defined as one entity of the communication system 110 shown in Figure 1. This new POF handles data collection (from network and compute resources). It handles EAS (edge app) placement that is optimal for the user application and it provides a novel Npof interface 161 (see Figure 2 for more details) to trigger edge location optimization near end users.

[0131] The Edge Computing Manager (ECM) 140 as shown in Figure 1 is enhanced with Edge Exposure API 122 shown in Figure 1, i.e., methods and parameters for service providers 121 to request deploying and optimizing their edge compute services; Interaction with the POF 160 (Npof 161) to make use of the optimized EAS deployment strategy (service deployment near end users); and use of monitoring parameters from the edge nodes 181 , 182, 183.

[0132] Five phases of operator / 3rdparty interaction can be defined for optimized service delivery as described below with respect to Figure 4.

[0133] The Placement Optimization Function (POF) 160 utilizes the various APIs of the service-based interfaces of the 5G / 6G core network to subscribe to monitoring information regarding networking infrastructure (e.g., user location and path latency, bandwidth, etc..). For example, the user location can be obtained from the AMF via the Namf_EventExposure API (3GPP 29.518), and the path latency from the SMF using the Nsmf_EventExposure API (3GPP 29.508). In relation to the computing infrastructure, the POF 160 receives information from the ECM 140 (e.g., bandwidth, energy consumption of edge nodes 181 , 182, 183 and virtual and physical resource utilization).

[0134] The POF 160 works in both reactive and proactive operation modes. In the first, the POF 160 reacts to a request from the ECM 140, which requests the optimal placement strategy for a particular service 112 that needs to be deployed in the operator’s 111 domain 110. This relates to the initial request from a service provider 121. In the latter, the POF 160 continuously monitors the network and computing infrastructure conditions to assess if the current placement strategy is still optimal or if migration and / or scaling are required. Should the placement be no longer optimal, the POF 160 provides a new placement strategy to the ECM 140.

[0135] The POF 160 runs one or many algorithms to compute the optimal placement strategy for a given set of constraints. The goal of these algorithms is to lower the cost to the operator 111 while providing optimal QoS to the users. Exemplary implementations how the POF 160 can calculate the optimal deployment strategy are presented in the following:

[0136] 1) The first exemplary implementation is a simple strategy based on choosing the edge locations that minimize the geographical distance between the user devices 131 , 132, 133 and the edge applications 181 , 182, 183. This can be done using a brute force search over edge locations while using the geographical location information available from other network functions such as the SMF 130 and PCF 150 and other network functions.

[0137] 2) The second exemplary implementation is a simple strategy based on choosing the edge locations that minimize the latency between the user devices 131 , 132, 133 and the edge applications 181 , 182, 183. This can be done using a brute force search over edge locations while using the latency information available from other network functions such as the SMF 130 and PCF 150 and other network functions.

[0138] 3) The third exemplary implementation is a simple strategy based on choosing the edge locations that maximize the bandwidth or throughput between the user devices 131, 132, 133 and the edge applications 181, 182, 183. This can be done using a brute force search over edge locations while using the bandwidth information available from other network functions such as the SMF 130 and PCF 159 and other network functions. 4) The fourth exemplary implementation is a simple strategy based on choosing the edge locations that minimize the energy consumption of the edge applications 181 , 182, 183. This can be done using a brute force search over edge locations while using the energy consumption information available from other network functions such as the SMF 130 and PCF 150 and other network functions.

[0139] 5) The fifth exemplary implementation is based on combining all the important aspects above (geographical location, latency, bandwidth, energy consumption) into one optimization algorithm. This is based on a technique called Order of Preference by Similarity to Ideal Solution (TOPSIS). This is a multi-criteria decision-making algorithm for edge service migration, targeting fast convergence with high accuracy of automated service migration.

[0140] In the following, the method 100 for controlling a service 112 in the communication system 110 based on at least one characteristic parameter of the communication system 110 is described in a generic representation but with respect to the example network configuration shown in Figure 1. The communication system 110 can be any communication system or operator network. It is not restricted to the 5G network as shown in Figure 1.

[0141] The method 100 can be used for controlling a service 112 in a communication system 110 based on at least one characteristic parameter of the communication system 110 for serving at least one User Equipment, UE 131, wherein a plurality of edge application servers 181 , 182, 183 are arranged in the communication system 110 for controlling the service 112 to serve at least one UE 131.

[0142] The method 100 comprises: receiving, by a network entity 140 of the communication system 110, a request 101 issued by a service provider entity 123 for instantiating one or more services on the plurality of edge application servers 181, 182, 183 of the communication system 110 and controlling the one or more services 112.

[0143] The method 100 comprises: upon receiving the request 101 , instantiating the one or more services on a first edge application server 181 of the plurality of edge application servers 181 , 182, 183 and controlling the one or more services 112 via the first edge application server 181 to serve the at least one U E 131.

[0144] The method 100 comprises: obtaining information about the at least one characteristic parameter of the communication system 110 for serving the at least one UE 131. The method 100 comprises: instantiating the one or more services on at least one second edge application server 182 of the plurality of edge application servers 181 , 182, 183 based on the information about the at least one characteristic parameter of the communication system 110 for serving the at least one UE 131 and controlling the one or more services 112 via the at least one second edge application server 182 to serve the at least one UE 131.

[0145] The service can be any kind of service, e.g., a communication service, a computation service, a location service, a storage service, a gaming service, or any other service.

[0146] The at least one characteristic parameter of the communication system 110 for serving at least one UE 131 may comprise at least one of the following: a location of the at least one UE 131 , a communication latency for a communication with the at least one UE 131 , a bandwidth or throughput of a communication channel to the at least one UE 131 , an energy consumption of each of the plurality of edge application servers 181 , 182, 183.

[0147] The first edge application server 181 may, for example, be a default application server of the communication system 110. A location of the at least one second edge application server 182 may be closer to a location of the at least one UE 131 than a location of the first edge application server 181.

[0148] The request 101 may comprise a service descriptor for identifying the service 112. The method 100 may further comprise: identifying the service 112 based on the service descriptor.

[0149] The request 101 may comprise information about at least one Key Performance Indicator, KPI, to be fulfilled by the communication system 110 in accordance with a predetermined Service Level Agreement, SLA.

[0150] The method 100 may further comprise: monitoring data traffic 301 between the at least one UE 131 and the service 112 to obtain the at least one characteristic parameter of the communication system 110 for serving the at least one UE 131.

[0151] The method 100 may comprise: monitoring data traffic 301 between the at least one UE 131 and a central server to obtain the at least one characteristic parameter of the communication system 110 for serving the at least one UE 131. In this scenario, the traffic could first be flowing to the central server (e.g., Internet) and not to a first edge server. The optimization then handles deploying the new edge server close to the UEs.

[0152] The central server can be for example a central application server outside the communication network, for example at the service provider.

[0153] The method 100 may comprise: determining the at least one second edge application server 182 from the plurality of edge application servers 181 , 182, 183 based on an optimal placement criterion with respect to the at least one UE 131 and the plurality of edge application servers 181 , 182, 183.

[0154] The optimal placement criterion may be based on at least one or any combination of the following: a minimum geographical distance between the at least one UE 131 and the at least one second edge application server 182, e.g., as described above, a minimum latency for communication between the at least one UE 131 and the at least one second edge application server 182, a maximum bandwidth or a maximum throughput for communication between the at least one UE 131 and the at least one second edge application server 182, a minimum energy consumption of the at least one second edge application server 182 with respect to the other edge application servers, fulfillment of at least one Key Performance Indicator, KPI, by the communication system 110 in accordance with a predetermined Service Level Agreement, SLA, at least one second edge application server fulfilling a predefined SLA.

[0155] The optimal placement criterion may include SLAs that are agreed upon beforehand; this means that we may choose a server (i.e., at least one second EAS) with a higher latency as long as it satisfies the SLAs.

[0156] Controlling the service 112 via the at least one second edge application server 182 to serve the at least one UE 131 may comprises: relocating an application context of the service 112 utilized by the at least one UE 131 from the first edge application server 181 to the at least one second edge application server 182, e.g., as described below with respect to Figures 4 to 14.

[0157] The method 100 may further comprise: continuous monitoring of user status and / or and resource utilization of the at least one UE 131 utilizing the service 112 via the at least one second edge application server 182; and relocating an application context of the service 112 towards another edge application server 183 of the plurality of edge application servers 181 , 182, 183 based on the monitored user status and / or resource utilization, e.g., as described below with respect to Figures 4 to 14.

[0158] The network entity 140 of the communication system 110 may comprise an interface 122 to a service provider entity 123 for receiving the request 101 for instantiating the one or more services 112.

[0159] The method 100 may further comprise: updating the service 112 controlled via the at least one second edge application server 182 and / or the first edge application server 181 based on a service scale request 451 received via the interface to the service provider entity 123, e.g., as described below with respect to Figures 4 to 14; or deleting the service 112 controlled via the at least one second edge application server 182 and / or the first edge application server 181 based on a service delete request 452 received via the interface 122 to the service provider entity 123, e.g., as described below with respect to Figures 4 to 14.

[0160] The network entity 140 of the communication system 110 may comprise an Edge Computing Management, ECM, network entity according to 3GPP TS 28.538 specification, e.g., according to the exemplary representation in Figure 1.

[0161] The ECM network entity 140 may comprises an Application Programmable Interface 122 for exposing methods and parameters for service providers 121 to request controlling and optimizing their services and for receiving monitoring parameters from the edge application servers 181 , 182, 183, e.g., according to the exemplary representation in Figure 1.

[0162] The communication system 110 may comprise a Placement Optimization Function, POF, network entity 160 for determining placement criteria for placement of services 112 based on the information about the at least one characteristic parameter of the communication system 110 for serving the at least one UE 131 , e.g., a POF entity having a functionality as described above.

[0163] The method 100 may further comprise: collecting data, by the POF network entity 160, from the communication system 110, the at least one UE 131, and / or from compute resources of the plurality of edge application servers 181 , 182, 183; and determining the placement criteria, by the POF entity 160, based on the collected data and based on fulfillment of a predetermined Service Level Agreement, SLA. The POF network entity 160 may comprise an interface 161 towards the network entity 140 configured to initiate relocation of services from one edge application server to another edge application server of the plurality of edge application servers 181 , 182, 183.

[0164] The method 100 for controlling a service in the communication system 110 can be implemented based on two Embodiments, as exemplarily described in the following. It understands that other embodiments not described here can be applied as well.

[0165] In a first Embodiment, also referred to as Optimal Service Placement for 3GPP edge computing environment, the following steps 101 , 102, 103 and 105 are implemented:

[0166] 1) Service Description and instantiation request, 101 : The ECM (TS 23.538) is extended for edge exposure to third-party service providers. Service providers leverage this API to place services (or subparts of it) closer to the users while requiring no insights on the core network.

[0167] 2) Novel Network Function for optimal placement strategy computation, 102: The new network function POF 160 (realized as an application function, AF) utilizes various network and edge computing monitoring parameters to compute an optimal placement strategy for service(s) to be instantiated.

[0168] 3) Users utilizing the services are located, 103: Users are located by tracing the application usage. This information is consumed by the POF 160 for optimal placing calculations.

[0169] 4) Services are instantiated closer to the users, 105: Services are instantiated and deployed close to the users, consequently saving resources.

[0170] In a second Embodiment, also referred to as Placement of the POF into different NFs, two variants can be implemented.

[0171] In a first variant A of the second embodiment, the POF is jointly realized on the ECM and NWDAF. In this first variant A, the following steps are implemented:

[0172] 1) NWDAF (23.501) is able to collect monitoring data regarding the edge infrastructure from the ECM. The NWDAF complements the network monitoring data it gathers from the core functions with monitoring data related to the edge infrastructure (e.g., energy consumption and resource utilization). 2) The NWDAF is extended to support algorithms for optimal placement of 3rd party applications, and to expose this information to other entities.

[0173] 3) The ECM subscribes to data analytics related to placement strategy from the NWDAF. By subscribing this information, the ECM triggers the computation of the optimal placement.

[0174] 4) The NWDAF computes and provides the optimal placement strategy to the ECM upon subscription. This subscription will also trigger continuous monitoring and reporting notifications to the ECM whenever the previously provided placement strategy is no longer optimal.

[0175] 5) Upon the notification from the NWDAF, the ECM enforces (e.g., instantiates, migrates, deletes, etc...) the placement strategy provided by the NWDAF.

[0176] It understands that further steps may be implemented, the sequence of the above steps may be changed, or steps can be subdivided or merged.

[0177] In a second variant B of the second embodiment, the POF is fully realized on the ECM. In this second variant B, the following steps are implemented:

[0178] 1) The ECM is extended to gather monitoring data from the core of the network (e.g., path latency and user location).

[0179] 2) The ECM implements the placement strategy algorithm and combines the network-related information retrieved from the core of the network with the information it already collects about the edge computing infrastructure. The combined information is used by the implemented algorithms to compute the optimal placement strategy for a particular service.

[0180] 3) The ECM places the service according to the computed placement strategy

[0181] 4) The ECM continuously monitors both network and computing conditions, which are fed to the optimization algorithms so as to assess if the current placement strategy is still optimal. In case it is no longer optimal, the ECM enforces the new placement strategy.

[0182] It understands that further steps may be implemented, the sequence of the above steps may be changed, or steps can be subdivided or merged.

[0183] Figure 2 shows a block diagram illustrating a communication system 200 for controlling a service based on a at least one characteristic parameter of the communication system according to the disclosure. The communication system may correspond to the communication system 110 described above with respect to Figure 1. In this communication system 200 shown in Figure 2, the network entities shown in Figure 1 are described in a 5G context.

[0184] The communication system 200 can be used for controlling a service 112 based on at least one characteristic parameter of the communication system 200 for serving at least one User Equipment, UE 131.

[0185] The communication system 200 comprises a plurality of edge application servers 181, 182, 183 for controlling one or more services 112 to serve at least one UE 131.

[0186] The communication system 200 comprises an Edge Computing Management, ECM, network entity 140 configured to receive a request 101 issued by a service provider entity 123 for instantiating one or more services on the plurality of edge application servers 181 , 182, 183 and controlling the one or more services 112.

[0187] The ECM network entity 140 is configured, upon receiving the request 101, to instantiate the one or more services on a first edge application server 181 of the plurality of edge application servers 181 , 182, 183 and to control the one or more services 112 via the first edge application server 181 to serve the at least one UE 131.

[0188] The communication system 200 comprises a Placement Optimization Function, POF, network entity 160 for determining a placement criterion for placement of the service 112 based on at least one characteristic parameter of the communication system 200 for serving the at least one UE 131 , e.g., as described above with respect to Figure 1.

[0189] The ECM network entity 140 may be configured to instantiate the one or more services 112 on at least one second edge application server 182 of the plurality of edge application servers 181 , 182, 183 based on the placement criterion determined by the POF network entity 160 and to control the one or more services 112 via the at least one second edge application server 182 to serve the at least one UE 131 , e.g., as described above with respect to Figure 1.

[0190] The at least one second edge application server 182 may be configured to initiate sending of a notification 434 to an Edge Enabler Client, EEC, 134 of the at least one UE or to a network entity 150 of the communication system 200, the notification 434 indicating the controlling of the one or more services 112 via the at least one second edge application server 182, e.g., as described below with respect to Figures 4 to 14. In the following, the ECM network entity 140, that can be generally described as a network entity within the communication system 200, and the POF network entity 160, that can be generally described as another (or even the same) network entity within the communication system 200, are described.

[0191] The ECM entity 140 can be used for controlling a service 112 based on at least one characteristic parameter of a communication system 200 for serving at least one User Equipment, UE 131.

[0192] The ECM network entity 140 is configured to: receive a request 101 from a service provider entity 123 for instantiating one or more services on a plurality of edge application servers 181 , 182, 183 of the communication system 200 and controlling the one or more services 112; upon receiving the request 101 , instantiate the one or more services on a first edge application server 181 of the plurality of edge application servers 181 , 182, 183 and control the one or more services 112 via the first edge application server 181 to serve the at least one UE 131 ; obtain information about the at least one characteristic parameter of the communication system 200 for serving the at least one UE 131 ; and instantiate the one or more services 112 on at least one second edge application server 182 of the plurality of edge application servers 181 , 182, 183 based on the information about the at least one characteristic parameter of the communication system 200 and control the one or more services 112 via the at least one second edge application server 182 to serve the at least one UE 131 , e.g. as described above with respect to the method shown in Figure 1.

[0193] As described above, instantiating the one or more services 112 on the edge application servers 181 , 182, 183 may include determining or identifying the one or more services 112, e.g., based on the service description, and actuating these services 112 on the respective edge application servers 181 , 182, 183. Instantiating may include mapping an identified, determined or advertised service to a reservable physical entity such as the edge application server 181 , 182, 183 on which this service 112 is served.

[0194] Upon receiving the request 101 , the one or more services 112 are instantiated on the first edge application server 181. This request 101 is the request 101 issued by the service provider entity 123 which is received by the ECM network entity 140.

[0195] Controlling the one or more services 112 via the first edge application server 181 to serve the at least one UE 131 may include a respective signaling between the first edge application server 181, the ECM network entity 140, and / or the at least one UE 131 , e.g., the UE 131 and / or the ECM network entity 140 transmits a respective service description to the first edge application server 181 and the first edge application server 181 provides the service 112 to the UE 131 according to the service description. The controlling may be performed according to any of the implementations of the method 100 as described above with respect to Figure 1.

[0196] Controlling the one or more services 112 via the at least one second edge application server 182 to serve the at least one UE 131 may include a respective signaling between the at least one second edge application server 182, the ECM network entity 140, and / or the at least one UE 131 , e.g., the UE 131 and / or the ECM network entity 140 transmits a respective service description to the at least one second edge application server 182 and the at least one second edge application server 182 provides the service 112 to the UE 131 according to the service description. The controlling may be performed according to any of the implementations of the method described above with respect to Figure 1.

[0197] The information about the at least one characteristic parameter may be obtained from the network, e.g., any network entity in the communication system 200. Such a network entity for obtaining or determining the at least one characteristic parameter may be, for example, the placement optimization function network entity 160 as shown in Figure 2 and described below in more detail.

[0198] Obtaining information about the at least one characteristic parameter of the communication system for serving the at least one UE 131 means here that the at least one UE 131 is served with the one or more services 112 based on the information about the at least one characteristic parameter. For example, if the characteristic parameter is a geographic location of the UE 131 , the UE 131 is served with the service 112 running on the edge application server which is closest to the location of the UE 131. For example, if the characteristic parameter is an energy consumption of the edge application servers, the UE is served with the service running on the edge application server which has the lowest energy consumption.

[0199] The at least one characteristic parameter of the communication system 200 for serving at least one UE 131 may comprise at least one of the following: a location of the at least one UE 131 , a communication latency for a communication with the at least one UE 131 , a bandwidth or throughput of a communication channel to the at least one UE 131 , an energy consumption of each of the plurality of edge application servers 181, 182, 183. The POF network entity 160 can be used for determining a placement criterion for placement of at least one service 112 based on at least one characteristic parameter of a communication system 200.

[0200] The POF network entity 160 is configured to: receive, from a network entity 140 of the communication system 200, a placement optimization request for determining a placement criterion for placement of at least one service 112 in the communication system 200; obtain at least one characteristic parameter of the communication system 200 from the communication system 200; determine the placement criterion based on the at least one characteristic parameter of the communication system 200; and provide the placement criterion to the network entity (140) of the communication system 200.

[0201] As described above, the at least one characteristic parameter of the communication system 200 for serving at least one UE 131 may comprise at least one of the following: a location of the at least one UE 131 , a communication latency for a communication with the at least one UE 131 , a bandwidth or throughput of a communication channel to the at least one UE 131 , an energy consumption of each of the plurality of edge application servers 181, 182, 183.

[0202] The POF network entity 160 may be configured to determine the placement criterion based on at least one of the following: a minimum distance of the at least one UE 131 to a respective edge application server of the plurality of edge application servers 181 , 182, 183, a minimum communication latency of a communication between the at least one UE 131 and a respective edge application server of the plurality of edge application servers 181 , 182, 183, a maximum bandwidth or maximum throughput of a communication channel between the at least one UE 131 and a respective edge application server of the plurality of edge application servers 181 , 182, 183, a minimum energy consumption of a respective edge application server of the plurality of edge application servers 181, 182, 183.

[0203] Figure 3 shows a block diagram of a communication system 300 using an edge data network 181 , 182, 183 for provisioning of compute services close to end-users.

[0204] The edge data network represents the edge nodes 181 , 182, 183 as shown and described above with respect to Figure 1. Application data traffic 301 is transmitted between the edge data network 181 , 182, 183 and the UEs 131 , 132, 133 via the 3GPP core network 110 that may correspond to the communication system described above with respect to Figures 1 and 2. The edge data network 181 , 182, 183 may correspond to the edge data network 181 , 182, 183 depicted in Figure 2 and the edge configuration server, ECS 240 may correspond to the ECS 240 shown in Figure 2.

[0205] The edge data network 181 , 182, 183 comprises one or more edge application servers 220 and one or more edge enabler servers 230.

[0206] The ECS 240 is connected via the 3GPP core network 110 with an edge enabler client, EEC 134 implemented on a respective UE 131 , 132, 133.

[0207] The components of the edge data network may be designed according to 3GPP TS 23.558 Architecture for enabling Edge Applications. I.e., Edge enabler server (EES) provides the functionality of network-side edge control plane, Edge enabler client (EEC) provides the functionality of UE-side edge control plane, Edge configuration server (ECS) provides the functionality of edge configuration support for EEC and EES; and Edge application server (EAS) provides the actual edge server.

[0208] The ECM 140 (shown in Figure 1) may be designed according to 3GPP TS 28.538 Edge Computing Management (ECM). I.e., its focus is on life cycle management for edge services in 3GPP networks; EAS, EES, ECS deployment and termination.

[0209] Interaction between the service provider 121 and network provider 111 (see Figure 1) is mainly handled using the application function (AF). The AF provides the basic interface.

[0210] In this disclosure, the functionality of the 3GPP core network 110 is enhanced by the following functions / procedures:

[0211] The new network function POF entity 160 as described above with respect to Figures 1 and 2, that handles data collection (from network and compute resources), handles EAS 220 placement that is optimal for the user application and provides a Npof interface 161 to trigger edge location optimization near end users, e.g., as described above with respect to Figures 1 and 2.

[0212] The ECM 140 network entity is enhanced with Edge Exposure API 122: methods and parameters for service providers to request deploying and optimizing their edge compute services; interaction with the POF 160 (via Npof interface 161) to make use of the optimized EAS 220 deployment strategy (service deployment near end users); and using monitoring parameters from the edge nodes 181 , 182, 183, e.g., as described above with respect to Figures 1 and 2. The five phases of operator / 3rdparty interaction for optimized service delivery are defined as described below with respect to Figures 4 to 14.

[0213] Figure 4 shows an exemplary message flow chart 400 illustrating the five phases of optimized service deployment according to the disclosure.

[0214] The message flow chart 400 describes messages between the components of the communication system 110 described above with respect to Figure 1 or the communication system 200 described above with respect to Figure 2, respectively. Messages are exchanged between service provider 121, ECM 140, POF 160, EES 230, PCF 150, AMF 135 and SMF 130.

[0215] In the following, the five phases of an optimized service deployment are described in detail.

[0216] Phase 1, 410 is related to Service provider request default EAS instantiation: The architecture receives an instantiation request 411 from the SP 121 and proceeds to instantiate 412 the service in a default edge location, inside the operator’s domain. EAS registration and EEC notification messages 413 are exchanged between ECM 140, POF 160 and EES 230. The target at this point is to provide a fast service instantiation, leaving optimality to the next phases.

[0217] Phase 2, 420 is related to Monitoring gathering and optimization computation: It identifies 423 the users consuming the associated service and obtains location information 424 regarding those UEs. Monitoring parameters 425 (network and edge computing related) are leveraged to obtain the optimal service placement strategy. In the beginning of phase 2, 420, Edge monitoring parameter provisioning 421 and Placement optimization request 422 messages are exchanged between ECM 140 and POF 160.

[0218] Phase 3, 430 is related to optimal EAS instantiation and application context transfer: It instantiates the Application 432 according to the optimal placement strategy 431 and relocates 433 the application context to the newly instantiated EAS(s). EES 230 notifies 434 EEC.

[0219] Phase 4, 440 is related to continuous monitoring and optimal service relocation: The POF 160 is continuously notified 441 about changes in user status and resource utilization for optimal service relocation 443. EAS is optimally instantiated 442 and EES 230 notifies 444 EEC. Phase 5, 450 is related to handling service provider updates: The service provider, which monitors its service, can trigger a service scale 451 (if the current service is not meeting the demands) or a service delete 452 if it no longer requires its service to run in the edge.

[0220] In the following description with respect to Figures 5 to 14, the details of each phase are detailed. The two options below can be applied.

[0221] Option 1 : with the Edge enablement layer (EEL) support (meaning following the architecture of TS 23.588), as described below with respect to Figures 5 to 9;

[0222] Option 2: without the Edge enablement layer (EEL) support (meaning a classical edge compute application that relies on the UPF to redirect traffic to the edge cloud) , as described below with respect to Figures 10 to 14.

[0223] Figure 5 shows an exemplary message flow chart 500 illustrating implementation of the first phase of optimized service deployment based on a first embodiment, i.e. , Option 1 : Phase 1 : Default EAS Instantiation.

[0224] The following messages are exchanged between service provider 121 , ECM 140, EES 230 and EEC 134:

[0225] ECM 140 exposes the API to the SP 121 , which uses it to request (1) the instantiation of its service.

[0226] ECM 140 deploys (2) the service (EAS) in a default location.

[0227] The EEC 134 is notified (3) that a new EAS is available.

[0228] The Instantiation Request (1) includes: request ID, preferred location, resource requirements (capabilities), topological or geographical service areas, software image information, QoS.

[0229] Figure 6 shows an exemplary message flow chart 600 illustrating implementation of the second phase of optimized service deployment based on the first embodiment, i.e., Option 1 : Phase 2: Monitoring and usage detection.

[0230] The following messages are exchanged between ECM 140, POF 160, PCF 150, AMF 135, SMF 130 and UPF 170: ECM 140 requests (1) an optimal EAS placement strategy to the POF 160, providing it with monitoring data from the edge computing nodes (e.g., energy consumption).

[0231] POF 160 collects (4) Network Monitoring Parameters.

[0232] The Placement Optimization Request (1) includes: request ID, application ID, monitoring data from edge nodes.

[0233] Figure 7 shows an exemplary message flow chart 700 illustrating implementation of the third phase of optimized service deployment based on the first embodiment, i.e., Option 1 : Phase 3: Optimal Placement of Edge Services (near end users).

[0234] The following messages are exchanged between ECM 140, POF 160, S-EES 230a, T-EES 230b and EEC 134:

[0235] POF 160 computes (1) the optimal placement strategy with the available data and sends the placement strategy to the ECM 140.

[0236] ECM 140 instantiates (3) the EAS in the Edge Nodes as instructed (2) by the POF 160. ECM 140 triggers (4) an Application Context Relocation in the default EES (S-EES, 230a), indicating the T-EES 230b.

[0237] The Application context is transferred (6) between the S-EES 230a and the T-EES 230b. This procedure also includes the registration of the EEC 134 with the T-EES 230b. The EEC 134 is notified (7) about the new EAS.

[0238] Figure 8 shows an exemplary message flow chart 800 illustrating implementation of the fourth phase of optimized service deployment based on the first embodiment, i.e., Option 1 : Phase 4: Continuous monitoring and optimal service relocation.

[0239] The following messages are exchanged between ECM 140, POF 160, S-EES 230a, T-EES 230b and EEC 134:

[0240] The POF 160 continuously monitors (0) network and edge computing conditions and can conclude (1) that the service should be relocated (e.g., due to user mobility or network congestion).

[0241] ECM 140 instantiates (3) the EAS in the Edge Nodes as instructed (2) by the POF 160. ECM 140 triggers (4) an Application Context Relocation in the default EES (S-EES 230a), indicating the T-EES 230b. The Application context is transferred (6) between the S-EES 230a and the T-EES 230b. This procedure also includes the registration of the EEC 134 with the T-EES 230b. The EEC 134 is notified (7) about the new EAS.

[0242] The S-EAS may be deleted if it is no longer serving users.

[0243] Figure 9 shows an exemplary message flow chart 900 illustrating implementation of the fifth phase of optimized service deployment based on the first embodiment, i.e., Option 1 : Phase 5: Handling Service Provider Updates.

[0244] The following messages are exchanged between service provider 121 , ECM 140 and EES 230:

[0245] The SP 121 continuously monitors its service’s parameters.

[0246] It can decide that the service is not handling all the users and it triggers (1) a service scale.

[0247] The service scale is processed (2) by the ECM 140.

[0248] The SP 121 can also conclude that it no longer requires its service to be in the edge, triggering (3) a service update (delete) to the ECM 140.

[0249] The ECM 140 triggers the service deletion (5), causing the EAS to de-register (4) itself in the EES 230.

[0250] The following Figures 10 to 14 describe the procedures for the option with no EEL support. This means that further interaction with the PCF 150 and SMF 130 can take place in order for the traffic to be redirected towards the edge compute.

[0251] Figure 10 shows an exemplary message flow chart 1000 illustrating implementation of the first phase of optimized service deployment based on a second embodiment, i.e., Option 2: Phase 1 : Default EAS Instantiation (Alternative: no EEC).

[0252] The following messages are exchanged between service provider 121 , ECM 140 and PCF 150:

[0253] ECM 140 Exposes the API to the SP 121 , which uses it to request (1) the instantiation of its service.

[0254] ECM 140 deploys (2) the service (EAS) in a default location.

[0255] ECM 140 redirects the traffic to the newly instantiated EAS by exchanging messages (3a), (3b) with the PCF 150. Figure 11 shows an exemplary message flow chart 1100 illustrating implementation of the second phase of optimized service deployment based on the second embodiment, i.e., Option 2: Phase 2: Monitoring Collection (Alternative: no EEC).

[0256] The following messages are exchanged between ECM 140, POF 160, PCF 150, AMF 135 and SMF 130:

[0257] ECM 140 requests (1) an optimal EAS placement strategy to the POF 160, providing it with monitoring data from the edge computing nodes (e.g., energy consumption). POF 160 Collects Network Monitoring Parameters.

[0258] Figure 12 shows an exemplary message flow chart 1200 illustrating implementation of the third phase of optimized service deployment based on the second embodiment, i.e., Option 2: Phase 3: Optimal Placement enforcement (Alternative no EEC).

[0259] The following messages are exchanged between ECM 140, POF 160, S-EES 230a, T-EES 230b and PCF 150:

[0260] POF 160 computes (1) the optimal placement strategy with the available data and sends (2) the placement strategy to the ECM 140.

[0261] ECM 140 Instantiates (3) the EAS in the Edge Nodes as instructed by the POF 160.

[0262] ECM 140 triggers (4) an Application Context Relocation in the default EES (S-EES 230a).

[0263] The Application Context is transferred (6) between the S-EAS and the T-EAS.

[0264] The application traffic is redirected from the S-EAS to the T-EAS.

[0265] Figure 13 shows an exemplary message flow chart 1300 illustrating implementation of the fourth phase of optimized service deployment based on the second embodiment, i.e., Option 2: Phase 4: Continuous monitoring and optimal service relocation (Alternative: no EEC)

[0266] The following messages are exchanged between ECM 140, POF 160, S-EES 230a, T-EES 230b and PCF 150:

[0267] The POF 160 continuously monitors network and edge computing conditions and can conclude (1) that the service should be relocated (e.g., due to user mobility or network congestion).

[0268] ECM 140 instantiates the EAS in the Edge Nodes as instructed by the POF 160. ECM 140 triggers (4) an Application Context Relocation in the default EES (S-EES 230a).

[0269] The Application Context is transferred (6) between the S-EAS and the T-EAS.

[0270] The application traffic is redirected from the S-EAS to the T-EAS.

[0271] Figure 14 shows an exemplary message flow chart 1400 illustrating implementation of the fifth phase of optimized service deployment based on the second embodiment, i.e., Phase 5: Handling Service Provider Updates (Alternative: no EEC).

[0272] The following messages are exchanged between service provider 121 , ECM 140 and PCF 150:

[0273] The SP 121 continuously monitors its service’s parameters.

[0274] It can decide that the service is not handling all the users and it triggers (1) a service scale

[0275] The SP 121 can also conclude that it no longer requires its service to be in the edge and triggers (3) a service update (delete) to the ECM 140.

[0276] The ECM 160 triggers (4) the service deletion and it deletes the traffic rules previously provided to the 5G network.

[0277] The messages described above with respect to Figures 4 to 14 can be implemented as computer executable code or computer executable instructions or computer program for execution on a computer.

[0278] The computer program may run on a controller or processor for controlling the abovedescribed service in a communication system, e.g., one of the components of the communication system described in Figure 1 or Figure 2.

[0279] While a particular feature or aspect of the disclosure may have been disclosed with respect to only one of several implementations, such feature or aspect may be combined with one or more other features or aspects of the other implementations as may be desired and advantageous for any given or particular application. Furthermore, to the extent that the terms "include", "have", "with", or other variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term "comprise". Also, the terms "exemplary", "for example" and "e.g." are merely meant as an example, rather than the best or optimal. The terms “coupled” and “connected”, along with derivatives may have been used. It should be understood that these terms may have been used to indicate that two elements cooperate or interact with each other, regardless whether they are in direct physical or electrical contact, or they are not in direct contact with each other.

[0280] Although specific aspects have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that a variety of alternate and / or equivalent implementations may be substituted for the specific aspects shown and described without departing from the scope of the present disclosure. This application is intended to cover any adaptations or variations of the specific aspects discussed herein.

[0281] Although the elements in the following claims are recited in a particular sequence with corresponding labeling, unless the claim recitations otherwise imply a particular sequence for implementing some or all of those elements, those elements are not necessarily intended to be limited to being implemented in that particular sequence.

[0282] Many alternatives, modifications, and variations will be apparent to those skilled in the art in light of the above teachings. Of course, those skilled in the art readily recognize that there are numerous applications of the disclosure beyond those described herein. While the present disclosure has been described with reference to one or more particular embodiments, those skilled in the art recognize that many changes may be made thereto without departing from the scope of the present disclosure. It is therefore to be understood that within the scope of the appended claims and their equivalents, the disclosure may be practiced otherwise than as specifically described herein.

Claims

CLAIMS:

1. A method (100) for controlling a service (112) in a communication system (110) based on at least one characteristic parameter of the communication system (110) for serving at least one User Equipment, UE (131), wherein a plurality of edge application servers (181 , 182, 183) are arranged in the communication system (110) for controlling the service (112) to serve at least one UE (131), the method (100) comprising: receiving, by a network entity (140) of the communication system (110), a request (101) issued by a service provider entity (123) for instantiating one or more services on the plurality of edge application servers (181, 182, 183) of the communication system (110) and controlling the one or more services (112); upon receiving the request (101), instantiating the one or more services on a first edge application server (181) of the plurality of edge application servers (181 , 182, 183) and controlling the one or more services (112) via the first edge application server (181) to serve the at least one UE (131); obtaining information about the at least one characteristic parameter of the communication system (110) for serving the at least one UE (131); and instantiating the one or more services on at least one second edge application server (182) of the plurality of edge application servers (181, 182, 183) based on the information about the at least one characteristic parameter of the communication system (110) for serving the at least one UE (131) and controlling the one or more services (112) via the at least one second edge application server (182) to serve the at least one UE (131).

2. The method (100) of claim 1, wherein the at least one characteristic parameter of the communication system (110) for serving at least one UE (131) comprises at least one of the following: a location of the at least one UE (131), a communication latency for a communication with the at least one UE (131), a bandwidth or throughput of a communication channel to the at least one UE (131), an energy consumption of each of the plurality of edge application servers (181, 182, 183).

3. The method (100) of claim 1 or 2, wherein the first edge application server (181) is a default application server of the communication system (110); andwherein a location of the at least one second edge application server (182) is closer to a location of the at least one UE (131) than a location of the first edge application server (181).

4. The method (100) of any of the preceding claims, wherein the request (101) comprises a service descriptor for identifying the service (112), the method (100) further comprising: identifying the service (112) based on the service descriptor.

5. The method (100) of any of the preceding claims, wherein the request (101) comprises information about at least one Key Performance Indicator, KPI, to be fulfilled by the communication system (110) in accordance with a predetermined Service Level Agreement, SLA.

6. The method (100) of any of the preceding claims, comprising: monitoring data traffic (301) between the at least one UE (131) and the service (112) to obtain the at least one characteristic parameter of the communication system (110) for serving the at least one UE (131).

7. The method (100) of any of the preceding claims, comprising: monitoring data traffic (301) between the at least one UE (131) and a central server to obtain the at least one characteristic parameter of the communication system (110) for serving the at least one UE (131).

8. The method (100) of any of the preceding claims, comprising: determining the at least one second edge application server (182) from the plurality of edge application servers (181, 182, 183) based on an optimal placement criterion with respect to the at least one UE (131) and the plurality of edge application servers (181, 182, 183).

9. The method (100) of claim 8, wherein the optimal placement criterion is based on at least one or any combination of the following: a minimum geographical distance between the at least one UE (131) and the at least one second edge application server (182), a minimum latency for communication between the at least one UE (131) and the at least one second edge application server (182),a maximum bandwidth or a maximum throughput for communication between the at least one UE (131) and the at least one second edge application server (182), a minimum energy consumption of the at least one second edge application server (182) with respect to the other edge application servers, fulfillment of at least one Key Performance Indicator, KPI, by the communication system (110) in accordance with a predetermined Service Level Agreement, SLA, at least one second edge application server fulfilling a predefined SLA.

10. The method (100) of any of the preceding claims, wherein controlling the service(112) via the at least one second edge application server (182) to serve the at least one UE (131) comprises: relocating an application context of the service (112) utilized by the at least one UE (131) from the first edge application server (181) to the at least one second edge application server (182).

11. The method (100) of any of the preceding claims, comprising: continuous monitoring of user status and / or and resource utilization of the at least one UE (131) utilizing the service (112) via the at least one second edge application server (182); and relocating an application context of the service (112) towards another edge application server (183) of the plurality of edge application servers (181 , 182, 183) based on the monitored user status and / or resource utilization.

12. The method (100) of any of the preceding claims, wherein the network entity (140) of the communication system (110) comprises an interface to a service provider entity (123) for receiving the request (101) for instantiating the one or more services (112).

13. The method (100) of claim 12, comprising: updating the service (112) controlled via the at least one second edge application server (182) and / or the first edge application server (181) based on a service scale request(451) received via the interface to the service provider entity (123); or deleting the service (112) controlled via the at least one second edge application server (182) and / or the first edge application server (181) based on a service delete request(452) received via the interface to the service provider entity (123).

14. The method (100) of any of the preceding claims, wherein the network entity (140) of the communication system (110) comprises an Edge Computing Management, ECM, network entity according to 3GPP TS 28.538 specification.

15. The method (100) of claim 14, wherein the ECM network entity (140) comprises an Application Programmable Interface (122) for exposing methods and parameters for service providers (121) to request controlling and optimizing their services and for receiving monitoring parameters from the edge application servers (181 , 182, 183).

16. The method (100) of any of the preceding claims, wherein the communication system (110) comprises a Placement Optimization Function, POF, network entity (160) for determining placement criteria for placement of services (112) based on the information about the at least one characteristic parameter of the communication system (110) for serving the at least one UE (131).

17. The method (100) of claim 16, comprising: collecting data, by the POF network entity (160), from the communication system (110), the at least one UE (131), and from compute resources of the plurality of edge application servers (181, 182, 183); and determining the placement criteria, by the POF entity (160), based on the collected data and based on fulfillment of a predetermined Service Level Agreement, SLA.

18. The method (100) of claim 16 or 17, wherein the POF network entity (160) comprises an interface (161) towards the network entity (140) configured to initiate relocation of services from one edge application server to another edge application server of the plurality of edge application servers (181 , 182, 183).

19. A network entity (140) for controlling a service (112) based on at least one characteristic parameter of a communication system (200) for serving at least one User Equipment, UE (131), wherein the network entity (140) is configured to: receive a request (101) from a service provider entity (123) for instantiating one or more services on a plurality of edge application servers (181 , 182, 183) of the communication system (200) and controlling the one or more services (112);upon receiving the request (101), instantiate the one or more services on a first edge application server (181) of the plurality of edge application servers (181 , 182, 183) and control the one or more services (112) via the first edge application server (181) to serve the at least one UE (131); obtain information about the at least one characteristic parameter of the communication system (200) for serving the at least one UE (131); and instantiate the one or more services (112) on at least one second edge application server (182) of the plurality of edge application servers (181 , 182, 183) based on the information about the at least one characteristic parameter of the communication system (200) and control the one or more services (112) via the at least one second edge application server (182) to serve the at least one UE (131).

20. The network entity (140) of claim 19, wherein the at least one characteristic parameter of the communication system (200) for serving at least one UE (131) comprises at least one of the following: a location of the at least one UE (131), a communication latency for a communication with the at least one UE (131), a bandwidth or throughput of a communication channel to the at least one UE (131), an energy consumption of each of the plurality of edge application servers (181, 182, 183).

21. A Placement Optimization Function, POF, network entity (160) for determining a placement criterion for placement of at least one service (112) based on at least one characteristic parameter of a communication system (200), wherein the POF network entity (160) is configured to: receive, from a network entity (140) of the communication system (200), a placement optimization request for determining a placement criterion for placement of at least one service (112) in the communication system (200); obtain at least one characteristic parameter of the communication system (200) from the communication system (200); determine the placement criterion based on the at least one characteristic parameter of the communication system (200); and provide the placement criterion to the network entity (140) of the communication system (200).

22. The POF network entity (160) of claim 21, wherein the at least one characteristic parameter of the communication system (200) comprises at least one of the following: a location of the at least one UE (131) served by the at least one service (112), a communication latency for a communication with the at least one UE (131), a bandwidth or throughput of a communication channel to the at least one UE (131), an energy consumption of each of a plurality of edge application servers (181 , 182, 183) controlling the at least one service (112) to serve the at least one UE (131).

23. The POF network entity (160) of claim 22, configured to determine the placement criterion based on at least one of the following: a minimum distance of the at least one UE (131) to a respective edge application server of the plurality of edge application servers (181, 182, 183), a minimum communication latency of a communication between the at least one UE (131) and a respective edge application server of the plurality of edge application servers (181 , 182, 183), a maximum bandwidth or maximum throughput of a communication channel between the at least one UE (131) and a respective edge application server of the plurality of edge application servers (181 , 182, 183), a minimum energy consumption of a respective edge application server of the plurality of edge application servers (181, 182, 183).

Images