Method and apparatus for improving control channel structure in shortened transmission time intervals in a wireless communication system

Control structures and techniques for transmission time interval (TTI) shortening in wireless communication systems are provided. Exemplary techniques can comprise establishing a UE device connection to a base station having a first TTI, wherein the UE device is configured to employ TTI shortening and has a second TTI different from the first TTI and monitoring a first short physical downlink control channel (PDCCH) region for a scheduled downlink (DL) transmission via the second TTI, wherein a time distribution associated with multiple second TTIs within the first TTI is determined based on a control format indicator (CFI) value indicated via the first TTI. Exemplary techniques can further comprise receiving a DL transmission via the second TTI and transmitting a hybrid automatic repeat request (HARD) acknowledgement (ACK) (HARQ-ACK) feedback on an associated UL channel for HARQ-ACK feedback, wherein for a number of DL transmissions via the second TTI within one of the first TTI on the associated DL, a number of associated UL channels for HARQ-ACK feedback occur within the same one of the first TTI on the associated UL. Further control structures and techniques for TTI shortening for wireless communication systems are described.

TECHNICAL FIELD

The subject disclosure is directed to wireless communications, and is more particularly related to control channel structure in shortened transmission time intervals in a wireless communication systems.

BACKGROUND

As maximum data rates of the wireless communication systems increase, packet data latency becomes one of the more important metrics for performance evaluation of wireless communication networks. Thus, reducing packet data latency can improve performance of wireless communication systems and efforts are being made to improve packet data latency for wireless medication systems.

Conventionally, Long Term Evolution (LTE) wireless communication systems employ a transmission time interval (TTI) of about 1 millisecond (ms) or approximately 14 orthogonal frequency division multiplexing (OFDM) symbols. In addition, LTE employs two types of control channels, physical downlink control channel (PDCCH), which is a wide band signal across whole system bandwidth and occupying the first several (e.g., approximately 1-4) OFDM symbols of a typical 1 ms subframe. The region occupied by PDCCH is usually named as control region, and the rest part of the subframe is usually known as data region. A second type of control channel, enhanced physical downlink control channel (ePDCCH), occupies the data region in the time domain, while typically occupying only part of the bandwidth in the frequency domain.

Accordingly, TTI shortening and processing time reduction can be considered for solutions that can facilitate reducing packet data latency, as the time unit for transmission can be reduced e.g., from 1 ms (e.g., approximately 14 OFDM symbols) and the delay caused by decoding can be reduced as well. However, reducing the length of TTI can also have significant impacts on current system design as the physical channels are developed based on 1 ms subframe structure. In addition, reducing the length of TTI can also have significant impacts for scheduling and transmission via physical downlink shared channel (PDSCH) and physical uplink shared channel (PUSCH) with such shortened TTI, due to PDCCH competition and/or short TTI (sTTI) inequality.

The above-described deficiencies of conventional control channel structures and/or transmission time intervals in wireless communication systems are merely intended to provide an overview of some of the problems of conventional systems and methods, and are not intended to be exhaustive. Other problems with conventional systems and corresponding benefits of the various non-limiting embodiments described herein may become further apparent upon review of the various non-limiting embodiments of the following description.

SUMMARY

As used herein, the following terms can be referred to by the respective abbreviations: 3rd Generation Partnership Project (3GPP); acknowledgement (ACK); buffer status report (BSR); Cell Radio Network Temporary Identifier (C-RNTI); channel quality indicator (CQI); control format indicator (CFI); downlink (DL); Enhanced Interference Mitigation and Traffic Adaptation (eIMTA); Evolved Node B (eNB or eNodeB); Evolved Universal Terrestrial Radio Access (E-UTRA); Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Frequency-Division Multiplexing (FDM); Hybrid Automatic Repeat Request (HARQ); Layer 1 (L1); Long Term Evolution (LTE); LTE-Advanced (LTE-A); Medium Access Control (MAC); multiple input, multiple output (MIMO); negative acknowledgement (NACK); New data indicator (NDI); Orthogonal Frequency Division Multiplexing (OFDM); Physical Downlink Control Channel (PDCCH); Physical Uplink Control Channel (PUCCH); Physical Downlink Shared Channel (PDSCH); Physical Uplink Shared Channel (PUSCH); Radio Network Temporary Identifier (RNTI); Relay Node (RN); Radio Resource Control (RRC); Short or Shortened (s-(prefix)), for example, PDCCH for short TTI (sPDCCH); Service Data Unit (SDU); System Frame Number (SFN); Special Cell (SpCell); Semi-Persistent Scheduling (SPS); Scheduling Request (SR); Sounding Reference Signal (SRS); Timing Advance Group (TAG); Time-Division Multiplexing (TDM); Technical Specification (TS); Transmission Time Interval (TTI); User Equipment (UE); Uplink (UL); and Uplink Shared Channel (UL-SCH).

In various non-limiting embodiments, the disclosed subject matter provides TTI shortening, which can facilitate efficient scheduling for sPDSCH and sPUSCH transmissions without sPDCCH competition and scheduling complexity due to sTTI inequality, for example, as further described herein.

For instance, various embodiments are disclosed that can facilitate TTI shortening and wireless medication systems. Accordingly, non-limiting embodiments of the disclosed subject matter can provide example methods that facilitate TTI shortening in UE devices. As non-limiting examples, exemplary methods can comprise establishing with the UE device a connection to a base station having a first TTI, wherein the UE device is configured to employ TTI shortening and has a second TTI different from the first TTI, and monitoring a first short physical downlink control channel (PDCCH) region for a scheduled downlink (DL) transmission via the second TTI, wherein a time distribution associated with multiple second TTIs within the first TTI is determined based in part on a control format indicator (CFI) value indicated via the first TTI.

As a further non-limiting examples, exemplary methods can comprise establishing with the UE device a connection to a base station having a first TTI for an associated DL and an associated uplink (UL), wherein the UE device is configured to employ TTI shortening and has a second TTI different from the first TTI, receiving a DL transmission via the second TTI, and transmitting hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback on an associated UL channel for HARQ-ACK feedback, wherein for a number of DL transmissions via the second TTI within one of the first TTI on the associated DL, a number of associated UL channels for HARQ-ACK feedback occur within the same one of the first TTI on the associated UL.

In still further non-limiting examples, exemplary methods can comprise establishing with the UE device a connection to a base station having a first TTI for an associated DL and an associated UL, wherein the UE device is configured to employ TTI shortening and having a third TTI of a number of TTIs different from the first TTI, detecting a second short physical downlink control channel (PDCCH) for scheduling an UL transmission via the third TTI, and transmitting at least a scheduled UL transmission on at least an associated UL channel, wherein for a number of short PDCCHs within one of the first TTI on the associated DL, a plurality of UL channels having the at least the scheduled UL transmission occur within the same one of the first TTI on the associated UL.

In addition, further example implementations are directed to systems, devices and/or other articles of manufacture that facilitate TTI shortening, as further detailed herein.

These and other features of the disclosed subject matter are described in more detail below.

DETAILED DESCRIPTION

As described above, deficiencies of conventional control channel structures and/or transmission time intervals in wireless communication systems can provide opportunities to reduce packet data latency, which can improve performance of wireless communication systems.

For example, Long Term Evolution (LTE) wireless communication systems employ a transmission time interval (TTI) of about 1 millisecond (ms) or approximately 14 orthogonal frequency division multiplexing (OFDM) symbols. In addition, LTE employs two types of control channels, physical downlink control channel (PDCCH), which is a wide band signal across whole system bandwidth and occupying the first several (e.g., approximately 1-4) OFDM symbols of a typical 1 ms subframe. The region occupied by PDCCH is usually named as control region, and the rest part of the subframe is usually known as data region. A second type of control channel, enhanced physical downlink control channel (ePDCCH), occupies the data region in the time domain, while typically occupying only part of the bandwidth in the frequency domain.

Accordingly, TTI shortening and processing time reduction can be considered for solutions that can facilitate reducing packet data latency, as the time unit for transmission can be reduced e.g., from 1 ms (e.g., approximately 14 OFDM symbols) and the delay caused by decoding can be reduced as well. However, while efforts are being made to improve packet data latency for wireless medication systems, reducing the length of TTI can have significant impacts on current system design as the physical channels are developed based on 1 ms subframe structure, as described above. In addition, reducing the length of TTI can also have significant impacts for scheduling and transmission via physical downlink shared channel (PDSCH) and physical uplink shared channel (PUSCH) with such shortened TTI, due to PDCCH competition and/or short TTI (sTTI) inequality.

Accordingly, non-limiting embodiments as described herein can provide control channel structures and/or techniques that facilitate reduction of transmission time intervals in wireless communication systems, which can provide opportunities to reduce packet data latency, which can improve performance of wireless communication systems, while avoiding and/or mitigating significant impacts for scheduling and transmission via PDSCH and PUSCH with such shortened TTI, due to PDCCH competition and/or sTTI inequality.

As non-limiting examples, exemplary control structures and techniques for TTI shortening are provided. Exemplary techniques can comprise establishing a UE device connection to a base station having a first TTI, wherein the UE device is configured to employ TTI shortening and has a second TTI different from the first TTI and monitoring a first short physical downlink control channel (PDCCH) region for a scheduled downlink (DL) transmission via the second TTI, wherein a time distribution associated with multiple second TTIs within the first TTI is determined based on a control format indicator (CFI) value indicated via the first TTI. Exemplary techniques can further comprise receiving a DL transmission via the second TTI and transmitting a hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback on a channel of an associated UL for HARQ-ACK feedback, wherein for the number of DL transmissions via the second TTI within one of the first TTI on the associated DL, the number of channels of the associated UL for HARQ-ACK feedback occur within the same one of the first TTI on the associated UL. Further non-limiting control structures and techniques for TTI shortening are described.

While a brief overview has been described above in order to provide a basic understanding of some aspects of the specification, various non-limiting devices, systems, and methods are now described as a further aid in understanding the advantages and benefits of various embodiments of the disclosed subject matter. To that end, it can be understood that such descriptions are provided merely for illustration and not limitation.

