Patent Application
20230239070
The subject matter disclosed herein generally relates to wireless communications, and more particularly relates to 16QAM transmission for NBIoT.
The following abbreviations are herewith defined, at least some of which are referred to within the following description: 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 Multiplex (TDM), User Entity/Equipment (Mobile Terminal) (UE), Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), Internet-of-Things (IoT), Narrowband Internet-of-Things (NB-IoT or NBIoT), Long Term Evolution (LTE), Narrowband (NB), Narrowband Primary Synchronization Signal (NPSS), Narrowband Secondary Synchronization Signal (NSSS), Narrowband Physical Broadcast Channel (NPBCH or NB-PBCH), System Information (SI), System Information Block (SIB), System Information Block Type1-NB (NB-SIB1), Physical Downlink Shared Channel (PDSCH), Narrowband Physical Downlink Shared Channel (NPDSCH), Physical Uplink Shared Channel (PUSCH), Narrowband 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).
In NB-IoT Release 16, for NPDSCH, when a coded data is transmitted from the base unit (e.g. gNB) to the remote unit (e.g. UE), the number of resource unit (NSF) and the subcarriers to be used in time and frequency domain are determined as follows:
Table 1 indicates the number of resource units (NSF) being determined by the resource assignment (ISF). The resource assignment (ISF) is indicated with 3 bits by the corresponding control signal (e.g., DCI format N1). The resource unit for NPDSCH is 1 ms for time domain and 1 PRB (12 subcarriers) in frequency domain.
The subcarriers to be used are a total of 12 subcarriers (each subcarrier is 15 KHz).
The coded data is transmitted with a transport block size (TBS), and transmitted by using a modulation type such as QPSK. The modulation type is associated with a modulation order (Qm). For example, the modulation order (Qm) of QPSK is 2. In the present application, the modulation order (Qm) represents the modulation type.
TBS is determined by TBS index (ITBS) and the resource assignment (ISF). TBS index (ITBS) is determined by MCS (modulation and coding scheme) index (IMCS). When QPSK (Qm=2) is assumed as the modulation type, ITBS=IMCS. The MCS index (IMCS) is indicated with 4 bits by the corresponding control signal (e.g., DCI format N1).
Table 2 indicates the Transport block size (TBS) table for NPDSCH in NB-IoT Release 16.
In Table 2, ITBS ranges from 0 to 13.
In NB-IoT Release 16, for NPUSCH, when a coded data is transmitted from the remote unit (e.g. UE) to the base unit (e.g. gNB), the number of resource unit (NRU) and the subcarriers to be used are determined as follows:
Table 3 indicates the number of resource units (NRU) being determined by the resource assignment (IRU). The resource assignment (IRU) is indicated with 3 bits by the corresponding control signal (e.g., DCI format N1). The resource unit for NPUSCH is determined by the subcarrier spacing of the NPUSCH data. For example, for 15 KHz subcarrier spacing, the resource unit of NPUSCH data transmission is 16 slots (8 ms) in time domain and 1 subcarrier in frequency domain, or 8 slots (4 ms) in time domain and 3 subcarriers in frequency domain.
The subcarriers to be used for NPUSCH data transmission are different for different subcarrier spacings. For subcarrier spacing of 3.75 KHz, only single-tone is supported and one of 48 subcarriers is used. The used subcarrier can be indicated by a 6-bits field. For subcarrier spacing of 15 KHz, both single-tone and multiple-tone are supported. One or three or six or twelve of twelve subcarriers is used. The subcarriers to be used may be indicated as indicated in Table 4.
TBS is determined by TBS index (ITBS) and resource assignment (IRU).
Table 5 indicates the Transport block size (TBS) table for NPUSCH in NB-IoT Release 16.
In Table 5, ITBS ranges from 01 to 13.
For single-tone, when NscRU=1, modulation order (Qm) and TBS index (ITBS) are determined by MCS index (IMCS), as shown in Table 6. It can be seen from Table 6 that only BPSK (i.e. Qm=1) and QPSK (i.e. Qm=2) are supported.
For multiple-tone, when NscRU>1, modulation order (Qm)=2 is assumed. In this condition, ITBS IMCS.
In the above TBS determination for NBIoT Release 16, only modulation order (Qm)=1 or 2 (i.e. modulation type of BPSK or QPSK) is supported. In NBIoT Release 17, modulation type of 16QAM (modulation order (Qm)=4) will be supported for uplink and downlink data transmission.
Methods and apparatuses for transmitting or receiving data for NBIoT supporting 16QAM modulation are disclosed.
In one embodiment, a method comprises 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.
In one embodiment, the transport block size index is further determined by a scaling factor. The scaling factor may be determined by the resource assignment index.
In another embodiment, the modulation type is determined by the MCS index and the resource assignment index. In particular, the modulation type may be further determined by a scaling factor. The scaling factor may be determined by the resource assignment index.
In some embodiment, the number of resource units is determined by the resource assignment index and the modulation type.
In some embodiment, the control signal further includes a first field, the first field indicates the modulation type and the set of subcarrier(s). In particular, the first field includes 6 bits, and at least the state values 19 to 25 indicate the modulation type being 16QAM.
In one embodiment, a base unit comprises a transceiver, the transceiver is configured to: transmit a control signal, wherein the control signal includes a MCS index and a resource assignment index; and receive or transmit a coded data on a number of resource units and a set of subcarrier(s), 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.
In another embodiment, a method comprises transmitting a control signal, wherein the control signal includes a MCS index and a resource assignment index; and receiving or transmitting a coded data on a number of resource units and a set of subcarrier(s), 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.
In yet another embodiment, a remote unit comprises a transceiver, the transceiver is configured to: receive a control signal, wherein the control signal includes a MCS index and a resource assignment index; and transmit or receive a coded data on a number of resource units and a set of subcarrier(s), 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.
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. Understanding that these drawings depict only some embodiments, and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:
As will be appreciated by one skilled in the art that certain aspects of the embodiments may be embodied as a system, apparatus, method, or program product.
Accordingly, embodiments may 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 may generally all be referred to herein as a “circuit”, “module” or “system”. Furthermore, embodiments may 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, referred to hereafter as “code”. The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.
Certain functional units described in this specification may be labeled as “modules”, in order to more particularly emphasize their independent implementation. For example, a module may 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 may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
Modules may 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, may include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.
Indeed, a module of code may contain a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules and may be embodied in any suitable form and organized within any suitable type of data structure. This operational data may be collected as a single data set, or may 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 on one or more computer readable storage devices.
Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing code. The storage device may be, for example, but need not necessarily be, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
A non-exhaustive list of more specific examples of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or Flash Memory), 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.
Code for carrying out operations for embodiments may include any number of lines and may be written in any combination of one or more programming languages including an object-oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the “C” programming language, or the like, and/or machine languages such as assembly languages. The code may be executed entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the very last scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Reference throughout this specification to “one embodiment”, “an embodiment”, or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment”, “in an embodiment”, and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including”, “comprising”, “having”, and variations thereof mean “including but are not limited to”, unless otherwise expressly specified. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, otherwise unless expressly specified. The terms “a”, “an”, and “the” also refer to “one or more” unless otherwise expressly specified.
Furthermore, described features, structures, or characteristics of various embodiments may 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 embodiments. One skilled in the relevant art will recognize, however, that embodiments may 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 to avoid any obscuring of aspects of an embodiment.
Aspects of different embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code.
This code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which are executed via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the schematic flowchart diagrams and/or schematic block diagrams for the block or blocks.
The code may 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 schematic flowchart diagrams and/or schematic block diagrams block or blocks.
The code may 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 executed on the computer or other programmable apparatus provides processes for implementing the functions specified in the flowchart and/or block diagram block or blocks.
The schematic flowchart diagrams and/or schematic block diagrams in the 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 schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).
It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may substantially be executed concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, to the illustrated Figures.
Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.
The description of elements in each Figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.
The first embodiment is related to the support of 16QAM for NPDSCH of release 17.
As in Release 16, the number of resource units (NSF) is determined by the resource assignment (ISF), as indicated in Table 7.
The subcarriers to be used are a total of 12 subcarriers (each subcarrier is 15 KHz).
TBS is determined by TBS index (ITBS) and the resource assignment (ISF). The maximal TBS can be increased to two times of legacy value for NPDSCH. The maximal TBS index (ITBS) can be extended to 20 or 21. The resource assignment (ISF) remains as ranging from 0 to 7. Table 8 indicates the Transport block size (TBS) table for NPDSCH for support of 16QAM, in which ITBS ranges from 0 to 21. If the maximum TBS index (ITBS) is extended to 20, the last line of the Table 8 is omitted.
As can be seen from Table 8, legacy TBS table (i.e. ITBS from 0 to 13) is kept for compatibility with Release 16. That is, UE in Release 16 can reuse legacy TBS table (ITBS from 0 to 13). New items (i.e. ITBS from 14 to 21) are added for the support of T6QAM (i.e. Qm=4).
The modulation order (Qm) and the TBS index (ITBS) are determined by MCS index (IMCS). In release 16, MCS index (IMCS) are represented by 4 bits. In release 17, MCS index (IMCS) may also be represented by 4 bits. There can be two options for the number of MCS indices. For option 1, the same number as the number of MCS indices in release 16 is used, i.e. 14 MCS indices are used. For option 2, the number of MCS indices is extended to 16, i.e. 16 MCS indices (that can still be represented by 4 bits) are used.
The modulation order (Qm) is determined by MCS index (IMCS). There can be two options of determining the modulation order (Qm) by the MCS index (IMCS). For option A1, QPSK (Qm=2) is used when ITBS is equal to 0 to 13; and T6QAM (Qm=4) is used when ITBS is equal to 14 to 20 (for option 1) or 14 to 21 (for option 2). For option A2, QPSK (Qm=2) is used when ITBS is equal to 0 to 9; and 16QAM (Qm=4) is used when ITBS is equal to 10 to 20 (for option 1) or 10 to 21 (for option 2).
The TBS index (ITBS) is determined by MCS index (IMCS). There can be two options of determining TBS index (ITBS) by the MCS index (IMCS). For option B1, the TBS index is selected from a total of 21 TBS indices (ITBS=0 to 20). For option B2, the TBS index is selected from a total of 22 TBS indices (ITBS=0 to 21). Incidentally, when ITBS=21 (i.e. in the condition of a total of 22 TBS indices), the code rate for some of the TBSs is slightly larger than 0.93, especially for inband operation mode of NBIoT.
Table 9 indicates the determination of the modulation order (Qm) and the TBS index (ITBS) by MCS index (IMCS) in option 1 (i.e. a total of 14 MCS indices).
Table 10 indicates the determination of the modulation order (Qm) and the TBS index (ITBS) by MCS index (IMCS) in option 2 (i.e. a total of 16 MCS indices).
The second embodiment is related to a first solution of the support of 16QAM for NPUSCH of release 17. The first solution is related to the extension of the TBS table.
The number of resource units (NRU) is determined by the resource assignment (IRU), as indicated in Table 11.
The subcarriers to be used are different for different subcarrier spacings. For subcarrier of 3.75 KHz, only single-tone is supported and one of 48 subcarriers is used. The used subcarrier can be indicated by a 6-bits field. For subcarrier of 15 KHz, both single-tone and multiple-tone are supported. One or three or six or twelve of twelve subcarriers is used. The subcarriers to be used may be indicated as indicated in Table 12.
As can be seen from Table 12, each subcarrier indication field (ISC) can be used to indicate the allocated subcarriers.
In particular, when ISC=0 to 11, the allocated carrier can be calculated by NSC=ISC. For example, when ISC=3, the allocated carrier is 3 (1 tone).
When ISC=12 to 15, the allocated carriers can be calculated by NSC=3 (ISC−12)+{0, 1, 2}. For example, when ISC=13, the allocated carriers are 3, 4 and 5 (3 tones).
When ISC=16 to 17, the allocated carriers can be calculated by NSC=6 (ISC−16)+{0, 1, 2, 3, 4, 5}. For example, when ISC=16, the allocated carriers are 0, 1, 2, 3, 4 and 5 (6 tones).
When ISC=18, the allocated carriers are 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 and 11 (12 tones).
The TBS is determined by TBS index (ITBS) and the resource assignment (IRU).
The maximal TBS remains as in release 16 for NPUSCH. That is, the maximal TBS is smaller than 2536. The maximum TBS index (ITBS) may be extended to 20 or 21. The resource assignment (IRU) remains as ranging from 0 to 7. Table 13 indicates the Transport block size (TBS) table for NPUSCH for support of 16QAM, in which 1 ms ranges from 0 to 21. If the maximum TBS index (ITBS) is extended to 20, the last line of the Table 13 is omitted.
As can be seen from Table 13, legacy TBS table (i.e. ITBS from 0 to 13) is kept for compatibility with Release 16. That is, legacy UE can use a part of TBS table (Table 13) in which ITBS is from 0 to 13. New items (i.e. ITBS from 14 to 21) are added for the support of T6QAM (i.e. Qm=4) for new UE.
In release 16 NBIoT, MCS index (IMCS) are represented by 4 bits. In release 17, MCS index (IMCS) may also be represented by 4 bits. There can be two options for the number of MCS indices. For option 1, the same number as the number of MCS indices in release 16 is used, i.e. 14 MCS indices are used. For option 2, the number of MCS indices is extended to 16, i.e. 16 MCS indices (that can still be represented by 4 bits) are used.
The modulation order (Qm) is determined by MCS index (IMCS) and resource assignment (IRU). The number of MCS indices (IMCS) can be 14 or 16. The resource assignment (IRU) may range from 0 to 7.
When the number of MCS indices (IMCS) is 14 and the resource assignment (IRU) is 0 or 1 or 2 or 3 or 4, two options of the modulation order (Qm) are indicated in Table 14.
When the number of MCS indices (IMCS) is 16 and the resource assignment (IRU) is 0 or 1 or 2 or 3 or 4, two options of the modulation order (Qm) are indicated in Table 15.
When the number of MCS indices (IMCS) is 14 and the resource assignment (IRU) is 5, two options of the modulation order (Qm) are indicated in Table 16.
When the number of MCS indices (IMCS) is 16 and the resource assignment (IRU) is 5, two options of the modulation order (Qm) are indicated in Table 17.
When the number of MCS indices (IMCS) is 14 and the resource assignment (IRU) is 6, two options of the modulation order (Qm) are indicated in Table 18.
When the number of MCS indices (IMCS) is 16 and the resource assignment (IRU) is 6, two options of the modulation order (Qm) are indicated in Table 19.
When the number of MCS indices (IMCS) is 14 and the resource assignment (IRU) is 7, two options of the modulation order (Qm) are indicated in Table 20.
When the number of MCS indices (IMCS) is 16 and the resource assignment (IRU) is 7, two options of the modulation order (Qm) are indicated in Table 21.
As an alternative way of determining the modulation order (Qm), the modulation order (Qm) may be determined by MCS index (IMCS) and scaling factor K. If round (KIMCS)>IMCS,max, QM=4. Otherwise, QM=2. For example, IMCS,max is fixed to 13 or configured by higher layer to 13.
The scaling factor K is determined by the resource assignment (IRU). For a first example, when IRU=0 or 1 or 2 or 3 or 4, K=21/14; when IRU=5, K=19/14; when IRU=6, K=16/14; when IRU=7, K=1. For a second example, when IRU=0 or 1 or 2 or 3 or 4, K=21/16; when IRU=5, K=19/16; when IRU=6 or 7, K=1. For a third example, when IRU=0 Or 1 or 2 or 3 or 4, K=22/14; when IRU=5, K=19/14; when IRU=6, K=16/14; when IRU=7, K=1. For a fourth example, when IRU=0 or 1 or 2 or 3 or 4, K=22/16; when IRU=5, K=19/16; when IRU=6 or 7, K=1.
The TBS index (ITBS) is determined by MCS index (IMCS) and resource assignment (IRU). The number of MCS indices (IMCS) can be 14 or 16. The resource assignment (IRU) may range from 0 to 7. There are two options for determining the TBS index (ITBS). For option B1, the TBS index is selected from a total of 21 TBS indices. For option B2, the TBS index is selected from a total of 22 TBS indices.
When the number of MCS indices (IMCS) is 14 and the resource assignment (IRU) is 0 or 1 or 2 or 3 or 4, two options of the TBS index (ITBS) are indicated in Table 16.
When the number of MCS indices (IMCS) is 16 and the resource assignment (IRU) is 0 or 1 or 2 or 3 or 4, two options of the TBS index (ITBS) are indicated in Table 23.
When the number of MCS indices (IMCS) is 14 and the resource assignment (IRU) is 5, the TBS index (ITBS) is indicated in Table 24.
When the number of MCS indices (IMCS) is 16 and the resource assignment (IRU) is 5, the TBS index (ITBS) is indicated in Table 25.
When the number of MCS indices (IMCS) is 14 and the resource assignment (IRU) is 6, the TBS index (ITBS) is indicated in Table 26.
When the number of MCS indices (IMCS) is 16 and the resource assignment (IRU) is 6, the TBS index (ITBS) is indicated in Table 27.
When the number of MCS indices (IMCS) is 14 and the resource assignment (IRU) is 7, the TBS index (ITBS) is indicated in Table 28.
When the number of MCS indices (IMCS) is 16 and the resource assignment (IRU) is 7, the TBS index (ITBS) is indicated in Table 29.
It can be seen from Tables 22-29, the MCS index is represented by 4 bits and the number of the MCS indices can be 14 or 16. On the other hand, the number of the TBS index can be 21 or 22. Therefore, some of the TBS indices (0 to 20 or to 21) are selected.
As an alternative way of determining the TBS index (ITBS), the TBS index (ITBS) may be determined by MCS index (IMCS) and scaling factor K. ITBS=round (KIMCS).
The scaling factor K is determined by the resource assignment (IRU). For a first example, when IRU=0 or 1 or 2 or 3 or 4, K=21/14; when IRU=5, K=19/14; when IRU=6, K=16/14; when IRU=7, K=1. For a second example, when IR=0 or 1 or 2 or 3 or 4, K=21/16; when IRU=5, K=19/16; when IRU=6 or 7, K=1. For a third example, when IRU=0 or 1 or 2 or 3 or 4, K=22/14; when IRU=5, K=19/14; when IRU=6, K=16/14; when IRU=7, K=1. For a fourth example, when IRU=0 or 1 or 2 or 3 or 4, K=22/16; when IRU=5, K=19/16; when IRU=6 or 7, K=1.
In the above determinations of the modulation order (Qm) and the TBS index (ITBS) according to the second embodiment, the modulation order (Qm) and the TBS index (ITBS) are determined separately for the resource assignment (IRU) being equal to 5 or 6 or 7. Alternatively, the modulation order (Qm) and the TBS index (ITBS) may be determined as the same values for the resource assignment (IRU) being equal to 5, 6 and 7. Table 30 indicates the determinations of the modulation order (Qm) and the TBS index (ITBS) based on the MCS index (IMCS) and the resource assignment (IRU), in which the same values are determined for IRU being equal to 1 or 2 or 3 or 4, and the same values are determined for IRU being equal to 5 or 6 or 7.
The third embodiment is related to a second solution of the support of 16QAM for NPUSCH data transmission of release 17. The second solution is related to adjusting the number of resource units.
According to the third embodiment, the number of resource units (NRU) is adjusted. The number of resource units is determined by the modulation order (Qm) in addition to the resource assignment (IRU). In particular, when 16QAM is used, the number of resource units is scaled down.
Table 31 indicates the number of resource units according to the third embodiment.
It can be seen from Table 31 that, when Qm is equal to 2, the number of resource units is 1, 2, 3, 4, 5, 6, 8 and 10 for the resource assignment (IRU) of 0, 1, 2, 3, 4, 5, 6 and 7, respectively. When Qm is equal to 4, the number of resource units is 1, 2, 3, 4 and 5 for the resource assignment (IRU) of 1, 3, 5, 6 and 7, respectively. As there are only 5 candidate numbers of resource units (i.e. 1 to 5) for Qm being equal to 4, it is enough to use only five resource assignments.
In Table 31, no value of NRU is configured for the resource assignment (IRU) being equal to 0, 2 and 4 when Qm is equal to 4. Alternatively, when Qm is equal to 4, the same value of NRU as that for IRU being equal to 1, 3 and 5 can be configured for IRU being equal to 0, 2 and 4, respectively. Table 32 indicates the alternative number of resource units according to the third embodiment.
BPSK and/or QPSK are assumed to be used in single-tone for coverage enhancement. Therefore, 16QAM is not suitable for single-tone. Under this assumption, 16QAM can be supported only in multiple-tone. A joint coding can be applied for subcarrier allocation and modulation order (Qm) for multiple-tone.
Table 33 indicates the joint coding of the modulation order (Qm) and allocated subcarriers for NPUSCH with Δf=15 kHz.
As can be seen from Table 33, each subcarrier indication field (ISC) can be used to indicate both the modulation order (Qm) and the allocated subcarriers.
In particular, when ISC=0 to 11, the modulation order (Qm) is 2 (i.e. QPSK), and the allocated carrier can be calculated by NSC=ISC. For example, when ISC=3, the allocated carrier is #3 (1 tone).
When ISC=12 to 15, the modulation order (Qm) is 2 (i.e. QPSK), and the allocated carriers can be calculated by NSC=3 (ISC−12)+{0, 1, 2}. For example, when ISC=13, the allocated carriers are #3, #4 and #5 (3 tones).
When ISC=16 to 17, the modulation order (Qm) is 2 (i.e. QPSK), and the allocated carriers can be calculated by NSC=6 (ISC−16)+{0, 1, 2, 3, 4, 5}. For example, when ISC=16, the allocated carriers are #0, #1 , #2 , #3 , #4 and #5 (6 tones).
When ISC=18, the modulation order (Qm) 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).
When ISC=19 to 22, the modulation order (Qm) is 4 (i.e. 16QAM), and the allocated carriers can be calculated by NSC=3 (ISC−19)+{0, 1, 2}. For example, when ISC=21, the allocated carriers are #6, #7 and #8 (3 tones).
When ISC=23 to 24, the modulation order (Qm) is 4 (i.e. 16QAM), and the allocated carriers can be calculated by NSC=6 (ISC−23)+{0, 1, 2, 3, 4, 5}. For example, when ISC=24, the allocated carriers are #6, #7 , #8 , #9 , #10 and #11 (6 tones).
When ISC=25, the modulation order (Qm) 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).
It can be seen that state values 19 to 25 indicate that the modulation order (Qm) is 4 (i.e. 16QAM).
The legacy TBS table is maintained. TBS is determined by TBS index (ITBS) and resource assignment (IRU). Table 34 indicates the Transport block size (TBS) table for NPUSCH according to the third embodiment.
Table 34 is the same as Table 5.
The TBS index (ITBS) is determined by MCS index (IMCS). For example, ITBS=IMCS.
The method 100 may include 102 transmitting a control signal, wherein the control signal includes a MCS index and a resource assignment index and 104 receiving or transmitting a coded data on a number of resource units (NRU) and a set of subcarrier(s), 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 (ITBS) is determined by at least one of the MCS index (IMCS) and the resource assignment index (IRU).
The method 200 may include 202 receiving a control signal, wherein the control signal includes a MCS index and a resource assignment index; and 204 transmitting or receiving a coded data on a number of resource units (NRU) and a set of subcarrier(s), 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 (ITBS) is determined by at least one of the MCS index (IMCS) and the resource assignment index (IRU).
Referring to
The memories may be positioned inside or outside the processors and connected with the processors by various well-known means.
In the embodiments described above, the components and the features of the embodiments are combined in a predetermined form. Each component or feature should be considered as an option unless otherwise expressly stated. Each component or feature may be implemented not to be associated with other components or features. Further, the embodiment may be configured by associating some components and/or features. The order of the operations described in the embodiments may be changed. Some components or features of any embodiment may be included in another embodiment or replaced with the component and the feature corresponding to another embodiment. It is apparent that the claims that are not expressly cited in the claims are combined to form an embodiment or be included in a new claim.
The embodiments may be implemented by hardware, firmware, software, or combinations thereof. In the case of implementation by hardware, according to hardware implementation, the exemplary embodiment described herein may be implemented by using 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, and the like.
Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects to be only illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/CN2020/071469 | 1/10/2020 | WO |
