Patent Description:
In a typical wireless communication network, user equipments (UE), also known as wireless communication devices, mobile stations, stations (STA) and/or wireless devices, may communicate via a Radio Access Network (RAN) to one or more core networks (CN). The RAN covers a geographical area which is divided into service areas, also known as cells, with each cell being served by a radio network node e.g., a Wi-Fi access point or a radio base station (RBS), which in some networks may also be called, for example, a NodeB, an eNodeB or a gNodeB. The cell is a geographical area where radio coverage is provided by the radio network node. The radio network node operates on radio frequencies to communicate over an air interface with the wireless devices within range of the radio network node. The radio network node communicates over a downlink (DL) to the wireless device and the wireless device communicates over an uplink (UL) to the radio network node.

A Universal Mobile Telecommunications network (UMTS) is a third generation (<NUM>) telecommunications network, which evolved from the second generation (<NUM>) Global System for Mobile Communications (GSM). The UMTS terrestrial radio access network (UTRAN) is essentially a RAN using wideband code division multiple access (WCDMA) and/or High Speed Packet Access (HSPA) for user equipments. In some RANs, e.g. as in UMTS, several radio network nodes may be connected, e.g., by landlines or microwave, to a controller node, such as a radio network controller (RNC) or a base station controller (BSC), which supervises and coordinates various activities of the plural radio network nodes connected thereto. This type of connection is sometimes referred to as a backhaul connection. The RNCs and BSCs are typically connected to one or more core networks.

Specifications for the Evolved Packet System (EPS), also called a Fourth Generation (<NUM>) network, have been completed within the Third Generation Partnership Project (3GPP) and this work continues in the coming 3GPP releases, for example to specify a Fifth Generation (<NUM>) network. The EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network.

With the emerging <NUM> technologies such as New Radio (NR), the use of very many transmit- and receive-antenna elements is of great interest as it makes it possible to utilize beamforming, such as transmit-side and receive-side beamforming. Transmit-side beamforming means that the transmitter can amplify the transmitted signals in a selected direction or directions, while suppressing the transmitted signals in other directions. Similarly, on the receive-side, a receiver can amplify signals from a selected direction or directions, while suppressing unwanted signals from other directions.

End-user services may be provided in a cloud manner through distributed applications that are hosted in a distributed cloud. The distribution can be exploited for different purposes. It may be exploited for providing improved service quality by allowing each user to be served from a nearby location in order to minimize the effects of network latency and congestion. It may be exploited for providing increased service resilience in case of failures in the cloud infrastructure or communication network.

An edge cloud here refers to a distributed cloud where users are accessing end-user services provided by applications that are hosted in the distributed cloud and where users are accessing the service via a mobile network. The application that provides the end-user service may be a distributed application deployed across multiple cloud locations. It may also be an application where individual application instances are deployed at multiple cloud locations. In both cases we will refer to the instantiation of an application or application component at a cloud location as an application instance. The mobile network carries user traffic between the UE and a communication anchor point. The anchor point herein meaning a point or node that terminates a mobile network user plane session at a data network. The data network may be identified by an identifier such as a data network access identifier (DNAI). The anchor point may e.g. in <NUM> be referred to as a protocol data unit (PDU) session anchor (PSA) user plane function (UPF) node. The user traffic is further carried between the anchor point and an application instance in the edge cloud node via the data network.

In order to exploit the geographical and topological distribution of edge cloud nodes, coordination between the mobile access networks and the edge cloud and/or the end-user service application is required to make sure UEs are served from a communication anchor point in the mobile access network which is close to the edge cloud location hosting the application instance which is serving the UE. <FIG> shows an edge cloud with nodes at multiple locations, where the end-user service is provided by an application with application instances at all or a subset of edge cloud locations, where the mobile network is capable of carrying user traffic between the client and more than one communication anchor point, and where the optimal selection of anchor point for a particular UE depends on the UE location and the subset of edge cloud nodes that are hosting the application instance. Coordination is needed for handling e.g. edge site selection and edge site handover of clients served by the edge cloud via the mobile access network.

