HK1262372B - Multiplexing uplink control information and data on physical uplink shared channel - Google Patents

Description

Multiplexing uplink control information and data on the physical uplink shared channel

Related applications

This application claims priority to U.S. Provisional Patent Application No. 62/295,927, filed February 16, 2016, which is hereby incorporated by reference in its entirety.

Technical Field

Embodiments herein generally relate to communications between devices in a broadband wireless communication network.

Background Art

Uplink control information (UCI) typically carries information related to message acknowledgment protocols (e.g., hybrid automatic repeat request (HARQ) retransmission schemes) as well as information about operating conditions at the mobile device. In many instances, the UCI payload can be quite large. For many conventional wireless communication systems, UCI is restricted to being communicated via control channels. Restricting UCI to certain control channels can prevent robust UCI performance. Improved techniques and systems for ensuring improved UCI performance that overcome the shortcomings of these conventional wireless systems, including those for 5G systems, have not yet been developed.

Summary of the Invention

According to a first aspect of the present disclosure, there is provided an apparatus for wireless communication, comprising: a memory; and a baseband circuit coupled to the memory, the baseband circuit being configured to: decode an indication contained in received downlink control information (DCI); determine, based on the indication, resource allocation for uplink control information (UCI) included on a physical uplink shared channel (PUSCH); encode UCI for inclusion on the PUSCH; and multiplex the UCI with data for inclusion on the PUSCH, wherein the UCI is mapped in a time-first manner and the data is mapped in a frequency-first manner.

According to a second aspect of the present disclosure, a wireless communication method is provided, comprising: processing an indication contained in received downlink control information DCI; identifying resource allocation for uplink control information UCI transmitted on a 5G physical uplink shared channel xPUSCH based on the indication; generating UCI for transmission on the xPUSCH; and transmitting UCI multiplexed with data on the xPUSCH, wherein the UCI is mapped in a time-first manner and the data is mapped in a frequency-first manner.

According to a third aspect of the present disclosure, a device for wireless communication is provided, comprising: a memory; a radio frequency (RF) circuit, the RF circuit being configured to: receive downlink control information (DCI) via a physical downlink control channel (PDCCH); and a baseband circuit coupled to the memory and to the RF circuit, the baseband circuit being configured to: decode an indication contained in the received downlink control information (DCI); determine, based on the indication, resource allocation for uplink control information (UCI) included on a physical uplink shared channel (PUSCH); encode the UCI for inclusion on the PUSCH; and multiplex the UCI with data to be included on the PUSCH, wherein the UCI is mapped in a time-first manner and the data is mapped in a frequency-first manner, the RF circuit being configured to: transmit the UCI on the PUSCH.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 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.

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

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

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

5B illustrates a second exemplary self-contained subframe structure based on a frequency-first resource mapping scheme for xPUSCH transmission including FDM-based multiplexing of UCI and data on the xPUSCH.

6A illustrates a first exemplary self-contained subframe structure based on a frequency-first resource mapping scheme for xPUSCH transmission including FDM-based multiplexing of UCI and data with frequency diversity on the xPUSCH.

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

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

FIG7 illustrates an exemplary self-contained subframe structure where UCI is mapped in a time-first manner with data within the xPUSCH.

FIG8 illustrates an exemplary coding scheme for UCI transmission.

FIG9 illustrates an embodiment of a logic flow.

FIG10 shows an embodiment of a storage medium.

FIG11 shows an embodiment of a first device.

FIG12 shows an embodiment of a second device.

FIG13 illustrates an embodiment of a wireless network.

DETAILED DESCRIPTION

Various embodiments may generally relate 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 may be improved. In various embodiments, UCI and data may be multiplexed on the xPUSCH. The UCI and data may be multiplexed using time division multiplexing (TDM) or frequency division multiplexing (FDM). The UCI may be mapped to the xPUSCH in a time-first manner or a frequency-first manner. The downlink control information may provide a mobile device with resource allocations for UCI and a means for multiplexing UCI and data on the xPUSCH. The xPUSCH may 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 include one or more elements. Elements may include any structure arranged to perform certain operations. Depending on the needs of a given set of design parameters or performance constraints, each element may be implemented as hardware, software, or any combination thereof. Although, for example, an embodiment may be described using a limited number of elements in a specific topology, the embodiment may include more or fewer elements in an alternative topology according to the needs of a given implementation. It is noteworthy that any reference to "one embodiment" or "embodiment" means that the specific features, structures, or characteristics described in conjunction with the embodiment are included in at least one embodiment. The phrases "in one embodiment," "in some embodiments," and "in various embodiments" that appear throughout the specification do not necessarily all refer to the same embodiment.

The technology disclosed herein may involve transmitting 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 in accordance with one or more Third Generation Partnership Project (3GPP), 3GPP Long Term Evolution (LTE), and/or 3GPP LTE Advanced (LTE-A) technologies and/or standards including amendments, derivatives, and variants thereof (including 4G and 5G wireless networks). Various embodiments may additionally or alternatively involve transmissions in accordance with 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 and/or standards including amendments, derivatives, and variants thereof.

Examples of wireless mobile broadband technologies and/or standards may also include, but are not limited to, any 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 1xRTT, CDMA2000 EV-DO, CDMA EV-DV, etc.), High Performance Wireless 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 amendments, derivative versions, and variations thereof.

Some embodiments may additionally or alternatively involve wireless communications according to other wireless communication technologies and/or standards. Examples of other wireless communication technologies and/or standards that may be used in various embodiments may include, but are not limited to, other IEEE wireless communication standards (such as IEEE 802.11, IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, IEEE 802.11u, IEEE 802.11ac, IEEE 802.11ad, 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 Service, Wireless Gigabit (WiGig), WiGig Display Extension (WDE), WiGig Bus Extension (WBE), WiGig Serial Extension (WSE) standards, and/or proximity awareness networks (NANs) developed by the WFA. ), Machine Type Communication (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 those developed by the NFC Forum), including amendments, derivatives, and/or variations of any of the foregoing. Embodiments are not limited to these examples.

In addition to transmission over one or more wireless connections, the technology disclosed herein may also involve transmitting content over one or more wired connections via one or more wired communication media. Examples of wired communication media may include leads, cables, metal wires, printed circuit boards (PCBs), backplanes, switch structures, semiconductor materials, twisted pairs, coaxial cables, optical fibers, etc. The embodiments are not limited in this respect.

FIG1 illustrates an exemplary operating environment 100, such as may represent some embodiments of techniques for multiplexing uplink control information and data. As further described herein, these techniques may include multiplexing uplink control information and data on a 5G physical uplink shared channel (PUSCH). Operating environment 100 may include a mobile device 102 and a cellular base station 104. Mobile device 102 may communicate with base station 104 via a wireless communication interface 106. Mobile device 102 may be a smartphone, tablet, laptop, netbook, or other mobile computing device capable of wireless communication with one or more wireless communication networks. As an example, mobile device 102 may be a user equipment (UE). For example, base station 104 may be a cellular base station, such as an evolved Node B (eNB). For example, base station 104 may be a serving cell for UE 102, such as a primary serving cell or a secondary serving cell. Wireless communication interface 106 may be, for example, a wireless interface for any wireless network or standard described herein, including, for example, 4G, LTE, or 5G wireless networks. Mobile device 102 and base station 104 may implement the multiplexing techniques described herein.

