Patent Description:
Aspects of the present disclosure relate, generally, to wireless communication systems and, more particularly, to mission critical data support in self-contained time division duplex (TDD) subframe structure.

Wireless communication networks, as are for example described in documents <NPL> and <NPL>, are widely deployed to provide various communication services such as telephony, video, data, messaging, broadcasts, and so on. The spectrum allocated to such wireless communication networks can include licensed spectrum and/or unlicensed spectrum. Licensed spectrum is generally restricted in its use for wireless communication except for licensed use as regulated by a governmental body or other authority within a given region. Unlicensed spectrum is generally free to use, within limits, without the purchase or use of such a license. The demand for wireless communication continues to increase for many use cases, including but not limited to telephones, smart phones, personal computers, smart meters, remote sensors, smart alarms, mesh nodes, and many others. Time division duplex (TDD) carriers may be utilized in many wireless communication networks. Enhancements directed to TDD carriers may benefit such wireless communication networks and the overall user experience.

In one aspect, the present disclosure provides an apparatus for wireless communication. The apparatus includes a transceiver, a memory, and at least one processor communicatively coupled to the transceiver and the memory. The at least one processor and the memory may be configured to generate instructions for the transceiver to enable at least one opportunity to transmit mission critical (MiCr) data and at least one opportunity to receive MiCr data in a time division duplex (TDD) subframe during a single transmission time interval (TTI). The at least one processor and the memory may be further configured to communicate the MiCr data in the TDD subframe during the single TTI.

In another aspect, the present disclosure provides a method for wireless communication. The method may include generating instructions for a transceiver to enable at least one opportunity to transmit MiCr data and at least one opportunity to receive MiCr data in a TDD subframe during a single TTI. The method may also include communicating the MiCr data in the TDD subframe during the single TTI.

In yet another aspect, the present disclosure provides a computer-readable medium configured for wireless communication. The computer-readable medium includes computer-executable instructions that may be configured for enabling at least one opportunity to transmit MiCr data and at least one opportunity to receive MiCr data in a TDD subframe during a single TTI. The computer-executable instructions may be further configured for communicating the MiCr data in the TDD subframe during the single TTI.

In a further aspect of the present disclosure, the present disclosure provides an apparatus for wireless communication. The apparatus may include means for enabling at least one opportunity to transmit MiCr data and at least one opportunity to receive MiCr data in a TDD subframe during a single TTI. The apparatus may also include means for communicating the MiCr data in the TDD subframe during the single TTI.

These and other aspects of the present disclosure will become more fully understood upon a review of the detailed description, which follows. Other aspects, features, and embodiments of the present disclosure will become apparent to those of ordinary skill in the art, upon reviewing the following description of specific, exemplary embodiments of the present disclosure in conjunction with the accompanying figures. While features of the present disclosure may be discussed relative to certain embodiments and figures below, all embodiments of the present disclosure can include one or more of the advantageous features discussed herein. In other words, while one or more embodiments may be discussed as having certain advantageous features, one or more of such features may also be used in accordance with the various embodiments of the disclosure discussed herein.

The 3rd Generation Partnership Project (3GPP) is a standards body that defines several wireless communication standards for networks involving an evolved packet system (EPS), which may sometimes be referred to as long-term evolution (LTE) network. In an LTE network, packets may utilize the same or similar latency targets. As such, an LTE network may provide a one-size-fits-all latency configuration. Evolved versions of an LTE network, such as a fifth-generation (<NUM>) network, may provide many different types of services and/or applications (e.g., web browsing, video streaming, VoIP, mission critical applications, multi-hop networks, remote operations with real-time feedback, tele-surgery, and others). Such services and/or applications may benefit from latency targets that can differ considerably from one another. However, the one-size-fits-all latency configuration of an LTE network can make multiplexing of traffic with different latency targets challenging. The spectrum compatibility of a system that supports such diverse latency targets can also be challenging. For example, time multiplexing of regular traffic and low latency traffic (e.g., mission critical (MiCr) data) may violate certain requirements of the low latency traffic (e.g., MiCr data). Furthermore, reserved frequency domain resources for low latency traffic (e.g., MiCr data) may limit the peak rate and trunking efficiency. Accordingly, support for multiplexing various types, classes, and categories of traffic and services having considerably different latency characteristics may enhance such next-generation networks (e.g., <NUM> networks) and the overall user experience.

<FIG> is a block diagram illustrating an example of various uplink (UL) and downlink (DL) communications between two devices. In accordance with aspects of the present disclosure, the term 'downlink' may refer to a point-to-multipoint transmission originating at DeviceA <NUM>, and the term 'uplink' may refer to a point-to-point transmission originating at Devices <NUM>. Broadly, DeviceA <NUM> is a node or device responsible for scheduling traffic in a wireless communication network, including various DL and UL transmissions. DeviceA <NUM> may sometimes be referred to as a scheduling entity, a scheduler, and/or any other suitable term without deviating from the scope of the present disclosure. DeviceA <NUM> may be, or may reside within, a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set, an extended service set, an access point, a Node B, a user equipment (UE), a mesh node, a relay, a peer, and/or any other suitable device.

Broadly, Devices <NUM> is a node or device that receives scheduling and/or control information, including but not limited to scheduling grants, synchronization or timing information, or other control information from another entity in the wireless communication network, such as DeviceA <NUM>. Devices <NUM> may be a referred to as a subordinate entity, a schedulee, and/or any other suitable term without deviating from the scope of the present disclosure. Devices <NUM> may be, or may reside within, a UE, a cellular phone, a smart phone, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, a mesh node, a peer, a session initiation protocol phone, a laptop, a notebook, a netbook, a smartbook, a personal digital assistant, a satellite radio, a global positioning system device, a multimedia device, a video device, a digital audio player, a camera, a game console, an entertainment device, a vehicle component, a wearable computing device (e.g., a smart watch, glasses, a health or fitness tracker, etc.), an appliance, a sensor, a vending machine, and/or any other suitable device.

DeviceA <NUM> may transmit DL data channel(s) <NUM> and DL control channel(s) <NUM>. Devices <NUM> may transmit UL data channel(s) <NUM> and UL control channel(s) <NUM>. The channels illustrated in <FIG> are not necessarily all of the channels that may be utilized by DeviceA <NUM> and Devices <NUM>. Those of ordinary skill in the art will recognize that other channels may be utilized in addition to those illustrated, such as other data, control, and feedback channels.

As described above, some data may be characterized as MiCr data. In some configurations, MiCr data refers to data that has a relatively low or ultra-low latency requirement. For example, the latency requirement of MiCr data may be lower than the latency requirement of other data included in that subframe. Generally, latency refers to the delay associated with receipt of data at its intended destination. In some configurations, MiCr data refers to data that has a relatively high priority requirement. For example, the priority requirement of MiCr data may be higher than the priority requirement of other data included in the subframe. Generally, priority refers to the importance or time-sensitivity of the data. Data having relatively higher importance and/or relatively greater time-sensitivity should be received before other data having relatively lesser importance and/or relatively lesser time-sensitivity. In some configurations, MiCr data refers to data that has a relatively high reliability requirement. For example, the reliability requirement of MiCr data may be greater than the reliability requirement of other data included in that subframe. Generally, reliability refers to how consistently data is successfully received by the intended destination without errors.