In existing deployments of distributed cloud, the degree of distribution is limited. Larger cloud providers offer limited distribution with few (if any) sites per country. Workload placement in the distributed cloud is optimized independently from the access network. In typical mobile network deployments, the number of communication anchor points per country are few. The selection of anchor point for a UE is static or semi-static and often based on the subscriber home address. It is primarily during roaming in another operator's mobile network that an alternative communication anchor point is selected for the UE in the visited mobile network operator.

In order to allow new edge-based end-user services to exploit further distribution of the cloud, several changes in the mobile networks are required. Additional communication anchor points are needed and clients should be able to flexibly handover between communication anchor points based on different optimization objectives.

In the context of <NUM> core network (5GC) new mechanisms are introduced to support local breakout in mobile packet core. These mechanisms will enable a more access near edge cloud and the benefits it may bring such as latency reduction and resource efficiency. It also introduces requirements on the handling the coordination between mobile access network and distributed cloud.

A problem in an edge cloud is how to configure an edge connectivity service (ECS) to a client UE. This is a problem since mobile connectivity traditionally is configured by the mobile operator in agreement with the UE, e.g. via a subscription. However, in an edge cloud ecosystem, the connectivity requirements depend critically on the application and its distribution across edge sites and it may be difficult to exploit the advantages that distribution could bring in terms of service performance.

<CIT> discloses how to extend the architecture's Application Function (AF), which is deployed in the networks where corresponding services are operated, to request and receive policy information from the nextgen control plane for local enforcement on the data plane. <CIT> discloses a method for sending a request from an application server functionality to a policy server functionality, storing local application policy for a user equipment, and receiving information from said policy server functionality. <CIT> discloses method and apparatuses for enabling third party edge clouds at the mobile edge. <CIT> discloses an apparatus and method for steering a protocol data unit session associated with traffic routed to a selected user plane function.

An object herein is to improve provisioning of application dependent connectivity services to UEs in a more efficient manner.

According to a first aspect the object is achieved by providing a method performed by a network node for handling a service request for an edge connectivity service from an application server in a communication network. The application server comprises an application providing an end-user service to a user equipment, The edge connectivity service is a connectivity between the application and the user equipment accessing the end-user service. The method comprises configuring the application with the edge connectivity service for the user equipment. Configuring comprises setting up configuration for the edge connectivity service by negotiating with the application server for determining the configuration of the edge connectivity service and by registering the edge connectivity service with the configuration for the application. Configuring further comprises receiving the service request for the edge connectivity service from the application server. The service request comprises an indication of the user equipment. Configuring further comprises setting up a configuration of one or more radio network nodes of a radio access network for providing the edge connectivity service to the user equipment.

According to a second aspect a network node for handling a service request for an edge connectivity service from an application server in a communication network is provided. The application server comprises an application providing an end-user service to a user equipment. The edge connectivity service is a connectivity between the application and the user equipment accessing the end-user service. The network node is configured to configure the application with the edge connectivity service for the user equipment by being configured to set up configuration for the edge connectivity service by negotiating with the application server for determining the configuration of the edge connectivity service and registering the edge connectivity service with the configuration for the application. The network node is configured to configure the application with the edge connectivity service for the user equipment by further being configured to receive the service request for the edge connectivity service from the application server, wherein the service request comprises an indication of the user equipment. The network node is configured to configure the application with the edge connectivity service for the user equipment by further being configured to setup a configuration of one or more radio network nodes of a radio access network for providing the edge connectivity service to the user equipment.

According to a third aspect it is provided herein a computer program product. The computer program product comprises instructions, which, when executed on at least one processor of a network node, cause the network node to carry out the method according to the first aspect.

According to a fourth aspect, it is provided herein a computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor of a network node, cause the network node to carry out the method according to the first aspect.

The invention is defined by a method according to claim <NUM>, a network node according to claim <NUM>, a computer program product according to claim <NUM> and a computer-readable storage medium according to claim <NUM>.

Embodiments herein provide the application with an ability to flexibly request configuration of an edge connectivity service (ECS) that meets the application requirements and to provide ECS to UEs accessing a service provided by the application such as a cloud application e.g. the application may be a distributed application.

