Network node and method implemented therein for handling communications in a wireless communication network

By configuring and managing edge connection services in network nodes, the flexibility of user equipment in the distributed cloud configuration of edge cloud connection services is solved, efficient service quality and resource utilization are achieved, and the development of edge ecosystems is promoted.

CN113841370BActive Publication Date: 2024-11-26TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201980096474.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2019-05-17
Publication Date
2024-11-26
Estimated Expiration
2039-05-17

AI Technical Summary

Technical Problem

In existing distributed cloud deployments, the configuration and service performance of edge cloud connection services are difficult to utilize, resulting in user equipment being unable to flexibly switch communication anchor points, affecting service quality and resource efficiency.

Method used

Through network nodes, the edge connection service is configured and managed, service requests are negotiated with the application server, and the edge connection service configuration and registration of user equipment is realized, flexible service policies and optimization solutions are provided, and edge connection services are supported for different application needs.

Benefits of technology

It realizes flexible configuration and optimization of edge connection services of user equipment, improves service quality and resource utilization, and promotes the evolution of edge ecosystems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113841370B_ABST
    Figure CN113841370B_ABST
Patent Text Reader

Abstract

Embodiments herein relate to a network node (13) for processing an application of an application server (15) in a communication network, wherein the network node is configured to configure the application with an edge connection service for a user equipment (10).
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments herein relate to network nodes and methods implemented therein relating to wireless communications. In particular, embodiments herein relate to processing communications, such as providing applications or services in a wireless communications network. Background Art

[0002] In a typical wireless communication network, a user equipment (UE), also known as a wireless communication device, mobile station, station (STA) and / or wireless device, can communicate with one or more core networks (CN) via a radio access network (RAN). The RAN covers a geographical area divided into service areas (also known as cells), where each cell is 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 referred to as, for example, a NodeB, eNodeB, or gNodeB. A cell is a geographical area where radio coverage is provided by a radio network node. The radio network node operates on radio frequencies to communicate with wireless devices within the range of the radio network node over an air interface. The radio network node communicates with the wireless device via a downlink (DL), and the wireless device communicates with the radio network node via an uplink (UL).

[0003] The Universal Mobile Telecommunications Network (UMTS) is a third generation (3G) telecommunications network that evolved from the second generation (2G) Global System for Mobile Communications (GSM). The UMTS Terrestrial Radio Access Network (UTRAN) is basically a RAN that uses Wideband Code Division Multiple Access (WCDMA) and / or High Speed ​​Packet Access (HSPA) for user equipment. In some RANs, such as in UMTS, several radio network nodes may be connected, for example, by landlines or microwaves, to a controller node, such as a Radio Network Controller (RNC) or Base Station Controller (BSC), which supervises and coordinates the various activities of the multiple radio network nodes connected to it. This type of connection is sometimes called a backhaul connection. The RNC and BSC are typically connected to one or more core networks.

[0004] Specifications for the Evolved Packet System (EPS), also known as the fourth generation (4G) network, have been completed in the 3rd Generation Partnership Project (3GPP), and this work will continue in upcoming 3GPP releases, for example in order to specify the fifth generation (5G) network. The EPS includes 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 the System Architecture Evolution (SAE) core network.

[0005] With the advent of emerging 5G technologies such as New Radio (NR), the use of many transmit and receive antenna elements has attracted great interest because 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 transmit signal in a selected direction or directions while suppressing the transmit signals in other directions. Similarly, on the receive side, the receiver can amplify the signal from the selected direction or directions while suppressing the unwanted signals from other directions.

[0006] End-user services can be provided in a cloud manner through distributed applications hosted in a distributed cloud. This distribution can be used for different purposes. It can be used to provide improved quality of service by allowing each user to obtain services from a nearby location to minimize the impact of network latency and congestion. It can be used to provide increased service resilience in the event of a failure in the cloud infrastructure or communication network.

[0007] The edge cloud here refers to a distributed cloud, where the user is accessing end-user services provided by applications hosted in the distributed cloud, and where the user is accessing the services through a mobile network. The application that provides end-user services may be a distributed application deployed across multiple cloud locations. It may also be an application in which individual application instances are deployed in multiple cloud locations. In both cases, we 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 the communication anchor point. The anchor point in the text refers to a point or node that terminates a mobile network user plane session at a data network. The data network can be identified by an identifier such as a data network access identifier (DNAI). The anchor point may be referred to as a protocol data unit (PDU) session anchor (PSA) user plane function (UPF) node in 5G, for example. User traffic is also carried between the anchor point and the application instance in the edge cloud node through the data network.

[0008] In order to exploit the geographical and topological distribution of edge cloud nodes, coordination between the mobile access network and the edge cloud and / or end-user service applications is required to ensure that the UE obtains service from a communication anchor point in the mobile access network that is close to the edge cloud location hosting the application instance that is serving the UE. Figure 1An edge cloud with nodes at multiple locations is shown, wherein end-user services are provided by applications having application instances at a subset or all of the edge cloud locations, wherein a mobile network is capable of carrying user traffic between a client and more than one communication anchor point, and wherein the best selection of an anchor point for a particular UE depends on the UE location and the subset of edge cloud nodes hosting the application instances. Coordination is required to handle, for example, edge site selection and edge site switching for clients served by the edge cloud over a mobile access network.

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

[0010] To allow new edge-based end-user services to take advantage of further distribution of the cloud, several changes in mobile networks are required. Additional communication anchor points are needed, and clients should be able to flexibly switch between communication anchor points based on different optimization goals.

[0011] In the context of the 5G Core Network (5GC), new mechanisms are introduced to support local breakout in the mobile packet core. These mechanisms will enable access closer to the edge cloud, and the benefits it may bring, such as latency reduction and resource efficiency. It also introduces the requirement to handle coordination between the mobile access network and the distributed cloud.

[0012] One issue in edge cloud is how to provision edge connection services (ECS) to client UEs. This is a problem because mobile connectivity is conventionally provisioned by mobile operators in negotiation with UEs, such as through subscriptions. However, in edge cloud ecosystems, connectivity requirements are heavily dependent on applications and their distribution across edge sites, and it can be difficult to take advantage of the benefits that distribution can bring in terms of service performance. Summary of the invention

