Patent Description:
The following abbreviations and acronyms are herewith defined, at least some of which are referred to within the following description.

Third Generation Partnership Project ("3GPP"), Cyclic redundancy check ("CRC"), Downlink ("DL"), Downlink Pilot Time Slot ("DwPTS"), Evolved Node B ("eNB"), <NUM> Node B ("gNB"), European Telecommunications Standards Institute ("ETSI"), Frequency Division Duplex ("FDD"), Frequency-Division Multiplexing ("FDM"), Frequency Division Multiple Access ("FDMA"), Hybrid Automatic Repeat Request ("HARQ"), Hybrid Automatic Repeat Request-Positive Acknowledgement ("HARQ-ACK"), Hybrid Automatic Repeat Request-Negative Acknowledgement ("HARQ-NACK"), Information Element ("IE"), Long Term Evolution ("LTE"), LTE Advanced ("LTE-A"), Media Access Control ("MAC"), Master Information Block ("MIB"), Machine Type Communication ("MTC"), MTC physical downlink control channel ("MPDCCH"), New Radio ("NR"), Physical control format indicator channel ("PCFICH"), Physical Downlink Shared Channel ("PDSCH"), Physical hybrid ARQ indicator channel ("PHICH"), Physical Uplink Control Channel ("PUCCH"), Physical Uplink Shared Channel ("PUSCH"), Quadrature Phase Shift Keyin ("QPSK"), Quadrature amplitude modulation ("QAM"), Radio Resource Control ("RRC"), Received Signal Strength Indicator ("RSSI"), Reference Signal Received Power ("RSRP"), Reference Signal Received Quality ("RSRQ"), Receive ("RX"), System Information Block ("SIB"), Time Division Duplex ("TDD"), Time-Division Multiplexing ("TDM"), Transmit ("TX"), User Entity/Equipment (Mobile Terminal) ("UE"), Uplink ("UL"), Universal Mobile Telecommunications System ("UMTS").

MTC is expected to play an essential role within future <NUM> systems. It has been identified as an important use case for <NUM> NR wireless technology. Applications of this type are characterized by huge volumes of end-points and connections, using low-cost devices and modules for wireless sensor networks, connected home, smart metering and so on. It is expected that a new network is able to handle significantly larger numbers of connections efficiently, which is prompting the development of new technologies to support Bandwidth Reduced Low Complexity / Coverage Enhancement (BL/CE) UEs.

Particularly, in the RAN80 plenary meeting of 3GPP, a new work item for Rel. <NUM> eMTC is approved. The objective is to specify the following set of improvements for machine-type communications for BL/CE UEs: Enable the use of LTE control channel region for DL transmission (MPDCCH/PDSCH) to BL/CE UEs. In another aspect, Rel. <NUM> eMTC UEs are not required to receive PDCCH/PCFICH/PHICH channels. The starting OFDM symbol for PDSCH and MPDCCH for Rel. <NUM> eMTC UEs is predefined or indicated by System Information Block <NUM> - Bandwidth Reduced (SIB1-BR).

However, with regard to Rel. <NUM> eMTC/MTC UE, in order to improve the spectrum usage, the legacy LTE control region should be used by Rel. <NUM> eMTC/MTC UE. In another aspect, a new solution enabling the use of the LTE control channel region for DL transmission to BL/CE UEs should consider compatibility with Rel. <NUM> eMTC/MTC UEs. The <NPL> disclose related subject-matter.

Transmission of data over legacy LTE control channels such as PDCCH/PCFICH/PHICH can increase spectrum utilization and data throughput, especially for eMTC/MTC UEs that are BL/CE UEs. The present disclosures are aimed at supporting the transmission of data over legacy LTE control channels. In another aspect, in order to be compatible with the processing mechanism of legacy Rel. <NUM> eMTC UEs on the transmission of data, it is preferred for network equipment to enable a physical share (data) channel to carry data firstly, and then enable a physical control channel to carry additional data.

The method and apparatus for data transmission are disclosed. One method proposed for network equipment includes scrambling and modulating coded bits to generate data; mapping the data into a first resource block and a second resource block, both of which form a resource block, wherein the first resource block is from a symbol with an indicated index to a symbol with an end index of the resource block, the second resource block is from a symbol with a start index to a symbol with the indicated index minus one of the resource block.

