Resource allocation for uplink control information (UCI) and data multiplexing on the Physical Uplink Shared Channel (PUSCH)

Abstract

Some aspects of this disclosure relate to methods and apparatus for multiplexing UCI with data in Physical Uplink Shared Channel (PUSCH) transmission.

Description

[0001] This application is a divisional application of the invention patent application filed on November 5, 2018, with application number 201880077459.8 and entitled "Resource Allocation for Uplink Control Information (UCI) and Data Multiplexing on Physical Uplink Shared Channel (PUSCH)".

[0002] Cross-reference to related applications and claims of priority

[0003] This application claims the rights and priority of Patent Cooperation Treaty application No. PCT / CN2017 / 114218, filed on December 1, 2017, which is assigned to the assignee of this application and is incorporated herein by reference as fully set forth below and for all applicable purposes. Technical Field

[0004] In general, this disclosure relates to communication systems, and more specifically, to methods and apparatus relating to the multiplexing of uplink control information (UCI) and data. Background Technology

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power). Examples of such multiple access technologies include Long Term Evolution (LTE) systems, 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, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0006] In some examples, a radio multiple access communication system may include multiple base stations, each supporting communication to multiple communication devices (also referred to as user equipment (UE)) simultaneously. In LTE or LTE-A networks, a set of one or more base stations may define an evolved Node B (eNB). In other examples (e.g., in next-generation or 5G networks), a radio multiple access communication system may include multiple distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmit-receive points (TRPs), etc.) communicating with multiple central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), wherein a set of one or more distributed units communicating with a central unit may define access nodes (e.g., new radio base stations (NR BSs), new radio Node Bs (NR NBs), network nodes, 5GNBs, eNBs, etc.). A base station or DU may communicate with a set of UEs on downlink channels (e.g., for transmissions from a base station to a UE) and uplink channels (e.g., for transmissions from a UE to a base station or distributed unit).

[0007] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, country, region, and even global levels. An example of an emerging telecommunications standard is New Radio (NR), such as 5G Radio Access. NR is a set of enhancements to the LTE mobile standard released by the 3rd Generation Partnership Project (3GPP). It is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and using OFDMA with a cyclic prefix (CP) on the downlink (DL) and uplink (UL), thereby better supporting mobile broadband internet access, as well as beamforming, multiple-input multiple-output (MIMO) antenna technologies, and carrier aggregation.

[0008] However, with the continued growth in demand for mobile broadband access, there is an expectation for further improvements to NR technology. Preferably, these improvements should be applicable to other multiple access technologies and telecommunications standards that employ these technologies. Summary of the Invention

[0009] The systems, methods, and apparatuses of this disclosure have several aspects, none of which individually assumes responsibility for their desired properties. Without limiting the scope of this disclosure as set forth in the following claims, some features will now be briefly discussed. Upon consideration of this discussion, and especially after reading the section entitled "Detailed Description," it will be understood how these features of the disclosure provide advantages, including improved communication between access points and stations in a wireless network.

[0010] Some aspects provide a method for wireless communication by a UE. In general, the method includes: determining a total amount of resources allocated for transmitting both uplink data and uplink control information (UCI) in a Physical Uplink Shared Channel (PUSCH) transmission; determining a maximum supported payload size for transmitting the UCI, based at least in part on the total amount of allocated resources and a minimum amount of resources allocated for the uplink data; and transmitting the uplink data and UCI in the PUSCH based on the total amount of allocated resources and the determined maximum supported payload size.

[0011] The aspects also include methods, apparatus, systems, computer-readable media, and processing systems capable of performing the above operations and fully described herein with reference to the accompanying drawings, which are also shown in the drawings.

[0012] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth certain illustrative features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of each aspect can be employed, and this description is intended to include all such aspects and their equivalents. Attached Figure Description

[0013] To gain a more detailed understanding of the features described above, reference can be made to various aspects (briefly outlined above), some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and are therefore not intended to limit its scope, as the description may allow for other equally valid aspects.

[0014] Figure 1 This is a conceptual block diagram illustrating an example telecommunications system based on certain aspects of this disclosure.

[0015] Figure 2 This is a block diagram illustrating an example logical architecture of a distributed RAN based on certain aspects of this disclosure.

[0016] Figure 3 This is a diagram illustrating an example physical architecture of a distributed RAN according to certain aspects of this disclosure.

[0017] Figure 4 This is a block diagram conceptually illustrating the design of an example BS and user equipment (UE) based on certain aspects of this disclosure.

[0018] Figure 5 This is a diagram illustrating an example of implementing a communication protocol stack according to certain aspects of this disclosure.

[0019] Figure 6 An example of a DL-centered subframe is shown, which is in accordance with certain aspects of this disclosure.

[0020] Figure 7 An example of a UL-centered subframe is shown, which is in accordance with certain aspects of this disclosure.

[0021] Figure 8A and 8B Example uplink and downlink structures according to certain aspects of this disclosure are shown respectively.

[0022] Figure 9 Example operation of wireless communication performed by a user equipment (UE) in accordance with certain aspects of this disclosure is shown.

[0023] Figure 10 and 11 Example operations that can be performed by the UE to determine the UCI payload are shown, based on certain aspects of this disclosure.

[0024] To aid understanding, the same reference numerals have been used where possible to designate common elements for the purposes of the figures. It is intended that elements disclosed in one aspect can be usefully applied to other aspects without requiring specific description. Detailed Implementation

[0025] Various aspects of this disclosure relate to methods and apparatus for multiplexing UCI and data, for example, in a single Physical Uplink Shared Channel (PUSCH) transmission.

[0026] This disclosure provides apparatus, methods, processing systems, and computer-readable media for new radio (NR) (new wireless access technology or 5G technology).

[0027] NR can support a variety of wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., over 80 MHz), millimeter wave (mmW) targeting high carrier frequencies (e.g., 60 GHz), massive MTC (mMTC) targeting non-backward-compatible MTC technologies, and / or mission-critical ultra-reliable low-latency communication (URLLC). These services can include latency and reliability requirements. These services can also have different transmission time intervals (TTIs) to meet corresponding quality of service (QoS) requirements. Furthermore, these services can coexist in the same subframe.

[0028] The following description provides examples and does not limit 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 this disclosure. Various processes or components may be omitted, substituted, or added as appropriate in the examples. For example, the described method may be performed in a different order than that described, and various steps may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined with those in other examples. For example, an apparatus or a method may be implemented using any number of aspects set forth herein. Moreover, the scope of this disclosure is intended to cover such apparatuses or methods implemented using structures, functions, or structures and functions other than or different from those aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims. The term “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects.

[0029] The technologies described in this article can be used in various wireless communication networks, such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and others. The terms "network" and "system" are often used interchangeably. CDMA networks can implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 encompasses the IS-2000, IS-95, and IS-856 standards. TDMA networks can implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA networks can implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). NR is an emerging wireless communication technology under development, integrated with the 5G Technology Forum (5GTF). 3GPP Long Term Evolution (LTE) and Improved LTE (LTE-A) are versions of UMTS using E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the 3rd Generation Partnership Project (3GPP). cdma2000 and UMB are described in documents from an organization called the 3rd Generation Partnership Project 2 (3GPP2). The technologies described herein can be used with the aforementioned wireless networks and radio technologies, as well as other wireless networks and radio technologies. For clarity, although this document may use terms commonly associated with 3G and / or 4G wireless technologies to describe aspects, aspects of this disclosure can be applied to communication systems based on other generations (e.g., 5G and later technologies, including NR technology).