[0013] The purpose of this document is to improve the provision of application-dependent connectivity services to UEs in a more efficient manner.

[0014] According to an aspect, the object is achieved by providing a method implemented by a network node for processing a service request for a connection service from an application server in a communication network. The network node configures the application with an edge connection service for a UE. The network node may, for example, establish an ECS and / or register the UE with the ECS.

[0015] A computer program product comprising instructions is also provided herein, which, when executed on at least one processor, causes the at least one processor to perform any of the above methods implemented by a network node. A computer-readable storage medium is further provided herein, having stored thereon a computer program product comprising instructions, which, when executed on at least one processor, causes the at least one processor to perform a method according to any of the above methods as implemented by a network node.

[0016] According to an embodiment of the present invention, a network node is further provided for processing a service request for a connection service from an application of an application server in a communication network, wherein the network node is configured to: configure the application with an edge connection service for a user equipment.

[0017] Embodiments of the present invention enable an application (also referred to as a cloud application) to configure an edge connectivity service (ECS) and provide it to one or more UEs. An edge system interface function (ESIF) is described herein that manages the ECS, the ESIF interfacing the application and the mobile packet core of a mobile access network. A process for configuring the ECS in the ESIF is disclosed herein, including negotiating with the application to define the ECS, creating associated policies, and registering the service in the ESIF. In addition, a process for provisioning services to a UE is disclosed herein, which involves negotiation between the application and the mobile access network and registering the UE as a subscriber to the ECS in the ESIF. In addition, a process for providing required information and policies (i.e., policies related to edge location selection and application participation) to a mobile network based on an edge connectivity service description is provided herein. Certain functions require 3GPP extensions.

[0018] Embodiments herein provide an application with the ability to flexibly request configuration of an edge connection service (ECS) that meets application requirements, and provide the ECS to a UE accessing services provided by an application such as a cloud application (eg, the application may be a distributed application).

[0019] The embodiments herein can optimize edge connectivity services according to use cases that place different requirements on edge connectivity, such as high-volume data and real-time applications, applications with large or limited distribution, and so on. By allowing application-controlled configuration and provisioning of edge connectivity services to capture requirements from applications, flexible edge connectivity services can be provided for different applications, and optimized use of infrastructure can be provided. The embodiments herein can promote the evolution of the edge ecosystem by providing a flexible infrastructure rather than a one-size-fits-all infrastructure and by providing a simple interface for configuring edge connectivity services. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Embodiments will now be described in more detail with reference to the accompanying drawings, in which:

[0021] Figure 1 is a schematic overview depicting a communication network using an edge cloud;

[0022] Figure 2 is a schematic overview depicting a communication network according to embodiments herein;

[0023] Figure 3 A method implemented by a network node according to an embodiment of the present invention is shown;

[0024] Figure 4a A combined flow chart and signaling scheme according to embodiments of the present invention are shown;

[0025] Figure 4b A combined flow chart and signaling scheme according to embodiments of the present invention are shown;

[0026] Figure 5a A combined flow chart and signaling scheme according to embodiments of the present invention are shown;

[0027] Figure 5b A schematic flow chart depicting a method implemented by a network node according to embodiments herein is shown;

[0028] Figure 6 is a block diagram depicting a network node according to embodiments herein;

[0029] Figure 7 shows a telecommunications network connected to a host computer via an intermediate network according to some embodiments;

[0030] Figure 8 A host computer is shown communicating with a user device via a base station over a partially wireless connection according to some embodiments;

[0031] Fig. 9 A method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments is shown;

[0032] Fig.10 A method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments is shown;

[0033] Fig.11 A method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments is shown; and

[0034] Fig.12 A method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments is shown. DETAILED DESCRIPTION

[0035] Embodiments herein generally relate to communication networks. Figure 2 is a schematic overview depicting a communication network 1. The communication network 1 comprises one or more mobile access networks (e.g. RAN) and one or more CNs. The communication network 1 may use one or more different technologies. The embodiments herein relate to the latest technology trends of particular interest in the context of 5G; however, the embodiments are also applicable to further developments of existing communication systems such as LTE and Wideband Code Division Multiple Access (WCDMA).

[0036] In the communication network 1, UEs are configured to communicate with the CN or with each other, for example, UE 10 (e.g., a mobile station, a non-access point station (non-AP-STA), a STA, a wireless device and / or a wireless terminal) can be configured for communication. It should be understood by those skilled in the art that "UE" is a non-restrictive term, which refers to any terminal, wireless communication terminal, user equipment, narrowband Internet of Things (NB-IoT) device, machine type communication (MTC) device, device-to-device (D2D) terminal, or node (e.g., a smart phone, a notebook computer, a mobile phone, a sensor, a repeater, a mobile tablet computer, or even a small base station capable of communicating using radio communication with a radio network node or a wireless device).

