WO2017142581A1

WO2017142581A1 - Multiplexing uplink control information and data on physical uplink shared channel

Info

Publication number: WO2017142581A1
Application number: PCT/US2016/039057
Authority: WO
Inventors: Gang Xiong; Ajit Nimbalker; Hong He; Jong-Kae Fwu
Original assignee: Intel IP Corporation
Priority date: 2016-02-16
Filing date: 2016-06-23
Publication date: 2017-08-24
Also published as: CN108702238B; CN108702238A

Abstract

Techniques for transmitting uplink control information (UCI) on a 5G physical uplink shared channel (xPUSCH) are provided. By allowing UCI to be transmitted on the xPUSCH, UCI performance can be improved. The UCI and data can be multiplexed on the xPUSCH. The UCI and data can be multiplexed in a time division multiplexing (TDM) or a frequency division multiplexing (FDM) manner. The UCI can be mapped onto the xPUSCH in a time first manner or a frequency first manner. Downlink control information can provide a mobile device with a resource allocation for the UCI and with a manner for multiplexing the UCI and data on the xPUSCH. The xPUSCH can be part of a 5G self-contained time division duplex (TDD) subframe structure or a frequency division duplex (FDD) subframe structure.

Description

MULTIPLEXING UPLINK CONTROL INFORMATION AND DATA ON PHYSICAL

UPLINK SHARED CHANNEL

RELATED CASE

This application claims priority to United States Provisional Patent Application Number 62/295,927, filed February 16, 2016, the entirety of which is hereby incorporated by reference.

TECHNICAL FIELD

Embodiments herein generally relate to communications between devices in broadband wireless communications networks.

BACKGROUND

Uplink control information (UCI) often carries information related to messaging confirmation protocols (e.g., a hybrid automatic repeat request (HARQ) retransmission scheme) as well as information regarding the operational conditions at a mobile device. In many instances, the UCI payload can be quite large. For many conventional wireless communication systems, UCI is restricted to being communicated over control channels. Restricting UCI to certain control channels can prevent robust UCI performance. Improved techniques and systems for ensuring improved UCI performance, including such techniques and systems for 5G systems, have yet to be developed that overcome the deficiencies of these conventional wireless systems.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary operating environment.

FIG. 2A illustrates an exemplary downlink self-contained time-division duplex subframe structure.

FIG. 2B illustrates an exemplary uplink self-contained time-division duplex subframe structure.

FIG. 3 illustrates an exemplary self-contained subframe structure based on a frequency first resource mapping scheme for physical uplink shared channel (xPUSCH) transmission.

FIG. 4 illustrates an exemplary self-contained subframe structure based on a frequency first resource mapping scheme for xPUSCH transmission that includes uplink control information (UCI).

FIG. 5A illustrates a first exemplary self-contained subframe structure based on a frequency first resource mapping scheme for xPUSCH transmission that includes frequency division multiplexing (FDM) of UCI and data on xPUSCH.

FIG. 5B illustrates a second exemplary self-contained subframe structure based on a frequency first resource mapping scheme for xPUSCH transmission that includes FDM based multiplexing of UCI and data on xPUSCH. FIG. 6A illustrates a first exemplary self-contained subframe structure based on a frequency first resource mapping scheme for xPUSCH transmission that includes FDM based multiplexing of UCI and data on xPUSCH with frequency diversity.

FIG. 6B illustrates a second exemplary self-contained subframe structure based on a frequency first resource mapping scheme for xPUSCH transmission that includes FDM based multiplexing of UCI and data on xPUSCH with frequency diversity.

FIG. 6C illustrates a third exemplary self-contained subframe structure based on a frequency first resource mapping scheme for xPUSCH transmission that includes FDM based multiplexing of UCI and data on xPUSCH with frequency diversity.

FIG. 7 illustrates an exemplary self-contained subframe structure with UCI mapped in a time first manner with data within xPUSCH.

FIG. 8 illustrates an exemplary coding scheme for UCI transmission.

FIG. 9 illustrates an embodiment of a logic flow.

FIG. 10 illustrates an embodiment of a storage medium.

FIG. 11 illustrates an embodiment of a first device.

FIG. 12 illustrates an embodiment of a second device.

FIG. 13 illustrates an embodiment of a wireless network.

DETAILED DESCRIPTION

Various embodiments may be generally directed to techniques for transmitting uplink control information (UCI) on a 5G physical uplink shared channel (xPUSCH). By allowing UCI to be transmitted on the xPUSCH, UCI performance can be improved. In various embodiments, the UCI and data can be multiplexed on the xPUSCH. The UCI and data can be multiplexed in a time division multiplexing (TDM) or a frequency division multiplexing (FDM) manner. The UCI can be mapped onto the xPUSCH in a time first manner or a frequency first manner.

Downlink control information can provide a mobile device with a resource allocation for the UCI and with a manner for multiplexing the UCI and data on the xPUSCH. The xPUSCH can be part of a 5G self-contained time division duplex (TDD) subframe structure or a frequency division duplex (FDD) subframe structure. Other embodiments are described and claimed.

Various embodiments may comprise one or more elements. An element may comprise any structure arranged to perform certain operations. Each element may be implemented as hardware, software, or any combination thereof, as desired for a given set of design parameters or performance constraints. Although an embodiment may be described with a limited number of elements in a certain topology by way of example, the embodiment may include more or less elements in alternate topologies as desired for a given implementation. It is worthy to note that any reference to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrases "in one embodiment," "in some

embodiments," and "in various embodiments" in various places in the specification are not necessarily all referring to the same embodiment.

The techniques disclosed herein may involve transmission of data over one or more wireless connections using one or more wireless mobile broadband technologies. For example, various embodiments may involve transmissions over one or more wireless connections according to one or more 3rd Generation Partnership Project (3GPP), 3GPP Long Term

Evolution (LTE), and/or 3GPP LTE-Advanced (LTE-A) technologies and/or standards, including their revisions, progeny and variants - including 4G and 5G wireless networks.

Various embodiments may additionally or alternatively involve transmissions according to one or more Global System for Mobile Communications (GSM)/Enhanced Data Rates for GSM Evolution (EDGE), Universal Mobile Telecommunications System (UMTS)/High Speed Packet Access (HSPA), and/or GSM with General Packet Radio Service (GPRS) system (GSM/GPRS) technologies and/or standards, including their revisions, progeny and variants.

Examples of wireless mobile broadband technologies and/or standards may also include, without limitation, any of the Institute of Electrical and Electronics Engineers (IEEE) 802.16 wireless broadband standards such as IEEE 802.16m and/or 802.16p, International Mobile Telecommunications Advanced (IMT-ADV), Worldwide Interoperability for Microwave Access (WiMAX) and/or WiMAX II, Code Division Multiple Access (CDMA) 2000 (e.g., CDMA2000 lxRTT, CDMA2000 EV-DO, CDMA EV-DV, and so forth), High Performance Radio

Metropolitan Area Network (HIPERMAN), Wireless Broadband (WiBro), High Speed

Downlink Packet Access (HSDPA), High Speed Orthogonal Frequency-Division Multiplexing (OFDM) Packet Access (HSOPA), High-Speed Uplink Packet Access (HSUPA) technologies and/or standards, including their revisions, progeny and variants.

Some embodiments may additionally or alternatively involve wireless communications according to other wireless communications technologies and/or standards. Examples of other wireless communications technologies and/or standards that may be used in various

embodiments may include, without limitation, other IEEE wireless communication standards such as the IEEE 802.11, IEEE 802.11a, IEEE 802.11b, IEEE 802. l lg, IEEE 802.11η, IEEE 802.Hu, IEEE 802.1 lac, IEEE 802. Had, IEEE 802.11af, and/or IEEE 802.11ah standards, High-Efficiency Wi-Fi standards developed by the IEEE 802.11 High Efficiency WLAN (HEW) Study Group, Wi-Fi Alliance (WFA) wireless communication standards such as Wi-Fi, Wi-Fi Direct, Wi-Fi Direct Services, Wireless Gigabit (WiGig), WiGig Display Extension (WDE), WiGig Bus Extension (WBE), WiGig Serial Extension (WSE) standards and/or standards developed by the WFA Neighbor Awareness Networking (NAN) Task Group, machine-type communications (MTC) standards such as those embodied in 3GPP Technical Report (TR) 23.887, 3GPP Technical Specification (TS) 22.368, and/or 3GPP TS 23.682, and/or near-field communication (NFC) standards such as standards developed by the NFC Forum, including any revisions, progeny, and/or variants of any of the above. The embodiments are not limited to these examples.

In addition to transmission over one or more wireless connections, the techniques disclosed herein may involve transmission of content over one or more wired connections through one or more wired communications media. Examples of wired communications media may include a wire, cable, metal leads, printed circuit board (PCB), backplane, switch fabric, semiconductor material, twisted-pair wire, co-axial cable, fiber optics, and so forth. The embodiments are not limited in this context.

