FIRST COMMUNICATION NODE. SECOND COMMUNICATION NODE. AND METHODS PERFORMED THEREBY FOR HANDLING MULTICONNECTIVITY

Technical field

Embodiments of the present disclosure relate to communication networks, and particularly to methods, apparatus and computer-readable mediums for handling a plurality of cell groups.

Background

Communication devices within a wireless communications network may be wireless devices such as e.g., User Equipments (UEs), stations (STAs), mobile terminals, wireless terminals, terminals, and/or Mobile Stations (MS). Wireless devices are enabled to communicate wirelessly in a cellular communications network or wireless communication network, sometimes also referred to as a cellular radio system, cellular system, or cellular network. The communication may be performed e.g., between two wireless devices, between a wireless device and a regular telephone, and/or between a wireless device and a server via a Radio Access Network (RAN) , and possibly one or more core networks, comprised within the wireless communications network. Wireless devices may further be referred to as mobile telephones, cellular telephones, laptops, or tablets with wireless capability, just to mention some further examples. The wireless devices in the present context may be, for example, portable, pocket-storable, hand- held, computer-comprised, or vehicle-mounted mobile devices, enabled to communicate voice and/or data, via the RAN, with another entity, such as another terminal or a server.

Communication devices may also be network nodes, such as radio network nodes, e.g., Transmission Points (TP). The wireless communications network covers a geographical area which may be divided into cell areas, each cell area being served by a network node such as a Base Station (BS), e.g. a Radio Base Station (RBS), which sometimes may be referred to as e.g., gNB, evolved Node B (“eNB”), “eNodeB”, “NodeB”,“B node”, or BTS (Base T ransceiver Station), depending on the technology and terminology used. The base stations may be of different classes such as e.g. Wide Area Base Stations, Medium Range Base Stations, Local Area Base Stations and Home Base Stations, based on transmission power and thereby also cell size. A cell is the geographical area where radio coverage is provided by the base station at a base station site. One base station, situated on the base station site, may serve one or several cells. Further, each base station may support one or several communication technologies. The wireless communications network may also be a non-cellular system, comprising network nodes which may serve receiving nodes, such as wireless devices, with serving beams. In 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE), base stations, which may be referred to as eNodeBs or even eNBs, may be directly connected to one or more core networks. In the context of this disclosure, the expression Downlink (DL) may be used for the transmission path from the base station to the wireless device. The expression Uplink (UL) may be used for the transmission path in the opposite direction i.e., from the wireless device to the base station.

The so-called 5G system, from a radio perspective started to be standardized in 3GPP, and the so-called New Radio (NR) is the name for the radio interface. One of the characteristics is that the frequency range going to higher frequencies than LTE, e.g., above 6 GHz, where it is known to have more challenging propagation conditions such as a higher penetration loss. To mitigate some of these effects, multi-antenna technologies such as beamforming may be massively used. Yet another NR characteristic is the use of multiple numerologies in DL and UL in a cell or for a UE and/or in different frequency bands. Yet another characteristic is the possibility to enable shorter latencies. NR architecture is being discussed in 3GPP. In the current concept, gNB denotes NR BS, where one NR BS may correspond to one or more transmission/reception points.

The current 5G RAN (NG-RAN) architecture is described in TS38.401 as schematically depicted in the example of Figure 1.

The NG architecture may be further described as follows:

• The NG-RAN consists of a set of gNBs 12, 14 connected to the 5GC 22 through the NG.

• A gNB 12, 14 can support FDD mode, TDD mode or dual mode operation.

• gNBs 12, 14 can be interconnected through the Xn 20.

• A gNB 14 may consist of a gNB-CU 18 and gNB-DUs 16a, 16b.

• A gNB-CU 18 and a gNB-DU 16a, 16b is connected via F1 logical interface.

One gNB-DU 16a, 16b is connected to only one gNB-CU 18.

NG, Xn and F1 are logical interfaces. For NG-RAN, the NG and Xn-C 20 interfaces for a gNB 14 consisting of a gNB-CU 18 and gNB-DUs 16a, 16b, terminate in the gNB- CU 18. For EN-DC, the S1 -U and X2-C 20 interfaces for a gNB 14 consisting of a gNB- CU 18 and gNB-DUs 16a, 16b, terminate in the gNB-CU 18. The gNB-CU 18 and connected gNB-DUs 16a, 16b are only visible to other gNBs 12 and the 5GC 22 as a gNB 14.

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 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 and signalling transport. In NG-Flex configuration, each gNB is connected to all AMFs within an AMF Region. The AMF Region is defined in 3GPP TS 23.501 .

The general principles for the specification of the F1 interface are as follows: the F1 interface is be open;

the F1 interface supports the exchange of signalling information between the endpoints, in addition the interface shall support data transmission to the respective endpoints; from a logical standpoint, the F1 is a point-to-point interface between the endpoints (a point-to-point logical interface may be feasible even in the absence of a physical direct connection between the endpoints); the F1 interface supports control plane and user plane separation; the F1 interface separates Radio Network Layer and Transport Network

Layer; the F1 interface enable exchanges of UE associated information and non- UE associated information; the F1 interface is defined to be future proof to fulfil different new requirements, support new services and new functions; one gNB-CU and set of gNB-DUs are visible to other logical nodes as a gNB. The gNB terminates X2, Xn, NG and S1 -U interfaces; the CU may be separated in control plane (CP) and user plane (UP).

3GPP RAN WG3 has also started working on a new open interface between the control plane (CU-CP) and the user plane (CU-UP) parts of the CU. The related agreements are collected in TR 38.806.The open interface between CU-CP and CU- UP is named E1 . A non-limiting example of the architecture is shown in Figure 2.

Three deployment scenarios for the split gNB are shown in TR 38.806:

- Scenario 1 : CU-CP and CU-UP centralized;

- Scenario 2: CU-CP distributed and CU-UP centralized;

- Scenario 3: CU-CP centralized and CU-UP distributed.

The E1 application protocol (E1 AP) is defined in TS 38.463. The E1 AP defines the messages that are exchanged between the CU-CP and the CU-UP for the sake of providing user-plane services to the UE.

E-UTRAN supports Dual Connectivity (DC) operation whereby a multiple Rx/Tx UE in RRC_CONNECTED is configured to utilize radio resources provided by two distinct schedulers, located in two eNBs (radio base stations) connected via a non-ideal backhaul over the X2 interface (see 3GPP 36.300).“Non-ideal-backhaul” implies that the transport of messages over the X2 interface between the nodes may be subject to both packet delays and losses. eNBs involved in DC for a certain UE may assume two different roles: an eNB may either act as an MN (Master node), also referred to as Master eNB (MeNB), or as an SN (Secondary node), also referred to as Secondary eNB. (SeNB). In DC a UE is connected to one MN and one SN. Thus, an eNB can act both as an MN and an SN at the same time, for different UEs. In LTE DC, only MeNB has RRC connection with UE, therefore only MeNB can send RRC signaling toward UE. For mobility measurement, MeNB configure UE which frequency to measure and how to report etc. Correspondingly UE send measurement result to MeNB once criterion is met. According to LTE principle, when UE may need to send measurement report, whatever it is due to event triggered or due to periodic trigger, UE may need to always send measurement results of serving cell to network. For UE in LTE-DC, serving cell means both cells in MCG (MN) and cell in SCG (SN). In LTE, only inter-frequency DC is supported (i.e. the MCG and SCG may need to operate in different carrier frequencies). Note that this subclause on LTE-DC is provided only as background information, while embodiments herein are intended to be applied to 5G DC solutions (as discussed below).

