16qam transmission for nbiot

Abstract

Methods and apparatuses for transmitting or receiving data for NB-IoT supporting 16QAM modulation are disclosed. One method includes receiving a control signal, wherein the control signal includes a MCS index and a resource assignment index; and receiving a control signal, wherein the control signal includes a MCS index and a resource assignment index, wherein the transport block size is determined by a combination of a transport block size index and the resource assignment index, and the transport block size index is determined by at least one of the MCS index and the resource assignment index.

Description

TECHNICAL FIELD

[0001] The subject matter disclosed herein relates generally to wireless communications, and more particularly to 16QAM transmission for NBIOT. BACKGROUND

[0002] The following abbreviations are defined herein, at least some of which are mentioned within the description below: Third Generation Partnership Project (3GPP), European Telecommunications Standards Institute (ETSI), Frequency Division Duplex (FDD), Frequency Division Multiple Access (FDMA), Long Term Evolution (LTE), New Radio (NR), Very Large Scale Integration (VLSI), Random Access Memory (RAM), Read Only Memory (ROM), Erasable Programmable Read Only Memory (EPROM or Flash memory), Compact Disc Read Only Memory (CD-ROM), Local Area Network (LAN), Wide Area Network (WAN), Personal Digital Assistant (PDA), User Equipment (UE), Uplink (UL), Evolved Node B (eNB), Next Generation Node B (gNB), Downlink (DL), Central Processing Unit (CPU), Graphics Processing Unit (GPU), Field Programmable Gate Array (FPGA), Dynamic RAM (DRAM), Synchronous Dynamic RAM (SDRAM), Static RAM (SRAM), Liquid Crystal Display (LCD), Light Emitting Diode (LED), Organic LED (OLED), Orthogonal Frequency Division Multiplexing (OFDM), Radio Resource Control (RRC), Reference Signal (RS), Single Carrier Frequency Division Multiple Access (SC-FDMA), Time Division Duplex (TDD), Time Division Multiplexing (TDM), User Equipment / Device (Mobile Terminal) (UE), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), Internet of Things (IoT), Narrow Band Internet of Things (NB-IoT or NBIoT), Long Term Evolution (LTE), Narrow Band (NB), Narrow Band Primary Synchronization Signal (NPSS), Narrow Band Secondary Synchronization Signal (NSSS), Narrow Band Physical Broadcast Channel (NPBCH or NB-PBCH), System Information (SI), System Information Block (SIB), System Information Block Type 1-NB (NB-SIB1), Physical Downlink Shared Channel (PDSCH), Narrow Band Physical Downlink Shared Channel (NPDSCH), Physical Uplink Shared Channel (PUSCH), Narrow Band Physical Uplink Shared Channel (NPUSCH), Physical Resource Block (PRB), Universal Mobile Telecommunications System (UMTS), Evolved UMTS Terrestrial Radio Access (E-UTRA or EUTRA), Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), Quadrature Amplitude Modulation (QAM), Transport Block Size (TBS), Modulation and Coding Scheme (MCS), Downlink Control Information (DCI).

[0003] In NB-IoT Rel. 16, for NPDSCH, the number of resource units (N SF ) and subcarriers to be used in time and frequency domain are determined as follows when coded data is transmitted from a base unit (e.g., gNB) to a remote unit (e.g., UE):

[0004] Table 1 indicates the number of resource units (N SF ) determined by a resource assignment (I SF ). The resource assignment (I SF ) is indicated by 3 bits through a corresponding control signal (e.g., DCI format N1). The resource units for NPDSCH are 1 ms in time domain, and 1 PRB (12 subcarriers) in frequency domain.

[0005]

[0006] Table 1

[0007] The subcarriers to be used are common 12 subcarriers (each subcarrier is 15 KHz).

[0008] Coded data is transmitted in a transport block size (TBS), and is transmitted by using a modulation type such as QPSK. The modulation type is associated with a modulation order (Q m ). For example, the modulation order (Q m ) of QPSK is 2. In this application, the modulation order (Q m ) means a modulation type.

[0009] The TBS is determined by a TBS index (I TBS ) and a resource assignment (I SF ). The TBS index (I TBS ) is determined by an MCS (Modulation and Coding Scheme) index (I MCS ). When QPSK (Q m = 2) is assumed as a modulation type, I TBS = I MCS . The MCS index (I MCS ) is indicated by 4 bits through a corresponding control signal (e.g., DCI format N1).

[0010] Table 2 indicates a transport block size (TBS) table for NPDSCH in NB-IoT Rel. 16.

[0011]

[0012] Table 2

[0013] In Table 2, I TBS ranges from 0 to 13.

[0014] In NB-IoT Rel-16, for NPUSCH, the number of resource units (N RU ) and the subcarriers to be used are determined as follows:

[0015] Table 3 indicates the number of resource units (N RU ) determined by the resource assignment (I RU ). The resource assignment (I RU ) is indicated by 3 bits through the corresponding control signal (e.g., DCI format N0). The resource units for NPUSCH are determined by the subcarrier spacing of NPUSCH data. For example, for a subcarrier spacing of 15 KHz, the resource units for NPUSCH data transmission are 16 slots (8 ms) in the time domain and 1 subcarrier in the frequency domain, or 8 slots (4 ms) in the time domain and 3 subcarriers in the frequency domain.