[0030] Example wireless communication system

[0031] Figure 1 An example wireless network 100, such as a new radio (NR) or 5G network, is shown in which aspects of this disclosure can be implemented.

[0032] like Figure 1As shown, the wireless network 100 may include multiple BS110s and other network entities. A BS may be a station communicating with a UE. Each BS110 may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a Node B and / or the Node B subsystem serving that coverage area, depending on the context in which the term is used. In NR systems, the term "cell" is interchangeable with eNB, Node B, 5G NB, AP, NR BS, NR BS, or TRP. In some examples, a cell may not be stationary, and the geographic area of ​​a cell may move depending on the location of the mobile base station. In some examples, base stations may interconnect with each other and / or with one or more other base stations or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces (e.g., direct physical connection, virtual network, or interface using any suitable transport network).

[0033] Typically, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific Radio Access Technology (RAT) and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks with different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0034] A BS can provide communication coverage for macrocells, picocells, femtocells, and / or other types of cells. A macrocell can cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access by UEs with service subscriptions. A picocell can cover a relatively small geographic area and allow unrestricted access by UEs with service subscriptions. A femtocell can cover a relatively small geographic area (e.g., a residential area) and allow restricted access by UEs associated with that femtocell (e.g., UEs in a Closed Subscriber Group (CSG), UEs for users in a residential area, etc.). A BS used for macrocells can be called a macro BS. A BS used for picocells can be called a pico BS. A BS used for femtocells can be called a femto BS or a home BS. Figure 1 In the examples shown, BS110a, 110b, and 110c can be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS110x can be a pico BS for pico cell 102x. BS110y and 110z can be femto BSs for femto cells 102y and 102z, respectively. A BS can support one or more (e.g., three) cells.

[0035] The wireless network 100 may also include relay stations. A relay station is a station that receives data transmissions and / or other information from an upstream station (e.g., a BS or a UE) and transmits the data transmissions and / or other information to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that relays transmissions for other UEs. Figure 1 In the example shown, relay station 110r can communicate with BS110a and UE120r to facilitate communication between BS110a and UE120r. A relay station can also be referred to as a relay BS, repeater, etc.

[0036] Wireless network 100 can be a heterogeneous network comprising different types of BSs (e.g., macro BS, pico BS, femto BS, repeaters, etc.). These different types of BSs can have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs can have high transmit power levels (e.g., 20 watts), while pico BSs, femto BSs, and repeaters can have lower transmit power levels (e.g., 1 watt).

[0037] Wireless network 100 can support synchronous or asynchronous operation. For synchronous operation, BSs can have similar frame timings, and transmissions from different BSs can be approximately time-aligned. For asynchronous operation, BSs can have different frame timings, and transmissions from different BSs can be time-disaligned. The techniques described herein can be used for both synchronous and asynchronous operations.

[0038] Network controller 130 can be coupled to a group of base stations (BSs) and provide coordination and control for these BSs. Network controller 130 can communicate with BS 110 via backhaul. BS 110 can also communicate with each other directly or indirectly, for example, via wireless or wired backhaul.

[0039] UE 120 (e.g., 120x, 120y, etc.) may be distributed throughout the wireless network 100, and each UE may be stationary or mobile. UE may also be referred to as a mobile station, terminal, access terminal, user unit, station, customer premises equipment (CPE), cellular phone, smartphone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet device, camera, gaming device, netbook, smartbook, ultrabook, medical device or medical apparatus, biometric sensor / device, wearable device (e.g., smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.)), entertainment device (e.g., music device, video device, satellite radio unit, etc.), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, GPS device, or any other suitable device configured to communicate via wireless or wired media. Some UEs can be considered evolved machine-type communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with a BS, another device (e.g., a remote device), or some other entity. Wireless nodes can provide connectivity to or from a network (e.g., a wide area network such as the Internet or cellular networks) via wired or wireless communication links. Some UEs can be considered Internet of Things (IoT) devices. Figure 1 In the diagram, a solid line with a double arrow indicates the desired transmission between the UE and the serving BS, which is the BS designated to serve the UE on the downlink and / or uplink. A dashed line with a double arrow indicates interference transmission between the UE and the BS.

[0040] Some wireless networks (e.g., LTE) utilize Orthogonal Frequency Division Multiplexing (OFDM) on the downlink and Single-Carrier Frequency Division Multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are often also referred to as tones, frequency bands, etc. Data can be used to modulate each subcarrier. Typically, modulation symbols are transmitted using OFDM in the frequency domain and SC-FDM in the time domain. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing can be 15 kHz, and the minimum resource allocation (called a "resource block") can be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, the nominal FFT size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband can cover 1.08MHz (i.e., 6 resource blocks), and for system bandwidths of 1.25, 2.5, 5, 10, or 20MHz, there can be 1, 2, 4, 8, or 16 subbands respectively.

[0041] While the aspects of the examples described herein can be associated with LTE technology, aspects of this disclosure can be applied with other wireless communication systems, such as NR. NR can utilize OFDM with CP on both the uplink and downlink, and can include support for half-duplex operation using Time Division Duplex (TDD). A single-component carrier bandwidth of 100 MHz can be supported. An NR resource block can span 12 subcarriers with a subcarrier bandwidth of 75 kHz over a duration of 0.1 ms. Each radio frame can consist of 50 subframes with a length of 10 ms. Therefore, each subframe can have a length of 0.2 ms. Each subframe can indicate the link direction (i.e., DL or UL) for data transmission, and the link direction for each subframe can be dynamically switched. Each subframe can include DL / UL data and DL / UL control data. The UL and DL subframes used for NR can be as follows: Figure 6 and 7 A more detailed description is provided. Beamforming can be supported and beam direction can be dynamically configured. MIMO transmission with precoding can also be supported. MIMO configuration in the DL can support up to 8 transmit antennas, with up to 8 streams in the multi-layer DL transmission and up to 2 streams per UE. Multi-layer transmission with up to 2 streams per UE can be supported. Aggregation of multiple cells with up to 8 serving cells can be supported. Alternatively, NR can support different air interfaces in addition to the OFDM-based air interface. The NR network can include entities such as CU and / or DU.

[0042] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., a base station) allocates resources for communication among some or all devices and apparatuses within its service area or cell. Within this disclosure, as further discussed below, the scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, the subordinate entity utilizes the resources allocated by the scheduling entity. A base station is not the only entity that can be used as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity, scheduling resources for one or more subordinate entities (e.g., one or more other UEs). In this example, the UE is acting as a scheduling entity, while other UEs utilize the resources scheduled by that UE for wireless communication. A UE can act as a scheduling entity in peer-to-peer (P2P) networks and / or mesh networks. In the mesh network example, in addition to communicating with a scheduling entity, UEs may optionally communicate directly with each other.

[0043] Therefore, in a wireless communication network with scheduled access to time and frequency resources and with cellular, P2P, and mesh configurations, the scheduling entity and one or more subordinate entities can use the scheduled resources to communicate.

