WO2017105300A1

WO2017105300A1 - Network node and analytics arrangement and methods performed thereby for delivering a service to a wireless device

Info

Publication number: WO2017105300A1
Application number: PCT/SE2015/051349
Authority: WO
Inventors: Hans Thomas ÅSBERG; Mathias Sintorn; Jari Vikberg
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2015-12-15
Filing date: 2015-12-15
Publication date: 2017-06-22

Abstract

A network node responsible for scheduling of radio resources to a wireless device and a method performed thereby are provided. The network node and the wireless device are operable in a wireless communication network, wherein the wireless device is engaged in communication with a node outside the wireless communication network thereby generating a traffic flow between the wireless device and the node outside the wireless communication network. The method comprises obtaining (110) analytics information of the traffic flow between the wireless device and the node outside the wireless communication network; obtaining (120) a Quality of Experience, QoE, for a service associated with the traffic flow; and performing (140) one or more actions for the wireless device based on the obtained analytics information and on the obtained QoE.

Description

NETWORK NODE AND ANALYTICS ARRANGEMENT AND METHODS PERFORMED THEREBY FOR DELIVERING A SERVICE TO A WIRELESS

DEVICE

Technical field

[0001 ] The present disclosure relates to wireless communication and in particular to a network node, analytics arrangement and methods performed thereby for delivering a service to a wireless device in a wireless communication network.

Background

[0002] Today's communication networks are interconnected and offer a very wide variety of different services to users of wireless devices. Generally, a service may be provided to a user by a server, which may be located within the wireless communication network or outside the wireless communication network. Often, the server providing a service requested by a user of a wireless device is located somewhere on the Internet.

[0003] Consequently, in order to provide services to wireless devices in the wireless communication network, the Internet is involved, wherein the wireless device communicates with one or more servers on the Internet. It is even possible that in order to reach the Internet, another separate network may need to be traversed.

[0004] As the wireless device is provided with a service from a server, e.g. on the Internet, generally packets are transmitted between the server and the wireless device. The packets travelling the path between the server and the wireless device "generate" a traffic flow there between. Different services are generally also associated with different Quality of Service, QoS, and/or Quality of Experience, QoE, requirements. Alongside with these requirements, the throughput of cells of network nodes in the wireless communication network should be optimised so as to make the most out of the available resources. [0005] When packets associated with a service travel along the path between a wireless device and the server providing the service, the packets may be subjected to e.g. delay due to congestion in one or more of the intermediate nodes in the path. The delay may be relatively small only affecting the QoE to a small degree, the delay may be of a magnitude such that it is difficult but not impossible to fulfil the QoE, or the delay may be significant to such a degree that it is not possible to fulfil the QoE. The delay may be caused within the wireless

communication network, by the network node responsible for scheduling of resources or by one or more nodes outside the wireless communication network.

[0006] The strive to optimise performance such as throughput by Radio

Resource Management, RRM, functions may interfere with QoE requirements especially in case where one or more packets have e.g. suffered a delay outside the wireless communication network. The independence of the strive to optimise performance and fulfilling QoE requirements may lead to that none of the conditions are met.

Summary

[0007] The object is to obviate at least some of the problems outlined above. In particular, it is an object to provide a network node, an analytics arrangement and methods performed thereby for delivering a service to a wireless device in a wireless communication network. These objects and others may be obtained by providing a network node and an analytics arrangement respectively, as well as a method performed by a network node and an analytics arrangement respectively according to the independent claims attached below.

[0008] According to an aspect a method performed by a network node responsible for scheduling of resources to a wireless device is provided. The network node and the wireless device being operable in a wireless communication network, wherein the wireless device is engaged in communication with a node outside the wireless communication network thereby generating a traffic flow between the wireless device and the node outside the wireless communication network. The method comprises obtaining analytics information of the traffic flow between the wireless device and the node outside the wireless communication network; obtaining a Quality of Experience, QoE, for a service associated with the traffic flow; and performing one or more actions for the wireless device based on the obtained analytics information and on the obtained QoE.

[0009] According to an aspect a method performed by an analytics arrangement implemented in a wireless device or in a node in or outside a wireless

communication network is provided. The method comprises receiving one or more packets of a traffic flow between the wireless device and a node outside the wireless communication network; analysing the traffic flow based on the received one or more packets; and providing the analysis as analytics information to a network node responsible for scheduling of radio resources to the wireless device.

[00010] According to an aspect a network node responsible for scheduling of resources to a wireless device is provided. The network node and the wireless device being operable in a wireless communication network, wherein the wireless device is engaged in communication with a node outside the wireless

communication network thereby generating a traffic flow between the wireless device and the node outside the wireless communication network. The network node is configured for obtaining analytics information of the traffic flow between the wireless device and the node outside the wireless communication network; obtaining a Quality of Experience, QoE, for a service associated with the traffic flow; and performing one or more actions for the wireless device based on the obtained analytics information and on the obtained QoE.

[0001 1 ] According to an aspect an analytics arrangement implemented in a wireless device or in a node in or outside a wireless communication network is provided. The analytics arrangement is configured for receiving one or more packets of a traffic flow between the wireless device and a node outside the wireless communication network; analysing the traffic flow based on the received one or more packets; and providing the analysis as analytics information to a network node responsible for scheduling of radio resources to the wireless device. [00012] The network node, the analytics arrangement, the method performed by the network node and the method performed by the analytics arrangement have several possible advantages. One possible advantage is that the network node may be enabled or allowed to act on performance related information normally only available to the client application in order to improve the overall end-user perceived performance in the network.

Brief description of drawings

[00013] Embodiments will now be described in more detail in relation to the accompanying drawings, in which:

[00014] Figure 1 a is a flowchart of a method performed by a network node responsible for scheduling of resources, according to an exemplifying

embodiment.

[00015] Figure 1 b is a flowchart of a method performed by a network node responsible for scheduling of resources, according to yet an exemplifying embodiment.

[00016] Figure 1 c is a flowchart of a method performed by a network node responsible for scheduling of resources, according to still an exemplifying embodiment.

[00017] Figure 2 is a flowchart of a method performed by an analytics arrangement implemented in a wireless device or in a node in or outside a wireless communication network, according to an exemplifying embodiment.

[00018] Figure 3a is an illustration of a radio scheduler selecting a queue of highest priority to be transmitted to the associated wireless device.

[00019] Figure 3b is an illustration of an end-to-end service flow passing through multiple networks and nodes.

[00020] Figure 3c is an illustration of an end-to-end service flow passing through multiple networks and nodes, according to an example. [00021 ] Figure 3d is an illustration of an end-to-end service flow passing through multiple networks and nodes, according to yet an example.

[00022] Figure 3e is an illustration of an end-to-end service flow passing through multiple networks and nodes, according to still an example.

[00023] Figure 3f is an illustration of an end-to-end service flow passing through multiple networks and nodes, according to a further example.

[00024] Figure 4 is a block diagram of a network node responsible for scheduling of resources, according to an exemplifying embodiment.

[00025] Figure 5 is a block diagram of network node responsible for scheduling of resources, according to another exemplifying embodiment.

[00026] Figure 6 is a block diagram of an analytics arrangement implemented in a wireless device or in a node in or outside a wireless communication network, according to an exemplifying embodiment.

[00027] Figure 7 is a block diagram of an analytics arrangement implemented in a wireless device or in a node in or outside a wireless communication network, according to another exemplifying embodiment.

[00028] Figure 8 is a block diagram of an arrangement in a network node responsible for scheduling of resources, according to an exemplifying

embodiment.

[00029] Figure 9 is a block diagram of an arrangement in an analytics

arrangement implemented in a wireless device or in a node in or outside a wireless communication network, according to an exemplifying embodiment.

Detailed description

[00030] Briefly described, a network node responsible for scheduling of resources and a method performed thereby are provided. [00031 ] Radio Resource Management, RRM, functions in RAN are generally not aware of the QoE of client applications on the wireless device. Irrespective if QoE is affected by elements outside of RAN, the RRM generally always tries to optimise performance of a flow given the situation in RAN alone. This may lead into situations in which a flow that is already affected by the elements outside RAN is still prioritised as there would be no such impact on QoE. This is not optimal on network level as if this information would be available in RAN then it would be possible to for example prioritise flows that still have the possibility to meet the end-to-end QoE.

