Method and application-specific network entity for handling of at least one application of the service type in a communication network

Abstract

Disclosed is an application-specific network entity (160; 170) for handling of the application in a communication network (100), the application being provided by an application server (150) The entity (160; 170) obtains application layer-related information, such as QoE metric, from a UE (140) running the application, and obtains radio-related information, such as QoS metric, related to a connection between the UE (140) and a Radio Access Network (130) to which the UE is connected. The entity (160; 170) determines, based on the obtained application layer-related information and radio-related information, an action for the RAN (130) and / or for the at least one application for improving QoE of sessions on the UE (140) of the application, and sends information on the determined action to the RAN(130), UE (140) or application server (160).

Description

METHOD AND APPLICATION-SPECIFIC NETWORK ENTITY FOR HANDLING OF AT LEAST ONE APPLICATION OF THE SERVICE TYPE IN A COMMUNICATION NETWORKTECHNICAL FIELD

[0001] The present disclosure relates generally to methods, application-specific network entities, User Equipment (UE) and systems for handling of at least one application of the service type in a communication network. The present disclosure further relates to computer programs and carriers corresponding to the above methods and entities.BACKGROUND

[0002] For an end user of a communication device, aka UE, the experienced quality of a communication network depends much on how services and applications on the UE behave, such as experienced response times, latency, packet loss rates, throughput, etc.

[0003] In the Radio Access Network (RAN) of the communication network, Quality of Service (QoS) and Quality of Experience (QoE) measurements are used to actively monitor and control the quality of the services / applications offered by the communication network to the UEs connected to the communication network. While QoS measurements are collected at the radio and transport layers of the communication network, the QoE measurements are collected at the application layer of the UE. Examples of QoS measurements are throughput, packet loss, bit rate, transmission delay, signal to noise ratio (SNR), etc. Examples of QoE measurements are application layer buffer levels, round-trip times, latency, experienced response times, etc.

[0004] In general, it is assumed that when the network ensures good QoS for the services running on top of the network infrastructure, the end-users also perceive a good QoE at the application layer. However, this inter-dependence doesn’t always hold in the context of certain applications - in other words, a good QoS does not fully translate into a good QoE for the end users. A classic exampleof this is video conferencing applications where simple QoS metrics like throughput may not translate into good video conferencing experience.

[0005] Both QoS and QoE measurements are standardized in the 3GPP standardization forum. Nevertheless, while QoS-related measurements may be gathered by the RAN independently from the user applications running on top of the UEs, e.g., via RRC measurements at the radio layer, gathering QoE-related measurements from the application layer is not trivial. Obtaining application layer measurements e.g., QoE measurements, to optimize the network performance, requires standardization since cooperation from the user applications running on the UEs may be required for exposure of QoE measurements. This, in general, translates to a tedious standardization process for agreeing which QoE measurements are valuable to be collected from the UE for network optimization.

[0006] With respect to QoE measurements, the 3GPP specifications enable the collection of QoE measurements from the application layer of the UE and their reporting to the network. In addition, 3GPP specified the so-called RAN Visible QoE (RVQoE) measurements, in which the QoE measurement results are reported to the RAN. The reason for introduction of RVQoE measurements is that the RAN can correlate these QoE measurement results with QoS measurement results and perform suitable reconfiguration of the RAN to ensure both QoS and QoE are delivered as expected.

[0007] The application servers, i.e. , providers of the service / application to UEs, also collect different application-specific QoE data from an application client software running on the UEs, mostly in proprietary, i.e., non-standardized, ways. An example of this could be a video streaming service collecting QoE-related information from the video streaming clients on the UEs to determine the observed QoE at the client side, and to make changes to video streams accordingly such as changing codecs or video stream resolution to improve the QoE of the end-user. The process of QoE-related data gathering at the application servers, however, is proprietary, i.e., it is transparent to the RAN and the mobile operator’s communication network, since all application layer information, including these QoE-related measurements, are carried as communication payload, e.g., as userplane data, across the communication network. If we borrow the User-Plane (UP) and Control-Plane (CP) analogy in the RAN for user applications, e.g., video conferencing applications, then the actual audio and video streams would correspond to UP traffic between the client application and application server while the QoE related measurements collected as part of that service would correspond to CP traffic meant to adapt the audio and video streams for better QoE.

[0008] Fig. 1 exemplifies the CP and UP streams that a UE 40 could have with a RAN network node, here exemplified by a gNodeB (gNB) 30 and an application server 50. The end-user of the UE 40 has downloaded software to the UE 40 for an application client 42 corresponding to the application provided by the application server 50 to be able to use the application. The UE 40, on start-up, establishes connectivity (1) via a CP connection with the gNB 30 and subsequently uses communication resources of the communication network to establish a UP connection (2) with the application server 50, more specifically between the application client 42 on the UE 40 and the application server 50. The connection (2) with the application server 50, however, can be viewed as comprising both UP and CP since both the application data streams as well as the application layer measurements such as QoE measurements are sent over that same connection.

[0009] As described above, the RAN will benefit from visibility of the user-perceived application layer QoE. This visibility will enable better RAN optimization for certain QoS targets that are more suited to the desired QoE at the application layer of UEs. Some of the main obstacles to enabling this will now be described.

[0010] Enabling the RAN to request the UE to send application layer performance measurements, e.g., QoE measurements, requires standardization, which is a long and difficult process in practice. Companies engaged in standardization, where the decisions are made by consensus, have different interests, so reaching the agreements on standardizing application layer-related information, e.g., RVQoE measurements, is generally difficult. So, in general, there is a need to enable service-specific, application layer QoE visibility in the RAN inorder to optimize the RAN QoS targets for those services without going through the standardization “bottlenecks”.

[0011] QoE-related information exchanged today between the application servers and the application clients on the UEs is transparent to the RAN / communication network, i.e., the RAN carries that information as UP traffic, and it has no visibility of the QoE-related information. The application servers may be incentivized to expose the QoE-related information back to the communication network / RAN, but as of today, such information would need to “travel” from the UE, transparently via the RAN and the core network of the communication network, to the application server somewhere on the Internet, and then back to the RAN. Consequently, due to excessive delay incurred by such a long path, the QoE information may be obsolete by the time it reaches back to the gNB where the UE is being served at a specific QoS level.

[0012] Different services / applications may have different ways of classifying a good QoE for the end-users and the QoS parameters that are important for that service to experience good QoE. In general, the application providing the service could determine better which QoS parameter may need to be optimized to affect the service QoE observed by the end-user. The RAN may not be able perform QoE-to-QoS mapping on a per-application basis without a full understanding of the application context. On the other hand, certain applications, such as, e.g., YouTube®, have global spread and are installed on nearly every smartphone in the world. Consequently, the possibility to optimize the QoE of such applications would impact enormous number of UEs and their end-users.

[0013] The QoE optimization performed over the top by the application servers and application clients, e.g., changing streaming resolution for video streams, is performed in complete incognizance of the capabilities in the RAN e.g., QoS settings available in the RAN / Network or possibilities in the RAN to maintain better QoE at the same application layer settings that could avoid such application layer adaptations or compromises. In other words, although both the application server and the RAN may have the tools to counteract QoE deterioration, as of today, there is no possibility forthem to cooperate in maintaining the desired QoE.

[0014] The currently standardized framework for QoE and RVQoE measurements is limited to only a few service types, where a service type represents a generic grouping of user services. For instance, a standardized service type for which QoE and / or RVQoE measurements can be collected is “Dynamic Adaptive Streaming over HTTP (DASH) streaming”. Standardization of QoE measurement support for additional service types in standardization takes very long time, and the current set of service types for which QoE measurements are supported is limited to applications used by humans.

[0015] As shown, there is a need of a way for improving handling of applications in a communication network in terms of handling QoE measurements and acting on performed QoE measurements.SUMMARY

[0016] It is an object of embodiments of the invention to address at least some of the problems and issues outlined above. It is an object of embodiments of the invention to provide a handling of applications in a communication network that results in improved QoE for an end-user of a UE that uses the application. It is possible to achieve at least of one of these objects by using methods, applicationspecific network entities, UEs and systems as defined in the attached independent claims.

[0017] According to one aspect, a method is provided that is performed by an application-specific network entity for handling of at least one application of the service type in a communication network, the at least one application being provided by an application server. Further, the communication network comprises a RAN. The method comprises obtaining, from a UE having a connection to the RAN, application layer-related information on a number of sessions on the UE of the at least one application handled by the application-specific network entity, and obtaining, from at least one of a network node of the RAN or the UE, radio-related information related to the connection between the UE and the RAN. The method further comprises determining, based on the obtained application layer-related information and the obtained radio-related information, an action for the RANand / or for the at least one application for improving QoE of any of the number of sessions on the UE of the at least one application. The method further comprises, when the determined action included an action for the RAN, sending, to the RAN, information on the determined action for the RAN, and when the determined action included an action for the at least one application, sending, to the application server or to the UE, information on the determined action for the at least one application.

[0018] According to another aspect, a method is provided that is performed by a UE connected to a RAN of a communication network. The method comprises obtaining application layer-related information for a number of sessions of at least one application executing on the UE and handled in the communication network by an application-specific network entity. The method further comprises sending the application layer-related information to the application-specific network entity, and receiving action information on an action for the number of sessions for the at least one application when the application-specific network entity determined, based on the sent application layer-related information, that such an action is required in order to improve QoE of the number of sessions of the at least one application at the UE, the action information originating from the applicationspecific network entity.

[0019] According to another aspect, a application-specific network entity is provided that is configured to operate in a communication network, and configured for handling of at least one application in the communication network. The at least one application is provided by an application server. The communication network comprises a RAN. The application-specific network entity comprises processing circuitry and memory. Said memory contains instructions executable by said processing circuitry, whereby the application-specific network entity is operative for obtaining, from a UE having a connection to the RAN, application layer-related information on a number of sessions on the UE of the at least one application handled by the application-specific network entity, and obtaining, from at least one of a network node of the RAN or the UE, radio-related information related to the connection between the UE and the RAN. The application-specific network entityis further operative for determining, based on the obtained application layer-related information and the obtained radio-related information, an action for the RAN and / or for the at least one application for improving QoE of the number of sessions on the UE of the at least one application, and when the determined action included an action for the RAN, sending, to the RAN, information on the determined action for the RAN, and when the determined action included an action for the at least one application, sending, to the application server or to the UE, information on the determined action for the at least one application.

[0020] According to another aspect, a UE is provided that is configured for connection to a RAN of a communication network. The UE comprises processing circuitry and memory. Said memory contains instructions executable by said processing circuitry, whereby the UE is operative for obtaining application layer-related information for a number of sessions of at least one application executing on the UE and handled in the communication network by an application-specific network entity, and sending the application layer-related information to the application-specific network entity. The UE is further operative for receiving action information on an action for the number of sessions for the at least one application when the application-specific network entity determined, based on the sent application layer-related information, that such an action is required in order to improve QoE of the number of sessions of the at least one application at the UE, the action information originating from the application-specific network entity .

