WO2022063636A1

WO2022063636A1 - Additional data capacity via use of candidate secondary cells for wireless communication

Info

Publication number: WO2022063636A1
Application number: PCT/EP2021/075199
Authority: WO
Inventors: Anand Bedekar
Original assignee: Nokia Technologies Oy
Priority date: 2020-09-22
Filing date: 2021-09-14
Publication date: 2022-03-31

Abstract

49 ABSTRACT A method may include sending, by a network node to a control entity, at least a data expansion information that indicates an additional downlink data capacity of a user device that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device; and receiving, by the network node, downlink data for the user device, having a data rate or amount of data that is based at least on the data expansion information for the user device. Fig. 8

Description

ADDITIONAL DATA CAPACITY VIA USE OF CANDIDATE SECONDARY CELLS FOR WIRELESS COMMUNICATION

TECHNICAL FIELD

[0001] This description relates to wireless communications.

BACKGROUND

[0002] A communication system may be a facility that enables communication between two or more nodes or devices, such as fixed or mobile communication devices. Signals can be carried on wired or wireless carriers.

[0003] An example of a cellular communication system is an architecture that is being standardized by the 3^rd Generation Partnership Project (3GPP). A recent development in this field is often referred to as the long-term evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio-access technology. E-UTRA (evolved UMTS Terrestrial Radio Access) is the air interface of 3GPP's Long Term Evolution (LTE) upgrade path for mobile networks. In LTE, base stations or access points (APs), which are referred to as enhanced Node AP (eNBs), provide wireless access within a coverage area or cell. In LTE, mobile devices, or mobile stations are referred to as user equipments (UE). LTE has included a number of improvements or developments. Aspects of LTE are also continuing to improve.

[0004] 5G New Radio (NR) development is part of a continued mobile broadband evolution process to meet the requirements of 5G, similar to earlier evolution of 3G & 4G wireless networks. In addition, 5G is also targeted at the new emerging use cases in addition to mobile broadband. A goal of 5G is to provide significant improvement in wireless performance, which may include new levels of data rate, latency, reliability, and security. 5G NR may also scale to efficiently connect the massive Internet of Things (loT) and may offer new types of mission-critical services. For example, ultra-reliable and low-latency communications (URLLC) devices may require high reliability and very low latency.

SUMMARY

[0005] According to an example embodiment, a method may include: sending, by a network node to a control entity, at least a data expansion information that indicates an additional downlink data capacity of a user device that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device; and receiving, by the network node, downlink data for the user device, having a data rate or amount of data that is based at least on the data expansion information for the user device.

[0006] According to an example embodiment, a method may include: sending, by a network node to a data determination entity, data delivery information for a user device within a wireless network, the data delivery information including at least one of a data rate and/or buffer size achieved by the user device based on one or more cells of the network node that are currently activated for the user device, or information associated with one or more additional cells that have not been activated by the network node for the user device and which are supportable by the user device; receiving, by the network node from the data determination entity, at least a data expansion information that indicates an additional downlink data capacity of the user device that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device; sending, by the network node to a control entity, the data expansion information; and receiving, by the network node, downlink data for the user device, having a data rate or amount of data that is based at least on the data expansion information for the user device.

[0007] According to an example embodiment, a method may include: receiving, by a data determination entity from a network node to, data delivery information for a user device within a wireless network, the data delivery information including at least one of a data rate and/or buffer size achieved by the user device based on one or more cells of the network node that are currently activated for the user device, or information associated with one or more additional cells that have not been activated by the network node for the user device and which are supportable by the user device; determining, by the data determination entity based on the data delivery information, at least a data expansion information that indicates an additional downlink data capacity of the user device that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device; and, sending, by the network node, to either the network node or a control entity that controls downlink data forwarding of data for the user device, at least the data expansion information. [0008] According to an example embodiment, a method may include receiving, by a control entity that controls downlink data forwarding of data for a user device via a plurality of nodes including a network node, at least a data expansion information that indicates an additional downlink data capacity of the user device that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device; determining, by the control entity, an updated data rate or amount of data to be transmitted by at least the network node to the user device, based at least on the data expansion information; and sending, by the control entity to the network node, data for the user device based on at least the data expansion information.

[0009] According to an example embodiment, a method may include sending, by a network node to a control entity, at least a data capacity information for the user device; sending, by the network node to the control entity, a data capacity format indication that indicates whether or not the data capacity information includes downlink data capacity of the user device that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device; and receiving, by the network node, downlink data for the user device, having a data rate or amount of data that is based at least on the data capacity information and the data capacity format indication.

[0010] Other example embodiments are provided or described for each of the example methods, including: means for performing any of the example methods; a non-transitory computer-readable storage medium comprising instructions stored thereon that, when executed by at least one processor, are configured to cause a computing system to perform any of the example methods; and an apparatus including at least one processor, and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform any of the example methods.

[0011] The details of one or more examples of embodiments are set forth in the accompanying drawings and the description below. Other features will be apparent from the description and drawings, and from the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] FIG. 1 is a block diagram of a wireless network according to an example embodiment.

[0013] FIG. 2 is a block diagram illustrating a system according to an example embodiment.

[0014] FIG. 3 is a flow chart illustrating operation of a network node according to an example embodiment.

[0015] FIG. 4 is a flow chart illustrating operation of a network node (e.g., gNB, DU, lower network node, or other network node) according to an example embodiment.

[0016] FIG. 5 is a flow chart illustrating operation of a data determination entity (e.g., such as a TDDF 236, or other data determination entity) according to an example embodiment.

[0017] FIG. 6 is a flow chart illustrating operation of a control entity (e.g., an anchor point 234, or other control entity) according to an example embodiment.

[0018] FIG. 7 is a flow chart illustrating operation of a network node according to another example embodiment.

[0019] FIG. 8 is a diagram illustrating operation of a system according to an example embodiment.

[0020] FIG. 9 is a block diagram of a wireless station or node (e.g., AP, BS, RAN node, DU, UE or user device, or other network node) according to an example embodiment.

DETAILED DESCRIPTION

[0021] FIG. 1 is a block diagram of a wireless network 130 according to an example embodiment. In the wireless network 130 of FIG. 1, user devices 131, 132, 133 and 135, which may also be referred to as mobile stations (MSs) or user equipment (UEs), may be connected (and in communication) with a base station (BS) 134, which may also be referred to as an access point (AP), an enhanced Node B (eNB), a gNB or a network node. The terms user device and user equipment (UE) may be used interchangeably. A BS may also include or may be referred to as a RAN (radio access network) node, and may include a portion of a BS or a portion of a RAN node, such as (e.g., such as a centralized unit (CU) and/or a distributed unit (DU) in the case of a split BS or split gNB). At least part of the functionalities of a BS (e.g., access point (AP), base station (BS) or (e)Node B (eNB), gNB, RAN node) may also be carried out by any node, server or host which may be operably coupled to a transceiver, such as a remote radio head. BS (or AP) 134 provides wireless coverage within a cell 136, including to user devices (or UEs) 131, 132, 133 and 135. Although only four user devices (or UEs) are shown as being connected or attached to BS 134, any number of user devices may be provided. BS 134 is also connected to a core network 150 via a SI interface 151. This is merely one simple example of a wireless network, and others may be used.

[0022] A base station (e.g., such as BS 134) is an example of a radio access network (RAN) node within a wireless network. A BS (or a RAN node) may be or may include (or may alternatively be referred to as), e.g., an access point (AP), a gNB, an eNB, or portion thereof (such as a /centralized unit (CU) and/or a distributed unit (DU) in the case of a split BS or split gNB), or other network node.

[0023] According to an illustrative example, a BS node (e.g., BS, eNB, gNB, CU/DU, ... ) or a radio access network (RAN) may be part of a mobile telecommunication system. A RAN (radio access network) may include one or more BSs or RAN nodes that implement a radio access technology, e.g., to allow one or more UEs to have access to a network or core network. Thus, for example, the RAN (RAN nodes, such as BSs or gNBs) may reside between one or more user devices or UEs and a core network. According to an example embodiment, each RAN node (e.g., BS, eNB, gNB, CU/DU, ... ) or BS may provide one or more wireless communication services for one or more UEs or user devices, e.g., to allow the UEs to have wireless access to a network, via the RAN node. Each RAN node or BS may perform or provide wireless communication services, e.g., such as allowing UEs or user devices to establish a wireless connection to the RAN node, and sending data to and/or receiving data from one or more of the UEs. For example, after establishing a connection to a UE, a RAN node or network node (e.g., BS, eNB, gNB, CU/DU, ... ) may forward data to the UE that is received from a network or the core network, and/or forward data received from the UE to the network or core network. RAN nodes or network nodes (e.g., BS, eNB, gNB, CU/DU, ... ) may perform a wide variety of other wireless functions or services, e.g., such as broadcasting control information (e.g., such as system information) to UEs, paging UEs when there is data to be delivered to the UE, assisting in handover of a UE between cells, scheduling of resources for uplink data transmission from the UE(s) and downlink data transmission to UE(s), sending control information to configure one or more UEs, and the like. These are a few examples of one or more functions that a RAN node or BS may perform.

[0024] A user device (user terminal, user equipment (UE), mobile terminal, handheld wireless device, etc.) may refer to a portable computing device that includes wireless mobile communication devices operating either with or without a subscriber identification module (SIM), including, but not limited to, the following types of devices: a mobile station (MS), a mobile phone, a cell phone, a smartphone, a personal digital assistant (PDA), a handset, a device using a wireless modem (alarm or measurement device, etc.), a laptop and/or touch screen computer, a tablet, a phablet, a game console, a notebook, a vehicle, a sensor, and a multimedia device, as examples, or any other wireless device. It should be appreciated that a user device may also be (or may include) a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network.

[0025] In LTE (as an illustrative example), core network 150 may be referred to as Evolved Packet Core (EPC), which may include a mobility management entity (MME) which may handle or assist with mobility/handover of user devices between BSs, one or more gateways that may forward data and control signals between the BSs and packet data networks or the Internet, and other control functions or blocks. Other types of wireless networks, such as 5G (which may be referred to as New Radio (NR)) may also include a core network.

[0026] In addition, by way of illustrative example, the various example embodiments or techniques described herein may be applied to various types of user devices or data service types, or may apply to user devices that may have multiple applications running thereon that may be of different data service types. New Radio (5G) development may support a number of different applications or a number of different data service types, such as for example: machine type communications (MTC), enhanced machine type communication (eMTC), Internet of Things (loT), and/or narrowband loT user devices, enhanced mobile broadband (eMBB), and ultra-reliable and low-latency communications (URLLC). Many of these new 5G (NR) - related applications may require generally higher performance than previous wireless networks.