[0016]

[0017] Table 3

[0018] For different subcarrier spacings, the subcarriers to be used for NPUSCH data transmission are different. For a subcarrier spacing of 3.75 KHz, only a single tone is supported, and one of 48 subcarriers is used. The used subcarrier can be indicated by a 6-bit field. For a subcarrier spacing of 15 KHz, both single tone and multiple tones are supported. 1 or 3 or 6 or 12 of 12 subcarriers are used. The subcarriers to be used can be indicated as indicated in Table 4.

[0019]

[0020] Table 4

[0021] TBS is determined by the TBS index (I TBS ) and the resource assignment (I RU ).

[0022] Table 5 indicates the transport block size (TBS) table for NPUSCH in NB-IoT Rel-16.

[0023]

[0024] Table 5

[0025] In Table 5, the range of I TBS is from 0 to 13.

[0026] For single tone, when , the modulation order (Q m ) and the TBS index (ITBS ) by the MCS index (I MCS ) as shown in Table 6. As can be seen from Table 6, only BPSK (i.e., Q m = 1) and QPSK (i.e., Q m = 2) are supported.

[0027]

[0028] Table 6

[0029] For multi-tone, when , the modulation order (Q m ) = 2 is assumed. In this case, I TBS = I MCS .

[0030] In the above TBS determination for NB-IoT Rel-16, only modulation order (Q m ) = 1 or 2 (i.e., modulation type of BPSK or QPSK) is supported. In NB-IoT Rel-17, modulation type of 16QAM (modulation order (Q m ) = 4) will be supported for uplink and downlink data transmission. SUMMARY

[0031] Methods and apparatuses for transmitting or receiving data for NB-IoT supporting 16QAM modulation are disclosed.

[0032] In one embodiment, a method includes receiving a control signal, wherein the control signal includes a MCS index and a resource assignment index; and receiving a control signal, wherein the control signal includes a MCS index and a resource assignment index, wherein the transport block size is determined by a combination of a transport block size index and the resource assignment index, and the transport block size index is determined by at least one of the MCS index and the resource assignment index.

[0033] In one embodiment, the transport block size index is further determined by a scaling factor. The scaling factor can be determined by the resource assignment index.

[0034] In another embodiment, a modulation type is determined by the MCS index and the resource assignment index. In particular, the modulation type can be further determined by a scaling factor. The scaling factor can be determined by the resource assignment index.

[0035] In some embodiments, a number of resource units is determined by the resource assignment index and the modulation type.

[0036] In some embodiments, the control signal further includes a first field indicating a modulation type and a set of subcarriers. Specifically, the first field includes 6 bits, and at least state values 19 to 25 indicate that the modulation type is 16QAM.

[0037] In one embodiment, a base unit includes a transceiver configured to: transmit a control signal, wherein the control signal includes a MCS index and a resource assignment index; and receive or transmit coded data on a plurality of resource units and a set of subcarriers, wherein the coded data is associated with a modulation type and a transport block size, wherein the transport block size is determined by a combination of a transport block size index and the resource assignment index, and the transport block size index is determined by at least one of the MCS index and the resource assignment index.

[0038] In another embodiment, a method includes transmitting a control signal, wherein the control signal includes a MCS index and a resource assignment index; and receiving or transmitting coded data on a plurality of resource units and a set of subcarriers, wherein the coded data is associated with a modulation type and a transport block size, wherein the transport block size is determined by a combination of a transport block size index and the resource assignment index, and the transport block size index is determined by at least one of the MCS index and the resource assignment index.

[0039] In yet another embodiment, a remote unit includes a transceiver configured to: receive a control signal, wherein the control signal includes a MCS index and a resource assignment index; and transmit or receive coded data on a plurality of resource units and a set of subcarriers, wherein the coded data is associated with a modulation type and a transport block size, wherein the transport block size is determined by a combination of a transport block size index and the resource assignment index, and the transport block size index is determined by at least one of the MCS index and the resource assignment index. BRIEF DESCRIPTION OF DRAWINGS

[0040] A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. When understood in their context, which is set forth in the following detailed description and illustrated in the various drawings, the embodiments will be described and explained with additional specificity and detail. It is to be understood that the drawings are not necessarily to scale.

[0041] Figure 1 is a schematic flow chart illustrating an embodiment of a method;

[0042] Figure 2 is a schematic flow chart illustrating yet another embodiment of a method; and

[0043] Figure 3 is a schematic block diagram illustrating an apparatus according to one embodiment. DETAILED DESCRIPTION

[0044] As will be appreciated by those skilled in the art, certain aspects of the embodiments can be embodied as a system, a device, a method or a program product. Accordingly, the embodiments can take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that can all generally be referred to herein as a "circuit," "module" or "system." Furthermore, the embodiments can take the form of a program product embodied in one or more computer readable storage devices storing machine-readable code, computer readable code, and / or program code, hereinafter referred to as code. The storage devices can be tangible, non-transitory, and / or non-transmission. The storage devices can not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.

[0045] Certain of the functional units described in this specification can be labeled as "modules," in order to more particularly emphasize their implementation independence. For example, a module can be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module can also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