[0021] According to another aspect, a system is provided that is configured for handling of at least one application in a communication network comprising a RAN, the at least one application being provided by an application server. The system comprises a UE configured for connection to the RAN and an applicationspecific network entity of the communication network for handling of the at least one application in the communication network. The UE is operative for obtaining application layer-related information for a number of sessions of the at least one application executing on the UE, and sending the application layer-related information to the application-specific network entity. The application-specific network entity is operative for obtaining the application layer-related informationfrom the UE and obtaining, from at least one of a network node of the RAN or the UE, radio-related information related to the connection between the UE and the RAN. The application-specific network entity is further operative for determining, based on the obtained application layer-related information and the obtained radiorelated information, an action for the RAN and / or for the at least one application for improving QoE of the number of sessions on the UE of the at least one application, and when the determined action included an action for the RAN, sending, to the RAN, information on the determined action for the RAN, and when the determined action included an action for the at least one application, sending, to the application server or to the UE, information on the determined action for the at least one application

[0022] According to other aspects, computer programs and carriers are also provided, the details of which will be described in the claims and the detailed description.

[0023] Further possible features and benefits of this solution will become apparent from the detailed description below.BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The solution will now be described in more detail by means of exemplary embodiments and with reference to the accompanying drawings, in which:

[0025] Fig. 1 is a schematic block diagram of control plane and user plane communications according to prior art.

[0026] Fig. 2 is a schematic diagram of a wireless communication network in which the present invention may be used.

[0027] Fig. 3 is a flow chart illustrating a method performed by a applicationspecific network entity, according to possible embodiments.

[0028] Fig. 4 is a flow chart illustrating a method performed by a UE, according to possible embodiments.

[0029] Fig. 5 is a block diagram of the O-RAN architecture, in which the present invention may be implemented.

[0030] Fig. 6 is a block diagram of the Near-RT RIC of fig. 5 in more detail.

[0031] Fig. 7 is a schematic block diagram of control plane communications according to possible embodiments.

[0032] Fig. 8 is a signaling diagram according to possible embodiments.

[0033] Fig. 9 is another signaling diagram according to other possible embodiments.

[0034] Fig. 10 is a block diagram illustrating a application-specific network entity in more detail, according to further possible embodiments.

[0035] Fig. 11 is a block diagram illustrating a UE in more detail, according to further possible embodiments.DETAILED DESCRIPTION

[0036] In this disclosure, the terms “service” and “application” are equivalent terms meaning an application provided by an application server to UEs in a communication network. The UEs using the application has downloaded an application client / client software for the application in order to use the application.

[0037] The term “service type” is a superset of term “application / service”. For example, streaming can be a service type, while YouTube® are Netflix® are examples of applications of the service type streaming.

[0038] The terms “server” and “application server” are regarded as equivalent. Further, the terms “E2 node” and “RAN node” are regarded as equivalent.

[0039] Fig. 2 shows a communication network 100 in which the present invention may be used. The communication network 100 comprises a radio access network (RAN) 130 having RAN nodes 132, 134. In embodiments, the RAN 130 may be an Open RAN (O-RAN). The RAN nodes 132, 134 are in, or adapted for,wireless communication with a wireless communication device aka wireless device, aka UE 140. The RAN nodes each provide radio access in a respective cell covering a geographic area. In fig. 2, this is exemplified by the RAN node 132 providing radio access in cell 145.

[0040] The communication network 100 may be any kind of communication network that can provide radio access to UEs. Example of such communication networks are networks based on Global System for Mobile communication (GSM), Enhanced Data Rates for GSM Evolution (EDGE), Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA 2000), Long Term Evolution (LTE), LTE Advanced, Wireless Local Area Networks (WLAN), Worldwide Interoperability for Microwave Access (WiMAX), WiMAX Advanced, as well as fifth generation (5G) communication networks based on technology such as New Radio (NR), and any possible future sixth generation (6G) communication network.

[0041] The RAN nodes 132, 134 may be any kind of network node that can provide wireless access to a UE 140 alone or in combination with another network node. Examples of RAN nodes 132, 134 are a base station (BS), a radio BS, a base transceiver station, a BS controller, a network controller, a Node B (NB), an evolved Node B (eNB), a gNodeB (gNB), a Multi-cell / multicast Coordination Entity, a relay node, an access point (AP), a radio AP, a remote radio unit (RRU), a remote radio head (RRH), a multi-standard BS (MSR BS), a WLAN Access Point (AP), a router, a Bluetooth AP, etc.

[0042] The wireless device 140 may be any type of device capable of communicating with a RAN node 132, 134 using radio signals. For example, the wireless device 140 may be a User Equipment (UE), a machine type UE or a UE capable of machine to machine (M2M) communication, a sensor, a tablet, a mobile terminal, a smart phone, a laptop embedded equipped (LEE), a laptop mounted equipment (LME), a USB dongle, a Customer Premises Equipment (CPE), an Internet of Things (loT) device, etc.

[0043] The communication network 100 further comprises an application server 150 for providing at least one application to UEs 140 connected to the communication network 100. According to an embodiment, for using the application provided by the application server 150, the UEs each has implemented / downloaded an application client with the ability to communicate with the application server 150 to execute the application. The application server 150 may reside outside the communication network 100, for example at the application developer. Alternatively, the application server 150 may be situated inside the communication network 100, e.g., running on a computing platform offered by the communication network e.g., Mobile Edge Computing. However, the application server 150 is normally not controlled by the communication network 100 in terms of how it handles its application(s) for the application clients on the UEs.

[0044] According to embodiments, there is also provided a new type of network entity called an application-specific network entity 160; 170. The applicationspecific network entity 160, 170 is an entity residing in the communication network 100 or connected to the communication network 100. The applicationspecific network entity 160, 170 is arranged to handle a specific application in the communication network.. Such an application-specific network entity 160, 170 may in some embodiments be developed by the application developer of that specific application, i.e. the same developer, or development organization, develops both the application and the application-specific network entity of the same application. In embodiments, the application-specific network entity is specific for one or more applications of one and the same service type. In O-RAN, an application-specific network entity may be called an application-specific xAPP. The application-specific entity / xAPP knows better what the application needs, e.g., in terms of data rate and maximum delay, for the application to provide good QoE to an end-user of a UE than a node in the communication network 100 that may be used for all applications. The application-specific entity / xAPP may have access to both network related QoS / QoE and to over-the-top (OTT) information. The application-specific xAPP may be implemented in a Near-Real Time RAN Intelligent Controller (Near-RT RIC).

[0045] The application-specific network entity 160 may be realized at or in one of the RAN nodes 132, 134. Alternatively, the application-specific network entity 160 may be arranged at or in any other network node of the communication network 100. Alternatively, the application-specific network entity 170 may be realized as a group of network nodes or functions, wherein functionality of the application-specific network entity 170 is spread out over the group of network nodes / functions. The group of network nodes / functions may be different physical, or virtual, nodes of the network. The application-specific network entity 170 may be arranged in a cloud network 175.

[0046] Fig. 3 shows, in conjunction with fig. 2, a method performed by an application-specific network entity 160; 170 for handling of at least one application in a communication network 100, the at least one application being provided by an application server 150. Further, the communication network 100 comprises a RAN 130. The method comprises obtaining 204, from a UE 140 having a connection to the RAN 130, application layer-related information on a number of sessions on the UE of the at least one application handled by the application-specific network entity 160; 170, and obtaining 206, from at least one of a network node 132 of the RAN 130 or the UE 140, radio-related information related to the connection between the UE 140 and the RAN 130. The method further comprises determining 210, based on the obtained application layer-related information and the obtained radio-related information, an action for the RAN 130 and / or for the at least one application for improving Quality of Experience, QoE, of any of the number of sessions on the UE of the at least one application. The method further comprises, when the determined action included an action for the RAN 130, sending 212, to the RAN 130, information on the determined action for the RAN 130, and when the determined action included an action for the at least one application, sending 214, to the application server 150 or to the UE 140, information on the determined action for the at least one application.

[0047] The application layer-related information may comprise application layer measurements performed by the UE on the number of sessions of the at least one application and / or other application layer-related information that relates tothe number of sessions of the at least one application. The application layer-related information may be QoE measurements. The application layer-related information may be one or more of Round-trip delay, jitter, application layer buffer state, codec used by the session, number of representation switches, resolution, and application ID, etc. The application layer-related information obtained from the UE 140 can be application-specific / proprietary, or the information can be some already standardized information and / or new metrics. The application layer-related information may be application layer information. The application layer-related information may be one or more of: proprietary application specific information, standardized application specific information, proprietary service type specific information, standardized service type specific information, proprietary service / application type agnostic information, standardized service / application type agnostic information.

[0048] The application layer-related information may be sent from the UE via the RAN to the application-specific network entity. The application-layer information may or may not be visible to or understood by the RAN when being sent via the RAN. For example, proprietary application layer-related information may be sent so that it is not visible to the RAN. The visibility may be achieved by tunneling of the information from UE to the application-specific network entity

[0049] Radio-related information comprises one or more of radio-related measurements for the connection between the UE 140 and the RAN 130, information on radio resource utilization for radio resources available for the connection between the UE 140 and the RAN 130, and configuration of the RAN 130. Example of radio-related information are modulation and coding scheme (MCS) used, QoS related parameters such as signal strength, Signal to Noise Ratio (SNR), Signal to Interference and Noise Ratio (SINR), Reference Signal Received Power (RSRP) etc. of signals transmitted between the UE and the RAN 130. The radio-related measurements could be determined for the RAN node 132 that handles the UE 140 but also for other RAN nodes, e.g., neighbors to the RAN node 132, and for the transport network in the RAN, such as Fronthaul, backhaul etc. Other examples of radio-related information areallocated Physical Resource Blocks (PRB), radio configuration information and information about other radio conditions and RAN state, and even UE hardware information, such as UE model, chipset model, etc., and UE software information, such as operating system, e.g. Android® version, application version, etc. According to embodiments, the radio-related information may be called radio-layer related information or Access Stratum (AS) layer related information. The radio-related information may refer to any radio information of any layer of the 3GPP stack of the Uu interface, as defined in e.g. TS 38.300 V18.3.0 (2024-09).

[0050] The action for the RAN 130 and / or for the application for improving QoE at the UE 140 could be for example a configuration change, e.g., to use a different value for a parameter or a control command from the RAN node 132 to the UE 140, i.e. to switch from using A to using B, such as to handover the UE from cell A to cell B. Other examples of actions are allocating additional resources for the UE, changing the treatment of the UE, coordination with the application server or with the application layer at the UE.

[0051] The information on the determined action for the RAN 130 may be a recommendation for the RAN to perform the determined action or alternatively a command for the RAN 130 to perform the determined action. The information on the determined action for the application may be a recommendation for the UE 140 or for the application server 150 to perform the determined action or alternatively a command for the UE 140 or for the application server 150 to perform the determined action.