[0037] The communication network 1 comprises a radio network node 12, also referred to as a first radio network node, which provides radio coverage over a geographical area, a service area 11, of a first radio access technology (RAT), such as NR or similar. The radio network node 12 may be a transmitting and receiving point, such as an access node, an access controller, a base station, for example a radio base station, such as a gNodeB (gNB), an evolved NodeB (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 access point station (AP STA), a transmission arrangement of a radio base station, a standalone access point, or any other network element or node (which is capable of communicating with wireless devices within the area served by the radio network node 12, depending on, for example, the first radio access technology and terminology used). The radio network node 12 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 10 in the form of DL transmissions to the wireless device 10 and UL transmissions from the wireless device 10. It should be noted that the service area may be represented as a cell, beam, beam group or similar to define an area of ​​radio coverage. The radio network node 12 may beamform its transmissions to one or more wireless devices such as the UE 10. Beamforming allows a stronger signal for an individual connection.

[0038] The communication network 1 also includes a network node 13, which is called a control node or a node with edge connection services, which is a network node such as a function or server collocated with another network node (such as a mobility management entity (MME) or an access and mobility management function (AMF) node), or an independent node. In addition, the communication network includes multiple other network nodes, such as AMF, which supports termination of non-access layer (NAS) signaling, NAS encryption and integrity protection, registration management, connection management, mobility management, access authentication and authorization, and security context management. Session management function (SMF) node, which supports: session management (session establishment, modification, release), UE IP address allocation and management, DHCP function, termination of NAS signaling related to session management, DL data notification, and service manipulation configuration of UPF for appropriate service routing. User plane function (UPF) node, which supports: packet routing and forwarding, packet inspection, quality of service (QoS) processing, acts as an external protocol data unit (PDU) session point for interconnection with the data network (DN), and is an anchor point for mobility within and between RATs. Other possible nodes or functions may be a Policy Control Function (PCF) node, which supports: unified policy framework, provision of policy rules for control plane (CP) functions, access subscription information for policy decisions in the Unified Data Repository (UDR). An Authentication Server Function (AUSF) node, which acts as an authentication server. A Unified Data Management (UDM) node, which supports: generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, subscription management. An Application Function (AF) node, which supports: application influence on service routing, access to NEF, interaction with the policy framework for policy control. A Network Exposure Function (NEF) node, which supports: exposure of capabilities and events, secure provision of information from external applications to the 3GPP network, translation of internal / external information. A NF Repository Function (NRF) node, which supports: service discovery functionality, maintenance of NF profiles and available NF instances.

[0039] The communication network 1 further comprises one or more data network nodes 14' and 14", also referred to as anchor point nodes, such as gateway nodes, user plane function (UPF) nodes or similar nodes. The one or more data network nodes provide access to a data network of the communication network, e.g. from different operator networks or similar networks.

[0040] The communication network 1 may also include one or more application nodes or application servers 15', 15", also referred to as application server 15, which include an application or service, which in turn uses an edge connection service for a connection between an application instance hosted at the edge (for example, in application servers 15' and 15") and a UE that is accessing an end-user service provided by the application. The application server 15 may be referred to as a cloud application node or the like and may include at least a portion of the application. The application that provides end-user services may be a distributed application deployed in multiple locations (referred to as a distributed network (DN), DN' and DN"). It may also be an application in which individual application instances are deployed in multiple cloud locations. The method according to an embodiment of the present invention is implemented by a network node 13. As an alternative, distributed nodes and functions (for example, included in a cloud) may be used to implement or partially implement the method.

[0041] Embodiments herein enable an application (also referred to as a cloud application) to configure an edge connection service (ECS) and provision the ECS to one or more UEs. Embodiments herein may use a network node 13, such as an edge system interface function (ESIF) in the network node 13, which interfaces with the application and the packet core of the mobile access network and provides additional functionality for providing the ECS. The network node 13 may be part of an operator domain. Figure 4a-4b Configuring an ECS using input from an application is disclosed. Figure 5a-5b An ECS that supplies applications to the UE 10 is described.

[0042] Now refer to Figure 3 The flowchart shown in the figure is used to describe the method actions for processing the service request for the connection service from the application server 15 in the communication network 1 by the network node 13 (also called ECS node) according to the embodiment. The actions do not have to be taken in the order described below, but can be taken in any suitable order. The actions implemented in some embodiments are marked with dashed boxes.

[0043] Action 301. The network node 13 configures the application with an edge connection service for the UE 10. The network node 13 may establish an ECS and / or register the UE 10 with the ECS.

[0044] Action 3011. For example, the network node 13 may establish a configuration for the edge connection service. This may be implemented by the network node negotiating with the application server 15 to determine the configuration of the edge connection service. For example, the network node 13 may register the edge connection service with the configuration for the application, so that the configuration of the service is completed, and the network node 13 registers the ECS as a service provided to the application and can now be used. This is in Figure 4a-4bThe configuration for the edge connection service may include one or more of the following: a policy for switching from a first anchor point to a second anchor point based on the location of the UE 10; one or more identifiers of the anchor points; quality of service (QoS) parameters; traffic classifier rules for the ECS application, e.g., rules that are specific to DNAI; and the degree of participation of the application in the switching. The configuration may include, for example, Figure 4a One or more service parameters as indicated.

[0045] Action 3012 . Alternatively or additionally, the network node 13 may receive a request such as a service request for an edge connection service from the application server 15 , wherein the request comprises an indication of the UE 10 .

[0046] Action 3013 . The network node 13 may establish a configuration of one or more radio network nodes of a radio access network for providing the UE 10 with an edge connectivity service.

[0047] Action 3014. The network node 13 may register the UE 10 to the edge connectivity service.

[0048] The embodiments herein provide an application with the ability to flexibly request the configuration of an edge connection service (ECS) that meets the requirements of one or more applications, and supply the ECS to clients accessing the services provided by the application. The embodiments provide the following advantages: for example, optimization of edge connection services is achieved according to use cases that place different requirements on edge connections (e.g., high-capacity data and real-time applications, applications with large or limited distribution, etc.). The embodiments herein can capture requirements from cloud applications by allowing the configuration and provision of edge connection services to be controlled by cloud applications, and optimize the use of infrastructure by providing flexible edge connection services to different applications. The embodiments herein can promote the evolution of the edge ecosystem by providing a flexible infrastructure rather than a one-size-fits-all infrastructure and by providing a simple interface for configuring edge connection services.

[0049] Figure 4a is a combined flow chart and signaling scheme according to embodiments of the present invention. The actions need not be taken in the order described below, but may be taken in any suitable order. The actions implemented in some embodiments are marked as dashed boxes. Figure 4a Publicly disclosed a Figure 3 The method for configuring ECS ​​is shown in action 3011 in FIG.

[0050] Action 401. The network node 13 opens an interface (also referred to as ESIF) to one or more applications running on the application server 15 for requesting configuration of the ECS. The application server 15 uses the ESIF to submit (i.e., send) a request such as an ECS Configuration Request (see below) containing one or more service parameters associated with the desired ECS. The one or more service parameters may include 3GPP defined connection parameters and edge specific parameters describing edge related behaviors (e.g., handover between edges, etc.). The following information may be part of the ECS Configuration Request:

[0051] ● Data Network Access Identifier (DNAI) list, for example, if requested;