[0046] Modules can also be implemented in code and / or software for execution by various types of processors. An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure or function. Nevertheless, the executables of an identified module need not be physically located together, but can include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.

[0047] Indeed, a module of code can be a single instruction, or many instructions, and can even be distributed over several different code segments, in several different programs and across several memory devices. Similarly, operational data can be identified and illustrated herein within modules, and can be embodied in any suitable form and organized within any suitable type of data structure. The operational data can be collected as a single data set, or can be distributed over different locations including over different computer readable storage devices. Where a module or portions of a module are implemented in software, the software portions are stored in one or more computer readable storage devices.

[0048] Any combination of one or more computer-readable media may be utilized. The computer-readable medium may be a computer-readable storage medium. The computer-readable storage medium may be a storage device that stores code. The storage device may be, for example, but not necessarily, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0049] A non-exhaustive list of more specific examples of storage devices would include the following: an electrical connection having one or more wires, a portable computer floppy disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0050] The code for performing the operations of the embodiments may include any number of lines and may be written in any combination of one or more programming languages ​​including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, and the like, as well as conventional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly language. The code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer via any type of network including a local area network (LAN) or a wide area network (WAN), or a connection may be made to an external computer (e.g., over the Internet using an Internet service provider).

[0051] References throughout the specification to "one embodiment," "an embodiment," or similar language mean that a particular feature, structure, or characteristic described in conjunction with the embodiment is included in at least one embodiment. Thus, unless expressly specified otherwise, appearances of the phrases "in one embodiment," "in an embodiment," and similar language throughout the specification may, but do not necessarily, all refer to the same embodiment, but rather to "one or more but not all embodiments." Unless expressly specified otherwise, the terms "comprise," "comprising," "having," and variations thereof mean "including but not limited to." Unless expressly specified otherwise, an enumerated listing of items does not imply that any or all of the items are mutually exclusive. Unless expressly specified otherwise, the terms "a," "an," and "the" also mean "one or more."

[0052] Furthermore, the described features, structures, or characteristics of the various embodiments can be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the embodiments. One having ordinary skill in the relevant art will recognize that the embodiments can be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail in order to avoid obscuring aspects of the embodiments.

[0053] Aspects of the various embodiments are described below with reference to schematic flowcharts and / or schematic block diagrams of methods, apparatuses, systems, and program products according to the various embodiments. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. The code can be provided to a processor of a general purpose computer, a special purpose computer, or other programmable data processing apparatus to produce a machine, such that the

[0054] The code can also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function specified in the flowcharts and / or schematic block diagrams block or blocks.

[0055] The code can also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions specified in the flowcharts and / or block diagrams block or blocks.

[0056] The flowcharts and / or block diagrams in the various figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and program products according to various embodiments. In this regard, each block in the flowcharts and / or block diagrams can represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the flowcharts and / or block diagrams can represent a

[0057] It should also be noted that in some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks shown in succession can in fact be executed substantially concurrently or can sometimes be executed in the reverse order, depending upon the functionality involved. Such variation, and other variations, can be apparent to those skilled in the art.

[0058] Although various arrow types and line types can be employed in the flowcharts and / or block diagrams, these are understood to be merely illustrative of the logical flows of the corresponding embodiments. In turn, some of the depicted arrows, as well as other connections can be used to indicate alternative functionality of the corresponding embodiments. For instance, an arrow can indicate a waiting or monitoring period of time after which a determination is made, or it can directly introduce what can be expected to be successive operations for illustrative purposes. The responsibility of the various pieces of hardware or combinations of hardware and software can be allocated differently or be shared among various hardware and software components. Furthermore, not all of the benefits or features will necessarily be included in all embodiments. It will also be recognized that the functions of a given block can be carried out inside or outside the block.

[0059] The descriptions of the elements in the figures can refer to elements of the preceding figures. Like reference numbers in all figures refer to like elements, including alternative embodiments of the like elements.

[0060] A first embodiment relates to support of 16QAM for NPDSCH for NB-IoT Rel-17.

[0061] As in Rel-16, the number of resource units (N SF ) is determined by the resource allocation (I SF ), as indicated in Table 7.

[0062]

[0063] Table 7

[0064] The total number of subcarriers to be used is 12 subcarriers (15 KHz each).

[0065] The TBS is determined by the TBS index (I TBS ) and the resource allocation (I SF ). The maximum TBS can be increased to twice the legacy value for NPDSCH. The maximum TBS index (I TBS ) can be extended to 20 or 21. The resource allocation (I SF ) remains in the range from 0 to 7. Table 8 indicates the transport block size (TBS) table for NPDSCH to support 16QAM, where I TBS ranges from 0 to 21. If the maximum TBS index (I TBS ) is extended to 20, the last row of Table 8 is omitted.

[0066]

[0067] Table 8

[0068] As can be seen from Table 8, in order to be compatible with Version 16, the traditional TBS table (i.e., I from 0 to 13) is retained. TBS ). That is, the UE in Release 16 can reuse the traditional TBS table (from 0 to 13 I TBS ). New entries were added (i.e., I from 14 to 21). TBS ) to support 16QAM (i.e., Q m =4).

