WO2018031083A1 - Transmissions de liaison descendante avec des temps de traitement variables - Google Patents

Transmissions de liaison descendante avec des temps de traitement variables Download PDF

Info

Publication number
WO2018031083A1
WO2018031083A1 PCT/US2017/028928 US2017028928W WO2018031083A1 WO 2018031083 A1 WO2018031083 A1 WO 2018031083A1 US 2017028928 W US2017028928 W US 2017028928W WO 2018031083 A1 WO2018031083 A1 WO 2018031083A1
Authority
WO
WIPO (PCT)
Prior art keywords
processing time
subframe
tbs
scaling factor
reduced
Prior art date
Application number
PCT/US2017/028928
Other languages
English (en)
Inventor
Hong He
Gang Xiong
Hwan-Joon Kwon
Seunghee Han
Alexei Davydov
Original Assignee
Intel IP Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel IP Corporation filed Critical Intel IP Corporation
Publication of WO2018031083A1 publication Critical patent/WO2018031083A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK

Definitions

  • Wireless mobile communication technology uses various standards and protocols to transmit data between a node (e.g., a transmission station) and a wireless device (e.g., a mobile device).
  • Some wireless devices communicate using orthogonal frequency-division multiple access (OFDMA) in a downlink (DL) transmission and single carrier frequency division multiple access (SC-FDMA) in uplink (UL).
  • OFDMA orthogonal frequency-division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • OFDM orthogonal frequency-division multiplexing
  • 3 GPP third generation partnership project
  • LTE long term evolution
  • IEEE Institute of Electrical and Electronics Engineers 802.16 standard
  • WiMAX Worldwide Interoperability for Microwave Access
  • WiFi Wireless Fidelity
  • the node can be a combination of Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node Bs (also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs) and Radio Network Controllers (RNCs), which communicates with the wireless device, known as a user equipment (UE).
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • Node Bs also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs
  • RNCs Radio Network Controllers
  • the downlink (DL) transmission can be a communication from the node (e.g., eNodeB) to the wireless device (e.g., UE), and the uplink (UL) transmission can be a communication from the wireless device to the node.
  • UE user equipment
  • FIG. 1 illustrates a physical uplink control channel (PUCCH) resource collision for PUCCH format la/lb in accordance with an example
  • FIG. 2 is a table that includes user equipment (UE)-category -based maximum transport block size (TBS) restrictions for processing time reduction in accordance with an example;
  • UE user equipment
  • TBS maximum transport block size
  • FIG. 3 illustrates a physical uplink control channel (PUCCH) resource mapping for a user equipment (UE) configured with a reduced processing time in accordance with an example
  • PUCCH physical uplink control channel
  • FIG. 4 is a table that includes physical uplink control channel (PUCCH) resource offset (URO) fields in downlink (DL) assignment downlink control information (DCI) formats in accordance with an example;
  • PUCCH physical uplink control channel
  • URO resource offset
  • DCI downlink control information
  • FIG. 5 depicts functionality of a user equipment (UE) operable to perform uplink transmissions using a reduced transport block size (TBS) in accordance with an example
  • UE user equipment
  • TBS transport block size
  • FIG. 6 depicts functionality of a user equipment (UE) operable to perform uplink transmissions using a reduced transport block size (TBS) in accordance with an example
  • FIG. 7 depicts a flowchart of a machine readable storage medium having instructions embodied thereon for performing uplink transmissions at a user equipment (UE) using a reduced transport block size (TBS) in accordance with an example;
  • UE user equipment
  • TBS transport block size
  • FIG. 8 depicts a flowchart of a machine readable storage medium having instructions embodied thereon for performing uplink transmissions at a user equipment (UE) using a reduced transport block size (TBS) in accordance with an example;
  • UE user equipment
  • TBS transport block size
  • FIG. 9 illustrates an architecture of a wireless network in accordance with an example
  • FIG. 10 illustrates a diagram of a wireless device (e.g., UE) in accordance with an example
  • FIG. 11 illustrates interfaces of baseband circuitry in accordance with an example
  • FIG. 12 illustrates a diagram of a wireless device (e.g., UE) in accordance with an example.
  • UE wireless device
  • Packet data latency is a key performance metric in wireless communication systems. Packet data latency can be important for perceived responsiveness of the wireless communication system. Packet data latency is also a parameter that can influence throughput.
  • Hypertext transfer protocol (HTTP)/transmission control protocol (TCP) is the prevalent application and transport layer protocol suite used on the internet today.
  • HTTP/TCP-based transactions over the internet can be in the range of a few tens of kilobytes to one megabyte. In this size range, a TCP slow start period can be a significant portion of a total transport period of a packet stream.
  • a shorted transmission time interval (TTI) and reduced processing time is desirable for 3GPP LTE systems, as well as support of a reduced minimum timing as compared to legacy downlink (DL) and uplink (UL) operations.
  • 3GPP LTE systems it is desirable for 3GPP LTE systems to support the reduced minimum timing as compared to a legacy operation between a UL grant and UL data and between DL data and DL hybrid automatic repeat request (HARQ) feedback for legacy 1 millisecond (ms) TTI operation, while reusing a 3GPP LTE Release 14 channel design for a physical downlink shared channel (PDSCH), enhanced physical downlink control channel (e)(PDCCH), physical uplink shared channel (PUSCH) and/or physical uplink control channel (PUCCH).
  • PDSCH physical downlink shared channel
  • e enhanced physical downlink control channel
  • PUSCH physical uplink shared channel
  • PUCCH physical uplink control channel
  • the support for the reduced minimum timing can apply for the case of restricted maximum supported transport block sizes for the PDSCH and/or PUSCH when the reduced minimum timing is in operation, and can be applicable for the case of unrestricted maximum supported transport block sizes (TBS).
  • a size of the reduction in minimum timing can be different between UL and DL cases.
  • 3 GPP LTE systems it is desirable for 3 GPP LTE systems to support a reduced maximum timing advance (TA) to enable processing time reductions. Processing time reductions can further be improved by modifying existing channel state information (CSI) feedback schemes.
  • TA timing advance
  • CSI channel state information
  • 3GPP LTE systems it is desirable for 3GPP LTE systems to support asynchronous HARQ for the PUSCH with reduced processing time.
  • the processing time can contribute to a total end to end delay for connected user equipments (UEs).
  • the processing time can impact a time budget for DL HARQ feedback and PUSCH scheduling.
  • Different implementations can be made with different constraints, and thus have different capabilities. Therefore, a trade-off between implementation complexity and latency performance can be considered.
  • a convolutional turbo code can be used for downlink shared channel (DL-SCH) and uplink shared channel (UL-SCH) encoding, and the processing time can be proportional to a transport block (TB) size.
  • the processing time can be reduced by limiting a maximum transport block size (TBS), which can effectively be the same size as that in a shortened TTI (sTTI).
  • TBS transport block size
  • the reduction in minimum timing can imply that different
  • PUCCH HARQ-ACK timings are applied by a UE configured for a reduced processing time as compared to a legacy UE.
  • the different PUCCH HARQ-ACK timings for the different UEs can create a collision risk in a PUCCH resource mapping in which two DL assignments point to a same PUCCH physical resource for a Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) transmission.
  • HARQ-ACK Hybrid Automatic Repeat Request Acknowledgement
  • FIG. 1 illustrates an example of a physical uplink control channel (PUCCH) resource collision for PUCCH format la/lb.
  • PUCCH resource collision can occur when a PDCCH #1 and PDCCH #2 use a same first control channel element (CCE) in subframe n and n+2, and two subframes are linked to a single UL subframe (i.e., subframe n+4) for HARQ-ACK feedback due to unequal HARQ-ACK feedback delays.
  • CCE first control channel element
  • a legacy UE can receive the PDCCH #1 on subframe n in a downlink.
  • the legacy UE can utilize a legacy HARQ timeline, and based on this legacy HARQ timeline, the legacy UE can transmit a physical uplink control channel (PUCCH) on subframe n+4 in an uplink (i.e., four subframes later).
  • a UE configured for the reduced processing time e.g., a 3GPP LTE Release 14 UE
  • the UE configured for the reduced processing time can utilize a reduced HARQ timeline, and based on this reduced HARQ timeline, the UE configured for the reduced processing time can transmit a PUCCH on subframe n+4 in the uplink (i.e., two subframes later).
  • the PDCCH #1 and PDCCH #2 can use the same first CCE in subframe n and subframe n+2, respectively, and the PUCCH for both UEs can be in the same uplink subframe (i.e., subframe n+4). As a result, there can be a PUCCH resource collision between the two UEs.
  • DCI downlink control information
  • a reduced DL HARQ and UL scheduling timeline can be supported in a 3GPP LTE wireless communication system by limiting a maximum transport block size (TBS) and/or a maximum timing advance (TA) value.
  • TTI transmission time interval
  • Techniques are provided for restricting a maximum number of transmission channel bits receivable in a transmission time interval (TTI) to support the reduced processing time in both DL and UL.
  • the reduced processing time can be for a legacy 1 ms TTI.
  • the reduced processing time can be supported while minimizing impacts on UE implementation.
  • a UE-category-dependent maximum TBS size restriction mechanism is defined, which can utilize a per-TB or per-DCI-dual-TBs-based approach.
  • the PUCCH resource collision issue can be resolved between legacy UEs and 3GPP LTE Release 14 UEs that are configured for the reduced processing time.
  • a number of UE categories are defined in 3 GPP LTE Release 13.
  • the UE categories can range from 0 to 17 in DL and to 14 in UL.
  • the UE categories can be used to define general UE performance characteristics, such as a maximum number of downlink shared channel (DL-SCH) or uplink shared channel (UL-SCH) transport block bits received or transmitted within a TTI, an extent to which different multi-antenna capabilities and modulation schemes are supported, etc.
  • DL-SCH and UL-SCH processing time requisites are defined assuming that the UE operates at a UE category maximum peak data rate at 100.15 kilometers (km) from an eNodeB (which corresponds to a 0.67 ms TA value).
  • a limitation on a maximum number of DL-SCH/UL-SCH TB bits within a TTI can be implemented to reduce a minimum processing time, while minimizing an impact on UE implementation.
  • a reduction to a number of blind decoding attempts on the PDCCH or ePDCCH can be implemented to reduce the minimum processing time, while minimizing the impact on UE implementation.
  • the restriction on the maximum number of DL-SCH/UL-SCH TB bits within the TTI can effectively restrict the transport block size (TBS), and the restriction on the TBS can allow for a faster convolutional turbo code (CTC) decoding or encoding on the UE side.
  • CTC convolutional turbo code
  • the TBS restriction allowing for the reduced processing time can be UE-category dependent.
  • different scaling factors ⁇ ⁇ (0 ⁇ n ⁇ N) can be defined corresponding to each reduced processing time (or delay value) D n , if the UE supports more than one reduced processing time.
  • the processing time (D n ) (or delay value) can be variable when the UE supports more than one reduced processing time.
  • the reduced processing time (or delay value) D n due to the TBS restriction can cause a UE to transmit HARQ-ACK feedback in a reduced number of subframes after receiving a PDCCH in a DL subframe (e.g., two subframes as opposed to four subframes).
  • FIG. 2 is an exemplary table that includes user equipment (UE)-category -based maximum transport block size (TBS) restrictions for processing time reduction.
  • UE user equipment
  • TBS maximum transport block size
  • a reduced processing time (D n ) (or delay value) can be determined based on an index value.
  • the index value can range from 0 to N— 1, where N is an integer.
  • the reduced processing time (D n ) (or delay value) can range from D 0 to O N _ t .
  • the scaled maximum TB size (or reduced TBS for UE category i) can range from ⁇ 0 x TBSi to A N _ t x TBSi, wherein TBS j can represent a maximum number of DL-SCH or UL-SCH transport block bits received or transmitted within a TTI for UE category i .
  • the corresponding reduced processing time (D n ) for the PDSCH can be D l5 and a scaled maximum TBS (or reduced TBS) for UE category i can be reduced by an scaling factor Ay to be Ay x TBS ; in order to apply the reduced processing time (D n ) (or delay value).
  • a TBS limitation can be performed on a per-TB basis, as different UE categories can have different ratios of maximum bits per TTI to maximum bits per TB.
  • paired values of ⁇ D n , ⁇ ⁇ > can be fixed in accordance with the 3 GPP LTE specification, and therefore, may not be dynamically adjustable. If a receive number of TBS is smaller than ⁇ 0 x TBS i for UE category 1 , then the UE can feedback HARQ-ACK or transmit a PUSCH (if scheduled) in subframe n + D 0 after receiving a PDSCH or UL grant on a PDCCH in a subframe n in an FDD system.
  • the UE can feedback HARQ-ACK or transmit a PUSCH (if scheduled) in subframe n + D 0 (i.e., n+2) after receiving a PDSCH or UL grant on a PDCCH in a subframe n in an FDD system.
  • the ability to transmit the HARQ- ACK feedback in subframe n + D 0 (i.e., n+2) is an improvement over previous solutions, in which HARQ-ACK feedback may be transmitted after four subframes (i.e., n+4).
  • the paired value of ⁇ D n , ⁇ ⁇ > can be indicated as part of a UE capability signaling.
  • an actual processing time for a given UE can depend on a timing advance (TA) value.
  • the limitation or restriction of the TBS can be a function of the TA value configured for the given UE.
  • a maximum number of bits of a downlink-SCH transport block received within a TTI can depend on a maximum number of supported layers for spatial multiplexing in downlink. Therefore, the limitation or restriction of the TBS can also be a function of the maximum number of supported layers for spatial multiplexing in downlink within the given UE category.
  • a maximum number of PRB pairs to be allocated can be defined. Since a number of computationally demanding components in a receiver chain (e.g., channel estimation, PDCCH decoding, TA values etc.) are agnostic to a number of TB bits, setting the maximum number of PRB pairs can relax the processing restraints of the UE category.
  • a reduced processing time (compared to 3GPP LTE Release 13) can be configured by the eNodeB, but subject to a corresponding UE capability.
  • the UE can skip decoding of one TB or multiple TBs scheduled by one DCI by comparing the TB(s) against a size threshold.
  • the size threshold can be defined in accordance with a value corresponding to the scaled maximum TB size (or reduced TBS for UE category i), such as ⁇ 0 x TBS A 1 x TBS t or N _- ⁇ x TBSi.
  • the UE can determine to skip the decoding based on the comparison between the size threshold and a sum of sizes for two TBs or on a per-TB basis associated with the reduced processing time configured by the eNodeB. In addition, the UE can determine to skip decoding based on the TA value.
  • a separate PUCCH resource starting position N puccH can be defined to resolve a PUCCH resource collision issue between legacy UEs and UEs
  • the UE can a PUCCH resource npj CCH to transmit a HARQ-ACK in subframe n + D n for a PDSCH transmission, and the PUCCH resource can be indicated by detection of a corresponding PDCCH in subframe n.
  • n P u CCH n CCE + py CCH
  • n P u CCH (M— i— 1) x
  • n CCE can represent a number of a first control channel element (CCE) used for transmission of a corresponding downlink control information (DCI) assignment
  • M can represent a number of DL subframes associated with a single UL subframe for HARQ-ACK feedback
  • Sj can represent CCE numbers within a symbol index (3)
  • N PUCCH can be configured by higher layers in a
  • N p (3 U ) CCH can be provided to the UE through a DL broadcast channel.
  • N ⁇ 3 ⁇ 4 can represent a downlink bandwidth configuration, expressed in units of resource blocks (RBs) and can represent a resource block size in a frequency domain that is expressed as a number of subcarriers.
  • n CCE can represent a number of the first CCE used to transmit a corresponding PDCCH in a DL subframe that links to subframe n + D n for a corresponding HARQ-ACK feedback.
  • FIG. 3 illustrates an example of a physical uplink control channel (PUCCH) resource mapping for a user equipment (UE) configured with a reduced processing time.
  • the PUCCH resource mapping can function to avoid collisions between legacy UEs and UE configured with the reduced processing time.
  • the PUCCH resource mapping can utilize separate PUCCH starting positions for the different UEs, thereby avoiding the collision between the legacy UEs and UE configured with the reduced processing time.
  • a legacy UE can receive a PDCCH #1 on subframe n in a downlink.
  • the legacy UE can utilize a legacy HARQ timeline (e.g., a DL HARQ timeline without a reduced processing time).
  • the legacy UE UE1 can transmit a PUCCH on subframe n+4 in an uplink (i.e., four subframes later).
  • the UE configured for the reduced processing time UE2 can receive a PDCCH #2 on subframe n+2 in the downlink.
  • the UE configured for the reduced processing time can utilize a reduced HARQ timeline (e.g., a DL HARQ timeline with a reduced processing time). Based on the reduced HARQ timeline, the UE configured for the reduced processing time (UE2) can transmit a PUCCH on subframe n+4 in the uplink (i.e., two subframes later).
  • the PDCCH #1 and PDCCH #2 can use the same first CCE (e.g., a n CCE value of 2) in subframe n and subframe n+2, respectively, and the PUCCH for both UEs can be in the same uplink subframe (i.e., subframe n+4).
  • the PUCCH #1 and PDCCH #2 can use the same first CCE (e.g., a n CCE value of 2) in subframe n and subframe n+2, respectively, and the PUCCH for both UEs can be in the same uplink subframe (i.e., subframe n+4).
  • the UE configured for the reduced processing time can be configured to utilize a reduced DL HARQ-ACK feedback delay (e.g., 2 ms) by controlling the TBS and scaling factor ⁇ ⁇ , as discussed earlier.
  • the legacy UE UE1 is not configured for the processing time reduction, and therefore, the legacy UE (UE1) can follow the legacy DL HARQ timeline.
  • n CCE 2
  • n P u CCH n CCE + N pyCCH for an FDD system. Therefore, the legacy
  • both UEs can transmit their respective HARQ-ACK feedbacks on the same subframe, while using different PUCCH resources.
  • a HARQ-ACK resource compression scheme can be implemented.
  • an eNodeB scheduler restriction can ensure that no PDCCHs have a same CCE for DL subframes associated with a single UL subframe for HARQ- ACK feedback.
  • a PUCCH resource offset URO
  • UCI PUCCH resource offset
  • a PUCCH resource (n pijCCH ) for HARQ-ACK corresponding to a PDSCH with a reduced processing time can be determined as a function of the first CCE used for a respective DL assignment and a value of an URO information element (IE), as
  • n P u CCH can be replaced with n pyCCH to further remove a resource collision risk.
  • n P u CCH can be replaced with n pyCCH to further
  • n pijCCH PUCCH resource for HARQ- ACK corresponding to the PDSCH with the reduced processing time
  • n p ⁇ ccH (M - i - 1) x S + i x S 1+1 + n CCE i + N ⁇ CCH + ⁇ ⁇ for a TDD system.
  • FIG. 4 is an exemplary table that includes physical uplink control channel (PUCCH) resource offset (URO) fields in downlink (DL) assignment downlink control information (DCI) formats.
  • a URO field or URO information element (IE) can be represented using 2 bits.
  • the URO field or URO IE in the DL assignment DCI formats can be mapped to certain URO IE values ( ⁇ ⁇ ).
  • a first URO field in the DL DCI format can be mapped to a ⁇ ⁇ value of 0.
  • a second URO field in the DL DCI format can be mapped to a ⁇ ⁇ value of -1.
  • a third URO field in the DL DCI format can be mapped to a ⁇ ⁇ value of -2.
  • a fourth URO field in the DL DCI format can be mapped to a ⁇ ⁇ value of 2.
  • the addition of an explicit URO field or URO IE in the DL DCI formats can be avoided if an existing IE is interpreted as providing the URO.
  • a transmission power control (TPC) IE in the DL subframe in which a downlink assignment index (DAI) is larger than one can be used as the URO IEs.
  • a set of PUCCH resources can be configured by higher layers as part of a reduced processing time configuration message, and then a URO can be additionally used to indicate one selected channel from this PUCCH resources set.
  • a UE can determine that a default processing time is used when a corresponding DCI format is transmitted in common search spaces (CSS), regardless of whether the UE is explicitly configured for the reduced processing time.
  • the default processing time can be a 3GPP LTE Release 13 DL HARQ timing or UL grant timing.
  • a fallback to a legacy processing timing can be supported depending on a type of search space.
  • DCI for a reduced processing time e.g., n+3
  • DCI for the legacy processing time e.g., n+4
  • the HARQ processes of the reduced processing time (e.g., n+3) 1 ms TTI can be shared with the legacy processing time (e.g., n+4) 1 ms TTI.
  • the HARQ processes of (n+3) 1 ms TTI and (n+4) 1 ms TTI can be shared for the PDSCH.
  • the HARQ processes of (n+3) 1 ms TTI and (n+4) 1 ms TTI can be shared.
  • the eNodeB can change between the (n+3) and (n+4) scheduling timing in a defined manner.
  • 3GPP Release 13 DCI formats can be modified to include a new bit.
  • the new bit can dynamically indicate which of the legacy timelines or shortened timeline with reduced processing times are selected for a scheduled DL or UL data transmission.
  • a user equipment can be configured to perform wireless communication.
  • the UE can receive one or more transport blocks or a downlink control information (DCI) format for an uplink (UL) grant in a subframe.
  • DCI downlink control information
  • the UE can select a physical uplink control channel (PUCCH) resource in an UL subframe for hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback or a physical uplink shared channel (PUSCH) transmission, and the PUCCH resource can be selected based on a UE category and/or transport block sizes (TBS) of a physical downlink shared channel (PDSCH) or a scheduled physical uplink shared channel (PUSCH), respectively.
  • HARQ hybrid automatic repeat request
  • ACK physical uplink shared channel
  • TBS transport block sizes
  • the UE in order to select the UL subframe for the HARQ-ACK feedback or PUSCH transmission based on the UE category and TBS of the PDSCH or scheduled PUSCH, the UE can define different scaling factors ⁇ ⁇ (0 ⁇ n ⁇ N) corresponding to each reduced processing time (or delay value) D n , and then transmit the HARQ-ACK or PUSCH in subframe n + D n if the TBS of the PDSCH in subframe n or the PUSCH scheduled by the UL grant in subframe n is not larger than ⁇ ⁇ x TBS ; , where TBS ; can represent a maximum number of downlink shared channel (DL-SCH) or uplink shared channel (UL-SCH) transport block bits received or transmitted within a transmission time interval (TTI) for UE category i .
  • TTI transmission time interval
  • a TBS limitation can be performed on a per transport block (TB) basis.
  • the scaling factors ⁇ ⁇ and a paired delay value D n can be fixed in the 3GPP LTE specification.
  • the scaling factors ⁇ ⁇ and a paired delay value D n can be indicated by the UE as part of a UE capability message for processing time reduction.
  • the scaling factors ⁇ ⁇ for an associated delay value D n can be a function of a timing advance (TA) value configured for a given UE.
  • the scaling factors ⁇ ⁇ for an associated delay value D n can be a function of a maximum number of supported layers for spatial multiplexing in downlink within a UE category.
  • processing requisites of a UE category can be relaxed by setting a maximum number of physical resource block (PRB) pairs that can be allocated for the UE.
  • the UE can skip decoding of one TB or multiple TBs scheduled by one DCI by comparing the TB(s) against a size threshold.
  • the size threshold can be compared to a sum of sizes for two TBs or on a per-TB basis associated with a processing time configured by an eNodeB.
  • the UE can receive a separate PUCCH resource starting position N PUCCH configured by higher layers, and then determine the PUCCH resource based on a number of a first control channel element (CCE) used for transmission of a corresponding DCI
  • CCE first control channel element
  • a PUCCH resource offset can be provided in respective DL assignment DCI formats, and the PUCCH resource can be determined based on a value of an URO information element (IE) field.
  • IE URO information element
  • four values of ⁇ 0, -1 , -2, 2> can be defined to associate with four states of a 2-bit URO field.
  • a value of a transmission power control can indicate a resource for a HARQ-ACK transmission if a value of a downlink assignment index (DAI) is greater than one.
  • FIG. 5 Another example provides functionality 500 of a user equipment (UE) operable to perform uplink transmissions using a reduced transport block size (TBS), as shown in FIG. 5.
  • the UE can comprise one or more processors.
  • the one or more processors can be configured to decode one or more transport blocks received from an eNodeB over a physical downlink shared channel (PDSCH) in a subframe n, as in block 510.
  • PDSCH physical downlink shared channel
  • the one or more processors can be configured to encode a hybrid automatic request (HARQ) acknowledgment (ACK) feedback for transmission using a selected PUCCH resource in a subframe n+D n when the TBS of the PDSCH in the subframe n is a reduced TBS that is not larger than a scaling factor ( ⁇ ⁇ ) multiplied by a maximum number of downlink shared channel (DL-SCH) transport block bits received within a transmission time interval (TTI) for a UE category i (TBSi), and D n is a reduced processing time that corresponds to the scaling factor ( ⁇ ⁇ ), as in block 520.
  • HARQ hybrid automatic request
  • ACK acknowledgment
  • the UE can comprise memory interfaced with the one or more processors, and the memory can be configured to store the scaling factor ( ⁇ ⁇ ), the maximum number of DL-SCH transport block bits received with the TTI for the UE category i (TBSi), and the reduced processing time (D n ).
  • Another example provides functionality 600 of a user equipment (UE) operable to perform uplink transmissions using a reduced transport block size (TBS), as shown in FIG. 6.
  • the UE can comprise one or more processors.
  • the one or more processors can be configured to decode a downlink control information (DCI) format for an uplink grant received from an eNodeB in a subframe n, as in block 610.
  • DCI downlink control information
  • the one or more processors can be configured to encode a physical uplink control channel (PUSCH) transmission for delivery in a subframe n+D n when the TBS of the PUSCH transmission scheduled by the uplink grant in the subframe n is a reduced TBS that is not larger than a scaling factor ( ⁇ ⁇ ) multiplied by a maximum number of uplink shared channel (UL-SCH) transport block bits transmitted within a transmission time interval (TTI) for a UE category i (TBSi), and Dn is a reduced processing time that corresponds to the scaling factor ( ⁇ ⁇ ), as in block 620.
  • PUSCH physical uplink control channel
  • the UE can comprise memory interfaced with the one or more processors, and the memory can be configured to store the scaling factor ( ⁇ ⁇ ), the maximum number of UL-SCH transport block bits received with the TTI for the UE category i (TBSi), and the reduced processing time (D n ).
  • Another example provides at least one machine readable storage medium having instructions 700 embodied thereon for performing uplink transmissions at a user equipment (UE) using a reduced transport block size (TBS), as shown in FIG. 7.
  • the instructions can be executed on a machine, where the instructions are included on at least one computer readable medium or one non-transitory machine readable storage medium.
  • the instructions when executed by one or more processors of the UE perform: decoding, at the UE, one or more transport blocks received from an eNodeB over a physical downlink shared channel (PDSCH) in a subframe n, as in block 710.
  • PDSCH physical downlink shared channel
  • the instructions when executed by one or more processors of the UE perform: selecting, at the UE, a PUCCH resource in a subframe n+D n based on a UE category i and a TBS of the PDSCH in the subframe n, wherein D n is a reduced processing time, as in block 720.
  • the instructions when executed by one or more processors of the UE perform: encoding, at the UE, a hybrid automatic request (HARQ) acknowledgment (ACK) feedback for transmission using the selected PUCCH resource in the subframe n+D n , as in block 730.
  • HARQ hybrid automatic request
  • ACK acknowledgment
  • Another example provides at least one machine readable storage medium having instructions 800 embodied thereon for performing uplink transmissions at a user equipment (UE) using a reduced transport block size (TBS), as shown in FIG. 8.
  • the instructions can be executed on a machine, where the instructions are included on at least one computer readable medium or one non-transitory machine readable storage medium.
  • the instructions when executed by one or more processors of the UE perform: decoding, at the UE, a downlink control information (DCI) format for an uplink grant received from an eNodeB in a subframe n, as in block 810.
  • DCI downlink control information
  • the instructions when executed by one or more processors of the UE perform: identifying, at the UE, a subframe n+D n based on a UE category i and a TBS of a physical uplink control channel (PUSCH) scheduled by the uplink grant in the subframe n, wherein D n is a reduced processing time, as in block 820.
  • the instructions when executed by one or more processors of the UE perform: encoding, at the UE, a PUSCH transmission for delivery using the subframe n+Dn, as in block 830.
  • PUSCH physical uplink control channel
  • FIG. 9 illustrates an architecture of a system 900 of a network in accordance with some embodiments.
  • the system 900 is shown to include a user equipment (UE) 901 and a UE 902.
  • the UEs 901 and 902 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.
  • PDAs Personal Data Assistants
  • pagers pagers
  • laptop computers desktop computers
  • wireless handsets wireless handsets
  • any of the UEs 901 and 902 can comprise an Internet of Things (IoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections.
  • An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network
  • M2M machine-to-machine
  • MTC machine-type communications
  • PLMN Proximity-Based Service
  • D2D device-to-device
  • An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.
  • the UEs 901 and 902 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 910—
  • the RAN 910 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.
  • UMTS Evolved Universal Mobile Telecommunications System
  • E-UTRAN Evolved Universal Mobile Telecommunications System
  • NG RAN NextGen RAN
  • the UEs 901 and 902 utilize connections 903 and 904, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 903 and 904 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like.
  • GSM Global System for Mobile Communications
  • CDMA code-division multiple access
  • PTT Push-to-Talk
  • POC PTT over Cellular
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 5G fifth generation
  • NR New Radio
  • the UEs 901 and 902 may further directly exchange communication data via a ProSe interface 905.
  • the ProSe interface 905 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the UE 902 is shown to be configured to access an access point (AP) 906 via connection 907.
  • the connection 907 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 906 would comprise a wireless fidelity (WiFi®) router.
  • WiFi® wireless fidelity
  • the AP 906 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • the RAN 910 can include one or more access nodes that enable the connections 903 and 904. These access nodes (ANs) can be referred to as base stations (BSs),
  • NodeBs evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • the RAN 910 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 911, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 912.
  • LP low power
  • any of the RAN nodes 911 and 912 can terminate the air interface protocol and can be the first point of contact for the UEs 901 and 902.
  • any of the RAN nodes 911 and 912 can fulfill various logical functions for the RAN 910 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller
  • the UEs 901 and 902 can be configured to communicate using Orthogonal Frequency -Division Multiplexing (OFDM)
  • OFDM Orthogonal Frequency -Division Multiplexing
  • OFDMMA Orthogonal Frequency -Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • the OFDM signals can comprise a plurality of orthogonal subcarriers.
  • a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 911 and 912 to the UEs 901 and 902, while uplink transmissions can utilize similar techniques.
  • the grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot.
  • a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
  • Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively.
  • the duration of the resource grid in the time domain corresponds to one slot in a radio frame.
  • the smallest time-frequency unit in a resource grid is denoted as a resource element.
  • Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements.
  • Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated.
  • the physical downlink shared channel may carry user data and higher- layer signaling to the UEs 901 and 902.
  • the physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 901 and 902 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel.
  • downlink scheduling (assigning control and shared channel resource blocks to the UE 901 within a cell) may be performed at any of the RAN nodes 911 and 912 based on channel quality information fed back from any of the UEs 901 and 902.
  • the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 901 and 902.
  • the PDCCH may use control channel elements (CCEs) to convey the control information.
  • CCEs control channel elements
  • the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching.
  • Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs).
  • RAGs resource element groups
  • QPSK Quadrature Phase Shift Keying
  • the PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition.
  • DCI downlink control information
  • There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L l, 2, 4, or 8).
  • Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts.
  • some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission.
  • the EPDCCH may be transmitted using one or more enhanced the control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.
  • EPCCH enhanced physical downlink control channel
  • ECCEs enhanced the control channel elements
  • each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs).
  • EREGs enhanced resource element groups
  • An ECCE may have other numbers of EREGs in some situations.
  • the RAN 910 is shown to be communicatively coupled to a core network (CN) 920— via an SI interface 913.
  • the CN 920 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN.
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the SI interface 913 is split into two parts: the SI -U interface 914, which carries traffic data between the RAN nodes 911 and 912 and the serving gateway (S-GW) 922, and the S l-mobility management entity (MME) interface 915, which is a signaling interface between the RAN nodes 911 and 912 and MMEs 921.
  • S-GW serving gateway
  • MME S l-mobility management entity
  • the CN 920 comprises the MMEs 921, the S-GW 922, the Packet Data Network (PDN) Gateway (P-GW) 923, and a home subscriber server (HSS) 924.
  • the MMEs 921 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • GPRS General Packet Radio Service
  • the MMEs 921 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS 924 may comprise a database for network users, including subscription-related information to support the network entities' handling of
  • the CN 920 may comprise one or several HSSs 924, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS 924 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • the S-GW 922 may terminate the SI interface 913 towards the RAN 910, and routes data packets between the RAN 910 and the CN 920.
  • the S-GW 922 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the P-GW 923 may terminate an SGi interface toward a PDN.
  • the P-GW 923 may route data packets between the EPC network 923 and external networks such as a network including the application server 930 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 925.
  • the application server 930 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.).
  • PS UMTS Packet Services
  • LTE PS data services etc.
  • the P-GW 923 is shown to be communicatively coupled to an application server 930 via an IP communications interface 925.
  • the application server 930 can also be configured to support one or more communication services (e.g., Voice- over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 901 and 902 via the CN 920.
  • VoIP Voice- over-Internet Protocol
  • PTT sessions PTT sessions
  • group communication sessions social networking services, etc.
  • the P-GW 923 may further be a node for policy enforcement and charging data collection.
  • Policy and Charging Enforcement Function (PCRF) 926 is the policy and charging control element of the CN 920.
  • PCRF Policy and Charging Enforcement Function
  • HPLMN Home Public Land Mobile Network
  • IP-CAN Internet Protocol Connectivity Access Network
  • HPLMN Home Public Land Mobile Network
  • V-PCRF Visited PCRF
  • VPLMN Visited Public Land Mobile Network
  • the PCRF 926 may be communicatively coupled to the application server 930 via the P-GW 923.
  • the application server 930 may signal the PCRF 926 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters.
  • the PCRF 926 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server 930.
  • PCEF Policy and Charging Enforcement Function
  • TFT traffic flow template
  • QCI QoS class of identifier
  • FIG. 10 illustrates example components of a device 1000 in accordance with some embodiments.
  • the device 1000 may include application circuitry 1002, baseband circuitry 1004, Radio Frequency (RF) circuitry 1006, front-end module (FEM) circuitry 1008, one or more antennas 1010, and power management circuitry (PMC) 1012 coupled together at least as shown.
  • the components of the illustrated device 1000 may be included in a UE or a RAN node.
  • the device 1000 may include less elements (e.g., a RAN node may not utilize application circuitry 1002, and instead include a processor/controller to process IP data received from an EPC).
  • the device 1000 may include additional elements such as, for example, memory /storage, display, camera, sensor, or input/output (I/O) interface.
  • additional elements such as, for example, memory /storage, display, camera, sensor, or input/output (I/O) interface.
  • the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).
  • C-RAN Cloud-RAN
  • the application circuitry 1002 may include one or more application processors.
  • the application circuitry 1002 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.).
  • the processors may be coupled with or may include memory /storage and may be configured to execute instructions stored in the memory /storage to enable various applications or operating systems to run on the device 1000.
  • processors of application circuitry 1002 may process IP data packets received from an EPC.
  • the baseband circuitry 1004 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 1004 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 1006 and to generate baseband signals for a transmit signal path of the RF circuitry 1006.
  • Baseband processing circuity 1004 may interface with the application circuitry 1002 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 1006.
  • the baseband circuitry 1004 may include a third generation (3G) baseband processor 1004a, a fourth generation (4G) baseband processor 1004b, a fifth generation (5G) baseband processor 1004c, or other baseband processor(s) 1004d for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.).
  • the baseband circuitry 1004 e.g., one or more of baseband processors 1004a-d
  • baseband processors 1004a-d may be included in modules stored in the memory 1004g and executed via a Central Processing Unit (CPU) 1004e.
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • modulation/demodulation circuitry of the baseband circuitry 1004 may include Fast- Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality.
  • FFT Fast- Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 1004 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • the baseband circuitry 1004 may include one or more audio digital signal processor(s) (DSP) 1004f.
  • the audio DSP(s) 1004f may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband circuitry 1004 and the application circuitry 1002 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 1004 may provide for
  • the baseband circuitry 1004 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • multi-mode baseband circuitry Embodiments in which the baseband circuitry 1004 is configured to support radio communications of more than one wireless protocol.
  • RF circuitry 1006 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 1006 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 1006 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 1008 and provide baseband signals to the baseband circuitry 1004.
  • RF circuitry 1006 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 1004 and provide RF output signals to the FEM circuitry 1008 for transmission.
  • the receive signal path of the RF circuitry 1006 may include mixer circuitry 1006a, amplifier circuitry 1006b and filter circuitry 1006c.
  • the transmit signal path of the RF circuitry 1006 may include filter circuitry 1006c and mixer circuitry 1006a.
  • RF circuitry 1006 may also include synthesizer circuitry 1006d for synthesizing a frequency for use by the mixer circuitry 1006a of the receive signal path and the transmit signal path.
  • the mixer circuitry 1006a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 1008 based on the synthesized frequency provided by synthesizer circuitry 1006d.
  • the amplifier circuitry 1006b may be configured to amplify the down-converted signals and the filter circuitry 1006c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • Output baseband signals may be provided to the baseband circuitry 1004 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 1006a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 1006a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1006d to generate RF output signals for the FEM circuitry 1008.
  • the baseband signals may be provided by the baseband circuitry 1004 and may be filtered by filter circuitry 1006c.
  • the mixer circuitry 1006a of the receive signal path and the mixer circuitry 1006a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
  • the mixer circuitry 1006a of the receive signal path and the mixer circuitry 1006a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 1006a of the receive signal path and the mixer circuitry 1006a may be arranged for direct downconversion and direct upconversion, respectively.
  • the mixer circuitry 1006a of the receive signal path and the mixer circuitry 1006a of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 1006 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 1004 may include a digital baseband interface to communicate with the RF circuitry 1006.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 1006d may be a fractional -N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 1006d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 1006d may be configured to synthesize an output frequency for use by the mixer circuitry 1006a of the RF circuitry 1006 based on a frequency input and a divider control input.
  • the synthesizer circuitry 1006d may be a fractional N/N+l synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 1004 or the applications processor 1002 depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 1002.
  • Synthesizer circuitry 1006d of the RF circuitry 1006 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA).
  • the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 1006d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (fLO).
  • the RF circuitry 1006 may include an IQ/polar converter.
  • FEM circuitry 1008 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 1010, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1006 for further processing.
  • FEM circuitry 1008 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 1006 for transmission by one or more of the one or more antennas 1010.
  • the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 1006, solely in the FEM 1008, or in both the RF circuitry 1006 and the FEM 1008.
  • the FEM circuitry 1008 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 1006).
  • the transmit signal path of the FEM circuitry 1008 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 1006), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1010).
  • PA power amplifier
  • the PMC 1012 may manage power provided to the baseband circuitry 1004.
  • the PMC 1012 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMC 1012 may often be included when the device 1000 is capable of being powered by a battery, for example, when the device is included in a UE.
  • the PMC 1012 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation
  • FIG. 10 shows the PMC 1012 coupled only with the baseband circuitry 1004.
  • the PMC 10 12 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 1002, RF circuitry 1006, or FEM 1008.
  • the PMC 1012 may control, or otherwise be part of, various power saving mechanisms of the device 1000. For example, if the device 1000 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 1000 may power down for brief intervals of time and thus save power.
  • DRX Discontinuous Reception Mode
  • the device 1000 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • the device 1000 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
  • the device 1000 may not receive data in this state, in order to receive data, it must transition back to
  • An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • Processors of the application circuitry 1002 and processors of the baseband circuitry 1004 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 1004 alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 1004 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers).
  • Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below.
  • RRC radio resource control
  • Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below.
  • Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.
  • FIG. 11 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • the baseband circuitry 1004 of FIG. 10 may comprise processors 1004a-1004e and a memory 1004g utilized by said processors.
  • Each of the processors 1004a-1004e may include a memory interface, 1104a-1104e, respectively, to send/receive data to/from the memory 1004g.
  • the baseband circuitry 1004 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 1112 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 1004), an application circuitry interface 1114 (e.g., an interface to send/receive data to/from the application circuitry 1002 of FIG. 10), an RF circuitry interface 1116 (e.g., an interface to send/receive data to/from RF circuitry 1006 of FIG.
  • a memory interface 1112 e.g., an interface to send/receive data to/from memory external to the baseband circuitry 1004
  • an application circuitry interface 1114 e.g., an interface to send/receive data to/from the application circuitry 1002 of FIG. 10
  • an RF circuitry interface 1116 e.g., an interface to send/receive data to/from RF circuitry 1006 of FIG.
  • a wireless hardware connectivity interface 1118 e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components
  • a power management interface 1120 e.g., an interface to send/receive power or control signals to/from the PMC 1012.
  • FIG. 12 provides an example illustration of the wireless device, such as a user equipment (UE), a mobile station (MS), a mobile wireless device, a mobile
  • the wireless device can include one or more antennas configured to communicate with a node, macro node, low power node (LPN), or, transmission station, such as a base station (BS), an evolved Node B (eNB), a baseband processing unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a relay station (RS), a radio equipment (RE), or other type of wireless wide area network (WWAN) access point.
  • the wireless device can be configured to communicate using at least one wireless communication standard such as, but not limited to, 3 GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and WiFi.
  • the wireless device can communicate using separate antennas for each wireless communication standard or shared antennas for multiple wireless communication standards.
  • the wireless device can communicate in a wireless local area network
  • the wireless device can also comprise a wireless modem.
  • the wireless modem can comprise, for example, a wireless radio transceiver and baseband circuitry (e.g., a baseband processor).
  • the wireless modem can, in one example, modulate signals that the wireless device transmits via the one or more antennas and demodulate signals that the wireless device receives via the one or more antennas.
  • FIG. 12 also provides an illustration of a microphone and one or more speakers that can be used for audio input and output from the wireless device.
  • the display screen can be a liquid crystal display (LCD) screen, or other type of display screen such as an organic light emitting diode (OLED) display.
  • the display screen can be configured as a touch screen.
  • the touch screen can use capacitive, resistive, or another type of touch screen technology.
  • An application processor and a graphics processor can be coupled to internal memory to provide processing and display capabilities.
  • a non-volatile memory port can also be used to provide data input/output options to a user.
  • the non-volatile memory port can also be used to expand the memory capabilities of the wireless device.
  • a keyboard can be integrated with the wireless device or wirelessly connected to the wireless device to provide additional user input.
  • a virtual keyboard can also be provided using the touch screen.
  • Example 1 includes an apparatus of a user equipment (UE) operable to perform uplink transmissions using a reduced transport block size (TBS), the apparatus comprising: one or more processors configured to: decode one or more transport blocks received from an eNodeB over a physical downlink shared channel (PDSCH) in a subframe n; and encode a hybrid automatic request (HARQ) acknowledgment (ACK) feedback for transmission using a selected PUCCH resource in a subframe n+D n when the TBS of the PDSCH in the subframe n is a reduced TBS that is not larger than a scaling factor ( ⁇ ⁇ ) multiplied by a maximum number of downlink shared channel (DL- SCH) transport block bits received within a transmission time interval (TTI) for a UE category i (TBSi), and D n is a reduced processing time that corresponds to the scaling factor ( ⁇ ⁇ ); and a memory interface configured to send to a memory the scaling factor ( ⁇ ⁇ ), the maximum number of DL-
  • Example 2 includes the apparatus of Example 1, further comprising a transceiver configured to: receive the one or more transport blocks from the eNodeB over the PDSCH in the subframe n; and transmit the HARQ ACK feedback using the selected PUCCH resource in the subframe n+D n .
  • Example 3 includes the apparatus of any of Examples 1 to 2, wherein the one or more processors are further configured to determine that the TBS of the PDSCH in the subframe n is the reduced TBS on a per-transport block basis.
  • Example 4 includes the apparatus of any of Examples 1 to 3, wherein the reduced processing time (D n ) and the scaling factor ( ⁇ ⁇ ) are predefined in a Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) Release 14 specification.
  • Example 5 includes the apparatus of any of Examples 1 to 4, wherein the one or more processors are further configured to generate a UE capability message for processing time reduction that includes the reduced processing time (D n ) and the scaling factor ( ⁇ ⁇ ).
  • Example 6 includes the apparatus of any of Examples 1 to 5, wherein the reduced processing time (D n ) and the scaling factor ( ⁇ ⁇ ) is a function of a timing advance (TA) value configured for the UE.
  • TA timing advance
  • Example 7 includes the apparatus of any of Examples 1 to 6, wherein the reduced processing time (D n ) and the scaling factor ( ⁇ ⁇ ) is a function of a maximum number of supported layers for spatial multiplexing in downlink within the UE category i.
  • Example 8 includes the apparatus of any of Examples 1 to 7, wherein the one or more processors are further configured to determine to skip decoding of the one or more transport blocks based on: a sum of sizes of the one or more transport blocks in relation to a defined threshold; or a size of the one or more transport blocks on a per-transport block basis in relation to a defined threshold.
  • Example 9 includes the apparatus of any of Examples 1 to 8, wherein the one or more processors are further configured to: process a separate PUCCH resource received via higher layer signaling, wherein the separate PUCCH resource is associated with a
  • Example 10 includes the apparatus of any of Examples 1 to 9, wherein the one or more processors are further configured to: process a downlink control information (DCI) assignment received from the eNodeB, wherein the downlink DCI assignment includes a PUCCH resource offset (URO) information element (IE) field; and determine the PUCCH resource for the HARQ ACK feedback based on a value of the PUCCH URO IE field (AURO).
  • DCI downlink control information
  • URO PUCCH resource offset
  • AURO PUCCH URO IE field
  • Example 11 includes an apparatus of a user equipment (UE) operable to perform uplink transmissions using a reduced transport block size (TBS), the apparatus comprising: one or more processors configured to: decode a downlink control information (DCI) format for an uplink grant received from an eNodeB in a subframe n; and encode a physical uplink control channel (PUSCH) transmission for delivery in a subframe n+D n when the TBS of the PUSCH transmission scheduled by the uplink grant in the subframe n is a reduced TBS that is not larger than a scaling factor ( ⁇ ⁇ ) multiplied by a maximum number of uplink shared channel (UL-SCH) transport block bits transmitted within a transmission time interval (TTI) for a UE category i (TBSi), and D n is a reduced processing time that corresponds to the scaling factor ( ⁇ ⁇ ); and a memory interface configured to send to a memory the scaling factor ( ⁇ ⁇ ), the maximum number of UL-SCH transport block bits received with
  • Example 12 includes the apparatus of Example 11, wherein the one or more processors are further configured to determine that the TBS of the PUSCH is the reduced TBS on a per-transport block basis.
  • Example 13 includes the apparatus of any of Examples 11 to 12, wherein the reduced processing time (D n ) and the scaling factor ( ⁇ ⁇ ) are predefined in a Third Generation Partnership Project (3 GPP) Long Term Evolution (LTE) Release 14 specification.
  • 3 GPP Third Generation Partnership Project
  • LTE Long Term Evolution
  • Example 14 includes the apparatus of any of Examples 11 to 13, wherein the one or more processors are further configured to generate a UE capability message for processing time reduction that includes the reduced processing time (D n ) and the scaling factor ( ⁇ ).
  • Example 15 includes the apparatus of any of Examples 11 to 14, wherein the reduced processing time (D n ) and the scaling factor ( ⁇ ⁇ ) is a function of a timing advance (TA) value configured for the UE.
  • D n reduced processing time
  • ⁇ ⁇ scaling factor
  • Example 16 includes the apparatus of any of Examples 11 to 15, wherein the reduced processing time (D n ) and the scaling factor ( ⁇ ⁇ ) is a function of a maximum number of supported layers for spatial multiplexing in downlink within the UE category i.
  • Example 17 includes at least one machine readable storage medium having instructions embodied thereon for performing uplink transmissions at a user equipment (UE) using a reduced transport block size (TBS), the instructions when executed by one or more processors of the UE perform the following: decoding, at the UE, one or more transport blocks received from an eNodeB over a physical downlink shared channel (PDSCH) in a subframe n; selecting, at the UE, a PUCCH resource in a subframe n+D n based on a UE category i and a TBS of the PDSCH in the subframe n, wherein D n is a reduced processing time; and encoding, at the UE, a hybrid automatic request (HARQ) acknowledgment (ACK) feedback for transmission using the selected PUCCH resource in the subframe n+Dn.
  • HARQ hybrid automatic request
  • ACK acknowledgment
  • Example 18 includes the at least one machine readable storage medium of Example 17, further comprising instructions when executed perform the following:
  • TBS of the PDSCH in the subframe n is a reduced TBS that is not larger than a scaling factor ( ⁇ ⁇ ) multiplied by a maximum number of downlink shared channel (DL-SCH) transport block bits received within a transmission time interval (TTI) for the UE category i (TBSi), and D n is the reduced processing time that corresponds to the scaling factor ( ⁇ ⁇ ).
  • Example 19 includes the at least one machine readable storage medium of any of Examples 17 to 18, wherein: the reduced processing time (D n ) and the scaling factor ( ⁇ ⁇ ) are predefined in a Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) Release 14 specification; or the reduced processing time (D n ) and the scaling factor ( ⁇ ⁇ ) is a function of a timing advance (TA) value configured for the UE; or the reduced processing time (D n ) and the scaling factor ( ⁇ ⁇ ) is a function of a maximum number of supported layers for spatial multiplexing in downlink within the UE category i.
  • 3GPP Third Generation Partnership Project
  • LTE Long Term Evolution
  • TA timing advance
  • Example 20 includes the at least one machine readable storage medium of any of Examples 17 to 19, further comprising instructions when executed perform the following: generating a UE capability message for processing time reduction that includes the reduced processing time (D n ) and the scaling factor ( ⁇ ⁇ ).
  • Example 21 includes the at least one machine readable storage medium of any of Examples 17 to 20, further comprising instructions when executed perform the following: processing a separate PUCCH resource received via higher layer signaling, wherein the
  • separate PUCCH resource is associated with a starting position of N y cct f ' m ⁇ determining the PUCCH resource for the HARQ ACK feedback based on a number of a first control channel element (CCE) used for transmission of a corresponding downlink
  • CCE first control channel element
  • DCI control information
  • Example 22 includes at least one machine readable storage medium having instructions embodied thereon for performing uplink transmissions at a user equipment (UE) using a reduced transport block size (TBS), the instructions when executed by one or more processors of the UE perform the following: decoding, at the UE, a downlink control information (DCI) format for an uplink grant received from an eNodeB in a subframe n; identifying, at the UE, a subframe n+D n based on a UE category i and a TBS of a physical uplink control channel (PUSCH) scheduled by the uplink grant in the subframe n, wherein D n is a reduced processing time; and encoding, at the UE, a PUSCH transmission for delivery using the subframe n+Dn.
  • DCI downlink control information
  • PUSCH physical uplink control channel
  • Example 23 includes the at least one machine readable storage medium of Example 22, further comprising instructions when executed perform the following:
  • TBS of the PUSCH scheduled by the uplink grant in the subframe n is a reduced TBS that is not larger than a scaling factor ( ⁇ ⁇ ) multiplied by a maximum number of uplink shared channel (UL-SCH) transport block bits transmitted within a transmission time interval (TTI) for the UE category i (TBSi), and D n is the reduced processing time that corresponds to the scaling factor ( ⁇ ⁇ ).
  • Example 24 includes the at least one machine readable storage medium of any of Examples 22 to 23, wherein: the reduced processing time (D n ) and the scaling factor ( ⁇ ⁇ ) are predefined in a Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) Release 14 specification; or the reduced processing time (D n ) and the scaling factor ( ⁇ ⁇ ) is a function of a timing advance (TA) value configured for the UE; or the reduced processing time (D n ) and the scaling factor ( ⁇ ⁇ ) is a function of a maximum number of supported layers for spatial multiplexing in downlink within the UE category i.
  • 3GPP Third Generation Partnership Project
  • LTE Long Term Evolution
  • TA timing advance
  • Example 25 includes a user equipment (UE) operable to perform uplink transmissions using a reduced transport block size (TBS), the UE comprising: means for decoding, at the UE, one or more transport blocks received from an eNodeB over a physical downlink shared channel (PDSCH) in a subframe n; means for selecting, at the UE, a PUCCH resource in a subframe n+D n based on a UE category i and a TBS of the PDSCH in the subframe n, wherein D n is a reduced processing time; and means for encoding, at the UE, a hybrid automatic request (HARQ) acknowledgment (ACK) feedback for transmission using the selected PUCCH resource in the subframe n+Dn.
  • HARQ hybrid automatic request
  • ACK acknowledgment
  • Example 26 includes the UE of Example 25, further comprising: means for encoding the HARQ ACK feedback for transmission using the selected PUCCH resource in the subframe n+D n when the TBS of the PDSCH in the subframe n is a reduced TBS that is not larger than a scaling factor ( ⁇ ⁇ ) multiplied by a maximum number of downlink shared channel (DL-SCH) transport block bits received within a transmission time interval (TTI) for the UE category i (TBSi), and D n is the reduced processing time that corresponds to the scaling factor ( ⁇ ).
  • a scaling factor ⁇ ⁇
  • Example 27 includes the UE of any of Examples 25 to 26, wherein: the reduced processing time (D n ) and the scaling factor ( ⁇ ⁇ ) are predefined in a Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) Release 14 specification; or the reduced processing time (D n ) and the scaling factor ( ⁇ ⁇ ) is a function of a timing advance (TA) value configured for the UE; or the reduced processing time (D n ) and the scaling factor ( ⁇ ⁇ ) is a function of a maximum number of supported layers for spatial multiplexing in downlink within the UE category i.
  • 3GPP Third Generation Partnership Project
  • LTE Long Term Evolution
  • TA timing advance
  • Example 28 includes the UE of any of Examples 25 to 27, further comprising: means for generating a UE capability message for processing time reduction that includes the reduced processing time (D n ) and the scaling factor ( ⁇ ⁇ ).
  • Example 29 includes the UE of any of Examples 25 to 28, further comprising: means for processing a separate PUCCH resource received via higher layer signaling, wherein the separate PUCCH resource is associated with a starting position of (3)
  • Np UCCH Np UCCH ; and means for determining the PUCCH resource for the HARQ ACK feedback based on a number of a first control channel element (CCE) used for transmission of a corresponding downlink control information (DCI) assignment and the starting position of (3)
  • CCE first control channel element
  • DCI downlink control information
  • Example 30 includes a user equipment (UE) operable to perform uplink transmissions using a reduced transport block size (TBS), the UE comprising: means for decoding, at the UE, a downlink control information (DCI) format for an uplink grant received from an eNodeB in a subframe n; means for identifying, at the UE, a subframe n+Dn based on a UE category i and a TBS of a physical uplink control channel (PUSCH) scheduled by the uplink grant in the subframe n, wherein Dn is a reduced processing time; and means for encoding, at the UE, a PUSCH transmission for delivery using the subframe n+Dn.
  • DCI downlink control information
  • PUSCH physical uplink control channel
  • Example 31 includes the UE of Example 30, further comprising: means for encoding the PUSCH transmission for delivery in the subframe n+D n when the TBS of the PUSCH scheduled by the uplink grant in the subframe n is a reduced TBS that is not larger than a scaling factor ( ⁇ ) multiplied by a maximum number of uplink shared channel (UL-SCH) transport block bits transmitted within a transmission time interval (TTI) for the UE category i (TBSi), and Dn is the reduced processing time that corresponds to the scaling factor ( ⁇ ⁇ ).
  • TTI transmission time interval
  • TTI transmission time interval
  • Example 32 includes the UE of any of Examples 30 to 31, wherein: the reduced processing time (Dn) and the scaling factor ( ⁇ ) are predefined in a Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) Release 14 specification; or the reduced processing time (D n ) and the scaling factor ( ⁇ ⁇ ) is a function of a timing advance (TA) value configured for the UE; or the reduced processing time (D n ) and the scaling factor ( ⁇ ⁇ ) is a function of a maximum number of supported layers for spatial multiplexing in downlink within the UE category i.
  • 3GPP Third Generation Partnership Project
  • LTE Long Term Evolution
  • TA timing advance
  • Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, compact disc-read-only memory (CD-ROMs), hard drives, non-transitory computer readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques.
  • the computing device may include a processor, a storage medium readable by the processor (including volatile and nonvolatile memory and/or storage elements), at least one input device, and at least one output device.
  • the volatile and non-volatile memory and/or storage elements may be a random-access memory (RAM), erasable programmable read only memory (EPROM), flash drive, optical drive, magnetic hard drive, solid state drive, or other medium for storing electronic data.
  • the node and wireless device may also include a transceiver module (i.e., transceiver), a counter module (i.e., counter), a processing module (i.e., processor), and/or a clock module (i.e., clock) or timer module (i.e., timer).
  • transceiver module i.e., transceiver
  • a counter module i.e., counter
  • a processing module i.e., processor
  • a clock module i.e., clock
  • timer module i.e., timer
  • selected components of the transceiver module can be located in a cloud radio access network (C-RAN).
  • C-RAN cloud radio access network
  • One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like.
  • API application programming interface
  • Such programs may be implemented in a high level procedural or object oriented programming language to communicate with a computer system.
  • the program(s) may be implemented in assembly or machine language, if desired.
  • the language may be a compiled or interpreted language, and combined with hardware implementations.
  • circuitry may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality.
  • ASIC Application Specific Integrated Circuit
  • the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
  • circuitry may include logic, at least partially operable in hardware.
  • modules may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components.
  • VLSI very-large-scale integration
  • a module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
  • Modules may also be implemented in software for execution by various types of processors.
  • An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module may not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.
  • a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices.
  • operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.
  • the modules may be passive or active, including agents operable to perform desired functions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention a trait à une technologie pour un équipement d'utilisateur (UE) pour réaliser une transmission de liaison montante à l'aide d'une TBS (taille de bloc de transport) réduite. L'UE peut décoder un ou plusieurs blocs de transport reçus en provenance d'un eNodeB dans un PDSCH (canal physique partagé de liaison descendante) dans une sous-trame n. L'UE peut sélectionner une ressource de PUCCH dans une sous-trame n+Dn sur la base d'une catégorie d'UE i et d'une TBS du PDSCH dans la sous-trame n, Dn étant un temps de traitement réduit. L'UE peut coder un renvoi d'acquittement (ACK) de demande de répétition automatique hybride (HARQ) pour une transmission à l'aide de la ressource de PUCCH sélectionnée dans la sous-trame n+Dn.