<FIG> is a diagram <NUM> illustrating an example of various subframe configurations according to aspects of some communication systems. Generally, as used within the present disclosure, a frame may refer to an encapsulated set and/or packet of data and/or information. A frame may include a plurality of subframes. Each subframe may include a plurality of symbols. Each subframe may have a particular duration. A transmission time interval (TTI) refers to the duration of a single subframe. Accordingly, a TTI refers to the duration of the aforementioned plurality of symbols in the single subframe. Each symbol may be received and decoded at a receiver. Each symbol may correspond to a single turbo code word that the receiver may understand and decode. In some configurations, a TTI may refer to the smallest granularity of a collection of symbols to be processed at the receiver. One of ordinary skill in the art will understand that the terms 'frame' and/or 'subframe' may be known as or referred to by various other suitable terms without deviating from the scope of the present disclosure.

The subframes illustrated in <FIG> may sometimes be referred to as time division duplex (TDD) subframes. For illustrative purposes, four TDD subframes are illustrated in <FIG>. Subframe<NUM> <NUM> is a DL communication during TTI<NUM> <NUM>. Subframe<NUM> <NUM> is an UL communication during TTI<NUM> <NUM>. Subframe<NUM> <NUM> is a DL communication during TTI<NUM> <NUM>. Subframe<NUM> <NUM> is an UL communication during TTI<NUM> <NUM>. In some communication systems, subframes may be scheduled as a DL subframe (e.g., Subframe<NUM> <NUM>, Subframe<NUM> <NUM>) or an UL subframe (e.g., Subframe<NUM> <NUM>, Subframe<NUM> <NUM>). Accordingly, DL MiCr data can be communicated in Subframe<NUM> <NUM> during TTI<NUM> <NUM> and/or Subframe<NUM> <NUM> during TTI<NUM> <NUM>, and UL MiCr data can be communicated in Subframe<NUM> <NUM> during TTI<NUM> <NUM> and/or Subframe<NUM> <NUM> during TTI<NUM> <NUM>.

However, in some communication systems, UL MiCr data cannot be communicated in Subframe<NUM> <NUM> during TTI<NUM> <NUM> nor in Subframe<NUM> <NUM> during TTI<NUM>, and DL MiCr data cannot be communicated in Subframe<NUM> <NUM> during TTI<NUM> <NUM> nor in Subframe<NUM> <NUM> during TTI<NUM> <NUM>. Accordingly, instead of communicating UL MiCr data in Subframe<NUM> <NUM> during TTI<NUM> <NUM> and/or Subframe<NUM> <NUM> during TTI<NUM>, communication of UL MiCr data will be delayed until Subframe<NUM> <NUM> during TTI<NUM> <NUM> and/or Subframe<NUM> <NUM> during TTI<NUM> <NUM>, respectively. Also, instead of communicating DL MiCr data in Subframe<NUM> <NUM> during TTI<NUM> <NUM>, communication of DL MiCr data will be delayed until Subframe<NUM> <NUM> during TTI<NUM>. Of course, this MiCr data latency can be extended to an even greater duration when multiple consecutive subframes are all in a single direction, and a MiCr packet is to be communicated in the other direction. Such a large latency in communicating MiCr data may adversely affect the communication system and the overall user experience.

Accordingly, one of ordinary skill in the art will readily understand that communication utilizing a TDD carrier may have certain drawbacks. While a device is transmitting a symbol, its receiver is disabled and generally unable to receive a symbol. Similarly, while a device is receiving a symbol, its transmitter is disabled and it is generally unable to transmit a symbol. One approach that attempts to overcome such an issue is to pair two TDD carriers with one another in a way that can enable full duplex communication at certain time slots, as described in greater detail below with reference to <FIG>.

<FIG> is a diagram <NUM> illustrating another example of various subframe configurations according to aspects of some communication systems. More specifically, <FIG> illustrates an example of a pairing of two TDD component carriers (CC). A first CC (CC<NUM>) is paired with a second CC (CC<NUM>). In the diagram <NUM>, the horizontal axis represents time (not to scale), and the vertical axis represents frequency (not to scale). CC<NUM> and CC<NUM> are TDD carriers. Uplink time slots (indicated with a "U") are time-multiplexed with downlink time slots (indicated with a "D") on each respective carrier. Some time slots are special time slots (indicated with an "S"), as described further below. Generally, a time slot may correspond to any suitable duration of time and may correspond to other nomenclature such as a TTI, a subframe, a frame, a symbol, a duration of time, and/or any other suitable term.

As illustrated in diagram <NUM>, the frame configured as "Configuration A" is paired with a frame configured as "Configuration -A", wherein "Configuration -A" represents the inverse (or conjugate) of "Configuration A. " Likewise, "Configuration B" frame is paired with a frame configured as "Configuration -B. " Here, CC<NUM> may implement an inverse, conjugate, and/or complementary transmit/receive organization relative to that of CC<NUM>. The terms inverse, complementary, and/or conjugate may be utilized interchangeably, generally referring to a configuration wherein at least some of the downlink time slots ("D") in CC<NUM> are paired with uplink time slots ("U") in CC<NUM>, and at least some of the uplink time slots ("U") in CC<NUM> are paired with downlink time slots ("D") in CC<NUM>.

The special time slot ("S") may be utilized for downlink-to-uplink switching. For example, a scheduling entity (e.g., DeviceA <NUM>) may utilize these special time slots ("S") as time gaps for a subordinate entity (e.g., Devices <NUM>) to transition from a downlink time slot ("D") to an uplink time slot ("U") when utilizing a TDD carrier. For example, there may exist a propagation delay between the transmission of the downlink time slot ("D") from the scheduling entity (e.g., DeviceA <NUM>) to the subordinate entity (e.g., Devices <NUM>). To account for such a propagation delay, special time slots ("S") provide a time gap between the end of an downlink time slots ("D") and the beginning of an uplink time slot ("U") such that the scheduling entity (e.g.. , DeviceA <NUM>) and the subordinate entity (e.g., Devices <NUM>) can maintain synchronization. Here, the time gap may correspond to a time when neither uplink nor downlink communication occurs.

However, switching between downlink time slots ("D") and uplink time slots ("U") may require complex interference management protocols. Also, paired component carriers may not always be available. Even if available, some time slots may not have a conjugate time slot. In other words, as illustrated in <FIG>, not every downlink time slots ("D") has a conjugate uplink time slots ("U"). For example, time slots in CC<NUM> do not have conjugate time slots in CC<NUM> whenever CC<NUM> has a special time slot ("S"). In other words, whenever CC<NUM> or CC<NUM> has a special time slot ("S"), the communication system does not have the capability to utilize both an uplink time slot ("U") and a downlink time slot ("D") at the same time. As such, the communication system cannot benefit from simultaneous/concurrent UL and DL communications when one of the component carriers is scheduled for a special time slot ("S"). Accordingly, the communication system may have to delay simultaneous/concurrent UL and DL communications until the end of that special time slot ("S"). Such latency in communicating certain types of data (e.g., MiCr) may adversely affect the communication system and the overall user experience.