[0044] As mentioned above, the RAN can include CU and DU. An NR BS (e.g., eNB, 5G Node B, Node B, Transmit / Receive Point (TPR), Access Point (AP)) can correspond to one or more BSs. An NR cell can be configured as an Access Cell (ACell) or a Data-Only Cell (DCell). For example, the RAN (e.g., Central Unit or Distributed Unit) can configure the cell. A DCell can be a cell used for carrier aggregation or dual connectivity, but not for initial access, cell selection / reselection, or handover. In some cases, a DCell may not transmit synchronization signals—in other cases, a DCell may transmit SS. An NRBS can transmit downlink signals to the UE to indicate the cell type. Based on the cell type indication, the UE can communicate with the NR BS. For example, the UE can determine which NR BS to consider for cell selection, access, handover, and / or measurement based on the indicated cell type.

[0045] Figure 2 It shows that it can be used Figure 1The diagram illustrates an example logical architecture of a distributed radio access network (RAN) 200 implemented in a wireless communication system. A 5G access node 206 may include an access node controller (ANC) 202. The ANC may be the central unit (CU) of the distributed RAN 200. Backhaul interfaces to the next-generation core network (NG-CN) 204 may terminate at the ANC. Backhaul interfaces to adjacent next-generation access nodes (NG-AN) may also terminate at the ANC. The ANC may include one or more TRPs 208 (which may also be referred to as a BS, NR BS, Node B, 5G NB, AP, or some other term). As mentioned above, TRPs can be used interchangeably with "cells".

[0046] TRP 208 may be a DU. A TRP may connect to one ANC (ANC 202) or more ANCs (not shown). For example, for RAN sharing, Radio as a Service (RaaS), and service-specific AND deployments, a TRP may connect to more than one ANC. A TRP may include one or more antenna ports. A TRP may be configured to provide services to the UE individually (e.g., dynamically selected) or jointly (e.g., jointly transmitted).

[0047] Local architecture 200 can be used to illustrate the fronthaul definition. This architecture can be defined to support fronthaul schemes across different deployment types. For example, the architecture can be based on sending network capabilities (e.g., bandwidth, latency, and / or jitter).

[0048] This architecture can share features and / or components with LTE. Depending on various aspects, the next-generation AN (NG-AN)210 can support dual connectivity with NR. NG-AN can share common fronthaul for both LTE and NR.

[0049] This architecture enables collaboration between and between TRPs 208. For example, collaboration can be pre-configured within and / or across TRPs via ANC 202. Depending on the circumstances, no inter-TRP interface may be required or even exist.

[0050] Depending on various factors, dynamic configuration of splitting logic functions is possible within Architecture 200. (Refer to...) Figure 5 In more detail, the Radio Resource Control (RRC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and Physical (PHY) layer can be adaptively placed at the DU or CU (e.g., TRP or ANC, respectively). Depending on some aspects, the BS may include a Central Unit (CU) (e.g., ANC 202) and / or one or more Distributed Units (e.g., one or more TRPs 208).

[0051] Figure 3 An example physical architecture of a distributed RAN 300 according to various aspects of this disclosure is shown. A centralized core network unit (C-CU) 302 can manage core network functions. The C-CU can be deployed centrally. C-CU functions can be offloaded (e.g., to Advanced Wireless Services (AWS)) to handle peak capacity.

[0052] The centralized RAN unit (C-RU) 304 can manage one or more ANC functions. Optionally, the C-RU can manage core network functions locally. The C-RU can be deployed in a distributed manner. The C-RU can be located closer to the network edge.

[0053] The DU 306 can manage one or more TRPs (Edge Nodes (EN), Edge Units (EU), Radio Headers (RH), Smart Radio Headers (SRH), etc.). The DU can be located at the edge of a network with radio frequency (RF) capabilities.

[0054] Figure 4 It shows in Figure 1 The example components of BS110 and UE 120 shown herein can be used to implement various aspects of this disclosure. As described above, the BS may include a TRP. One or more components of BS110 and UE 120 can be used to implement various aspects of this disclosure. For example, antenna 452, Tx / Rx 222, processors 466, 458, 464 and / or controller / processor 480 of UE 120, and / or antenna 434, processors 460, 420, 438 and / or controller / processor 440 of BS110 can be used to perform the operations described herein.

[0055] Figure 4 The BS110 and UE 120 are shown (they can be...) Figure 1 A block diagram of the design of a BS (BS in the BS) and a UE (UE in the UE). For restricted association scenarios, base station 110 can be Figure 1 In the UE 120, the macro BS110c and UE 120 can be UE120y. The base station 110 can also be some other type of base station. The base station 110 can be equipped with antennas 434a to 434t, and the UE 120 can be equipped with antennas 452a to 452r.

[0056] At base station 110, transmit processor 420 can receive data from data source 412 and control information from controller / processor 440. The control information can be used for the Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid ARQ Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), etc. Data can be used for the Physical Downlink Shared Channel (PDSCH), etc. Processor 420 can process (e.g., encode and symbol mapping) the data and control information separately to obtain data symbols and control symbols. Processor 420 can also generate reference symbols, for example, for PSS, SSS, and cell-specific reference signals. Transmit (TX) Multiple-Input Multiple-Output (MIMO) processor 430 can perform spatial processing (e.g., precoding, if applicable) on data symbols, control symbols, and / or reference symbols, and can provide an output symbol stream to modulators (MODs) 432a to 432t. For example, TX MIMO processor 430 can perform certain aspects described herein with respect to RS multiplexing. Each modulator 432 can (e.g., for OFDM, etc.) process the corresponding output symbol stream to obtain an output sample stream. Each modulator 432 can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signal from modulators 432a to 432t can be transmitted via antennas 434a to 434t respectively.

