WO2021034255A1

WO2021034255A1 - Data rate handling for nr-dc with mcg and scg operation in same frequency range

Info

Publication number: WO2021034255A1
Application number: PCT/SE2020/050788
Authority: WO
Inventors: Ajit Nimbalker
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2019-08-16
Filing date: 2020-08-14
Publication date: 2021-02-25

Abstract

According to one or more embodiments, a network node (16) configured to communicate with a wireless device (22) is provided. The wireless device (22) is configured with dual connectivity to a plurality of cell groups operating in a frequency range. The network node (16) comprising processing circuitry (68) configured to receive capability information associated with the plurality of cell groups, and transmit at least one Radio Resource Control, RRC, parameter indicating a first data rate that is based on the capability information where the first data rate is configured for use by the wireless device (22) with a first cell group of the plurality of cell groups.

Description

DATA RATE HANDLING FOR NR-DC WITH MCG AND SCG OPERATION

IN SAME FREQUENCY RANGE

TECHNICAL FIELD

The present disclosure relates to wireless communications, and in particular, to data rate handling for dual connectivity (DC) with multiple cell groups.

BACKGROUND

The New Radio (NR, also referred to as 5^th Generation (5G)) standard in third generation partnership project (3GPP) is being designed to help provide service for multiple use cases such as enhanced mobile broadband (eMBB), ultra-reliable and low latency communication (URLLC), and machine type communication (MTC).

FIG. 1 illustrates an example radio resource in NR. Each of these services has different technical requirements. For example, the general requirement for eMBB is a high data rate with moderate latency and moderate coverage, while URLLC service may require low latency and high reliability transmission but perhaps for moderate data rates.

One of the methods for help provide low latency data transmission is shorter transmission time intervals. In NR in addition to transmission in a slot, a mini-slot transmission is also allowed to reduce latency. A mini-slot may consist of any number of 1 to 14 OFDM symbols. It should be noted that the concepts of slot and mini-slot are not specific to a specific service meaning that a mini-slot may be used for either eMBB, URLLC, or other services.

Peak rate and transport block size

Unlike LTE, NR transmission duration for a packet, processing times, transmission bandwidths are flexible, and therefore, how to define the peak data rate and its implications on scheduling decisions (e.g., transport block size) are not clearly defined.

For 3GPP standards such as 3GPP Release 15 (Rel-15) including late drop, the data rate related transport block size (TBS) restriction is applied on a per-FR per-CG basis based on a data rate calculation that is based on feature sets reported in wireless device capability signaling. This can be problematic for the case when master cell group (MCG) and secondary cell group (SCG) are operating on carriers in the same frequency range because in such cases the wireless device may have a hardware partitioning that might limit the data rate sharing based the reported features. For example, the MCG and SCG may, due to independent scheduling, end up scheduling the wireless device based on a peak rate larger than it can support, or end up with conservative scheduling and under-utilize wireless device capability, i.e., schedule the wireless device based on a peak rate smaller than the wireless device can support.

Therefore, existing systems suffer from one or more problems related to dual connectivity with multiple cell groups.

SUMMARY

Some embodiments advantageously provide methods, systems, and apparatuses for data rate handling for dual connectivity wireless communication environments.

A method to configure new RRC parameters for data rate calculation in applying TBS restriction in case of MCG and SCG operation in same frequency range for one wireless device is described.

According to one aspect of the disclosure, a network node configured to communicate with a wireless device is provided. The wireless device is configured with dual connectivity to a plurality of cell groups operating in a frequency range. The network node includes processing circuitry configured to: receive capability information associated with the plurality of cell groups; and transmit at least one Radio Resource Control, RRC, parameter indicating a first data rate that is based on the capability information, the first data rate being configured for use by the wireless device with a first cell group of the plurality of cell groups.

According to one or more embodiments of this aspect, the at least one RRC parameter further indicates a second data rate that is based on the capability information where the second data rate is configured for use by the wireless device with a second cell group of the plurality of cell groups. According to one or more embodiments of this aspect, the at least one RRC parameter includes at least one per- cell RRC parameter that is reused to indicate at least one per-component carrier parameter. According to one or more embodiments of this aspect, the at least one per- component carrier parameter indicates at least one of: a maximum number of MIMO layers, and a numerology. According to one or more embodiments, the at least one RRC parameter indicates at least one of: a modulation order configured per- component carrier, a scaling factor configured per-component carrier, and a resource block allocation configured per-component carrier.

According to one or more embodiments of this aspect, the at least one RRC parameter indicates a first constraint per component-carrier for the first cell group and a second constraint per component-carrier for the second cell group of the plurality of cell groups. According to one or more embodiments of this aspect, the first constraint is a first transport block size (TBS) size constraint per component-carrier for the first cell group and the second constraint is a second TBS size constraint per component- carrier for the second cell group. According to one or more embodiments of this aspect, the first and second constraints are configured to be applied to at least one reference slot duration for at least one component-carrier.

According to one or more embodiments of this aspect, the first cell group is a master cell group and the second cell group is a secondary cell group. According to one or more embodiments of this aspect, the first data rate corresponds to a maximum data rate configured to be used by the wireless device with the first cell group. According to one or more embodiments of this aspect, the processing circuitry is further configured to transmit control information for scheduling data transmission, the control information scheduling data transmission for the wireless device that does not exceed the first data rate.

According to another aspect of the disclosure, a wireless device configured to communicate with a network node is provided. The wireless device is configured to support dual connectivity to a plurality of cell groups operating in a frequency range. The wireless device includes processing circuitry configured to: transmit of capability information associated with the plurality cell groups; and receive at least one Radio Resource Control, RRC, parameter indicating a first data rate that is based on the capability information where the first data rate is configured for use by the wireless device with a first cell group of the plurality of cell groups.

According to one or more embodiments of this aspect, the processing circuitry is further configured to: receive control information for scheduling data transmission in the first cell group where the scheduled data does not exceed the first data rate, receive the data transmission according to the control information; and process the data transmission. According to one or more embodiments of this aspect, the first data is based on a number of configured serving cells per frequency range. According to one or more embodiments of this aspect, the at least one RRC parameter further indicates a second data rate that is based on capability information where the second data rate is configured for use by the wireless device with a second cell group of the plurality of cell groups.

According to one or more embodiments of this aspect, the at least one RRC parameter includes at least one per-cell RRC parameter that is reused to indicate at least one per-component carrier parameter. According to one or more embodiments of this aspect, the at least one per-component carrier RRC parameter indicates at least one of: a maximum number of MIMO layers, and a numerology. According to one or more embodiments of this aspect, the at least one RRC parameter indicates at least one of: a modulation order configured per-component carrier, a scaling factor configured per-component carrier, and a resource block allocation configured per- component carrier. According to one or more embodiments of this aspect, the at least one RRC parameter indicates a first constraint per component-carrier for the first cell group and a second constraint per component-carrier for the second cell group of the plurality of cell groups.

According to one or more embodiments of this aspect, the first constraint is a first transport block size (TBS) size constraint per component-carrier for the first cell group and the second constraint is a second TBS size constraint per component-carrier for the second cell group. According to one or more embodiments of this aspect, the processing circuitry is further configured to process at least one reference slot duration for at least one component-carrier that meets at least one of the first and second constraints. According to one or more embodiments of this aspect, the first data rate corresponds to a maximum data rate configured to be used by the wireless device with the first cell group.

According to another aspect of the disclosure, a method implemented by a network node that is configured to communicate with a wireless device is provided. The wireless device is configured with dual connectivity to a plurality of cell groups operating in a frequency range. Capability information associated with the plurality of cell groups is received. At least one Radio Resource Control, RRC, parameter indicating a first data rate that is based on the capability information is transmitted. The first data rate is configured for use by the wireless device with a first cell group of the plurality of cell groups.

