Method, network node, wireless device, and medium for 16-QAM-based communication
By performing time domain resource assignment and rescheduling of transmission blocks in NB-IoT, the problem of low utilization efficiency of 16-QAM resources in NB-IoT is solved, and the stability of signal-to-noise ratio and the consistency of code rate are achieved.
Patent Information
- Application Number
- CN202180044514.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-04-22
- Filing Date
- 2021-04-22
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2041-04-22
AI Technical Summary
The prior art is difficult to effectively support the time domain resource assignment and transmission block redistribution of 16-QAM in NB-IoT, resulting in signal-to-noise ratio changes and resource utilization efficiency.
Through time domain resource assignment rescheduling and transmission block redistribution, the number of resource units and subframes at 16-QAM is reduced, and the TBS index and time domain resource index are adjusted to achieve resource utilization optimization and signal-to-noise ratio stability compared with QPSK.
The signal-to-noise ratio gap between 16-QAM and QPSK is reduced, resource utilization efficiency is improved, and the code rate consistency is maintained, reducing the impact of channel changes on communication.
Smart Images

Figure CN115804045B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to wireless communications, and in particular to a method, a network node, a wireless device, and a computer-readable storage medium for 16-quadrature amplitude modulation (16-QAM) based communications based on at least one of time-domain resource assignment rearrangement and transport block redistribution. Background Art
[0002] At the 86th plenary meeting of Radio Access Network (RAN) (RP-193264), a new work item (WI) titled "Rel-17 enhancements for NB-IoT and LTE-MTC" was discussed. In the work item description (WID), one of the goals is described as follows:
[0003] - Specify 16-QAM for unicast in uplink (UL) and downlink (DL), including necessary changes to DL power allocation and DL transport block size (TBS) for the narrowband physical downlink shared channel (NPDSCH). This will be specified without new NB-IoT UE categories. For DL, an increase in soft buffer size and maximum TBS may be specified by modifying at least the existing category NB2, e.g., 2 times the 3rd Generation Partnership Project (3GPP) Release 16 (Rel-16) maximum. For UL, the maximum TBS is not increased. [NB-IoT][RAN1, RAN4]
[0004] The following describes how “Modulation and coding scheme, resource assignment and TBS allocation” is performed in NB-IoT in both UL and DL, starting with the latter.
[0005] Modulation and coding schemes, resource assignment, and TBS allocation for narrowband IoT (NB-IoT) in DL
[0006] According to one or more wireless communication standards such as 3GPP Technical Specification (TS) 36.213 v16.0.0, the available modulation orders are (i.e., Quadrature Phase Shift Keying (QPSK)), and within the context of transmitting wireless device (i.e., UE) data, in the DL, the transport block size (TBS) on the NPDSCH is determined as follows:
[0007] - The wireless device may first,
[0008] Read the 4-bit "Modulation and Coding Scheme" field in the Downlink Control Information (DCI) ( ) and set .
[0009] – and secondly,
[0010] Read the 3-bit "Resource Assignment" field in the DCI ( ), and determines its TBS by, for example, the procedure in subclause 16.4.1.5.1 of 3GPP TS 36.213v16.0.0.
[0011] The resource allocation information of DCI formats N1 and N2 (paging) of NPDSCH indicates to the scheduled wireless device:
[0012] - According to, for example, Table 16.4.1.3-1 of 3GPP TS 36.213 v16.0.0, the resource assignment field in the corresponding DCI ( ) determines the number of subframes ( ).
[0013] - According to, for example, Table 16.4.1.3-2 of 3GPP TS 36.213 v16.0.0, the repetition number field in the corresponding DCI ( ) determines the number of replicates ( ).
[0014] For example, Table 16.4.1.3-1 of 3GPP TS 36.213 v16.0.0:
[0015] The number of NPDSCH subframes ( )
[0016] #timg# #timg# 0 1 1 2 2 3 3 4 4 5 5 6 6 8 7 10
[0017] For example, Table 16.4.1.3-2 of 3GPP TS 36.213 v16.0.0:
[0018] The number of repetitions of NPDSCH ( )
[0019] #timg# #timg# 0 1 1 2 2 4 3 8 4 16 5 32 6 64 7 128 8 192 9 256 10 384 11 512 12 768 13 1024 14 1536 15 2048
[0020] Related to the above, Cat-NB2 devices can support up to 2536 bits of TBS in DL. TBS is determined by, for example, ( ) entries are given.
[0021] For example, Table 16.4.1.5.1-1 of 3GPP TS 36.213 v16.0.0:
[0022] Transport Block Size (TBS) Table
[0023]
[0024] Modulation and coding scheme, resource assignment and TBS allocation for NB-IoT in UL
[0025] NPUSCH format 1 transmissions using 15 KHz subcarrier spacing can be scheduled to use a single tone (π / 2 BPSK, π / 4 QPSK) or multi-tone allocation (QPSK) consisting of 3, 6, or 12 subcarriers. In addition, in the time domain, a given TBS can be mapped on one or more resource elements. According to wireless communication standards such as 3GPP TS 36.213 v16.0.0, in order to determine the modulation order, redundancy version, and transport block size of NPUSCH, the following process can be followed:
[0026] - Wireless devices can first
[0027] Read the "Modulation and Coding Scheme" field in the DCI or configured by higher layers for Narrowband Physical Uplink Shared Channel (NPUSCH) transmission using pre-configured uplink resources ( ),as well as
[0028] Read the "Redundancy Version" field in the DCI ( ),as well as
[0029] Read the "Resource Assignment" field in the DCI or configured by higher layers for NPUSCH transmission using pre-configured uplink resources ( ),as well as
[0030] The total number of allocated subcarriers is calculated according to, for example, subclause 16.5.1.1 of 3GPP TS 36.213 v16.0.0 ( ), the number of resource units ( ) and the number of repetitions ( ).
[0031] ……,if , then the wireless device can use the modulation order .if , the wireless device may use, for example, Table 16.5.1.2-1 and To determine the modulation order for NPUSCH.
[0032] For subcarrier spacing NPUSCH transmission, the subcarrier indication field in the DCI ( ) Determine the set of consecutively allocated subcarriers according to, for example, Table 16.5.1.1-1 of 3GPP TS 36.213 v16.0.0 ( ).
[0033] For example, Table 16.5.1.1-1 of 3GPP TS 36.213 v16.0.0:
[0034] The allocated subcarriers of NPUSCH
[0035]
[0036] For example, Table 16.5.1.1-2 of 3GPP TS 36.213 v16.0.0:
[0037] The number of resource units of NPUSCH ( )
[0038] #timg# #timg# 0 1 1 2 2 3 3 4 4 5 5 6 6 8 7 10
[0039] For example, Table 16.5.1.1-3 of 3GPP TS 36.213 v16.0.0:
[0040] The number of repetitions of NPUSCH ( )
[0041] #timg# #timg# 0 1 1 2 2 4 3 8 4 16 5 32 6 64 7 128
[0042] Related to the above, Cat-NB2 devices can support up to 2536-bit TBS in UL. Wireless communication standards such as 3GPP TS 36.213v16.0.0 specify that wireless devices can use ( ) and Table 16.5.1.2-2 to determine the TBS to be used for NPUSCH. If , then given in Table 16.5.1.2-1 ,otherwise .
[0043] Table 16.5.1.2-2: Transport Block Size (TBS) Table for NPUSCH
[0044] Summary of the invention
[0045] Some embodiments advantageously provide methods, systems, and devices for supporting / enabling 16-Quadrature Amplitude Modulation (16-QAM) based communications based on at least one of: time domain resource assignment rearrangement and transport block redistribution.
[0046] One or more embodiments of the present disclosure focus on time domain resource assignment rearrangement and transport block redistribution to support 16-QAM for unicast in UL and DL.
[0047] According to a first aspect of the present disclosure, a method performed by a network node configured to communicate with a wireless device is provided. The method includes: determining a resource allocation for 16-QAM-based communication for the wireless device; and indicating to the wireless device a TBS associated with the determined resource allocation and / or the number of allocated time domain resources using a TBS index and a time domain resource index, wherein the TBS index and the time domain resource index are determined according to a table for allocating a number of transport blocks and / or allocated time domain resources for 16-QAM-based communication, wherein the table for allocating a number of transport blocks and / or allocated time domain resources for 16-QAM-based communication corresponds to at least one of the following: a time domain resource assignment (TDRA) rearrangement relative to a table for allocating a number of transport blocks and / or allocated time domain resources defined for QPSK-based communication, and a transport block redistribution relative to a table for allocating a number of transport blocks and / or allocated time domain resources defined for QPSK-based communication.
[0048] In an exemplary embodiment, a table for allocating transport blocks and / or the number of allocated time domain resources for 16-QAM based communications corresponds to a TDRA rearrangement relative to a table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communications, and a TBS is indicated using a TBS index and a time domain resource index corresponding to a reduced number of allocated time domain resources compared to the number of allocated time domain resources corresponding to the same TBS required in the table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communications.
[0049] In an exemplary embodiment, the method further includes transmitting an indication to the wireless device to use 16-QAM.
[0050] In an exemplary embodiment, a table for allocating transport blocks and / or the number of allocated time domain resources for 16-QAM based communication corresponds to a TDRA rearrangement and transport block redistribution relative to a table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication, and a TBS is indicated using a TBS index and a time domain resource index, which are respectively different from those TBS indexes and time domain resource indexes indicating the same TBS required in the table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication, wherein the time domain resource index corresponds to a reduced number of allocated time domain resources compared to the number of allocated time domain resources corresponding to the same TBS required in the table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication.
[0051] In an exemplary embodiment, the time domain resource index corresponds to a number of allocated time domain resources reduced by half compared to the number of allocated time domain resources corresponding to the same TBS required in a table for allocating transport blocks and / or allocated time domain resources defined for QPSK-based communication.
[0052] In an exemplary embodiment, transport block redistribution relative to a table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication comprises:
[0053] one or more TBSs of a first subset of TBS indices in a table for allocating transport blocks and / or allocated numbers of time domain resources defined for QPSK based communication that are reused for 16-QAM based communication, but each of said TBSs is indicated by a TBS index and / or a time domain resource index that is different from those TBS indices and / or time domain resource indices that indicate the same TBS required in the table for allocating transport blocks and / or allocated numbers of time domain resources defined for QPSK based communication, respectively; and optionally
[0054] One or more TBSs in a table for allocating transport blocks and / or allocated numbers of time domain resources defined for QPSK-based communication that are skipped for 16-QAM-based communication, the one or more skipped TBSs corresponding to a second subset of TBS indices in a table for allocating transport blocks and / or allocated numbers of time domain resources defined for QPSK-based communication; and optionally
[0055] One or more TBSs for QPSK based communication corresponding to a third subset of TBS indices in a table for allocating transport blocks and / or allocated quantities of time domain resources defined for QPSK based communication.
[0056] In an exemplary embodiment, a table for allocating transport blocks and / or the number of allocated time domain resources for 16-QAM based communication corresponds to a transport block redistribution relative to a table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication, and a TBS is indicated using a TBS index and a time domain resource index, which are different from those TBS indexes and time domain resource indexes respectively indicating the same TBS required in the table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication.
[0057] In an exemplary embodiment, transport block redistribution relative to a table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication comprises:
[0058] one or more TBSs of a first subset of TBS indices in a table for allocating transport blocks and / or allocated numbers of time domain resources defined for QPSK based communication that are reused for 16-QAM based communication, but each of said TBSs is indicated by a TBS index and / or a time domain resource index that is different from those TBS indices and / or time domain resource indices that indicate the same TBS required in the table for allocating transport blocks and / or allocated numbers of time domain resources defined for QPSK based communication, respectively; and optionally
[0059] One or more TBSs in a table for allocating transport blocks and / or allocated numbers of time domain resources defined for QPSK-based communication that are skipped for 16-QAM-based communication, the one or more skipped TBSs corresponding to a second subset of TBS indices in a table for allocating transport blocks and / or allocated numbers of time domain resources defined for QPSK-based communication; and optionally
[0060] One or more TBSs for QPSK based communication corresponding to a third subset of TBS indices in a table for allocating transport blocks and / or allocated quantities of time domain resources defined for QPSK based communication.
[0061] In an exemplary embodiment, in a case where 16-QAM based communication is used for uplink, the time domain resource index corresponds to the number of allocated time domain resource units.
[0062] In an exemplary embodiment, the method further includes: switching from QPSK-based uplink communication to 16-QAM-based uplink communication based on the determined resource allocation, wherein the 16-QAM-based uplink communication is allocated the same TBS as the TBS defined for the QPSK-based uplink communication, together with a reduced number of allocated time-domain resource units corresponding to the same TBS required by the number of allocated transport blocks and / or allocated time-domain resource units defined for the QPSK-based uplink communication, to reduce a signal-to-noise ratio (SNR) variation between the QPSK-based uplink communication and the 16-QAM-based uplink communication.
[0063] In an exemplary embodiment, the method also includes receiving a 16-QAM based uplink transmission from a wireless device using a reduced number of allocated time domain resource units corresponding to the same TBS required by the number of allocated transport blocks and / or allocated time domain resource units defined for QPSK based uplink communications.
[0064] In an exemplary embodiment, in a case where 16-QAM based communication is used for downlink, the time domain resource index corresponds to the number of allocated subframes.
[0065] In an exemplary embodiment, the method further includes switching from QPSK-based downlink communication to 16-QAM-based downlink communication based on the determined resource allocation, wherein the 16-QAM-based downlink communication is allocated the same TBS as that defined for the QPSK-based downlink communication, together with a reduced number of allocated subframes corresponding to the same TBS required by the number of allocated transport blocks and / or allocated subframes defined for the QPSK-based downlink communication, so as to reduce the SNR variation between the QPSK-based downlink communication and the 16-QAM-based downlink communication.
[0066] In an exemplary embodiment, the method further includes transmitting a 16-QAM based downlink transmission to the wireless device using a reduced number of allocated subframes corresponding to the same TBS required by the number of allocated transport blocks and / or allocated subframes defined for QPSK based downlink communications.
[0067] According to a second aspect of the present disclosure, a method performed by a wireless device configured to communicate with a network node is provided. The method includes: receiving an indication of a TBS index and a time domain resource index from the network node; determining the number of TBSs and / or allocated time domain resources using the received TBS index and the time domain resource index according to a table for allocating the number of transport blocks and / or allocated time domain resources for 16-QAM-based communication, so as to obtain resource allocation for 16-QAM-based communication for the wireless device, wherein the table for allocating the number of transport blocks and / or allocated time domain resources for 16-QAM-based communication corresponds to at least one of the following: a time domain resource assignment (TDRA) rearrangement relative to a table for allocating the number of transport blocks and / or allocated time domain resources defined for QPSK-based communication, and a transport block redistribution relative to a table for allocating the number of transport blocks and / or allocated time domain resources defined for QPSK-based communication.
[0068] In an exemplary embodiment, a table for allocating transport blocks and / or the number of allocated time domain resources for 16-QAM based communications corresponds to a TDRA rearrangement relative to a table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communications, and the TBS and / or the number of allocated time domain resources are determined using a TBS index and a time domain resource index corresponding to a reduced number of allocated time domain resources compared to the number of allocated time domain resources corresponding to the same TBS required in the table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communications.
[0069] In an exemplary embodiment, the method further comprises receiving an indication to use 16-QAM from a network node.
[0070] In an exemplary embodiment, a table for allocating transport blocks and / or the number of allocated time domain resources for 16-QAM based communication corresponds to a TDRA rearrangement and transport block redistribution relative to a table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication, and the TBS and / or the number of allocated time domain resources are determined using a TBS index and a time domain resource index, which are respectively different from those TBS indexes and time domain resource indexes indicating the same TBS required in the table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication, wherein the time domain resource index corresponds to a reduced number of allocated time domain resources compared to the number of allocated time domain resources corresponding to the same TBS required in the table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication.
[0071] In an exemplary embodiment, the time domain resource index corresponds to a number of allocated time domain resources reduced by half compared to the number of allocated time domain resources corresponding to the same TBS required in a table for allocating transport blocks and / or allocated time domain resources defined for QPSK-based communication.
[0072] In an exemplary embodiment, transport block redistribution relative to a table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication comprises:
[0073] One or more TBSs corresponding to a first subset of TBS indices in a table for allocating transport blocks and / or allocated numbers of time domain resources defined for QPSK based communication that are reused for 16-QAM based communication, but each of said TBSs is indicated by a TBS index and / or a resource index that is different from those of the same TBS required in the table for allocating transport blocks and / or allocated numbers of time domain resources defined for QPSK based communication, respectively; and optionally
[0074] One or more TBSs in a table for allocating transport blocks and / or allocated numbers of time domain resources defined for QPSK-based communication that are skipped for 16-QAM-based communication, the one or more skipped TBSs corresponding to a second subset of TBS indices in a table for allocating transport blocks and / or allocated numbers of time domain resources defined for QPSK-based communication; and optionally
[0075] One or more TBSs for QPSK based communication corresponding to a third subset of TBS indices in a table for allocating transport blocks and / or allocated quantities of time domain resources defined for QPSK based communication.
[0076] In an exemplary embodiment, a table for allocating transport blocks and / or the number of allocated time domain resources for 16-QAM based communication corresponds to a transport block redistribution relative to a table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication, and the TBS and / or the number of allocated time domain resources are determined using a TBS index and a time domain resource index, which are different from those TBS indexes and time domain resource indexes indicating the same TBS required in the table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication, respectively.
[0077] In an exemplary embodiment, transport block redistribution relative to a table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication comprises:
[0078] one or more TBSs of a first subset of TBS indices in a table for allocating transport blocks and / or allocated numbers of time domain resources defined for QPSK based communication that are reused for 16-QAM based communication, but each of said TBSs is indicated by a TBS index and / or a time domain resource index that is different from those TBS indices and / or time domain resource indices that indicate the same TBS required in the table for allocating transport blocks and / or allocated numbers of time domain resources defined for QPSK based communication, respectively; and optionally
[0079] One or more TBSs in a table for allocating transport blocks and / or allocated numbers of time domain resources defined for QPSK-based communication that are skipped for 16-QAM-based communication, the one or more skipped TBSs corresponding to a second subset of TBS indices in a table for allocating transport blocks and / or allocated numbers of time domain resources defined for QPSK-based communication; and optionally
[0080] One or more TBSs for QPSK based communication corresponding to a third subset of TBS indices in a table for allocating transport blocks and / or allocated quantities of time domain resources defined for QPSK based communication.
[0081] In an exemplary embodiment, in a case where 16-QAM based communication is used for uplink, the time domain resource index corresponds to the number of allocated time domain resource units.
[0082] In an exemplary embodiment, the method further includes switching from QPSK-based uplink communication to 16-QAM-based uplink communication based on the obtained resource allocation, wherein the 16-QAM-based uplink communication is allocated the same TBS as that defined for the QPSK-based uplink communication, together with a reduced number of allocated time domain resource units corresponding to the same TBS required by the number of allocated transport blocks and / or allocated time domain resource units defined for the QPSK-based uplink communication, so as to reduce the SNR variation between the QPSK-based uplink communication and the 16-QAM-based uplink communication.
[0083] In an exemplary embodiment, the method also includes transmitting a 16-QAM based uplink transmission to a network node using a reduced number of allocated time domain resource units corresponding to the same TBS required by the number of allocated transport blocks and / or allocated time domain resource units defined for QPSK based uplink communications.
[0084] In an exemplary embodiment, the method further includes performing power boosting by adding a power increment in a calculation of transmit power of the wireless device to reduce a gap in required SNR between QPSK-based uplink communications and 16-QAM-based uplink communications.
[0085] In an exemplary embodiment, in a case where 16-QAM based communication is used for downlink, the time domain resource index corresponds to the number of allocated subframes.
[0086] In an exemplary embodiment, the method further includes switching from QPSK-based downlink communication to 16-QAM-based downlink communication based on the obtained resource allocation, wherein the 16-QAM-based downlink communication is allocated the same TBS as that defined for the QPSK-based downlink communication, together with a reduced number of allocated subframes corresponding to the same TBS required by the number of allocated transport blocks and / or allocated subframes defined for the QPSK-based downlink communication, so as to reduce the SNR variation between the QPSK-based downlink communication and the 16-QAM-based downlink communication.
[0087] In an exemplary embodiment, the method further includes receiving a 16-QAM based downlink transmission from a network node using a reduced number of allocated subframes corresponding to the same TBS required by the number of allocated transport blocks and / or allocated subframes defined for QPSK based downlink communications.
[0088] According to a third aspect of the present disclosure, a network node is provided, comprising: at least one processor, and at least one memory storing instructions, wherein when the instructions are executed on the at least one processor, the network node executes any method according to the first aspect of the present disclosure.
[0089] According to a fourth aspect of the present disclosure, a wireless device is provided, comprising: at least one processor, and at least one memory storing instructions, wherein when the instructions are executed on the at least one processor, the wireless device performs any method according to the second aspect of the present disclosure.
[0090] According to a fifth aspect of the present disclosure, a computer-readable storage medium is provided. The computer-readable storage medium has computer program instructions stored thereon, and when the computer program instructions are executed by at least one processor, the at least one processor executes the method according to any of the first and second aspects of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0091] A more complete understanding of the present embodiments and attendant advantages and features will be more readily appreciated by reference to the following detailed description when considered in conjunction with the accompanying drawings, in which:
[0092] Figure 1 is a schematic diagram illustrating an exemplary network architecture of a communication system connected to a host computer via an intermediate network according to the principles of the present disclosure;
[0093] Figure 2 is a block diagram of a host computer communicating with a wireless device via a network node over an at least partially wireless connection according to some embodiments of the present disclosure;
[0094] Figure 3 is a flow chart illustrating an exemplary method for executing a client application at a wireless device implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;
[0095] Figure 4 is a flow chart illustrating an exemplary method for receiving user data at a wireless device implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;
[0096] Figure 5 is a flow chart illustrating an exemplary method for receiving user data from a wireless device at a host computer implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;
[0097] Figure 6 is a flow chart illustrating an exemplary method for receiving user data at a host computer implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;
[0098] Figure 7 is a flow chart of an exemplary process in a network node according to some embodiments of the present disclosure;
[0099] Figure 8 is a flow chart of an exemplary process in a wireless device according to some embodiments of the present disclosure;
[0100] Fig. 9 is a graph of a side-by-side comparison of Alt-1 and Alt-2 with TBS=10 according to some embodiments of the present disclosure;
[0101] Fig.10 is a graph of a side-by-side comparison of Alt-1 and Alt-2 with TBS=11 according to some embodiments of the present disclosure;
[0102] Fig.11is a graph of a side-by-side comparison of Alt-1 and Alt-2 for TBS=12 according to some embodiments of the present disclosure; and
[0103] Fig.12 is a graph of a side-by-side comparison of Alt-1 and Alt-2 for TBS=13 according to some embodiments of the present disclosure. DETAILED DESCRIPTION
[0104] As mentioned above, one of the goals of the WI for “Rel-17 Enhancements for NB-IoT and LTE-MTC” is to “specify 16-QAM for unicast in UL and DL”; however, at least some of the issues with its support in NB-IoT are noted below:
[0105] - Although the frequency resource allocation (i.e., multi-tone allocation and single-tone allocation) used for QPSK in NB-IoT is expected to be fully or partially reused for 16-QAM, the resource allocation in the time domain may not remain unchanged in order to observe more gains from the introduction of 16-QAM.
[0106] - The WID states that "for DL, the maximum TBS is increased to, e.g., 2x the Rel-16 maximum", but this means that new transport block size (TBS) entries will have to be added relative to the available entries for Cat-NB2 devices. However, it does not describe which of those existing TBS entries will be used with 16-QAM in the DL and how.
[0107] -WID states that "For UL, there is no increase in maximum TBS", which means that 16-QAM will have to be available on existing TBS entries for Cat-NB2 devices. However, there is currently no description of which of those existing TBS entries will be used with 16-QAM in the UL and how.
[0108] Before describing the exemplary embodiments in detail, it is noted that the embodiments reside primarily in combinations of device components and processing steps related to supporting / implementing 16-quadrature amplitude modulation (16-QAM) based communications based on at least one of time domain resource assignment rearrangement and transport block redistribution.
[0109] Therefore, where appropriate, components have been represented by conventional symbols in the drawings, showing only those specific details relevant to understanding the embodiments, to avoid obscuring the present disclosure with details that would be readily apparent to one of ordinary skill in the art having the benefit of the description herein. Throughout this description, like numbers refer to like elements.
[0110] As used herein, relational terms such as "first" and "second", "top" and "bottom", etc., may be used only 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 terms used herein are for the purpose of describing specific embodiments only and are not intended to limit 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 also be understood that the terms "comprise, comprising, include and / or including", when used herein, specify the presence of stated features, wholes, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or groups thereof.
[0111] In the embodiments described herein, the connection terms "in communication with..." and the like may be used to indicate electrical communication or data communication, which may be achieved, for example, by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling, or optical signaling. Those skilled in the art will recognize that multiple components may interoperate, and modifications and variations in achieving electrical communication and data communication are possible.
[0112] In some embodiments described herein, the terms "coupled," "connected," and the like may be used herein to indicate a connection (although not necessarily a direct one), and may include wired and / or wireless connections.
[0113] The term "network node" used herein may be any kind of network node included in a radio network, and may also include any of the following items: a base station (BS), a radio base station, a base transceiver station (BTS), a base station controller (BSC), a radio network controller (RNC), a gNode B (gNB), an evolved Node B (eNB or eNodeB), a Node B, a multi-standard radio (MSR) radio node (such as an MSR BS), a multi-cell / multicast coordination entity (MCE), an integrated access and backhaul (IAB) node, a relay node, a donor node controlling a relay, a radio access point (AP), a transmission point, a transmission node, a remote radio unit (RRU), a remote radio head (RRH), a core network node (e.g., a mobile management entity (MME), a self-organizing network (SON) node, a coordination node, a positioning node, an MDT node, etc.), an external node (e.g., a third-party node, a node outside the current network), a node in a distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also include a test device. As used herein, the term "radio node" may also be used to refer to a wireless device, such as a wireless device or a radio network node.
[0114] In some embodiments, the non-limiting terms wireless device or user equipment (UE) are used interchangeably. The wireless device herein may be any type of wireless device capable of communicating with a network node or another wireless device via a radio signal, such as a wireless device. The wireless device may also be a radio communication device, a target device, a device-to-device (D2D) wireless device, a machine type wireless device, or a wireless device capable of machine-to-machine communication (M2M), a low-cost and / or low-complexity wireless device, a sensor equipped with a wireless device, a tablet, a mobile terminal, a smart phone, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a customer premises equipment (Customer Premises Equipment) (CPE), an Internet of Things (IoT) device, or a narrowband IoT (NB-IOT) device, etc.
[0115] Furthermore, in some embodiments, the generic term "radio network node" is used. It may be any kind of radio network node, which may include any of the following: 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).
[0116] Note that although terminology from one particular wireless system such as, for example, 3GPP Long Term Evolution (LTE) and / or New Radio (NR) may be used in the present disclosure, this should not be viewed as limiting the scope of the present disclosure to only the aforementioned systems. Other wireless systems including, but not limited to, Wideband 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 utilizing the concepts encompassed within the present disclosure.
[0117] Note also that the functions described herein as being performed by a wireless device or network node may be distributed across multiple wireless devices and / or network nodes. In other words, it is contemplated that the functions of the network nodes and wireless devices described herein are not limited to being performed by a single physical device and may in fact be distributed across several physical devices.
[0118] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as those commonly understood by those skilled in the art to which the present disclosure belongs. It will also be understood that, unless expressly defined as such herein, the terms used herein should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and this specification, and will not be interpreted in an idealized or overly formal sense.
[0119] Embodiments provide support and implementation for 16-Quadrature Amplitude Modulation (16-QAM) based communications based on at least one of, for example, time domain resource assignment rearrangement and transport block redistribution.
[0120] One or more embodiments of the present disclosure describe the following solutions / methods, processes / actions for possible problems supporting 16-QAM for unicast in UL and DL, e.g., for NB-IoT:
[0121] - Time domain resource assignment rescheduling:
[0122] 16-QAM for unicast in UL: When 16-QAM is used, the number of allocated resource units is reduced by, for example, half relative to the number of allocated resource units when QPSK is used.
[0123] ▪To reduce the gap in required SNR between QPSK and 16-QAM, a new component (e.g., power increase) can be added to the transmit power control equation of the wireless device in NB-IoT to increase the power by X dB when using 16-QAM.
[0124] 16-QAM for unicast in DL: When using 16-QAM, the number of allocated subframes for NPDSCH is reduced, for example, by half relative to the allocated subframes when using QPSK.
[0125] - Transport block redistribution:
[0126] 16-QAM for unicast in UL: When 16-QAM is used, (I TBS , I RU ) The selected TBS entry does not have the same position in the TBS table as that used for QPSK (i.e. (I TBS , I RU ) position), while some other entries may be skipped.
[0127] 16-QAM for unicast in DL: When 16-QAM is used, (I TBS , I SF ) The selected TBS entry does not have the same position in the TBS table as that used for QPSK (i.e., (I TBS , I SF ) position), while some other entries may be skipped.
[0128] - Time domain resource assignment rearrangement along with transport block redistribution.
[0129] 16-QAM for unicast in UL: When 16-QAM is used, the number of allocated resource units is reduced (e.g., reduced by half) and is determined by (I TBS , I RU ) The selected TBS entry does not have the same position in the TBS table as that used for QPSK (i.e., (I TBS , I RU )Location).
[0130] 16-QAM for unicast in DL: When 16-QAM is used, the number of allocated subframes for NPDSCH is reduced (e.g., reduced by half) and is given by (I TBS , I RU ) The selected TBS entry does not have the same position in the TBS table as that used for QPSK (i.e., (I TBS , I RU )Location).
[0131] One or more advantages associated with one or more embodiments described herein may include the following:
[0132] - Time domain resource assignment rescheduling:
[0133] When 16-QAM is used, resources in the time domain can be released earlier than when QPSK is used.
[0134] One or more embodiments described herein may be directly applicable to conventional TBS tables used with QPSK when using 16-QAM, for example by reducing the number of allocated resource units by half. This may reduce resource utilization in the time domain by half.
[0135] Performing a time domain resource assignment rearrangement (eg, by reducing the number of allocated resource units by half when using 16-QAM) may not require changing the allocation of resources in the frequency domain.
[0136] When switching from 16-QAM to QPSK and vice versa, all legacy TBS entries for QPSK may be fully available since the solution under "Time Domain Resource Assignment Rescheduling" does not require modification of the legacy TBS table for QPSK.
[0137] - Transport block redistribution:
[0138] One or more embodiments described herein allow for reorganizing existing TBS entries, for example, based on achievable code rates for both QPSK and 16-QAM, in order to reduce the gap in required signal-to-interference-plus-noise ratio (SINR) between these two modulation schemes. Furthermore, appropriate link adaptation is achieved on wireless devices experiencing different channel conditions or different SINR scenarios by carefully redistributing the TBS entries, in order to keep small differences in achievable codes, for example, for neighbors and adjacent rows in the TBS table.
[0139] In the UL, transport block redistribution avoids having to include a new component (e.g., power increase) to the wireless device's transmit power control equation in order to boost power to close the gap in SNR requirements between 16-QAM and QPSK, for example in NB-IoT.
[0140] Transport block redistribution may be applied to TBS entries used by both QPSK and 16-QAM, and in this case, there may be no need to add 1 bit as part of the downlink control information to indicate whether the wireless device uses QPSK or 16-QAM, because as long as the 16-QAM feature is enabled, a single redistributed TBS table can be used by both modulation schemes, with some portions of the TBS table being used only with QPSK and the rest being used with 16-QAM. That is, the index used to select a TBS entry in the TBS table will be used to select one modulation scheme or the other, because it is known in advance which entries can be used with QPSK and which entries can be used with 16-QAM.
[0141] - Time domain resource assignment rearrangement along with transport block redistribution.
[0142] In one or more embodiments, when 16-QAM is used, the hybrid scheme allows for reducing resource utilization in the time domain while keeping the gap in SNR requirements between QPSK and 16-QAM within a predefined range or, for example, not exceeding a few dB.
[0143] Referring now to the drawings, wherein like elements are referred to by like reference numerals, Figure 1 1 shows a schematic diagram of a communication system 10 according to an embodiment, such as a 3GPP-type cellular network that can support standards such as LTE and / or NR (5G), which includes an access network 12 such as a radio access network and a core network 14. The access network 12 includes a plurality of network nodes 16a, 16b, 16c (collectively referred to as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each of which defines a corresponding coverage area 18a, 18b, 18c (collectively referred to as coverage area 18). Each network node 16a, 16b, 16c is connectable to the core network 14 via a wired or wireless connection 20. A first wireless device 22a located in the coverage area 18a is configured to be wirelessly connected to the corresponding network node 16a, or to be paged by the corresponding network node 16a. A second wireless device 22b in the coverage area 18b is wirelessly connectable to the corresponding network node 16b. Although multiple wireless devices 22a, 22b (collectively referred to as wireless devices 22) are shown in this example, the disclosed embodiments are equally applicable to situations where only a wireless device is in the coverage area or a only wireless device is connecting to the corresponding network node 16. Note that although only two wireless devices 22 and three network nodes 16 are shown for convenience, the communication system may include many more wireless devices 22 and network nodes 16.
[0144] Furthermore, it is contemplated that the wireless device 22 may communicate with more than one network node 16 and more than one type of network node 16 simultaneously and / or be configured to communicate with more than one network node 16 and more than one type of network node 16, respectively. For example, the wireless device 22 may have dual connectivity with a network node 16 supporting LTE and the same or different network node 16 supporting NR. As an example, the wireless device 22 may communicate with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.
[0145] The communication system 10 itself may be connected to a host computer 24, which may be embodied in hardware and / or software as 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 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 a combination of one or more of a public network, a private network, or a managed network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may include two or more subnetworks (not shown).
[0146] Figure 1 The communication system as a whole enables connectivity between one of the connected wireless devices 22a, 22b and the host computer 24. This connectivity can be described as an over-the-top (OTT) connection. The host computer 24 and the connected wireless devices 22a, 22b are configured to use the access network 12, the core network 14, any intermediate network 30 and possible additional infrastructure (not shown) as intermediaries to transfer data and / or signaling via the OTT connection. The OTT connection can be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes do not know the routes of the uplink and downlink communications. For example, the network node 16 may not or need not be informed of the past routes of incoming downlink communications, which have data from the host computer 24 to be forwarded (e.g., handed over) to the connected wireless device 22a. Similarly, the network node 16 does not need to know the future routes of outgoing uplink communications from the wireless device 22a toward the host computer 24.
[0147] The network node 16 is configured to include at least: a determination unit 31, which is configured to determine a resource allocation for 16-QAM based communication for the wireless device 22; and an indication unit 32, which is configured to indicate the transport block size TBS and / or the number of allocated time domain resources associated with the determined resource allocation to the wireless device 22 using a TBS index and a time domain resource index, wherein the TBS index and the time domain resource index are determined according to a table for allocating transport blocks and / or the number of allocated time domain resources for 16-QAM based communication, wherein the table for allocating transport blocks and / or the number of allocated time domain resources for 16-QAM based communication corresponds to at least one of the following: a time domain resource assignment (TDRA) rearrangement relative to a table for allocating the number of transport blocks and / or the number of allocated time domain resources defined for QPSK based communication, and a transport block redistribution relative to a table for allocating the number of transport blocks and / or the number of allocated time domain resources defined for QPSK based communication.
[0148] The wireless device 22 is configured to include at least a determination unit 34, which is configured to determine the number of allocated transport blocks and / or allocated time domain resources according to a table for 16-QAM-based communication using a method such as ( Figure 2 The method comprises the steps of: determining a TBS and / or the number of allocated time domain resources based on a TBS index and a time domain resource index received by a radio interface 82 of the wireless communication system (as shown in the figure) to obtain a resource allocation for 16-QAM-based communication for a wireless device, wherein the table for allocating the number of transport blocks and / or allocated time domain resources for 16-QAM-based communication corresponds to at least one of the following: a TDRA rearrangement relative to a table for allocating the number of transport blocks and / or allocated time domain resources defined for quadrature phase shift keying (QPSK)-based communication, and a transport block redistribution relative to a table for allocating the number of transport blocks and / or allocated time domain resources defined for QPSK-based communication.
[0149] According to the embodiment, reference will now be made to Figure 2An example implementation of the wireless device 22, network node 16, and host computer 24 discussed in the previous paragraphs is described. In the communication system 10, the host computer 24 includes hardware (HW) 38, which includes a communication interface 40, which is configured to establish and maintain a wired or wireless connection with the interface of different communication devices of the communication system 10. The host computer 24 also includes a processing circuit 42, which may have storage and / or processing capabilities. The processing circuit 42 may include a processor 44 and a memory 46. In particular, in addition to or instead of a processor (such as a central processing unit) and a memory, the processing circuit 42 may include an integrated circuit for processing and / or control, for example, one or more processors and / or processor cores and / or FPGAs (field programmable gate arrays) and / or ASICs (application-specific integrated circuits) suitable for executing instructions. The processor 44 may be configured to access (e.g., write to and / or read from) a memory 46, which may include any kind of volatile and / or non-volatile memory, such as 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).
[0150] Processing circuit 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, for example, by host computer 24. Processor 44 corresponds to one or more processors 44 for performing the functions of host computer 24 described herein. Host computer 24 includes memory 46 configured to store data, programmatic software code, and / or other information described herein. In some embodiments, software 48 and / or host application 50 may include instructions that, when executed by processor 44 and / or processing circuit 42, cause processor 44 and / or processing circuit 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with host computer 24.
[0151] The software 48 may be executable by the processing circuit 42. The software 48 includes a host application 50. The host application 50 may be operable to provide services to a remote user (such as a wireless device 22 connected via an OTT connection 52 terminated at the wireless device 22 and the host computer 24). When providing services to the remote user, the host application 50 may provide user data transmitted using the OTT connection 52. "User data" may be data and information described herein as implementing the functionality. In one embodiment, the host computer 24 may be configured to provide control and functionality to a service provider and may be operated by or on behalf of the service provider. The processing circuit 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 a service provider to one or more of process, store, determine, forward, relay, transmit, receive, etc., information related to support and implementation of 16-quadrature amplitude modulation (16-QAM) based communications based on, for example, at least one of time domain resource assignment rearrangement and transport block redistribution.
[0152] The communication system 10 also includes a network node 16, which is arranged in the communication system 10 and includes hardware 58 that enables it to communicate with the host computer 24 and the wireless device 22. The hardware 58 may include a communication interface 60 for establishing and maintaining a wired or wireless connection to the interface of different communication devices of the communication system 10, and a radio interface 62 for establishing and maintaining a wireless connection 64 with the wireless device 22 located in the 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 be through the core network 14 of the communication system 10 and / or through one or more intermediate networks 30 external to the communication system 10.
[0153] In the illustrated embodiment, the hardware 58 of the network node 16 also includes a processing circuit 68. The processing circuit 68 may include a processor 70 and a memory 72. In particular, in addition to or in place of a processor (such as a central processing unit) and a memory, the processing circuit 68 may include an integrated circuit for processing and / or control, for example, one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) adapted to execute instructions. The processor 70 may be configured to access the memory 72 (e.g., write to the memory 72 and / or read from the memory 72), and the memory 72 may include any kind of volatile and / or non-volatile memory, such as a cache and / or buffer memory and / or a RAM (random access memory) and / or a ROM (read-only memory) and / or an optical memory and / or an EPROM (erasable programmable read-only memory).
[0154] Therefore, the network node 16 also has software 74, which is stored internally, for example, in the memory 72, or stored in an external memory (e.g., a database, a storage array, a network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 is executable by the processing circuit 68. The processing circuit 68 can be configured to control any of the methods and / or processes described herein, and / or cause such methods and / or processes to be performed, for example, by the network node 16. The processor 70 corresponds to one or more processors 70 for performing the network node 16 functions described herein. The memory 72 is configured to store data, programmed 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 the processing circuit 68, cause the processor 70 and / or the processing circuit 68 to perform the processes described herein with respect to the network node 16. For example, the processing circuit 68 of the network node 16 may include at least a determination unit 31 and an indication unit 32, wherein the determination unit 31 is configured to determine a resource allocation for 16-QAM based communication for the wireless device 22, and the indication unit 32 is configured to indicate the transport block size TBS and / or the number of allocated time domain resources associated with the determined resource allocation to the wireless device 22 using a TBS index and a time domain resource index, wherein the TBS index and the time domain resource index are determined according to a table for allocating transport blocks and / or the number of allocated time domain resources for 16-QAM based communication, wherein the table for allocating transport blocks and / or the number of allocated time domain resources for 16-QAM based communication corresponds to at least one of the following: a time domain resource assignment (TDRA) rearrangement relative to a table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication, and a transport block redistribution relative to a table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication.
[0155] The communication system 10 also includes the already mentioned wireless device 22. The wireless device 22 may have hardware 80, which may include a radio interface 82 configured to establish and maintain a wireless connection 64 with a network node 16 serving the coverage area 18 in which the wireless device 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.
[0156] The hardware 80 of the wireless device 22 also includes a processing circuit 84. The processing circuit 84 may include a processor 86 and a memory 88. In particular, in addition to or in place of a processor (such as a central processing unit) and a memory, the processing circuit 84 may include an integrated circuit for processing and / or control, such as one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) adapted to execute instructions. The processor 86 may be configured to access the memory 88 (e.g., write to the memory 88 and / or read from the memory 88), and the memory 88 may include any kind of volatile and / or non-volatile memory, such as a cache and / or buffer memory and / or a RAM (random access memory) and / or a ROM (read-only memory) and / or an optical memory and / or an EPROM (erasable programmable read-only memory).
[0157] Therefore, the wireless device 22 may also include software 90, which is stored in, for example, the memory 88 of the wireless device 22, or in an external memory (e.g., a database, a storage array, a network storage device, etc.) accessible by the wireless device 22. The software 90 may be executable by the processing circuit 84. The software 90 may include a client application 92. The client application 92 may be operable to provide services to a human or non-human user via the wireless device 22 with the support of the host computer 24. In the host computer 24, the executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminated at the wireless device 22 and the host computer 24. When providing services 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 transmit both the request data and the user data. The client application 92 may interact with the user in order to generate the user data it provides.
[0158] The processing circuit 84 may be configured to control any of the methods and / or processes described herein and / or cause such methods and / or processes to be performed, for example, by the wireless device 22. The processor 86 corresponds to one or more processors 86 for performing the functions of the wireless device 22 described herein. The wireless device 22 includes a memory 88, which is configured to store data, programming 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 the processing circuit 84, cause the processor 86 and / or the processing circuit 84 to perform the processes described herein with respect to the wireless device 22. For example, the processing circuit 84 of the wireless device 22 may include at least a determination unit 34 that is configured to determine the number of allocated transport blocks and / or allocated time domain resources based on a table for 16-QAM-based communication using, for example, a method (e.g., Figure 2The method comprises the steps of: determining a TBS and / or the number of allocated time domain resources based on a TBS index and a time domain resource index received by a radio interface 82 of the wireless communication system (as shown in the figure) to obtain a resource allocation for 16-QAM-based communication for a wireless device, wherein the table for allocating the number of transport blocks and / or allocated time domain resources for 16-QAM-based communication corresponds to at least one of the following: a TDRA rearrangement relative to a table for allocating the number of transport blocks and / or allocated time domain resources defined for quadrature phase shift keying (QPSK)-based communication, and a transport block redistribution relative to a table for allocating the number of transport blocks and / or allocated time domain resources defined for QPSK-based communication.
[0159] In some embodiments, the internal workings of network node 16, wireless device 22, and host computer 24 may be as follows: Figure 2 As shown in , and independently, the surrounding network topology can be Figure 1 network topology.
[0160] exist Figure 2 , the OTT connection 52 has been abstractly drawn to illustrate communications 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. The network infrastructure can determine the routing, which can be configured to be hidden from the wireless device 22 or the service provider operating the host computer 24, or both. When the OTT connection 52 is active, the network infrastructure can also make decisions by which it dynamically changes the routing (e.g., based on reconfiguration of the network or load balancing considerations).
[0161] The wireless connection 64 between the wireless device 22 and the network node 16 is consistent with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improves the performance of OTT services provided to the wireless device 22 using the OTT connection 52, where the wireless connection 64 may form the last leg. More specifically, the teachings of some of these embodiments may improve data rates, latency, and / or power consumption, and thereby provide benefits such as reduced user waiting time, relaxed restrictions on file size, better responsiveness, extended battery life, etc.
[0162] In some embodiments, a measurement process may be provided for the purpose of monitoring data rates, latency, and other factors improved by one or more embodiments. There may also be optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and the wireless device 22 in response to changes in the measurement results. The measurement process and / or network functionality for reconfiguring the OTT connection 52 may be implemented with the software 48 of the host computer 24, or with the software 90 of the wireless device 22, or with both. In an embodiment, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 52 passes; the sensor may participate in the measurement process by supplying the values of the monitored quantities exemplified above, or supplying the values of other physical quantities from which the software 48, 90 can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 52 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not need to affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such processes and functionalities may be known and practiced in the art. In some embodiments, the measurements may involve proprietary wireless device signaling that facilitates the host computer 24's measurement of throughput, propagation time, latency, etc. In some embodiments, the measurements may be implemented where the software 48, 90 uses the OTT connection 52 to cause messages (particularly empty or "dummy" messages) to be transmitted while it monitors propagation time, errors, etc.
[0163] Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 configured to forward the user data to a cellular network for transmission to the wireless device 22. In some embodiments, the cellular network also includes a network node 16 having a radio interface 62. In some embodiments, the network node 16 is configured to and / or the processing circuitry 68 of the network node 16 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / terminating transmissions to the wireless device 22 and / or preparing / terminating / maintaining / supporting / terminating reception of transmissions from the wireless device 22.
[0164] In some embodiments, host computer 24 includes processing circuitry 42 and communication interface 40 configured to receive user data originating from transmissions from wireless device 22 to network node 16. In some embodiments, wireless device 22 is configured to and / or includes a radio interface 82 and / or processing circuitry 84 configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / terminating transmissions to network node 16 and / or preparing / terminating / maintaining / supporting / terminating reception of transmissions from network node 16.
[0165] although Figure 1 and Figure 2 Various "units" such as the determination unit 31 and the indication unit 32 of the network node 16 and the determination unit 34 of the wireless device 22 are shown as being within respective processors, but 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 circuit. In other words, these units may be implemented within the processing circuit in hardware or a combination of hardware and software.
[0166] Figure 3 is a diagram showing a communication system (such as, for example, Figure 1 and Figure 2 Flowchart of an exemplary method implemented in a communication system of FIG. 1 . The communication system may include a host computer 24, a network node 16, and a wireless device 22, which may be a reference Figure 2 Those host computers, network nodes, and wireless devices described herein. In a first step of the method, the host computer 24 provides user data (block S100). In an optional sub-step 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 S102). In a second step, the host computer 24 initiates a transmission to the wireless device 22 carrying the user data (block S104). In an optional third step, in accordance with the teachings of the embodiments described throughout the present disclosure, the network node 16 transmits the user data carried in the transmission initiated by the host computer 24 to the wireless device 22 (block S106). In an optional fourth step, the wireless device 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 S108).
[0167] Figure 4 is a diagram showing a communication system (such as, for example, Figure 1 Flowchart of an exemplary method implemented in a communication system of FIG. 1 . The communication system may include a host computer 24, a network node 16, and a wireless device 22, which may be a reference Figure 1 and2 1. The method of claim 1, wherein the host computer 24 provides user data (block S110). In an optional sub-step (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 to the wireless device 22 carrying the user data (block S112). In accordance with the teachings of the embodiments described throughout this disclosure, the transmission may be delivered via the network node 16. In an optional third step, the wireless device 22 receives the user data carried in the transmission (block S114).
[0168] Figure 5 is a diagram showing a communication system (such as, for example, Figure 1 The communication system may include a host computer 24, a network node 16, and a wireless device 22, which may be a reference Figure 1 and 2 Those host computers, network nodes, and wireless devices described herein. In an optional first step of the method, the wireless device 22 receives input data provided by the host computer 24 (block S116). In an optional sub-step of the first step, the wireless device 22 executes the client application 92, which provides user data as a reaction to the received input data provided by the host computer 24 (block S118). Additionally or alternatively, in an optional second step, the wireless device 22 provides user data (block S120). In an optional sub-step of the second step, the wireless device provides user data by executing a client application (such as, for example, the client application 92) (block S122). In providing the user data, the executed client application 92 may also take into account user input received from the user. Regardless of the particular manner in which the user data is provided, in an optional third sub-step, the wireless device 22 may initiate transmission of the user data to the host computer 24 (block S124). In a fourth step of the method, host computer 24 receives user data transmitted from wireless device 22 (block S126 ), in accordance with the teachings of the embodiments described throughout this disclosure.
[0169] Figure 6 is a diagram showing a communication system (such as, for example, Figure 1 The communication system may include a host computer 24, a network node 16, and a wireless device 22, which may be a reference Figure 1 and 2In an optional first step of the method, the network node 16 receives user data from the wireless device 22 in accordance with the teachings of the embodiments described throughout this disclosure (block S128). In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (block S130). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (block S132).
[0170] Figure 7 is a flow chart of an exemplary process (method 700 ) in the network node 16 according to some embodiments of the present disclosure.
[0171] One or more blocks and / or functions performed by the network node 16 may be performed by one or more elements of the network node 16, such as by the determination unit 31, the indication unit 32, the processor 70, the radio interface 62, etc. in the processing circuit 68. In one or more embodiments, the network node 16, such as via one or more of the processing circuit 68, the processor 70, the determination unit 31, the communication interface 60, and the radio interface 62, may be configured to determine (block S701) resource allocation for communication based on 16-quadrature amplitude modulation (16-QAM) for the wireless device 22. Then, the network node 16, such as via one or more of the processing circuit 68, the processor 70, the indication unit 32, the communication interface 60 and the radio interface 62, may be configured to indicate (block S703) the TBS associated with the determined resource allocation and / or the number of allocated time domain resources to the wireless device 22 using the TBS index and the time domain resource index, wherein the TBS index and the time domain resource index are determined according to a table for allocating a number of transport blocks and / or allocated time domain resources for 16-QAM based communication, wherein the table for allocating a number of transport blocks and / or allocated time domain resources for 16-QAM based communication corresponds to at least one of the following: a time domain resource assignment (TDRA) rearrangement relative to a table for allocating a number of transport blocks and / or allocated time domain resources defined for QPSK based communication, and a transport block redistribution relative to a table for allocating a number of transport blocks and / or allocated time domain resources defined for QPSK based communication, as described herein.
[0172] In an exemplary embodiment, the table for allocating transport blocks and / or the number of allocated time domain resources for 16-QAM based communications may correspond to a TDRA rearrangement (e.g., Alternative 1, Alternative 2 as will be described in detail later) relative to the table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communications (e.g., Table 16.5.1.2-2 as previously shown).
[0173] In this case, the TBS can be indicated using a TBS index and a time domain resource index, wherein the time domain resource index corresponds to a reduced number of allocated time domain resources compared to the number of allocated time domain resources corresponding to the same TBS required in the table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK-based communications, for example, reduced by half (for example, as will be described later, as shown in Table 1.1c for Alternative 1, Table 1.2b for Alternative 2).
[0174] Alternatively or additionally, the network node 16 transmits an indication to the wireless device 22 to use 16-QAM.
[0175] In an exemplary embodiment, the table for allocating transport blocks and / or the number of allocated time domain resources for 16-QAM based communication may correspond to a transport block redistribution relative to a table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication (e.g., Table 16.5.1.2-2 as previously shown) (e.g., as Alternative Scheme 3 which will be described in detail later).
[0176] In this case, a TBS may be indicated using a TBS index and a time domain resource index that are different from those TBS indexes and time domain resource indexes, respectively, for the same TBS required in a table indicating the number of allocated transport blocks and / or allocated time domain resources defined for QPSK-based communications (for example, as shown in Table 2.2a for Alternative Scheme 3 to be described later).
[0177] The transport block redistribution relative to a table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication may include:
[0178] A first subset of TBS indices (e.g., I ) in a table corresponding to the number of allocated transport blocks and / or allocated time domain resources previously defined for QPSK based communications (e.g., Table 16.5.1.2-2 as previously shown) that is reused for 16-QAM based communications TBS = 3, 5, 9, 12 and 13), but each TBS is indicated by a TBS index and / or a time domain resource index different from those TBS indexes and / or time domain resource indexes respectively required for the same TBS in a table indicating the number of allocated transport blocks and / or allocated time domain resources previously defined for QPSK-based communication, and optionally
[0179] One or more TBSs in a table for allocating transport blocks and / or allocated numbers of time domain resources previously defined for QPSK based communication that are skipped for 16-QAM based communication, the one or more skipped TBSs corresponding to a second subset (e.g., I ) of TBS indices in a table for allocating transport blocks and / or allocated numbers of time domain resources previously defined for QPSK based communication (e.g., Table 16.5.1.2-2 as previously shown). TBS = 3, 5, 9, 12, and 13); and optionally
[0180] A third subset of TBS indices (e.g., I ) for QPSK-based communications corresponding to a table previously defined for QPSK-based communications for allocating transport blocks and / or the number of allocated time domain resources (e.g., Table 16.5.1.2-2 as previously shown). TBS = 0, 1, 2, 4, 6, 7, 8, 10, and 11) of one or more TBS.
[0181] In an exemplary embodiment, the table for allocating transport blocks and / or the number of allocated time domain resources for 16-QAM based communication may correspond to TDRA rearrangement and transport block redistribution (e.g., as described in detail later in Alternative Scheme 4) relative to the table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication (e.g., as shown in Table 16.5.1.2-2 previously).
[0182] In this case, a TBS may be indicated using a TBS index and a time domain resource index that are different from those TBS indexes and time domain resource indexes that indicate the same TBS required in a table indicating the number of transport blocks and / or allocated time domain resources defined for QPSK-based communications (for example, as shown in Table 3.3a for Alternative Scheme 4, which will be described in detail later), wherein the time domain resource index corresponds to a reduced number of allocated time domain resources compared to the number of allocated time domain resources corresponding to the same TBS required in a table indicating the number of transport blocks and / or allocated time domain resources defined for QPSK-based communications.
[0183] The transport block redistribution relative to a table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication may include:
[0184] A first subset of TBS indices (e.g., I ) in a table corresponding to the number of allocated transport blocks and / or allocated time domain resources previously defined for QPSK based communications (e.g., Table 16.5.1.2-2 as previously shown) that is reused for 16-QAM based communications TBS= 3, 5, 9, 12 and 13), but each TBS is indicated by a TBS index and / or a time domain resource index different from those TBS indexes and / or time domain resource indexes respectively required for the same TBS in a table indicating the number of allocated transport blocks and / or allocated time domain resources previously defined for QPSK-based communication, and optionally
[0185] One or more TBSs in a table for allocating transport blocks and / or allocated numbers of time domain resources previously defined for QPSK-based communication (e.g., Table 16.5.1.2-2 as previously shown) that are skipped for 16-QAM-based communication, the one or more skipped TBSs corresponding to a second subset (e.g., I ) of TBS indices in a table for allocating transport blocks and / or allocated numbers of time domain resources previously defined for QPSK-based communication (e.g., Table 16.5.1.2-2 as previously shown). TBS = 3, 5, 9, 12, and 13); and optionally
[0186] A third subset of TBS indices (e.g., I ) for QPSK-based communications corresponding to a table previously defined for QPSK-based communications for allocating transport blocks and / or the number of allocated time domain resources (e.g., Table 16.5.1.2-2 as previously shown). TBS = 0, 1, 2, 4, 6, 7, 8, 10, and 11) of one or more TBS.
[0187] For the uplink (UL), the time domain resource index corresponds to the number of allocated time domain resource units.
[0188] In an exemplary embodiment, the network node 16 and the wireless device 22 may have previously performed QPSK-based communication. In block S701, the network node 16 may determine resource allocation for 16-QAM-based communication, for example, based on channel conditions, etc. As previously described in block S703, the network node 16 may indicate to the wireless device 22 the corresponding TBS and / or the number of allocated time domain resource units associated with the determined resource allocation using the TBS index and the time domain resource index determined according to the table for allocating transport blocks and / or the number of allocated time domain resource units for 16-QAM-based communication as previously described.
[0189] Therefore, the network node 16 can switch from QPSK-based uplink communication to 16-QAM-based uplink communication based on the determined resource allocation, wherein the 16-QAM-based uplink communication is allocated the same TBS as the TBS defined for the QPSK-based uplink communication, together with a reduced number of allocated time domain resource units corresponding to the same TBS required by the number of allocated transport blocks and / or allocated time domain resource units defined for the QPSK-based uplink communication, so as to reduce the SNR variation between the QPSK-based uplink communication and the 16-QAM-based uplink communication.
[0190] Alternatively or additionally, the network node 16 may receive 16-QAM based uplink transmissions from the wireless device 22 using a reduced number of allocated time domain resource units corresponding to the same TBS required by the number of allocated transport blocks and / or allocated time domain resource units defined for QPSK based uplink communications to achieve the same or similar code rate.
[0191] For the downlink (DL), the time domain resource index corresponds to the number of allocated subframes.
[0192] Similarly, in another exemplary embodiment, the network node 16 and the wireless device 22 may have previously performed QPSK-based communication. In block S701, the network node 16 may determine resource allocation for 16-QAM-based communication, for example, based on channel conditions, etc. As previously described in block S703, the network node 16 may indicate to the wireless device 22 the corresponding TBS and / or the number of allocated subframes associated with the determined resource allocation using the TBS index and the time domain resource index determined according to the table for allocating transport blocks and / or the number of allocated subframes for 16-QAM-based communication as previously described.
[0193] Therefore, the network node 16 can switch from QPSK-based downlink communication to 16-QAM-based downlink communication based on the determined resource allocation, wherein the 16-QAM-based downlink communication is allocated the same TBS as the TBS defined for the QPSK-based downlink communication, together with a reduced number of allocated subframes corresponding to the same TBS required by the number of allocated transport blocks and / or allocated subframes defined for the QPSK-based downlink communication, so as to reduce the SNR variation between the QPSK-based downlink communication and the 16-QAM-based downlink communication.
[0194] Alternatively or additionally, the network node 16 may transmit 16-QAM based downlink transmissions to the wireless device using a reduced number of allocated subframes as compared to the number of allocated subframes corresponding to the same TBS required by the number of allocated transport blocks and / or allocated subframes defined for QPSK based downlink communications.
[0195] Figure 8 is a flow chart of an exemplary process (method 800 ) in the wireless device 22 according to some embodiments of the present disclosure.
[0196] The one or more blocks and / or functions performed by the wireless device 22 may be performed by one or more elements of the wireless device 22, such as by the determination unit 34 in the processing circuit 84, the processor 86, the radio interface 82, etc. In one or more embodiments, the wireless device 22 is configured to receive (block S801) an indication of a TBS index and a time domain resource index from the network node 16, such as via the radio interface 82. Then, the wireless device 22 is configured, such as via one or more of the processing circuit 84, the processor 86, the determination unit 34, and the radio interface 82, to determine (box S803) the TBS and / or the number of allocated time domain resources using the received TBS index and the time domain resource index according to a table for allocating transport blocks and / or the number of allocated time domain resources for 16-QAM based communication to obtain resource allocation for 16-QAM based communication for the wireless device, wherein the table for allocating transport blocks and / or the number of allocated time domain resources for 16-QAM based communication corresponds to at least one of the following: TDRA rearrangement relative to a table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication, and transport block redistribution relative to a table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication, as described herein.
[0197] In an exemplary embodiment, the table for allocating transport blocks and / or the number of allocated time domain resources for 16-QAM based communications may correspond to a TDRA rearrangement (e.g., Alternative 1, Alternative 2 as will be described in detail later) relative to the table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communications (e.g., Table 16.5.1.2-2 as previously shown).
[0198] In this case, the TBS can be indicated using a TBS index and a time domain resource index, wherein the time domain resource index corresponds to a reduced number of allocated time domain resources compared to the number of allocated time domain resources corresponding to the same TBS required in the table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK-based communications, for example, reduced by half (for example, as will be described later, as shown in Table 1.1c for Alternative 1, Table 1.2b for Alternative 2).
[0199] Alternatively or additionally, the wireless device 22 may receive an indication from the network node 16 to use 16-QAM.
[0200] In an exemplary embodiment, the table for allocating transport blocks and / or the number of allocated time domain resources for 16-QAM based communication may correspond to a transport block redistribution relative to a table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication (e.g., Table 16.5.1.2-2 as previously shown) (e.g., as Alternative Scheme 3 which will be described in detail later).
[0201] In this case, a TBS may be indicated using a TBS index and a time domain resource index that are different from those TBS indexes and time domain resource indexes, respectively, for the same TBS required in a table indicating the number of allocated transport blocks and / or allocated time domain resources defined for QPSK-based communications (for example, as shown in Table 2.2a for Alternative Scheme 3 to be described later).
[0202] The transport block redistribution relative to a table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication may include:
[0203] A first subset of TBS indices (e.g., I ) in a table corresponding to the number of allocated transport blocks and / or allocated time domain resources previously defined for QPSK based communications (e.g., Table 16.5.1.2-2 as previously shown) that is reused for 16-QAM based communications TBS = 3, 5, 9, 12 and 13), but each TBS is indicated by a TBS index and / or a time domain resource index different from those TBS indexes and / or time domain resource indexes respectively required for the same TBS in a table indicating the number of allocated transport blocks and / or allocated time domain resources previously defined for QPSK-based communication, and optionally
[0204] One or more TBSs in a table for allocating transport blocks and / or allocated numbers of time domain resources previously defined for QPSK based communication that are skipped for 16-QAM based communication, the one or more skipped TBSs corresponding to a second subset (e.g., I ) of TBS indices in a table for allocating transport blocks and / or allocated numbers of time domain resources previously defined for QPSK based communication (e.g., Table 16.5.1.2-2 as previously shown). TBS = 3, 5, 9, 12, and 13); and optionally
[0205] A third subset of TBS indices (e.g., I ) for QPSK-based communications corresponding to a table previously defined for QPSK-based communications for allocating transport blocks and / or the number of allocated time domain resources (e.g., Table 16.5.1.2-2 as previously shown). TBS = 0, 1, 2, 4, 6, 7, 8, 10, and 11) of one or more TBS.
[0206] In an exemplary embodiment, the table for allocating transport blocks and / or the number of allocated time domain resources for 16-QAM based communication may correspond to TDRA rearrangement and transport block redistribution (e.g., as described in detail later in Alternative Scheme 4) relative to the table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication (e.g., as shown in Table 16.5.1.2-2 previously).
[0207] In this case, a TBS may be indicated using a TBS index and a time domain resource index that are different from those TBS indexes and time domain resource indexes that indicate the same TBS required in a table indicating the number of transport blocks and / or allocated time domain resources defined for QPSK-based communications (for example, as shown in Table 3.3a for Alternative Scheme 4, which will be described in detail later), wherein the time domain resource index corresponds to a reduced number of allocated time domain resources compared to the number of allocated time domain resources corresponding to the same TBS required in a table indicating the number of transport blocks and / or allocated time domain resources defined for QPSK-based communications.
[0208] The transport block redistribution relative to a table for allocating transport blocks and / or the number of allocated time domain resources defined for QPSK based communication may include:
[0209] A first subset of TBS indices (e.g., I ) in a table corresponding to the number of allocated transport blocks and / or allocated time domain resources previously defined for QPSK based communications (e.g., Table 16.5.1.2-2 as previously shown) that is reused for 16-QAM based communications TBS= 3, 5, 9, 12 and 13), but each TBS is indicated by a TBS index and / or a time domain resource index different from those TBS indexes and / or time domain resource indexes respectively required for the same TBS in a table indicating the number of allocated transport blocks and / or allocated time domain resources previously defined for QPSK-based communication, and optionally
[0210] One or more TBSs in a table previously defined for QPSK-based communication for allocating transport blocks and / or allocated numbers of time domain resources that are skipped for 16-QAM-based communication, the one or more skipped TBSs corresponding to a second subset (e.g., I ) of TBS indices in a table previously defined for QPSK-based communication for allocating transport blocks and / or allocated numbers of time domain resources that are skipped (e.g., Table 16.5.1.2-2 as previously shown). TBS = 3, 5, 9, 12, and 13); and optionally
[0211] A third subset of TBS indices (e.g., I ) for QPSK-based communications corresponding to a table previously defined for QPSK-based communications for allocating transport blocks and / or the number of allocated time domain resources (e.g., Table 16.5.1.2-2 as previously shown). TBS = 0, 1, 2, 4, 6, 7, 8, 10, and 11) of one or more TBS.
[0212] For the uplink (UL), the time domain resource index corresponds to the number of allocated time domain resource units.
[0213] In an exemplary embodiment, the wireless device 22 may calculate the transmit power by adding a power increment (eg, Δ TF,c (i)) to perform power boosting to reduce the difference in required SNR between QPSK-based uplink communication and 16-QAM-based uplink communication, ie, SNR variation.
[0214] In an exemplary embodiment, the network node 16 and the wireless device 22 may have previously performed QPSK-based uplink communication. As described above, the network node 16 may determine resource allocation for 16-QAM-based uplink communication, for example, based on channel conditions, etc., and indicate to the wireless device 22 the corresponding TBS and / or the number of allocated time domain resources associated with the determined resource allocation using the TBS index and the time domain resource index. Therefore, after receiving (block S801) the indication of the TBS index and the time domain resource index from the network node 16, the wireless device 22 may determine (block S803) the corresponding TBS and / or the number of allocated time domain resources using the received TBS index and the time domain resource index according to the table for allocating transport blocks and / or the number of allocated time domain resource units for 16-QAM-based uplink communication as described above, so as to obtain the resource allocation for 16-QAM-based uplink communication configured by the network node 16 for the wireless device 22.
[0215] Thus, the wireless device 22 may switch from QPSK-based uplink communication to 16-QAM-based uplink communication based on the obtained resource allocation, wherein the 16-QAM-based uplink communication is allocated the same TBS as that defined for the QPSK-based uplink communication, together with a reduced number of allocated time-domain resource units corresponding to the same TBS required by the number of allocated transport blocks and / or allocated time-domain resource units defined for the QPSK-based uplink communication, so as to reduce the SNR variation between the QPSK-based uplink communication and the 16-QAM-based uplink communication.
[0216] Alternatively or additionally, the wireless device 22 may transmit 16-QAM based uplink transmissions to the network node 16 using a reduced number of allocated time domain resource units corresponding to the same TBS required by the number of allocated transport blocks and / or allocated time domain resource units defined for QPSK based uplink communications to achieve the same or similar code rate.
[0217] For the downlink (DL), the time domain resource index corresponds to the number of allocated subframes.
[0218] Similarly, in another exemplary embodiment, the network node 16 and the wireless device 22 may have previously performed QPSK-based communication. As described above, after receiving (block S801) an indication of a TBS index and a time domain resource index from the network node 16, the wireless device 22 may determine (block S803) the corresponding TBS and / or the number of allocated subframes using the received TBS index and the time domain resource index according to the table for allocating transport blocks and / or the number of allocated subframes for 16-QAM-based uplink communication as described above, so as to obtain resource allocation for 16-QAM-based uplink communication configured by the network node 16 for the wireless device 22.
[0219] Thus, the wireless device 22 may switch from QPSK-based downlink communication to 16-QAM-based downlink communication based on the obtained resource allocation, wherein the 16-QAM-based downlink communication is allocated the same TBS as that defined for the QPSK-based downlink communication, together with a reduced number of allocated subframes corresponding to the same TBS required by the number of allocated transport blocks and / or allocated subframes defined for the QPSK-based downlink communication, so as to reduce the SNR variation between the QPSK-based downlink communication and the 16-QAM-based downlink communication.
[0220] Alternatively or additionally, the wireless device 22 may receive 16-QAM based downlink transmissions from the network node 16 using a reduced number of allocated subframes corresponding to the same TBS required by the number of allocated transport blocks and / or allocated subframes defined for QPSK based downlink communications.
[0221] Arrangements for supporting and implementing 16-quadrature amplitude modulation (16-QAM) based communications based on, for example, at least one of time domain resource assignment rearrangement and transport block redistribution have been generally described, details of these arrangements, functions and processes are provided below, and they may be implemented by a network node 16, a wireless device 22 and / or a host computer 24.
[0222] Embodiments provide support and implementation for 16-quadrature amplitude modulation (16-QAM) based communications based on, for example, at least one of time domain resource assignment rearrangement and transport block redistribution. In the following subsections from the "Time Domain Resource Assignment Rearrangement" subsection to the "Time Domain Resource Assignment Rearrangement with Transport Block Redistribution" subsection, one or more embodiments focused on the uplink (UL) are described, while in the "Time Domain Resource Assignment Rearrangement and Transport Block Redistribution for Introducing 16-QAM in DL" subsection, one or more embodiments applicable to the downlink (DL) (such as, for example, DL in NB-IoT) are described.
[0223] Time Domain Resource Reassignment
[0224] The 16-QAM modulation scheme doubles the number of bits per M-ary symbol relative to QPSK. Therefore, when the wireless device 22 and / or the network node 16 implements the 16-QAM modulation scheme, it is possible to reduce the time domain resource utilization by half compared to the time domain resources used when using the QPSK modulation scheme.
[0225] Alternative 1
[0226] When the number of subcarriers allocated by UL is not 1, I TBS =I MCS , and index I RU The number of resource units (RUs) mapped to the allocation according to Table 16.5.1.1-2 in 3GPP TS 36.213 v.16.0.0. That is, I MCS The number of RUs is as follows:
[0227] Table 1.1a: Number of RUs for QPSK in UL
[0228]
[0229] In Alternative 1, I MCS The range is from 10 to 13 in steps of 1, and for the “number of RUs”, the following principles apply to Table 1a:
[0230] - The number of RUs is determined by Ceil (Num_of_RUs / 2) to produce the following table:
[0231] Table 1.1b: Rearrangement according to number of Alt-1RUs for 16-QAM in UL
[0232]
[0233] The above rearrangement can reduce the resource utilization in the time domain while keeping the achievable code rate of 16-QAM no higher than the code rate provided by QPSK. Table 1.1c shows the TBS table for 16-QAM in the UL according to Alternative 1 (Alt-1), while Table 1d compares the achievable code rates achieved by QPSK and 16-QAM respectively on the same transport block.
[0234] Table 1.1c: TBS table for 16-QAM in UL according to Alternative 1
[0235]
[0236] Table 1.1d: Code rates achievable by A) QPSK, B) 16-QAM in the UL according to Alternative 1
[0237] A) Code rates achievable by QPSK
[0238]
[0239] B) Code rate achievable by 16-QAM in UL according to Alternative 1
[0240]
[0241] If alternative 1 is implemented to introduce 16-QAM in the UL for NB-IoT, an indication to the wireless device 22, such as via one or more of the processing circuit 68, the processor 70, the radio interface 62, the indication unit 32, etc., as to whether the wireless device 22 has been instructed to use QPSK or 16-QAM may be required (e.g., via 1 bit in the DCI), i.e., the wireless device 22 may receive the indication, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the determination unit 34, etc. This means that when the network node 16 has instructed the wireless device 22 to use QPSK, such as via one or more of the processing circuit 68, the processor 70, the radio interface 62, the indication unit 32, etc., the legacy TBS table will be fully available and used, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the determination unit 34, etc., as performed in the existing system (according to Table 1.1a, I MCS 13 in steps of 1, together with the RU), while when 16-QAM is used, only I in steps of 1 from 10 to 13 will be used together with the RU rearrangement as shown in Table 1.1b. MCS .
[0242] Alternative 2
[0243] In Alternative 2, I MCS The range is from 10 to 13 in steps of 1, and for the “number of RUs”, the following principles apply to Table 1.1a:
[0244] - The first, third and fifth columns are not used, and for the rest, the number of RUs is determined by Num_of_RUs / 2 to produce the following results:
[0245] Table 1.2a: Rearrangement of the number of RUs according to alternative 2 for 16-QAM in UL
[0246]
[0247] Alternative 2 also reduces (e.g., significantly reduces) resource utilization in the time domain, keeping the achievable code rate for 16-QAM the same as the code rate provided by QPSK. Table 1.2b shows the TBS table for 16-QAM in the UL according to Alternative 2, while Table 1.2c compares the achievable code rates achieved by QPSK and 16-QAM, respectively, on the same transport block.
[0248] Table 1.2b: TBS table for 16-QAM in UL according to alternative 2
[0249]
[0250] Table 1.2c: Code rates achievable by A) QPSK, B) 16-QAM in the UL according to Alt-2
[0251] A) Code rates achievable by QPSK
[0252]
[0253] B) Code rates achievable by 16-QAM in UL according to Alt-2
[0254]
[0255] If alternative 2 (which is a subset of alternative 1) is implemented to introduce 16-QAM in the UL for NB-IoT, an indication to the wireless device 22 (e.g., via 1 bit in the DCI), such as via one or more of the processing circuit 68, the processor 70, the radio interface 62, the indication unit 32, etc., as to whether the wireless device 22 has been instructed to use QPSK or 16-QAM, may be required, i.e., the wireless device 22 may receive the indication, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, etc. This means that when the network node 16 has indicated the wireless device 22 to use QPSK, such as via one or more of the processing circuit 68, the processor 70, the radio interface 62, the determination unit 31, the indication unit 32, etc., the legacy TBS table will be fully available and used as used in existing systems (as per Table 1.1a, I MCS 1 from 0 to 13 in steps of 1, together with the RU), while when 16-QAM is used, only I in steps of 1 from 10 to 13 will be used together with the RU rearrangement as shown in Table 1.2a. MCS .
[0256] Performance comparison between Alternative 1 and Alternative 2
[0257] The following table illustrates the BLER performance difference between Alternative 1 and Alternative 2 one-to-one.
[0258] Table 1.3a: Comparison of BLER performance of Alternative 1 (Alt-1) and Alternative 2 (Alt-2)
[0259] Alternative 1
[0260]
[0261] Alternative 2
[0262]
[0263] Figure 9-12 is an example illustrating the performance comparison between Alt-1 and Alt-2.
[0264] Figure 9-12 A side-by-side comparison of Alt-1 and Alt-2 in the example above shows that: In Alt-1, even with the same I TBS (Recall I TBS =I MCS ), there will be a large SNR change when switching from one RU allocation to another. On the other hand, in Alt-2, if the same I TBS , then when, for example, the wireless device 22 switches from using one RU allocation to another RU allocation, there is no overall SNR change. TBS = 12 and the number of allocated RUs = 2, the only significant change is observed, as the evaluated TBS entry leads to a higher code rate compared to the code rate obtained when allocating a different number of RUs (see Table 1.2c, where, at this point, neither Alt-1 nor Alt-2 performs any TBS redistribution).
[0265] Even keeping Alternative 2, in Table 1.3b below, it is shown that Alt-2 requires a significantly larger SNR than that required for QPSK.
[0266] Table 1.3b: BLER performance comparison between QPSK and Alt-2
[0267]
[0268] In order to reduce the SNR gap between 16-QAM and QPSK in the UL, it may be possible to perform a power increase, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the determination unit 34, etc., to move the SNR of 16-QAM towards the SNR required by QPSK. In LTE, as the number of bits per resource element (RE) increases with higher order modulation schemes, the Δ TFis used to increase power, so in the case of using 16-QAM in the UL, similar elements can be incorporated into the following equation for NB-IoT (which is described in wireless communication standards such as 3GPP TS 36.213 v16.0.0):
[0269] For serving the community NB-IoT UL time slot i The transmit power of the wireless device 22 in the NPUSCH transmission Given by:
[0270] For NPUSCH (re)transmissions corresponding to random access response grants, if enhanced random access power control is not applied, and for all other NPUSCH transmissions except NPUSCH transmissions using preconfigured uplink resources, when the number of repetitions of the allocated NPUSCH RU is greater than 2:
[0271] [dBm]
[0272] otherwise
[0273] [dBm]
[0274] Since in the above equation, the transmit power of the wireless device 22 is related to the time slot i , so in one form, Alt-2 may include a merge Δ TF,c (i) = 10log 10 (X), where X can be an integer or an integer with a fractional part, for example, X = 2. TF It can also be obtained from simulations, for example, by using the margins (dB) found in Table 1.3b above comparing 16-QAM with rearranged RUs to QPSK. TF Incorporates the transmit power equation for the wireless device 22 used in NB-IoT.
[0275] [dBm]
[0276] The above power boost solution, in which a new term (in bold) is introduced into the transmit power equation of the wireless device 22, is compatible and applicable to one or more embodiments described herein that introduce 16-QAM in the UL for NB-IoT.
[0277] Transport Block Redistribution
[0278] As mentioned above, for a given I MCSand different numbers of allocated RUs, Alt-2 can reduce the large variation of SNR. However, the performance evaluation described in the "Performance Comparison of Alt-1 and Alt-2" section indicates that even if Alt-2 meets the above design criteria, 16-QAM based on Alt-2 may still require a much larger SNR (e.g., >6dB) than that required by QPSK to achieve a 10% BLER target.
[0279] In order to mitigate the large difference between 16-QAM and QPSK in terms of the SNR required to meet the 10% BLER target, a solution based on transport block redistribution (which corresponds to Alternative 3 (Alt-3)) is described in this subsection, which solution consists in keeping the number of allocated RUs unchanged relative to QPSK (i.e., 1, 2, 3, 4, 5, 6, 8, 10), and creating a TBS table, such as for storage at the wireless device 22, in which some existing TBS entries and numbers of allocated RUs are skipped, some others are redistributed, and in which a set of entries is used only for QPSK, while complementary entries are used only for 16-QAM in the UL.
[0280] The design goals of Alt-3 include: MCS and changing the number of allocated RUs, and also includes avoiding large SNR changes when the wireless device 22 switches from QPSK to 16-QAM in the UL and vice versa, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the determination unit 34, etc. In order to meet the above two design criteria in Alt-3, when a given I is selected MCS When the number of allocated RUs is changed, the transport block sizes available in the existing system for Cat-NB2 devices are reused but redistributed so that the same / similar code rates and similar levels of code rates are achievable on TBS entries that cross near the boundary between 16-QAM and QPSK in the UL. MCS = 3, 5, 9, 12, and 13 and their associated TBS entries for all possible RU assignments are skipped, so the complete set of legacy TBSs is no longer available for QPSK. That is, Alt-3 reserves 14 I MCS 9 of the indices can be used for QPSK (such as by renumbering them so that they start at 0 and end / end at 8), while the I from 9 to 13 MCS Index is the I used with 16-QAM in UL MCS An index including a redistribution of available TBS entries for Cat-NB2 devices.
[0281] Table 2.2a shows by way of example (note: the final selection of TBS entries may be changed until the best performance is found through simulation) a TBS table for both 16-QAM and QPSK in the UL according to Alt-3, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the determination unit 34, etc., while Table 2.2b shows the achievable code rates achieved by QPSK and 16-QAM, respectively, in their corresponding parts in the table.
[0282] Table 2.2a: TBS table for 16-QAM and QPSK in UL according to Alt-3
[0283]
[0284] Table 2.2b: Code rates achievable by 16-QAM and QPSK in UL on their corresponding TBS entries according to Alt-3
[0285]
[0286] If Alt-3 is implemented in 16-QAM in UL for NB-IoT, then there is no need to introduce an indication of using QPSK or 16-QAM to the wireless device 22. This means that with Alt-3, as long as the 16-QAM feature is enabled, the wireless device will reference / use a TBS table (e.g., Table 2.2a) containing TBS entries for both 16-QAM and QPSK in UL, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the determination unit 34, etc., where the TBS entry for the specific TBS entry in the TBS table will be pointed to by the index I in the DCI. MCS and I RU To implicitly provide the choice of modulation order.
[0287] Time domain resource assignment rearrangement together with transport block redistribution
[0288] With Alternative 4 (Alt-4), a slight variation on Alt-3 is introduced by allocating half the number of RUs available for QPSK to 16-QAM when the number of RUs is >= 6, which helps ensure that for a given TBS that can be used with 16-QAM, time domain resource utilization remains minimal. In one or more embodiments, for a given TBS using Alt-3, 16-QAM may use half or twice the number of allocated RUs in some cases.
[0289] Table 3.3a shows an example of a TBS table for both 16-QAM and QPSK to be used in the UL according to Alt-4, while Table 3.3b shows the achievable code rates achieved by QPSK and 16-QAM in their corresponding parts of the table, respectively. In one or more embodiments, the last / final selection of the TBS entry may be changed until the best performance is found through simulation.
[0290] Table 3.3a: TBS table for 16-QAM and QPSK in UL according to Alt-4
[0291]
[0292] Table 3.3b: Code rates achievable by 16-QAM and QPSK in UL on their corresponding TBS entries according to Alt-4
[0293]
[0294] Alt-4 can be considered as a sub-case of Alt-3. For example, with Alt-3, it is possible to use 10 RUs or 5 RUs to transmit a TBS equal to 2536 bits using 16-QAM, while with Alt-4, 5 RUs can always be used to transmit a TBS equal to 2536 bits.
[0295] If Alt-4 is implemented to introduce 16-QAM in the UL for NB-IoT, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the determination unit 34, etc., then there is no need to introduce an indication of using QPSK or 16-QAM to the wireless device 22. This means that with Alt-4, as long as the 16-QAM feature is enabled, the wireless device 22 will reference a TBS table (e.g., Table 3.3a) containing TBS entries for both 16-QAM and QPSK in the UL, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the determination unit 34, etc., where the selection of the modulation order will be determined by an index I in the DCI pointing to a specific TBS entry in the TBS table. MCS and I RU Given implicitly.
[0296] Time domain resource assignment rearrangement and transport block redistribution for introducing 16-QAM in DL
[0297] The above subsections describe various methods / processes / solutions for incorporating 16-QAM in the UL for NB-IoT. The "5.4 Time Domain Resource Assignment Rescheduling and Transport Block Redistribution for Introducing 16-QAM in the DL" subsection describes how to introduce 16-QAM in the DL for NB-IoT using the concepts / principles in the above subsections.
[0298] The following bullet points describe what would be different if the same solution described for the UL were adopted in the DL.
[0299] - Time domain resource assignment rescheduling:
[0300] The design principles described in subsections: Alternative 1, Alternative 2 and "Performance comparison of Alt-1 and Alt-2" can be adopted in DL, which is that the number of allocated subframes for NPDSCH will be reduced by, for example, half the time domain resources allocated when using QPSK. Table 16.4.1.3-1 of 3GPP TS 36.213 v16.0.0 can be used as a reference for performing time domain resource assignment rearrangement.
[0301] - Transport block redistribution:
[0302] The design principles described in the "Transport Block Redistribution" subsection for Alt-3 can be adopted in DL, and Table 16.4.1.5.1-1 of 3GPP TS 36.213 v16.0.0 is used as a reference to perform transport block redistribution.
[0303] - Time domain resource assignment rearrangement along with transport block redistribution.
[0304] The design principles described in the "Time domain resource assignment rearrangement together with transport block redistribution" subsection for Alt-4 can be adopted in the DL, as is Table 16.4.1.3-1 used as a reference for performing time domain resource assignment rearrangement, and Table 16.4.1.5.1-1 of 3GPP TS 36.213 v16.0.0, which is used as a reference for performing transport block redistribution.
[0305] Furthermore, any of one or more of the above embodiments (i.e., Alt-1, Alt-2, Alt-3, or Alt-4) may be used to introduce 16-QAM for NB-IoT in the DL to address differences in deployment patterns. Furthermore, one or more of the embodiments described herein (i.e., Alt-2, Alt-3, Alt-4) will likely increase DL throughput without having to introduce a TBS larger than the maximum supported in existing systems for Cat-NB2 devices.
[0306] Therefore, the present disclosure describes one or more embodiments for supporting 16-QAM for unicast in UL and DL for NB-IoT, as follows:
[0307] - Time domain resource assignment rescheduling:
[0308] 16-QAM for unicast in UL: When 16-QAM is used, the number of allocated resource units is reduced by, for example, half relative to the number of allocated resource units when QPSK is used.
[0309] ▪To reduce the gap in required SNR between QPSK and 16-QAM, a new component (e.g., power increase) may be added to the transmit power control equation of the wireless device 22 in NB-IoT to increase the power by X dB when using 16-QAM.
[0310] 16-QAM for unicast in DL: When using 16-QAM, the number of allocated subframes for NPDSCH is reduced, for example, by half relative to the allocated subframes when using QPSK.
[0311] - Transport block redistribution:
[0312] 16-QAM for unicast in UL: When 16-QAM is used, (I TBS , I RU ) The selected TBS entry does not have the same position in the TBS table as that used for QPSK (i.e. (I TBS , I RU ) position), while some other entries will be skipped.
[0313] 16-QAM for unicast in DL: When 16-QAM is used, (I TBS , I SF ) The selected TBS entry does not have the same position in the TBS table as that used for QPSK (i.e., (I TBS , I SF ) position), while some other entries will be skipped.
[0314] - Time domain resource assignment rearrangement along with transport block redistribution.
[0315] 16-QAM for unicast in UL: When 16-QAM is used, the number of allocated resource units (RUs) is reduced (e.g., halved) and is determined by (I TBS , I RU ) The selected TBS entry does not have the same position in the TBS table as that used for QPSK (i.e. (I TBS , I RU )Location).
[0316] 16-QAM for unicast in DL: When 16-QAM is used, the number of allocated subframes for NPDSCH is reduced (e.g., reduced by half) and is given by (I TBS , I RU ) The selected TBS entry does not have the same position in the TBS table as that used for QPSK (i.e., (I TBS , I RU )Location).
[0317] In an embodiment, a network node is configured to communicate with a wireless device. The network node is configured to and / or comprises a radio interface and / or comprises a processing circuit configured to:
[0318] Support for 16-quadrature amplitude modulation (16-QAM) based communications based on at least one of the following:
[0319] Time domain resource assignment rescheduling; and
[0320] Transport blocks are redistributed.
[0321] As will be appreciated by those skilled in the art, the concepts described herein may be embodied as methods, data processing systems, computer program products, and / or computer storage media storing executable computer programs. Thus, the concepts described herein may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects, all of which are collectively referred to herein as "circuits" or "modules." Any process, step, action, and / or functionality described herein may be performed by and / or associated with a corresponding module, which may be implemented in software and / or firmware and / or hardware. In addition, the present disclosure may take the form of a computer program product on a tangible computer-usable storage medium having a computer program code embodied in the medium that may be executed by a computer. Any suitable tangible computer-readable medium may be utilized, including a hard disk, a CD-ROM, an electronic storage device, an optical storage device, or a magnetic storage device.
[0322] 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 frame of the flowchart illustration and / or block diagram and the combination of frames in the flowchart illustration and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer (thereby creating a special-purpose computer), a special-purpose computer, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device create a component for implementing the function / action specified in one or more flowcharts and / or block diagram frames.
[0323] These computer program instructions may also be stored in a computer-readable memory or storage medium, which can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including instruction components, which implement the functions / actions specified in one or more flowcharts and / or block diagrams.
[0324] The computer program instructions may also be loaded onto a computer or other programmable data processing device to cause a series of operable steps to be performed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions / actions specified in one or more flowcharts and / or block diagram blocks.
[0325] It is to be understood that the functions / actions indicated in the blocks may not occur in the order indicated in the operational diagrams. For example, two blocks shown in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending on the functionality / actions involved. Although some of the diagrams in the figures include arrows on communication paths to illustrate the primary direction of communication, it is to be understood that communication may occur in the opposite direction of the arrows depicted.
[0326] The computer program code for performing the operation of the concepts described herein can be written in an object-oriented programming language such as Java® or C++. However, the computer program code for performing the operation of the present disclosure can also be written in a conventional procedural programming language such as "C" programming language. The program code can be executed completely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or completely on a remote computer. In the latter scenario, the remote computer can be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., by using the Internet of an Internet service provider).
[0327] In conjunction with the above description and the accompanying drawings, many different embodiments have been disclosed herein. It will be understood that it would be overly repetitive and confusing to literally describe and illustrate every combination and subcombination of these embodiments. Thus, all embodiments can be combined in any manner and / or combination, and this specification including the accompanying drawings should be interpreted as constituting a complete written description of all combinations and subcombinations of the embodiments described herein and the manner and process of making and using them, and should support claims to any such combination or subcombination.
[0328] Those skilled in the art will recognize that the embodiments described herein are not limited to what has been specifically shown and described herein above. In addition, unless otherwise mentioned above, it should be noted that all drawings are not to scale. In view of the above teachings, various modifications and variations are possible.
Claims
1. A method (700) performed by a network node configured to communicate with a wireless device, the method (700) comprising: Determining (S701) resource allocation for communication based on 16-quadrature amplitude modulation 16-QAM for the wireless device; as well as indicating (S703) to the wireless device a transport block size TBS and / or a number of allocated time domain resources associated with the determined resource allocation using a TBS index and a time domain resource index, wherein the TBS index and the time domain resource index correspond to values in a table for allocating transport blocks and / or a number of allocated time domain resources for the 16-QAM based communication, wherein the table for allocating transport blocks and / or a number of allocated time domain resources for the 16-QAM based communication corresponds to a time domain resource assignment rearrangement relative to the table for allocating transport blocks and / or a number of allocated time domain resources defined for QPSK based communication, and The TBS is indicated using the TBS index and the time domain resource index, wherein the time domain resource index corresponds to a reduced number of allocated time domain resources compared to the number of allocated time domain resources corresponding to the same TBS required in the table of the number of allocated transport blocks and / or allocated time domain resources defined for the QPSK-based communication.
2. The method (700) of claim 1, further comprising: An indication to use 16-QAM is transmitted to the wireless device.
3. The method (700) of claim 1, wherein: The TBS is indicated using the TBS index and the time domain resource index, which are respectively different from those TBS indices and time domain resource indices indicating the same TBS required in the table indicating the number of allocated transport blocks and / or allocated time domain resources defined for the QPSK-based communication, wherein the time domain resource index corresponds to a reduced number of allocated time domain resources compared to the number of allocated time domain resources corresponding to the same TBS required in the table indicating the number of allocated transport blocks and / or allocated time domain resources defined for the QPSK-based communication.
4. The method (700) according to any one of claims 1 to 3, wherein: The transport block redistribution relative to the table defined for the QPSK based communication for allocating transport blocks and / or the number of allocated time domain resources comprises: one or more TBSs of a first subset of the TBS indices in the table of allocated transport blocks and / or allocated numbers of time domain resources defined for the QPSK based communication that are reused for the 16-QAM based communication, but each TBS is indicated by a TBS index and / or time domain resource index that is different from those TBS indices and / or time domain resource indices that indicate the same TBS required in the table of allocated transport blocks and / or allocated numbers of time domain resources defined for the QPSK based communication, respectively; and optionally One or more TBSs in the table for allocating the number of transmission blocks and / or the allocated time domain resources defined for the QPSK-based communication are skipped for the 16-QAM-based communication, the one or more skipped TBSs corresponding to a second subset of TBS indices in the table for allocating the number of transmission blocks and / or the allocated time domain resources defined for the QPSK-based communication; and optionally one or more TBSs corresponding to a third subset of TBS indices in the table for allocating the number of transmission blocks and / or the allocated time domain resources defined for the QPSK-based communication for the QPSK-based communication.
5. The method (700) according to any one of claims 1 to 3, wherein: In the case where the 16-QAM based communication is for downlink, the time domain resource index corresponds to the number of allocated subframes, the method (700) further comprises: Based on the determined resource allocation, switch from QPSK-based downlink communication to 16-QAM-based downlink communication, wherein the 16-QAM-based downlink communication is allocated the same TBS as the TBS defined for the QPSK-based downlink communication, together with a reduced number of allocated subframes corresponding to the same TBS required by the number of allocated transport blocks and / or allocated subframes defined for the QPSK-based downlink communication, so as to reduce the signal-to-noise ratio (SNR) variation between the QPSK-based downlink communication and the 16-QAM-based downlink communication.
6. The method (700) of claim 5, further comprising: A 16-QAM based downlink transmission is transmitted to the wireless device using a reduced number of allocated subframes as compared to the number of allocated subframes corresponding to the same TBS required by the number of allocated transport blocks and / or allocated subframes defined for QPSK based downlink communications.
7. A method (800) performed by a wireless device configured to communicate with a network node, the method (800) comprising: Receiving (S801) an indication of a TBS index and a time domain resource index from the network node; determining (S803) a transport block size TBS and / or a number of allocated time domain resources using the received TBS index and the time domain resource index according to a table for allocating transport blocks and / or a number of allocated time domain resources for communication based on 16-quadrature amplitude modulation, 16-QAM, so as to obtain resource allocation for the 16-QAM based communication for the wireless device, wherein the table for allocating transport blocks and / or a number of allocated time domain resources for the 16-QAM based communication corresponds to a time domain resource assignment rearrangement relative to the table for allocating transport blocks and / or a number of allocated time domain resources defined for QPSK based communication, and The TBS and / or the number of allocated time domain resources are determined using the TBS index and the time domain resource index, wherein the time domain resource index corresponds to a reduced number of allocated time domain resources compared to the number of allocated time domain resources corresponding to the same TBS required in the table of the number of allocated transport blocks and / or allocated time domain resources defined for the QPSK-based communication.
8. The method (800) of claim 7, further comprising: An indication to use 16-QAM is received from the network node.
9. The method (800) of claim 7, wherein: The TBS and / or the number of allocated time domain resources are determined using the TBS index and the time domain resource index, which are respectively different from those TBS indices and time domain resource indices indicating the same TBS required in the table indicating the number of allocated transport blocks and / or the number of allocated time domain resources defined for the QPSK-based communication, wherein the time domain resource index corresponds to a reduced number of allocated time domain resources compared to the number of allocated time domain resources corresponding to the same TBS required in the table for allocating transport blocks and / or the number of allocated time domain resources defined for the QPSK-based communication.
10. The method (800) according to any one of claims 7 to 9, wherein: The transport block redistribution relative to the table defined for the QPSK based communication for allocating transport blocks and / or the number of allocated time domain resources comprises: One or more TBSs of a first subset of the TBS indices in the table for allocating the number of transport blocks and / or allocated time domain resources defined for the QPSK-based communication are reused for the 16-QAM-based communication, but each TBS is indicated by a TBS index and / or resource index that is different from those time domains of the same TBS required in the table for allocating the number of transport blocks and / or allocated time domain resources defined for the QPSK-based communication; and one or more TBSs in the table for allocating the number of transport blocks and / or allocated time domain resources defined for the QPSK-based communication are optionally skipped for the 16-QAM-based communication, the one or more skipped TBSs corresponding to a second subset of the TBS indices in the table for allocating the number of transport blocks and / or allocated time domain resources defined for the QPSK-based communication; and one or more TBSs of a third subset of the TBS indices in the table for allocating the number of transport blocks and / or allocated time domain resources defined for the QPSK-based communication are optionally used for the QPSK-based communication.
11. The method (800) according to any one of claims 7 to 9, wherein: In the case where the 16-QAM based communication is used for uplink, the time domain resource index corresponds to the number of allocated time domain resource units, the method (800) further comprises: Based on the obtained resource allocation, switch from QPSK-based uplink communication to 16-QAM-based uplink communication, wherein the 16-QAM-based uplink communication is allocated the same TBS as the TBS defined for the QPSK-based uplink communication, together with a reduced number of allocated time domain resource units corresponding to the same TBS required by the number of allocated transport blocks and / or allocated time domain resource units defined for the QPSK-based uplink communication, so as to reduce the signal-to-noise ratio SNR variation between the QPSK-based uplink communication and the 16-QAM-based uplink communication.
12. The method (800) of claim 11, further comprising: A 16-QAM based uplink transmission is transmitted to the network node using a reduced number of allocated time domain resource units compared to the number of allocated time domain resource units corresponding to the same TBS required by the number of allocated transport blocks and / or allocated time domain resource units defined for QPSK based uplink communication.
13. The method (800) of claim 11, further comprising: Power boosting is performed by adding a power increment in the calculation of the transmit power of the wireless device to reduce the difference in required signal-to-noise ratio (SNR) between the QPSK-based uplink communication and the 16-QAM-based uplink communication.
14. The method (800) of any one of claims 7 to 9, wherein: In the case where the 16-QAM based communication is for downlink, the time domain resource index corresponds to the number of allocated subframes, the method (800) further comprises: Based on the obtained resource allocation, switch from QPSK-based downlink communication to 16-QAM-based downlink communication, wherein the 16-QAM-based downlink communication is allocated the same TBS as the TBS defined for the QPSK-based downlink communication, together with a reduced number of allocated subframes corresponding to the same TBS required by the number of allocated transport blocks and / or allocated subframes defined for the QPSK-based downlink communication, so as to reduce the signal-to-noise ratio SNR variation between the QPSK-based downlink communication and the 16-QAM-based downlink communication.
15. The method (800) of claim 13, further comprising: A 16-QAM based downlink transmission is received from the network node using a reduced number of allocated subframes compared to the number of allocated subframes corresponding to the same TBS required by the number of allocated transport blocks and / or allocated subframes defined for QPSK based downlink communications.
16. A network node (16), comprising: at least one processor (70), and at least one memory (72) storing instructions that, when executed on the at least one processor (70), cause the network node (16) to: determining resource allocation for 16-quadrature amplitude modulation 16-QAM based communications for the wireless device; and indicating to the wireless device a transport block size TBS and / or a number of allocated time domain resources associated with the determined resource allocation using a TBS index and a time domain resource index, wherein the TBS index and the time domain resource index correspond to values in a table for allocating transport blocks and / or a number of allocated time domain resources for the 16-QAM based communication, wherein the table for allocating transport blocks and / or a number of allocated time domain resources for the 16-QAM based communication corresponds to a time domain resource assignment rearrangement relative to the table for allocating transport blocks and / or a number of allocated time domain resources defined for QPSK based communication, and The TBS and / or the number of allocated time domain resources are determined using the TBS index and the time domain resource index, wherein the time domain resource index corresponds to a reduced number of allocated time domain resources compared to the number of allocated time domain resources corresponding to the same TBS required in the table of the number of allocated transport blocks and / or allocated time domain resources defined for the QPSK-based communication.
17. The network node (16) of claim 16, wherein: The instructions, when executed on the at least one processor (70), further cause the network node (16) to perform a method according to any one of claims 2 to 6.
18. A wireless device (22), comprising: at least one processor (86), and at least one memory (88) storing instructions that, when executed on the at least one processor (86), cause the wireless device (22) to: receiving an indication of a TBS index and a time domain resource index from a network node; determining a transport block size TBS and / or a number of allocated time domain resources using the received TBS index and the time domain resource index according to a table for allocating transport blocks and / or a number of allocated time domain resources for 16-quadrature amplitude modulation, 16-QAM, based communications to obtain resource allocation for the 16-QAM based communications for the wireless device, wherein the table for allocating transport blocks and / or a number of allocated time domain resources for the 16-QAM based communications corresponds to a rearrangement of time domain resource assignments relative to the table for allocating transport blocks and / or a number of allocated time domain resources defined for QPSK based communications, and The TBS and / or the number of allocated time domain resources are determined using the TBS index and the time domain resource index, wherein the time domain resource index corresponds to a reduced number of allocated time domain resources compared to the number of allocated time domain resources corresponding to the same TBS required in the table of the number of allocated transport blocks and / or allocated time domain resources defined for the QPSK-based communication.
19. The wireless device (22) of claim 18, wherein: The instructions, when executed on the at least one processor (86), also cause the wireless device (22) to perform the method of any one of claims 8 to 15.
20. A computer readable storage medium having stored thereon computer program instructions which, when executed by at least one processor, cause the at least one processor to perform the method of any one of claims 1 to 7 or 8 to 15.