[0057] At UE 120, antennas 452a to 452r can receive downlink signals from base station 110 and can provide the received signals to demodulators (DEMODs) 454a to 454r respectively. Each demodulator 454 can adjust (e.g., filter, amplify, down-convert, and digitize) the corresponding received signal to obtain an input sample. Each demodulator 454 can further process the input sample (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 456 can obtain received symbols from all demodulators 454a to 454r, perform MIMO detection on the received symbols (if applicable), and provide the detected symbols. For example, MIMO detector 456 provides detected RS transmitted using the techniques described herein. Receiver processor 458 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 120 to data sink 460, and provide decoded control information to controller / processor 480. Depending on one or more of these cases, the CoMP aspect may include providing an antenna and some Tx / Rx functions, such that they are located in a distributed unit. For example, some Tx / Rx processing may be performed in a central unit, while other processing may be performed in a distributed unit. For example, according to one or more aspects shown in the figure, the BS modulator / demodulator 432 may be located in a distributed unit.

[0058] On the uplink, at UE 120, the transmitting processor 464 can receive and process data from data source 462 (e.g., for the Physical Uplink Shared Channel (PUSCH)) and control information from controller / processor 480 (e.g., for the Physical Uplink Control Channel (PUCCH)). The transmitting processor 464 can also generate reference symbols for reference signals. Symbols from the transmitting processor 464 can be pre-encoded (if applicable) by TX MIMO processor 466, further processed by demodulators 454a to 454r (e.g., for SC-FDM, etc.), and transmitted to base station 110. At BS 110, the uplink signal from UE 120 can be received by antenna 434, processed by modulator 432, detected by MIMO detector 436 (if applicable), and further processed by receiving processor 438 to obtain decoded data and control information transmitted by UE 120. The receiver processor 438 can provide decoded data to the data sink 439 and decoded control information to the controller / processor 440.

[0059] Controllers / processors 440 and 480 can respectively direct operations at base station 110 and UE 120. Processor 440 and / or other processors and modules at base station 110 can perform or direct, for example, operations at... Figure 9 , 10 The execution of the functional blocks shown in 11 and / or other processes used in the techniques described herein. Processor 480 and / or other processors and modules at UE 120 may also execute or direct processes used in the techniques described herein. Memory 442 and 482 may store data and program code for BS 110 and UE 120, respectively. Scheduler 444 may schedule the UE for data transmission on the downlink and / or uplink.

[0060] Figure 5Figure 500 illustrates examples of implementing a communication protocol stack according to various aspects of this disclosure. The illustrated communication protocol stack can be implemented by a device operating in a 5G system (e.g., a system supporting uplink-based mobility). Figure 500 illustrates a communication protocol stack including a Radio Resource Control (RRC) layer 510, a Packet Data Convergence Protocol (PDCP) layer 515, a Radio Link Control (RLC) layer 520, a Media Access Control (MAC) layer 525, and a Physical (PHY) layer 530. In various examples, these layers of the protocol stack can be implemented as separate software modules, portions of a processor or ASIC, portions of non-co-located devices connected via a communication link, or various combinations thereof. Co-located and non-co-located implementations can be used, for example, in a protocol stack for a network access device (e.g., AN, CU, and / or DU) or a UE.

[0061] Option 505-a illustrates a split implementation of the protocol stack, where, in a centralized network access device (e.g., Figure 2 ANC 202) and distributed network access devices (e.g., Figure 2 The implementation of the protocol stack is split between DU 208. In option 505-a, the RRC layer 510 and PDCP layer 515 can be implemented by the central unit, while the RLC layer 520, MAC layer 525, and physical layer 530 can be implemented by the DU. In various examples, the CU and DU can be co-located or non-co-located. Option 505-a can be useful in macrocell, microcell, or picocell deployments.

[0062] Option 505-b illustrates a unified implementation of the protocol stack, where the stack is implemented in a single network access device (e.g., Access Node (AN), New Radio Base Station (NR BS), New Radio Node B (NR NB), Network Node (NN), etc.). In this option, the RRC layer 510, PDCP layer 515, RLC layer 520, MAC layer 525, and physical layer 530 can all be implemented by the AN. Option 505-b can be useful in femtocell deployments.

[0063] Regardless of whether the network access device implements part or all of the protocol stack, the UE can implement the entire protocol stack (e.g., RRC layer 510, PDCP layer 515, RLC layer 520, MAC layer 525 and physical layer 530).

[0064] Figure 6Figure 600 illustrates an example of a DL-centered subframe. The DL-centered subframe may include a control portion 602. The control portion 602 may exist in the initial or beginning portion of the DL-centered subframe. The control portion 602 may include various scheduling and / or control information corresponding to the various portions of the DL-centered subframe. In some configurations, the control portion 602 may be a Physical DL Control Channel (PDCCH), such as... Figure 6 As indicated in [the document], the DL-centric subframe may also include a DL data portion 604. The DL data portion 604 may sometimes be referred to as the payload of the DL-centric subframe. The DL data portion 604 may include communication resources for transmitting DL data from a scheduling entity (e.g., a UE or BS) to a subordinate entity (e.g., a UE). In some configurations, the DL data portion 604 may be a Physical DL Shared Channel (PDSCH).

[0065] The DL-centered subframe may also include a common UL portion 606. The common UL portion 606 may sometimes be referred to as a UL burst, a common UL burst, and / or various other suitable terms. The common UL portion 606 may include feedback information corresponding to other portions of the DL-centered subframe. For example, the common UL portion 606 may include feedback information corresponding to the control portion 602. Non-limiting examples of feedback information may include ACK signals, NACK signals, HARQ indicators, and / or various other suitable types of information. The common UL portion 606 may include additional or alternative information, such as information related to the Random Access Channel (RACH) procedure, scheduling requests (SR), and various other suitable types of information. Figure 6 As shown, the end of the DL data portion 604 may be temporally separated from the start of the common UL portion 606. This temporal separation may sometimes be referred to as a gap, guard period, guard interval, and / or various other suitable terms. This separation provides the time for switching from DL communication (e.g., a receive operation performed by a subordinate entity (e.g., a UE)) to UL communication (e.g., a transmit operation performed by a subordinate entity (e.g., a UE)). Those skilled in the art will understand that the foregoing is merely an example of a DL-centric subframe, and alternative structures with similar features may exist without necessarily departing from the aspects described herein.

[0066] Figure 7 Figure 700 shows an example of a subframe centered on UL. The UL-centered subframe may include a control section 702. The control section 702 may be present in the initial or beginning portion of the UL-centered subframe. Figure 7 The control section 702 in the above reference can be similar to the one described above. Figure 6The control portion is described. The UL-centric subframe may also include a UL data portion 704. The UL data portion 704 may sometimes be referred to as the payload of the UL-centric subframe. The UL data portion may refer to the communication resources used to transmit UL data from a subordinate entity (e.g., the UE) to a scheduling entity (e.g., the UE or the BS). In some configurations, the control portion 702 may be the Physical DL Control Channel (PDCCH).

[0067] like Figure 7 As shown, the end of control section 702 may be temporally separated from the start of UL data section 704. This temporal separation may sometimes be referred to as a gap, protection period, protection interval, and / or various other suitable terms. This separation provides the time for switching from DL communication (e.g., a receive operation performed by a scheduling entity) to UL communication (e.g., a transmit operation performed by a scheduling entity). UL-centric subframes may also include a common UL section 706. Figure 7 The public UL section 706 in the document can be similar to the above reference. Figure 7 The common UL portion 706 is described. The common UL portion 706 may additionally or alternatively include information relating to the Channel Quality Indicator (CQI), the Sounding Reference Signal (SRS), and various other suitable types of information. Those skilled in the art will understand that the foregoing is merely an example of a UL-centric subframe, and that alternative structures with similar features may exist without necessarily departing from the aspects described herein.

[0068] In some cases, two or more dependent entities (e.g., UEs) can communicate with each other using secondary link signaling. Real-world applications of such secondary link communication can include public safety, proximity services, UE-to-network relay, vehicle-to-vehicle (V2V) communication, Internet of Things (IoE) communication, IoT communication, mission-critical mesh networks, and / or various other suitable applications. Typically, secondary link signaling can refer to a signal transmitted from one dependent entity (e.g., UE1) to another dependent entity (e.g., UE2) without requiring relaying by a scheduling entity (e.g., UE or BS), even if the scheduling entity may be used for scheduling and / or control purposes. In some examples, licensed spectrum can be used to transmit secondary link signaling (unlike wireless LANs that typically use unlicensed spectrum).

[0069] The UE can operate in various radio resource configurations, including configurations associated with using a dedicated resource set to transmit pilot signals (e.g., Radio Resource Control (RRC) dedicated state, etc.) or configurations associated with using a common resource set to transmit pilot signals (e.g., RRC common state, etc.). When operating in RRC dedicated state, the UE can select the dedicated resource set for transmitting pilot signals to the network. When operating in RRC common state, the UE can select the common resource set for transmitting pilot signals to the network. In either case, the pilot signals transmitted by the UE can be received by one or more network access devices (e.g., AN or DU or portions thereof). Each receiving network access device can be configured to receive and measure pilot signals transmitted on the common resource set, and also to receive and measure pilot signals transmitted on the dedicated resource set allocated to the UE (for these UEs, the network access device is a member of a set of network access devices monitored for the UE). A CU that receives measurement results from one or more network access devices, or from pilot signals sent to it by a network access device, can use the measurement results to identify the serving cell for a UE, or initiate a change to the serving cell for one or more of these UEs.

[0070] Example slot design

[0071] In mobile communication systems conforming to certain wireless communication standards (e.g., Long Term Evolution (LTE) standards), certain techniques can be used to increase the reliability of data transmission. For example, after the base station performs an initial transmission operation for a specific data channel, the receiving receiver attempts to demodulate the data channel. During this process, the receiver performs a Cyclic Redundancy Check (CRC) for the data channel. As a result of the check, if the initial transmission is successfully demodulated, the receiver can send an acknowledgment (ACK) to the base station to confirm successful demodulation. However, if the initial transmission is not successfully demodulated, the receiver can send a non-acknowledgment (NACK) to the base station. The channel through which ACK / NACK are sent is called the response or ACK channel.

[0072] In some cases, under the LTE standard, the ACK channel can comprise two time slots (i.e., one subframe) or 14 symbols, which can be used to send an ACK that may include one or two bits of information. In some cases, the wireless device can perform frequency hopping when sending ACK channel information. Frequency hopping refers to the practice of repeatedly switching frequencies within a frequency band to reduce interference and avoid overlap.

[0073] Under other wireless communication standards (e.g., NR), it is possible to... Figure 8A The uplink structure shown is used to send ACK channel information (and other information). Figure 8AAn example uplink structure with a transmission time interval (TTI) is shown, which includes areas for long uplink burst transmissions. Long uplink bursts can send information such as acknowledgments (ACKs), channel quality indicators (CQIs), or scheduling requests (SRs).

[0074] The area used for long uplink burst transmissions (in) Figure 8A The duration of a "UL long burst" (referred to as a "UL short burst") can vary depending on how many symbols are used in the Physical Downlink Control Channel (PDCCH), gaps, and short uplink bursts (referred to as UL short bursts), such as... Figure 8A As shown. For example, a UL long burst can include multiple time slots (e.g., 4), where the duration of each time slot can vary from 4 to 14 symbols. Figure 8B A downlink structure with a TTI is also shown, which includes the PDCCH, the downlink physical downlink shared channel (PDSCH), gaps, and uplink short bursts. Similar to UL long bursts, the duration of the DL PDSCH can also depend on the number of symbols used by the PDCCH, gaps, and uplink short bursts.

[0075] As described above, a short UL burst can be 1 or 2 symbols, and different methods can be used to transmit the UCI within that duration. For example, according to a "1-symbol" UCI design, frequency division multiplexing (FDM) can be used to transmit 3 or more bits of UCI. For 1 or 2-bit acknowledgment (ACK) or 1-bit scheduling request (SR), a sequence-based design can be used. For example, an SR can be transmitted using a single sequence and on / off keying, and up to 12 users can be multiplexed per RB. For a 1-bit ACK, 2 sequences can be used, and up to 6 users can be multiplexed per RB. For a 2-bit ACK, 4 sequences can be used, and up to 3 users can be multiplexed per RB.

[0076] Example RE mapping rules for UCI payloads on PUSCH

[0077] Several methods can be provided to multiplex simultaneous PUCCH and PUSCH from the same UE. For example, a first method could include transmitting PUCCH and PUSCH on different RBs, such as FDM PUCCH and PUSCH. A second method could include carrying the PUCCH on an assigned PUSCH RB. Both methods can be supported in NR.

[0078] For frequency-priority mapping, the UCI payload on the PUSCH may include UCI resource mapping principles (e.g., around RS) that can be common to PUSCHs with both DFT-s-OFDM and CP-OFDM waveforms. The UCI payload on the PUSCH may also include UL data, which can be rate-matched around the UCI at least for periodic CSI reports configured by RRC and / or aperiodic CSI reports triggered by UL authorization.

[0079] In one or more cases, slot-based scheduling for HARQ-ACK with more than two bits may include rate-matched PUSCH. In some cases, PUSCH may be punctured for slot-based scheduling for HARQ-ACK with a maximum of two bits. In one or more cases, the NR can provide a sufficiently reliable understanding of the HARQ-ACK bits between the gNB and the UE. In some cases, additional considerations regarding channel multiplexing of PUCCH and PUSCH may be taken into account.

[0080] Considerations associated with UCI payloads on the PUSCH can include how to determine HARQ-ACK payload rules. For example, if the PUSCH is punctured by ACKs, the impact on PUSCH decoding performance can be non-negligible with large ACK payload sizes. If rate matching is performed on the PUSCH around the ACKs, the eNB and UE may have different assumptions about the number of ACK bits carried on the PUSCH in the event of a UE false detection of DCI, which may require the eNB to perform blind detection to resolve this ambiguity. Furthermore, as the ACK payload size increases, the number of blind detections that the eNB may need to perform may also increase.

[0081] Example resource allocation for UCI and data reuse on PUSCH

[0082] This disclosure provides various techniques that allow both the network (base station / gNB) and the UE to identify which PUSCH resources are available for transmitting UCI with dynamic payloads.

[0083] As mentioned above, uplink control information (UCI) can be carried via PUSCH. UCI can transmit different types of information, such as ACK / NACK and CSI reports. The CSI report type may also vary, for example, having different types including semi-persistent CSI and aperiodic CSI. In either case, the CSI report can be wideband, partial band, or subband.

[0084] In some cases, the UCI payload can be dynamically changed (e.g., depending on the type and amount of information to be reported). For example, CSI reporting can include Type I and Type II feedback. Type I feedback can include CSI feedback at a standard resolution for a single antenna panel and / or multiple panels. Type II feedback can include higher resolution CSI feedback (e.g., targeting MU-MIMO).

[0085] When UCI and data are jointly reported (multiplexed) on the same PUSCH, the PUSCH is shared between UCI and data. In LTE, the number of UCI bits is fixed and known to the base station, and the base station can allocate the correct resources for both UCI and data.

[0086] As mentioned above, in NR, the UCI payload can be dynamic. This can pose a challenge for base stations to correctly allocate resources to UCI and data. For example, if UCI always takes precedence over data, the base station may not be able to allocate sufficient resources for some UCI (e.g., subband PMI omission) and all data. This can lead to a decrease in data throughput in UL.

[0087] The techniques presented in this paper provide the correct resource allocation to dynamically adjust the maximum supported payload size for UCI (e.g., part of 2CSI) based on the amount of UL data.

[0088] For example, Figure 9 Example operation 900 is shown for a UE to conduct wireless communication to determine resources available for multiplexing UCI and data, according to certain aspects of this disclosure.

[0089] At 902, operation 900 begins by determining the total amount of resources allocated for transmitting both uplink data and uplink control information (UCI) in the Physical Uplink Shared Channel (PUSCH) transmission.

[0090] At 904, the UE determines the size of the supporting payload for transmitting UCI based at least in part on the total number of allocated resources and the number of resources allocated for uplink data.

[0091] At 906, the UE transmits uplink data and UCI in the PUSCH based on the total amount of allocated resources and the determined supported payload size.

[0092] In this way, aspects of this disclosure can be adapted to UCIs with dynamic (and often large) payload sizes. For example, aspects of this disclosure can be used in NR systems where the CSI payload size may be very large (e.g., type IICSI with rank 2 CSI reporting). In such cases, CSI omission rules are supported for determining when to discard certain CSI information. In some cases, if resources on the PUSCH are insufficient for wider-band CSI reporting, only one subband can be reported.

[0093] In order to support such dynamic CSI payload size in this way, various aspects of this disclosure can help prioritize certain types of bits during resource allocation when multiplexing UCI and data.

[0094] According to some solutions, the maximum supported payload size for a portion of 2CSI (referred to as J_max) can be dynamically changed accordingly based on the amount of UL data. In such a case, the UE can determine the maximum supported payload size based on a pre-configured amount or based on the maximum amount of resources available for the CSI payload. If the CSI payload is less than the maximum supported payload size for UCI (e.g., less than J_max), the entire CSI can be transmitted. On the other hand, if the portion of 2CSI is greater than J_max, CSI omission will occur, and the portion of 2CSI will be reduced to less than or equal to J_max.

[0095] In some cases, the UE can determine the maximum supported payload size based on the maximum supported coding rate (Rmax) for UL data. Rmax can be signaled by the network, for example, via higher-layer signaling, semi-static signaling, or lower-layer signaling. For example, Rmax can be determined using the following formula:

[0096] Rmax=min(Rmcs+Δ,R_bound),

[0097] Where Rmcs is the coding rate indicated in the MCS, Δ is the allowable coding rate offset, and R_bound is the upper limit of the coding rate. Δ and R_bound can be configured by higher layers. Rmax can determine the minimum resource allocation for data and therefore can be used to determine the maximum resource allocation for UCI (e.g., CSI, HARQ-ACK / NACK, SR).

[0098] CSI payload (especially for partial 2CSI reports (e.g., damaged portions)) can be calculated based on resource allocations for other UCI portions (ACK / NACK, SR, partial 1CSI), which can be used to further determine the maximum number of payload sizes (J_max) for partial 2CSIs. As an example, if the minimum resources (in REs) for the UL data portion become:

[0099]

[0100] Where Q is the number of bits carried per RE, which depends on the UL MCS configuration. The maximum allocation resource for UCI can be found to be:

[0101] N2 = N0 - N1

[0102] Where N0 is the total number of REs allocated for PUSCH. By subtracting the REs occupied by other UCI sections (e.g., ACK / NACK, RI / CRI / CQI in section 1), the UCI REs for section 2 can be found to be:

[0103] Npart2 = N2 - Npart1 - Nack

[0104] Then, the effective payload J_max can be found to be:

[0105]

[0106] Where Q is the number of bits carried per RE, and Rmcs is the coding rate of PUSCH from DCI signaling.

[0107] In some cases, the minimum resources (e.g., the minimum number of RBs or REs) to be allocated for data can be signaled to the UE. For example, the minimum number of RBs or REs can be signaled via higher-layer signaling, semi-static signaling, or lower-layer signaling. As an example, Downlink Control Information (DCI) signaling can indicate the allocation of RBs for both data and UCI, and can signal parameters configured at a higher layer that determine the minimum portion of RBs to be allocated for UL data, such that:

[0108] min_RB_data = RB_total (allocated via DCI) * alpha

[0109] Here, alpha can be a parameter indicated via higher-layer signaling. Then, the maximum available resources for a portion of 2CSI can be further derived as follows:

[0110] max_RB_UCI=RB_total–min_RB_data,

[0111] max_RE_UCI = max_RB_UCI * Q (modulation order used for UCI)

[0112] max_RE_part2_CSI=max_RE_UCI-RE_ACK–RE_part1_CSI

[0113]

[0114] Typically, the maximum number of REs available for UCI can be derived from the minimum number of REs used for data.

[0115] exist Figure 10 An example of this method is shown. As shown, at 1002, the base station can first allocate total resources (for UCI and data). At 1004, the UE can calculate the maximum payload (J_max) for the partial 2CSI based on the UL data. At 1006, the UE calculates the partial 2CSI and the payload. At 1008, the UE can determine the resource allocation on the PUSCH, for example, in the following order:

[0116] 1. HARQ ACK / NACK

[0117] 2. CSI Part 1

[0118] 3. CSI Part 2, and

[0119] 4. UL data.

[0120] In some cases, UL data resources can be allocated to the UE before a partial 2CSI report. In such cases, the resource allocation order can be changed so that resources for data are allocated before a partial 2CSI report.

[0121] For example, such as Figure 11 As shown, at point 1102, the base station can first allocate total resources for data and UCI. At point 1104, the UE can allocate UL resources, where the order of UCI and data is as follows (in priority order):

[0122] 1. HARQ ACK / NACK

[0123] 2. CSI Part 1

[0124] 3. UL data, and

[0125] 4. CSI Part 2.

[0126] Furthermore, at 1106, the UE can calculate the maximum payload (J_max) for a portion of 2CSI based on resource allocation (after allocating resources for other UCIs and data according to 1104).

[0127] In some cases, each CSI reporting setting can have its own associated partial 2CSI maximum payload. In such cases, each CSI reporting setting can define its own partial 2CSI maximum payload J_max. Again, J_max can be configured at a higher level or predefined based on CSI reporting configuration (e.g., based on the number of ports, Type I, or Type IICSI). If multiple CSI reports are triggered within a single PUSCH reporting time, the following items are summed:

[0128] J_max = sum(J_k)

[0129] It will be used as the maximum payload of the largest part 2, where J_k is the maximum CSI report size configured for the k-th CSI report.

[0130] The methods disclosed herein include one or more steps or actions for implementing the described methods. These method steps and / or actions may be interchanged with each other without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and / or use of a particular step and / or action may be modified without departing from the scope of the claims.

[0131] As used in this article, the phrase “at least one of” in a list of items refers to any combination of those items, including a single member. For example, “at least one of a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination of multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0132] As used herein, the term "determine" encompasses a wide variety of actions. For example, "determine" can include calculation, operation, processing, derivation, investigation, lookup (e.g., searching in a table, database, or other data structure), ascertainment, and so on. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), and so on. Additionally, "determine" can include parsing, selecting, choosing, establishing, and so on.

