Techniques for determining resources for transmitting wireless communications

Abstract

Aspects described herein relate to: determining a beta offset for determining a number of shared channel resources to be used for transmitting uplink control information, wherein downlink control information indicating a resource grant for the shared channel resources does not include at least an indication of a selection of a dynamic beta offset. A shared data channel including uplink control information may be generated based at least in part on the beta offset and transmitted on the shared data channel resources.

Description

[0001] Cross - Reference to Related Applications

[0002] This patent application claims priority to the following applications: Provisional Application No. 62 / 891,929, filed on August 26, 2019, entitled "TECHNIQUES FOR DETERMINING RESOURCES FOR TRANSMITTING WIRELESS COMMUNICATIONS"; and U.S. Patent Application No. 16 / 940,127, filed on July 27, 2020, and entitled "TECHNIQUES FOR DETERMINING RESOURCES FOR TRANSMITTING WIRELESS COMMUNICATIONS", all of which are assigned to the assignee of this application and are hereby incorporated by reference in their entirety for all purposes. Field of the Invention

[0003] Broadly speaking, aspects of the present disclosure relate to wireless communication systems, and more particularly, aspects of the present disclosure relate to determining resources on which to transmit control information. Background Art

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

[0005] These multi - access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels. For example, fifth - generation (5G) wireless communication technology (which may be referred to as 5G New Radio (5G NR)) is envisioned to extend and support a diverse range of use cases and applications with respect to current generations of mobile networks. In one aspect, 5G communication technology may include: enhanced mobile broadband that addresses human - centric use cases for accessing multimedia content, services, and data; ultra - reliable low - latency communication (URLLC) with certain specifications for latency and reliability; and massive machine - type communication that can permit a relatively large number of connected devices and the transmission of a relatively low volume of non - latency - sensitive information.

[0006] In some wireless communication technologies, a user equipment (UE) may be configured to transmit control information on multiple data (e.g., non-control) channel resources. The UE may be configured with a beta offset for determining the data channel resources on which to send the control information, and may multiplex the control information with data on the determined data channel resources. Currently, the UE may be configured with either a semi-static beta offset or a set of dynamic beta offsets (one of the dynamic beta offsets in the set of dynamic beta offsets may be specified in a corresponding downlink control information (DCI)), but not both. SUMMARY OF THE INVENTION

[0007] To provide a basic understanding of one or more aspects, a simplified overview of these aspects is given below. This overview is not an exhaustive review of all expected aspects, and is neither intended to identify key or critical elements of all aspects, nor to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that follows.

[0008] According to one example, a method of wireless communication is provided. The method includes: determining a beta offset for determining the number of shared channel resources to be used for transmitting uplink control information, wherein downlink control information indicating a resource grant for the shared channel resources does not include at least an indication of a selection of a dynamic beta offset; generating a shared data channel including the uplink control information at least in part based on the beta offset; and transmitting the shared data channel on the shared data channel resource.

[0009] In another example, a method of wireless communication is provided, the method includes: receiving a configuration of a set of multiple dynamic beta offsets; determining that downlink control information indicating a resource grant for a shared channel resource does not include at least an indication of a selection of one of the multiple dynamic beta offsets; and generating a shared data channel not including uplink control information at least in part based on the determination; and transmitting the shared data channel on the shared data channel resource.

[0010] In another example, a method of wireless communication is provided, the method includes: determining a beta offset for determining the number of shared channel resources to be used for transmitting uplink control information, wherein downlink control information indicating a resource grant for the shared channel resources does not include at least an indication of a selection of a dynamic beta offset; and receiving a shared data channel including the uplink control information at least in part based on the beta offset.

[0011] In another example, a device for wireless communication is provided, the device comprising: a transceiver; a memory configured to store instructions; and one or more processors communicatively coupled to the transceiver and the memory. The one or more processors are configured to execute the instructions to perform the operations of the methods and examples described above and further described herein. In another aspect, a device for wireless communication is provided, the device comprising: means for performing the operations of the methods and examples described above and further described herein. In yet another aspect, a computer-readable medium comprising code is provided, the code being executable by one or more processors to perform the operations of the methods and examples described above and further described herein.

[0012] In one aspect, a device for wireless communication is provided, the device comprising: a transceiver; a memory configured to store instructions; and one or more processors communicatively coupled to the transceiver and the memory. The one or more processors are configured to: determine a beta offset for determining a number of shared channel resources to be used for transmitting uplink control information, wherein downlink control information indicating a resource grant for the shared channel resources does not at least include an indication of a selection of a dynamic beta offset; generate a shared data channel comprising the uplink control information at least in part based on the beta offset; and transmit the shared data channel on the shared data channel resources.

[0013] In another aspect, a device for wireless communication is provided, the device comprising: a transceiver; a memory configured to store instructions; and one or more processors communicatively coupled to the transceiver and the memory. The one or more processors are configured to: determine a beta offset for determining a number of shared channel resources to be used for transmitting uplink control information, wherein downlink control information indicating a resource grant for the shared channel resources does not at least include an indication of a selection of a dynamic beta offset; and receive a shared data channel comprising the uplink control information at least in part based on the beta offset.

[0014] In one aspect, a device for wireless communication. The device comprises: means for determining a beta offset for determining a number of shared channel resources to be used for transmitting uplink control information, wherein downlink control information indicating a resource grant for the shared channel resources does not at least include an indication of a selection of a dynamic beta offset; means for generating a shared data channel comprising the uplink control information at least in part based on the beta offset; and means for transmitting the shared data channel on the shared data channel resources.

[0015] In one aspect, a device for wireless communication is provided. The device includes: a unit for determining a beta offset for determining the number of shared channel resources to be used for transmitting uplink control information, wherein the downlink control information indicating resource authorization for the shared channel resources at least does not include an indication of a selection of a dynamic beta offset; and a unit for receiving a shared data channel including the uplink control information at least partially based on the beta offset.

[0016] In one aspect, a computer-readable medium including code executable by one or more processors for wireless communication is provided. The code includes code for performing the following operations: determining a beta offset for determining the number of shared channel resources to be used for transmitting uplink control information, wherein the downlink control information indicating resource authorization for the shared channel resources at least does not include an indication of a selection of a dynamic beta offset; generating a shared data channel including the uplink control information at least partially based on the beta offset; and transmitting the shared data channel on the shared data channel resources.

[0017] In one aspect, a computer-readable medium including code executable by one or more processors for wireless communication is provided. The code includes code for performing the following operations: determining a beta offset for determining the number of shared channel resources to be used for transmitting uplink control information, wherein the downlink control information indicating resource authorization for the shared channel resources at least does not include an indication of a selection of a dynamic beta offset; and receiving a shared data channel including the uplink control information at least partially based on the beta offset.

[0018] To achieve the foregoing and related purposes, one or more aspects include the features described in detail hereinafter and particularly pointed out in the claims. The following description and the drawings set forth in detail certain illustrative features of one or more aspects. However, these features indicate only some of the various ways in which the principles of the various aspects may be employed, and this description is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Aspects of the disclosure will be described hereinafter with reference to the accompanying drawings, which are provided for illustration and not limitation of the disclosed aspects, where like numerals represent like elements, and in which:

[0020] Figure 1 An example of a wireless communication system in accordance with various aspects of the present disclosure is shown;

[0021] Figure 2is a block diagram illustrating examples of UEs in accordance with various aspects of the present disclosure;

[0022] Figure 3 is a block diagram illustrating examples of base stations in accordance with various aspects of the present disclosure;

[0023] Figure 4 is a flowchart illustrating an example of a method for determining a beta offset for transmitting uplink control information (UCI) on a shared channel resource in accordance with various aspects of the present disclosure;

[0024] Figure 5 is a flowchart illustrating an example of a method for determining a beta offset for receiving UCI on a shared channel resource in accordance with various aspects of the present disclosure;

[0025] Figure 6 illustrates an example of a system for avoiding transmitting UCI on a shared channel resource in accordance with various aspects of the present disclosure; and

[0026] Figure 7 is a block diagram illustrating an example of a MIMO communication system including a base station and a UE in accordance with various aspects of the present disclosure. DETAILED DESCRIPTION

[0027] Aspects are now described with reference to the drawings. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects. It may be evident, however, that such aspects may be practiced without these specific details.

[0028] Generally, the described features relate to determining resources on which to transmit control information in wireless communication. For example, a resource may be determined as a data (e.g., non-control) channel resource on which to transmit control information. In one example, control information transmitted on a data channel resource may be multiplexed with data (e.g., non-control data). In a wireless communication technology such as fifth generation (5G) new radio (NR), a user equipment (UE) may be configured to transmit uplink control information (UCI) on a physical uplink control channel (PUCCH) intended for control information transmission or on a physical uplink shared channel (PUSCH) intended for data (e.g., non-control data), where the control information may be information that facilitates establishing a data channel (e.g., PUSCH) and / or may include other parameters for transmitting data on the data channel. In the case of transmitting UCI on a PUSCH, the UCI may or may not be multiplexed with the data transmitted on the PUSCH resource. In this example, the UE may be configured (e.g., by a base station) with parameters for determining the PUSCH resource on which to transmit the UCI.

[0029] For example, a UE may be configured with a beta offset for determining PUSCH resources, which may be formula-based. In a particular example, for hybrid automatic repeat request (HARQ)-acknowledgment (ACK) transmissions on a PUSCH with an uplink shared channel (UL-SCH), the number of coded modulation symbols per layer for HARQ-ACK transmissions (denoted as Q′ ACK ) may be determined based on a formula similar to the following terms:

[0030]