According to one or more embodiments of this aspect, the at least one RRC parameter further indicates a second data rate that is based on the capability information where the second data rate is configured for use by the wireless device with a second cell group of the plurality of cell groups. According to one or more embodiments of this aspect, the at least one RRC parameter includes at least one per- cell RRC parameter that is reused to indicate at least one per-component carrier parameter. According to one or more embodiments of this aspect, the at least one per- component carrier parameter indicates at least one of: a maximum number of MIMO layers, and a numerology. According to one or more embodiments of this aspect, the at least one RRC parameter indicates at least one of: a modulation order configured per-component carrier, a scaling factor configured per-component carrier, and a resource block allocation configured per-component carrier.

According to one or more embodiments of this aspect, the first cell group is a master cell group and the second cell group is a secondary cell group. According to one or more embodiments of this aspect, the first data rate corresponds to a maximum data rate configured to be used by the wireless device with the first cell group. According to one or more embodiments of this aspect, control information for scheduling data transmission is transmitted where the control information scheduling data transmission for the wireless device that does not exceed the first data rate. According to another aspect of the disclosure, a method implemented by a wireless device that is configured to communicate with a network node is provided. The wireless device is configured to support dual connectivity to a plurality of cell groups operating in a frequency range. Capability information associated with the plurality cell groups is transmitted. At least one Radio Resource Control, RRC, parameter indicating a first data rate that is based on the capability information is received. The first data rate is configured for use by the wireless device with a first cell group of the plurality of cell groups.

According to one or more embodiments of this aspect, control information for scheduling data transmission in the first cell group is received where the scheduled data transmission does not exceed the first data rate, , the data transmission is received according to the control information, and the data transmission is processed.

According to one or more embodiments of this aspect, the first data is based on a number of configured serving cells per frequency range. According to one or more embodiments of this aspect, the at least one RRC parameter further indicates a second data rate that is based on capability information where the second data rate is configured for use by the wireless device with a second cell group of the plurality of cell groups.

According to one or more embodiments of this aspect, the first constraint is a first transport block size (TBS) size constraint per component-carrier for the first cell group and the second constraint is a second TBS size constraint per component-carrier for the second cell group. According to one or more embodiments of this aspect, processing of at least one reference slot duration for at least one component-carrier that meets at least one of the first and second constraints is performed. According to one or more embodiments of this aspect, the first data rate corresponds to a maximum data rate configured to be used by the wireless device with the first cell group.

According to another aspect of the disclosure, a wireless device configured to communicate with a network node is provided. The wireless device is configured with dual connectivity to a plurality of cell groups operating in a frequency range.

The wireless device includes processing circuitry configured to: transmit capability information associated with a first cell group of the plurality of cell groups where the capability information includes band combination signaling information and feature set information, receive at least one Radio Resource Control, RRC, parameter indicating a first maximum data rate that is based on the capability information where the first maximum data rate is configured for use by the wireless device with a first cell group of the plurality of cell groups, and receive control information for scheduling data transmission in the first cell group where the scheduled data transmission does not exceed the first maximum data rate.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

FIG. l is a diagram of radio resources in NR;

FIG. 2 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;

FIG. 3 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure; FIG. 4 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure;

FIG. 5 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure;

FIG. 6 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure;

FIG. 7 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure;

FIG. 8 is a flowchart of an example process in a network node according to some embodiments of the present disclosure;

FIG. 9 is a flowchart of another example process in the network node according to some embodiments of the present disclosure;

FIG. 10 is a flowchart of an example process in a wireless device according to some embodiments of the present disclosure; and

FIG. 11 is a flowchart of another exemplary process in the wireless device according to some embodiments of the present disclosure.

DETAILED DESCRIPTION

There is a need for an arrangement method that can enhance data rate sharing for MCG and SCG operation in same frequency range for a wireless device. Further, it would be advantageous to have an arrangement that can reflect the impact of peak data rate on scheduling decisions such as transport block size. In particular, the arrangement may need to address the cases where wireless device capability signalling can include multiple parameters that together are used for defining an approximate peak data rate, including a scaling factor that can at least take values 1, 0.8, 0.75 and 0.4, for example. As used herein, wireless device capability may, for example, refer to a wireless device configuration such as a current configuration and/or potential configuration that is indicated by the wireless device where the network node configures the wireless device for operation according to the wireless device capability. For example, the network node may configure the wireless device based on wireless device capability to help ensure that wireless capability if not exceed by such as configuration. Cases including multiple numerologies, multiple carriers with same or different numerologies, dual connectivity cases, etc, may also need to be addressed in any new scheme.

One or more embodiments of the disclosure advantageously solves at least a portion of at least one issue with existing systems at least in part by accommodating complexity and decoding constraints at the wireless device, while keeping the scheduler restrictions to a minimum such as in cases where MCG and SCG operate in same frequency range for a wireless device. In one or more embodiments, a method/process/scheme is provided to configure new RRC parameters for data rate calculation in applying TBS restriction in case of MCG and SCG operation in same frequency range for a wireless device.

Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to data rate handling in dual connectivity schemes. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and/or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.

The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node. In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD). The WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (IoT) device, or a Narrowband IoT (NB-IOT) device, etc.

Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

An indication generally may explicitly and/or implicitly indicate the information it represents and/or indicates. Implicit indication may for example be based on position and/or resource used for transmission. Explicit indication may for example be based on a parametrization with one or more parameters, and/or one or more index or indices, and/or one or more bit patterns representing the information.

A cell may be generally a communication cell, e.g., of a cellular or mobile communication network, provided by a node. A serving cell may be a cell on or via which a network node (the node providing or associated to the cell, e.g., base station, gNB or eNodeB) transmits and/or may transmit data (which may be data other than broadcast data) to a user equipment, in particular control and/or user or payload data, and/or via or on which a user equipment transmits and/or may transmit data to the node; a serving cell may be a cell for or on which the user equipment is configured and/or to which it is synchronized and/or has performed an access procedure, e.g., a random access procedure, and/or in relation to which it is in a RRC connected or RRC idle state, e.g., in case the node and/or user equipment and/or network follow the LTE-standard and/or NR standard. One or more carriers (e.g., uplink and/or downlink carrier/s and/or a carrier for both uplink and downlink) may be associated to a cell.

Transmitting in downlink may pertain to transmission from the network or network node to the terminal. Transmitting in uplink may pertain to transmission from the terminal to the network or network node. Transmitting in sidelink may pertain to (direct) transmission from one terminal to another. Uplink, downlink and sidelink (e.g., sidelink transmission and reception) may be considered communication directions. In some variants, uplink and downlink may also be used to described wireless communication between network nodes, e.g. for wireless backhaul and/or relay communication and/or (wireless) network communication for example between base stations or similar network nodes, in particular communication terminating at such. It may be considered that backhaul and/or relay communication and/or network communication is implemented as a form of sidelink or uplink communication or similar thereto.

Configuring a terminal or wireless device or node may involve instructing and/or causing the wireless device or node to change its configuration, e.g., at least one setting and/or register entry and/or operational mode and/or to report wireless device capability. A terminal or wireless device or node may be adapted to configure itself, e.g., according to information or data in a memory of the terminal or wireless device. Configuring a node or terminal or wireless device by another device or node or a network may refer to and/or comprise transmitting information and/or data and/or instructions to the wireless device or node by the other device or node or the network, e.g., allocation data (which may also be and/or comprise configuration data) and/or scheduling data and/or scheduling grants. Configuring a terminal may include sending allocation/configuration data to the terminal indicating which modulation and/or encoding to use. A terminal may be configured with and/or for scheduling data and/or to use, e.g., for transmission, scheduled and/or allocated uplink resources, and/or, e.g., for reception, scheduled and/or allocated downlink resources. Uplink resources and/or downlink resources may be scheduled and/or provided with allocation or configuration data.

Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and/or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

Embodiments provide data rate handling in dual connectivity schemes. Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 2 a schematic diagram of a communication system 10, according to an embodiment, such as a 3 GPP -type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16c. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16a. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16.