[0069] Modulation order (Q m ) and TBS index (I TBS ) by MCS index (I MCS ) is determined. In Release 16, the MCS index (I MCS ) is represented by 4 bits. In Release 17, the MCS index (I MCS ) can also be represented by 4 bits. There are two options for the number of MCS indices. For Option 1, the same number of MCS indices as in Release 16 is used, that is, 14 MCS indices are used. For Option 2, the number of MCS indices is expanded to 16, that is, 16 MCS indices are used (still capable of being represented by 4 bits).

[0070] Modulation order (Q m ) by MCS index (I MCS ) is determined. There can be a MCS index (I MCS ) determines the modulation order (Q m ) two options. For option A1, when I TBS When it is equal to 0 to 13, QPSK (Q m =2); and when I TBS 16QAM (Q m =4). For option A2, when I TBS When it is equal to 0 to 9, QPSK (Q m =2); and when I TBS 16QAM (Q m =4).

[0071] TBS Index (I TBS ) by MCS index (I MCS ) is determined. There can be a MCS index (I MCS )Determine the TBS index (ITBS For Option Bl, the TBS index is selected from a total of 21 TBS indices (I TBS = 0 to 20). For Option B2, the TBS index is selected from a total of 22 TBS indices (I TBS = 0 to 21). By the way, when I TBS = 21 (i.e., in the condition of a total of 22 TBS indices), the code rate of some TBSs is slightly greater than 0.93, especially for the in-band operation mode of NB IoT.

[0072] Table 9 indicates that the modulation order (Q MCS ) and the TBS index (I m ) are determined by the MCS index (I TBS ) in Option 1 (i.e., a total of 14 MCS indices).

[0073]

[0074] Table 9

[0075] Table 10 indicates that the modulation order (Q MCS ) and the TBS index (I m ) are determined by the MCS index (I TBS ) in Option 2 (i.e., a total of 16 MCS indices).

[0076]

[0077] Table 10

[0078] The second embodiment relates to a first solution for support of 16QAM for NPUSCH for Rel. 17. The first solution relates to extension of the TBS table.

[0079] The number of resource units (N RU ) is determined by the resource assignment (I RU ), as indicated in Table 11.

[0080]

[0081] Table 11

[0082] For different subcarrier spacings, different subcarriers are to be used. For subcarriers of 3.75 KHz, only single tone is supported and one of 48 subcarriers is used. The used subcarrier can be indicated by a field of 6 bits. For subcarriers of 15 KHz, both single tone and multi-tone are supported. One or three or six or twelve of twelve subcarriers are used. The subcarriers to be used can be indicated as indicated in Table 12.

[0083] subcarrier field (I SC )]]> A set of allocated subcarriers (N SC )]]> 0-11 I SC ]] 12-15 3(I SC -12)+{0,1,2}]]> 16-17 6(I SC -16)+{0,1,2,3,4,5}]]> 18 {0,1,2,3,4,5,6,7,8,9,10,11} 19-63 retention

[0084] Table 12

[0085] As can be seen from Table 12, each subcarrier indication field (I SC ) can be used to indicate allocated subcarriers.

[0086] In particular, when I SC = 0 to 11, the allocated carriers can be calculated by N SC = I SC . For example, when I SC = 3, the allocated carriers are 3 (1 tone).

[0087] When I SC = 12 to 15, the allocated carriers can be calculated by N SC = 3(I SC - 12) + {0, 1, 2}. For example, when I SC = 13, the allocated carriers are 3, 4, and 5 (3 tones).

[0088] When I SC = 16 to 17, the allocated carriers can be calculated by N SC = 6(I SC - 16) + {0, 1, 2, 3, 4, 5}. For example, when I SC = 16, the allocated carriers are 0, 1, 2, 3, 4, and 5 (6 tones).

[0089] When I SC = 18, the allocated carriers are 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, and 11 (12 tones).

[0090] The TBS is determined by the TBS index (I TBS ) and the resource allocation (I RU ). For NPUSCH, the maximum TBS remains as in Rel-16. That is, the maximum TBS is less than 2536. The maximum TBS index (I TBS ) can be extended to 20 or 21. The resource allocation (I RU ) remains in the range of 0 to 7. Table 13 indicates a transport block size (TBS) table for NPUSCH to support 16QAM, where I TBS ranges from 0 to 21. If the maximum TBS index (I TBS ) is extended to 20, the last row of Table 13 is omitted.

[0091]

[0092]

[0093] Table 13

[0094] From Table 13, it can be seen that legacy TBS table (i.e., I TBS from 0 to 13) is kept for compatibility with Rel-16. That is, legacy UEs can use a part of TBS table (Table 13) where I TBS comes from 0 to 13. New entries (i.e., I TBS from 14 to 21) are added to support 16QAM (i.e., Q m = 4) for new UEs.

[0095] In Rel-16 NB IoT, MCS index (I MCS ) is represented by 4 bits. In Rel-17, MCS index (I MCS ) can also be represented by 4 bits. There can be two options for the number of MCS indexes. For Option 1, the same number of MCS indexes as in Rel-16 is used, i.e., 14 MCS indexes are used. For Option 2, the number of MCS indexes is extended to 16, i.e., 16 MCS indexes are used (still can be represented by 4 bits).

[0096] Modulation order (Q m ) is determined by MCS index (I MCS ) and resource allocation (I RU ). The number of MCS indexes (I MCS ) can be 14 or 16. The range of resource allocation (I RU ) can be from 0 to 7.