FIG. 1 illustrates an exemplary operating environment 100 such as may be representative of some embodiments in which techniques for multiplexing uplink control information and data may be implemented. As further described herein, these techniques can include multiplexing uplink control information and data on a 5G physical uplink shared channel (PUSCH). The operating environment 100 can include a mobile device 102 and a cellular base station 104. The mobile device 102 can communicate with the base station 104 over a wireless communications interface 106. The mobile device 102 can be a smartphone, tablet, laptop, netbook, or other mobile computing device capable of communicating wirelessly with one or more wireless communication networks. As an example, the mobile device 102 can be a user equipment (UE). The base station 104 can be a cellular base station such as, for example, an evolved node B (eNB). The base station 104 can be a serving cell for the UE 102 such as, for example, a primary or secondary serving cell. The wireless communications interface 106 can be, for example, a wireless interface for any of the wireless networks or standards described herein including, for example, a 4G, LTE, or 5G wireless network. The mobile device 102 and the base station 104 can implement the multiplexing techniques described herein.

The 5G wireless communication system is expected to provide access to information and the sharing of data virtually anywhere at any time by various users across a wide range of diverse applications. Further, the 5G wireless communication system is expected to evolve based on 3GPP LTE- Advanced with potential new Radio Access Technologies (RATs) to provide users with seamless wireless solutions that include high speed and low latency connections. To provide low latency transmissions, the 5G wireless communication system may use self- contained time-division duplex (TDD) subframe structures. FIGs. 2A and 2B illustrate exemplary self-contained TDD subframe structures. A self- contained TDD subframe can include uplink (UL) and downlink (DL) communications in the same subframe. In some instances, a self-contained TDD subframe can include

acknowledgement (ACK) messages and/or non-acknowledgement (NACK) messages. Further, a self-contained TDD subframe can include ACK/NACK messages within the same subframe as received data to which the ACK/NACK messages may correspond. The ACK/NACK messages may be part of an automatic repeat request (ARQ) retransmission scheme or hybrid automatic repeat request (HARQ) retransmission scheme.

FIG. 2A illustrates an exemplary DL self-contained TDD subframe structure 202. The DL self-contained TDD subframe structure 202 can be implemented by the base station 104 and/or the mobile device 102 depicted in FIG. 1. The DL self-contained TDD subframe structure 202 can be, for example, a 5G DL self-contained TDD subframe structure. As such, the channels and communications in the DL self-contained TDD subframe structure 202 can be 5G channels and communications.

As shown in FIG. 2A, the DL self-contained TDD subframe structure 202 can include a physical downlink control channel (xPDCCH) 204, a physical downlink shared channel

(xPDSCH) 206, a guard period (GP) 208, and a physical uplink control channel (xPUCCH) 210. To accommodate the switching time between DL and UL communications and the round-trip propagation delay, the GP 208 can be inserted between the xPDSCH 206 and the xPUCCH 210. The GP 208 can have a duration, for example, of one or two OFDM symbols. A duration of the DL self-contained TDD subframe structure 202 is indicated by 212.

FIG. 2B illustrates an exemplary UL self-contained TDD subframe structure 214. The UL self-contained TDD subframe structure 214 can be implemented by the base station 104 and/or the mobile device 102 depicted in FIG. 1. The UL self-contained TDD subframe structure 214 can be, for example, a 5G DL self-contained TDD subframe structure. As such, the channels and communications in the UL self-contained TDD subframe structure 214 can be 5G channels and communications.

As shown in FIG. 2B, the UL self-contained TDD subframe structure 202 can include an xPDCCH 204, a GP 208, a physical uplink shared channel (xPUSCH) 216, and an xPUCCH 210. To accommodate the switching time between DL and UL communications and the round-trip propagation delay, the GP 208 can be inserted between the xPDCCH 204 and the xPUSCH 216. A duration of the UL self-contained TDD subframe structure 214 can also be indicated by 212.

The xPUCCH 210 may include uplink control information (UCI). The UCI may include HARQ ACK/NACK feedback and/or channel state information (CSI) including, for example, channel quality indicator (CQI), pre-coding matrix indicator (PMI), and/or rank indicator (RI). For cmWave and mmWave bands, UCI may also include a beam related information, such as beamforming reference signal (BRS) index and/or a BRS reception power (BRS-RP) report.

Typically, the UCI can require more robust performance than a data channel. Further, UCI payloads may be relatively large due to the amount of information the UCI payload may contain about the condition of a mobile device (e.g., the mobile device or UE 102 depicted in FIG. 1). Techniques described herein enable the UCI to be carried within the xPUSCH 216 to improve the link budget by multiplexing the UCI and data on the xPUSCH 216, thereby improving performance over systems that are limited to carrying UCI in the xPUCCH 210.

As shown in FIG. 2B, data within the xPUSCH 216 and the xPUCCH 210 are multiplexed in a time division multiplexing (TDM) manner. The xPUCCH 210 can have a duration of, for example, one or more OFDM symbols. Under a scenario where one symbol is allocated for the xPUCCH 210, increasing the number of frequency resources for transmission of the xPUCCH 210 may not improve the link budget as would be expected. The lack of improved link budget can be due to the coding rate being reduced at the cost of increased noise power when more frequency resources are allocated for the xPUCCH 210. As such, with the same transmit power, the maximum coupling loss (MCL) between a mobile device (e.g., the mobile device 102) and a base station (e.g., the base station 104) can remain the same - and so also the link budget for transmission of the xPUCCH 210.

To improve the link budget for transmitting UCI, techniques described herein provide for the UCI to be carried in the xPUSCH 216 along with the data of the xPUSCH 216. Under a scenario where the mobile device 102 is assigned with uplink resources for transmission on an uplink shared channel (UL-SCH) and the UCI payload size is relatively large, techniques described herein enable the UCI to be transmitted in the xPUSCH 216 together with coded UL- SCH data.

FIG. 3 illustrates an exemplary self-contained subframe structure 300 based on a frequency first resource mapping scheme for xPUSCH transmission. As shown in FIG. 3, the self- contained subframe structure 300 can include an xPDCCH 314, a GP 316, and an xPUSCH 318. A duration of the self-contained subframe structure 300 can be indicated by 320. An indicator 302 indicates the self-contained subframe structure 300 relative to increasing frequency. An indicator 304 indicates the self-contained subframe structure 300 relative to increasing time. An OFDM symbol index 322 illustrates the contents of the self-contained subframe structure 300 relative to the number of OFDM symbols occupied by the self-contained subframe structure 300. As shown, the xPDCCH 314 occupies OFDM symbol "0", the GP 316 occupies OFDM symbol "1", and the xPUSCH 318 occupies OFDM symbols "2" through "13". Data transmission in the xPUSCH 318 for the self-contained subframe structure 300 may be mapped in a frequency domain first manner. By mapping data transmission in the xPUSCH 318 in a frequency first manner, a base station (e.g., the base station 104) that receives the self- contained subframe structure 300 can decode the xPUSCH 318 more quickly since pipeline and parallel processing of the xPUSCH 318 can be maximized. As shown in FIG. 3, the xPUSCH 318 can occupy a frequency range 306. Below the frequency range 306 occupied by the xPUSCH 318 can be a lower frequency range 308. Above the frequency range 306 occupied by the xPUSCH 318 can be an upper frequency range 310. The frequency ranges 308 and 310 can be frequency ranges not occupied by the xPUSCH 318. The frequency ranges 308 and 310 can be frequency ranges occupied or used by another user. Although not shown in FIG. 3 for simplicity, an xPUCCH can be allocated in the last OFDM symbol - i.e., OFDM symbol "13". Arrows 312 illustrate that data in the xPUSCH 318 is filled in a frequency first manner - e.g., by occupying the frequency range 306 (e.g., from relatively lower to higher frequency) on a symbol-by-symbol manner.

According to the techniques described herein, when the UCI is scheduled for transmission together with data in the xPUSCH 318, UCI resource mapping (e.g., frequency resource mapping) can follow the same principle as the resource mapping of the data in the xPUSCH 318 - i.e., in a frequency first manner. FIG. 4 illustrates an exemplary self-contained subframe structure 400 based on a frequency first resource mapping scheme for xPUSCH transmission that includes UCI. As shown in FIG. 4, the xPUSCH 318 can occupy OFDM symbols "2" through "13" and the UCI 402 can occupy OFDM symbol "2" - i.e., the first OFDM symbol allocated for the xPUSCH 318. OFDM symbols "3" through "13" can include data 404. The UCI 402 and the data 404 within the xPUSCH 318 can be mapped in a frequency first manner with the UCI 402 occupying a single OFDM symbol after the GP 208.

FIG. 4 illustrates one example of a TDM based multiplexing scheme for the UCI 402 and the data 404 transmission within or on the xPUSCH 318. In general, the UCI 402 can occupy one or more of the OFDM symbols in the xPUSCH 318, within any region of the xPUSCH 318, over any frequency region, and with multiple occupied OFDM symbols being adjacent or non- adjacent. In various embodiments, the UCI 402 may span the entire uplink transmission region other than the region allocated for xPUCCH. In doing so, the link budget for the UCI 402 can be improved. Further, the UCI 402 can be multiplexed with coded UL-SCH data in the xPUSCH 318 in a frequency division multiplexing (FDM) manner.

Various embodiments provide for FDM based multiplexing of UCI and data on xPUSCH. Various embodiments provide for the FDM scheme used for multiplexing data on the PUSCH to be a SC-FDMA scheme. FIG. 5A illustrates an exemplary self-contained subframe structure 502 based on a frequency first resource mapping scheme for xPUSCH transmission that includes FDM based multiplexing of UCI and data on xPUSCH. As shown in FIG. 5A, UCI 504 can be contained within the allocated xPUSCH 318. The xPUSCH 318 can occupy a frequency range 506. Below the frequency range 506 occupied by the xPUSCH 318 can be a lower frequency range 510. Above the frequency range 506 occupied by the xPUSCH 318 can be an upper frequency range 508. The frequency ranges 508 and 510 can be frequency ranges not occupied by the xPUSCH 318. The frequency ranges 508 and 510 can be frequency ranges occupied or used by another user.