[0133] The foregoing description is provided to enable any person skilled in the art to implement the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are given the full scope consistent with the written claims, wherein, unless specifically stated otherwise, reference to the singular form of an element is not intended to mean “one and only one,” but rather “one or more.” Unless otherwise expressly stated, the term “some” refers to one or more. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure are expressly incorporated herein by reference and intended to be included by the claims, such structural and functional equivalents being known or to be known by those skilled in the art. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly stated in the claims. No claim element is to be interpreted pursuant to paragraph 6 of 35 U.S.SC § 112 unless the element is expressly stated using the phrase “unit for…” or, in the case of a method claim, using the phrase “step for…”.

[0134] The various operations of the methods described above can be performed by any suitable unit capable of performing the corresponding function. These units can include various hardware and / or software components and / or modules, including but not limited to: circuits, application-specific integrated circuits (ASICs), or processors. Typically, in the presence of the operations shown in the figures, those operations can have corresponding paired units plus functional components with similar numbering. For example, Figure 9 , 10 The various operations shown in 11 can be performed by Figure 4 The various processors shown in the figure execute.

[0135] For example, the units for transmitting and / or receiving may include one or more of the following: a transmit processor 420, a TX MIMO processor 430, a receive processor 438 or an antenna 434 of base station 110, and / or a transmit processor 464, a TX MIMO processor 466, a receive processor 458 or an antenna 452 of user equipment 120. Additionally, the units for generating, multiplexing, and / or applying may include one or more processors, such as a controller / processor 440 of base station 110 and / or a controller / processor 480 of user equipment 120.