In 3GPP, a study item on a new radio interface for 5G has recently been completed and 3GPP has now continued with the effort to standardize this new radio interface, often abbreviated by NR (New Radio). LTE-NR DC (also referred to as LTE-NR tight interworking or EN-DC) is currently being defined for Release 15 of the 3GPP specifications.

In this context, the major changes from LTE-DC (Release 12) are described below:

• The introduction of split bearer from the SN (known as SCG split bearer). The SN in this case is also referred to as SgNB (secondary gNB, where gNB denotes the NR base station);

• The introduction of split bearer for RRC (known as split SRB);

• The introduction of a direct RRC from the SN (known as SCG SRB or direct SRB or SRB3).

Figure 3 and Figure 4 show non-limiting examples of the UP and Control Plane (CP) architectures, respectively, for NR dual connectivity and LTE-NR tight interworking.

From Figure 4 shows that separate Signaling Radio Bearers (SRBs) 402-406 are supported both from the MN 408 and SN 410. This means that a UE can receive signaling messages, i.e. RRC messages (Radio Resource Control messages) both from the MN 408 and the SN 410. There will thus be two RRC instances responsible for controlling the UE - one directed from the MN 408 and another from the SN 410 in the depicted scenario.

The consequence of this architecture is that the UE may need to terminate RRC signaling from two instances: both from the MN 408 and the SN 410. The motivation for introducing such multiple RRC instances in NR DC, and in LTE-NR DC, is that the MN 408 and SN 410 will partly be autonomously responsible for the control of radio resources. For example, the MN 408 is allocating resources from some spectrum using LTE, while the SN 410 will be responsible for configuring and allocating resources from some other spectrum that uses NR. As challenges for allocating resources in LTE and NR may differ substantially (e.g., since NR might be allocated in a spectrum where beam forming is highly desirable, while LTE might be allocated in a spectrum with good coverage but with very congested resources), it is important that the SN 410 has some level of autonomy to configure and manage the UE on resources associated with the SN 410. On the other hand, the overall responsibility for connectivity to the UE will likely be at MN node 408, so the MN node 408 has the overall responsibility e.g. for mobility, state changes of the UE, for meeting quality of service demands of the UE, etc.

The MN 408 and SN 410 may be nodes that use LTE (4G) or NR (5G) radio access technologies. They may both support the same technology, or they may support different technologies.

In the current work in 3GPP, the first step is to support the scenario where the MN 408 uses LTE, connected to the Evolved Packet Core (EPC) and the SN 410 uses NR. In this first step, the NR node (SN 410 in this scenario) in the control plane is not connected directly to the core-network, but all control plane signalling to and from the UE is carried via the MN 408 from/to the EPC. This scenario is also known as non- stand alone NR. After the completion of this alternative, 3GPP will then likely continue with standardization efforts that encompass other scenarios, such as when the NR node (also called gNB, i.e. a base-station supporting NR radio) is connected to the Next Generation Core and acts as an MN 408. The dual connectivity for NR includes many scenarios, such as:

1 . The MN 408 supports LTE and SN 410 supports NR;

2. The MN 408 supports NR and the SN 410 supports LTE;

3. Both MN 408 and SN 410 support NR.

From UE perspective, both the cells that operates in LTE and the cells that operates in NR are its serving cell. To summarize, an example of the Control plane architecture for LTE DC and EN-DC is depicted in Figure 5.

The following terminologies are used to differentiate different dual connectivity scenarios:

DC: LTE DC (i.e. both MN 502 and SN 504 employ LTE)

EN-DC: LTE-NR dual connectivity where LTE is the master 506 and NR is the secondary 508

NE-DC: LTE-NR dual connectivity where NR is the master and LTE is the secondary NR-DC (or NR-NR DC): both MN and SN employ NR

MR-DC (multi-RAT DC): a generic term to describe where the MN and SN employ different RATs (EN-DC is one example of MR-DC)

It is also worth noting that while in Release 15 only dual-connectivity is supported. Existing methods do not support multi-connectivity solutions, where the UE may be served simultaneously by more than two nodes.

Summary

It is an object of embodiments herein to improve communications in a wireless communications network.

Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments.

In one aspect, the present disclosure provides a method performed by a first communication node operable in a wireless communications network. The method comprises providing, to a second communication node operable in the wireless communications network, a first indicator indicating a plurality of cell groups for a split bearer to be set up by the second communication node; and receiving, from the second communication node, a first response based on the first indicator.

In another aspect, the present disclosure provides a method performed by a second communication node operable in a wireless communications network. The method comprises receiving, from a first communication node operable in the wireless communications network, a first indicator indicating a plurality of cell groups for a split bearer to be set up by the second communication node; and providing, to the first communication node, a first response based on the first indicator.

Apparatus are also provided for performing the methods set out above. For example, in one aspect there is provided a first communication node operable in a wireless communications network. The first communication node comprises processing circuitry and memory, the memory storing instructions which, when executed by the processing circuitry, cause the first communication node to provide, to a second communication node operable in the wireless communications network, a first indicator indicating a plurality of cell groups for a split bearer to be set up by the second communication node; and receive, from the second communication node, a first response based on the first indicator.

In another aspect, there is provided a second communication node operable in a wireless communications network. The second communication node comprises processing circuitry and memory. The memory stores instructions which, when executed by the processing circuitry, cause the second communication node to receive, from a first communication node operable in the wireless communications network, a first indicator indicating a plurality of cell groups for a split bearer to be set up by the second communication node; and provide, to the first communication node, a first response based on the first indicator.

Another aspect relates to a method, performed by the first communication node 101 is described herein. The method may be understood to be for handling a plurality of cell groups. The first communication node 101 may operate in the wireless communications network 100. The method may comprise the following actions: o Providing 702, to the second communication node 102, a first indicator indicating a plurality of cell groups, or radio legs, for a split bearer to be set up by the second communication node 102.

The second communication node 102 may operate in the wireless communications network 100. o Receiving 703 a first response from the second communication node 102, based on the provided first indicator.

A further aspect relates to a method, performed by the second communication node 102 is described herein. The method may be understood to be for handling a plurality of cell groups. The second communication node 102 may operate in the wireless communications network 100. The method may comprise the following actions: o Receiving 801 , from the first communication node 101 , the first indicator. The first indicator may indicate the plurality of cell groups, or radio legs, for the split bearer to be set up by the second communication node 102.

The first communication node 101 may operate in the wireless communications network 100.

0 Providing 802 the first response to the first communication node 101 , based on the received first indicator.

By the first communication node 101 providing the first indicator to the second communication node 102, the first communication node 101 enables the first communication node 101 to setup a split bearer in the second communication node 102. This may allow to increase data throughput, e.g., for a wireless device such as the wireless device 130, reduce interruption time during mobility, and to take advantage of other features related LTE/NR and NR/NR dual-connectivity.

Brief description of the drawings

Examples of embodiments herein are described in more detail with reference to the accompanying drawings, and according to the following description.

Figure 1 is a schematic diagram depicting the overall architecture of a 5G RAN (NG- RAN).

Figure 2 is a schematic diagram depicting a split gNB architecture.

Figure 3 is a schematic diagram depicting an LTE-NR tight interworking (user- plane). Figure 4 is a schematic diagram depicting an LTE-NR tight interworking (control- plane).

Figure 5 is a schematic diagram depicting a C-plane architecture for Dual Connectivity in LTE DC and EN-DC.

Figure 6 is a schematic diagram illustrating a wireless communications network, according to embodiments herein.

Figure 7 is a flowchart depicting a method in a first communication node, according to embodiments herein.

Figure 8 is a flowchart depicting a method in a second communication node, according to embodiments herein. Figure 9 is a schematic diagram depicting a non-limiting example of a setup of a

DRB1 with two cell groups (i.e., radio legs), according to embodiments herein.