The UCI 504 can occupy a frequency range 512. The frequency range 512 can be a range of frequencies within the frequency range 506. That is, the UCI 504 can be allocated to an upper frequency region of the data transmission region allocated for the xPUSCH 318. The UCI 504 can occupy or be allocated the frequency range 512 for the entire duration of the xPUSCH 318. As shown in FIG. 5 A, the UCI 504 occupies an upper frequency range 512 of the xPUSCH 318 which is allocated the frequency range 506. As such, the UCI 504 is multiplexed in an FDM manner with data in the xPUSCH 318.

FIG. 5B illustrates an exemplary self-contained subframe structure 514 based on a frequency first resource mapping scheme for xPUSCH transmission that includes FDM based multiplexing of UCI and data on xPUSCH. As shown in FIG. 5B, UCI 516 can be contained within the allocated xPUSCH 318. The xPUSCH 318 can occupy a frequency range 518. Below the frequency range 518 occupied by the xPUSCH 318 can be a lower frequency range 522. Above the frequency range 518 occupied by the xPUSCH 318 can be an upper frequency range 520. The frequency ranges 520 and 522 can be frequency ranges not occupied by the xPUSCH 318. The frequency ranges 520 and 520 can be frequency ranges occupied or used by another user.

The UCI 516 can occupy a frequency range 524. The frequency range 524 can be a range of frequencies within the frequency range 518. That is, the UCI 516 can be allocated to a lower frequency region of the data transmission region allocated for the xPUSCH 318. The UCI 516 can occupy or be allocated the frequency range 524 for the entire duration of the xPUSCH 318. As shown in FIG. 5B, the UCI 516 occupies a lower frequency range 524 of the xPUSCH 318 which is allocated the frequency range 518. As such, the UCI 516 is multiplexed in an FDM manner with data in the xPUSCH 318.

In various embodiments, the UCI can be allocated to any frequency range within xPUSCH in an FDM manner. In various embodiments, the UCI can be allocated to a lower edge of the xPUSCH (e.g., as shown in FIG. 5B) or can be allocated to an upper edge of the xPUSCH (e.g., as shown in FIG. 5A). In various embodiments, the UCI can be allocated to a frequency range that is not adjacent to an upper or lower frequency boundary of the xPUSCH. For example, the UCI can be allocated to a frequency range bordered on either side by data contained in the xPUSCH. Further, the UCI can be occupied an allocated a designated frequency range within the xPUSCH for a period equal to the entire duration of the xPUSCH or for a period of time equal to less than the entire duration of the xPUSCH.

In various embodiments, a base station (e.g., the base station 104) can provide control and/or signaling information for coordinating the multiplexing of UCI with data on xPUSCH by a mobile device (e.g., the mobile device 102). The control or signaling information by the base station 104 can include various indications and/or bit fields. For example, the base station 104 can provide a first indication that indicates to the mobile device 102 that UCI can be multiplexed with data on xPUSCH. Further, the base station 104 can provide a second indication that indicates an allocation for the UCI or a payload for the UCI to be multiplexed with data in xPUSCH. In various embodiments, this second indication can be considered to be a resource allocation (e.g., an amount of frequency resource or time resource that can be occupied by the UCI within the xPUSCH). In various embodiments, an indication provided by the base station 104 in the DCI can be used by the mobile device 102 to determine the resource allocation for the UCI. The determined resource allocation can specify an amount of time and frequency range for the UCI for transmission within the xPUSCH with data. In general, a determined resource allocation can specify how much resource in terms of time and frequency within the resource allocated for the xPUSCH can be used for the UCI.

In various embodiments, the base station 104 can also provide a third indication that indicates where to position the UCI in the xPUSCH. In various embodiments, a one bit field provided by the base station 104 can specify where the UCI can be positioned. For example, a bit value of "0" can indicate that the UCI is to be allocated into an upper frequency range of xPUSCH (e.g., as shown in FIG. 5A) and a bit value of "1" can indicate that the UCI is to be allocated into a lower frequency range of xPUSCH (e.g., as shown in FIG. 5B). In general, a bit field indicating where to position the UCI within the xPUSCH can be of any size and can be proportional in size to the number of various possible positions of the UCI within xPUSCH.

In various embodiments, indications from the base station 104 regarding allowance of multiplexing, payload size, and payload positioning can be accomplished using one or more bit fields of various sizes. In various embodiments, these indications can be provided within xPDCCH (e.g., xPDCCH 204). In various embodiments, these indications can be provided by downlink control information (DCI).

In various embodiments, resource allocation (e.g., payload size) for UCI on xPUSCH can be separately indicated in the DCI format for uplink grant from data resource allocation. In various embodiments, a number of physical resource blocks (PRBs) may be allocated for UCI transmission based on interpretation of a bit field reserved for indicating as much. Table 1 below illustrates an exemplary manner for allocating one, two, four, or eight PRBs for UCI transmission based on a two bit field.

Table 1

In various embodiments, the base station 104 can provide a further indication on the type of multiplexing to be used for multiplexing UCI with data on xPUSCH. For example, an indication can be provided to indicate if the multiplexing is to be performed in a frequency first manner or in a time first manner, as described further below.

FIGs. 6A-6C illustrate additional exemplary multiplexing of UCI with data on xPUSCH in a frequency first manner. In particular, FIGs. 6A-6C illustrate exemplary transmission schemes for UCI that can exploit frequency diversity.

FIG. 6A illustrates an exemplary self-contained subframe structure 602 based on a frequency first resource mapping scheme for xPUSCH transmission that includes FDM based multiplexing of UCI and data on xPUSCH with frequency diversity. As shown in FIG. 6A, UCI 604 can be contained within the allocated xPUSCH 318. The xPUSCH 318 can occupy a frequency range 606. Below the frequency range 606 occupied by the xPUSCH 318 can be a lower frequency range 608. Above the frequency range 606 occupied by the xPUSCH 318 can be an upper frequency range 610. The frequency ranges 608 and 610 can be frequency ranges not occupied by the xPUSCH 318. The frequency ranges 608 and 610 can be frequency ranges occupied or used by another user.

The UCI 604 can occupy two distinct regions within xPUSCH 318. Specifically, the UCI 604 can include a first UCI portion occupying a first frequency range 612 and a second UCI portion occupying a second frequency range 614. The first and second UCI frequency ranges 612 and 614 can be contained within the xPUSCH 318 frequency range 606. The first UCI frequency range 612 can be adjacent to data transmitted in xPUSCH 318 within an upper frequency region of xPUSCH 318. The second UCI frequency range 614 can be adjacent to data transmitted in xPUSCH 318 within a lower frequency region of xPUSCH 318. The UCI 604 can occupy or be allocated within the frequency ranges 612 and 614 for the entire duration of the xPUSCH 318. For the self-contained subframe structure 602, the UCI 604 is multiplexed in an FDM manner with data in the xPUSCH 318 and, by being distributed over distinct frequency ranges, can exploit the benefit of frequency diversity.

FIG. 6B illustrates an exemplary self-contained subframe structure 616 based on a frequency first resource mapping scheme for xPUSCH transmission that includes FDM based multiplexing of UCI and data on xPUSCH with frequency diversity. As shown in FIG. 6B, UCI 618 can be contained within the allocated xPUSCH 318. The xPUSCH 318 can occupy a frequency range 620. Below the frequency range 620 occupied by the xPUSCH 318 can be a lower frequency range 622. Above the frequency range 620 occupied by the xPUSCH 318 can be an upper frequency range 624. The frequency ranges 622 and 624 can be frequency ranges not occupied by the xPUSCH 318. The frequency ranges 622 and 624 can be frequency ranges occupied or used by another user.

Similar to as shown in FIG. 6 A, the UCI 618 can occupy two distinct regions within xPUSCH 318. Specifically, the UCI 618 can include a first UCI portion occupying a first frequency range 626 for a first amount of time 630 and a second UCI portion occupying a second frequency range 626 for a second amount of time 632. As shown in FIG. 6B, the first and second amounts of time 630 and 632 are non-overlapping but are not so limited. The first and second UCI frequency ranges 626 and 628 can be contained within the xPUSCH 318 frequency range 620. The first UCI frequency range 626 can be adjacent to data transmitted in xPUSCH 318 within an upper frequency region of xPUSCH 318. The second UCI frequency range 628 can be adjacent to data transmitted in xPUSCH 318 within a lower frequency region of xPUSCH 318. The UCI 618 can occupy or be allocated within the frequency ranges 626 and 628 for less than the entire duration of the xPUSCH 318. For the self-contained subframe structure 616, the UCI 618 is multiplexed in an FDM manner with data in the xPUSCH 318 and, by being distributed over distinct frequency ranges, can exploit the benefit of frequency diversity.