[0052] ○ Each DNAI represents an anchor point, such as a UPF node, for edge positioning of the radio network node. The set of DNAIs belonging to the ECS may depend on the application. For example, the application may exist on application server 1 via, for example, UPF1, on application server 3 via, for example, UPF3, but not on application server 2 (e.g., UPF2). In this case, the ECS may exclude UPF2.

[0053] o For each DNAI, there may be an associated uplink traffic classifier rule that specifies a subset of traffic that should be forwarded to the DNAI, e.g., a range of destination IP addresses.

[0054] 3GPP-defined connection parameters, e.g., where requested;

[0055] o QoS parameters such as signal-to-interference-plus-noise ratio (SINR), signal-to-noise ratio (SNR), throughput, latency or similar parameters.

[0056] ● Service Continuity Mode (SSC), e.g., if requested;

[0057] ○ In 3GPP, SSC is defined as being related to the handover behavior between communication anchor points (i.e., DNAI).

[0058] ■SSC Mode 1 (no change in communication anchor point)

[0059] ■SSC Mode 2 (break-before-make)

[0060] ■SSC Mode 3 (make-before-break)

[0061] ● Application impact, e.g., where requested;

[0062] ○ Applications of a specified application server participate in events such as DNAI switching:

[0063] ■No;

[0064] ■ Early notification, for example, the app subscribes to information notifications about the switch before the switch;

[0065] ■ Late notification, for example, the app subscribes to information notifications about the switch after the switch;

[0066] ■ Handoff approval, i.e., the application requests to participate in a handoff and is approved before any handoff is performed.

[0067] ●Service parameter priority

[0068] o If all requirements cannot be met, each of the above service parameters may be appended with a priority parameter, where, for example, a value of 1 may represent a hard requirement, and subsequent values ​​(2, 3, 4, ...) represent decreasing priority. Thus, the service parameters are sorted internally.

[0069] Action 402. The network node 13 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., RAN). The network node 13 may check available support in the RAN for the information indicated in the ECS configuration request. The service capabilities may include, for example, the registered capabilities of the mobile access network associated with the ECS, such as:

[0070] ●DNAI list (all DNAIs that can be used by ESIF)

[0071] o Specification of DNAI type and whether it is associated with, for example, an IP anchor for the UE;

[0072] QoS profile (range of supported options)

[0073] o A list of predefined profiles or the complete range of defined connection parameters supported by 3GPP;

[0074] ●Service Continuity Mode (Supported Options)

[0075] ○SSC Mode 1 (Yes / No)

[0076] ○SSC Mode 2 (Yes / No)

[0077] ■optionally, a DNAI group between which SSC mode 2 is supported;

[0078] ○SSC Mode 3 (Yes / No)

[0079] ■optionally, a DNAI group between which SSC mode 3 is supported;

[0080] ●Application Impact (Supported Options)

[0081] ○None (yes / no)

[0082] ○Early notice (yes / no)

[0083] ○ Late notice (yes / no)

[0084] ○Switch Approval (Yes / No)

[0085] Action 403. The network node 13 responds to the application server 15 with an ECS description (ECSD) that at least partially matches the ECS configuration request based on the available capabilities. It may be necessary to prioritize the service parameters to generate the ECSD. These priorities may be pre-configured in the ESIF or provided by the application as part of the ECS configuration request. The ECSD may include one or more of the following:

[0086] = DNAI list (and classifier rules if applicable), e.g. validated;

[0087] QoS profile, such as 3GPP TS23.501-5.7.1.2, such as confirmed;

[0088] ●Service continuity model, such as confirmed;

[0089] ●Application impact, such as confirmed.

[0090] Action 404. The application server or application determines the ECS configuration to use based on the received ECSD and the application requirements. Further negation between the network node 13 and the application may be required to agree on the ECSD. For example, instead of accepting the ECSD, the application may submit a modified ECS configuration request, which generates an updated ECSD from the network node 13. The ECS may also supplement the ECSD with information about service capabilities to facilitate modifying the ECS configuration request for the application.

[0091] Action 405. Once the ECSD generated by the network node 13 is accepted by the application, the application server 15 sends an ECSD configuration request to instruct the network node 13 to configure the confirmed ECSD.

[0092] Action 406. The network node 13 receives the ECSD configuration request and implements the necessary configuration. The network node 13 may register the ECS as configured for the application. The network node 13 may define a policy for DNAI selection (i.e., define a service area such as a geographic service area for a communication anchor point (i.e., DNAI) that is part of the ECSD). Therefore, the network node 13 may add an entry for the configured ECS in the registration table and may insert the ECSD and policy information related to DNAI selection. The network node 13 may support maintaining the provisioned services according to the ECS description, for example, handling the impact of the application on the handover.

[0093] The network node 13 may maintain a registry of configured ECSs. For each ECS entry, the following information may be included:

[0094] ECSID

[0095] ○ECS logo

[0096] ECSD

[0097] ○See "ECS Description"

[0098] CloudAppID (cloud application registered to ECSID)

[0099] ○ List of applications registered as the user of the ECSID (e.g., the application requesting configuration of the ECS)

[0100] ●ClientID (client ID), such as Universal Public Subscription Identifier (GPSI), ClientAppID, current DNAI (optional)

[0101] ○ The client that was provisioned to ECS and the corresponding application identifier that requested the client provisioning

[0102] ○ ESIF can track the current DNAI of the client UE in order to respond to queries from cloud applications

[0103] ●Strategy information

[0104] ○DNAI selection strategy (UPF selection strategy information)

[0105] For example, if the ECSD includes notifications of DNAI switching, the network node 13 can receive notifications from SMF nodes related to DNAI switching. These notifications can be forwarded to the application. If the ECSD includes, for example, application participation in DNAI switching, 3GPP extensions may be required. Extensions to NEF / PCF / SMF messaging allow the SMF node to request AF approval of UPF switching, for example, by specifying a target DNAI for the client ID through PCF / NEF, and extensions allow the AF to respond to the SMF request through NEF / PCF. The network node 13 can then receive a switching approval request from the SMF node, and the network node 13 can coordinate the approval with the application on the application server 15.