Various embodiments of the subject disclosure described herein can be applied to or implemented in exemplary wireless communication systems and devices described below. In addition, various embodiments of the subject disclosure are described mainly in the context of the 3GPP architecture reference model. However, it is understood that with the disclosed information, one skilled in the art could easily adapt for use and implement aspects of the subject disclosure in a 3GPP2 network architecture as well as in other network architectures, as further described herein.

FIG.1is a block diagram representing an exemplary non-limiting multiple access wireless communication system100in which various embodiments described herein can be implemented. An access network102(AN) includes multiple antenna groups, one group including antennas104and106, another group including antennas108and110, and an additional group including antennas112and114. InFIG.1, only two antennas are shown for each antenna group, however, more or fewer antennas may be utilized for each antenna group. Access terminal116(AT) is in communication with antennas112and114, where antennas112and114transmit information to access terminal116over forward link118and receive information from access terminal116over reverse link120. Access terminal (AT)122is in communication with antennas106and108, where antennas106and108transmit information to access terminal (AT)122over forward link124and receive information from access terminal (AT)122over reverse link126. In a Frequency Division Duplex (FDD) system, communication links118,120,124and126may use different frequency for communication. For example, forward link118may use a different frequency than that used by reverse link120.

Each group of antennas and/or the area in which they are designed to communicate is often referred to as a sector of the access network. In non-limiting aspects, antenna groups each can be designed to communicate to access terminals in a sector of the areas covered by access network102.

In communication over forward links118and124, the transmitting antennas of access network102may utilize beamforming in order to improve the signal-to-noise ratio of forward links for the different access terminals116and122. Also, an access network using beamforming to transmit to access terminals scattered randomly through its coverage normally causes less interference to access terminals in neighboring cells than an access network transmitting through a single antenna to all its access terminals.

An access network (AN) may be a fixed station or base station used for communicating with the terminals and may also be referred to as an access point, a Node B, a base station, an enhanced base station, an eNodeB, or some other terminology. An access terminal (AT) may also be called user equipment (UE), a communication device, a wireless communication device, a mobile device, a mobile communication device, a terminal, an access terminal or some other terminology.

FIG.2is a simplified block diagram of an exemplary non-limiting MIMO system200depicting an exemplary embodiment of a transmitter system202(also referred to herein as the access network) and a receiver system204(also referred to herein as an access terminal (AT) or user equipment (UE)), suitable for incorporation of various aspects directed to sTTIs described herein.

In a non-limiting aspect, each data stream can be transmitted over a respective transmit antenna. Exemplary TX data processor206can format, code, and interleave the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.

The coded data for each data stream may be multiplexed with pilot data using OFDM techniques. The pilot data is typically a known data pattern that is processed in a known manner and may be used at the receiver system204to estimate the channel response. The multiplexed pilot and coded data for each data stream is then modulated (e.g., symbol mapped) based on a particular modulation scheme (e.g., binary phase-shift keying (BPSK), quadrature phase shift keying (QPSK), M-ary or higher-order PSK (M-PSK), or M-ary quadrature amplitude modulation (M-QAM), etc.) selected for that data stream to provide modulation symbols. The data rate, coding, and modulation for each data stream may be determined by instructions performed by processor208.

The modulation symbols for all data streams are then provided to a TX MIMO processor210, which may further process the modulation symbols (e.g., for OFDM). TX MIMO processor210then provides multiple (NT) modulation symbol streams to NT transmitters (TMTR)212athrough212t. In certain embodiments, TX MIMO processor210applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.

Each transmitter212receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts, etc.) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel. NT modulated signals from transmitters212athrough212tare then transmitted from NT antennas214athrough214t, respectively.

At receiver system204, the transmitted modulated signals are received by multiple (NR) antennas216athrough216rand the received signal from each antenna216is provided to a respective receiver (RCVR)218athrough218r. Each receiver218conditions (e.g., filters, amplifies, and downconverts, etc.) a respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding “received” symbol stream.

A RX data processor220then receives and processes the NR received symbol streams from NR receivers218based on a particular receiver processing technique to provide NT “detected” symbol streams. The RX data processor220then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream. The processing by RX data processor220is complementary to that performed by TX MIMO processor210and TX data processor206at transmitter system202.

A processor222periodically determines which pre-coding matrix to use, for example, as further described herein. Processor222formulates a reverse link message comprising a matrix index portion and a rank value portion.

The reverse link message may comprise various types of information regarding the communication link and/or the received data stream. The reverse link message is then processed by a TX data processor224, which also receives traffic data for a number of data streams from a data source226, modulated by a modulator228, conditioned by transmitters218athrough218r, and transmitted back to transmitter system202.

At transmitter system202, the modulated signals from receiver system204are received by antennas214, conditioned by receivers212, demodulated by a demodulator230, and processed by a RX data processor232to extract the reserve link message transmitted by the receiver system204. Processor208then determines which pre-coding matrix to use for determining the beamforming weights then processes the extracted message.

Memory234may be used to temporarily store some buffered/computational data from230or232through Processor208, store some buffed data from data source236, or store some specific program codes, for example, as further described herein, for example, regardingFIGS.15-18. Likewise, memory238may be used to temporarily store some buffered/computational data from RX data processor220through processor222, store some buffed data from data source226, or store some specific program codes, for example, as further described herein, for example, regardingFIGS.15-18.

As described above, deficiencies of conventional control channel structures and/or transmission time intervals in wireless communication systems can provide opportunities to reduce packet data latency, which can improve performance of wireless communication systems. As such, investigations to reduce latency in LTE networks have been undertaken to study enhancements to the E-UTRAN radio system in order to significantly reduce the packet data latency over the LTE Uu air interface for an active UE and significantly reduce the packet data transport round trip latency for UEs that have been inactive for a longer period (in connected state), and for both FDD) and TDD modes, for example, in 3GPP RP-150465, “New SI proposal: Study on Latency reduction techniques for LTE”, Ericsson, Huawei, the entirety of which is incorporated herein by reference.

Among other things, the study is assessing specification impact, feasibility, and performance of TTI lengths between 0.5 ms and one OFDM symbol, taking into account impact on reference signals and physical layer control signaling. As described above, TTI shortening and processing time reduction can be considered for solutions that can facilitate reducing packet data latency, as the time unit for transmission can be reduced e.g., from 1 ms (e.g., approximately 14 OFDM symbols) and the delay caused by decoding can be reduced as well. As further described herein, reducing the length of TTI can also have significant impacts on current system design as the physical channels are developed based on 1 ms subframe structure. Thus, non-limiting embodiments as described herein can provide control channel structures and/or techniques that facilitate reduction of transmission time intervals in wireless communication systems, which can provide opportunities to reduce packet data latency, which can improve performance of wireless communication systems, while avoiding and/or mitigating significant impacts for scheduling and transmission via PDSCH and PUSCH with such shortened TTI, due to PDCCH competition and/or sTTI inequality.

As further described above, for control channels, the region occupied by PDCCH is usually named as control region, and the rest part of the subframe is usually known as data region, whereas ePDCCH, occupies the data region in the time domain, while typically occupying only part of the bandwidth in the frequency domain, for example, as further described in 3GPP TS 36.213 v13.1.1, “E-UTRA Physical layer procedures (Release 13)”, and 3GPP TR 36.211 V13.1.0, “E-UTRA Study on latency reduction techniques for LTE (Release 13)”, the entireties of which are incorporated herein by reference. Among other things, these describe control format indicator (CFI) assignment procedures, physical control format indicator channel (PCFICH), which carries information about the number of OFDM symbols used for transmission of PDCCHs in a subframe, resource-element groups (REGs) used for defining the mapping of control channels to resource elements, enhanced resource-element groups (EREGs) used for defining the mapping of enhanced control channels to resource elements, and formats for EPDCCH, which carries scheduling assignments.

Thus, it is understood that downlink control information (DCI) would be carried on one or more control channel, e.g., PDCCH/ePDCCH. For instance, DCI may be used to carry scheduling for downlink data or uplink data. In addition, DCI may also be used carry special messages, e.g., triggering some procedure or control UE power, from eNB to the UE, etc. Conventionally, different DCI formats exist to serve aforementioned different purposes. As an example using downlink data scheduling, DCI for downlink data scheduling may comprise the resource allocation (in the frequency domain), modulation and coding scheme, redundancy version, HARQ process ID, and other information require to perform the reception, for example, as further described in 3GPP TS 36.212 V13.1.0, “E-UTRA Multiplexing and channel coding (Release 13)”, the entirety of which is incorporated herein by reference, which, among other things, describes conventional DCI formatting.

As a result, because different DCI formats may have different payload sizes and a UE may need to acquire different DCI formats, the UE is required to decode several decoding candidates without knowing which or whether candidate exist, which is known as blind decoding. The resource of decoding candidate(s) is known as a search space of the UE, and the search space is further partitioned to common search space and UE specific search space which may contain different type of messages. Within search space, the UE may search for different DCI format. Also, within search space, the UE would monitor control channel addressed different identifier, e.g., Radio Network Temporary Identifier (RNTI), which can be done by descrambling cyclic redundancy check (CRC) of a decoding candidate with different RNTI and check which one would pass the check, for example, similar to related procedures described in 3GPP TS 36.213 v13.1.1, “E-UTRA Physical layer procedures (Release 13)”, and 3GPP TS 36.212 V13.1.0, “E-UTRA Multiplexing and channel coding (Release 13),” directed to UE monitoring of PDCCH/ePDCCH and assignment, UE receiving and decoding PDCCH/ePDCCH and corresponding PDSCH, DCI composition and coding, and so on.