FIG. 6C illustrates an exemplary self-contained subframe structure 634 based on a frequency first resource mapping scheme for xPUSCH transmission that includes FDM based multiplexing of UCI and data on xPUSCH with frequency diversity. As shown in FIG. 6C, UCI 636 can be contained within the allocated xPUSCH 318. The xPUSCH 318 can occupy a frequency range 638. Below the frequency range 638 occupied by the xPUSCH 318 can be a lower frequency range 640. Above the frequency range 638 occupied by the xPUSCH 318 can be an upper frequency range 642. The frequency ranges 640 and 642 can be frequency ranges not occupied by the xPUSCH 318. The frequency ranges 640 and 642 can be frequency ranges occupied or used by another user. Similar to as shown in FIGs. 6A and 6B, the UCI 636 can occupy two distinct regions within xPUSCH 318. Specifically, the UCI 636 can include a first UCI portion occupying a first frequency range 644 for a first amount of time 650 and a second UCI portion occupying a second frequency range 646 for a second amount of time 646. As shown inn FIG. 6C, the first and second amounts of time 648 and 650 are non-overlapping but are not so limited. Further, the time allocated for the first UCI portion occupying frequency range 644 can occur after transmission of the second UCI portion occupying frequency range 646. The first and second UCI frequency ranges 644 and 646 can be contained within the xPUSCH 318 frequency range 638.

The first UCI frequency range 644 can be adjacent to data transmitted in xPUSCH 318 within an upper frequency region of xPUSCH 318. The second UCI frequency range 646 can be adjacent to data transmitted in xPUSCH 318 within a lower frequency region of xPUSCH 318. The UCI 636 can occupy or be allocated within the frequency ranges 644 and 646 for less than the entire duration of the xPUSCH 318. For the self-contained subframe structure 634, the UCI 638 is multiplexed in an FDM manner with data in the xPUSCH 318 and, by being distributed over distinct frequency ranges, can exploit the benefit of frequency diversity.

Overall, in various embodiments, self-contained subframe structures as described herein can include one or more UCI portions or regions within xPUSCH. The one or more UCI regions can be positioned or allocated in any manner within the xPUSCH based on temporal and frequency allocation, thereby benefiting from time and/or frequency diversity. The one or more UCI regions can overlap or not overlap in time. In various embodiments, signaling provided by a base station (e.g., the base station 104) can indicate to a receiving mobile device (e.g., the mobile device 102) how many distinct UCI regions are to be positioned within xPUSCH, the resource allocation in terms of frequency and time and payload size (e.g., the frequency ranges, times of occupancy and amounts thereof).

In various embodiments, UCI can be mapped in the xPUSCH in a time first manner. In various embodiments, a portion of the xPUSCH can include UCI mapped into the xPUSCH in a time first manner and the remaining portion of the xPUSCH can include data (e.g., coded UL- SCH data) mapped in a frequency first manner (on the remaining resource of the xPUSCH). With mapping UCI in a time first manner, an additional bit field in the DCI to indicate the resource size for UCI transmission may not be necessary, thereby reducing control signaling overhead.

FIG. 7 illustrates an exemplary self-contained subframe structure 700 with UCI mapped in a time first manner with data within xPUSCH. As shown in FIG. 7, UCI 702 is mapped in a time first manner within xPUSCH 318. The xPUSCH 318 occupies a frequency range (not labeled in FIG. 7 for simplicity) that can be less than the frequency range occupied by the xPDCCH 314 and the GP 316. The UCI 702 can be mapped in a time first manner by having a first portion of the UCI 702 occupy the entire time range of the xPUSCH 318 (i.e., OFDM symbols "2" through "13") within a first range of frequencies 704 and a second portion of the UCI 702 occupy less than the entire time range of the xPUSCH 318 (i.e., OFDM symbols "2" through "6") within a second range of frequencies 706.

Arrows 708 illustrate that UCI 702 within the xPUSCH 318 is filled in a time first manner - by having the UCI 702 cover the entire time range of the xPUSCH 318 for a first frequency portion 704 of the xPUSCH 318 and then having any additional portion of the UCI 702 cover any additional needed time range of the xPUSCH 318 for a second frequency portion 706 of the xPUSCH 318. The exemplary mapping of the UCI 702 as shown in FIG. 7 is not limited to the allocation of UCI as shown. Instead, in various embodiments, the UCI 702 can include one or more distinct frequency regions that occupy all or less than the entire time range of the xPUSCH 318. Further, the separate regions of the UCI 702 can be adjacent to one another or can be separated by data in the xPUSCH 318.

After mapping the UCI 702 into the xPUSCH 318 in a time first manner - by occupying as much of the xPUSCH 318 as needed or allocated - the remaining resource portion of the xPUSCH 318 can be mapped with data in a frequency first manner, as indicated by arrows 710.

In various embodiments, the base station 104 may request that the mobile station 102 provide ACK/NACK feedback for HARQ processes together with CSI and/or BRS-RP report, for example, in a dynamic TDD system. Under such various embodiments, ACK/NACK feedback for HARQ processes may be encoded first and concatenated with CSI and/or BRS-RP report. Subsequently, the concatenated bits may be encoded by further other coding schemes. In turn, the performance for ACK/NACK feedback may be improved.

FIG. 8 illustrates an exemplary coding scheme for UCI transmission 1000. As shown in FIG. 8, ACK/NACK feedback information 802, CSI report information 804, and BRS-RP report information 806 for UCI are provided. The ACK/NACK feedback information 802, the CSI report information 804, and the BRS-RP report information 806 can comprise UCI information to be multiplexed with data in the xPUSCH based on the techniques described herein. The ACK/NACK feedback information 802 can be encoded by block coding 808. The block coding 808 can be based on a block code such as, for example, a Reed-Muller code.

The encoded ACK/NACK feedback information 802 outputted by the block encoding 808 can be concatenated with the CSI report information 804 and the BRS-RP report information 806 by bit collection 810. After concatenation of the ACK/NACK feedback information 802 outputted by the block encoding 808, the CSI report information 804, and the BRS-RP report information 806, a cyclic redundancy check (CRC) 812 may be appended to the concatenated output of the bit collection 810. A CRC having a length of 8 or 16 - for example, as specified in the LTE standard - can be used. After appending the CRC 812, further coding by a tail- biting convolutional coder (TBCC) 814 can be provided. The TBCC coding can be, for example, coding as defined in the LTE specification. The output 816 of the TBCC coding 814 can be considered to be coded UCI information 816. The coded UCI information 816 can be multiplexed with data in the xPUSCH of a self-contained subframe structure as described herein.

FIG. 9 illustrates an example of a logic flow 900 that may be representative of the implementation of one or more of the disclosed techniques for multiplexing UCI and data on a 5G xPUSCH. For example, logic flow 900 may be representative of operations that may be performed in some embodiments by mobile device 102 (e.g., as a UE) in operating environment 100 of FIG. 1 and may be representative of operations for generating the subframe structures or transmission structures depicted in FIGs. 2A, 2B, 3, 4, 5A, 5B, 6A, 6B, 6C, and 7 and may be representative of operations for performing the coding operations 1000 depicted in FIG. 8.

At 902, a mobile device can receive DCI. The DCI can be received on xPDCCH.

At 904, the DCI information can be processed. In particular, an indication within the DCI can be processed. In various embodiments, the indication within the DCI can be decoded. The indication can include one or more fields or information structures. The indication can include various information regarding the coordination and setup for multiplexing UCI and data on xPUSCH. In various embodiments, the indication can indicate one or more of the following: whether multiplexing UCI and data on xPUSCH is allowable or not allowable; a pay load size for the UCI; a resource allocation for the UCI; one or more frequency ranges for the UCI; one or more time periods for the UCI; a manner for multiplexing the UCI and the data (e.g., specification of a multiplexing scheme include FDM and TDM); whether UCI is to be mapped in a time first or a frequency first manner; how to encode the UCI; and what information to include as part of the UCI.

At 906, a resource allocation for the UCI can be determined. The resource allocation for the DCI can be determined based on the processed or decoded indication. The resource allocation for the DCI can include a variety of information including, but not limited to, a payload size for the UCI, one or more frequency ranges for the UCI, and one or more time periods for the UCI.

At 908, a multiplexing scheme for the UCI can be determined. In various embodiments, the multiplexing scheme for the DCI can be determined based on the determined resource allocation for the DCI. In various embodiments, the multiplexing scheme for the DCI can be determined based on the processed indication. The multiplexing scheme for the DCI can including a variety of information including, but not limited to, a manner for multiplexing the UCI and the data (e.g., specification of a multiplexing scheme include FDM and TDM), and whether UCI is to be mapped in a time first or a frequency first manner.

At 910, the UCI data is generated. In various embodiments, the UCI data can be encoded for inclusion in the xPUSCH. The UCI data can be generated and encoded as specified in relation to FIG. 8 discussed above.

At 912, the generated UCI is transmitted on the xPUSCH. The UCI can be multiplexed with data on the xPUSCH. The transmission of the UCI and data on the xPUSCH can be based on the determination made for resource allocation and/or the determination made for multiplexing that are based on the indication provided in the DCI from a remote base station (e.g., the base station 104).

FIG. 10 illustrates an embodiment of a storage medium 1000. Storage media 1000 may comprise any non-transitory computer-readable storage media or machine-readable storage media, such as an optical, magnetic or semiconductor storage media. In various embodiments, storage media 1000 may comprise an article of manufacture. In some embodiments, storage media 1000 may store computer-executable instructions, such as computer-executable instructions to implement logic flow 900 of FIG. 9. Examples of a computer-readable storage medium or machine -readable storage medium may include any tangible media capable of storing electronic data, including volatile memory or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and so forth. Examples of computer-executable instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, visual code, and the like. The embodiments are not limited in this context.