PCT/US2017/028928 2016-08-12 2017-04-21 Transmissions de liaison descendante avec des temps de traitement variables WO2018031083A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201662374648P 2016-08-12 2016-08-12
US62/374,648 2016-08-12
US201662375364P 2016-08-15 2016-08-15
US62/375,364 2016-08-15

Publications (1)

Publication Number Publication Date
WO2018031083A1 true WO2018031083A1 (fr) 2018-02-15

Family

ID=58664861

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/028928 WO2018031083A1 (fr) 2016-08-12 2017-04-21 Transmissions de liaison descendante avec des temps de traitement variables

Country Status (1)

Country Link
WO (1) WO2018031083A1 (fr)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020033884A1 (fr) * 2018-08-10 2020-02-13 Intel Corporation Améliorations de transmission de données et de commande de nouvelle radio (nr)
CN111726216A (zh) * 2018-03-06 2020-09-29 Oppo广东移动通信有限公司 一种应答信息处理方法、设备及存储介质
WO2020215288A1 (fr) * 2019-04-25 2020-10-29 北京小米移动软件有限公司 Procédé et appareil d'ordonnancement pour des blocs de transport, station de base, terminal et support de stockage
CN112673672A (zh) * 2018-07-06 2021-04-16 株式会社Ntt都科摩 用户终端以及无线通信方法
US11196512B2 (en) 2018-06-29 2021-12-07 Qualcomm Incorporated Resolving decodability for subsequent transmissions whose throughput exceeds a threshold
CN114600529A (zh) * 2020-09-04 2022-06-07 北京小米移动软件有限公司 Harq-ack反馈处理方法、装置、通信设备及存储介质
CN115412209A (zh) * 2018-10-09 2022-11-29 联发科技（新加坡）私人有限公司 用于移动通信中的系统信息重传的方法和装置
US11582735B2 (en) 2016-09-26 2023-02-14 Ofinno, Llc Wireless device capability for a physical uplink shared channel processing period

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130242729A1 (en) * 2012-03-16 2013-09-19 Qualcomm Incorporated Transport block size limitation for enhanced control channel operation in lte

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130242729A1 (en) * 2012-03-16 2013-09-19 Qualcomm Incorporated Transport block size limitation for enhanced control channel operation in lte

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Areas for latency reduction", vol. RAN WG2, no. Beijing, P.R. China; 20150824 - 20150828, 23 August 2015 (2015-08-23), XP051004201, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN2/Docs/> [retrieved on 20150823] *
LG ELECTRONICS: "System-level simulation results for TDD scenario with latency reduction", vol. RAN WG1, no. Nanjing, China; 20160523 - 20160527, 20 May 2016 (2016-05-20), XP051111626, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_85/Docs/> [retrieved on 20160520] *

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11582735B2 (en) 2016-09-26 2023-02-14 Ofinno, Llc Wireless device capability for a physical uplink shared channel processing period
US11910404B2 (en) 2016-09-26 2024-02-20 Ofinno, Llc Physical uplink shared channel processing period
CN111726216A (zh) * 2018-03-06 2020-09-29 Oppo广东移动通信有限公司 一种应答信息处理方法、设备及存储介质
US11695509B2 (en) 2018-06-29 2023-07-04 Qualcomm Incorporated Resolving decodability for subsequent transmissions whose throughput exceeds a threshold
US11196512B2 (en) 2018-06-29 2021-12-07 Qualcomm Incorporated Resolving decodability for subsequent transmissions whose throughput exceeds a threshold
CN112673672A (zh) * 2018-07-06 2021-04-16 株式会社Ntt都科摩 用户终端以及无线通信方法
CN112567662A (zh) * 2018-08-10 2021-03-26 苹果公司 用于新空口(nr)的数据和控制传输增强
WO2020033884A1 (fr) * 2018-08-10 2020-02-13 Intel Corporation Améliorations de transmission de données et de commande de nouvelle radio (nr)
US11985674B2 (en) 2018-08-10 2024-05-14 Apple Inc. Data and control transmission enhancements for new radio (NR)
CN115412209A (zh) * 2018-10-09 2022-11-29 联发科技（新加坡）私人有限公司 用于移动通信中的系统信息重传的方法和装置
CN115412209B (zh) * 2018-10-09 2024-06-07 联发科技（新加坡）私人有限公司 用于移动通信中的系统信息重传的方法和装置
WO2020215288A1 (fr) * 2019-04-25 2020-10-29 北京小米移动软件有限公司 Procédé et appareil d'ordonnancement pour des blocs de transport, station de base, terminal et support de stockage
CN114600529A (zh) * 2020-09-04 2022-06-07 北京小米移动软件有限公司 Harq-ack反馈处理方法、装置、通信设备及存储介质
CN114600529B (zh) * 2020-09-04 2023-08-29 北京小米移动软件有限公司 Harq-ack反馈处理方法、装置、通信设备及存储介质

