Patent Description:
Embodiments herein further relates to computer programs and carriers corresponding to the above methods and network nodes.

In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) and/or User Equipment (UE), communicate via a Local Area Network such as a Wi-Fi network or a Radio Access Network (RAN) to one or more core networks (CN). 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 <NUM>. 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.

Specifications for the Evolved Packet System (EPS), also called a Fourth Generation (<NUM>) network, have been completed within the 3rd Generation Partnership Project (3GPP) and this work continues in the coming 3GPP releases, for example to specify a Fifth Generation (<NUM>) network also referred to as <NUM> New Radio (NR) or Next Generation (NG). The EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network. E-UTRAN/LTE is a variant of a 3GPP radio access network wherein the radio network nodes are directly connected to the EPC core network rather than to RNCs used in <NUM> networks. In general, in E-UTRAN/LTE the functions of a <NUM> RNC are distributed between the radio network nodes, e.g. eNodeBs in LTE, and the core network. As such, the RAN of an EPS has an essentially "flat" architecture comprising radio network nodes connected directly to one or more core networks, i.e. they are not connected to RNCs. To compensate for that, the E-UTRAN specification defines a direct interface between the radio network nodes, this interface being denoted the X2 interface.

Multi-antenna techniques may significantly increase the data rates and reliability of a wireless communication system. 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. Such systems and/or related techniques are commonly referred to as MIMO.

Baseband refers to the original frequency range of a transmission signal before it is modulated. A baseband unit (BBU) is a unit that processes baseband in telecomm systems. A typical base station comprises a BBU and an Radio Frequency (RF) processing unit also referred to as a remote radio unit - RRU. The BBU may e.g. be located in an equipment room of a base station and may be connected with the RRU via optical fiber.

In a radio access network, a Transmission Reception Point (TRP) is a term that is used when referring to the geographical position from where radio transmission is emitted. A TRP comprises an antenna array with one or more antenna elements available to the wireless communications network located at a specific geographical location for a specific area, see 3GPP <NUM>. Sector Carriers represent spectrum and power resources of each TRP included in a cell. A cell may have one to many sector carriers, see 3GPP <NUM>. A TRP provides radio access to UEs in the radio access network. The TRP may be located at a specific geographical location for providing radio coverage for a specific area. Data traffic served by this TRP is processed on a BBU. Processed by the BBU, when used herein means utilize Central Processing Unit (CPU) cycles and memory of the BBU. The BBU has a defined compute capacity to support a certain number of cells, sector carriers, users and throughput etc..

A problem with prior art will be developed and discussed below. <CIT> and <CIT> disclose background information that are useful to understand the context of the invention, as defined in the appended claims.

An object of embodiments herein is to improve the performance in a wireless communications network using Baseband Units (BBUs).

According to an aspect, the object is achieved by a method performed by a control node according to claim <NUM>.

According to another aspect, the object is achieved by a method performed by a network node according to claim <NUM>.

According to another aspect, the object is achieved by a control node according to claim <NUM>.

According to another aspect, the object is achieved by a network node according to claim <NUM>.

An advantage of embodiments herein is that the provided method will dynamically re-allocate a sector carrier to another BBU, multiple BBUs may be used as pooled HW for load balance, the BBU HW utilization may be scaled with traffic load for energy efficiency, and inter-sector carrier coordination may be optimized. This results in that the performance in a wireless communications network using BBUs is improved.

A further advantage is that they also improve Hardware (HW) utilization and provide flexibility.

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

A BBU must be able to manage peak load situations. The traffic load varies a lot during time therefore peak traffic load only happens in a small percent of the time, which leads to low average BBU Hardware (HW) utilization.

Peak load of different TRPs usually does not happen simultaneously. By run-time re-allocating processing of data traffic to another BBU, the processing load may be balanced among a pool of BBUs. The term run-time when used herein means no need to re-configure a cell or drop of UE data traffic. The wording run-time re-allocate TRP when used herein means to change the processing HW for the UE traffic carried by a TRP without drop of UE data traffic. In average, the HW utilization is improved and required HW may be reduced. During non-busy hours, TRPs may also be re-allocated to fewer BBUs to gain energy efficiency.

The re-allocating of the TRP processing to another BBU may be done by reconfiguring the cell that represents the TRP to another BBU. However, the cell will be homed by on another BBU and get another cell Identity (cellld). This will mess up the cell level management. The wording "the cell will be homed" when used herein means that the cell ID, cell data for configuration management, performance management and fault management are stored and/or connected to the BBU.