As used herein, the term "circuitry" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry may be

implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, circuitry may include logic, at least partially operable in hardware. Embodiments described herein may be implemented into a system using any suitably configured hardware and/or software.

FIG. 11 illustrates an example of a mobile device 1100 that may be representative of a mobile device such as, for example, a UE that implements one or more of the disclosed techniques in various embodiments. For example, mobile device 1100 may be representative of mobile device 102 according to some embodiments. In some embodiments, the mobile device 1100 may include application circuitry 1102, baseband circuitry 1104, Radio Frequency (RF) circuitry 1106, front-end module (FEM) circuitry 1108 and one or more antennas 1110, coupled together at least as shown.

The application circuitry 1102 may include one or more application processors. For example, the application circuitry 1102 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with and/or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.

The baseband circuitry 1104 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 1104 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 1106 and to generate baseband signals for a transmit signal path of the RF circuitry 1106. Baseband processing circuity 1104 may interface with the application circuitry 1102 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 1106. For example, in some embodiments, the baseband circuitry 1104 may include a second generation (2G) baseband processor 1104a, third generation (3G) baseband processor 1104b, fourth generation (4G) baseband processor 1104c, and/or other baseband processor(s) 1104d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry 1104 (e.g., one or more of baseband processors 1104a-d) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 1106. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments,

modulation/demodulation circuitry of the baseband circuitry 1104 may include Fast-Fourier Transform (FFT), precoding, and/or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 1104 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments. In some embodiments, the baseband circuitry 1104 may include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (EUTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements. A central processing unit (CPU) 1104e of the baseband circuitry 1104 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers. In some embodiments, the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 1104f. The audio DSP(s) 1104f may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 1104 and the application circuitry 1102 may be implemented together such as, for example, on a system on a chip (SOC).

In some embodiments, the baseband circuitry 1104 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 1104 may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 1104 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

RF circuitry 1106 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 1106 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 1106 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 1108 and provide baseband signals to the baseband circuitry 1104. RF circuitry 1106 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 1104 and provide RF output signals to the FEM circuitry 1108 for transmission.

In some embodiments, the RF circuitry 1106 may include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 1106 may include mixer circuitry 1106a, amplifier circuitry 1106b and filter circuitry 1106c. The transmit signal path of the RF circuitry 1106 may include filter circuitry 1106c and mixer circuitry 1106a. RF circuitry 1106 may also include synthesizer circuitry 1106d for synthesizing a frequency for use by the mixer circuitry 1106a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 1106a of the receive signal path may be configured to down- convert RF signals received from the FEM circuitry 1108 based on the synthesized frequency provided by synthesizer circuitry 1106d. The amplifier circuitry 1106b may be configured to amplify the down-converted signals and the filter circuitry 1106c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 1104 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 1106a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 1106a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1106d to generate RF output signals for the FEM circuitry 1108. The baseband signals may be provided by the baseband circuitry 1104 and may be filtered by filter circuitry 1106c. The filter circuitry 1106c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 1106a of the receive signal path and the mixer circuitry 1106a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and/or upconversion respectively. In some embodiments, the mixer circuitry 1106a of the receive signal path and the mixer circuitry 1106a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 1106a of the receive signal path and the mixer circuitry 1106a may be arranged for direct downconversion and/or direct upconversion, respectively. In some embodiments, the mixer circuitry 1106a of the receive signal path and the mixer circuitry 1106a of the transmit signal path may be configured for super-heterodyne operation.

In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 1106 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 1104 may include a digital baseband interface to communicate with the RF circuitry 1106. In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 1106d may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 1106d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

The synthesizer circuitry 1106d may be configured to synthesize an output frequency for use by the mixer circuitry 1106a of the RF circuitry 1106 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 1106d may be a fractional N/N+l synthesizer.

In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 1104 or the applications processor 1102 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 1102.

Synthesizer circuitry 1106d of the RF circuitry 1106 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuitry 1106d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some

embodiments, the RF circuitry 1106 may include an IQ/polar converter. FEM circuitry 1108 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 1110, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1106 for further processing. FEM circuitry 1108 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 1106 for transmission by one or more of the one or more antennas 1110.

In some embodiments, the FEM circuitry 1108 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 1106). The transmit signal path of the FEM circuitry 1108 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 1106), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1110.

In some embodiments, the mobile device 1100 may include additional elements such as, for example, memory/storage, display, camera, sensor, and/or input/output (I/O) interface.

FIG. 12 illustrates an embodiment of a communications device 1200 that may implement one or more of mobile device 102, base station 104, logic flow 900, storage medium 1000, and the mobile device 1100. In various embodiments, device 1200 may comprise a logic circuit 1228. The logic circuit 1228 may include physical circuits to perform operations described for one or more of mobile device 102, base station 104, logic flow 200, logic flow 700, and the mobile device 1100 of FIG. 9 for example. As shown in FIG. 10, device 1200 may include a radio interface 1210, baseband circuitry 1220, and computing platform 1230, although the embodiments are not limited to this configuration.

The device 1200 may implement some or all of the structure and/or operations for one or more of mobile device 102, base station 104, logic flow 200, logic flow 700, storage medium 1200, storage medium 850, the mobile device 1100, and logic circuit 1228 in a single computing entity, such as entirely within a single device. Alternatively, the device 1200 may distribute portions of the structure and/or operations for one or more of mobile device 102, base station 104, logic flow 200, logic flow 700, storage medium 1200, storage medium 850, the mobile device 1100, and logic circuit 1228 across multiple computing entities using a distributed system architecture, such as a client-server architecture, a 3-tier architecture, an N-tier architecture, a tightly-coupled or clustered architecture, a peer-to-peer architecture, a master-slave architecture, a shared database architecture, and other types of distributed systems. The embodiments are not limited in this context. In one embodiment, radio interface 1210 may include a component or combination of components adapted for transmitting and/or receiving single-carrier or multi-carrier modulated signals (e.g., including complementary code keying (CCK), orthogonal frequency division multiplexing (OFDM), and/or single-carrier frequency division multiple access (SC-FDMA) symbols) although the embodiments are not limited to any specific over-the-air interface or modulation scheme. Radio interface 1210 may include, for example, a receiver 1212, a frequency synthesizer 1214, and/or a transmitter 1216. Radio interface 1210 may include bias controls, a crystal oscillator and/or one or more antennas 1218-/. In another embodiment, radio interface 1210 may use external voltage-controlled oscillators (VCOs), surface acoustic wave filters, intermediate frequency (IF) filters and/or RF filters, as desired. Due to the variety of potential RF interface designs an expansive description thereof is omitted.

Baseband circuitry 1220 may communicate with radio interface 1210 to process receive and/or transmit signals and may include, for example, a mixer for down-converting received RF signals, an analog- to-digital converter 1222 for converting analog signals to digital form, a digital-to-analog converter 1224 for converting digital signals to analog form, and a mixer for up-converting signals for transmission. Further, baseband circuitry 1220 may include a baseband or physical layer (PHY) processing circuit 1226 for PHY link layer processing of respective receive/transmit signals. Baseband circuitry 1220 may include, for example, a medium access control (MAC) processing circuit 1227 for MAC/data link layer processing. Baseband circuitry 1220 may include a memory controller 1232 for communicating with MAC processing circuit 1227 and/or a computing platform 1230, for example, via one or more interfaces 1234.

In some embodiments, PHY processing circuit 1226 may include a frame construction and/or detection module, in combination with additional circuitry such as a buffer memory, to construct and/or deconstruct communication frames. Alternatively or in addition, MAC processing circuit 1227 may share processing for certain of these functions or perform these processes independent of PHY processing circuit 1226. In some embodiments, MAC and PHY processing may be integrated into a single circuit.

The computing platform 1230 may provide computing functionality for the device 1200. As shown, the computing platform 1230 may include a processing component 1040. In addition to, or alternatively of, the baseband circuitry 1220, the device 1200 may execute processing operations or logic for one or more of mobile device 102, base station 104, logic flow 200, logic flow 700, storage medium 1200, storage medium 850, the mobile device 1100, and logic circuit 1228 using the processing component 1040. The processing component 1040 (and/or PHY 1226 and/or MAC 1227) may comprise various hardware elements, software elements, or a combination of both. Examples of hardware elements may include devices, logic devices, components, processors, microprocessors, circuits, processor circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, and so forth), integrated circuits, application specific integrated circuits (ASIC), programmable logic devices (PLD), digital signal processors (DSP), field programmable gate array (FPGA), memory units, logic gates, registers, semiconductor device, chips, microchips, chip sets, and so forth. Examples of software elements may include software components, programs, applications, computer programs, application programs, system programs, software development programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (API), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. Determining whether an embodiment is implemented using hardware elements and/or software elements may vary in accordance with any number of factors, such as desired computational rate, power levels, heat tolerances, processing cycle budget, input data rates, output data rates, memory resources, data bus speeds and other design or performance constraints, as desired for a given implementation.