[00032] In order to avoid such undesired situations, the network node obtains information about current conditions for a packet of a traffic flow associated with a service being provided to a wireless device. The network node also obtains QoE for the service. Then based on the QoE for the service and the current conditions for the packet, the network node may take appropriate actions with regards to both the possibility of fulfilling the QoE for the service for the wireless device, the possibility of fulfilling QoE of other services and/or wireless device currently being served by the network node. In this manner, the strive to optimise throughput does not negatively affect the QoE for a service in case packet(s) of that service has suffered a delay in one or more nodes outside the wireless communication network.

[00033] Embodiments herein relate to a method performed by a network node responsible for scheduling of radio resources to a wireless device. The network node and the wireless device being operable in a wireless communication network, wherein the wireless device is engaged in communication with a node outside the wireless communication network thereby generating a traffic flow between the wireless device and the node outside the wireless communication network. Embodiments of such a method will now be described with reference to figures 1a-c. Figure 1a illustrates the method 100 comprising obtaining 1 10 analytics information of the traffic flow between the wireless device and the node outside the wireless communication network; obtaining 120 a Quality of

Experience, QoE, for a service associated with the traffic flow; and performing 140 one or more actions for the wireless device based on the obtained analytics information and on the obtained QoE.

[00034] Generally, the network node may serve a plurality of wireless devices, wherein several of the wireless devices may be engaged in, or making use of, one or more services, which are provided from one or more servers being located outside the wireless communication network, e.g. on the Internet. Each service may be delivered or provided to the wireless device by means of a traffic flow between respective wireless devices and respective servers. A server is thus a node outside the wireless communication network. Simultaneously, a plurality of wireless device may be engaged in services provided by means of nodes and/or equipment within the wireless communication network, e.g. a telephone call or a video call. As these different traffic flows travel between the respective wireless devices and the respective servers, i.e. travels through the wireless

communication network and one or more other networks, e.g. the Internet, the traffic flows may pass through a plurality of network nodes inside and outside the wireless communication network, wherein each may cause a small delay depending on the load of the respective network nodes.

[00035] The network node responsible for the scheduling of radio resources to the wireless device (and also other wireless device being served by the network node) obtains analytics information of the traffic flow between the wireless device and the node outside the wireless communication network. There are several ways for the network node to obtain the analytics information as will be explained in more detail below. The analytics information may comprise a plurality of different types and pieces of information. In an example, the analytics information comprises information about a delay at least within a part of the path travelled by the traffic flow e.g. between the node outside the wireless communication network and the network node responsible for the scheduling of radio resources to the wireless device. It shall be pointed out that this is merely an example, and the analytics information may comprise other and/or more information; and the example of the delay may be between any two points along the path travelled by the traffic flow from the node outside the wireless communication network and the wireless device.

[00036] The network node responsible for the scheduling of radio resources to the wireless device also obtains the QoE for the service associated with the traffic flow. Different services may be associated with different QoE and/or Quality of Service, QoS, depending on the type of service. For example, some services are delay tolerant, whereas some have strict requirements on minimal delay.

[00037] Once the network node responsible for the scheduling of radio resources to the wireless device has obtained analytics information indicating the current traffic situation for the traffic flow associated with the service that the wireless device is engaged in and the QoE for that service, or traffic flow, the network node may perform one or more actions for the wireless device based on the obtained analytics information and on the obtained QoE. The actions that the network node may perform may relate to different things as will be explained in more detail below. In one example, the network node may down-prioritise the wireless device if the traffic flow is already subjected to e.g. delay somewhere along the path between the node outside the network providing the service and the network node. In such an example, the network node may prioritise other wireless devices thereby increasing the probability for meeting the required QoE associated with services being provided to those other wireless devices.

[00038] The method performed by the network node may have several advantages. One possible advantage is that the network node may be enabled or allowed to act on performance related information normally only available to the client application in order to improve the overall end-user perceived performance in the network. This overall end-user perceived performance may be called as QoE.

[00039] The method may further comprise, as illustrated in figure 1 b,

determining 130 the load of the network node. [00040] Determining the load of the network node may be done in different ways. Merely as an example, the network node may determine a ratio between currently used radio resources and total amount of radio resources, wherein the ratio may be compared to one or more load thresholds. If the load meets one or more of the load thresholds, the network node may determine if the load is high, medium, or low for example. If the load is high, the network node may have to take some actions in order to sustain acceptable QoE for as many wireless devices and/or services as possible.

[00041 ] Another example of determining the load of the network node may be to determine status of buffers of the network node. If the amount of data or packets in the buffers is above one or more buffer thresholds, the network node may determine that the load is high, medium or low. Still another example of

determining the load of the network node may be to determine usage level (or ratio) of internal resources of the network node, such as memory, processing units, CPU etc.

[00042] In an example, the performing 140 one or more actions for the wireless device is further based on the determined load of the network node.

[00043] Once the network node has determined the load of the network node, the network node may take that into account when determining which action(s) to perform.

[00044] In other words, the network node may perform one or more actions based on the obtained analytics information, the obtained QoE and the determined load of the network node. In this manner, the network node may perform actions such that as many services, traffic flows, and/or wireless devices are affected by e.g. a high load of the network node. It may be that the network node is not able to schedule radio resources for all services, traffic flows, and/or wireless devices without causing delay to one or more of the services, traffic flows, and/or wireless devices. If so, the network node may down-prioritise those services, traffic flows, and/or wireless devices that are already subjected to e.g. delay such that the QoE for those services are already impossible to fulfil. In this manner, the network node may increase the probability for being able to fulfil the QoE for those services that are not already subjected to e.g. delay by other nodes inside or outside the wireless communication network.

[00045] The obtaining of the analytics information may comprise (a) receiving the analytics information from an analytics arrangement implemented in either the wireless device or in another node in or outside the wireless communication network, or (b) determining the analytics information by analysing the traffic flow.

[00046] There are different ways to obtain the analytics information, partly based on where the analytics arrangement is implemented. The analytics arrangement may be implemented in the network node responsible for scheduling of radio resources to a wireless device or in the wireless device. The analytics

arrangement may also, or alternatively, be implemented in any node or nodes in the path between the wireless device and the node outside the wireless

communication network. More than one node may comprise an analytics arrangement, see e.g. figure 3c.

[00047] The traffic flow will pass through one or more nodes outside the wireless communication network and one or more nodes within the wireless communication network. The service that the wireless device is engaged in, or that is being provided to the wireless device may be supported or provided by a server, the server itself being a node outside the wireless communication network. There may be one or more other nodes outside the wireless communication network that are involved in delivering the service (by means of the traffic flow) to the wireless device, such as e.g. routers and gateways. Within the wireless communication network, there may also be one or more nodes involved, such as e.g. a gateway, one or more switches, a radio network controller and a radio base station. The analytics arrangement may be implemented or comprised in any node through which the traffic flow passes.

[00048] In the case (a) that the analytics arrangement is implemented or comprised in any other node other than the network node responsible for scheduling of radio resources to a wireless device or that the analytics arrangement is implemented or comprised in the wireless device, the network node may receive the analytics information from the entity in which the analytics information is implemented or comprised. Any node in the path between the server (i.e. the node outside the wireless communication network providing/delivering the service) and the wireless device will receive and forward packet(s) of the traffic flow and may analyse the packet or traffic flow. The analysis may then be sent to the network node responsible for scheduling of radio resources to a wireless device as analytics information. Alternatively, the analytics arrangement is comprised in the wireless device, wherein the analytics information is received from the wireless device.

[00049] In the case (b) that the analytics arrangement is implemented or comprised in the network node responsible for scheduling of radio resources to a wireless device, the analytics information is obtained by the network node itself performing the above described analysis of the packet(s) or the traffic flow and thereby determining the analytics information.

[00050] How the analysis of the packet(s) or the traffic flow may be performed is described in more detail below.