Also, it is contemplated that a WD 22 can be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, WD 22 can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.

The communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).

The communication system of FIG. 2 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24. The connectivity may be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.

A network node 16 is configured to include a rate unit 32 which is configured to perform one or more network node 16 function as described herein such as with respect data rate handling. A wireless device 22 is configured to include an indication unit 34 which is configured to perform one or more wireless device 22 functions described herein such as with respect to data rate handling.

Example implementations, in accordance with an embodiment, of the WD 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to FIG. 3. In a communication system 10, a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and/or read from) memory 46, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read- Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 24. Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein. The host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with the host computer 24.

The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52. The “user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and or the wireless device 22. The processing circuitry 42 of the host computer 24 may include an information unit 54 configured to enable the service provider to one or more of process, store, determine, receive, transmit, forward, relay, route, etc. information related to data rate handling that is described herein.

The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10.

In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and/or read from) the memory 72, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include rate unit 32 configured to perform one or more network node 16 functions described herein such as with respect to data rate handling.

The communication system 10 further includes the WD 22 already referred to. The WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.

The hardware 80 of the WD 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides. The processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD 22. The processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein. The WD 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to WD 22. For example, the processing circuitry 84 of the wireless device 22 may include an indication unit 34 configured to perform one or more wireless device functions as described herein such as with respect to data rate handling.

In some embodiments, the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in FIG. 3 and independently, the surrounding network topology may be that of FIG. 2.

In FIG. 3, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

The wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc. In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and WD 22, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors etc.

Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the WD 22, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the WD 22. In some embodiments, the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16. In some embodiments, the WD 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for preparing/ini tiating/maintaining/supporting/ending a transmission to the network node 16, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the network node 16.

Although FIGS. 2 and 3 show various “units” such as rate unit 32, and indication unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

FIG. 4 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIGS. 2 and 3, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG. 3. In a first step of the method, the host computer 24 provides user data (Block SI 00). In an optional substep of the first step, the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block SI 02). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 04). In an optional third step, the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06). In an optional fourth step, the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block SI 08).

FIG. 5 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3. In a first step of the method, the host computer 24 provides user data (Block SI 10). In an optional substep (not shown) the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 12). The transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the WD 22 receives the user data carried in the transmission (Block SI 14).

FIG. 6 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3. In an optional first step of the method, the WD 22 receives input data provided by the host computer 24 (Block SI 16). In an optional substep of the first step, the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block SI 18). Additionally or alternatively, in an optional second step, the WD 22 provides user data (Block S120). In an optional substep of the second step, the WD provides the user data by executing a client application, such as, for example, client application 92 (Block S122). In providing the user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block S124). In a fourth step of the method, the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).

FIG. 7 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 receives user data from the WD 22 (Block S128). In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (Block SI 30). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block SI 32).

FIG. 8 is a flowchart of an example process in a network node 16 according to one or more embodiments of the present disclosure. One or more Blocks and/or functions performed by network node 16 may be performed by one or more elements of network node 16 such as by rate unit 32 in processing circuitry 68, processor 70, radio interface 62, etc. In one or more embodiments, the network node 16 is configured to communicate with a wireless device 22 where the wireless device 22 is configured with dual connectivity to a master cell group (MCG) operating on a first component carrier, CC, and secondary cell group (SCG) operating on a second CC that at least partially overlaps the first CC. In one or more embodiments, network node 16 such as via one or more of processing circuitry 68, processor 70, communication interface 60 and radio interface 62 is configured to receive (Block SI 34) radio resource control, RRC, signaling indicating wireless device capability, as described herein. In one or more embodiments, network node 16 such as via one or more of processing circuitry 68, processor 70, communication interface 60 and radio interface 62 is configured to schedule (Block S136) the wireless device 22 according to a peak data rate that is based at least in part on the wireless device capability, as described herein.

According to one or more embodiments, the network node 16 is further configured to, and/or the radio interface 62 and/ processing circuitry 68 is further configured to cause the wireless device 22 to report the wireless device capability using RRC signaling, as described herein. According to one or more embodiments, the wireless device capability includes at least one of: maximum number of multiple- in multiple out, MIMO, layers configured for at least one of the first CC and second CC, modulation order for data rate calculation configured for at least one of the first CC and second CC, scaling factor for data rate calculation configured for at least one of the first CC and second CC, ^m is the numerology for at least one of the first CC and second CC, and resource block, RB, allocation for data rate calculation configured for at least one of the first CC and second CC.

FIG. 9 is a flowchart of another example process in a network node 16 according to one or more embodiments of the present disclosure. One or more Blocks and/or functions performed by network node 16 may be performed by one or more elements of network node 16 such as by rate unit 32 in processing circuitry 68, processor 70, radio interface 62, etc. In one or more embodiments, the network node 16 is configured to communicate with a wireless device 22 where the wireless device 22 is configured with dual connectivity to a plurality of cell groups operating in a frequency range. In one or more embodiments, network node 16 such as via one or more of processing circuitry 68, processor 70, communication interface 60 and radio interface 62 is configured to receive (Block S138) capability information associated with the plurality of cell groups, as described herein. In one or more embodiments, network node 16 such as via one or more of processing circuitry 68, processor 70, communication interface 60 and radio interface 62 is configured to transmit (Block S140) at least one Radio Resource Control, RRC, parameter indicating a first data rate that is based on the capability information where the first data rate is configured for use by the wireless device with a first cell group of the plurality of cell groups, as described herein.

According to one or more embodiments, the at least one RRC parameter further indicates a second data rate that is based on the capability information where the second data rate is configured for use by the wireless device with a second cell group of the plurality of cell groups. According to one or more embodiments, the at least one RRC parameter includes at least one per-cell RRC parameter that is reused to indicate at least one per-component carrier parameter. According to one or more embodiments, the at least one per-component carrier parameter indicates at least one of: a maximum number of MIMO layers, and a numerology. According to one or more embodiments, the at least one RRC parameter indicates at least one of a modulation order configured per-component carrier, a scaling factor configured per- component carrier, and a resource block allocation configured per-component carrier.

According to one or more embodiments, the at least one RRC parameter indicates a first constraint per component-carrier for the first cell group and a second constraint per component-carrier for the second cell group of the plurality of cell groups. According to one or more embodiments, the first constraint is a first transport block size (TBS) size constraint per component-carrier for the first cell group and the second constraint is a second TBS size constraint per component-carrier for the second cell group. According to one or more embodiments, the first and second constraints are configured to be applied to at least one reference slot duration for at least one component-carrier.

According to one or more embodiments, the first cell group is a master cell group and the second cell group is a secondary cell group. According to one or more embodiments, the first data rate corresponds to a maximum data rate configured to be used by the wireless device with the first cell group. According to one or more embodiments, the processing circuitry is further configured to transmit control information for scheduling data transmission, the control information scheduling data transmission for the wireless device 22 that does not exceed the first data rate.

FIG. 10 is a flowchart of an example process in a wireless device 22 according to one or more embodiments of the present disclosure. One or more Blocks and/or functions performed by wireless device 22 may be performed by one or more elements of wireless device 22 such as by indication unit 34 in processing circuitry 84, processor 86, radio interface 82, etc. In one or more embodiments, the network node 16 is configured to communicate with a wireless device 22 where the wireless device 22 is configured with dual connectivity to a master cell group (MCG) operating on a first component carrier, CC, and secondary cell group (SCG) operating on a second CC that at least partially overlaps the first CC. In one or more embodiments, wireless device 22 such as via one or more of processing circuitry 84, processor 86 and radio interface 82 is configured to transmit (Block S142) radio resource control, RRC, signaling indicating wireless device capability, as described herein. In one or more embodiments, wireless device 22, such as via one or more of processing circuitry 84, processor 86 and radio interface 82 is configured to receive (Block S144) a scheduling according to a peak data rate that is based at least in part on the wireless device capability, as described herein.