[0052] By implementing such a method performed by a application-specific network entity 160, 170 of the communication network, the entity can rather fast get hold of current data relevant for QoE from the application server or the UE and of current data relevant for QoS in the communication network from the RAN, and take actions on them to improve QoE of the application at the UE. Using an application-specific network entity instead of a general entity of the communication network improves the possibility of getting relevant application layer-related data from the one or more application as the application-specific network entity isspecialized on this one or more application. Further, with such a method, a solution is provided that can be proprietary, i.e. it can handle information, such as application layer-related information of the application that is specific for this specific application, whereby most relevant data of the application can be received. Further, the communication of application layer-related information for the application to the application-specific network entity will function smoothly without any necessary standardization agreement. Further, hereby, the RAN and the application server can cooperate in providing a desired QoE for the application provided by the application server.

[0053] According to an embodiment, the method further comprises sending 202, to the UE 140, an instruction to send, to the application-specific network entity 160; 170, the application layer-related information for the number of sessions on the UE 140 of the at least one application handled by the application-specific network entity 160; 170. Hereby, the entity 160; 170 can provide the UE with instructions of current interest, i.e., when such application layer-relation information are of interest.

[0054] Such an instruction may be sent 202 by the application-specific network entity 160; 170 in a command not only for a single UE but also for a group of UEs, wherein a “group” can be either explicitly listed UEs or it can be UEs with some common property, such as “all UEs served by the RAN that are pursuing a streaming session”, or “all streaming sessions of all UEs served by this RAN node”. The instruction can be sent by the application-specific network entity 160: 170 directly to the UE 140 or the application-specific network entity 160; 170 can ask the RAN 130 to send the instruction to the UE 140. The instruction can further comprise an instruction to the UE 140 to perform application layer-related measurements for the at least one application, in case the UE 140 is not already instructed to perform such measurements. This can both pertain to an ongoing measurement performed by the UE 140, or the instruction can trigger the UE 140 to perform a new measurement. An alternative to the application-specific network entity 160; 170 sending the instruction is that the application server 150 instructs the UE 140, forexamplewhen the application is installed at the UE 140.

[0055] According to an embodiment, the instruction sent 202 to the UE 140 comprises information on a triggering condition for obtaining the application layer-related information for the number of sessions of the at least one application. By sending information on a triggering condition for at which events or when to obtain application layer-related information, the UE would know when to report to the application-specific network entity, whereby unnecessary reporting can be avoided. Such a triggering condition may be the occurrence of certain events in the communication network, such as a handover of the UE from one network node to another network node. In other words, the instruction may be for the UE to obtain the application layer-related information upon the occurrence of such an event. Another example of event is when the application layer-related information meets an information condition, such as a certain QoS value. Such information conditions are described in more detail further down in this disclosure.

[0056] According to another embodiment, the method further comprises obtaining 208, from the application server 150, second application layer-related information on the number of sessions on the UE 140 of the at least one application handled by the application-specific network entity 160; 170. Further, the determining 210 of an action for the RAN 130 and / or for the at least one application for improving the QoE of the at least one application is further based on the second application layer-related information. The second application layer-related information are from the perspective of the application server 150 whereas the application layer-related information obtained from the UE are from the UE perspective of the communication between the UE and the application server for the same number of sessions for the at least one application. By also taking into consideration application layer-related information from the application server gives a better estimate of the information and, consequently, a better supported determined action.

[0057] According to yet another embodiment, the method further comprises, before the obtaining 204 of the application layer-related information from the UE 140, registering 201 the application-specific network entity 160, 170 at the communication network 100 as authorized to determine actions for the RAN 130and / or for the at least one application for improving the QoE of sessions of the at least one application for UEs in the communication network 100, including the UE 140. This is a coordination between the application-specific network entity 160; 170 and the communication network 100 so as to allow the application-specific network entity 160; 170 to obtain the application-specific information for a number of sessions for a certain UE 140, or for a group of UEs including the UE 140. The application-specific network entity 160; 170 may register itself, using e.g., a Near-RT RIC application programming interface (API), as a “service producer” for certain service-specific optimizations. According to an alternative, the application-specific network entity 160; 170 can try to fetch the application layer-related information without being sure that the information is available, i.e. in an unsolicited manner.

[0058] According to another embodiment, the method further comprises obtaining 203, from the application server 150, an instruction on how to perform the determining 210 of an action for the RAN 130 and / or for the at least one application for improving the QoE of the at least one application at the UE.

[0059] According to yet another embodiment, the method further comprises, when the determined 210 action included an action for the RAN 130 and after the information on the determined action for the RAN 130 was sent 212 to the RAN 130, receiving 216 from the RAN 130, information on whether the RAN has performed or will perform the determined action or not. Hereby, the RAN cannot just decide whether to implement the determined action, the application-specific network entity will also now whether the RAN implemented the action.

[0060] According to yet another embodiment, only when the application layer-related information obtained 204 from the UE 140 or when second application layer-related information obtained from the application server 150 meet an information condition, an action for the RAN 130 and / or for the at least one application for improving the QoE can be determined 210. Hereby, it is secured that actions are only triggered when needed. The information condition may be a threshold. The application layer-related information maybe QoE. An example of application layer-related information is data rate. If measured data rate is below adata rate threshold, an action is determined, if the measured data rate is above the data rate threshold, no action is determined. The threshold may be other application layer-related information such as delay, jitter, packet loss rate, retransmission rate. If the measured information is above the threshold, an action is determined, if below the threshold, no action is determined.

[0061] According to still another embodiment, the application layer-related information obtained 204 from the UE 140 is received from the UE 140 in one or more information elements (IE) of an application protocol and over an F1 , E1 , Xn or E2 communication interface.

[0062] According to still another embodiment, the RAN 130 is an O-RAN and the application-specific network entity 160, 170 is hosted on an O-RAN Near-RIC function / node.

[0063] According to an embodiment, the application-specific network entity 160, 170 informs one or more of the RAN 130, the application server 150 and UEs in the communication network including the UE 140, that the application-specific network entity 160, 170 is able to determine actions for the RAN 130 and / or for the at least one application for improving the QoE for sessions of the at least one application on the UEs in the communication network.

[0064] Fig. 4 in conjunction with fig. 2 describes a method performed by a UE 140 connected to a RAN 130 of a communication network 100. The method comprises obtaining 304 application layer-related information fora number of sessions of at least one application executing on the UE 140 and handled in the communication network 100 by an application-specific network entity 160; 170. The method further comprises sending 306 the application layer-related information to the application-specific network entity 160; 170, and receiving 308 action information on an action for the number of sessions for the at least one application when the application-specific network entity 160; 170 determined, based on the sent application layer-related information, that such an action is required in order to improve QoE of the number of sessions of the at least oneapplication at the UE 140, the action information originating from the applicationspecific network entity 160; 170.

[0065] According to an embodiment, the method further comprises receiving 310 from the RAN 130, an instruction of reconfiguration as a result of the application-specific network entity 160; 170 determining an action for the RAN 130 for improving QoE of the number of sessions on the UE 140 of the at least one application. The application-specific network entity 160; 170 sends the determined action to the RAN 130. The RAN 130 either follows the action or makes the decision itself whether to follow the determined action or not. When the RAN 130 follows / decides to follow the action, the RAN 130 takes the necessary action in the RAN according to the received action from the application-specific network entity and the sends the instruction of reconfiguration to the UE 140 in accordance with the actions taken by the RAN 130.

[0066] According to another embodiment, the method further comprises receiving 302, from the application-specific network entity 160; 170 or from an application server 150 providing the at least one application, an instruction to obtain the application layer-related information for the number of sessions of the at least one application executing on the UE 140 and to send the obtained application layer-related information to the application-specific network entity 160; 170.

[0067] According to an embodiment, the received 302 instruction to obtain the application layer-related information comprises information on a triggering condition for obtaining the application layer-related information for the number of sessions of the at least one application. Further, the application layer-related information is obtained 304 for the number of sessions of the at least one application when the triggering conditions are met.

[0068] According to yet another embodiment, the method further comprises sending 307, to the RAN 130, radio-related information related to the connection between the UE 140 and the RAN 130. Such information is then sent further by the RAN 130 to the application-specific network entity 160; 170.

[0069] According to yet another embodiment, the application layer-related information is sent 306 to the application-specific network entity 160; 170 in one or more information elements (IE) of an application protocol and over an F1 , E1 , Xn or E2 communication interface.

[0070] In the following, embodiments are described for enabling applicationspecific network entities in the O-RAN architecture, the network entities in the following being called xApps. In the O-RAN architecture (fig. 5), xApps are defined as third party applications for providing value-added functionality for RAN performance optimization, such as better traffic steering, better QoS management, etc. Even though the following embodiments are described for O-RAN, the invention is equally applicable to other RAN architectures.

[0071] Fig. 5 describes the O-RAN architecture. The O-RAN architecture comprises a service management and orchestration (SMO) function 402 having a Non-Real-Time RAN Intelligent Controller (Non-RT RIC) function 404 and a Near-RT RIC function 406. The Non-RT RIC function 404 is connected to the Near-RT RIC over an A1 interface. The O-RAN architecture further comprises a number of different network nodes for handling communication with UEs, the network nodes being called E2 nodes in O-RAN. The E2 nodes comprises one or more O-RAN eNodeB (O-eNB) 408, O-RAN Central Unit - Control Plane (O-CU-CP) 410, O-RAN Central Unit - User Plane (O-CU-UP) 412, O-RAN Distributed Unit (O-DU) 414 and O-RAN Radio Unit (O-RU) 416. The O-eNB 408, the O-CU-CP 410, the O-CU-UP 412 and the O-DU 414 are all connected to the near-RT RIC 406 over E2 interfaces. The O-CU-UP 412 is connected to the O-CU-UP 410 over an E1 interface. The O-CU-UP 410 is connected to the O-DU 414 over a 3GPP F1 control plane (F1-c) interface. The O-CU-UP 412 is connected to the O-DU over a 3GPP F1 user plane (F1-u) interface. Further, the O-eNB 408 is connected to the SMO function 402 over an 01 interface. The O-RU 416 is connected to the O-DU 414 over an Open Fronthaul (FH) Control User Synchronization (CUS) plane (Open FM CUS-plane) and an Open Fronthaul Management plane (Open FM M-plane). The O-RU 416 is further connected to the SMO function 402 over an Open FM M-plane. The O-RAN architecturefurther comprises an O-Cloud 418 which is connected to the SMO function 402 over an 02 interface. Further, the O-RAN architecture has a Y1 interface over which Y1 Consumers 420 are connected to the Near-RT RIC 406. A Y1 consumer may be for example an application server. Further, the O-DU 414, the O-CU-CP 410, the O-CU-UP 412 and the Near-RT RIC 406 are all connected to the SMO 402 over the 01 interface. Further, the O-CU-CP 410 and the O-CU-UP 412 are connected to 3GPP-based network nodes via 3GPP interfaces X2-c, X2-u, NG-c, NG-u, Xn-c, X-u.

