STEERING DATA TRAFFIC IN COMMUNICATION WITH USER EQUIPMENT IN A WIRELESS COMMUNICATIONS NETWORK

A method performed by a first network node for steering data traffic in a communication with a User Equipment, UE, in a wireless communications network is provided. The first network node sends (601) a request to a second network node. The 5 request requests to set up an interface between the first network node hosting a first cell and a second network node hosting a second cell. The second cell is a neighbor to the first cell. The first network node receives (602) a message from the second network node over the requested set up interface. The message comprises indications indicating that: A third cell provided by a third network node is a neighbor to the second cell, the second cell 10 is supporting multi carrier connectivity towards the third cell, and the third cell is supporting multi carrier connectivity towards the second cell. The first network node determines (603) whether or not to handover the UE from the first cell to the second cell for multi carrier connectivity towards the third cell, based on the indications in the received message. The first network node then steers (604) the data traffic in the communication 15 with the UE according to the determining of whether or not to handover the UE to the second network node.

TECHNICAL FIELD

Embodiments herein relate to a network node and a method therein. In some aspects, they relate to steering data traffic in a communication with a User Equipment (UE) in a wireless communications network.

BACKGROUND

In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) and/or User Equipments (UE)s, communicate via a Wide Area Network or a Local Area Network such as a Wi-Fi network or a cellular network comprising a Radio Access Network (RAN) part and a Core Network (CN) part. The RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a Wi-Fi access point or a radio base station (RBS), which in some networks may also be denoted, for example, a NodeB, eNodeB (eNB), or gNB as denoted in Fifth Generation (5G) telecommunications. A service area or cell area is a geographical area where radio coverage is provided by the radio network node. The radio network node communicates over an air interface operating on radio frequencies with the wireless device within range of the radio network node.

3GPP is the standardization body for specify the standards for the cellular system evolution, e.g., including 3G, 4G, 5G and the future evolutions. Specifications for the Evolved Packet System (EPS), also called a Fourth Generation (4G) network, have been completed within the 3rd Generation Partnership Project (3GPP). As a continued network evolution, the new releases of 3GPP specifies a 5G network also referred to as 5G New Radio (NR).

Frequency bands for 5G NR are being separated into two different frequency ranges, Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 comprises sub-6 GHz frequency bands. Some of these bands are bands traditionally used by legacy standards but have been extended to cover potential new spectrum offerings from 410 MHz to 7125 MHz. FR2 comprises frequency bands from 24.25 GHz to 52.6 GHz. Bands in this millimeter wave range have shorter range but higher available bandwidth than bands in the FR1.

Multi-antenna techniques may significantly increase the data rates and reliability of a wireless communication system. For a wireless connection between a single user, such as UE, and a base station, the performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple-Output (MIMO) communication channel. This may be referred to as Single-User (SU)-MIMO. In the scenario where MIMO techniques is used for the wireless connection between multiple users and the base station, MIMO enables the users to communicate with the base station simultaneously using the same time-frequency resources by spatially separating the users, which increases further the cell capacity. This may be referred to as Multi-User (MU)-MIMO. Note that MU-MIMO may benefit when each UE only has one antenna. Such systems and/or related techniques are commonly referred to as MIMO.