Figure 10 is a schematic diagram depicting a non-limiting example of removal of one cell group (i.e., radio leg) for DRB1 , according to embodiments herein. Figure 1 1 is a schematic block diagram illustrating two non-limiting examples, a) and b), of a first communication node, according to embodiments herein.

Figure 12 is a schematic block diagram illustrating two non-limiting examples, a) and b), of a second communication node, according to embodiments herein. Figure 13 is a schematic block diagram illustrating a telecommunication network connected via an intermediate network to a host computer, according to embodiments herein.

Figure 14 is a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection, according to embodiments herein.

Figure 15 is a flowchart depicting embodiments of a method in a communications system including a host computer, a base station and a user equipment, according to embodiments herein.

Figure 16 is a flowchart depicting embodiments of a method in a communications system including a host computer, a base station and a user equipment, according to embodiments herein.

Figure 17 is a flowchart depicting embodiments of a method in a communications system including a host computer, a base station and a user equipment, according to embodiments herein. Figure 18 is a flowchart depicting embodiments of a method in a communications system including a host computer, a base station and a user equipment, according to embodiments herein.

Detailed description As part of the development of embodiments herein, one or more problems with the existing technology will first be identified and discussed.

As shown in Figure 3, in the user-plane in dual-connectivity it is possible to establish split bearers. A split bearer may be characterized by:

(1 ) A single PDCP entity that is located either in the MN or in the SN. The split bearer is referred to as MN-terminated if the PDCP entity is located in the MN; and SN-terminated if the PDCP entity is located in the SN.

(2) Two cell groups (or radio legs or RLC/MAC entities). One cell group is located in the MN and is referred to as master cell group (MCG); and the other cell group is located in the SN and is referred to as secondary cell group (SCG).

In multi-connectivity, it is expected that a split bearer can be configured with more than two cell groups (one cell group per network node serving the UE). For example, for forward compatibility the current RRC signalling in TS 38.331 is already designed to configure up to four cell groups for the same split bearer. It may be possible for the network to dynamically add/remove/modify a cell group (or radio leg) of a split bearer based on e.g., the radio conditions and the services requested by the UE.

In NG-RAN, the CU-CP decides when to add/remove/modify a cell group for a split bearer. This is because the CU-CP receives the measurement reports from the UE and therefore is aware about the radio conditions. Besides, the CU-CP is also aware of the services that are requested for the UE. The CU-CP may then be able to request the CU- UP to setup a split bearer and it may also be able to request the CU-UP to add/remove/modify a cell group (or radio leg) for the split bearer. This requires appropriate signalling over the E1 interface. It also requires the capability of identifying the cell group (or radio leg) of a split bearer over the E1 interface.

The CU-UP may assign one UL tunnel endpoint identifier (UL TEID) for each cell group (or radio leg) of a split bearer. This is because each cell group (or radio leg) requires a separate GTP tunnel over the RAN interfaces (F1 , X2 and/or Xn). The CU-UP may also provide to the CU-CP the mapping between the UL TEID and the cell group (or radio leg).

Currently, the E1 application protocol as defined in TS 38.806, TS 38.460 and TS 38.463 does not offer the possibility for: setting up a split bearer, identifying the cell group (or radio leg) of a split bearer, adding/removing/modifying a given radio leg of a split bearer.

Certain aspects of the present disclosure and their embodiments may provide solutions to this challenge or other challenges. There are, proposed herein, various embodiments which address one or more of the issues disclosed herein.

Embodiments herein may be understood to address these problems in existing methods by providing one or more methods related to a mechanism that may allow the establishment and management of split DRBs in NG-RAN over the E1 interface between CU-CP and CU-UP.

Particular embodiments herein may be understood to be related to methods for multi connectivity over E1 .

Some of the embodiments contemplated will now be described more fully hereinafter with reference to the accompanying drawings, in which examples are shown. In this section, the embodiments herein will be illustrated in more detail by a number of exemplary embodiments. Other embodiments, however, are contained within the scope of the subject matter disclosed herein. The disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. It should be noted that the exemplary embodiments herein are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments.

Note that although terminology from LTE/5G has been used in this disclosure to exemplify the embodiments herein, this should not be seen as limiting the scope of the embodiments herein to only the aforementioned system. Other wireless systems with similar features, may also benefit from exploiting the ideas covered within this disclosure.

Figure 6 depicts two non-limiting examples, in panels“a” and“b”, respectively, of a computer system 10, in which embodiments herein may be implemented. In some example implementations, such as that depicted in the non-limiting example of Figure 6a, the computer system 10 may be a computer network. In other example implementations, such as that depicted in the non-limiting example of Figure 6b, the computer system 10 may be implemented in a wireless communications network 100, sometimes also referred to as a wireless communications system, cellular radio system, telecommunications network, or cellular network, in which embodiments herein may be implemented. The wireless communications network 100 may typically be a 5G system, 5G network, NR-U or Next Gen System or network, LAA, or MulteFire. The wireless communications network 100 may alternatively be a younger system than a 5G system The wireless communications network 100 may support other technologies such as, for example, Long-Term Evolution (LTE), LTE- Advanced / LTE-Advanced Pro, e.g. LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), LTE Half-Duplex Frequency Division Duplex (HD-FDD), LTE operating in an unlicensed band, NB-loT. Thus, although terminology from 5G/NR and LTE may be used in this disclosure to exemplify embodiments herein, this should not be seen as limiting the scope of the embodiments herein to only the aforementioned systems.

The computer system 10 comprises a plurality of communication nodes, whereof a first communication node 101 , a second communication node 102, a third communication node 103 and a fourth communication node 104 are depicted in the non-limiting examples of Figure 6, in panel a) and panel b). Each of the first communication node 101 , the second communication node 102, the third communication node 103 and the fourth communication node 104 may be understood, respectively, as a first computer, a second computer, a third computer, and a fourth computer, or as logical entities within the computer system 10. The computer system may typically be, as depicted in the example of Figure 6 panel b), a radio network node, such as the radio network node 1 10, which will be described later. The first communication node 101 , the second communication node 102, the third communication node 103, and the fourth communication node 104 may operate as part of the same radio network node 1 10. In other words, the first communication node 101 , the second communication node 102, the third communication node 103, and the fourth communication node 104 may be comprised in a same radio network node 1 10.

In some particular embodiments, the first communication node 101 may be a Central Unit Control Plane (CU-CP) entity, and the second communication node 102 is a Central Unit User Plane (CU-CP) entity.

In some embodiments, the third communication node 103 may be a first Distribution Unit (DU) and the fourth communication node 104 may be a second DU. The third communication node 103 and the fourth communication node 104 may operate as part of a same radio network node 1 10.

In some examples, any of the first communication node 101 , the second communication node 102, the third communication node 103 and the fourth communication node 104 may be implemented, as a standalone server in e.g., a host computer in the cloud, which is not depicted in the examples of Figure 6. Any of the first communication node 101 , the second communication node 102, the third communication node 103 and the fourth communication node 104 may in some examples be a distributed node or distributed server, with some of their respective functions being implemented locally, and some of its functions implemented in the cloud. Yet in other examples, any of the first communication node 101 , the second communication node 102, the third communication node 103 and the fourth communication node 104 may be may also be implemented as processing resources in a server farm. Any of the first communication node 101 , the second communication node 102, the third communication node 103 and the fourth communication node 104 may be may be under the ownership or control of a service provider.