[0027] loT may refer to an ever-growing group of objects that may have Internet or network connectivity, so that these objects may send information to and receive information from other network devices. For example, many sensor type applications or devices may monitor a physical condition or a status, and may send a report to a server or other network device, e.g., when an event occurs. Machine Type Communications (MTC, or Machine to Machine communications) may, for example, be characterized by fully automatic data generation, exchange, processing and actuation among intelligent machines, with or without intervention of humans. Enhanced mobile broadband (eMBB) may support much higher data rates than currently available in LTE.

[0028] Ultra-reliable and low-latency communications (URLLC) is a new data service type, or new usage scenario, which may be supported for New Radio (5G) systems. This enables emerging new applications and services, such as industrial automations, autonomous driving, vehicular safety, e-health services, and so on. 3 GPP targets in providing connectivity with reliability corresponding to block error rate (BLER) of 10'⁵ and up to 1 ms U-Plane (user/data plane) latency, by way of illustrative example. Thus, for example, URLLC user devices/UEs may require a significantly lower block error rate than other types of user devices/UEs as well as low latency (with or without requirement for simultaneous high reliability). Thus, for example, a URLLC UE (or URLLC application on a UE) may require much shorter latency, as compared to a eMBB UE (or an eMBB application running on a UE).

[0029] The various example embodiments may be applied to a wide variety of wireless technologies or wireless networks, such as LTE, LTE- A, 5G (New Radio (NR)), cmWave, and/or mmWave band networks, loT, MTC, eMTC, eMBB, URLLC, etc., or any other wireless network or wireless technology. These example networks, technologies or data service types are provided only as illustrative examples.

[0030] As noted above, a wireless network may use a classical (or traditional) BS architecture wherein both a central unit (CU, or gNB-CU) functions and distributed unit (DU or gNB-DU) functions of the base station (BS or gNB) are provided within a single network node (e.g., BS or gNB). Alternatively, a wireless network, or one or more network nodes within a wireless network, may use a split BS architecture in which a BS or gNB may be split into a central unit (CU) and one or more distributed units (DUs). Various techniques described herein may be applicable to (or used in) wireless networks or network nodes that use either the classical BS/gNB architecture or a split BS/gNB architecture.

[0031] In dual-connectivity (or more generally referred to as multi-connectivity), a UE may be connected to multiple base stations or network nodes simultaneously, where the network nodes may be of the same or different radio access technologies (RATs). Thus, for multi-connectivity, each of the network nodes may be an eNB, gNB, or other network node. For example, one of the network nodes may be referred to as a master network node (e.g., master gNB (MgNB) or master eNB (MeNB)), while another network node may be referred to as a secondary network node (e.g., a secondary gNB (SgNB) or secondary eNB (SeNB)), e.g, with respect to the classical BS architecture. For dual or multi-connectivity, the UE may, for example, establish a first connection to a master network node, and then establish a second connection to a secondary network node. For each of the network nodes, a UE may be able to communicate and/or receive data via multiple (a plurality of) cells, e.g., using carrier aggregation (CA). The cells of the master network node may be referred to as a master cell group (MCG), while the cells of a secondary network node may be referred to as a secondary cell group (SCG).

[0032] An anchor point may be provided to control the forwarding of downlink data to a UE via the multiple network nodes. The anchor point may receive data or traffic from the core network that is directed to a UE, and then may split or divide the downlink data among the two (or multiple) network nodes, e.g., to increase data rate of the downlink data transmitted to the UE. The anchor point may, for example, be located at one of the network nodes (e.g., master network node or secondary network node), or may be located at another location. In a classical BS architecture, the anchor point may be provided in (or as part of) a master network node, or in (or part of) the secondary network node. In a split BS architecture, an anchor point may be provided within or as part of a CU, or at other location.

[0033] FIG. 2 is a block diagram illustrating a system according to an example embodiment. The system shown in the example of FIG. 2 may use a split architecture, e.g., in which a BS or gNB may be split, e.g., in which some functions of the gNB may be provided at a central (or centralized) unit (CU or gNB-CU), and other gNB functions may be provided at each distributed unit (DU or gNB-DU). There may be one or more DUs provided for each CU. Thus, as shown in FIG. 2, an upper network node (e.g., CU) 230 may be connected to and/or in communication with lower network nodes (e.g., DUs) 212 and 214. CU 230 may include a packet data convergence protocol (PDCP) entity 232, which may perform header compression of packets, and security/encryption functions (e.g., integrity protection and ciphering/encryption). An anchor point 234 may be provided, and may control the forwarding of downlink data to a UE 210 via one or more lower network nodes, such as via the multiple lower network nodes 212, 214 (e.g., via multiple DUs). The anchor point 234 may be provided at the CU 230 or at other location, such as on a server, within a cloud, etc. The anchor point 234 may include the PDCP entity 212, or the anchor point may be implemented as part of the PDCP entity, for example. In some embodiments, the DU and the CU may be combined into a common network node or gNB.

[0034] Each of the lower network nodes (e.g., DUs) 212, 214 in FIG. 2 may include multiple protocol entities, e.g., including a radio link control (RLC) entity, a media access control (MAC) entity, and a physical layer (PHY) entity. A RLC entity may perform link layer retransmissions using automatic repeat request (ARQ) protocol, for example. A MAC entity may perform combining of data from different radio bearers to form a transport block to fit within resources allocated by a PHY entity. The PHY entity may perform a wireless transmission via physical media based on PHY resources (e.g., such as based on time, frequency, and/or beam resources). Each lower network node (or DU) 212 or 214, may typically provide multiple cells, and thus, each lower network node may typically include multiple PHY entities.

[0035] UE 210 may be connected via multi-connectivity, in which the UE 210 is connected to multiple network nodes (e.g., connected to dual or multiple BSs, gNBs, DUs (gNB-DUs), and/or eNBs, etc.) simultaneously, e.g., in order to increase data capacity (e.g., data rate) to the UE. As shown in FIG. 2, UE 210 may be connected to and/or in communication with one or more lower network nodes (e.g., DUs) 212 and 214. In the illustrative example shown in FIG. 2, an upper network node (e.g., CU, gNB-CU) 230 may be connected to and/or control the lower network nodes (e.g., DUs) 212, 214, according to the split gNB architecture. In some embodiments, the CU may be collocated with one of the DUs to which the UE has connected in dual-connectivity or multi-connectivity, e.g., either the CU may be collocated with the DU of the master network node, or with the DU of a secondary network node. In some embodiments, the CU may not be collocated with any of the DUs to which the UE has connected in multiconnectivity or dual-connectivity.

[0036] Anchor point 234 (e.g., a multi-connectivity anchor point, other control entity) may control downlink data forwarding or sending of data to the UE via each of the one or more network nodes (e.g., via each of the one or more lower network nodes (or DUs) 212, 214) to which the UE may connect. The anchor point 234 may, for example, be located or provided at the upper network node (e.g., CU) 230, or other location, such as within the cloud, a server, or other node. As part of the dual (or multi) - connectivity, the UE 210 may first establish a connection with a master network node (which may be a master gNB, master eNB, or master DU), which may provide one or more cells that are part of a master cell group. The anchor point 234 may control the downlink data sending or forwarding of data to the UE via the master DU. The UE may then establish a connection to a secondary network node (e.g., a secondary gNB, secondary eNB or secondary DU), which may provide one or more cells that are part of a secondary cell group, with respect to the UE 210. The anchor point may then control the downlink data sending or forwarding of data to the UE via both the master gNB/DU and the secondary gNB/DU.

[0037] The UE 210 may be connected to each lower network node 212, 214 via one or more carriers or cells, which may be referred to as multi-carrier (or multi-cell) communication, or carrier aggregation. Thus, in some cases, downlink data rate to the UE210 may be increased via one or both of: 1) dual (or multi) connectivity where the UE is connected to multiple network nodes (e.g., multiple lower network nodes (or DUs) 212, 214), and/or 2) multi-carrier communication where the UE 210 may be connected to a network node (e.g., lower network node or DU) via multiple cells, where the UE 210 may receive downlink data via both a primary cell and a secondary cell of the lower network node. While some of the examples described herein are provided with respect to a dual or multi-connectivity configuration in which the UE is connected to multiple network nodes (e.g., multiple lower network nodes or DUs), the embodiments and techniques described herein are applicable to either: a single connectivity configuration (UE connected only to one network node, such as connected to only one lower network node or DU), or to a dual or multi-connectivity configuration in which the UE is connected to multiple network nodes (e.g., connected to multiple lower network nodes or UEs). In either case, a lower network node may send a data expansion information, possibly in addition to basic data capacity information, to the sending of downlink data by the control entity or anchor point, and carrier aggregation may be used where the lower network node may activate one or more Scells in addition to a Pcell. This may occur at each of one or more network nodes (e.g., at or for one or more lower network nodes or DUs) that may be connected to the UE.

[0038] Messages or signaling may be sent between each of lower network nodes (or DUs) 212, 214 and anchor point 234, e.g., to support flow control or adjustment of a data capacity (e.g., data rate) in the downlink direction to the UE 210. For example, lower network nodes 212, 214 may each send feedback messages to the anchor point 234 to allow the anchor point 234 to determine, e.g., for a given user or flow, the amount or the rate of data to send to a given lower network node 212, 214. For example, each lower network node 212214 may send a downlink data delivery status message to anchor point 234 that may indicate a desired buffer size and/or a desired data rate for downlink data transmitted to the UE 210 via the lower network node.