The computing platform 1230 may further include other platform components 1250. Other platform components 1250 include common computing elements, such as one or more processors, multi-core processors, co-processors, memory units, chipsets, controllers, peripherals, interfaces, oscillators, timing devices, video cards, audio cards, multimedia input/output (I/O) components (e.g., digital displays), power supplies, and so forth. Examples of memory units may include without limitation various types of computer readable and machine readable storage media in the form of one or more higher speed memory units, such as read-only memory (ROM), random-access memory (RAM), dynamic RAM (DRAM), Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, polymer memory such as ferroelectric polymer memory, ovonic memory, phase change or ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS) memory, magnetic or optical cards, an array of devices such as Redundant Array of Independent Disks (RAID) drives, solid state memory devices (e.g., USB memory, solid state drives (SSD) and any other type of storage media suitable for storing information.

Device 1200 may be, for example, an ultra-mobile device, a mobile device, a fixed device, a machine-to- machine (M2M) device, a personal digital assistant (PDA), a mobile computing device, a smart phone, a telephone, a digital telephone, a cellular telephone, user equipment, eBook readers, a handset, a one-way pager, a two-way pager, a messaging device, a computer, a personal computer (PC), a desktop computer, a laptop computer, a notebook computer, a netbook computer, a handheld computer, a tablet computer, a server, a server array or server farm, a web server, a network server, an Internet server, a work station, a mini-computer, a main frame computer, a supercomputer, a network appliance, a web appliance, a distributed computing system, multiprocessor systems, processor-based systems, consumer electronics, programmable consumer electronics, game devices, display, television, digital television, set top box, wireless access point, base station, node B, subscriber station, mobile subscriber center, radio network controller, router, hub, gateway, bridge, switch, machine, or combination thereof. Accordingly, functions and/or specific configurations of device 1200 described herein, may be included or omitted in various embodiments of device 1200, as suitably desired.

Embodiments of device 1200 may be implemented using single input single output (SISO) architectures. However, certain implementations may include multiple antennas (e.g., antennas 1218- ) for transmission and/or reception using adaptive antenna techniques for beamforming or spatial division multiple access (SDMA) and/or using MIMO communication techniques.

The components and features of device 1200 may be implemented using any combination of discrete circuitry, application specific integrated circuits (ASICs), logic gates and/or single chip architectures. Further, the features of device 1200 may be implemented using

microcontrollers, programmable logic arrays and/or microprocessors or any combination of the foregoing where suitably appropriate. It is noted that hardware, firmware and/or software elements may be collectively or individually referred to herein as "logic" or "circuit."

It should be appreciated that the exemplary device 1200 shown in the block diagram of FIG. 12 may represent one functionally descriptive example of many potential implementations. Accordingly, division, omission or inclusion of block functions depicted in the accompanying figures does not infer that the hardware components, circuits, software and/or elements for implementing these functions would be necessarily be divided, omitted, or included in embodiments.

FIG. 13 illustrates an embodiment of a broadband wireless access system 1300. As shown in FIG. 13, broadband wireless access system 1300 may be an internet protocol (IP) type network comprising an internet 1310 type network or the like that is capable of supporting mobile wireless access and/or fixed wireless access to internet 1310. In one or more embodiments, broadband wireless access system 1300 may comprise any type of orthogonal frequency division multiple access (OFDMA)-based or single-carrier frequency division multiple access (SC-FDMA)-based wireless network, such as a system compliant with one or more of the 3GPP LTE Specifications and/or IEEE 802.16 Standards, and the scope of the claimed subject matter is not limited in these respects. In the exemplary broadband wireless access system 1300, radio access networks (RANs) 1312 and 1318 are capable of coupling with evolved node Bs or base stations (eNBs) 1314 and 1320, respectively, to provide wireless communication between one or more fixed devices 1316 and internet 1310 and/or between or one or more mobile devices 1322 and Internet 1310. One example of a fixed device 1316 and a mobile device 1322 is device 1200 of FIG. 12, with the fixed device 1316 comprising a stationary version of device 1200 and the mobile device 1322 comprising a mobile version of device 1200. RANs 1312 and 1318 may implement profiles that are capable of defining the mapping of network functions to one or more physical entities on broadband wireless access system 1300. eNBs 1314 and 1320 may comprise radio equipment to provide RF communication with fixed device 1316 and/or mobile device 1322, such as described with reference to device 1200, and may comprise, for example, the PHY and MAC layer equipment in compliance with a 3GPP LTE Specification or an IEEE 802.16 Standard. Base stations or eNBs 1314 and 1320 may further comprise an IP backplane to couple to Internet 1310 via RANs 1312 and 1318, respectively, although the scope of the claimed subject matter is not limited in these respects.

Broadband wireless access system 1300 may further comprise a visited core network (CN) 1324 and/or a home CN 1326, each of which may be capable of providing one or more network functions including but not limited to proxy and/or relay type functions, for example authentication, authorization and accounting (AAA) functions, dynamic host configuration protocol (DHCP) functions, or domain name service controls or the like, domain gateways such as public switched telephone network (PSTN) gateways or voice over internet protocol (VoIP) gateways, and/or internet protocol (IP) type server functions, or the like. However, these are merely example of the types of functions that are capable of being provided by visited CN 1324 and/or home CN 1326, and the scope of the claimed subject matter is not limited in these respects. Visited CN 1324 may be referred to as a visited CN in the case where visited CN 1324 is not part of the regular service provider of fixed device 1316 or mobile device 1322, for example where fixed device 1316 or mobile device 1322 is roaming away from its respective home CN 1326, or where broadband wireless access system 1300 is part of the regular service provider of fixed device 1316 or mobile device 1322 but where broadband wireless access system 1300 may be in another location or state that is not the main or home location of fixed device 1316 or mobile device 1322. The embodiments are not limited in this context.

Fixed device 1316 may be located anywhere within range of one or both of base stations or eNBs 1314 and 1320, such as in or near a home or business to provide home or business customer broadband access to Internet 1310 via base stations or eNBs 1314 and 1320 and RANs 1312 and 1318, respectively, and home CN 1326. It is worthy of note that although fixed device 1316 is generally disposed in a stationary location, it may be moved to different locations as needed. Mobile device 1322 may be utilized at one or more locations if mobile device 1322 is within range of one or both of base stations or eNBs 1314 and 1320, for example. In accordance with one or more embodiments, operation support system (OSS) 1328 may be part of broadband wireless access system 1300 to provide management functions for broadband wireless access system 1300 and to provide interfaces between functional entities of broadband wireless access system 1300. Broadband wireless access system 1300 of FIG. 13 is merely one type of wireless network showing a certain number of the components of broadband wireless access system 1300, and the scope of the claimed subject matter is not limited in these respects.

Various embodiments may be implemented using hardware elements, software elements, or a combination of both. Examples of hardware elements may include processors,

microprocessors, circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, and so forth), integrated circuits, application specific integrated circuits (ASIC), programmable logic devices (PLD), digital signal processors (DSP), field programmable gate array (FPGA), logic gates, registers, semiconductor device, chips, microchips, chip sets, and so forth. Examples of software may include software components, programs, applications, computer programs, application programs, system programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (API), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. Determining whether an embodiment is implemented using hardware elements and/or software elements may vary in accordance with any number of factors, such as desired computational rate, power levels, heat tolerances, processing cycle budget, input data rates, output data rates, memory resources, data bus speeds and other design or performance constraints.

One or more aspects of at least one embodiment may be implemented by representative instructions stored on a machine -readable medium which represents various logic within the processor, which when read by a machine causes the machine to fabricate logic to perform the techniques described herein. Such representations, known as "IP cores" may be stored on a tangible, machine readable medium and supplied to various customers or manufacturing facilities to load into the fabrication machines that actually make the logic or processor. Some embodiments may be implemented, for example, using a machine -readable medium or article which may store an instruction or a set of instructions that, if executed by a machine, may cause the machine to perform a method and/or operations in accordance with the embodiments. Such a machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware and/or software. The machine-readable medium or article may include, for example, any suitable type of memory unit, memory device, memory article, memory medium, storage device, storage article, storage medium and/or storage unit, for example, memory, removable or nonremovable media, erasable or non-erasable media, writeable or re-writeable media, digital or analog media, hard disk, floppy disk, Compact Disk Read Only Memory (CD-ROM), Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), optical disk, magnetic media, magneto-optical media, removable memory cards or disks, various types of Digital Versatile Disk (DVD), a tape, a cassette, or the like. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, encrypted code, and the like, implemented using any suitable high-level, low- level, object-oriented, visual, compiled and/or interpreted programming language.

The following examples pertain to further embodiments:

Example 1 is a user equipment (UE) comprising a memory and logic, at least a portion of the logic implemented in circuitry coupled to the memory, the logic to process an indication contained in received downlink control information (DCI), determine a resource allocation for uplink control information (UCI) for transmission on a physical uplink shared channel (PUSCH) based on the indication, and generate the UCI for transmission on the PUSCH.

Example 2 is an extension of Example 1 or any other example disclosed herein, the logic further comprising reception logic to receive the DCI on a physical downlink control channel (PDCCH).

Example 3 is an extension of Example 1 or any other example disclosed herein, the logic further comprising transmission logic to transmit the UCI on the PUSCH.

Example 4 is an extension of Example 3 or any other example disclosed herein, the transmission logic to transmit the UCI on the PUSCH multiplexed with data.

Example 5 is an extension of Example 3 or any other example disclosed herein, the PUSCH to comprise part of a 5G self-contained time division duplex (TDD) subframe or a frequency division duplex (FDD) subframe.

Example 6 is an extension of Example 1 or any other example disclosed herein, the indication to indicate that transmission of the UCI on the PUSCH is allowable.