[0106] Figure 4b An example is shown when the network node 13 is instantiated as an ESIF and the application is instantiated as a cloud application. The following steps may be implemented to configure the ECS at the network node 13:

[0107] ESIF opens an interface to cloud applications for requesting ECS ​​configuration. Cloud applications use this interface to submit ECS configuration requests, which contain service parameters associated with the required ECS. Service parameters can include 3GPP-defined connection parameters and edge-specific parameters that describe edge-related behaviors (inter-edge handover, etc.).

[0108] The ESIF receives the ECS configuration request and compares it with an internal registry of service capabilities of the relevant mobile access network. The information is contained in this registry.

[0109] The ESIF responds with an ECS Description (ECSD) that best matches the request based on available capabilities. Service parameters may need to be prioritized to generate the ECSD. These priorities may be pre-configured in the ESIF or may be provided by the cloud application as part of the ECS configuration request.

[0110] ● Further negotiation between the ESIF and the cloud application may be required to agree on the ECSD.

[0111] o Instead of accepting the ECSD, the cloud application may submit a modified ECS configuration request, which generates an updated ECSD from the ESIF. The ECS may also supplement the ECSD with information about service capabilities to facilitate modifying the ECS configuration request for the cloud application.

[0112] ●Once the ECSD generated by the ESIF is accepted by the cloud application, it submits an ECSD configuration request to instruct the ESIF to configure the confirmed ECSD.

[0113] ●ESIF receives ECSD configuration requests and implements necessary configuration.

[0114] o ESIF defines the policy for DNAI selection (ie, defines the service area of ​​the communication anchor point (ie, DNAI) as part of ECSD).

[0115] o ESIF adds an entry in its registry for the configured ECS and inserts the ECSD and policy information related to the DNAI selection.

[0116] Figure 5a is a combined flow chart and signaling scheme according to embodiments of the present invention. The actions need not be taken in the order described below, but may be taken in any suitable order. The actions implemented in some embodiments are marked as dashed boxes. Figure 5a A method for providing ECS ​​to a UE is disclosed, such as Figure 3 As shown in actions 3012-3014.

[0117] Action 501. The UE sends a service request to an application or application server 15. The application may provide ECS enablement.

[0118] Action 502. The application server sends a service request such as an ECS request to a network node 13 such as an ECS server. Therefore, in order to provide the configured ECS to the UE 10, the application submits a provisioning request to the network node 13, the request including one or more of the following: an ID of the UE, such as a client ID (ClientID-GPSI / IP / MAC), an application identifier, such as a client application identifier (ClientAppID); and an identifier of the configured ECS (ECSID). The application may have received the UE ID and the application ID in the service request from the UE 10.

[0119] Action 503. The network node 13 may establish an ECS for the UE upon request. For example, the network node 13 may configure the mobile packet core to provide the requested service to the UE 10. For example, the network node 13 may submit policy information for DNAI selection associated with the ECSID to the mobile packet core. The network node may use an AF request (3GPP TS 23.501-5.6.7) related to the policy for UPF selection. The AF request is sent directly to the PCF via N5 or via NEF (depending on the operator configuration). The PCF converts the AF request into a policy that is applied to the PDU session and used by the SMF node. The AF request used by the network node 13 may include the following 3GPP defined entries:

[0120] ■Potential location for application: DNAI list from ECSD.

[0121] ■Target UE identifier: ClientID, i.e. GPSI / Subscription Permanent Identifier (SUPI) / IP / MAC.

[0122] ■ Information about AF subscription to corresponding SMF events: Early / Late Notification (3GPP TS23.501-5.6.7), depending on the application impact as defined in ECSD.

[0123] ■3GPP extension: In the case where DNAI handover is handled by SMF, 3GPP TS 23.501 may need to be extended to support application participation at the ECSD level “handover approval”.

[0124] • Extension to 3GPP TS 23.501-5.6.7 with additional fields, such as "Impact of AF corresponding to SMF events", where the AF can request that it must approve before performing any UPF changes.

[0125] ● Extension of 3GPP TS 23.501-6.3.3, where the SMF may require AF approval to change to the selected UPF / DNAI. In addition, the policy related to the situation where the AF refuses to change (i.e. the timeout value before the new AF approves the request) is set by the SMF.

[0126] The network node 13 may further initiate a network-triggered PDU session establishment procedure defined by 3GPP (3GPP TS23.502-4.3.2). The network node 13 may achieve this by invoking an application trigger to the UE via the NEF. (TS23.502-4.13.2). The network node 13 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 about which application (ClientAppID) on the UE side is expected to trigger the PDU session establishment request. This may be an identifier of a client application associated with the application.

[0127] The client application (ClientAppID) on the UE side can trigger the PDU session establishment process. This is a NAS message, which contains the following information: S-NSSAI, DNN, PDU session ID, request type, old PDU session ID, N1 SM container (PDU session establishment request).

[0128] During the PDU session establishment process, the SMF node associated with the UE 10 performs UPF selection based on the policy provided by the network node via the PCF / NEF in the previous step (e.g., as described in TS23.501-6.3.3.3). If requested by the network node according to the policy, a notification of the current DNAI is sent to the network node 13.

[0129] Action 504. The network node 13 may then register the UE 10 with the ECS, for example, together with the identifier of the application. For example, the network node 13 may register the ClientID (GPSI) as a subscriber of the ECSID in its ECS registry, along with the associated application identifiers (CloudAppID, ClientAppID) and the current DNAI. The edge connection service is now available to the UE 10, and the network node 13 may confirm to the application that the service has been provisioned to the UE, as well as the current DNAI.

[0130] Figure 6 is a block diagram depicting a network node 13 according to embodiments herein, in both embodiments, the network node 13 is used to process a service request for a connectivity service, such as enabling an application providing an ECS in a wireless communication network.

[0131] The network node 13 may include a processing circuit 601, such as one or more processors, configured to implement the methods herein.

[0132] The network node 13 may include a configuration unit 602. The network node 13, the processing circuit 601 and / or the configuration unit 602 are configured to configure the application to have an edge connection service for the UE 10.

[0133] The network node 13, the processing circuit 601 and / or the configuration unit 602 may be configured to configure the application by being configured to establish a configuration for the edge connection service.