[0039] For carrier aggregation (wherein a UE may be configured to use multiple cells for data transmission to/from the UE), a UE may establish a connection to a network node (e.g., lower network node or DU, or gNB), via a first cell known as the primary cell. The first cell within the master DU to which the UE connects is typically known as the Pcell (or primary cell). In the case of dual- or multi- connectivity, the first cell within the secondary DU to which the UE connects is typically known as the PScell, which serves as a primary cell as far as the UE’s connectivity to the secondary DU is concerned. After connecting to the primary cell (Pcell or PScell), the UE may be further configured with information about additional cells from the master DU or secondary DU, known as secondary cells that can be activated for transmission to/from the UE. For example, based on cell measurement reports received by the lower network node from the UE for various cells, the network node (e.g., lower network node or DU or gNB) may send a message to the UE 210 indicating a set of N possible (or candidate) secondary cells or Scells(e.g., indicating a carrier and/or physical cell identifier (PCI) for each potential secondary cell, along with relevant radio resource configuration information for the Scell(s)) that may be activated by the network node for the UE 210. Thus, based on this message, the UE 210 is now configured with these N possible (or candidate) secondary cells that can be activated by the network node. At some point, e.g., as demands for downlink data rate to the UE 210 have increased, the network node (e.g., lower network node or DU 212 or 214) may send a message or control information (e.g., MAC control element) indicating that one or more cells of the N possible or candidate cells that are being activated. Based on this secondary cell activation for the UE 210 by the network node, the UE 210 may then perform various functions associated with this activated secondary cell, e.g., including monitoring downlink control information (DCI) on a physical downlink control channel (PDCCH) for that activated secondary cell to determine if downlink data has been scheduled to the UE for that secondary cell. The UE may then, based on the indicated data scheduling for the secondary cell, receive data via a downlink shared channel (PDSCH) for the secondary cell. This data may be received by the UE from the network node via the activated secondary cell, in addition to data that may be received by the UE from the network node via the primary cell. In this manner, the UE may receive downlink data via multiple cells, such as via both a primary cell and a secondary cell of a network node (e.g., of a lower network node 212 or 214).

[0040] For example, if a UE 210 is connected to a lower network node (or DU), then at least a primary cell of the lower network node is active for the UE, e.g., meaning that the UE may typically at least monitor downlink control information for that active primary cell to determine if downlink data has been scheduled on that cell, and then may receive downlink data via that active cell, among other functions. If a secondary cell of the lower network node is activated, then, after secondary cell activation, both the primary cell and the (activated) secondary cell are now active (or activated) for the UE, and the UE may receive downlink data via both of these cells of the lower network node, e.g., until such time that the lower network node deactivates the secondary cell (which would mean that the UE at that point would no longer be able to receive data via the secondary cell of the lower network node, since that secondary cell has been deactivated).

[0041] However, some problems or inefficiencies may arise that may inhibit downlink data forwarding performance from anchor point 234 to UE 210 via each of the one or more lower network nodes. As noted, within (or for) each lower network node (or DU) 212, 214, a UE 210 may be able to receive data from the lower network node simultaneously via more than once cell, which may be referred to as carrier aggregation. Data capacity (e.g., data rate) of downlink data transmitted to the UE 210 may be increased by aggregating the downlink resources of the multiple carriers or multiple cells (e.g., primary cell and at least one secondary cell) of a particular lower network node (or DU). However, carrier aggregation may not always be activated for a UE, in order to conserve battery power and reduce control channel overhead for the UE. Carrier aggregation may be activated by the RAN (e.g., gNB, CU, DU), e.g., such as if there is enough downlink data directed to the UE to justify sending this data to the UE over multiple carriers. A variable number of carriers/cells may be active for a given UE at a time, ranging from one cell (the primary cell only in that case) to N carriers/cells (a primary cell, and one or more secondary cells), up to the maximum number of cells that the UE 210 supports (based on the UE capability). Thus, the data capacity (e.g., data rate or throughput) of data transmitted to UE 210 through a particular lower network node (or DU) may depend on the number of active carriers or cells for the UE, which may fluctuate as carriers or cells of the lower network node are activated or deactivated for carrier aggregation for the UE 210.

[0042] At least in some cases, it may be desirable that the anchor point 234 (or other control entity) control the sending of data to a particular lower network node in a manner that may be based upon, e.g., commensurate with the data capacity of the UE at the lower network node. Thus, the anchor point 234 may send a higher amount or rate of data to a lower network node that has a higher data capacity, and may send a lower (or less) amount or rate of data to a lower network node that has a lower data capacity. For example, the anchor point may send data for the UE to the lower network node at a data rate commensurate with the data rate or throughput of data transmittable to the UE via the lower network node. Or, the anchor point may send an amount of data to the lower network node that may be commensurate with, the amount of buffer size or buffer space available for the UE at the lower network node, which in turn may be dependent on the data rate or throughput of data transmittable to the UE via the lower network node. If the anchor point were to send data for the UE to the lower network node at too high a data rate or with too large an amount of data, that may cause the lower network node to drop the excess data (for example due to running out of buffer space), a situation sometimes known as overflow. If the anchor point were to send data for the UE to the lower network node at too low a data rate or with too small an amount of data, that may cause the lower network node to not have enough data to transmit to the UE (a situation sometimes known as underflow), leading to the UE not receiving sufficient data which may lead to a poor user experience. As noted, the anchor point 234 (or other control entity) may receive some limited flow control feedback (e.g., such as a downlink data delivery status message indicating a desired data capacity information of the UE 210, such as indicating a desired buffer size or a desired data rate) from the lower network node (or DU). However, in most cases, anchor point 234 may send only enough data to a particular lower network node (or DU) to meet the indicated desired data rate or desired buffer size for the UE. Typically, the desired data capacity information may be determined by the lower network node or DU based only on the currently activated carriers or cells for the UE within that DU. Thus, the anchor point does not typically account for the possibility of activation of one or more additional carriers or cells at the lower network node for the UE 210, which may allow the UE to attain a higher data capacity than it currently has based on the currently activated carriers or cells. Due to this, an anchor point may typically send only enough data to achieve the desired data rate or data capacity as indicated, based on the lower network node using only the currently activated cell(s) (for example, using only the primary cell (only one cell or carrier) for the UE 210 if no further Scells have been activated), without considering the possibility that additional carriers or cells can be activated by the lower network node (or DU) for the UE 210. The lower network node may trigger the activation of further Scells for the UE only when a sufficiently high amount of data is available for the UE, or when the rate at which the lower network node receives data from the anchor point is sufficiently high, as activating additional carriers when there is insufficient data to transmit to the UE is wasteful in terms of control channel resources as well as battery drain on the UE. Therefore, in many cases, additional carriers or cells are never activated because a sufficient amount of downlink data is not forwarded by the anchor point to trigger the addition (activation) of one or more secondary cells. As a result, in many cases, the higher data capacity (higher data rates or data throughput) that can be achieved for downlink data via use of multiple cells for carrier aggregation will not be achieved since one or more secondary cells may not be activated by the lower network node for the UE 210. This can lead to the UE having a poor user experience, and may also impact the system capacity. On the other hand, if the anchor point were to simply assume that the lower network node may be able to always activate additional carriers and pre-emptively send data to the lower network node at too high a data rate or with too high an amount of data, that may also be inefficient, as it may turn out that the lower network node cannot actually activate additional carriers for the UE e.g., due to reasons of high load on the Scells or poor signal strength or poor coverage, or other reason. This could lead to potential overflow at the lower network node. Thus, the limited feedback that may be provided by a lower network node to the anchor point using the desired data rate or desired data size that is based only on the currently activated cells (Pcell and or Scells) may lead to inefficiencies in data delivery, impacting the network performance as well as the user experience.

[0043] Therefore, according to an example embodiment, a network node (e.g., a lower network node or DU, or other network node) may send a data expansion information (e.g., such as a data expansion factor (DEF)) to a control entity (e.g., anchor point 234) that indicates an additional downlink data capacity (e.g., additional data rate or additional buffer size) of a UE 210 (or user device) that can be achieved via an activation by the network node (e.g., lower network node 212 or 214) of one or more candidate cells of the network node (e.g., cells that can possibly be activated) for the UE 210 that are not currently activated (e.g., not currently being used) for the UE 210. The network node (e.g., lower network node 212 or 214 or DU) may receive downlink data from the control entity (e.g., anchor point 234) or CU, for the UE 210, having a data rate or amount of data that may be based at least on the data expansion information for the UE.

[0044] In this manner, the control entity (e.g., anchor point 234) may be notified of a possible (e.g., potential or available)) increase or expansion in a data capacity (e.g., data rate, data throughput or buffer size) that can be achieved for the UE through activation of one or more cells for the UE. The control entity (e.g., anchor point 234) may then adjust (e.g., increase) the amount of data or data rate that is being forwarded to the network node (e.g., lower network node or DU), based on the data expansion information, e.g., since the control entity or anchor point 234 is now aware (based on the data expansion information received by the control entity or anchor point 234) that additional data capacity for the UE is available at the network node. As necessary, the network node (e.g., lower network node 212 or 214), may then activate one or more additional cells for the UE, e.g., based on the amount or rate of data for the UE that is received by the lower network node. The network node (e.g., lower network node 212 or 214) may then forward the received data to the UE 210 via the activated cells.

[0045] For example, the data expansion information (e.g., a data expansion factor or DEF) sent by the network node (e.g., lower network node or DU, 212 or 214) to the control entity (e.g., anchor point 234) may include an additional downlink data rate or an additional buffer size for the UE that may be achieved by activation of one or more (e.g., candidate) cells that are not currently being used by the network node to forward data to the UE, but may be used. For example, at least in some cases, the data expansion information may be sent by the network node (e.g., lower network node or DU 212 or 214) to the control entity (e.g., anchor point 234), in addition to the network node sending to the control entity a basic data capacity information that indicates a current downlink data capacity of the UE based on one or more cells of the network node that are currently activated for the UE. Thus, for example, the basic data capacity information may indicate a basic or current data (e.g., rate or amount of data) capacity of the UE based on currently activated cells of the network node (e.g., lower network node or DU) for the UE. Therefore, in some cases, the network node (e.g., lower network node or DU, 212 or 214) may send both the basic data capacity information and the data expansion information for the UE 210 to the control entity (e.g., anchor point 234), e.g., to indicate both a basic or current data capacity of the UE and an additional data capacity of the UE that can be achieved via activation of one or more additional cells for the UE.