Further, the method implemented by the network equipment comprises performing encoding of source bits to generate the coded bits, wherein a size of source bits is determined based on a first scaling factor, a first number of resource blocks and a predefined table.

Further, the method implemented by the network equipment comprises mapping the data, which is scrambled and modulated from a first portion of the coded bits, into the first resource block; and mapping the data, which is scrambled and modulated from a second portion of the coded bits, into the second resource block.

The method and apparatus disclosed herein not only provides a mechanism for supporting data transmission on the physical control region, but also provides new mechanisms for scaling source bits and selecting data for different physical channels. Thus, the method and apparatus disclosed herein contribute to increasing spectrum utilization data throughput.

Given that these drawings depict only some embodiments and are not therefore considered to be limiting in 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, aspects of the embodiments may be embodied as a system, apparatus, method, or a program product. Accordingly, embodiments may take the form of an all-hardware embodiment, an all-software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects.

Furthermore, one or more 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 device may be, for example, but is not limited to being, 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 may include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory ("RAM"), a read-only memory ("ROM"), an 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.

The terms "including", "comprising", "having", and variations thereof mean "including but not limited to", unless expressly specified otherwise. The terms "a", "an", and "the" also refer to "one or more" unless expressly specified otherwise.

Aspects of various embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products. 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 - executed via the processor of the computer or other programmable data processing apparatus - create a means for implementing the functions/acts specified in the schematic flowchart diagrams and/or schematic block diagrams.

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/acts specified in the schematic flowchart diagrams and/or schematic block diagram.

The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of different apparatuses, systems, methods, and program products according to various embodiments. One skilled in the relevant art will recognize, however, that the flowchart diagrams need not necessarily be practiced in the sequence shown and are able to be practiced without one or more of the specific steps, or with other steps not shown.

It should also be noted that, in some alternative implementations, the functions noted in the identified blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be substantially executed in concurrence, or the blocks may sometimes be executed in reverse order, depending upon the functionality involved.

Enhancements of a mechanism for data transmission to BL/CE UEs should be studied to enable the legacy LTE physical control channel, which is not received/solved by the legacy BL/CE UEs, to carry data. In this way, spectrum utilization, data throughput, as well as transmission efficiency, can be increased for the new BL/CE UEs. In the present application, method and apparatus for data transmission to BL/CE UEs are disclosed, which provides a few mechanisms for mapping data into both the legacy LTE physical control channel and physical data channels. Further, the compatibility with the legacy BL/CE UEs is also considered.

It should be noted that the physical channel, resource block, and physical resource block can be used alternatively in the present application. The legacy LTE physical control channel includes but is not limited to PDCCH, PHICH, PCFICH, while the physical share channel includes but is not limited to PDSCH.

