Patent Description:
The disclosed subject matter relates generally to telecommunications. Certain embodiments relate more particularly to concepts such as 3GPP New Radio (NR), Long Term Evolution (LTE), retransmission, hybrid automatic repeat request (HARQ), transport block size (TBS) and transmission time interval (TTI).

In cellular wireless systems, such as those using Long Term Evolution (LTE) and New Radio (NR) standards, resources for UL transmissions are normally scheduled by a network node (e.g., eNB or gNB). This can be done dynamically, for instance by an eNB scheduling an UL transmission per transmission time interval (TTI). Alternatively, this can be done using a semi persistent scheduling (SPS) framework, so that multiple TTIs are granted at the same time prior to a data transmission.

Configuration of SPS typically includes periodicity of the grant, allocation and modulation and coding scheme (MCS) in subsequent SPS occasions. Other types of grant-free transmissions can also be envisioned where some or all resources are granted semi-statically to a user equipment (UE), so that the UE can start transmitting over resources whenever needed without a need to ask for a dynamic grant.

Further background information can be found in <CIT> <NPL>, European patent application <CIT>, Canadian patent application <CIT>, and United States patent application <CIT>.

In certain embodiments of the disclosed subject matter, techniques and technologies are provided for configuring and indicating a TBS to a UE. In some embodiments, for example, a scaling factor for a TBS is dynamically or semi-statically configured by a network. The configuration can be specified for different services, TTI lengths, directions, transmission modes, and downlink control information (DCI) types, for example. The UE applies the scaling factor to compute the TBS for a transmission based on the MCS and the default TBS table or function. MCS subsets can be semi-statically configured for a certain service or DCI type. For UEs running multiple services with different configurations the configuration to used may be indicated by a bit field in the DCI.

Certain embodiments are presented in recognition of shortcomings associated with conventional techniques and technologies, such as the following examples. The TBS needs to be adapted to the number of OFDM symbols in a transmission, the TTI length. If not, the code rate with be higher than intended. Also, for certain services, the code rate should be lower than the nominal to improve transmission robustness.

Certain embodiments may provide potential benefits compared to conventional techniques and technologies, such as the following examples. Some methods or apparatuses provide a unified solution for calculating TBS in scenarios of varying TTI length, and for services requiring different code rates.

In certain embodiments of the disclosed subject matter, a method of operating a wireless communication device is provided as defined in claim <NUM> of the appended claims.

In certain related embodiments, applying the scaling factor to the base value to determine the transport block size comprises multiplying the base value by the scaling factor to produce a scaled value, and rounding the scaled value.

In certain related embodiments, the scaling factor is configured according to at least one of a transmission time interval, a service type associated with the transmission, a type of DCI, a transmission direction, a transmission mode, a user equipment (UE) class, and a block error rate (BLER) target.

In some embodiments of the disclosed subject matter, a wireless communication device is provided as defined in claim <NUM> of the appended claims.

In certain related embodiments, the scaling factor is configured according to at least one of a transmission time interval, a service type associated with the transmission, a type of downlink control information (DCI), a transmission direction, a transmission mode, a user equipment (UE) class, and a block error rate (BLER) target.

In some embodiments of the disclosed subject matter, a method of operating a radio access node is provided as defined in claim <NUM> of the appended claims.

In certain related embodiments, the transport block size is determined by multiplying the base value by the scaling factor to produce a scaled value, and rounding the scaled value.

In certain related embodiments, the scaling factor is determined according to at least one of a transmission time interval, a service type associated with the transmission, a type of downlink control information (DCI), a transmission direction, a transmission mode, a user equipment (UE) class, and a block error rate (BLER) target.

In some embodiments of the disclosed subject matter, a radio access node is provided as defined in claim <NUM> of the appended claims.

The drawings illustrate selected embodiments of the disclosed subject matter. In the drawings, like reference labels denote like features.

For example, certain details of the described embodiments may be modified, omitted, or expanded upon without departing from the scope of the disclosed subject matter.

Certain embodiments provide techniques and technologies to scale TBS using semi-statically configured factors, enabling a desired code rate for transmissions with different TTI length for different services. Certain embodiments also define subsets of the MCS list for computing the TBS.