Embodiments herein enable optimization of edge connectivity services depending on use cases that put different requirements on edge connectivity, e.g. high volume data vs real.

time applications, applications with large or limited distribution etc. An optimized use of infrastructure may be provided by providing flexible edge connectivity services to different applications by allowing application controlled configuration and provisioning of the edge connectivity service to capture the requirements from the application. Embodiments herein may facilitate evolution of the edge ecosystem by providing a flexible infrastructure instead of one size fits all and by providing a simple interface for configuring an edge connectivity service.

The embodiments related to <FIG> are not covered by the claimed invention.

Embodiments herein relate to communication networks in general. <FIG> is a schematic overview depicting a communication network <NUM>. The communication network <NUM> comprises one or more mobile access networks such as RANs and one or more CNs. The communication network <NUM> may use one or a number of different technologies. Embodiments herein relate to recent technology trends that are of particular interest in a <NUM> context; however, embodiments are also applicable in further development of existing communication systems such as e.g. LTE and Wideband Code Division Multiple Access (WCDMA).

In the communication network <NUM>, UEs are configured to communicate with the CN or with one another e.g. a UE <NUM>, such as a mobile station, a non-access point station (non-AP STA), a STA, a wireless device and/or a wireless terminal, may be configured for communication. It should be understood by the skilled in the art that "UE" is a non-limiting term which means any terminal, wireless communication terminal, user equipment, narrowband-internet of things (NB-loT) device, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station capable of communicating using radio communication with a radio network node or a wireless device.

The communication network <NUM> comprises a radio network node <NUM> , also referred to as a first radio network node, providing radio coverage over a geographical area, a service area <NUM>, of a first radio access technology (RAT), such as NR or similar. The radio network node <NUM> may be a transmission and reception point such as an access node, an access controller, a base station, e.g. a radio base station such as a gNodeB (gNB), an evolved Node B (eNB, eNode B), a NodeB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), a transmission arrangement of a radio base station, a stand-alone access point or any other network unit or node capable of communicating with a wireless device within the area served by the radio network node <NUM> depending e.g. on the first radio access technology and terminology used. The radio network node <NUM> may be referred to as a serving radio network node wherein the service area may be referred to as a serving cell, and the serving network node communicates with the UE <NUM> in form of DL transmissions to the wireless device <NUM> and UL transmissions from the wireless device <NUM>. It should be noted that a service area may be denoted as cell, beam, beam group or similar to define an area of radio coverage. The radio network node <NUM> may beamform its transmissions towards one or more wireless devices such as the UE <NUM>. Beamforming allows the signal to be stronger for an individual connection.

The communication network <NUM> further comprises a network node <NUM> referred to as control node or node with edge connectivity service which is a network node such as a server or a function collocated with another network node such as a mobility management entity (MME) or Access and Mobility Management function (AMF) node, or a standalone node. Furthermore, the communication network comprises a number of other network node such as AMF nodes that supports termination of non-access stratum (NAS) signalling, NAS ciphering & integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management. Session Management function (SMF) node which supports: session management (session establishment, modification, release), UE IP address allocation & management, DHCP functions, termination of NAS signalling related to session management, DL data notification, traffic steering configuration for UPF for proper traffic routing. User plane function (UPF) node which supports: packet routing & forwarding, packet inspection, quality of service (QoS) handling, acts as external protocol data unit (PDU) session point of interconnect to Data Network (DN), and is an anchor point for intra- & inter-RAT mobility. Other possible nodes or functions may be a Policy Control Function (PCF) node which supports: unified policy framework, providing policy rules to control plane (CP) functions, access subscription information for policy decisions in Unified Data Repository (UDR). Authentication Server Function (AUSF) node which acts as an authentication server. Unified Data Management (UDM) node which supports: generation of Authentication and Key Agreement (AKA) credentials, user identification handling, access authorization, subscription management. Application Function (AF) node which supports: application influence on traffic routing, accessing NEF, interaction with policy framework for policy control. Network Exposure function (NEF) node which supports: exposure of capabilities and events, secure provision of information from external application to 3GPP network, translation of internal/external information. NF Repository function (NRF) node which supports: service discovery function, maintains NF profile and available NF instances.