[0046] For example, both the basic data capacity information and the data expansion information, together, may indicate to the control entity (or anchor point 234) a total data capacity of the UE 210 for the network node (e.g., with respect to the lower network node or DU 212 or 214). Thus, in some cases, the control entity (e.g., anchor point 234) may determine a total data capacity of the UE at the network node (based on both the basic data capacity information and the data expansion information for the UE), and then send a data rate or amount of data for the UE 210 to the network node (e.g., a lower network node 212 or 214) that is based on both the basic data capacity information and the data expansion information for the UE. In one example embodiment, sending the data expansion information, possibly together with the basic data capacity information, may thereby cause the control entity (e.g., anchor point 234) to send data to the network node (e.g., lower network node 212 or 214) at a data rate or with an amount of data that may be better able to fully utilize the additional data capacity available (as indicated by the data expansion information), for example if there is a sufficiently high amount of downlink data (traffic) for the UE or if the traffic type of the UE is such that data needs to be delivered as quickly as possible. Receiving data at such a data rate or with such an amount of data from the control entity (e.g., anchor point 234) by the network node (e.g., lower network node 212 or 214) may thereby cause the network node to appropriately activate one or more additional candidate secondary cells for the UE which are not yet activated. This will enable the data to be delivered more rapidly to the UE by utilizing the additional data capacity provided by the secondary cells, while minimizing the likelihood of underflow and overflow. In another example embodiment, sending the data expansion information, possibly together with the basic data capacity information, may thereby cause the control entity (e.g., anchor point 234) to send data to a given lower network node at a rate that is close to the basic data capacity without significantly utilizing the additional data capacity available, for example if there is an insufficient amount of downlink data for the UE, or if the UE has other multi-connectivity lower network nodes that are providing better performance (e.g., which may cause the control entity or anchor point to send more, or a higher portion, of the downlink data for the UE via the higher performing lower network node(s)). Receiving data at such a data rate or with such an amount of data from the control entity (e.g., anchor point 234) by the network node (e.g., lower network node 212 or 214) may thereby cause the lower network node to avoid unnecessarily activating additional secondary cells, thereby avoiding undesirable impacts such as wastage of control channel resources and battery drain at the UE as well as overflow or underflow.

[0047] In another example embodiment, sending the data expansion information, possibly together with the basic data capacity information, may thereby cause the control entity (e.g., anchor point 234) to send data to a given lower network node only at a data rate or with an amount of data that partially utilizes the additional data capacity available (as indicated by the data expansion information), depending on the situation. By sending the data expansion information, possibly along with the basic data capacity information, thereby causing control entity or anchor point to control sending of downlink data to the user device via the network node (e.g., DU or lower network node) at a data rate or amount of data that is based on the data expansion information for the user device, it may be possible to improve overall network and UE performance, e.g., such as to ensure that the lower network node will have an adequate amount of data to quickly trigger activation of additional Scells for the UE to make use of the additional data capacity (indicated by the data expansion information) when the downlink data traffic for the UE warrants it, while reducing the likelihood that the lower network node experiences overflow or underflow. This may improve the user experience without degrading the network’s overall performance. As described herein, the sending or transmitting of a data expansion information (e.g., DEF) to a control entity (e.g., an anchor point) may provide a technical effect of improving network and UE performance, e.g., based on improved resource usage, improving the likelihood of appropriate secondary cell activation at a lower network node (e.g., DU), and decreasing a possibility of a data overflow or underflow.

[0048] According to an example embodiment, with reference to FIG. 2, a data determination entity, e.g., such as a total data determination function (TDDF) 236, may be provided at (or as part of) a network node, such as a DU, on or as part of a radio intelligent controller (RIC), within the cloud, or provided at other location or node. For example, there may be a (e.g., one) TDDF 236, or a TDDF instance, provided for each network node (e.g., for each lower network node or DU, 212 or 214). Or, alternatively, a TDDF 236 may be provided and perform data determination for multiple network nodes. Thus, for example, the TDDF 236 may receive data delivery information for the network node for the UE that may indicate a (current) data capacity (e.g., data rate and/or buffer size of the UE) that has been achieved based on one or more cells that are currently activated or in use by the network node for the UE, and/or information associated with one or more additional (e.g., candidate) cells that have not been activated by the network node for the UE and which are supportable by the UE. For example, the TDDF 236 may determine, e.g., based on the data delivery information for the network node (e.g., for a lower network node or DU 212 or 214) for the UE, at least the data expansion information for the network node. The TDDF 236 may send to the control entity (e.g., that controls and/or performs data forwarding of downlink data to the UE via the network node, such as the anchor point 234) at least the data expansion information. Or, the TDDF 236 may determine, e.g., based on the data delivery information for the UE 210 or based on other information, both the basic data capacity information and the data expansion information for the UE 210 for the network node. The TDDF 236 may, for example, send at least one of, or both of, the basic data capacity information and/or data expansion information for the network node and UE to the control entity (e.g., the control entity that controls and/or performs data forwarding of downlink data to the UE 210 via the network node, such as the anchor point 234), so that the control entity (e.g., anchor point 234) may then adjust and/or send (transmit) a data rate or amount of data (or data capacity) to the UE 210 via the network node (or send the data rate or amount of data to the network node) based on at least the data expansion information (or based on both the basic data capacity information and the data expansion information) for the UE.

[0049] FIG. 3 is a flow chart illustrating operation of a network node according to an example embodiment. In the example of FIG. 3, the TDDF 236 (or data determination entity) may be provided on or as part of the network node (e.g., within or part of a lower network node or DU, 212 or 214, for example). Thus, in this example shown in FIG. 3, the network node may send the data expansion information to the control entity (e.g., anchor point 234). The network node may determine the data expansion information, or may receive it from another entity. For example, the network node may include a gNB, a lower network node, a DU, or other network node. Operation 310 includes sending, by a network node (e.g., a gNB, a lower network node, or DU 212 or 214, FIG. 2, or other network node) to a control entity (e.g., to an anchor point 234, FIG. 2), at least a data expansion information (e.g., a data expansion factor (DEF)) that indicates an additional downlink data capacity of a user device (e.g., of UE 210, FIG. 2) that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device. Operation 320 includes receiving, by the network node, downlink data for the user device, having a data rate or amount of data that is based at least on the data expansion information for the user device.

[0050] With respect to the method of FIG. 3, the sending may include sending, by the network node to the control entity, at least the data expansion information that indicates the additional downlink data capacity, thereby causing the control entity to control forwarding of downlink data to the user device via the network node at a data rate or amount of data that is based on the data expansion information for the user device. Thus, for example, the sending of at least the data expansion information to the control entity (e.g., to the anchor point 234) may cause the control entity to control forwarding of downlink data (that is directed to the UE 210) to the network node at a data rate or amount of data that is base at least on the data expansion information for the UE 210.

[0051] With respect to the method of FIG. 3, the data expansion information may include at least one of the following: a data expansion information that indicates an additional downlink data rate of the user device; or, a data expansion information that indicates an additional buffer size of the user device.

[0052] With respect to the method of FIG. 3, the method may further include sending, by the network node to the control entity, in addition to the data expansion information, a basic data capacity information that indicates a current downlink data capacity of the user device based on one or more cells of the network node that are currently activated for the user device.

[0053] With respect to the method of FIG. 3, the receiving may include: receiving, by the network node (e.g., from a CU and/or from the control entity or anchor point), downlink data for the user device (for UE 210), having a data rate or amount of data that is based at least on both of the basic data capacity information and the data expansion information for the user device. Thus, in this case, a data rate or amount of data (for UE 210) that is transmitted to the network node is based on both the basic data capacity information and the data expansion information for the user device or UE. For example, the basic data capacity information may include a downlink data delivery status message including at least one of a desired buffer size and a desired data rate. In this case, the existing desired buffer size and desired data rate would be defined to indicate (or would mean) a desired data capacity (buffer size or data rate) based on only a currently activated set of cells for the UE (e.g., not taking into account any candidate cells that could be further activated for the UE.

[0054] With respect to the method of FIG. 3, the data expansion information may indicate at least one of: an additive factor that indicates an additional downlink data capacity of a user device, in addition to the current downlink data capacity of the user device, that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device; or a multiplicative factor that indicates an additional percentage or amount of the current downlink data capacity of the user device, that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device.

[0055] With respect to the method of FIG. 3, the method may further include determining, by the network node, data delivery information for the user device, including: a data rate and/or buffer size achieved by the user device based on the one or more cells of the network node that are currently activated for the user device; and information associated with one or more additional cells that have not been activated by the network node for the user device and which are supportable by the user device; the method further including: determining the data expansion information that indicates the additional downlink data capacity of a user device based on at least a portion of the data delivery information.

[0056] FIG. 4 is a flow chart illustrating operation of a network node (e.g., gNB, DU, lower network node, or other network node) according to an example embodiment. In the example illustrated in FIG. 4, the network node and the data determination entity (e.g., TDDF) may be provided at (or as part of) separate entities, locations or nodes, for example.

With respect to FIG. 4, operation 410 may include sending, by a network node to a data determination entity (e.g., TDDF 236, FIG. 2) data delivery information for a user device (e.g., for UE 210, FIG. 2) within a wireless network, the data delivery information including at least one of a data rate and/or buffer size achieved by the user device based on one or more cells of the network node that are currently activated for the user device, or information associated with one or more additional cells that have not been activated by the network node for the user device and which are supportable by the user device. Operation 420 may include receiving, by the network node from the data determination entity, at least a data expansion information (e.g., such as a data expansion factor (DEF)) that indicates an additional downlink data capacity of the user device that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device. Operation 430 may include forwarding, by the network node to a control entity

(e.g., to anchor point 234, FIG. 2) the data expansion information. Operation 440 may include receiving, by the network node (e.g., as shown in FIG. 2, lower network node 212 or 214 may receive data from another network node, from a CU or upper network node 230, or from anchor point 234 or other entity), downlink data for the user device, having a data rate or amount of data that is based at least on the data expansion information for the user device.

[0057] With respect to FIG. 4, the method may further include sending, by the network node (e.g., a lower network node or DU, 212 or 214) to the data determination entity (e.g., to TDDF 236), in addition to the data expansion information, a basic data capacity information that indicates a current downlink data capacity of the user device based on one or more cells of the network node that are currently activated for the user device.

[0058] With respect to FIG. 4, the receiving may include receiving, by the network node, downlink data for the user device, having a data rate or amount of data that is based at least on both of the basic data capacity information and the data expansion information for the user device.

[0059] FIG. 5 is a flow chart illustrating operation of a data determination entity (e.g., such as a TDDF 236, or other data determination entity) according to an example embodiment. In this example, the network node (e.g., lower network node or DU, or other network node) may be provided separately (e.g., at a separate node or entity) from the data determination entity, for example. Operation 510 includes receiving, by a data determination entity from a network node to, data delivery information for a user device within a wireless network, the data delivery information including at least one of a data rate and/or buffer size achieved by the user device based on one or more cells of the network node that are currently activated for the user device, or information associated with one or more additional cells that have not been activated by the network node for the user device and which are supportable by the user device. Operation 520 includes determining, by the data determination entity based on the data delivery information, at least a data expansion information that indicates an additional downlink data capacity of the user device that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device. And, operation 530 includes sending, by the network node, to either the network node or a control entity that controls downlink data forwarding of data for the user device, at least the data expansion information.

[0060] FIG. 6 is a flow chart illustrating operation of a control entity (e.g., an anchor point 234, or other control entity) according to an example embodiment. Operation 610 includes receiving, by a control entity that controls downlink data forwarding of data for a user device via a plurality of nodes including a network node, at least a data expansion information that indicates an additional downlink data capacity of the user device that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device. Operation 620 includes determining, by the control entity, an updated data rate or amount of data to be transmitted by at least the network node to the user device, based at least on the data expansion information. And, operation 630 includes sending, by the control entity to the network node, data for the user device based on at least the data expansion information.

[0061] With respect to the method of FIG. 6, the method may further include receiving, by the control entity from at least one of the network node or a data determination entity, in addition to the data expansion information, a basic data capacity information that indicates a current downlink data capacity of the user device based on one or more cells of the network node that are currently activated for the user device. Thus, in this example, a control entity (e.g., an anchor point 234) may receive basic data capacity information from at least one of or from either the network node (e.g., lower network node or DU 212 or 214) or data determination entity (e.g., TDDF 236) one or both of the basic data capacity information and the data expansion information. Also, for example, the determining may include determining, by the control entity, an updated data rate or amount of data to be transmitted by at least the network node to the user device, based at least on the basic data capacity information and the data expansion information. Also, for example, the sending may include sending, by the control entity to the network node, data for the user device based on at least the data expansion information and the basic data capacity information.

[0062] FIG. 7 is a flow chart illustrating operation of a network node according to another example embodiment. In the example of FIG. 7, the network node may send to a control entity both a data capacity information and a data capacity format indication (e.g., a flag, a bit or other control information) that may indicate whether or not the data capacity information includes (takes into account) the (e.g., the additional or expandable) downlink data capacity of the UE that can be achieved via activation other one or more candidate cells the data expansion capabilities of the UE. Thus, with respect to FIG. 7, operation 710 includes sending, by a network node to a control entity, at least a data capacity information for the user device. Operation 720 includes sending, by the network node to the control entity, a data capacity format indication that indicates whether or not the data capacity information includes downlink data capacity of the user device that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device. And, operation 730 may include receiving, by the network node, downlink data for the user device, having a data rate or amount of data that is based at least on the data capacity information and the data capacity format indication. For example, the data capacity format indication may be either a first value to indicate that the data capacity information indicates a downlink data capacity of the user device based on only one or more cells of the network node that are currently activated for the user device, or a second value to indicate that the data capacity information indicates an expanded data capacity of the user device that is based on both one or more cells of the network node that are currently activated for the user device and one or more candidate cells for the user device that are not currently activated for the user device. As an illustrative example, the data capacity information may be or may include the information provided in the downlink data delivery status message (e.g., indicating desired buffer size or desired data rate). And, the data capacity format may indicate either 1) a first value to indicate that the data capacity information indicates only a current data capacity of the UE that does not consider additional data capacity of the UE via one or more candidate cells that are not activated; or, 2) a second value to indicate that the data capacity information reflects total UE data capacity (including current data capacity, and additional data capacity via candidate cells that can be activated for the UE). Thus, for example, with respect to FIG. 7, the data capacity format indication indicates whether 1) the data capacity information indicates only current data capacity of the UE (not taking into account additional or expandable data capacity of the UE), or 2) a data capacity of the UE that takes into account additional or expandable data capacity of the UE via possible activation of one or more candidate cells (which may reflect the total data capacity of the UE, including current and additional data capacity).