The described embodiments may be implemented in any appropriate type of communication system supporting any suitable communication standards and using any suitable components. As one example, certain embodiments may be implemented in a communication system such as that illustrated in <FIG>. Although certain embodiments are described with respect to 3GPP systems (e.g., LTE or NR) and related terminology, the disclosed concepts are not limited to 3GPP system. Additionally, although reference may be made to the term "cell", the described concepts may also apply in other contexts, such as beams used in Fifth Generation (<NUM>) systems, for instance.

Referring to <FIG>, a communication system <NUM> comprises a plurality of wireless communication devices <NUM> (e.g., UEs, machine type communication [MTC] / machine-to-machine [M2M] UEs) and a plurality of radio access nodes <NUM> (e.g., eNodeBs or other base stations). Communication system <NUM> is organized into cells <NUM>, which are connected to a core network <NUM> via corresponding radio access nodes <NUM>. Radio access nodes <NUM> are capable of communicating with wireless communication devices <NUM> along with any additional elements suitable to support communication between wireless communication devices or between a wireless communication device and another communication device (such as a landline telephone).

Although wireless communication devices <NUM> may represent communication devices that include any suitable combination of hardware and/or software, these wireless communication devices may, in certain embodiments, represent devices such as those illustrated in greater detail by <FIG>. Similarly, although the illustrated radio access node may represent network nodes that include any suitable combination of hardware and/or software, these nodes may, in particular embodiments, represent devices such those illustrated in greater detail by <FIG> and <FIG>.

Referring to <FIG>, a wireless communication device 200A comprises a processor <NUM> (e.g., Central Processing Units [CPUs], Application Specific Integrated Circuits [ASICs], Field Programmable Gate Arrays [FPGAs], and/or the like), a memory <NUM>, a transceiver <NUM>, and an antenna <NUM>. In certain embodiments, some or all of the functionality described as being provided by UEs, MTC or M2M devices, and/or any other types of wireless communication devices may be provided by the device processor executing instructions stored on a computer-readable medium, such as memory <NUM>. Alternative embodiments may include additional components beyond those shown in <FIG> that may be responsible for providing certain aspects of the device's functionality, including any of the functionality described herein.

Referring to <FIG>, a wireless communication device 200B comprises at least one module <NUM> configured to perform one or more corresponding functions. Examples of such functions include various method steps or combinations of method steps as described herein with reference to wireless communication device(s). In general, a module may comprise any suitable combination of software and/or hardware configured to perform the corresponding function. For instance, in some embodiments a module comprises software configured to perform a corresponding function when executed on an associated platform, such as that illustrated in <FIG>.

Referring to <FIG>, a radio access node 300A comprises a control system <NUM> that comprises a node processor <NUM> (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like), memory <NUM>, and a network interface <NUM>. In addition, radio access node 300A comprises at least one radio unit <NUM> comprising at least one transmitter <NUM> and at least one receiver <NUM> coupled to at least one antenna <NUM>. In some embodiments, radio unit <NUM> is external to control system <NUM> and connected to control system <NUM> via, e.g., a wired connection (e.g., an optical cable). However, in some other embodiments, radio unit <NUM> and potentially the antenna <NUM> are integrated together with control system <NUM>. Node processor <NUM> operates to provide at least one function <NUM> of radio access node 300A as described herein. In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory <NUM> and executed by node processor <NUM>.

In certain embodiments, some or all of the functionality described as being provided by a base station, a Node B, an eNodeB, gNodeB and/or any other type of network node may be provided by node processor <NUM> executing instructions stored on a computer-readable medium, such as memory <NUM> shown in <FIG>. Alternative embodiments of radio access node <NUM> may comprise additional components to provide additional functionality, such as the functionality described herein and/or related supporting functionality.

Referring to <FIG>, a radio access node 300B comprises at least one module <NUM> configured to perform one or more corresponding functions. Examples of such functions include various method steps or combinations of method steps as described herein with reference to radio access node(s). In general, a module may comprise any suitable combination of software and/or hardware configured to perform the corresponding function. For instance, in some embodiments a module comprises software configured to perform a corresponding function when executed on an associated platform, such as that illustrated in <FIG>.