A radio network node 1 10 is depicted in the non-limiting examples of Figure 6. The radio network node 1 10 may be comprised in the wireless communications network 100, which may comprise a plurality of network nodes. The radio network node 1 10 may be a radio network node, such as a radio base station, or any other network node with similar features capable of serving a wireless device, such as a user equipment or a machine type communication device, in the wireless communications network 100. In some particular embodiments, the radio network node 1 10 may be a transmission point operating on NR, for example a New Radio (NR) NodeB or a Next Generation radio network node, that is, a gNB. In some examples, the radio network node 1 10 may be radio base station operating on LTE, such as an eNB.

The wireless communications network 100 covers a geographical area which may be divided into cell areas, wherein each cell area may be served by a network node, although, one radio network node may serve one or several cells. The wireless communications network 100 may comprise at least a cell 120. In the non- limiting example depicted in Figure 6, panel a), the radio network node 1 10 serves the cell 120. The radio network node 1 10 may be of different classes, such as, e.g., macro base station (BS), home BS or pico BS, based on transmission power and thereby also cell size. The radio network node 1 10 may be directly connected to one or more core networks, which are not depicted in Figure 6 to simplify the Figure. In some examples, the radio network node 1 10 may be a distributed node, such as a virtual node in the cloud, and it may perform its functions entirely on the cloud, or partially, in collaboration with a radio network node.

A plurality of wireless devices may be located in the wireless communication network 100, whereof a wireless device 130, which may also be referred to as a device, is depicted in the non-limiting example of Figure 6, panel b). The wireless device 130, e.g., a 5G UE, may be a wireless communication device which may also be known as e.g., a UE, a mobile terminal, wireless terminal and/or mobile station, a mobile telephone, cellular telephone, or laptop with wireless capability, just to mention some further examples. The wireless device 130 may be, for example, portable, pocket-storable, hand-held, computer-comprised, or a vehicle-mounted mobile device, enabled to communicate voice and/or data, via the RAN, with another entity, such as a server, a laptop, a Personal Digital Assistant (PDA), or a tablet, Machine-to-Machine (M2M) device, device equipped with a wireless interface, such as a printer or a file storage device, modem, or any other radio network unit capable of communicating over a radio link in a communications system. The wireless device 130 comprised in the wireless communications network 100 may be enabled to communicate wirelessly in the wireless communications network 100. The communication may be performed e.g., via a RAN, and possibly the one or more core networks, which may be comprised within the wireless communications network 100.

The radio network node 1 10 may be configured to communicate in the wireless communications network 100 with the wireless device 130 over a radio link 140, although communication over more links may be possible.

The first communication node 101 is configured to communicate within the computer system 10 with the second communication node 102 over a first link 151 , e.g., a radio link or a wired link. The first communication node 101 is configured to communicate within the computer system 10 with the third communication node 103 over a second link 152, e.g., another radio link or another wired link. The first communication node 101 is configured to communicate within the computer system 10 with the fourth communication node 104 over a third link 153, e.g., another radio link or another wired link. The second communication node 102 may be further configured to communicate within the computer system 10 with the third communication node 103 over a fourth link 154, e.g., another radio link, a wired link, an infrared link, etc... The second communication node 102 may be further configured to communicate within the computer system 10 with the fourth communication node 104 over a fifth link 155, e.g., another radio link, a wired link, an infrared link, etc...

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

In general, the usage of “first”,“second”,“third”,“fourth”,“fifth� �,“sixth”,“seventh”, “eighth”, and/or“ninth” herein may be understood to be an arbitrary way to denote different elements or entities, and may be understood to not confer a cumulative or chronological character to the nouns they modify, unless otherwise noted, based on context.

Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments.

More specifically, the following are embodiments related to the first communication node 101 , and to the second communication node 102.

The first communication node 101 embodiments relate to Figure 7, Figure 9, Figure 10, Figure 11 , and Figures 13-18.

A method, performed by the first communication node 101 is described herein. The method may be understood to be for handling a plurality of cell groups. The first communication node 101 may operate in the wireless communications network 100. The method may comprise the following actions.

In some embodiments all the actions may be performed. In some embodiments, one or more actions may be performed. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. In Figure 7, optional actions are indicated with dashed lines. Some actions may be performed in a different order than that shown in Figure 7. o Providing 702, to the second communication node 102, a first indicator indicating a plurality of cell groups, or radio legs, for a split bearer to be set up by the second communication node 102.

The second communication node 102 may operate in the wireless communications network 100. The first communication node 101 may be configured to perform this providing 702 action, e.g. by means of a providing unit 1101 within the first communication node 101 , configured to perform this action. The providing unit 1 101 may be a processor 1 106 of the first communication node 101 , or an application running on such processor.

Providing may be understood as e.g., initiating sending or sending, e.g., via the first link 151 .

In some embodiments, the first indicator may indicate, via, e.g., an information element, one of: a) a number of cell groups in the plurality of cell groups, and b) a list of the cell groups in the plurality of cell groups. Some examples of the information element are described later.

The split bearer may support New Radio-New Radio-Dual Connectivity (NR- NR- DC) between the third communication node 103 and the fourth communication node 104. The third communication node 103 may provide a Master Cell Group (MCG) and the fourth communication node 104 may provide a Secondary Cell Group (SCG).

In some examples, the split bearer may support NR-NR-Multi Connectivity (NR- NR-MC) between the third communication node 103 and the fourth communication node 104.

The first indicator may be provided comprised in a Bearer Context Setup Request message. o Receiving 703 a first response from the second communication node 102, based on the provided first indicator. The first communication node 101 may be configured to perform this receiving action 703, e.g. by means of a receiving unit 1 102 within the first communication node 101 , configured to perform this action. The receiving unit 1 102 may be the processor 1 106 of the first communication node 101 , or an application running on such processor.

The receiving may be performed via, e.g., the first link 151 .

The first response may comprise a second indicator. The second indicator may identify each cell group in the plurality of cell groups in the uplink (UL). For example, the second indicator may indicate a General Packet Radio Service (GPRS) tunnelling protocol (GTP) tunnel endpoint identifier (TEID), for each cell group in the plurality of cell groups. In some embodiments, the method may further comprise one or more of the actions: o Determining 701 to set up the split bearer. The first communication node 101 may be configured to perform this determining action 701 , e.g., by means of a determining unit 1103 within the first communication node 101 , configured to perform this action. The determining unit 1 103 may be the processor 1 106 of the first communication node 101 , or an application running on such processor. o Providing 704, to the third communication node 103, a third indicator indicating to configure an MCG. The MCG may be comprised within the plurality of cell groups. The first communication node 101 may be configured to perform this providing action 704, e.g. by means of the providing unit 1 101 within the first communication node 101 , configured to perform this action. o Providing 705, to the fourth communication node 104, a fourth indicator indicating to configure an SCG. The SCG may be comprised within the plurality of cell groups. The first communication node 101 may be configured to perform this providing action 705, e.g. by means of the providing unit 1 101 within the first communication node 101 , configured to perform this action. o Providing 706, to the second communication node 102, a fifth indicator identifying each cell group in the plurality of cell groups in the downlink (DL). For example, the fifth indicator may indicate a GTP TEID for each cell group in the plurality of cell groups. The first communication node 101 may be configured to perform this providing action 706, e.g. by means of the providing unit 1 101 within the first communication node 101 , configured to perform this action. o Receiving 707 a second response from the second communication node 102, based on the provided fifth indicator. The first communication node 101 may be configured to perform this receiving action 707, e.g. by means of a receiving unit 1102 within the first communication node 101 , configured to perform this action. o Determining 708 to remove the SCG. The first communication node 101 may be configured to perform this determining action 708, e.g., by means of the determining unit 1 103 within the first communication node 101 , configured to perform this action. o Providing 709 a sixth indicator to the second communication node 102, based on the determination. The sixth indicator may indicate that the second communication node 102 is to refrain from transmitting data for a cell group associated with the SCG. The first communication node 101 may be configured to perform this providing action 709, e.g. by means of the providing unit 1 101 within the first communication node 101 , configured to perform this action. o Receiving 710 a third response from the second communication node 102, based on the provided sixth indicator. The third response may confirm that the second communication node 102 refrains from transmitting data for the cell group associated with the SCG. The first communication node 101 may be configured to perform this receiving action 710, e.g. by means of the receiving unit 1 102 within the first communication node 101 , configured to perform this action. o Providing 711 , to the third communication node 103, and based on the received third response, a seventh indicator. The seventh indicator may indicate a radio resource control reconfiguration. The first communication node 101 may be configured to perform this providing action 71 1 , e.g. by means of the providing unit 1 101 within the first communication node 101 , configured to perform this action. o Providing 712, to the fourth communication node 104, and based on the received third response, an eighth indicator. The eighth indicator may indicate to refrain from transmitting data for the cell group associated with the SCG. The first communication node 101 may be configured to perform this providing action 712, e.g. by means of the providing unit 1 101 within the first communication node 101 , configured to perform this action. o Providing 713 a ninth indicator to the second communication node 102, based on the determination. The ninth indicator may indicate that the second communication node 102 is to remove the cell group associated with the SCG. The first communication node 101 may be configured to perform this providing action 713, e.g. by means of the providing unit 1 101 within the first communication node 101 , configured to perform this action. o Releasing 714 resources, e.g., a context, established for the cell group associated with the SCG. The first communication node 101 may be configured to perform this releasing action 714, e.g. by means of a releasing unit 1104 within the first communication node 101 , configured to perform this action. The releasing unit 1 104 may be the processor 1 106 of the first communication node 101 , or an application running on such processor. o Receiving 715 a fourth response from the second communication node 102, based on the provided ninth indicator. The fourth response may confirm that the second communication node 102 has removed the cell group associated with the SCG. The first communication node 101 may be configured to perform this receiving action 715, e.g. by means of the receiving unit 1 102 within the first communication node 101 , configured to perform this action.