The communication network <NUM> further comprises one or more data network nodes <NUM>' and <NUM>", also referred to as an anchor point node such as a gateway nodes, user plane function (UPF) node or similar. The one or more data network nodes provides access to data network of the communication network from e.g. different operator networks or similar.

The communication network <NUM> may further comprise one or more application nodes or an application servers <NUM>', <NUM>" also referred to as application server <NUM> comprising an application or a service which in turn is using an edge connectivity service for connectivity between application instances hosted at the edge in e.g. the application servers <NUM>' and <NUM>" and UEs that are accessing the end-user service provided by the application. The application server <NUM> may be referred to as cloud application node or similar and may comprise at least part of the application. The application, that provides the end-user service, may be a distributed application deployed across multiple locations referred to as distributed networks (DN), DN' and DN". It may also be an application where individual application instances are deployed at multiple cloud locations. The method according to embodiments herein is performed by the network node <NUM>. As an alternative, a Distributed Node and functionality, e.g. comprised in a cloud, may be used for performing or partly performing the method.

Embodiments herein enable an application, also referred to as cloud application, to configure an edge connectivity service (ECS) and provision the ECS to one or more UEs. The embodiments herein may use the network node <NUM> e.g. an edge system interface function (ESIF) in the network node <NUM>, which interfaces the application as well as the packet core of the mobile access network and provides an additional functionality for providing ECSs. The network node <NUM> may be part of the operator domain. <FIG> disclose for configuring the ECS with input from the application. <FIG> describe provisioning ECS of the application to the UE <NUM>.

The method actions performed by the network node <NUM> also referred to as ECS node for handling a service request for a connectivity service from an application of the application server <NUM> in the communication network <NUM> according to embodiments will now be described with reference to a flowchart depicted in <FIG>. The actions do not have to be taken in the order stated below, but may be taken in any suitable order. Actions performed in some embodiments are marked with dashed boxes.

Action <NUM>. The network node <NUM> configures the application with an edge connectivity service for the UE <NUM>. The network node <NUM> may setup the ECS and/or register the UE <NUM> to the ECS.

Action <NUM>. The network node <NUM> is configured to set-up configuration for the edge connectivity service. This is performed by the network node negotiating with the application server <NUM> for determining the configuration of the edge connectivity service. The network node <NUM> registers the edge connectivity service with the configuration for the application, and thus, the configuration of the service is completed and network node <NUM> registers the ECS as a service provided to the application and is now ready to be used. This is illustrated in <FIG>. The configuration for the edge connectivity service may comprise one or more of: policy of a handover to a second anchor point from a first anchor point based on a location of the UE <NUM>; one or more identities of anchor points; quality of service (QoS) parameters; traffic classifier rules to which the ECS applies e.g. rules are DNAI specific; and level of involvement of the application in a handover. The configuration may comprise one or more service parameters as indicated in <FIG>.

Action <NUM>. Additionally, the network node <NUM> receives a request such as a service request for the edge connectivity service from the application server <NUM>, wherein the request comprises an indication of the UE <NUM>.

Action <NUM>. The network node <NUM> is configured to set-up a configuration of one or more radio network nodes of a radio access network for providing the edge connectivity service to the UE <NUM>.

Action <NUM>. The network node <NUM> may register the UE <NUM> to the edge connectivity service.

Embodiments herein provide the application with an ability to flexibly request configuration of an edge connectivity service (ECS) that meets one or more application requirements and to provision that ECS to clients accessing a service provided by the application. Embodiments provide the benefit of e.g. enable optimization of edge connectivity services depending on use cases that put different requirements on edge connectivity, e.g. high volume data vs real time applications, applications with large or limited distribution etc.. Embodiments herein may optimize use of infrastructure by providing flexible edge connectivity services to different applications by allowing cloud application controlled configuration and provisioning of the edge connectivity service to capture the requirements from the cloud application. Embodiments herein mayfacilitate evolution of the edge ecosystem by providing a flexible infrastructure instead of one size fits all and by providing a simple interface for configuring an edge connectivity service.