The current 5G RAN, also referred to as NG-RAN, architecture is depicted and described in 3GPP TS 38.401v15.5.0 (see http://www.3gpp.org/ftp//Specs/archive/38_series/38.401/38401-f50.zip) inFIG.1.FIG.1depicts an overall NG RAN architecture. The NG architecture may be further described as follows:

The NG-RAN comprises of a set of gNBs connected to the Fifth Genetation Core network (5GC) through the NG.

A gNB may support Frequency Division Duplex (FDD) mode, Time Division Duplex (TDD) mode, or dual mode operation.

gNBs may be interconnected through an Xn interface.

A gNB may comprise a gNB-Central Unit (CU) and gNB-Distributed Unit (DU)s. A gNB-CU and a gNB-DU is connected via an F1 logical interface.

One gNB-DU is connected to only one gNB-CU.

It should be noted that for resiliency, a gNB-DU may be connected to multiple gNB-CU by appropriate implementation.

NG, Xn and F1 are logical interfaces. The NG-RAN is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN architecture, i.e., the NG-RAN logical nodes and interfaces between them, is defined as part of the Radio Network Layer (RNL). For each NG-RAN interface, NG, Xn, F1, the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport, signalling transport. If security protection for control plane and user plane data on TNL of NG-RAN interfaces has to be supported, Network Domain Security (NDS)/Internet Protocol (IP) (NDS/IP) 3GPP TS 33.401 shall be applied.

A gNB may also be connected to an LTE eNB via an EN-DC X2 interface. Another architectural option is that where an LTE eNB connected to the Evolved Packet Core network is connected over the NR Dual Connectivity (EN-DC) X2 interface with a so called en-gNB. The latter is a gNB not connected directly to a CN and connected via EN-DC X2 to an eNB for the sole purpose of performing dual connectivity (DC). This is shown inFIG.2depicting an overall Evolved Universal Terrestrial Access Network (E-UTRAN) architecture for EN-DC.

The architecture inFIG.1may be expanded by spitting the gNB-CU into two entities. SeeFIG.3. So, in the split architecture option, the RAN protocol stack functionality is separated in different parts. The CU-Control Plane (CP) is expected to handle the RRC layer, the CU-User Plane (UP) will handle the Packet Data Convergence Protocol (PDCP) layer and the DU will handle the Radio Link Control (RLC), Medium Access Control (MAC) and Physical (PHY) layer of the protocol stack. In some further split the DU may have separated unit that handles the PHY parts separately compared to RLC and MAC layers that are handled in a DU.

As different units handle different protocol stack functionalities, there will be a need for inter-node communication between the DU, the CU-UP and the CU-CP. This is achieved via a F1-C interface related to control plane signalling, via F1-U interface related to user plane signalling for communication between CU and DU and via E1 for communication between CU-UP and CU-CP.

The E1 interface is a logical interface. It supports the exchange of signalling information between the endpoints. From a logical standpoint, the E1 is a point-to-point interface between a gNB-CU-CP and a gNB-CU-UP. The E1 interface enables exchange of UE associated information and non-UE associated information. The E1 interface is a control interface and is not used for user data forwarding.

All the interfaces F1-C, X2 and Xn are used to communicate information about for example served cells to a neighbour node, X2 and Xn, or to a central node CU-CP, F1-C.

The interface Xn is for example used by one node for informing neighbour nodes about served cells and configuration, but also comprises information about neighbours of the served cells. This may be done both via an Xn setup and/or response procedure and in NG-RAN node in a configuration update procedure.

In Xn the setup request and/or response one node sends a message to the cells served by the node. The message is sent from one NG-RAN node to another NG-RAN node. This message is e.g. sent by a NG-RAN node to a neighbouring NG-RAN node to transfer application data for an Xn-C interface instance. There may be three ways to transform information about served cells, Setup request, setup response and configuration transfer. The two first are exchanged when the Xn interface is established and the configuration transfer is sent when one node experience a change in its configuration and needs to report this to all neighbour nodes. The Neighbour Information NR IE from 3GPP TS 38.423, ver. 16.4, is shown below.

The Neighbour Information NR IE may be used for reporting basic parameters for the neighbour cells, such as PCI and CGI. There is also frequency info that may be reported.

The IE Connectivity Support is shown below, and it is used for informing if a neighbour cell supports EN-DC or not.

The Connectivity Support IE is used to indicate the connectivity supported by a NR cell

A problem with the above prior art is reduced DL throughput, which will be explained below.

SUMMARY

As part of developing embodiments herein the inventors have identified a problem which first will be discussed.

Deployed radio networks may have a complicated topology. For example one cell (C) may have two neighbour cells (A, B) on different frequencies, but a network node serving the cell (C) may not be able to configure a UE with these neighbour cells as Secondary Cells (SCell)s due to limited hardware (HW) or Software (SW). However, these two neighbour cells (A, B) may have the necessary HW or SW required to do Carrier Aggregation (CA) between them. With the existing prior art solutions, there is no way for the network to consider the possibility of aggregation between A and B for a UE with its Primary Cell (PCell) currently located in cell C. The main problem with this is reduced DL throughput since the opportunity to perform a HO to cell A and configuring B as an SCell cannot be considered.

An object of embodiments herein is to improve the performance of a wireless communications network using multi carrier connectivity.

According to an aspect of embodiments herein, the object is achieved by a method performed by a first network node for steering data traffic in a communication with a User Equipment, UE, in a wireless communications network. The first network node sends a request to a second network node. The request requests to set up interface between the first network node hosting a first cell and a second network node hosting a second cell. The second cell is a neighbor to the first cell. The first network node receives a message from the second network node over the requested set up interface. The message comprises indications indicating that: A third cell provided by a third network node is a neighbor to the second cell, the second cell is supporting multi carrier connectivity towards the third cell, and the third cell is supporting multi carrier connectivity towards the second cell. The first network node determines whether or not to handover the UE from the first cell to the second cell for multi carrier connectivity towards the third cell, based on the indications in the received message. The first network node then steers the data traffic in the communication with the UE according to the determining of whether or not to handover the UE to the second network node.

According to another aspect of embodiments herein, the object is achieved by a method performed by a first network node configured to steer data traffic in a communication with a User Equipment, UE, in a wireless communications network. The first network node further being configured to:Send a request to a second network node, which request is adapted to request to set up an interface between the first network node hosting a first cell and a second network node hosting a second cell.receive a message from the second network node over the requested set up interface, which message is adapted to comprise indications indicating that: A third cell provided by a third network node is a neighbor to the second cell, the second cell is supporting multi carrier connectivity towards the third cell, and the third cell is supporting multi carrier connectivity towards the second cell,determine whether or not to handover the UE from the first cell to the second cell for multi carrier connectivity towards the third cell based on the indications in the received message, andsteer the data traffic in the communication with the UE according to the determining of whether or not to handover the UE to the second network node.

Thanks to the indication indicating multi carrier connectivity of neighbor cells, the network node can perform traffic steering accordingly, and thereby make more beneficial traffic steering decisions for each UE in connected to the network. This in turn results in an improved performance of a wireless communications network using multi carrier connectivity.

DETAILED DESCRIPTION

Example embodiments herein relate to enhanced traffic steering with additional indicated connectivity support.

According to example embodiments herein, more types of connectivity capability for a served cell is indicated when information message is sent to a neighbor node. The neighbor node is then capable to incorporate indicated capability of multi carrier connectivity in traffic steering decisions and thereby make more beneficial decisions for each UE that it serves.

In some embodiments, the Connectivity Support IE is expanded to also include an indication about which served cells that are capable to perform multi carrier connectivity towards its neighbor cells.

In some other embodiments, the Connectivity Support IE may comprise indications about which cells that are capable of performing NR Dual Connectivity (DC) such as EN-DC and NR-DC towards neighbor cells.

Thus, examples of embodiments herein provide an expanded connectivity status IE to allow for better traffic steering with multi carrier connectivity such as e.g. carrier aggregation and NR-DC capability between neighbor cells and their neighbors to current serving network node e.g., gNB.

With the indications about which of the neighbor cells that also are capable of performing multi carrier connectivity, for example CA, towards their neighbors a network node such as e.g. an NG-RAN Node may utilize the indicated capability of multi carrier connectivity in traffic steering decisions. For example, it is possible to realize that a UE may get better performance after being handed over to the neighbor cell and thereby improve the Downlink (DL) and/or Uplink (UL) throughput for single UE:s, and on a network level.

If also capability of multi carrier connectivity, such as a NR-DC connectivity, is included over Xn, traffic steering may take that information into account when taking decision about the most suitable Primary Cell (PCell) for a UE.

FIG.4is a schematic overview depicting a wireless communications network100wherein embodiments herein may be implemented. The wireless communications network100comprises one or more RANs and one or more CNs. The wireless communications network100may use a number of different technologies, such as Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, 5G, NR, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications/enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations. Embodiments herein relate to recent technology trends that are of particular interest in a 5G context, however, embodiments are also applicable in further development of the existing wireless communication systems such as e.g. WCDMA and LTE.

A number of network nodes operate in the wireless communications network100such as e.g., a first network node111, second network node112, and a third network node113. The first, second and third network node111,112,113each provide radio coverage in a cell which may also be referred to as a beam or a beam group of beams, such as a cell11provided by the first network node111, a cell12provided by the second network node112, and a cell13provided by the third network node113.

The first, second and third network node111,112,113may each be any of a NG-RAN node, a transmission and reception point e.g. a base station, a radio access network node such as a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), an access controller, a base station, e.g. a radio base station such as a NodeB, an evolved Node B (eNB, eNode B), a gNB, an NG-RAN node, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point or any other network unit capable of communicating with UEs121,122within the service area served by the network node110depending e.g. on the first radio access technology and terminology used. The first, second and third network node111,112,113may communicate with UEs such as a UE120, in DL transmissions to the UEs and UL transmissions from the UEs.