Other units 1105 may be comprised in the first communication node 101 . In Figure 1 1 , optional units are indicated with dashed boxes.

The first communication node 101 may comprise an interface unit to facilitate communications between the first communication node 101 and other nodes or devices, e.g., the second communication node 102, the third communication node 103, the fourth communication node 104, or any of the other nodes. In some particular examples, the interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

The first communication node 101 may comprise an arrangement as shown in Figure 1 1 or in Figure 14.

Some embodiments herein will now be further described with some non- limiting examples.

The second communication node 102 embodiments relate to Figure 8, Figure 9, Figure 10, Figure 12, and Figures 13-18.

A method, performed by the second communication node 102 is described herein. The method may be understood to be for handling a plurality of cell groups. The second communication node 102 may operate in the wireless communications network 100. The method may comprise the following actions.

In some embodiments all the actions may be performed. In some embodiments, one or more actions may be performed. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. In Figure 8, optional actions are indicated with dashed lines. Some actions may be performed in a different order than that shown in Figure 8. o Receiving 801 , from the first communication node 101 , the first indicator. The first indicator may indicate the plurality of cell groups, or radio legs, for the split bearer to be set up by the second communication node 102.

The first communication node 101 may operate in the wireless communications network 100.

The second communication node 102 may be configured to perform this receiving 801 action, e.g. by means of a receiving unit 1201 within the second communication node 102, configured to perform this action. The receiving unit 1201 may be a processor 1204 of the second communication node 102, or an application running on such processor.

The receiving may be performed via, e.g., the first link 151 .

In some embodiments, the first indicator may indicate, via, e.g., the information element, one of: a) the number of cell groups in the plurality of cell groups, and b) the list of the cell groups in the plurality of cell groups. Some examples of the information element are described later.

The split bearer may support New Radio-New Radio-Dual Connectivity (NR- NR- DC) between the third communication node 103 and the fourth communication node 104. The third communication node 103 may provide the Master Cell Group (MCG) and the fourth communication node 104 may provide the Secondary Cell Group (SCG).

In some examples, the split bearer may support NR-NR-Multi Connectivity (NR- NR-MC) between the third communication node 103 and the fourth communication node 104.

The first indicator may be provided comprised in a Bearer Context Setup Request message. o Providing 802 the first response to the first communication node

101 , based on the received first indicator. The second communication node 102 may be configured to perform this providing action 802, e.g. by means of a providing unit 1202 within the second communication node 102, configured to perform this action. The providing unit 1202 may be the processor 1204 of the second communication node 102, or an application running on such processor.

Providing may be understood as e.g., initiating sending or sending, e.g., via the first link 151.

The first response may comprise the second indicator. The second indicator may identify each cell group in the plurality of cell groups in the uplink (UL). For example, the second indicator may indicate the GTP TEID, for each cell group in the plurality of cell groups.

In some embodiments, the method may further comprise one or more of the actions: o Receiving 803, from the first communication node 101 , the fifth indicator. The fifth indicator may identify each cell group in the plurality of cell groups in the DL. For example, the fifth indicator may indicate the GTP TEID for each cell group in the plurality of cell groups. The second communication node 102 may be configured to perform this receiving 803 action, e.g. by means of the receiving unit 1201 within the second communication node 102, configured to perform this action. o Providing 804 the second response to the first communication node 101 , based on the received fifth indicator. The second communication node 102 may be configured to perform this providing action 804, e.g. by means of the providing unit 1202 within the second communication node 102, configured to perform this action. o Receiving 805 the sixth indicator from the first communication node 101 . The sixth indicator may indicate that the second communication node 102 is to refrain from transmitting data for a cell group associated with the SCG. The second communication node 102 may be configured to perform this receiving 805 action, e.g. by means of the receiving unit 1201 within the second communication node 102, configured to perform this action. o Providing 806 the third response to the first communication node 101 , based on the received sixth indicator. The third response may confirm that the second communication node 102 refrains from transmitting data for the cell group associated with the SCG. The second communication node 102 may be configured to perform this providing action 805, e.g. by means of the providing unit 1202 within the second communication node 102, configured to perform this action. o Receiving 807 the ninth indicator from the first communication node 101. The ninth indicator may indicate that the second communication node 102 is to remove the cell group associated with the SCG. The second communication node 102 may be configured to perform this receiving 807 action, e.g. by means of the receiving unit 1201 within the second communication node 102, configured to perform this action. o Providing 808 the fourth response to the first communication node 101 , based on the received ninth indicator. The fourth response may confirm that the second communication node 102 has removed the cell group associated with the SCG. The second communication node 102 may be configured to perform this providing action 808, e.g. by means of the providing unit 1202 within the second communication node 102, configured to perform this action.

Other units 1203 may be comprised in the second communication node 102.

In Figure 1 1 , optional units are indicated with dashed boxes.

The second communication node 102 may comprise an interface unit to facilitate communications between the second communication node 102 and other nodes or devices, e.g., the second communication node 102, the third communication node 103, the fourth communication node 104, or any of the other nodes. In some particular examples, the interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

The second communication node 102 may comprise an arrangement as shown in Figure 12 or in Figure 14.

Some embodiments herein will now be further described with some non- limiting examples.

In the following description, any reference to a/the gNB-CU-CP may be understood to equally refer the first communication node 101 ; any reference to a/the gNB-CU-UP may be understood to equally refer the second communication node 102; any reference to a/the gNB-DU1 may be understood to equally refer the third communication node 103; any reference to a/the gNB-DU2 may be understood to equally refer the fourth communication node 104.

As an overview of the examples of the embodiments that will be described next, particular examples of embodiments herein may be understood to relate to methods over the E1 interface for setting up a split bearer, identifying the cell group (or radio leg) of a split bearer, adding/removing/modifying a radio leg of a split bearer.