[0072] In some embodiments, the application-specific xApps are hosted on the Near-RT RIC 406. In some embodiments, the application-specific xApps on the Near-RT RIC 406 use the E2 interface to trigger / notify the UEs via E2 nodes, i.e. , the O-CU-CP 410, O-CU-UP 412, O-DU 414 and O-eNB 408, to send applicationspecific, application layer information, e.g., QoE measurements, to the servicespecific xApps transparently over one or more of the F1 , E1 , Xn, E2 and Uu interfaces, wherein the Uu-interface is thre wireless interface between the UE and a node of the RAN, for an O-RAN for example the O-eNB 408 or the O-RU 416. In other words, one application-specific xApp instructs a UE that executes or has launched the application of the application-specific xApp to send application layer-related information such as QoS information of the application to the service specific xApp. The application-specific application layer information may be sent to the application-specific xApp in dedicated F1, E1, Xn, E2 and RRC information element (IE) containers. These lEs may only be parsed or understood by the dedicated application-specific xApp on the Near-RT RIC 406. The applicationspecific xApp may then analyze the real-time application layer information coming from the UE. Also, the application-specific xAPP obtains from the RAN, radiorelated information related to the connection between the UE and the RAN such as one or more of information about the RAN state, radio resource utilization and configurations coming from the E2 nodes. Based on the application-specific application layer information and the radio-layer related information the application-specific xApps may determine one or more of the following actions to be performed: Use O-RAN standardized E2 service models to control or reconfigure the E2 nodes in order to improve the observed QoE of the applicationat the UE application layer; Use enhanced E2, F1 , E1, Xn and Uu interface features to request the UE to adapt / modify its application layer settings to better suit the real-time conditions and constraints of the RAN; Coordinate with the application server providing the application of the application-specific x-App for possible configuration adaptations for the application sessions.

[0073] According to an embodiment, the service-specific xApps may use Artificial Intelligence / Machine Learning (AI / ML) based algorithms to generate the required insights to perform one or more of the above actions or others described in this disclosure.

[0074] Fig. 6 shows the O-RAN Near-RT RIC 406 of fig. 5 in more detail and according to embodiments. Also, the connection between the Near-RT RIC 406 and the SMO 402 via 01 and A1 interfaces as well as the connection to Y1 consumers 420 via the Y1 interface are shown as well as the connection between the Near-RT RIC 406 and the E2 nodes 408, 410, 412, 414 over the E2 interface. The near-RT RIC 406 comprises the application-specific xApps 431 , 432, 433 and a Near-RT RIC platform 440. The xApps communicate with the Near-RT RIC platform 440 via Near-RT RIC Application Programming Interfaces (API). The Near-RT RIC platform 440 may further comprise an 01 termination unit 441 handling communication over the 01 interface to the SMO 402 and an A1 termination unit 442 handling communication over the A1 interface to the Non-RT RIC 404 of the SMO 402. The Near-RT RIC platform 440 may further comprise an AI-ML support for supporting possible AI-ML handling of data and an API enablement unit 444 for handling the APIs. The Near-RT RIC platform 440 may further comprise an xApp repository 445 for storing the xApps 431 , 432, 433 and an Y1 termination unit 446 for handling communication over the Y1 interface to theY1 consumers 420. The Near-RT RIC platform 440 may further comprise messaging infrastructure 447, a shared data layer 448 and a database 449. The Near-RT RIC platform 440 may further comprise one or more of xApp subscription management 450 for handling subscriptions of applications, a conflict mitigation unit 451 , a security unit 452, management unit 453 andeventually an E2 termination unit 454 for handling communication with the E2 nodes 408, 410, 412, 414 over the E2 interface.

[0075] According to embodiment, the xApps 431 , 432, 433 use the services offered by the E2 interface using E2 application protocol (E2AP) to control the functionality of the RAN nodes, i.e., O-CU-CP 410, O-CU-UP 412, O-DU 414, etc., for the said RAN performance optimization. xApps 431 , 432, 433 interact with the Near-RT RIC platform 440 using Near-RT RIC APIs, and they run as cloud-native applications on the O-RAN defined O-Cloud platform 418.

[0076] As shown, the Near-RT RIC 406 can host the proposed applicationspecific xApps 431 , 432, 433. Hosted on the Near-RT RIC 406, these xApps 431 , 432, 433 can, for its respective specific application: Fetch or obtain real-time application layer information from the corresponding application client on the UEs; Obtain real-time radio-related information from the E2 nodes, such as RAN status information, radio resource utilization, and configurations, and, using the E2 interface, effectuate necessary adaptations or reconfigurations in the RAN and the corresponding UE application to ensure the right level of QoE for the end users of UEs using the corresponding application, taking the above information on application layer information for the specific application and the real-time radiorelated information into account.

[0077] Fig. 7 shows an example of possible interactions according to embodiments between an application-specific xApp 501 and different actors, i.e. application server 502, gNodeB 503, and application client 504 for the specific application downloaded onto UE 505. It is anticipated that the service-specific xApp 501 has different logical control plane (CP) interfaces with: The application server(s) 502 located outside of the RAN / communication network; The RAN nodes, e.g., O-RAN E2 nodes, gNodeB 503, and The application clients’ 504 software on the UE 505. The above-mentioned interfaces are depicted in fig. 7 as arrows 1, 2, and 5, respectively. Similarly, it is anticipated for the RAN / E2 nodes e.g. the gNodeB 503, to have the traditional RAN CP interfaces with the UEs 505, arrow 3, e.g., the RRC, which RAN CP interfaces are used, for example, to control the UE QoS in the RAN. Lastly, the application client 504 will have a logical UPand CP connection with the application server 502 (arrow 4) for end-user service and application layer adaptations. In the following, fig. 7 and its depicted logical interfaces will be to explain embodiments of the invention in the context of the O-RAN architecture.

[0078] The proposed application-specific xApp 501 may, as discussed, be deployed by network operators on certain Near-RT RIC(s) 406 in the RAN. Upon deployment, such an application-specific xApp 501 may register itself, using Near-RT RIC APIs interface, as a “service producer” for certain service-specific optimizations. In some embodiments, the registration may also pertain to more than one application whose optimization the application-specific xApp 501 supports. In some cases, where the application-specific xApp 501 can optimize more than one application, either one registration can pertain to more than one application, or the registration for each application is done individually. In the registration, the application(s) whose optimization the application-specific xApp supports may be identified with dedicated identifier(s).

[0079] The service the application-specific xApp 501 produces may be exposed to the application server 502 as depicted with arrow 1 in fig. 7, to establish a logical control plane interface between the application-specific xApp 501 and the application server 502. This exposure of application-specific xApp service towards the application server 502 pertaining to this application may be performed over the O-RAN Y1 interface from the Near-RT RIC platform 440. The interactions over the interface depicted with arrow 1 in fig. 7 between the application server 502 and the application-specific xApp 501 may be proprietary with the request / response interactions between the application-specific xApp 501 and application service visible to the Near-RT RIC platform 440, but the actual information exchanged as part of those interactions may be visible to the endpoints only. The applicationspecific xApp 501 may also establish a logical control plane interface with the RAN / E2 nodes, e.g. gNodeB 503, (arrow 2) using the E2 interface as defined in O-RAN E2AP specification.

[0080] According to embodiment, it is proposed that the application-specific xApp 501 establishes a logical control plane interface with the application client software 504 (arrow 5) using O-RAN E2 and RAN interfaces, e.g., F1, O-FH, Uu.

[0081] Fig. 8 shows a signal diagram of signals sent between the applicationspecific xApp 501, e2 Nodes (e.g. gNodeB 503), Application client 504 / UE 505 and application server 502 according to embodiments. Using e.g., the logical CP interfaces defined above between the application-specific xApp 501, E2 nodes 503 and the application client 504 / UE 505, the application-specific xApp 501 may gather RAN information, UE information, and client application layer information as follows: The application-specific xApp 501 may, using e.g., O-RAN defined E2AP interface and E2 service models (E2SM) such as E2SM-RC, get / obtain (arrow 1 in fig. 8) configuration information of E2 nodes from the E2 nodes 503, such as configured RAN slices, Physical Resource Block (PRB) quota & allocation, bearer information, QoS flows to bearer mapping etc. Using the same logical CP interface, the application-specific xApp 501 may also get / obtain (arrow 2 in fig. 8) UE specific information from the E2 nodes 503, such as UE-IDs, UE group assignments etc.

[0082] Further, the application-specific xApp 501 may, using enhancements to existing E2SMs, or using new O-RAN defined E2SMs, or using proprietary E2SMs, get / obtain (according to arrows 2-5 in fig. 8) application layer information from the UEs, such as application layer buffers status, video resolution, Audio / Video codecs etc. A request for application layer information may be sent from the xApp 501 to the e2nodes 503 (arrow 2) and further from the e2nodes 503 to the application client 504 on the UE 505 (arrow 3). A response with such application layer information may be sent by the application client 504 on the UE 505 to the e2nodes 503 (arrow 4) and further from the e2nodes 503 to the application-specific xApp 501 (arrow 5). The collected information may also include QoE / RVQoE measurement results of such measurements performed at the UE. E2AP and / or E2SMs enhancements may be needed to trigger an E2 node 503 to send proprietary, service-specific information to the application clients / UEs. Additionally, enhancement to 3GPP defined RAN interfaces such as F1, E1, Xn,and / or CP functionality e.g., RRC may be needed to transport lEs populated by service-specific xApp and sent to the application client software in the UE devices.

[0083] Further, the application-specific xApp 501 may, using the logical CP or UP interface, gather hardware / software information-specific for the UE I mobile terminal / operating system on which the application is or may be executed. The application-specific xApp 501 may also collect radio-related measurement results, e.g., Minimization of Drive Testing (MDT) measurements or signal strength measurements, from the E2 nodes 503 and / or the UE 505.

[0084] Also, the application-specific xApp 501 may, using Y1 interface, interact with and collect from, or expose information to, the application server 502. The collected information may include application-layer information, including, e.g., server-side configuration settings for the service, QoE measurement results, e.g., uplink QoE measurement results. This is depicted with arrow 6 in fig. 8.

[0085] Using the information gathered from the above listed sources and means, the application-specific xApp 501 analyze (point 7) the obtained information, including radio-related information and application layer-related information and determine actions for the RAN or for the application to improve QoE at the UE 505 for the application handled by the applications-specific xApp 501. The applications-specific xApp 501 can apply service-specific optimization algorithms to identify or generate the necessary actions or updates for the RAN, such as identifying updating configurations or control actions for the RAN, i.e., E2 nodes, and / or to identify or generate actions, e.g. updates to the application in the UE 505 or application server 506. One example could be the use of AI / ML algorithms to predict the real-time QoE of the service, based on the real-time data collected and to trigger necessary remedy actions in case of measured unsatisfactory QoE or predicted unsatisfactory QoE.