<FIG> is a diagram <NUM> illustrating yet another example of various subframe configurations according to aspects of some communication systems. Various aspects of the TDD carriers illustrated in <FIG> are similar to aspects of the TDD carriers described above with reference to <FIG> and therefore will not be repeated. TDD carriers may be utilized to transmit data from one device to another device. Frequency division duplex (FDD) carriers may be utilized to trigger a switch between downlink time slots ("D") and uplink time slots ("U"). For example, an FDD carrier may indicate that the communication system should switch from a downlink time slot ("D") to an uplink time slot ("U"). An FDD carrier may also be used for communicating feedback. For example, an FDD carrier may be utilized to communicate an acknowledgement message (ACK) or a negative acknowledgement message (NACK).

However, switching between downlink time slots ("D") and uplink time slots ("U") may require complex interference management protocols. Also, the communication system is unable to perform simultaneous/concurrent high bit rate DL and UL communication. In the example illustrated in <FIG>, the TDD carriers accommodates a single component carrier that can either (i) perform an UL communication during an uplink time slot ("U"), (ii) perform a DL communication during a downlink time slot ("D"), or (iii) transition from a DL communication to an UL communication during a special time slot ("S"). Accordingly, the communication system faces unavoidable delays during special time slots ("S"). The communication system cannot perform a DL communication nor an UL communication during the special time slot ("S"). Accordingly, the communication system may have to delay the UL/DL communication until the end of the special time slot ("S"). Such delays in communicating certain types of data (e.g., MiCr) may adversely affect the communication system and the overall user experience.

The description provided above with reference to <FIG> pertains to some communication systems. Generally, such communication systems may introduce delays in the communication of MiCr data in certain circumstances. These circumstances may sometimes be referred to as TDD self-blocking, which can occur (i) when DL MiCr data is blocked from being communicated in the current subframe because the current subframe is an UL communication, and/or (ii) when UL MiCr data is blocked from being communicated in the current subframe because the current subframe is a DL communication. However, aspects of the present disclosure may reduce or eliminate these issues by enabling communication of both UL MiCr data and DL MiCr data in the same, single TDD subframe. Furthermore, aspects of the present disclosure enable such communication without dynamic UL/DL switching, which facilitates interference management and avoids some of the complex interference management protocols of some communication systems, as described above with reference to <FIG>.

<FIG> is a diagram <NUM> illustrating an example of a DL-centric TDD subframe according to aspects of the present disclosure. In some examples, such a TDD subframe may be a self-contained TDD subframe. A self-contained TDD subframe may contain control information, data, and acknowledgement information within a single TDD subframe. The control information may include scheduling information. The control/scheduling information may provide control/scheduling for all of the data within that same subframe. The acknowledgement information may include acknowledgement (ACK) or negative acknowledgement (NACK) signals for all of the data within that same subframe. The ACK signal and/or NACK signal may be reserved for all data packets before the next scheduling instance (where the next subframe also includes scheduling for data in that subframe). In some configurations, the acknowledgement information corresponding to certain data in a particular subframe may be included in a different subframe. For example, the ACK/NACK signal corresponding to MiCr data in a first subframe may be included in a second subframe (which may be subsequent to the first subframe).

Additional description pertaining to such a self-contained subframe is provided throughout the present disclosure. The self-contained TDD subframe structure may include transmissions in both the uplink direction as well as the downlink direction. In some examples, the self-contained TDD subframe includes DL control/scheduling information, DL data information corresponding to the scheduling information and UL acknowledgement information corresponding to the data information, as described in greater detail herein. In other examples, the self-contained subframe includes DL control/scheduling information, UL data information corresponding to the scheduling information and DL acknowledgement information corresponding to the data information, as described in greater detail herein. Even if not explicitly referred to as a self-contained subframe, one of ordinary skill in the art will understand that any one or more of the subframes described herein may be configured, implemented, and/or otherwise deployed as a self-contained subframe without deviating from the scope of the present disclosure.

Referring to the example illustrated in <FIG>, the DL-centric TDD subframe includes a control portion <NUM>. The control portion <NUM> may include various scheduling information and/or control information corresponding to various portions of the DL-centric TDD subframe. In some configurations, the control portion <NUM> may be configured for DL communication, as illustrated in <FIG>. In some configurations, the control portion <NUM> may be a physical downlink control channel (PDCCH).

The DL-centric TDD subframe may also include a data portion <NUM>. The data portion <NUM> may sometimes be referred to as the payload of the TDD subframe. The data portion <NUM> may include various types of information as well as any padding that may be appropriate. In some configurations, the data portion <NUM> may be configured for DL communication, as illustrated in <FIG>. In some configurations, MiCr data may be included in the data portion <NUM>. Accordingly, the data portion <NUM> may enable at least one opportunity to transmit MiCr data. As used herein, the opportunity to transmit MiCr data refers to the availability, option, or possibility to transmit MiCr data during a particular portion of the TDD subframe or during a particular duration of the TTI. Generally, the term 'enabling' (e.g., of an opportunity to transmit and/or to receive) may refer to the activation of relevant circuits, utilization of particular hardware components, and/or execution of corresponding algorithms that allow a particular feature or aspect to exist. Generally, the term 'generating' (e.g., of instructions) may refer to the activation of relevant circuits, the utilization of particular hardware components, and/or execution of corresponding algorithms that cause, trigger, or otherwise lead in the creation, construction, synthesis, development, and/or rendering of certain aspects (e.g., instructions) in accordance with the present disclosure.

The DL-centric TDD subframe may also include a guard period <NUM>. The guard period <NUM> may sometimes be referred to as a guard interval without deviating from the scope of the present disclosure. Generally, the guard period <NUM> ensures that distinct transmissions do not interfere with one another. Such interference may include propagation delays, echoes, reflections, and other effects. For example, the guard period <NUM> may ensure that the DL communication of the data portion <NUM> (which precedes the guard period <NUM>) does not interfere with the UL communication of the feedback portion <NUM> (which follows the guard period <NUM>).

In some configurations, the feedback portion <NUM> may be configured for UL communication, as illustrated in <FIG>. The feedback portion <NUM> may be configured for receiving a feedback message from another apparatus. For example, the feedback message may be an ACK or a NACK. In some configurations, the feedback message corresponds to other portions of the TDD subframe. For example, an ACK in the feedback portion <NUM> may indicate that the MiCr data included in the data portion <NUM> was successfully transmitted to and received by another apparatus. Furthermore, in some configurations, the feedback portion <NUM> may enable at least one opportunity to receive MiCr data. As used herein, the opportunity to receive MiCr data refers to the availability, option, or possibility to receive MiCr data during a particular portion of the TDD subframe or during a particular duration of the corresponding TTI. Generally, the term 'enabling' (e.g., of an opportunity to transmit and/or to receive) may refer to the activation of relevant circuits, utilization of particular hardware components, and/or execution of corresponding algorithms that allow a particular feature or aspect to exist.

