Techniques for transmitting physical uplink shared channel in uplink pilot time slots

Abstract

Techniques for wireless communications are described. A method for wireless communications at a user equipment (UE) includes identifying that a physical uplink shared channel (PUSCH) is to be transmitted in an uplink pilot time slot (UpPTS) of a subframe, determining whether to transmit uplink control information (UCI) on the PUSCH in the UpPTS, and transmitting the PUSCH in the UpPTS based at least in part on the determination. A method for wireless communications at a network access device includes determining whether to schedule transmission of UCI on the PUSCH in the UpPTS of a subframe, scheduling the PUSCH in the UpPTS based at least in part on the determination, and transmitting scheduling information for the PUSCH in the UpPTS to the UE.

Description

[0001] This application is a divisional application of the invention patent with application date of June 6, 2017, application number 201780040514.1, and invention name “Technology for transmitting physical uplink shared channel in uplink pilot time slot”.

[0002] Cross-references

[0003] This patent application claims priority to U.S. patent application No. 15 / 462,356, filed by Chen et al. on March 17, 2017, entitled “Techniques for Transmitting APhysical Uplink Shared Channel In An Uplink Pilot Time Slot”; and U.S. provisional patent application No. 62 / 357,843, filed by Chen et al. on July 1, 2016, entitled “Techniques for Transmitting A Physical Uplink Shared Channel In An Uplink Pilot Time Slot”; and U.S. provisional patent application No. 62 / 372,642, filed by Chen et al. on August 9, 2016, entitled “Techniques for Transmitting A Physical Uplink Shared Channel In An Uplink Pilot Time Slot”, each of which is assigned to the assignee of this application. Technical Field

[0004] The present disclosure relates, for example, to wireless communication systems, and more particularly, to techniques for transmitting a Physical Uplink Shared Channel (PUSCH) in an Uplink Pilot Time Slot (UpPTS), such as a six-symbol period UpPTS. Background Art

[0005] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be multiple-access systems capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, and orthogonal frequency division multiple access (OFDMA) systems.

[0006] As an example, a wireless multiple-access communication system may include multiple network access devices (e.g., base stations), each of which simultaneously supports communications for multiple communication devices, referred to as user equipment (UE). The base stations may communicate with the UEs on downlink channels (e.g., downlink, for transmissions from the base station to the UE) and uplink channels (e.g., uplink, for transmissions from the UE to the base station).

[0007] Some wireless communication systems may provide an UpPTS during a portion of a subframe. During the UpPTS, the UE may transmit a pilot signal (or reference signal) to the base station. Summary of the Invention

[0008] In some Long Term Evolution (LTE) and LTE-Advanced (LTE-A) networks, an Uplink Pilot Time Slot (UpPTS) of two symbol periods is provided in some subframes of some configurations of the Time Domain Duplex (TDD) radio frame structure. A user equipment (UE) can use the UpPTS of two symbol periods to transmit a pilot signal (or reference signal) to a base station. The UpPTS of two symbol periods can also be used by UEs performing a random access procedure. In some LTE / LTE-A networks, an UpPTS of six symbol periods may be provided in some subframes of some configurations of the TDD radio frame structure. The present disclosure describes techniques for transmitting a Physical Uplink Shared Channel (PUSCH) in the UpPTS.

[0009] In one example, a method for wireless communication at a UE is described. The method may include: identifying a PUSCH to be transmitted in an UpPTS of a subframe; determining whether to transmit uplink control information (UCI) on the PUSCH in the UpPTS; and transmitting the PUSCH in the UpPTS based at least in part on the determination.

[0010] In one example, an apparatus for wireless communication at a UE is described. The apparatus may include: means for identifying a PUSCH to be transmitted in an UpPTS of a subframe; means for determining whether to transmit UCI on the PUSCH in the UpPTS; and means for transmitting the PUSCH in the UpPTS based at least in part on the determination.

[0011] In one example, another apparatus for wireless communication at a UE is described. The apparatus may include a processor and a memory in electronic communication with the processor. The processor and the memory may be configured to: identify a PUSCH to be transmitted in an UpPTS of a subframe; determine whether to transmit UCI on the PUSCH in the UpPTS; and transmit the PUSCH in the UpPTS based at least in part on the determination.

[0012] In one example, a non-transitory computer-readable medium storing computer-executable code for wireless communication at a UE is described. The code is executable by a processor to: identify a PUSCH to be transmitted in an UpPTS of a subframe; determine whether to transmit UCI on the PUSCH in the UpPTS; and transmit the PUSCH in the UpPTS based at least in part on the determination.

[0013] Some examples of the above methods, apparatuses, and non-transitory computer-readable media may also include a process, feature, unit, instruction, or code for receiving scheduling information for a PUSCH in an UpPTS during a transmission time interval (TTI). The timing of the TTI may be based at least in part on a delay reduction capability of the UE. In some examples of the above methods, apparatuses, and non-transitory computer-readable media, the delay reduction capability of the UE may include at least one of: a scheduling timing reduction capability, a TTI duration reduction capability, or a combination thereof. In some examples of the above methods, apparatuses, and non-transitory computer-readable media, the timing of the TTI in which the scheduling information is received may include: a preamble boundary occurring at least two subframes before the UpPTS, or a preamble boundary occurring at least 2.5 subframes before the UpPTS.

[0014] Some examples of the above methods, apparatus, and non-transitory computer-readable media may also include processes, features, units, instructions, or codes for at least one of: separately managing uplink hybrid automatic repeat request (HARQ) for PUSCH in UpPTS and uplink HARQ for PUSCH transmission in uplink TTI, jointly managing uplink HARQ for PUSCH in UpPTS and uplink HARQ for PUSCH transmission in uplink TTI, asynchronously receiving uplink HARQ for PUSCH in UpPTS and uplink HARQ for PUSCH transmission in uplink TTI, or receiving acknowledgment for PUSCH in UpPTS in the same physical HARQ indicator channel (PHICH) resource set used to acknowledge PUSCH transmission in an uplink subframe.

[0015] Some examples of the above methods, apparatus, and non-transitory computer-readable media may also include a process, feature, unit, instruction, or code for determining whether an uplink TTI is scheduled for transmission on at least a first component carrier (CC) while a PUSCH in an UpPTS is transmitted on a second CC. Determining whether to transmit UCI on the PUSCH may be based at least in part on whether the uplink TTI is scheduled for transmission on at least the first CC.

[0016] Some examples of the above methods, apparatus, and non-transitory computer-readable media may also include processes, features, units, instructions, or codes for: when operating in carrier aggregation mode, determining that a PUSCH in an UpPTS is scheduled for transmission, and determining not to transmit at least one of the following based at least in part on determining that a PUSCH in an UpPTS is scheduled for transmission when operating in carrier aggregation mode: periodic channel state information (P-CSI) on a PUSCH in an UpPTS, aperiodic channel state information (A-CSI) on a PUSCH in an UpPTS, UCI on a PUSCH in an UpPTS, or a combination thereof.

[0017] Some examples of the above methods, apparatus, and non-transitory computer-readable media may also include a process, feature, unit, instruction, or code for: when operating in carrier aggregation mode, determining that a PUSCH in an UpPTS is scheduled for transmission, and at least in part based on determining that a PUSCH in an UpPTS is scheduled for transmission when operating in carrier aggregation mode, determining to transmit at least one of the following on a CC that does not carry the PUSCH in the UpPTS in parallel with the PUSCH in the UpPTS: P-CSI, A-CSI, UCI, or a combination thereof.

[0018] Some examples of the above methods, apparatus, and non-transitory computer-readable media may also include a process, feature, unit, instruction, or code for determining that a PUSCH in an UpPTS is scheduled for transmission when operating in a carrier aggregation mode, and selecting a CC for transmitting UCI based at least in part on a priority ranking of the CCs, wherein the priority ranking of the CCs causes the CC selection to deviate from the CC carrying the PUSCH in the UpPTS.

[0019] Some examples of the above methods, apparatus, and non-transitory computer-readable media may also include processes, features, units, instructions, or codes for determining whether the UE is configured for parallel physical uplink control channel (PUCCH) and PUSCH transmissions, and determining whether to transmit UCI on the PUSCH based at least in part on whether the UE is configured for parallel PUCCH and PUSCH transmissions.

[0020] Some examples of the above methods, apparatus, and non-transitory computer-readable media may also include processes, features, units, instructions, or code for: receiving downlink control information (DCI), and identifying an uplink grant for PUSCH in UpPTS received in the DCI based at least in part on: a state of an information field included in the DCI, masking of a control channel including the DCI using a predetermined cyclic redundancy check (CRC) mask, an association of the uplink grant with a predetermined decoding candidate, a size of the DCI, an identifier of a subframe in which the DCI is received, a DCI format, or a combination thereof.

[0021] Some examples of the above methods, apparatus, and non-transitory computer-readable media may also include processes, features, units, instructions, or codes for: receiving DCI, determining the size of the DCI, and identifying at least one decoding candidate for an uplink grant for a PUSCH in an UpPTS within the DCI, the at least one decoding candidate being based at least in part on the size of the DCI.

[0022] Some examples of the above methods, apparatuses, and non-transitory computer-readable media may also include a process, feature, unit, instruction, or code for identifying a first power control parameter for a TTI, and determining a second power control parameter for a PUSCH in an UpPTS based at least in part on the first power control parameter for the TTI. In some examples of the above methods, apparatuses, and non-transitory computer-readable media, the second power control parameter may be determined based at least in part on a semi-static relationship between the first power control parameter and the second power control parameter, or a variable structure of the PUSCH in the UpPTS.

[0023] Some examples of the above methods, apparatus, and non-transitory computer-readable media may also include a process, feature, unit, instruction, or code for: receiving scheduling information for a PUSCH in an UpPTS, wherein the scheduling information includes a first offset that is different from a second offset configured for at least one UCI type received for an uplink subframe.

[0024] Some examples of the above methods, apparatus, and computer-readable media may also include a process, feature, unit, instruction, or code for determining whether to enable at least one of the following based at least in part on the number of reference symbols to be transmitted in the UpPTS: frequency hopping during transmission of the PUSCH in the UpPTS, use of orthogonal cover codes (OCC) during transmission of the PUSCH in the UpPTS, or a combination thereof.

[0025] Some examples of the above methods, apparatus, and computer-readable media may also include processes, features, units, instructions, or codes for transmitting a random access preamble and receiving a random access response message for scheduling a PUSCH in an UpPTS in response to transmitting the random access preamble.

[0026] Some examples of the above methods, apparatus, and computer-readable media may also include processes, features, units, instructions, or codes for transmitting a demodulation reference signal (DM-RS) for the PUSCH in the UpPTS based at least in part on a DM-RS pattern that is different from a DM-RS pattern used for the PUSCH in the uplink subframe.

[0027] In one example, a method for wireless communication at a network access device is described. The method may include determining whether to schedule transmission of UCI on a PUSCH in an UpPTS of a subframe; scheduling the PUSCH in the UpPTS based at least in part on the determination; and transmitting scheduling information for the PUSCH in the UpPTS to a UE.

[0028] In one example, an apparatus for wireless communication at a network access device is described. The apparatus may include: means for determining whether to schedule transmission of UCI on a PUSCH in an UpPTS of a subframe; means for scheduling the PUSCH in the UpPTS based at least in part on the determination; and means for transmitting scheduling information for the PUSCH in the UpPTS to a UE.

[0029] In one example, another apparatus for wireless communication at a network access device is described. The apparatus may include a processor and a memory in electronic communication with the processor. The processor and the memory may be configured to: determine whether to schedule transmission of UCI on a PUSCH in an UpPTS of a subframe; schedule a PUSCH in the UpPTS based at least in part on the determination; and transmit scheduling information for the PUSCH in the UpPTS to a UE.

[0030] In one example, a non-transitory computer-readable medium storing computer-executable code for wireless communication at a network access device is described. The code is executable by a processor to: determine whether to schedule transmission of UCI on a PUSCH in an UpPTS of a subframe; schedule a PUSCH in the UpPTS based at least in part on the determination; and transmit scheduling information for the PUSCH in the UpPTS to a UE.

[0031] Some examples of the above methods, apparatuses, and non-transitory computer-readable media may also include a process, feature, unit, instruction, or code for selecting a timing of a TTI in which scheduling information is transmitted based at least in part on a delay reduction capability of the UE. In some examples of the above methods, apparatuses, and non-transitory computer-readable media, the delay reduction capability of the UE may include at least one of a scheduling timing reduction capability, a TTI duration reduction capability, or a combination thereof. In some examples of the above methods, apparatuses, and non-transitory computer-readable media, the timing of the TTI in which scheduling information is transmitted may include a preamble boundary occurring at least two subframes before an UpPTS, or a preamble boundary occurring at least 2.5 subframes before an UpPTS.

[0032] Some examples of the above methods, apparatus, and non-transitory computer-readable media may also include processes, features, units, instructions, or codes for at least one of: separately managing uplink HARQ for PUSCH in UpPTS and uplink HARQ for PUSCH transmission in an uplink TTI, jointly managing uplink HARQ for PUSCH in UpPTS and uplink HARQ for PUSCH transmission in an uplink TTI, asynchronously transmitting uplink HARQ for PUSCH in UpPTS and uplink HARQ for PUSCH transmission in an uplink TTI, or transmitting an acknowledgment for PUSCH in UpPTS in the same PHICH resource set used to acknowledge PUSCH transmission in an uplink subframe.

[0033] Some examples of the above methods, apparatus, and non-transitory computer-readable media may also include a process, feature, unit, instruction, or code for transmitting DCI to a UE and indicating in the DCI the presence of an uplink grant for a PUSCH in an UpPTS based at least in part on: a state of an information field included in the DCI, masking of a control channel including the DCI with a predetermined CRC mask, an association of the uplink grant with a predetermined decoding candidate, a size of the DCI, an identifier of a subframe in which the DCI is received, a DCI format, or a combination thereof.