A number of UEs operate in the wireless communication network100, such as e.g. the UE120. The UE120may also referred to as a device, an IoT device, a mobile station, a non-access point (non-AP) STA, a STA, a user equipment and/or a wireless terminals, communicate via one or more Access Networks (AN), e.g. RAN, to one or more core networks (CN). It should be understood by the skilled in the art that “wireless device” is a non-limiting term which means any terminal, wireless communication terminal, user equipment, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g., smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station communicating within a cell.

Methods herein may be performed by the first network node111. As an alternative, a Distributed Node (DN) and functionality, e.g. comprised in a cloud135as shown inFIG.4and inFIG.5, may be used for performing or partly performing the methods herein.

FIG.5. Depicts Radio control functions in a centralized computing environment e.g., in the cloud135. The RAN part of embodiments may be in an NG-RAN, typically located in a Radio Control Function (RCF) in the first network node111, the second network node112or third network node113(not shown inFIG.5) e.g., being gNBs or ng-eNBs. The RCF may be located physically in a distributed entity close to the radio nodes (RN) such as the first network node111, the second network node112or third network node113, or in a data center in a central location or on suitable hardware somewhere in between, e.g., in the cloud135.

A number of embodiments will now be described, some of which may be seen as alternatives, while some may be used in combination.