<FIG> is a block diagram that illustrates a virtualized radio access node <NUM> according to an embodiment of the disclosed subject matter. The concepts described in relation to <FIG> may be similarly applied to other types of network nodes. As used herein, the term "virtualized radio access node" refers to an implementation of a radio access node in which at least a portion of the functionality of the radio access node is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)).

Referring to <FIG>, radio access node <NUM> comprises control system <NUM> as described in relation to <FIG>.

Control system <NUM> is connected to one or more processing nodes <NUM> coupled to or included as part of a network(s) <NUM> via network interface <NUM>. Each processing node <NUM> comprises one or more processors <NUM> (e.g., CPUs, ASICs, FPGAs, and/or the like), memory <NUM>, and a network interface <NUM>.

In this example, functions <NUM> of radio access node 300A described herein are implemented at the one or more processing nodes <NUM> or distributed across control system <NUM> and the one or more processing nodes <NUM> in any desired manner. In some embodiments, some or all of the functions <NUM> of radio access node 300A described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by processing node(s) <NUM>. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between processing node(s) <NUM> and control system <NUM> is used in order to carry out at least some of the desired functions <NUM>. As indicated by dotted lines, in some embodiments control system <NUM> may be omitted, in which case the radio unit(s) <NUM> communicate directly with the processing node(s) <NUM> via an appropriate network interface(s).

In some embodiments, a computer program comprises instructions which, when executed by at least one processor, causes at least one processor to carry out the functionality of a radio access node (e.g., radio access node <NUM> or 300A) or another node (e.g., processing node <NUM>) implementing one or more of the functions of the radio access node in a virtual environment according to any of the embodiments described herein.

The following description presents various concepts as "Aspects". The use of this terminology is merely for convenience and is not intended to be limiting or indicative of any hierarchy, separation, interaction etc. between the described concepts. In fact, concepts described in connection with different aspects may be combined in various ways as described below and/or as may be envisioned by those skilled in the art.

In some embodiments, a scaling factor Lambda is configured for a UE. The configuration can be done semi-statically over RRC, or dynamically over DCI, for instance. In one example, the UE would be configured during attachment to the network.

The UE applies the configured Lambda when computing a TBS value for a transmission, based on a nominal TBS0 such that TBS = TBS0*Lambda. In this context, the term "nominal" may refer to e.g. a base value or initial value to be used in a computation or determination in which other values are to be derived.

The value of Lambda may be determined based on any of several alternative factors. For instance:.

In some embodiments, Lambda is configured as two different parameters: Lambda = alpha*beta, where alpha is set per TTI length and direction, and beta is set per service type or BLER target. Both can be semi-statically configured for a UE. In addition, alpha or beta separately can be connected to DCI type such that the reception of a certain DCI means applying a factor alpha or beta, or both.

The "beta" part in above embodiments can be specified by CQI report, for example. In one example, the UE reports CQI containing a scaling factor beta which depends on its present channel condition.

The beta part can also be indicated dynamically in the DCI depending on service type or BLER target or both.

As one example, the network configures Lambda for a DCI for URLLC transmission of length <NUM> OFDM symbols to be <NUM>* <NUM>*<NUM>/N0, where N0 is a nominal value, effectively reducing the number of bits in the transmission to be adapted to the transmission length, and also reducing the code rate by half.

In some embodiments, Lambda is not directly configured, but computed as N/N0, where the value N is configured instead of Lambda, and N0 is a nominal value of REs per PRB. In an embodiment N0 is a function of TTI, e.g. such that N0(<NUM>) = <NUM>* <NUM> REs, and N0(<NUM>) = <NUM>* <NUM> REs per PRB.

Thus the UE can be configured with Lambda (TTI, Service, Direction, DCI, Transmission mode, UE class) or N (TTI, Service, Direction, DCI, Transmission mode, UE class), where not all parameters need to be used.

In certain embodiments, a UE receives a DCI for a transmission. Based on this, it computes a nominal TBS value, TBS0. The nominal value can be from a table or a formula. The UE also computes Lambda or N as described above, based on DCI input (DCI type, TTI length, direction, transmission mode, service type, UE class). The UE then computes the TBS = Lambda*TBS0. Alternatively, the UE calculates TBS = N*X, where X corresponds to TBS0/N0, that is the number of PRBs times the modulation times the code rate times the number of layers. Here, X can also be found in a table or computed from a formula.