[0063] Further examples are described below with reference to the features and/or operation shown in FIGs. 1-7.

[0064] As noted, a TDDF 236 may be provided, and may be, for example, a functional entity that may be instantiated as part of a lower network node (e.g., part of a base station that performs lower network node functions such as RLC/MAC/PHY) or instantiated as part of a Radio Intelligent Controller, or other network entity.

[0065] According to an example embodiment, a method or technique may be provided and may include one or more of the following:

[0066] • A) TDDF 236 (FIG. 2) may receive or obtain data delivery information about the

UE from the lower network node (e.g., from a lower network node 212 or 214, FIG. 2) based on the currently achieved throughput and buffer levels of the UE, based on already (or currently) activated (primary (P), and possibly secondary (S)) cells, and the supportable (but not yet activated) secondary cells (Scells). At least a primary cell (Pcell) of a lower network node will be activated for a UE when the UE is connected to the lower network node (e.g., DU or gNB). For example, the data delivery information may include information related to UE usage of data buffers (e.g., percent full), the amount of remaining buffer space of the UE, the (e.g., mean and/or standard deviation of) a data rate (throughput) achieved on the currently activated primary and secondary cells for the UE, the load on the other candidate Scells (secondary cells), and/or the capability of the UE in terms of number of supportable Scells. In the case where TDDF 236 is at RIC 240, this data delivery information may be sent by the lower network node 212 or 214 (e.g., DU) to the RIC 240.

[0067] • B) The TDDF 236 may determine data expansion information, such as, for example, a Data Expansion Factor (DEF), that may indicate an additional downlink capacity of the UE, e.g., that can be achieved via activation of one or more candidate cells of the network node that are not currently activated for the UE. For example, the DEF may indicate an additive or multiplicative factor with respect to the basic or current data capacity of the UE, which may have been indicated by the lower network node via a basic data capacity information. Thus, for example, the DEF may indicate an additional or increased amount or rate of data based on candidate cells that can be activated, on top of (or in addition to) the amount or rate of data that is being provided by the anchor point 234 to the lower network node based on the basic or current UE data capacity (e.g., which may be indicated by the network node to the anchor point 234 by sending the basic data capacity information to the anchor point 234). For example, the DEF may be a multiplicative factor, e.g., such as 1.2 or a 120% of the amount or rate of data that is being sent based on the basic or current data capacity of the UE, or an additive factor 0.2, or 20 %) with respect to the basic or current data capacity, representing an additional (or increased) rate or amount of data that is being indicated, on top of (or in addition to) the amount or rate of data that is being sent by the anchor point 234 based on the UE’s basic or current data capacity (e.g., where basic or current data capacity of the UE is based on currently activated cell(s) of the lower network node for the UE). Thus, in an example embodiment, the DEF may be indicated as a numerical value with reference to a current amount or rate of data that is being provided to the lower network node for the UE, e.g., with respect to a basic or current data capacity of the UE that may have been indicated to the anchor point 234 (e.g., based on the lower network node signaling the basic data capacity information to anchor point 234). In the case where TDDF 236 is at RIC 240, this DEF may be sent by the TDDF 236 to the lower network node (e.g., DU) 212 or 214. Thus, a technical effect of improving network performance and UE performance may be provided by sending, by the network node (e.g., lower network node or DU) to the control entity (e.g., anchor point), at least the data expansion information that indicates the additional downlink data capacity, thereby causing the control entity to control sending of downlink data to the user device (e.g., UE) via the network node at a data rate or amount of data that is based on the data expansion information for the user device. A further technical effect may be provided by sending the data expansion information as an additive factor that indicates the additional downlink data an additive factor that indicates an additional downlink data capacity of a user device, in addition to the current downlink data capacity of the user device, that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device. Or, a further technical effect may be provided by sending the data expansion information as a multiplicative factor that indicates an additional percentage or amount of the current downlink data capacity of the user device, that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device. [0068] • C) A DEF may be sent to the anchor point 234 for the UE from each of its lower network nodes 212 and 214. For example, typically, the lower node 212 or 214 may send feedback information such as “Downlink Data Delivery Status” message in 3 GPP 38.425, and its constituent elements such as “desired buffer size”, “desired data rate”, and “highest delivered PDCP SN” etc. Thus, in this case or example, the basic data capacity information may be indicated or sent by lower network node to anchor point 234 by transmitting the existing downlink data delivery status message, e.g., with a desired buffer size or desired data rate, which, according to an example embodiment, may be used to indicate a basic or current data capacity of the UE based on currently activated cells, for example (and not taking into account one or more candidate cells that may be activated for the UE). In addition to this current or basic data capacity of the UE (e.g., which may be indicated by the lower network node sending a basic data capacity information to the anchor point 234), the lower network node 212 or 214 may also send a data expansion information (such as the DEF), e.g., to indicate additional data capacity of the UE. According to an example embodiment, the basic (or current) data capacity indicated by the basic data capacity information may be interpreted to be a data capacity (e.g., amount or rate of data) that is supportable for the UE using the already (or currently) activated (P or S) cells at the lower network node. The DEF may represent or may indicate a factor by which the current data capacity of the UE can be increased or expanded (e.g., indicated or associated with a basic data capacity information), e.g., based on one or more additional Scells of the lower network node (that are not currently activated for the UE) that may be activated for the UE.

[0069] • D) The anchor point 234 may consider or take into account the DEF (data expansion factor) along with the basic data capacity information to determine an updated total amount (or rate) of data to send to each lower network node. In this manner, the anchor point may receive: 1) a basic data capacity information (e.g., which may be indicated via a downlink data delivery status message indicating a desired data rate or desired buffer size, based on currently activated cells for the UE) indicating a basic or current data capacity of the UE based on currently activated cell(s), and 2) a data expansion information (e.g., such as a DEF) that may indicate additional data capacity for the UE (e.g., downlink data rate or additional downlink buffer size) that is available for the UE at the lower network node (beyond the current data capacity for the UE) based on activation of one or more available or candidate cells of the lower network node that are not currently activated for the UE, but which can be activated. [0070] • E ) The anchor point 234 may send data to the lower network node 212 or 214

(e.g., DU) based on the updated total amount/rate of data, which may take into account both the basic data capacity information and the DEF. Based on the (amount or rate of) received data, the lower network node may activate additional Scells based on the data received. Thus, for example, the lower network node sending a data expansion information (DEF) to the anchor point may inform the anchor point 234 that there is potential for a higher data capacity (e.g., higher data rate or throughput) for the UE at the lower network node than indicated in the basic data capacity information, so the anchor point 234 may send additional amount or rate data for the UE to the lower network node (since additional data capacity is available for the UE).

[0071] Some example advantages and/or benefits may include one or more of the following, by way of example:

[0072] • Provides the anchor point 234 with information indicating an additional data capacity of the UE at a network node (e.g., data expansion information, such as DEF).