Accordingly, it is understood that timing relationships between control channel and data channel is specified in LTE. For instance, when a UE receives a control channel in a subframe, n, for scheduling downlink data, the associated downlink data would located in the data region of the same subframe, n. And it would transmit corresponding HARQ feedback in a specific subframe after the reception, e.g., in subframe, n+4. For the downlink data reception, asynchronous HARQ is applied, e.g., the retransmission timing is not tied to the feedback timing. Therefore, HARQ process ID would be required for the DL data scheduling. For the UL data scheduling, when a UE receives a control channel in a subframe, n, for scheduling uplink data, the associated downlink data would located in subframe, n+4. For UL data, there is no control region as the control/data are multiplexed in frequency domain and UL data can occupy all symbols in a subframe within the allocated resource, except for those may be occupied by reference signal (RS). And it would expect corresponding HARQ feedback or a retransmission grant in a specific subframe after the reception, e.g., in subframe, n+4. For the uplink data transmission, synchronous HARQ is applied, e.g., the retransmission timing is tied to the feedback timing. Therefore, HARQ process ID is not required for the UL data scheduling. Such detail timing and related procedures are described, for example, in 3GPP TS 36.213 v13.1.1, “E-UTRA Physical layer procedures (Release 13)”, directed to UE procedures for receiving/transmitting PDSCH/PUSCH, Physical Hybrid-ARQ Indicator Channel (PHICH) assignment procedures, and UL HARQ-ACK timing, etc.

As a result of these and further studies, a control signal, sPDCCH (PDCCH for short TTI), is proposed to accommodate the shorter TTI length, and in addition, it is proposed that short TTI on DL may contain sPDCCH decoding candidates, where a maximum number of blind decondings (BDs) will be defined for sPDCCH in UE-specific search space (USS) and where any DCI for sTTI scheduling carried on PDCCH may be taken into account in the maximum total number of BDs, in the event that 2-level DCI is adopted.

Besides the timing domain structure, a two-level DCI structure is proposed to minimize anticipated increase of control overhead when employing shortened TTI, for example such as described for a slow DCI and a fast DCI with TTI structures with different TTI lengths in R1-163068, “DL channel design for shortened TTI”, Qualcomm Incorporated, the entirety of which is incorporated herein by reference.

That is, instead of carrying all the information required for one TTI data reception as in conventional systems, some control information in a DCI, called slow DCI, which may not vary from time to time may be common for multiple TTI and could be signaled once, but not in every TTI, for which UE would assume the same content applied for multiple TTIs, for example, as described below regardingFIG.4. As there would still be some information which would vary between TTIs, some control information in a DCI, called fast DCI, would be signal for each TTI, for example, as described below regardingFIG.4. For receiving data in one TTI, UE may need to combine/concatenate slow DCI and fast DCI to obtain the required information.

For instance, for a proposed two-level DCI, slow DCI, can comprise DCI content, which applies to more than one sTTI and can be carried on either legacy PDCCH, or sPDCCH transmitted not more than once per subframe, whereas fast DCI can comprise DCI content, which applies to a specific sTTI and can be carried on sPDCCH. In addition, for a sPDSCH in a given sTTI, the scheduling information is obtained from either a combination of slow DCI and fast DCI, or fast DCI only, overriding the slow DCI for that sTTI.

Furthermore, it is proposed, regarding handling transmissions with different TTI length, UE can be expected to handle, in the same carrier in a subframe, receiving legacy TTI non-unicast PDSCH and short TTI unicast PDSCH, and receiving legacy TTI non-unicast PDSCH and legacy TTI unicast PDSCH(s). In addition, it is proposed that a UE can be dynamically scheduled (with subframe to subframe granularity) with PUSCH and/or sPUSCH, but a UE is not expected to transmit PUSCH and sPUSCH simultaneously on the same resources, e.g., by superposition.

Accordingly, while an overview of relevant technologies has been described above in order to provide a basic understanding of some aspects of the specification, various non-limiting devices, systems, and methods are now described as a further aid in understanding the advantages and benefits of various embodiments of the disclosed subject matter.

FIG.3depicts an exemplary instance of a short TTI (sTTI) pattern300in the time domain, demonstrating a potential for interference or gaps302or unused resources, wherein some resources in the gap302cannot be utilized by sPDCCH/sPDSCH/PDCCH, without control format indicator (CFI) consideration, according to non-limiting aspects. As described, for short TTI304, noted as sTTI, sPDCCH (or PDCCH for sTTI) (not shown) is designed for at least scheduling DL data or UL data transmission. Each sTTI304on DL may contain sPDCCH decoding candidates. The sPDSCH scheduled by a sPDCCH may be allocated to unused resources in the scheduled sTTI304wherein the sPDCCH and sPDSCH are TDM. The frequency resources of the sPDSCH and the sPDCCH may be the same, but the symbols of the sPDSCH and the sPDCCH are separated within one sTTI304.

Firstly, for acquiring sPDCCH and/or sPDSCH, a UE (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) requires the sTTI pattern/sPDCCH pattern to know how sTTIs/sPDCCHs are distributed within a subframe306. Since the sPDCCH region is improper to overlap with PDCCH region308(as indicated in310), a fixed sTTI pattern may induce interference or gap considering different PDCCH region308. As shown inFIG.3, if PDCCH region308is one symbol, the symbol #1312results in a gap wherein some resources in the gap302cannot be utilized by sPDCCH/sPDSCH/PDCCH. If PDCCH region308is three symbols, it induces interference in symbol #2314if the overlapped sTTI304transmission transmits or it induces gap302in symbol #3 #4 if the overlapped sTTI304transmission does not transmit. Thus, CFI value representing PDCCH region308size may be considered for determine sTTI pattern, in a non-limiting aspect. The CFI consideration can not only avoid collision between sPDCCH region (not shown) and PDCCH region308, but also avoid gap302generation, in a further non-limiting aspect. Thus,FIG.3depicts an instance of sTTI304pattern without CFI consideration. For indicating sTTI pattern/sPDCCH pattern in time domain, there are some alternatives, in still other non-limiting aspects.

As a non-limiting example, an exemplary sTTI/sPDCCH pattern can be indicated by CFI, for example, as further described herein. For instance, when a UE (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) is configured with TTI shortening, the UE can be configured to derive the sTTI/sPDCCH pattern based at least in part on the CFI value in the subframe306. In a non-limiting aspect, corresponding sTTI/sPDCCH patterns could be different for different CFI values. In yet another non-limiting aspect, the sTTI/sPDCCH pattern for a specific CFI value may be configured via a higher layer or specified. Moreover, the sTTI/sPDCCH pattern may be relevant to the configured sTTI304size. Furthermore, some CFI values may mean that there is no short TTI304scheduling or no sPDCCH transmission in the subframe306. For instance, if a UE configured with TTI shortening detects CFI=1 or 3, for example, the UE can be configured to neither monitor sPDCCH nor receive sPDSCH in the subframe306.

As a further non-limiting example, an exemplary sTTI/sPDCCH pattern can be indicated by CFI and a special PDCCH, for example, as further described herein. In an exemplary embodiment, the special PDCCH can be configured to indicate how sTTIs/sPDCCHs are distributed within a subframe306, except the PDCCH region308indicated by CFI, in a non-limiting aspect. Furthermore, a field in DCI content carried on the special PDCCH can be configured to indicate the sTTI/sPDCCH pattern, in a further non-limiting aspect. In addition, for different CFI values, a field value may be configured to correspond to different sTTI/sPDCCH pattern, in yet another non-limiting aspect.

As yet another non-limiting example, an exemplary sTTI/sPDCCH pattern can be indicated by a special PDCCH, for example, as further described herein. An exemplary special PDCCH can be configured to indicate how sTTIs/sPDCCHs are distributed within a subframe306, for example, as further described above. Furthermore, a field in DCI content carried on the special PDCCH can be configured to indicate the sTTI/sPDCCH pattern, as described above. In addition, for different CFI values, a field value may be configured to correspond to the same sTTI/sPDCCH pattern. Moreover, an exemplary network can be configured to determine sTTI/sPDCCH pattern considering PDCCH region308size. In this non-limiting example, it is noted that it is possible to induce a timing gap302wherein some resources in the timing gap302cannot be utilized by sPDCCH/sPDSCH/PDCCH.

FIG.4illustrates an exemplary 2-stage downlink control information (DCI) structure400comprising an exemplary slow DCI402for PDCCH308, and an exemplary fast DCI404for sPDCCH406, and sPDSCH408, in further non-limiting aspects. Secondly, for sPDCCH406scheduling, two-level DCI structure can be employed to facilitate reducing DL control overhead when TTI shortening is configured for a UE (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.). The slow DCI402may carry the common DCI content which applies to more than one sTTI304within a subframe306, as further described herein. The slow DCI402may be UE-specific or common for multiple UEs and may be transmitted on legacy PDCCH or sPDCCH406transmitted not more than once per subframe306, as described above. As further described above, the fast DCI404may be transmitted on sPDCCH406and can be configured to carry DCI content that applies to a specific sTTI304.

The UE (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) can know sPDCCH406decoding candidates for fast DCI404based on sTTI/sPDCCH pattern, in a non-limiting aspect. The special PDCCH described above may be the PDCCH carrying slow DCI402. That is, the slow DCI402received in a subframe306can be configured to include the information of sTTI/sPDCCH pattern for the subframe306. Thus,FIG.4shows a structure instance of slow DCI402on PDCCH, fast DCI404on sPDCCH406, and sPDSCH408. The frequency resource allocation information for the sPDCCH406and/or sPDSCH408may be included in the slow DCI402, in a non-limiting aspect. However, available resources for sPDSCH408are restricted by the interval of sPDCCH406occasions. As a result, to obtain more flexibility of available sPDSCH408resources, available OFDM symbol occasions for a scheduled sPDSCH408can be indicated by the scheduling sPDCCH406, in a further non-limiting aspect. As a result, an exemplary sPDCCH406can have flexibility to perform timing scheduling, including number of OFDM symbols and/or the OFDM symbol occasions, for a scheduled sPDSCH408, in various non-limiting embodiments.

As a non-limiting example,FIG.5depicts an exemplary resource scheduling pattern500in the time domain for available sPDSCH408resources, wherein available OFDM symbol occasions for a scheduled sPDSCH408can be indicated by a scheduling sPDCCH406in addition to timing scheduling, including number of OFDM symbols, OFDM symbol occasions, etc. for a scheduled sPDSCH408, in further non-limiting aspects. Thus, as an instance for UEs (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) 502512, shown inFIG.5, the sPDCCH1 (sP1) for UE1502indicate one OFDM symbol for the scheduled sPDSCH1 (D1); the sPDCCH2 (sP2) for UE2504indicates two OFDM symbols for the scheduled sPDSCH2 (D2); the sPDCCH3 (sP3) for UE3506indicates one OFDM symbol occasion for the scheduled sPDSCH3 (D3); the sPDCCH4 (sP4) for UE4508indicates three OFDM symbol occasions for the scheduled sPDSCH4 (D4), and so on. Thus, the network could utilize sPDCCH406resources for sPDSCH408transmission, and it could be transparent to UEs, except the scheduled UEs502-512.