[0034] Some examples of the above-mentioned methods, apparatus, and non-transitory computer-readable media may also include processes, features, units, instructions, or codes for: selecting a first offset for scheduling information, wherein the first offset is different from a second offset configured for at least one UCI type selected for an uplink subframe; and indicating the first offset in the scheduling information.

[0035] Some examples of the above methods, apparatuses, and non-transitory computer-readable media may also include procedures, features, units, instructions, or codes for: receiving a random access preamble, and scheduling a PUSCH in an UpPTS in response to receiving the random access preamble.

[0036] Some examples of the above methods, apparatus, and non-transitory computer-readable media may also include processes, features, units, instructions, or codes for: receiving a DM-RS for PUSCH in an UpPTS based at least in part on a DM-RS pattern that is different from a DM-RS pattern used for PUSCH in an uplink subframe.

[0037] The foregoing has been outlined rather broadly in order that the following detailed description of the techniques and technical advantages according to the examples of the present disclosure may be better understood. Additional techniques and advantages will be described below. The concepts and specific examples disclosed may be readily used as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent structures do not depart from the scope of the appended claims. The features of the concepts disclosed herein, their organization and method of operation, and related advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each of the figures is provided for the purpose of illustration and description and not as a definition of limitations of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] A further understanding of the nature and advantages of the present disclosure may be achieved by reference to the following drawings. In the drawings, similar components or features may be given the same reference numerals. In addition, multiple components of the same type may be distinguished by following the reference numeral with a dash and a second reference numeral that distinguishes the similar components. If only the first reference numeral is used in the specification, the description applies to any similar component having the same first reference numeral, regardless of the second reference numeral.

[0039] Figure 1 An example of a wireless communication system according to various aspects of the present disclosure is shown;

[0040] Figure 2 A set of time domain duplex (TDD) radio frame structures that may be supported by wireless communication devices (e.g., base stations and user equipment (UE)) of a wireless communication system according to various aspects of the present disclosure is shown;

[0041] Figure 3 A TDD radio frame structure is shown having a downlink-uplink (DL-UL) subframe configuration associated with a 5 ms switch point periodicity in accordance with various aspects of the present disclosure;

[0042] Figure 4A TDD radio frame structure is shown with a DL-UL subframe configuration associated with a 5 ms switch point periodicity in accordance with various aspects of the present disclosure;

[0043] Figure 5 illustrates a configuration of a subframe including multiple parallel component carriers (CCs) in accordance with various aspects of the present disclosure;

[0044] Figure 6 An alternative configuration of a subframe including an uplink pilot time slot (UpPTS) of six symbol periods is shown in accordance with various aspects of the present disclosure;

[0045] Figure 7 A block diagram illustrating an apparatus for wireless communication according to various aspects of the present disclosure is shown;

[0046] Figure 8 A block diagram of a wireless communication manager for wireless communication according to various aspects of the present disclosure is shown;

[0047] Figure 9 A block diagram illustrating an apparatus for wireless communication according to various aspects of the present disclosure is shown;

[0048] Figure 10 A block diagram of a wireless communication manager for wireless communication according to various aspects of the present disclosure is shown;

[0049] Figure 11 A block diagram illustrating a UE for wireless communication according to various aspects of the present disclosure is shown;

[0050] Figure 12 A block diagram of a base station (e.g., a base station forming part or all of an eNB) for wireless communication according to various aspects of the present disclosure is shown;

[0051] Figure 13 is a flow chart illustrating an example of a method for wireless communication at a UE according to various aspects of the present disclosure;

[0052] Figure 14 is a flow chart illustrating an example of a method for wireless communication at a UE according to various aspects of the present disclosure;

[0053] Figure 15 is a flow chart illustrating an example of a method for wireless communication at a network access device (eg, a base station) according to various aspects of the present disclosure; and

[0054] Figure 16 is a flow chart illustrating an example of a method for wireless communication at a network access device (eg, a base station) in accordance with various aspects of the present disclosure. DETAILED DESCRIPTION

[0055] Techniques are described for transmitting a physical uplink shared channel (PUSCH) by a user equipment (UE) using an uplink pilot time slot (UpPTS), such as an UpPTS of six symbol periods. Some techniques involve selecting timing (e.g., selecting a subframe or other transmission time interval (TTI)) for transmitting / receiving scheduling information for a PUSCH transmitted in the UpPTS. In some examples, selecting timing for transmitting / receiving scheduling information for a PUSCH in the UpPTS may be based at least in part on the capabilities of the UE. Some techniques involve determining whether to transmit uplink control information (UCI) on the PUSCH in the UpPTS. In some examples, determining whether to transmit UCI on the PUSCH in the UpPTS may be based at least in part on whether the UE is operating in carrier aggregation mode. Some techniques involve distinguishing uplink grants for a PUSCH in the UpPTS from uplink grants for other uplink transmissions (e.g., uplink transmissions in the next uplink TTI immediately following the PUSCH in the UpPTS).

[0056] The following description provides examples and is not intended to limit the scope, applicability, or examples set forth in the claims. The functions and arrangements of the elements discussed may be modified without departing from the scope of this disclosure. Various examples may omit, replace, or add various processes or components as appropriate. For example, the operations of the described methods may be performed in an order different from that described, and various operations may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined in other examples.

[0057] Figure 1 An example of a wireless communication system 100 according to various aspects of the present disclosure is shown. The wireless communication system 100 may include network access equipment (e.g., base stations 105), UEs 115, and a core network 130. The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The base stations 105 may interface with the core network 130 via a backhaul link 132 (e.g., S1, etc.) and may perform radio configuration and scheduling for communicating with the UEs 115, or may operate under the control of a base station controller (not shown). In various examples, the base stations 105 may communicate with each other directly or indirectly (e.g., through the core network 130) via a backhaul link 134 (e.g., X1, etc.), which may be a wired or wireless communication link.

[0058] Base stations 105 can wirelessly communicate with UEs 115 via one or more base station antennas. Each base station 105 site can provide communication coverage for a corresponding geographic coverage area 110. In some examples, base stations 105 can be referred to as base transceiver stations, radio base stations, access points, radio transceivers, NodeBs, eNodeBs (eNBs), Home NodeBs, Home eNodeBs, or some other suitable terminology. The geographic coverage area 110 of a base station 105 can be divided into sectors (not shown) that constitute a portion of the coverage area. The wireless communication system 100 can include different types of base stations 105 (e.g., macrocell base stations or small cell base stations). There can be overlapping geographic coverage areas 110 for different technologies.

[0059] In some examples, the wireless communication system 100 may include an LTE / LTE-A network. In an LTE / LTE-A network, the term evolved Node B (eNB) may be used to describe the base station 105, and the term UE may be used to describe the UE 115. The wireless communication system 100 may be a heterogeneous LTE / LTE-A network in which different types of eNBs provide coverage for various geographic areas. For example, each eNB or base station 105 may provide communication coverage for a macro cell, a small cell, or other type of cell. The term "cell" is a 3GPP term that may be used to describe a base station, a carrier or component carrier associated with a base station, or a coverage area (e.g., a sector, etc.) of a carrier or base station, depending on the context.

[0060] A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access to UEs that have subscribed to the network provider's services. Compared to a macro cell, a small cell may be a lower-power base station that may operate in the same or different (e.g., licensed, shared, etc.) radio spectrum band as the macro cell. According to various examples, a small cell may include a pico cell, a femto cell, and a micro cell. A pico cell may cover a relatively small geographic area and may allow unrestricted access to UEs that have subscribed to the network provider's services. A femto cell may additionally or alternatively cover a relatively small geographic area (e.g., a home) and may provide restricted access to UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs for users in a home, etc.). An eNB for a macro cell may be referred to as a macro eNB. An eNB for a small cell may be referred to as a small cell eNB, a pico eNB, a femto eNB, or a home eNB. An eNB may support one or more (e.g., two, three, four, etc.) cells (e.g., component carriers).

[0061] The wireless communication system 100 can support synchronous operation or asynchronous operation. For synchronous operation, the base stations can have similar frame timing, and transmissions from different base stations can be approximately aligned in time. For asynchronous operation, the base stations can have different frame timing, and transmissions from different base stations may not be aligned in time. The techniques described herein can be used for either synchronous or asynchronous operation.

[0062] A communication network that can adapt to some of the various disclosed examples can be a packet-based network operating according to a layered protocol stack. In the user plane, communications at the bearer or packet data convergence protocol (PDCP) layer can be IP-based. The radio link control (RLC) layer can perform packet segmentation and reassembly to communicate over logical channels. The media access control (MAC) layer can perform priority processing and multiplexing of logical channels to transport channels. The MAC layer can additionally or alternatively use hybrid ARQ (HARQ) to provide retransmission at the MAC layer to improve link efficiency. In the control plane, the radio resource control (RRC) protocol layer can provide the establishment, configuration, and maintenance of an RRC connection between the UE 115 and the base station 105 or the core network 130 to support radio bearers of user plane data. At the physical (PHY) layer, transport channels can be mapped to physical channels.

[0063] UEs 115 may be dispersed throughout the wireless communication system 100, and each UE 115 may be fixed or mobile. UE 115 may also include or be referred to by those skilled in the art as a mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term. UE 115 may also be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, etc. UEs may be capable of communicating with various types of base stations and network devices, including macro eNBs, small cell eNBs, relay base stations, etc.

[0064] The communication link 125 shown in the wireless communication system 100 may include a downlink (DL) from the base station 105 to the UE 115, or an uplink (UL) from the UE 115 to the base station 105. The downlink may also be referred to as a forward link, while the uplink may also be referred to as a reverse link.

[0065] In some examples, each communication link 125 may include one or more carriers, where each carrier may be a signal composed of multiple subcarriers (e.g., waveform signals of different frequencies) modulated according to the various radio technologies described above. Each modulated signal may be transmitted on a different subcarrier and may carry control information (e.g., reference signals, control channels, etc.), overhead information, user data, etc. The communication link 125 may transmit bidirectional communications using frequency domain duplex (FDD) operation (e.g., using paired spectrum resources) or TDD operation (e.g., using unpaired spectrum resources). A frame structure for FDD operation (e.g., frame structure type 1) and a frame structure for TDD operation (e.g., frame structure type 2) may be defined.

[0066] In some examples of the wireless communication system 100, the base station 105 or the UE 115 may include multiple antennas for employing an antenna diversity scheme to improve the communication quality and reliability between the base station 105 and the UE 115. Additionally or alternatively, the base station 105 or the UE 115 may employ multiple-input multiple-output (MIMO) technology, which can utilize a multipath environment to transmit multiple spatial layers carrying the same or different coded data.

[0067] The wireless communication system 100 may support operation on multiple cells or carriers, a feature that may be referred to as carrier aggregation (CA) or dual connectivity operation. A carrier may also be referred to as a component carrier (CC), layer, channel, etc. The terms "carrier," "component carrier," "cell," and "channel" are used interchangeably herein. Carrier aggregation may be used with both FDD and TDD component carriers.

[0068] In an LTE / LTE-A network, a UE 115 can be configured to communicate using up to five CCs when operating in carrier aggregation mode or dual connectivity mode. One or more of the CCs can be configured as DL CCs, and one or more of the CCs can be configured as UL CCs. In addition, one of the CCs assigned to the UE 115 can be configured as a primary CC (PCC), and the remaining CCs assigned to the UE 115 can be configured as secondary CCs (SCCs).

[0069] Figure 2 A set of TDD radio frame structures 200 that may be supported by wireless communication devices (eg, base stations and UEs) of a wireless communication system according to various aspects of the present disclosure is shown. In some examples, the wireless communication system may be a reference Figure 1 Examples of aspects of the wireless communication system 100 are described.

[0070] In some examples, the TDD radio frame structure may include a set of subframes (e.g., 10 subframes, numbered 0-9) configured according to different TDD DL-UL subframe configurations (e.g., 7 different TDD DL-UL subframe configurations, numbered 0-6). In some examples, the TDD DL-UL subframe configurations may include subsets of DL-UL subframe configurations associated with different switch point periodicities. For example, a first subset of DL-UL subframe configurations may be associated with a 5 millisecond (ms) switch point periodicity, and a second subset of DL-UL subframe configurations may be associated with a 10 ms switch point periodicity. Each DL-UL subframe configuration in the first subset of DL-UL subframe configurations may include multiple downlink (D) subframes, multiple uplink (U) subframes, and two special (S) subframes. Each DL-UL subframe configuration in the second subset of DL-UL subframe configurations may include multiple D subframes, multiple U subframes, and one S subframe. Each S subframe may provide a transition between downlink bursts (eg, one or more D subframes) and uplink bursts (eg, one or more U subframes).

[0071] Figure 3 A TDD radio frame structure 300 is shown with a DL-UL subframe configuration associated with a 5 ms switch point periodicity in accordance with various aspects of the present disclosure. In some examples, the DL-UL subframe configuration may be Figure 2 Examples of various aspects of DL-UL subframe configurations numbered 0, 1, 2, or 6 in FIG.

[0072] In some examples, the TDD radio frame structure 300 may include a first half-frame structure 305 followed by a second half-frame structure 310. Each of the first half-frame structure 305 and the second half-frame structure 310 may have a duration equal to half the duration of the TDD radio frame structure 300. In some examples, each of the first half-frame structure 305 and the second half-frame structure 310 may have the same structure and may include a subset of five subframes 315 (e.g., subframes 315 numbered 0, 1, 2, 3, and 4, or subframes 315 numbered 5, 6, 7, 8, and 9).