[0073] • Provides the anchor point 234 more complete information describing the total UE data capacity for the lower network node, e.g., indicating both the basic or current data capacity (e.g., indicated by a basic data capacity information) for the UE based on currently activated cells for the UE, and an expanded data capacity (e.g., indicated by data expansion information, such as DEF) for the UE that may be achieved by the lower network node activating one or more candidate or additional cells that are not currently activated for the UE. This provides the anchor point 234 with more accurate or more complete data capacity information for the UE. This may allow a more effective use of carrier aggregation, as needed.

[0074] • Enables quicker activation of Scells with dual/multi-connectivity flow control.

[0075] • Enables rapidly achieving full (or at least higher) data capacity for the UE

(e.g., higher data rate or throughput).

[0076] • In lightly loaded systems - enables reaching high peak throughput quickly.

[0077] • In medium loaded systems - better user experience by quicker draining of buffers, via rapid activation of Scells (e.g., by the anchor point 234 receiving additional information related to additional data capacity, and then, as needed, taking advantage of the additional data capacity or additional cells that can be activated for the UE, as indicated by the data expansion information). [0078] • In highly loaded systems, enables efficient load balancing by quick activation of Scells.

[0079] Further example details of Aspect A). TDDF 236 receives data delivery information for the UE 210. For example, the TDDF 236 may obtain or receive data delivery information about the UE 210 from the lower network node based on the currently achieved throughput and/or buffer levels of the UE, based on currently activated (P (primary) or S (secondary)) cells, and/or the supportable (but not yet activated) Scells of the lower network node. For example, this data delivery information may include different kinds of information, such as for example: If the lower network node has already determined a basic data capacity information (e.g., which may include or indicate a desired data rate and/or desired buffer size) for the UE based on currently activated cells for the UE at the lower network node, the lower network node (e.g., DU) may send this basic data capacity information to the TDDF 236; an amount of buffered data at the lower network node, the amount of remaining buffer space (typically at RLC layer); the data capacity, e.g., data rate, and/or mean and/or standard deviation of such data rate or throughput, that has been achieved on the currently activated P/S Cells for the UE; an amount of data successfully delivered by the lower network node (at PHY or MAC or RLC or PDCP layer) and the time taken to deliver the data; a number and bandwidth of P/Scells already activated for the UE at the lower network node; a number or fraction of available/unused resources on currently activated P/Scells, e.g., such as a fraction of available physical resource block (PRBs), which may indicate whether the existing carriers are fully used, or there is still more resources available on currently activated P/Scells; a number and/or bandwidth of Scells available at the lower network node (e.g., but not activated for the UE), and a number of Scells the UE may have or is able to add (UE capability for a number of supportable Scells); the load on one or more candidate Scells for the UE; if available, estimated spectral efficiency of UE on one or more candidate Scells; if spectral efficiency of one or more candidate Scells is not directly available (e.g., channel quality indication (CQI) reports for the Scell is not available, and cannot be predicted based on reference signal received power (RSRP) or reference signal received quality (RSRQ) measured by UE or other radio frequency/wireless indication or fingerprint), then average spectral efficiency of all current UEs/users on the Scell can be used; and/or a throughput or data rate achievable by UE on one or more candidate Scells. In case where TDDF 236 is at (provided on, or at or within) the RIC 240, this information can be sent by the lower network node (e.g., a DU).

[0080] Further details of Aspect B) TDDF 236 determines Data Expansion Factor (DEF). The TDDF 236 may determine the data expansion information, such as a Data Expansion Factor (DEF), representing an additive or multiplicative factor for the desired rate (or amount) of data that the anchor point can or should send to the lower network node for the UE. For example, the DEF may be a multiplicative factor or an additive factor, e.g., which may be indicated with respect to the basic data capacity of the UE, or with respect to the amount or rate of data being transmitted based on the basic or current data capacity of the UE. An example algorithm or technique to determine the DEF may include, for example:

[0081] 1) If not already done, the lower network node may determine the basic data capacity information for the UE based on the currently activated P/Scells for the UE. Any algorithm can be used for this, but an example algorithm for this may be: Set Desired data rate = Average Throughput achieved by the UE on already activated P/Scells; and Set Desired buffer size = Min ( (Average Throughput achieved by the UE on already activated P/Scells) * (interval between feedback messages to the anchor), Remaining buffer space at the lower layer leg).

[0082] 2) Then determine the DEF: First determine the additional throughput potentially achievable by the UE via additional Scells: Select a candidate set of Scells, consisting of 1 to N Scells where N = Min ( Max remaining Scells at lower layer, Max UE capability for Scells - Number of already activated Scells). For each of the Scells, estimate achievable throughput of the UE on that Scell = BW of Scell * Estimated spectral efficiency of UE on Scell / Load on the Scell. In the above, typically load = a weighted average number of active users on the Scell. Estimate achievable throughput on additional candidate Scells = sum(estimated throughputs achievable on all selected candidate Scells). For the case where DEF is a multiplicative factor: Set DEF candidate = 1 + (Estimate achievable throughput on additional candidate Scells) / Average Throughput achieved by the UE on already activated P/Scells.

[0083] To make this algorithm more robust, the following may be used, for example: Maintain a filtered value of the DEF: DEF filtered(new) = DEF filtered(old) * (1 -alpha) + DEF candi date * alpha. (Initialize DEF filtered(old) = 1). Alpha between 0 and 1. If the Set of already activated Scells has not changed since the last report, use DEF filtered for Aspect C. If set of already activated Scells has changed since the last report (e.g., a new Scell activated, or old Scell swapped with new Scell), reinitialize DEF filtered(old) = 1. Alpha controls the rate (or aggressiveness) with which the algorithm will try to make use of the additional available bandwidth. Alpha can be set closer to 1 if there is high confidence in the availability of additional Scells and the achievable throughput on those, and lower value for a more gradual probing of the available additional Scells.

[0084] Further details of Aspect C) DEF is sent to the anchor. The data expansion information (e.g., such as DEF) may be sent to the anchor point 234 for the UE from each of its lower network nodes (e.g., such as in the case of multi-connectivity, the UE is connected to multiple lower network nodes, for example). In an example embodiment, each lower network node may determine and send a basic data capacity information for the UE to the anchor point 234. This basic data capacity information may be sent, e.g., by the lower network node sending a “Downlink Data Delivery Status” message (e.g., see 3GPP 38.425), and its constituent elements such as “desired buffer size”, “desired data rate”, and “highest delivered PDCP SN” etc. The basic data capacity information may indicate the basic or current data capacity of the UE (e.g., only taking into account currently activated cells). Thus, the basic data capacity information may indicate a current downlink data capacity of the UE for the lower network node based on one or more cells of the network node that are currently activated for the UE. In addition to the basic data capacity information for the UE, the lower network node may send the data expansion information (e.g., DEF) to the anchor point 234. Thus, by the lower network node sending to the anchor point 234 both the basic data capacity information that indicates a current downlink data capacity of the UE, and a data expansion information (e.g., DEF) that indicates additional data capacity that may be achieved for the UE, the anchor point 234 is provided more complete data capacity information for the UE, e.g., which may allow the anchor point 234 to more effectively use the available cells or resources to transmit downlink data to the UE. In an illustrative example, the basic data capacity information may indicate a data capacity (e.g., data rate, amount of data, throughput) that has been achieved for the UE (or the basic data capacity information may be based on performance measurements for the UE), whereas the data expansion information (e.g., DEF) may indicate an estimated or expected additional data capacity that can likely be achieved by the lower network node activating one or more additional cells for the UE. Thus, by providing the data expansion information (e.g., DEF) to the anchor point 234, this informs the anchor point 234 that there is (or is likely) additional data capacity that can be used to transmit data via this lower network node to the UE via activation one or more additional cells.

[0085] Further details: Aspect D) Determination of amount (or rate) of data to send to each lower network node by the anchor point for the UE. The anchor point may determine a total amount or rate of data to be sent to the UE, e.g., based on both the basic data capacity information and the data expansion information (e.g., DEF). For example, the anchor point 234 may consider or take into account the data expansion information (e.g., DEF) along with the basic data capacity information to determine the amount (or rate) of data to send to each lower network node for the UE. For example, a larger amount of data, or a higher data rate, may be sent via a lower network node that has a higher total data capacity for the UE, as compared to a lower network node that has a lower total data capacity for the UE. Based on the incoming amount (or rate) of data received by the anchor point (e.g., from the core network) for the UE, the anchor point 234 may determine how to apportion or split the incoming data or traffic among the multiple lower network nodes, e.g., based on the total data capacity of each lower network node for the UE. Thus, in an example embodiment, the anchor point 234 may consider both the basic data capacity information and data expansion information for each lower network node, e.g., to determine a total data capacity for the UE at each lower network node, and then may, for example, apportion the amount or rate of data among the multiple lower network nodes in accordance with (e.g., proportional to) the total data capacity of each lower network node.

[0086] The following is an example technique or algorithm that the anchor point may use to determine the amount or rate of data to be sent to each of the lower network nodes for the UE. For each lower network node j : estimate a “likely rate” (R_L(j)) and an “additional potentially supportable rate” (R_A(j) ) based on the basic data capacity information and the DEF: e.g., R_A(j) = R_L(j) * DEF, in the case where DEF is a multiplicative factor like 1.2x, or R_A(j) = R_L(j) + DEF, in the case where the DEF is an additive factor. For each lower network node, estimate an amount of buffered (or not yet delivered) data, B(j) from the basic data capacity information received by the anchor point 234. For example, B(j) = (highest PDCP sequence number (SN) sent by anchor point) - (highest PDCP SN delivered to UE). Estimate the delay based on the “likely rate” or basic data capacity of UE, as D_L(j) = B(j) / R_L(j), and a delay based on “additional potentially supportable rate” D_A(j) = B(j) / R_A(j). Generally D_A(j) < D_L(j). Let Dmax = maximum delay tolerable on any lower network node (e.g., this can be a configurable parameter). For each incoming packet, if any lower network node has D_L(j) < Dmax, send the packet to the lower network node j with minimum D_L(j). If there is no such lower network node, check if any lower network node has D_A(j) < Dmax, and send the packet to the lower network node j with minimum D_A(j). If no lower network node has D_A(j) < Dmax, the packet is buffered until further feedback updates are received from the lower network nodes, which may reflect higher data capacity, and then calculation is repeated.