Overview of examples 1 . The CU-CP can include in the E1 Bearer Context Setup Request message, as part of the bearer configuration information, a new information element (e.g., an integer) that indicates the number of cell groups (or radio legs) for the bearer. The new information element (IE) is referred to as Leg Setup. The CU-UP reserves for the split bearer a number of UL TEIDs that corresponds to the number indicated in the Leg Setup IE. The CU-UP also assigns a Leg ID to each radio leg. The CU-UP includes in the E1 Bearer Context Setup Response message the assigned UL TEIDs and the corresponding Leg ID. A possible realization of this method is illustrated in Examples provided below.

2. Alternatively, the CU-CP can include in the E1 Bearer Context Setup Request message, as part of the bearer configuration information, a list of cell groups that are configured for the split bearer. Each cell group is characterized by a CG-ID that is defined in TS 38.331. For example, for dual-connectivity (Release 15): CG-ID = 0 indicates MCG and CG-ID = 1 indicates SCG. Additional CG-IDs will be assigned in TS 38.331 for multi-connectivity. The CU-UP assigns one UL TEID per CG-ID. The CU-UP includes in the E1 Bearer Context Setup Response message the assigned UL TEIDs and the corresponding CG-ID. A possible realization of this method is illustrated in the following five examples, in which more explanations and examples for the embodiments proposed herein are provided.

Example 1 : establishing a split bearer using embodiment 2 ( Overview of examples)

The procedure for configuring a split bearer (referred to as DRB1 in the following) with two cell groups (i.e., radio legs) using the solution described in embodiment 2 is shown in Figure 9.

0. The CU-CP 902 decides to setup DRB1 to support NR-NR-DC (NN-DC) between gNB-DU1 904 (providing the MCG) and gNB-DU2 906 (providing the SCG).

1 . The CU-CP 902 sends Bearer Context Setup Request message requesting to setup DRB1 with two cell groups and potentially providing the corresponding cell group IDs.

2. The CU-UP 908 responds with Bearer Context Setup Response message with two UL GTP TEIDs allocated for DRB1 (one per cell group). 3. The CU-CP 902 sends the F1 UE context Setup Request to gNB-DU1 904 to configure the MCG. The F1 UE Context Setup Request may include the RRC- Reconfiguration for the UE. The CU-CP 902 sends the F1 UE context Setup Request to gNB-DU2 906 to configure the SCG. 4. The CU-CP 902 sends the Bearer Context Modification Request message and provides two DL TEIDs for DRB1 (one per cell group).

5. The CU-UP 908 replies with Bearer Context Modification Response message. From this moment, the UE is configured with DRB1 with two cell groups, where the MCG is served by gNB-DU1 904 and the SCG is served bygNB-DU2 906.

Example 2: removing a cell group (or radio leg) of a split bearer using embodiment 2 ( Overview of examples)

Let us assume that after some time the CU-CP 902 decides to remove the SCG radio leg of DRB1 that has been established using the procedure in“example 1” (and is served by gNB-DU2 906). An example of the procedure is shown in Figure 10.

0. The CU-CP 902 decides to remove the SCG leg for DRB1 . (Note that according to TS 38.331 : MCG cell group = 0; SCG cell group = 1 ).

1 . The CU-CP 902 sends Bearer Context Modification Request message requesting the CU-UP 908 to stop DL data transmission for cell group 1 for DRB1 . 2. The CU-UP 908 responds with Bearer Context Modification Response message confirming that it stopped DL data transmission over cell group 1.

3. The CU-CP 902 sends the F1 UE Context Modification Request to gNB- DU1 904 with RRC-Reconfiguration message for the UE and optionally update in configuration for gNB-DU1 904 (e.g., change QoS parameters because the UE is not in DC anymore). The CU-CP 902 also sends F1 UE Context Modification Request to gNB- DU2 906 with UL TX stop indication.

4. The CU-CP 902 sends the Bearer Context Modification Request message requesting the CU-UP 908 to remove the leg corresponding to cell group 1.

5. In parallel to the step 4, the CU-CP 902 runs the F1 UE Context Release procedure to release the SCG resources in gNB-DU2 906. 6. The CU-UP 908 sense Bearer Context Modification Response message confirming that the leg corresponding to cell group 1 has been removed.

Table 1 a

Table 1 b Example 3: Bearer Context Setup Request message using embodiment 2

( Overview of examples).

An example of the simplified tabular structure of the Bearer Context Setup message based on embodiment 2 is shown in Table 1 a. Particularly, in Table 1 a, the information elements added as part of embodiments herein are found on the last row of the table.

A further example of the tabular structure of a Bearer Context Request Setup message is shown in Table 1 b. Table 1 b may be appended to Table 1 a, so that Tables 1 a and 1 b are sent together as part of a Bearer Context Request Setup message. The Cell Group Information IE is added as part of embodiments herein. It carries the information about the cell groups for a split bearer that the CU-CP requests the CU- UP to configure. It can be defined for example as shown in the following Table 2. In Table 2, the information elements added as part of embodiments herein are found on rows 2-6 of the table, that is, all except the header.

Table 2

9.3.1.B Cell Group Information

Upon receiving this information element (IE), the CU-UP knows how many UL TEIDs it may reserve for each DRB. The CU-UP may reply to the CU-CP by providing the UL TEIDs and the corresponding mapping to the cell group. This can be done for example by adding the following IE in the Bearer Context Setup Response message (see an example below in Table 3). Particularly, in Table 3, the information elements added as part of embodiments herein are found on the last row of the table Example 4: Bearer Context Setup request message using embodiment 1 ( Overview of examples).

Table 2

An example of the simplified tabular structure of the Bearer Context Setup message based on embodiment 1 is shown in Table 4. Particularly, in Table 4, the information elements added as part of embodiments herein are found on the last row of the table.

Table 3

Upon receiving the Leg Setup IE, the CU-UP knows how many UL TEIDs it may reserve for each DRB. The CU-UP may reply to the CU-UP by providing the UL TEIDs and a unique Leg ID. This can be done for example by adding the IE in Table 5 in the Bearer Context Setup Response message (see an example below). In Table 5, the information element added as part of embodiments herein is found on the last row of the table.

Table 4

Certain embodiments disclosed herein may provide one or more of the following technical advantage(s), which may be summarized as that they provide for mechanisms that allow the CU-CP to setup a split bearer in the CU-UP and identify each cell group (or radio leg) composing the split bearer over the E1 interface. This also enables the CU- CP to add/modify/release individual cell groups (or radio legs) of a split bearer.

Figure 11 depicts two different examples in panels a) and b), respectively, of the arrangement that the first communication node 101 may comprise. In some embodiments, the first communication node 101 may comprise the following arrangement depicted in Figure 11a.

The embodiments herein in the first communication node 101 may be implemented through one or more processors, such as a processor 1106 in the first communication node 101 depicted in Figure 1 1 a, together with computer program code for performing the functions and actions of the embodiments herein. A processor, as used herein, may be understood to be a hardware component. 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 first communication node 101 . 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 communication node 101 .

The first communication node 101 may further comprise a memory 1107 comprising one or more memory units. The memory 1 107 is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the first communication node 101 .

In some embodiments, the first communication node 101 may receive information from, e.g., the second communication node 102, the third communication node 103, and the fourth communication node 104, through a receiving port 1108. In some embodiments, the receiving port 1 108 may be, for example, connected to one or more antennas in first communication node 101 . In other embodiments, the first communication node 101 may receive information from another structure in the wireless communications network 100 through the receiving port 1 108. Since the receiving port 1 108 may be in communication with the processor 1 106, the receiving port 1 108 may then send the received information to the processor 1 106. The receiving port 1 108 may also be configured to receive other information.