<FIG> is a schematic diagram illustrating data mapping into different types of physical channels. An illustrative diagram for a resource block is shown in <FIG>, in which the lateral axis represents a time domain while the vertical axis represents a frequency domain. In one embodiment, the resource block is composed of a first resource block, which can be used for PDSCH to carry data generated from transport blocks (TB), and a second resource block, which can be used for legacy control channel such as PDCCH to carry signaling in a physical layer. As shown in <FIG>, the first resource block is from a symbol with an indicated index to a symbol with an end index of the resource block, and the second resource block is from a symbol with a start index to a symbol with the indicated index minus one of the resource block. The first resource block is used for PDSCH transmission, and the second resource block is used for legacy control channel such as PDCCH. In a particular MTC case, the second resource block can also use for PDSCH/data transmission. In another aspect, a resource block composed of both the first resource block and second resource block includes a few subcarriers in frequency domain, for example, <NUM> subcarriers are included in one resource block. As shown in <FIG>, an example of the resource block includes a region span of <NUM> symbols in time domain and <NUM> subcarriers in frequency domain. Particularly, the first resource block includes a region span of the last <NUM> symbols (symbol #<NUM> ~ symbol #<NUM>) in time domain and <NUM> subcarriers in frequency domain, and the second resource includes a region span of the first <NUM> symbols (symbol #<NUM> ~ symbol #<NUM>) in time domain and <NUM> subcarriers in the frequency domain, given that the indicated index is <NUM>. It should be understood that the first resource blocks and second resource block may include different regions determined by the indicated index, for example, the first resource block may include a region span of <NUM> symbols in time domain and <NUM> subscribers in frequency domain, in the case that the indicated index is <NUM>.

As shown in <FIG>, part A of the data in the form of symbols is mapped to the first resource block; part B of the data is mapped to the second resource block. The legacy BL/CE UEs are able to receive/resolve part A of the data in the first resource block. Correspondingly, the new BL/CE UEs are able to both receive/resolve part A of the data in the first resource block and part B of the data in the second resource block. Therefore, an extra gain for decoding can be obtained in the case that part B is a portion of part A of the data. Alternatively, spectrum utilization and/or data throughput can be increased if additional source bits are supported in the data, which will be described hereinafter.

<FIG> is a simple flow illustrating data processing in the physical layer of network equipment such as an eNB or a gNB. It should be understood that the processing modules shown in <FIG> are not limited to the ones shown. Particularly, additional modules can be added for data processing in the physical layer; alternatively, some shown modules can be removed from the procedure of data processing shown in <FIG>.

As shown in <FIG>, transport block containing source bits is received from the MAC layer. A size of source bits is determined based on Table <NUM> as a predefined table, which is shown in <FIG>. With regard to the new BL/CE UEs, a size of source bits can be scaled based on a first scaling factor to increase data throughput, which will be described hereinafter.

CRC is computed for the transport block and appended to the source block bits in order to realize error detection on the UE side. Then segmentation is performed on the transport block in the case that transport block size is more than an allowed code block size. In the case of eMTC and/or NB-IoT, in which the maximum size of transport block is <NUM>, the segmentation is not needed.

The bits contained in segmented transport block is encoded in the module of channel coding to generate coded bits. To be more particular, the module of channel coding may include a coder such as turbo coder, and a circular buffer. The coded bits from a coder are concentrated into a circular buffer for the coder to be selected. A few mechanisms for selection of coded bits from the circular buffer are described hereinafter. In one embodiment, turbo coded bits consist of three interleaving bit streams, followed by the collection of bits into a circular buffer. The output bits from the circular buffer are determined by the particular bit-selection mechanism as described hereinafter.

The coded bits are then scrambled for the purpose of interference randomization as part of the algorithm executed in the Scrambling block.

The scrambled bits are modulated according to the modulation order specified by a Modulation and Coding Schema (MCS) index IMCS in Table <NUM> shown in <FIG> to generate symbols (for example, QPSK corresponding to modulation order <NUM> , <NUM> QAM corresponding to modulation order <NUM>, or <NUM> QAM corresponding to modulation order <NUM>) as data as defined in <FIG>.

The symbols are mapped into the resource blocks. With regard to the new BL/CE UEs, a few mechanisms for mapping data into both the first resource block and the second resource block are described hereinafter.

A baseband signal is generated through Inverse fast Fourier transform (IFFT), a Cyclic Prefix (CP) is added to the signal in the time domain, and the signal is modulated to a Radio Frequency (not shown) for transmission, which is known for one skilled in the relevant art.

Enhancements on the determination of transport block size, selection of bits from the circular buffer, as well as mapping data into the resource block, are functions identified in the dashed frames shown in <FIG> and further described in <FIG>.

<FIG> is a call flow illustrating data mapping into resource blocks according to a first embodiment. The call flow is implemented at network equipment such as eNB/gNB. It should be understood that a inverse call flow is implemented at UE.

In step S301, the network equipment determines a size of source bits based on a first number of resource blocks and a predefined table. Particularly, the network equipment assigns an MCS index IMCS and a first number of resource blocks NPRB on the basis of Channel Quality Indication (CQI), which is based on values such as RSRP/RSRQ/RSSI reported from UE and other information for downlink transmission on PDSCH. Subsequently, the network equipment determines the TBS index ITBS based on the assigned MCS index IMCS defined in 'Table <NUM> Modulation and TBS Index' shown in <FIG> (only a portion thereof is included herein for the purpose of brevity), which is described in 3GPP TS <NUM> and learns a corresponding modulation order which is used in the modulation module shown in <FIG>. Finally, the network equipment determines a size of source bits based on the determined ITBS and assigned NPRB defined in 'Table <NUM> Determination of Transport Block Size' (shown in <FIG>) as the predefined table mentioned above. This is also described in 3GPP TS <NUM> (only a portion thereof is included herein for the purpose of brevity).

In step S302, the network equipment performs encoding on the source bits to generate the coded bits.

In step S303, the network equipment selects the coded bits from the circular buffer for the coder. As shown in <FIG>, which is a schematic diagram illustrating a circular buffer for a coder applicable for the embodiments, coded bits stored in different sections of the circular buffer are associated with different Redundancy Versions (RV), for example marked by RV0, RV1, RV2 and RV3 and specified by a different starting address, are selected to be scrambled, modulated and then mapped into different resource blocks later. Usually, coded bits associated with RV0 are selected for initial transmission, therefore, the starting address of RV0 is also known as the starting address of the circular buffer. It should be understood that although the circular buffer has been described to have four section associated with <NUM> RVs (i.e. RV0, RV1, RV2 and RV3) are shown in <FIG>, the number of sections of the circular buffer and hence, the number of associated RVs is not limited to four.

In another embodiment, in order to increase spectrum utilizaition/data throughput, a second portion of coded bits, which may be stored in RV section of the circular buffer described in <FIG> and marked by RVx_y. is to be scrambled, modulated, and then mapped into the second resource block later. Simultaneously, the first portion of coded bits, which is stored in RV section of the circular buffer marked by RVx, is to be scrambled, modulated and then mapped into the first resource blocks later, wherein, 'x' indicates a starting index of RV section of the circular buffer loaded with the first portion of coded bits, for example RV0, RV1, RV2 and RV3. On the contrary, 'y' indicates a different solution for selecting coded bits corresponding to the second resource block. Particularly, with regard to RVx section of the circular buffer loaded with the first portion of coded bits, there is more than one solution for selecting the second portion of coded bits. For example, in the case that coded bits stored in the portion of the circular buffer corresponding to RV1 are selected to be scrambled, modulated, and then mapped into the second resource block/PDSCH shown in <FIG>, coded bits stored in one of RV1_0, RV1_1, RV1_2 and RV1_3 portions of the circular buffer can be selected to be scrambled, modulated, and then mapped into the second resource block/PDCCH as shown in <FIG>.

Further, assuming the first portion of coded bits mapping to the first resource block has a first unit length 'M' and the second portion of coded bits mapping to the second resource block has a second unit length 'N', it's possible that the start address of RVx_y is determined according to the following:.

In summary, the first portion of coded bits has a first unit length, and is selected from a starting address plus zero or at least one times the first unit length of a circular buffer for a coder. That is, the starting address of the first portion of coded bits 'Add<NUM>' is determined according to Expression <NUM> below, where 'Add<NUM>' is the starting address of the circular buffer for the coder. For example, as mentioned above, the starting address of RV0 is usually used as the starting address of the circular buffer. 'M' is the length of the first portion of coded bits, which is the first unit length mentioned above. "x" is a non-negative integer, i.e. x=<NUM>,<NUM>,<NUM>,.

In another aspect, the second portion of coded bits has a second unit length and is selected from the starting address plus zero or at least one times the first unit length plus zero or at least one times the second unit length of the circular buffer. That is, the starting address of the second portion of coded bits 'Add<NUM>' is determined according to Expression <NUM>, where 'Add<NUM>' is the starting address of the circular buffer for the coder. As mentioned above, the starting address of RV0 is usually used as the starting address of the circular buffer. 'M' is the length of the first portion of coded bits, which is the first unit length mentioned above. 'N' is the length of the second portion of coded bits, which is the second unit length mentioned above. Both 'x' and 'y' are non-negative integers, i.e. x=<NUM>,<NUM>,<NUM>,. , y=<NUM>,<NUM>,<NUM>,.

Further, the first unit length 'M' is determined according to at least one of a type of resource block, the indicated index and a first modulation type such as QPSK, <NUM> QAM or <NUM> QAM. The second unit length 'N' is determined according to at least one of a type of resource block, the indicated index and a second modulation type such as QPSK, <NUM> QAM or <NUM> QAM. For example, in the case that the transport block is transmitted over DwPTS of the special subframe in frame structure type <NUM>, the time duration for the corresponding resource block is configured by a higher layer, which is also known that different types of resource blocks may occupy different time domains and/or frequency domains. Further, the available resource elements of the first resource block is determined by the symbols with the indicated index to the symbols with the end index of the first resource block. The available resource elements of the second resource block is determined by the symbol with the start index to the symbols with the indicated index minus <NUM>.

In step S304, the coded bits are scrambled for the purpose of interference randomization.

In step S305, the scramble bits are modulated according to the modulation order Qm or Q'm specified by the Modulation and Coding Schema (MCS) index IMCS in 'Table <NUM> Modulation vs. TBS Index' shown in <FIG>.

In step S306, the network equipment maps the data into a first resource block and a second resource block.

In one embodiment, the network equipment maps the data, which is scrambled and modulated from a first portion of the coded bits, into the first resource block, which is from a symbol with the indicated index to a symbol with the end index of the resource block. Then it maps the data, which is scrambled and modulated from a second portion of the coded bits, into the second resource block, which is from a symbol with the start index to a symbol with the indicated index minus one of the resource block. In this way, the legacy BL/CE UEs are still able to receive/resolve data in the first resource block according to the current mechanism, while the new BL/CE UEs are able to receive/resolve data in both the first resource block and the second resource block. Therefore, the spectrum utilization/ data throughput is increased for the new BL/CE UEs.

In another embodiment, the network equipment maps the data, which is scrambled and modulated from a first potion of the coded bits, into the first resource block, which is from a symbol with the indicated index to a symbol with the end index of the resource block; and maps a portion of the data in the first resource block into the second resource block, which is from a symbol with the start index to a symbol with the indicated index minus one of the resource block. In this way, the legacy BL/CE UEs are still able to receive/resolve data in PDSCH as/from the first resource block according to the current mechanism, while the new BL/CE UEs are able to receive/resolve data in both the first resource block and the second resource block to obtain extra gains for decoding.

To be more specific, the network equipment maps the data, which is scrambled and modulated from the coded bits, into the first resource block, which is from a symbol of the indicated index to a symbol of an end index of the resource block; and continues to map the data into the second resource block, which is from a symbol of a start index to a symbol of the indicated index minus one of the resource block. In this way, the legacy BL/CE UEs are still able to receive/resolve data in the first resource block according to the current mechanism, while the new BL/CE UEs are able to receive/resolve data in both the first resource block and the second resource block to obtain extra gains for decoding.

In a scenario for eMTC, a transport block directed to eMTC UEs is transmitted multiple times by the network equipment. Usually, the network equipment indicates a first repetition number in control signal, so that the eMTC UEs is able to expect the repetition number of the received transport block. In step S307, optionally, the network equipment indicates a first repetition number in DCI format, and configures the second scaling factor by RRC signaling or the second scaling factor is predefined. The network equipment transmits the data in the resource blocks by a second repetition number related to a second scaling factor. Then BL/CE UEs can derive the actual repetition number (i.e. the second repetition number)according to the first repetition number and the second scaling factor. To be more specific, the second repetition number is a product of the first repetition number and the scaling factor. Assuming that the indicated index is <NUM>, the start index of the resource block is <NUM> and the end index of the resource block is <NUM>, so the second resource block occupies <NUM> symbols and the first resource block occupies <NUM> symbols, yielding the second scaling factor of <NUM>/<NUM>. In another example, assuming that the indicated index is <NUM>, the start index of the resource block is <NUM> and the end index of the resource block is <NUM>, so the second resource block occupies <NUM> symbols and the first resource block occupies <NUM> symbols, yielding the second scaling factor of <NUM>/<NUM>. Therefore, it should be understood that the second scaling factor is related to the indicated index. However, the second scaling factor may be predefined value or may be also determined according to at least one of followings: a type of Cyclic Prefix (CP), a special subframe configuration defined in 3GPP TS36. <NUM>, and the indicated index. Particularly, the second scaling factor is <NUM>*<NUM> for special subframe configurations.

Further, the calculated repetition number meets at least one of followings: not less than a fifth threshold and not more than a sixth threshold.

Since the repetition number for transmission of PDSCH may be reduced, early reception of ACK/NACK for transmission of PDSCH based on HARQ can be achieved from the prospective of the network equipment.

In another aspect, although <FIG> shows a call flow implemented at the network equipment such as eNB or gNB, it should be understood that a inverse call flow is implemented at UE. Particularly, BL/CE UEs first receives the data in a first resource block and a second resource block, both of which form a resource block, wherein the first resource block is from a symbol with an indicated index to a symbol with an end index of the resource block, the second resource block is from a symbol with a start index to a symbol with the indicated index minus one of the resource block. BL/CE UEs should obtain (demodulates and descrambles) the data in a sequence same as that described in step S306.

<FIG> is a call flow illustrating data mapping into resource blocks according to a second embodiment. The enhancement of the call flow in <FIG> against that in <FIG> is that the size of resource bits is adjusted, given that the second resource block also carries user data.

In step S401, the network equipment assigns a first number of resource blocks NPRB, as well as an MCS index IMCS, on the basis of Channel Quality Indication (CQI), which is based on values such as RSRP/RSRQ/RSSI reported from UE and other information for downlink transmission on PDSCH.

In step S402, the network equipment determines a second number of resource blocks based on a first scaling factor and the first number of resource blocks. Particularly, the second number of resource blocks is related to the product of the first number of resource blocks and the scaling factor. To be more specific, the second number of resource blocks <MAT> is obtained according to expression <NUM>, given that the maximum number of (physical) resource blocks is <NUM> for eMTC UE <MAT> Wherein, α is the first scaling factor.

Assuming that the indicated index is <NUM>, the start index of the resource block is <NUM> and the end index of the resource block is <NUM>, so the second resource block occupies <NUM> symbols and the first resource block occupies <NUM> symbols, yielding the first scaling factor of <NUM>/<NUM>. In another example, assuming that the indicated index is <NUM>, the start index of the resource block is <NUM> and the end index of the resource block is <NUM>, so the second resource block occupies <NUM> symbols and the first resource block occupies <NUM> symbols, yielding the first scaling factor of <NUM>/<NUM>. Therefore, it should be understood that the first scaling factor is related to the indicated index. However, the first scaling factor may be predefined value or may be also determined according to at least one of following: a type of Cyclic Prefix (CP), a special subframe configuration, and the indicated index. Particularly, the first scaling factor α may be <NUM> for special subframe configurations <NUM> and <NUM> with normal cyclic prefix or special subframe configuration <NUM> with extended cyclic prefix the type and is <NUM> for other special subframe configurations.

According to expression <NUM>, the second number of resource blocks has both a maximum value (i.e. <NUM>) and a minimum value (i.e. <NUM>). However, the second number of resource blocks may be limited by either the maximum value or the minimum value. That is, the second number of resource blocks meets at least one of following: not less than a first threshold and not more than a second threshold.

In step S403, the network equipment determines a size of source bits based on a second number of resource blocks <MAT> and 'Table <NUM> Determination of Transport Block Size' (shown in <FIG>) as the predefined table mentioned above.

For example, assuming that α is <NUM>/<NUM>, a first number of resource blocks NPRB is <NUM> and MCS index is <NUM>, then ITBS is <NUM> according to the MCS index with the value of <NUM> in Table <NUM> shown in <FIG>, the second number of resource blocks <MAT> is <NUM> according to expression <NUM>. Therefore the size of source bits is <NUM> according to the TBS index ITBS with a value of <NUM> and the second number of resource blocks <MAT> with a value of <NUM> in Table <NUM> shown in <FIG>. In another aspect, without the application of the bits scaling, the size of source bits is <NUM> according to the TBS index ITBS with a value of <NUM> and the first number of resource blocks NPRB with a value of <NUM> in Table <NUM> shown in <FIG>.

The descriptions for steps S404-S409 in <FIG> are similar with that for steps S302-S307 in <FIG>. Thus, the descriptions thereof are omitted for the purpose of brevity.

<FIG> is a call flow illustrating data mapping into resource blocks according to a third embodiment. The enhancement of the call flow in <FIG> against that in <FIG> is that the size of resource bits is adjusted, given that the second resource block also carries user data.

In step S501, the network equipment assigns a first number of resource blocks NPRB, as well as an MCS index IMCS, on the basis of Channel Quality Indication (CQI), which is based on values such as RSRP/RSRQ/RSSI reported from UE and other information for downlink transmission on PDSCH.

In step S502, the network equipment determines a first size of source bits based on 'Table <NUM> Determination of Transport Block Size' (shown in <FIG>) as the predefined table and the first number of resource blocks.

In step S503, the network equipment determines a size of source bits based on the firs size of source bits NTBS and a first scaling factor. Particularly, the size of source bits is related to the product of the first size of source bits and the scaling factor. To be more specific, the size of source bits <MAT> is obtained according to expression <NUM>, given that the maximum number of (physical) resource blocks is <NUM> for eMTC UE <MAT> Wherein, α is the first scaling factor.

According to expression <NUM>, the size of source bits has both a maximum value (i.e. <NUM>) and a minimum value (i.e. <NUM>). However, the size of source bits may be limited by either the maximum value or the minimum value. That is, the size of source bits meets at least one of following: not less than a third threshold and not more than a fourth threshold. In another aspect, in order to comply with the current design for size of source bits, the size of source bits <MAT> is rounded to the nearest value in the predefined table, for example, it is rounded down to the nearest value in the predefined table.

For example, assuming that α is <NUM>/<NUM>, a first number of resource blocks NPRB is <NUM> and MCS index is <NUM>, then ITBS is <NUM> according to the MCS index with the value of <NUM> in Table <NUM> shown in <FIG>, the first size of source bits is <NUM> according to the TBS index ITBS with a value of <NUM> and the first number of resource blocks NPRB with a value of <NUM> in Table <NUM> shown in <FIG>, which is also a size of source bits without application of the bits scaling. Therefore, the size of source bits is <NUM> calculated by expression <NUM> and then is adjusted to be <NUM> by rounding down <NUM> to the nearest value in Table <NUM>.

The descriptions for steps S504-S509 in <FIG> are similar with those for steps S302-S307 in <FIG>. Thus, the descriptions therein are omitted for the purpose of brevity.

One skilled in the relevant art will recognize that the process described in <FIG> does not need to be practiced in the sequence shown in the Figures, and may be practiced without one or more of the specific steps or with other steps not shown in the Figures.

<FIG> is a schematic block diagram illustrating components of a UE such as BL/CE UEs according to one embodiment.

UE800 is an embodiment of the UE described from <FIG>. Furthermore, UE <NUM> may include a processor <NUM>, a memory <NUM>, and a transceiver <NUM>. In some embodiments, UE <NUM> may include an input device <NUM> and/or a display <NUM>. In certain embodiments, the input device <NUM> and the display <NUM> may be combined into a single device, such as a touch screen.

The processor <NUM> is communicatively coupled to the memory <NUM>, the input device <NUM>, the display <NUM>, and the transceiver <NUM>.

In some embodiments, the processor <NUM> controls the transceiver <NUM> to receive various configuration and data from Network Equipment <NUM>. In certain embodiments, the processor <NUM> may monitor DL signals received via the transceiver <NUM> for specific messages.

In some embodiments, the memory <NUM> stores data relating to trigger conditions for transmitting the measurement report to Network Equipment <NUM>. In some embodiments, the memory <NUM> also stores program code and related data, such as an operating system or other controller algorithms operating on UE <NUM>.

UE <NUM> may optionally include an input device <NUM>. In some embodiments, the input device <NUM> may be integrated with the display <NUM>, for example, as a touch screen or similar touch-sensitive display. In some embodiments, the input device <NUM> includes a touch screen such that text may be input using a virtual keyboard displayed on the touch screen and/or by handwriting on the touch screen. In certain embodiments, the input device <NUM> may include one or more sensors for monitoring an environment of UE <NUM>.

UE <NUM> may optionally include a display <NUM>. For example, the display <NUM> may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, or the like to a user.

In certain embodiments, the display <NUM> may include one or more speakers for producing sound. For example, the input device <NUM> and display <NUM> may form a touch screen or similar touch-sensitive display.

The transceiver <NUM>, in one embodiment, is configured to communicate wirelessly with Network Equipment <NUM>. In certain embodiments, the transceiver <NUM> comprises a transmitter <NUM> and a receiver <NUM>. The transmitter <NUM> is used to transmit UL communication signals to Network Equipment <NUM> and the receiver <NUM> is used to receive DL communication signals from Network Equipment <NUM>. For example, the transmitter <NUM> may transmit a HARQ-ACK codebook including feedbacks for one or more DL transmissions. As another example, the receiver <NUM> may receive various configurations/data from Network Equipment <NUM>.

The transmitter <NUM> and the receiver <NUM> may be any suitable types of transmitters and receivers. Although only one transmitter <NUM> and one receiver <NUM> are illustrated, the transceiver <NUM> may have any suitable number of transmitters <NUM> and receivers <NUM>. For example, in some embodiments, UE <NUM> includes a plurality of transmitter <NUM> and receiver <NUM> pairs for communicating on a plurality of wireless networks and/or radio frequency bands, each transmitter <NUM> and receiver <NUM> pair configured to communicate on a different wireless network and/or radio frequency band than the other transmitter <NUM> and receiver <NUM> pairs.

<FIG> is a schematic block diagram illustrating components of a network equipment according to one embodiment.

Network Equipment <NUM> includes one embodiment of eNB/gNB described from <FIG>. Furthermore, Network Equipment <NUM> may include a processor <NUM>, a memory <NUM>, an input device <NUM>, a display <NUM>, and a transceiver <NUM>. As may be appreciated, the processor <NUM>, the memory <NUM>, the input device <NUM>, and the display <NUM> may be substantially similar to the processor <NUM>, the memory <NUM>, the input device <NUM>, and the display <NUM> of UE <NUM>, respectively.

In some embodiments, the processor <NUM> controls the transceiver <NUM> to transmit DL signals/data to UE <NUM>. The processor <NUM> may also control the transceiver <NUM> to receive UL signals/data from UE <NUM>. For example, the processor <NUM> may control the transceiver <NUM> to receive a HARQ-ACK codebook including feedbacks for one or more DL transmissions. In another example, the processor <NUM> may control the transceiver <NUM> to transmit a DL signals for various configurations to UE <NUM>, as described above.

The transceiver <NUM>, in one embodiment, is configured to communicate wirelessly with UE <NUM>. In certain embodiments, the transceiver <NUM> comprises a transmitter <NUM> and a receiver <NUM>. The transmitter <NUM> is used to transmit DL communication signals to UE <NUM> and the receiver <NUM> is used to receive UL communication signals from UE <NUM>. For example, the receivers <NUM> may receive a HARQ-ACK codebook from UE <NUM>. As another example, the transmitter <NUM> may transmit the various configurations/data of Network Equipment <NUM>.

The transceiver <NUM> may communicate simultaneously with a plurality of UE <NUM>. For example, the transmitter <NUM> may transmit DL communication signals to UE <NUM>. As another example, the receiver <NUM> may simultaneously receive UL communication signals from UE <NUM>. The transmitter <NUM> and the receiver <NUM> may be any suitable types of transmitters and receivers. Although only one transmitter <NUM> and one receiver <NUM> are illustrated, the transceiver <NUM> may have any suitable number of transmitters <NUM> and receivers <NUM>. For example, Network Equipment <NUM> may serve multiple cells and/or cell sectors, wherein the transceiver <NUM> includes a transmitter <NUM> and a receiver <NUM> for each cell or cell sector.

Claim 1:
An apparatus comprising:
a processor (<NUM>) that is configured to:
scramble and modulate coded bits to generate data;
map the data into a first resource block and a second resource block, both of which form a resource block, wherein the first resource block is from a symbol with an indicated index to a symbol with an end index of the resource block, the second resource block is from a symbol with a start index to a symbol with the indicated index minus one of the
resource block;
a transmitter (<NUM>) that is configured to:
transmit the data in the resource block;
wherein the processor (<NUM>) is further configured to:
map the data, which are scrambled and modulated from a first portion of the coded bits, into the first resource block;
map the data, which are scrambled and modulated from a second portion of the coded bits, into the second resource block.