[0087] FIG. 8 is a diagram illustrating operation of a system according to an example embodiment. As shown in FIG. 8, a UE 210, a lower network node (e.g., DU) 212, an anchor point 234, a TDDF 236, and a core network 810 are shown, and may be in communication. At 812, downlink data may be forwarded or sent from core network 810 to UE 210 via PDCP or anchor point 234 and lower network node 212. At 814, lower network node 212 may send data delivery information to the TDDF 236 (e.g., which may include, for example, currently achieved data rate or throughput for UE, buffer size, and/or information on supportable but not activated cells for UE). At 816, the TDDF 236 may determine a basic data capacity information for the UE, e.g., based on the data delivery information. At 818, the TDDF 236 may determine data expansion information (e.g., DEF) for the UE, e.g., based on the data delivery information. At 820, the TDDF 236 may send or provide the basic data capacity information and data expansion information to the lower network node 212. TDDF may be provided on or within TDDF, for example, or other location. At 822, the lower network node provides the anchor point 234 (or sends to the anchor point 234) both the basic data capacity information and the data expansion information (e.g., DEF). At 834, the anchor point 234 may determine an updated (e.g., a total) amount or rate of data to send to lower network node 212 for UE 210, based on the basic data capacity information and the data expansion information for the UE 210. At 826, the anchor point sends or delivers the data (the amount or rate of data) as determined at 824 based on the basic data capacity information and the data expansion information. At 828, the lower network node 212 receives the data, and may activate one or more additional secondary cells for the UE 210, e.g., to accommodate the amount or rate of data that is being received by the lower network node for the UE 210. At 830, the lower network node 212 may deliver or transmit the data to the UE 210 via the plurality of activated cells for the UE (e.g., a primary cell and one or more secondary cells). [0088] Example 1. A method comprising: sending, by a network node to a control entity, at least a data expansion information that indicates an additional downlink data capacity of a user device that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device; and receiving, by the network node, downlink data for the user device, having a data rate or amount of data that is based at least on the data expansion information for the user device.

[0089] Example 2. The method of example 1, wherein the sending comprises: sending, by the network node to the control entity, at least the data expansion information that indicates the additional downlink data capacity, thereby causing the control entity to control sending of downlink data to the user device via the network node at a data rate or amount of data that is based on the data expansion information for the user device.

[0090] Example 3. The method of any of examples 1-2, wherein the receiving comprises: receiving, by the network node, downlink data for the user device, having a data rate or amount of data that is based at least on the data expansion information for the user device, thereby causing the network node to activate one or more candidate cells for the user device that are not currently activated for the user device.

[0091] Example 4. The method of any of examples 1-3, further comprising: activating, by the network node based on the receiving of downlink data for the user device, one or more candidate cells for the user device that are not currently activated for the user device.

[0092] Example 5. The method of any of examples 1-4, wherein: the control entity comprises an anchor point that controls downlink data sending of data for the user device one or more nodes including the network node; and the network node comprises at least one of a gNB or a gNB-distributed unit (gNB-DU).

[0093] Example 6. The method of any of examples 1-5 wherein the data expansion information comprises at least one of the following: a data expansion information that indicates an additional downlink data rate of the user device; a data expansion information that indicates an additional buffer size of the user device.

[0094] Example 7. The method of any of examples 1-6, further comprising: sending, by the network node to the control entity, in addition to the data expansion information, a basic data capacity information that indicates a current downlink data capacity of the user device based on one or more cells of the network node that are currently activated for the user device. [0095] Example 8. The method of example 7, wherein the receiving comprises: receiving, by the network node, downlink data for the user device, having a data rate or amount of data that is based at least on both of the basic data capacity information and the data expansion information for the user device.

[0096] Example 9. The method of any of examples 7-8, wherein the basic data capacity information comprises a downlink data delivery status message including at least one of a desired buffer size and a desired data rate.

[0097] Example 10. The method of any of examples 1-9, wherein the data expansion information indicates: an additive factor that indicates an additional downlink data capacity of a user device, in addition to the current downlink data capacity of the user device, that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device.

[0098] Example 11. The method of any of examples 1-10, wherein the data expansion information indicates: a multiplicative factor that indicates an additional percentage or amount of the current downlink data capacity of the user device, that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device.

[0099] Example 12. The method of any of examples 1-11, further comprising: determining, by the network node, data delivery information for the user device, including: a data rate and/or buffer size achieved by the user device based on the one or more cells of the network node that are currently activated for the user device; and information associated with one or more additional cells that have not been activated by the network node for the user device and which are supportable by the user device; the method further comprising: determining the data expansion information that indicates the additional downlink data capacity of a user device based on at least a portion of the data delivery information.

[0100] Example 13. A method comprising: sending, by a network node to a data determination entity, data delivery information for a user device within a wireless network, the data delivery information including at least one of a data rate and/or buffer size achieved by the user device based on one or more cells of the network node that are currently activated for the user device, or information associated with one or more additional cells that have not been activated by the network node for the user device and which are supportable by the user device; receiving, by the network node from the data determination entity, at least a data expansion information that indicates an additional downlink data capacity of the user device that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device; sending, by the network node to a control entity, the data expansion information; and receiving, by the network node, downlink data for the user device, having a data rate or amount of data that is based at least on the data expansion information for the user device.

[0101] Example 14. The method of example 13, wherein: the network node comprises a gNB or a gNB-distributed unit (gNB-DU); and the control entity comprises an anchor point that controls downlink data forwarding of data for the user device via a plurality of nodes including the network node.

[0102] Example 15. The method of any of examples 13-14, further comprising: sending, by the network node to the data determination entity, in addition to the data expansion information, a basic data capacity information that indicates a current downlink data capacity of the user device based on one or more cells of the network node that are currently activated for the user device.

[0103] Example 16. The method of example 15, wherein the receiving comprises: receiving, by the network node, downlink data for the user device, having a data rate or amount of data that is based at least on both of the basic data capacity information and the data expansion information for the user device.

[0104] Example 17. A method comprising: receiving, by a data determination entity from a network node to, data delivery information for a user device within a wireless network, the data delivery information including at least one of a data rate and/or buffer size achieved by the user device based on one or more cells of the network node that are currently activated for the user device, or information associated with one or more additional cells that have not been activated by the network node for the user device and which are supportable by the user device; determining, by the data determination entity based on the data delivery information, at least a data expansion information that indicates an additional downlink data capacity of the user device that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device; and, sending, by the network node, to either the network node or a control entity that controls downlink data forwarding of data for the user device, at least the data expansion information.

[0105] Example 18. The method of example 17, wherein: the network node comprises a gNB or a gNB-distributed unit (gNB-DU); and the control entity comprises an anchor point that controls downlink data forwarding of data for the user device via a plurality of nodes including the network node.

[0106] Example 19. The method of any of examples 17-18, further comprising: determining a basic data capacity information that indicates a current downlink data capacity of the user device based on one or more cells of the network node that are currently activated for the user device.

[0107] Example 20. The method of example 19, wherein the sending comprises: sending, by the network node, to either the network node or the control entity that controls downlink data forwarding of data for the user device, both the basic data capacity information and the data expansion information.

[0108] Example 21. A method comprising: receiving, by a control entity that controls downlink data forwarding of data for a user device via a plurality of nodes including a network node, at least a data expansion information that indicates an additional downlink data capacity of the user device that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device; determining, by the control entity, an updated data rate or amount of data to be transmitted by at least the network node to the user device, based at least on the data expansion information; and sending, by the control entity to the network node, data for the user device based on at least the data expansion information.

[0109] Example 22. The method of example 21 wherein: the network node comprises a gNB or a gNB-distributed unit (gNB-DU); and the control entity comprises an anchor point that controls downlink data forwarding of data for the user device via a plurality of nodes including the network node.

[0110] Example 23. The method of any of examples 21-22, further comprising: receiving, by the control entity from at least one of the network node or a data determination entity, in addition to the data expansion information, a basic data capacity information that indicates a current downlink data capacity of the user device based on one or more cells of the network node that are currently activated for the user device. [0111] Example 24. The method of example 23, wherein the determining comprises: determining, by the control entity, an updated data rate or amount of data to be transmitted by at least the network node to the user device, based at least on the basic data capacity information and the data expansion information.

[0112] Example 25. The method of example 24, wherein the sending comprises: sending, by the control entity to the network node, data for the user device based on at least the data expansion information and the basic data capacity information.

[0113] Example 26. An apparatus comprising means for performing the method of any of examples 1-25.

[0114] Example 27. A non-transitory computer-readable storage medium comprising instructions stored thereon that, when executed by at least one processor, are configured to cause a computing system to perform the method of any of examples 1-25.

[0115] Example 28. An apparatus comprising: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform the method of any of examples 1-25.

[0116] Example 29. A method comprising: sending, by a network node to a control entity, at least a data capacity information for the user device; sending, by the network node to the control entity, a data capacity format indication that indicates whether or not the data capacity information includes downlink data capacity of the user device that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device; and receiving, by the network node, downlink data for the user device, having a data rate or amount of data that is based at least on the data capacity information and the data capacity format indication.

[0117] Example 30. The method of example 29, wherein the data capacity format indication may be either a first value to indicate that the data capacity information indicates a downlink data capacity of the user device based on only one or more cells of the network node that are currently activated for the user device, or a second value to indicate that the data capacity information indicates an expanded data capacity of the user device that is based on both one or more cells of the network node that are currently activated for the user device and one or more candidate cells for the user device that are not currently activated for the user device. [0118] Example 31. The method of any of examples 29-30, wherein the data capacity information comprises at least one of a desired buffer size and a desired data rate.

[0119] Example 32. An apparatus comprising means for performing the method of any of examples 29-31.

[0120] Example 33. A non-transitory computer-readable storage medium comprising instructions stored thereon that, when executed by at least one processor, are configured to cause a computing system to perform the method of any of examples 29-31.

[0121] Example 34. An apparatus comprising: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform the method of any of examples 29-31.

[0122] FIG. 9 is a block diagram of a wireless station (e.g., AP, BS or user device/UE, or other network node) 1200 according to an example embodiment. The wireless station 1200 may include, for example, one or more (e.g., two as shown in FIG. 9) RF (radio frequency) or wireless transceivers 1202A, 1202B, where each wireless transceiver includes a transmitter to transmit signals and a receiver to receive signals. The wireless station also includes a processor or control unit/entity (controller) 1204 to execute instructions or software and control transmission and receptions of signals, and a memory 1206 to store data and/or instructions.