The processor 1 106 in the first communication node 101 may be further configured to transmit or send information to e.g., the second communication node 102, the third communication node 103, and the fourth communication node 104, another structure in the wireless communications network 100, through a sending port 1109, which may be in communication with the processor 1 106, and the memory 1 107.

Those skilled in the art will also appreciate that the providing unit 1 101 , the receiving unit 1 102, the determining unit 1 103, the releasing unit 1 104, and the other units 1 105 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 memory, that, when executed by the one or more processors such as the processor 1 106, perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuit (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).

Also, in some embodiments, the different units 1 101 -1 105 described above may be implemented as one or more applications running on one or more processors such as the processor 1 106.

Thus, the methods according to the embodiments described herein for the first communication node 101 may be respectively implemented by means of a computer program 1110 product, comprising instructions, i.e., software code portions, which, when executed on at least one processor 1 106, cause the at least one processor 1 106 to carry out the actions described herein, as performed by the first communication node 101 . The computer program 1 1 10 product may be stored on a computer-readable storage medium 1111. The computer-readable storage medium 1 1 1 1 , having stored thereon the computer program 1 1 10, may comprise instructions which, when executed on at least one processor 1 106, cause the at least one processor 1 106 to carry out the actions described herein, as performed by the first communication node 101 . In some embodiments, the computer-readable storage medium 1 1 1 1 may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick. In other embodiments, the computer program 1 1 10 product may be stored on a carrier containing the computer program 1 1 10 just described, wherein the carrier is one of an electronic signal, optical signal, radio signal, or the computer-readable storage medium 1 1 1 1 , as described above.

The first communication node 101 may comprise a communication interface configured to facilitate communications between the first communication node 101 and other nodes or devices, e.g., the second communication node 102, the third communication node 103, and the fourth communication node 104. The interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

In other embodiments, the first communication node 101 may comprise the following arrangement depicted in Figure 11 b. The first communication node 101 may comprise a processing circuitry 1106, e.g., one or more processors such as the processor 1 106, in the first communication node 101 and the memory 1 107.

The first communication node 101 may also comprise a radio circuitry 1112, which may comprise e.g., the receiving port 1 108 and the sending port 1 109. The processing circuitry 1 106 may be configured to, or operable to, perform the method actions according to Figure 7, Figure 9, Figure 10, and/or Figures 14-18, in a similar manner as that described in relation to Figure 1 1 a. The radio circuitry 1 1 12 may be configured to set up and maintain at least a wireless connection with the first communication node 101 . Circuitry may be understood herein as a hardware component.

Flence, embodiments herein also relate to the first communication node 101 . The first communication node 101 may comprise the processing circuitry 1 106 and the memory 1 107, said memory 1 107 containing instructions executable by said processing circuitry 1 106, whereby the first communication node 101 is further operative to perform the actions described herein in relation to the first communication node 101 , e.g., in Figure 7, Figure 9, Figure 10, and/or Figures 14-18.

Figure 12 depicts two different examples in panels a) and b), respectively, of the arrangement that the second communication node 102 may comprise. In some embodiments, the second communication node 102 may comprise the following arrangement depicted in Figure 12a.

The embodiments herein in the second communication node 102 may be implemented through one or more processors, such as a processor 1204 in the second communication node 102 depicted in Figure 12a, together with computer program code for performing the functions and actions of the embodiments herein. A processor, as used herein, may be understood to be a hardware component. 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 second communication node 102. 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 second communication node 102.

The second communication node 102 may further comprise a memory 1205 comprising one or more memory units. The memory 1205 is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the second communication node 102.

In some embodiments, the second communication node 102 may receive information from, e.g., the first communication node 102, the third communication node 103, and the fourth communication node 104, through a receiving port 1206. In some embodiments, the receiving port 1206 may be, for example, connected to one or more antennas in second communication node 102. In other embodiments, the second communication node 102 may receive information from another structure in the wireless communications network 100 through the receiving port 1206. Since the receiving port 1206 may be in communication with the processor 1204, the receiving port 1206 may then send the received information to the processor 1204. The receiving port 1206 may also be configured to receive other information.

The processor 1204 in the second communication node 102 may be further configured to transmit or send information to e.g., the first communication node 101 , the third communication node 103, and the fourth communication node 104, another structure in the wireless communications network 100, through a sending port 1207, which may be in communication with the processor 1204, and the memory 1205.

Those skilled in the art will also appreciate that the receiving unit 1201 , the providing unit 1202, and the other units 1203 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 memory, that, when executed by the one or more processors such as the processor 1204, perform as described above.

One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuit (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).

Also, in some embodiments, the different units 1201 -1203 described above may be implemented as one or more applications running on one or more processors such as the processor 1204.

Thus, the methods according to the embodiments described herein for the second communication node 102 may be respectively implemented by means of a computer program 1208 product, comprising instructions, i.e., software code portions, which, when executed on at least one processor 1204, cause the at least one processor 1204 to carry out the actions described herein, as performed by the second communication node 102. The computer program 1208 product may be stored on a computer-readable storage medium 1209. The computer-readable storage medium 1209, having stored thereon the computer program 1208, may comprise instructions which, when executed on at least one processor 1204, cause the at least one processor 1204 to carry out the actions described herein, as performed by the second communication node 102. In some embodiments, the computer-readable storage medium 1209 may be a non-transitory computer- readable storage medium, such as a CD ROM disc, or a memory stick. In other embodiments, the computer program 1208 product may be stored on a carrier containing the computer program 1208 just described, wherein the carrier is one of an electronic signal, optical signal, radio signal, or the computer-readable storage medium 1209, as described above.

The second communication node 102 may comprise a communication interface configured to facilitate communications between the second communication node 102 and other nodes or devices, e.g., the first communication node 101 , the third communication node 103, and the fourth communication node

104. The interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

In other embodiments, the second communication node 102 may comprise the following arrangement depicted in Figure 12b. The second communication node 102 may comprise a processing circuitry 1204, e.g., one or more processors such as the processor 1204, in the second communication node 102 and the memory 1205. The second communication node 102 may also comprise a radio circuitry 1210, which may comprise e.g., the receiving port 1206 and the sending port 1207. The processing circuitry 1204 may be configured to, or operable to, perform the method actions according to Figure 8, Figure 9, Figure 10, and/or Figures 14-18, in a similar manner as that described in relation to Figure 12a. The radio circuitry 1210 may be configured to set up and maintain at least a wireless connection with the first communication node 101 . Circuitry may be understood herein as a hardware component. Hence, embodiments herein also relate to the second communication node 102. The second communication node 102 may comprise the processing circuitry 1204 and the memory 1205, said memory 1205 containing instructions executable by said processing circuitry 1204, whereby the second communication node 102 is further operative to perform the actions described herein in relation to the second communication node 102, e.g., in Figure 8, Figure 9, Figure 10, and/or Figures 14-18.

Further Extensions And Variations

Figure 13: Telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments With reference to FIGURE 13, in accordance with an embodiment, a communication system includes telecommunication network 1310 such as the wireless communications network 100, for example, a 3GPP-type cellular network, which comprises access network 131 1 , such as a radio access network, and core network 1314. Access network 131 1 comprises a plurality of network nodes such as the radio network node 1 10. For example, base stations 1312a, 1312b, 1312c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1313a, 1313b, 1313c. Each base station 1312a, 1312b, 1312c is connectable to core network 1314 over a wired or wireless connection 1315. In Figure 13, a first UE 1391 located in coverage area 1313c is configured to wirelessly connect to, or be paged by, the corresponding base station 1312c. A second UE 1392 in coverage area 1313a is wirelessly connectable to the corresponding base station 1312a. While a plurality of UEs 1391 , 1392 are 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 station 1312. Any of the UEs 1391 , 1392 may be considered examples of the radio network node 1 10.