5G wireless communication systems are expected to provide a wide range of users with access to information and data sharing anytime, anywhere in a wide range of applications. Furthermore, 5G wireless communication systems are 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 transmission, 5G wireless communication systems may use a self-contained time division duplex (TDD) subframe structure.

Figures 2A and 2B illustrate exemplary self-contained TDD subframe structures. A self-contained TDD subframe can include uplink (UL) and downlink (DL) communications within the same subframe. In some instances, a self-contained TDD subframe can include an acknowledgement (ACK) message and/or a negative acknowledgement (NACK) message. Furthermore, a self-contained TDD subframe can include an ACK/NACK message within the same subframe as received data that can correspond to the ACK/NACK message. The ACK/NACK message can be part of an automatic repeat request (ARQ) retransmission scheme or a hybrid automatic repeat request (HARQ) retransmission scheme.

FIG2A illustrates an exemplary DL self-contained TDD subframe structure 202. The DL self-contained TDD subframe structure 202 may be implemented by the base station 104 and/or the mobile device 102 depicted in FIG1 . The DL self-contained TDD subframe structure 202 may be, for example, a 5G DL self-contained TDD subframe structure. Thus, the channels and communications within the DL self-contained TDD subframe structure 202 may be 5G channels and communications.

As shown in FIG2A , a DL self-contained TDD subframe structure 202 may 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 switching time between DL and UL communications and round-trip propagation delay, a GP 208 may be inserted between the xPDSCH 206 and the xPUCCH 210. The GP 208 may have a duration of, for example, one or two OFDM symbols. The duration of the DL self-contained TDD subframe structure 202 is indicated by 212.

FIG2B illustrates an exemplary UL self-contained TDD subframe structure 214. UL self-contained TDD subframe structure 214 may be implemented by base station 104 and/or mobile device 102 as depicted in FIG1 . UL self-contained TDD subframe structure 214 may be, for example, a 5G DL self-contained TDD subframe structure. Thus, the channels and communications within UL self-contained TDD subframe structure 214 may be 5G channels and communications.

2B , the UL self-contained TDD subframe structure 202 may include an xPDCCH 204, a GP 208, a physical uplink shared channel (xPUSCH) 216, and an xPUCCH 210. To accommodate switching time between DL and UL communications and round-trip propagation delay, the GP 208 may be inserted between the xPDCCH 204 and the xPUSCH 216. The duration of the UL self-contained TDD subframe structure 214 may 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, a channel quality indicator (CQI), a precoding matrix indicator (PMI), and/or a rank indicator (RI). For cmWave and mmWave bands, the UCI may also include beam-related information, such as a beamforming reference signal (BRS) index and/or a BRS received power (BRS-RP) report.

Typically, UCI may require more robust performance than data channels. Furthermore, due to the amount of information a UCI payload may contain about the status of a mobile device (e.g., the mobile device or UE 102 depicted in FIG1 ), the UCI payload may be relatively large. Techniques described herein enable carrying UCI within the xPUSCH 216 to improve link budget by multiplexing UCI with data on the xPUSCH 216, thereby improving performance in systems limited by carrying UCI in the xPUCCH 210.

As shown in FIG2B , the data within the xPUSCH 216 and the xPUCCH 210 are multiplexed in a time division multiplexing (TDM) manner. The xPUCCH 210 may have a duration of, for example, one or more OFDM symbols. In the case where one symbol is allocated for the xPUCCH 210, increasing the number of frequency resources used to transmit the xPUCCH 210 may not improve the link budget as expected. When more frequency resources are allocated for the xPUCCH 210, the link budget may not be improved because the coding rate is reduced at the expense of increased noise power. Therefore, with the same transmit power, the maximum coupling loss (MCL) between the mobile device (e.g., mobile device 102) and the base station (e.g., base station 104) can remain the same - and the link budget for transmitting the xPUCCH 210 is the same.

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

FIG3 illustrates an exemplary self-contained subframe structure 300 based on a frequency-first resource mapping scheme for xPUSCH transmission. As shown in FIG3 , self-contained subframe structure 300 may include xPDCCH 314, GP 316, and xPUSCH 318. The duration of self-contained subframe structure 300 may be indicated by 320. Indicator 302 indicates the self-contained subframe structure 300 relative to increasing frequency. Indicator 304 indicates the self-contained subframe structure 300 relative to increasing time. OFDM symbol index 322 shows the contents of self-contained subframe structure 300 relative to the OFDM symbol number occupied by self-contained subframe structure 300. As shown, xPDCCH 314 occupies OFDM symbol "0," GP 316 occupies OFDM symbol "1," and xPUSCH 318 occupies OFDM symbols "2" through "13."

3, the xPUSCH 318 may occupy a frequency range 306. Below the frequency range 306 occupied by the xPUSCH 318 may be a lower frequency range 308. Above the frequency range 306 occupied by the xPUSCH 318 may be an upper frequency range 310. Frequency ranges 308 and 310 may be frequency ranges not occupied by the xPUSCH 318. Frequency ranges 308 and 310 may be frequency ranges occupied or used by another user. Although not shown in FIG3 for simplicity, the xPUCCH may be allocated in the last OFDM symbol (i.e., OFDM symbol "13"). Arrow 312 shows that data in the xPUSCH 318 is populated in a frequency-first manner, e.g., by occupying the frequency range 306 in a symbol-by-symbol manner (e.g., from relatively lower frequencies to higher frequencies).

According to the techniques described herein, when UCI is scheduled for transmission along with data in xPUSCH 318, UCI resource mapping (e.g., frequency resource mapping) can follow the same principles as resource mapping for data in xPUSCH 318—i.e., in a frequency-first manner. FIG4 illustrates an exemplary self-contained subframe structure 400 based on a frequency-first resource mapping scheme for xPUSCH transmissions including UCI. As shown in FIG4, xPUSCH 318 can occupy OFDM symbols "2" through "13," and UCI 402 can occupy OFDM symbol "2"—i.e., the first OFDM symbol allocated for xPUSCH 318. OFDM symbols "3" through "13" can include data 404. UCI 402 and data 404 within xPUSCH 318 can be mapped in a frequency-first manner, where UCI 402 occupies a single OFDM symbol following GP 208.

FIG4 illustrates an example of a TDM-based multiplexing scheme for transmission of UCI 402 and data 404 within or on the xPUSCH 318. In general, UCI 402 may occupy one or more OFDM symbols within the xPUSCH 318, within any region of the xPUSCH 318, and on any frequency region, with the multiple occupied OFDM symbols being contiguous or non-contiguous. In various embodiments, UCI 402 may span the entire uplink transmission region, excluding the region allocated for the xPUCCH. Doing so may improve the link budget for UCI 402. Furthermore, coded UL-SCH data may be multiplexed with UCI 402 in the xPUSCH 318 using frequency division multiplexing (FDM).

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