[0136] The various illustrative logic blocks, modules, and circuits described in connection with this disclosure can be implemented or executed using a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0137] If implemented in hardware, an example hardware configuration could include a processing system in a wireless node. The processing system could utilize a bus architecture. Depending on the specific application and overall design constraints of the processing system, the bus could include any number of interconnect buses and bridges. The bus could connect various circuits, including a processor, machine-readable media, and a bus interface. In addition, the bus interface could be used to connect a network adapter to the processing system via the bus. The network adapter could be used to implement signal processing functions at the PHY layer. In user terminal 120 (see...) Figure 1 In this case, a user interface (e.g., keypad, display, mouse, joystick, etc.) can also be connected to the bus. The bus can also connect various other circuits such as timing sources, peripherals, voltage regulators, power management circuits, etc., which are well known in the art and therefore will not be described further. The processor can be implemented using one or more general-purpose and / or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuits capable of executing software. Those skilled in the art will recognize how the functions described for the processing system can be optimally implemented based on the specific application and the overall design constraints imposed on the system as a whole.

[0138] If implemented in software, the functionality can be stored or transmitted as one or more instructions or code on or through a computer-readable medium. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted to mean instructions, data, or any combination thereof. Computer-readable media includes both computer storage media and communication media, with communication media encompassing any medium that facilitates the transfer of a computer program from one place to another. The processor may be responsible for managing the bus and general-purpose processing, including executing software modules stored on the machine-readable storage medium. The computer-readable storage medium may be coupled to the processor so that the processor can read information from and write information to the storage medium. Alternatively, the storage medium may be an integral part of the processor. For example, the machine-readable medium may include a transmission line, a carrier wave modulated by data, and / or a separate computer-readable storage medium containing instructions stored thereon, all accessible to the processor via a bus interface. Alternatively or additionally, the machine-readable medium or any portion thereof may be integrated into the processor; for example, this could be a cache and / or a general-purpose register file. For example, examples of machine-readable storage media may include RAM (random access memory), flash memory, ROM (read-only memory), PROM (programmable read-only memory), EPROM (erasable programmable read-only memory), EEPROM (electrically erasable programmable read-only memory), registers, disks, optical disks, hard drives, or any other suitable storage media, or any combination thereof. Machine-readable media may be embodied in computer program products.