FIG.6shows example embodiments of a method performed by the first network node111for steering data traffic in a communication with the UE120in the wireless communications network100.

The method comprises the following actions, which actions may be taken in any suitable order. Optional actions are referred to as dashed boxes inFIG.6.

According to an example scenario, the first network node is about to start a communication with the UE120. The first network node111requires to retrieve basis for steering data traffic in an advantageous way in this communication.

The first network node111sends a request to the second network node112. The request requests to set up an interface between the first network node111hosting a first cell11and a second network node112hosting a second cell12. The second cell12is a neighbour to the first cell11. In some embodiments the interface between the first cell11and the second cell12comprises an Xn interface.

The purpose of the Xn Setup procedure is to exchange application level configuration data needed for two NG-RAN nodes such as the first and second network nodes111,112, to interoperate correctly over the Xn-C interface, for example to enable a handover between two cells residing on different NG-RAN nodes.

The request may be sent in a message such as a XN SETUP REQUEST, XN SETUP RESPONSE or NG-RAN NODE CONFIGURATION UPDATE. The neighbour node such as the second network node112then sends a XN Setup Response. After both these messages has been exchanged the interface can be considered to be established. Information about node configuration can be sent in both setup request and setup response, but also in the NG-RAN Node Configuration update, but that message is not part of the interface setup procedure.

The first network node111receives a message from the second network node112over the requested set up interface. The message comprises indications indicating that:a third cell13provided by a third network node113is a neighbour to the second cell12,the second cell12is supporting multi carrier connectivity towards the third cell13,the third cell13is supporting multi carrier connectivity towards the second cell12,

The message may e.g. be an XN SETUP REQUEST, XN SETUP RESPONSE or NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE or NG-RAN NODE Configuration update.

The first network node111determines whether or not to handover the UE120from the first cell11to the second cell12for multi carrier connectivity towards the third cell13based on the indications in the received message.

In some embodiments the determining whether or not to handover the UE120to the second cell12for multi carrier connectivity towards the third cell13is further based on the available bandwidth in the respective first cell11, second cell12and third cell13. In some embodiments it may further be based on other properties of the cell.

In some embodiments the determining whether or not to handover the UE120further comprises determining a PCell for the UE120in the communication based on the indications in the received message.

The multi carrier connectivity may e.g. comprise anyone out of: Dual connectivity, or Carrier aggregation.

In some embodiments the determining whether or not to handover the UE120based on the indications in the received message, further comprises determining to handover the UE120to the second cell12, and that the second cell12is to be a PCell for the UE120, and that the third cell13is to be an SCell for the UE120, in the communication.