UCI 504 may occupy frequency range 512. Frequency range 512 may be a frequency range within frequency range 506. That is, UCI 504 may be allocated to an upper frequency region of the data transmission region allocated for xPUSCH 318. UCI 504 may occupy or be allocated frequency range 512 for the entire duration of xPUSCH 318. As shown in FIG5A , UCI 504 occupies the upper frequency range 512 of xPUSCH 318 to which frequency range 506 is allocated. In this manner, UCI 504 is multiplexed with data in an FDM manner in xPUSCH 318.

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

UCI 516 may occupy frequency range 524. Frequency range 524 may be a frequency range within frequency range 518. That is, UCI 516 may be allocated to a lower frequency region of the data transmission region allocated for xPUSCH 318. UCI 516 may occupy or be allocated frequency range 524 for the entire duration of xPUSCH 318. As shown in FIG5B , UCI 516 occupies the lower frequency range 524 of xPUSCH 318 to which frequency range 518 is allocated. In this manner, UCI 516 is multiplexed with data in an FDM manner in xPUSCH 318.

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

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

In various embodiments, the base station 104 may also provide a third indication indicating the location of the UCI in the xPUSCH. In various embodiments, a bit field provided by the base station 104 may specify where the UCI may be located. For example, a bit value of "0" may indicate that the UCI is to be allocated in the upper frequency range of the xPUSCH (e.g., as shown in FIG5A ), and a bit value of "1" may indicate that the UCI is to be allocated in the lower frequency range of the xPUSCH (e.g., as shown in FIG5B ). In general, the bit field indicating where the UCI is to be located within the xPUSCH may be of any size and may be proportional in size to the number of various possible locations for the UCI within the xPUSCH.

In various embodiments, one or more bit fields of various sizes may be used to provide indications of allowed multiplexing, payload size, and payload positioning from base station 104. In various embodiments, these indications may be provided within an xPDCCH (e.g., xPDCCH 204). In various embodiments, these indications may be provided by downlink control information (DCI).

In various embodiments, the resource allocation (e.g., payload size) for UCI on the xPUSCH can be indicated separately by the DCI format of the uplink grant from the data resource allocation. In various embodiments, a number of physical resource blocks (PRBs) can be allocated for UCI transmission based on the interpretation of the bit field indicating how many are reserved. Table 1 below shows an example method for allocating one, two, four, or eight PRBs for UCI transmission based on two bit fields.

Table 1

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

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

FIG6A illustrates an exemplary self-contained subframe structure 602 based on a frequency-first resource mapping scheme for xPUSCH transmissions including FDM-based multiplexing of UCI and data on the xPUSCH to exploit frequency diversity. As shown in FIG6A , UCI 604 may be contained within an allocated xPUSCH 318. The xPUSCH 318 may occupy a frequency range 606. Below the frequency range 606 occupied by the xPUSCH 318 may be a lower frequency range 608. Above the frequency range 606 occupied by the xPUSCH 318 may be an upper frequency range 610. Frequency ranges 608 and 610 may be frequency ranges not occupied by the xPUSCH 318. Frequency ranges 608 and 610 may be frequency ranges occupied or used by another user.

UCI 604 may occupy two different regions within the xPUSCH 318. Specifically, UCI 604 may include a first UCI portion occupying a first frequency range 612 and a second UCI portion occupying a second frequency range 614. The first UCI frequency range 612 and the second UCI frequency range 614 may be included within the xPUSCH 318 frequency range 606. The first UCI frequency range 612 may be adjacent to data transmitted in the upper frequency region of the xPUSCH 318 in the xPUSCH 318. The second UCI frequency range 614 may be adjacent to data transmitted in the lower frequency region of the xPUSCH 318 in the xPUSCH 318. UCI 604 may occupy or be allocated within 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 with data in the xPUSCH 318 in an FDM manner and can take advantage of frequency diversity by being distributed over different frequency ranges.

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

Similar to FIG6A , UCI 618 may occupy two different regions within the xPUSCH 318. Specifically, UCI 618 may include a first UCI portion that occupies a first frequency range 626 for a first amount of time 630 and a second UCI portion that occupies a second frequency range 626 for a second amount of time 632. As shown in FIG6B , the first amount of time 630 and the second amount of time 632 do not overlap, but are not limited to such. The first UCI frequency range 626 and the second UCI frequency range 628 may be included within the xPUSCH 318 frequency range 620. The first UCI frequency range 626 may be adjacent to data transmitted within the upper frequency region of the xPUSCH 318 on the xPUSCH 318. The second UCI frequency range 628 may be adjacent to data transmitted within the lower frequency region of the xPUSCH 318 on the xPUSCH 318. UCI 618 may occupy or be allocated within frequency ranges 626 and 628 for less than the entire duration of the xPUSCH 318. For the self-contained subframe structure 616, UCI 618 is multiplexed with data in the xPUSCH 318 in an FDM manner and can take advantage of frequency diversity by being distributed over different frequency ranges.

6C illustrates an exemplary self-contained subframe structure 634 based on a frequency-first resource mapping scheme for xPUSCH transmissions including FDM-based multiplexing of UCI and data on the xPUSCH with frequency diversity. As shown in FIG6C , UCI 636 may be contained within the allocated xPUSCH 318. The xPUSCH 318 may occupy a frequency range 638. Below the frequency range 638 occupied by the xPUSCH 318 may be a lower frequency range 640. Above the frequency range 638 occupied by the xPUSCH 318 may be an upper frequency range 642. Frequency ranges 640 and 642 may be frequency ranges not occupied by the xPUSCH 318. Frequency ranges 640 and 642 may be frequency ranges occupied or used by another user.

Similar to FIG6A and FIG6B , UCI 636 may occupy two different regions within the xPUSCH 318. Specifically, UCI 636 may include a first UCI portion that occupies a first frequency range 644 for a first amount of time 650 and a second UCI portion that occupies a second frequency range 646 for a second amount of time 646. As shown in FIG6C , the first amount of time 648 and the second amount of time 650 do not overlap, but are not limited to this. Furthermore, the time allocated for the first UCI portion occupying frequency range 644 may occur after the transmission of the second UCI portion occupying frequency range 646. The first UCI frequency range 644 and the second UCI frequency range 646 may be contained within the xPUSCH 318 frequency range 638.

The first UCI frequency range 644 may be adjacent to data transmitted in the xPUSCH 318 within the upper frequency region of the xPUSCH 318. The second UCI frequency range 646 may be adjacent to data transmitted in the xPUSCH 318 within the lower frequency region of the xPUSCH 318. The UCI 636 may 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 with the data in the xPUSCH 318 in an FDM manner and, by being distributed over different frequency ranges, may exploit the benefits of frequency diversity.