The existing Centralized RAN (CRAN) deployment, only co-locate BBUs to the same site. Each BBU has an individual capacity. Due to the nature of traffic variation, some BBUs may be over-loaded while other may be under loaded at the same time. There is no solution to run-time balance the BBU load and at the same time keep cell level management.

To reduce risk that peak load exceeds the BBU capacity, one solution provides to over dimension the BBU to handle peak load. Drawbacks of this solution are that it results in very low average HW utilization. Higher Capital Expenses (CAPEX) due to more over dimensioned BBUs is needed and higher Operating Expenses (OPEX) due to energy cost per BBU. There may not be enough space to have many BBUs.

To balance processing load on BBUs one solution is to shut down a cell on high loaded BBU and move it to low loaded BBU. Drawbacks of this solution are that this will introduce cell down time and drop of traffic. It is complicated to keep cell level management due to that the cell changed home BBU and most probably also the NodeB.

Another solution to balance processing load on BBUs is to move traffic to neighbor cells before shutting down the cell in the above solution. Drawbacks of this solution is that it is no guarantee that there is a neighbor cell to move the UE to. It is complicated to keep the cell level management due to that the cell changed home BBU and most probably also the NodeB.

A further solution to balance processing load on BBUs is to move a UE to neighbor cells to balance cell load. Drawbacks of this solution is that the neighbor cell may not locate the processed data traffic on the suitable BBU. The BBU HW load cannot be balanced by this method.

An object of embodiments herein is to improve the performance and the HW utilization in a wireless communications network using Baseband Units (BBUs).

Example of embodiments herein relates to run-time sector carrier re-allocation between BBUs. Embodiments herein provide methods to run-time balance the BBU load and at the same time keep cell level management. According to embodiments herein, the sector carrier is not shut down and neither the cell is shut down.

Embodiments herein further enable BBU pooling. The wording BBU pooling when used herein means the processing of UE traffic may be re-allocate to different BBUs.

A TRP is represented by sector carrier. The same spectrum and power resources of a TRP may be presented in multiple cells by different sector carriers. see reference <NUM>, SC3, <NUM> and SC3' in <FIG> described below. ) A cell may comprise multiple TRPs therefore have multiple sector carriers. see reference first cell <NUM>, second cell <NUM>, <NUM> and <NUM> in <FIG> described below).

The re-allocation may be performed by run-time switching an active sector carrier to present the TRP. The cell level management may then be kept untouched. This is since the sector carrier is only part of a cell. No need to change cell ID or lock and/or unlock a cell to activate or de-activate a sector carrier. Some embodiments herein further provide a handover procedure to coordinate the de-activating the sector carrier on the source BBU and activating the sector carrier on the target BBU.

An advantage of embodiments herein is that the provided method will have no impact on cell level management. The UE is handed over to the multi-TRP cell on the target BBU, thus the impact on traffic is minimized. There will be no cell down time and no drop of connection with the UE. The wording cell down time means a period of time during which a UE cannot be connected to the cell.

A further advantage of embodiments herein is that they may be applied on both LTE and NR, both on embedded BBUs and on cloud BBUs.

A yet further advantage of embodiments herein is that by dynamically re-allocate a sector carrier to another BBU, multiple BBUs may be used as pooled HW for load balance, the HW utilization may be scaled with traffic load for energy efficiency, and inter-sector carrier coordination may be optimized.