[0073] In some examples, each of the subframes 315 configured as a downlink subframe or an uplink subframe (e.g., subframes (SFs) 315 numbered 0, 2, 3, 4, 5, 7, 8, and 9) may include a first time slot 320 followed by a second time slot 325. Each of the first time slot 320 and the second time slot 325 may have a time slot duration equal to half the subframe duration. In some examples, each of the subframes 315 configured as a special subframe (e.g., subframes 315 numbered 2 and 6) may include a downlink pilot time slot (DwPTS) 330, a guard period (GP) 335, and an uplink pilot time slot (UpPTS) 340, wherein the guard period may provide a transition gap from downlink to uplink in TDD mode.

[0074] In some wireless communication systems, it is possible to dynamically adjust the DL-UL subframe configuration used by a wireless communication system (or a subset of devices of the wireless communication system (e.g., a base station and UE)) based at least in part on the DL-UL traffic demand of the wireless communication system. A wireless communication system that employs evolved interference management for traffic adjustment (eIMTA) may perform such adjustment. For example, if a large data burst on the downlink is required for a short duration, the TDD radio frame structure used for communication between a subset of wireless communication devices in the wireless communication system may be changed from Figure 2 The DL-UL subframe configuration numbered 1 in (with a 6:4 DL:UL ratio) is changed to Figure 2 5 (with a 9:1 DL:UL ratio). In some examples, the DL-UL subframe configuration used for communication can be adjusted to be no slower than 640ms and as fast as 10ms.

[0075] In some cases, the use of different DL-UL subframe configurations by different cells may cause inter-cell interference. For example, inter-cell interference may arise from the following: a first cell uses a first DL-UL subframe configuration including a D subframe in subframe number n, while a second cell uses a second DL-UL subframe configuration including a U subframe in subframe number n.

[0076] In some examples, the base station may provide a dynamic indication of the DL-UL subframe configuration employed. The dynamic indication may be provided via explicit layer signaling of the reconfiguration in the UE-group-common physical downlink control channel (PDCCH) or enhanced PDCCH (EPDCCH).

[0077] Adjusting the DL-UL subframe configuration based at least in part on traffic demand may increase the complexity of HARQ management. In some examples, HARQ management may be simplified by identifying one or more reference DL-UL subframe configurations for HARQ. For example, for UL HARQ, scheduling and HARQ timing may be based on the DL-UL subframe configuration indicated in a system information block (SIB) (e.g., the DL-UL subframe configuration indicated in SIB1). For DL ​​HARQ, scheduling and HARQ timing may be based on the reference DL-UL subframe configuration indicated for use by the UE (e.g., Figure 2 DL-UL subframe configuration numbered 2, 4 or 5 in ).

[0078] In a wireless communication system employing eIMTA, some subframes (e.g., some subframe numbers) may be subject to dynamic adjustment in the transmission direction, while other subframes may not be subject to dynamic adjustment in the transmission direction. For example, D subframes in the DL-UL subframe configuration indicated in SIB1 may not be subject to dynamic adjustment in the transmission direction, and U subframes in the DL-UL subframe configuration indicated for UE use for DL ​​HARQ may not be subject to dynamic adjustment in the transmission direction.

[0079] refer to Figure 3 The UpPTS 340 described can have different durations. In some examples, the UpPTS 340 can have a duration of one or two symbols (e.g., one or two orthogonal frequency division multiplexing (OFDM) symbol periods or single carrier frequency division multiplexing (SC-FDM) symbol periods). In these examples, the UpPTS 340 can be used to carry a shortened physical random access channel (PRACH) (e.g., LTE / LTE-A PRACH format 4) and / or a sounding reference signal (SRS), but no physical uplink control channel (PUCCH) transmissions or physical uplink shared channel (PUSCH) transmissions. In other examples, the UpPTS 340 can have a longer duration (e.g., a duration of six symbol periods (e.g., six symbol periods)). In these examples, the UpPTS 340 can provide more SRS transmission opportunities (e.g., for 3D-MIMO applications) or be used to carry PUSCH transmissions.

[0080] In some examples, the PUSCH to be transmitted in the UpPTS (i.e., PUSCH in UpPTS) may be scheduled separately from the UL transmission in the next immediately following UL subframe. Scheduling the PUSCH in the UpPTS separately from other UL transmissions may provide greater scheduling flexibility. However, in some examples, the timing of the transmission of scheduling information for the PUSCH in the UpPTS may be associated with the timing of the transmission of scheduling information for the UL transmission in the next immediately following UL subframe (e.g., the two sets of scheduling information may be transmitted during the same TTI or on the same channel). The transmission of scheduling information for both the PUSCH in the UpPTS and the UL transmission in the next immediately following UL subframe in the same TTI may reduce the lead time for the UE to prepare to transmit the PUSCH in the UpPTS (e.g., in a radio frame structure based on 1 ms subframes (or 1 ms TTI), when the duration of the PUSCH in the UpPTS is 0.5 ms, the lead time for the UE to prepare to transmit the PUSCH in the UpPTS may be reduced by 0.5 ms).

[0081] When the duration of an UpPTS in which a PUSCH is transmitted is less than a first duration of a first TTI associated with a first radio frame structure (e.g., less than the duration of an LTE / LTE-A subframe) and less than a second duration of a second TTI associated with a second radio frame structure (e.g., less than the duration of an ultra-low latency (ULL) TTI, or less than the duration of a slot of an LTE / LTE-A subframe), the timing of transmission of scheduling information for the PUSCH in the UpPTS may vary based on the UE's capability to operate according to the first radio frame structure or the second radio frame structure. The timing of transmission of scheduling information for the PUSCH in the UpPTS may also vary based on the UE's processing capability. In some examples, the timing of the TTI in which scheduling information for the PUSCH in the UpPTS is transmitted or received (e.g., the timing of the preamble boundary of the TTI) may be based at least in part on the UE's delay reduction capability. The delay reduction capability may include, for example, at least one of a scheduling timing reduction capability, a TTI duration reduction capability, or a combination thereof.

[0082] Figure 4 A TDD radio frame structure 400 is shown with a DL-UL subframe configuration associated with a 5 ms switch point periodicity in accordance with various aspects of the present disclosure. In some examples, the DL-UL subframe configuration may be Figure 2FIG2 illustrates an example of various aspects of a DL-UL subframe configuration numbered 2 in FIG2 . As shown, the DL-UL subframe configuration may include D subframes, U subframes, and S subframes. An uplink transmission (e.g., a PUSCH) may be scheduled to be transmitted in the UpPTS of each S subframe (e.g., an UpPTS of six symbol periods).

[0083] Uplink transmissions (e.g., PUSCH) in each U subframe may be scheduled based at least in part on an uplink grant transmitted in an earlier transmitted D subframe. PUSCH in the six-symbol period UpPTS in each S subframe may also be scheduled based at least in part on an uplink grant transmitted in an earlier transmitted subframe.

[0084] For LTE / LTE-A UEs without delay reduction capability (e.g., UEs without delay reduction capability, UEs without UL delay reduction capability, and / or UEs associated with n+4 scheduling timing (where scheduling information for a UL subframe is transmitted four subframes before UL SF n)), scheduling information for a PUSCH in an UpPTS in SF 6 may be transmitted / received during SF 3, such that the scheduling information for the PUSCH in the UpPTS is transmitted / received in a TTI having a preamble boundary occurring at least 3.5 subframes before the UpPTS in SF 6. Scheduling information for UL transmission in an immediately next UL subframe after the UpPTS (i.e., SF 7) may also be transmitted / received during SF 3, such that the scheduling information for UL transmission in the immediately next UL subframe after the UpPTS is transmitted / received in a TTI having a preamble boundary occurring at least four subframes before SF 7. In some examples, scheduling information for PUSCH in UpPTS may be transmitted in PDCCH in SF 3 instead of EPDCCH to provide LTE / LTE-A UEs with sufficient time to decode and process the scheduling information for PUSCH in UpPTS.

[0085] For LTE / LTE-A UEs with delay reduction capability (e.g., UEs with scheduling time reduction capability, such as n+3 scheduling timing reduction capability (where scheduling information for a UL subframe is transmitted three subframes before UL SF n)), scheduling information for a PUSCH in an UpPTS in SF 6 may be transmitted / received during SF 4, such that the scheduling information for the PUSCH in the UpPTS is transmitted / received in a TTI having a preamble boundary occurring at least 2.5 subframes before the UpPTS in SF 6. In some examples, scheduling information for UL transmission in an immediately next UL subframe after the UpPTS (i.e., SF 7) may also be transmitted / received during SF 4, such that the scheduling information for UL transmission in the immediately next UL subframe after the UpPTS is transmitted / received in a TTI having a preamble boundary occurring at least three subframes before SF 7. In some examples, scheduling information for PUSCH in UpPTS may be transmitted in PDCCH in SF 4 instead of EPDCCH to provide LTE / LTE-A UEs with sufficient time to decode and process the scheduling information for PUSCH in UpPTS. Alternatively, scheduling information for PUSCH in UpPTS in SF 6 and / or scheduling information for UL transmission in SF 7 may be transmitted / received in SF 3, similar to how scheduling information for LTE / LTE-A UEs without delay reduction capability is transmitted.

[0086] For ULL UEs with delay reduction capability (e.g., UEs with TTI duration reduction capability), scheduling information for PUSCH in UpPTS in SF 6 may be transmitted / received during the second time slot of SF 4, such that the scheduling information for PUSCH in UpPTS is transmitted / received in a TTI with a preamble boundary occurring at least 2 subframes (or 4 0.5ms ULL TTIs) before the UpPTS in SF 6. In some examples, the scheduling information for PUSCH in UpPTS may be transmitted in a PDCCH or EPDCCH in SF 4. Alternatively, scheduling information for PUSCH in UpPTS in SF 6 and / or scheduling information for UL transmissions in SF 7 may be transmitted / received in SF 3 or SF 4, similar to how scheduling information is transmitted for LTE / LTE-A UEs without delay reduction capability or LTE / LTE-A UEs with scheduling timing reduction capability.

[0087] Shortening the scheduling timing for PUSCH in UpPTS when operating in CA mode (e.g., shortening the time between transmitting / receiving scheduling information and the time for receiving / transmitting PUSCH in UpPTS) can cause UCI transmission issues related to CA. For example, a CC other than the CC carrying PUSCH in UpPTS may determine that UCI should be transmitted on PUSCH in UpPTS, and the time required for the UE to prepare UCI for transmission on PUSCH in UpPTS may be greater than the lead time provided by the scheduling timing. In some examples, this situation can be avoided by not allowing UCI to be transmitted on PUSCH in UpPTS and transmitting UCI on PUCCH or PUSCH carried by CCs other than the CC carrying PUSCH in UpPTS. Additionally or alternatively, the probability of UCI being transmitted on PUSCH in UpPTS can be reduced by shifting the selection of CC for carrying UCI away from the CC carrying PUSCH in UpPTS.

[0088] In some examples, HARQ for PUSCH in UpPTS may be managed jointly with HARQ for UL transmissions in UL subframes (e.g., when HARQ is used for transmissions in the same transport block, HARQ for PUSCH in UpPTS and HARQ for transmissions in UL subframes may be mixed). However, joint management may undesirably increase HARQ overhead in some subframes of some configurations of the TDD radio frame structure (e.g., for UL-multiple configurations). In some examples, HARQ for PUSCH in UpPTS may be managed separately from HARQ for UL transmissions in UL subframes (e.g., when HARQ is used for transmissions in the same transport block, HARQ for PUSCH in UpPTS and HARQ for transmissions in UL subframes may not be mixed). In some examples, HARQ for PUSCH in UpPTS and / or HARQ for UL transmissions in UL subframes may be transmitted / received asynchronously. In the case of such asynchronous HARQ operation, a HARQ process identity may be included in the control information used to schedule the PUSCH to indicate the HARQ process associated with the PUSCH transmission.

[0089] When scheduling information for a PUSCH in an UpPTS and scheduling information for an UL transmission in an UL subframe can be transmitted / received in the same TTI, the base station and the UE can use various methods to distinguish a first UL grant for a PUSCH in an UpPTS from a second UL grant for an UL transmission in an UL subframe in downlink control information (DCI). In some examples, the DCI including the first UL grant for the PUSCH can be associated with DCI format 0 or DCI format 4, and the second UL grant for an UL transmission in the UL subframe can be associated with a format (denoted as DCI format 0' or DCI format 4' for convenience).

[0090] In some examples, a UL grant for a PUSCH in an UpPTS (e.g., as distinguished from a UL grant for an UL transmission in an UL subframe) can be identified by one or more of: a state of an information field included in the DCI, masking of a control channel including the DCI with a predetermined cyclic redundancy check (CRC) mask, an association of the UL grant with a predetermined decoding candidate, a size of the DCI containing the UL grant, an identifier of a subframe in which the DCI containing the UL grant is received, a DCI format, or a combination thereof.

[0091] In examples where a UL grant for a PUSCH in an UpPTS is identified based at least in part on a state of an information field included in a DCI, the information field may include, for example, a UL index or a DL allocation index (DAI). In some examples, a UL index of 00 may identify a UL grant for a PUSCH in an UpPTS. For example, a UL index of 00 may be applicable to Figure 2 In some examples, a DAI not used for a specific TDD DL-UL subframe configuration may be used to identify an UL grant for PUSCH in UpPTS (e.g., for Figure 2 For TDD DL-UL subframe configuration 6 in LTE, without FDD / TDD CA, or without differently configured TDD, DAI=1 or DAI=4 may be used, and DAI=2 and DAI=3 may not be used).