In summary, in various embodiments, a self-contained subframe structure as described herein can include one or more UCI parts or regions within the xPUSCH. One or more UCI regions can be positioned or allocated within the xPUSCH in any manner based on time and frequency allocation, thereby benefiting from time and/or frequency diversity. One or more UCI regions can overlap or not overlap in time. In various embodiments, the signaling provided by the base station (e.g., base station 104) can indicate to the receiving mobile device (e.g., mobile device 102) how many different UCI regions to locate within the xPUSCH, the resource allocation in terms of frequency and time, and the payload size (e.g., the occupied frequency range, time, and amount thereof).

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

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

Arrow 708 illustrates filling the xPUSCH 318 with UCI 702 in a time-first manner (by having UCI 702 cover the entire time range of the xPUSCH 318 within the first frequency portion 704 of the xPUSCH 318, and then having any additional portions of UCI 702 cover any additional required time range of the xPUSCH 318 within the second frequency portion 706 of the xPUSCH 318). As shown in FIG7 , the exemplary mapping of UCI 702 is not limited to the allocation of UCI as shown. Rather, in various embodiments, UCI 702 may include one or more different frequency regions that occupy the entire time range of the xPUSCH 318 or less. Furthermore, separate regions of UCI 702 may be adjacent to each other or may 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 many xPUSCHs 318 as needed or allocated), the remaining resource portion of the xPUSCH 318 may be mapped with data in a frequency-first manner, as indicated by arrow 710 .

In various embodiments, base station 104 may request mobile station 102 to provide ACK/NACK feedback for HARQ processing and CSI and/or BRS-RP reports, for example in a dynamic TDD system. In such various embodiments, the ACK/NACK feedback for HARQ processing may be first encoded and concatenated with the CSI and/or BRS-RP reports. The concatenated bits may then be encoded using another encoding scheme. This may improve the performance of the ACK/NACK feedback.

FIG8 illustrates an exemplary coding scheme for UCI transmission 800. As shown in FIG8 , 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, CSI report information 804, and BRS-RP report information 806 may include UCI information to be multiplexed with data in the xPUSCH based on the techniques described herein. The ACK/NACK feedback information 802 may be encoded using block coding 808. For example, block coding 808 may be based on a block code, such as a Reed-Müller code.

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

FIG9 illustrates an example of a logic flow 900 that may represent an implementation of one or more disclosed techniques for multiplexing UCI and data on a 5G xPUSCH. For example, logic flow 900 may represent operations that may be performed by a mobile device 102 (e.g., as a UE) in the operating environment 100 of FIG1 in some embodiments, and may represent operations for generating the subframe structures or transmission structures depicted in FIG2A, FIG2B, FIG3, FIG4, FIG5A, FIG5B, FIG6A, FIG6B, FIG6C, and FIG7, and may represent operations for performing the encoding operation 800 depicted in FIG8.

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

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

At 906, a resource allocation for the UCI may be determined. The resource allocation for the DCI may be determined based on the processed or decoded indication. The resource allocation for the DCI may include various 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 may be determined. In various embodiments, the multiplexing scheme for the DCI may be determined based on the determined resource allocation for the DCI. In various embodiments, the multiplexing scheme for the DCI may be determined based on the processed indication. The multiplexing scheme for the DCI may include various information, including, but not limited to, a method for multiplexing the UCI and data (e.g., specifications for multiplexing schemes include FDM and TDM) and whether the UCI is mapped in a time-first or frequency-first manner.

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

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

Figure 10 shows an embodiment of a storage medium 1000. Storage medium 1000 may include any non-transient computer-readable storage medium or machine-readable storage medium, such as optical, magnetic or semiconductor storage media. In various embodiments, storage medium 1000 may include manufactured goods. In some embodiments, storage medium 1000 may store computer-executable instructions, such as computer-executable instructions for implementing the logic flow 900 of Figure 9. Examples of computer-readable storage media or machine-readable storage media may include any tangible medium capable of storing electronic data, including volatile memory or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writable or rewritable memory, etc. 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, etc. The embodiments are not limited in this respect.

As used herein, the term "circuit" 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 executes one or more software or firmware programs, a combinational logic circuit that provides the described functionality, and/or other suitable hardware components. In some embodiments, the circuit may be implemented in one or more software or firmware modules, or the functionality associated with the circuit may be implemented by one or more software or firmware modules. In some embodiments, the circuit may include logic that is at least partially operable in hardware. The embodiments described herein may be implemented into a system using suitably configured hardware and/or software.

11 shows an example of a mobile device 1100, which can represent a mobile device, such as, for example, a UE that implements one or more disclosed techniques in various embodiments. For example, according to some embodiments, the mobile device 1100 can represent the mobile device 102. In some embodiments, the mobile device 1100 can 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.

Application circuitry 1102 may include one or more application processors. For example, application circuitry 1102 may include circuitry such as, but not limited to, one or more single-core processors or multi-core processors. The processors may include any combination of general-purpose processors and specialized processors (e.g., graphics processors, application processors, etc.). The processors may be coupled to and/or 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 processors 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 the receive signal path of the RF circuitry 1106 and generate baseband signals for the transmit signal path of the RF circuitry 1106. The baseband circuitry 1104 may interface with the application circuitry 1102 to generate and process baseband signals and control the operation of the RF circuitry 1106. For example, in some embodiments, the baseband circuitry 1104 may include a second-generation (2G) baseband processor 1104a, a third-generation (3G) baseband processor 1104b, a fourth-generation (4G) baseband processor 1104c, and/or other baseband processors 1104d for other existing, developing, or future generations (e.g., fifth-generation (5G), 6G, etc.). The baseband circuitry 1104 (e.g., one or more of the baseband processors 1104a-d) may handle various radio control functions that enable communication with one or more wireless networks via the RF circuitry 1106. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency offset, etc. In some embodiments, the modulation/demodulation circuitry of the baseband circuitry 1104 may include fast Fourier transform (FFT), precoding, and/or constellation mapping/demapping functions. In some embodiments, the 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 functions. Embodiments of the modulation/demodulation and encoder/decoder functions are not limited to these examples and may include other suitable functions in other embodiments.

In some embodiments, the baseband circuitry 1104 may include elements of a protocol stack, such as, for example, elements of the Evolved Universal Terrestrial Radio Access Network (EUTRAN) protocol, including, for example, physical (PHY) elements, media access control (MAC) elements, radio link control (RLC) elements, packet data convergence protocol (PDCP) elements, and/or radio resource control (RRC) elements. The central processing unit (CPU) 1104e of the baseband circuitry 1104 may be configured to execute elements of the protocol stack for signaling at the PHY, MAC, RLC, PDCP, and/or RRC layers. In some embodiments, the baseband circuitry may include one or more audio digital signal processors (DSPs) 1104f. The audio DSPs 1104f may include elements for compression/decompression and echo cancellation, and in other embodiments may include other suitable processing elements. In some embodiments, the components of the baseband circuitry may be appropriately combined in a single chip, a single chipset, or provided on the same circuit board. 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, baseband circuitry 1104 can provide communications compatible with one or more radio technologies. For example, in some embodiments, baseband circuitry 1104 can support communications with the Evolved Universal Terrestrial Radio Access Network (EUTRAN) and/or other wireless metropolitan area networks (WMANs), wireless local area networks (WLANs), and wireless personal area networks (WPANs). Embodiments in which baseband circuitry 1104 is configured to support wireless communications using more than one wireless protocol may be referred to as multi-mode baseband circuitry.