<FIG> is a combined flowchart and signaling scheme according to embodiments herein. The actions do not have to be taken in the order stated below, but may be taken in any suitable order. Actions performed in some of the embodiments are marked as dashed boxes. <FIG> discloses a method of configuring the ECS as shown in action <NUM> in <FIG>.

Action <NUM>. The network node <NUM> exposes an interface, also referred to as ESIF, to one or more applications running on the application server <NUM> for requesting configuration of an ECS. The application server <NUM> uses the ESIF to submit, i.e. transmits, a request such as an ECS configuration request (see below) that contains one or more service parameters associated with the desired ECS. The one or more service parameters may include 3GPP defined connectivity parameters as well as edge specific parameters that describe edge related behavior, e.g. inter-edge handover, etc. The following information may be part of the ECS configuration request:.

Action <NUM>. The network node <NUM> receives the ECS configuration request and compares the ECS configuration request with an internal registry of service capabilities of the associated mobile access network i.e. the RAN. The network node <NUM> may check available support in the RAN for the information indicated in the ECS configuration request. Service capabilities may comprise e.g. registered capabilities of the mobile access network related to ECS such as:.

Action <NUM>. The network node <NUM> responds to the application server <NUM> with an ECS description (ECSD) that matches at least partly the ECS configuration request based on available capabilities. Prioritization of service parameters may be required to produce the ECSD. Such priorities may be preconfigured in ESIF or provided by the application as part of the ECS configuration request. The ECSD may comprise one or more of the following:.

Action <NUM>. The application server or the application determines ECS configuration to use based on the received ECSD and application requirements. Further negotiation between the network node <NUM> and the application may be needed to agree on an ECSD. instead of accepting the ECSD, the application may submit a modified ECS configuration request which generates an updated ECSD from the network node <NUM>. ECS may also complement the ECSD with information on service capabilities in order to facilitate for the application to modify the ECS configuration request.

Action <NUM>. Once the ECSD generated by the network node <NUM> is accepted by the application, the application server <NUM> transmits an ECSD configuration request to instruct the network node <NUM> to configure the confirmed ECSD.

Action <NUM>. The network node <NUM> receives the ECSD configuration request and performs necessary configurations. The network node <NUM> may register the ECS as configured for the application. The network node <NUM> may define policies for DNAI selection (i.e. defines service areas, such as geographical service areas, for the communication anchor points, i.e. DNAIs, that are part of the ECSD). Thus, the network maintaining the provisioned service according to the ECS description e.g. handling of application influence on handovers.

The network node <NUM> may maintain a registry of configured ECSs. For each ECS entry the following information may be included:.

if ECSD includes a notification of DNAI handover, the network node <NUM> may receive notifications originating from a SMF node related to DNAI handover. These notifications may be forwarded to the application. If the ECSD includes e.g. an application involvement in DNAI handover, 3GPP extensions may be needed. Extensions to NEF/PCF/SMF messaging such that SMF node may request AF approval for UPF handover, e.g. specifying target DNAI for ClientID, via PCF/NEF and extensions such that AF may respond to the request by SMF via NEF/PCF. The network node <NUM> may then receive handover approval requests originating from the SMF node, and the network node <NUM> may coordinate approval with the application on the application server <NUM>.

<FIG> shows an example when the network node <NUM> is exemplified as an ESIF and the application is exemplified as a cloud application. The following steps may be performed to configure an ECS at the network node <NUM>:.

<FIG> is a combined flowchart and signaling scheme according to embodiments herein. The actions do not have to be taken in the order stated below, but may be taken in any suitable order. Actions performed in some of the embodiments are marked as dashed boxes. <FIG> discloses a method of providing ECS to a UE as shown in actions <NUM>-<NUM> in <FIG>.

Action <NUM>. The UE transmits a service request to the application or the application server <NUM>. The application may provide ECS enablement.