According to one or more embodiments, the wireless device 22 is further configured to, and/or the radio interface 82 and/ processing circuitry 84 is further configured to receive an indication for the wireless device 22 to report the wireless device capability using RRC signaling, as described herein. According to one or more embodiments, the wireless device capability includes at least one of: maximum number of multiple-in multiple out, MIMO, layers configured for at least one of the first CC and second CC, modulation order for data rate calculation configured for at least one of the first CC and second CC, scaling factor for data rate calculation configured for at least one of the first CC and second CC, ^m is the numerology for at least one of the first CC and second CC, and resource block, RB, allocation for data rate calculation configured for at least one of the first CC and second CCA

FIG. 11 is a flowchart of an example process in a wireless device 22 according to one or more embodiments of the present disclosure. One or more Blocks and/or functions performed by wireless device 22 may be performed by one or more elements of wireless device 22 such as by indication unit 34 in processing circuitry 84, processor 86, radio interface 82, etc. In one or more embodiments, the network node 16 is configured to communicate with a wireless device 22 where the wireless device 22 is configured with dual connectivity to a plurality of cell groups operating in a frequency range. In one or more embodiments, wireless device 22 such as via one or more of processing circuitry 84, processor 86 and radio interface 82 is configured to transmit (Block S146) of capability information associated with the plurality cell groups, as described herein. In one or more embodiments, wireless device 22 such as via one or more of processing circuitry 84, processor 86 and radio interface 82 is configured to receive (Block S148) at least one Radio Resource Control, RRC, parameter indicating a first data rate that is based on the capability information where the first data rate is configured for use by the wireless device with a first cell group of the plurality of cell groups, as described herein.

According to one or more embodiments, the processing circuitry is further configured to: receive control information for scheduling data transmission in the first cell group where the scheduled data transmission does not exceed the first data rate, receive the data transmission according to the control information, and process the data transmission. According to one or more embodiments, the first data is based on a number of configured serving cells per frequency range. According to one or more embodiments, the at least one RRC parameter further indicates a second data rate that is based on capability information, the second data rate being configured for use by the wireless device with a second cell group of the plurality of cell groups.

According to one or more embodiments, the at least one RRC parameter includes at least one per-cell RRC parameter that is reused to indicate at least one per- component carrier parameter. According to one or more embodiments, the at least one per-component carrier RRC parameter indicates at least one of: a maximum number of MIMO layers, and a numerology. According to one or more embodiments, the at least one RRC parameter indicates at least one of: a modulation order configured per-component carrier, a scaling factor configured per-component carrier, and a resource block allocation configured per-component carrier. According to one or more embodiments, the at least one RRC parameter indicates a first constraint per component-carrier for the first cell group and a second constraint per component- carrier for the second cell group of the plurality of cell groups.

According to one or more embodiments, the first constraint is a first transport block size (TBS) size constraint per component-carrier for the first cell group and the second constraint is a second TBS size constraint per component-carrier for the second cell group. According to one or more embodiments, the processing circuitry is further configured to process at least one reference slot duration for at least one component-carrier that meets at least one of the first and second constraints.

According to one or more embodiments, the first data rate corresponds to a maximum data rate configured to be used by the wireless device with the first cell group.

Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for data rate handling.

Having generally described arrangements for data rate handling in dual connectivity schemes associated with a multiple cell groups, details for these arrangements, functions and processes are provided as follows, and which may be implemented by the network node 16, wireless device 22 and/or host computer 24.

Embodiments provide data rate handling in dual connectivity schemes. The Third Generation Partnership Project (3GPP) is defining technical specifications for New Radio (NR) (e.g., 5G). In 3GPP release 15 (3GPP Rel-15) NR, a wireless device 22 can be configured by network node 16 with up to four carrier bandwidth parts (BWPs) in the downlink, with a single downlink carrier bandwidth part being active at a given time. A wireless device 22 can be configured by network node 16 with up to four carrier bandwidth parts in the uplink, with a single uplink carrier bandwidth part being active at a given time. If a wireless device 22 is configured with a supplementary uplink, the wireless device 22 can additionally be configured with up to four carrier bandwidth parts in the supplementary uplink with a single supplementary uplink carrier bandwidth part being active at a given time.

For a carrier bandwidth part with a given numerology ^m' , a contiguous set of physical resource blocks (PRBs) are defined and numbered from 0 to

where ^; is the index of the carrier bandwidth part. A resource block (RB) is defined as 12 consecutive subcarriers in the frequency domain.

Numerologies

Multiple orthogonal frequency-division multiplexing (OFDM) numerologies, ^m , are supported in NR as shown by Table 1, where the subcarrier spacing, D/, and the cyclic prefix for a carrier bandwidth part are configured by different higher layer parameters for downlink (DL) and uplink (UL), respectively.

Table 1: Supported transmission numerologies.

Physical Channels

A downlink physical channel corresponds to a set of resource elements carrying information originating from higher layers, e.g., open systems interconnection (OSI) layers. The following are examples of downlink physical channels: - Physical Downlink Shared Channel, PDSCH; - Physical Broadcast Channel, PBCH;

Physical Downlink Control Channel, PDCCH.

PDSCH is a physical channel used for unicast downlink data transmission, but also for transmission of RAR (random access response), certain system information blocks, and paging information. PBCH carries the basic system information, that may be required by the wireless device to access the network/network node 16. PDCCH is used for transmitting downlink control information (DCI), mainly scheduling decisions, that may be required for reception of PDSCH, and for uplink scheduling grants enabling transmission on PUSCH.

An uplink physical channel corresponds to a set of resource elements carrying information originating from higher layers, i.e., higher open system interconnection (OSI) layers. The following are examples of uplink physical channels:

- Physical Uplink Shared Channel, PUSCH;

Physical Uplink Control Channel, PUCCH;

- Physical Random Access Channel, PRACH;

PUSCH is the uplink counterpart to the PDSCH. PUCCH is used by wireless devices 22 to transmit uplink control information, including HARQ acknowledgements, channel state information reports, etc. PRACH is used for random access preamble transmission.

An example peak rate formula

For NR, the approximate data rate for a given number of aggregated carriers in a band or band combination is computed as follows: data rate (in Mbps)

wherein

J is the number of aggregated component carriers in a band or band combination

Rmax = 948/1024

For the j-th CC, y ⁾ is the maximum number of supported layers given by higher layer parameter maxNumberMIMO-LayersPDSCH for downlink and maximum of higher layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH for uplink. o ~^mU) is the maximum supported modulation order given by higher layer parameter supportedModulationOrderDL for downlink and higher layer parameter supportedModulationOrderUL for uplink.

Hi)

^J is the scaling factor given by higher layer parameter scalingFactor and can take the values 1, 0.8, 0.75, and 0.4. m is the numerology (as defined in 3GPP standards such as 3GPP technical specification (TS) 38.211)

J m s is the average OFDM symbol duration in a subframe for to ³

T? = - numerology ^m , i.e. ^{14 2}“ . A normal cyclic prefix is assumed.

^{N r} '^i)'m i_s th maximum RB allocation in bandwidth

numerology ^m , as defined in 3GPP standards such as 3GPP TS 38.101-1 and/or 3GPP

TS 38.101-2, where

is the wireless device supported maximum bandwidth in the given band or band combination.

^0HiJ) is the overhead and takes the following values:

0.14, for frequency range FR1 for DL;

0.18, for frequency range FR2 for DL;

0.08, for frequency range FR1 for UL;

0.10, for frequency range FR2 for UL,

NOTE: Only one of the UL or SUL carriers (the one with the higher data rate) is counted for a cell operating SUL.

The approximate maximum data rate can be computed as the maximum of the approximate data rates computed using the above formula for each of the supported band or band combinations.

Related aspects