[0092] In an example where the UL grant for the PUSCH in the UpPTS is identified based at least in part on masking (or unmasking) a control channel including DCI (including the UL grant) with a predetermined CRC mask, the UL grant may be transmitted according to DCI format 0' or DCI format 4' and scrambled by a CRC mask of 0000 0000 0000 0001. When CRC masking is used to identify the UL grant for the PUSCH in the UpPTS, indication regarding antenna switching based on the CRC masking may be suppressed or may be performed using a CRC mask different from the CRC masking used to identify the UL grant for the PUSCH in the UpPTS.

[0093] In an example where a UL grant for a PUSCH in an UpPTS is identified based at least in part on its association with a predetermined decoding candidate (e.g., a decoding candidate having a predetermined length and starting from a predetermined resource element (RE)), the UL grant may be transmitted based on a single predetermined decoding candidate, or may be transmitted based on a decoding candidate selected from a plurality of predetermined decoding candidates allocated for transmission of a UL grant for a PUSCH in an UpPTS. Other predetermined decoding candidates may be allocated for transmission of a UL grant for an UL transmission in an UL subframe.

[0094] In an example where an UL grant for a PUSCH in an UpPTS is identified based at least in part on the size of the DCI containing the UL grant, DCI format 0 and DCI format 0' may be distinguished by increasing or decreasing the size of one of DCI format 0 and DCI format 0' (e.g., by expanding or contracting one or more existing information fields), and DCI format 4 and DCI format 4' may be distinguished by increasing or decreasing the size of one of DCI format 4 and DCI format 4'. In some examples, the size of a DCI format may be increased or decreased to match the size of another DCI format (e.g., the size of DCI format 1A may be increased or decreased to match the size of a DCI format 0 that has been increased or decreased in size). Increasing or decreasing the size of a DCI format compared to the size of another DCI format may be combined with limiting the number of decoding candidates associated with one or more resource aggregation levels in order to limit the number of blind decodes that a UE may have to perform.

[0095] In an example where a UL grant for a PUSCH in an UpPTS is identified based at least in part on an identifier of a subframe in which a DCI containing the UL grant is received, the UL grant for the PUSCH in the UpPTS may be transmitted according to DCI format 0 or DCI format 4 in a first TTI associated with a first identifier, and the UL grant for an UL transmission in an UL subframe may be transmitted according to DCI format 0' or DCI format 4' in a second TTI associated with a second identifier. However, for example, Figure 2 For TDD DL-UL subframe configurations 0 or 6 in UpPTS, a different method may have to be used to identify the UL grant for PUSCH in UpPTS because the number of subframes available for PUSCH transmission exceeds the number of subframes available for carrying UL grants.

[0096] In an example where a UL grant for a PUSCH in an UpPTS is identified based at least in part on a DCI format associated with the UL grant, the set of DCI formats that can be used for transmission of the UL grant can be limited. For example, DCI format 0' can be used or DCI format 4' can be used, but the base station may not be allowed to select a DCI format from a DCI format set that includes both DCI format 0' and DCI format 4'.

[0097] In some examples, techniques for distinguishing UL grants for PUSCH in UpPTS from UL grants for UL transmissions in UL subframes may be used for TTIs in which both types of UL grants are transmitted (or intended to be transmitted), but not for other TTIs.

[0098] In some examples, the power control parameter for the PUSCH in the UpPTS can be based at least in part on the power control parameter for the TTI. For example, the power control parameter for the PUSCH in the UpPTS can be based at least in part on a semi-static relationship (e.g., an offset) between a first power control parameter for the TTI and a second power control parameter for the PUSCH in the UpPTS (e.g., the second control parameter can be based at least in part on the value of the first power control parameter, multiplied by the ratio of the fixed duration of the PUSCH in the UpPTS to the fixed duration of the TTI). As another example, the power control parameter for the PUSCH in the UpPTS can be based at least in part on the variable structure of the PUSCH in the UpPTS (e.g., the second control parameter for the PUSCH in the UpPTS can be based at least in part on the value of the first power control parameter for UL transmissions in a UL subframe, multiplied by the ratio of the duration of the PUSCH in the UpPTS to the duration of the TTI).

[0099] Examples of UCI include periodic channel state information (P-CSI), aperiodic channel state information (A-CSI), scheduling request (SR), and acknowledgement / negative acknowledgement (ACK / NAK) data. With respect to PUSCH in UpPTS, P-CSI to be transmitted on PUSCH in UpPTS may come from the CC carrying PUSCH in UpPTS and, when operating in CA mode, from other CCs. Similarly, A-CSI to be transmitted on PUSCH in UpPTS may come from the CC carrying PUSCH in UpPTS and, when operating in CA mode, from other CCs. In some examples, SR may not be transmitted on the CC carrying PUSCH in UpPTS but may be transmitted on a PCC that is not the CC carrying PUSCH in UpPTS. ACK / NAK data may not be transmitted on PUSCH in UpPTS when DL HARQ timing remains unchanged regardless of whether PUSCH can be transmitted in UpPTS.

[0100] In some examples, transmission of UCI (e.g., P-CSI and A-CSI) on the PUSCH in the UpPTS may be supported (or allowed) regardless of whether CCs other than the CC carrying the PUSCH in the UpPTS are available for carrying the UCI. In other examples, transmission of UCI (e.g., P-CSI and A-CSI) on the PUSCH in the UpPTS may not be supported (or allowed) when CCs other than the CC carrying the PUSCH in the UpPTS are available for carrying the UCI (e.g., when an uplink TTI is scheduled for transmission on at least a first CC and the PUSCH in the UpPTS is transmitted on a second CC, as is the case when operating in CA mode).

[0101] In some examples, whether transmission of UCI (e.g., P-CSI and A-CSI) on the PUSCH in the UpPTS is supported may depend on whether the UE is configured for parallel PUCCH and PUSCH transmission. If the UE is not configured for parallel PUCCH and PUSCH transmission, and if the PUSCH in the UpPTS is the only PUSCH transmission on two or more CCs in a group configured for carrier aggregation or dual connectivity for the UE, the PUSCH may be dropped and the UCI may be transmitted on the PUCCH channel. That is, the UE may skip the transmission of the only PUSCH in the group when there is also UCI that should be transmitted. In this case, the PUSCH scheduled in the UpPTS may be considered an error case. Alternatively, if the PUSCH in the UpPTS is the only PUSCH transmission in a group across two or more CCs configured for carrier aggregation or dual connectivity for the UE, the UCI may be included as part of the PUSCH in the UpPTS instead of being transmitted on the PUCCH channel to avoid parallel PUCCH and PUSCH transmission. If the UE is configured with parallel PUCCH and PUSCH transmission, the PUSCH in the UpPTS may or may not participate in UCI transmission. If the PUSCH in the UpPTS is not used to transmit UCI, the PUCCH channel can be transmitted together with the PUSCH in the UpPTS, resulting in parallel PUCCH and PUSCH transmission. If the PUSCH in the UpPTS participates in transmitting UCI, the PUSCH in the UpPTS can transmit one or more UCI, such as periodic CSI (if it should be transmitted).

[0102] In some examples, the demodulation reference signal (DM-RS) for PUSCH in UpPTS can follow the legacy DM-RS, as in regular UL subframes. Alternatively, the DM-RS pattern for PUSCH in UpPTS can use a different pattern. As an example, the DM-RS pattern can use a pattern similar to SRS, where comb levels 2 or 4 can be used. This can allow the DM-RS for PUSCH in UpPTS to be more efficiently multiplexed with the SRS in UpPTS.

[0103] In some examples, a physical HARQ indicator channel (PHICH) for non-adaptive retransmission of PUSCH in UpPTS can be located in a downlink subframe, where the same set of PHICH resources can be used to confirm PUSCH transmissions in one or more UL subframes. In order to distinguish the PHICH resources used for PUSCH in UpPTS and PUSCH in UL subframes, in addition to other parameters used for PHICH resource derivation (e.g., starting PRB index of PUSCH, DM-RS cyclic shift of PUSCH, etc.), an additional offset can be introduced for determining the PHICH resources corresponding to PUSCH in UpPTS.

[0104] Figure 5 A configuration of a subframe 500 including multiple parallel CCs according to various aspects of the present disclosure is shown. As an example, the CCs may include a first CC 505, a second CC 510, and a third CC 515. Depending on the FDD transmission mode between the first CC 505 and the second CC 510, the first CC 505 may be configured for downlink use, and the second CC 510 may be configured for uplink use. Depending on the TDD transmission mode on the third CC 515, the third CC 515 may be configured with a DwPTS 520, followed by a GP 525, followed by an UpPTS 530. The PUSCH may be transmitted in the UpPTS 530.

[0105] In some examples, transmission of P-CSI, A-CSI, or other UCI on the PUSCH in the UpPTS 530 may not be supported. Therefore, the PUSCH in the UpPTS 530 (or the third CC 515) may not be included in the prioritization of PUSCHs or PUCCHs (or CCs) from which the PUSCHs or PUCCHs (or CCs) may be selected for carrying UCI. Figure 5 In the UpPTS 530, P-CSI, A-CSI, or other UCI may be transmitted on a PUSCH or PUCCH transmitted on a second CC 510. In some examples, when P-CSI is transmitted on another CC and the UE is not configured for parallel PUCCH and / or PUSCH transmission, PUSCH in the UpPTS 530 may not be transmitted.

[0106] In some examples, transmission of P-CSI, A-CSI, or other UCI can be supported on the PUSCH in the UpPTS 530. In these examples, the PUSCH in the UpPTS 530 (or the third CC 515) can be included in the priority ranking of the PUSCH or PUCCH (or CC) from which the PUSCH or PUCCH (or CC) can be selected for carrying UCI, and transmission of P-CSI, A-CSI, or other UCI can be performed on the PUSCH in the UpPTS 530. In some examples, the PUSCH in the UpPTS 530 (or the third CC 515) can be assigned a lower cell index or a lower priority in the priority ranking of the PUSCH or PUCCH (or CC), which can reduce the probability that the PUSCH in the UpPTS 530 (or the third CC 515) is selected to carry UCI when the PUSCH or PUCCH (or other CC, such as the second CC 510) is assigned a higher cell index or a higher priority and can be used to carry UCI. When selecting PUSCH or PUCCH (or CC) to carry UCI, criteria other than cell index or priority may be used in addition or alternatively.

[0107] When the transmission of P-CSI, A-CSI, or other UCI on the PUSCH in the UpPTS 530 is supported (or allowed), a first set of offsets may be configured for transmitting the P-CSI, A-CSI, or other UCI on the PUSCH in the UpPTS 530. The first set of offsets may be different from a second set of offsets configured for at least one UCI type in the uplink subframe. The first set of offsets may determine the amount of resources allocated for each UCI type that may be transmitted on the PUSCH in the UpPTS 530. In some examples, the offsets may be RRC-configured offsets (e.g., beta_offset). The offsets may include offsets for ACK / NAK data, channel quality indicator (CQI) / precoding matrix indicator (PMI), rank indicator (RI) / precoding type indicator (PTI), and the like. In some examples, each offset may identify the number of REs allocated for a UCI type. The first set of offsets may be configured differently from the second set of offsets because the PUSCH in the UpPTS 530 may have a different amount of resources than the PUSCH in the uplink subframe. Some or all UCI types may be associated with two offsets. As an example, ACK / NAK and RI / PTI may be associated with two offsets—one for the UL subframe and another for the UpPTS, while CQI may be associated with a single offset applicable to both the UL subframe and the UpPTS. As another example, all UCI types may be associated with two offsets—one for the UL subframe and another for the UpPTS.

[0108] Figure 6 An alternative configuration of a subframe 600 including a six-symbol period UpPTS is shown in accordance with various aspects of the present disclosure. In some examples, the subframe 600 may be a reference Figure 2 Examples of aspects of one of the S subframes included in one of the DL-UL subframe configurations are described. Subframe 600 may include a first slot 605 (slot 0) followed by a second slot 610 (slot 1). Subframe 600 may include a DwPTS 615 of six symbol periods within the first slot 605, followed by a two-symbol GP 620 spanning the first slot 605 and the second slot 610, followed by an UpPTS 625 of six symbol periods within the second slot 610. A PUSCH may be transmitted in the UpPTS 625 of six symbol periods. In some examples, subframe 600 may have a duration of 1 ms.

[0109] In some examples, a subset of the modulation symbols of the nominal PUSCH configuration for the slot may be mapped to the six-symbol period UpPTS 625. In some examples, the subset of the modulation symbols of the nominal PUSCH configuration for the slot may include: a temporally last subset of the modulation symbols of the nominal PUSCH configuration for the slot (e.g., the first symbol of the nominal PUSCH configuration of seven symbols for the slot may not be mapped to the six-symbol period UpPTS 625, resulting in a DDRDDD symbol pattern being transmitted during the six-symbol period UpPTS 625, as shown in Alternative 1 630), or a temporally first subset of the modulation symbols of the nominal PUSCH configuration for the slot (e.g., the last symbol of the nominal PUSCH configuration of seven symbols for the slot may not be transmitted during the six-symbol period UpPTS 625, resulting in a DDDRDD symbol pattern being transmitted during the six-symbol period UpPTS 625, as shown in Alternative 2 635). The D symbol is the PUSCH data symbol, and the R symbol is the demodulation reference signal transmission.