[00051 ] The analytics information may comprise one or more of (i) packet delay, (ii) number of dropped packets, (iii) buffer bloating, (iv) jitter, (v) ratio of dropped packets, (vi) estimated QoE, and (vii) specific QoE requirements for the traffic flow

[00052] These are several examples of what may be comprised in the analytics information. Due to congestion in one or more nodes in the path may result in a delay of the packet(s) passing that/those node(s) since they will have to wait at that/those node(s) before being forwarded towards the wireless device or towards the server. Such a congestion may also result in packets being dropped. Buffer bloating refers to excess buffering of packets resulting in high latency and packet delay variation. Jitter may be defined or explained as a variation in data flow, which may be due to congestion somewhere in the path between the server and the wireless device. [00053] All these above described examples may negatively influence the QoE. The analytics information may also, or alternatively, comprise information pertaining to estimated QoE and/or specific QoE requirements for the traffic flow, i.e. for the service being delivered or provided by the traffic flow.

[00054] Generally, any delay may be determined by the analytics arrangement by some type or packet inspection. In the simplest case, if the packet is time stamped at the sender, i.e. the server (which is a node outside the wireless communication network), the analytics arrangement may simple determine the current time and compare the current time to the time stamp. In this manner, the difference between the current time and the time stamp is an indication of the time passed from when the server transmitted the packet and until it has reached the node/device in which the analytics arrangement is implemented/comprised.

[00055] In case time stamp is not available, then delay may be estimated by measuring the time between a packet and the corresponding ACK passes the analytics arrangement.

[00056] The obtaining 120 of the QoE may comprise (I) processing the obtained analytics information to determine or estimate the QoE, or (II) obtaining the QoE from the obtained analytics information, the QoE then being comprised in the obtained analytics information.

[00057] As described above, the analytics information may comprise information about delay and latency, e.g. by indicating (i) packet delay, (ii) number of dropped packets, (iii) buffer bloating, (iv) jitter, and (v) ratio of dropped packets. The network node may then use this information to determine or estimate the QoE. Using the estimated or determined QoE, the network node may assess whether it is possible to meet the end-to-end QoE for the service associated with the packet and traffic flow.

[00058] Alternatively, the analytics information does already comprise this information, wherein the network node may simply have to extract the QoE from the analytics information. [00059] The network node needs to identify the different service/traffic flows. In this case the QoE requirements of the different flows may be stored for example in a database the network node has access to. Once the network node identifies the service/traffic flow, it may retrieve the related QoS requirements from the database, and then combine this with the information received from the analytics arrangement of the delay (and other traffic characteristics).

[00060] The performing 140 of one or more actions for the wireless device may comprise, when the obtained QoE does not meet a QoE threshold for the service associated with the service and/or the load of the network node meets a load threshold: (i) scheduling radio resources to or from one or more other wireless device before scheduling radio resources to the wireless device, (ii) discarding acknowledgement(s), ACK(s), (iii) holding packets of the traffic flow thereby delaying ACKs and reducing the speed of the flow, (iv) discarding packets of the traffic flow, (v) refraining from activating Carrier Aggregation or Dual Connectivity for the wireless device, (vi) giving the wireless device a lower priority compared to other wireless devices, (vii) triggering mobility actions for the wireless device, and/or (viii) activating wireless device specific energy savings.

[00061 ] There are different options available for the network node in order to cope with a situation in which the estimated or determined QoE associated with the service currently being provided to the wireless device are not likely to meet the QoE requirements. In case it is not possible, or not very likely that the QoE requirements will be fulfilled, the network node may down-prioritise the wireless device, thereby possibly increasing the probability that the QoE associated with other services for other wireless devices may be met. In other words, if one service being provided to a wireless device is possible to fulfil the QoE

requirements and the service provided to the wireless in question is not likely to fulfil the QoE requirements, the network node may prioritise the wireless device for which it is possible to fulfil the QoE requirements over the wireless device in question for which it is not possible or likely to fulfil the QoE requirements. Down- prioritising the wireless device may comprise (i) scheduling radio resources to or from one or more other wireless device before scheduling radio resources to the wireless device and/or giving the wireless device a lower priority compared to other wireless devices.

[00062] Another option for the network node is to discard ACK(s) sent to/from the wireless device for which it is not possible or likely to fulfil the QoE requirements. In this manner, the amount of traffic, or the load of the network node, may be reduced (by TCP backing-off) thereby freeing capacity for e.g. packets of other services. Still another option is to hold packets of the traffic flow thereby delaying ACKs and reducing the speed of the flow. In case the QoE requirements are not possible to fulfil, the network node may further hold packets of the traffic flow even though that may further deteriorate the QoE for that service. However, doing so may further increase the possibility of fulfilling QoE requirements for other ongoing services being provided or delivered to wireless device being served by the network node.

[00063] Yet another option available to the network node is to simply discard packets of the traffic flow destined to, or received from, the wireless device. Doing so may further deteriorate the QoE for the service being provided or delivered to the wireless device, but it will also free resources for the network node that the network node may assign to other wireless devices currently being served by the network node and engaged in different services.

[00064] The network node may further refrain from awarding or assigning additional resources to the wireless device, such as Carrier Aggregation and/or dual connectivity. Instead, such resources may be assigned to other wireless devices.

[00065] Other options available to the network node are to triggering mobility actions for the wireless device, and/or activating/re-configuring wireless device specific energy savings such as Discontinuous Reception (DRX). For example, the network node may initiate a handover of the wireless device to a neighbouring network node if possible, e.g. if the network node is relatively close to a cell edge of both the serving network node, i.e. the one currently being responsible for scheduling resources to the wireless device, and the neighbouring network node. [00066] The traffic flow may be identified by (a) when the analytics information is received from an analytics arrangement implemented in either the wireless device or in another node in or outside the wireless communication network: being comprised in the analytics information, or (b) when the analytics information is determined by analysing the traffic flow: (b1 ) identifying a bearer by means of which the traffic flow is provided to the wireless device, or (b2) an identifier on the traffic flow.

[00067] Different traffic flows may be associated with different services and different wireless devices. Depending on whether the network node itself analysis the traffic flow and thereby determines the analytics information or receives the analytic information from the analytics arrangement being implemented in another node or the wireless device, the traffic flow may be identified in different ways.

[00068] In the case when the analytics information is received from the analytics arrangement being implemented in either the wireless device or in another node in or outside the wireless communication network, the analytics information may already have identified the traffic flow and incorporates the identity of the traffic flow in the analytics information before sending it, or providing it, to the network node. In this manner, the network node may simply extract the identity of the traffic flow from the analytics information.

[00069] In the case when the network node itself performs the analysis of the traffic flow, e.g. when the analytics arrangement is comprised or implemented in the network node, the network node may identify the traffic flow by analysing it. This may in turn be done in different ways. In a first example, the network node may identify the bearer by means of which the traffic flow is provided to the wireless device. A bearer may be characterised by different features, e.g. different QoS services related characteristics and specific service and traffic flows mapped to a bearer. The traffic flow may be associated with a bearer by means of which the packet(s) of the traffic flow are being delivered or provided to the wireless device. Thus, the traffic flow may be identified by means of the bearer. A bearer carries traffic in the form of IP packets. Which traffic is carried on a bearer is defined by filters. A filter is an n-tuple where each element in the tuple contains a value, a range, or a wildcard. An n-tuple is also known as an IP flow. An example of a 5-tuple is (dst IP=83.50.20.1 10, src IP=145.45.68.201 , dst port=80, src port=^*, prot=TCP). This 5-tuple defines a source and destination IP address, a source and destination port, and a protocol. The source port is a wildcard. Traffic matching this 5-tuple filter would be all TCP traffic from IP=145.45.68.201 to IP=83.50.20.1 10 and port=80. In a second example, the traffic flow is associated with an identity, which may be comprised in packet(s) of the traffic flow. The identity may be a n- tuple or a 5-tuple or other packet marking in the packet itself.

[00070] The method may further comprise, as illustrated in figure 1c, transmitting 105 a test packet to generate the traffic flow.