RF circuitry 1106 can enable communication with a wireless network using modulated electromagnetic radiation over a non-solid medium. In various embodiments, RF circuitry 1106 can include switches, filters, amplifiers, and the like to facilitate communication with the wireless network. RF circuitry 1106 can include a receive signal path, which can include circuitry for downconverting RF signals received from FEM circuitry 1108 and providing a baseband signal to baseband circuitry 1104. RF circuitry 1106 can also include a transmit signal path, which can include circuitry for upconverting baseband signals provided by baseband circuitry 1104 and providing an RF output signal to FEM circuitry 1108 for transmission.

In some embodiments, RF circuitry 1106 may include a receive signal path and a transmit signal path. The receive signal path of RF circuitry 1106 may include a mixer circuit 1106a, an amplifier circuit 1106b, and a filter circuit 1106c. The transmit signal path of RF circuitry 1106 may include a filter circuit 1106c and the mixer circuit 1106a. RF circuitry 1106 may also include a synthesizer circuit 1106d for synthesizing frequencies used by mixer circuitry 1106a in the receive and transmit signal paths. In some embodiments, mixer circuitry 1106a in the receive signal path may be configured to downconvert the RF signal received from FEM circuitry 1108 based on the synthesized frequency provided by synthesizer circuitry 1106d. Amplifier circuitry 1106b may be configured to amplify the downconverted signal, and filter circuitry 1106c may be a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove unwanted signals from the downconverted signal to generate an output baseband signal. The output baseband signal can be provided to baseband circuit 1104 for further processing. In some embodiments, the output baseband signal can be a zero-frequency baseband signal, but this is not required. In some embodiments, the mixer circuit 1106a of the receive signal path can include a passive mixer, but the scope of the embodiments is not limited in this regard.

In some embodiments, mixer circuit 1106a of the transmit signal path can be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 1106d to generate an RF output signal for FEM circuit 1108. The baseband signal can be provided by baseband circuit 1104 and can be filtered by filter circuit 1106c. Filter circuit 1106c can include a low-pass filter (LPF), but the scope of the embodiments is not limited in this regard.

In some embodiments, the mixer circuit 1106a of the receive signal path and the mixer circuit 1106a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and/or up-conversion, respectively. In some embodiments, the mixer circuit 1106a of the receive signal path and the mixer circuit 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 circuit 1106a of the receive signal path and the mixer circuit 1106a of the transmit signal path may be arranged for direct down-conversion and/or direct up-conversion, respectively. In some embodiments, the mixer circuit 1106a of the receive signal path and the mixer circuit 1106a of the transmit signal path may be configured for superheterodyne operation.

In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, but the scope of the embodiments is not limited in this regard. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuitry 1106 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and baseband circuitry 1104 may include a digital baseband interface to communicate with RF circuitry 1106.

In some dual-mode embodiments, separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this regard.

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

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

In some embodiments, the frequency input can be provided by a voltage-controlled oscillator (VCO), but this is not required. Depending on the desired output frequency, the divider control input can be provided by baseband circuitry 1104 or application processor 1102. In some embodiments, the divider control input (e.g., N) can be determined from a lookup table based on the channel indicated by application processor 1102.

The synthesizer circuit 1106d of the RF circuit 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-mode 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 N or N+1 (e.g., based on a carry) 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 decompose the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this manner, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuit 1106d can be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency), and used in conjunction with a quadrature generator and divider circuit to generate multiple signals at the carrier frequency with multiple different phases relative to each other. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, RF circuit 1106 can 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 RF circuitry 1106 for further processing. FEM circuitry 1108 may also include a transmit signal path, which may include circuitry configured to amplify transmit signals provided by 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 and receive modes of 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 a received RF signal and provide the amplified received RF signal 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 an input RF signal (e.g., provided by the RF circuitry 1106) and one or more filters to generate an RF signal for subsequent transmission (e.g., by one or more of the one or more antennas 1110).

In some embodiments, mobile device 1100 may include additional elements, such as memory/storage, displays, cameras, sensors, and/or input/output (I/O) interfaces.

FIG12 illustrates an embodiment of a communication device 1200 that may implement one or more of mobile device 102, base station 104, logic flow 900, storage medium 1000, and mobile device 1100. In various embodiments, device 1200 may include logic circuitry 1228. For example, logic circuitry 1228 may include physical circuitry to perform the operations described in FIG9 for one or more of mobile device 102, base station 104, and mobile device 1100. As shown in FIG10 , device 1200 may include a radio interface 1210, baseband circuitry 1220, and a computing platform 1230, although embodiments are not limited to this configuration.

Device 1200 may implement some or all of the structure and/or operations of one or more of mobile device 102, base station 104, storage medium 1000, mobile device 1100, and logic circuitry 1228 in a single computing entity (such as entirely within a single device). Alternatively, device 1200 may distribute portions of the structure and/or operations of one or more of mobile device 102, base station 104, storage medium 1000, mobile device 1100, and logic circuitry 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). Embodiments are not limited in this respect.

In one embodiment, the radio interface 1210 may include a component or combination of components adapted to transmit and/or receive 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 embodiments are not limited to any particular air interface or modulation scheme. The radio interface 1210 may include, for example, a receiver 1212, a frequency synthesizer 1214, and/or a transmitter 1216. The radio interface 1210 may include bias control, a crystal oscillator, and/or one or more antennas 1218-f. In another embodiment, the radio interface 1210 may utilize an external voltage-controlled oscillator (VCO), a surface acoustic wave filter, an intermediate frequency (IF) filter, and/or an RF filter, as needed. Due to the variety of possible RF interface designs, a general description thereof is omitted.

The baseband circuitry 1220 can communicate with the radio interface 1210 to process received and/or transmitted signals and can 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 to be transmitted. Furthermore, the baseband circuitry 1220 can include baseband or physical layer (PHY) processing circuitry 1226 for PHY link layer processing of corresponding received/transmitted signals. The baseband circuitry 1220 can include, for example, medium access control (MAC) processing circuitry 1227 for MAC/data link layer processing. The baseband circuitry 1220 can include a memory controller 1232 for communicating with the MAC processing circuitry 1227 and/or the computing platform 1230, for example, via one or more interfaces 1234.

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