[0031] where O ACK is the number of HARQ-ACK bits (e.g., UCI), and if O ACK ≥ 360, then L ACK = 11; otherwise, L ACK is the number of CRC bits for HARQ-ACK, (e.g., where this may be the beta offset), C UL-SCH is the number of code blocks of the UL-SCH for PUSCH transmission, and if the downlink control information (DCI) format scheduling the PUSCH transmission includes a code block group transmission information (CBGTI) field indicating that the UE may not transmit the r-th code block, then K r = 0; otherwise, K r is the size of the r-th code block of the UL-SCH for PUSCH transmission, is the scheduled bandwidth of the PUSCH transmission, expressed as the number of subcarriers, is the number of subcarriers in the orthogonal frequency division multiplexing (OFDM) symbol l carrying the phase-tracking reference signal (PTRS) in the PUSCH transmission, is the number of resource elements that can be used to transmit UCI in the OFDM symbol l (for ) in the PUSCH transmission, and is the total number of OFDM symbols of the PUSCH, including all OFDM symbols for the demodulation reference signal (DMRS), and for any OFDM symbol carrying the DMRS of the PUSCH, for any OFDM symbol not carrying the DMRS of the PUSCH, α is configured by scaling with a higher layer parameter, and l 0 is the symbol index of the first OFDM symbol not carrying the DMRS of the PUSCH after the first DMRS symbol in the PUSCH transmission.

[0032] Other formulas can be used and / or specified in wireless communication technology (e.g., at least partially based on beta offset ) to determine the number of coded modulation symbols per layer for UCI in different scenarios (e.g., for whether to multiplex PUSCH data with UCI, for different types of UCI, etc.). In 5G NR, radio resource control (RRC) signaling can be used to configure the UE to have (1) a semi-static beta offset or (2) a set of dynamic beta offsets (one of the dynamic beta offsets in the set can be specified in the corresponding DCI (e.g., where the DCI can include a resource grant for PUSCH resources)), but not both. In the case where the UE is configured to use dynamic beta offsets, the base station may send DCI using a DCI format that does not include a dynamic beta offset selection. For example, when a dynamic beta offset selection is configured in RRC signaling, a fallback DCI format (e.g., DCI format 0_0) can be used, but the base station does not specify a dynamic beta offset selection in the fallback DCI format. In this example, the UE behavior for determining the beta offset is not currently defined.

[0033] Aspects described herein relate to determining UE behavior regarding a beta offset when a dynamic beta offset is configured, but the UE has not received an indication of which dynamic beta offset to select. In one example, a base station may configure the UE with both a semi-static beta offset and a set of dynamic beta offsets, and in the absence of a specified selection of a dynamic beta offset, the UE may use the semi-static beta offset. In another example, in the absence of a specified selection of a dynamic beta offset in DCI, the UE may select one of the dynamic beta offsets from the set of dynamic beta offsets. For example, the UE may select the first or last dynamic beta offset in the configured set. In yet another example, in the absence of a specified selection of a dynamic beta offset, the UE may select one of the dynamic beta offsets from the set of dynamic beta offsets based on information related to the DCI (such as the starting control channel element (CCE) of the physical downlink control channel (PDCCH) carrying the DCI, the number of CCEs in the control resource set (CORESET) in which the PDCCH is received, etc.). In yet another example, in the absence of a specified selection of a dynamic beta offset, the UE may use a default beta offset specified in the specification for the radio communication technology (e.g., as stored in the UE's memory). In additional examples, in the absence of a specified selection of a dynamic beta offset, the UE may avoid transmitting or multiplexing UCI on the PUSCH resource. Additionally, for example, the base station may perform a corresponding determination for the beta offset to receive and process (e.g., demultiplex) UCI from the PUSCH resource. In these examples, the UE may operate accordingly to determine the beta offset when a dynamic beta offset is configured but no selection of the dynamic beta offset is received from the base station.

[0034] The following is referred to Figure 1-7 to present the described features in more detail.

[0035] As used in this application, the terms "component", "module", "system", etc. are intended to include computer-related entities, such as but not limited to hardware, software, combinations of hardware and software, or software in execution. For example, a component can be, but is not limited to, the following: a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and / or a computer. By way of illustration, both an application running on a computing device and the computing device can be components. One or more components can reside within a process and / or thread of execution, and a component can be located on one computer and / or distributed between two or more computers. In addition, these components can execute from various computer-readable media having various data structures stored thereon. A component can communicate in a local and / or remote process manner through signals, such as in accordance with one or more data packets (e.g., data from one component that interacts with another component in a local system, a distributed system, and / or across a network such as the Internet with other systems) in the form of signals. Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, should be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc.

[0036] The techniques described herein can be used in a variety of wireless communication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other systems. The terms "system" and "network" are often used interchangeably. CDMA systems can implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers the IS-2000, IS-95, and IS-856 standards. IS-2000 Releases 0 and A are commonly referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. TDMA systems can implement radio technologies such as the Global System for Mobile Communications (GSM). OFDMA systems can implement radio technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM TMRadio technologies such as. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long-Term Evolution (LTE) and Enhanced LTE (LTE-A) are new versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). The technologies described herein can be used in the systems and radio technologies mentioned above and other systems and radio technologies, including cellular (e.g., LTE) communication on shared radio frequency spectrum bands. However, for illustrative purposes, the following description describes the LTE / LTE-A system, and the LTE terminology is used in most of the following description, but the technologies are applicable to applications other than LTE / LTE-A applications (e.g., applicable to 5th Generation (5G) New Radio (NR) networks or other next-generation communication systems).

[0037] The following description provides examples without limiting the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of the elements discussed without departing from the scope of the present disclosure. Various processes or components may be omitted, replaced, or added as appropriate for each example. For instance, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, features described with respect to some examples may be combined into other examples.

[0038] Aspects or features will be given in terms of a system that may include multiple devices, components, modules, etc. It should be understood and appreciated that various systems may include additional devices, components, modules, etc., and / or may not include all of the devices, components, modules, etc. discussed in conjunction with the figures. Combinations of these methods may also be used.

[0039] Figure 1FIG. is a diagram illustrating an example of a wireless communication system and an access network 100. A wireless communication system (also referred to as a wireless wide area network (WWAN)) may include base stations 102, UEs 104, an evolved packet core (EPC) 160, and / or a 5G core (5GC) 190. The base stations 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). The macro cells may include base stations. The small cells may include femto cells, pico cells, and micro cells. In one example, the base stations 102 may further include gNBs 180, as further described herein. In one example, some nodes of the wireless communication system may have a modem 240 and a communication component 242 for determining a beta offset for transmitting UCI on a shared channel resource. Additionally, some nodes may have a modem 340 and a scheduling component 342 for scheduling and / or indicating a shared channel resource on which to transmit UCI, as described herein. Although the UE 104 is shown as having a modem 240 and a communication component 242, and the base station 102 is shown as having a modem 340 and a scheduling component 342, this is an illustrative example, and substantially any node or any type of node may include a modem 240 and a communication component 242 and / or a modem 340 and a scheduling component 342 for providing the corresponding functionality described herein.

[0040] The base stations 102 configured for 4G LTE (which may be collectively referred to as an evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN)) may interface with the EPC 160 via a backhaul link 132 (e.g., using the S1 interface). The base stations 102 configured for 5G NR (which may be collectively referred to as a next-generation RAN (NG-RAN)) may interface with the 5GC 190 via a backhaul link 184. In addition to other functions, the base stations 102 may also perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), user and device tracking, radio access network information management (RIM), paging, positioning, and transmission of warning messages. The base stations 102 may communicate with each other directly or indirectly (e.g., via the EPC 160 or 5GC 190) via a backhaul link 134 (e.g., using the X2 interface). The backhaul link 134 may be wired or wireless.

[0041] Base station 102 may communicate wirelessly with one or more UEs 104. Each base station 102 among the base stations 102 may provide communication coverage for a corresponding geographical coverage area 110. There may be overlapping geographical coverage areas 110. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network including both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group (which may be referred to as a closed subscriber group (CSG)). The communication link 120 between the base station 102 and the UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from the UE 104 to the base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from the base station 102 to the UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, which includes spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be over one or more carriers. The base station 102 / UE 104 may use a spectrum with a bandwidth of up to a total of Yx MHz (e.g., for x component carriers) allocated in carrier aggregation for transmission in the DL and / or UL directions, with each carrier having a bandwidth of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz). The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to the DL and UL (e.g., more or fewer carriers may be allocated for the DL compared to the UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell), and the secondary component carriers may be referred to as secondary cells (SCells).

[0042] In another example, certain UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. The D2D communication links 158 may use DL / UL WWAN spectrum. The D2D communication links 158 may use one or more sidelink channels, e.g., physical sidelink broadcast channel (PSBCH), physical sidelink discovery channel (PSDCH), physical sidelink shared channel (PSSCH), and physical sidelink control channel (PSCCH). D2D communication may be through a variety of wireless D2D communication systems, e.g., FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0043] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a Clear Channel Assessment (CCA) before communicating to determine if the channel is available.

[0044] The small cell 102’ may operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell 102’ may employ NR and use the same 5 GHz unlicensed spectrum as used by the Wi-Fi AP 150. The small cell 102’ that employs NR in the unlicensed spectrum may enhance coverage and / or increase the capacity of the access network.

[0045] The base station 102 (whether a small cell 102’ or a large cell (e.g., a macro base station)) may include an eNB, a gNodeB (gNB), or other types of base stations. Some base stations (e.g., gNB 180) may operate in the traditional sub-6 GHz spectrum, at millimeter wave (mmW) frequencies, and / or near mmW frequencies to communicate with the UE 104. When the gNB 180 operates at mmW or near mmW frequencies, the gNB 180 may be referred to as a mmW base station. The Extremely High Frequency (EHF) is a part of the RF in the electromagnetic spectrum. The EHF has a range of 30 GHz to 300 GHz and has a wavelength between 1 millimeter and 10 millimeters. The radio waves in this band may be referred to as millimeter waves. Near mmW may extend down to a frequency of 3 GHz, having a wavelength of 100 millimeters. The Super High Frequency (SHF) band extends between 3 GHz and 30 GHz and is also referred to as centimeter waves. Communications using the mmW / near mmW radio frequency bands have extremely high path loss and short distances. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short distances. The base station 102 referred to herein may include the gNB 180.