[0097] When the number of MCS indexes (I MCS ) is 14 and resource allocation (I RU ) is 0 or 1 or 2 or 3 or 4, two options of modulation order (Q m ) are indicated in Table 14.

[0098]

[0099]

[0100] Table 14

[0101] When the number of MCS indexes (I MCS ) is 16 and resource allocation (I RU ) is 0 or 1 or 2 or 3 or 4, two options of modulation order (Q m ) are indicated in Table 15.

[0102]

[0103] Table 15

[0104] When the number of MCS indexes (I MCS ) is 14 and the resource allocation (I RU ) is 5, two options of modulation order (Q m ) are indicated in Table 16.

[0105]

[0106]

[0107] Table 16

[0108] When the number of MCS indexes (I MCS ) is 16 and the resource allocation (I RU ) is 5, two options of modulation order (Q m ) are indicated in Table 17.

[0109]

[0110] Table 17

[0111] When the number of MCS indexes (I MCS ) is 14 and the resource allocation (I RU ) is 6, two options of modulation order (Q m ) are indicated in Table 18.

[0112]

[0113]

[0114] Table 18

[0115] When the number of MCS indexes (I MCS ) is 16 and the resource allocation (I RU ) is 6, two options of modulation order (Q m ) are indicated in Table 19.

[0116]

[0117] Table 19

[0118] When the number of MCS indexes (I MCS ) is 14 and the resource allocation (I RU ) is 7, two options of modulation order (Q m ) are indicated in Table 20.

[0119]

[0120] Table 20

[0121] When the number of MCS indexes (I MCS ) is 16 and the resource assignment (I RU ) is 7, two options of modulation order (Q m ) are indicated in Table 21.

[0122]

[0123] Table 21

[0124] As an alternative way of determining the modulation order (Q m ), the modulation order (Q m ) can be determined by the MCS index (I MCS ) and a scaling factor K. If rounding(KI MCS )>I MCS,max , then Q m =4. Otherwise, Q m =2. For example, I MCS,max is fixed to 13 or configured to 13 by higher layer.

[0125] The scaling factor K is determined by the resource assignment (I RU ). For the first example, when I RU =0 or 1 or 2 or 3 or 4, K=21 / 14; when I RU =5, K=19 / 14; when I RU =6, K=16 / 14; when I RU =7, K=1. For the second example, when I RU =0 or 1 or 2 or 3 or 4, K=21 / 16; when I RU =5, K=19 / 16; when I RU =6 or 7, K=1. For the third example, when I RU =0 or 1 or 2 or 3 or 4, K=22 / 14; when I RU =5, K=19 / 14; when I RU =6, K=16 / 14; when I RU =7, K=1. For the fourth example, when I RU =0 or 1 or 2 or 3 or 4, K=22 / 16; when I RU =5, K=19 / 16; when I RU =6 or 7, K=1.

[0126] The TBS index (I TBS ) is determined by the MCS index (I MCS ) and the resource assignment (I RU ). The number of MCS indexes (I MCS ) can be 14 or 16. The resource assignment (IRU ) can range from 0 to 7. There is a method for determining the TBS index (I TBS ). For option B1, the TBS index is selected from a total of 21 TBS indexes. For option B2, the TBS index is selected from a total of 22 TBS indexes.

[0127] When the MCS index (I MCS ) is 14 and the resource assignment (I RU ) is 0 or 1 or 2 or 3 or 4, the TBS index (I TBS ) are indicated in Table 16.

[0128]

[0129] Table 22

[0130] When the MCS index (I MCS ) is 16 and the resource assignment (I RU ) is 0 or 1 or 2 or 3 or 4, the TBS index (I TBS ) are indicated in Table 23.

[0131]

[0132]

[0133] Table 23

[0134] When the MCS index (I MCS ) is 14 and the resource assignment (I RU ) is 5, the TBS index (I TBS ) are indicated in Table 24.

[0135]

[0136] Table 24

[0137] When the MCS index (I MCS ) is 16 and the resource assignment (I RU ) is 5, the TBS index (I TBS ) are indicated in Table 25.

[0138]

[0139] Table 25

[0140] When the MCS index (I MCS ) is 14 and the resource assignment (I RU ) is 6, TBS index (I TBS ) are indicated in Table 26.

[0141]

[0142] Table 26

[0143] When the number of MCS indexes (I MCS ) is 16 and the resource assignment (I RU ) is 6, the TBS index (I TBS ) is indicated in Table 27.

[0144]

[0145] Table 27

[0146] When the number of MCS indexes (I MCS ) is 14 and the resource assignment (I RU ) is 7, the TBS index (I TBS ) is indicated in Table 28.

[0147]

[0148] Table 28

[0149] When the number of MCS indexes (I MCS ) is 16 and the resource assignment (I RU ) is 7, the TBS index (I TBS ) is indicated in Table 29.

[0150]

[0151] Table 29

[0152] As can be seen from Tables 22-29, the MCS index is represented by 4 bits, and the number of MCS indexes can be 14 or 16. On the other hand, the number of TBS indexes can be 21 or 22. Therefore, some of the TBS indexes (0 to 20 or 21) are selected.