[0086] In some embodiments, the applications-specific xApp 501 may collect QoE related information and / or RVQoE related information from the application client 504 in the UE 505, even though the RAN has not configured the UE 505 to perform any QoE measurements and / or RVQoE measurements. The applications-specific xApp 501 could thus leverage QoE / RVQoE functionality independently of the legacy QoE / RVQoE mechanisms, e.g. without depending on the RAN or the Operations and Maintenance (OAM) system, although the 0AM system may be involved in configuring the xApp.

[0087] In some embodiments, the applications-specific xApp 501 that controls the QoE / RVQoE can use the same QoE / RVQoE metrics that have been specified by 3GPP for QoE and / or RVQoE measurements. In some other embodiments, the applications-specific xApp 501 that controls the QoE / RVQoE can use metrics that have been defined elsewhere or through other means, e.g., by an application developer and / or a developer of the xApp, i.e., application- or service-specific metrics. These metrics may or may not have some metrics in common with the metrics that 3GPP has specified. In some cases, the applications-specific xApp 501 and the UE client 504 application may coordinate on which metrics are to be collected. In some embodiments, information other than QoE / RVQoE metrics, e.g., various QoE-related information, e.g., information on compression and decompression (coded) algorithms used for streaming of audio / video streams, can be collected.

[0088] In some embodiments, the applications-specific xApp 501 can configure the application, e.g., the application client 504 in the UE 505, to perform QoE / RVQoE measurements, or other measurements or data collection that may reflect the Quality of Experience, using a communication protocol or an API between the applications-specific xApp 501 and the application. When the applications-specific xApp 501 configures the application to perform QoE / RVQoE measurements and / or data collection, the applications-specific xApp 501 may also configure the application, e.g. application client 504, in the UE 505 to report the result of the QoE / RVQoE measurements and / or data collection to the applications-specific xApp 501. Alternatively, the applications-specific xApp 501 may retrieve the result of the QoE / RVQoE measurements and / or data collection, which the UE 505 has logged, e.g. in the application, e.g. the application client 504, in the UE 505, or in the application layer in the UE 505, or in the UE radio layer, i.e., the UE Access Stratum (AS) using explicit requests sent to the UE 505, e.g. to theapplication, e.g. application client 504, in the UE 505, onto the application layer in the UE, or to the UE AS.

[0089] In one embodiment, the applications-specificxApp 501 is configured, e.g., from the SMO, with per-application QoE / RVQoE threshold(s). For instance, the applications-specificxApp 501 is configured with a value / degree of QoE that is considered to be a minimum satisfactory QoE / RVQoE level, and / or with a value / degree of QoE / RVQoE that is considered sufficient to fulfill a service level agreement, and / or with a value / degree of QoE / RVQoE that is considered as a warning QoE / RVQoE level below which adjustment(s) at RAN and / or at application layer is / are needed. The applications-specificxApp 501 can also or alternatively be configured with a per application mapping between QoE / RVQoE metric(s) and QoS parameters, so that, based on, e.g., QoS measurements, the applications-specific xApp 501 can estimate and / or predict QoE.

[0090] In one embodiment, the applications-specificxApp 501 can configure the application, e.g., the application client 504 in the UE 505, with triggering conditions for starting and / or ending QoE / RVQoE measurements. For example, the applications-specificxApp 501 can configure the application client 504 in the UE 505, to start or end executing QoE / RVQoE measurements just before or upon certain events in the network, such as, e.g., the handover of the UE 505 in question. Another example is that the UE 505 stops measuring and reporting, or only reporting, upon the indicated event. In another embodiment, the applications-specificxApp 501 uses per-application QoE / RVQoE threshold(s) it has been configured with, and / or a per application mapping between QoE / RVQoE and QoS it has been configured with, to trigger RAN configuration / control for QoE optimization. So, when the QoE / RVQoE drops below a certain threshold, the UE 505 starts performing QoE / RVQoE measurements.

[0091] In one embodiment, the applications-specificxApp 501 becomes aware of the possibility for collecting static or semi-static application layer information from the UE 505 when the end-user of the UE triggers the execution of the application. For instance, when the UE 505 requests a Packet Data Unit (PDU) Session Establishment or a PDU Session Modification, the E2 node informs theNear RT RIC that a session is being established for the UE, and the applications-specificxApp 501 initiates the steps 2-5 in fig. 8.

[0092] In another embodiment, the applications-specificxApp 501 initiates a subscription towards the UE 505, or part of the UE, such as the operating system, requesting the UE 505 to provide the applications-specificxApp 501 an indication, indicating whether / when the application(s) / service(s) the applications-specific xApp 501 is interested in, is executed, or whose execution is being started, in the UE 505. Once the applications-specificxApp 501 receives the indication, it initiates the steps 2-5 shown in fig.8.

[0093] In the following, embodiments for application-specific xApp-triggered RAN configuration / control forQoE optimization will be described. The O-RAN has defined a standardized set of E2 Service Model (E2SM) specifications that enable xApps to configure and control the RAN for certain functionalities, e.g., triggering UE handovers, QoS flow to Data Radio Bearer (DRB) mapping, slice PRB quota modification etc. The service model specifications are meant to fulfill the requirements of specific use cases such as traffic steering, QoS management, RAN slicing, etc., by providing RAN control and configuration capabilities to the xApps running on the Near-RT RIC platform. xApps can use the E2AP CONTROL and E2AP Policy services for this purpose.

[0094] Using the information gathered from the above-listed sources and means, an applications-specificxApp 501 can apply service-specific optimization algorithms to identify or generate the necessary configurations or control actions for the RAN, i.e. , E2 nodes, and / or to identify or generate updates to the application service in the UEs or in the application servers. One example could be the use of AI / ML algorithms to predict the real-time QoE of the service, based on the real-time data collected, and to trigger necessary remedy actions in case of measured unsatisfactory QoE or predicted unsatisfactory QoE.

[0095] According to embodiments, it is anticipated, as one possibility, the same E2 service model approach used by the application-specific xApps to control and / or reconfigure the RAN / E2 nodes to improve the QoE of the clientapplications. Which RAN control and / or configurations would be needed and whether the existing E2SMs provide those would depend on the specific service and use case. An application-specific xApp may selectively use the O-RAN specified E2SM services or proprietary E2SMs that may provide sophisticated monitoring and control capabilities.

[0096] Fig. 9 shows a signal diagram according to embodiments for executing RAN control and configuration using E2AP and E2SM specifications. When the application-specific xApp 501 has determined, based on the obtained application layer-related information and the obtained radio-related information, that an action for the RAN would be appropriate in order to improve QoE at the UE 505 for a session of the at least one application, the application-specific xApp 501 requests (arrow 1) the e2node 503 to perform the action. In case the action is to update the RAN configuration, and the RAN accepts the request, the RAN configuration is updated (box 2). The e2node 503 responds to the application-specific xApp 501 with an E2 service response (arrow 3) informing the application-specific xApp 501 whether the request was accepted or not. Thereafter, when the request was accepted, the UE 505 is treated (box 4) by the e2node 503 based on the requested action, e.g. according to the updated RAN configuration.

[0097] In some embodiments, the application-specific xApp 501 uses a variant f the above-described method to instruct the RAN to apply a certain QoS for one of the UE’s DRBs, e.g. a DRB which has no QoS associated with it, e.g. a default bearer, default DRB, or as another option, a DRB that has another QoS associated with it. In the latter case, the QoS associated with the DRB would be overridden by the QoS that the application-specific xApp 501 configures, optionally only better QoS than the one previously associated with the DRB may be configured this way. The application-specific xApp 501 may then also inform the application, e.g., the application client 504 in the UE 505 about the QoS the application-specific xApp 501 has instructed the RAN to associate with the DRB.

[0098] In some embodiments, the application-specific xApp 501 instructs, requests or recommends the RAN to do something, e.g. perform an action or apply a configuration with respect to the treatment of the UE 505 running orhosting the application the application-specific xApp 501 is associated with, or the treatment of the data flow(s) and / or DRB(s) used for the application’s communication, e.g. the communication between the application client 504 and the application server 502, and the RAN may respond with what it will do or what it has done. For instance, the RAN may confirm that it will do or has done as the application-specific xApp 501 instructed or requested or recommended.Alternatively, the RAN may inform the application-specific xApp 501 that the RAN rejects the instruction or request or recommendation from the application-specific xApp 501. Still alternatively, the RAN may inform the application-specific xApp 501 that the RAN will do, or has done, something different than the application-specific xApp 501 instructed or requested or recommended, e.g. a modification of what the application-specific xApp 501 instructed or requested or recommended, e.g. a partial fulfillment of the instruction or request or recommendation from the application-specific xApp 501, such as providing an improved QoS for the concerned data flow(s) and / or DRB(s) but not as good as the application-specific xApp 501 instructed or requested or recommended. The application-specific xApp 501 may then give suitable instruction to the application in the UE 505 based on what the RAN signaled that it would do or has done.