[0046] The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may communicate with a Home Subscriber Server (HSS) 174. The MME 162 is a control node that processes signaling between the UE 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation and other functions. The PDN Gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functions for MBMS user service provisioning and delivery. The BM-SC 170 may act as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS services to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area for a particular broadcast service, and may be responsible for session management (start / stop) and collecting charging information related to eMBMS.

[0047] The 5GC 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may communicate with a Unified Data Management (UDM) 196. The AMF 192 may be a control node that processes signaling between the UE 104 and the 5GC 190. Generally, the AMF 192 may provide QoS flow and session management. All user Internet Protocol (IP) packets (e.g., from one or more UEs 104) may be transmitted through the UPF 195. The UPF 195 may provide UE IP address allocation for one or more UEs and other functions. The UPF 195 is connected to IP services 197. The IP services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS streaming service, and / or other IP services.

[0048] A base station may also be referred to as a gNB, Node B, evolved Node B (eNB), access point, base station transceiver, radio base station, radio transceiver, transceiver functional unit, basic service set (BSS), extended service set (ESS), transmit receive point (TRP), or some other suitable term. Base station 102 provides an access point for UE 104 to EPC 160 or 5GC 190. Examples of UE 104 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radio units, positioning systems (e.g., satellite, terrestrial), multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, robots, drones, industrial / manufacturing devices, wearable devices (e.g., smart watches, smart clothing, smart glasses, virtual reality glasses, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets)), vehicle / vehicle equipment, meters (e.g., parking meters, electricity meters, gas meters, water meters, flow meters), air pumps, large or small kitchen appliances, medical / healthcare devices, implants, sensors / actuators, displays, or any other device with a similar function. Some of the UEs 104 may be referred to as IoT devices (e.g., meters, pumps, monitors, cameras, industrial / manufacturing devices, appliances, vehicles, robots, drones, etc.). IoT UEs may include MTC / enhanced MTC (eMTC, also known as CAT-M, Cat M1) UEs, NB-IoT (also known as CAT NB1) UEs, and other types of UEs. In the present disclosure, eMTC and NB-IoT may refer to future technologies that may evolve from or be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (further enhanced eMTC), mMTC (massive MTC), etc., while NB-IoT may include eNB-IoT (enhanced NB-IoT), FeNB-IoT (further enhanced NB-IoT), etc. UE 104 may also be referred to as a station, mobile station, user station, mobile unit, user unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile user station, access terminal, mobile terminal, wireless terminal, remote terminal, cell phone, user agent, mobile client, client, or some other suitable term.

[0049] In one example, the communication component 242 can determine a beta offset for determining a shared channel resource (e.g., a PUSCH resource) on which to send (and / or multiplex) UCI. For example, the UE 104 can be configured with a semi-statically configured beta offset and / or a possible set of dynamic beta offsets, which can be further selected or indicated using a DCI (e.g., for an uplink resource grant for a PUSCH or other resource). In this example, the communication component 242 can determine the beta offset, including when the possible set of dynamic beta offsets is configured but the selection of one of the dynamic beta offsets in the set is not indicated (e.g., by the base station 102), as further described herein. In addition, the scheduling component 342 can configure one or more UEs 104 with a beta offset for determining a shared channel resource (e.g., a PUSCH resource) on which to send (and / or multiplex) UCI, and can similarly determine the beta offset, including when the possible set of dynamic beta offsets is configured but the selection of one of the dynamic beta offsets in the set is not indicated (e.g., by the base station 102), as further described herein.

[0050] Now go to Figure 2-7 , various aspects are depicted with reference to one or more components and one or more methods that can perform the actions or operations described herein, where aspects with dashed lines may be optional. Figure 4-6 The operations described in the description are given in a specific order and / or performed by exemplary components, but it should be understood that the order in which the actions and components perform the actions may vary depending on the implementation. In addition, it should be understood that the following actions, functions and / or components described may be performed by a specially programmed processor, a processor executing specially programmed software or computer-readable media, or any other combination of hardware components and / or software components capable of performing the described actions or functions.

[0051] Reference Figure 2 , an example of an implementation of UE 104 may include various components, some of which have been described above and are further described herein, including components such as one or more processors 212 and memory 216 in communication via one or more buses 244 and a transceiver 202, which may operate in conjunction with a modem 240 and / or a communication component 242 for determining a beta offset for transmitting and / or multiplexing UCI on a data channel (e.g., a shared channel) resource, as described herein.

[0052] In one aspect, one or more processors 212 may include a modem 240 that uses one or more modem processors and / or may be part of the modem 240. Accordingly, various functions associated with the communication component 242 may be included in the modem 240 and / or the processor 212, and in one aspect, may be performed by a single processor, while in other aspects, different functions among these functions may be performed by a combination of two or more different processors. For example, in one aspect, one or more processors 212 may include any one or any combination of the following: a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receive processor, or a transceiver processor associated with the transceiver 202. In other aspects, some of the features of one or more processors 212 and / or the modem 240 associated with the communication component 242 may be performed by the transceiver 202.

[0053] In addition, the memory 216 may be configured to store data used herein and / or a local version of an application 275 executed by at least one processor 212 or one or more subcomponents of the communication component 242 and / or its subcomponents. The memory 216 may include any type of computer-readable medium that can be used by a computer or at least one processor 212, such as, for example, random access memory (RAM), read-only memory (ROM), magnetic tape, magnetic disk, optical disk, volatile memory, non-volatile memory, and any combination thereof. In one aspect, for example, the memory 216 may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes, where when the UE 104 is operating at least one processor 212 to execute one or more subcomponents of the communication component 242 and / or its subcomponents, the one or more computer-executable codes are used to define one or more subcomponents of the communication component 242 and / or its subcomponents, and / or data associated therewith.

[0054] The transceiver 202 may include at least one receiver 206 and at least one transmitter 208. The receiver 206 may include hardware for receiving data and / or software executable by a processor, the code including instructions and being stored in a memory (e.g., a computer-readable medium). The receiver 206 may be, for example, a radio frequency (RF) receiver. In one aspect, the receiver 206 may receive signals transmitted by at least one base station 102. Additionally, the receiver 206 may process these received signals and may also obtain measurements of the signals, such as but not limited to Ec / Io, signal-to-noise ratio (SNR), reference signal received power (RSRP), received signal strength indicator (RSSI), etc. The transmitter 208 may include hardware for transmitting data and / or software executable by a processor, the code including instructions and being stored in a memory (e.g., a computer-readable medium). Suitable examples of the transmitter 208 may include but are not limited to RF transmitters.

[0055] Furthermore, in one aspect, the UE 104 may include an RF front end 288, which may operate communicatively with one or more antennas 265 and the transceiver 202 for receiving and transmitting radio transmissions, e.g., wireless communications transmitted by at least one base station 102 or wireless transmissions transmitted by the UE 104. The RF front end 288 may be connected to one or more antennas 265 and may include one or more low-noise amplifiers (LNAs) 290, one or more switches 292, one or more power amplifiers (PAs) 298, and one or more filters 296 for transmitting and receiving RF signals.

[0056] In one aspect, the LNA 290 may amplify the received signal to a desired output level. In one aspect, each LNA 290 may have a specified minimum gain value and a specified maximum gain value. In one aspect, the RF front end 288 may use one or more switches 292 to select a particular LNA 290 and its specified gain value based on the desired gain value for a particular application.

[0057] Additionally, for example, the RF front end 288 may use one or more PAs 298 to amplify the signal for RF output to a desired output power level. In one aspect, each PA 298 may have a specified minimum gain value and a specified maximum gain value. In one aspect, the RF front end 288 may use one or more switches 292 to select a particular PA 298 and its specified gain value based on the desired gain value for a particular application.

[0058] In addition, for example, the RF front end 288 may use one or more filters 296 to filter the received signal to obtain an input RF signal. Similarly, in one aspect, for example, corresponding filters 296 may be used to filter the output from the corresponding PA 298 to generate an output signal for transmission. In one aspect, each filter 296 may be connected to a specific LNA 290 and / or PA 298. In one aspect, the RF front end 288 may use one or more switches 292 to select a transmit path or a receive path that uses the specified filter 296, LNA 290, and / or PA 298 based on a configuration specified by, for example, the transceiver 202 and / or the processor 212.

[0059] Accordingly, the transceiver 202 may be configured to transmit and receive wireless signals via the RF front end 288 and one or more antennas 265. In one aspect, the transceiver may be tuned to operate at a specified frequency such that the UE 104 can communicate with, for example, one or more base stations 102 or one or more cells associated with the one or more base stations 102. In one aspect, for example, the modem 240 may configure the transceiver 202 to operate at a specified frequency and power level based on the UE configuration of the UE 104 and the communication protocol used by the modem 240.

[0060] In one aspect, the modem 240 may be a multi-band multi-mode modem that can process digital signals and communicate with the transceiver 202 such that the transceiver 202 is used to transmit and receive digital data. In one aspect, the modem 240 may be multi-band and may be configured to support multiple bands for a particular communication protocol. In one aspect, the modem 240 may be multi-mode and configured to support multiple operating networks and communication protocols. In one aspect, the modem 240 may control one or more components of the UE 104 (e.g., the RF front end 288, the transceiver 202) based on a specified modem configuration to effect transmission and / or reception of signals from the network. In one aspect, the modem configuration may be based on the mode of the modem and the band in use. In another aspect, the modem configuration may be based on UE configuration information associated with the UE 104 (such as provided by the network during cell selection and / or cell reselection).