As described in greater detail above, <FIG> illustrates an example of a DL-centric TDD subframe that enables at least one opportunity to transmit MiCr data (e.g., by including MiCr data in the data portion <NUM> that is transmitted) and at least one opportunity to receive MiCr data (e.g., by including MiCr data in the feedback portion <NUM> that is received). In many configurations, the DL-centric TDD subframe is included in a single TTI, and the duration of that TTI is no greater than <NUM> microseconds. By including at least one opportunity to transmit MiCr data and at least one opportunity to receive MiCr data in the same, single TDD subframe, MiCr data can be communicated sooner than it might be otherwise. As described above, some communication systems may introduce delays or increased latency in the communication of MiCr data in certain circumstances. These circumstances may sometimes be referred to as TDD self-blocking, which can occur (i) when DL MiCr data is blocked from being communicated in the current subframe because the current subframe is an UL communication, and/or (ii) when UL MiCr data is blocked from being communicated in the current subframe because the current subframe is a DL communication. However, aspects of the present disclosure may reduce or eliminate these issues by enabling the communication of both UL MiCr data as well DL MiCr data in the same, single TDD subframe.

As illustrated in <FIG>, the control portion <NUM> is separated from the data portion <NUM> by a first partition <NUM>, the data portion <NUM> is separated from the guard period <NUM> by a second partition <NUM>, and the guard period <NUM> is separated from the feedback portion <NUM> by a third partition <NUM>. As used herein, the term 'partition' may refer to a marker, separation, and/or any other suitable term without deviating from the scope of the present disclosure. In some configurations, one or more of these partitions <NUM>, <NUM>, <NUM> may be adjusted, altered, optimized, and/or otherwise changed in location and/or position based on various factors. Such factors may include one or more characteristics of the MiCr data. Characteristics of the MiCr data may include the loading of the MiCr data, the amount of MiCr data to be transmitted (e.g., in the data portion <NUM>), the amount of MiCr data to be received (e.g., in the feedback portion <NUM>), and/or various other suitable factors.

Based on one or more characteristics of the MiCr data, one or more of these partitions <NUM>, <NUM>, <NUM> may be adjusted, altered, optimized, and/or otherwise changed in location and/or position. Accordingly, how much of the TDD subframe is configured for the at least one opportunity to transmit the MiCr data and/or how much of the TDD subframe is configured for the at least one opportunity to receive the MiCr data may be adjusted, altered, optimized, and/or otherwise changed in location and/or position based on one or more characteristics of the MiCr data. As an example, the first partition <NUM> may be adjusted to the left (e.g., earlier in time) if the amount of DL MiCr data to be included in data portion <NUM> is greater than the amount of DL MiCr data that would otherwise be accommodated in the data portion <NUM>. As another example, the second partition <NUM> and the third partition <NUM> may be adjusted to the left (e.g., earlier in time) if the amount of UL MiCr data to be included in the feedback portion <NUM> is greater than the amount of MiCr data that would otherwise be accommodated in the feedback portion <NUM>. Accordingly, various portions of the DL-centric subframe can be adjusted to accommodate for one or more characteristics of the MiCr data without adjusting the total size or length of the DL-centric subframe or TTI (e.g., <NUM> microseconds). One of ordinary skill in the art understands that the example illustrated in <FIG> is not intended to limit the scope of the present disclosure and alternative examples of a DL-centric TDD subframe are within the scope of the present disclosure.

<FIG> is a diagram <NUM> illustrating an example of an UL-centric TDD subframe according to aspects of the present disclosure. In this example, the UL-centric TDD subframe includes a control portion <NUM>. The control portion <NUM> may include various scheduling information and/or control information corresponding to various portions of the UL-centric TDD subframe. In some configurations, the control portion <NUM> may be configured for DL communication, as illustrated in <FIG>. In some configurations, the control portion <NUM> may be a PDCCH. In some configurations, MiCr data may be included in the control portion <NUM>. Accordingly, the control portion <NUM> may enable at least one opportunity to receive MiCr data. As used herein, the opportunity to receive MiCr data refers to the availability, option, or possibility to receive MiCr data during a particular portion of the TDD subframe or during a particular duration of the corresponding TTI. Generally, the term 'enabling' (e.g., of an opportunity to transmit and/or to receive) may refer to the activation of relevant circuits, utilization of particular hardware components, and/or execution of corresponding algorithms that allow a particular feature or aspect to exist.

The UL-centric TDD subframe may also include a guard period <NUM>. The guard period <NUM> may sometimes be referred to as a guard interval without deviating from the scope of the present disclosure. Generally, the guard period <NUM> ensures that distinct transmissions do not interfere with one another. Such interference may include propagation delays, echoes, reflections, and other effects. For example, the guard period <NUM> may ensure that the DL communication of the control portion <NUM> (which precedes the guard period <NUM>) does not interfere with the UL communication of the data portion <NUM> (which follows the guard period <NUM>).

The data portion <NUM> may sometimes be referred to as the payload of the TDD subframe. The data portion <NUM> may include various types of information (e.g., data, scheduling resources for future transmissions, etc.) as well as any padding that may be appropriate. In some configurations, the data portion <NUM> may be configured for UL communication, as illustrated in <FIG>. In some configurations, the data portion <NUM> may include MiCr data. Accordingly, the data portion <NUM> may enable at least one opportunity to transmit MiCr data. As used herein, the opportunity to transmit MiCr data refers to the availability, option, or possibility to receive MiCr data during a particular portion of the TDD subframe or during a particular duration of the corresponding TTI. Generally, the term 'enabling' (e.g., of an opportunity to transmit and/or to receive) may refer to the activation of relevant circuits, utilization of particular hardware components, and/or execution of corresponding algorithms that allow a particular feature or aspect to exist.