[0139] Software modules may include a single instruction or many instructions, and may be distributed across several different code segments, within different programs, and across multiple storage media. Computer-readable media may include multiple software modules. A software module includes instructions that, when executed by a device such as a processor, cause a processing system to perform various functions. A software module may include sending modules and receiving modules. Each software module may reside in a single storage device or be distributed across multiple storage devices. For example, when a triggering event occurs, a software module may be loaded from a hard drive into RAM. During the execution of a software module, the processor may load some of the instructions into a cache to increase access speed. One or more cache lines may then be loaded into a general-purpose register file for execution by the processor. It will be understood that when the functionality of a software module is referred to below, this functionality is implemented by the processor when executing the instructions from that software module.

[0140] Furthermore, any connection is appropriately referred to as 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, digital subscriber line (DSL), or wireless technology (e.g., infrared (IR), radio, and microwave), then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (e.g., infrared, radio, and microwave) is included in the definition of medium. As used herein, disk and disc include compressed optical disc (CD), laser disc, optical disc, digital versatile optical disc (DVD), floppy disk, and... Optical discs, where magnetic disks typically copy data magnetically, use lasers to optically copy data. Therefore, in some aspects, computer-readable media can include non-transitory computer-readable media (e.g., tangible media). In other aspects, computer-readable media can include transient computer-readable media (e.g., signals). Combinations of the above should also be included within the scope of computer-readable media.

[0141] Therefore, certain aspects may include a computer program product for performing the operations given herein. For example, such a computer program product may include a computer-readable medium having instructions stored (and / or encoded thereon) thereon, which can be executed by one or more processors to perform the operations described herein.

[0142] Furthermore, it should be understood that modules and / or other suitable units for performing the methods and techniques described herein can be downloaded and / or otherwise obtained by the user terminal and / or base station, where applicable. For example, such a device can be coupled to a server to facilitate the transmission of units for performing the methods described herein. Alternatively, the various methods described herein can be provided via storage units (e.g., RAM, ROM, physical storage media such as compressed optical discs (CDs) or floppy disks, etc.) so that the user terminal and / or base station can access the various methods when the storage units are coupled to or provided to the device. Furthermore, any other suitable techniques for providing the methods and techniques described herein to the device can be used.

[0143] It should be understood that the claims are not limited to the precise configurations and components shown above. Various modifications, alterations, and variations may be made in the arrangement, operation, and details of the methods and apparatus described above without departing from the scope of the claims.

Claims

1. A method for wireless communication by a user equipment (UE), comprising: Determine the total amount of resources allocated for transmitting both uplink data and uplink control information (UCI) in the Physical Uplink Shared Channel (PUSCH) transmission, wherein the UCI includes part 1 Channel State Information (CSI) and part 2 CSI. The supporting payload size for transmitting the portion of 2CSI is determined at least in part based on the total number of allocated resources and the number of resources allocated for the uplink data, wherein the supporting payload size for transmitting the portion of 2CSI is determined by multiplying a signaled parameter alpha by the total number of allocated resources; and The uplink data and the UCI are transmitted in the PUSCH based on the supporting payload size used to transmit the portion 2CSI.

2. The method according to claim 1, wherein, The UCI includes types of CSIs with dynamic payload sizes.

3. The method according to claim 1, wherein, The supported payload size used to transmit the portion 2CSI is determined based on the payload size of the uplink data.

4. The method according to claim 1, wherein, The amount of resources allocated for the uplink data is transmitted via higher-layer signaling, semi-static signaling, or lower-layer signaling.

5. The method according to claim 1, wherein, The size of the supporting payload used to transmit the portion 2CSI is determined based on the number of resource blocks (RBs) or resource elements (REs) allocated for the uplink data.

6. The method according to claim 5, wherein, Determining the size of the supporting payload used to transmit the portion 2CSI includes: The number of REs or RBs available for transmitting the portion 2CSI is determined by subtracting the number of RBs or REs allocated for the uplink data from the number of REs or RBs allocated for the PUSCH; and The number of partial 2CSI bits that can be transmitted in the PUSCH is determined based on the number of REs or RBs available for transmitting the partial 2CSI and the encoding rate of the PUSCH.