[00071 ] Instead of analysing packets of a traffic flow providing a service to the wireless device, the network node, or the analytics arrangement, may transmit one or more test packets to form a traffic flow to perform analysis on. The test packet may travel the same path as a packet of the traffic flow providing the service and thereby estimation of e.g. delay could be done on the test packet if no traffic exist at the moment.

[00072] The test packets may thus be used to perform the analysis as described above. The test packets may e.g. be inserted into an existing traffic flow that is providing a service to the wireless device. In this manner, the test packets may be more easily inspected without having to perform e.g. deep packet inspection in order to analyse the packets and the compile the analytics information.

[00073] The network node may be one of a Node B, evolved Node B (eNB), Base Station (BS), and Radio Network Controller (RNC), and Base Station Controller (BSC).

[00074] Depending on the technology implemented in the wireless

communication system, the network node responsible for scheduling of radio resources to the wireless device, the network node may be any of the above.

Merely as an example, if the network node is operating in a Long Term Evolution, LTE, (also known as 4G) based wireless communication network, the network node may be an eNB or Radio Base Station, RBS. If the network node is operating in a Universal Mobile Telecommunications System, UMTS, (also known as 3G) based wireless communication network, the network node may be a BS, an RNC, or an RBS. If the network node is operating in a Global System for Mobile

Communications, GSM, (also known as 3G) based wireless communication network, the network node may be a BS, an RBS or a BSC.

[00075] It shall be pointed out that these examples are not exhaustive. For example, the network node may be an access point in a Wi-Fi or Wireless Local Area Network, WLAN, or in a network node of a 5G communication network.

[00076] The network node is responsible for scheduling of radio resources to the wireless device and therefore, the network node may perform different actions with regard to the wireless device and/or the service being provided to the wireless device depending on the overall load of the network node and/or the current situation for the service being provided to the network node as described in detail above.

[00077] Embodiments herein also relate to a method performed by an analytics arrangement implemented in a wireless device or in a node in or outside a wireless communication network.

[00078] Embodiments of such a method will now be described with reference to figure 2. Figure 2 illustrates the method 200 comprising receiving 210 one or more packets of a traffic flow between the wireless device and a node outside the wireless communication network; analysing 220 the traffic flow based on the received one or more packets; and providing 230 the analysis as analytics information to a network node responsible for scheduling of radio resources to the wireless device.

[00079] The analytics arrangement may be implemented in the wireless device or in a node in or outside a wireless communication network. However, the network node may alternatively itself perform the actions or method of the analytics arrangement as described above. Thus, in an exemplifying embodiment, the analytics arrangement may alternatively be implemented in the network node responsible for scheduling of resources to the wireless device.

[00080] The analytics arrangement receives one or more packets of a traffic flow between the wireless device and a node outside the wireless communication network. This means that the analytics arrangement is implemented in either the wireless device or in an intermediate node in the path of the traffic flow between the wireless device and a server providing the service to the wireless device. The server is a node outside the wireless communication network. It shall again be pointed out that there may be one of more nodes outside the wireless

communication network that are "part of" the traffic flow, i.e. that are intermediate nodes between the wireless device and the server.

[00081 ] Once the one or more packets is/are received by the analytics

arrangement, i.e. the one or more packets is/are received by the node in which the analytics arrangement is implemented, the analytics arrangement may analyse the traffic flow based on the received one or more packets. Based on the analysis, the analytics arrangement may compile analytics information associated with the traffic flow. Then the analytics arrangement provides the analysis, i.e. the analytics information, to a network node responsible for scheduling of radio resources to the wireless device. In this manner, the analytics information is provided to the network node so that it may take appropriate actions with regard to the situation for the service and/or wireless device, as described above.

[00082] The method performed by the arrangement has the same advantages as the method performed by the network node. One possible advantage is that the network node may be enabled or allowed to act on performance related

information normally only available to the client application in order to improve the overall end-user perceived performance in the network.

[00083] The analysis may comprise analysing one or more of (i) packet delay, (ii) number of dropped packets, (iii) buffer bloating, (iv) jitter, (v) ratio of dropped packets, (vi) estimated QoE, and (vii) specific QoE requirements for the traffic flow. [00084] As described above, due to congestion in one or more nodes in the path may result in a delay of the packet(s) passing that/those node(s) since they will have to wait at that/those node(s) before being forwarded towards the wireless device. Such a congestion may also result in packets being dropped. Buffer bloating refers to excess buffering of packets resulting in high latency and packet delay variation. Jitter may be defined or explained as a variation in data flow, which may be due to congestion somewhere in the path between the server and the wireless device.

[00085] The Radio Resource Management, RRM, in the Radio Access Network, RAN, allocates radio resources to govern the service performance in the wireless communication network by functions like radio link adaptation, radio scheduling, discontinuous transmission and reception, admission control, mobility load balancing, etc. The functions operate using information in control plane e.g. based on measurements made by the network or by wireless devices currently being served by, or connected to, network nodes in the RAN. This adds the possibility to use the analytics information as input to RRM.

[00086] The main objective of RRM is to maximise the amount of "satisfied traffic", given the restrictions of the situation, e.g.:

• UE capabilities

• Cell capabilities (of potentially serving cells)

• Radio link quality for each pair of UE-cell and UL/DL

• Traffic demands (services) per UE

• UE velocity

• Network (cell) topology

[00087] The concept of "satisfied traffic" is generally interpreted as "meeting the Quality of Service, QoS, parameters" for the traffic bearers, assuming that service (application) data flows are mapped onto bearers.

[00088] Figure 3a illustrates a radio scheduler selecting a queue of highest priority to be sent to the associated wireless device. The queues are associated with radio access bearers of a certain QoS class. The QoS class may define a priority level, but RAN may also take other input when deciding the priority used by the scheduler.

[00089] Figure 3b illustrates an example of an end-to-end service between a wireless device and an Over-The-Top, OTT, server in the Internet. The end-to-end traffic flow, or service flow, traverses multiple different networks and network nodes. Any of the nodes on the traffic path may impact the QoE as experienced by the end user. The first part as seen from the wireless device's side is the different nodes in the mobile operator network RAN and Core Network, CN, and examples of these are the eNodeB, the Serving GW and the PDN-GW. After the traffic leaves the network of the mobile operator, it enters the Internet and traverses multiple different routers on its way to the OTT server. The internet part is likely to comprise multiple different networks as well driven by different internet operators.

[00090] In the art and in this disclosure, "analytics" means turning data into information and insights that serve as a basis for decision making and triggering of actions. Analytics may broadly be grouped into Batch Analytics and Stream

Analytics. Batch Analytics is performed on data that is stored before it is

processed and Stream Analytics is performed on data in real-time before it is stored. Both have their merits and are used for different purposes. Batch processing is generally used for trend analytics collected over longer time periods, whereas stream processing is generally needed when analytics is used for controlling systems in real-time. The combination of historic- and real time data is powerful and allows for better decisions and the ability to take the right actions. Analytics may be used for reactive and proactive actions. Reactive means acting after something has happened and proactive means taking measures to avoid that it happens.

[00091 ] Figure 3c illustrates on a high level that "analytics" may be performed in different parts of the network. An analytics function is shown in the eNodeB, the MME, the Serving GW, PDN-GW, routers, and OTT-server as examples. In addition, network level analytics (not shown in figure 3c) may mean that the information collected from the different analytics functions in the network may be collected to a more central network level database. This may then enable analytics functionality on network level. The analytics function may be implemented in the form of the analytics arrangement as described above.

[00092] Still another important and interesting area is the usage of the collected and analysed information. This may also be performed on different levels, for example in a distributed variant, the analytics arrangement in the eNB performs local actions and feeds the analysed information back to the eNB logic such as RRM. Therefore in this case the "analytics" may be seen as local actions.

[00093] In another example, a more centralised variant of "Analytics" is

performed on network level. Information from multiple sources may be collected to the more central network database. In addition, information from this central network database may be fed back to the existing network functions. In one example such information is sent back to the eNB logic such as RRM allowing possible new use cases and functionality based on this new information available.