[0061] In one aspect, the communication component 242 may optionally include: an offset determination component 252 for determining a beta offset for determining a shared channel resource on which to transmit or multiplex UCI; and / or a resource determination component 254 for determining the shared channel resource based on the beta offset, as described herein.

[0062] In one aspect, the processor 212 may correspond to one or more of the processors described in connection with the UE in Figure 7 . Similarly, the memory 216 may correspond to the memory described in connection with the UE in Figure 7 .

[0063] Referring to Figure 3 , an example implementation of the base station 102 (e.g., the base station 102 and / or gNB 180 as described above) may include various components, some of which have been described above, but including components such as one or more processors 312 and a memory 316 that communicate via one or more buses 344, and a transceiver 302, which may operate in conjunction with a modem 340 and a scheduling component 342 that is used to schedule communications and / or determine a beta offset for receiving and / or processing UCI on data channel (e.g., shared channel) resources, as described herein.

[0064] The transceiver 302, receiver 306, transmitter 308, one or more processors 312, memory 316, application 375, bus 344, RF front end 388, LNA 390, switch 392, filter 396, PA 398, and one or more antennas 365 may be the same as or similar to the corresponding components of the UE 104 as described above, but are configured or otherwise programmed for base station operations as opposed to UE operations.

[0065] In one aspect, the scheduling component 342 may optionally include: an offset determination component 352 that is used to determine a beta offset for determining a shared channel resource on which to receive UCI; and / or a resource determination component 354 that is used to determine a shared channel resource (as described herein) based on the beta offset for receiving and / or processing UCI from the shared channel resource.

[0066] In one aspect, the processor 312 may correspond to one or more of the processors described in connection with the base station in Figure 7 . Similarly, the memory 316 may correspond to the memory described in connection with the base station in Figure 7 .

[0067] Figure 4 A flowchart illustrating an example of a method 400 for determining a beta offset for determining a shared channel resource on which to transmit UCI is shown. Figure 5FIG. 500 is a flowchart illustrating an example of a method 500 for determining a beta offset for a shared channel resource on which to receive or process UCI. For ease of explanation, methods 400 and 500 are described in conjunction with each other, but methods 400 and 500 are not required to be executed in conjunction. In one example, UE 104 may use one or more of the components described in Figure 1 and 2 to perform the functions described in method 400, and / or base station 102 and / or other network components may use one or more of the components described in Figure 1 and 3 to perform the functions described in method 500.

[0068] In method 400, optionally at block 402, a configuration indicating a set of possible dynamic beta offsets may be received. In one aspect, an offset determination component 252 (e.g., in conjunction with a processor 212, a memory 216, a transceiver 202, a communication component 242, etc.) may receive a set of possible dynamic beta offsets. For example, the offset determination component 252 may receive a set of possible dynamic beta offsets in a configuration from a base station (e.g., an RRC configuration). In a specific example for 5G NR, for the case of dynamic beta offsets, the configuration from base station 102 may indicate four possible beta offset values, which may be indicated in a table of values and corresponding indices, an enumeration of values (wherein the index may be implied based on the position of the value in the enumeration), etc.

[0069] In method 400, optionally at block 404, a configuration indicating a semi-statically configured beta offset may be received. In one aspect, an offset determination component 252 (e.g., in conjunction with a processor 212, a memory 216, a transceiver 202, a communication component 242, etc.) may receive a configuration indicating a semi-statically configured beta offset. For example, the offset determination component 252 may receive a semi-statically configured beta offset in a configuration from a base station (e.g., an RRC configuration, which may be the same or a different RRC configuration from which the set of possible dynamic beta offsets was received). Currently, in 5G NR, the beta offset may be configured as a choice between a set of possible dynamic beta offsets or a semi-statically configured beta offset, but not both. As further described herein, for some DCI formats, and in the case where a dynamic beta offset is configured, bits in the DCI (e.g., two bits for four possible beta offset values) may be used to dynamically select one beta offset from the set of possible beta offsets received in the configuration.

[0070] In method 400, optionally at block 406, a DCI indicating a resource grant for transmitting uplink communication may be received. In one aspect, communication component 242 (e.g., in combination with processor 212, memory 216, transceiver 202, etc.) may receive a DCI indicating a resource grant for transmitting uplink communication. For example, communication component 242 may receive the DCI in a downlink control channel (e.g., PDCCH), which may indicate the resources (e.g., time and / or frequency resources) on which the UE may transmit communication to base station 102. Thus, for example, the resource grant may indicate the shared channel resources on which UE 104 may transmit uplink communication, such as PUSCH resources. For example, the DCI may have a certain format (such as DCI format 0_0, DCI format 0_1, etc.), which may or may not have a bit for indicating one of the possible beta offsets in a set of possible beta offsets when dynamic beta offset is configured. In one example, the DCI may include a resource grant specifying the resources, or may include an activation of resources previously indicated in a type 2 configuration grant received from the base station.

[0071] In method 500, optionally at block 502, a configuration indicating a set of possible dynamic beta offsets may be sent. In one aspect, scheduling component 342 (e.g., in combination with processor 312, memory 316, transceiver 302, etc.) may send a set of possible dynamic beta offsets. For example, scheduling component 342 may send a set of possible dynamic beta offsets to the UE in a configuration (e.g., RRC configuration), which may include an indication of the four possible beta offset values described. In other examples, another number of possible beta offset values may be configured similarly.

[0072] In method 500, optionally at block 504, a configuration indicating a semi-statically configured beta offset may be sent. In one aspect, a scheduling component 342 (e.g., in combination with a processor 312, a memory 316, a transceiver 302, etc.) may send a configuration indicating a semi-statically configured beta offset. For example, the scheduling component 342 may send the semi-statically configured beta offset to the UE in a configuration (e.g., an RRC configuration, which may be the same or a different RRC configuration from which a set of possible dynamic beta offsets is sent). As described, in 5G NR, a shared channel resource (e.g., PUSCH) may be dynamically scheduled by another DCI format that does not include a beta offset field (e.g., does not include a selection of one of the possible dynamic beta offsets in a set). For example, DCI format 0_0, which is a fallback DCI format, may not have a beta offset field. Aspects further described herein relate to determining a beta offset or avoiding sending UCI in this scenario and / or similar scenarios where a beta offset is not determined or cannot be determined. Additionally, UE 104 and base station 102 may similarly determine the beta offset to use in order to determine how (e.g., by UE 104) to send and / or (by base station 102) receive / process UCI on a shared channel resource (e.g., multiplexed with non-control data and / or otherwise).

[0073] In method 500, optionally at block 506, a DCI indicating a resource grant for sending uplink communication may be sent. In one aspect, a scheduling component 342 (e.g., in combination with a processor 312, a memory 316, a transceiver 302, etc.) may send a DCI indicating a resource grant for sending uplink communication. For example, the scheduling component 342 may send the DCI in a downlink control channel (e.g., PDCCH), which may indicate the resources (e.g., time and / or frequency resources) on which the UE may send communication to the base station 102 (e.g., a shared channel resource, such as a PUSCH resource). For example, the DCI may have a certain format (such as DCI format 0_0, DCI format 0_1, etc.), which may or may not have a bit for indicating one of the possible beta offsets in a set of possible beta offsets in the case where a dynamic beta offset is configured. In one example, the DCI may include a resource grant specifying the resources, or may include an activation of resources previously indicated in a type 2 configured grant sent by the base station.

[0074] In method 400, at block 408, in the case where the DCI does not indicate a dynamic beta offset, a beta offset can be determined for determining the number of shared channel resources to be used for transmitting the UCI. In one aspect, the offset determination component 252 (e.g., in combination with the processor 212, the memory 216, the transceiver 202, the communication component 242, etc.) can determine, in the case where the DCI does not indicate a dynamic beta offset, a beta offset for determining the number of shared channel resources to be used for transmitting the UCI. For example, the offset determination component 252 can determine a beta offset for transmitting HARQ feedback, channel state information (CSI) (e.g., periodic CSI (P-CSI) report, semi-persistent channel state information (SP-CSI) report, or other CSI reports), etc. For example, as described, the UE 104 can be configured with possible dynamic beta offsets, but may receive a DCI that does not indicate which dynamic beta offset to use (e.g., DCI format 0_0, or other DCI formats or information that do not include a bit or other indicator specifying which of the multiple configured dynamic beta offsets to use when transmitting the UCI).

[0075] When determining the beta offset at block 408, optionally at block 410, it can be determined that the DCI does not include an indication of the selection of a dynamic beta offset. For example, the offset determination component 252 (e.g., in combination with the processor 212, the memory 216, the transceiver 202, the communication component 242, etc.) can determine that the DCI does not include an indication of the selection of a dynamic beta offset. In one example, the offset determination component 252 can determine this based on the DCI format of the received DCI. For example, as described, the communication component 242 can receive DCI from the base station 102 on a downlink control channel (e.g., PDCCH), which can be for the purpose of scheduling resources for the UE 104 to use when transmitting the UCI. In one example, the DCI can indicate a resource grant for an uplink resource (e.g., for a shared channel resource such as a PUSCH resource). For example, the offset determination component 252 can determine that the DCI does not include a selection of a beta offset based on the DCI format. In a specific example, the offset determination component 252 can determine that the DCI has a DCI format 0_0, which may not have the ability to indicate a portion of the beta offset bit or may otherwise not indicate a portion of the beta offset bit. Additionally, in one example, the offset determination component 252 can determine that the DCI does not include a selection of a beta offset based on first determining that the base station 102 is configured with a set of possible dynamic beta offsets (e.g., based on receiving a configuration at block 402).