In some embodiments, the computed TBS is corrected for CRC.

In some embodiments, the computed TBS is corrected for additional control overhead.

In some embodiments, the computed TBS is rounded off, rounded up, or rounded down to bytes (B).

In certain embodiments, the UE is configured with a mapping between a subset of MCS and the full MCS set. The mapping can be semi-statically configured over RRC for a certain DCI type, TTI length, direction, transmission mode, service type or UE class. The mapping can be a list of length(MCS subset) and contain the MCS indices in the full set. In one example the configuration can look like: {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>}. New numeration of MCSs in a subset can be applied based on index of MCS in the set. Before indexing the list of MCS should be sorted, e.g. in ascending order. This list of <NUM> MCS in the subset can then be indicated with fewer bits in the relevant DCI. Another way of MCS mapping configuration is signaling a bitmap on full MCS set, where each bit shows either MCS is used in subset or not and a bit position corresponds to MCS number in full MCS set, e.g. the same configuration as before can be signaled like {<NUM>.

In certain embodiments, a UE receives a DCI with a configured MCS subset. It then reads the MCS field and maps the index to the configured list in the subset to get the index corresponding to the full set. It then uses this full-set index to compute the TBS.

In certain embodiments, the UE can be configured with several "TBS/MCS configurations", which are sets of parameters, mentioned in connection with Aspects <NUM>-<NUM>. Each configured set should have an index. The UE receives a DCI comprising a bit field indicating a "TBS/MCS configuration" index. The indicated configuration is then used by the UE when determining the TBS/MCS. Aspect <NUM> enables the UE to run multiple services where data for each of the services (with different "TBS scaling") may be assigned using a common DCI format. In the simplest form, one bit is used to indicate scaling or no scaling applied to the TBS.

In some embodiments, the indication is instead associated to the address (RNTI) used to convey the DCI to the UE, such that the normal RNTI is not associated with TBS scaling, while a configured Scaling-RNTI is associated with scaling, and upon detection of a DCI sent to this address the UE applies the scaling.

<FIG> illustrate methods according to various embodiments of the disclosed subject matter. These methods may include e.g. certain concepts described in relation to Aspects <NUM>-<NUM>, respectively. Additionally, these methods may be variously performed by e.g. a network node and/or UE as described elsewhere herein. For instance, the described operations, functions, or steps may be performed by a combination of processing circuitry, memory, and/or transceiver circuitry as illustrated and/or described elsewhere herein. Moreover, in addition to the described operations, functions or steps, the methods may further comprise communication (e.g. transmitting and/or receiving information between a network node and a UE) and related operations (e.g., rate matching, modulation and coding, etc.) performed according to various information described below, such as a TBS produced by application of a scaling factor. For instance, in each method in which TBS is determined, scaled, adjusted, etc., the resulting TBS may be used for communication by a UE or network node. Such use may include, e.g., performing physical channel processing using the determined TBS.

Referring to <FIG>, a method <NUM> comprises determining a scaling factor for a TBS (S505), and applying the scaling factor to the TBS (S510). Determining the scaling factor may comprise e.g., a network node determining a value of lambda (or "N") as described herein, and applying the scaling factor to the TBS may comprise, for instance, multiplying the scaling factor by a nominal value or base value of TBS to produce a scaled value for TBS. Applying the scaling factor may further comprise or be accompanied by various alternative adjustments to the TBS or scaled value of TBS, such as correction for CRC, control overhead, rounding, etc., as described above. The determination of the scaling factor, and the related scaling or other adjustments to the TBS may be performed either at the network node, or at UE, for instance. Moreover, applying the scaling factor, configuring other parameters to be used when determining the scaling factor, etc., may involve communication between the network node and the UE, such as RRC signaling or other forms of transmission as described above.

Referring to <FIG>, a method <NUM> comprises a UE receiving DCI from a network node (S605), determining a nominal value or base value for TBS based on the received DCI and/or other applicable information (S610), determining a scaling factor for the TBS based on the DCI and/or other applicable information (S615), and determining a TBS based on the nominal value and the scaling factor (S620).

Referring to <FIG>, a method <NUM> comprises determining a mapping between a subset of MCS and a full MCS set (S705), and determining a TBS according to the determined mapping (S710). The determination of the mapping and TBS may be performed as described above in relation to various aspects, such as e.g. Aspect <NUM> and/or <NUM>.

Referring to <FIG>, a method <NUM> comprises receiving DCI with a configured MCS subset (S805), and determining TBS according to the received DCI (S810). In this context, the determining of the TBS may comprise e.g. reading an MCS field from the DCI to identify the subset, mapping an index associated with the MCS field to a configured list to get an index corresponding to a full MCS set, and using the index corresponding to the full MCS set to compute the TBS, as described above in relation to Aspect <NUM>.

Referring to <FIG>, a method <NUM> comprises determining a TBS/MCS configuration (S905), and determining a TBS based on the determined configuration (S910). In this context, the determining of the TBS/MCS configuration and the TBS may be performed according to the description of Aspect <NUM>, for instance. In other words, determining the TBS/MCS configuration may comprise e.g. a UE receiving DI comprising a bit field that indicates a TBS/MCS configuration, and so on.

Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in <FIG>. For simplicity, the wireless network of <FIG> only depicts network <NUM>, network nodes <NUM> and 1060b, and WDs <NUM>, 1010b, and 1010c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node <NUM> and wireless device (WD) <NUM> are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.

As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE). a vehicle-mounted wireless terminal device, etc.. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