[0134] The network node 13, the processing circuit 601 and / or the configuration unit 602 may be configured to establish the configuration by being configured to negotiate with an application server to determine the configuration of the edge connection service.

[0135] The network node 13, the processing circuit 601 and / or the configuration unit 602 may be configured to configure the application by registering the edge connection service with the configuration for the application.

[0136] The network node 13, the processing circuit 601 and / or the configuration unit 602 can be configured to configure the application by being configured to implement the following operations: receiving a request for an edge connection service from an application server, wherein the request includes an indication of a user equipment; and establishing a configuration of one or more radio network nodes of a radio access network for providing edge connection services to the user equipment.

[0137] The network node 13, the processing circuit 601 and / or the configuration unit 602 may be configured to configure the application by being configured to register the user equipment to the edge connection service.

[0138] Configuration for edge connectivity services includes one or more of the following:

[0139] A strategy for switching from a first anchor point to a second anchor point based on the location of the user equipment; one or more identifiers of the anchor point; quality of service QoS parameters; and the degree of participation of the application in the handover. The radio network node 13 also includes a memory 603. The memory 603 includes one or more units to be used for storing data (e.g., signal strength or quality, mapping of TA to anchor point, service ID, UE ID of the subscribing UE, an application that implements the method disclosed herein when executed, etc.). The network node 13 may also include a communication interface (including, for example, one or more antennas or antenna elements).

[0140] The methods according to the embodiments described herein for the network node 13 are implemented by, for example, a computer program product 607 or a computer program, respectively, which comprises instructions, i.e. software code portions, which, when executed on at least one processor, cause the at least one processor to perform the actions described herein as implemented by the network node 13. The computer program product 607 may be stored on a computer-readable storage medium 608, such as an optical disk, a universal serial bus (USB) stick, or the like. The computer-readable storage medium 608 on which the computer program product has been stored may comprise instructions, which, when executed on at least one processor, cause the at least one processor to perform the actions described herein as implemented by the network node 13. In some embodiments, the computer-readable storage medium may be a transient or non-transitory computer-readable storage medium.

[0141] In some embodiments, the more general term "network node" is used, and it may correspond to any type of radio network node or any network node that communicates with a wireless device and / or with another network node. Examples of network nodes are NodeB, gNodeB, eNodeB, MeNB, SeNB, network nodes belonging to a master cell group (MCG) or a secondary cell group (SCG), a base station (BS), a multi-standard radio (MSR) radio node, such as an MSR BS, an eNodeB, a network controller, a radio network controller (RNC), a base station controller (BSC), a repeater, a donor node controlling a repeater, a base transceiver station (BTS), an access point (AP), a transmission point, a transmission node, a remote radio unit (RRU), a remote radio head (RRH), a node in a distributed antenna system (DAS), and the like.

[0142] In some embodiments, the non-limiting term "wireless device" or "user equipment (UE)" is used and refers to any type of wireless device that communicates with a network node and / or with another wireless device in a cellular or mobile communication system. Examples of UEs are target devices, device-to-device (D2D) UEs, proximity UEs (also known as ProSe UEs), machine-type UEs or UEs capable of machine-to-machine (M2M) communication, tablet computers, mobile terminals, smart phones, laptop embedded systems (LEEs), laptop mounted devices (LMEs), USB dongles, and the like.

[0143] Embodiments are applicable to any RAT or multi-RAT system in which a wireless device receives and / or transmits signals (e.g., data), such as New Radio (NR), Wi-Fi, Long Term Evolution (LTE), LTE Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile Communications / Enhanced Data Rates for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), to name a few possible implementations.

[0144] As will be readily understood by those familiar with communication design, functional components or units can be implemented using digital logic and / or one or more microcontrollers, microprocessors or other digital hardware. In certain embodiments, several or all of the various functions can be implemented together, such as in a single application specific integrated circuit (ASIC), or in two or more separated devices with suitable hardware and / or software interfaces between them. For example, several functions can be implemented on a processor shared with other functional components of a wireless device or network node.

[0145] Alternatively, some functional elements of the processing means discussed may be provided using dedicated hardware, while other functional elements are provided using hardware for executing software in association with appropriate software or firmware. Therefore, the terms "processor" or "controller" as used herein do not exclusively refer to hardware capable of executing software, but may implicitly include, but are not limited to, digital signal processor (DSP) hardware and / or program or application data. Other conventional and / or custom hardware may also be included. Designers of communication equipment will understand the cost, performance, and maintenance trade-offs inherent in these design choices.

[0146] Any appropriate steps, methods, features, functions or benefits disclosed herein may be implemented by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple such functional units. These functional units may be implemented by processing circuits, which may include one or more microprocessors or microcontrollers, and other digital hardware, which may include digital signal processors (DSPs), dedicated digital logic, etc. The processing circuit may be configured to execute program codes stored in a memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache, flash memory device, optical storage device, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more technologies described herein. In some embodiments, the processing circuit may be used to cause the corresponding functional unit to implement the corresponding functions according to one or more embodiments of the present disclosure.

[0147] refer to Figure 7 According to an embodiment, the communication system includes a telecommunication network 3210 (such as a cellular network of the 3GPP type), which includes an access network 3211 (such as a radio access network) and a core network 3214. The access network 3211 includes a plurality of base stations 3212a, 3212b, 3212c, such as NBs, eNBs, gNBs or other types of wireless access points as examples of radio network nodes 12 herein, each base station defining a corresponding coverage area 3213a, 3213b, 3213c. Each base station 3212a, 3212b, 3212c may be connected to the core network 3214 via a wired or wireless connection 3215. As an example of a wireless device 10, a first user equipment (UE) 3291 located in the coverage area 3213c is configured to be wirelessly connected to the corresponding base station 3212c or to be paged by the corresponding base station 3212c. A second UE 3292 in the coverage area 3213a may be wirelessly connected to the corresponding base station 3212a. Although multiple UEs 3291, 3292 are shown in this example, the disclosed embodiments are equally applicable to situations where only a UE is in the coverage area or only a UE is connected to the corresponding base station 3212.