The first network node111then steers the data traffic in the communication with the UE120, according to the determination of whether or not to handover the UE120to the second network node112.

This is an advantage since it may be beneficial for the UE120to perform a handover towards the second cell12provided by the second network node112, in those cases where it gives a better estimated throughput for the UE120. This is since the third cell13is a neighbor to the second cell12and the second cell is supporting multi carrier connectivity towards the third cell13.

The above embodiments will now be further explained and exemplified below. The embodiments below may be combined with any suitable embodiment above.

To enable the first network node111to also send the indication about different types of multi carrier connectivity support some of the embodiments herein provide to expand the Connectivity support IE from 3GPP TS 38.423 with more information. The suggestion is presented in the below Table, where the underlined text is the provided new content.

The Connectivity Support IE is used to indicate the connectivity such as the multi carrier connectivity supported by an NR cell such as e.g. the first, second or third cell11,12,13.

The Connectivity Support IE is part of the Neighbor Information NR IE that is exchanged between gNBs such as e.g. the first and second network node111,112in messages such as XN SETUP REQUEST, XN SETUP RESPONSE, NG-RAN NODE CONFIGURATION UPDATE and NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE.

In the message NG-RAN NODE CONFIGURATION UPDATE the Neighbor Information NR IE is sent in the served cells to update NR IE.

This means that according to embodiments herein a network node such as the second network node112, during setup phase and during configuration update phase, may inform another network node such as the first network node111about the multi carrier connectivity support towards the third cell13.

The benefit of the provided expansion and introduction of Connectivity Support is shown in the following example.

InFIG.7an example deployment is shown. According to an example scenario, the UE120is connected to the first cell11providing 10 MHz in the first network node111. In the example there is also two other network node e.g. gNBs, the second network node112and the third network node113that have cells12,13providing respective 40 MHz, with overlap to the first cell11.

When the first network node111starts doing evaluations for the UE120it may use a Connectivity Support/NR NR-DC parameter that it received from the second network node112and the third network node113during Xn setup phase or configuration update.

When Xn between the first network node111and the second network node112is established the second network node112informs the first network node111that the second cell12has a neighbor cell, the third cell13, and that the second cell12and the third cell13have connectivity support for multi carrier connectivity.

The first network node111may then utilize the indication that the second network node112has a cell providing 40 MHz, the second12, and one neighbor cell providing 40 MHz, the third cell13, that it can do aggregation towards. In this particular example it may be beneficial for the UE120to perform a HO towards the second cell12in order to get a better, e.g., maximized, bandwidth for the UE120. This may mean that the UE120would use the second cell12as PCell and the third cell13as an SCell in this example, providing 40 MHZ+40 MHz. Instead of as before the handover having the first cell11as a PCell providing 10 MHZ and the second cell12providing 40 MHZ as an SCell. In this case the bandwidth and/or the DL throughput is maximized

As mentioned above, the second cell12is supporting multi carrier connectivity towards the third cell13. In some embodiments, the indication may comprise both a direction of property and what is supported. This means that the indication may be used to inform that the multi carrier connectivity is supported from second cell12towards third cell13, from third cell13towards second cell12or in both directions.

To perform the method actions above, the first network node111is configured to steer data traffic in a communication with the UE120in the wireless communications network100. The network node110may comprise an arrangement depicted inFIGS.8aand8b.

The first network node111may comprise an input and output interface800configured to communicate with UEs such as the UE120and other network nodes such as the second and third network node112,113. The input and output interface800may comprise a wireless receiver (not shown) and a wireless transmitter (not shown).

The first network node111may further be configured to, e.g. by means of a sending unit810in the first network node111, send a request to a second network node112. The request is adapted to request to set up an interface between the first network node111hosting a first cell11and a second network node112hosting a second cell12, which second cell12is adapted to be a neighbour to the first cell11.

The interface between the first cell11and the second cell12may be adapted to comprise an Xn interface.

The first network node111is further configured to, e.g. by means of a receiving unit820in the first network node111, receive a message from the second network node112over the requested set up interface. The message is adapted to comprise indications indicating that:a third cell13provided by a third network node113is a neighbour to the second cell12,the second cell12is supporting multi carrier connectivity towards the third cell13, andthe third cell13is supporting multi carrier connectivity towards the second cell12,The first network node111is further configured to, e.g. by means of a determining unit830in the first network node111, determine whether or not to handover the UE120from the first cell11to the second cell12for multi carrier connectivity towards the third cell13based on the indications in the received message.