[0153] As an alternative way of determining the TBS index (I TBS ), the TBS index (I TBS ) can be determined from the MCS index (I MCS ) and a scaling factor K. I TBS = round(KI MCS ).

[0154] The scaling factor K is determined from the resource assignment (I RU ). For the first example, when I RU = 0 or 1 or 2 or 3 or 4, K = 21 / 14; when I RU = 5, K = 19 / 14; when I RU= 6, K = 16 / 14; when I RU = 7, K = 1. For the second example, when I RU = 0 or 1 or 2 or 3 or 4, K = 21 / 16; when I RU = 5, K = 19 / 16; when I RU = 6 or 7, K = 1. For the third example, when I RU = 0 or 1 or 2 or 3 or 4, K = 22 / 14; when I RU = 5, K = 19 / 14; when I RU = 6, K = 16 / 14; when I RU = 7, K = 1. For the fourth example, when I RU = 0 or 1 or 2 or 3 or 4, K = 22 / 16; when I RU = 5, K = 19 / 16; when I RU = 6 or 7, K = 1.

[0155] In the above determination of modulation order (Q m ) and TBS index (I TBS ) according to the second embodiment, modulation order (Q RU ) and TBS index (I m ) are determined separately for resource allocation (I TBS ) equal to 5 or 6 or 7. Alternatively, modulation order (Q RU ) and TBS index (I m ) can be determined to the same value for resource allocation (I TBS ) equal to 5, 6 and 7. Table 30 indicates the determination of modulation order (Q MCS ) and TBS index (I RU ) based on MCS index (I m ) and resource allocation (I TBS ), where the same value is determined for I RU equal to 1 or 2 or 3 or 4 and the same value is determined for I RU equal to 5 or 6 or 7.

[0156]

[0157]

[0158] Table 30

[0159] The third embodiment relates to a second solution for support of 16QAM for NPUSCH data transmission for Rel. 17. The second solution involves adjusting the number of resource units.

[0160] According to the third embodiment, the number of resource units (N RU). In addition to the resource allocation (I RU ), the number of resource units is determined by the modulation order (Q m ). In particular, when 16QAM is used, the number of resource units is scaled down.

[0161] Table 31 indicates the number of resource units according to the third embodiment.

[0162]

[0163] Table 31

[0164] As can be seen from Table 31, when Q m is equal to 2, for resource allocations (I RU ) of 0, 1, 2, 3, 4, 5, 6, and 7, the number of resource units is 1, 2, 3, 4, 5, 6, 8, 10, respectively. When Q m is equal to 4, for resource allocations (I RU ) of 1, 3, 5, 6, and 7, the number of resource units is 1, 2, 3, 4, and 5, respectively. Since there are only 5 candidate numbers of resource units (i.e., 1 to 5) for Q m equal to 4, only 5 resource allocations are used.

[0165] In Table 31, when Q m is equal to 4, no N RU values are configured for resource allocations (I RU ) equal to 0, 2, and 4. Alternatively, when Q m is equal to 4, the same N RU values as for I RU equal to 1, 3, and 5, respectively, can be configured for I RU equal to 0, 2, and 4, respectively. Table 32 indicates alternative numbers of resource units according to the third embodiment.

[0166]

[0167] Table 32

[0168] It is assumed that BPSK and / or QPSK is used in a single tone to enhance coverage. Therefore, 16QAM is not applicable to a single tone. Under this assumption, 16QAM can only be supported in a multi-tone. Joint compilation can be applied to the subcarrier allocation and the modulation order (Q m ) of a multi-tone.

[0169] Table 33 indicates the joint compilation of the modulation order (Q m ) and the allocated subcarriers for NPUSCH with Δf = 15 kHz.

[0170]

[0171] Table 33

[0172] As can be seen from Table 33, each subcarrier indication field (I SC ) can be used to indicate both the modulation order (Q m ) and the allocated subcarriers.

[0173] In particular, when I SC = 0 to 11, the modulation order (Q m ) is 2 (i.e., QPSK), and the allocated carriers can be calculated by N SC = I SC . For example, when I SC = 3, the allocated carriers are #3 (1 tone).

[0174] When I SC = 12 to 15, the modulation order (Q m ) is 2 (i.e., QPSK), and the allocated carriers can be calculated by N SC = 3(I SC - 12) + {0, 1, 2}. For example, when I SC = 13, the allocated carriers are #3, #4, and #5 (3 tones).

[0175] When I SC = 16 to 17, the modulation order (Q m ) is 2 (i.e., QPSK), and the allocated carriers can be calculated by N SC = 6(I SC - 16) + {0, 1, 2, 3, 4, 5}. For example, when I SC = 16, the allocated carriers are #0, #1, #2, #3, #4, and #5 (6 tones).

[0176] When I SC = 18, the modulation order (Q m ) is 2 (i.e., QPSK), and the allocated carriers are #0, #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, and #11 (12 tones).

[0177] When I SC = 19 to 22, the modulation order (Q m ) is 4 (i.e., 16QAM), and the allocated carriers can be calculated by N SC = 3(I SC - 19) + {0, 1, 2}. For example, when I SC = 21, the allocated carriers are #6, #7, and #8 (3 tones).