[0099] In some embodiments, different application-specific xApps may have different rights or authorizations with respect to what they are allowed to change in a RAN’s configuration or in the configuration or scheduling aspects the RAN uses towards a certain UE. The scope and / or restriction of what an application-specific xApp 501 is authorized to instruct or recommend or configure the RAN to do and / or what information the application-specific xApp 501 is authorized to retrieve from the RAN may be configured when the application-specific xApp 501 is installed. The authorization may for instance give the application-specific xApp 501 the right to configure certain aspects or parameters in a RAN, possibly within a certain range. As another example, an application-specific xApp 501 can be configured with the set of conditions, upon the fulfillment, or lack of fulfillment of which, it may or may not perform RAN reconfiguration. As yet another example, an application-specific xApp 501 may be authorized to instruct / configure a RAN to perform certain actions or apply certain policies, while another application-specificxApp 501 is only authorized to recommend the RAN to perform certain actions or apply certain policies, while the RAN may or may not accept the recommendation or may choose to modify the recommended actions or policy or may choose to reject or ignore the recommendation altogether.[000100] In the following, embodiments for xApp-triggered application layer adaptations are described. In one embodiment, the application-specific xApp uses or per-application configurations and / or QoE / RVQoE threshold(s) it has been configured with, and / or the per application mapping between QoE / RVQoE and QoS it has been configured with, to trigger application layer adaptation. In some embodiments, the application-specific xApp suggests, requests, or recommends necessary adaptation to the UE application layer, while in some other embodiments it suggest adaptation actions to be performed by the application server, which may accept or reject the adaptation recommended by the RAN. The handling may be as described above for the application-specific xApp control of the RAN.[000101] The application-specific xApp may use E2AP to trigger the E2 node(s) to transparently forward certain service-specific lEs to the application client in the UE(s). These lEs may contain service-specific information that the application client in the UE can use to update its service parameters, e.g., requesting resolution or codec change etc., and improve the QoE in line with the real-time capabilities of the RAN.[000102] As an example embodiment, an application-specific xApp may instruct / request an application client in the UE to use certain application-specific option(s), such as requesting certain video quality, e.g. resolution, when requesting streamed video content from a video application server, or increasing the content / level of the playout buffer of a streaming video session, or maintaining a certain playout buffer level during an ongoing streaming video session. The instruction from the application-specific xApp to the application client may apply to an ongoing application session and / or to future application sessions, optionally, the instruction is valid only while the UE remains in the same cell as it receives the instruction in. The application-specific xApp can in this way make the applicationclient adapt to the coming treatment it will receive, or can expect to receive, from the RAN instead of basing the application client behavior on observation of recent / historical treatment or communication quality or properties of the communication channel / path, e.g. delay and / or data rate. As a further option, the application-specific xApp may inform the RAN about what the application-specific xApp has instructed the application client in the UE to do, or the applicationspecific xApp may instruct the RAN to give the UE, or one or more certain DRB(s) of the UE, a certain treatment which is adapted to the application-specific option(s) the application-specific xApp has instructed the application client in the UE to use, e.g. adapted to what the UE (or the application client in the UE) needs to appropriately and successfully execute the application-specific option(s) with satisfactory result.[000103] In some embodiments, the application-specific xApp may provide to an application client in the UE the information that the application server associated with the application client may use to contact the application-specific xApp, wherein the application client in the UE forwards this information to the application server. As an alternative, the application client in the UE may by itself determine or derive information that the application server may use to contact the applicationspecific xApp and the UE may send this information to the application server.[000104] With the application server, the application-specific xApp may use Y1AP to expose information or RAN analytics to the application server across the Y1 interface, enabling the application server to make service layer updates. In a different realization, based on the information received from the applicationspecific xApp, the application server may provide new configurations back to the service-specific xApp to enable it to optimize the client application QoE based on RAN configuration and control and / or application layer adaptations in the client. As another option, the application server may suggest, recommend, or request the application-specific xApp to reconfigure the RAN in certain ways, e.g. adapting the RAN’s treatment of the UE(s) running application client(s) associated with the application server, e.g. so that better QoE can be achieved.[000105] In some embodiments where the suggestions / recommendations / instructions are provided between the application server / client and the xApp, the receiver of the suggestion / recommendation / instruction may indicate to the sender whether and to what extent the suggestion / recommendation / instruction has been adopted / accepted / enforced .[000106] In some embodiments, an application-specific xApp / entity may not be tied to a certain application but to a service type. Such a service-type specific xAPP / entity may act in a similar way as described above for any of the embodiments of the application-specific xApp, only that the service-type specific xApp can handle many different applications of the same service type. In addition, such a service-type specific xApp may use a discovery mechanism to discover applications implementing the service type on UEs. Such a discovery mechanism may leverage as mediator entity, at the application layer of a UE or in the operating system in the UE, which keeps track of, e.g., registers applications that are installed in the UE. Through such a mediating entity, the service-type specific xApp may obtain information that may be used to directly contact an application, e.g. an application client, implementing the concerned service type in the UE, e.g. to form an association with the application, e.g. application client, e.g. information in the form of IP address(es), transport protocol port number(s), application ID, key(s) for integrity protection and / or encryption, cryptographic certificate(s), token(s) (e.g. randomly generated). Alternatively, the service-type specific xApp may contact the application in the UE directly, e.g. using a service type-specific protocol and / or well-known / preconfigured transport protocol port number(s) and / or possibly an API or API(s).[000107] In some embodiments, the discovery may be done in the other direction. To this end, an application, e.g., an application client, in a UE connected to the network, may signal a discovery message to an xApp in the Near-RT RIC which targets the service type of the application (e.g. application client). This signal may e.g. be forwarded by an O-DU to an O-CU-CP, e.g. using one or more I E(s) in an F1AP message, and the O-CU-CP may in turn forward the signal to the Near-RTRIC, e.g. using one or more(s) I E(s) in an E2AP message. Messages from the xApp to the application (e.g. application client) in the UE may be forwarded in the opposite path, e.g., using one or more I E(s) in one or more E2AP message(s) and one or more I E(s) in F1 AP message(s). This way, an association may be formed between the xApp and the application (e.g., application client) in the UE.[000108] Once an association is formed between the service-type specific xApp and the application (e.g. application client) in the UE, or even without forming such an association, the service-type specific xApp may obtain from the application in the UE (e.g. application client) further information that may be specific to that specific implementation of the service type, such as application ID, vendor name or vendor ID, software version, configurations or settings of parameters governing or impacting the operation of the application, e.g., timers or thresholds, such as buffer level thresholds, e.g. thresholds related to a playout buffer of a streaming service where the thresholds may control when the application client sends requests, or suspends and / or resume requests, for additional content from the application server, or switches between different representations of the content.[000109] Furthermore, the service-type specific xApp may obtain information from the application, e.g. application client, in the UE, about the application server(s) the application is using. Such information may include e.g. contact information, e.g. a server’s fully qualified domain name (FQDN), IP address and transport protocol port number(s) used for communication with the application, e.g. application client, in the and / or for the service-type specific xApp to use when communicating with the application server. Further information related to the server may include e.g. vendor name or vendor ID, including any open source or freeware implementations, software version, security related information such as security key(s) or cryptographic certificate(s) and / or an application client identifier to be used if / when the service-type specific xApp contacts the application server.[000110] In the following possible communication options between mentioned entities are described. As previously described, the communication between the application-specific xApp in the Near-RT RIC and the application, e.g. application client, in the UE may take place across the Uu interface between the UE and theO-DU, across the F1-C interface between the O-DU and the O-CU, or, more specifically, the O-CU-CP, and across the E2 interface between the O-CU or, more specifically, the O-CU-CP, and the Near-RT RIC. However, alternative communication paths are also conceivable. One possibility is that the communication path traverses the user plane from the UE to the O-CU-UP, over F1-U between the O-DU and the O-CU-UP, and over E1 between the O-CU-UP and the O-CU-CP, and over E2 between the O-CU-CP and the Near-RT RIC. Another possibility is that the Near-RT RIC and the UE can communicate with each other entirely across the user plane.[000111] According to embodiments, the actual messages exchanged between the UE and the Near-RT RIC could be encapsulated in lEs in the existing protocols on the relevant interfaces, e.g., in RRC across the Uu interface, where an alternative to using RRC lEs could be to use Medium Access Control (MAC) Control Elements (CEs), in F1AP across the F1-C interface, and in E2AP across the E2 interface. Across the E1 interface, the messages exchanged between the UE and the Near-RT RIC may be encapsulated in lEs in the E1AP protocol. In addition, inside the UE, the application, e.g. application client, on the UE’s application layer may communicate with the lower layers in the UE, e.g. the UE Access Stratum (AS), using AT commands.[000112] In case of mobility, where the RAN node serving the UE changes, it is necessary to transfer from the source RAN node to the target RAN node the information about the associations between the source RAN node and the Near-RT RIC, to enable mobility support for the functionality proposed in this disclosure. In this case, the target RAN node assumes the role of the source node. The information would need to be passed via the Xn Application Protocol (XnAP) or the Next Generation Application Protocol (NGAP) , depending on the handover type. In some embodiments, the above is applicable to other types of mobility as well, types that include UE context transfer, e.g., RRC reestablishment.[000113] According to embodiment, the application client and the applicationspecific xApp may communicate via the user plane and E2, or via the user plane all the way between the application (client) and the xApp in the Near-RT RIC. Itmay also be possible to specify one or more entirely new protocol(s) for the exchange of messages between the Near-RT RIC and the UE or the application, e.g. application client, in the UE.[000114] In addition to communicating with the application, e.g. application client in the UE, the Near-RT RIC may communicate with the UE Access Stratum. In some embodiments, the UE Access Stratum is the only entity in the UE the Near-RT RIC communicates with, and the UE Access Stratum handles the corresponding communication with the application (e.g., application client) on the UE’s application layer.[000115] Certain elements described in this disclosure can be realized in a distributed manner on a cloud platform. The Near-RT RIC and service-specific xApps are anticipated in the O-RAN architecture to be hosted by O-Cloud platform which is a cloud virtualization platform for running cloud-native applications. Both the Near-RT RIC and service-specific xApps can be realized as distributed elements in a cloud platform.[000116] Fig. 10, in conjunction with fig. 2, shows an application-specific network entity 160; 170 configured to operate in a communication network 100, and configured for handling of at least one application in the communication network 100. The at least one application is provided by an application server 150. The communication network comprises a RAN 130. The application-specific network entity 160; 170 comprises processing circuitry 603 and memory 604. Said memory contains instructions executable by said processing circuitry, whereby the application-specific network entity 160; 170 is operative for obtaining, from a UE 140 having a connection to the RAN 130, application layer-related information on a number of sessions on the UE of the at least one application handled by the application-specific network entity 160; 170, and obtaining, from at least one of a network node 132 of the RAN 130 or the UE 140, radio-related information related to the connection between the UE 140 and the RAN 130. The application-specific network entity 160; 170 is further operative for determining, based on the obtained application layer-related information and the obtained radio-related information, an action for the RAN 130 and / or for the at least one application for improving QoE ofthe number of sessions on the UE of the at least one application, and when the determined action included an action for the RAN 130, sending, to the RAN 130, information on the determined action for the RAN 130, and when the determined action included an action for the at least one application, sending, to the application server 150 or to the UE 140, information on the determined action for the at least one application.[000117] According to an embodiment, the application-specific network entity 160; 170 is further operative for sending, to the UE 140, an instruction to send the application layer-related information for the number of sessions on the UE 140 of the at least one application handled by the application-specific network entity 160; 170 to the application-specific network entity 160; 170.[000118] According to another embodiment, the application-specific network entity 160; 170 is operative for the sending of the instruction to the UE 140 by sending information on a triggering condition for obtaining the application layer-related information for the number of sessions of the at least one application.[000119] According to another embodiment, the application-specific network entity 160; 170 is further operative for obtaining, from the application server 150, second application layer-related information on the number of sessions on the UE 140 of the at least one application handled by the application-specific network entity 160; 170. Further, the application-specific network entity 160; 170 is operative for the determining of an action for the RAN 130 and / or for the at least one application for improving the QoE of the at least one application further based on the second application layer-related information.[000120] According to another embodiment, the application-specific network entity 160; 170 is further operative for, before the obtaining of the application layer-related information from the UE 140, registering the application-specific network entity 160, 170 at the communication network 100 as authorized to determine actions for the RAN 130 and / or for the at least one application, for improving the QoE of sessions of the at least one application for UEs in the communication network, including the UE 140.[000121] According to yet another embodiment, the application-specific network entity 160; 170 is further operative for obtaining 203, from the application server 150, an instruction on how to perform the determining 210 of an action for the RAN 130 and / or for the at least one application for improving the QoE of the at least one application at the UE.[000122] According to yet another embodiment, the application-specific network entity 160; 170 is further operative for receiving from the RAN 130, information on whether the RAN has performed or will perform the determined action or not, when the determined action included an action for the RAN 130 and after the information on the determined action for the RAN 130 was sent to the RAN 130.[000123] According to yet another embodiment, the application-specific network entity 160; 170 is operative for the determining of an action for the RAN 130 and / or for the at least one application for improving the QoE only when the application layer-related information obtained from the UE 140 or when second application layer-related information obtained from the application server 160 meet an information condition.[000124] According to still another embodiment, the application-specific network entity 160; 170 is operative for the obtaining of the application layer-related information from the UE 140 by receiving the application layer-related information from the UE 140 in one or more information elements, IE, of an F1, E1, Xn or E2 application protocol communication interface.[000125] According to another embodiment, the RAN 130 is an O-RAN and the application-specific network entity 160, 170 is hosted on an O-RAN Near-RIC function / node.[000126] According to other embodiments, the application-specific network entity 160, 170 may further comprise a communication unit 602, which may be considered to comprise conventional means for communication with other nodes and entities of the communication network 100. The instructions executable by said processing circuitry 603 may be arranged as a computer program 605 storede.g. in said memory 604. The processing circuitry 603 and the memory 604 may be arranged in a sub-arrangement 601. The sub-arrangement 601 may be a micro-processor and adequate software and storage therefore, a Programmable Logic Device, PLD, or other electronic component(s) / processing circuit(s) configured to perform the methods mentioned above. The processing circuitry 603 may comprise one or more programmable processor, application-specific integrated circuits, field programmable gate arrays or combinations of these adapted to execute instructions.[000127] The computer program 605 may be arranged such that when its instructions are run in the processing circuitry 603, the instructions cause the application-specific network entity 160, 170 to perform the steps described in any of the described embodiments of application-specific network entity 160, 170 and its method. The computer program 605 may be carried by a computer program product connectable to the processing circuitry 603. The computer program product may be the memory 604, or at least arranged in the memory. The computer program product may be called a computer-readable storage medium. The memory 604 may be realized as for example a Random-access memory (RAM), Read-Only Memory (ROM) or an Electrical Erasable Programmable ROM (EEPROM). In some embodiments, a carrier may contain the computer program 605. The carrier may be one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or computer readable storage medium. The computer-readable storage medium may be e.g., a CD, DVD or flash memory, from which the program could be downloaded into the memory 604. Alternatively, the computer program 605 may be stored on a server or any other entity to which the application-specific network entity 160, 170 has access via the communication unit 602. The computer program 605 may then be downloaded from the server into the memory 604.[000128] Fig. 11, in conjunction with fig. 2, describes a UE 140 configured for connection to a RAN 130 of a communication network 100. The UE 140 comprises processing circuitry 703 and memory 704. Said memory contains instructionsexecutable by said processing circuitry, whereby the UE 140 is operative for obtaining application layer-related information for a number of sessions of at least one application executing on the UE 140 and handled in the communication network 100 by an application-specific network entity 160; 170, and sending the application layer-related information to the application-specific network entity 160; 170. The UE 140 is further operative for receiving action information on an action for the number of sessions for the at least one application when the applicationspecific network entity 160; 170 determined, based on the sent application layer-related information, that such an action is required in order to improve QoE of the number of sessions of the at least one application at the UE 140, the action information originating from the application-specific network entity 160; 170.[000129] According to an embodiment, the UE 140 is operative for receiving from the RAN 130, an instruction of reconfiguration as a result of the applicationspecific network entity 160; 170 determining an action for the RAN 130 for improving QoE of the number of sessions on the UE of the at least one application.[000130] According to another embodiment, the UE 140 is further operative for receiving, from the application-specific network entity 160; 170 or from an application server 150 providing the at least one application, an instruction to obtain the application layer-related information for the number of sessions of the at least one application executing on the UE 140 and to send the obtained application layer-related information to the application-specific network entity 160; 170.[000131] According to another embodiment, the received instruction to obtain the application layer-related information comprises information on a triggering condition for obtaining the application layer-related information for the number of sessions of the at least one application. Further, the UE 140 is operative for obtaining the application layer-related information for the number of sessions of the at least one application when the triggering condition is met.[000132] According to another embodiment, the UE 140 is further operative for sending, to the RAN 130, radio-related information related to the connection between the UE 140 and the RAN 130. Such information is then sent further by the RAN to the application-specific network entity 160; 170.[000133] According to another embodiment, the UE 140 is operative for sending the application layer-related information to the application-specific network entity 160; 170 in one or more information elements, IE, of an F1, E1, Xn or E2 application protocol communication interface.[000134] According to other embodiments, the UE 140 may further comprise a communication unit 702, which may be considered to comprise conventional means for wireless communication with a RAN node, such as RAN nodes 132, 134 of fig. 2. The conventional means for wireless communication may be e.g., a transceiver for wireless transmission and reception of signals in the communication network. The instructions executable by said processing circuitry 703 may be arranged as a computer program 705 stored e.g. in said memory 704. The processing circuitry 703 and the memory 704 may be arranged in a subarrangement 701. The sub-arrangement 701 may be a micro-processor and adequate software and storage therefore, a Programmable Logic Device, PLD, or other electronic component(s) / processing circuit(s) configured to perform the methods mentioned above. The processing circuitry 703 may comprise one or more programmable processor, application-specific integrated circuits, field programmable gate arrays or combinations of these adapted to execute instructions.[000135] The computer program 705 may be arranged such that when its instructions are run in the processing circuitry 703, the instructions cause the UE 140 to perform the steps described in any of the described embodiments of UE 140 and its method. The computer program 705 may be carried by a computer program product connectable to the processing circuitry 703. The computer program product may be the memory 704, or at least arranged in the memory. The computer program product may be called a computer-readable storage medium. The memory 704 may be realized as for example a Random-access memory(RAM), Read-Only Memory (ROM) or an Electrical Erasable Programmable ROM (EEPROM). In some embodiments, a carrier may contain the computer program 705. The carrier may be one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or computer readable storage medium. The computer-readable storage medium may be e.g., a CD, DVD or flash memory, from which the program could be downloaded into the memory 704. Alternatively, the computer program 705 may be stored on a server or any other entity to which the UE 140 has access via the communication unit 702. The computer program 705 may then be downloaded from the server into the memory 704. The UE may further comprise a power source such as a battery 706.[000136] According to another embodiment, and referring to fig. 2, a system is shown which is configured for handling of at least one application in a communication network 100 comprising a RAN 130, the at least one application being provided by an application server 150. The system comprises a UE 140 configured for connection to the RAN 130 and an application-specific network entity 160; 170 of the communication network 100 for handling of the at least one application in the communication network 100. The UE 140 is operative for obtaining application layer-related information for a number of sessions of the at least one application executing on the UE 140, and sending 306 the application layer-related information to the application-specific network entity 160; 170. The application-specific network entity 160; 170 is operative for obtaining the application layer-related information from the UE 140 and obtaining, from at least one of a network node 132 of the RAN 130 or the UE 140, radio-related information related to the connection between the UE 140 and the RAN 130. The application-specific network entity 160; 170 is further operative for determining, based on the obtained application layer-related information and the obtained radiorelated information, an action for the RAN 130 and / or for the at least one application for improving QoE of the number of sessions on the UE of the at least one application, and when the determined action included an action for the RAN 130, sending, to the RAN 130, information on the determined action for the RAN 130, and when the determined action included an action for the at least oneapplication, sending, to the application server 150 or to the UE 140, information on the determined action for the at least one application.[000137] Although the description above contains a plurality of specificities, these should not be construed as limiting the scope of the concept described herein but as merely providing illustrations of some exemplifying embodiments of the described concept. It will be appreciated that the scope of the presently described concept fully encompasses other embodiments which may become obvious to those skilled in the art, and that the scope of the presently described concept is accordingly not to be limited. Reference to an element in the singular is not intended to mean "one and only one" unless explicitly so stated, but rather "one or more." All structural and functional equivalents to the elements of the abovedescribed embodiments that are known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed hereby. Moreover, it is not necessary for an apparatus or method to address each and every problem sought to be solved by the presently described concept, for it to be encompassed hereby. In the exemplary figures, a broken line generally signifies that the feature within the broken line is optional.