<FIG> and <FIG> are schematic overviews depicting a wireless communications network <NUM> wherein embodiments herein may be implemented. <FIG> depicts a scenario before re-allocating processing of data traffic from a first BBU to a second BBU. <FIG> depicts a scenario after re-allocating the processing of data traffic from the first BBU to the second BBU according to embodiments herein. The wireless communications network <NUM> comprises one or more RANs and one or more CNs. The wireless communications network <NUM> may use <NUM> Fifth Generation New Radio, (<NUM> NR) but may further use a number of other different Radio Access Technologies (RAT)s, such as, Wi-Fi, (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications/enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations. According to some embodiments herein, a first RAT may e.g. be any one out of LTE or NR. A second RAT may e.g. be LTE if the first RAT is NR or NR if the first RAT is LTE.

Network nodes such as a network node <NUM> operate in the wireless communications network <NUM>. The network node <NUM> operates and or controls one or more TRPs such as a TRP <NUM> and one or more other TRPs <NUM>. The network node <NUM> further may control and one or more BBUs such as a first BBU <NUM> and a second BBU <NUM> shown in <FIG> described below. The TRP <NUM> and the other TRPs <NUM> each provides radio access in one or more cells by means of one or more second sector carriers, such as e.g. the TRP <NUM> provides a first sector carrier in the first cell <NUM> and a second sector carrier in the second cell <NUM>. <FIG> depicts the first cell <NUM> and the second cell <NUM> in a scenario before re-allocating processing of data traffic from a first BBU to a second BBU. <FIG> depicts the first cell <NUM> and the second cell <NUM> in a scenario after re-allocating the processing of data traffic from the first BBU to the second BBU according to embodiments herein.

The TRP <NUM> may comprise antennas covering areas. The TRP <NUM> may be a part of a network comprising BBUs. The network node <NUM>, the TRP <NUM>, the first and second BBUs <NUM>, <NUM>, may be co-located on the same node or may be separated to different nodes.

The network node <NUM> may provide transmission and reception points and may e.g. be a radio access network node such as a base station, e.g. a radio base station such as a NodeB, an evolved Node B (eNB, eNode B), an NR Node B (gNB), 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, a Wireless Local Area Network (WLAN) access point, an Access Point Station (AP STA), an access controller, a UE acting as an access point or a peer in a Device to Device (D2D) communication, or any other network unit capable of communicating with a UE within the cell served by network node <NUM> depending e.g. on the radio access technology and terminology used.

Other network nodes such as a control node <NUM> operate in the wireless communications network <NUM>. The location and implementation of the control node <NUM> may be very flexible; both inside or outside a base station such as the network node <NUM> is possible.

The control node <NUM> may provide control functions and may be a standalone node or may be collocated with the network node <NUM> or any other network node or distributed node in a cloud. The control node <NUM> may control data traffic between the TRP <NUM> and a UE <NUM> in the wireless communications network <NUM>.

Wireless devices such as the UE <NUM> operate in the wireless communications network <NUM>. The UE <NUM> may e.g. be an NR device, a mobile station, a wireless terminal, an NB-loT device, an eMTC device, a CAT-M device, a WiFi device, an LTE device and an a non-access point (non-AP) STA, a STA, that communicates via a base station such as e.g. the TRP <NUM>, one or more RANs to one or more CNs. It should be understood by the skilled in the art that the UE <NUM> relates to a non-limiting term which means any UE, terminal, wireless communication terminal, user equipment, (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 control node <NUM> and the network node <NUM>. As an alternative, a Distributed Node (DN) and functionality, e.g. comprised in a cloud <NUM> as shown in <FIG>, may be used for performing or partly performing the methods.

<FIG> depicts a more detailed example scenario of the wireless communications network <NUM> wherein embodiments herein may be implemented. Six TRPs, the TRP <NUM> and other TRPs <NUM>, operate in this example scenario, TRP1, TRP2, TRP3, TRP4, TRP5, and TRP6. The TRP <NUM> is in this example and <FIG> represented by TRP3. The other TRPs <NUM> are in this example and <FIG> represented by TRP1, TRP2, TRP4, TRP5, and TRP6. An Ethernet switch is used to provide front haul connectivity between all BBUs and RRUs.

<FIG> depicts two example scenarios, one before and one after a re-allocation of one TRP, TRP3, such as the TRP <NUM> from one BBU, the first BBU <NUM>, to another BBU, the second BBU <NUM>. The top part of <FIG> depicts a scenario before re-allocation <NUM> and the bottom part of <FIG> depicts a scenario after re-allocation <NUM>.

TRP1 is represented by Sector Carrier (SC) <NUM>, TRP2 is represented by SC2, and TRP3 is represented by SC3 in cell <NUM> and are processed in a first BBU <NUM>, referred to as BBU1.

TRP4 is represented by Sector Carrier SC4, TRP5 is represented by SC5, and TRP6 is represented by SC6 in cell <NUM> and are processed in a second BBU <NUM>, referred to as BBU2.

According to embodiments herein, to re-allocate TRP3 from BBU1 to BBU2, the SC3 is removed from the first cell <NUM> and added as SC3' to the second cell <NUM>. This means in other words, to re-allocate the TRP <NUM> from the first BBU <NUM> to the second BBU <NUM>, a first sector carrier is removed from the first cell <NUM> and added as a second sector carrier to the second cell <NUM>.

The method will first be described in as seen from the control node <NUM> perspective together with <FIG>, and then as seen from the network node <NUM> perspective together with <FIG>.

<FIG> shows example embodiments of a method performed by the control node <NUM> for handling data traffic between the TRP <NUM> and the UE <NUM> in the wireless communications network <NUM>. The TRP <NUM> is related to the network node <NUM>. This means that the network node <NUM> may manage or control the TRP <NUM> and data traffic in the TRP <NUM>.

The control node <NUM> may be represented by any one out of: the TRP <NUM>, or a distributed node, a centralized node or a management node in the cloud <NUM>, the first BBU <NUM>, the second BBU <NUM>, a Core Network, CN, node in the wireless communications network <NUM>. The data in the data traffic may comprise control data and/or user data.

The TRP <NUM> is serving the data traffic in a first sector carrier. The data traffic in the first sector carrier is processed by the first BBU <NUM>.

The method comprises one or more of the following actions, which actions may be taken in any suitable order. Actions that are optional are marked with dashed boxes in the figure.

In an example scenario with an ongoing communication of data traffic between the TRP <NUM> and the UE <NUM>, the control node <NUM> deems that the processing of data traffic in the first BBU <NUM>, e.g. including data traffic with other UEs, may become overloaded, or any other reason. To avoid an overload in the first BBU <NUM>, the control node <NUM> decides to re-allocate the processing of the data traffic in the first BBU <NUM> to the second BBU <NUM>. The second BBU <NUM> processes data traffic in a second sector carrier provided by the TRP <NUM>.

The deciding to re-allocate the processing of the data traffic in the first BBU <NUM> to a second BBU <NUM> may be based on one or more criterion related to any one or more out of: Processor load, memory load, coordination performance, energy efficiency, in the first BBU <NUM> or operator decisions, for example site migration, relating to the first BBU <NUM>.

When the re-allocation has been decided, the control node <NUM> controls the realization of the re-allocation by sending orders and instructions to the network node <NUM> according to the actions below.

A preparation of the new second sector carrier for the TRP <NUM> is required. Thus, in some embodiments, the control node <NUM> sends a first order to the network node <NUM>. The first order orders the network node <NUM>, e.g. the second BBU <NUM> of the network node <NUM>, to prepare the second sector carrier to represent the TRP <NUM> in the second cell <NUM>. The preparation of the second sector carrier to represent the TRP <NUM> in the second cell <NUM> means that the second sector carrier such as e.g. SC3', is configured and added to the second <NUM> and connection between TRP <NUM> and BBU <NUM> is setup.

The second sector carrier for the TRP <NUM> may be also always pre-configured in the second BBU <NUM> or more BBUs to avoid the preparation step in run time.

Further, the first sector carrier needs to stop processing the data traffic. Thus, the control node <NUM> sends a second order to the network node <NUM>, e.g. to be sent to the first BBU <NUM>, to stop processing the data traffic of the first sector carrier in the first BBU <NUM>. This means that the first BBU <NUM> will stop to take new UEs on the first sector carrier and buffer the data traffic from the active UE <NUM>. The order is sent to the first BBU <NUM> e.g. in the first cell <NUM>.

The first BBU <NUM> may process data traffic in a first cell <NUM>, and the second BBU <NUM> may process data traffic in a second cell <NUM>.

The UE <NUM> may be directed to other neighbor cells. In some embodiments, the control node <NUM> sends an instruction to the network node <NUM>, e.g. to be sent to the first BBU <NUM> through cell <NUM>, to configure active UEs, e.g. comprising the UE <NUM>, to handover the data traffic from the first cell <NUM> to the second cell <NUM>.

Further, the second sector carrier needs to be activated and the processing of the data traffic in the second BBU <NUM> requires to be started. Thus, the control node <NUM> sends a third order to the network node <NUM>, e.g. to the second BBU <NUM> through the second cell <NUM>, to activate the second sector carrier, start processing the data traffic in the second BBU <NUM>, and e.g. to be sent to the first BBU 111through the first cell <NUM> to deactivate the first sector carrier.

After configured UE <NUM> to handover to the second cell <NUM>, the first BBU <NUM> may de-activate the first sector carrier and send confirmation back to the network node <NUM>,<NUM>.

The re-allocation of the processing of the data traffic in the first BBU <NUM> to the second BBU <NUM> may be performed by a run-time switch. This is an advantage and means that there is no cell lock and/or unlock and/or re-configuration, and no drop of UE <NUM> data traffic.

In order to perform the re-allocation as a run-time switch, the orders of activating of the second sector carrier and the de-activating of the first sector carrier shall preferably be be coordinated so that the deactivation of the first sector carrier is done after the UE <NUM> is configured, e.g. RRC re-configured, to the second cell <NUM>. The de-activation of the first sector carrier and the activation of the second sector carrier is done with a short interval so that the second sector carrier is activated before UE <NUM> completes the handover successfully.

The method will now be described as seen from the network node <NUM> perspective. <FIG> shows example embodiments of a method performed by the network node <NUM> for handling data traffic between the TRP <NUM> and the UE <NUM> in the wireless communications network <NUM>. The TRP <NUM> is serving the data traffic in a first sector carrier. The data traffic in the first sector carrier is processed by the BBU <NUM>. In some embodiments, the first BBU <NUM> processes data traffic in a first cell <NUM>, and the second BBU <NUM> processes data traffic in a second cell <NUM>.

A first order may be received when the control node <NUM> has decided to re-allocate the processing of the data traffic in the first BBU <NUM> to a second BBU <NUM>. The first order orders the NETWORK NODE <NUM> to prepare the second sector carrier to represent the TRP <NUM> in the second cell <NUM>. Thus, in some embodiments, the network node <NUM> may prepare the second sector carrier to represent the TRP <NUM> in the second cell <NUM>. This action is triggered by a first order received from the control node <NUM>.

The network node <NUM> receives a second order, ordering the TRP <NUM> to deactivate the first sector carrier and stop processing the data traffic of the first sector carrier in the first BBU <NUM>. The network node <NUM> stops processing the data traffic of the first sector carrier in the first BBU <NUM>. This action is triggered by the second order. The second order is received from the control node <NUM> in the wireless communications network <NUM> when the control node <NUM> has decided to re-allocate the processing of the data traffic in the first BBU <NUM> to a second BBU <NUM>.

The re-allocation of the processing of the data traffic in the first BBU <NUM> to the second BBU <NUM>, may be performed by a run-time switch.

The network node <NUM> may receive an instruction, instructing the network node <NUM> to configure the UE <NUM> to handover the data traffic from the first cell <NUM> to the second cell <NUM>.

In some embodiments, the network node <NUM> configures the UE <NUM> to handover the data traffic from the first cell <NUM> to the second cell <NUM>. This is triggered by an instruction received from the control node <NUM> e.g. when the control node <NUM> has decided to re-allocate the processing of the data traffic in the first BBU <NUM> to a second BBU <NUM>. The instruction is to configure the UE <NUM> to handover the data traffic from the first cell <NUM> to the second cell <NUM>.

The network node <NUM> receives a third order from the control node <NUM>, ordering the network node <NUM> to activate the second sector carrier, and start processing the data traffic in the second BBU <NUM>.

The network node <NUM> activates the second sector carrier, starts processing the data traffic in the second BBU <NUM>, and deactivates the first sector carrier. The second BBU <NUM> processes data traffic in a second sector carrier provided by the TRP <NUM>. This action is triggered by a third order received from the control node <NUM> e.g. when the control node <NUM> has decided to re-allocate the processing of the data traffic in the first BBU <NUM> to a second BBU <NUM>.

In this way, by performing the methods described above, the load of the first and second BBUs <NUM>, <NUM>, are run-time balanced and at the same time the cell level management is kept.

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

<FIG> shows an example of actions of the procedure to re-allocate the processing of the data traffic in the first BBU <NUM> to a second BBU <NUM>. The control node <NUM> decides to move the TRP <NUM> processing from the first cell <NUM> on the first BBU <NUM> to the second cell <NUM> on the second BBU <NUM>. A sector carrier is referred to as SC in the Figure.

The UE <NUM> data traffic in the first sector carrier is processed by the first BBU <NUM> in the first cell <NUM>, referred to as the first cell <NUM>.

Action <NUM>. When the control node <NUM> has decided (See action <NUM>) to re-allocate the processing of the data traffic in the first BBU <NUM> to a second BBU <NUM>, the control node <NUM>, sends the first order (See action <NUM>) to the network node <NUM> e.g. to the second cell <NUM> provided by the TRP <NUM>. The first order is to prepare the second sector carrier to represent the TRP <NUM> in the second cell, the second cell <NUM>.

Action <NUM>. The second sector carrier gets connected to the TRP <NUM> but is still deactivated.

Action <NUM>. The control node <NUM>, then sends the second order (See action <NUM>) to the network node <NUM>, e.g. to the first cell <NUM> provided by the TRP <NUM>. The second order is to deactivate the first sector carrier and move the data traffic to the second cell <NUM>.

Action <NUM>. The first sector carrier and first BBU <NUM> stops take new UE <NUM> data traffic.

Action <NUM>. A handover (HO) request is sent from the first cell <NUM> to the second cell <NUM>.

Action <NUM>. A HO confirmation from the second cell <NUM> to the first cell <NUM>, if the HO is possible.

Action <NUM>. An RRC reconfiguration is sent from the first cell <NUM> to the second cell <NUM>. e.g. in a HO Command.

Action <NUM>. The first sector carrier is then de-activated.

Action <NUM>. The first sector carrier deactivation is confirmed (Cfm) to the control node <NUM>. (See action <NUM>).

Action <NUM>. The control node <NUM>, then sends the third order (See action <NUM>) to the network node <NUM>, e.g. through the second cell <NUM> provided by the TRP <NUM>. The third order is to activate the second sector carrier.

Action <NUM>. The second sector carrier is activated according to the third order. (See action <NUM>.

Action <NUM>. The UE <NUM> accesses to the second cell <NUM> and sends a HO complete message to the second cell <NUM> of the TRP <NUM>, when the HO is completed.

Action <NUM>. The data traffic of the UE <NUM> is then forward via the second cell, the first cell <NUM>.

Action <NUM>. A release UE <NUM> context message is sent from the second cell <NUM> to the first cell <NUM>. The first sector carrier may now be removed from the first cell <NUM>.

Action <NUM>. The UE data traffic in the second sector carrier is now processed by the second BBU <NUM> in the second cell <NUM>. Thus the TRP <NUM> is successfully switched to the second BBU <NUM>.

These methods as described above, run-time switch TRP processing to different BBU HW, such as the first BBU <NUM> and the second BBU <NUM>, is enabled. This further enables pooling of BBU HW, such as the first BBU <NUM> and the second BBU <NUM>, to allow scaling HW utilization with traffic load. The benefit may be lower CAPEX & OPEX due to efficient HW utilization, energy efficiency and better network performance with run-time optimized coordination.

A significant action provided herein is to enable one TRP <NUM> as a sector carrier in a Multi -TRP cell on both source BBU, such as the first BBU <NUM>, and target BBU such as the second BBU <NUM>, and run-time switch the processing of the TRP <NUM> traffic by de-activate one of the sector carriers such as the first sector carrier and activate another of the sector carriers such as the second sector carrier.

According to some embodiments herein:
The TRP <NUM> is represented by <NUM> sector carriers, one sector carrier on the source BB HW such as the first sector carrier on the first BBU <NUM>, and one sector carrier on the target BB HW, such as the second sector carrier on the second BBU <NUM>.

The two sector carriers, such as the first and second sector carriers are not activate at the same time.

The switch of the TRP processing, such as the re-allocation of the processing of the data traffic from the first BBU <NUM> to the second BBU <NUM> is performed by deactivating the first sector carrier on the first BBU <NUM> and activate the second sector carrier on the second BBU <NUM>.

The two sector carriers, such as the first and second sector carriers belongs to respective operational cells such as the first cell <NUM> and the second cell <NUM>, the on source and target BB HW, such as the first BBU <NUM> and the second BBU <NUM>.

A controller, such as the control node <NUM> triggers the switch from the first cell <NUM> in the source BBU such as the first BBU <NUM> and handover of UE data traffic to the second cell <NUM> on target BB HW such as the second BBU <NUM>.

The handover procedure is coordinated with the de-activation of the first sector carrier and activation of the second sector carrier, so UE <NUM> ongoing communication of data traffic is not dropped.

To perform the action as mentioned above, the control node <NUM> may comprise the arrangement as shown in <FIG> a and b. The control node <NUM> is configured to handle data traffic between the TRP <NUM> and the UE <NUM> in the wireless communications network <NUM>. The TRP is related to a network node <NUM>. The TRP <NUM> is adapted to serve data traffic in a first sector carrier. The data traffic in the first sector carrier further is adapted to be processed by the first BBU <NUM>.

The control node <NUM> may comprise a respective input and output interface <NUM> configured to communicate with the TRP <NUM>, see <FIG>. The input and output interface <NUM> may comprise a wireless receiver (not shown) and a wireless transmitter (not shown).

The control node <NUM> is further configured to, e.g. by means of a deciding unit <NUM> in the control node <NUM>, decide to re-allocate the processing of the data traffic in the first BBU <NUM> to a second BBU <NUM>. The second BBU <NUM> is adapted to process data traffic in a second sector carrier provided by the TRP <NUM>.

The decision to re-allocate the processing of the data traffic in the first BBU <NUM> to a second BBU (<NUM>), may be adapted to be based on one or more criterion related to any one or more out of: processor load, memory load, coordination performance.

The re-allocation of the processing of the data traffic in the first BBU <NUM> to the second BBU <NUM>, may be adapted to be performed as a run-time switch.

The first BBU <NUM> may be configured to process data traffic in a first cell <NUM>, and the second BBU <NUM> is configured to process data traffic in a second cell <NUM>.

The control node <NUM> may be adapted to be represented by any one out of: A control node <NUM>, the TRP <NUM>, a distributed node in a cloud <NUM>, the first BBU <NUM>, the second BBU <NUM>, a Core Network, CN, node in the wireless communications network <NUM>.

The control node <NUM> is further configured to, e.g. by means of a sending unit <NUM> in the control node <NUM>, send a second order to the network node <NUM>. The second order is to stop processing the data traffic of the first sector carrier in the first BBU <NUM>.

The control node <NUM> is further configured to, e.g. by means of the sending unit <NUM> in the control node <NUM>, send a third order to the network node <NUM>. The third order is to activate the second sector carrier, start processing the data traffic in the second BBU <NUM> and to deactivate the first sector carrier.

In some embodiments the control node <NUM> is further configured to, e.g. by means of the sending unit <NUM> in the control node <NUM>, send a first order to the network node <NUM>. The first order is to prepare the second sector carrier to represent the TRP <NUM> in the second cell <NUM>.

In some embodiments the control node <NUM> is further configured to, e.g. by means of the sending unit <NUM> in the control node <NUM>, send an instruction to the network node <NUM>. The instruction is to configure active UEs, e.g. the UE <NUM>, on the first sector carrier to handover the data traffic from the first cell <NUM> to the second cell <NUM>.

The embodiments herein may be implemented through a respective processor or one or more processors, such as a processor <NUM> of a processing circuitry in the control node <NUM>, depicted in <FIG> a and b, together with 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 control node <NUM>. 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 control node <NUM>.

The control node <NUM> may further comprise a respective memory <NUM> comprising one or more memory units. Each memory <NUM> comprises instructions executable by the processor <NUM> in the control node <NUM>.

Each respective memory <NUM> is arranged to be used to store orders, requirements, , information, data, configurations, and applications to perform the methods herein when being executed in the control node <NUM>.

In some embodiments, a respective computer program <NUM> comprises instructions, which when executed by the at least one processor <NUM>, cause the at least one processor <NUM> of the control node <NUM> to perform the actions above.

In some embodiments, a respective carrier <NUM> comprises the respective computer program <NUM>, wherein the carrier <NUM> is 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.

Those skilled in the art will also appreciate that the units in the units described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g. stored in the network node <NUM>, that when executed by the respective one or more processors such as the processors or processor circuitry described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuitry (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a-chip (SoC).

To perform the action as mentioned above, the TRP <NUM> may comprise the arrangement as shown in <FIG> a and b. The TRP <NUM> is configured to handle data traffic between the TRP <NUM> and a UE <NUM> in a wireless communications network <NUM>. The TRP <NUM> is related to a network node <NUM>. The TRP <NUM> is adapted to serve the data traffic in a first sector carrier. The data traffic in the first sector carrier is adapted to be processed by a first BBU <NUM>.

The TRP <NUM> may comprise a respective input and output interface <NUM> configured to communicate with the control node <NUM>, see <FIG>. The input and output interface <NUM> may comprise a wireless receiver (not shown) and a wireless transmitter (not shown).

The TRP <NUM> is further configured to, e.g. by means of a preparing unit <NUM> in the TRP <NUM>, triggered by a first order, prepare the second sector carrier to represent the TRP <NUM> in the second cell <NUM>. The first order is adapted to be received from the control node <NUM>.

The TRP <NUM> is further configured to, e.g. by means of a stopping unit <NUM> in the TRP <NUM>, triggered by a second order, stop processing the data traffic of the first sector carrier in the first BBU <NUM>. The second order is adapted to be received from a control node <NUM> in the wireless communications network <NUM> when decided to re-allocate the processing of the data traffic in the first BBU <NUM> to a second BBU <NUM>.

The TRP <NUM> is further configured to, e.g. by means of a configuring unit <NUM> in the TRP <NUM>, triggered by an instruction, configure the UE <NUM> to handover the data traffic from the first cell <NUM> to the second cell <NUM>. The instruction is adapted to be received from the control node <NUM>.

The TRP <NUM> is further configured to, e.g. by means of an activating unit <NUM> and a de-activating unit <NUM> in the TRP <NUM>, triggered by a third order, activate the second sector carrier, start processing the data traffic in the second BBU <NUM>, and deactivate the first sector carrier. The third order is adapted to be received from the control node <NUM>. The second BBU <NUM> is adapted to process data traffic in a second sector carrier provided by the TRP <NUM>.

The re-allocation of the processing of the data traffic in the first BBU <NUM> to the second BBU <NUM> may be adapted to be performed as a run-time switch.

The first BBU <NUM> may be configured to process data traffic in a first cell <NUM>, and wherein the second BBU <NUM> is configured to process data traffic in a second cell <NUM>.

The embodiments herein may be implemented through a respective processor or one or more processors, such as the processor <NUM> of a processing circuitry in the TRP <NUM>, depicted in <FIG> a and b, together with 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 node <NUM>. 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 network node <NUM>.

The TRP <NUM> may further comprise a respective memory <NUM> comprising one or more memory units. Each memory comprises instructions executable by the processor <NUM> in the TRP <NUM>. Each respective memory <NUM> is arranged to be used to store orders, requirements, , information, data, configurations, and applications to perform the methods herein when being executed in the TRP <NUM>.

In some embodiments, a respective computer program <NUM> comprises instructions, which when executed by the at least one processor <NUM>, cause the at least one processor <NUM> of the TRP <NUM> to perform the actions above.

In some embodiments, a respective carrier <NUM> comprises the respective computer program <NUM>, wherein the carrier is 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.

When using the word "comprise" or "comprising" it shall be interpreted as non-limiting, i.e. meaning "consist at least of".

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

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

The hardware <NUM> may include a communication interface <NUM> for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system <NUM>, as well as a radio interface <NUM> for setting up and maintaining at least a wireless connection <NUM> with a UE <NUM> located in a coverage area (not shown) served by the base station <NUM>.

The wireless connection <NUM> between the UE <NUM> and the base station <NUM> is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE <NUM> using the OTT connection <NUM>, in which the wireless connection <NUM> forms the last segment. More precisely, the teachings of these embodiments may improve the applicable RAN effect: data rate, latency, power consumption, and thereby provide benefits such as corresponding effect on the OTT service: e.g. reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime.

The communication system includes a host computer, a base station such as the network node <NUM>, and a UE such as the UE <NUM>, which may be those described with reference to <FIG> and <FIG>. In a first action <NUM> of the method, the host computer provides user data. In an optional subaction <NUM> of the first action <NUM>, the host computer provides the user data by executing a host application. In a second action <NUM>, the host computer initiates a transmission carrying the user data to the UE. In an optional third action <NUM>, the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional fourth action <NUM>, the UE executes a client application associated with the host application executed by the host computer.

The communication system includes a host computer, a base station such as a AP STA, and a UE such as a Non-AP STA which may be those described with reference to <FIG> and <FIG>. In a first action <NUM> of the method, the host computer provides user data. In an optional subaction (not shown) the host computer provides the user data by executing a host application. In a second action <NUM>, the host computer initiates a transmission carrying the user data to the UE. In an optional third action <NUM>, the UE receives the user data carried in the transmission.

The communication system includes a host computer, a base station such as a AP STA, and a UE such as a Non-AP STA which may be those described with reference to <FIG> and <FIG>. In an optional first action <NUM> of the method, the UE receives input data provided by the host computer. Additionally or alternatively, in an optional second action <NUM>, the UE provides user data. In an optional subaction <NUM> of the second action <NUM>, the UE provides the user data by executing a client application. In a further optional subaction <NUM> of the first action <NUM>, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. Regardless of the specific manner in which the user data was provided, the UE initiates, in an optional third subaction <NUM>, transmission of the user data to the host computer. In a fourth action <NUM> of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

Claim 1:
A method performed by a control node (<NUM>) for handling data traffic between a Transmission and Reception Point, TRP, (<NUM>), and a User Equipment, UE, (<NUM>) in a wireless communications network (<NUM>), which TRP (<NUM>) is controlled by a network node (<NUM>) and is serving the data traffic in a first sector carrier, and which data traffic in the first sector carrier is processed by a first Baseband Unit, BBU, (<NUM>), the method comprising:
deciding (<NUM>) to re-allocate the processing of the data traffic in the first BBU (<NUM>) to a second BBU (<NUM>), which second BBU (<NUM>) processes data traffic in a second sector carrier provided by the TRP (<NUM>),
wherein the first BBU (<NUM>) processes data traffic of the first sector carrier in a first cell (<NUM>), and wherein the second BBU (<NUM>) processes data traffic of the second sector carrier in a second cell (<NUM>),
sending (<NUM>) a first order to the network node (<NUM>) to prepare the second sector carrier to represent the TRP (<NUM>) in the second cell (<NUM>),
sending (<NUM>) a second order to the network node (<NUM>), to stop processing data traffic of the first sector carrier in the first BBU (<NUM>),
sending (<NUM>) an instruction to the network node (<NUM>) to configure active UEs on the first sector carrier to handover the data traffic from the first cell (<NUM>) to the second cell (<NUM>)
sending (<NUM>) a third order to the network node (<NUM>), to activate the second sector carrier, start processing the data traffic in the second BBU (<NUM>), and to deactivate the first sector carrier.