A data rate restriction based on data rate sharing is described below, and also in 3GPP standards such as 3GPP TS 38.214: Within a cell group, a wireless device may not be required to handle PDSCH(s) transmissions in slot S_j in serving cell -j, and for j = 0,1,2.. ./-/, slot 5,- overlapping with any given point in time, if the following condition is not satisfied at that point in time:

where,

J is the number of configured serving cells belonging to a frequency range for the j-th serving cell, is the number of TB(s) transmitted in slot Sj.

T_siof ^l(j) =10 ’/2-^/"^/y, where p(j) is the numerology for PDSCH(s) in slot S_j of the j- th serving cell. for the

A is the number of bits in the transport block as defined in 3GPP standards such as in 3GPP TS 38.212 Subclause 7.2.1;

C is the total number of code blocks for the transport block defined in 3GPP standards such as in 3GPP 38.212 Subclause 5.2.2;

C is the number of scheduled code blocks for the transport block as defined in 3 GPP standards such as in 3 GPP TS 38.212 Subclause 5.4.2.1;

DataRate [Mbps] is computed as the maximum data rate summed over all the carriers in the frequency range for any signaled band combination and feature set consistent with the configured servings cells, where the data rate value is given by the formula defined in 3GPP standards such as 3GPP TS 38.306 Subclause 4.1.2, including the scaling factor f(i).

For a j- th serving cell, if higher layer parameter processingType2Enabled of PDSCH-ServingCellConfig is configured for the serving cell and set to enable, or if at least one IMCS > W for a PDSCH, where W= 28 for MCS tables, and W = 27 for MCS table, the wireless device 22 may not be required to handle PDSCH transmissions, if the following condition is not satisfied: where

L is the number of symbols assigned to the PDSCH

M is the number of TB(s) in the PDSCH numerology of the PDSCH

C is the total number of code blocks for the transport block defined in 3GPP standards such as in 3GPP TS 38.212 Subclause 5.2.2;

DataRateCC [Mbps] is computed as the maximum data rate for a carrier in the frequency band of the serving cell for any signaled band combination and feature set consistent with the serving cell, where the data rate value is given by the formula in 3GPP standards such as in 3GPP TS 38.306 Subclause 4.1.2, including the scaling factor f(i).

Details of one or more embodiments

In 3GPP Rel-15, the data rate related TBS restriction is applied on a per-FR per-CG basis. Thus, a wireless device 22 configured such as by network node 16, e.g., such as via one or more of processing circuitry 68, processor 70, radio interface 62, rate unit 32, etc., with one cell group and with FR1+FR2 CA may have a per-FRl cap and a per-FR2 cap. Similarly, a wireless device 22 configured by network node 16 (such as via one or more of processing circuitry 68, processor 70, radio interface 62, rate unit 32, etc.), with two cell groups with FR1 carrier in MCG, and FR2 carriers in SCG may have a per-FRl cap for MCG, and a per-FR2 cap for SCG. The caps or limits are determined based at least in part on the data rate value calculated from the data rate formula in 3GPP standards such as in 3GPP TS 38.306 using the reported capability information that may include feature set(s) and band combination signaling as may be described in 3GPP standards such as in 3GPP TS 38.214. The band combination information may include frequency range information associated with the cell groups. The capability information from the wireless device 22 may be associated with multiple cell groups such as with MCG and SCG. A per-CC cap is applied for PDSCH/PUSCH capability#2 processing time or implicit MCS based retransmissions.

In 3GPP Rel-15, the data rate partitioning (or determination) across cells groups and across frequency range is based at least in part on the feature sets consistent with the capabilities reported by the wireless device 22.

In Rel-16 NR-DC, two cell groups may contain cells belonging to the same frequency range. Consider the following case for a wireless device 22 configured with an MCG and SCG

- MCG in FR1 and in FR2

SCG in FR1 only

For FR1, since both MCG and SCG have the carriers in FR1, the data rate sharing principle from 3GPP Rel-15 may not be directly applicable since flexible data rate sharing across CGs might not be feasible as the wireless device hardware 80 resource sharing between MCG and SCG may be split semi-statically. Therefore, another way of indicating the data rate constraint may be needed for this case.

For FR2 however, since only MCG has carriers in FR2, explicit partitioning is not required, and the 3GPP Rel-15 principle of per-FR-per-CG can be applied for MCG FR2 carriers. One option is to allow an explicit higher layer configuration of maximum TBS bits within a slot for cells belonging to a frequency range within a cell group. Another option is to introduce a one or more additional RRC parameters (i.e., that indicate wireless device capability, for example) such that network node 16 can explicitly indicate such as via one or more of processing circuitry 68, processor 70, radio interface 62, rate unit 32, etc., the data rate to utilize through RRC configuration in case two cell groups are operating in the same frequency range. The data rate expression in 3GPP standards such as 3GPP TS 38.306 may utilize the following parameters: Parameter 1. ^Layers is the maximum number of supported layers given by higher layer parameter maxNumberMIMO-LayersPDSCH for downlink and maximum of higher layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH for uplink. Parameter 2. o^U) is the maximum supported modulation order given by higher layer parameter supportedModulationOrderDL for downlink and higher layer parameter supportedModulationOrderUL for uplink.

Hi)

Parameter 3. is the scaling factor given by higher layer parameter scalingFactor and can take the values 1, 0.8, 0.75, and 0.4. Parameter 4. ^m is the numerology (as defined in 3GPP standards such as 3GPP TS 38.211)

J m

Parameter 5. ^s is the average OFDM symbol duration in a subframe to ³

T? = - for numerology ^m , i.e. ¹⁴ 2 " Note that normal cyclic prefix is assumed.

Parameter 6.

is the maximum RB allocation in bandwidth BW^(j) _with numerology ^m , as defined in 3GPP standards such as 3GPP TS 38.101-1 and/or 3GPP TS 38.101-2, where

If the wireless device 22 can be informed and/or configured such as via one or more of processing circuitry 84, processor 86, radio interface 82, indication unit 34, etc. to use RRC parameters instead of the corresponding parameters 1-6 from the feature set, the formula can be reused. Form the list of parameters 1-6, the corresponding parameters that are not readily available in RRC include the following: scaling factor f(i), parameter 3;

“modulation order for data rate calculation” Qm(j) , parameter 2. Note, in the wireless device feature set, this parameter is separate from the actual modulation order that a wireless device supports, i.e. effectively another scaling factor.

The parameters (MIMO layers, numerology, etc.) can readily reuse the corresponding RRC parameters from 3 GPP standards such as 3 GPP Rel-15 that are configured on per-cell (e.g. MIMO layers) or available in BWP configuration (RB allocation, numerology, etc.). New RRC parameters may be beneficial. While the number of PRBs is also available from the BWP configuration, a separate parameter that is used solely for data rate calculation may be better as the network node 16 can indicate data rate separately (since it may be dependent on multiple parameters feature set) from PRBs configured for a BWP. For example, if wireless device 22 supports 2 layers, 100 PRBs, with f = 0.4 and Qm’ = 6, then for a BWP with 80 PRBs, the network node 16 can configure the same of parameters and achieve the same data rate as the BWP with 100 PRBs. The same methodology can apply for the MIMO layers as well, but, in some cases, the granularity in MIMO layers may be enough.

Example 1 (parameter signaling):

For NR-DC operation. MCG and SCG operating with CCs in a same FR, for serving cells in the FR, the following new RRC parameters are introduced for each serving cell:

Q_m ’: Modulation order for data rate calculation;

- Same value range as ModulationOrder

/’: Scaling factor for data rate calculation;

- Same value range as scalingF actor ft ^pm ’ ; RB allocation for data rate calculation;

- Value range may be from 1 to 275

Example 2 (usage of the signaled parameters):

For NR-DC operation, with MCG and SCG operating with CCs in a same FR, for each cell group and the FR, DataRate is calculated as follows:

- DataRate [Mbps] is computed such as via one or more of processing circuitry 68, processor 70, radio interface 62, rate unit 32, etc., as the data rate summed over all the configured CCs in the frequency range in the cell group, where the data rate value is given by the formula described in 3GPP standards such as in 3GPP TS 38.306 Subclause and applying the following parameters for the active BWP:

- “Maximum number of MIMO layers configured for the CC” instead of ^r - “Modulation order for data rate calculation configured for the

CC” instead

- “Scaling factor for data rate calculation configured for the

Hi)

CC” instead of ^J

- ^m is the numerology for the CC(as defined in 3GPP standards such as 3GPP TS 38.211)

- “RB allocation for data rate calculation configured for the CC” instead

- DataRateCC following the same principle as DataRate but applied only in one CC.

A wireless device 22 can be configured by network node 16 such as via one or more of processing circuitry 68, processor 70, radio interface 62, rate unit 32, etc., with NR-DC operation with a first cell group and a second cell group. The wireless device 22 can be configured by network node 16 )such as via one or more of processing circuitry 68, processor 70, radio interface 62, rate unit 32, etc.), with at least one serving cell (CCl)in a frequency range (FRx) in the first cell group, and at least a second serving cell (CC2) in the frequency range (FRx) in the second cell group. The wireless device 22 such as via one or more of processing circuitry 84, processor 86, radio interface 82, indication unit 34, etc. acquires a first set of parameters from higher layer signaling where the first set of parameters are associated with serving cell CC1 for a data rate calculation for a first cell group, and acquires a second set of parameters from higher layer signaling where the second set of parameters are associated with serving cell CC2 for a data rate calculation for a second cell group. The wireless device 22, such as for example via one or more of processing circuitry 84, processor 86, radio interface 82, indication unit 34, etc. determines a TB size constraint for operation on CC1 based at least in part on the first set of parameters. The wireless device 22 such as for example via one or more of processing circuitry 84, processor 86, radio interface 82, indication unit 34, etc. determines a TB size constraint for operation on CC2 based at least in part on the second set of parameters.

The set of parameters can include one or more of the following: - Modulation order for data rate calculation

Scaling factor for data rate calculation

- RB allocation for data rate calculation

The modulation order for data rate calculation can be distinct from the maximum modulation order configured for the data reception/transmission. The RB allocation for data rate calculation can be distinct from the maximum number of resources blocks configured for the data reception/transmission.

The set of parameters can include a grouped scaling factor that may reflect the multiple parameters from the feature set such as modulation order for data rate calculate and scaling factor for data rate calculation.

The wireless device 22 can be configured by network node 16 such as via one or more of processing circuitry 68, processor 70, radio interface 62, rate unit 32, etc., with additional serving cells in FRx in the first cell group, and acquire a plurality of sets of parameters from higher layer signaling for additional serving cell in FRx for a data rate calculation for the first cell group, and determine a TB size constraint for operation on all serving cells in FRx in the first cell group.

The data rate calculation may be performed across all serving cells in FRx in the first cell group.

The wireless device 22 can be configured by network node 16 (such as for example via one or more of processing circuitry 68, processor 70, radio interface 62, rate unit 32, etc.), with additional serving cells in FRx in the second cell group, and acquire a plurality of sets of parameters from higher layer signaling for an additional serving cell in FRx for a data rate calculation for the second cell group, and determine a TB size constraint for operation on all serving cells in FRx in the second cell group.

The data rate calculation may be performed across all serving cells in FRx in the second cell group.

In one or more embodiments, FR1 refers to frequency range 1 or below 6GHz, and FR2 refers to frequency range 2 or mmWave frequencies.

The constraint can also be referred to as a condition and can be checked for a reference slot duration. In one or more embodiments, the conditions can be satisfied for all reference slot durations (among the configured CCs). In one or more embodiments, the conditions can be satisfied for a reference slot duration, e.g., for FR1, 0.5 ms, and/or for FR1/FR2, the slot duration corresponding to the SCS associated with the data channel (for PDSCH, SCS is used for downlink data channel, and for PUSCH, SCS is used for the uplink data channel). The reference slot duration may be the shortest slot duration across all configured component carriers.

In one or more embodiments, the conditions can be satisfied for a subset of reference slot duration, e.g., for FR1, 1 and 0.5 ms, and/or for FR1/FR2, the slot duration may corresponds to the SCS associated with the data channel (for PDSCH, SCS is used for downlink data channel, and for PUSCH, SCS is used for the uplink data channel).

In one or more embodiments, the constraint can be based on a sum (TBS / reference duration) across all serving cells in FRx in a CG or over one serving cell in FRx in a CG.

In dual connectivity, the conditions can be applied separately for each cell group and FR.

In one or more embodiments, the respective conditions are applied for carriers within a band in CA case, e.g., the data rate may be calculated and applied on carriers per-band.

The set of parameters for each carrier may be determined from the feature set signaling associated with a cell group.

- Example: NR-NR DC may have primary cell group corresponding to carriers in FR1, and a secondary cell group corresponding to carriers in FR2. A band/band combination for FR1 and FR2 can indicate support of NR-NR DC with MCG on FR1 and SCG on FR2 (or vice-versa).

In one or more embodiments, the data rate is a maximum data rate based at least in part on the band/band combination signaling and feature set information for one cell group from the capability signaling associated with multiple cell groups. In one or more embodiments, the MCG informs to SCG the allowable feature set partition that the SCG can use, and the SCG applies the corresponding feature set information in the data rate calculation to identify the data rate schedulable for the wireless device 22 within SCG. In one or more embodiments, the sum TBS is calculated based on those code block or blocks whose transmission ends within the reference slot duration. In one example, the decoder processing (such as decoding operation) can begin only after the entire transmission of code block or blocks is received. Therefore, in some embodiments, control information such as physical layer control information includes scheduling information (e.g., MCS, resource allocation, etc.) where the wireless device 22 uses the control information to determine whether to process/decode the data that is received according to the control information scheduling. For example, the wireless device 22 verifies whether the MCS and resource allocation in the control information indicates a TB that exceeds the determined data rate. Control information can change every slot or every milli second.

It is noted that the above approaches can be generalized to any combination of transmissions durations on the carriers.

If the condition is not satisfied (i.e., is exceeded), there are some different options for wireless device 22 behavior, including for example:

1. The wireless device 22 such as for example via one or more of processing circuitry 84, processor 86, radio interface 82, indication unit 34, etc. may consider such a scheduling as an error case, where the wireless device 22 behavior is unspecified,

2. The wireless device 22 such as for example via one or more of processing circuitry 84, processor 86, radio interface 82, indication unit 34, etc. may skip decoding the transport block(s); if the wireless device 22 skips decoding then it can indicate a NACK to the upper layers the wireless device 22 such as for example via one or more of processing circuitry 84, processor 86, radio interface 82, indication unit 34, etc. may or may not be able to store and soft combine the received information

3. The wireless device 22 such as for example via one or more of processing circuitry 84, processor 86, radio interface 82, indication unit 34, etc. may partially process the transport block(s), e.g., provide ACK for the TBs or CBGs that were processed and NACK for the unfinished blocks;

4. For uplink, the wireless device 22 such as for example via one or more of processing circuitry 84, processor 86, radio interface 82, indication unit 34, etc. may not be able transmit since its transmission capability is exceeded, and hence may drop the transmission. In one or more embodiments, if the different transmissions are scheduled by different PDCCHs occurring at different time instances, the wireless device 22 may continue to transmit any ongoing transmissions, while dropping any transmissions that may cause wireless device 22 transmission capability to be exceeded.

An example is as follows:

If the wireless device 22 is configured by network node 16 with MCG and SCG with at least one carrier configured in a frequency range FRx in MCG and at least one carrier configured in the frequency range FRx in SCG, then within a cell group, a wireless device 22 is not required to handle PDSCH(s) transmissions in slot S_j in serving cell -j, and for j = 0,1,2.. ./-/, slot s, overlapping with any given point in time, if the following condition is not satisfied at that point in time:

where,