[00094] As described above, many nodes are involved in delivering user data from the server to the client (as illustrated by examples in figures 3b and 3c). The data packets of the traffic flow will for example pass a number of routers in the transport network (or Internet). When one of these routers gets congested, this router will probably add delay to the path between client and server, i.e. the wireless device and the OTT server depicted in figures 3b and 3c. For example, one already active Transport Control Protocol, TCP, flow (with large congestion window) may send a burst of packets to a router, filling up the buffer so that a packet from a new TCP flow (with small congestion window) have to wait a long time before being transmitted. This is often referred to as buffer-bloat. When congestion gets really severe, the router will also start to drop packets. All this will affect end user QoE negatively.

[00095] With the analytics arrangement/function placed in the user data flow, monitoring the packets, the occurrence of congestion could be observed by collecting information about e.g. packet delay, dropped packets and jitter. By providing this information about impact on end user QoE from bottlenecks inside or outside the wireless communication network is forwarded to the RAN scheduler, the RAN scheduler may use this information e.g. in the scheduling decision but also in other ways as described above by e.g. refraining from activating Carrier Aggregation or Dual Connectivity for the wireless device, giving the wireless device a lower priority compared to other wireless devices, triggering mobility actions for the wireless device, and/or activating wireless device specific energy savings. The RAN scheduler is comprised in the network node responsible for scheduling of resources.

[00096] As a first example, a packet already affected by a congested router so that significant delay has been added to the transmission from server to the wireless device could be slightly delayed in the RAN scheduler without additional large impact on end user QoE. This means that the RAN scheduler, i.e. the network node responsible for scheduling, could allow to be slightly more

Opportunistic' in the scheduling of this packet. By being more opportunistic, there is e.g. possibility for the scheduler to wait for an occasion with better radio condition or to prioritise a wireless device with more urgent data or a flow that still has the possibility to meet the end-to-end QoE.

[00097] A second example is that with the information about buffer-bloat occurring outside of RAN, the RAN scheduler could 'throttle' the flow that is causing the buffer bloat by 'holding' packets in the scheduler, thereby delaying ACKs and reducing the speed of the flow. Other solutions also exist for these buffer bloat problems, e.g. information about the buffer bloat could also be sent to the end points of the communication, i.e. the wireless device and/or the server that could then directly impact/reduce the speed of the flow.

[00098] Figure 3d illustrates an example of the case when RAN-internal analytics is performed in the RAN/eNB, e.g. in the network node responsible for scheduling of resources, and the analysis result is also used locally in RAN. The analytics function in the eNB estimates what is the total delay for a service/traffic flow between the eNB and the OTT server. The analytics function may in an example be realized by the above described analytics arrangement being implemented in the eNB, i.e. the network node responsible for scheduling of resources. [00099] In one embodiment this is performed by analysing traffic (i.e. packet(s) of the traffic flow) sent between the wireless device and the OTT server being the node outside the wireless communication network. The network node measures the delay (and other traffic characteristics) between the network node and the OTT server. In addition, the network node also needs to identify the different service flows and have knowledge about the QoE requirements for these flows as described above. Based on all this information, the network node may know when it is still possible to meet the end-to-end QoE or when it would be feasible to e.g. temporarily down-prioritise a traffic flow.

[000100] In another embodiment, the network node may inject test traffic packets to test the properties of the network between the OTT server and the network node. The possibility to perform this embodiment depends on the end-to- end service protocol used between the wireless device and the OTT server (i.e. if the used protocol enables test packets e.g. in the form of "ping"-packets or resent application packets).

[000101 ] Figure 3e illustrates an example of the case when RAN-external analytics is performed on the network side and the analysis result is then sent to the RAN/network node. The analytics arrangement/function estimates what is the end-to-end delay (and other traffic characteristics) for a service/traffic flow between the node in which the analytics arrangement is implemented and the OTT server. The analytics arrangement may also estimate the delay and other traffic characteristics between the "node in which analytics arrangement is implemented and the current network node of the wireless device (in case this part would also provide dynamically varying characteristics).

[000102] Also in this case there are two different embodiments i.e. the analysis is performed either by analysing traffic sent between the wireless device and the OTT server or by injecting test traffic packets to test the properties of the network between the OTT server and the node in which the analytics arrangement is implemented. And also in this case, the analytics arrangement needs to identify the different service flows and have knowledge about the QoE requirements for these flows. Note that figure 3e illustrates the analytics arrangement in the PDN- GW and this is just an example. Other placement is for example SGW, or a new node/function on the S1 -U, S5 or SGi interfaces. Also note that figures 3b-3e illustrate a wireless communication network based on LTE, which is merely also an example as the wireless communication network may be based on other technologies as described above.

[000103] Figure 3f illustrates an example of the case when RAN-external analytics is performed on the wireless device side (i.e. the analytics arrangement is implemented in the wireless device) and the analysis result is then sent to RAN, i.e. the network node responsible for scheduling of resources. The analytics arrangement may estimate what is the end-to-end delay (and other traffic characteristics) for a service/traffic flow between the analytics arrangement (i.e. the wireless device in this example) and the OTT server. The analytics

arrangement may then provide the analysed information to the RAN/network node, and as RAN may know the delay (and other traffic characteristics) for the service/traffic flow over the air interface, then RAN also becomes aware of the delay (and other traffic characteristics) between the network node and the OTT server.

[000104] In this case analysis is generally performed by analysing traffic sent between the wireless device and the OTT server. It is however also possible for the wireless device to inject test traffic packets to test the properties of the network towards the OTT server. This may be beneficial for the case when a connection towards a specific destination would need to be checked in advance to any real traffic sent. And also in this case, the analytics arrangement or the network node responsible for scheduling of resources needs to identify the different service flows and have knowledge about the QoE requirements for these flows.

[000105] An aspect of this disclosure is for the network node to understand the QoE requirements for the different service/traffic flows. There are different ways to perform this. In a first example, the analytics arrangement is also able to identify these QoE requirements and then this information may be passed on, or provided, to the network node together with the analysis of the delay (and other traffic characteristics), i.e. the analytics information. In this case the network node doesn't really need to identify the different service/traffic flows as all needed information is received from the analytics function (although this may be beneficial in the case the wireless device has multiple simultaneous service/traffic flows).

[000106] In a second example, the network node needs to identify the different service/traffic flows. In this case the QoE requirements of the different flows may be stored for example in a database the network node has access to. Once the network node identifies the service/traffic flow, it may retrieve the related QoS requirements from the database, and then combine this with the information received from the analytics arrangement of the delay (and other traffic

characteristics).

[000107] The possible actions performed by the network node may be different in uplink and downlink. In the downlink, the network node may be aware of the traffic (and the related traffic characteristics and QoE requirements) to be sent to the wireless device and may really be aware of when a specific traffic is scheduled for the wireless device. In uplink, the actions performed by the network node may be somewhat limited as the network node does know that the wireless device has something in the uplink buffers but the network node don't really have control over which traffic the wireless device eventually selects to send in the uplink. The uplink vs downlink aspect is therefore important for the multi service/traffic flow aspect for a wireless device. If the wireless device has a single traffic flow active then actions also taken by the network node for the uplink may be controlled and impact the correct single flow. The same doesn't apply for multi service/traffic flow as described above. In the downlink, the multi service/traffic flow case is solved by the network node being able to identify the different service/traffic flows and maintaining the related traffic characteristics and QoE requirements for each flow separately. This is needed for the network node to be able to handle the multiple service/traffic flows in a different way, and based on the QoE requirements and traffic characteristics.

[000108] Embodiments herein also relate to a network node responsible for scheduling of radio resources to a wireless device, the network node and the wireless device being operable in a wireless communication network, wherein the wireless device is engaged in communication with a node outside the wireless communication network thereby generating a traffic flow between the wireless device and the node outside the wireless communication network. The network node has the same technical features, objects and advantages as the method performed by the network node. Hence, the network node will only be described in brief in order to avoid unnecessary repetition.

[000109] Embodiments of such a network node will now be described with reference to figures 4 and 5. Figures 4 and 5 illustrate the network node 400, 500 being configured for obtaining analytics information of the traffic flow between the wireless device and the node outside the wireless communication network; for obtaining a Quality of Experience, QoE, for a service associated with the traffic flow; and for performing one or more actions for the wireless device based on the obtained analytics information and on the obtained QoE.