Thirdly, determining the associated sPUCCH resources for HARQ-ACK feedback after a UE (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) receives sPDCCH406and/or sPDSCH408transmission can be performed as described herein, in further non-limiting aspects. For instance, considering that TTI shortening can induce processing time reduction on sPDCCH/sPDSCH, the earliest timing for a HARQ-ACK feedback may be N×sTTIDLafter sPDCCH406and/or sPDSCH408reception. The sTTIDLmay be the sTTI length for DL, including a sPDCCH406transmission and an associated sPDSCH408transmission. As further described herein, some alternatives for sPUCCH resources (not shown) derivation for HARQ-ACK feedback are provided in further non-limiting aspects. Note that, for purposes of describing alternatives for sPUCCH resources derivation for HARQ-ACK feedback, the DL sTTI length may be different from the UL sTTI length.

In a first non-limiting example (denoted Alternative i inFIGS.6-8), when a UE (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) receives sPDCCH406and/or sPDSCH408in a sTTI304, the associated sPUCCH resource for HARQ-ACK feedback can be the first available sPUCCH after N×sTTIDL, and in a non-limiting aspect, N=3. For the non-limiting case where DL sTTI304length is larger than or equal to UL sTTI304length, there may be some UL sTTIs304without associated sPDCCH406and/or sPDSCH408reception. Accordingly, in a further non-limiting aspect, to balance the sPUCCH resource utilization, a time offset/delay can be introduced for sPUCCH resource determination. For instance, if the time offset/delay is zero, the associated sPUCCH resource is the first available sPUCCH after N×sTTIDL, in a non-limiting aspect. In a further non-limiting aspect, if the time offset/delay is not zero, e.g., one, etc. the associated sPUCCH resource is the next one of the first available sPUCCH after N×sTTIDL. Thus, an exemplary time offset/delay can be configured or indicated in sPDCCH406or indicated in slow DCI402. With an exemplary time offset/delay, the network can be configured to multiplex two sPDCCH406regions separated in frequency domain into the same sPUCCH region via time-division multiplexing, in yet another non-limiting aspect. Furthermore, the frequency resource allocation of sPDCCH406region can be configured or indicated via slow DCI402on PDCCH addressed via a special RNTI, as further described herein. In another non-limiting aspect, different UEs can be configured with different sPDCCH406regions in frequency domain or configured with different special RNTI for slow DCI402detection. In addition, an exemplary time offset/delay can also be utilized for avoiding collision of sPUCCH and SRS. Note that the multiple sPDSCH408transmissions in different sTTIs304within one DL subframe may not be associated with sPUCCH resources for HARQ-ACK feedback within the same UL subframe, however.

In a second non-limiting example (denoted Alternative ii inFIGS.6-8), multiple sPDSCH408transmissions in different sTTIs304within one DL subframe can be associated into sPUCCH resources for HARQ-ACK feedback within one UL subframe. For instance, subframe-based association can be readily configured for network scheduling, in further non-limiting aspects. For example, one exemplary embodiment can comprise a UE (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.), which can be configured to receive sPDCCH406and/or sPDSCH408in a sTTI304, wherein the associated sPUCCH resource for HARQ-ACK feedback is the first available sPUCCH after N×sTTIDL+k, wherein k induces same UL subframe association for all sPDSCH408transmissions in different sTTIs304within one DL subframe. In another exemplary embodiment, a UE can be configured to receive sPDCCH406and/or sPDSCH408in a sTTI304, wherein the associated sPUCCH resource for HARQ-ACK feedback is within some time offset/delay of the first available sPUCCH after N×sTTIDL, in a further non-limiting aspect. An exemplary time offset/delay can be specified, configured, and/or indicated via L1 signaling, such that same UL subframe association for all sPDSCH408transmissions in different sTTIs304within one DL subframe, in yet another non-limiting aspect.

As non-limiting examples,FIGS.6-8depict non-limiting instances demonstrating exemplary difference between the two non-limiting examples described above. As a non-limiting example,FIG.6depicts an exemplary aspect of a non-limiting resource scheduling pattern600demonstrating exemplary sPUCCH resources derivation after a UE (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) receives sPDCCH406and/or sPDSCH408transmission, wherein DL sTTI (including sPDCCH406and sPDSCH408) is greater than sTTI of sPUCCH, in further non-limiting embodiments. Note that an exemplary time offset/delay can be set differently for slow DCI402on PDCCH308addressed via different special RNTI602604, as further described herein. In addition, note that Dijrefers to j-th sTTI DL transmission, which comprises sPDCCH406and sPDSCH408, wherein the sPDCCH406region in frequency domain is indicated via slow DCI402on PDCCH308addressed via a special RNTI-i (e.g., RNTI602604), in a non-limiting aspect. Note further that Uijrefers to the sPUCCH606transmission associated with Dij. The time offset/delay is zero for slow DCI402on PDCCH308addressed via special RNTI1, and is not zero, e.g., one, for slow DCI402on PDCCH308addressed via special RNTI2.

As another non-limiting example,FIG.7depicts an exemplary aspect of a non-limiting resource scheduling pattern700demonstrating exemplary sPUCCH resources derivation after a UE (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) receives sPDCCH406and/or sPDSCH408transmission, wherein DL sTTI (including sPDCCH406and sPDSCH408) equal to sTTI of sPUCCH, in still further non-limiting embodiments. Thus, in a non-limiting aspect, exemplary time offset/delay, k sTTI of sPUCCH, after considering processing time, can facilitate ensuring that all sPDSCH408transmissions within one DL subframe are associated with the sPUCCH resources for HARQ-ACK feedback within one UL subframe. In addition, note that Djrefers to j-th sTTI DL transmission (e.g., sTTI DL transmission702), which comprises sPDCCH406and sPDSCH408, and Ujrefers to the sPUCCH transmission associated with Dj(e.g., sPUCCH transmission704). Note further that U(k) refers to associated sPUCCH resource Ujis with additional time offset/delay, k sTTI of sPUCCH, after considering processing time (e.g., sPUCCH706). The time offset/delay ensures that all sPDSCH408transmissions within one DL subframe are associated with the sPUCCH resources within one UL subframe.

FIG.8depicts an exemplary aspect of a non-limiting resource scheduling pattern800demonstrating exemplary sPUCCH resources derivation after a UE (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) receives sPDCCH406and/or sPDSCH408transmission, wherein DL sTTI (including sPDCCH406and sPDSCH408) is less than sTTI of sPUCCH, in yet another non-limiting embodiment. According to further non-limiting aspects, different time offset/delay for different reception times of sPDCCH406and/or sPDSCH408can ensure that all sPDSCH408transmissions within one DL subframe are associated with the sPUCCH resources for HARQ-ACK feedback within one UL subframe. For instance, note that Djrefers to j-th sTTI DL transmission which comprises sPDCCH406and sPDSCH408(e.g., sTTI DL transmission802), and Ujrefers to the sPUCCH transmission associated with Dj (e.g., sPUCCH transmission804)). Note further that two exemplary sPUCCH transmissions within one sTTI of sPUCCH can be separated via CDM or FDM, in a non-limiting aspect. In addition, note that associated sPUCCH resource Ujis within additional time offset/delay after considering processing time, in another non-limiting aspect. Furthermore, different Ujcan have different time offset/delay, for example, as described herein, to facilitate ensuring that all sPDSCH408transmissions within one DL subframe are associated with the sPUCCH resources within one UL subframe.

It can be understood that, for scheduling sPUSCH transmission, since an exemplary one symbol sPDCCH406region may not be able to accommodate more than one sPDCCH406transmissions, the sPUSCH and sPDSCH408scheduling may be competitive and/or mutually exclusive. In addition, increasing frequency resources of the sPDCCH406region for accommodating more than one sPDCCH406may restrict sPDSCH408to use the same increased frequency resources for sPDSCH408, which can result in inefficient resource utilization. Moreover, exemplary sPUSCH can utilize different sTTI lengths from DL sTTI length, as further described herein. Furthermore, because sPDCCH406occasions are relevant to DL sTTI, including sPDCCH406and sPDSCH408, network scheduling of sPUSCH transmissions without unequal sPDCCH406occasions would be complex.

Accordingly, further non-limiting embodiments can facilitate scheduling sPUSCH transmission, for example, by separating sPDCCH406regions for scheduling sPUSCH and sPDSCH408transmission, in further non-limiting aspects. For instance, an exemplary sPDCCH406region for scheduling sPDSCH408can be frequency divided from the sPDCCH406region for scheduling sPUSCH. In a further non-limiting aspect, an exemplary sPDCCH406region for scheduling sPUSCH can comprise sPDCCH406carrying an UL grant, wherein a sPDCCH406can be carried on part of the symbol(s) within the duration of the DL data channel (e.g., the PDSCH region). More specifically, duration of the DL data channel can be the remaining region excluding PDCCH region308within one subframe. In a non-limiting aspect, there is neither sPDCCH406carrying DL assignment nor sPDSCH408within the sPDCCH406region for scheduling sPUSCH. In addition, there is no sPDCCH406carrying an UL grant within the sPDCCH406region for scheduling sPDSCH408. Accordingly, a sPDSCH408scheduled by a sPDCCH406can be allocated to unused resources within the same frequency resources as the scheduling sPDCCH406region for the sPDSCH408.