Jis the number of configured serving cells belonging to FRx in the cell group for the j-th serving cell, is the number of TB(s) transmitted in slot s,.

the numerology for PDSCH(s) in slot S_j of the j- th serving cell.

A for the m- th TB, V_{j m} = C' c

A is the number of bits in the transport block as defined for example in 3GPP standards such as in 3GPP TS 38.212 Subclause 7.2.1

C is the total number of code blocks for the transport block defined in for example 3GPP standards such as in 3GPP TS 38.212 Subclause 5.2.2.

C' is the number of scheduled code blocks for the transport block as defined for example in 3 GPP standards such as in 3 GPP TS 38.212 Subclause 5.4.2.1. ^{y )} is the maximum number of layers; v(j) is modulation order for data rate calculation f⁽j)

^J is scaling factor for data rate calculation;

^max= 948/1024; ft

^PRB is RB allocation for data rate calculation;

overhead as given in 3GPP standards such as in 3GPP TS 38.306 subclause 4.1.2.

Note : Also, additionally, for a wireless device 22 configured by network node 16 with capability#2, a potential single CC upper limit is applied using J = 1. Note : In one or more embodiments, the data rate sharing can be generalized to sharing across both FRs within a cell group.

While the concepts herein are described primarily from an uplink or downlink perspective, the same concepts are applicable for sidelink, integrated access backhaul, and other forms of communication links in a cellular communication system.

Therefore, as described herein the disclosure advantageously provides new RRC parameters to enable data rate handling in the case of NR-DC operation where MCG and SCG operate in same frequency range for a wireless device.

Some Examples

Example A1. A network node 16 configured to communicate with a wireless device 22 (WD 22) where the wireless device 22 is configured with dual connectivity to a master cell group operating on a first component carrier, CC, and secondary cell group operating on a second CC that at least partially overlaps the first CC, the network node 16 configured to, and/or comprising a radio interface and/or comprising processing circuitry 68 configured to: receive radio resource control, RRC, signaling indicating wireless device capability; and schedule the wireless device 22 according to a peak data rate that is based at least in part on the wireless device capability. Example A2. The network node 16 of Example Al, wherein the network node 16 is further configured to, and/or the radio interface 62 and/ processing circuitry 68 is further configured to cause the wireless device 22 to report the wireless device capability using RRC signaling.

Example A3. The network node 16 of Example Al, wherein the wireless device capability includes at least one of: maximum number of multiple-in multiple out, MIMO, layers configured for at least one of the first CC and second CC; modulation order for data rate calculation configured for at least one of the first CC and second CC; scaling factor for data rate calculation configured for at least one of the first CC and second CC; m is the numerology for at least one of the first CC and second CC; and resource block, RB, allocation for data rate calculation configured for at least one of the first CC and second CC.

Example Bl. A method implemented in a network node 16 that is configured to communicate with a wireless device 22 that is configured with dual connectivity to a master cell group operating on a first component carrier, CC, and secondary cell group operating on a second CC that at least partially overlaps the first CC, the method comprising: receiving radio resource control, RRC, signaling indicating wireless device capability; and scheduling the wireless device 22 according to a peak data rate that is based at least in part on the wireless device capability

Example B2. The method of Example Bl, further comprising causing the wireless device 22 to report the wireless device capability using RRC signaling.

Example B3. The method of Example B 1 , wherein the wireless device capability includes at least one of: maximum number of multiple-in multiple out, MIMO, layers configured for at least one of the first CC and second CC; modulation order for data rate calculation configured for at least one of the first CC and second CC; scaling factor for data rate calculation configured for at least one of the first CC and second CC; m is the numerology for at least one of the first CC and second CC; and resource block, RB, allocation for data rate calculation configured for at least one of the first CC and second CC.

Example Cl . A wireless device 22 (WD 22) configured to communicate with a network node 16 where the wireless device 22 is configured with dual connectivity to a master cell group operating on a first component carrier, CC, and secondary cell group operating on a second CC that at least partially overlaps the first CC, the WD configured to, and/or comprising a radio interface 62 and/or processing circuitry 68 configured to: transmit radio resource control, RRC, signaling indicating wireless device capability; and receive a scheduling according to a peak data rate that is based at least in part on the wireless device capability.

Example C2. The WD 22 of Example Cl, wherein the network node 16 is further configured to, and/or the radio interface 62 and/ processing circuitry 68 is further configured to receive an indication for the wireless device 22 to report the wireless device capability using RRC signaling.

Example C3. The WD 22 of Example Cl, wherein the wireless device capability includes at least one of: maximum number of multiple-in multiple out, MIMO, layers configured for at least one of the first CC and second CC; modulation order for data rate calculation configured for at least one of the first CC and second CC; scaling factor for data rate calculation configured for at least one of the first CC and second CC; m is the numerology for at least one of the first CC and second CC; and resource block, RB, allocation for data rate calculation configured for at least one of the first CC and second CC.

Example DT A method implemented in a wireless device 22 (WD 22) that is configured to communicate with a network node 16 where the wireless device 22 is configured with dual connectivity to a master cell group operating on a first component carrier, CC, and secondary cell group operating on a second CC that at least partially overlaps the first CC, the method comprising: transmitting radio resource control, RRC, signaling indicating wireless device capability; and receiving a scheduling according to a peak data rate that is based at least in part on the wireless device capability.

Example D2. The method of Example Dl, further comprising receiving an indication for the wireless device 22 to report the wireless device capability using RRC signaling.

Example D3. The method of Example Dl, wherein the wireless device capability includes at least one of: maximum number of multiple-in multiple out, MIMO, layers configured for at least one of the first CC and second CC; modulation order for data rate calculation configured for at least one of the first CC and second CC; scaling factor for data rate calculation configured for at least one of the first CC and second CC; m is the numerology for at least one of the first CC and second CC; and resource block, RB, allocation for data rate calculation configured for at least one of the first CC and second CC.

As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

Some embodiments are described herein with reference to flowchart illustrations and/or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

It is to be understood that the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

Abbreviations that may be used in the preceding description include:

Abbreviation Explanation

CC Component carrier eMBB enhanced Mobile BroadBand

LTE Long Term Evolution

NR Next Radio

PDCCH Physical Downlink Control Channel

PDSCH Physical Downlink Shared Channel

PUSCH Physical Uplink Shared Channel scs Subcarrier spacing TBS Transport block size

UE User Equipment

It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

What is claimed is:

1. A network node (16) configured to communicate with a wireless device (22), the wireless device (22) being configured with dual connectivity to a plurality of cell groups operating in a frequency range, the network node (16) comprising: processing circuitry (68) configured to: receive capability information associated with the plurality of cell groups; and transmit at least one Radio Resource Control, RRC, parameter indicating a first data rate that is based on the capability information, the first data rate being configured for use by the wireless device (22) with a first cell group of the plurality of cell groups.

2. The network node (16) of Claim 1, wherein the at least one RRC parameter further indicates a second data rate that is based on the capability information, the second data rate being configured for use by the wireless device (22) with a second cell group of the plurality of cell groups.

3. The network node (16) of any one of Claims 1-2, wherein the at least one RRC parameter includes at least one per-cell RRC parameter that is reused to indicate at least one per-component carrier parameter.

4. The network node (16) of Claim 3, wherein the at least one per- component carrier parameter indicates at least one of: a maximum number of MIMO layers; and a numerology.

5. The network node of any one of Claims 1-4, wherein the at least one RRC parameter indicates at least one of: a modulation order configured per-component carrier; a scaling factor configured per-component carrier; and a resource block allocation configured per-component carrier.

6. The network node (16) of any one of Claims 2-5, wherein the at least one RRC parameter indicates a first constraint per component-carrier for the first cell group and a second constraint per component-carrier for the second cell group of the plurality of cell groups.

7. The network node (16) of Claim 6, wherein the first constraint is a first transport block size, TBS, size constraint per component-carrier for the first cell group and the second constraint is a second TBS size constraint per component-carrier for the second cell group.