[0076] In one example, in a case where the offset determination component 252 determines that the DCI does not include an indication regarding the selection of a dynamic beta offset, the offset determination component 252 may determine to use a semi-statically configured beta offset. In this example, the base station 102 is capable of configuring both the semi-statically configured beta offset and a set of possible dynamic beta offsets. Thus, in this example, the UE 104 may receive a configuration indicating the set of possible dynamic beta offsets and the semi-statically configured beta offset (e.g., at blocks 402 and 404), and the base station 102 may send both (e.g., at blocks 502 and 504), whether in separate configurations or in the same configuration (e.g., in one or more RRC messages).

[0077] In a particular example, the base station may configure both a semi-static beta offset and a dynamic beta offset. In this case, if the PUSCH is scheduled by DCI format 0_0, the UE may use the semi-statically configured beta offset. If the PUSCH is configured with DCI format 0_1 and the DCI format 0_1 includes a beta offset field, the UE may use the dynamically signaled beta offset, which is dynamically selected (e.g., via DCI) from the set of possible dynamic offsets received from the base station (e.g., as described in blocks 402 and 502).

[0078] In another example, when determining the beta offset at block 408, optionally at block 412, one dynamic beta offset from the set of possible dynamic beta offsets may be selected. For example, the offset determination component 252 (e.g., in combination with the processor 212, the memory 216, the transceiver 202, the communication component 242, etc.) may select one dynamic beta offset from the set of possible dynamic beta offsets. For example, the offset determination component 252 may be configured to: in a case where it determines that the DCI does not indicate a dynamic beta offset (e.g., and in a case where it determines that a dynamic beta offset has been configured), select a particular dynamic beta offset from the set of possible dynamic beta offsets. In this example, the offset determination component 252 may select a particular dynamic beta offset for sending HARQ feedback, CSI, or other UCI.

[0079] For example, the offset determination component 252 can determine the first dynamic beta offset in the dynamic beta offset set, the last dynamic beta offset in the set, the dynamic beta offset at the calculated position in the set, the dynamic beta offset with the minimum value in the set, the dynamic beta offset with the maximum value in the set, the mean or median average of the values of the dynamic beta offsets in the set, etc. For example, if the UE is configured with a dynamic beta offset indication and the PUSCH is scheduled by DCI format 0_0 (which does not include a beta offset field), the UE can use the first (or last) of the four configured beta offset values. For example, as described, a possible set of dynamic beta offsets can include a set of four offsets, which can be indicated by a 2-bit beta offset indication value (which can be the value indicated in the DCI to select one of the possible dynamic beta offsets), as follows:

[0080] beta offset index beta offset 00 <![CDATA[β 0 > 01 <![CDATA[β 1 > 10 <![CDATA[β 2 > 11 <![CDATA[β 3 >

[0081] For example, in the case where the selected dynamic beta offset is not indicated in the DCI, selecting a beta offset can include: selecting a beta offset corresponding to the beta offset index β 0 (e.g., the first beta offset), a beta offset corresponding to β 3 (e.g., the last beta offset), etc.

[0082] In another example, when selecting one dynamic beta offset from the possible set of dynamic beta offsets at block 412, optionally at block 414, the index can be inferred based on the starting CCE or number of CCEs for the downlink control channel. For example, the offset determination component 252 (e.g., in combination with the processor 212, the memory 216, the transceiver 202, the communication component 242, etc.) can infer the index (e.g., the beta offset index for the possible set of dynamic beta offsets, examples of which are shown and described above) based on the starting CCE, the number of CCEs, or other parameters for the downlink control channel. For example, the downlink control channel can be the channel on which the DCI is received (e.g., as described above, the PDCCH on which the DCI is received). Thus, for example, the beta offset to be used can be implicitly signaled via DCI format 0_0, where the UE can infer the beta offset value (e.g., among the 4 configured values) based on some parameters associated with the received DCI (e.g., the starting CCE of the PDCCH carrying DCI format 0_0). In a particular example, the beta offset can be determined as: where d betaOffsetIt can be a beta offset index as described above (which can be used to select a beta offset from a set of possible dynamic beta offsets), n CCE is the index of the first CCE for PDCCH reception, and N CCE represents the number of CCEs in the CORESET for PDCCH reception.

[0083] When determining the beta offset at block 408, optionally at block 416, a default beta offset hard-coded in the memory can be determined. For example, the offset determination component 252 (e.g., in combination with the processor 212, memory 216, transceiver 202, communication component 242, etc.) can determine a default beta offset hard-coded in the memory (e.g., memory 216) (e.g., to be used when no beta offset can be determined). For example, the default value can be indicated as in the specification for wireless communication technology, and thus, the default value can be encoded in the UE 104, stored in the configuration in the memory 216 of the UE 104, and so on. For example, the UE can use the default value β as the beta offset, which can be written / hard-coded in the specification. In this example, all base stations and / or UEs can use the same beta offset to transmit UCI in the shared channel resource. In one example, the default value can be used before the UE establishes an RRC connection with the base station.

[0084] In method 400, at block 418, a shared data channel including UCI can be generated at least partially based on the beta offset. For example, the resource determination component 254 (e.g., in combination with the processor 212, memory 216, transceiver 202, communication component 242, etc.) can generate a shared data channel (e.g., PUSCH) including UCI at least partially based on the beta offset. For example, the resource determination component 254 can determine at least partially based on the beta offset the resources (e.g., time and / or frequency resources) on which the UCI is to be sent in the shared data channel. As described, this can include calculating the number of coded modulation symbols (e.g., per layer, per UCI transmission (such as in one example, HARQ-ACK)), which can include determining the start symbol and / or the duration of the symbol, the number of resource blocks, which can include determining at least partially based on the beta offset the start resource block and / or the span of the resource blocks, etc. Additionally, when generating a shared data channel with UCI, the resource determination component 254 can multiplex the UCI with data (e.g., non-control) communication (where the determined resources overlap with the data), or can not multiplex the UCI with the data.

[0085] In method 400, at block 420, a shared data channel may be transmitted on shared data channel resources. For example, communication component 242 (e.g., in combination with processor 212, memory 216, transceiver 202, etc.) may transmit a shared data channel on shared data channel resources, where the shared data channel may include UCI multiplexed with data (e.g., non-control) communications, non-multiplexed UCI, etc.

[0086] Additionally, method 500 may include blocks 408, 410, 412, 414, 416, or similar blocks, where offset determination component 352 (e.g., in combination with processor 312, memory 316, transceiver 302, scheduling component 342, etc.) (e.g., in a base station) may determine a beta offset in the case where a beta offset is not indicated in DCI, based on determining that the DCI does not include an indication regarding a selection of a dynamic beta offset, based on using a semi-statically configured beta offset, based on selecting one dynamic beta offset from a set of possible dynamic beta offsets (e.g., the first, the last, etc., one selected based on an inferred index, etc.), based on determining a default beta offset hard-coded in memory, etc.

[0087] In method 500, at block 518, a shared data channel including UCI may be received and / or processed at least in part based on the beta offset. For example, resource determination component 352 (e.g., in combination with processor 312, memory 316, transceiver 302, scheduling component 342, etc.) may receive and / or process a shared data channel including UCI at least in part based on the beta offset. Thus, for example, resource determination component 352 may use the determined beta offset to locate the UCI in shared channel communications, which may include determining the resources (e.g., time and / or frequency resources) on which the UCI is multiplexed with data (e.g., non-control) communications, the resources on which the UCI is transmitted and not multiplexed, etc. In this regard, as described, at least in the case where a dynamic beta offset is configured but not specified (e.g., in DCI, via DCI format, etc.), UE 104 may use the determined beta offset (similarly determined by the base station) to transmit UCI in PUSCH.

[0088] Figure 6 A flowchart of an example of method 600 for avoiding transmitting UCI in the case where a beta offset is not determined is shown. In one example, UE 104 may use one or more of the components described in Figure 1 and 2 to perform the functions described in method 600.

[0089] In method 600, at block 602, a configuration of a set of multiple dynamic beta offsets may be received. In one aspect, an offset determination component 252 (e.g., in combination with processor 212, memory 216, transceiver 202, communication component 242, etc.) may receive a configuration of a set of multiple dynamic beta offsets. As described above, the offset determination component 252 may receive a set of multiple possible dynamic beta offsets in an RRC configuration.

[0090] In method 600, at block 604, it may be determined that DCI indicating resource authorization for a shared channel resource does not at least include an indication of a selection of one of the multiple dynamic beta offsets. In one aspect, an offset determination component 252 (e.g., in combination with processor 212, memory 216, transceiver 202, communication component 242, etc.) may determine that DCI (e.g., DCI received via PDCCH) indicating resource authorization for a shared channel resource (e.g., PUSCH resource) does not at least include an indication of a selection of one of the multiple dynamic beta offsets. In one example, as described, the offset determination component 252 may determine that the DCI does not indicate a selection of one of the multiple dynamic beta offsets based on determining the format of the DCI (e.g., determined to be DCI format 0_0).

[0091] In method 600, at block 606, a shared data channel without UCI may be generated at least in part based on the determination. In one aspect, a resource determination component 254 (e.g., in combination with processor 212, memory 216, transceiver 202, communication component 242, etc.) may generate a shared data channel without UCI at least in part based on determining that DCI indicating resource authorization for a shared channel resource does not at least include an indication of a selection of one of the multiple dynamic beta offsets. For example, in this regard, the resource determination component 254 may determine not to transmit the UCI because the beta offset cannot be determined (e.g., not indicated by the DCI), and thus may discard the UCI.

[0092] In method 600, at block 608, the shared data channel may be transmitted on the shared data channel resource. In one aspect, a communication component 242 (e.g., in combination with processor 212, memory 216, transceiver 202, etc.) may transmit a shared data channel without UCI on the shared data channel resource (e.g., to base station 102).

[0093] In method 600, optionally at block 610, an error may be indicated in the case where the UCI includes HARQ feedback. In one aspect, a resource determination component 254 (e.g., in combination with a processor 212, a memory 216, a transceiver 202, a communication component 242, etc.) may indicate an error in the case where the UCI includes HARQ feedback. For example, the resource determination component 254 may indicate the error to another component in the UE 104 to trigger a remedial action. For example, the UE 104 may retransmit the UCI accordingly, send the UCI on different resources (e.g., PUCCH resources, subsequent PUSCH resources, etc.), enter a specific communication state, and so on.

[0094] For example, if the UE is configured with dynamic beta offset signaling via RRC, the UE 104 may not send the UCI on a PUSCH scheduled by DCI format 0_0. In this case, for example, if the UCI is a P-CSI report or an SP-CSI report on the PUCCH, the UE may discard the P-CSI or SP-CSI and only send data (e.g., non-control) communication (if any). If the UCI is a HARQ-ACK feedback (e.g., ACK, non-ACK (NACK), etc.), the UE may consider it an error situation. For example, the HARQ feedback may be considered more important (or have a higher priority) than the PUSCH. In this regard, the PUSCH may be discarded to protect the HARQ-ACK feedback; however, if the UE needs to send the HARQ-ACK feedback on the PUSCH, the grant for the PUSCH must occur later than the grant for the HARQ-ACK feedback, and it may not be intuitive for the base station to schedule the PUSCH transmission, where the base station knows that the PUSCH transmission will be cancelled / discarded. In other words, for example, the UE may not expect to be scheduled by DCI format 0_0 to have a PUSCH that overlaps with a PUCCH transmission carrying HARQ-ACK feedback.

[0095] Figure 7 is a block diagram of a MIMO communication system 700 including a base station 102 and a UE 104 according to various aspects of the present disclosure. The MIMO communication system 700 may illustrate aspects of the wireless communication access network 100 described with reference to Figure 1 described. The base station 102 may be with reference to Figure 1Examples of aspects of the described base station 102. The base station 102 may be equipped with antennas 734 and 735, and the UE 104 may be equipped with antennas 752 and 753. In the MIMO communication system 700, the base station 102 is capable of transmitting data simultaneously on multiple communication links. Each communication link may be referred to as a "layer", and the "rank" of a communication link may indicate the number of layers used for communication. For example, in a 2x2 MIMO communication system in which the base station 102 transmits two "layers", the rank of the communication link between the base station 102 and the UE 104 is 2.

[0096] At the base station 102, a transmit (Tx) processor 720 may receive data from a data source. The transmit processor 720 may process the data. The transmit processor 720 may also generate control symbols or reference symbols. A transmit MIMO processor 730 may perform spatial processing (e.g., precoding) on the data symbols, control symbols, or reference symbols (if applicable), and may provide an output symbol stream to transmit modulators / demodulators 732 and 733. Each modulator / demodulator 732 to 733 may process the respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator / demodulator 732 to 733 may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a DL signal. In one example, the DL signals from modulators / demodulators 732 and 733 may be transmitted via antennas 734 and 735, respectively.

[0097] The UE 104 may be an example of aspects of the UE 104 described with reference to Figure 1-2 At the UE 104, UE antennas 752 and 753 may receive DL signals from the base station 102, and may provide the received signals to demodulators / demodulators 754 and 755, respectively. Each demodulator / demodulator 754 to 755 may condition (e.g., filter, amplify, down-convert, and digitize) the respective received signal to obtain input samples. Each demodulator / demodulator 754 to 755 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 756 may obtain the received symbols from demodulators 754 and 755, perform MIMO detection (if applicable) on the received symbols, and provide the detected symbols. A receive (Rx) processor 758 may process (e.g., demodulate, de-interleave, and decode) the detected symbols, provide the decoded data for the UE 104 to a data output, and provide the decoded control information to a processor 780 or a memory 782.

[0098] In some cases, the processor 780 may execute stored instructions to instantiate a communication component 242 (e.g., see Figure 1 and 2)。

[0099] On the uplink (UL), at the UE 104, a transmit processor 764 may receive data from a data source and process the data. The transmit processor 764 may also generate reference symbols for reference signals. Symbols from the transmit processor 764 may be precoded by a transmit MIMO processor 766 (if applicable), further processed by modulators / demodulators 754 and 755 (e.g., for SC-FDMA, etc.), and transmitted to the base station 102 according to communication parameters received from the base station 102. At the base station 102, the UL signals from the UE 104 may be received by antennas 734 and 735, processed by demodulators / demodulators 732 and 733, detected by a MIMO detector 736 (if applicable), and further processed by a receive processor 738. The receive processor 738 may provide the decoded data to a data output and processor 740 or a memory 742.

[0100] In some cases, the processor 740 may execute stored instructions to instantiate a scheduling component 342 (e.g., see Figure 1 and 3 )。

[0101] One or more ASICs suitable for performing some or all of the applicable functions in hardware may be used to implement the components of the UE 104, either alone or in combination. Each of the modules mentioned may be a unit for performing one or more functions related to the operation of the MIMO communication system 700. Similarly, one or more ASICs suitable for performing some or all of the applicable functions in hardware may be used to implement the components of the base station 102, either alone or in combination. Each of the components mentioned may be a unit for performing one or more functions related to the operation of the MIMO communication system 700.

[0102] The above detailed description set forth above in connection with the drawings describes examples and does not represent the only examples that may be implemented or that are within the scope of the claims. The term "example" as used in this description means "serving as an example, instance, or illustration" and is not "preferred" or "advantageous over other examples". For the purpose of providing an understanding of the technologies described, the detailed description includes specific details. However, the technologies may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0103] Information and signals can be represented using any one of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, computer-executable code or instructions stored on a computer-readable medium, or any combination thereof.

[0104] The various illustrative blocks and components described in connection with the present disclosure can be implemented or performed using a specially programmed device designed to perform the functions described herein, such as, but not limited to, a processor, a digital signal processor (DSP), an ASIC, an FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The specially programmed processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. The specially programmed processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0105] The functions described herein can be implemented in hardware, software, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted through a non-transitory computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope and spirit of the present disclosure and the appended claims. For example, due to the nature of software, the functions described above can be implemented using software executed by a specially programmed processor, hardware, hardwiring, or any combination of these items. The features for implementing the functions can also be physically located at various positions, including being distributed such that portions of the functions are implemented at different physical locations. Additionally, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clear from the context, a phrase such as "X employs A or B" is intended to mean any of the natural inclusive permutations. That is, for example, any of the following instances satisfies the phrase "X employs A or B": X employs A; X employs B; or X employs both A and B. Further, as used herein (including in the claims), the "or" used in a list of items terminated by "at least one of" indicates a disjunctive list, such that, for example, a list of "at least one of A, B, or C" means A or B or C or AB or AC or BC or ABC (A and B and C).

[0106] A computer-readable medium includes both computer storage media and communication media, where the communication media includes any medium that facilitates the transfer of a computer program from one place to another. The storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example and not limitation, a computer-readable medium can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code units in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Additionally, any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave), then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is included in the definition of the medium. As used herein, disk and optical disk include compact disk (CD), laser disk, optical disk, digital versatile disk (DVD), floppy disk, and Blu-ray disk, where disks typically reproduce data magnetically, while optical disks utilize lasers to optically reproduce data. Combinations of the above are also included within the scope of computer-readable medium.

[0107] The foregoing description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Additionally, while elements of the described aspects and / or embodiments may be described or claimed in the singular, the plural is contemplated unless expressly stated to be limited to the singular. Moreover, unless otherwise stated, any aspect and / or embodiment's entirety or part may be used in conjunction with any other aspect and / or embodiment's entirety or part. Accordingly, the disclosure is not limited to the examples and designs described herein but is accorded the broadest scope consistent with the principles and novel features disclosed herein.

[0108] Below, an overview of additional examples is provided:

[0109] 1. A method for wireless communication, comprising:

[0110] Determining a beta offset for determining the number of shared channel resources to be used for transmitting uplink control information, where the downlink control information indicating a resource grant for the shared channel resources at least does not include an indication of a selection of a dynamic beta offset;

[0111] Generate a shared data channel including the uplink control information, at least partially based on the beta offset; and

[0112] Transmit the shared data channel on the shared data channel resource.

[0113] 2. The method according to Example 1, further comprising: receiving a configuration indicating a set of multiple possible dynamic beta offsets, wherein determining the beta offset includes: selecting one dynamic beta offset from the set of multiple possible dynamic beta offsets.

[0114] 3. The method according to Example 2, wherein determining the beta offset includes: selecting a first dynamic beta offset from the set of multiple possible dynamic beta offsets.

[0115] 4. The method according to any one of Examples 2 or 3, wherein the set of multiple possible dynamic beta offsets is indicated in a table with an associated index, and wherein determining the beta offset includes: selecting one dynamic beta offset having the lowest index in the table from the multiple possible dynamic beta offsets.

[0116] 5. The method according to any one of Examples 2 to 4, wherein determining the beta offset includes: selecting the last dynamic beta offset from the set of multiple possible dynamic beta offsets.

[0117] 6. The method according to any one of Examples 2 to 5, wherein selecting one dynamic beta offset from the set of multiple possible dynamic beta offsets includes:

[0118] Infer an index based at least in part on at least one of a start control channel element or a number of control channel elements of a channel on which the downlink control information is received; and

[0119] Select the one dynamic beta offset from the set of multiple possible dynamic beta offsets based at least in part on the index.

[0120] 7. The method according to any one of Examples 1 to 6, further comprising: determining that the downlink control information does not at least include the indication regarding the selection of the dynamic beta offset, at least in part based on determining a format of the downlink control information.

[0121] 8. The method according to any one of Examples 1 to 7, further comprising: receiving a configuration indicating a set of multiple possible dynamic beta offsets and a semi-static beta offset, wherein determining the beta offset includes: determining the semi-static beta offset.

[0122] 9. A method for wireless communication, comprising:

[0123] Determining a beta offset for determining a number of shared channel resources to be used for transmitting uplink control information, wherein downlink control information indicating a resource grant for the shared channel resources at least does not include an indication of a selection of a dynamic beta offset; and

[0124] Receiving a shared data channel including the uplink control information at least partially based on the beta offset.

[0125] 10. The method according to Example 9, further comprising: Transmitting a configuration indicating a set of multiple possible dynamic beta offsets, wherein determining the beta offset includes: Selecting one dynamic beta offset from the set of multiple possible dynamic beta offsets.

[0126] 11. The method according to Example 10, wherein determining the beta offset includes: Selecting a first dynamic beta offset from the set of multiple possible dynamic beta offsets.

[0127] 12. The method according to any one of Examples 10 or 11, wherein the set of multiple possible dynamic beta offsets is indicated in a table having an associated index, and wherein determining the beta offset includes: Selecting one dynamic beta offset having the lowest index in the table from the multiple possible dynamic beta offsets.

[0128] 13. The method according to any one of Examples 10 to 12, wherein determining the beta offset includes: Selecting a last dynamic beta offset from the set of multiple possible dynamic beta offsets.

[0129] 14. The method according to any one of Examples 10 to 13, wherein selecting one dynamic beta offset from the set of multiple possible dynamic beta offsets includes:

[0130] Inferring an index at least partially based on at least one of a start control channel element or a number of control channel elements of a channel on which the downlink control information is received; and

[0131] Selecting the one dynamic beta offset from the set of multiple possible dynamic beta offsets at least partially based on the index.

[0132] 15. The method according to any one of Examples 9 to 14 further includes: determining that the downlink control information at least does not include the indication regarding the selection of the dynamic beta offset, at least in part based on determining the format of the downlink control information.

[0133] 16. The method according to any one of Examples 9 to 15 further includes: transmitting a configuration indicating a set of multiple possible dynamic beta offsets and a semi-static beta offset, wherein determining the beta offset includes: determining the semi-static beta offset.

[0134] 17. The method according to any one of Examples 9 to 16, wherein determining the beta offset includes: determining a default beta offset hard-coded in a memory.

[0135] 18. An apparatus for wireless communication includes:

[0136] A transceiver;

[0137] A memory configured to store instructions; and

[0138] One or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to:

[0139] Determine a beta offset for determining a number of shared channel resources to be used for transmitting uplink control information, wherein the downlink control information indicating a resource grant for the shared channel resources at least does not include an indication of a selection of a dynamic beta offset;

[0140] Generate a shared data channel including the uplink control information at least in part based on the beta offset; and transmit the shared data channel on the shared data channel resources.

[0141] 19. The apparatus according to Example 18, wherein the one or more processors are further configured to: receive a configuration indicating a set of multiple possible dynamic beta offsets, wherein the one or more processors are configured to: determine the beta offset at least in part by selecting one dynamic beta offset from the set of multiple possible dynamic beta offsets.

[0142] 20. The apparatus according to Example 19, wherein the one or more processors are configured to: determine the beta offset at least in part by selecting a first dynamic beta offset from the set of multiple possible dynamic beta offsets.

[0143] 21. The apparatus according to any one of Examples 19 or 20, wherein the set of the plurality of possible dynamic beta offsets is indicated in a table having an associated index, and wherein the one or more processors are configured to: determine the beta offset by at least partially selecting, from the plurality of possible dynamic beta offsets, a dynamic beta offset having the lowest index in the table.

[0144] 22. The apparatus according to any one of Examples 19 to 21, wherein the one or more processors are configured to: determine the beta offset by at least partially selecting, from the set of the plurality of possible dynamic beta offsets, the last dynamic beta offset.

[0145] 23. The apparatus according to any one of Examples 19 to 22, wherein the one or more processors are configured to at least partially select, from the set of the plurality of possible dynamic beta offsets, a dynamic beta offset by:

[0146] inferring an index based at least in part on at least one of a starting control channel element or a control channel element count of a channel on which the downlink control information is received; and

[0147] selecting, based at least in part on the index, the dynamic beta offset from the set of the plurality of possible dynamic beta offsets.

[0148] 24. The apparatus according to any one of Examples 18 to 23, wherein the one or more processors are further configured to: determine that the downlink control information does not include at least the indication regarding the selection of the dynamic beta offset, at least in part based on determining a format of the downlink control information.

[0149] 25. The apparatus according to any one of Examples 18 to 24, wherein the one or more processors are further configured to: receive a configuration indicating a set of a plurality of possible dynamic beta offsets and a semi-static beta offset, wherein the one or more processors are configured to: determine the beta offset by at least partially determining the semi-static beta offset.

[0150] 26. An apparatus for wireless communication, comprising:

[0151] a transceiver;

[0152] a memory configured to store instructions; and

[0153] one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to:

[0154] Determine a beta offset for determining the number of shared channel resources to be used for transmitting uplink control information, wherein the downlink control information indicating a resource grant for the shared channel resources does not include at least an indication of a selection of a dynamic beta offset; and

[0155] Receive a shared data channel including the uplink control information, at least in part based on the beta offset.

[0156] 27. The apparatus according to example 26, wherein the one or more processors are further configured to: transmit a configuration indicating a set of multiple possible dynamic beta offsets, wherein the one or more processors are configured to determine the beta offset by at least in part selecting one dynamic beta offset from the set of multiple possible dynamic beta offsets.

[0157] 28. The apparatus according to example 27, wherein the one or more processors are configured to determine the beta offset by at least in part selecting a first dynamic beta offset from the set of multiple possible dynamic beta offsets.

[0158] 29. The apparatus according to any one of examples 27 or 28, wherein the set of multiple possible dynamic beta offsets is indicated in a table with associated indices, and wherein the one or more processors are configured to determine the beta offset by at least in part selecting one dynamic beta offset having the lowest index in the table from the multiple possible dynamic beta offsets.

[0159] 30. The apparatus according to any one of examples 27 to 29, wherein the one or more processors are configured to determine the beta offset by at least in part selecting a last dynamic beta offset from the set of multiple possible dynamic beta offsets.

[0160] 31. The apparatus according to any one of examples 27 to 30, wherein the one or more processors are configured to select one dynamic beta offset from the set of multiple possible dynamic beta offsets by at least in part:

[0161] Infer an index based at least in part on at least one of a start control channel element or a number of control channel elements of a channel on which the downlink control information is received; and

[0162] Select the one dynamic beta offset from the set of multiple possible dynamic beta offsets based at least in part on the index.

[0163] 32. The apparatus according to any one of Examples 26 to 31, wherein the one or more processors are further configured to determine that the downlink control information does not at least include the indication regarding the selection of the dynamic beta offset, at least in part based on determining the format of the downlink control information.

[0164] 33. The apparatus according to any one of Examples 26 to 32, wherein the one or more processors are further configured to transmit a configuration indicating a set of multiple possible dynamic beta offsets and a semi-static beta offset, wherein the one or more processors are configured to determine the beta offset at least in part by determining the semi-static beta offset.

[0165] 34. The apparatus according to any one of Examples 26 to 33, wherein the one or more processors are configured to determine the beta offset at least in part by determining a default beta offset hard-coded in a memory.

[0166] 35. An apparatus for wireless communication, comprising:

[0167] a unit for determining a beta offset for determining a number of shared channel resources to be used for transmitting uplink control information, wherein downlink control information indicating a resource grant for the shared channel resources does not at least include an indication regarding the selection of a dynamic beta offset;

[0168] a unit for generating a shared data channel including the uplink control information at least in part based on the beta offset; and

[0169] a unit for transmitting the shared data channel on the shared data channel resources.

[0170] 36. The apparatus according to Example 35, further comprising: a unit for receiving a configuration indicating a set of multiple possible dynamic beta offsets, wherein the determining unit determines the beta offset at least in part by selecting one dynamic beta offset from the set of multiple possible dynamic beta offsets.

[0171] 37. The apparatus according to Example 36, wherein the determining unit determines the beta offset at least in part by selecting a first dynamic beta offset from the set of multiple possible dynamic beta offsets.

[0172] 38. The apparatus according to any one of Examples 36 or 37, wherein the set of multiple possible dynamic beta offsets is indicated in a table with associated indices, and wherein the unit for determination determines the beta offset at least in part by selecting one dynamic beta offset among the multiple possible dynamic beta offsets that has the lowest index in the table.

[0173] 39. A wireless communication apparatus, comprising:

[0174] a unit for determining a beta offset for determining the number of shared channel resources to be used for transmitting uplink control information, wherein the downlink control information indicating a resource grant for the shared channel resources does not include at least an indication of a selection of a dynamic beta offset; and

[0175] a unit for receiving a shared data channel including the uplink control information at least in part based on the beta offset.

[0176] 40. The apparatus according to Example 39, further comprising: a unit for transmitting a configuration indicating a set of multiple possible dynamic beta offsets, wherein the unit for determination determines the beta offset at least in part by selecting one dynamic beta offset from the set of multiple possible dynamic beta offsets.

[0177] 41. The apparatus according to Example 40, wherein the unit for determination determines the beta offset at least in part by selecting a first dynamic beta offset from the set of multiple possible dynamic beta offsets.

[0178] 42. The apparatus according to any one of Examples 40 or 41, wherein the set of multiple possible dynamic beta offsets is indicated in a table with associated indices, and wherein the unit for determination determines the beta offset at least in part by selecting one dynamic beta offset among the multiple possible dynamic beta offsets that has the lowest index in the table.

[0179] 43. A computer-readable medium, comprising code executable by one or more processors for wireless communication, the code including code for performing the following operations:

[0180] Determine a beta offset for determining the number of shared channel resources to be used for transmitting uplink control information, wherein the downlink control information indicating a resource grant for the shared channel resources does not include at least an indication of a selection of a dynamic beta offset;

[0181] Generate a shared data channel including the uplink control information based at least in part on the beta offset; and

[0182] Transmit the shared data channel on the shared data channel resources.

[0183] 44. The computer-readable medium according to example 43, further comprising: code for receiving a configuration indicating a set of multiple possible dynamic beta offsets, wherein the code for determining determines the beta offset at least in part by selecting one dynamic beta offset from the set of multiple possible dynamic beta offsets.

[0184] 45. The computer-readable medium according to example 44, wherein the code for determining determines the beta offset at least in part by selecting a first dynamic beta offset from the set of multiple possible dynamic beta offsets.

[0185] 46. The computer-readable medium according to any one of examples 44 or 45, wherein the set of multiple possible dynamic beta offsets is indicated in a table having an associated index, and wherein the code for determining determines the beta offset at least in part by selecting one dynamic beta offset having the lowest index in the table from the multiple possible dynamic beta offsets.

[0186] 47. A computer-readable medium, comprising code executable by one or more processors for wireless communication, the code comprising code for performing the following operations:

[0187] Determine a beta offset for determining the number of shared channel resources to be used for transmitting uplink control information, wherein the downlink control information indicating a resource grant for the shared channel resources does not include at least an indication of a selection of a dynamic beta offset; and

[0188] Receive a shared data channel including the uplink control information based at least in part on the beta offset.

[0189] 48. The computer-readable medium according to example 47, further comprising: code for transmitting a configuration indicating a set of multiple possible dynamic beta offsets, wherein the code for determining determines the beta offset at least in part by selecting one dynamic beta offset from the set of multiple possible dynamic beta offsets.

[0190] 49. The computer-readable medium according to Example 48, wherein the code for determination determines the beta offset by at least partially selecting a first dynamic beta offset from the set of the plurality of possible dynamic beta offsets.

[0191] 50. The computer-readable medium according to any one of Examples 48 or 49, wherein the set of the plurality of possible dynamic beta offsets is indicated in a table having an associated index, and wherein the code for determination determines the beta offset by at least partially selecting a dynamic beta offset having the lowest index in the table from the plurality of possible dynamic beta offsets.

Claims

1. A method for wireless communication, comprising: receiving a configuration indicating a set of multiple possible dynamic beta offsets; receiving downlink control information for scheduling or activating shared channel resources, wherein the downlink control information at least does not include an indication of a selection of a dynamic beta offset; determining a beta offset from a first value in the set of multiple possible dynamic beta offsets; and transmitting a shared data channel including uplink control information on the shared channel resources using the determined beta offset.

2. The method according to claim 1, wherein the set of multiple possible dynamic beta offsets is indicated in a table with associated indexes, and wherein determining the beta offset includes: selecting a dynamic beta offset in the set of multiple possible dynamic beta offsets that has the lowest index in the table.

3. The method according to claim 1, further comprising: determining that the downlink control information at least does not include the indication of the selection of the dynamic beta offset, at least partially based on determining the format of the downlink control information.

4. The method according to claim 1, further comprising: receiving a configuration indicating a set of multiple possible dynamic beta offsets and a semi-static beta offset, wherein determining the beta offset includes: determining the semi-static beta offset.

5. A method for wireless communication, comprising: transmitting a configuration indicating a set of multiple possible dynamic beta offsets to a user equipment (UE); and in response to the downlink control information for scheduling or activating shared channel resources at least not including an indication of a selection of a dynamic beta offset, receiving a shared data channel including uplink control information from the UE on the shared channel resources using a first dynamic beta offset in the set of multiple possible dynamic beta offsets.

6. The method according to claim 5, wherein the set of multiple possible dynamic beta offsets is indicated in a table with associated indexes, and wherein receiving the shared data channel includes: using a dynamic beta offset in the set of multiple possible dynamic beta offsets that has the lowest index in the table.

7. The method according to claim 5, further comprising: determining that the downlink control information at least does not include the indication of the selection of the dynamic beta offset, at least partially based on determining the format of the downlink control information.

8. The method according to claim 5, further comprising: transmitting a configuration indicating a set of multiple possible dynamic beta offsets and a semi-static beta offset, wherein using the first dynamic beta offset in the set of multiple possible dynamic beta offsets is based on determining the semi-static beta offset.

9. An apparatus for wireless communication, comprising: a transceiver; a memory configured to store instructions; and one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: receive a configuration indicating a set of multiple possible dynamic beta offsets; receive downlink control information scheduling or activating a shared channel resource, wherein the downlink control information at least does not include an indication of a selection of a dynamic beta offset; determine a beta offset from a first value in the set of multiple possible dynamic beta offsets; and transmit a shared data channel including uplink control information on the shared channel resource using the determined beta offset.

10. The apparatus according to claim 9, wherein, the set of multiple possible dynamic beta offsets is indicated in a table having associated indices, and wherein the one or more processors are configured to: determine the beta offset at least in part by selecting one dynamic beta offset in the set of multiple possible dynamic beta offsets that has the lowest index in the table.

11. The apparatus according to claim 9, wherein, the one or more processors are further configured to: determine that the downlink control information at least does not include the indication of the selection of the dynamic beta offset at least in part based on determining a format of the downlink control information.

12. The apparatus according to claim 9, wherein, the one or more processors are further configured to: receive a configuration indicating a set of multiple possible dynamic beta offsets and a semi-static beta offset, wherein the one or more processors are configured to: determine the beta offset at least in part by determining the semi-static beta offset.

13. An apparatus for wireless communication, comprising: a transceiver; a memory configured to store instructions; and one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: send a configuration indicating a set of multiple possible dynamic beta offsets to a user equipment (UE); and in response to downlink control information scheduling or activating a shared channel resource at least not including an indication of a selection of a dynamic beta offset, receive a shared data channel including uplink control information from the UE on the shared channel resource using a first dynamic beta offset in the set of multiple possible dynamic beta offsets.

14. The apparatus according to claim 13, wherein, the set of multiple possible dynamic beta offsets is indicated in a table having associated indices, and wherein the one or more processors are configured to: receive the shared data channel including using one dynamic beta offset in the set of multiple possible dynamic beta offsets that has the lowest index in the table.

15. The apparatus according to claim 13, wherein, The one or more processors are further configured to determine that the downlink control information does not include at least the indication regarding the selection of the dynamic beta offset, at least in part based on determining the format of the downlink control information.

16. The apparatus according to claim 13, wherein the one or more processors are further configured to: transmit a configuration indicating a set of multiple possible dynamic beta offsets and a semi-static beta offset, wherein the one or more processors are configured to use a first dynamic beta offset in the set of multiple possible dynamic beta offsets based on determining the semi-static beta offset.

17. An apparatus for wireless communication, comprising: a unit for receiving a configuration indicating a set of multiple possible dynamic beta offsets; a unit for receiving downlink control information for scheduling or activating shared channel resources, wherein the downlink control information does not include at least an indication regarding the selection of a dynamic beta offset; a unit for determining a beta offset from a first value in the set of multiple possible dynamic beta offsets; and a unit for transmitting a shared data channel including uplink control information on the shared channel resources using the determined beta offset.

18. The apparatus according to claim 17, wherein the set of multiple possible dynamic beta offsets is indicated in a table with an associated index, and wherein the unit for determining determines the beta offset at least in part by selecting a dynamic beta offset in the set of multiple possible dynamic beta offsets that has the lowest index in the table.

19. An apparatus for wireless communication, comprising: a unit for transmitting to a user equipment (UE) a configuration indicating a set of multiple possible dynamic beta offsets; and a unit for receiving, in response to downlink control information for scheduling or activating shared channel resources that does not include at least an indication regarding the selection of a dynamic beta offset, a shared data channel including uplink control information from the UE on the shared channel resources using a first dynamic beta offset in the set of multiple possible dynamic beta offsets.

20. The apparatus according to claim 19, wherein the set of multiple possible dynamic beta offsets is indicated in a table with an associated index, and wherein the unit for receiving receives the shared data channel by using a dynamic beta offset in the set of multiple possible dynamic beta offsets that has the lowest index in the table.

21. A computer-readable storage medium comprising code executable by one or more processors for wireless communication, the code including code for performing the following operations: receiving a configuration indicating a set of multiple possible dynamic beta offsets; receiving downlink control information for scheduling or activating shared channel resources, wherein the downlink control information does not include at least an indication regarding the selection of a dynamic beta offset; Determine a beta offset from a first value in the set of the plurality of possible dynamic beta offsets; and Transmit a shared data channel including uplink control information on the shared channel resource using the determined beta offset.

22. The computer-readable storage medium according to claim 21, wherein the set of the plurality of possible dynamic beta offsets is indicated in a table with associated indices, and wherein the code for determination determines the beta offset at least in part by selecting a dynamic beta offset in the set of the plurality of possible dynamic beta offsets that has the lowest index in the table.

23. A computer-readable storage medium comprising code executable by one or more processors for wireless communication, the code comprising code for performing the following operations: Transmit a configuration indicating a set of a plurality of possible dynamic beta offsets to a user equipment (UE); and In response to downlink control information scheduling or activating a shared channel resource not including at least an indication of a selection of a dynamic beta offset, receive a shared data channel including uplink control information from the UE on the shared channel resource using a first dynamic beta offset in the set of the plurality of possible dynamic beta offsets.

24. The computer-readable storage medium according to claim 23, wherein the set of the plurality of possible dynamic beta offsets is indicated in a table with associated indices, and wherein the code for reception receives the shared data channel by using a dynamic beta offset in the plurality of possible dynamic beta offsets that has the lowest index in the table.

Images