Computing platform 1230 can provide computing functionality for device 1200. As shown, computing platform 1230 can include processing component 1040. In addition to or as an alternative to baseband circuitry 1220, device 1200 can use processing component 1040 to perform processing operations or logic for one or more of mobile device 102, base station 104, storage medium 1000, mobile device 1100, and logic circuitry 1228. Processing component 1040 (and/or PHY 1226 and/or MAC 1227) can include various hardware elements, software elements, or a combination of both. Examples of hardware elements can include devices, logic devices, components, processors, microprocessors, circuits, processor circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, etc.), integrated circuits, application specific integrated circuits (ASICs), programmable logic devices (PLDs), digital signal processors (DSPs), field programmable gate arrays (FPGAs), memory cells, logic gates, registers, semiconductor devices, chips, microchips, chipsets, and the like. 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, processes, software interfaces, application program interfaces (APIs), instruction sets, computing codes, computer codes, code segments, computer code segments, words, values, symbols, or any combination thereof. Determining whether to implement an embodiment using hardware elements and/or software elements may vary depending on any number of factors, such as desired computing rates, power levels, thermal tolerances, processing cycle budgets, input data rates, output data rates, memory resources, data bus speeds, and other design or performance constraints, as desired for a given implementation.

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, coprocessors, 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, etc. Examples of memory cells may include, but are not limited to, various types of computer-readable and machine-readable storage media in the form of one or more higher-speed memory cells, 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, bidirectional memory, phase change or ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS) memory), magnetic or optical cards, device arrays such as redundant array of independent disks (RAID) drives, solid-state memory devices (e.g., USB memory, solid-state drives (SSDs)), and any other type of storage medium suitable for storing information.

Device 1200 can 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 smartphone, a telephone, a digital telephone, a cellular phone, a user device, an e-book reader, a handheld device, 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 workstation, a minicomputer, a mainframe computer, a supercomputer, a network appliance, a web appliance, a distributed computing system, a multiprocessor system, a processor-based system, a consumer electronic product, a programmable consumer electronic product, a gaming device, a display, a television, a digital television, a set-top box, a wireless access point, a base station, a node B, a subscriber station, a mobile subscriber center, a radio network controller, a router, a hub, a gateway, a bridge, a switch, a machine, or a combination thereof. Thus, the functionality and/or specific configurations of device 1200 described herein may be included or omitted in various embodiments of device 1200 as appropriate.

Embodiments of the device 1200 may be implemented using a single-input single-output (SISO) architecture. However, some implementations may include multiple antennas (e.g., antennas 1218-f for transmitting and/or receiving 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 circuits, application specific integrated circuits (ASICs), logic gates, and/or single-chip architectures. Additionally, features of device 1200 may be implemented using microcontrollers, programmable logic arrays, and/or microprocessors, or any combination of the foregoing where appropriate. Note that hardware, firmware, and/or software elements may be collectively or individually referred to herein as "logic" or "circuitry."

It should be understood that the exemplary device 1200 shown in the block diagram of Figure 12 may represent one functional description example of many possible implementations. Therefore, the division, omission, or inclusion of block functions depicted in the figures does not infer that the hardware components, circuits, software, and/or elements used to implement these functions will necessarily be divided, omitted, or included in the embodiments.

FIG13 illustrates an embodiment of a broadband wireless access system 1300. As shown in FIG13 , the broadband wireless access system 1300 may be an Internet Protocol (IP) type network, including an Internet 1310 type network capable of supporting mobile wireless access and/or fixed wireless access to the Internet 1310, and the like. In one or more embodiments, the broadband wireless access system 1300 may include 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 the IEEE 802.16 standards, and the scope of the claimed subject matter is not limited in these respects.

In exemplary broadband wireless access system 1300, radio access networks (RANs) 1312 and 1318 can be coupled with evolved Node Bs or base stations (eNBs) 1314 and 1320, respectively, to provide wireless communications between one or more fixed devices 1316 and the Internet 1310 and/or between one or more mobile devices 1322 and the Internet 1310. An example of fixed device 1316 and mobile device 1322 is device 1200 of FIG. 12 , where fixed device 1316 comprises a fixed version of device 1200 and mobile device 1322 comprises a mobile version of device 1200. RANs 1312 and 1318 can implement profiles that define a mapping of network functions to one or more physical entities on broadband wireless access system 1300. eNBs 1314 and 1320 may include radio equipment to provide RF communications with fixed devices 1316 and/or mobile devices 1322, such as described with reference to device 1200, and may include, for example, PHY and MAC layer equipment compliant with the 3GPP LTE specification or the IEEE 802.16 standard. Base stations or eNBs 1314 and 1320 may also include an IP backplane coupled to the Internet 1310 via RANs 1312 and 1318, respectively, although the scope of the claimed subject matter is not limited in these respects.

The broadband wireless access system 1300 may further include an access core network (CN) 1324 and/or a home CN 1326, each capable of providing one or more network functions, including but not limited to proxy and/or relay-type functions (e.g., authentication, authorization, and accounting (AAA) functions), dynamic host configuration protocol (DHCP) functions or domain name service control, etc., 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, etc. However, these are merely examples of the types of functions that can be provided by the access CN 1324 and/or home CN 1326, and the scope of the claimed subject matter is not limited in these respects. The visiting CN 1324 may be referred to as a visiting CN in situations where the visiting CN 1324 is not part of the regular service provider for the fixed device 1316 or the mobile device 1322, such as when the fixed device 1316 or the mobile device 1322 is roaming away from its corresponding home CN 1326, or where the broadband wireless access system 1300 is part of the regular service provider for the fixed device 1316 or the mobile device 1322, but the broadband wireless access system 1300 may be in another location or state that is not the primary or home location for the fixed device 1316 or the mobile device 1322. Embodiments are not limited in this respect.

Fixed device 1316 can 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 broadband access to the Internet 1310 and home CN 1326 to the home or business customer via base stations or eNBs 1314 and 1320 and RANs 1312 and 1318, respectively. It is worth noting that while fixed device 1316 is typically located at a fixed location, it can be moved to different locations as needed. For example, if mobile device 1322 is within range of one or both of base stations or eNBs 1314 and 1320, then mobile device 1322 can be used at one or more locations. According to one or more embodiments, an operations support system (OSS) 1328 can 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. The broadband wireless access system 1300 of FIG. 13 is merely one type of wireless network illustrating a certain number of components of the broadband wireless access system 1300 , however, the scope of the claimed subject matter is not limited in these respects.

Various embodiments can be implemented using hardware elements, software elements or a combination thereof. The example of hardware elements can include a processor, a microprocessor, a circuit, a circuit element (e.g., a transistor, a resistor, a capacitor, an inductor, etc.), an integrated circuit, an application specific integrated circuit (ASIC), a programmable logic device (PLD), a digital signal processor (DSP), a field programmable gate array (FPGA), a logic gate, a register, a semiconductor device, a chip, a microchip, a chipset, etc. The example of software can include a software component, a program, an application, a computer program, an application program, a system program, a machine program, an operating system software, middleware, firmware, a software module, a routine, a subroutine, a function, a method, a process, a software interface, an application program interface (API), an instruction set, a computing code, a computer code, a code segment, a computer code segment, a word, a value, a symbol or any combination thereof. Determining whether to implement an embodiment using hardware elements and/or software elements can vary according to any number of factors, such as desired computing rate, power level, heat resistance, processing cycle budget, input data rate, output data rate, memory resources, data bus speed and other design or performance constraints.

One or more aspects of at least one embodiment may be implemented via representative instructions stored on a machine-readable medium, which represents various logic within a processor. When read by a machine, the instructions cause the machine to produce logic to perform the techniques described herein. Such representations, known as "IP cores," may be stored on tangible, machine-readable media and provided to various customers or manufacturing facilities to be loaded into manufacturing machines that actually produce the logic or processor. Some embodiments may be implemented, for example, using a machine-readable medium or article that may store an instruction or set of instructions that, if executed by a machine, may cause the machine to perform methods and/or operations according to an embodiment. Such a machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, etc., 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, such as memory, removable or non-removable media, erasable or non-erasable media, writable or rewritable media, digital or analog media, hard disk, floppy disk, compact disk read only memory (CD-ROM), compact disk recordable (CD-R), compact disk rewritable (CD-RW), optical disk, magnetic media, magneto-optical media, removable memory cards or disks, various types of digital versatile disks (DVDs), tapes, cartridges, etc. 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, etc., 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 a circuit coupled to the memory, the logic to: process an indication contained in received downlink control information (DCI); based on the indication, determine a resource allocation for uplink control information (UCI) transmitted on a physical uplink shared channel (PUSCH); and generate UCI for transmission on the PUSCH.

Example 2 is an extension of Example 1 or any other example disclosed herein, wherein the logic further includes receiving logic for receiving DCI on a physical downlink control channel (PDCCH).

Example 3 is an extension of Example 1 or any other example disclosed herein, wherein the logic further includes transmitting logic for transmitting UCI on a PUSCH.

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

Example 5 is an extension of Example 3 or any other example disclosed herein, where the PUSCH includes a portion 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, where the indication is used to indicate that transmission of UCI on the PUSCH is allowed.

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

Example 8 is an extension of Example 7 or any other example disclosed herein, in a manner including time division multiplexing (TDM).

Example 9 is an extension of Example 8 or any other example disclosed herein, wherein the resource allocation includes one or more symbols of PUSCH.

Example 10 is an extension of Example 7 or any other example disclosed herein, in which the approach includes frequency division multiplexing (FDM).

Example 11 is an extension of Example 10 or any other example disclosed herein, wherein the resource allocation includes one or more different frequency ranges.

Example 12 is an extension of Example 10 or any other example disclosed herein, wherein the resource allocation includes one or more different time periods.

Example 13 is an extension of Example 12 or any other example disclosed herein, where the different time periods include overlapping time periods.

Example 14 is an expansion of Example 12 or any other example disclosed herein, where the different time periods include non-overlapping time periods.

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

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

Example 17 is an extension of Example 16 or any other example disclosed herein, wherein the indication is used to indicate whether the UCI frequency range is higher or lower than the frequency range of the data based on a one-bit field.

Example 18 is an extension of Example 1 or any other example disclosed herein, wherein the UCI includes hybrid automatic repeat request (HARQ) acknowledgement (ACK)/negative acknowledgement (NACK) feedback concatenated with channel state information (CSI) feedback or beam-related feedback, and the HARQ ACK/NACK feedback is encoded with a block code before 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); based on the indication, identifying resource allocation for uplink control information (UCI) transmitted on a 5G physical uplink shared channel (xPUSCH); and generating UCI for transmission on the xPUSCH.