Example 7 is an extension of Example 1 or any other example disclosed herein, the indication to indicate a manner of multiplexing the UCI and data on the PUSCH.

Example 8 is an extension of Example 7 or any other example disclosed herein, the manner to comprise time division multiplexing (TDM). Example 9 is an extension of Example 8 or any other example disclosed herein, the resource allocation to comprise one or more symbols of the PUSCH.

Example 10 is an extension of Example 7 or any other example disclosed herein, the manner to comprise frequency division multiplexing (FDM).

Example 11 is an extension of Example 10 or any other example disclosed herein, the resource allocation to comprise one or more distinct frequency ranges.

Example 12 is an extension of Example 10 or any other example disclosed herein, the resource allocation to comprise one or more distinct time periods.

Example 13 is an extension of Example 12 or any other example disclosed herein, the distinct time periods to comprise overlapping time periods.

Example 14 is an extension of Example 12 or any other example disclosed herein, the distinct time periods to comprise non-overlapping time periods.

Example 15 is an extension of Example 10 or any other example disclosed herein, the logic to map the UCI in the PUSCH in a time first manner.

Example 16 is an extension of Example 10 or any other example disclosed herein, the resource allocation to comprise a UCI frequency range adjacent to a frequency range for the data on the PUSCH.

Example 17 is an extension of Example 16 or any other example disclosed herein, the indication to indicate whether the UCI frequency range is above or below the frequency range for the data based on a one bit field.

Example 18 is an extension of Example 1 or any other example disclosed herein, the UCI to comprise hybrid automatic repeat request (HARQ) acknowledgement (ACK)/non- acknowledgement (NACK) feedback concatenated with channel state information (CSI) feedback or beam related feedback, the HARQ ACK/NACK feedback encoded by a block code prior to concatenation.

Example 19 is a UE according to any of Examples 1 to 18 or any other example disclosed herein and at least one radio frequency (RF) transceiver and at least one RF antenna.

Example 20 is a wireless communication method comprising processing an indication contained in received downlink control information (DCI), identifying a resource allocation for uplink control information (UCI) for transmission on a 5G physical uplink shared channel (xPUSCH) based on the indication and generating the UCI for transmission on the xPUSCH.

Example 21 is an extension of Example 20 or any other example disclosed herein, comprising receiving the DCI on a 5G physical downlink control channel (xPDCCH).

Example 22 is an extension of Example 20 or any other example disclosed herein, comprising transmitting the UCI on the xPUSCH. Example 23 is an extension of Example 22 or any other example disclosed herein, comprising transmitting the UCI on the xPUSCH multiplexed with data.

Example 24 is an extension of Example 23 or any other example disclosed herein, comprising transmitting the UCI on the xPUSCH multiplexed with the data as part of a 5G self- contained time division duplex (TDD) subframe or a frequency division duplex (FDD) subframe.

Example 25 is an extension of Example 20 or any other example disclosed herein, the indication indicating that transmission of the UCI on the xPUSCH is allowable.

Example 26 is an extension of Example 20 or any other example disclosed herein, the indication indicating a manner of multiplexing the UCI and data on the xPUSCH.

Example 27 is an extension of Example 26 or any other example disclosed herein, the manner of multiplexing comprising time division multiplexing (TDM).

Example 28 is an extension of Example 27 or any other example disclosed herein, identifying the resource allocation to comprise one or more symbols of the xPUSCH.

Example 29 is an extension of Example 26 or any other example disclosed herein, the manner of multiplexing comprising frequency division multiplexing (FDM).

Example 30 is an extension of Example 29 or any other example disclosed herein, identifying the resource allocation to comprise one or more distinct frequency ranges.

Example 31 is an extension of Example 29 or any other example disclosed herein, identifying the resource allocation to comprise one or more distinct time periods.

Example 32 is an extension of Example 31 or any other example disclosed herein, the distinct time periods to comprise overlapping time periods.

Example 33 is an extension of Example 31 or any other example disclosed herein, the distinct time periods to comprise non-overlapping time periods.

Example 34 is an extension of Example 29 or any other example disclosed herein, comprising mapping the UCI in the xPUSCH in a time first manner.

Example 35 is an extension of Example 29 or any other example disclosed herein, identifying the resource allocation to comprise a UCI frequency range adjacent to a frequency range for the data on the xPUSCH.

Example 36 is an extension of Example 35 or any other example disclosed herein, the indication indicating whether the UCI frequency range is above or below the frequency range for the data based on a one bit field.

Example 37 is an extension of Example 20 or any other example disclosed herein, comprising encoding hybrid automatic repeat request (HARQ) acknowledgement (ACK)/non- acknowledgement (NACK) feedback data using a block code and concatenating the encoded HARQ ACK/NACK feedback data with channel state information (CSI) feedback to form the UCI.

Example 38 is at least one computer-readable storage medium comprising a set of instructions that, in response to being executed on a computing device, cause the computing device to perform a wireless communication method according to any of claims 20 to 38.

Example 39 is a user equipment (UE) comprising means for performing a wireless communication method according to any of claims 20 to 38.

Example 40 is at least one computer-readable storage medium comprising a set of instructions that, in response to being executed on a computing device, cause the computing device to process an indication contained in received downlink control information (DCI), identify a resource allocation for uplink control information (UCI) for transmission on a physical uplink shared channel (PUSCH) based on the indication, and generate the UCI for transmission on the PUSCH.

Example 41 is an extension of Example 40 or any other example disclosed herein, comprising instructions that, in response to being executed on the computing device, cause the computing device to receive the DCI on a physical downlink control channel (PDCCH).

Example 42 is an extension of Example 40 or any other example disclosed herein, comprising instructions that, in response to being executed on the computing device, cause the computing device to transmit the UCI on the PUSCH.

Example 43 is an extension of Example 42 or any other example disclosed herein, comprising instructions that, in response to being executed on the computing device, cause the computing device to transmit the UCI on the PUSCH multiplexed with data.

Example 44 is an extension of Example 43 or any other example disclosed herein, comprising instructions that, in response to being executed on the computing device, cause the computing device to transmit the UCI on the PUSCH multiplexed with the data as part of a 5G self-contained time division duplex (TDD) subframe or a frequency division duplex (FDD) subframe.

Example 45 is an extension of Example 40 or any other example disclosed herein, comprising instructions that, in response to being executed on the computing device, cause the computing device to determine that transmission of the UCI on the PUSCH is allowable based on the indication.

Example 46 is an extension of Example 40 or any other example disclosed herein, comprising instructions that, in response to being executed on the computing device, cause the computing device to determine a manner of multiplexing the UCI and data on the PUSCH based on the indication. Example 47 is an extension of Example 46 or any other example disclosed herein, comprising instructions that, in response to being executed on the computing device, cause the computing device to determine the manner of multiplexing to comprise time division multiplexing (TDM).

Example 48 is an extension of Example 47 or any other example disclosed herein, comprising instructions that, in response to being executed on the computing device, cause the computing device to identify the resource allocation to comprise one or more symbols of the PUSCH.

Example 49 is an extension of Example 46 or any other example disclosed herein, comprising instructions that, in response to being executed on the computing device, cause the computing device to determine the manner of multiplexing to comprise frequency division multiplexing (FDM).

Example 50 is an extension of Example 49 or any other example disclosed herein, comprising instructions that, in response to being executed on the computing device, cause the computing device to identify the resource allocation to comprise one or more distinct frequency ranges.

Example 51 is an extension of Example 49 or any other example disclosed herein, comprising instructions that, in response to being executed on the computing device, cause the computing device to identify the resource allocation to comprise one or more distinct time periods.

Example 52 is an extension of Example 51 or any other example disclosed herein, comprising instructions that, in response to being executed on the computing device, cause the computing device to determine the distinct time periods to comprise overlapping time periods.

Example 53 is an extension of Example 51 or any other example disclosed herein, comprising instructions that, in response to being executed on the computing device, cause the computing device to determine the distinct time periods to comprise non-overlapping time periods.

Example 54 is an extension of Example 49 or any other example disclosed herein, comprising instructions that, in response to being executed on the computing device, cause the computing device to map the UCI in the PUSCH in a time first manner.

Example 55 is an extension of Example 49 or any other example disclosed herein, comprising instructions that, in response to being executed on the computing device, cause the computing device to identify the resource allocation to comprise a UCI frequency range adjacent to a frequency range for the data on the PUSCH. Example 56 is an extension of Example 55 or any other example disclosed herein, comprising instructions that, in response to being executed on the computing device, cause the computing device to determine the UCI frequency range is above or below the frequency range for the data based on a one bit field of the indication.

Example 57 is an extension of Example 40 or any other example disclosed herein, comprising instructions that, in response to being executed on the computing device, cause the computing device to encode hybrid automatic repeat request (HARQ) acknowledgement (ACK)/non-acknowledgement (NACK) feedback data using a block code and concatenating the encoded HARQ ACK/NACK feedback data with channel state information (CSI) feedback to form the UCI.

Example 58 is an apparatus comprising a memory and baseband circuitry coupled to the memory, the baseband circuitry to decode an indication contained in received downlink control information (DCI), determine a resource allocation for uplink control information (UCI) for inclusion on a physical uplink shared channel (PUSCH) based on the indication, and encode the UCI for inclusion on the PUSCH.