[0178] When I SC = 23 to 24, the modulation order (Q m ) is 4 (i.e., 16QAM), and the allocated carriers can be calculated by N SC = 6(I SC - 23) + {0, 1, 2, 3, 4, 5}. For example, when I SC = 24, the allocated carriers are #6, #7, #8, #9, #10, and #11 (6 tones).

[0179] When I SC = 25, the modulation order (Q m ) is 4 (i.e., 16QAM), and the allocated carriers are #0, #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, and #11 (12 tones).

[0180] It can be seen that the state values 19 to 25 indicate that the modulation order (Q m ) is 4 (i.e., 16QAM).

[0181] The legacy TBS table is maintained. The TBS is determined by the TBS index (I TBS ) and the resource allocation (I RU ). Table 34 indicates the transport block size (TBS) table for NPUSCH according to the third embodiment.

[0182]

[0183] Table 34

[0184] Table 34 is the same as Table 5.

[0185] The TBS index (I TBS ) is determined by the MCS index (I MCS ). For example, I TBS = I MCS .

[0186] Figure 1 is a schematic flowchart illustrating an embodiment of a method 100 according to the present application. In some embodiments, the method 100 is performed by an apparatus, such as a base unit. In certain embodiments, the method 100 can be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0187] The method 100 can comprise 102 transmitting a control signal, wherein the control signal comprises a MCS index and a resource allocation index; and 104 transmitting a data signal over a plurality of resource units (N RU) and a set of subcarriers, wherein the coded data is associated with a modulation type and a transport block size, wherein the transport block size is determined by a combination of a transport block size index and a resource assignment index, and the transport block size index (I TBS ) is determined by at least one of an MCS index (I MCS ) and the resource assignment index (I RU ).

[0188] Figure 2 is a schematic flow chart illustrating yet another embodiment of a method 200 according to the present application. In some embodiments, the method 200 is performed by an apparatus, such as a remote unit. In certain embodiments, the method 200 can be performed by a processor, e.g., a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like, executing program code.

[0189] The method 200 can comprise 202 receiving a control signal, wherein the control signal comprises an MCS index and a resource assignment index; and 204 transmitting or receiving coded data on a plurality of resource units (N RU ) and a set of subcarriers, wherein the coded data is associated with a modulation type and a transport block size, wherein the transport block size is determined by a combination of a transport block size index and a resource assignment index, and the transport block size index (I TBS ) is determined by at least one of an MCS index (I MCS ) and the resource assignment index (I RU ).

[0190] Figure 3 is a schematic block diagram illustrating an apparatus according to an embodiment.

[0191] With reference to Figure 3 , the UE (i.e., remote unit) comprises a processor, a memory, and a transceiver. The processor implements the functions, procedures, and / or methods proposed in Figure 2 . The gNB (i.e., base station unit) comprises a processor, a memory, and a transceiver. The processor implements the functions, procedures, and / or methods proposed in Figure 1 . Layers of the radio interface protocol can be implemented by the processor. The memory is connected with the processor to store various pieces of information for driving the processor. The transceiver is connected with the processor to transmit and / or receive radio signals. Needless to say, the transceiver can be implemented as a transmitter for transmitting radio signals and a receiver for receiving radio signals.

[0192] The memory can be positioned inside or outside the processor and connected with the processor by various well-known means.

[0193] In the above-described embodiments, components and features of the embodiments are combined in predetermined forms. Each component or function can be implemented as hardware or software. Unless explicitly described as software, each component or function is understood to be implemented in software. Each component or feature of the embodiments can be used alone or in combination with other components or features. It is obvious that the components or features from one embodiment can be used in another embodiment on the premise of no contradiction is included. It is also obvious that the scope of the present disclosure includes a combination of some components or features of the embodiments.

[0194] The embodiments can be implemented by hardware, firmware, software, or a combination thereof. In case of implementation by hardware, the exemplary embodiments described herein can be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, etc., according to hardware implementation.

[0195] The embodiments can be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the disclosure is therefore indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning of and equivalents to the claims are intended to be embraced therein.

Claims

1. A method for wireless communication performed by a user equipment (UE), comprising: receiving a control signal, the control signal comprising a modulation and coding scheme (MCS) index and a resource assignment index; and transmitting or receiving a coded data on one or more resource units and one or more subcarriers, wherein the coded data is associated with a modulation type and a transport block size (TBS), wherein the TBS is determined based on a TBS index and the resource assignment index, and wherein the TBS index is determined by the MCS index, wherein the TBS index ranges from 0 to 13 or 0 to 21 depending on whether the UE is configured to support 16 quadrature amplitude modulation (QAM), wherein the TBS index ranging from 0 to 13 is used for quadrature phase shift keying (QPSK) when 16 QAM is not supported, and wherein the TBS index ranging from 0 to 13 is used for QPSK and the TBS index ranging from 14 to 21 is used for 16 QAM when 16 QAM is supported.

2. The method of claim 1, wherein, the TBS index is further determined by a scaling factor.

3. The method of claim 1, wherein, the modulation type is determined by the MCS index and the resource assignment index.

4. The method of claim 3, wherein, the modulation type is further determined by a scaling factor.

5. The method of claim 2 or 4, wherein, the scaling factor is determined by the resource assignment index.