Network connection interface <NUM> may be configured to provide a communication interface to network 1143a. Network 1143a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 1143a may comprise a Wi-Fi network.

In <FIG>, processing circuitry <NUM> may be configured to communicate with network 1143b using communication subsystem <NUM>. Network 1143a and network 1143b may be the same network or networks or different network or networks. Communication subsystem <NUM> may be configured to include one or more transceivers used to communicate with network 1143b.

Network 1143b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 1143b may be a cellular network, a Wi-Fi network, and/or a near-field network.

Access network <NUM> comprises a plurality of base stations 1312a, 1312b, 1312c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1313a, 1313b, 1313c. Each base station 1312a, 1312b, 1312c is connectable to core network <NUM> over a wired or wireless connection <NUM>. A first UE <NUM> located in coverage area 1313c is configured to wirelessly connect to, or be paged by, the corresponding base station 1312c. A second UE <NUM> in coverage area 1313a is wirelessly connectable to the corresponding base station 1312a.

It is noted that host computer <NUM>, base station <NUM> and UE <NUM> illustrated in <FIG> may be similar or identical to host computer <NUM>, one of base stations 1312a, 1312b, 1312c and one of UEs <NUM>, <NUM> of <FIG>, respectively.

Wireless connection <NUM> between UE <NUM> and base station <NUM> is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE <NUM> using OTT connection <NUM>, in which wireless connection <NUM> forms the last segment. More precisely, the teachings of these embodiments may improve physical channel processing and thereby provide benefits such as improvements in user data delivery.

In substep <NUM> of step <NUM>, the host computer provides the user data by executing a host application. In step <NUM>, the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step <NUM>, the UE executes a client application associated with the host application executed by the host computer.

In step <NUM>, the UE receives the user data carried in the transmission.

In step <NUM>, the UE receives input data provided by the host computer Additionally or alternatively, in step <NUM>, the UE provides user data. In substep <NUM> of step <NUM>, the UE provides the user data by executing a client application. In substep <NUM> of step <NUM>, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep <NUM>, transmission of the user data to the host computer.

In step <NUM>, in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step <NUM>, the base station initiates transmission of the received user data to the host computer. In step <NUM>, the host computer receives the user data carried in the transmission initiated by the base station.

Claim 1:
A method of operating a wireless communication device (<NUM>), comprising:
determining a base value for a transport block size, TBS, (S605), wherein determining the base value for the TBS comprises receiving downlink control information, DCI, and determining the base value according to the received DCI;
determining a scaling factor for the TBS (S615);
in response to detection of a radio network temporary identifier, RNTI, associated with TBS scaling, applying the scaling factor to the base value to determine the TBS (S615);
in response to detection of a RNTI not associated with TBS scaling, not applying the scaling factor to the base value to determine the TBS; and
receiving information from a radio access node according to the determined TBS.