[0123] Processor 1204 may also make decisions or determinations, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein. Processor 1204, which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wireless transceiver 1202 (1202 A or 1202B). Processor 1204 may control transmission of signals or messages over a wireless network, and may control the reception of signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 1202, for example). Processor 1204 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above. Processor 1204 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and/or any combination of these. Using other terminology, processor 1204 and transceiver 1202 together may be considered as a wireless transmitter/receiver system, for example.

[0124] In addition, referring to FIG. 9, a controller (or processor) 1208 may execute software and instructions, and may provide overall control for the station 1200, and may provide control for other systems not shown in FIG. 9, such as controlling input/output devices (e.g., display, keypad), and/or may execute software for one or more applications that may be provided on wireless station 1200, such as, for example, an email program, audio/video applications, a word processor, a Voice over IP application, or other application or software.

[0125] In addition, a storage medium may be provided that includes stored instructions, which when executed by a controller or processor may result in the processor 1204, or other controller or processor, performing one or more of the functions or tasks described above.

[0126] According to another example embodiment, RF or wireless transceiver(s) 1202A/1202B may receive signals or data and/or transmit or send signals or data. Processor 1204 (and possibly transceivers 1202A/1202B) may control the RF or wireless transceiver 1202 A or 1202B to receive, send, broadcast or transmit signals or data.

[0127] The embodiments are not, however, restricted to the system that is given as an example, but a person skilled in the art may apply the solution to other communication systems. Another example of a suitable communications system is the 5G concept. It is assumed that network architecture in 5G will be quite similar to that of the LTE-advanced. 5G is likely to use multiple input - multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.

[0128] It should be appreciated that future networks will most probably utilise network functions virtualization (NFV) which is a network architecture concept that proposes virtualizing network node functions into “building blocks” or entities that may be operationally connected or linked together to provide services. A virtualized network function (VNF) may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized. In radio communications this may mean node operations may be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labour between core network operations and base station operations may differ from that of the LTE or even be non-existent.

[0129] Embodiments of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Embodiments may be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, a data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. Embodiments may also be provided on a computer readable medium or computer readable storage medium, which may be a non-transitory medium. Embodiments of the various techniques may also include embodiments provided via transitory signals or media, and/or programs and/or software embodiments that are downloadable via the Internet or other network(s), either wired networks and/or wireless networks. In addition, embodiments may be provided via machine type communications (MTC), and also via an Internet of Things (IOT).

[0130] The computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers.

[0131] Furthermore, embodiments of the various techniques described herein may use a cyber-physical system (CPS) (a system of collaborating computational elements controlling physical entities). CPS may enable the embodiment and exploitation of massive amounts of interconnected ICT devices (sensors, actuators, processors microcontrollers, . . .) embedded in physical objects at different locations. Mobile cyber physical systems, in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals. The rise in popularity of smartphones has increased interest in the area of mobile cyber-physical systems. Therefore, various embodiments of techniques described herein may be provided via one or more of these technologies.

[0132] A computer program, such as the computer program(s) described above, can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit or part of it suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.

[0133] Method steps may be performed by one or more programmable processors executing a computer program or computer program portions to perform functions by operating on input data and generating output. Method steps also may be performed by, and an apparatus may be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

[0134] Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer, chip or chipset. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer also may include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto- optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory may be supplemented by, or incorporated in, special purpose logic circuitry.

[0135] To provide for interaction with a user, embodiments may be implemented on a computer having a display device, e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor, for displaying information to the user and a user interface, such as a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.

[0136] Embodiments may be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an embodiment, or any combination of such back-end, middleware, or front-end components. Components may be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (LAN) and a wide area network (WAN), e.g., the Internet.

[0137] While certain features of the described embodiments have been illustrated as described herein, many modifications, substitutions, changes and equivalents will now occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the various embodiments.

Claims

43 WHAT IS CLAIMED IS:

1. A method comprising: sending, by a network node to a control entity, at least a data expansion information that indicates an additional downlink data capacity of a user device that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device; and receiving, by the network node, downlink data for the user device, having a data rate or amount of data that is based at least on the data expansion information for the user device.

2. The method of claim 1, wherein the sending comprises: sending, by the network node to the control entity, at least the data expansion information that indicates the additional downlink data capacity, thereby causing the control entity to control sending of downlink data to the user device via the network node at a data rate or amount of data that is based on the data expansion information for the user device.

3. The method of any of claims 1-2, wherein the receiving comprises: receiving, by the network node, downlink data for the user device, having a data rate or amount of data that is based at least on the data expansion information for the user device, thereby causing the network node to activate one or more candidate cells for the user device that are not currently activated for the user device.

4. The method of any of claims 1-3, further comprising: activating, by the network node based on the receiving of downlink data for the user device, one or more candidate cells for the user device that are not currently activated for the user device.

5. The method of any of claims 1-4, wherein: the control entity comprises an anchor point that controls downlink data sending of data for the user device one or more nodes including the network node; and the network node comprises at least one of a gNB or a gNB-distributed unit (gNB-DU). 44

6. The method of any of claims 1-5 wherein the data expansion information comprises at least one of the following: a data expansion information that indicates an additional downlink data rate of the user device; a data expansion information that indicates an additional buffer size of the user device.

7. The method of any of claims 1-6, further comprising: sending, by the network node to the control entity, in addition to the data expansion information, a basic data capacity information that indicates a current downlink data capacity of the user device based on one or more cells of the network node that are currently activated for the user device.

8. The method of claim 7, wherein the receiving comprises: receiving, by the network node, downlink data for the user device, having a data rate or amount of data that is based at least on both of the basic data capacity information and the data expansion information for the user device.

9. The method of claim 7, wherein the basic data capacity information comprises a downlink data delivery status message including at least one of a desired buffer size and a desired data rate.

10. The method of any of claims 1-9, wherein the data expansion information indicates: an additive factor that indicates an additional downlink data capacity of a user device, in addition to the current downlink data capacity of the user device, that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device. 45

11. The method of any of claims 1-10, wherein the data expansion information indicates: a multiplicative factor that indicates an additional percentage or amount of the current downlink data capacity of the user device, that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device.

12. The method of any of claims 1-11, further comprising: determining, by the network node, data delivery information for the user device, including: a data rate and/or buffer size achieved by the user device based on the one or more cells of the network node that are currently activated for the user device; and information associated with one or more additional cells that have not been activated by the network node for the user device and which are supportable by the user device; the method further comprising: determining the data expansion information that indicates the additional downlink data capacity of a user device based on at least a portion of the data delivery information.

13. A method comprising: sending, by a network node to a data determination entity, data delivery information for a user device within a wireless network, the data delivery information including at least one of a data rate and/or buffer size achieved by the user device based on one or more cells of the network node that are currently activated for the user device, or information associated with one or more additional cells that have not been activated by the network node for the user device and which are supportable by the user device; receiving, by the network node from the data determination entity, at least a data expansion information that indicates an additional downlink data capacity of the user device that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device; sending, by the network node to a control entity, the data expansion information; and receiving, by the network node, downlink data for the user device, having a data rate or amount of data that is based at least on the data expansion information for the user device.

14. The method of claim 13, wherein: the network node comprises a gNB or a gNB-distributed unit (gNB-DU); and the control entity comprises an anchor point that controls downlink data forwarding of data for the user device via a plurality of nodes including the network node.

15. The method of any of claims 13-14, further comprising: sending, by the network node to the data determination entity, in addition to the data expansion information, a basic data capacity information that indicates a current downlink data capacity of the user device based on one or more cells of the network node that are currently activated for the user device.

16. The method of claim 15, wherein the receiving comprises: receiving, by the network node, downlink data for the user device, having a data rate or amount of data that is based at least on both of the basic data capacity information and the data expansion information for the user device.

17. A method comprising: receiving, by a data determination entity from a network node to, data delivery information for a user device within a wireless network, the data delivery information including at least one of a data rate and/or buffer size achieved by the user device based on one or more cells of the network node that are currently activated for the user device, or information associated with one or more additional cells that have not been activated by the network node for the user device and which are supportable by the user device; determining, by the data determination entity based on the data delivery information, at least a data expansion information that indicates an additional downlink data capacity of the user device that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device; sending, by the network node, to either the network node or a control entity that controls downlink data forwarding of data for the user device, at least the data expansion information.

18. The method of claim 17, wherein: the network node comprises a gNB or a gNB-distributed unit (gNB-DU); and the control entity comprises an anchor point that controls downlink data forwarding of data for the user device via a plurality of nodes including the network node.

19. The method of any of claims 17-18, further comprising: determining a basic data capacity information that indicates a current downlink data capacity of the user device based on one or more cells of the network node that are currently activated for the user device.

20. The method of claim 19, wherein the sending comprises: sending, by the network node, to either the network node or the control entity that controls downlink data forwarding of data for the user device, both the basic data capacity information and the data expansion information.

21. A method comprising: receiving, by a control entity that controls downlink data forwarding of data for a user device via a plurality of nodes including a network node, at least a data expansion information that indicates an additional downlink data capacity of the user device that can be achieved via an activation by the network node of one or more candidate cells for the user device that are not currently activated for the user device; determining, by the control entity, an updated data rate or amount of data to be transmitted by at least the network node to the user device, based at least on the data expansion information; and sending, by the control entity to the network node, data for the user device based on at least the data expansion information.

22. The method of claim 21 wherein: the network node comprises a gNB or a gNB-distributed unit (gNB-DU); and the control entity comprises an anchor point that controls downlink data forwarding of data for the user device via a plurality of nodes including the network node. 48

23. The method of any of claims 21-22, further comprising: receiving, by the control entity from at least one of the network node or a data determination entity, in addition to the data expansion information, a basic data capacity information that indicates a current downlink data capacity of the user device based on one or more cells of the network node that are currently activated for the user device.

24. The method of claim 23, wherein the determining comprises: determining, by the control entity, an updated data rate or amount of data to be transmitted by at least the network node to the user device, based at least on the basic data capacity information and the data expansion information.

25. The method of claim 24, wherein the sending comprises: sending, by the control entity to the network node, data for the user device based on at least the data expansion information and the basic data capacity information.

26. An apparatus comprising means for performing the method of any of claims 1-25.

27. A non-transitory computer-readable storage medium comprising instructions stored thereon that, when executed by at least one processor, are configured to cause a computing system to perform the method of any of claims 1-25.

28. An apparatus comprising: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform the method of any of claims 1-25.