[0001 10] The network node may be realised on implemented in various ways. A first exemplifying realisation or implementation is illustrated in figure 4. Figure 4 illustrates the network node 400 comprising a processor 421 and memory 422, the memory comprising instructions, e.g. by means of a computer program 423, which when executed by the processor 421 causes the network node 400 to obtain analytics information of the traffic flow between the wireless device and the node outside the wireless communication network; to obtain a Quality of Experience, QoE, for a service associated with the traffic flow; and to perform one or more actions for the wireless device based on the obtained analytics information and on the obtained QoE.

[0001 1 1 ] Figure 4 also illustrates the network node 400 comprising a memory 410. It shall be pointed out that figure 4 is merely an exemplifying illustration and memory 410 may be optional, be a part of the memory 422 or be a further memory of the network node 400. The memory may for example comprise information relating to the network node 400, to statistics of operation of the network node 400, just to give a couple of illustrating examples. Figure 4 further illustrates the network node 400 comprising processing means 420, which comprises the memory 422 and the processor 421 . Still further, figure 4 illustrates the network node comprising a communication unit 430. The communication unit 430 may comprise an interface through which the network node 400 communicates with other nodes or entities of or outside the wireless communication network as well as other communication units. Figure 4 also illustrates the network node 400 comprising further functionality 440. The further functionality 440 may comprise hardware of software necessary for the network node 400 to perform different tasks that are not disclosed herein.

[0001 12] An alternative exemplifying realisation, or implementation, of the network node 400, 500 is illustrated in figure 5. Figure 5 illustrates the network node 500 comprising an obtaining unit 503 for obtaining analytics information of the traffic flow between the wireless device and the node outside the wireless communication network; and for obtaining a Quality of Experience, QoE, for a service associated with the traffic flow. Figure 5 illustrates the network node 500 comprising a performing unit 504 for performing one or more actions for the wireless device based on the obtained analytics information and on the obtained QoE.

[0001 13] In figure 5, the network node 500 is also illustrated comprising a communication unit 501 . Through this unit, the network node 500 is adapted to communicate with other nodes and/or entities in or outside the wireless

communication network. The communication unit 501 may comprise more than one receiving arrangement. For example, the communication unit 501 may be connected to both a wire and an antenna, by means of which the network node 500 is enabled to communicate with other nodes and/or entities in the wireless communication network. Similarly, the communication unit 501 may comprise more than one transmitting arrangement, which in turn is connected to both a wire and an antenna, by means of which the network node 500 is enabled to communicate with other nodes and/or entities in the wireless communication network. The network node 500 further comprises a memory 502 for storing data. Further, the network node 500 may comprise a control or processing unit (not shown) which in turn is connected to the different units 503-504. It shall be pointed out that this is merely an illustrative example and the network node 500 may comprise more, less or other units or modules which execute the functions of the network node 500 in the same manner as the units illustrated in figure 5.

[0001 14] It should be noted that figure 5 merely illustrates various functional units in the network node 500 in a logical sense. The functions in practice may be implemented using any suitable software and hardware means/circuits etc. Thus, the embodiments are generally not limited to the shown structures of the network node 500 and the functional units. Hence, the previously described exemplary embodiments may be realised in many ways. For example, one embodiment includes a computer-readable medium having instructions stored thereon that are executable by the control or processing unit for executing the method steps in the network node 500. The instructions executable by the computing system and stored on the computer-readable medium perform the method steps of the network node 500 as set forth in the claims.

[0001 15] The method performed by the network node has the same advantages as the method performed by the network node. One possible advantage is that the network node may be enabled or allowed to act on performance related

[0001 16] According to an embodiment, the network node is further configured for determining the load of the network node.

[0001 17] According to yet an embodiment, the network node is further configured for performing the one or more actions for the wireless device further based on the determined load of the network node.

[0001 18] According to still an embodiment, the network node is configured for obtaining the analytics information by (a) receiving the analytics information from an analytics arrangement implemented in either the wireless device or in another node in or outside the wireless communication network, or (b) determining the analytics information by analysing the traffic flow. [0001 19] According to a further embodiment, the analytics information comprises one or more of (i) packet delay, (ii) number of dropped packets, (iii) buffer bloating, (iv) jitter, (v) ratio of dropped packets, (vi) estimated QoE, and (vii) specific QoE requirements for the traffic flow.

[000120] According to another embodiment, the network node is configured for obtaining the QoE by (I) processing the obtained analytics information to determine or estimate the QoE, or (II) obtaining the QoE from the obtained analytics information, the QoE then being comprised in the obtained analytics information.

[000121 ] According to yet an embodiment, the network node is configured for performing the one or more actions for the wireless device by, when the obtained QoE does not meet a QoE threshold for the service associated with the service and/or the load of the network node meets a load threshold: (i) scheduling radio resources to or from one or more other wireless device before scheduling radio resources to the wireless device, (ii) discarding acknowledgement(s), ACK(s), (iii) holding packets of the traffic flow thereby delaying ACKs and reducing the speed of the flow, (iv) discarding packets of the traffic flow, (v) refraining from activating Carrier Aggregation or Dual Connectivity for the wireless device, (vi) giving the wireless device a lower priority compared to other wireless devices, (vii) triggering mobility actions for the wireless device, and/or (viii) activating wireless device specific energy savings

[000122] According to still an embodiment, the traffic flow is identified by (a) when the analytics information is received from an analytics arrangement implemented in either the wireless device or in another node in or outside the wireless communication network: being comprised in the analytics information, or (b) when the analytics information is determined by analysing the traffic flow: (b1 ) identifying a bearer by means of which the traffic flow is provided to the wireless device, or (b2) an identifier on the traffic flow.

[000123] According to a further embodiment, the network node is further configured for transmitting a test packet to generate the traffic flow. [000124] According to an embodiment, the network node is one of a Node B, evolved Node B, Base Station, and Radio Network Controller, Base Station Controller.

[000125] Embodiments herein also relate to an analytics arrangement implemented in a wireless device or in a node in or outside a wireless

communication network. The analytics arrangement has the same technical features, objects and advantages as the method performed by the analytics arrangement. Hence, the analytics arrangement will only be described in brief in order to avoid unnecessary repetition.

[000126] Embodiments of such an analytics arrangement will now be described with reference to figures 6 and 7. Figures 6 and 7 illustrate the analytics arrangement 600, 700 being configured for receiving one or more packets of a traffic flow between the wireless device and a node outside the wireless

communication network; for analysing the traffic flow based on the received one or more packets; and for providing the analysis as analytics information to a network node responsible for scheduling of radio resources to the wireless device.

[000127] The analytics arrangement may be realised on implemented in various ways. A first exemplifying realisation or implementation is illustrated in figure 6. Figure 6 illustrates the analytics arrangement comprising a processor 621 and memory 622, the memory comprising instructions, e.g. by means of a computer program 623, which when executed by the processor 621 causes the analytics arrangement 600 to operable to receive one or more packets of a traffic flow between the wireless device and a node outside the wireless communication network; analyse the traffic flow based on the received one or more packets; and to provide the analysis as analytics information to a network node responsible for scheduling of radio resources to the wireless device.

[000128] Figure 6 also illustrates the analytics arrangement 600 comprising a memory 610. It shall be pointed out that figure 6 is merely an exemplifying illustration and memory 610 may be optional, be a part of the memory 622 or be a further memory of the analytics arrangement 600. The memory may for example comprise information relating to the analytics arrangement 600, to statistics of operation of the analytics arrangement 600, just to give a couple of illustrating examples. Figure 6 further illustrates the analytics arrangement 600 comprising processing means 620, which comprises the memory 622 and the processor 621 . Still further, figure 6 illustrates the analytics arrangement 600 comprising a communication unit 630. The communication unit 630 may comprise an interface through which the analytics arrangement 600 communicates with other nodes or entities of or outside the wireless communication network as well as other communication units. Figure 6 also illustrates the analytics arrangement 600 comprising further functionality 640. The further functionality 640 may comprise hardware of software necessary for the analytics arrangement 600 to perform different tasks that are not disclosed herein.