7. The method according to claim 1, wherein, When the size of the UCI to be sent exceeds the determined supported payload size, a portion of the UCI is discarded.

8. The method according to claim 1, wherein, The supporting payload size used to transmit the portion 2CSI is determined by allocating PUSCH resources to the uplink data before allocating PUSCH resources for UCI.

9. The method according to claim 1, wherein: The UCI includes CSIs reported according to at least one of a plurality of CSI reporting settings, wherein each CSI reporting setting is associated with a corresponding maximum payload.

10. The method according to claim 9, wherein, If multiple CSI reports are triggered in a single PUSCH report, the maximum payload size used to send the UCI is determined based on the sum of the corresponding maximum payloads associated with each of the triggered CSI reports.

11. The method according to claim 1, wherein, The size of the supporting payload used to send the portion 2CSI is determined at least in part based on the resource elements assigned to the portion 1CSI.

12. An apparatus for wireless communication by a user equipment (UE), comprising: The unit is used to determine the total number of resources allocated for transmitting both uplink data and uplink control information (UCI) in a Physical Uplink Shared Channel (PUSCH) transmission, wherein the UCI includes a portion 1 Channel State Information (CSI) and a portion 2 CSI. A unit for determining the supporting payload size for transmitting the portion of 2CSI based at least in part on the total number of allocated resources and the number of resources allocated for the uplink data, wherein the supporting payload size for transmitting the portion of 2CSI is determined by multiplying a signaled parameter alpha by the total number of allocated resources; and A unit for transmitting the uplink data and the UCI in the PUSCH based on the supporting payload size for transmitting the portion 2CSI.

13. The apparatus according to claim 12, wherein, The UCI includes types of CSIs with dynamic payload sizes.

14. The apparatus according to claim 12, wherein, The supported payload size used to transmit the portion 2CSI is determined based on the payload size of the uplink data.

15. The apparatus according to claim 12, wherein, The amount of resources allocated for the uplink data is transmitted via higher-layer signaling, semi-static signaling, or lower-layer signaling.

16. The apparatus according to claim 12, wherein, The size of the supporting payload used to transmit the portion 2CSI is determined based on the number of resource blocks (RBs) or resource elements (REs) allocated for the uplink data.

17. The apparatus according to claim 16, wherein, The unit for determining the supported payload size for transmitting the portion 2CSI includes: A unit for determining the number of REs or RBs available for transmitting the partial 2CSI by subtracting the number of RBs or REs allocated for the uplink data from the number of REs or RBs allocated for the PUSCH; and A unit for determining the number of partial 2CSI bits that can be transmitted in the PUSCH based on the number of REs or RBs available for transmitting the partial 2CSI and the encoding rate of the PUSCH.

18. The apparatus according to claim 12, wherein, When the size of the UCI to be sent exceeds the determined supported payload size, a portion of the UCI is discarded.

19. The apparatus according to claim 12, wherein, The supporting payload size used to transmit the partial 2CSI is determined by allocating PUSCH resources to uplink data before allocating PUSCH resources for the partial 2CSI.

20. The apparatus according to claim 12, wherein: The UCI includes CSIs reported according to at least one of a plurality of CSI reporting settings, wherein each CSI reporting setting is associated with a corresponding maximum payload.

21. The apparatus according to claim 20, wherein, If multiple CSI reports are triggered in a single PUSCH report, the maximum payload size used to send the UCI is determined based on the sum of the corresponding maximum payloads associated with each of the triggered CSI reports.

22. The apparatus according to claim 12, wherein, The size of the supporting payload used to send the portion 2CSI is determined at least in part based on the resource elements assigned to the portion 1CSI.

23. An apparatus for wireless communication by a user equipment (UE), comprising: At least one processor is configured to: determine the total amount of resources allocated for transmitting both uplink data and uplink control information (UCI) in a Physical Uplink Shared Channel (PUSCH) transmission, wherein the UCI includes a portion of Channel State Information (CSI) and a portion of Channel State Information (CSI); and determine, at least in part, a supporting payload size for transmitting the portion of CSI based on the total amount of allocated resources and the amount of resources allocated for the uplink data, wherein the supporting payload size for transmitting the portion of CSI is determined by multiplying a signaled parameter alpha by the total amount of allocated resources; and The transmitter is configured to transmit uplink data and the UCI in the PUSCH based on the supported payload size for transmitting the portion 2CSI.

24. The apparatus according to claim 23, wherein, The UCI includes types of CSIs with dynamic payload sizes.

25. The apparatus according to claim 23, wherein, The supported payload size used to transmit the portion 2CSI is determined based on the payload size of the uplink data.

26. The apparatus according to claim 23, wherein, The amount of resources allocated for the uplink data is transmitted via higher-layer signaling, semi-static signaling, or lower-layer signaling.

27. The apparatus according to claim 23, wherein, The size of the supporting payload used to transmit the portion 2CSI is determined based on the number of resource blocks (RBs) or resource elements (REs) allocated for the uplink data.

28. The apparatus according to claim 27, wherein, The at least one processor is configured to determine the supported payload size for transmitting the portion 2CSI, including being configured to: The number of REs or RBs available for transmitting the portion 2CSI is determined by subtracting the number of RBs or REs allocated for the uplink data from the number of REs or RBs allocated for the PUSCH. as well as The number of partial 2CSI bits that can be transmitted in the PUSCH is determined based on the number of REs or RBs available for transmitting the partial 2CSI and the encoding rate of the PUSCH.

29. The apparatus according to claim 23, wherein, The at least one processor is further configured to discard a portion of the UCI when the size of the UCI to be transmitted exceeds the determined supported payload size.

30. The apparatus according to claim 23, wherein, The supporting payload size used to transmit the partial 2CSI is determined by allocating PUSCH resources to uplink data before allocating PUSCH resources for the partial 2CSI.

31. The apparatus according to claim 23, wherein: The UCI includes CSIs reported according to at least one of a plurality of CSI reporting settings, wherein each CSI reporting setting is associated with a corresponding maximum payload.

32. The apparatus according to claim 31, wherein, If multiple CSI reports are triggered in a single PUSCH report, the maximum payload size used to send the UCI is determined based on the sum of the corresponding maximum payloads associated with each of the triggered CSI reports.

33. The apparatus according to claim 23, wherein, The size of the supporting payload used to send the portion 2CSI is determined at least in part based on the resource elements assigned to the portion 1CSI.

34. A non-transitory computer-readable medium having instructions stored thereon, which, when executed by a processor, are used to perform the following operations: Determine the total amount of resources allocated for transmitting both uplink data and uplink control information (UCI) in the Physical Uplink Shared Channel (PUSCH) transmission, where, The UCI includes part 1 Channel State Information (CSI) and part 2CSI; The supporting payload size for transmitting the portion of 2CSI is determined at least in part based on the total number of allocated resources and the number of resources allocated for the uplink data, wherein the supporting payload size for transmitting the portion of 2CSI is determined by multiplying a signaled parameter alpha by the total number of allocated resources; and The uplink data and the UCI are transmitted in the PUSCH based on the supporting payload size used to transmit the portion 2CSI.

Images