FIG.9illustrates an exemplary 2-stage DCI structure900comprising an exemplary slow DCI for PDCCH308, an exemplary fast DCI for sPDCCH408, wherein the sPDCCH406region for scheduling sPDSCH408can be frequency divided from the sPDCCH902region for scheduling sPUSCH904, according to further non-limiting aspects. Thus,FIG.9depicts an instance of the frequency divided structure of separated sPDCCH regions (e.g., sPDCCH406and sPDCCH902) for scheduling sPUSCH904and sPDSCH408transmission. In a non-limiting aspect, the separated sPDCCH regions (e.g., sPDCCH406and sPDCCH902) for scheduling sPUSCH904and sPDSCH408transmission are not overlapped in frequency domain. One frequency resources region is utilized for sPDCCH406for scheduling sPDSCH408and the scheduled sPDSCH408transmission. The scheduling sPDCCH406and the scheduled sPDSCH408are transmitted within one DL sTTI304. Another frequency resources region is utilized only for sPDCCH902for scheduling sPUSCH904. From the perspective of an exemplary eNB, available sPDCCH(s)406occasions for scheduling sPDSCH408within the one sPDCCH406region is smaller than the available sPDCCH(s)902occasions for scheduling sPUSCH904within the another one sPDCCH406region, in a further non-limiting aspect.

In non-limiting embodiments, frequency resource allocation information for the sPDCCH902region for scheduling sPUSCH904can be included in slow DCI, as further described herein. Exemplary multiple sPDCCHs902for scheduling sPUSCHs904for different UEs (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) can be multiplexed via one or more of FDM, TDM, and/or combinations thereof. Considering UE search space design for monitoring sPDCCH902candidates, a UE can be configured to monitor all or substantially all OFDM symbols within the sPDCCH902region for scheduling sPUSCH904, in a non-limiting aspect. In other non-limiting aspects, a UE (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) can be configured to monitor parts of the OFDM symbols within the sPDCCH902region for scheduling sPUSCH904, in still further non-limiting aspects. In addition, determination on the parts of the OFDM symbols can depend on the sTTI304length and/or sTTI304pattern of sPUSCH904for the UE. As a non-limiting example, parts of the OFDM symbols can be separated with an interval equal to sPUSCH904sTTI304length. Moreover, to facilitate accommodation of the search space of multiple UEs, an exemplary time offset/symbol offset can be utilized to time-division multiplex multiple search spaces within a sPDCCH region902for scheduling sPUSCH904. Furthermore, parts of OFDM symbols for sPDCCH902monitoring may be indicated in the slow DCI, as further described herein. As a non-limiting example, exemplary slow DCI can be configured to include information of sPDCCH902pattern and/or one or more of sPUSCH904sTTI length, time offset, symbol offset, and/or combinations thereof.

In yet another non-limiting aspect, when a UE (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) receives sPDCCH902which schedules sPUSCH904transmission, it needs to determine the associated UL sTTI (not shown) for scheduled sPUSCH904transmission. Considering that the TTI shortening may induce processing time reduction on preparing sPUSCH signaling, the earliest associated sTTI for sPUSCH904transmission may be N′×sTTIULafter sPDCCH902reception. The sTTIULmay be the sTTI length for sPUSCH904transmission or the interval of monitored sPDCCH902occasions. Thus, various embodiments described herein can facilitate providing for such sPUSCH904resources derivation.

As a non-limiting example (denoted as Alternative I inFIGS.10-11), when a UE (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) receives sPDCCH902which schedules sPUSCH904transmission, an associated sPUSCH904resource can be the first available sPUSCH904after N′×sTTIUL, and in a non-limiting aspect, N′=3. Because an sPDCCH902region can utilize the DL OFDM symbols except for a legacy PDCCH region, there may be some sPUSCH904sTTIs (not shown) without associated sPDCCH902reception. Accordingly, in a non-limiting aspect, embodiments described herein, can facilitate balancing sPUSCH904resource utilization, by employing a UL time offset for some sPDCCH902occasions considering sPUSCH904resource determination. for instance, if the UL time offset/delay is zero, the associated sPUSCH904resource is the first available sPUSCH904after N′×sTTIUL, in a non-limiting aspect. In another non-limiting aspect, if the UL time offset/delay is not zero, e.g., one, etc., the associated sPUSCH904resource is the next one of the first available sPUSCH904after N′×sTTIUL. Accordingly, an exemplary UL time offset/delay can be configured or indicated in sPDCCH902, as described herein. Note that the multiple sPDCCH902in different sTTIs within one DL subframe may not be associated with sPUSCH904resources within the same UL subframe.

Thus, as another non-limiting example (denoted as Alternative II inFIGS.10-11) multiple sPDCCH902in different sTTIs within one DL subframe can be associated into sPUSCH904resources within one UL subframe. For instance, subframe-based association can be readily configured for network scheduling. As an exemplary embodiment, when a UE (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) receives sPDCCH902scheduling sPUSCH904transmission, the associated sPUSCH904resource can be the first available sPUSCH904after N′×sTTIUL+k′, wherein k induces same UL subframe association for all sPDCCH902transmissions in different sTTIs within one DL subframe. In another non-limiting embodiment, when a UE receives sPDCCH902scheduling sPUSCH904transmission, associated sPUSCH904resource can be within some exemplary UL time offset/delay of the first available sPUSCH904after N′×sTTIUL, in a further non-limiting aspect. Accordingly, exemplary UL time offset/delay can be specified, configured, indicated via L1 signaling, for example, as described herein, such that all sPUSCH904transmissions within one UL subframe are associated with the sPDCCH902resources within one DL subframe.

As a non-limiting example,FIG.10depicts exemplary aspects of a non-limiting resource scheduling pattern1000demonstrating exemplary UE (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) determination of the associated UL sTTI for scheduled sPUSCH904transmission, after receiving sPDCCH902which schedules sPUSCH904transmission, to facilitate ensuring that all sPUSCH904transmissions within one UL subframe are associated with the sPDCCH902resources within one DL subframe, in further non-limiting embodiments. Thus,FIG.10depicts sPDCCH902and sPUSCH904association. For Alternative II, note that exemplary time offset/delay, k′ sTTI of sPUSCH904(or k intervals of sPDCCH902occasions), after considering processing time ensures that all sPUSCH904transmissions within one UL subframe are associated with the sPDCCH902resources within one DL subframe. Note further that a-f refers to the OFDM symbols for sPDCCH902monitoring for a UE (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.), and Ua-Ufrefers to the associated sPUSCH904transmission scheduled by sPDCCH902received in OFDM symbols a-f (e.g., a is associated with Ua, etc.). In addition, note that f is possibly associated with Uf1and Uf2. Thus, if the time offset/delay is zero, f is associated with Uf1, in a non-limiting aspect, otherwise, f is associated with Uf2, in a further non-limiting aspect. In addition, note that for Alternative II, U(k′) refers to the situation where the associated sPUSCH904Ua-Ufis with an exemplary time offset/delay,k′ sTTI of sPUSCH904(or k intervals of sPDCCH902occasions), after considering processing time. As result, an exemplary offset/delay can be configured to facilitate ensuring that all sPUSCH904transmissions within one UL subframe are associated with the sPDCCH902resources within one DL subframe.