Telecommunication network 1310 is itself connected to host computer 1330, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm. Host computer 1330 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 1321 and 1322 between telecommunication network 1310 and host computer 1330 may extend directly from core network 1314 to host computer 1330 or may go via an optional intermediate network 1320. Intermediate network 1320 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 1320, if any, may be a backbone network or the Internet; in particular, intermediate network 1320 may comprise two or more sub-networks (not shown).

The communication system of Figure 13 as a whole enables connectivity between the connected UEs 1391 , 1392 and host computer 1330. The connectivity may be described as an over-the-top (OTT) connection 1350. Host computer 1330 and the connected UEs 1391 , 1392 are configured to communicate data and/or signaling via OTT connection 1350, using access network 131 1 , core network 1314, any intermediate network 1320 and possible further infrastructure (not shown) as intermediaries. OTT connection 1350 may be transparent in the sense that the participating communication devices through which OTT connection 1350 passes are unaware of routing of uplink and downlink communications. For example, base station 1312 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 1330 to be forwarded (e.g., handed over) to a connected UE 1391 . Similarly, base station 1312 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1391 towards the host computer 1330.

In relation to Figures 14, 15, 16, 17, and 18, which are described next, it may be understood that a UE is an example of the wireless device 130, and that any description provided for the UE equally applies to the wireless device 130. It may be also understood that the base station may be considered an example of the radio network node 1 10, and that any description provided for the base station equally applies to the radio network node 1 10.

Figure 14: Host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments

Example implementations, in accordance with an embodiment, of the wireless device 130, e.g., a UE, and the radio network node 1 10, e.g., a base station and host computer discussed in the preceding paragraphs will now be described with reference to Figure 14. In communication system 1400, such as the wireless communications network 100, host computer 1410 comprises hardware 1415 including communication interface 1416 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 1400. Host computer 1410 further comprises processing circuitry 1418, which may have storage and/or processing capabilities. In particular, processing circuitry 1418 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. Host computer 1410 further comprises software 141 1 , which is stored in or accessible by host computer 1410 and executable by processing circuitry 1418. Software 141 1 includes host application 1412. Host application 1412 may be operable to provide a service to a remote user, such as UE 1430 connecting via OTT connection 1450 terminating at UE 1430 and host computer 1410. In providing the service to the remote user, host application 1412 may provide user data which is transmitted using OTT connection 1450.

Communication system 1400 further includes the radio network node 1 10, exemplified in Figure 14 as a base station 1420 provided in a telecommunication system and comprising hardware 1425 enabling it to communicate with host computer 1410 and with UE 1430. Hardware 1425 may include communication interface 1426 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 1400, as well as radio interface 1427 for setting up and maintaining at least wireless connection 1470 with the wireless device 130, exemplified in Figure 14 as a UE 1430 located in a coverage area (not shown in Figure 14) served by base station 1420. Communication interface 1426 may be configured to facilitate connection 1460 to host computer 1410. Connection 1460 may be direct or it may pass through a core network (not shown in Figure 14) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 1425 of base station 1420 further includes processing circuitry 1428, 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. Base station 1420 further has software 1421 stored internally or accessible via an external connection.

Communication system 1400 further includes UE 1430 already referred to. Its hardware 1435 may include radio interface 1437 configured to set up and maintain wireless connection 1470 with a base station serving a coverage area in which UE 1430 is currently located. Hardware 1435 of UE 1430 further includes processing circuitry 1438, 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. UE 1430 further comprises software 1431 , which is stored in or accessible by UE 1430 and executable by processing circuitry 1438. Software 1431 includes client application 1432. Client application 1432 may be operable to provide a service to a human or non-human user via UE 1430, with the support of host computer 1410. In host computer 1410, an executing host application 1412 may communicate with the executing client application 1432 via OTT connection 1450 terminating at UE 1430 and host computer 1410. In providing the service to the user, client application 1432 may receive request data from host application 1412 and provide user data in response to the request data. OTT connection 1450 may transfer both the request data and the user data. Client application 1432 may interact with the user to generate the user data that it provides.

It is noted that host computer 1410, base station 1420 and UE 1430 illustrated in Figure 14 may be similar or identical to host computer 1330, one of base stations 1312a, 1312b, 1312c and one of UEs 1391 , 1392 of Figure 13, respectively. This is to say, the inner workings of these entities may be as shown in Figure 14 and independently, the surrounding network topology may be that of Figure 13.

In Figure 14, OTT connection 1450 has been drawn abstractly to illustrate the communication between host computer 1410 and UE 1430 via base station 1420, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE 1430 or from the service provider operating host computer 1410, or both. While OTT connection 1450 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection 1470 between UE 1430 and base station 1420 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 UE 1430 using OTT connection 1450, in which wireless connection 1470 forms the last segment. More precisely, the teachings of these embodiments may improve the spectrum efficiency, and latency, and thereby provide benefits such as reduced user waiting time, better responsiveness and extended battery lifetime.

A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection 1450 between host computer 1410 and UE 1430, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 1450 may be implemented in software 141 1 and hardware 1415 of host computer 1410 or in software 1431 and hardware 1435 of UE 1430, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 1450 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 141 1 , 1431 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 1450 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 1420, and it may be unknown or imperceptible to base station 1420. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 1410’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 141 1 and 1431 causes messages to be transmitted, in particular empty or‘dummy’ messages, using OTT connection 1450 while it monitors propagation times, errors etc.

Figure 15: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

Figure 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure 15 will be included in this section. In step 1510, the host computer provides user data. In substep 151 1 (which may be optional) of step 1510, the host computer provides the user data by executing a host application. In step 1520, the host computer initiates a transmission carrying the user data to the UE. In step 1530 (which may be optional), 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 step 1540 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

Figure 16: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

Figure 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure 16 will be included in this section. In step 1610 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 1620, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1630 (which may be optional), the UE receives the user data carried in the transmission.

Figure 17: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

Figure 17 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure 17 will be included in this section. In step 1710 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1720, the UE provides user data. In substep 1721 (which may be optional) of step 1720, the UE provides the user data by executing a client application. In substep 171 1 (which may be optional) of step 1710, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 1730 (which may be optional), transmission of the user data to the host computer. In step 1740 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.

Figure 18: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

Figure 18 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure 18 will be included in this section. In step 1810 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 1820 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1830 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

Some example embodiments:

1. A base station configured to communicate with a user equipment (UE), the base station comprising a radio interface and processing circuitry configured to perform any of the methods described in claims 1 -18 appended hereto.

2. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the methods described in claims 1 -18 appended hereto.

3. The communication system of embodiment 2, further including the base station.

4. The communication system of embodiment 3, further including the UE, wherein the UE is configured to communicate with the base station.

5. The communication system of embodiment 4, wherein:

the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.

6. A method implemented in a base station, comprising any of the methods described in claims 1 -18 appended hereto. 7. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and

at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the methods described in claims 1 -18 appended hereto.

8. The method of embodiment 7, further comprising: at the base station, transmitting the user data.

9. The method of embodiment 8, wherein the user data is provided at the host computer by executing a host application, the method further comprising: at the UE, executing a client application associated with the host application.

10. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the methods described in claims 1 -18 appended hereto.

1 1. The communication system of embodiment 10, further including the base station.

12. The communication system of embodiment 1 1 , further including the UE, wherein the UE is configured to communicate with the base station.

13. The communication system of embodiment 12, wherein:

the processing circuitry of the host computer is configured to execute a host application; the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.