The multi carrier connectivity may be adapted to comprise anyone out of: Dual connectivity, or carrier aggregation.

The first network node111is further configured to, e.g. by means of a determining unit830in the first network node111, determine a Primary Cell, PCell, for the UE120in the communication based on the indications in the received message.

The first network node111may be further configured to, e.g. by means of the determining unit830in the first network node111, determine whether or not to handover the UE120to the second cell12for multi carrier connectivity towards the third cell13by further basing it on the available bandwidth in the respective first cell11, second cell12and third cell13.

The first network node111may be further configured to, e.g. by means of the determining unit830in the first network node111, determine whether or not to handover the UE120based on the indications in the received message, by determining to handover the UE120to the second cell12and that second cell12is to be a Primary Cell, PCell, for the UE120, and that the third cell13is to be a Secondary Cell, SCell, for the UE120, in the communication.

The first network node111is further configured to, e.g. by means of a steering unit840, steer the data traffic in the communication with the UE120according to the determining of whether or not to handover the UE120to the second network node112.

The embodiments herein may be implemented through a respective processor or one or more processors, such as the processor850of a processing circuitry in the first network node111depicted inFIG.8a, together with respective computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the network node110. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the first network node111.

The first network node111may further comprise a memory860comprising one or more memory units. The memory860comprises instructions executable by the processor in the first network node111. The memory860is arranged to be used to store e.g. information, indications, data, configurations, and applications to perform the methods herein when being executed in the first network node111.

In some embodiments, a computer program870comprises instructions, which when executed by the respective at least one processor360, cause the at least one processor of the first network node111to perform the actions above.

In some embodiments, a respective carrier880comprises the respective computer program870, wherein the carrier880is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

With reference toFIG.9, in accordance with an embodiment, a communication system includes a telecommunication network3210, such as a 3GPP-type cellular network, e.g. the wireless communications network100, which comprises an access network3211, such as a radio access network, and a core network3214. The access network3211comprises a plurality of base stations3212a,3212b,3212c, e.g. the first network node111, such as AP STAs NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area3213a,3213b,3213c. Each base station3212a,3212b,3212cis connectable to the core network3214over a wired or wireless connection3215. A first user equipment (UE) such as a Non-AP STA3291, e.g. the UE120, located in coverage area3213cis configured to wirelessly connect to, or be paged by, the corresponding base station3212c. A second UE3292e.g. the UE122, such as a Non-AP STA in coverage area3213ais wirelessly connectable to the corresponding base station3212a. While a plurality of UEs3291,3292are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station3212.

The communication system3300further includes the UE3330already referred to. Its hardware3335may include a radio interface3337configured to set up and maintain a wireless connection3370with a base station serving a coverage area in which the UE3330is currently located. The hardware3335of the UE3330further includes processing circuitry3338, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The UE3330further comprises software3331, which is stored in or accessible by the UE3330and executable by the processing circuitry3338. The software3331includes a client application3332. The client application3332may be operable to provide a service to a human or non-human user via the UE3330, with the support of the host computer3310. In the host computer3310, an executing host application3312may communicate with the executing client application3332via the OTT connection3350terminating at the UE3330and the host computer3310. In providing the service to the user, the client application3332may receive request data from the host application3312and provide user data in response to the request data. The OTT connection3350may transfer both the request data and the user data. The client application3332may interact with the user to generate the user data that it provides. It is noted that the host computer3310, base station3320and UE3330illustrated inFIG.10may be identical to the host computer3230, one of the base stations3212a,3212b,3212cand one of the UEs3291,3292ofFIG.9, respectively. This is to say, the inner workings of these entities may be as shown inFIG.10and independently, the surrounding network topology may be that ofFIG.9.

The wireless connection3370between the UE3330and the base station3320is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE3330using the OTT connection3350, in which the wireless connection3370forms the last segment. More precisely, the teachings of these embodiments may improve the RAN effect: data rate, latency, power consumption and thereby provide benefits such as corresponding effect on the OTT service: reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime.

The embodiments herein are not limited to the above described preferred embodiments. Various alternatives, modifications and equivalents may be used.

Abbreviations