The UL-centric TDD subframe may also include a feedback portion <NUM> that follows the data portion <NUM>. In some configurations, the feedback portion <NUM> may be configured for DL communication, as illustrated in <FIG>. The feedback portion <NUM> may be configured for receiving a feedback message from another apparatus. For example, the feedback message may be an ACK or a NACK. In some configurations, the feedback message corresponds to other portions of the TDD subframe. For example, an ACK in the feedback portion <NUM> may indicate that the MiCr data included in the data portion <NUM> was successfully transmitted to and received by another apparatus. Furthermore, in some configurations, the feedback portion <NUM> may include MiCr data. Accordingly, the feedback portion <NUM> may enable at least one additional opportunity to receive MiCr data. (As described above, the control portion <NUM> also enables at least one opportunity to receive MiCr data.

As described in greater detail above, <FIG> illustrates an example of an UL-centric TDD subframe that enables at least one opportunity to receive MiCr data (e.g., by including MiCr data in the control portion <NUM> and/or the feedback portion <NUM> that is/are received) and at least one opportunity to transmit MiCr data (e.g., by including MiCr data in the data portion <NUM> that is transmitted). In many configurations, the UL-centric TDD subframe is included in a single TTI, and the duration of that TTI is no greater than <NUM> microseconds. By including at least one opportunity to receive MiCr data and at least one opportunity to transmit MiCr data in the same, single TDD subframe, MiCr data can be communicated sooner than it might be otherwise. As described above, some communication systems may introduce delays in the communication of MiCr data in certain circumstances. These circumstances may sometimes be referred to as TDD self-blocking, which can occur (i) when DL MiCr data is blocked from being communicated in the current subframe because the current subframe is an UL communication, and/or (ii) when UL MiCr data is blocked from being communicated in the current subframe because the current subframe is a DL communication. However, aspects of the present disclosure overcome such limitations by enabling the communication of both UL MiCr data as well DL MiCr data in the same, single TDD subframe.

As illustrated in <FIG>, the control portion <NUM> is separated from the guard period <NUM> by a first partition <NUM>, the guard period <NUM> is separated from the data portion <NUM> by a second partition <NUM>, and the data portion <NUM> is separated from the feedback portion <NUM> by a third partition <NUM>. In some configurations, one or more of these partitions <NUM>, <NUM>, <NUM> may be adjusted, altered, optimized, and/or otherwise changed in location and/or position based on various factors. Such factors may include one or more characteristics of the MiCr data. Characteristics of the MiCr data may include the loading of the MiCr data, the amount of MiCr data to be transmitted (e.g., in the data portion <NUM>), the amount of MiCr data to be received (e.g., in the control portion <NUM> and/or the feedback portion <NUM>), and/or various other suitable factors.

Based on one or more characteristics of the MiCr data, one or more of these partitions <NUM>, <NUM>, <NUM> may be adjusted, altered, optimized, and/or otherwise changed in location and/or position. Accordingly, how much of the TDD subframe is configured for the at least one opportunity to transmit the MiCr data and/or how much of the TDD subframe is configured for the at least one opportunity to receive the MiCr data may be adjusted, altered, optimized, and/or otherwise changed in location and/or position based on one or more characteristics of the MiCr data. As an example, the first partition <NUM> and the second partition <NUM> may be adjusted to the right (e.g., later in time) if the amount of DL MiCr data to be included in the control portion <NUM> is greater than the amount of DL MiCr data that would otherwise be accommodated in the control portion <NUM>. As another example, the third partition <NUM> may be adjusted to the left (e.g., earlier in time) if the amount of DL MiCr data to be included in the feedback portion <NUM> is greater than the amount of DL MiCr data that would otherwise be accommodated in the feedback portion <NUM>. Accordingly, various portions of the UL-centric subframe can be adjusted to accommodate for one or more characteristics of the MiCr data without adjusting the total size or length of the UL-centric subframe or TTI (e.g., <NUM> microseconds). One of ordinary skill in the art understands that the example illustrated in <FIG> is not intended to limit the scope of the present disclosure and alternative examples of a UL-centric TDD subframe are within the scope of the present disclosure.

<FIG> is a diagram <NUM> illustrating an example of various communications according to aspects of the present disclosure. In this diagram <NUM>, three subframes (Subframe<NUM>, Subframe<NUM>, Subframe<NUM>) are shown for three TTIs (TTI<NUM>, TTI<NUM>, TTI<NUM>, respectively). Subframe<NUM> and Subframe<NUM> are DL-centric TDD subframes, as described in greater detail above with reference to <FIG>. Subframe<NUM> is an UL-centric TDD subframe, as described in greater detail above with reference to <FIG>. During each TTI, there exists at least one opportunity to transmit MiCr data and at least one opportunity to receive MiCr data. For example, during TTI<NUM>, MiCr data may be included in the data portion <NUM>' of Subframe<NUM> (thus enabling at least one opportunity to transmit MiCr data), and MiCr data may be included in the feedback portion <NUM>' of Subframe<NUM> (thus enabling at least one opportunity to receive MiCr data). As another example, during TTI<NUM>, MiCr data may be included in the data portion <NUM>" of Subframe<NUM> (thus enabling at least one opportunity to transmit MiCr data), and MiCr data may be included in the feedback portion <NUM>" of Subframe<NUM> (thus enabling at least one opportunity to receive MiCr data). As yet another example, during TTI<NUM>, MiCr data may be included in the control portion <NUM>' of Subframe<NUM> (thus enabling a first opportunity of at least one opportunity to receive MiCr data), MiCr data may be included in the data portion <NUM>' of Subframe<NUM> (thus enabling at least one opportunity to transmit MiCr data), and MiCr data may be included in the feedback portion <NUM>' (thus enabling a second opportunity of at least one opportunity to receive MiCr data).

One of ordinary skill in the art understands that the TDD spectrum cannot necessarily be considered an 'always on' resource for the communication system. As such, certain TDD carriers may sometimes be unavailable to the communication system. However, the FDD spectrum may be considered an 'always on' resource for the communication system. In some configurations, the feedback message (e.g., ACK/NACK) may be communicated using an FDD carrier. This may be done because (i) the FDD is regularly available to the communication system, and/or (ii) the feedback portions (e.g., feedback portions <NUM>', <NUM>", <NUM>') of the TDD subframe may be occupied with MiCr data. Accordingly, in some configurations, an FDD carrier may be utilized for communication of a feedback message corresponding to MiCr data. Also, in some configurations, an FDD carrier may be utilized for retransmission (e.g., hybrid automatic repeat request (HARQ) retransmission) of the MiCr data. In some configurations, the feedback message (e.g., ACK/NACK) may be communicated using a paired TDD carrier. In such configurations, the paired TDD carrier may be utilized for communication of a feedback message corresponding to MiCr data and/or for retransmission (e.g., HARQ retransmission) of the MiCr data.

The communication system may determine how frequently to utilize an UL-centered TDD subframe and/or a DL-centered TDD subframe according to various factors without deviating from the scope of the present disclosure. In some configurations, the communication system may determine how frequently to utilize an UL-centered TDD subframe and/or a DL-centered TDD subframe according to predetermined settings set by the network. Accordingly, the proportion, number, ratio, and/or percentage of UL-centered TDD subframes relative to DL-centered TDD subframes may be determined according to such predetermined settings set by the network. In some configurations, the communication system may determine how frequently to utilize an UL-centered TDD subframe and/or a DL-centered TDD subframe according to settings that are dynamically or semi-statically adjusted based on various traffic or network conditions. For instance, if current traffic or network conditions indicate a relatively high proportion, number, ratio, and/or percentage of UL data (e.g., UL MiCr data), then the communication system may utilize a greater proportion, number, ratio, and/or percentage of UL-centric subframes relative to the proportion, number, ratio, and/or percentage of DL-centric subframes. Conversely, if current traffic or network conditions indicate a relatively high proportion, number, ratio, and/or percentage of DL data (e.g., DL MiCr data), then the communication system may utilize a greater proportion, number, ratio, and/or percentage of DL-centric subframes relative to the proportion, number, ratio, and/or percentage of UL-centric subframes.

<FIG> is a diagram <NUM> illustrating an example of a hardware implementation of an apparatus <NUM> according to various aspects of the present disclosure. Generally, the apparatus <NUM> may be any device configured for wireless communication. In some configurations, the apparatus <NUM> may be DeviceA <NUM>, as described in greater detail above. In some configurations, the apparatus <NUM> may be Devices <NUM>, as described in greater detail above. The apparatus <NUM> may include a user interface <NUM>. The user interface <NUM> may be configured to receive one or more inputs from a user of the apparatus <NUM>. The user interface <NUM> may also be configured to display information to the user of the apparatus <NUM>. The user interface <NUM> may exchange data via the bus interface <NUM>.

The apparatus <NUM> may also include a transceiver <NUM>. The transceiver <NUM> may be configured to receive data and/or transmit data in communication with another apparatus. The transceiver <NUM> provides a means for communicating with another apparatus via a wired or wireless transmission medium. In some configurations, the transceiver <NUM> may provide the means for communicating MiCr data in a TDD subframe during a single TTI. According to aspects of the present disclosure, the term(s) 'communicate' and/or 'communicating' refer to at least one of a transmission or a reception. In other words, without deviating from the scope of the present disclosure, the term(s) 'communicate' and/or 'communicating' may refer to a transmission without a simultaneous/concurrent reception, a reception without a simultaneous/concurrent transmission, and/or a transmission with a simultaneous/concurrent reception.

In some examples, the transceiver <NUM> may provide DeviceA <NUM> with the means for transmitting data (e.g., MiCr data) to Devices <NUM> as well as the means for receiving data (e.g., MiCr data) from Devices <NUM> (e.g., in a TDD subframe during a single TTI). In some other examples, the transceiver <NUM> may provide Devices <NUM> with the means for transmitting data (e.g., MiCr data) to DeviceA <NUM> as well as the means for receiving data (e.g., MiCr data) from DeviceA <NUM> (e.g., in a TDD subframe during a single TTI). The transceiver <NUM> may be configured to perform such communications using various types of technologies, as described in greater detail above. One of ordinary skill in the art will understand that many types of technologies may perform such communication without deviating from the scope of the present disclosure.

The apparatus <NUM> may also include a memory <NUM>, one or more processors <NUM>, a computer-readable medium <NUM>, and a bus interface <NUM>. The bus interface <NUM> may provide an interface between a bus <NUM> and the transceiver <NUM>. The memory <NUM>, the one or more processors <NUM>, the computer-readable medium <NUM>, and the bus interface <NUM> may be connected together via the bus <NUM>. The processor <NUM> may be communicatively coupled to the transceiver <NUM> and/or the memory <NUM>.

The processor <NUM> may include a TDD circuit <NUM>. The TDD circuit <NUM> may include various hardware components and/or may perform various algorithms that provide the means for enabling at least one opportunity to transmit MiCr data and at least one opportunity to receive the MiCr data in a TDD subframe during a single TTI. The TDD circuit <NUM> may also include various hardware components and/or may perform various algorithms that provide the means for communicating the MiCr data in the TDD subframe during the single TTI.

The processor <NUM> may also include an adjustment circuit <NUM>. The adjustment circuit <NUM> may include various hardware components and/or may perform various algorithms that provide the means for adjusting how much of the TDD subframe is configured for the at least one opportunity to transmit the MiCr data and how much of the TDD subframe is configured for the at least one opportunity to receive the MiCr data based on one or more characteristics of the MiCr data. The processor <NUM> may also include an FDD circuit <NUM>. The FDD circuit <NUM> may include various hardware components and/or may perform various algorithms that provide the means for utilizing an FDD carrier for communication of a feedback message corresponding to the MiCr data. The FDD circuit <NUM> may also include various hardware components and/or may perform various algorithms that provide the means for utilizing an FDD carrier for retransmission of the MiCr data. The foregoing description provides a non-limiting example of the processor <NUM> of the apparatus <NUM>. Although various circuits <NUM>, <NUM>, <NUM> are described above, one of ordinary skill in the art will understand that the processor <NUM> may also include various other circuits <NUM> that are in addition and/or alternative(s) to the aforementioned circuits <NUM>, <NUM>, <NUM>. Such other circuits <NUM> may provide the means for performing any one or more of the functions, methods, processes, features and/or aspects described herein.

The computer-readable medium <NUM> may include various computer-executable instructions. The computer-executable instructions may include computer-executable code configured to perform various functions and/or enable various aspects described herein. The computer-executable instructions may be executed by various hardware components (e.g., the processor <NUM> and/or any of its circuits <NUM>, <NUM>, <NUM>, <NUM>) of the apparatus <NUM>. The computer-executable instructions may be a part of various software programs and/or software modules. The computer-readable medium <NUM> may include TDD instructions <NUM>. The TDD instructions <NUM> may include computer-executable instructions configured for enabling at least one opportunity to transmit MiCr data and at least one opportunity to receive the MiCr data in a TDD subframe during a single TTI. The TDD instructions <NUM> may also include computer-executable instructions configured for communicating the MiCr data in the TDD subframe during the single TTI.

The computer-readable medium <NUM> may also include adjustment instructions <NUM>. The adjustment instructions <NUM> may include computer-executable instructions configured for adjusting how much of the TDD subframe is configured for the at least one opportunity to transmit the MiCr data and how much of the TDD subframe is configured for the at least one opportunity to receive the MiCr data based on one or more characteristics of the MiCr data. The computer-readable medium <NUM> may include FDD instructions <NUM>. The FDD instructions <NUM> may include computer-executable instructions configured for utilizing an FDD carrier for communication of a feedback message corresponding to the MiCr data. The FDD instructions <NUM> may also include computer-executable instructions configured for utilizing an FDD carrier for retransmission of the MiCr data. The foregoing description provides a non-limiting example of the computer-readable medium <NUM> of the apparatus <NUM>. Although various computer-executable instructions <NUM>, <NUM>, <NUM> are described above, one of ordinary skill in the art will understand that the computer-readable medium <NUM> may also include various other computer-executable instructions <NUM> that are in addition and/or alternative(s) to the aforementioned computer-executable instructions <NUM>, <NUM>, <NUM>. Such other computer-executable instructions <NUM> may be configured for any one or more of the functions, methods, processes, features and/or aspects described herein.

The memory <NUM> may include various memory modules. The memory modules may be configured to store, and have read therefrom, various values and/or information by the processor <NUM>, or any of its circuits <NUM>, <NUM>, <NUM>, <NUM>. The memory modules may also be configured to store, and have read therefrom, various values and/or information upon execution of the computer-executable code included in the computer-readable medium <NUM>, or any of its instructions <NUM>, <NUM>, <NUM>, <NUM>. The memory <NUM> may include scheduling data <NUM>. The scheduling data <NUM> may include at least some of the information included in one or more of the control portions <NUM>, <NUM>', <NUM>", <NUM>, <NUM>' described herein. The memory may also include MiCr data <NUM>. The MiCr data <NUM> may include at least some of the MiCr data that may be included in one or more of the control portions <NUM>, <NUM>', data portions <NUM>, <NUM>', <NUM>", <NUM>, <NUM>', and/or feedback portions <NUM>, <NUM>', <NUM>", <NUM>, <NUM>' described herein. The foregoing description provides a non-limiting example of the memory <NUM> of the apparatus <NUM>. Although various types of data of the memory <NUM> are described above, one of ordinary skill in the art will understand that the memory <NUM> may also include various other data that are in addition and/or alternative(s) to the aforementioned data <NUM>, <NUM>. Such other data may be associated with any one or more of the functions, methods, processes, features and/or aspects described herein.

One of ordinary skill in the art will also understand that the apparatus <NUM> may include alternative and/or additional features without deviating from the scope of the present disclosure. In accordance with various aspects of the present disclosure, an element, or any portion of an element, or any combination of elements may be implemented with a processing system that includes one or more processors <NUM>. Examples of the one or more processors <NUM> include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. The processing system may be implemented with a bus architecture, represented generally by the bus <NUM> and bus interface <NUM>. The bus <NUM> may include any number of interconnecting buses and bridges depending on the specific application of the processing system and the overall design constraints. The bus <NUM> may link together various circuits including the one or more processors <NUM>, the memory <NUM>, and the computer-readable medium <NUM>. The bus <NUM> may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art.

The one or more processors <NUM> may be responsible for managing the bus <NUM> and general processing, including the execution of software stored on the computer-readable medium <NUM>. The software, when executed by the one or more processors <NUM>, causes the processing system to perform the various functions described below for any one or more apparatuses. The computer-readable medium <NUM> may also be used for storing data that is manipulated by the one or more processors <NUM> when executing software. The software may reside on the computer-readable medium <NUM>.

The computer-readable medium <NUM> may be a non-transitory computer-readable medium. A non-transitory computer-readable medium includes, by way of example, a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip), an optical disk (e.g., a compact disc (CD) or a digital versatile disc (DVD)), a smart card, a flash memory device (e.g., a card, a stick, or a key drive), a random access memory (RAM), a read only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), a register, a removable disk, and any other suitable medium for storing software and/or instructions that may be accessed and read by a computer. The computer-readable medium <NUM> may also include, by way of example, a carrier wave, a transmission line, and any other suitable medium for transmitting software and/or instructions that may be accessed and read by a computer. The computer-readable medium <NUM> may reside in the processing system, external to the processing system, or distributed across multiple entities including the processing system. The computer-readable medium <NUM> may be embodied in a computer program product. By way of example and not limitation, a computer program product may include a computer-readable medium in packaging materials. Those skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system.