Action <NUM>. The application server transmits a service request such as a ECS request to the network node <NUM> such as the ECS server. Thus, to provide a configured ECS to the UE <NUM>, the application submits a provisioning request to the network node <NUM> comprising one or more of the following: the ID of the UE such as as a client ID (ClientID - GPSI/IP/MAC), application identity such as a client application identity (ClientAppID); and identity of the configured ECS (ECSID). The application may have received UE ID and application ID in a service request from the UE <NUM>.

Action <NUM>. The network node <NUM> may setup the ECS for the UE as requested. the network node <NUM> may configure the mobile packet core to provide the requested service to the UE <NUM>. the network node <NUM> may submit policy information for DNAI selection associated with the ECSID to the mobile packet core. The network node may use AF requests (3GPP TS <NUM>-<NUM>. <NUM>) related to policies for UPF selection. The AF requests are sent either directly to the PCF(s) via N5 or via NEF (depending on operator configuration). The PCF(s) transform(s) the AF requests into policies that apply to PDU Sessions and used by SMF node. The AF request used by the network node <NUM> may include the following 3GPP defined entries:.

The network node <NUM> may further initiate a 3GPP defined network triggered PDU Session Establishment procedure (3GPP TS <NUM> - <NUM>. The network node <NUM> may do this by invoking an application trigger to the UE via NEF. <NUM> - <NUM>. The network node <NUM> then sends a device trigger message to the application (ClientAppID) on the UE side. The payload included in the device trigger message may contain information on which application (ClientAppID) on the UE side is expected to trigger the PDU Session establishment request. This may be an identifier of the client application associated with the application.

The client application (ClientAppID) on the UE side may trigger the PDU Session Establishment procedure. This is a NAS Message containing the following info: S-NSSAI(s), DNN, PDU Session ID, Request type, Old PDU Session ID, N1 SM container (PDU Session Establishment Request).

During the PDU session establishment procedure the SMF node associated with the UE <NUM> does UPF selection (e.g. as stated in TS23. <NUM>-<NUM>. <NUM>) based on policies that network node provided via PCF/NEF in a previous step. A notification of current DNAI is sent to the network node <NUM> if request by the network node in policy.

Action <NUM>. The network node <NUM> may then register the UE <NUM> to the ECS e.g. together with identifier of the application. the network node <NUM> may register ClientID (GPSI) as a subscriber to ECSID in its ECS registry together with associated application identifiers (CloudAppID, ClientApplD) and current DNAI. The edge connectivity service is now available to the UE <NUM> and the network node <NUM> may confirm to the application that the service has been provisioned to the UE as well as current DNAI.

<FIG> is a block diagram depicting the network node <NUM>, in two embodiments, for handling a service request for a connectivity service such as enabling the application providing ECS in the wireless communication network according to embodiments herein.

The network node <NUM> may comprise processing circuitry <NUM>, e.g. one or more processors, configured to perform the methods herein.

The network node <NUM> may comprise a configuring unit <NUM>. The network node <NUM>, the processing circuitry <NUM>, and/or the configuring unit <NUM> is configured to configure the application with an edge connectivity service for a UE <NUM>.

The network node <NUM>, the processing circuitry <NUM>, and/or the configuring unit <NUM> may be configured to configure the application by being configured to set up configuration for the edge connectivity service.

The network node <NUM>, the processing circuitry <NUM>, and/or the configuring unit <NUM> may be configured to set up the configuration by being configured to negotiate with the application server for determining the configuration of the edge connectivity service.

The network node <NUM>, the processing circuitry <NUM>, and/or the configuring unit <NUM> may be configured to configure the application by registering the edge connectivity service with the configuration for the application.

The network node <NUM>, the processing circuitry <NUM>, and/or the configuring unit <NUM> may be configured to configure the application by being configured to receive a request for the edge connectivity service from the application server, wherein the request comprises an indication of the user equipment; and to setup a configuration of one or more radio network nodes of a radio access network for providing the edge connectivity service to the user equipment.

The network node <NUM>, the processing circuitry <NUM>, and/or the configuring unit <NUM> may be configured to configure the application by being configured to register the user equipment to the edge connectivity service.

The configuration for the edge connectivity service comprises one or more of:
policy of a handover to a second anchor point from a first anchor point based on a location of the user equipment; one or more identities of anchor points; quality of service, QoS, parameters; and level of involvement of the application in an handover. The radio network node <NUM> further comprises a memory <NUM>. The memory <NUM> comprises one or more units to be used to store data on, such as signal strengths or qualities, mappings of TA to anchor points, service IDs, UE IDs of subscribing UEs, applications to perform the methods disclosed herein when being executed, and similar. The network node <NUM> may further comprise a communication interface comprising e.g. one or more antenna or antenna elements.

The methods according to the embodiments described herein for the network node <NUM> are respectively implemented by means of e.g. a computer program product <NUM> or a computer program, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the network node <NUM>. The computer program product <NUM> may be stored on a computer-readable storage medium <NUM>, e.g. a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium <NUM>, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the network node <NUM>. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium.

In some embodiments a more general term "network node" is used and it can correspond to any type of radio-network node or any network node, which communicates with a wireless device and/or with another network node. Examples of network nodes are NodeB, gNodeB, eNodeB, MeNB, SeNB, a network node belonging to Master cell group (MCG) or Secondary cell group (SCG), base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, network controller, radio-network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, Remote radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), etc..