6. The method of claim 1, wherein, the one or more resource units are determined by the resource assignment index and the modulation type.

7. The method of claim 1, wherein, the control signal further comprises a first field indicating the modulation type and the one or more subcarriers.

8. The method of claim 7, wherein, the first field comprises 6 bits, and wherein at least state values 19 to 25 indicate the modulation type is 16 quadrature amplitude modulation (QAM).

9. A method for wireless communication performed by a base station, comprising: transmitting a control signal, the control signal comprising a modulation and coding scheme (MCS) index and a resource assignment index; and receiving or transmitting a coded data on one or more resource units and one or more subcarriers, wherein the coded data is associated with a modulation type and a transport block size (TBS), wherein the TBS is determined based on a TBS index and the resource assignment index, and wherein the TBS index is determined by the MCS index, wherein the TBS index ranges from 0 to 13 or 0 to 21 depending on whether 16 quadrature amplitude modulation (QAM) is supported, wherein the TBS index ranging from 0 to 13 is used for quadrature phase shift keying (QPSK) when 16 QAM is not supported, and wherein the TBS index ranging from 0 to 13 is used for QPSK and the TBS index ranging from 14 to 21 is used for 16 QAM when 16 QAM is supported.

10. The method of claim 9, wherein, the TBS index is further determined by a scaling factor.

11. The method of claim 9, wherein, the modulation type is determined by the MCS index and the resource assignment index.

12. The method of claim 11, wherein, the modulation type is further determined by a scaling factor.

13. The method of claim 10 or 12, wherein, the scaling factor is determined by the resource assignment index.

14. The method of claim 9, wherein, the one or more resource units are determined by the resource assignment index and the modulation type.

15. The method of claim 9, wherein, The control signal further comprises a first field, the first field indicating the modulation type and the one or more subcarriers.

16. The method of claim 15, wherein, The first field comprises 6 bits, and wherein at least state values 19 to 25 indicate the modulation type as 16 quadrature amplitude modulation QAM.

17. A user equipment, UE, for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: receive a control signal, the control signal comprising a modulation and coding scheme, MCS, index and a resource assignment index; and transmit or receive a coded data on one or more resource units and one or more subcarriers, wherein the coded data is associated with a modulation type and a transport block size, TBS, wherein the TBS is determined based on a TBS index and the resource assignment index, and wherein the TBS index is determined by the MCS index, wherein the TBS index ranges from 0 to 13 or 0 to 21 depending on whether the UE is configured to support 16 quadrature amplitude modulation, QAM, wherein the TBS index ranging from 0 to 13 is used for quadrature phase shift keying, QPSK, when 16 QAM is not supported, and wherein the TBS index ranging from 0 to 13 is used for QPSK and the TBS index ranging from 14 to 21 is used for 16 QAM when 16 QAM is supported.

18. The UE of claim 17, wherein, The TBS index is further determined by a scaling factor.

19. The UE of claim 17, wherein, The modulation type is determined by the MCS index and the resource assignment index.

20. The UE of claim 19, wherein, The modulation type is further determined by a scaling factor.

21. The UE of claim 18 or 20, wherein, The scaling factor is determined by the resource assignment index.

22. The UE of claim 17, wherein, The one or more resource units are determined by the resource assignment index and the modulation type.

23. The UE of claim 17, wherein, The control signal further comprises a first field, the first field indicating the modulation type and the one or more subcarriers.

24. The UE of claim 23, wherein, The first field comprises 6 bits, and wherein at least state values 19 to 25 indicate the modulation type as 16 quadrature amplitude modulation QAM.

25. A base station for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the base station to: transmit a control signal, the control signal comprising a modulation and coding scheme, MCS, index and a resource assignment index; and receive or transmit a coded data on one or more resource units and one or more subcarriers, wherein the coded data is associated with a modulation type and a transport block size, TBS, wherein the TBS is determined based on a TBS index and the resource assignment index, and wherein the TBS index is determined by the MCS index, wherein the TBS index ranges from 0 to 13 or 0 to 21 depending on whether 16 quadrature amplitude modulation, QAM, is supported, wherein the TBS index ranging from 0 to 13 is used for quadrature phase shift keying, QPSK, when 16 QAM is not supported, and wherein the TBS index ranging from 0 to 13 is used for QPSK and the TBS index ranging from 14 to 21 is used for 16 QAM when 16 QAM is supported. wherein, when 16 QAM is supported, the TBS indices ranging from 0 to 13 are used for QPSK and the TBS indices ranging from 14 to 21 are used for 16 QAM.

26. The base station of claim 25, wherein, The TBS index is further determined by a scaling factor.

27. The base station of claim 25, wherein, The modulation type is determined by the MCS index and the resource assignment index.

28. The base station of claim 27, wherein, The modulation type is further determined by a scaling factor.

29. The base station of claim 26 or 28, wherein, The scaling factor is determined by the resource assignment index.

30. The base station of claim 25, wherein, The one or more resource units are determined by the resource assignment index and the modulation type.

31. The base station of claim 25, wherein, The control signal further comprises a first field indicating the modulation type and the one or more subcarriers.

32. The base station of claim 31, wherein, The first field comprises 6 bits, and wherein at least state values 19 to 25 indicate the modulation type as 16 quadrature amplitude modulation, QAM.

Images