[0148] The telecommunications network 3210 itself is connected to a host computer 3230, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 3230 may be under the ownership or control of a service provider, or may be operated by or on behalf of a service provider. The connections 3221 and 3222 between the telecommunications network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230, or may pass through an optional intermediate network 3220. The intermediate network 3220 may be one of a public network, a private network, or a managed network, or a combination of more than one of them; the intermediate network 3220 (if any) may be a backbone network or the Internet; in particular, the intermediate network 3220 may include two or more sub-networks (not shown).

[0149] Figure 7 The communication system generally implements a connection between one of the connected UEs 3291, 3292 and the host computer 3230. The connection can be described as an over-the-top (OTT) connection 3250. The host computer 3230 and the connected UEs 3291, 3292 are configured to use the access network 3211, the core network 3214, any intermediate network 3220, and possible other infrastructure (not shown) as intermediaries to transmit data and / or signaling via the OTT connection 3250. The OTT connection 3250 can be transparent in the sense that the participating communication devices through which the OTT connection 3250 passes do not know the routes of the uplink and downlink communications. For example, the base station 3212 may not be informed or need not be informed of the past routes of the incoming downlink communication of the data from the host computer 3230 to be forwarded (e.g., switched) to the connected UE 3291. Similarly, base station 3212 need not be aware of future routing of outbound uplink communications originating from UE 3291 toward host computer 3230.

[0150] Now refer to Figure 8Describe the example implementation of the UE, base station and host computer discussed in the previous paragraph according to the embodiment. In the communication system 3300, the host computer 3310 includes hardware 3315, the hardware 3315 includes a communication interface 3316, and the communication interface 3316 is configured to establish and maintain a wired or wireless connection of the interface of different communication devices of the communication system 3300. The host computer 3310 also includes a processing circuit 3318, which may have storage and / or processing capabilities. In particular, the processing circuit 3318 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these components (not shown) suitable for executing instructions. The host computer 3310 also includes software 3311, which is stored in the host computer 3310 or can be accessed by the host computer 3310 and can be executed by the processing circuit 3318. Software 3311 includes a host application 3312. The host application 3312 is operable to provide services to a remote user, such as a UE 3330 connected via an OTT connection 3350 terminating at the UE 3330 and the host computer 3310. In providing services to the remote user, the host application 3312 may provide user data transmitted using the OTT connection 3350.