Example 21 is an extension of Example 20 or any other example disclosed herein, comprising: receiving 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 UCI on xPUSCH.

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

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

Example 25 is an extension of Example 20 or any other example disclosed herein, where the indication is used to indicate that transmission of UCI on the xPUSCH is allowed.

Example 26 is an extension of Example 20 or any other example disclosed herein, and is used to indicate how to multiplex UCI and data on the xPUSCH.

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

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

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

Example 30 is an extension of Example 29 or any other example disclosed herein, identifying that the resource allocation includes one or more different frequency ranges.

Example 31 is an extension of Example 29 or any other example disclosed herein, identifying that the resource allocation includes one or more different time periods.

Example 32 is an extension of Example 31 or any other example disclosed herein, where the different time periods include overlapping time periods.

Example 33 is an extension of Example 31 or any other example disclosed herein, where the different time periods include non-overlapping time periods.

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

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

Example 36 is an extension of Example 35 or any other example disclosed herein, wherein the indication is used to indicate whether the UCI frequency range is higher or lower than the frequency range of 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)/negative 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 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, causes the computing device to perform a wireless communication method according to any one of Examples 20 to 37.

Example 39 is a user equipment (UE), comprising: a module for performing a wireless communication method according to any one of Examples 20 to 37.

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, causes the computing device to: process an indication contained in received downlink control information (DCI); based on the indication, identify a resource allocation for uplink control information (UCI) transmitted on a physical uplink shared channel (PUSCH); and generate 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 a computing device, cause the computing device to receive 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 a computing device, cause the computing device to transmit UCI on a PUSCH.

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

Example 44 is an extension of Example 43 or any other example disclosed herein, comprising instructions that, in response to being executed on a computing device, cause the computing device to transmit UCI multiplexed with data on a PUSCH as part of a 5G self-contained time division duplex (TDD) subframe or 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 a computing device, cause the computing device to determine that transmission of UCI on the PUSCH is allowed 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 a computing device, cause the computing device to determine a manner to multiplex UCI and data on a 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 a computing device, cause the computing device to determine that the manner of multiplexing includes 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 a computing device, cause the computing device to identify that a resource allocation includes one or more symbols of a PUSCH.

Example 49 is an extension of Example 46 or any other example disclosed herein, comprising instructions that, in response to being executed on a computing device, cause the computing device to determine that the manner of multiplexing includes 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 a computing device, cause the computing device to recognize that a resource allocation includes one or more different 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 a computing device, cause the computing device to recognize that a resource allocation includes one or more different 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 a computing device, cause the computing device to determine that the different time periods include 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 a computing device, cause the computing device to determine that the different time periods include 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 a computing device, cause the computing device to map UCI in a time-first manner in a PUSCH.

Example 55 is an extension of Example 49 or any other example disclosed herein, comprising instructions that, in response to being executed on a computing device, cause the computing device to identify that a resource allocation includes a UCI frequency range adjacent to a frequency range for data on a PUSCH.

Example 56 is an extension of Example 55 or any other example disclosed herein, comprising instructions that, in response to being executed on a computing device, cause the computing device to determine whether the UCI frequency range is above or below the frequency range of the data based on the 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 execution on a computing device, cause the computing device to encode hybrid automatic repeat request (HARQ) acknowledgement (ACK)/negative acknowledgement (NACK) feedback data using a block code and concatenate the encoded HARQ ACK/NACK feedback data with channel state information (CSI) feedback to form UCI.

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

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

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

Example 61 is an extension of Example 58 or any other example, wherein the indication is used to indicate that including UCI on the PUSCH is allowed.

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

Example 63 is an extension of Example 62 or any other example disclosed herein, in a manner including time division multiplexing (TDM).

