METHOD FOR A TRANSPORT BLOCK SIZE DETERMINATION PROCEDURE
20230058672 · 2023-02-23
Assignee
Inventors
- Qiujin GUO (Shenzhen, CN)
- Jun Xu (Shenzhen, CN)
- Mengzhu CHEN (Shenzhen, CN)
- Xiaoying MA (Shenzhen, CN)
- Qiang FU (Shenzhen, CN)
- Jian KANG (Shenzhen, CN)
Cpc classification
H04W52/0219
ELECTRICITY
H04W72/23
ELECTRICITY
H04W52/0216
ELECTRICITY
International classification
Abstract
A wireless communication method for use in a wireless terminal is disclosed. The wireless communication method comprises determining an intermediate transport block size (TBS) for a transport block transmitted between the wireless terminal and a wireless network node based on a plurality of transmission parameters, modifying the intermediate TBS to generate a modified TBS in response to at least one event, and determining a final TBS based on the modified TBS and a specific step in response to the at least one event, wherein the specific step is determined based on the plurality of transmission parameters
Claims
1. A wireless communication method for use in a wireless terminal, the wireless communication method comprising: determining an intermediate transport block size (TBS) for a transport block transmitted between the wireless terminal and a wireless network node based on a plurality of transmission parameters, modifying the intermediate TBS to generate a modified TBS in response to at least one event, and determining a final TBS based on the modified TBS and a specific step in response to the at least one event, wherein the specific step is determined based on the plurality of transmission parameters.
2. The wireless communication method of claim 1, wherein the plurality of transmission parameters comprises at least one of: a downlink control information (DCI) format, a type of a transmission mode configured for the wireless terminal, a type of a frequency range, a type of a radio network temporary identifier (RNTI) scrambling a cyclic redundancy check (CRC) of DCI, the number of physical resource blocks (PRBs) used to determine the intermediate TBS, the modulation and coding scheme (MCS) index used to determine the code rate and modulation order, a coverage capability of the wireless terminal, the value of sub-carrier spacing, or a value of an average orthogonal frequency-division multiplexing (OFDM) symbol duration, wherein the transmission mode is determined based on one of a user equipment (UE) capability and a UE category, wherein the number of physical resource blocks is smaller than or equal to the maximum number of PRBs, wherein the maximum number of PRBs is determined based on at least one of the maximum bandwidth supported by the wireless terminal, the maximum symbols per slot used for data scheduling, and the type of the transmission mode of the wireless terminal, and wherein the type of the transmission mode of the wireless terminal is associated with at least one of: the maximum bandwidth supported by the wireless terminal, the minimum bandwidth supported by the wireless terminal, the maximum number of layers supported by the wireless terminal, the maximum number of antenna ports for transmitting the signal, a peak data rate for uplink and/or downlink supported by the wireless terminal, a battery life of the wireless terminal, a modulation order supported by the wireless terminal, the maximum code rate supported by the wireless terminal, the maximum TBS supported by the wireless terminal, the maximum number of physical resource blocks associated with a bandwidth supported by the wireless terminal, a target block error rate of transmitting the signal, an end-to-end latency supported by the wireless terminal, the number of frequency range FR types supported by the wireless terminal, a coverage enhancement capability of the wireless terminal, a power class of the wireless terminal, a processing time capability of the wireless terminal, a type of use case of the wireless terminal, wherein the use case comprises at least one of an industrial wireless sensor, a video surveillance or a wearable device, or a duplex mode of the wireless terminal.
3. The wireless communication method of claim 1, wherein the final TBS is smaller than or equal to the maximum TBS, wherein the maximum TBS is determined based on the plurality of transmission parameters, wherein the plurality of transmission parameters includes at least one of the maximum code block size, the maximum code rate supported by the wireless terminal, the maximum code rate of MCS table, the maximum modulation order supported by the wireless terminal and the maximum modulation order of the MCS table, wherein the maximum TBS is: one of elements in a TBS table which is greater than or equal to the product of the maximum code block size and a ratio of the maximum code rate supported by the wireless terminal and the maximum code rate in a configurable modulation and coding scheme (MCS) table, wherein the ratio of the maximum code rate supported by the wireless terminal and the maximum code rate in the configurable MCS table is a value in a range [0.27, 0.7201], and wherein the maximum code block size is equal to 3840 for low-density parity-check (LDPC) base graph 2 and is 8448 for LDPC base graph 1, or one of elements in a TBS table which is greater than or equal to a product of the maximum code block size and a ratio of the maximum modulation order supported by the wireless terminal and the maximum modulation order in a configurable MCS table, wherein the ratio of the maximum modulation order supported by the wireless terminal and the maximum modulation order in the configurable MCS table is a value in a range [0.25, 1], and wherein the maximum code block size is equal to 3840 for LDPC base graph 2 and 8448 for LDPC base graph 1.
4. The wireless communication method of claim 1, wherein the final TBS is smaller than or equal to the maximum TBS, wherein the maximum TBS for a first type of a transmission mode comprises at least one element in a first TBS set and the maximum TBS for a second type of the transmission mode comprises at least one element in a second TBS set, wherein the transport block is transmitted in: a physical downlink shared channel, wherein the first TBS set comprises at least one of {1000, 1736, 3752, 3824, 3840, 4008, 5160, 8424, 27376, 51240}, a physical uplink shared channel, wherein the first TBS set comprises at least one of {328, 408, 456, 504, 600, 712, 808, 936, 1000, 1736, 3752, 3824, 3840, 4008, 5160, 8424}, a physical downlink shared channel, wherein the second TBS set comprises at least one of {8424, 15110, 15370, 15620, 15880, 16140, 27376, 50180, 51220}, or a physical uplink shared channel, wherein the second TBS set comprises at least one of {3824, 5160, 8424, 25100, 27376}, and wherein: a value of any element in the first TBS set is smaller than or equal to 5160 and a value of any element in the second TBS set is smaller than or equal to 8848, or a value of any element in the first TBS set is smaller than or equal to 3840 and a value of any element in the second TBS set is smaller than or equal to 3840.
5. The wireless communication method of claim 1, wherein the wireless terminal supports LDPC base graph 2, and wherein the intermediate TBS or the final TBS is smaller than or equal to 3824.
6. The wireless communication method of claim 1, wherein the at least one event comprises at least one of the intermediate TBS is greater than 3824, the wireless terminal supports LDPC based graph 2, the type of RNTI scrambling the CRC of the DCI is an RNTI other than the RNTI in Rel-16 NR, or the type of transmission mode is a first type of transmission mode including the maximum modulation order smaller than or equal to 64 quadrature amplitude modulation (QAM), wherein the specific step comprises using a TBS table to determine the closest TBS that is greater than or equal to the modified TBS, each element in the TBS table is different from all of the elements in TBS table in Rel-16 NR, and each element in the TBS table is divisible by 3816 and a quotient of the element divided by 3816 is larger than 1, wherein the final TBS is determined by:
n=└log.sub.2(N.sub.info−24)┘−5, wherein └ ┘ is a bottom function.
7. The wireless communication method of claim 1, wherein the number of physical resource blocks in the signal is quantized by a scaling factor which is associated with a bandwidth of a bandwidth part of the wireless terminal.
8. The wireless communication method of claim 1, wherein a MCS table with transform precoding is used for transmitting the transport block, and wherein the wireless terminal is configured with a type of transmission mode which is associated with at least one of: a type of a radio network temporary identifier scrambling a cyclic redundancy check of downlink control information, a peak data rate for uplink and/or downlink, a battery life of the wireless terminal, a modulation order supported by the wireless terminal, the maximum code rate, the maximum TBS supported by the wireless terminal, the maximum number of physical resource blocks associated with a bandwidth configured for of a bandwidth part of the wireless terminal, a target block error rate of transmitting the transport block, an end-to-end latency supported by the wireless terminal, the type of frequency range supported by the wireless terminal, a coverage enhancement capability of the wireless terminal, a power class of the wireless terminal, a processing time capability of the wireless terminal, a use case of the wireless terminal, wherein the use case comprises at least one of an industrial wireless sensor, a video surveillance or a wearable device, or a duplex mode supported by the wireless terminal.
9. The wireless communication method of claim 1, wherein a buffer size for LDPC rate matching is determined by a higher layer signaling comprising at least one of: the maximum bandwidth supported by the wireless terminal, the number of physical resource blocks available for the wireless terminal in a bandwidth supported by the wireless terminal, the maximum number of layers supported by the wireless terminal, a peak data rate supported by the wireless terminal, the maximum modulation order supported by the wireless terminal, a bandwidth part activated for the wireless terminal, or a type of a radio network temporary identifier scrambling cyclic redundancy check of downlink control information.
10. A wireless communication method for use in a wireless network node, the wireless communication method comprising: transmitting, to a wireless terminal, a signal comprising a plurality of transmission parameters; determining an intermediate transport block size (TBS) for a transport block transmitted between the wireless terminal and the wireless network node based on the plurality of transmission parameters, modifying the intermediate TBS to generate a modified TBS in response to at least one event, and determining a final TBS based on the modified TBS and a specific step in response to the at least one event, wherein the specific step is determined based on the plurality of transmission parameters.
11. The wireless communication method of claim 10, wherein the plurality of transmission parameters comprises at least one of: a downlink control information (DCI) format, a type of a transmission mode configured for the wireless terminal, a type of a frequency range, a type of a radio network temporary identifier (RNTI) scrambling a cyclic redundancy check (CRC) of DCI, the number of physical resource blocks (PRBs) used to determine the intermediate TBS, the modulation and coding scheme (MCS) index used to determine the code rate and modulation order, a coverage capability of the wireless terminal, the value of sub-carrier spacing, or a value of an average orthogonal frequency-division multiplexing (OFDM) symbol duration, wherein the transmission mode is determined based on one of a user equipment (UE) capability and a UE category, wherein the number of physical resource blocks is smaller than or equal to the maximum number of PRBs, wherein the maximum number of PRBs is determined based on at least one of the maximum bandwidth supported by the wireless terminal, the maximum symbols per slot used for data scheduling, and the type of the transmission mode of the wireless terminal, and wherein the type of the transmission mode of the wireless terminal is associated with at least one of: the maximum bandwidth supported by the wireless terminal, the minimum bandwidth supported by the wireless terminal, the maximum number of layers supported by the wireless terminal, the maximum number of antenna ports for transmitting the signal, a peak data rate for uplink and/or downlink supported by the wireless terminal, a battery life of the wireless terminal, a modulation order supported by the wireless terminal, the maximum code rate supported by the wireless terminal, the maximum TBS supported by the wireless terminal, the maximum number of physical resource blocks associated with a bandwidth supported by the wireless terminal, a target block error rate of transmitting the signal, an end-to-end latency supported by the wireless terminal, the number of frequency range FR types supported by the wireless terminal, a coverage enhancement capability of the wireless terminal, a power class of the wireless terminal, a processing time capability of the wireless terminal, a type of use case of the wireless terminal, wherein the use case comprises at least one of an industrial wireless sensor, a video surveillance or a wearable device, or a duplex mode of the wireless terminal.
12. The wireless communication method of claim 10, wherein the final TBS is smaller than or equal to the maximum TBS, wherein the maximum TBS is determined based on the plurality of transmission parameters, wherein the plurality of transmission parameters includes at least one of the maximum code block size, the maximum code rate supported by the wireless terminal, the maximum code rate of MCS table, the maximum modulation order supported by the wireless terminal and the maximum modulation order of the MCS table, wherein the maximum TBS is: one of elements in a TBS table which is greater than or equal to the product of the maximum code block size and a ratio of the maximum code rate supported by the wireless terminal and the maximum code rate in a configurable modulation and coding scheme (MCS) table, wherein the ratio of the maximum code rate supported by the wireless terminal and the maximum code rate in the configurable MCS table is a value in a range [0.27, 0.7201], and wherein the maximum code block size is equal to 3840 for low-density parity-check (LDPC) base graph 2 and is 8448 for LDPC base graph 1, or one of elements in a TBS table which is greater than or equal to a product of the maximum code block size and a ratio of the maximum modulation order supported by the wireless terminal and the maximum modulation order in a configurable MCS table, wherein the ratio of the maximum modulation order supported by the wireless terminal and the maximum modulation order in the configurable MCS table is a value in a range [0.25, 1], and wherein the maximum code block size is equal to 3840 for LDPC base graph 2 and 8448 for LDPC base graph 1.
13. The wireless communication method of claim 10, wherein the final TBS is smaller than or equal to the maximum TBS, wherein the maximum TBS for a first type of a transmission mode comprises at least one element in a first TBS set and the maximum TBS for a second type of the transmission mode comprises at least one element in a second TBS set, wherein the transport block is transmitted in: a physical downlink shared channel, wherein the first TBS set comprises at least one of {1000, 1736, 3752, 3824, 3840, 4008, 5160, 8424, 27376, 51240}, a physical uplink shared channel, wherein the first TBS set comprises at least one of {328, 408, 456, 504, 600, 712, 808, 936, 1000, 1736, 3752, 3824, 3840, 4008, 5160, 8424}, a physical downlink shared channel, wherein the second TBS set comprises at least one of {8424, 15110, 15370, 15620, 15880, 16140, 27376, 50180, 51220}, or a physical uplink shared channel, wherein the second TBS set comprises at least one of {3824, 5160, 8424, 25100, 27376}, and wherein a value of any element in the first TBS set is: smaller than or equal to 5160 and a value of any element in the second TBS set is smaller than or equal to 8848, or smaller than or equal to 3840 and a value of any element in the second TBS set is smaller than or equal to 3840.
14. The wireless communication method of claim 10, wherein the wireless terminal supports LDPC base graph 2, and wherein the intermediate TBS or the final TBS is smaller than or equal to 3824.
15. The wireless communication method of claim 10, wherein the at least one event comprises at least one of the intermediate TBS is greater than 3824, the wireless terminal supports LDPC based graph 2, the type of RNTI scrambling the CRC of the DCI is an RNTI other than the RNTI in Rel-16 NR, or the type of transmission mode is a first type of transmission mode including the maximum modulation order smaller than or equal to 64 quadrature amplitude modulation (QAM), wherein the specific step comprises using a TBS table to determine the closest TBS that is greater than or equal to the modified TBS, wherein each element in the TBS table is different from all of the elements in TBS table in Rel-16 NR, and wherein each element in the TBS table is divisible by 3816 and a quotient of the element divided by 3816 is larger than 1, wherein the final TBS is determined by:
n=└log.sub.2(N.sub.info−24)┘−5, wherein └ ┘ is a bottom function.
16. The wireless communication method of claim 10, wherein the number of physical resource blocks in the signal is quantized by a scaling factor which is associated with a bandwidth of a bandwidth part of the wireless terminal.
17. The wireless communication method of claim 10, wherein a MCS table with transform precoding is used for transmitting the transport block, and wherein the wireless terminal is configured with a type of transmission mode which is associated with at least one of: a type of a radio network temporary identifier scrambling a cyclic redundancy check of downlink control information, a peak data rate for uplink and/or downlink, a battery life of the wireless terminal, a modulation order supported by the wireless terminal, the maximum code rate, the maximum TBS supported by the wireless terminal, the maximum number of physical resource blocks associated with a bandwidth configured for of a bandwidth part of the wireless terminal, a target block error rate of transmitting the transport block, an end-to-end latency supported by the wireless terminal, the type of frequency range supported by the wireless terminal, a coverage enhancement capability of the wireless terminal, a power class of the wireless terminal, a processing time capability of the wireless terminal, a use case of the wireless terminal, wherein the use case comprises at least one of an industrial wireless sensor, a video surveillance or a wearable device, or a duplex mode supported by the wireless terminal.
18. The wireless communication method of claim 10, wherein a buffer size for LDPC rate matching is determined by a higher layer signaling comprising at least one of: the maximum bandwidth supported by the wireless terminal, the number of physical resource blocks available for the wireless terminal in a bandwidth supported by the wireless terminal, the maximum number of layers supported by the wireless terminal, a peak data rate supported by the wireless terminal, the maximum modulation order supported by the wireless terminal, a bandwidth part activated for the wireless terminal, or a type of a radio network temporary identifier scrambling cyclic redundancy check of downlink control information.
19. A wireless terminal, comprising a processor configured to: determine an intermediate transport block size (TBS) for a transport block transmitted between the wireless terminal and a wireless network node based on a plurality of transmission parameters, modify the intermediate TBS to generate a modified TBS in response to at least one event, and determine a final TBS based on the modified TBS and a specific step in response to the at least one event, wherein the specific step is determined based on the plurality of transmission parameters.
20. A wireless network node, comprising: a communication unit, configured to transmit, to a wireless terminal, a signal indicating a plurality of transmission parameters, and a processor, configured to: determine an intermediate transport block size (TBS) for a transport block transmitted between the wireless terminal and the wireless network node based on the plurality of transmission parameters, modify the intermediate TBS to generate a modified TBS in response to at least one event, and determine a final TBS based on the modified TBS and a specific step in response to the at least one event, and wherein the specific step is determined based on the plurality of transmission parameters.
Description
BRIEF DESCRIPTION OF THE DRAWINGS
[0101] The above and other aspects and their implementations are described in greater detail in the drawings, the descriptions, and the claims.
[0102]
[0103]
[0104]
[0105]
[0106]
DETAILED DESCRIPTION
[0107] In an embodiment, the storage unit 110 and the program code 112 may be omitted and the processor 100 may include a storage unit with stored program code.
[0108] The processor 100 may implement any one of the steps in exemplified embodiments on the wireless terminal 10, e.g., by executing the program code 112.
[0109] The communication unit 120 may be a transceiver. The communication unit 120 may as an alternative or in addition be combining a transmitting unit and a receiving unit configured to transmit and to receive, respectively, signals to and from a wireless network node (e.g. a base station).
[0110]
[0111] In an embodiment, the storage unit 210 and the program code 212 may be omitted. The processor 200 may include a storage unit with stored program code.
[0112] The processor 200 may implement any steps described in exemplified embodiments on the wireless network node 20, e.g., via executing the program code 212.
[0113] The communication unit 220 may be a transceiver. The communication unit 220 may as an alternative or in addition be combining a transmitting unit and a receiving unit configured to transmit and to receive, respectively, signals to and from a wireless terminal (e.g. a user equipment).
[0114] In general, there is a new type of NR device called reduced capability UE (RedCap UE) including three use cases: industrial wireless sensors, video surveillance and wearables. These three types of NR devices have different requirements on the parameters of data rate, end-to-end latency, reliability and battery life as shown in Table 2 below. The data rate among the requirements for different use cases may be very different. Therefore, it is necessary to support a limited or reduced capability for some use cases with lower data rate, such as a limited bandwidth, a limited maximum number of MIMO layers, or a limited modulation order etc. Some of the limited parameters are associated with the transport block size (TBS) determination.
[0115] According to an embodiment, the TBS determination methods for RedCap UE described herein are methods of defining the limited capability and TBS determination procedure for RedCap UE.
TABLE-US-00003 TABLE 2 Use cases and requirements for Rel-17 REDCAP E-to-E Battery Use cases Data rate latency reliability cost life Industrial less than 2 less 99.99% Low Few wireless Mbps than years sensors (potential 100 (≥5 yr (TS asymmetric, ms, in TR 22.104) e.g. UL 5~10 ms 22.832) heavy safety traffic) related (TR 22.804) Video Economic less 99%~ Medium — Surveillance video: 2-4 than 99.9% or less Mbps 500 ms limitation High-end video: 7.5- 25 Mbps (TR 22.804) Wearables Peak DL Same Same as Medium multiple (small in up to as eMBB days size) 150 Mbps, eMBB (up to peak UL 1-2 up to weeks) 50 Mbps, 2-5 Mbps in UL and 5-50 Mbps in DL
[0116] In the present disclosure, the higher layer parameter may be the MAC layer signaling and/or the RRC signaling. In the following embodiments, the term “and” may be used for either “and” or “or” or “and/or”. In the present disclosure, a RedCap UE may correspond to a UE with one or more limited parameters, wherein the parameters include at least one of the following: 1) the UL/DL bandwidth, 2) the data rate for UL/DL, 3) the modulation order for UL/DL, 4) the code rate for UL/DL, 5) the number of layers for UL/DL.
[0117] In the present disclosure, the parameter may be defined as follows:
[0118] In some embodiments, the bandwidth in the unit of MHz represents the frequency domain resource. In some embodiments, the bandwidth may be at least one of the values {1, 2, 2.5, 5, 10, 15, 20, 25, 30, 40, 50, 60, 70, 80, 90, 100} MHz. In some embodiments, the maximum transmission bandwidth configuration N.sub.RB for each UE channel bandwidth and subcarrier spacing is specified in Table 3 below.
TABLE-US-00004 TABLE 3 Maximum transmission bandwidth configuration N.sub.RB 5 MHz 10 MHz 15 MHz 20 MHz 25 MHz 30 MHz 40 MHz 50 MHz 60 MHz 70 MHz 80 MHz 90 MHz 100 MHz SCS (kHz) N.sub.RB N.sub.RB N.sub.RB N.sub.RB N.sub.RB N.sub.RB N.sub.RB N.sub.RB N.sub.RB N.sub.RB N.sub.RB N.sub.RB N.sub.RB 15 25 52 79 106 133 160 216 270 N/A N/A N/A N/A N/A 30 11 24 38 51 65 78 106 133 162 189 217 245 273 60 N/A 11 18 24 31 38 51 65 79 93 107 121 135
[0119] In some embodiments, the maximum number of available PRBs for each maximum transmission bandwidth may be determined by the transmission bandwidth and the minimum guard for each transmission bandwidth and SCS (kHz). For a UE, all PRBs falling within the UE channel bandwidth not covering the minimum guard band may be used.
[0120] In some embodiments, the combination of channel bandwidths, SCS and operating bands is specified and the combination of channel bandwidths and SCS available for each operating band is different. In some embodiments, the operating band includes at least one of the followings: {n1, n2, n3, n5, n7, n8, n12, n14, n18, n20, n25, n26, n28, n29, n30, n34, n38, n39, n40, n41, n48, n50, n51, n53, n65, n66, n70, n71, n74, n75, n76, n77, n78, n79, n80, n81, n82, n83, n84, n86, n89, n90, n91, n92, n93, n94, n95}. In some embodiments, the operating band may be used for DFT-s-OFDM and/or CP-OFDM waveform configured by higher layer parameter for a UE.
[0121] For intra-band contiguous carrier aggregation, a carrier aggregation configuration is a single operating band supporting a carrier aggregation bandwidth class with associated bandwidth combination sets. For each carrier aggregation configuration, requirements are specified for all aggregated channel bandwidths contained in a bandwidth combination set, a UE can indicate support of several bandwidth combination sets per carrier aggregation configuration.
[0122] For intra-band non-contiguous carrier aggregation, a carrier aggregation configuration is a single operating band supporting two or more sub-blocks, each of which supports a carrier aggregation bandwidth class.
[0123] For inter-band carrier aggregation, a carrier aggregation configuration is a combination of operating bands, each of which supports a carrier aggregation bandwidth class.
[0124] In some embodiments, the peak data rate represents the maximum data rate supported by the UE for UL and/or DL. The peak data rate in a unit of Mbps (10.sup.6 bits per second) may be determined based on at least one of the followings: 1) the number of aggregated component carriers in a band or band combination, 2) the maximum number of supported layers for the UE for the uplink or downlink, 3) the maximum rate supported by the UE, 4) the maximum modulation order supported by the UE configured by higher layer parameter for uplink or downlink, 5) the scaling factor given by higher layer parameter, 6) the numerology (μ), 7) the average OFDM symbol duration in a subframe for numerology (μ), 8) the maximum RB allocation in bandwidth BW with numerology μ supported by the UE, 9) the overhead, 10) the maximum TBS supported by the UE. BW is the UE supported maximum bandwidth in the given band or band combination.
[0125] In some embodiments, the time of battery life represents the time for the UE to continuously work, i.e. without recharging. In some embodiments, the time of battery life may be longer if the UE uses power saving techniques.
[0126] In some embodiments, the UE processing time capability represents at least one of the followings: 1) physical downlink shared channel (PDSCH) processing time N1, 2) physical uplink shared channel (PUSCH) preparation procedure time N2, 3) MAC (Medium Access Control) CE (Control Element) processing time, 4) channel state information (CSI) computation time, 5) physical downlink control channel (PDCCH) decoding time, 6) the minimum applicable scheduling offset indicated by DCI format 0_1/1_1 including the minimum applicable K0 and/or K2 and/or the minimum applicable value of the aperiodic CSI-RS triggering offset and/or the minimum applicable value of aperiodic SRS triggering offset, 7) the value of K0, and/or K1, and/or K2, and/or aperiodic CSI-RS triggering offset, and/or aperiodic SRS triggering offset.
[0127] The PDSCH processing time N1 may represent a number of symbols for the UE to process PDSCH, which is used to calculate the minimum time gap between the end of the last symbol of the PDSCH carrying the transport block (TB) being acknowledged and the first uplink symbol of the physical uplink control channel (PUCCH), which carriers the Hybrid automatic repeat request acknowledgement (HARQ-ACK) information.
[0128] The PUSCH preparation procedure time N2 may represent a number of symbols, which is used to calculate a minimum time gap between the end of the reception of the last symbol of the PDCCH carrying the downlink control information (DCI) scheduling the PUSCH and the first uplink symbol in the PUSCH. MAC CE processing time may represent the time between a PUCCH with HARQ-ACK information and the slot applying the command carried by PDSCH.
[0129] The CSI computation time may represent a number of symbols, which is used to calculate a minimum time gap between the end of the last symbol of the PDCCH triggering a CSI report and the uplink symbol of the CSI report, or used to calculate a minimum time gap between the end of the last symbol in time of the latest of: aperiodic channel state information reference signal (CSI-RS) resource for channel measurements, aperiodic CSI-Intereference Measurement (IM) used for interference measurements, and aperiodic non zero power (NZP) CSI-RS for interference measurement and the first uplink symbol of n-th CSI report. PDCCH decoding time may represent the time used for UE to decode a PDCCH/DCI.
[0130] Aperiodic CSI-RS triggering offset may include a slot offset between a triggering downlink control information and an aperiodic non zero power channel state information reference signal (NZP CSI-RS) resources set. Aperiodic SRS triggering offset may include an offset in number of slots between the triggering DCI and the actual transmission of this SRS-ResourceSet. K0 may include an offset between DCI and its scheduled PDSCH. K2 may include a slot offset between DCI and its scheduled PUSCH. K1 may include a slot offset between PDSCH and the DL ACK or slot offset between DCI and HARQ. Wherein the minimum K0/K1/K2/A-CSI-RS triggering offset/A-SRS triggering offset are the minimum applicable value of the parameter indicated by DCI format 0_1/1_1.
[0131] In some embodiments, the target block error rate (BLER) for the data transmission represents the target BLER to be used to report the available channel quality information (CQI) by the UE. In some embodiments, the target BLER can be at least one of the following values: {0.1, 0.01, 0.001, 0.00001}.
[0132] In some embodiments, the power class represents the performance for the UE to consume power. For example, the UE may support power class 3 by using some specific power saving techniques.
[0133] In some embodiments, the duplex mode represents the capability of whether both the UE side and the network side are able to receive and transmit data at/to the same resource. The duplex mode in NR may include time-division duplex (TDD) and frequency-division duplex (FDD).
[0134] In some embodiments, the frequency range represents the different operation bands. In 5G NR, there are two types of frequency range including FR1 and FR2. FR1 represents an operating band frequency range between 450 MHz and 6000 MHz, and FR2 represents an operating band frequency range between 24250 MHz and 52600 MHz.
[0135] In some embodiments, the end-to-end latency means the time of latency for the UE to process data transmission completely relative to the data processed completely in general. In some embodiments, the maximum end-to-end latency supported by the UE can be at least one of the following values: 5 ms, 10 ms, 100 ms and/or 500 ms.
[0136] In some embodiments, the type of use case represents the scenario or purpose or device size that the user equipment should use. For example, there can be three types of use cases including 1) industrial wireless sensors, 2) video Surveillance, and 3) wearables according to the different purpose and scenarios. For example, there can be two types of use case including 1) wireless sensors and video Surveillance, 2) wearables according to the different device sizes.
[0137] In some embodiments, the coverage capability or the coverage enhancement represents the maximum number of repetition for a data transmission; and/or the transmit power; and/or the SRS transmission power determined by the UE; and/or the UE configured maximum output power for a carrier f of primary cell c in PUCCH transmission occasion i, etc. For example, if the UE supports a smaller maximum number of repetition than the general UE, it means the UE can transmit data under a coverage without a large amount of repetition, namely, the UE has an enhanced coverage capability.
[0138] An embodiment relates to a transmission mode for RedCap UE.
[0139] In some embodiments, there are N types of transmission modes for the RedCap UE. In some embodiments, each type of transmission mode includes a set of parameters. In some embodiments, the set of parameters for UL and DL includes at least one of the followings: [0140] 1) the maximum bandwidth, [0141] 2) the minimum bandwidth, [0142] 3) the maximum number of layers in spatial domain, [0143] 4) the maximum number of antenna ports for data transmission, [0144] 5) the peak data rate, [0145] 6) the time of battery life, [0146] 7) the supported modulation order, [0147] 8) the maximum code rate, [0148] 9) the supported maximum TBS, [0149] 10) the maximum number of PRBs or RBs for the bandwidth, [0150] 11) the target BLER for the data transmission, [0151] 12) the supported end-to-end latency, [0152] 13) the total number of supported frequency range (FR) type, [0153] 14) the coverage enhancement capability, [0154] 15) power class, [0155] 16) the UE processing time capability, [0156] 17) the type of use case, [0157] 18) the maximum number of SCells for a carrier aggregation (CA) configuration, [0158] 19) duplex mode, etc.
[0159] In some embodiments, N is an integer which is not smaller than 1, i.e. N≥1. In some embodiments, N is not larger than 16, i.e. N≤16. In some embodiments, N is not smaller than 1 and not larger than 16, i.e. 1≤N≤16.
[0160] In some embodiments, the transmission mode is a UE capability. In some embodiments, the transmission mode is a UE category. In some embodiments, the transmission mode is a higher layer parameter reported by the UE. In some embodiments, the transmission mode is a higher layer parameter transmitted by the network. In some embodiments, the transmission mode is a parameter for the UE supporting release 17. In some embodiments, the transmission mode is a parameter for the UE supporting release 17 and the further release versions.
[0161] In some embodiments, at least one of the parameters included in the set of parameters corresponding to the different types of transmission mode have different values. In some embodiments, the TBS determination procedure may be different for different types of transmission modes.
[0162] In some embodiments, the value of at least one of the parameters related to a type of transmission mode is defined as P1 and the value of at least one of the parameters related to another type of transmission mode is defined as P2. In some embodiments, P1 is not larger than P2, i.e. P1≤P2. In some embodiments, the total number of types of parameters supported by a transmission mode is not larger than that supported by another type of transmission mode. In some embodiments, the ID of a transmission mode is smaller than that of another type of transmission mode.
[0163] Next, UL/DL peak data rate is described in accordance with various embodiments.
[0164] In some embodiments, for the parameter of DL peak data rate, P1 is not larger than 150 Mbps and P2 is not less than 150 Mbps. In some embodiments, for the parameter of UL peak data rate, P1 is not larger than 50 Mbps and P2 is not less than 50 Mbps.
[0165] For example, there are two types of transmission modes. The DL peak data rate of the first type transmission mode supported by the UE is not larger than 50 Mbps. The DL peak data rate of the second type transmission mode supported by the UE is not less than 150 Mbps. The UL peak data of the second type transmission mode supported by the UE is not larger than 10 Mbps. The UL peak data rate of the second type transmission mode supported by the UE is not less than 50 Mbps.
[0166] In some embodiments, the data rate for a given number of aggregated carriers in a band or band combination is determined as followings:
[0167] wherein J is the number of aggregated component carriers in a band or band combination; R.sub.max is the maximum rate supported by the UE; for the j-th Component Carrier (CC); v.sub.Layers.sup.(j) is the maximum number of supported layers for the UE for the uplink or downlink; Q.sub.m.sup.(j) is the maximum modulation order supported by the UE configured by higher layer parameter for uplink or downlink; f.sup.(j) is the scaling factor given by higher layer parameter and can take the values 1, 0.8, 0.75, and 0.4; μ is the numerology (as defined in TS 38.211); T.sub.s.sup.μ is the average OFDM symbol duration in a subframe for numerology μ, i.e.
(The normal cyclic prefix is assumed.); N.sub.PRB.sup.BW(j),μ is the maximum RB allocation in bandwidth BW.sup.(j) with numerology μ supported by the UE; where BW.sup.(j) is the UE supported maximum bandwidth in the given band or band combination; OH.sup.(j) is the overhead and may take the following values: 1) 0.14, for frequency range FR1 for DL, 2) 0.18, for frequency range FR2 for DL, 3) 0.08, for frequency range FR1 for UL, 4) 0.10, for frequency range FR2 for UL.
[0168] S.sup.(j) is a new scaling factor and is not larger than 1. In some embodiments, the new scaling factor is the value configured by a higher layer parameter from a first candidate set for the UE supporting the first type of transmission mode. In some embodiments, the new scaling factor is the value configured by a higher layer parameter from a second candidate set for the UE supporting the second type of transmission mode. In some embodiments, at least one of the values in the first candidate set for the new scaling factor is different from the value in the second candidate set. In some embodiments, the new scaling factor is related to at least one of the following parameters for the UE: 1) the number of PRBs allocated, 2) the bandwidth of the active UL/DL BWP, 3) the maximum number of layers, 4) the maximum rate, 5) the maximum modulation order, etc.
[0169] For example, R.sub.max is not larger than 948/1024 and Q.sub.m.sup.(j) is 256 QAM for the second type of transmission mode. For example, R.sub.max is not larger than 658/1024 and Q.sub.m.sup.(j) is not lower than 16 QAM for the second type of transmission mode.
[0170] Next, the bandwidth in accordance with various embodiments is described.
[0171] In some embodiments, for the parameter of the maximum bandwidth, P1 is not larger than 20 MHz and P2 is not less than 50 MHz. In some embodiments, for the parameter of the minimum bandwidth, P1 is not larger than 10 MHz and P2 is not less than 10 MHz.
[0172] In some embodiments, the maximum bandwidth is related to the supported frequency range. In some embodiments, for the parameter of the maximum bandwidth in FR1, P1 is not larger than 20 MHz and P2 is not less than 20 MHz. In some embodiments, for the parameter of the maximum bandwidth in FR2, P1 is not larger than 40 MHz and P2 is not less than 50 MHz. In some embodiments, for the parameter of the minimum bandwidth in FR1, P1 is not larger than 10 MHz and P2 is not less than 10 MHz. In some embodiments, for the parameter of the minimum bandwidth in FR2, P1 is not larger than 80 MHz and P2 is not less than 10 MHz.
[0173] In some embodiments, the maximum bandwidth is related to the subcarrier spacing (SCS). In some embodiments, the maximum bandwidth is scaled by a scaling factor if the SCS is less than 30 KHz. In some embodiments, the maximum bandwidth is scaled by a scaling factor if the SCS is not less than 30 KHz.
[0174] In some embodiments, the maximum bandwidth is related to the frequency range. In some embodiments, the maximum bandwidth is scaled by a scaling factor if the FR1 is configured for the UE in the serving cell. In some embodiments, the maximum bandwidth is scaled by a scaling factor if the FR2 is configured for the UE in the serving cell. The scaling factor may be configured by the higher layer parameter and is not larger than 1.
[0175] For example, there are two types of transmission modes. The bandwidth of the first type transmission mode supported by the UE is not larger than 20 MHz. The bandwidth of the second type transmission mode supported by the UE is not less than 20 MHz. The UL peak data of the second type transmission mode supported by the UE is not larger than 10 Mbps. The UL peak data rate of the second type transmission mode supported by the UE is not less than 50 Mbps.
[0176] Next, bandwidth scaling in accordance with various embodiments is described.
[0177] In some embodiments, the bandwidth of the BWP configured for the UE is scaled by a scaling factor S.sub.bwp. In some embodiments, the scaling factor S.sub.bwp is not larger than 1 and is configured by the higher layer parameter. In some embodiments, the scaling factor S.sub.bwp is different for the BWPs with different bandwidth. In some embodiments, there are at least four candidate values for the scaling factor S.sub.bwp.
[0178] In some embodiments, the scaling factor S.sub.bwp is related to at least one of the following parameters supported by the UE: 1) the type of transmission mode, 2) the BWP ID, 3) the frequency range, 4) the maximum modulation order, 5) the maximum code rate, 6) the maximum number of layers, 7) the bandwidth of the active UL/DL BWP, 8) the number of allocated PRB for the data transmission in PDSCH/PUSCH.
[0179] An embodiment relates to TBS determination procedure.
[0180] In some embodiments, the TBS is determined by min{the final TBS determined by the TBS determination procedure, the maximum TBS}, wherein min{ } is a function of obtaining the minimum input variable. In some embodiments, the maximum TBS is related to at least one of the following parameters: 1) the uplink or downlink data transmission; 2) the type of transmission mode; 3) the type of frequency range; 4) the type of RNTIs scrambling the CRC of DCI format 0_1 and/or DCI format 1_1 and/or DCI format 0_2 and/or DCI format 1_2 and/or a DCI format new to the DCI format of Release 16; 5) the number of PRBs used for TBS determination; 6) the capability for coverage; 7) the supported transmission numerologies μ; 8) the value of average OFDM symbol duration T.sub.s.sup.μ; 9) the type of the radio link, etc.
[0181] In some embodiments, the maximum TBS is determined based on the plurality of transmission parameters. In some embodiments, the plurality of transmission parameters includes at least one of the maximum code block size, the maximum code rate supported by the wireless terminal, the maximum code rate of MCS table, the maximum modulation order supported by the wireless terminal and the maximum modulation order of the MCS table.
[0182] In some embodiments, the maximum TBS is one of elements in a TBS table which is greater than or equal to the product of the maximum code block size and a ratio of the maximum code rate supported by the wireless terminal and the maximum code rate in a configurable modulation and coding scheme (MCS) table. In some embodiments, the ratio of the maximum code rate supported by the wireless terminal and the maximum code rate in the configurable MCS table is a value in a range [0.27, 0.7201]. In some embodiments, the maximum code block size is equal to 3840 for low-density parity-check (LDPC) base graph 2 and is 8448 for LDPC base graph 1. In some embodiments, the TBS table includes at least one of the TBS table shown as Table 1, the new TBS table shown as Table 4 and/or Table 5.
[0183] In some embodiments, the maximum TBS is one of elements in a TBS table which is greater than or equal to a product of the maximum code block size and a ratio of the maximum modulation order supported by the wireless terminal and the maximum modulation order in a configurable MCS table. In some embodiments, the ratio of the maximum modulation order supported by the wireless terminal and the maximum modulation order in the configurable MCS table is a value in a range [0.25, 1]. In some embodiments, the maximum code block size is equal to 3840 for LDPC base graph 2 and 8448 for LDPC base graph 1. In some embodiments, the TBS table includes at least one of the TBS table shown as Table 1, the new TBS table shown as Table 4 and/or Table 5.
[0184] In some embodiments, the maximum TBS for the first transmission mode is at least one of the elements in the first TBS set. In some embodiments, the maximum TBS for the second transmission mode is at least one of the elements in the second TBS set.
[0185] In some embodiments, the first TBS set may include at least one of the following elements {1000, 1736, 3752, 3824, 3840, 4008, 5160, 8424, 27376, 51240} for PDSCH. In some embodiments, the first TBS set may include at least one of the following elements {328, 408, 456, 504, 600, 712, 808, 936, 1000, 1736, 3752, 3824, 3840, 4008, 5160, 8424} for PUSCH.
[0186] In some embodiments, the second TBS set may include at least one of the following elements {8424, 15110, 15370, 15620, 15880, 16140, 27376, 50180, 51220} for PDSCH. In some embodiments, the first TBS set may include at least one of the following elements {3824, 5160, 8424, 25100, 27376} for PUSCH.
[0187] In some embodiments, the value of each element in the first TBS set is not larger than 5160 for UL/DL. In some embodiments, the value of each element in the second TBS set is not smaller than 8448.
[0188] In some embodiments, the value of each element in the first TBS set is not larger than 3840 for UL/DL. In some embodiments, the value of each element in the second TBS set is not smaller than 3840.
[0189] Next, the number of PRBs used to determine N.sub.info and/or TBS is described in accordance with various embodiments.
[0190] In some embodiments, the number of PRBs used to determine TBS is determined by a maximum value between the number of allocated PRBs and a maximum number of PRBs supported by the UE for the PUSCH/PDSCH. In some embodiments, the maximum number of PRBs supported by the UE is configured by the higher layer parameter. In some embodiments, the maximum number of PRBs supported by the UE corresponding to each BWP is not larger than the maximum number of PRBs of the corresponding bandwidth in TS 38.101.
[0191] In some embodiments, the maximum number of PRBs supported by the UE corresponding to each BWP is not larger than a threshold1. In some embodiments, the maximum number of PRBs supported by the UE corresponding to each BWP is not less than a threshold2. In some embodiments, threshold1 is not less than 270. In some embodiments, threshold2 is not less than 6.
[0192] In some embodiments, the number of PRBs used to determine TBS is determined by a scaling factor (S.sub.PRB) and the number of allocated PRB (n.sub.PRB) for PDSCH or PUSCH. In some embodiments, the number of PRBs used to determine TBS is determined as (S.sub.PRB*n.sub.PRB). In some embodiments, the scaling factor (S.sub.PRB) is related to the bandwidth of the active UL/DL BWP for the UE.
[0193] In some embodiments, the maximum number of PRBs for each bandwidth is predefined for a specific type of transmission mode. In some embodiments, the quantized number of PRBs for each bandwidth for the UE supported the specific transmission mode is not larger than the original maximum number of PRBs defined in the NR Release 16 specification. In some embodiments, the number of PRBs for different bandwidth are quantized as follows:
TABLE-US-00005 Bandwidth (MHz) 5 . . . 20 Maximum number of PRBs N1 . . . Nx (max_n.sub.PRB)
[0194] In some embodiments, the number of available PRBs for each bandwidth is configured by the higher layer parameter. In some embodiments, the number of available PRB for each bandwidth is related to the type of the transmission mode and/or the bandwidth of the BWP. In some embodiments, the number of PRBs used to determine TBS should be not lager than the available PRB for the corresponding bandwidth.
[0195] In some embodiments, the number of PRBs used to determine TBS is determined by a scaling factor and the number of allocated PRBs for PDSCH or PUSCH. In some embodiments, the scaling factor is related to the type of transmission mode.
[0196] In some embodiments, the number of PRBs used for TBS determination may not be larger than the maximum number of PRBs. In some embodiments, the number of PRBs used for TBS determination may be determined as the min{the number of allocated PRBs, the number of PRBs} for the UE. In some embodiments, the maximum number of PRBs is related to the type of transmission mode supported by the UE. In some embodiments, the maximum number of PRBs for different transmission mode are quantized as follows:
TABLE-US-00006 The type of Maximum number of PRBs transmission mode (max_n.sub.PRB) Mode 1 N1 . . . . . . Mode x Nx
[0197] In some embodiments, the scaling factor (S.sub.PRB) for a specific transmission mode is not larger than 1. In some embodiments, the scaling factor (S.sub.PRB) for the other transmission mode is equal to 1 or is not available. The supported maximum bandwidth, and/or the supported maximum modulation order, and/or the supported maximum number of layers for the specific transmission mode may be smaller than that for the other transmission modes.
[0198] In some embodiments, the UE does not expect the number of PRBs allocated for the PDSCH/PUSCH larger than the maximum number of PRBs for the active UL/DL BWP.
[0199] In some embodiments, the above method for determining the number of PRBs by using a scaling factor (S.sub.PRB) can be determined as function(S.sub.PRB*n.sub.PRB). In some embodiments, the function( ) represents rounding, and/or rounding down, and/or rounding up, and/or retaining the original value. In some embodiments, the above method for determining the number of PRBs used for TBS determination can be also used to determine the value of N.sub.info.
[0200] Next, MCS determination is described in accordance with various embodiments.
[0201] In some embodiments, the supported MCS index is related to at least one of the following parameters: 1) the number of allocated PRBs for PUSCH/PDSCH, 2) the number of layers, 3) the bandwidth for the active BWP, 4) the type of transmission mode supported by the UE.
[0202] In some embodiments, if the UE supports the specific type of transmission mode, the maximum MCS index available for the UE is smaller than a threshold1 when the MCS table 1 for PDSCH and/or the MCS table 2 for PDSCH and/or the MCS table 3 for PDSCH and/or the MCS table for PUSCH with transform precoding and/or the MCS table 2 for PUSCH with transform precoding is configured for the UE. In some embodiments, the threshold is not larger than 28. In some embodiments, the specific type of transmission mode is configured by the higher layer parameter.
[0203] In some embodiments, the MCS index available for the UE is related to the supported type of transmission mode. In some embodiments, the number of available MCS index for the specific type of transmission mode is less than the other type of transmission mode.
[0204] In some embodiments, the UE supporting the specific type of transmission mode may be configured by the MCS table with the maximum modulation order (Q.sub.m) not larger than 64 QAM (Q.sub.m=6) for PUSCH and/or PDSCH. In some embodiments, the UE supporting the specific type of transmission mode may not be configured by the MCS table with the maximum modulation order (Q.sub.m) larger than 256 QAM (Q.sub.m=8) for PUSCH and/or PDSCH.
[0205] In some embodiments, the UE supporting the specific type of transmission mode is not expected using the MCS table for PUSCH with transform precoding for UL transmission.
[0206] In some embodiments, the supported modulation order (Q.sub.m) is related to at least one of the following parameters: 1) the number of allocated PRBs for PUSCH/PDSCH, 2) the number of layers, 3) the bandwidth for the active BWP, 4) the type of transmission mode supported by the UE.
[0207] In some embodiments, the supported rate (R) is related to at least one of the following parameters: 1) the number of allocated PRBs for PUSCH/PDSCH, 2) the number of layers, 3) the bandwidth for the active BWP, 4) the type of transmission mode supported by the UE.
[0208] In some embodiments, the modulation order for the UE supporting the specific type of transmission mode is determined as the minimum value between the modulation order corresponding to the MCS index (I.sub.MCS) and the maximum modulation order Q.sub.m.sup.max. Wherein the maximum modulation order supported by the UE can be configured by the higher layer parameter. In some embodiments, the maximum modulation order supported by the UE is related to the type of transmission mode supported by the UE.
[0209] In some embodiments, the type of transmission mode is identified by the RNTI scrambling the CRC of the DCI transmitted on PDCCH. In some embodiments, the available MCS table configured for the UE can be determined based on at least one of the following parameters: 1) the type of RNTI scrambling the CRC of the DCI, 2) the type of transmission mode, 3) the type of link of data transmission (i.e. PDSCH data scheduling or PUSCH data scheduling), etc.
[0210] Next, the maximum code block size determination is described in accordance with various embodiments.
[0211] In some embodiments, the maximum code block size determination is determined by at least one of the following parameters: 1) the number of allocated PRBs for PUSCH/PDSCH, 2) the number of layers, 3) the bandwidth for the active BWP, 4) the type of transmission mode , 5) the selected LDPC base graph, 6) the code rate, 7) the value of TBS supported by the UE.
[0212] In some embodiments, the maximum code block size is not larger than 3840 if the UE only supports the LDPC base graph 2 configured by the higher layer parameter. In some embodiments, if the UE only supports the LDPC base graph 2 configured by the higher layer parameter, the UE uses steps 1) and 3) to determine TBS for PDSCH and PUSCH.
[0213] In some embodiments, if the UE only supports the LDPC base graph 2 configured by the higher layer parameter and if the value of N.sub.info is larger than 3824, the UE uses step 4) to modify the N.sub.info.
[0214] In some embodiments, the maximum code block size for the UE can be larger than 3840 if the higher layer parameter configures the UE supporting the LDPC base graph 1. In some embodiments, if the UE is configured to support LDPC base graph 1, the UE may use steps 1)-4) of TBS determination procedure in Release 16 for PDSCH and PUSCH.
[0215] In some embodiments, if the UE only supports the LDPC base graph 2 configured by the higher layer parameter and if the value of N.sub.info is larger than 3824, the modified N.sub.info (N′.sub.info) may be determined as the following step to determine TBS. [0216] quantized intermediate number of information bits
[0218] In some embodiments, the UE only supports the LDPC base graph 2 if the higher layer parameter configures the UE supporting the specific type of transmission mode. In some embodiments, the specific type of transmission mode may be configured by the higher layer parameter.
[0219] In some embodiments, the UE may support a TBS not larger than a maximum TBS. In some embodiments, the maximum TBS is configured by the higher layer parameter. In some embodiments, the maximum TBS is not larger than a threshold. In some embodiments, the threshold is not smaller than 3824. In some embodiments, the UE may determine the TBS using step 1)-3) of the TBS determination procedure.
[0220] In some embodiments, the UE determines the final TBS as the minimum between the maximum TBS and the calculated TBS by the TBS determination procedure. In some embodiments, the TBS determination procedure can be the TBS determination procedure in above embodiments or the TBS determination procedure in NR Rel-16 specification.
[0221] In some embodiments, the UE does not expect the determined TBS by the current TBS procedure to be larger than the maximum TBS supported by the UE.
[0222] In some embodiments, the UE determines the TBS using steps 1)-3) of the TBS determination procedure. In some embodiments, the UE finds the TBS in the new TBS table closest to the modified TBS (N′.sub.info) as the final TBS. In some embodiments, the new TBS table is a TBS table including the current TBS elements in the TBS table. In some embodiments, the new TBS table is an extension to the current TBS table. The current TBS table may be TBS table in table 2. In some embodiments, the new TBS table is an additional or independent TBS table new to the current TBS table. The current TBS table may be the TBS table in table 2.
[0223] In some embodiments, the elements (E) in the new TBS table can be satisfied with at least one of the following conditions:
and/or [0224] 7) The maximum value of E is not larger than a threshold, wherein the threshold is 84064.
[0225] In some embodiments, if the N.sub.info is larger than 3824, the UE may calculate the modified TBS by step 4). In some embodiments, if the N.sub.info is larger than 3824, the UE may determine the TBS by finding the TBS in the new TBS table closest to the modified TBS (N′.sub.info) as the final TBS. In some embodiments, the final TBS (noted as TBS1) closest to the modified TBS (N′.sub.info) is the TBS in TBS table that is not larger than and closest to the modified TBS (N′.sub.info). In some embodiments, the final TBS (noted as TBS2) closest to the modified TBS (N′.sub.info) is the TBS in TBS table that is not less than and closest to the modified TBS.
[0226] In some embodiments, the final TBS closest to the modified TBS (N′.sub.info) is the TBS in the TBS table, which has the smallest gap with the modified TBS (N′.sub.info). Denote the gap between the TBS1 and modified TBS (N′.sub.info) as gap1. Denote the gap between the TBS2 and modified TBS (N′.sub.info) as gap2. In some embodiments, if the gap1 is equal to gap2, the TBS with smaller index is determined as the final TBS.
[0227] In some embodiments, the final TBS closest to the modified TBS (N′.sub.info) is the TBS in the TBS table, which has the smallest gap with the modified TBS (N′.sub.info). Denote the gap between the TBS1 and modified TBS (N′.sub.info) as gap1. Denote the gap between the TBS2 and modified TBS (N′.sub.info) as gap2. In some embodiments, if the gap1 is equal to gap2, the TBS with larger index is determined as the final TBS.
[0228] In some embodiments, the new TBS table is shown in table 4.
TABLE-US-00007 TABLE 4 new TBS table index TBS 1 3848 2 3912 3 3976 4 4040 5 4104 6 4232 7 4360 8 4488 9 4616 10 4744 11 4872 12 5000 13 5128 14 5256 15 5384 16 5512 17 5640 18 5768 19 5896 20 6024 21 6152 22 6280 23 6408 24 6536 25 6664 26 6792 27 6920 28 7048 29 7176 30 7304 31 7432 32 7560 33 7680 34 7824 35 7944 36 8064 37 8208 38 8448 39 8712 40 8976 41 9216 42 9480 43 9744 44 9984 45 10248 46 10512 47 10752 48 11016 49 11280 50 11528 51 11784 52 12040 53 12296 54 12552 55 12808 56 13064 57 13320 58 13576 59 13832 60 14088 61 14344 62 14600 63 14856 64 15112 65 15376 66 15616 67 15896 68 16136 69 16416 70 16896 71 17416 72 17936 73 18456 74 18976 75 19464 76 19992 77 20520 78 21000 79 21528 80 22056 81 22536 82 23048 83 23552 84 24112 85 24616 86 25120 87 25624 88 26128 89 26632 90 27176 91 27688 92 28200 93 28712 94 29224 95 29736 96 30248 97 30720 98 31296 99 31800 100 32304 101 32808 102 33816 103 34856 104 35896 105 36936 106 37896 107 38960 108 40016 109 40984 110 42024 111 43080 112 44040 113 45096 114 46152 115 47192 116 48128 117 49168 118 50264 119 51272 120 52280 121 53288 122 54336 123 55296 124 56376 125 57448 126 58472 127 59496 128 60520 129 61448 130 62536 131 63488 132 64576 133 65640 134 67656 135 69744 136 71720 137 73736 138 75816 139 77928 140 79944 141 81992 142 84064 143 144 145 146 147 148 149 150
[0229] In some embodiments, the new TBS table used to determine the final TBS includes at least one of the elements in the table 5.
TABLE-US-00008 TABLE 5 new TBS table index TBS 1 24 2 32 3 40 4 48 5 56 6 64 7 72 8 80 9 88 10 96 11 104 12 112 13 120 14 128 15 136 16 144 17 152 18 160 19 168 20 176 21 184 22 192 23 208 24 224 25 240 26 256 27 272 28 288 29 304 30 320 31 336 32 352 33 368 34 384 35 408 36 432 37 456 38 480 39 504 40 528 41 552 42 576 43 608 44 640 45 672 46 704 47 736 48 768 49 808 50 848 51 888 52 928 53 984 54 1032 55 1064 56 1128 57 1160 58 1192 59 1224 60 1256 61 1288 62 1320 63 1352 64 1416 65 1480 66 1544 67 1608 68 1672 69 1736 70 1800 71 1864 72 1928 73 2024 74 2088 75 2152 76 2216 77 2280 78 2408 79 2472 80 2536 81 2600 82 2664 83 2728 84 2792 85 2856 86 2976 87 3104 88 3240 89 3368 90 3496 91 3624 92 3752 93 3824 94 3840 95 3848 96 3904 97 3912 98 3968 99 3976 100 4032 101 4040 102 4096 103 4104 104 4224 105 4232 106 4352 107 4360 108 4480 109 4488 110 4608 111 4616 112 4736 113 4744 114 4864 115 4872 116 4992 117 5000 118 5120 119 5128 120 5248 121 5256 122 5376 123 5384 124 5504 125 5512 126 5632 127 5640 128 5760 129 5768 130 5888 131 5896 132 6016 133 6024 134 6144 135 6152 136 6272 137 6280 138 6400 139 6408 140 6528 141 6536 142 6656 143 6664 144 6784 145 6792 146 6912 147 6920 148 7040 149 7048 150 7168 151 7176 152 7296 153 7304 154 7424 155 7432 156 7552 157 7560 158 7680 159 7808 160 7824 161 7936 162 7944 163 8064 164 8192 165 8208 166 8448 167 8456 168 8712 169 8968 170 8976 171 9216 172 9224 173 9480 174 9736 175 9744 176 9984 177 9992 178 10248 179 10504 180 10512 181 10752 182 10760 183 11016 184 11272 185 11280 186 11528 187 11784 188 12040 189 12296 190 12552 191 12808 192 13064 193 13320 194 13576 195 13832 196 14088 197 14344 198 14600 199 14856 200 15112 201 15368 202 15376 203 15616 204 15624 205 15880 206 15896 207 16136 208 16392 209 16416 210 16896 211 17416 212 17424 213 17928 214 17936 215 18432 216 18456 217 18960 218 18976 219 19464 220 19968 221 19992 222 20496 223 20520 224 21000 225 21504 226 21528 227 22032 228 22056 229 22536 230 23040 231 23048 232 23552 233 23568 234 24072 235 24112 236 24576 237 24616 238 25104 239 25120 240 25608 241 25624 242 26120 243 26128 244 26632 245 27144 246 27176 247 27656 248 27688 249 28168 250 28200 251 28680 252 28712 253 29192 254 29224 255 29704 256 29736 257 30216 258 30248 259 30720 260 30728 261 31240 262 31296 263 31752 264 31800 265 32264 266 32304 267 32776 268 32808 269 33816 270 34816 271 34856 272 35856 273 35896 274 36896 275 36936 276 37896 277 38936 278 38960 279 39936 280 40016 281 40976 282 40984 283 42016 284 42024 285 43032 286 43080 287 44040 288 45096 289 46104 290 46152 291 47112 292 47192 293 48128 294 48168 295 49168 296 49176 297 50184 298 50264 299 51216 300 51272 301 52224 302 52280 303 53288 304 54296 305 54336 306 55296 307 55304 308 56368 309 56376 310 57376 311 57448 312 58384 313 58472 314 59432 315 59496 316 60456 317 60520 318 61448 319 61480 320 62504 321 62536 322 63488 323 63528 324 64552 325 64576 326 65576 327 65640 328 67584 329 67656 330 69672 331 69744 332 71688 333 71720 334 73736 335 73776 336 75792 337 75816 338 77896 339 77928 340 79896 341 79944 342 81976 343 81992 344 83976 345 84064 346 86040 347 88064 348 90176 349 92200 350 94248 351 96264 352 98376 353 100392 354 102416 355 104496 356 106576 357 108552 358 110632 359 112648 360 114776 361 116792 362 118896 363 120936 364 122976 365 125016 366 127080 367 129128 368 131176 369 135296 370 139376 371 143400 372 147576 373 151608 374 155776 375 159880 376 163976 377 167976 378 172176 379 176208 380 180376 381 184424 382 188576 383 192624 384 196776 385 200808 386 204976 387 208976 388 213176 389 217128 390 221376 391 225480 392 229576 393 233608 394 237776 395 241720 396 245976 397 250056 398 254176 399 258144 400 262376 401 270576 402 278776 403 286976 404 295176 405 303240 406 311368 407 319784 408 327888 409 335976 410 344376 411 352440 412 360488 413 368872 414 376896 415 385272 416 393272 417 401640 418 409616 419 417976 420 426336 421 434280 422 442632 423 450984 424 458896 425 467240 426 475584 427 483464 428 491800 429 500136 430 507984 431 516312 432 524640 433 540776 434 557416 435 573504 436 590128 437 606504 438 622760 439 638984 440 655800 441 671976 442 688776 443 704904 444 721000 445 737768 446 753816 447 770568 448 786568 449 803304 450 819256 451 835976 452 852696 453 868584 454 885288 455 901344 456 918192 457 934152 458 950984 459 966896 460 983712 461 999576 462 1016376 463 1032192 464 1048976 465 1081512 466 1115048 467 1147488 468 1179864 469 1213032 470 1245544 471 1277992
[0230] In some embodiments, the final TBS is determined by the minimum value between the maximum TBS supported by the UE and the temporary TBS determined by the TBS determining steps 1)-4) in TS 38.214.
[0231] In some embodiments, the UE does not expect the final TBS to be larger than the maximum TBS supported by the UE associated with a specific resource configuration. In some embodiments, if the final TBS based on the information indicated by a DCI is larger than the maximum TBS supported by the UE associated with a specific resource configuration, the UE may ignore the scheduling UL/DL data. In some embodiments, the specific resource configuration includes at least one of the followings: the bandwidth, the maximum peak data rate, the frequency range type, the number of activated secondary cells (SCells), and/or the subcarrier spacing.
[0232] In some embodiments, the maximum TBS for the different transmission modes supported by the UE may be different. In some embodiments, there is no maximum TBS limitation for the transmission mode with a higher ID. In some embodiments, the maximum TBS for the transmission mode with a higher ID is larger than that for the transmission mode with a lower ID.
[0233] In some embodiments, there are two types of transmission modes including first transmission mode and second transmission mode. In some embodiments, the range of the maximum TBS for the first transmission modes may be determined based on at least one of the following parameters supported by the UE: [0234] 1) the maximum bandwidth; [0235] 2) the number of PRBs available for the UE in the bandwidth; [0236] 3) the maximum number of layers; [0237] 4) the DL and/or UL peak data rate; [0238] 5) the maximum modulation order; [0239] 6) the maximum rate; [0240] 7) the current active BWP; [0241] 8) the scheduled active BWP, etc.
[0242] In some embodiments, the above parameters are the value configured in the active DL and/or UL BWP.
[0243] In some embodiments, the TBS determination is related to the base graph for low density parity check (LDPC) coding.
[0244] In some embodiments, the N.sub.info is modified by the scaling factor. In some embodiments, the scaling factor is not larger than 1. In some embodiments, the scaling factor is configured by the higher layer parameter. In some embodiments, the scaling factor is determined based on the number of PRBs available for PUSCH and/or PDSCH and the maximum number of PRBs available for PUSCH and/or PDSCH for active and/or scheduled BWP.
[0245] In some embodiments, the UE can select a specific TBS determination Step to determine the final TBS based on the N.sub.info, and/or at least one of the parameters related to the TBS determination described in above embodiments. In some embodiments, the specific TBS determination Step can be at least one step in the TBS determination procedure in the above embodiments.
[0246] Next, an embodiment related to soft/limited buffer size is described.
[0247] In some embodiments, the determination procedure for the limited buffer for rate matching for LDPC coding for UL-SCH and DL-SCH/PCH is based on the following parameters: [0248] 1) the maximum number of layers for one TB for UL-SCH and/or DL-SCH/PCH; [0249] 2) the MCS table available for the UE configured by the higher layer parameters; [0250] 3) the maximum modulation order corresponding to the available MCS table; [0251] 4) the maximum coding rate; [0252] 5) the number of PRBs; [0253] 6) the number of code blocks; [0254] 7) the type of transmission mode; [0255] 8) the maximum number of resource elements per PRB; [0256] 9) the type of RNTI scrambling the CRC of the DCI, etc.
[0257] In some embodiments, the number of PRBs used for determining the TBS.sub.LBRM may be configured by the higher layer parameter for each bandwidth. In some embodiments, the number of PRBs used for determining the TBS.sub.LBRM may be determined as the number of PRBs n.sub.PRB,LBRM defined in the NR Release 16 for each bandwidth if the higher layer parameter configures the UE to support the type of transmission mode other than the specific transmission mode. In some embodiments, the number of PRBs used for determining the TBS.sub.LBRM may be determined as the scaled number of PRBs n.sub.PRB,LBRM defined in the NR Release 16 for each bandwidth by a scaling factor if the higher layer parameter configures the UE to support the specific transmission mode. In some embodiments, the number of PRBs used for determining the TBS.sub.LBRM may be determined as the scaled number of PRBs n.sub.PRB,LBRM defined in the NR Release 16 for each bandwidth by a scaling factor if the higher layer parameter configures the UE with the scaling factor for the number of PRBs used for determining the TBS.sub.LBRM.
[0258] In some embodiments, the number of PRBs is determined as the quantized value of n′.sub.PRB predefined in a specific table. In some embodiments, the number of PRBs is quantized by a specific table. In some embodiments, the quantized value of n′.sub.PRB in each range is not larger than the corresponding quantized value of n′.sub.PRB in the same range as shown in the following table 6.
TABLE-US-00009 TABLE 6 Value of n’.sub.PRB Maximum number of PRBs across all configured DL BWPs and UL BWPs respectively n’.sub.PRB Less than 33 32 33 to 66 66 67 to 107 107 108 to 135 135 136 to 162 162 163 to 217 217 Larger than 217 273
[0259] In some embodiments, the TBS determination procedure defined in the above methods may be reused to determine the TBS.sub.LBRM.
[0260] In some embodiments, the UE determines the final TBS based on the above assumed parameters and modifies the final TBS by a scaling factor of rate matching (S.sub.RM) and a predefined function to generate the modified final TBS. In some embodiments, the UE determines the modified final TBS as the TBS.sub.LBRM. In some embodiments, the predefined function represents rounding, and/or rounding down, and/or rounding up, and/or retaining the original value.
[0261] In some embodiments, the UE determines the maximum TBS as the TBS.sub.LBRM. In some embodiments, the maximum TBS is reported by the UE. In some embodiments, the maximum TBS is related to at least one of the following parameters: [0262] 1) the maximum bandwidth; [0263] 2) the number of PRBs available for the UE in the bandwidth; [0264] 3) the maximum number of layers; [0265] 4) the DL and/or UL peak data rate; [0266] 5) the maximum modulation order; [0267] 6) the maximum rate; [0268] 7) the current active BWP; [0269] 8) the scheduled active BWP, etc.
[0270] In some embodiments, the maximum modulation order is determined as the value configured by the higher layer parameter. In some embodiments, the higher layer parameter is related to the type of transmission mode.
[0271] In some embodiments, the maximum code rate may be the value that is not larger than 948/1024. In some embodiments, the maximum code rate is determined as the value configured by the higher layer parameter. In some embodiments, the higher layer parameter is related to the type of transmission mode.
[0272] In summary, as apparent from the foregoing description, embodiments comprise one or more of the following aspects: [0273] 1) The TBS determination is related to at least one of the following parameters: [0274] a. the uplink or downlink data transmission; [0275] b. the type of transmission mode; [0276] c. the type of frequency range; [0277] d. the type of RNTIs scrambling the CRC of DCI format 0_1 and/or DCI format 1_1 and/or DCI format 0_2 and/or DCI format 1_2 and/or a DCI format new to the DCI format of Release 16; [0278] e. the number of PRBs used for TBS determination; [0279] f. the capability for coverage; [0280] g. the supported transmission numerologies μ; [0281] h. the value of average OFDM symbol duration T.sub.s.sup.μ. [0282] 2) The TBS may be determined by min(TBS determined by TBS procedure in Release 16, the maximum TBS). [0283] a. The maximum TBS may be related to at least one of the followings: [0284] i. the uplink or downlink data transmission; [0285] ii. the type of transmission mode; [0286] iii. the type of frequency range; [0287] iv. the type of RNTIs scrambling the CRC of DCI format 0_1 and/or DCI format 1_1 and/or DCI format 0_2 and/or DCI format 1_2 and/or a DCI format new to the DCI format of Release 16; [0288] v. the number of PRBs used for TBS determination; [0289] vi. the capability for coverage; [0290] vii. the supported transmission numerologies μ; [0291] viii. the value of average OFDM symbol duration T.sub.s.sup.μ. [0292] b. The maximum TBS for the first transmission mode is at least one of the elements in the first TBS set. The maximum TBS for the second transmission mode is at least one of the elements in the second TBS set. [0293] i. The first TBS set may include at least one of the following elements {1000, 1736, 3752, 3824, 3840, 4008, 5160, 8424, 27376, 51240} for PDSCH. The first TBS set may include at least one of the following elements {328, 408, 456, 504, 600, 712, 808, 936, 1000, 1736, 3752, 3824, 3840, 4008, 5160, 8424} for PUSCH. [0294] ii. The second TBS set may include at least one of the following elements {8424, 15110, 15370, 15620, 15880, 16140, 27376, 50180, 51220} for PDSCH. The first TBS set may include at least one of the following elements {3824, 5160, 8424, 25100, 27376} for PUSCH. [0295] iii. The value of each element in the first TBS set is not larger than 5160 for UL/DL. The value of each element in the second TBS set is not smaller than 8448. [0296] iv. The value of each element in the first TBS set is not larger than 3840 for UL/DL. The value of each element in the second TBS set is not smaller than 3840. [0297] 3) The TBS is determined by some of the specific steps of the TBS determination procedure. [0298] a. if the UE only supports the LDPC base graph 2 configured by the higher layer parameter, the UE uses steps 1)-3) to determine TBS for PDSCH and PUSCH. [0299] b. if the UE is configured to support LDPC base graph 1, the UE may use steps 1)-4) of TBS determination procedure in Release 16 for PDSCH and PUSCH. When N.sub.info>3824, the UE may use a new TBS table to determine the final TBS according to the modified TBS (N′.sub.info). The N′.sub.info is determined based on N.sub.info according to step 4). The TBS in the TBS table should be satisfied with the following conditions:
and/or [0300] 6) The maximum value of E is not larger than a threshold, wherein the threshold is 84064. [0301] c. if the UE only supports the LDPC base graph 2 configured by the higher layer parameter, the final TBS may be determined by
by using the modified N.sub.info (N′.sub.info) in step 4), where
[0347]
[0348] Step 300: Determine an intermediate TBS for a transport block transmitted between the wireless terminal and a wireless network node based on a plurality of transmission parameters.
[0349] Step 301: Modify the intermediate TBS to generate a modified TBS in response to at least one event.
[0350] Step 302: Determine a final TBS based on the modified TBS and a specific step in response to the at least one event.
[0351] More specifically, the wireless terminal determines an intermediate TBS for a transport block transmitted between the wireless terminal and a wireless network node based on a plurality of transmission parameters. Next, the wireless terminal modifies the intermediate TBS in response to at least one event, to generate a modified TBS. Based on the modified TBS and a specific step in response to the at least one event, the wireless terminal determines a final TBS for the transport block transmitted between the wireless terminal.
[0352] In an embodiment, the plurality of transmission parameters comprises at least one of (1) a DCI format, (2) a type of a transmission mode configured for the wireless terminal, (3) a type of a frequency range, (4) a type of an RNTI scrambling a CRC of DCI, (5) the number of PRBs used to determine intermediate TBS, (6) the MCS index used to determine the code rate and modulation order, (7) a coverage capability of the wireless terminal, (8) the value of sub-carrier spacing, or (9) a value of an average OFDM symbol duration.
[0353] In an embodiment, the wireless terminal may receive, from the wireless network node, a signal indicating the plurality of transmission parameters.
[0354] The features and/or details of the plurality of transmission parameters and/or the at least one event and/or the specific step can refer to aforementioned embodiments and are not described herein for brevity.
[0355]
[0356] Step 400: Transmit, to a wireless terminal, a signal indicating a plurality of transmission parameters.
[0357] Step 401: Determine an intermediate TBS for a transport block transmitted between the wireless terminal and the wireless network node based on the plurality of transmission parameters.
[0358] Step 402: Modify the intermediate TBS to generate a modified TBS in response to at least one event.
[0359] Step 403: Determine a final TBS based on the modified TBS and a specific step in response to the at least one event.
[0360] Specifically, the wireless network node transmits a signal to a wireless terminal (e.g. UE) to indicate a plurality of transmission parameters. In this embodiment, the wireless network node determines an intermediate TBS for a transport block transmitted between the wireless terminal and a wireless network node based on a plurality of transmission parameters. Next, the wireless network node modifies the intermediate TBS in response to at least one event, to generate a modified TBS. Based on the modified TBS and a specific step in response to the at least one event, the wireless network node determines a final TBS for the transport block transmitted between the wireless terminal.
[0361] As an alternative or in addition, the wireless network node may receive, from the wireless terminal, the TBS determined by the wireless terminal.
[0362] In an embodiment, the plurality of transmission parameters comprises at least one of (1) a DCI format, (2) a type of a transmission mode configured for the wireless terminal, (3) a type of a frequency range, (4) a type of an RNTI scrambling a CRC of DCI, (5) the number of PRBs used to determine intermediate TBS, (6) the MCS index used to determine the code rate and modulation order, (7) a coverage capability of the wireless terminal, (8) the value of sub-carrier spacing, or (9) a value of an average OFDM symbol duration.
[0363] The features and/or details of the plurality of transmission parameters and/or the at least one event and/or the specific step can refer to aforementioned embodiments and are not described herein for brevity.
[0364] While various embodiments of the present disclosure have been described above, it should be understood that they have been presented by way of example only, and not by way of limitation. Likewise, the various diagrams may depict an example architectural or configuration, which are provided to enable persons of ordinary skill in the art to understand exemplary features and functions of the present disclosure. Such persons would understand, however, that the present disclosure is not restricted to the illustrated example architectures or configurations, but can be implemented using a variety of alternative architectures and configurations. Additionally, as would be understood by persons of ordinary skill in the art, one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments.
[0365] It is also understood that any reference to an element herein using a designation such as “first,” “second,” and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.
[0366] Additionally, a person having ordinary skill in the art would understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits and symbols, for example, which may be referenced in the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0367] A skilled person would further appreciate that any of the various illustrative logical blocks, units, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two), firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as “software” or a “software unit”), or any combination of these techniques.
[0368] To clearly illustrate this interchangeability of hardware, firmware and software, various illustrative components, blocks, units, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware or software, or a combination of these techniques, depends upon the particular application and design constraints imposed on the overall system. Skilled artisans can implement the described functionality in various ways for each particular application, but such implementation decisions do not cause a departure from the scope of the present disclosure. In accordance with various embodiments, a processor, device, component, circuit, structure, machine, unit, etc. can be configured to perform one or more of the functions described herein. The term “configured to” or “configured for” as used herein with respect to a specified operation or function refers to a processor, device, component, circuit, structure, machine, unit, etc. that is physically constructed, programmed and/or arranged to perform the specified operation or function.
[0369] Furthermore, a skilled person would understand that various illustrative logical blocks, units, devices, components and circuits described herein can be implemented within or performed by an integrated circuit (IC) that can include a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, or any combination thereof. The logical blocks, units, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device. A general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein. If implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium.
[0370] Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another. A storage media can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.
[0371] In this document, the term “unit” as used herein, refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various units are described as discrete units; however, as would be apparent to one of ordinary skill in the art, two or more units may be combined to form a single unit that performs the associated functions according embodiments of the present disclosure.
[0372] Additionally, memory or other storage, as well as communication components, may be employed in embodiments of the present disclosure. It will be appreciated that, for clarity purposes, the above description has described embodiments of the present disclosure with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present disclosure. For example, functionality illustrated to be performed by separate processing logic elements, or controllers, may be performed by the same processing logic element, or controller. Hence, references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.
[0373] Various modifications to the implementations described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other implementations without departing from the scope of this disclosure. Thus, the disclosure is not intended to be limited to the implementations shown herein, but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as recited in the claims below.