[0151] The communication system 3300 also includes a base station 3320 provided in the telecommunication system, and the base station 3320 includes hardware 3325 that enables it to communicate with the host computer 3310 and the UE 3330. The hardware 3325 may include a communication interface 3326 for establishing and maintaining a wired or wireless connection with different communication devices of the communication system 3300, and a communication interface 3326 for establishing and maintaining a connection with a network located in the coverage area ( Figure 8 3327 of at least a wireless connection 3370 of a UE 3330 in the example embodiment (not shown). The communication interface 3326 may be configured to facilitate a connection 3360 to a host computer 3310. The connection 3360 may be direct, or it may pass through a core network ( Figure 8 3320) and / or traverse one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 3325 of the base station 3320 also includes processing circuitry 3328, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these components (not shown) suitable for executing instructions. The base station 3320 also has software 3321 stored internally or accessible via an external connection.

[0152] The communication system 3300 also includes the UE 3330 already cited. Its hardware 3335 may include a radio interface 3337, which is configured to establish and maintain a wireless connection 3370 with a base station serving the coverage area where the UE 3330 is currently located. The hardware 3335 of the UE 3330 also includes a processing circuit 3338, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these components (not shown) suitable for executing instructions. The UE 3330 also includes software 3331, which is stored in the UE 3330 or can be accessed by the UE 3330 and can be executed by the processing circuit 3338. The software 3331 includes a client application 3332. The client application 3332 is operable to provide services to human users or non-human users via the UE 3330 under the support of the host computer 3310. In the host computer 3310, the executing host application 3312 can communicate with the executing client application 3332 via an OTT connection 3350 that terminates at the UE 3330 and the host computer 3310. When providing services to users, the client application 3332 can receive request data from the host application 3312 and provide user data in response to the request data. The OTT connection 3350 can transmit both the request data and the user data. The client application 3332 can interact with the user to generate the user data it provides.

[0153] It should be noted that Figure 8 The host computer 3310, base station 3320 and UE 3330 shown in FIG. Figure 7 The host computer 3230, one of the base stations 3212a, 3212b, 3212c, and one of the UEs 3291, 3292 are the same. That is, the internal workings of these entities can be as follows Figure 8 As shown in , and independently, the surrounding network topology can be Figure 7 network topology.

[0154] exist Figure 8 In the figure, OTT connection 3350 has been abstractly drawn to show communication between host computer 3310 and UE 3330 via base station 3320, without explicitly involving any intermediate devices and the precise routing of messages via these devices. The network infrastructure can determine the route, which can be configured to hide the route from UE 3330 or the service provider operating host computer 3310, or both. When OTT connection 3350 is active, the network infrastructure can further make decisions to dynamically change the route (e.g., based on load balancing considerations or reconfiguration of the network).

[0155] The wireless connection 3370 between the UE 3330 and the base station 3320 is based on the teachings of the embodiments described throughout the present disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 3330 using the OTT connection 3350, where the wireless connection 3370 forms the last segment. More specifically, the teachings of these embodiments can improve the use of resources because the mitigation scheme is used based on the load in the adjacent radio network nodes, which leads to efficient use of resources and improved performance, and this can affect latency, thereby providing benefits such as reduced user waiting time and better responsiveness.

[0156] A measurement process may be provided to enable monitoring of data rates, latency, and other factors improved by one or more embodiments. In response to changes in the measurement results, there may also be an optional network function for reconfiguring the OTT connection 3350 between the host computer 3310 and the UE 3330. The measurement process and / or network function for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310 or in the software 3331 of the UE 3330, or in both. In an embodiment, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 3350 passes; the sensor may participate in the measurement process by providing the values ​​of the monitored quantities exemplified above, or by providing the values ​​of other physical quantities from which the software 3311, 3331 can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 3350 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not need to affect the base station 3320, and the base station 3320 may not know or be aware of the reconfiguration. These processes and functions may be known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates the host computer 3310 to measure throughput, propagation time, latency, etc. The measurements may be implemented as follows: the software 3311, 3331 uses the OTT connection 3350 to cause messages (particularly empty or "dummy" messages) to be transmitted while it monitors propagation time, errors, etc.

[0157] Fig. 9 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Figure 7 and Figure 8 To simplify this disclosure, only the Fig. 9. In a first step 3410 of the method, the host computer provides user data. In an optional sub-step 3411 of the first step 3410, the host computer provides the user data by executing a host application. In a second step 3420, the host computer initiates a transmission carrying the user data to the UE. In an optional third step 3430, in accordance with the teachings of the embodiments described throughout the present disclosure, the base station transmits the user data carried in the transmission initiated by the host computer to the UE. In an optional fourth step 3440, the UE executes a client application associated with the host application executed by the host computer.

[0158] Fig.10 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Figure 7 and Figure 8 To simplify this disclosure, only the Fig.10 Reference is made to the accompanying drawings of the method. In a first step 3510 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In a second step 3520, the host computer initiates a transmission carrying the user data to the UE. According to the teachings of the embodiments described throughout the present disclosure, the transmission may pass through a base station. In an optional third step 3530, the UE receives the user data carried in the transmission.

[0159] Fig.11 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Figure 7 and Figure 8 To simplify this disclosure, only the Fig.11 . In an optional first step 3610 of the method, the UE receives input data provided by the host computer. Additionally or optionally, in an optional second step 3620, the UE provides user data. In an optional sub-step 3621 of the second step 3620, the UE provides the user data by executing a client application. In another optional sub-step 3611 of the first step 3610, the UE executes a client application, which provides the user data in response to the received input data provided by the host computer. When providing the user data, the executed client application may also consider the user input received from the user. Regardless of the specific manner of providing the user data, the UE initiates the transmission of the user data to the host computer in an optional third sub-step 3630. In a fourth step 3640 of the method, in accordance with the teachings of the embodiments described throughout the present disclosure, the host computer receives the user data transmitted from the UE.

[0160] Fig.12 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Figure 7 and Figure 8 To simplify this disclosure, only the Fig.12 In an optional first step 3710 of the method, the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout the present disclosure. In an optional second step 3720, the base station initiates a transmission of the received user data to the host computer. In a third step 3730, the host computer receives the user data carried in the transmission initiated by the base station.

[0161] It should be understood that the foregoing description and drawings represent non-limiting examples of the methods and devices taught herein. Therefore, the devices and techniques taught herein are not limited by the foregoing description and drawings. Instead, the embodiments herein are limited only by the following claims and their legal equivalents.

Claims

1. A method implemented by a network node (13) for processing a service request for a connection service from an application of an application server (15) in a communication network, comprising: - configuring (301) the application with an edge connection service for a user device, Wherein, the configuration includes: - receiving an edge connection service description (ECSD) configuration request for the edge connection service from the application server, the ECSD configuration request instructing the network node to configure the confirmed ECSD; - registering the edge connection service as configured for the application; - receiving a request for the edge connection service from the application server, wherein the request for the edge connection service comprises an indication of the user equipment; and - establishing the edge connection service for the user equipment according to the request for the edge connection service.

2. The method according to claim 1, wherein: Configuration includes: - Establishing (3011) a configuration for said edge connection service.

3. The method according to claim 2, wherein: Building the configuration includes: - Negotiating with said application server to determine said configuration of said edge connection service.

4. The method according to claim 2 or 3, wherein: The configuration also includes: -Registering the edge connection service with the configuration for the application.

5. The method according to claim 1 or 2, wherein: The configuration also includes: - establishing (3013) a configuration of one or more radio network nodes of a radio access network for providing said edge connectivity service to said user equipment.

6. The method according to claim 5, wherein: The configuration also includes: -Registering (3014) the user equipment to the edge connectivity service.

7. The method according to claim 1 or 2, wherein: The configuration for the edge connection service includes one or more of the following: a strategy for switching from a first anchor point to a second anchor point based on a location of the user equipment; One or more identifiers of anchor points; Quality of service QoS parameters; Traffic classifier rules applicable to the edge connection service; and The degree of involvement of the application in the handoff.

8. A network node (13) for processing a service request for a connection service from an application of an application server (15) in a communication network, wherein: The network node is configured to: configure the application with an edge connection service for a user device (10), The network node is configured to configure the application by being configured to perform the following operations: - receiving an edge connection service description (ECSD) configuration request for the edge connection service from the application server, the ECSD configuration request instructing the network node to configure the confirmed ECSD; - registering the edge connection service as configured for the application; - receiving a request for the edge connection service from the application server, wherein the request for the edge connection service comprises an indication of the user equipment; and - establishing the edge connection service for the user equipment according to the request for the edge connection service.

9. The network node (13) according to claim 8, wherein: The network node is configured to configure the application by being configured to establish a configuration for the edge connection service.

10. The network node (13) according to claim 9, wherein: The network node is configured to establish the configuration by being configured to negotiate with the application server to determine the configuration of the edge connection service.

11. The network node (13) according to claim 9 or 10, wherein: The network node is configured to configure the application by registering the edge connection service with the configuration for the application.

12. The network node (13) according to claim 8 or 9, wherein: The network node is configured to configure the application by being configured to perform the following operations: establishing a configuration of one or more radio network nodes of a radio access network for providing the edge connection service to the user equipment.

13. The network node (13) according to claim 12, wherein: The network node is configured to configure the application by being configured to register the user equipment with the edge connection service.

14. The network node (13) according to claim 8 or 9, wherein: The configuration for the edge connection service includes one or more of the following: a strategy for switching from a first anchor point to a second anchor point based on a location of the user equipment; One or more identifiers of anchor points; Quality of service QoS parameters; Traffic classifier rules applicable to the edge connection service; and The degree of involvement of the application in the handoff.

15. A computer-readable storage medium having instructions stored thereon, which, when executed on at least one processor, cause the at least one processor to perform the method according to any one of claims 1-7 as implemented by the network node (13).