Example 59 is an extension of Example 58 or any other example disclosed herein, the baseband circuitry to multiplex the UCI with data for inclusion on the PUSCH.

Example 60 is an extension of Example 58 or any other example disclosed herein, the PUSCH to comprise part of a 5G self-contained subframe.

Example 61 is an extension of Example 58 or any other example, the indication to indicate that inclusion of the UCI on the PUSCH is allowable.

Example 62 is an extension of Example 58 or any other example disclosed herein, the indication to indicate a manner of multiplexing the UCI and data for inclusion on the PUSCH.

Example 63 is an extension of Example 62 or any other example disclosed herein, the manner to comprise time division multiplexing (TDM).

Example 64 is an extension of Example 62 or any other example disclosed herein, the manner to comprise frequency division multiplexing (FDM).

Example 64a is an extension of Example 62 or any other example disclosed herein, the FDM scheme used for multiplexing data on the PUSCH can comprise single-carrier frequency division multiple access (SC-FDMA).

Example 65 is an extension of Example 64 or any other example disclosed herein, the resource allocation to comprise one or more distinct frequency ranges.

Example 66 is an extension of Example 64 or any other example disclosed herein, the resource allocation to comprise one or more distinct time periods. Example 67 is an extension of Example 58 or any other example disclosed herein, the baseband circuitry to map the UCI in a time first manner.

Example 68 is an extension of Example 58 or any other example disclosed herein, the UCI to comprise hybrid automatic repeat request (HARQ) acknowledgement (ACK)/non- acknowledgement (NACK) feedback concatenated with at least one of channel state information (CSI) feedback and beam related information feedback, the HARQ ACK/NACK feedback encoded by a block code prior to concatenation.

Example 69 is an extension of Example 58 or any other example disclosed herein, the apparatus comprising a User Equipment (UE).

Example 70 is an apparatus comprising a memory, radio frequency (RF) circuitry, the RF circuitry to receive downlink control information (DCI) over a physical downlink control channel (PDCCH), and baseband circuitry coupled to the memory and coupled to the RF circuitry, the baseband circuitry to decode an indication contained in the received downlink control information (DCI), determine a resource allocation for uplink control information (UCI) for inclusion on a physical uplink shared channel (PUSCH) based on the indication, and encode the UCI for inclusion on the PUSCH, the RF circuitry to transmit the UCI on the PUSCH.

Example 71 is an extension of Example 70 or any other example disclosed herein, the PUSCH to comprise part of a 5G self-contained subframe.

Example 72 is an extension of Example 70 or any other example disclosed herein, the apparatus comprising a User Equipment (UE).

Numerous specific details have been set forth herein to provide a thorough understanding of the embodiments. It will be understood by those skilled in the art, however, that the embodiments may be practiced without these specific details. In other instances, well-known operations, components, and circuits have not been described in detail so as not to obscure the embodiments. It can be appreciated that the specific structural and functional details disclosed herein may be representative and do not necessarily limit the scope of the embodiments.

Some embodiments may be described using the expression "coupled" and "connected" along with their derivatives. These terms are not intended as synonyms for each other. For example, some embodiments may be described using the terms "connected" and/or "coupled" to indicate that two or more elements are in direct physical or electrical contact with each other. The term "coupled," however, may also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other.

Unless specifically stated otherwise, it may be appreciated that terms such as "processing," "computing," "calculating," "determining," or the like, refer to the action and/or processes of a computer or computing system, or similar electronic computing device, that manipulates and/or transforms data represented as physical quantities (e.g., electronic) within the computing system's registers and/or memories into other data similarly represented as physical quantities within the computing system's memories, registers or other such information storage, transmission or display devices. The embodiments are not limited in this context.

It should be noted that the methods described herein do not have to be executed in the order described, or in any particular order. Moreover, various activities described with respect to the methods identified herein can be executed in serial or parallel fashion.

Although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. It is to be understood that the above description has been made in an illustrative fashion, and not a restrictive one. Combinations of the above

embodiments, and other embodiments not specifically described herein will be apparent to those of skill in the art upon reviewing the above description. Thus, the scope of various embodiments includes any other applications in which the above compositions, structures, and methods are used.

It is emphasized that the Abstract of the Disclosure is provided to comply with 37 C.F.R. § 1.72(b), requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate preferred embodiment. In the appended claims, the terms "including" and "in which" are used as the plain- English equivalents of the respective terms "comprising" and "wherein," respectively.

Moreover, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

CLAIMS What is claimed is:

1. An apparatus, comprising:

a memory; and

baseband circuitry coupled to the memory, the baseband circuitry to:

decode an indication contained in received downlink control information (DCI); determine a resource allocation for uplink control information (UCI) for inclusion on a physical uplink shared channel (PUSCH) based on the indication; and encode the UCI for inclusion on the PUSCH.

2. The apparatus of claim 1, the baseband circuitry to multiplex the UCI with data for inclusion on the PUSCH.

3. The apparatus of claims 1 or 2, the PUSCH to comprise part of a 5G self-contained subframe.

4. The apparatus of claim 1, the indication to indicate that inclusion of the UCI on the PUSCH is allowable.

5. The apparatus of claims 1 or 4, the indication to indicate a manner of multiplexing the UCI and data for inclusion on the PUSCH.

6. The apparatus of claim 5, the manner to comprise time division multiplexing (TDM).

7. The apparatus of claim 5, the manner to comprise frequency division multiplexing (FDM).

8. The apparatus of claim 7, the resource allocation to comprise one or more distinct frequency ranges.

9. The apparatus of claims 7 or 8, the resource allocation to comprise one or more distinct time periods.

10. The apparatus of claim 7, the baseband circuitry to map the UCI in a time first manner.

11. The apparatus of claim 1, the UCI to comprise hybrid automatic repeat request (HARQ) acknowledgement (ACK)/non-acknowledgement (NACK) feedback concatenated with at least one of channel state information (CSI) feedback and beam related information feedback, the HARQ ACK/NACK feedback encoded by a block code prior to concatenation.

12. At least one computer-readable storage medium comprising a set of wireless communication instructions that, in response to being executed on a computing device, cause the computing device to:

process an indication contained in received downlink control information (DCI);

identify a resource allocation for uplink control information (UCI) for transmission on a physical uplink shared channel (PUSCH) based on the indication; and

generate the UCI for transmission on the PUSCH.

13. The at least one computer-readable storage medium of claim 12, comprising wireless communication instructions that, in response to being executed on the computing device, cause the computing device to transmit the UCI on the PUSCH multiplexed with data.

14. The at least one computer-readable storage medium of claim 13, comprising wireless communication instructions that, in response to being executed on the computing device, cause the computing device to transmit the UCI on the PUSCH multiplexed with the data as part of a 5G self-contained subframe.

15. The at least one computer-readable storage medium of claim 12, comprising wireless communication instructions that, in response to being executed on the computing device, cause the computing device to determine that transmission of the UCI on the PUSCH is allowable based on the indication.

16. The at least one computer-readable storage medium of claims 12 or 15, comprising wireless communication instructions that, in response to being executed on the computing device, cause the computing device to determine a manner of multiplexing the UCI and data on the PUSCH based on the indication.

17. The at least one computer-readable storage medium of claim 16, comprising wireless communication instructions that, in response to being executed on the computing device, cause the computing device to determine the manner of multiplexing to comprise time division multiplexing (TDM).

18. The at least one computer-readable storage medium of claim 16, comprising wireless communication instructions that, in response to being executed on the computing device, cause the computing device to determine the manner of multiplexing to comprise frequency division multiplexing (FDM).

19. The at least one computer-readable storage medium of claim 18, comprising wireless communication instructions that, in response to being executed on the computing device, cause the computing device to identify the resource allocation to comprise one or more distinct frequency ranges.

20. The at least one computer-readable storage medium of claims 18 or 19, comprising wireless communication instructions that, in response to being executed on the computing device, cause the computing device to identify the resource allocation to comprise one or more distinct time periods.

21. The at least one computer-readable storage medium of claim 18, comprising wireless communication instructions that, in response to being executed on the computing device, cause the computing device to identify the resource allocation to comprise a UCI frequency range adjacent to a frequency range for the data on the PUSCH.

22. The at least one computer-readable storage medium of claim 21, comprising wireless communication instructions that, in response to being executed on the computing device, cause the computing device to determine the UCI frequency range is above or below the frequency range for the data based on a one bit field of the indication.

23. The at least one computer-readable storage medium of claim 12, comprising wireless communication instructions that, in response to being executed on the computing device, cause the computing device to encode hybrid automatic repeat request (HARQ) acknowledgement (ACK)/non-acknowledgement (NACK) feedback data using a block code and to concatenate the encoded HARQ ACK/NACK feedback data with at least one of channel state information (CSI) feedback and beam related feedback to form the UCI.

24. An apparatus, comprising:

a memory;

radio frequency (RF) circuitry, the RF circuitry to receive downlink control information (DCI) over a physical downlink control channel (PDCCH); and

baseband circuitry coupled to the memory and coupled to the RF circuitry, the baseband circuitry to:

decode an indication contained in the received downlink control information (DCI);

determine a resource allocation for uplink control information (UCI) for inclusion on a physical uplink shared channel (PUSCH) based on the indication; and encode the UCI for inclusion on the PUSCH,

the RF circuitry to transmit the UCI on the PUSCH.

25. The apparatus of claim 25, the PUSCH to comprise part of a 5G self-contained subframe.