<FIG> is a diagram <NUM> illustrating an example of various methods and/or processes according to aspects of the present disclosure. The methods and/or processes may be performed by an apparatus. In some configurations, such an apparatus is the apparatus <NUM> described above with reference to <FIG>. In some configurations, such an apparatus is DeviceA <NUM> (described above). In some configurations, such an apparatus is Devices <NUM> (described above). At block <NUM>, the apparatus (e.g., apparatus <NUM>, DeviceA <NUM>, Devices <NUM>) may generate instructions for a transceiver to enable at least one opportunity to transmit MiCr data and at least one opportunity to receive the MiCr data in a TDD subframe during a single TTI. For example, referring to <FIG>, during TTI<NUM>, MiCr data may be included in the data portion <NUM>' of Subframe<NUM> (thus enabling at least one opportunity to transmit MiCr data), and MiCr data may be included in the feedback portion <NUM>' of Subframe<NUM> (thus enabling at least one opportunity to receive MiCr data). During TTI<NUM>, MiCr data may be included in the data portion <NUM>" of Subframe<NUM> (thus enabling at least one opportunity to transmit MiCr data), and MiCr data may be included in the feedback portion <NUM>" of Subframe<NUM> (thus enabling at least one opportunity to receive MiCr data). During TTI<NUM>, MiCr data may be included in the control portion <NUM>' of Subframe<NUM> (thus enabling a first opportunity of at least one opportunity to receive MiCr data), MiCr data may be included in the data portion <NUM>' of Subframe<NUM> (thus enabling at least one opportunity to transmit MiCr data), and MiCr data may be included in the feedback portion <NUM>' (thus enabling a second opportunity of at least one opportunity to receive MiCr data).