[0110] In some examples, a pattern of modulation symbols other than a subset of the modulation symbols of the nominal PUSCH configuration for the slot may be mapped to the six-symbol period of the UpPTS 625 . For example, the demodulation reference signal transmission (R symbol) may be mapped to the third symbol period in time of the six-symbol period UpPTS 625, and the PUSCH data symbol (D symbol) may be mapped to at least some of the other symbol periods in the six-symbol period UpPTS 625, as shown in alternative 1 630. Alternatively, the demodulation reference signal transmission may be mapped to the fourth symbol period in time of the six-symbol period UpPTS 625, and the PUSCH data symbol may be mapped to at least some of the other symbol periods in the six-symbol period UpPTS 625, as shown in alternative 2 635. Alternatively, the demodulation reference signal transmission may be mapped to the second symbol period in time and the fifth symbol period in time of the six-symbol period UpPTS 625, and the PUSCH data symbol may be mapped to at least some of the other symbol periods in the six-symbol period UpPTS 625, as shown in alternative 3. Alternatively, the demodulation reference signal may be mapped to two symbol periods in the six-symbol period UpPTS 625, and the PUSCH data symbols may be mapped to at least some of the other symbol periods in the six-symbol period UpPTS 625, as shown in Alternative 3 640. Alternatively, the demodulation reference signal may be mapped to at least the first symbol period in time of the six-symbol period UpPTS 625, and the PUSCH data symbols may be mapped to at least some of the other symbol periods in the six-symbol period UpPTS 625 (not shown). The configuration of mapping the demodulation reference signal to at least two symbol periods in the six-symbol period UpPTS 625 is useful because other LTE / LTE-A PUSCH transmissions are transmitted in the two time slots of the subframe, with one demodulation reference signal transmitted in each time slot. Additionally or alternatively, the use of some orthogonal cover codes (OCCs) in MIMO transmissions may require that a demodulation reference signal be transmitted during each of the two symbol periods.

[0111] In some examples, a PUSCH may be transmitted during the UpPTS 625 of six symbol periods using one of a plurality of alternative data structures and demodulation reference signal structures (e.g., one of the data structures and demodulation reference signal structures associated with Alternative 1 630, Alternative 2 635, or Alternative 3 640), and a network access device (e.g., a base station) may transmit an indication of the data structure and demodulation reference signal structure that the UE should use. The indication of the data structure and demodulation reference signal structure may include, for example, at least one of the following: an RRC configuration, or a dynamic indication in downlink control information (DCI), or a DCI format, or a combination thereof. In some examples, the dynamic indication in the DCI may be implicit. For example, when the DCI indicates single-input multiple-output (SIMO) operation, the use of Alternative 1 630 may be implicitly indicated, or when the DCI indicates MIMO operation, the use of Alternative 3 640 may be implicitly indicated.

[0112] In some examples, frequency hopping during transmission of the PUSCH in the UpPTS can be enabled (or disabled) based at least in part on the number of reference symbols to be transmitted in the UpPTS. Figure 6 Frequency hopping may not be enabled in the UpPTS 625 of a six-symbol period that includes only one demodulation reference symbol transmission (e.g., for Alternative 1 630 or Alternative 2 635, the frequency hopping enable bit may be set to a frequency hopping disabled state, or may not be transmitted). However, frequency hopping may be enabled in the UpPTS 625 of a six-symbol period that includes two or more demodulation reference symbol transmissions (e.g., for Alternative 3 640, the frequency hopping enable bit may be set or not set to a frequency hopping enabled state, or may be transmitted).

[0113] In some examples, multi-cluster resource allocation may or may not be supported for PUSCH in UpPTS (e.g., for Figure 6 Any of Alternative 1 630, Alternative 2 635, or Alternative 3 640 may or may not support multi-cluster resource allocation).

[0114] In some examples, the use of cyclic shifts or OCC indices during transmission of the PUSCH in the UpPTS can be enabled (or disabled) based at least in part on the number of reference symbols to be transmitted in the UpPTS. Referring to Figure 6, the use of cyclic shifts or OCC indices may not be enabled in an UpPTS 625 that includes only one demodulation reference symbol transmission for a six-symbol period (e.g., for Alternative 1 630 or Alternative 2 635). However, the use of cyclic shifts or OCC indices may be enabled in an UpPTS 625 that includes two or more demodulation reference symbol transmissions for a six-symbol period (e.g., for Alternative 3 640).

[0115] In response to receiving a random access preamble from the UE (e.g., message 1 of the random access procedure), the network access device may schedule or not schedule the PUSCH in the UpPTS. When the PUSCH in the UpPTS is scheduled in response to receiving a random access preamble from the UE, scheduling information for the PUSCH in the UpPTS may be transmitted to the UE in a random access response message (e.g., message 3 of the random access procedure).

[0116] Figure 7 A block diagram 700 of an apparatus 715 for wireless communication according to various aspects of the present disclosure is shown. The apparatus 715 may be a reference Figure 1 Examples of various aspects of one or more of the described UEs 115. The apparatus 715 may also be or include a processor. The apparatus 715 may include a receiver 710, a wireless communication manager 720, or a transmitter 730. Each of these components may be in communication with each other.

[0117] The components of device 715 can be implemented individually or collectively using one or more application-specific integrated circuits (ASICs) adapted to perform some or all of the applicable functions in hardware. Alternatively, the functions can be performed by one or more other processing units (or cores) on one or more integrated circuits. In other examples, other types of integrated circuits (e.g., structured / platform ASICs, field programmable gate arrays (FPGAs), systems on chips (SoCs), and / or other types of semi-custom ICs) can be used, which can be programmed in any manner known in the art. The functions of each component can be implemented in whole or in part using instructions contained in a memory formatted to be executed by one or more general-purpose or application-specific processors.