Similar Documents

Publication Publication Date Title
US11006397B2 (en) Multiplexing physical uplink control channels in a slot for a new radio (NR) system
US11832267B2 (en) Uplink transmissions in preconfigured resources for enhanced machine type communication (EMTC) and narrow-band internet of things (NB-IOT)
US10461979B2 (en) Subframe structure for discrete Fourier transform (DFT) spread orthogonal frequency division multiplexing (S-OFDM) waveforms
US10595309B2 (en) Downlink control channel transmissions
US20240040598A1 (en) Downlink control channel signaling for improved power consumption at a user equipment (ue)
US11832262B2 (en) Uplink control information (UCI) multiplexing on multiple physical uplink shared channels (PUSCHs)
US20190239093A1 (en) Beam indication information transmission
US11140705B2 (en) Configuration of grant-less uplink transmissions for a user equipment
US20200137834A1 (en) Handling radio resource control (rrc) configured channels and signals with conflict direction
US11038652B2 (en) Concurrent transmission of acknowledgment and scheduling request information on a control channel
US20210219166A1 (en) Channel quality measurement reporting
US20200128579A1 (en) CHANNEL DESIGN FOR ENHANCED MACHINE TYPE COMMUNICATION IN AN UNLICENSED SPECTRUM (eMTC-U) SYSTEM
WO2020092264A1 (fr) Multiplexage d&#39;informations de commande de liaison montante (uci) pour système à multiples points de transmission et de réception (trp)
WO2018031083A1 (fr) Transmissions de liaison descendante avec des temps de traitement variables
WO2018144641A1 (fr) Segmentation de signalisation de commande de liaison descendante
US11825418B2 (en) Enhanced physical uplink control channel (PUCCH) power control
US20190239286A1 (en) Common and user equipment (ue)-specific physical uplink control channel (pucch) configuration
WO2018071853A1 (fr) Transmission de commande de liaison descendante améliorée pour une transmission de liaison montante autonome
US20240163717A1 (en) Latency management for integrated access and backhaul
EP3520263A1 (fr) Procédé d&#39;indication d&#39;un csi-rs apériodique pour une nouvelle radio
WO2020033888A1 (fr) Structure de transmission de signal de référence de sondage (srs)
US12040999B2 (en) Sounding reference signal (SRS) transmission framework

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17720999

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17720999

Country of ref document: EP

Kind code of ref document: A1