[000129] An alternative exemplifying realisation, or implementation, of the analytics arrangement is illustrated in figure 7. Figure 7 illustrates the analytics arrangement 700 comprising a receiving unit 703 for receiving one or more packets of a traffic flow between the wireless device and a node outside the wireless communication network; and an analysing unit 704 for analysing the traffic flow based on the received one or more packets. Figure 7 also illustrates the analytics arrangement 700 comprising a providing unit 705 for providing the analysis as analytics information to a network node responsible for scheduling of radio resources to the wireless device.

[000130] In figure 7, the analytics arrangement 700 is also illustrated

comprising a communication unit 701 . Through this unit, the analytics arrangement 700 is adapted to communicate with other nodes and/or entities in the wireless communication network or the network outside the wireless communication network. The communication unit 701 may comprise more than one receiving arrangement. For example, the communication unit 701 may be connected to both a wire and an antenna, by means of which the analytics arrangement 700 is enabled to communicate with other nodes and/or entities in or outside the wireless communication network. Similarly, the communication unit 701 may comprise more than one transmitting arrangement, which in turn is connected to both a wire and an antenna, by means of which the analytics arrangement 700 is enabled to communicate with other nodes and/or entities in the wireless communication network. The analytics arrangement 700 further comprises a memory 702 for storing data. Further, the analytics arrangement 700 may comprise a control or processing unit (not shown) which in turn is connected to the different units 703- 705. It shall be pointed out that this is merely an illustrative example and the analytics arrangement 700 may comprise more, less or other units or modules which execute the functions of the analytics arrangement 700 in the same manner as the units illustrated in figure 7.

[000131 ] It should be noted that figure 7 merely illustrates various functional units in the analytics arrangement 700 in a logical sense. The functions in practice may be implemented using any suitable software and hardware means/circuits etc. Thus, the embodiments are generally not limited to the shown structures of the analytics arrangement 700 and the functional units. Hence, the previously described exemplary embodiments may be realised in many ways. For example, one embodiment includes a computer-readable medium having instructions stored thereon that are executable by the control or processing unit for executing the method steps in the analytics arrangement 700. The instructions executable by the computing system and stored on the computer-readable medium perform the method steps of the analytics arrangement 700 as set forth in the claims.

[000132] The analytics arrangement has the same possible advantages as the method performed by the wireless device. One possible advantage is that the network node may be enabled or allowed to act on performance related

[000133] According to an embodiment, the analysis comprises analysing one or more of (i) packet delay, (ii) number of dropped packets, (iii) buffer bloating, (iv) jitter, (v) ratio of dropped packets, (vi) estimated QoE, and (vii) specific QoE requirements for the traffic flow. [000134] Figure 8 schematically shows an embodiment of an arrangement 800 in a network node 500 responsible for scheduling of radio resources to a wireless device. Comprised in the arrangement 800 in the network node 500 are here a processing unit 806, e.g. with a Digital Signal Processor, DSP. The processing unit 806 may be a single unit or a plurality of units to perform different actions of procedures described herein. The arrangement 800 of ,or in, the network node 500 may also comprise an input unit 802 for receiving signals from other entities, and an output unit 804 for providing signal(s) to other entities. The input unit and the output unit may be arranged as an integrated entity or as illustrated in the example of figure 5, as one or more interfaces 501 .

[000135] Furthermore, the arrangement in the network node 500 comprises at least one computer program product 808 in the form of a non-volatile memory, e.g. an Electrically Erasable Programmable Read-Only Memory, EEPROM, a flash memory and a hard drive. The computer program product 808 comprises a computer program 810, which comprises code means, which when executed in the processing unit 806 in the arrangement 800 in the network node 500 causes the network node 500 to perform the actions e.g. of the procedure described earlier in conjunction with figures 1a-1c.

[000136] The computer program 810 may be configured as a computer program code structured in computer program modules 810a-810e. Hence, in an

exemplifying embodiment, the code means in the computer program of the arrangement 800 in the network node comprises an obtaining unit, or module, for obtaining analytics information of the traffic flow between the wireless device and the node outside the wireless communication network; for obtaining a QoE for a service associated with the traffic flow. The code means in the computer program of the arrangement 800 in the network node 500 further comprises a performing unit, or module, for performing one or more actions for the wireless device based on the obtained analytics information and on the obtained QoE.

[000137] The computer program modules could essentially perform the actions of the flow illustrated in figures 1a-1c, to emulate the network node 500. In other words, when the different computer program modules are executed in the processing unit 806, they may correspond to the units 503 and 504 of figure 5.

[000138] Figure 9 schematically shows an embodiment of an arrangement 900 in an analytics arrangement 700. Comprised in the arrangement 900 are here a processing unit 906, e.g. with a Digital Signal Processor. The processing unit 906 may be a single unit or a plurality of units to perform different actions of

procedures described herein. The arrangement 900 may also comprise an input unit 902 for receiving signals from other entities, and an output unit 904 for providing signal(s) to other entities. The input unit and the output unit may be arranged as an integrated entity or as illustrated in the example of figure 7, as one or more interfaces 701 .

[000139] Furthermore, the arrangement 900 in the analytics arrangement 700 comprises at least one computer program product 908 in the form of a non-volatile memory, e.g. an Electrically Erasable Programmable Read-Only Memory,

EEPROM, a flash memory and a hard drive. The computer program product 908 comprises a computer program 910, which comprises code means, which when executed in the processing unit 906 in the arrangement 900 in the analytics arrangement 700 causes the analytics arrangement 700to perform the actions e.g. of the procedure described earlier in conjunction with figure 2.

[000140] The computer program 910 may be configured as a computer program code structured in computer program modules 910a-910e. Hence, in an

exemplifying embodiment, the code means in the computer program of the arrangement 900 in the analytics arrangement 700 comprises a receiving unit, or module, for receiving one or more packets of a traffic flow between the wireless device and a node outside the wireless communication network; and an analysing unit, or module, for analysing the traffic flow based on the received one or more packets; The computer program further comprises a providing unit, or module, for providing the analysis as analytics information to a network node responsible for scheduling of radio resources to the wireless device. [000141 ] The computer program modules could essentially perform the actions of the flow illustrated in figure 2, to emulate the analytics arrangement 700. In other words, when the different computer program modules are executed in the processing unit 906, they may correspond to the units 703-705 of figure 7.

[000142] Although the code means in the respective embodiments disclosed above in conjunction with figures 5 and 7 are implemented as computer program modules which when executed in the respective processing unit causes the network node and the analytics arrangement respectively to perform the actions described above in the conjunction with figures mentioned above, at least one of the code means may in alternative embodiments be implemented at least partly as hardware circuits.

[000143] The processor may be a single Central Processing Unit, CPU, but could also comprise two or more processing units. For example, the processor may include general purpose microprocessors; instruction set processors and/or related chips sets and/or special purpose microprocessors such as Application Specific Integrated Circuits, ASICs. The processor may also comprise board memory for caching purposes. The computer program may be carried by a computer program product connected to the processor. The computer program product may comprise a computer readable medium on which the computer program is stored. For example, the computer program product may be a flash memory, a Random-Access Memory RAM, Read-Only Memory, ROM, or an EEPROM, and the computer program modules described above could in alternative embodiments be distributed on different computer program products in the form of memories within the network node and the analytics arrangement respectively.

[000144] It is to be understood that the choice of interacting units, as well as the naming of the units within this disclosure are only for exemplifying purpose, and nodes suitable to execute any of the methods described above may be configured in a plurality of alternative ways in order to be able to execute the suggested procedure actions. [000145] It should also be noted that the units described in this disclosure are to be regarded as logical entities and not with necessity as separate physical entities.

[000146] While the embodiments have been described in terms of several embodiments, it is contemplated that alternatives, modifications, permutations and equivalents thereof will become apparent upon reading of the specifications and study of the drawings. It is therefore intended that the following appended claims include such alternatives, modifications, permutations and equivalents as fall within the scope of the embodiments and defined by the pending claims.

Claims