In some configurations, at block <NUM>, the apparatus (e.g., apparatus <NUM>, DeviceA <NUM>, Devices <NUM>) adjusts how much of the TDD subframe is configured for the at least one opportunity to transmit the MiCr data and how much of the TDD subframe is configured for the at least one opportunity to receive the MiCr data based on one or more characteristics of the MiCr data. For example, one or more of the partitions <NUM>, <NUM>, <NUM> in <FIG> and/or one or more of the partitions <NUM>, <NUM>, <NUM> may be adjusted, altered, optimized, and/or otherwise changed in location and/or position based one or more characteristics of the MiCr data. Characteristics of the MiCr data may include the loading of the MiCr data, the amount of MiCr data to be transmitted, the amount of MiCr data to be received, and/or various other suitable factors.

In some configurations, at block <NUM>, the apparatus (e.g., apparatus <NUM>, DeviceA <NUM>, Devices <NUM>) utilizes a paired carried (e.g., an FDD carrier or a paired TDD carrier) for communication of a feedback message corresponding to the MiCr data. Because MiCr data may be included in at least some of the feedback portions (e.g., feedback portions <NUM>', <NUM>", <NUM>' in <FIG>), the feedback message (e.g., ACK/NACK) may be communicated using an FDD carrier or a TDD carrier. In some configurations, at block <NUM>, the apparatus may utilize a paired carried (e.g., an FDD carrier or a paired TDD carrier) for retransmission of the MiCr data. For example, if the feedback message (corresponding to the MiCr data transmission) is a NACK, then an FDD carrier or a paired TDD carrier may be utilized for HARQ retransmission of that MiCr data. In some configurations, the apparatus (e.g., apparatus <NUM>, DeviceA <NUM>, Devices <NUM>) transmits the MiCr data in the TDD subframe and receives the MiCr data in the TDD subframe during the same, single TTI. As described in greater detail above, such a TDD subframe may be considered a self-contained TDD subframe. Examples of such subframes are described above with reference to <FIG>, for example, and therefore will not be repeated. At block <NUM>, the apparatus may communicate the MiCr data in the TDD subframe during the single TTI.

The methods and/or processes described with reference to <FIG> are provided for illustrative purposes and are not intended to limit the scope of the present disclosure. The methods and/or processes described with reference to <FIG> may be performed in sequences different from those illustrated therein without deviating from the scope of the present disclosure. Additionally, some or all of the methods and/or processes described with reference to <FIG> may be performed individually and/or together without deviating from the scope of the present disclosure.

The above description is provided to enable any person skilled in the art to practice the various aspects described herein. Thus, the claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language of the claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more. As an example, "at least one of: a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b and c. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are intended to be encompassed by the claims. §<NUM>(f), unless the element is expressly recited using the phrase "means for" or, in the case of a method claim, the element is recited using the phrase "step for.

In the following, further examples are described to facilitate the understanding of the invention.