In some embodiments the non-limiting term wireless device or user equipment (UE) is used and it refers to any type of wireless device communicating with a network node and/or with another wireless device in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, proximity capable UE (aka ProSe UE), machine type UE or UE capable of machine to machine (M2M) communication, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles etc..

Embodiments are applicable to any RAT or multi-RAT systems, where the wireless device receives and/or transmit signals (e.g. data) e.g. New Radio (NR), Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications/enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.

As will be readily understood by those familiar with communications design, that functions means or units may be implemented using digital logic and/or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and/or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a wireless device or network node, for example.

Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term "processor" or "controller" as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware and/or program or application data. Designers of communications devices will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

With reference to <FIG>, in accordance with an embodiment, a communication system includes a telecommunication network <NUM>, such as a 3GPP-type cellular network, which comprises an access network <NUM>, such as a radio access network, and a core network <NUM>. The access network <NUM> comprises a plurality of base stations 3212a, 3212b, 3212c, such as NBs, eNBs, gNBs or other types of wireless access points being examples of the radio network node <NUM> herein, each defining a corresponding coverage area 3213a, 3213b, 3213c. Each base station 3212a, 3212b, 3212c is connectable to the core network <NUM> over a wired or wireless connection <NUM>. A first user equipment (UE) <NUM>, being an example of the wireless device <NUM>, located in coverage area 3213c is configured to wirelessly connect to, or be paged by, the corresponding base station 3212c. A second UE <NUM> in coverage area 3213a is wirelessly connectable to the corresponding base station 3212a.

The wireless connection <NUM> between the UE <NUM> and the base station <NUM> is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE <NUM> using the OTT connection <NUM>, in which the wireless connection <NUM> forms the last segment. More precisely, the teachings of these embodiments may improve usage of resources since the mitigation scheme is used based on the load in a neighboring radio network node resulting in an efficient use of resource with improved performance and that may affect the latency and thereby provide benefits such as reduced user waiting time, and better responsiveness.

It will be appreciated that the foregoing description and the accompanying drawings represent non-limiting examples of the methods and apparatus taught herein.

Claim 1:
A method performed by a network node (<NUM>) for handling a service request for an edge connectivity service from an application server (<NUM>) in a communication network, wherein the application server (<NUM>) comprises an application providing an end-user service to a user equipment, wherein the edge connectivity service is a connectivity between the application and the user equipment accessing the end-user service, the method comprising:
- configuring (<NUM>) the application with the edge connectivity service for the user equipment, wherein configuring (<NUM>) comprises:
- setting up (<NUM>) configuration for the edge connectivity service by negotiating with the application server (<NUM>) for determining the configuration of the edge connectivity service and by registering the edge connectivity service with the configuration for the application;
- receiving (<NUM>) the service request for the edge connectivity service from the application server (<NUM>), wherein the service request comprises an indication of the user equipment; and
- setting up (<NUM>) a configuration of one or more radio network nodes of a radio access network for providing the edge connectivity service to the user equipment.