1 . A method (100) performed by a network node responsible for scheduling of radio resources to a wireless device, the network node and the wireless device being operable in a wireless communication network, wherein the wireless device is engaged in communication with a node outside the wireless communication network thereby generating a traffic flow between the wireless device and the node outside the wireless communication network, the method comprising:

- obtaining (1 10) analytics information of the traffic flow between the wireless device and the node outside the wireless communication network,

- obtaining (120) a Quality of Experience, QoE, for a service associated with the traffic flow, and

- performing (140) one or more actions for the wireless device based on the obtained analytics information and on the obtained QoE.

2. The method (100) according to claim 1 , further comprising determining (130) the load of the network node.

3. The method (100) according to claim 2, wherein the performing (140) one or more actions for the wireless device is further based on the determined load of the network node.

4. The method (100) according to any of claims 1 -3, wherein the obtaining of the analytics information comprises (a) receiving the analytics information from an analytics arrangement implemented in either the wireless device or in another node in or outside the wireless communication network, or (b) determining the analytics information by analysing the traffic flow.

5. The method (100) according to any of claims 1 -4, wherein the analytics information comprises one or more of (i) packet delay, (ii) number of dropped packets, (iii) buffer bloating, (iv) jitter, (v) ratio of dropped packets, (vi) estimated QoE, and (vii) specific QoE requirements for the traffic flow.

6. The method (100) according to any of claims 1 -5, wherein the obtaining (120) of the QoE comprises (I) processing the obtained analytics information to determine or estimate the QoE, or (II) obtaining the QoE from the obtained analytics information, the QoE then being comprised in the obtained analytics information.

7. The method (100) according to any of claims 1 -6, wherein the performing (140) of one or more actions for the wireless device comprises, when the obtained QoE does not meet a QoE threshold for the service associated with the service and/or the load of the network node meets a load threshold: (i) scheduling radio resources to or from one or more other wireless device before scheduling radio resources to the wireless device, (ii) discarding acknowledgement(s), ACK(s), (iii) holding packets of the traffic flow thereby delaying ACKs and reducing the speed of the flow, (iv) discarding packets of the traffic flow, (v) refraining from activating Carrier Aggregation or Dual Connectivity for the wireless device, (vi) giving the wireless device a lower priority compared to other wireless devices, (vii) triggering mobility actions for the wireless device, and/or (viii) activating wireless device specific energy savings.

8. The method (100) according to any of claims 1 -6, wherein the traffic flow is identified by (a) when the analytics information is received from an analytics arrangement implemented in either the wireless device or in another node in or outside the wireless communication network: being comprised in the analytics information, or (b) when the analytics information is determined by analysing the traffic flow: (b1 ) identifying a bearer by means of which the traffic flow is provided to the wireless device, or (b2) an identifier on the traffic flow.

9. The method (100) according to any of claims 1 -8, further comprising transmitting (105) a test packet to generate the traffic flow.

10. The method (100) according to any of claims 1 -9, wherein the network node is one of a Node B, evolved Node B, Base Station, and Radio Network Controller, Base Station Controller.

1 1 . A method (200) performed by an analytics arrangement implemented in a wireless device or in a node in or outside a wireless communication network, the method comprising:

- receiving (210) one or more packets of a traffic flow between the wireless device and a node outside the wireless communication network,

- analysing (220) the traffic flow based on the received one or more packets, and

- providing (230) the analysis as analytics information to a network node

responsible for scheduling of radio resources to the wireless device.

12. The method (200) according to claim 1 1 , wherein the analysis comprises analysing one or more of (i) packet delay, (ii) number of dropped packets, (iii) buffer bloating, (iv) jitter, (v) ratio of dropped packets, (vi) estimated QoE, and (vii) specific QoE requirements for the traffic flow.

13. A network node (400, 500) responsible for scheduling of radio resources to a wireless device, the network node and the wireless device being operable in a wireless communication network, wherein the wireless device is engaged in communication with a node outside the wireless communication network thereby generating a traffic flow between the wireless device and the node outside the wireless communication network, the network node being configured for:

- obtaining analytics information of the traffic flow between the wireless

device and the node outside the wireless communication network,

- obtaining a Quality of Experience, QoE, for a service associated with the traffic flow, and

- performing one or more actions for the wireless device based on the

obtained analytics information and on the obtained QoE.

14. The network node (400, 500) according to claim 13, further being configured for determining the load of the network node.

15. The network node (400, 500) according to claim 14, wherein the network node is configured for performing the one or more actions for the wireless device further based on the determined load of the network node.

16. The network node (400, 500) according to any of claims 13-15, wherein the network node is configured for obtaining the analytics information by (a) receiving the analytics information from an analytics arrangement implemented in either the wireless device or in another node in or outside the wireless

communication network, or (b) determining the analytics information by analysing the traffic flow.

17. The network node (400, 500) according to any of claims 13-16, wherein the analytics information comprises one or more of (i) packet delay, (ii) number of dropped packets, (iii) buffer bloating, (iv) jitter, (v) ratio of dropped packets, (vi) estimated QoE, and (vii) specific QoE requirements for the traffic flow.

18. The network node (400, 500) according to any of claims 13-17, wherein the network node is configured for obtaining the QoE by (I) processing the obtained analytics information to determine or estimate the QoE, or (II) obtaining the QoE from the obtained analytics information, the QoE then being comprised in the obtained analytics information.

19. The network node (400, 500) according to any of claims 13-18, wherein the network node is configured for performing the one or more actions for the wireless device by, when the obtained QoE does not meet a QoE threshold for the service associated with the service and/or the load of the network node meets a load threshold: (i) scheduling radio resources to or from one or more other wireless device before scheduling radio resources to the wireless device, (ii) discarding acknowledgement(s), ACK(s), (iii) holding packets of the traffic flow thereby delaying ACKs and reducing the speed of the flow, (iv) discarding packets of the traffic flow, (v) refraining from activating Carrier Aggregation or Dual Connectivity for the wireless device, (vi) giving the wireless device a lower priority compared to other wireless devices, (vii) triggering mobility actions for the wireless device, and/or (viii) activating wireless device specific energy savings.

20. The network node (400, 500) according to any of claims 13-18, wherein the traffic flow is identified by (a) when the analytics information is received from an analytics arrangement implemented in either the wireless device or in another node in or outside the wireless communication network: being comprised in the analytics information, or (b) when the analytics information is determined by analysing the traffic flow: (b1 ) identifying a bearer by means of which the traffic flow is provided to the wireless device, or (b2) an identifier on the traffic flow.

21 . The network node (400, 500) according to any of claims 13-20, further being configured for transmitting a test packet to generate the traffic flow.

22. The network node (400, 500) according to any of claims 13-21 , wherein the network node is one of a Node B, evolved Node B, Base Station, and Radio Network Controller, Base Station Controller.

23. An analytics arrangement (600, 700) implemented in a wireless device or in a node in or outside a wireless communication network, the analytics

arrangement being configured for:

- receiving one or more packets of a traffic flow between the wireless device and a node outside the wireless communication network,

- analysing the traffic flow based on the received one or more packets, and

- providing the analysis as analytics information to a network node

responsible for scheduling of radio resources to the wireless device.

24. The analytics arrangement (600, 700) according to claim 23, wherein the analysis comprises analysing one or more of (i) packet delay, (ii) number of dropped packets, (iii) buffer bloating, (iv) jitter, (v) ratio of dropped packets, (vi) estimated QoE, and (vii) specific QoE requirements for the traffic flow.

25. A Computer program (810), comprising computer readable code means, which when run in a processing unit (806) comprised in an arrangement (800) in a network node (500) according to claims 13-21 causes the network node (500) to perform the corresponding method according to any of claims 1 -10.

26. A Computer program product (808) comprising the computer program (810) according to claim 25.

27. A Computer program (910), comprising computer readable code means, which when run in a processing unit (906) comprised in an arrangement (900) in an analytics arrangement (700) according to claims 23-24 causes the analytics arrangement (700) to perform the corresponding method according to any of claims 1 1 -12.

28. A Computer program product (908) comprising the computer program (910) according to claim 27.