In a first further example, an apparatus for wireless communication is described, the apparatus comprising a transceiver, a memory, and at least one processor communicatively coupled to the transceiver and the memory, wherein the at least one processor and the memory are configured to generate instructions for the transceiver to enable at least one opportunity to transmit mission critical (MiCr) data and at least one opportunity to receive MiCr data in a time division duplex (TDD) subframe during a single transmission time interval (TTI), and to communicate the MiCr data in the TDD subframe during the single TTI. Further, the apparatus may comprise that the at least one processor and the memory are further configured to, based on one or more characteristics of the MiCr data, generate instructions for the transceiver to adjust how much of the TDD subframe is configured for the at least one opportunity to transmit the MiCr data and how much of the TDD subframe is configured for the at least one opportunity to receive the MiCr data. Also, the apparatus may comprise that the TDD subframe comprises a downlink (DL)-centric TDD subframe, the DL-centric TDD subframe comprising a first portion comprising the at least one opportunity to transmit the MiCr data, a guard period following the first portion, and a second portion following the guard period, wherein the second portion corresponds to the first portion and comprises the at least one opportunity to receive MiCr data. Also, the apparatus may comprise that the TDD subframe comprises an uplink (UL)-centric TDD subframe, the UL-centric TDD subframe comprising a first portion comprising a first opportunity of the at least one opportunity to receive the MiCr data, a guard period following the first portion, a second portion following the guard period, wherein the second portion comprises the at least one opportunity to transmit the MiCr data, and a third portion following the second portion, wherein the third portion corresponds to the second portion and comprises a second opportunity of the at least one opportunity to receive the MiCr data. Further, the apparatus may comprise that the at least one processor and the memory are further configured to generate instructions for the transceiver to utilize a frequency duplex division (FDD) carrier or a paired TDD carrier for communication of a feedback message corresponding to the MiCr data. Also, the apparatus may comprise that the at least one processor and the memory are further configured to generate instructions for the transceiver to utilize a frequency duplex division (FDD) carrier or a paired TDD carrier for retransmission of the MiCr data. Also, the apparatus may comprise that the single TTI comprises no greater than <NUM> microseconds. Further, the apparatus may comprise that the MiCr data comprises data having a latency requirement lower than a latency requirement of other data included in the TDD subframe. Further, the apparatus may comprise that the MiCr data comprises data having a priority requirement higher than a priority requirement of other data included in the TDD subframe. Also, the apparatus may comprise that the MiCr data comprises data having a reliability requirement higher than a reliability requirement of other data included in the TDD subframe. Also, the apparatus may comprise that the TDD subframe comprises control information in a control portion of the TDD subframe, data information in a data portion of the TDD subframe, the data information corresponding to the control information, and acknowledgement information in an acknowledgement portion of the TDD subframe, the acknowledgement information corresponding to the data information, wherein the control portion, the data portion, and the acknowledgement portion are contained in the same TDD subframe.

In a second further example, a method for wireless communication is described, the method comprising generating instructions for a transceiver to enable at least one opportunity to transmit mission critical (MiCr) data and at least one opportunity to receive MiCr data in a time division duplex (TDD) subframe during a single transmission time interval (TTI), and communicating the MiCr data in the TDD subframe during the single TTI. Further, the method may comprise, based on one or more characteristics of the MiCr data, generating instructions for the transceiver to adjust how much of the TDD subframe is configured for the at least one opportunity to transmit the MiCr data and how much of the TDD subframe is configured for the at least one opportunity to receive the MiCr data. Also, the method may comprise that the TDD subframe comprises a downlink (DL)-centric TDD subframe, the DL-centric TDD subframe comprising a first portion comprising the at least one opportunity to transmit the MiCr data, a guard period following the first portion, and a second portion following the guard period, wherein the second portion corresponds to the first portion and comprises the at least one opportunity to receive MiCr data. Further, the method may comprise that the TDD subframe comprises an uplink (UL)-centric TDD subframe, the UL-centric TDD subframe comprising a first portion comprising a first opportunity of the at least one opportunity to receive the MiCr data, a guard period following the first portion, a second portion following the guard period, wherein the second portion comprises the at least one opportunity to transmit the MiCr data, and a third portion following the second portion, wherein the third portion corresponds to the second portion and comprises a second opportunity of the at least one opportunity to receive the MiCr data. Also, the method may comprise at least one of generating instructions for the transceiver to utilize a frequency duplex division (FDD) carrier or a paired TDD carrier for communication of a feedback message corresponding to the MiCr data, or generating instructions for the transceiver to utilize an FDD carrier or a paired TDD carrier for retransmission of the MiCr data. Further, the method may comprise that the single TTI comprises no greater than <NUM> microseconds, and that the MiCr data comprises data having at least one of a latency requirement lower than a latency requirement of other data included in the TDD subframe, a priority requirement higher than a priority requirement of other data included in the TDD subframe, or a reliability requirement higher than a reliability requirement of other data included in the TDD subframe. Also, the method may comprise that the TDD subframe comprises control information in a control portion of the TDD subframe, data information in a data portion of the TDD subframe, the data information corresponding to the control information, and acknowledgement information in an acknowledgement portion of the TDD subframe, the acknowledgement information corresponding to the data information, wherein the control portion, the data portion, and the acknowledgement portion are contained in the same TDD subframe.

In a third further example, a computer-readable medium configured for wireless communication is described, the computer-readable medium comprising computer-executable instructions configured for enabling at least one opportunity to transmit mission critical (MiCr) data and at least one opportunity to receive MiCr data in a time division duplex (TDD) subframe during a single transmission time interval (TTI), and for communicating the MiCr data in the TDD subframe during the single TTI. Further, the computer-readable medium may comprise that the computer-executable instructions are further configured for, based on one or more characteristics of the MiCr data, adjusting how much of the TDD subframe is configured for the at least one opportunity to transmit the MiCr data and how much of the TDD subframe is configured for the at least one opportunity to receive the MiCr data. Also, the computer-readable medium may comprise that the TDD subframe comprises a downlink (DL)-centric TDD subframe, the DL-centric TDD subframe comprising a first portion comprising the at least one opportunity to transmit the MiCr data, a guard period following the first portion, and a second portion following the guard period, wherein the second portion corresponds to the first portion and comprises the at least one opportunity to receive MiCr data. Further, the computer-readable medium may comprise that the TDD subframe comprises an uplink (UL)-centric TDD subframe, the UL-centric TDD subframe comprising a first portion comprising a first opportunity of the at least one opportunity to receive the MiCr data, a guard period following the first portion, a second portion following the guard period, wherein the second portion comprises the at least one opportunity to transmit the MiCr data; and a third portion following the second portion, wherein the third portion corresponds to the second portion and comprises a second opportunity of the at least one opportunity to receive the MiCr data. Also, the computer-readable medium may comprise that the computer-executable instructions are further configured for at least one of utilizing a frequency duplex division (FDD) carrier or a paired TDD carrier for communication of a feedback message corresponding to the MiCr data, or utilizing an FDD carrier or a paired TDD carrier for retransmission of the MiCr data. Also, the computer-readable medium may comprise that the single TTI comprises no greater than <NUM> microseconds, and that the MiCr data comprises data having at least one of a latency requirement lower than a latency requirement of other data included in the TDD subframe, a priority requirement higher than a priority requirement of other data included in the TDD subframe, or a reliability requirement higher than a reliability requirement of other data included in the TDD subframe.

Claim 1:
An apparatus for wireless communication, the apparatus comprising:
means for communicating a time division duplex, TDD, subframe (<NUM>, <NUM>) during a single transmission time interval, TTI, wherein the TDD subframe (<NUM>, <NUM>) includes:
control information in a control portion (<NUM>, <NUM>) of the TDD subframe (<NUM>, <NUM>),
data in a data portion (<NUM>, <NUM>) of the TDD subframe (<NUM>, <NUM>), and
acknowledgement information in a feedback portion (<NUM>, <NUM>) of the TDD subframe (<NUM>, <NUM>), the acknowledgement information corresponding to the data.