[0118] In some examples, receiver 710 may include at least one radio frequency (RF) receiver, such as at least one RF receiver operable to receive transmissions over at least one radio spectrum band. In some examples, one or more of the at least one radio spectrum band may be used for LTE / LTE-A communications, such as, for example, as described with reference to Figure 1 、 2 , 3, 4, 5 or 6. The receiver 710 may be used to communicate with one or more communication links of a wireless communication system (e.g., Figure 1 The wireless communication system 100 may be configured to receive various types of data or control signals (ie, transmissions) from one or more communication links of the depicted wireless communication system 100.

[0119] In some examples, transmitter 730 may include at least one RF transmitter, such as at least one RF transmitter operable to transmit over at least one radio spectrum band. Transmitter 730 may be used to transmit over one or more communication links of a wireless communication system (e.g., reference Figure 1 One or more communication links of the described wireless communication system 100 transmit various types of data or control signals (ie, transmissions).

[0120] In some examples, wireless communication manager 720 can be used to manage one or more aspects of wireless communications of device 715. In some examples, portions of wireless communication manager 720 can be incorporated into or shared with receiver 710 or transmitter 730. In some examples, wireless communication manager 720 can include a PUSCH identifier 735, a UCI manager 740, or a PUSCH transmission manager 745.

[0121] A PUSCH identifier 735 may be configured to identify a PUSCH to be transmitted in the UpPTS of a subframe. A UCI manager 740 may be configured to determine whether to transmit UCI on the PUSCH in the UpPTS. A PUSCH transmission manager 745 may be configured to transmit the PUSCH in the UpPTS based at least in part on the determination made by the UCI manager 740.

[0122] Figure 8 A block diagram 800 illustrates a wireless communication manager 820 for wireless communication according to various aspects of the present disclosure. The wireless communication manager 820 may be a reference Figure 7 Examples of aspects of wireless communication manager 720 are described.

[0123] The components of wireless communication manager 820 may be implemented individually or collectively using one or more ASICs adapted to perform some or all applicable functions in hardware. Alternatively, the functions may be performed by one or more other processing units (or cores) on one or more integrated circuits. In other examples, other types of integrated circuits (e.g., structured / platform ASICs, FPGAs, SoCs, and / or other types of semi-custom ICs) may be used, which may be programmed in any manner known in the art. The functionality of each component may be implemented in whole or in part using instructions contained in memory formatted to be executed by one or more general-purpose or application-specific processors.

[0124] In some examples, the wireless communication manager 820 can be used to manage UEs or devices (e.g., Figure 1 One of the UEs 115 described or referenced Figure 7 In some examples, a portion of the wireless communication manager 820 may be incorporated into a receiver or transmitter (e.g., a reference to FIG. Figure 7 Receiver 710 or transmitter 730 described herein) or with a receiver or transmitter (e.g., reference Figure 7 70). In some examples, the wireless communication manager 820 may include an optional random access manager 850, an optional carrier aggregation manager 855, a PUSCH identifier 835, a UCI manager 840, a PUSCH transmission manager 845, or a HARQ manager 875. The PUSCH identifier may include a PUSCH scheduling manager 860. The UCI manager 840 may include an optional UCI CC selector 865. The PUSCH transmission manager 845 may include a power controller 870.

[0125] Under some conditions, the random access manager 850 may be used to transmit a random access preamble.

[0126] The PUSCH identifier 835 may be used to identify the PUSCH to be transmitted in the UpPTS of a subframe.

[0127] The PUSCH scheduling manager 860 may be configured to receive scheduling information for a PUSCH in an UpPTS during a TTI. The timing of the TTI may be based at least in part on the delay reduction capabilities of the UE including the wireless communication manager 820. In some examples, the delay reduction capabilities of the UE may include at least one of: a scheduling timing reduction capability, a TTI duration reduction capability, or a combination thereof. In some examples, the timing of the TTI in which the scheduling information is received may include: a preamble boundary occurring at least two subframes prior to the UpPTS, or a preamble boundary occurring at least 2.5 subframes prior to the UpPTS. In some examples, the scheduling information may include a first offset that is different from a second offset configured for at least one UCI type received for an uplink subframe. In some examples, some or all of the scheduling information may be received in DCI or RRC signaling. In some examples, the PUSCH scheduling manager 860 may receive a random access response message for scheduling a PUSCH in the UpPTS. The random access response message may be received in response to the random access manager 850 transmitting a random access preamble.

[0128] In some examples, the PUSCH scheduling manager 860 can be configured to receive DCI. The DCI can be received as part of the received scheduling information. In some examples, the PUSCH scheduling manager 860 can identify an uplink grant for PUSCH in the UpPTS received in the DCI based at least in part on: a state of an information field included in the DCI, masking of a control channel including the DCI using a predetermined CRC mask, an association of the uplink grant with a predetermined decoding candidate, a size of the DCI, an identifier of a subframe in which the DCI is received, a DCI format, or a combination thereof. In some examples, the PUSCH scheduling manager 860 can determine the size of the DCI. In some examples, the PUSCH scheduling manager 860 can identify at least one decoding candidate within the DCI for the uplink grant for PUSCH in the UpPTS. The at least one decoding candidate is based at least in part on the size of the DCI.

[0129] The carrier aggregation manager 855 may be configured to determine whether an uplink TTI is scheduled for transmission on at least a first CC while a PUSCH in an UpPTS is transmitted on a second CC. Additionally or alternatively, the carrier aggregation manager 855 may be configured to determine whether a PUSCH in an UpPTS is scheduled for transmission when operating in carrier aggregation mode.

[0130] The UCI manager 840 may be configured to determine whether to transmit UCI on the PUSCH in the UpPTS. In some examples, the determination made by the UCI manager 840 may be based at least in part on one of the determinations made by the carrier aggregation manager 855. For example, when the carrier aggregation manager 855 determines that an uplink TTI is scheduled for transmission on at least the first CC, the UCI manager 840 may determine to transmit UCI on the PUSCH in the UpPTS. In some examples, the determination made by the UCI manager 840 may be based at least in part on a determination that the PUSCH in the UpPTS is scheduled for transmission when operating in carrier aggregation mode. For example, when operating in carrier aggregation mode, the UCI manager 840 may determine not to transmit at least one of periodic CSI, aperiodic CSI, UCI, or a combination thereof on the PUSCH in the UpPTS. When operating in carrier aggregation mode, the determination made by the UCI manager 840 may additionally or alternatively include determining to transmit at least one of: periodic CSI, aperiodic CSI, UCI, or a combination thereof, on a CC that does not carry the PUSCH in the UpPTS in parallel with the PUSCH in the UpPTS. Alternatively, when operating in carrier aggregation mode, the UCI manager 840 may determine to transmit at least one of periodic CSI, aperiodic CSI, UCI, or a combination thereof, on the PUSCH in the UpPTS.

[0131] A UCI CC selector 865 may be used to select a CC for transmitting UCI. In some examples, a CC may be selected based at least in part on a priority ranking of the CCs that biases selection of the CCs away from CCs carrying PUSCH in an UpPTS.

[0132] The power controller 870 may be configured to identify a first power control parameter for a TTI and determine a second power control parameter for a PUSCH in an UpPTS based at least in part on the first power control parameter for the TTI. In some examples, the second power control parameter may be determined based at least in part on a semi-static relationship between the first power control parameter and the second power control parameter, or based at least in part on a variable structure of the PUSCH in the UpPTS.

[0133] The PUSCH transmission manager 845 may be configured to transmit the PUSCH in the UpPTS based at least in part on the determination made by the UCI manager 840. In some examples, the PUSCH transmission manager 845 may additionally or alternatively be configured to determine, based at least in part on the number of reference symbols to be transmitted in the UpPTS, whether to enable at least one of: frequency hopping during transmission of the PUSCH in the UpPTS, use of an OCC during transmission of the PUSCH in the UpPTS, or a combination thereof.

[0134] The HARQ manager 875 can be used to manage HARQ. In some examples, managing HARQ can include at least one of: separately managing uplink HARQ for PUSCH in the UpPTS and uplink HARQ for PUSCH transmission in the uplink TTI, jointly managing uplink HARQ for PUSCH in the UpPTS and uplink HARQ for PUSCH transmission in the uplink TTI, or asynchronously receiving uplink HARQ for PUSCH in the UpPTS and uplink HARQ for PUSCH transmission in the uplink TTI.

[0135] Figure 9 A block diagram 900 of an apparatus 905 for wireless communication according to various aspects of the present disclosure is shown. The apparatus 905 may be a network access device (such as a Figure 1 The apparatus 905 may also be or include a processor. The apparatus 905 may include a receiver 910, a wireless communication manager 920, or a transmitter 930. Each of these components may communicate with each other.

[0136] The components of device 905 can be implemented individually or collectively using one or more ASICs adapted to perform some or all applicable functions in hardware. Alternatively, the functions can be performed by one or more other processing units (or cores) on one or more integrated circuits. In some other examples, other types of integrated circuits (e.g., structured / platform ASICs, FPGAs, SoCs, and / or other types of semi-custom ICs) can be used, which can be programmed in any manner known in the art. The functions of each component can be implemented in whole or in part using instructions contained in a memory formatted to be executed by one or more general-purpose or application-specific processors.

[0137] In some examples, receiver 910 can include at least one RF receiver, such as at least one RF receiver operable to receive transmissions over at least one radio spectrum band. In some examples, one or more of the at least one radio spectrum band can be used for LTE / LTE-A communications, such as, for example, as described with reference to FIG. Figure 1 、 2 , 3, 4, 5 or 6. The receiver 910 may be used to communicate with one or more communication links of a wireless communication system (e.g., Figure 1 The wireless communication system 100 may be configured to receive various types of data or control signals (ie, transmissions) from one or more communication links of the depicted wireless communication system 100.

[0138] In some examples, transmitter 930 may include at least one RF transmitter, such as at least one RF transmitter operable to transmit over at least one radio spectrum band. Transmitter 930 may be used to transmit over one or more communication links of a wireless communication system (e.g., reference Figure 1 One or more communication links of the described wireless communication system 100 transmit various types of data or control signals (ie, transmissions).

[0139] In some examples, wireless communication manager 920 can be used to manage one or more aspects of wireless communications of device 905. In some examples, portions of wireless communication manager 920 can be incorporated into or shared with receiver 910 or transmitter 930. In some examples, wireless communication manager 920 can include a UCI manager 935, a PUSCH scheduler 940, or a scheduling information transmission manager 945.

[0140] The UCI manager 935 may be configured to determine whether to schedule transmission of UCI on the PUSCH in the UpPTS of a subframe. The PUSCH scheduler 940 may be configured to schedule the PUSCH in the UpPTS based at least in part on the determination made by the UCI manager 935. The scheduling information transmission manager 945 may be configured to transmit scheduling information for the PUSCH in the UpPTS to the UE.

[0141] Figure 10 A block diagram 1000 of a wireless communication manager 1020 for wireless communication according to various aspects of the present disclosure is shown. The wireless communication manager 1020 may be a reference Figure 9 Examples of aspects of the wireless communication manager 920 are described.

[0142] The components of the wireless communication manager 1020 may be implemented individually or collectively using one or more ASICs adapted to perform some or all applicable functions in hardware. Alternatively, the functions may be performed by one or more other processing units (or cores), on one or more integrated circuits. In some other examples, other types of integrated circuits (e.g., structured / platform ASICs, FPGAs, SoCs, and / or other types of semi-custom ICs) may be used, which may be programmed in any manner known in the art. The functionality of each component may be implemented in whole or in part using instructions contained in memory, formatted to be executed by one or more general-purpose or application-specific processors.

[0143] In some examples, wireless communication manager 1020 can be used to manage network access devices or equipment (e.g., Figure 1 One of the base stations 105 described or referenced Figure 9In some examples, a portion of the wireless communication manager 1020 may be incorporated into a receiver or transmitter (e.g., a reference to FIG. Figure 9 Receiver 910 or transmitter 930 described herein) or with a receiver or transmitter (e.g., reference Figure 9 In some examples, the wireless communication manager 1020 may include an optional random access manager 1050, a UCI manager 1035, a PUSCH scheduler 1040, a scheduling information transmission manager 1045, or a HARQ manager 1055.

[0144] The random access manager 1050 may be configured to receive a random access preamble.

[0145] The UCI manager 1035 may be used to determine whether to schedule transmission of UCI on the PUSCH in the UpPTS of a subframe.

[0146] The PUSCH scheduler 1040 can be configured to schedule a PUSCH in the UpPTS based at least in part on a determination made by the UCI manager 935. In some examples, the PUSCH in the UpPTS can be scheduled in response to receiving a random access preamble by the random access manager 1050. In some examples, the PUSCH scheduler 1040 can select a first offset for scheduling information for the PUSCH in the UpPTS. In some examples, the first offset can be different from a second offset configured for at least one UCI type selected for the uplink subframe.

[0147] The scheduling information transmission manager 1045 may be configured to transmit scheduling information for the PUSCH in the UpPTS to the UE. In some examples, a first offset may be indicated in the scheduling information. In some examples, the scheduling information transmission manager 1045 may select the timing of a TTI in which the scheduling information for the PUSCH in the UpPTS is transmitted. The TTI may be selected based at least in part on a delay reduction capability of the UE. In some examples, the delay reduction capability of the UE may include at least one of: a scheduling timing reduction capability, a TTI duration reduction capability, or a combination thereof. In some examples, the timing of the TTI in which the scheduling information is transmitted may include: a preamble boundary occurring at least two subframes before the UpPTS, or a preamble boundary occurring at least 2.5 subframes before the UpPTS. In some examples, the scheduling information transmission manager 1045 may transmit DCI to the UE. In some examples, the scheduling information transmission manager 1045 may indicate in the DCI the presence of an uplink grant for the PUSCH in the UpPTS. The indication may be based at least in part on: a status of an information field included in the DCI, masking of a control channel including the DCI using a predetermined CRC mask, an association of the uplink grant with a predetermined decoding candidate, a size of the DCI, an identifier of a subframe in which the DCI is received, a DCI format, or a combination thereof.

[0148] The HARQ manager 1055 can be used to manage HARQ. In some examples, managing HARQ can include at least one of: separately managing uplink HARQ for PUSCH in UpPTS and uplink HARQ for PUSCH transmission in uplink TTI, jointly managing uplink HARQ for PUSCH in UpPTS and uplink HARQ for PUSCH transmission in uplink TTI, or asynchronously transmitting uplink HARQ for PUSCH in UpPTS and uplink HARQ for PUSCH transmission in uplink TTI.

[0149] Figure 11 A block diagram 1100 of a UE 1115 for wireless communication according to various aspects of the present disclosure is shown. The UE 1115 may be included in or be a personal computer (e.g., a laptop, a netbook computer, a tablet computer, etc.), a cellular phone, a PDA, a DVR, an Internet appliance, a game console, an e-reader, etc. In some examples, the UE 1115 may have an internal power source (not shown), such as a small battery, to facilitate mobile operation. In some examples, the UE 1115 may be a reference Figure 1 Aspects of one or more of the UE 115 described herein, or referenced herein Figure 7Examples of various aspects of the apparatus 715 described herein. The UE 1115 may be configured to implement the reference Figure 1 、 2 , 3, 4, 5, 6, 7 or 8 described in at least some of the UE features and functions.

[0150] The UE 1115 may include a UE processor 1110, a UE memory 1120, at least one UE transceiver (represented by a UE transceiver 1130), at least one UE antenna (represented by a UE antenna 1140), or a UE wireless communication manager 1150. Each of these components may communicate with each other directly or indirectly via one or more UE buses 1135.

[0151] The UE memory 1120 may include random access memory (RAM) or read-only memory (ROM). The UE memory 1020 may store computer-readable computer-executable code 1125 containing instructions that, when executed, are configured to cause the UE processor 1110 to perform various functions related to wireless communication described herein, including, for example, identifying a PUSCH to be transmitted in the UpPTS of a subframe, determining whether to transmit UCI on the PUSCH in the UpPTS, and transmitting the PUSCH in the UpPTS based at least in part on the determination. Alternatively, the computer-executable code 1125 may not be directly executable by the UE processor 1110, but may be configured to cause the UE 1115 (e.g., when compiled and executed) to perform various functions described herein.

[0152] The UE processor 1110 may include an intelligent hardware device, such as a central processing unit (CPU), a microcontroller, an ASIC, etc. The UE processor 1110 may process information received through the UE transceiver 1130 or information to be sent to the UE transceiver 1130 for transmission through the UE antenna 1140. The UE processor 1110 may handle various aspects of communicating (or managing communications) over one or more radio spectrum bands, either alone or in conjunction with the UE wireless communication manager 1150.

[0153] The UE transceiver 1130 may include a modem configured to modulate packets and provide the modulated packets to the UE antenna 1140 for transmission, and to demodulate packets received from the UE antenna 1140. In some examples, the UE transceiver 1130 may be implemented as one or more transmitters and one or more separate receivers. The UE transceiver 1130 may support communication over one or more wireless communication links. The UE transceiver 1130 may be configured to communicate with one or more network access devices or other apparatuses (e.g., reference UE antennas 1140) via the UE antennas 1140. Figure 1One or more of the base stations 105 described or referenced Figure 9 Although the UE 1115 may include a single UE antenna, there may be examples where the UE 1115 may include multiple UE antennas.

[0154] The UE wireless communication manager 1150 may be configured to execute or control the reference Figure 1 、 2 , 3, 4, 5, 6, 7 or 8. The UE wireless communication manager 1150 or a portion thereof may include a processor, or some or all of the functions of the UE wireless communication manager 1050 may be performed by or in conjunction with the UE processor 1110. In some examples, the UE wireless communication manager 1150 may be a reference to Figure 7 or 8 describe an example of a wireless communication manager 720 or 820.

[0155] Figure 12 A block diagram 1200 illustrates a base station 1205 (e.g., a base station forming part or all of an eNB) for wireless communication according to various aspects of the present disclosure. In some examples, the base station 1205 may be a reference Figure 1 Aspects of one or more of the base stations 105 described or referenced Figure 1 Examples of various aspects of the apparatus 1105 described herein. The base station 1205 may be configured to implement or facilitate reference Figure 1 、 2 , 3, 4, 5, 6, 7, 8, 9, 10, 11 or 12 described in terms of at least some of the network access device or base station features and functions.

[0156] The base station 1205 may include a base station processor 1210, a base station memory 1220, at least one base station transceiver (represented by base station transceiver 1250), at least one base station antenna (represented by base station antenna 1255), or a base station wireless communication manager 1260. The base station 1205 may also include one or more of a network access device communicator 1230 or a network communicator 1240. Each of these components may communicate with each other directly or indirectly via one or more base station buses 1235.

[0157] The base station memory 1220 may include RAM or ROM. The base station memory 1220 may store computer-readable computer-executable code 1225 containing instructions that, when executed, are configured to cause the base station processor 1210 to perform various functions related to wireless communications described herein, including, for example, determining whether to schedule transmission of UCI on the PUSCH in the UpPTS of a subframe, scheduling the PUSCH in the UpPTS based at least in part on the determination, and transmitting scheduling information for the PUSCH in the UpPTS to the UE. Alternatively, the computer-executable code 1225 may not be directly executable by the base station processor 1210, but may be configured to cause the base station 1205 (e.g., when compiled and executed) to perform various functions described herein.

[0158] The base station processor 1210 may include an intelligent hardware device, such as a CPU, a microcontroller, an ASIC, etc. The base station processor 1210 may process information received through the base station transceiver 1250, the network access device communicator 1230, or the network communicator 1240. The base station processor 1210 may also process information to be sent to the base station transceiver 1250 for transmission through the base station antenna 1225, to the network access device communicator 1230 for transmission to one or more other network access devices (e.g., base station 1205-a or base station 1205-b), or to the network communicator 1240 for transmission to the core network 1290, which may be a reference network. Figure 1 Examples of one or more aspects of the described core network 130. Base station processor 1210, alone or in conjunction with base station wireless communication manager 1260, may handle various aspects of communicating (or managing communications) over one or more radio spectrum bands.

[0159] The base station transceiver 1250 may include a modem configured to modulate packets and provide the modulated packets to the base station antenna 1255 for transmission, and to demodulate packets received from the base station antenna 1255. In some examples, the base station transceiver 1250 may be implemented as one or more transmitters and one or more separate receivers. The base station transceiver 1250 may support communications over one or more wireless communication links. The base station transceiver 1250 may be configured to communicate with one or more UEs or other devices (e.g., reference UEs) via the base station antenna 1255. Figure 1 or one or more of the UEs 115 or 1115 described in 11 or reference Figure 7Base station 1205 can communicate with core network 1290 via network communicator 1240. Base station 1205 can also communicate with other network access devices (e.g., base station 1205-a or base station 1205-b) using network access device communicator 1230.

[0160] The base station wireless communication manager 1260 may be configured to execute or control the reference Figure 1 、 2 , 3, 4, 5, 6, 9 or 10. The base station wireless communication manager 1260 or a portion thereof may include a processor, or some or all of the functions of the base station wireless communication manager 1260 may be performed by or in conjunction with the base station processor 1210. In some examples, the base station wireless communication manager 1260 may be a reference to Figure 9 or 10 describe an example of a wireless communication manager 920 or 1020.

[0161] Figure 13 is a flow chart illustrating an example of a method 1300 for wireless communication at a UE according to various aspects of the present disclosure. Figure 1 or 11 described in one or more aspects of the UE 115 or 1115, reference Figure 7 The method 1300 is described with reference to a UE that includes various aspects of the apparatus 715. In some examples, the UE may execute one or more code sets to control the functional units of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform one or more of the functions described below.

[0162] At block 1305, method 1300 may include identifying a PUSCH to be transmitted in an UpPTS of a subframe. The operations at block 1305 may use reference Figure 7 or 8 described wireless communication manager 720 or 820, reference Figure 11 UE wireless communication manager 1150 described or referenced Figure 7 or 8 described by the PUSCH identifier 735 or 835.

[0163] At block 1310, method 1300 may include determining whether to transmit UCI on the PUSCH in the UpPTS. The operations at block 1310 may use reference Figure 7 or 8 described wireless communication manager 720 or 820, reference Figure 11 UE wireless communication manager 1150 described or referenced Figure 7or 8 described by the UCI manager 740 or 840.

[0164] At block 1315, method 1300 may include transmitting the PUSCH in the UpPTS based at least in part on the determination made at block 1310. The operations at block 1315 may use reference Figure 7 or 8 described wireless communication manager 720 or 820, reference Figure 11 UE wireless communication manager 1150 described or referenced Figure 7 or 8 described by the PUSCH transmission manager 745 or 845.

[0165] Figure 14 is a flow chart illustrating an example of a method 1400 for wireless communication at a UE according to various aspects of the present disclosure. Figure 1 or 11 described in one or more aspects of the UE 115 or 1115, reference Figure 7 The method 1400 is described with reference to a UE that includes various aspects of the apparatus 715 described herein. In some examples, the UE may execute one or more code sets to control the functional units of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform one or more of the functions described below.

[0166] At block 1405, method 1400 may optionally include transmitting a random access preamble. The operations at block 1405 may use reference Figure 7 or 8 described wireless communication manager 720 or 820, reference Figure 11 UE wireless communication manager 1150 described or referenced Figure 8 The random access manager 850 described above is executed.

[0167] At one or more of blocks 1410, 1415, or 1420, method 1400 may include identifying a PUSCH to be transmitted in an UpPTS of a subframe. At block 1410, method 1400 may include receiving scheduling information for the PUSCH in the UpPTS during a TTI. The timing of the TTI may be based at least in part on a delay reduction capability of the UE. In some examples, the delay reduction capability of the UE may include at least one of: a scheduling timing reduction capability, a TTI duration reduction capability, or a combination thereof. In some examples, the timing of the TTI in which the scheduling information is received may include: a preamble boundary occurring at least two subframes before the UpPTS, or a preamble boundary occurring at least 2.5 subframes before the UpPTS. In some examples, the scheduling information may include a first offset that is different from a second offset configured for at least one UCI type received for the uplink subframe. In some examples, some or all of the scheduling information may be received in DCI or RRC signaling. In some examples, the operations at block 1410 may include receiving a random access response message for scheduling the PUSCH in the UpPTS. In response to transmitting the random access preamble at block 1405, a random access response message may be received. The operations at block 1410 may use reference Figure 7 or 8 described wireless communication manager 720 or 820, reference Figure 11 UE wireless communication manager 1150 described in reference Figure 7 or PUSCH identifier 735 or 835 described in 8 or reference Figure 8 The PUSCH scheduling manager 860 described above is executed.

[0168] At block 1415, method 1400 may include receiving a DCI. In some examples, the DCI may be received as part of receiving scheduling information at block 1410. In some examples, the operations at block 1415 may include identifying an uplink grant for a PUSCH in an UpPTS received in the DCI based at least in part on: a state of an information field included in the DCI, masking of a control channel including the DCI with a predetermined CRC mask, an association of the uplink grant with a predetermined decoding candidate, a size of the DCI, an identifier of a subframe in which the DCI is received, a DCI format, or a combination thereof. In some examples, the operations at block 1415 may include determining a size of the DCI. In some examples, the operations at block 1415 may include identifying at least one decoding candidate for an uplink grant for a PUSCH in an UpPTS within the DCI. The at least one decoding candidate may be based at least in part on the size of the DCI. The operations at block 1415 may use a reference Figure 7 or 8 described wireless communication manager 720 or 820, reference Figure 11UE wireless communication manager 1150 described in reference Figure 7 or PUSCH identifier 735 or 835 described in 8 or reference Figure 8 The PUSCH scheduling manager 860 described above is executed.

[0169] At block 1420, method 1400 may optionally include determining whether an uplink TTI is scheduled for transmission on at least the first CC while a PUSCH in the UpPTS is transmitted on the second CC, or determining whether a PUSCH in the UpPTS is scheduled for transmission when operating in carrier aggregation mode. The operations at block 1420 may use reference Figure 7 or 8 described wireless communication manager 720 or 820, reference Figure 11 UE wireless communication manager 1150 described or referenced Figure 8 The carrier aggregation manager 855 described above is executed.

[0170] At block 1425, method 1400 may include determining whether to transmit UCI on the PUSCH in the UpPTS. In some examples, the determination at block 1425 may be based at least in part on one of the determinations at block 1420. For example, method 1400 may include determining to transmit UCI on the PUSCH in the UpPTS when it is determined at block 1420 that the uplink TTI is scheduled for transmission on at least the first CC. In some examples, the determination at block 1425 may be based at least in part on determining whether the PUSCH in the UpPTS is scheduled for transmission when operating in carrier aggregation mode. For example, when operating in carrier aggregation mode, it may be determined at block 1425 not to transmit at least one of periodic CSI, aperiodic CSI, UCI, or a combination thereof on the PUSCH in the UpPTS. When operating in carrier aggregation mode, the determination made at block 1425 may additionally or alternatively include determining to transmit at least one of: periodic CSI, aperiodic CSI, UCI, or a combination thereof, in parallel with the PUSCH in the UpPTS on a CC that does not carry the PUSCH in the UpPTS. Alternatively, when operating in carrier aggregation mode, the determination made at block 1425 may determine to transmit at least one of periodic CSI, aperiodic CSI, UCI, or a combination thereof on the PUSCH in the UpPTS. The operations at block 1425 may use reference Figure 7 or 8 described wireless communication manager 720 or 820, reference Figure 11 UE wireless communication manager 1150 described or referenced Figure 7 or 8 described by the UCI manager 740 or 840.

[0171] At block 1430, method 1400 may optionally include selecting a CC for transmitting UCI. In some examples, the CC may be selected based at least in part on a priority ranking of the CCs that causes the CC selection to deviate from the CC carrying the PUSCH in the UpPTS. The operations at block 1430 may use reference Figure 7 or 8 described wireless communication manager 720 or 820, reference Figure 11 UE wireless communication manager 1150 described in reference Figure 7 or UCI manager 740 or 840 described in 8 or reference Figure 8 The UCI CC selector 865 described above is executed.

[0172] At block 1435, method 1400 may optionally include determining, based at least in part on the number of reference symbols to be transmitted in the UpPTS, whether to enable at least one of: frequency hopping during transmission of the PUSCH in the UpPTS, use of OCC during transmission of the PUSCH in the UpPTS, or a combination thereof. The operations at block 1435 may use reference symbols. Figure 7 or 8 described wireless communication manager 720 or 820, reference Figure 11 UE wireless communication manager 1150 described or referenced Figure 7 or 8 described by the PUSCH transmission manager 745 or 845.

[0173] At block 1440, method 1400 may optionally include identifying a first power control parameter for the TTI. The operations at block 1440 may use reference Figure 7 or 8 described wireless communication manager 720 or 820, reference Figure 11 UE wireless communication manager 1150 described in reference Figure 7 or PUSCH transmission manager 745 or 845 described in 8 or reference Figure 8 The power controller 870 described above is executed.

[0174] At block 1445, method 1400 may optionally include determining a second power control parameter for the PUSCH in the UpPTS based at least in part on the first power control parameter for the TTI. In some examples, the second power control parameter may be determined based at least in part on a semi-static relationship between the first power control parameter and the second power control parameter, or based at least in part on a variable structure of the PUSCH in the UpPTS. The operations at block 1445 may use reference Figure 7 or 8 described wireless communication manager 720 or 820, reference Figure 11 UE wireless communication manager 1150 described in reference Figure 7or PUSCH transmission manager 745 or 845 described in 8 or reference Figure 8 The power controller 870 described above is executed.

[0175] At block 1450, method 1400 may include transmitting the PUSCH in the UpPTS based at least in part on the determination made at block 1425. The operations at block 1450 may use reference Figure 7 or 8 described wireless communication manager 720 or 820, reference Figure 11 UE wireless communication manager 1150 described or referenced Figure 7 or 8 described by the PUSCH transmission manager 745 or 845.

[0176] At block 1455, method 1400 may include managing HARQ. In some examples, managing HARQ may include at least one of separately managing uplink HARQ for PUSCH in the UpPTS and uplink HARQ for PUSCH transmission in an uplink TTI, jointly managing uplink HARQ for PUSCH in the UpPTS and uplink HARQ for PUSCH transmission in an uplink TTI, or asynchronously receiving uplink HARQ for PUSCH in the UpPTS and uplink HARQ for PUSCH transmission in an uplink TTI. The operations at block 1455 may use reference Figure 7 or 8 described wireless communication manager 720 or 820, reference Figure 11 UE wireless communication manager 1150 described or referenced Figure 8 The HARQ manager 875 described above is executed.

[0177] Figure 15 is a flow chart illustrating an example of a method 1500 for wireless communication at a network access device (eg, a base station) in accordance with various aspects of the present disclosure. Figure 1 or 12 described in one or more aspects of the base station 105 or 1205, reference Figure 9 Method 1500 is illustrated using a network access device with various aspects of the apparatus 905 described herein. In some examples, a base station may execute one or more code sets to control functional units of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform one or more of the functions described below.

[0178] At block 1505, method 1500 may include determining whether to schedule transmission of UCI on the PUSCH in the UpPTS of a subframe. The operations at block 1505 may be performed using reference Figure 9or 10 described wireless communication manager 920 or 1020, reference Figure 12 Base station wireless communication manager 1260 described or referenced Figure 9 or 10 described UCI manager 935 or 1035 to execute.

[0179] At block 1510, method 1500 may include scheduling a PUSCH in the UpPTS based at least in part on the determination. The operations at block 1510 may use reference Figure 9 or 10 described wireless communication manager 920 or 1020, reference Figure 12 Base station wireless communication manager 1260 described or referenced Figure 9 or 10 described by the PUSCH scheduler 940 or 1040.

[0180] At block 1515, method 1500 may include transmitting scheduling information for PUSCH in the UpPTS to the UE. The operations at block 1515 may be performed using reference Figure 9 or 10 described wireless communication manager 920 or 1020, reference Figure 12 Base station wireless communication manager 1260 described or referenced Figure 9 or 10 described in the scheduling information transmission manager 945 or 1045 to execute.

[0181] Figure 16 is a flow chart illustrating an example of a method 1600 for wireless communication at a network access device (eg, a base station) in accordance with various aspects of the present disclosure. Figure 1 or 12 described in one or more aspects of the base station 105 or 1205, reference Figure 9 Method 1600 is illustrated using a network access device with various aspects of the apparatus 905 described herein. In some examples, a base station may execute one or more code sets to control functional units of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform one or more of the functions described below.

[0182] At block 1605, method 1600 may optionally include receiving a random access preamble. The operations at block 1605 may use reference Figure 9 or 10 described wireless communication manager 920 or 1020, reference Figure 12 Base station wireless communication manager 1260 described or referenced Figure 10 The random access manager 1050 described above is executed.

[0183] At block 1610, method 1600 may include determining whether to schedule transmission of UCI on a PUSCH in an UpPTS of a subframe. The operations at block 1610 may be performed using reference Figure 9 or 10 described wireless communication manager 920 or 1020, reference Figure 12 Base station wireless communication manager 1260 described or referenced Figure 9 or 10 described UCI manager 935 or 1035 to execute.

[0184] At block 1615, method 1600 may include scheduling a PUSCH in the UpPTS based at least in part on the determination made at block 1610. In some examples, the PUSCH in the UpPTS may be scheduled in response to receiving the random access preamble at block 1605. In some examples, some or all of the scheduling information may be conveyed in DCI or RRC signaling. The operations at block 1615 may use reference Figure 9 or 10 described wireless communication manager 920 or 1020, reference Figure 12 Base station wireless communication manager 1260 described or referenced Figure 9 or 10 described by the PUSCH scheduler 940 or 1040.

[0185] At block 1620, method 1600 may optionally include selecting a first offset for scheduling information for the PUSCH in the UpPTS. In some examples, the first offset may be different from a second offset for at least one UCI type configuration selected for the uplink subframe. The operations at block 1620 may use reference Figure 9 or 10 described wireless communication manager 920 or 1020, reference Figure 12 Base station wireless communication manager 1260 described or referenced Figure 9 or 10 described by the PUSCH scheduler 940 or 1040.

[0186] At block 1625, method 1600 may optionally include selecting a timing of a TTI in which scheduling information for the PUSCH in the UpPTS is to be transmitted. The TTI may be selected based at least in part on a delay reduction capability of the UE. In some examples, the delay reduction capability of the UE may include at least one of a scheduling timing reduction capability, a TTI duration reduction capability, or a combination thereof. In some examples, the timing of the TTI in which the scheduling information is transmitted may include a preamble boundary occurring at least two subframes before the UpPTS, or a preamble boundary occurring at least 2.5 subframes before the UpPTS. The operations at block 1625 may use reference Figure 9 or 10 described wireless communication manager 920 or 1020, reference Figure 12Base station wireless communication manager 1260 described or referenced Figure 9 or 10 described in the scheduling information transmission manager 945 or 1045 to execute.

[0187] At block 1630, method 1600 may include transmitting scheduling information for the PUSCH in the UpPTS to the UE. In some examples, the first offset may be indicated in the scheduling information. The operations at block 1630 may use reference Figure 9 or 10 described wireless communication manager 920 or 1020, reference Figure 12 Base station wireless communication manager 1260 described or referenced Figure 9 or 10 described in the scheduling information transmission manager 945 or 1045 to execute.

[0188] At block 1635, method 1600 may include transmitting the DCI to the UE. In some examples, the DCI may be transmitted as part of the scheduling information transmitted at block 1630. In some examples, method 1600 may include indicating in the DCI that an uplink grant for the PUSCH in the UpPTS is present. The indication may be based at least in part on: a state of an information field included in the DCI, masking of a control channel including the DCI with a predetermined CRC mask, an association of the uplink grant with a predetermined decoding candidate, a size of the DCI, an identifier of a subframe in which the DCI is received, a DCI format, or a combination thereof. The operations at block 1635 may use a reference Figure 9 or 10 described wireless communication manager 920 or 1020, reference Figure 12 Base station wireless communication manager 1260 described or referenced Figure 9 or 10 described in the scheduling information transmission manager 945 or 1045 to execute.

[0189] At block 1640, method 1600 may include managing HARQ. In some examples, managing HARQ may include at least one of separately managing uplink HARQ for PUSCH in the UpPTS and uplink HARQ for PUSCH transmission in an uplink TTI, jointly managing uplink HARQ for PUSCH in the UpPTS and uplink HARQ for PUSCH transmission in an uplink TTI, or asynchronously transmitting uplink HARQ for PUSCH in the UpPTS and uplink HARQ for PUSCH transmission in an uplink TTI. The operations at block 1640 may use reference Figure 9 or 10 described wireless communication manager 920 or 1020, reference Figure 12 Base station wireless communication manager 1260 described or referenced Figure 10The HARQ manager 1055 described above is executed.

[0190] The technology described herein can be used for various wireless communication systems, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other systems. The terms "system" and "network" are generally used interchangeably. A CDMA system can implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), and the like. CDMA2000 covers IS-2000, IS-95, and IS-856 standards. IS-2000 versions 0 and A can be referred to as CDMA2000 1X, 1X, and the like. IS-856 (TIA-856) can be referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), and the like. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. A TDMA system can implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA systems can implement technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.20, Flash-OFDM TM UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP LTE and LTE-A are new versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called 3GPP. CDMA2000 and UMB are described in documents from an organization called "3rd Generation Partnership Project 2" (3GPP2). The technology described herein can be used for the above systems and radio technologies as well as other systems and radio technologies, including cellular (e.g., LTE) communications on unlicensed or shared bandwidths. However, the above description describes an LTE / LTE-A system for example purposes, and LTE terminology is used in most of the above description, but the technology is applicable beyond LTE / LTE-A applications.

[0191] The specific embodiments described above in conjunction with the accompanying drawings illustrate examples, but do not represent all examples that can be implemented or within the scope of the claims. When used in this description, the terms "example" and "exemplary" mean "used as an example, instance, or illustration," rather than "preferred" or "better than other examples." The detailed description includes specific details to provide an understanding of the technology. However, these technologies can be implemented without these specific details. In some cases, well-known structures and devices are shown in block diagram form to avoid making the concepts of the examples difficult to understand.

[0192] A variety of different technologies and methods can be used to represent information and signals. For example, the data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0193] The various illustrative blocks and components described in conjunction with the present disclosure may be implemented or performed using a general-purpose processor, a digital signal processor (DSP), an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0194] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored or transmitted as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope and spirit of this disclosure and the appended claims. For example, due to the nature of software, the functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features that implement the functions can be physically located in multiple locations, including being distributed so that parts of the functions are implemented in different physical locations. As used herein, including in the claims, the term "and / or" when used in a list of two or more items means that any one of the listed items can be used alone, or any combination of two or more of the listed items can be used. For example, if a composition is described as containing components A, B, and / or C, the composition can include A alone; B alone; C alone; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B, and C. In addition, as used herein, including in the claims, "or" used in a list of items (e.g., a list of items preceded by a phrase such as "at least one" or "one or more") indicates an inclusive list, such that, for example, a phrase referring to "at least one of a list of items" refers to any combination of these items, including single members. For example, "at least one of A, B, or C" is intended to cover A, B, C, AB, AC, BC, and ABC, as well as any combination with multiple identical elements (e.g., AA, AAA, AAB, AAC, ABB, ACC, BB, BBB, BBC, CC, and CCC or any other ordering of A, B, and C). As used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an exemplary operation described as "based on condition A" can be based on condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" will be interpreted in the same manner as the phrase "based at least in part on."

[0195] Computer-readable media include non-volatile computer storage media and communication media, including any media that facilitates the transfer of computer programs from one place to another. Non-volatile storage media can be any available media that can be accessed by a general-purpose or special-purpose computer. By way of example and not limitation, non-volatile computer-readable media can include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), compact disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-volatile media that can be used to carry or store the required program code units in the form of instructions or data structures and can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. In addition, any connection is appropriately referred to as a computer-readable medium. For example, if a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwaves are used to transmit software from a website, server or other remote source, the coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwaves are included in the definition of medium. Disk and disc, as used herein, includes CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0196] The foregoing description of the present disclosure is provided to enable those skilled in the art to practice or use the present disclosure. Various modifications to the present disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel technologies disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), comprising: receiving downlink control information (DCI) during a first subframe of a transmission time interval (TTI), the DCI being associated with a first DCI format in a DCI format set, wherein the DCI associated with the first DCI format indicates an uplink index value that identifies resources for transmitting a physical uplink shared channel (PUSCH) in an uplink pilot time slot (UpPTS) of a second subframe; determining, based at least in part on the uplink index value, timing between receiving the DCI in the first subframe of the TTI and transmitting the PUSCH on the UpPTS, wherein the determined timing is based on a processing delay capability of the UE and the identified resource indicated by the DCI associated with the first DCI format; and The PUSCH is transmitted in the UpPTS via the identified resources based at least in part on the determined timing and the uplink index value.

2. The method according to claim 1, wherein The processing delay capability of the UE includes a delay reduction capability of the UE.

3. The method according to claim 2, wherein: The delay reduction capability of the UE includes at least one of the following: a scheduling timing reduction capability, a TTI duration reduction capability, or a combination thereof.

4. The method according to claim 3, further comprising: determining that the UE does not have delay reduction capability, Wherein the determined timing is based at least in part on determining that the UE does not have delay reduction capability, and wherein the determined timing includes a preamble boundary occurring at least 3.5 subframes before the UpPTS.

5. The method according to claim 3, further comprising: determining that the processing delay capability of the UE includes the scheduling timing reduction capability, Wherein the determined timing is based at least in part on determining that the processing delay capability of the UE includes the scheduling timing reduction capability, and wherein the determined timing includes a preamble boundary occurring at least 2 subframes before the UpPTS.

6. The method according to claim 3, further comprising: determining the processing delay capability of the UE including the TTI duration reduction capability, The determined timing is based at least in part on determining that the processing delay capability of the UE includes the TTI duration reduction capability, wherein the determined timing of the TTI includes a preamble boundary occurring at least 2.5 subframes before the UpPTS.

7. The method according to claim 1, further comprising: An uplink hybrid automatic repeat request (HARQ) for the PUSCH in the UpPTS and uplink HARQ for PUSCH transmission in one or more uplink TTIs are managed separately.

8. The method according to claim 1, further comprising: An uplink hybrid automatic repeat request (HARQ) for the PUSCH in the UpPTS and uplink HARQ for PUSCH transmission in one or more uplink TTIs are jointly managed.

9. The method according to claim 1, further comprising: An uplink hybrid automatic repeat request (HARQ) for the PUSCH in the UpPTS and an uplink HARQ for PUSCH transmission in one or more uplink TTIs are asynchronously received.

10. The method according to claim 1, further comprising: An acknowledgement for the PUSCH in the UpPTS is received in the same physical hybrid automatic repeat request (HARQ) indicator channel (PHICH) resource set used to acknowledge PUSCH transmissions in one or more uplink subframes.

11. The method according to claim 1 , further comprising: An uplink grant for the PUSCH in the UpPTS received in the DCI is identified based at least in part on: a status of an information field included in the DCI, masking of a control channel including the DCI with a predetermined cyclic redundancy check (CRC) mask, an association of the uplink grant with a predetermined decoding candidate, a size of the DCI, the first subframe in which the DCI is received, a DCI format, or a combination thereof.

12. The method according to claim 1, further comprising: Determining the size of the DCI; as well as At least one decoding candidate for an uplink grant for the PUSCH in the UpPTS is identified within the DCI, the at least one decoding candidate based at least in part on the size of the DCI.

13. The method according to claim 1, further comprising: identifying a first power control parameter for the TTI; as well as A second power control parameter for the PUSCH in the UpPTS is determined based at least in part on the first power control parameter for the TTI.

14. The method according to claim 13, wherein The second power control parameter is determined based at least in part on: a semi-static relationship between the first power control parameter and the second power control parameter, or a variable structure of the PUSCH in the UpPTS.

15. A method for wireless communication, comprising: determining whether to schedule a transmission of a physical uplink shared channel (PUSCH) to be sent in an uplink pilot time slot (UpPTS); transmitting, during a first subframe, to a user equipment (UE), downlink control information (DCI) associated with a first DCI format in a DCI format set, wherein the DCI associated with the first DCI format includes an uplink index value that identifies a resource set allocated for transmission of the PUSCH in the UpPTS of a second subframe, the uplink index value further indicating: timing of a transmission time interval (TTI) for transmitting the DCI and receiving the PUSCH in the UpPTS based at least in part on a processing delay capability of the UE and the resource set indicated by the DCI associated with the first DCI format; as well as The PUSCH in the UpPTS is received via the resource set based at least in part on the timing and the uplink index value.

16. The method according to claim 15, wherein The processing delay capability of the UE includes a delay reduction capability of the UE.

17. The method according to claim 16, wherein The delay reduction capability of the UE includes at least one of the following: a scheduling timing reduction capability, a TTI duration reduction capability, or a combination thereof.

18. The method according to claim 17, wherein The timing of the TTI for sending the DCI includes at least one of: a preamble boundary occurring at least 3.5 subframes before the UpPTS, a preamble boundary occurring at least 2 subframes before the UpPTS, a preamble boundary occurring at least 2.5 subframes before the UpPTS, or a combination thereof.

19. The method of claim 15, further comprising: An uplink hybrid automatic repeat request (HARQ) for the PUSCH in the UpPTS and uplink HARQ for PUSCH transmission in one or more uplink TTIs are managed separately.

20. The method of claim 15, further comprising: An uplink hybrid automatic repeat request (HARQ) for the PUSCH in the UpPTS and uplink HARQ for PUSCH transmission in one or more uplink TTIs are jointly managed.

21. The method of claim 15, further comprising: An uplink hybrid automatic repeat request (HARQ) for the PUSCH in the UpPTS and an uplink HARQ for PUSCH transmission in one or more uplink TTIs are asynchronously transmitted.

22. The method of claim 15, further comprising: Acknowledgements for the PUSCH in the UpPTS are sent in the same Physical Hybrid Automatic Repeat Request (HARQ) Indicator Channel (PHICH) resource set used to acknowledge PUSCH transmissions in one or more uplink subframes.

23. The method of claim 15, further comprising: The presence of an uplink grant for the PUSCH in the UpPTS in the DCI is indicated based at least in part on: a status of an information field included in the DCI, masking of a control channel including the DCI with a predetermined cyclic redundancy check (CRC) mask, an association of the uplink grant with a predetermined decoding candidate, a size of the DCI, the first subframe in which the DCI is received, a DCI format, or a combination thereof.

24. The method according to claim 15, in, The DCI includes at least one decoding candidate for an uplink grant for the PUSCH in the UpPTS, the at least one decoding candidate being based at least in part on a size of the DCI.

25. The method of claim 15, further comprising: receiving a random access preamble; as well as The transmission of the PUSCH in the UpPTS is scheduled in response to receiving the random access preamble.

26. An apparatus for wireless communication at a user equipment (UE), comprising: processor; as well as a memory coupled to the processor; The processor and the memory are configured to: receiving downlink control information (DCI) during a first subframe of a transmission time interval (TTI), the DCI being associated with a first DCI format in a DCI format set, wherein the DCI associated with the first DCI format indicates an uplink index value that identifies resources for transmitting a physical uplink shared channel (PUSCH) in an uplink pilot time slot (UpPTS) of a second subframe; determining, based at least in part on the uplink index value, timing between receiving the DCI in the first subframe of the TTI and transmitting the PUSCH on the UpPTS, wherein the determined timing is based on a processing delay capability of the UE and the identified resource indicated by the DCI associated with the first DCI format; and The PUSCH is transmitted in the UpPTS via the identified resources based at least in part on the determined timing and the uplink index value.

27. The device according to claim 26, wherein The processing delay capability of the UE includes a delay reduction capability of the UE.

28. The apparatus according to claim 27, wherein The delay reduction capability of the UE includes at least one of the following: a scheduling timing reduction capability, a TTI duration reduction capability, or a combination thereof.

29. An apparatus for wireless communication at a network device, comprising: processor; as well as a memory coupled to the processor; The processor and the memory are configured to: determining whether to schedule a transmission of a physical uplink shared channel (PUSCH) to be sent in an uplink pilot time slot (UpPTS); transmitting, during a first subframe, to a user equipment (UE), downlink control information (DCI) associated with a first DCI format in a DCI format set, wherein the DCI associated with the first DCI format includes an uplink index value that identifies a resource set allocated for transmission of the PUSCH in the UpPTS of a second subframe, the uplink index value further indicating: timing of a transmission time interval (TTI) for transmitting the DCI and receiving the PUSCH in the UpPTS based at least in part on a processing delay capability of the UE and the resource set indicated by the DCI associated with the first DCI format; and UpPTS; The PUSCH in the UpPTS is received via the resource set based at least in part on the timing and the uplink index value.

30. The apparatus according to claim 29, wherein The processing delay capability of the UE includes a delay reduction capability of the UE.

Images