8. The network node (16) of any one of Claim 6-7, wherein the first and second constraints are configured to be applied to at least one reference slot duration for at least one component-carrier.

9. The network node (16) of any one of Claims 6-8, wherein the first cell group is a master cell group and the second cell group is a secondary cell group.

10. The network node (16) of any one of Claims 1-9, wherein the first data rate corresponds to a maximum data rate configured to be used by the wireless device with the first cell group.

11. The network node (16) of any one of Claims 1-10, wherein the processing circuitry (68) is further configured to transmit control information for scheduling data transmission, the control information scheduling data transmission for the wireless device (22) that does not exceed the first data rate.

12. A wireless device (22) configured to communicate with a network node (16), the wireless device (22) being configured to support dual connectivity to a plurality of cell groups operating in a frequency range, the wireless device (22) comprising: processing circuitry (68) configured to: transmit capability information associated with the plurality cell groups; and receive at least one Radio Resource Control, RRC, parameter indicating a first data rate that is based on the capability information, the first data rate being configured for use by the wireless device (22) with a first cell group of the plurality of cell groups.

13. The wireless device (22) of Claim 12, wherein the processing circuitry (84) is further configured to: receive control information for scheduling data transmission in the first cell group, the scheduled data transmission does not exceed the first date rate; receive the data transmission according to the control information; and process the data transmission .

14. The wireless device (22) of Claim 13, wherein the first data is based on a number of configured serving cells per frequency range.

15. The wireless device (22) of any one of Claims 12-14, wherein the at least one RRC parameter further indicates a second data rate that is based on capability information, the second data rate being configured for use by the wireless device (22) with a second cell group of the plurality of cell groups.

16. The wireless device (22) of any one of Claims 12-15, wherein the at least one RRC parameter includes at least one per-cell RRC parameter that is reused to indicate at least one per-component carrier parameter.

17. The wireless device (22) of Claim 16, wherein the at least one per- component carrier RRC parameter indicates at least one of: a maximum number of MIMO layers; and a numerology.

18. The wireless device (22) of any one of Claims 12-17, wherein the at least one RRC parameter indicates at least one of: a modulation order configured per-component carrier; a scaling factor configured per-component carrier; and a resource block allocation configured per-component carrier.

19. The wireless device (22) of any one of Claims 15-18, wherein the at least one RRC parameter indicates a first constraint per component-carrier for the first cell group and a second constraint per component-carrier for the second cell group of the plurality of cell groups.

20. The wireless device (22) of Claim 19, wherein the first constraint is a first transport block size, TBS, size constraint per component-carrier for the first cell group and the second constraint is a second TBS size constraint per component-carrier for the second cell group.

21. The wireless device (22) of any one of Claims 19-20, wherein the processing circuitry (84) is further configured to process at least one reference slot duration for at least one component-carrier that meets at least one of the first and second constraints.

22. The wireless device (22) of any one of Claims 12-21, wherein the first data rate corresponds to a maximum data rate configured to be used by the wireless device (22) with the first cell group.

23. A method implemented by a network node (16) that is configured to communicate with a wireless device (22), the wireless device (22) being configured with dual connectivity to a plurality of cell groups operating in a frequency range, the method comprising: receiving (SI 38) capability information associated with the plurality of cell groups; and transmitting (S140) at least one Radio Resource Control, RRC, parameter indicating a first data rate that is based on the capability information, the first data rate being configured for use by the wireless device (22) with a first cell group of the plurality of cell groups.

24. The method of Claim 23, wherein the at least one RRC parameter further indicates a second data rate that is based on the capability information, the second data rate being configured for use by the wireless device (22) with a second cell group of the plurality of cell groups.

25. The method of any one of Claims 23-24, wherein the at least one RRC parameter includes at least one per-cell RRC parameter that is reused to indicate at least one per-component carrier parameter.

26. The method of Claim 25, wherein the at least one per-component carrier parameter indicates at least one of: a maximum number of MIMO layers; and a numerology.

27. The method of any one of Claims 23-26, wherein the at least one RRC parameter indicates at least one of: a modulation order configured per-component carrier; a scaling factor configured per-component carrier; and a resource block allocation configured per-component carrier.

28. The method of any one of Claims 24-27, wherein the at least one RRC parameter indicates a first constraint per component-carrier for the first cell group and a second constraint per component-carrier for the second cell group of the plurality of cell groups.

29. The method of Claim 28, wherein the first constraint is a first transport block size, TBS, size constraint per component-carrier for the first cell group and the second constraint is a second TBS size constraint per component-carrier for the second cell group.

30. The method of any one of Claim 28-29, wherein the first and second constraints are configured to be applied to at least one reference slot duration for at least one component-carrier.

31. The method of any one of Claims 28-30, wherein the first cell group is a master cell group and the second cell group is a secondary cell group.

32. The method of any one of Claims 23-31, wherein the first data rate corresponds to a maximum data rate configured to be used by the wireless device (22) with the first cell group.

33. The method of any one of Claims 23-32, further comprising transmitting control information for scheduling data transmission, the control information scheduling data transmission for the wireless device (22) that does not exceed the first data rate.

34. A method implemented by a wireless device (22) that is configured to communicate with a network node (16), the wireless device (22) being configured to support dual connectivity to a plurality of cell groups operating in a frequency range, the method comprising: transmitting (SI 46) capability information associated with the plurality cell groups; and receiving (SI 48) at least one Radio Resource Control, RRC, parameter indicating a first data rate that is based on the capability information, the first data rate being configured for use by the wireless device (22) with a first cell group of the plurality of cell groups.

35. The method of Claim 34, further comprising: receiving control information for scheduling data transmission in the first cell group, the scheduled data transmission does not exceed the first data rate; receiving the data transmission according to the control information; and processing the data transmission.

36. The method of Claim 35, wherein the first data is based on a number of configured serving cells per frequency range.

37. The method of any one of Claims 34-36, wherein the at least one RRC parameter further indicates a second data rate that is based on capability information, the second data rate being configured for use by the wireless device with a second cell group of the plurality of cell groups.

38. The method of any one of Claims 34-37, wherein the at least one RRC parameter includes at least one per-cell RRC parameter that is reused to indicate at least one per-component carrier parameter.

39. The method of Claim 38, wherein the at least one per-component carrier RRC parameter indicates at least one of: a maximum number of MIMO layers; and a numerology.

40. The method of any one of Claims 34-39, wherein the at least one RRC parameter indicates at least one of: a modulation order configured per-component carrier; a scaling factor configured per-component carrier; and a resource block allocation configured per-component carrier.

41. The method of any one of Claims 37-40, wherein the at least one RRC parameter indicates a first constraint per component-carrier for the first cell group and a second constraint per component-carrier for the second cell group of the plurality of cell groups.

42. The method of Claim 41, wherein the first constraint is a first transport block size, TBS, size constraint per component-carrier for the first cell group and the second constraint is a second TBS size constraint per component-carrier for the second cell group.

43. The method of any one of Claims 41-42, further comprising processing at least one reference slot duration for at least one component-carrier that meets at least one of the first and second constraints.

44. The method of any one of Claims 34-43, wherein the first data rate corresponds to a maximum data rate configured to be used by the wireless device (22) with the first cell group.

45. A wireless device (22) configured to communicate with a network node (16), the wireless device (22) being configured with dual connectivity to a plurality of cell groups operating in a frequency range, the wireless device (22) comprising: processing circuitry (84) configured to: transmit capability information associated with a first cell group of the plurality of cell groups, the capability information including band combination signaling information and feature set information; receive at least one Radio Resource Control, RRC, parameter indicating a first maximum data rate that is based on the capability information, the first maximum data rate being configured for use by the wireless device (22) with a first cell group of the plurality of cell groups; and receive control information for scheduling data transmission in the first cell group, the scheduled data transmission does not exceed the first maximum data rate.