Claims

CLAIMS1. A method performed by an application-specific network entity (160; 170) for handling of at least one application in a communication network (100), the at least one application being provided by an application server (150), the communication network comprising a radio access network, RAN (130), the method comprising:obtaining (204), from a User Equipment, UE (140), having a connection to the RAN (130), application layer-related information on a number of sessions on the UE of the at least one application handled by the application-specific network entity (160; 170);obtaining (206), from at least one of a network node (132) of the RAN (130) or the UE (140), radio-related information related to the connection between the UE (140) and the RAN (130);determining (210), based on the obtained application layer-related information and the obtained radio-related information, an action for the RAN (130) and / or for the at least one application for improving Quality of Experience, QoE, of the number of sessions on the UE of the at least one application,when the determined action included an action for the RAN (130), sending (212), to the RAN (130), information on the determined action for the RAN (130), andwhen the determined action included an action for the at least one application, sending (214), to the application server (150) or to the UE (140), information on the determined action for the at least one application.

2. Method according to claim 1 , further comprising:sending (202), to the UE (140), an instruction to send the application layer-related information for the number of sessions on the UE (140) of the at least one application handled by the application-specific network entity (160; 170) to the application-specific network entity (160; 170).

3. Method according to claim 2, wherein the instruction sent (202) to the UE (140) comprises information on a triggering condition for obtaining theapplication layer-related information for the number of sessions of the at least one application.

4. Method according to any of claims 1-3, further comprising:obtaining (208), from the application server (150), second application layer-related information on the number of sessions on the UE (140) of the at least one application handled by the application-specific network entity (160; 170), wherein the determining (210) of an action for the RAN (130) and / or for the at least one application for improving the QoE of the at least one application is further based on the second application layer-related information.

5. Method according to any of the preceding claims, further comprising, before the obtaining (204) of the application layer-related information from the UE (140), registering (201) the application-specific network entity (160, 170) at the communication network (100) as authorized to determine actions for the RAN (130) and / or for the at least one application, for improving the QoE of sessions of the at least one application for UEs in the communication network, including the UE (140).

6. Method according to any of the preceding claims, further comprising obtaining (203), from the application server (150), an instruction on how to perform the determining (210) of an action for the RAN (130) and / or for the at least one application for improving the QoE of the at least one application at the UE.

7. Method according to any of the preceding claims, further comprising, when the determined (210) action included an action for the RAN (130) and after the information on the determined action for the RAN (130) was sent (212) to the RAN (130), receiving (216) from the RAN (130), information on whether the RAN has performed or will perform the determined action or not.