In yet another non-limiting example,FIG.11depicts exemplary aspect of a non-limiting resource scheduling pattern1100demonstrating exemplary UE (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) determination of the associated UL sTTI for scheduled sPUSCH904transmission, after receiving sPDCCH902which schedules sPUSCH904transmission, to accommodate instances where the number of sPUSCH904occasions can be smaller than the number of sPDCCH902occasions, and where an sPUSCH904occasion may be associated with multiple possible sPDCCHs902occasions, in still further non-limiting embodiments. As a result,FIG.11depicts an instance where the number of sPUSCH904occasions is smaller than the number of sPDCCH902occasions. Thus, a sPUSCH904occasion Can be associated with multiple possible sPDCCHs902occasions. As the instance inFIG.11shows, the sPUSCH904occasion, Ua/Ub/Uc,1102, can be scheduled by sPDCCH902received in any of OFDM symbols a, b, c, in a further non-limiting aspect. In yet another non-limiting example, if the UE (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) has detected UL grant for scheduling a sPUSCH904transmission, the UE can be configured to skip detecting other sPDCCH902candidates which associate with the same sPUSCH904occasion of the scheduled sPUSCH904transmission. As the instance inFIG.10depicts, the processing time is assumed as N′×sTTIUL, wherein N′=3 and sTTIULis the intervals of the monitored sPDCCH902occasions. Note further that a-f refers to the OFDM symbols for sPDCCH902monitoring for a UE (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.), and Ua-Uf refers to the associated sPUSCH904transmission scheduled by sPDCCH902received in OFDM symbols a-f (e.g., a is associated with Ua, etc.). In addition, note that, since the number of sPUSCH904occasions is more than the number of sPDCCH902occasions, a sPUSCH904occasion can be associated with multiple possible sPDCCHs902occasions (e.g., the sPUSCH904occasion, Ua/Ub/Uc,1102, can be scheduled by sPDCCH902received in any of OFDM symbols a, b, c, in a non-limiting aspect. In a further non-limiting aspect, processing time is assumed as N′×sTTIUL, wherein N′=3 and sTTIULis the intervals of sPDCCH902occasions, as further described above.

In view of the example embodiments described, methods that can be implemented in accordance with the disclosed subject matter will be better appreciated with reference to the flowcharts ofFIGS.12-14, for example. While for purposes of simplicity of explanation, the methods are shown and described as a series of blocks, it is to be understood and appreciated that the claimed subject matter is not limited by the order of the blocks, as some blocks may occur in different orders and/or concurrently with other blocks from what is depicted and described herein. Where non-sequential, or branched, flow is illustrated via flowchart, it can be understood that various other branches, flow paths, and orders of the blocks, can be implemented which achieve the same or a similar result. Moreover, not all illustrated blocks may be required to implement the methods described hereinafter. Additionally, it should be further understood that the methods and/or functionality disclosed hereinafter and throughout this specification are capable of being stored on an article of manufacture to facilitate transporting and transferring such methods to computers, for example, as further described herein. The terms computer readable medium, article of manufacture, and the like, as used herein, are intended to encompass a computer program accessible from any computer-readable device or media such as a tangible computer readable storage medium.

FIG.12illustrates an example non-limiting flow diagram of methods1200for performing aspects of embodiments of the disclosed subject matter. For instance, referring toFIG.12, methods1200for TTI shortening can comprise, at1202, establishing with the UE device (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) a connection to a base station (e.g., a base station such as an access network102, a transmitter system202, and/or portions thereof, configured for TTI shortening, etc.) having a first TTI, wherein the UE device (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) is configured to employ TTI shortening and has a second TTI (e.g., sTTI304, etc.) different from the first TTI, as described herein. As a non-limiting example, exemplary methods1200can comprise establishing the connection to the base station having the first TTI comprising a subframe (e.g., subframe306). In a further non-limiting example, exemplary methods1200can comprise establishing the connection to the base station, wherein the UE device (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) has the second TTI (e.g., sTTI304, etc.) comprising one or more of a one symbol, a two symbol, a three symbol, a four symbol, or a seven symbol duration (e.g., sTTI304, etc.).

In addition, as described above, methods1200can further comprise, at1204, monitoring a first short PDCCH region (e.g., a region comprising first sPDCCH406, etc.) for a scheduled downlink (DL) transmission via the second TTI (e.g., sTTI304, etc.), wherein a time distribution associated with multiple second TTIs (e.g., sTIIs304, etc.) within the first TTI is determined based on a CFI value indicated via the first TTI, as further described herein. As a non-limiting example, exemplary methods1200can comprise monitoring the first short PDCCH region (e.g., a region comprising first sPDCCH406, etc.) via the second TTI (e.g., sTTI304, etc.), wherein the time distribution associated with the multiple second TTIs (e.g., sTTIs304, etc.) within the first TTI is based on one or more of a symbol size of a PDCCH region within the first TTI, a first PDCCH (e.g., first PDCCH402, etc.) received in the first TTI, or the CFI value indicated in the first TTI. In another non-limiting example, exemplary methods1200can comprise monitoring the first short PDCCH region (e.g., a region comprising first sPDCCH406, etc.) according to a time distribution for monitoring the first short PDCCH region (e.g., a region comprising first sPDCCH406, etc.) within a first TTI based on one or more of the symbol size of the PDCCH region within the first TTI, the first PDCCH (e.g., first PDCCH402, etc.) received in the first TTI, or the CFI value indicated in the first TTI.

In further non-limiting implementations, exemplary methods1200can comprise, at1206, detecting a first short PDCCH (e.g., first sPDCCH406, etc.). In still further non-limiting implementations, exemplary methods1200can comprise, at1208, determining one or more of a number of symbols or a number of symbol occasions for the scheduled DL transmission via the second TTI (e.g., sTTI304, etc.) based on the first short PDCCH (e.g., first sPDCCH406, etc.).

FIG.13illustrates an example non-limiting flow diagram of methods1300for performing aspects of embodiments of the disclosed subject matter. For instance, referring toFIG.13, methods1300for TTI shortening can comprise, at1302, establishing with the UE device (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) a connection to a base station (e.g., a base station such as an access network102, a transmitter system202, and/or portions thereof, configured for TTI shortening, etc.) having a first TTI for an associated DL and an associated UL, wherein the UE device (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) is configured to employ TTI shortening and has a second TTI (e.g., sTTI304, etc.) different from the first TTI, as further described herein. As a non-limiting example, exemplary methods1300can comprise establishing the connection to the base station having the first TTI comprising a subframe (e.g., subframe306). In a further non-limiting example, exemplary methods1300can comprise establishing the connection to the base station, wherein the UE device (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) has the second TTI (e.g., sTTI304, etc.) comprising one or more of a one symbol, a two symbol, a three symbol, a four symbol, or a seven symbol duration (e.g., sTTI304, etc.), for example, as further described above.

In addition, as described above, methods1300can further comprise, at1304, receiving a DL transmission via the second TTI (e.g., sTTI304, etc.), in further non-limiting aspects. In further non-limiting implementations, exemplary methods1300can comprise, at1306, transmitting hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback on an associated UL channel for HARQ-ACK feedback, wherein for a number of DL transmissions via the second TTI (e.g., sTTI304, etc.) within one of the first TTI on the associated DL, a number of associated UL channels for HARQ-ACK feedback occur within the same one of the first TTI on the associated UL, as further described herein. More specifically, for all of DL transmissions via the second TTI with one of the first TTI on the associated DL, all associated UL channels of the associated UL for HARQ-ACK feedback occur within the same one of the first TTI on the associated UL. As a non-limiting example, exemplary methods1300can comprise transmitting the HARQ-ACK feedback with subframe (e.g., subframe306) association for the associated UL for short PDSCH transmissions in different shortened TTIs within one DL subframe (e.g., subframe306), as further described herein. In a further non-limiting example, exemplary methods1300can comprise transmitting the HARQ-ACK feedback, wherein when detecting the first short PDCCH, the HARQ-ACK is transmitted on the associated UL channel for HARQ-ACK feedback with a first time offset of the first available associated UL channel for HARQ-ACK feedback after N×second TTI (e.g., sTTI304, etc.) length, where N is an integer, and wherein for the number of DL transmissions via the second TTI within one of the first TTI on the associated DL, a first time offset induces same association on the one of the first TTI on the associated UL, in still further non-limiting aspects.

In still further non-limiting implementations, exemplary methods1300can comprise, at1308, detecting with the UE device (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) a first short PDCCH (e.g., first sPDCCH406, etc.) for scheduling the DL transmission via the second TTI (e.g., sTTI304, etc.), in further non-limiting aspects.

In addition, exemplary method1300can comprise, at1310, transmitting the HARQ-ACK feedback of the at least the DL transmission, wherein when detecting the first short PDCCH, the HARQ-ACK is transmitted on a first available associated UL channel for HARQ-ACK feedback after N×second TTI (e.g., sTTI304, etc.) length+k, where N is an integer and where k is a value specified, configured, or indicated in the first sPDCCH or in a PDCCH received in the first TTI to induce subframe (e.g., subframe306) association for the associated UL for sPDSCH (e.g., sPDCCH406, sPDCCH902, etc.) transmissions in different shortened TTIs within one DL subframe (e.g., subframe306) or to balance sPUCCH resource utilization, in still further non-limiting aspects. For a number of DL transmissions via the second TTI within one of the first TTI on the associated DL, k induces same association on one of the first TTI on the associated UL, according to further non-limiting aspects. More specifically, for all of DL transmissions via the second TTI within one of the first TTI on the associated DL, k induces same association on one of the first TTI on the associated UL, according to further non-limiting aspects.

FIG.14illustrates an example non-limiting flow diagram of methods1400for performing aspects of embodiments of the disclosed subject matter. For instance, referring toFIG.14, methods1400for TTI shortening can comprise, at1402, establishing with a UE device (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) a connection to a base station (e.g., a base station such as an access network102, a transmitter system202, and/or portions thereof, configured for TTI shortening, etc.) having a first TTI for an associated DL and an associated UL, wherein the UE device (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) is configured to employ TTI shortening and having a third TTI (e.g., sTTI304, etc.) of a number of TTIs different from the first TTI, as further described herein. In a further non-limiting example, exemplary methods1300can comprise establishing the connection to the base station, wherein the UE device (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) has the third TTI (e.g., sTTI304, etc.) comprising one or more of a one symbol, a two symbol, a three symbol, a four symbol, or a seven symbol duration (e.g., sTTI304, etc.), for example, as further described above.

In addition, as described above, methods1400can further comprise, at1404, detecting a second sPDCCH (e.g., second short PDCCH902, etc.) for scheduling an UL transmission via the third TTI (e.g., sTTI304, etc.), in a further non-limiting aspect.

In further non-limiting implementations, exemplary methods1400can comprise, at1406, transmitting one or more scheduled UL transmission on one or more associated UL channel, wherein for a number of short PDCCHs within one of the first TTI on the associated DL, a plurality of associated UL channels having the one or more scheduled UL transmission occur within the same one of the first TTI on the associated UL, in still further non-limiting aspects. More specifically, for all of short PDCCHs within one of the first TTI on the associated DL, all of associated UL channels having the one or more scheduled UL transmission occur within the same one of the first TTI on the associated UL. As a non-limiting example, exemplary methods1400can comprise transmitting the one or more scheduled UL transmission on the associated UL channel for scheduled UL transmission with a second time offset of another of a first available channel of the associated UL channel for scheduled UL transmission after N′×TTIUL, and wherein, for a number of short PDCCHs within one of the first TTI on the associated DL, the second time offset induces same association on one of the first TTI on the associated UL for a plurality of associated UL channels scheduled via the number of short PDCCHs. More specifically, for all of short PDCCHs within one of the first TTI on the associated DL, the second time offset induces same association on one of the first TTI on the associated UL for all of associated UL channels scheduled via the number of short PDCCHs. In addition, in a further non-limiting example, exemplary methods1400can comprise transmitting the one or more scheduled UL transmission on a first available associated UL channel for scheduled UL transmission after N′×TTIUL+k′, where N′ is the integer, TTIULis the length of the third TTI or an interval between symbols of a monitored second sPDCCH, and where k′ is specified, configured, or indicated in the second sPDCCH, wherein for a number of sPDCCHs within the one of the first TTI on the associated DL, k′ induces same association on the one of the first TTI on the associated UL for the plurality of associated UL channels scheduled via the number of sPDCCHs. More specifically, for all of sPDCCHs within the one of the first TTI on the associated DL, k′ induces same association on the one of the first TTI on the associated UL for all of associated UL channels scheduled via the all of sPDCCHs.

In still further non-limiting implementations, exemplary methods1400can comprise, at1408, monitoring the second short PDCCH (e.g., second short PDCCH902, etc.) according to a time distribution for monitoring the second short PDCCH (e.g., second short PDCCH902, etc.) within the first TTI based on one or more of a PDCCH region (e.g., PDCCH region308, etc.) within the first TTI or a CFI value indicated in the first TTI. As a non-limiting example, exemplary methods1400can comprise monitoring the second short PDCCH (e.g., second short PDCCH902, etc.), according to the time distribution for monitoring the second short PDCCH (e.g., second short PDCCH902, etc.) within the first TTI based on a subset of all symbols in the first TTI except the PDCCH region (e.g., PDCCH region308) within the first TTI, in still further non-limiting aspects.

In view of the example embodiments described supra, devices and systems that can be implemented in accordance with the disclosed subject matter will be better appreciated with reference to the diagrams ofFIGS.15-18. While for purposes of simplicity of explanation, the example devices and systems are shown and described as a collection of blocks, it is to be understood and appreciated that the claimed subject matter is not limited by the order, arrangement, and/or number of the blocks, as some blocks may occur in different orders, arrangements, and/or combined and/or distributed with other blocks or functionality associated therewith from what is depicted and described herein. Moreover, not all illustrated blocks may be required to implement the example devices and systems described hereinafter. Additionally, it should be further understood that the example devices and systems and/or functionality disclosed hereinafter and throughout this specification are capable of being stored on an article of manufacture to facilitate transporting and transferring such methods to computers, for example, as further described herein. The terms computer readable medium, article of manufacture, and the like, as used herein, are intended to encompass a computer program product accessible from any computer-readable device or media such as a tangible computer readable storage medium.

It can be further understood that while a brief overview of example systems, methods, scenarios, and/or devices has been provided, the disclosed subject matter is not so limited. Thus, it can be further understood that various modifications, alterations, addition, and/or deletions can be made without departing from the scope of the embodiments as described herein. Accordingly, similar non-limiting implementations can be used or modifications and additions can be made to the described embodiments for performing the same or equivalent function of the corresponding embodiments without deviating therefrom.

FIG.15illustrates an example non-limiting device or system1500suitable for performing various aspects of the disclosed subject matter. The device or system1500can be a stand-alone device or a portion thereof, a specially programmed computing device or a portion thereof (e.g., a memory retaining instructions for performing the techniques as described herein coupled to a processor), and/or a composite device or system comprising one or more cooperating components distributed among several devices, as further described herein. As an example, example non-limiting device or system1500can comprise example devices and/or systems regardingFIGS.1-14, as described above, or as further described below regardingFIGS.16-18, for example, or portions thereof. For example,FIG.15depicts an example device1500, such as a UE device (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.). In another non-limiting example,FIG.15depicts an example device1500, such as a base station (e.g., a base station such as an access network102, a transmitter system202, and/or portions thereof, configured for TTI shortening, etc.), according to control channel structures and/or TTI shortening methods as described herein.

Accordingly, device or system1500can comprise a memory1502that retains various instructions with respect to facilitating various operations, for example, such as: establishing with the UE device (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) a connection to a base station (e.g., a base station such as an access network102, a transmitter system202, and/or portions thereof, configured for TTI shortening, etc.) having a first TTI, wherein the UE device (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) is configured to employ TTI shortening and has a second TTI (e.g., sTTI304, etc.) (or third TTI and so on) different from the first TTI; monitoring a first short PDCCH region (e.g., a region comprising first sPDCCH406, etc.) for a scheduled downlink (DL) transmission via the second TTI (e.g., sTTI304, etc.), wherein a time distribution associated with multiple second TTIs (e.g., sTIIs304, etc.) within the first TTI is determined based on a CFI value indicated via the first TTI; detecting a first short PDCCH (e.g., first sPDCCH406, etc.); determining one or more of a number of symbols or a number of symbol occasions for the scheduled DL transmission via the second TTI (e.g., sTTI304, etc.) based on the first short PDCCH (e.g., first sPDCCH406, etc.); encryption; decryption; providing various user or device interfaces; and/or communications routines such as networking, and/or peer-to-peer communications routines, and/or the like.

For instance, device or system1500can comprise a memory1502that retains instructions for establishing the connection to the base station having the first TTI comprising a subframe (e.g., subframe306), for establishing the connection to the base station, wherein the UE device (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) has the second TTI (e.g., sTTI304, etc.) comprising one or more of a one symbol, a two symbol, a three symbol, a four symbol, or a seven symbol duration (e.g., sTTI304, etc.), and so on, as further described above regardingFIGS.12-14, for example.

Additionally, memory1502can retain instructions for receiving a DL transmission via the second TTI (e.g., sTTI304, etc.); transmitting hybrid automatic repeat request (HARD) acknowledgement (ACK) (HARQ-ACK) feedback on an associated UL channel for HARQ-ACK feedback, wherein for a number of DL transmissions via the second TTI (e.g., sTTI304, etc.) within one of the first TTI on the associated DL, a number of channels of the associated UL for HARQ-ACK feedback occur within the same one of the first TTI on the associated UL; detecting with the UE device (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) a first short PDCCH (e.g., first sPDCCH406, etc.) for scheduling the DL transmission via the second TTI (e.g., sTTI304, etc.); transmitting the HARQ-ACK feedback of the at least the DL transmission, wherein when detecting the first sPDCCH, the HARQ-ACK is transmitted on a first associated UL channel for HARQ-ACK feedback after N×second TTI (e.g., sTTI304, etc.) length+k, where N is an integer and where k is a value specified, configured, or indicated in the first sPDCCH or in a PDCCH received in the first TTI; encryption; decryption; providing various user or device interfaces; and/or communications routines such as networking, and/or peer-to-peer communications routines, and/or the like, for example, as further described above regardingFIG.13.

Additionally, memory1502can retain instructions for establishing with the UE device (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) a connection to a base station (e.g., a base station such as an access network102, a transmitter system202, and/or portions thereof, configured for TTI shortening, etc.) having a first TTI for an associated DL and an associated UL, wherein the UE device (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) is configured to employ TTI shortening and having a third TTI (e.g., sTTI304, etc.) of a number of TTIs different from the first TTI; detecting a second sPDCCH (e.g., second short PDCCH902, etc.) for scheduling an UL transmission via the third TTI (e.g., sTTI304, etc.); transmitting the one or more scheduled UL transmission on one or more associated UL, wherein for a number of short PDCCHs received within one of the first TTI on the associated DL, a plurality of associated UL channels having the one or more scheduled UL transmission occur within the same one of the first TTI on the associated UL; monitoring the second short PDCCH (e.g., second short PDCCH902, etc.) according to a time distribution for monitoring the second short PDCCH (e.g., second short PDCCH902, etc.) within the first TTI based on one or more of a PDCCH region within the first TTI or a CFI value indicated in the first TTI; encryption; decryption; providing various user interfaces; and/or communications routines such as networking, and/or the like, for example, as further described above regardingFIG.14.

The above example instructions and other suitable instructions for functionalities as described herein, alternatives for, and/or modifications thereof for example, regarding FIGS.1-14and16-18, etc., can be retained within memory1502, and a processor1504can be utilized in connection with executing the instructions.

One or more embodiments as described herein can comprise a computer program product directed to a tangible computer readable storage medium comprising computer-executable instructions, for example, as described above regardingFIGS.1-15, etc., that, in response to execution by a processor, can cause a computing device including a processor, for example, such as a UE device (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.), a base station (e.g., a base station such as an access network102, a transmitter system202, and/or portions thereof, configured for TTI shortening, etc.), etc., to perform operations according to the computer-executable instructions on the tangible computer readable storage medium, for example, as further described herein.

FIG.16depicts a simplified functional block diagram of an exemplary non-limiting communication device1600, such as a UE device (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.), a base station (e.g., a base station such as an access network102, a transmitter system202, and/or portions thereof, configured for TTI shortening, etc.), etc., suitable for incorporation of various aspects of the subject disclosure. As shown inFIG.16, exemplary communication device1600in a wireless communication system can be utilized for realizing the UEs (or ATs)116and122inFIG.1, for example, and the wireless communications system such as described above regardingFIG.1, as a further example, can be the LTE system, the NR system, etc. Exemplary communication device1600can comprise an input device1602, an output device1604, a control circuit1606, a central processing unit (CPU)1608, a memory1610, a program code1612, and a transceiver1614. Exemplary control circuit1606can execute the program code1612in the memory1610through the CPU1608, thereby controlling an operation of the communications device1600. Exemplary communications device1600can receive signals input by a user through the input device1602, such as a keyboard or keypad, and can output images and sounds through the output device1604, such as a monitor or speaker. Exemplary transceiver1614can be used to receive and transmit wireless signals, delivering received signals to the control circuit1606, and outputting signals generated by the control circuit1606wirelessly, for example, as described above regardingFIG.1.

Accordingly, further non-limiting embodiments as described herein can comprise a UE device (e.g., UE device configured to employ short TTI and comprising AT116, AT122, receiver system204, or portions thereof, and/or as further described herein regardingFIGS.12-18, etc.) that can comprise one or more of a exemplary control circuit1606, a processor (e.g., CPU1608, etc.) installed in the control circuit (e.g., control circuit1606), a memory (e.g., memory1610) installed in the control circuit (e.g., control circuit1606) and coupled to the processor (e.g., CPU1608, etc.), wherein the processor (e.g., CPU1608, etc.) is configured to execute a program code (e.g., program code1612) stored in the memory (e.g., memory1610) to perform method steps and/or provide functionality as described herein. As a non-limiting example, exemplary program code (e.g., program code1612) can comprise computer-executable instructions as described above regardingFIG.15, portions thereof, and/or complementary or supplementary instructions thereto, in addition to computer-executable instructions configured to achieve functionalities as described herein, regardingFIGS.1-14, and/or any combinations thereof.

FIG.17depicts a simplified block diagram1700of exemplary program code1612shown inFIG.16, suitable for incorporation of various aspects of the subject disclosure. In this embodiment, exemplary program code1612can comprise an application layer1702, a Layer 3 portion1704, and a Layer 2 portion1706, and can be coupled to a Layer 1 portion1708. The Layer 3 portion1704generally performs radio resource control. The Layer 2 portion1706generally performs link control. The Layer 1 portion1708generally performs physical connections. For LTE, LTE-A, or NR system, the Layer 2 portion1706may include a Radio Link Control (RLC) layer and a Medium Access Control (MAC) layer. The Layer 3 portion1704may include a Radio Resource Control (RRC) layer. In addition, as further described above, exemplary program code (e.g., program code1612) can comprise computer-executable instructions as described above regardingFIG.15, portions thereof, and/or complementary or supplementary instructions thereto, in addition to computer-executable instructions configured to achieve functionalities as described herein, regardingFIGS.1-14, and/or any combinations thereof.

FIG.18depicts a schematic diagram of an example mobile device1800(e.g., a mobile handset, UE, AT, etc.) that can facilitate various non-limiting aspects of the disclosed subject matter in accordance with the embodiments described herein. Although mobile handset1800is illustrated herein, it will be understood that other devices can be any of a number of other a mobile devices, for instance, and that the mobile handset1800is merely illustrated to provide context for the embodiments of the subject matter described herein. The following discussion is intended to provide a brief, general description of an example of a suitable environment1800in which the various embodiments can be implemented. While the description includes a general context of computer-executable instructions embodied on a tangible computer readable storage medium, those skilled in the art will recognize that the subject matter also can be implemented in combination with other program modules and/or as a combination of hardware and software.

A computing device can typically include a variety of computer readable media. Computer readable media can comprise any available media that can be accessed by the computer and includes both volatile and non-volatile media, removable and non-removable media. By way of example and not limitation, computer readable media can comprise tangible computer readable storage and/or communication media. Tangible computer readable storage can include volatile and/or non-volatile media, removable and/or non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. Tangible computer readable storage can include, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD ROM, digital video disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer.

Communication media, as contrasted with tangible computer readable storage, typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal, for example, as further described herein. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of the any of the above should also be included within the scope of computer readable communications media as distinguishable from computer-readable storage media.

The handset1800can include a processor1802for controlling and processing all onboard operations and functions. A memory1804interfaces to the processor1802for storage of data and one or more applications1806(e.g., communications applications such as browsers, apps, etc.). Other applications can support operation of communications and/or financial communications protocols. The applications1806can be stored in the memory1804and/or in a firmware1808, and executed by the processor1802from either or both the memory1804or/and the firmware1808. The firmware1808can also store startup code for execution in initializing the handset1800. A communications component1810interfaces to the processor1802to facilitate wired/wireless communication with external systems, e.g., cellular networks, VoIP networks, and so on. Here, the communications component1810can also include a suitable cellular transceiver1811(e.g., a GSM transceiver, a CDMA transceiver, an LTE transceiver, etc.) and/or an unlicensed transceiver1813(e.g., Wireless Fidelity (WiFi™), Worldwide Interoperability for Microwave Access (WiMax®)) for corresponding signal communications, and the like. The handset1800can be a device such as a cellular telephone, a personal digital assistant (PDA) with mobile communications capabilities, and messaging-centric devices. The communications component1810also facilitates communications reception from terrestrial radio networks (e.g., broadcast), digital satellite radio networks, and Internet-based radio services networks, and so on.

The handset1800includes a display1812for displaying text, images, video, telephony functions (e.g., a Caller ID function, etc.), setup functions, and for user input. For example, the display1812can also be referred to as a “screen” that can accommodate the presentation of multimedia content (e.g., music metadata, messages, wallpaper, graphics, etc.). The display1812can also display videos and can facilitate the generation, editing and sharing of video quotes. A serial I/O interface1814is provided in communication with the processor1802to facilitate wired and/or wireless serial communications (e.g., Universal Serial Bus (USB), and/or Institute of Electrical and Electronics Engineers (IEEE) 1494) through a hardwire connection, and other serial input devices (e.g., a keyboard, keypad, and mouse). This supports updating and troubleshooting the handset1800, for example. Audio capabilities are provided with an audio I/O component1816, which can include a speaker for the output of audio signals related to, for example, indication that the user pressed the proper key or key combination to initiate the user feedback signal. The audio I/O component1816also facilitates the input of audio signals through a microphone to record data and/or telephony voice data, and for inputting voice signals for telephone conversations.

The handset1800can include a slot interface1818for accommodating a SIC (Subscriber Identity Component) in the form factor of a card Subscriber Identity Module (SIM) or universal SIM1820, and interfacing the SIM card1820with the processor1802. However, it is to be appreciated that the SIM card1820can be manufactured into the handset1800, and updated by downloading data and software.

The handset1800can process Internet Protocol (IP) data traffic through the communication component1810to accommodate IP traffic from an IP network such as, for example, the Internet, a corporate intranet, a home network, a person area network, a cellular network, etc., through an internet service provider (ISP) or broadband cable provider. Thus, VoIP traffic can be utilized by the handset1800and IP-based multimedia content can be received in either an encoded or a decoded format.

A video processing component1822(e.g., a camera and/or associated hardware, software, etc.) can be provided for decoding encoded multimedia content. The video processing component1822can aid in facilitating the generation and/or sharing of video. The handset1800also includes a power source1824in the form of batteries and/or an alternating current (AC) power subsystem, which power source1824can interface to an external power system or charging equipment (not shown) by a power input/output (I/O) component1826.

The handset1800can also include a video component1830for processing video content received and, for recording and transmitting video content. For example, the video component1830can facilitate the generation, editing and sharing of video. A location-tracking component1832facilitates geographically locating the handset1800. A user input component1834facilitates the user inputting data and/or making selections as previously described. The user input component1834can also facilitate selecting perspective recipients for fund transfer, entering amounts requested to be transferred, indicating account restrictions and/or limitations, as well as composing messages and other user input tasks as required by the context. The user input component1834can include such conventional input device technologies such as a keypad, keyboard, mouse, stylus pen, and/or touch screen, for example.

Referring again to the applications1806, a hysteresis component1836facilitates the analysis and processing of hysteresis data, which is utilized to determine when to associate with an access point. A software trigger component1838can be provided that facilitates triggering of the hysteresis component1838when a WiFi™ transceiver1813detects the beacon of the access point. A Session Initiation Protocol (SIP) client1840enables the handset1800to support SIP protocols and register the subscriber with the SIP registrar server. The applications1806can also include a communications application or client1846that, among other possibilities, can facilitate user interface component functionality as described above.

While the various embodiments of the subject disclosure have been described in connection with various non-limiting aspects, it will be understood that the embodiments of the subject disclosure may be capable of further modifications. This application is intended to cover any variations, uses or adaptation of the subject disclosure following, in general, the principles of the subject disclosure, and including such departures from the present disclosure as come within the known and customary practice within the art to which the subject disclosure pertains.

Those skilled in the art will recognize that it is common within the art to describe devices and/or processes in the fashion set forth herein, and thereafter use engineering practices to integrate such described devices and/or processes into systems. That is, at least a portion of the devices and/or processes described herein can be integrated into a system via a reasonable amount of experimentation. Those having skill in the art will recognize that a typical system can include one or more of a system unit housing, a video display device, a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices, such as a touch pad or screen, and/or control systems including feedback loops and control device (e.g., feedback for sensing position and/or velocity; control devices for moving and/or adjusting parameters). A typical system can be implemented utilizing any suitable commercially available components, such as those typically found in data computing/communication and/or network computing/communication systems.

Various embodiments of the disclosed subject matter sometimes illustrate different components contained within, or connected with, other components. It is to be understood that such depicted architectures are merely exemplary, and that, in fact, many other architectures can be implemented which achieve the same and/or equivalent functionality. In a conceptual sense, any arrangement of components to achieve the same and/or equivalent functionality is effectively “associated” such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermediary components. Likewise, any two components so associated can also be viewed as being “operably connected,” “operably coupled,” “communicatively connected,” and/or “communicatively coupled,” to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being “operably couplable” or “communicatively couplable” to each other to achieve the desired functionality. Specific examples of operably couplable or communicatively couplable can include, but are not limited to, physically mateable and/or physically interacting components, wirelessly interactable and/or wirelessly interacting components, and/or logically interacting and/or logically interactable components.

With respect to substantially any plural and/or singular terms used herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as can be appropriate to the context and/or application. The various singular/plural permutations may be expressly set forth herein for the sake of clarity, without limitation.

From the foregoing, it will be noted that various embodiments of the disclosed subject matter have been described herein for purposes of illustration, and that various modifications may be made without departing from the scope and spirit of the subject disclosure. Accordingly, the various embodiments disclosed herein are not intended to be limiting, with the true scope and spirit being indicated by the appended claims.

In addition, the words “example” and “non-limiting” are used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. Moreover, any aspect or design described herein as “an example,” “an illustration,” “example” and/or “non-limiting” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent example structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, for the avoidance of doubt, such terms are intended to be inclusive in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements, as described above.

Systems described herein can be described with respect to interaction between several components. It can be understood that such systems and components can include those components or specified sub-components, some of the specified components or sub-components, or portions thereof, and/or additional components, and various permutations and combinations of the foregoing. Sub-components can also be implemented as components communicatively coupled to other components rather than included within parent components (hierarchical). Additionally, it should be noted that one or more components can be combined into a single component providing aggregate functionality or divided into several separate sub-components, and that any one or more middle component layers, such as a management layer, can be provided to communicatively couple to such sub-components in order to provide integrated functionality, as mentioned. Any components described herein can also interact with one or more other components not specifically described herein but generally known by those of skill in the art.

As mentioned, in view of the example systems described herein, methods that can be implemented in accordance with the described subject matter can be better appreciated with reference to the flowcharts of the various figures and vice versa. While for purposes of simplicity of explanation, the methods can be shown and described as a series of blocks, it is to be understood and appreciated that the claimed subject matter is not limited by the order of the blocks, as some blocks can occur in different orders and/or concurrently with other blocks from what is depicted and described herein. Where non-sequential, or branched, flow is illustrated via flowchart, it can be understood that various other branches, flow paths, and orders of the blocks, can be implemented which achieve the same or a similar result. Moreover, not all illustrated blocks can be required to implement the methods described hereinafter.

While the disclosed subject matter has been described in connection with the disclosed embodiments and the various figures, it is to be understood that other similar embodiments may be used or modifications and additions may be made to the described embodiments for performing the same function of the disclosed subject matter without deviating therefrom. Still further, multiple processing chips or multiple devices can share the performance of one or more functions described herein, and similarly, storage can be effected across a plurality of devices. In other instances, variations of process parameters (e.g., configuration, number of components, aggregation of components, process step timing and order, addition and/or deletion of process steps, addition of preprocessing and/or post-processing steps, etc.) can be made to further optimize the provided structures, devices and methods, as shown and described herein. In any event, the systems, structures and/or devices, as well as the associated methods described herein have many applications in various aspects of the disclosed subject matter, and so on. Accordingly, the subject disclosure should not be limited to any single embodiment, but rather should be construed in breadth, spirit and scope in accordance with the appended claims.