Example 64 is an extension of Example 62 or any other example disclosed herein, in a manner including frequency division multiplexing (FDM).

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

Example 65 is an extension of Example 64 or any other example disclosed herein, wherein the resource allocation includes one or more different frequency ranges.

Example 66 is an extension of Example 64 or any other example disclosed herein, wherein the resource allocation includes one or more different time periods.

Example 67 is an extension of Example 58 or any other example disclosed herein, wherein the baseband circuit maps the UCI in a time-first manner.

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

Example 69 is an extension of Example 58 or any other example disclosed herein, wherein the apparatus includes a user equipment (UE).

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

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

Example 72 is an extension of Example 70 or any other example disclosed herein, wherein the apparatus includes a user equipment (UE).

Many specific details are set forth herein to provide a thorough understanding of the embodiments. However, those skilled in the art will appreciate that these embodiments may be practiced without these specific details. In other instances, well-known operations, components, and circuits are not described in detail to avoid obscuring the embodiments. It is understood that the specific structural and functional details disclosed herein may be representative and do not necessarily limit the scope of the embodiments.

The expressions "coupled" and "connected" and their derivatives may be used to describe some embodiments. These terms are not intended to be synonyms for each other. For example, the terms "connected" and/or "coupled" may be used to describe some embodiments to indicate that two or more elements are in direct physical or electrical contact with each other. However, the term "coupled" may also mean that two or more elements are not in direct contact with each other, but still cooperate or interact with each other.

Unless otherwise specifically stated, it is understood that terms such as "processing," "computing," "calculating," "determining," etc. refer to the actions and/or processing of a computer or computing system or similar electronic computing device that operates on and/or converts data represented as physical quantities (e.g., electronic) within the registers and/or memories of the computing system into other data similarly represented as physical quantities within the memories, registers, or other such information storage, transmission, or display devices of the computing system. The embodiments are not limited in this respect.

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

Although specific embodiments have been illustrated and described herein, it should be understood that any arrangement calculated to achieve the same purpose may replace the specific embodiments shown. This disclosure is intended to cover any and all modifications or variations of the various embodiments. It should be understood that the above description is provided in an illustrative manner and not restrictive. Combinations of the above embodiments and other embodiments not specifically described herein will be apparent to those skilled in the art after reading the above description. Therefore, the scope of the various embodiments includes any other applications using the above combinations, structures, and methods.

It is emphasized that the Abstract of the Disclosure is provided to comply with the requirement of 37 C.F.R. §1.72(b) that an abstract 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 should not be interpreted as reflecting an intention that the claimed embodiments require more features than expressly recited in each claim. Rather, as reflected in the following claims, the inventive subject matter lies in less than all the features of a single disclosed embodiment. Accordingly, the claims appended hereto are incorporated into the Detailed Description, wherein each claim can stand on its own as a separate preferred embodiment. In the appended claims, the words "including" and "in which" are used as ordinary equivalents of the corresponding 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 should 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 (22)

1. An apparatus for wireless communication, comprising: Memory; and Baseband circuitry, coupled to the memory, the baseband circuitry being used for: Decode the indications contained in the received downlink control information (DCI); Based on the indication, resource allocation for uplink control information (UCI) including on the Physical Uplink Shared Channel (PUSCH) is determined; Encoding the UCI used for inclusion on the PUSCH; and The UCI is multiplexed with data to be included on the PUSCH, wherein the UCI is mapped in a time-priority manner and the data is mapped in a frequency-priority manner. 2. The apparatus of claim 1, wherein the PUSCH comprises a portion of a 5G self-contained subframe. 3. The apparatus of claim 1, wherein the indication is used to indicate that including the UCI on the PUSCH is permitted. 4. The apparatus according to claim 1 or 3, wherein the indication is used to indicate a manner in which the UCI and data are multiplexed to be included on the PUSCH. 5. The apparatus of claim 4, wherein the mode comprises time division multiplexing (TDM). 6. The apparatus of claim 4, wherein the mode comprises frequency division multiplexing (FDM). 7. The apparatus of claim 6, wherein the resource allocation includes one or more different frequency ranges. 8. The apparatus according to claim 6 or 7, wherein the resource allocation includes one or more different time periods. 9. The apparatus of claim 1, wherein the UCI includes a hybrid automatic repeat request (HARQ) ACK/NACK feedback concatenated with at least one of channel state information (CSI) feedback and beam-related information feedback, the HARQ ACK/NACK feedback being encoded by block codes prior to concatenation. 10. A wireless communication method, comprising: Process the indications contained in the received downlink control information (DCI); Based on the indication, resource allocation for uplink control information (UCI) to be transmitted on the 5G physical uplink shared channel xPUSCH is identified. Generate a UCI for transmission on the xPUSCH; and The multiplexed UCI is transmitted on the xPUSCH, wherein the UCI is mapped in a time-priority manner and the data is mapped in a frequency-priority manner. 11. The wireless communication method according to claim 10, comprising: Data-multiplexed UCIs are transmitted on the xPUSCH as part of a 5G self-contained time-division duplex (TDD) subframe or frequency-division duplex (FDD) subframe. 12. The wireless communication method of claim 10, wherein the indication indicates that transmission of the UCI on the xPUSCH is permitted. 13. The wireless communication method of claim 10, wherein the indication indicates the manner in which the UCI and data are multiplexed on the xPUSCH. 14. The wireless communication method according to claim 13, wherein the multiplexing method includes time division multiplexing (TDM). 15. The wireless communication method according to claim 13, wherein the multiplexing method includes frequency division multiplexing (FDM). 16. The wireless communication method of claim 15, wherein the resource allocation is identified to include one or more different frequency ranges. 17. The wireless communication method of claim 15, wherein the resource allocation is identified to include one or more different time periods. 18. The wireless communication method according to claim 17, wherein the different time periods include overlapping time periods. 19. The wireless communication method according to claim 17, wherein the different time periods include non-overlapping time periods. 20. The wireless communication method according to claim 10, comprising: The HARQ ACK/NACK feedback data is encoded using block codes, and the encoded HARQ ACK/NACK feedback data is concatenated with the Channel State Information (CSI) feedback to form the UCI. 21. An apparatus for wireless communication, comprising: Memory; Radio frequency (RF) circuitry, the RF circuitry being used to: receive downlink control information (DCI) via the physical downlink control channel (PDCCH); and A baseband circuit, coupled to the memory and the RF circuit, is used for: Decode the indications contained in the received downlink control information (DCI); Based on the indication, resource allocation for uplink control information (UCI) including on the Physical Uplink Shared Channel (PUSCH) is determined; Encoding the UCI used in the PUSCH; and The UCI is multiplexed with data to be included on the PUSCH, wherein the UCI is mapped in a time-priority manner and the data is mapped in a frequency-priority manner, and the RF circuitry is used to transmit the UCI on the PUSCH. 22. The apparatus of claim 21, wherein the PUSCH comprises a portion of a 5G self-contained subframe.