8. Method according to any of the preceding claims, wherein only when the application layer-related information obtained (204) from the UE (140) or when second application layer-related information obtained from the application server(160) meet an information condition, an action for the RAN (130) and / or for the at least one application for improving the QoE can be determined (210).

9. Method according to any of the preceding claims, wherein the application layer-related information obtained (204) from the UE (140) is received from the UE (140) in one or more information elements, IE, of an F1, E1, Xn or E2 application protocol communication interface .

10. Method according to any of the preceding claims, wherein the RAN (130) is an O-RAN and the application-specific network entity (160, 170) is hosted on an O-RAN Near-RIC function / node.

11. A method performed by a UE (140) connected to a RAN (130) of a communication network (100), the method comprising:obtaining (304) application layer-related information fora number of sessions of at least one application executing on the UE (140) and handled in the communication network (100) by a application-specific network entity (160; 170), sending (306) the application layer-related information to the application-specific network entity (160; 170), andreceiving (308) action information on an action for the number of sessions for the at least one application when the application-specific network entity (160; 170) determined, based on the sent application layer-related information, that such an action is required in order to improve QoE of the number of sessions of the at least one application at the UE (140), the action information originating from the application-specific network entity (160; 170).

12. Method according to claim 11 , further comprising:receiving (310) from the RAN (130), an instruction of reconfiguration as a result of the application-specific network entity (160; 170) determining an action for the RAN (130) for improving QoE of the number of sessions on the UE of the at least one application.

13. Method according to claim 11 or 12, further comprising:receiving (302), from the application-specific network entity (160; 170) or from an application server (150) providing the at least one application, an instruction to obtain the application layer-related information for the number of sessions of the at least one application executing on the UE (140) and to send the obtained application layer-related information to the application-specific network entity (160; 170).

14. Method according to claim 13, wherein the received (302) instruction to obtain the application layer-related information comprises information on a triggering condition for obtaining the application layer-related information for the number of sessions of the at least one application, andwherein the application layer-related information is obtained (304) for the number of sessions of the at least one application when the triggering condition is met.

15. Method according to any of claims 11-14, further comprising sending (307), to the RAN (130), radio-related information related to the connection between the UE (140) and the RAN (130).

16. Method according to any of claims 11-15, wherein the application layer-related information is sent (306) to the application-specific network entity (160; 170) in one or more information elements, IE, of an F1, E1, Xn or E2 application protocol communication interface.

17. A system configured for handling of at least one application in a communication network (100) comprising a radio access network, RAN (130), the at least one application being provided by an application server (150), the system comprising:a UE (140) configured for connection to the RAN (130), a application-specific network entity (160; 170) of the communication network (100) for handling of the at least one application in the communication network (100),wherein the UE (140) is operative for:obtaining application layer-related information fora number of sessions of the at least one application executing on the UE (140),sending (306) the application layer-related information to the application-specific network entity (160; 170),wherein the application-specific network entity (160; 170) is operative for:obtaining the application layer-related information from the UE (140), obtaining, from at least one of a network node (132) of the RAN (130) or the UE (140), radio-related information related to the connection between the UE (140) and the RAN (130);determining, based on the obtained application layer-related information and the obtained radio-related information, an action for the RAN (130) and / or for the at least one application for improving Quality of Experience, QoE, of the number of sessions on the UE of the at least one application,when the determined action included an action for the RAN (130), sending, to the RAN (130), information on the determined action for the RAN (130),when the determined action included an action for the at least one application, sending, to the application server (150) or to the UE (140), information on the determined action for the at least one application.

18. An application-specific network entity (160; 170) configured to operate in a communication network (100), and configured for handling of at least one application in the communication network (100), the at least one application being provided by an application server (150), the communication network comprising a radio access network, RAN (130), the application-specific network entity (160; 170) comprising processing circuitry (603) and memory (604), said memory containing instructions executable by said processing circuitry, whereby the application-specific network entity (160; 170) is operative for:obtaining, from a User Equipment, UE (140), having a connection to the RAN (130), application layer-related information on a number of sessions on the UE of the at least one application handled by the application-specific network entity (160; 170);obtaining, from at least one of a network node (132) of the RAN (130) or the UE (140), radio-related information related to the connection between the UE (140) and the RAN (130);determining, based on the obtained application layer-related information and the obtained radio-related information, an action for the RAN (130) and / or for the at least one application for improving Quality of Experience, QoE, of the number of sessions on the UE of the at least one application,when the determined action included an action for the RAN (130), sending, to the RAN (130), information on the determined action for the RAN (130), andwhen the determined action included an action for the at least one application, sending, to the application server (150) or to the UE (140), information on the determined action for the at least one application.

19. Application-specific network entity (160; 170) according to claim 18, further being operative for:sending, to the UE (140), an instruction to send the application layer-related information for the number of sessions on the UE (140) of the at least one application handled by the application-specific network entity (160; 170) to the application-specific network entity (160; 170).

20. Application-specific network entity (160; 170) according to claim 19, operative for the sending of the instruction to the UE (140) by sending information on a triggering condition for obtaining the application layer-related information for the number of sessions of the at least one application.

21. Application-specific network entity (160; 170) according to any of claims 18-20, further being operative for obtaining, from the application server (150), second application layer-related information on the number of sessions on the UE (140) of the at least one application handled by the application-specific network entity (160; 170),wherein the application-specific network entity (160; 170) is operative for the determining of an action for the RAN (130) and / or for the at least one application for improving the QoE of the at least one application further based on the second application layer-related information.

22. Application-specific network entity (160; 170) according to any of claims 18-21, further being operative for, before the obtaining of the application layer-related information from the UE (140), registering the application-specific network entity (160, 170) at the communication network (100) as authorized to determine actions for the RAN (130) and / or for the at least one application, for improving the QoE of sessions of the at least one application for UEs in the communication network, including the UE (140).

23. Application-specific network entity (160; 170) according to any of claims 18-22, further being operative for obtaining (203), from the application server (150), an instruction on how to perform the determining (210) of an action for the RAN (130) and / or for the at least one application for improving the QoE of the at least one application at the UE.

24. Application-specific network entity (160; 170) according to any of claims 18-23, further being operative for receiving from the RAN (130), information on whether the RAN has performed or will perform the determined action or not, when the determined action included an action for the RAN (130) and after the information on the determined action for the RAN (130) was sent to the RAN (130).

25. Application-specific network entity (160; 170) according to any of claims 18-24, operative for the determining of an action for the RAN (130) and / or for the at least one application for improving the QoE only when the application layer-related information obtained from the UE (140) or when second application layer-related information obtained from the application server (160) meet an information condition.

26. Application-specific network entity (160; 170) according to any of claims 18-25, operative for the obtaining of the application layer-related information from the UE (140) by receiving the application layer-related information from the UE (140) in one or more information elements, IE, of an F1, E1, Xn or E2 application protocol communication interface.

27. Application-specific network entity (160; 170) according to any of claims 18-26, wherein the RAN (130) is an O-RAN and the application-specific network entity (160, 170) is hosted on an O-RAN Near-RIC function / node.

28. A computer program (605) comprising instructions, which, when executed by at least one processing circuitry of a application-specific network entity (160; 170) of a communication network (100), configured for handling of at least one application in the communication network (100), the at least one application being provided by an application server (150), the communication network comprising a radio access network, RAN (130), causes the applicationspecific network entity (160; 170) to perform the following steps:obtaining, from a User Equipment, UE (140), having a connection to the RAN (130), application layer-related information on a number of sessions on the UE of the at least one application handled by the application-specific network entity (160; 170);obtaining, from at least one of a network node (132) of the RAN (130) or the UE (140), radio-related information related to the connection between the UE (140) and the RAN (130);determining, based on the obtained application layer-related information and the obtained radio-related information, an action for the RAN (130) and / or for the at least one application for improving Quality of Experience, QoE, of the number of sessions on the UE of the at least one application,when the determined action included an action for the RAN (130), sending, to the RAN (130), information on the determined action for the RAN (130), andwhen the determined action included an action for the at least one application, sending, to the application server (150) or to the UE (140), information on the determined action for the at least one application.

29. A carrier containing the computer program (605) according to claim 28, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, an electric signal or a computer readable storage medium (606).

30. A UE (140) configured for connection to a RAN (130) of a communication network (100), the UE (140) comprising processing circuitry (t03) and memory (704), said memory containing instructions executable by said processing circuitry, whereby the UE (140) is operative for:obtaining application layer-related information fora number of sessions of at least one application executing on the UE (140) and handled in the communication network (100) by a application-specific network entity (160; 170), sending the application layer-related information to the applicationspecific network entity (160; 170), andreceiving action information on an action for the number of sessions for the at least one application when the application-specific network entity (160; 170) determined, based on the sent application layer-related information, that such an action is required in order to improve QoE of the number of sessions of the at least one application at the UE (140), the action information originating from the application-specific network entity (160; 170).

31. UE (140) according to claim 30, further being operative for:receiving from the RAN (130), an instruction of reconfiguration as a result of the application-specific network entity (160; 170) determining an action for the RAN (130) for improving QoE of the number of sessions on the UE of the at least one application.

32. UE (140) according to claim 30 or 31 , further being operative for:receiving, from the application-specific network entity (160; 170) or from an application server (150) providing the at least one application, an instruction to obtain the application layer-related information for the number of sessions of the at least one application executing on the UE (140) and to send the obtained application layer-related information to the application-specific network entity (160; 170).

33. UE (140) according to claim 32, wherein the received instruction to obtain the application layer-related information comprises information on a triggering condition for obtaining the application layer-related information for the number of sessions of the at least one application, andwherein the UE (140) is operative for obtaining the application layer-related information for the number of sessions of the at least one application when the triggering condition is met.

34. UE (140) according to any of claims 30-33, further being operative for sending, to the RAN (130), radio-related information related to the connection between the UE (140) and the RAN (130).

35. UE (140) according to any of claims 30-34, operative for sending the application layer-related information to the application-specific network entity (160; 170) in one or more information elements, IE, of an F1, E1, Xn or E2 application protocol communication interface,36. A computer program (605) comprising instructions, which, when executed by at least one processing circuitry of a UE (140) connected to a RAN (130) of a communication network (100), causes the UE (140) to perform the following steps:obtaining application layer-related information fora number of sessions of at least one application executing on the UE (140) and handled in the communication network (100) by a application-specific network entity (160; 170), sending the application layer-related information to the applicationspecific network entity (160; 170), andreceiving action information on an action for the number of sessions for the at least one application when the application-specific network entity (160; 170) determined, based on the sent application layer-related information, that such an action is required in order to improve QoE of the number of sessions of the at least one application at the UE (140), the action information originating from the application-specific network entity (160; 170).

37. A carrier containing the computer program (605) according to claim 36, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, an electric signal or a computer readable storage medium (606).

Images