Uplink control information reporting techniques

Abstract

The present disclosure relates generally to uplink control information (UCI) reporting without a physical uplink control channel (PUCCH) resource. In some implementations, a user equipment (UE) receives control signaling that configures one or more parameters for UCI reporting on a physical uplink shared channel (PUSCH) resource. The UE can determine a mapping between at least one downlink component carrier (CC) and at least one uplink CC in accordance with the one or more parameters configured for UCI reporting on the PUSCH resource. Accordingly, the UE can transmit UCI via one or more PUSCH resources associated with the at least one uplink CC based at least on the determined mapping.

Description

Technical Field

[0001] This disclosure relates in general to wireless communications, and more specifically to uplink control information (UCI) reporting techniques. Background Technology

[0002] Wireless communication networks provide an integrated communication platform and telecommunications services to wireless user equipment. Example telecommunications services include telephone, data (e.g., voice, audio, video), messaging, and / or other services. Wireless communication networks have wireless access nodes that use one or more wireless network protocols, such as those described in various telecommunications standards issued by the European Telecommunications Standards Institute (ETSI) 3GPP program, to exchange wireless signals with wireless user equipment. Wireless communication networks use techniques such as Orthogonal Frequency Division Multiple Access (OFDMA), Multiple-Input Multiple-Output (MIMO), Advanced Channel Decoding, Massive MIMO, beamforming, and / or other features to facilitate mobile broadband services. Summary of the Invention

[0003] One aspect of this disclosure relates to a method comprising: receiving control signaling configuring one or more parameters for uplink control information (UCI) reporting on physical uplink shared channel (PUSCH) resources; determining a mapping between at least one downlink component carrier (CC) and at least one uplink CC based on the one or more parameters configured for UCI reporting on the PUSCH resources; and transmitting the UCI via one or more PUSCH resources associated with the at least one uplink CC based on the determined mapping.

[0004] In some specific implementations, the UCI includes at least one of periodic channel state information (P-CSI) reports, aperiodic CSI (A-CSI) reports, event-triggered CSI reports, hybrid automatic repeat request (HARQ) acknowledgment (ACK) feedback, or scheduling request (SR).

[0005] In some implementations, the control signaling configures event-triggered CSI reporting on one or more PUSCH resources.

[0006] In some implementations, the method further includes sending capability signaling indicating at least one of the following: (i) the number of valid uplink CCs that can be reported for P-CSI on PUSCH resources per time slot; (ii) the maximum number of valid uplink CCs reported for P-CSI on PUSCH resources; or (iii) the number of downlink CCs that can be measured and reported on a single uplink CC.

[0007] In some specific implementations, this capability signaling indicates that more than one downlink CC can be measured and reported on a single uplink CC.

[0008] In some specific implementations, this control signaling configuration CSI-ReportConfigId A set of values, each associated with a different downlink CC.

[0009] In some specific implementations, each CSI-ReportConfigId The value is associated with at most one valid periodic CSI report.

[0010] In some implementations, this control signaling indicates the configured-grant (CG)PUSCH resource to be used for P-CSI reporting.

[0011] In some specific implementations, the identifier or configuration of the CG PUSCH resource is determined by... ServingCellConfig Information elements (IE) CSI-MeasConfig Fields CSI-MeasConfig Within the field CSI-ReportConfig subfield, or ServingCellConfig In IE uplinkConfig At least one of the fields must be provided.

[0012] In some implementations, this parameter may include a list of CG PUSCH identifiers or configurations for P-CSI reporting configured for each serving cell.

[0013] In some implementations, a list of CG PUSCH identifiers or configurations is provided for each uplink bandwidth portion (BWP).

[0014] In some specific implementations, a single CG PUSCH resource is configured for each serving cell for a specific uplink BWP, and the CG PUSCH resource is activated when the specific uplink BWP is active.

[0015] In some implementations, the method also includes multiplexing the accumulated HARQ-ACK bit on one or more PUSCH resources according to the control signaling.

[0016] In some implementations, this control signaling includes downlink control information (DCI) or radio resource control (RRC) signaling.

[0017] In some specific implementations, these accumulated HARQ-ACK bits are multiplexed with uplink data.

[0018] In some specific implementations, determining the mapping includes receiving a mapping between a downlink CC and an uplink CC via the control signaling, a mapping between more than one downlink CC and an uplink CC, a mapping between one downlink CC and more than one uplink CC, or a mapping between more than one downlink CC and more than one uplink CC.

[0019] In some specific implementations, HARQ-ACK feedback is not reported for the Physical Downlink Shared Channel (PDSCH) that is mapped to more than one uplink CC.

[0020] In some specific implementations, HARQ-ACK feedback is reported for PDSCHs scheduled on downlink CCs that are mapped to more than one uplink CC.

[0021] In some implementations, the control signaling includes RRC messages, Media Access Control (MAC) control elements (CE), or DCIs that indicate the association between the downlink CC and the uplink CC.

[0022] In some implementations, the fields in the DCI instruct the PUSCH to send a HARQ-ACK feedback carrying one or more uplink CCs in the uplink CCs.

[0023] In some specific implementations, the DCI scheduler may or may not have PUSCH transmissions with uplink data.

[0024] In some specific implementations, the DCI schedules the PDSCH transmission on the downlink CC.

[0025] In some implementations, the PUSCH transmission is scheduled on an uplink CC associated with the downlink CC on which the PDSCH transmission is received.

[0026] In some specific implementations, this control signaling configures one or more PUSCH resources for UCI transmissions that do not have uplink data.

[0027] In some specific implementations, the method further includes: in response to determining that a flag in the DCI is set to one, multiplexing the HARQ-ACK bit used for all downlink HARQ procedures on the downlink CC mapped to the uplink CC on which the PUSCH is scheduled to be transmitted.

[0028] In some implementations, the DCI includes a downlink assignment indicator (DAI) and a K1 offset value indicating the number of bits to be reported in the uplink timeslot.

[0029] In some specific implementations, the DAI spans all downlink CCs corresponding to the uplink CCs that are scheduled to be sent by the PUSCH on it.

[0030] In some specific implementations, the DCI instruction is to be used for sending PUSCH resources for HARQ-ACK feedback sent in response to PDSCH, and the indicated PUSCH resources do not carry uplink data.

[0031] In some specific implementations, this control signaling configures one or more PUSCH resources for each uplink CC to carry SRs that do not contain uplink data.

[0032] In some specific implementations, the one or more PUSCH resources do not overlap with PUSCH resources that carry uplink data across any uplink CC.

[0033] In some specific implementations, the method also includes multiplexing the HARQ-ACK feedback with the SR on a shared PUSCH resource when both the SR and HARQ-ACK feedback are scheduled on the same uplink CC.

[0034] In some implementations, the method also includes configuring cell-specific PUSCH resources for each uplink CC to carry HARQ-ACK feedback for Msg4, wherein the cell-specific PUSCH resources are released when one or more UE-specific PUSCH resources are configured.

[0035] In some specific implementations, the cell-specific PUSCH resources do not overlap with the PUSCH resources specific to one or more UEs.

[0036] In some implementations, the method further includes: identifying overlaps between multiple PUSCH transmissions scheduled on the uplink CC; and resolving the overlap by prioritizing Dynamically Granted (DG) PUSCH transmissions over CG PUSCH transmissions and prioritizing CG PUSCH transmissions over P-CSI reports.

[0037] In some specific implementations, PUSCH resources configured for UCI transmission on a specific uplink CC do not overlap with PUSCH resources carrying data scheduled by DCI.

[0038] In some implementations, a single PUSCH carrying the CSI is allowed to be sent across all uplink CCs.

[0039] In some specific implementations, A-CSI reports with data take precedence over A-CSI reports without data, and A-CSI reports with or without data take precedence over P-CSI reports, and CSI transmissions associated with a lower serving cell index take precedence over CSI reports with a higher serving cell index.

[0040] In some implementations, the method also includes concurrently sending overlapping PUSCH transmissions across different uplink CCs without multiplexing the UCI across these uplink CCs.

[0041] In some implementations, the method further includes determining the priority of the PUSCH resource based on at least one of the following: (i) the priority of the uplink data carried by the PUSCH resource; or (ii) the priority of the HARQ-ACK feedback carried by the PUSCH resource, wherein the priority of the HARQ-ACK feedback corresponds to the priority of the uplink data.

[0042] In some implementations, the method also includes discarding lower-priority PUSCH transmissions when the sum of transmission power across multiple serving cells exceeds a threshold.

[0043] In some implementations, the method also includes performing measurements on one or more resources based on an event-driven CSI reporting configuration, wherein the one or more resources include periodic or semi-persistent CSI reference signal (CSI-RS) resources or synchronization signal blocks (SSBs).

[0044] In some implementations, this control signaling is configured to trigger timers and one or more thresholds for event-driven CSI reporting.

[0045] In some implementations, the timer is reset after an event-driven CSI report is sent.

[0046] In some implementations, the method also includes sending a triggered event-driven CSI report in the MAC-CE, which indicates which CSI quantities are included in the CSI report.

[0047] In some specific implementations, a separate MAC-CE format is configured for each CSI report volume.

[0048] In some implementations, the control signaling that receives one or more parameters configured for UCI reporting on PUSCH resources includes receiving network indications for one or more parameters to be used for overlap resolution and resource selection.

[0049] In some specific implementations, the control signaling further indicates the set of UCI types to be multiplexed on the one or more PUSCH resources selected for transmitting the UCI.

[0050] Another aspect of this disclosure relates to an apparatus comprising: one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform any of the aforementioned operations.

[0051] Another aspect of this disclosure relates to a baseband processor configured to perform any of the operations described above.

[0052] Another aspect of this disclosure relates to a method comprising: sending control signaling configuring one or more parameters for UCI reporting on PUSCH resources; determining a mapping between at least one downlink CC and at least one uplink CC based on the one or more parameters configured for UCI reporting on PUSCH resources; and receiving UCIs via one or more PUSCH resources associated with the at least one uplink CC based on the determined mapping.

[0053] In some implementations, the UCI includes at least one of the following: P-CSI report, A-CSI report, event-triggered CSI report, HARQ-ACK feedback, or SR.

[0054] In some implementations, the control signaling configures event-triggered CSI reporting on one or more PUSCH resources.

[0055] In some implementations, the method further includes receive capability signaling indicating at least one of the following: (i) the number of valid uplink CCs that can be reported for P-CSI on PUSCH resources per time slot; (ii) the maximum number of valid uplink CCs reported for P-CSI on PUSCH resources; or (iii) the number of downlink CCs that can be measured and reported on a single uplink CC.

[0056] In some specific implementations, this capability signaling indicates that more than one downlink CC can be measured and reported on a single uplink CC.

[0057] In some specific implementations, this control signaling configuration CSI-ReportConfigId A set of values, each associated with a different downlink CC.

[0058] In some specific implementations, each CSI-ReportConfigId The value is associated with at most one valid periodic CSI report.

[0059] In some implementations, this control signaling directs the use of CG PUSCH resources for P-CSI reporting.

[0060] In some specific implementations, the identifier or configuration of the CG PUSCH resource is determined by... ServingCellConfig IE CSI-MeasConfig Fields CSI-MeasConfig Within the field CSI-ReportConfig subfield or ServingCellConfig In IE uplinkConfig At least one of the fields must be provided.

[0061] In some implementations, this parameter may include a list of CG PUSCH identifiers or configurations for P-CSI reporting configured for each serving cell.

[0062] In some specific implementations, a list of CG PUSCH identifiers or configurations is provided for each uplink BWP.

[0063] In some specific implementations, a single CG PUSCH resource is configured for each serving cell for a specific uplink BWP, and the CG PUSCH resource is activated when the specific uplink BWP is active.

[0064] In some implementations, the method also includes receiving accumulated HARQ-ACK bits multiplexed on the one or more PUSCH resources according to the control signaling.

[0065] In some specific implementations, this control signaling includes DCI or RRC signaling.

[0066] In some specific implementations, these accumulated HARQ-ACK bits are multiplexed with uplink data.

[0067] In some specific implementations, determining the mapping includes receiving a mapping between a downlink CC and an uplink CC via the control signaling, a mapping between more than one downlink CC and an uplink CC, a mapping between one downlink CC and more than one uplink CC, or a mapping between more than one downlink CC and more than one uplink CC.

[0068] In some specific implementations, HARQ-ACK feedback is not reported for PDSCH on downlink CCs that are mapped to more than one uplink CC.

[0069] In some specific implementations, HARQ-ACK feedback is reported for PDSCHs scheduled on downlink CCs that are mapped to more than one uplink CC.

[0070] In some implementations, the control signaling includes RRC messages, MAC-CE, or DCI that indicate the association between the downlink CC and the uplink CC.

[0071] In some implementations, the fields in the DCI instruct the PUSCH to send a HARQ-ACK feedback carrying one or more uplink CCs in the uplink CCs.

[0072] In some specific implementations, the DCI scheduler may or may not have PUSCH transmissions with uplink data.

[0073] In some specific implementations, the DCI schedules the PDSCH transmission on the downlink CC.

[0074] In some implementations, the PUSCH transmission is scheduled on an uplink CC associated with the downlink CC on which the PDSCH transmission is received.

[0075] In some specific implementations, this control signaling configures one or more PUSCH resources for UCI transmissions that do not have uplink data.

[0076] In some implementations, the DCI includes the DAI and a K1 offset value indicating the number of bits to be reported in the uplink timeslot.

[0077] In some specific implementations, the DAI spans all downlink CCs corresponding to the uplink CCs that are scheduled to be sent by the PUSCH on it.

[0078] In some specific implementations, the DCI instruction is to be used for sending PUSCH resources for HARQ-ACK feedback sent in response to PDSCH, and the indicated PUSCH resources do not carry uplink data.

[0079] In some specific implementations, this control signaling configures one or more PUSCH resources for each uplink CC to carry SRs that do not contain uplink data.

[0080] In some specific implementations, the one or more PUSCH resources do not overlap with PUSCH resources that carry uplink data across any uplink CC.

[0081] In some implementations, the method also includes configuring cell-specific PUSCH resources for each uplink CC to carry HARQ-ACK feedback for Msg4, wherein the cell-specific PUSCH resources are released when one or more UE-specific PUSCH resources are configured.

[0082] In some implementations, cell-specific PUSCH resources do not overlap with UE-specific PUSCH resources. In some implementations, PUSCH resources configured for UCI transmission on a specific uplink CC do not overlap with PUSCH resources carrying data scheduled by DCI.

[0083] In some implementations, a single PUSCH carrying the CSI is allowed to be sent across all uplink CCs.

[0084] In some specific implementations, A-CSI reports with data take precedence over A-CSI reports without data, and A-CSI reports with or without data take precedence over P-CSI reports, and CSI transmissions associated with a lower serving cell index take precedence over CSI reports with a higher serving cell index.

[0085] In some implementations, the method also includes concurrently receiving overlapping PUSCH transmissions across different uplink CCs, wherein the UCI is not multiplexed across these uplink CCs.

[0086] In some implementations, the method further includes determining the priority of the PUSCH resource based on at least one of the following: (i) the priority of the uplink data carried by the PUSCH resource; or (ii) the priority of the HARQ-ACK feedback carried by the PUSCH resource, wherein the priority of the HARQ-ACK feedback corresponds to the priority of the uplink data.

[0087] In some implementations, this control signaling is configured to trigger timers and one or more thresholds for event-driven CSI reporting.

[0088] In some implementations, the timer is reset after an event-driven CSI report is sent.

[0089] In some implementations, the method also includes receiving a triggered event-driven CSI report in the MAC-CE, which indicates which CSI quantities are included in the CSI report.

[0090] In some specific implementations, a separate MAC-CE format is configured for each CSI report volume.

[0091] In some implementations, the control signaling that sends the one or more parameters configured for UCI reporting on PUSCH resources includes sending network indications for the one or more parameters to be used for overlap resolution and resource selection.

[0092] In some specific implementations, the control signaling further indicates the set of UCI types to be multiplexed on the one or more PUSCH resources selected for transmitting the UCI.

[0093] Another aspect of this disclosure relates to an apparatus comprising: one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform any of the aforementioned operations.

[0094] Another aspect of this disclosure relates to a baseband processor configured to perform any of the operations described above.

[0095] Details of one or more embodiments of these systems and methods are set forth in the following figures and description. Other features, objects, and advantages of these systems and methods will be apparent from the specification, figures, and claims. Attached Figure Description

[0096] Figure 1 Examples of wireless networks based on some specific implementations are illustrated.

[0097] Figure 2 Example resource diagrams based on some specific implementations are shown.

[0098] Figure 3 Example signaling diagrams based on some specific implementations are shown.

[0099] Figure 4 A flowchart illustrating an example method for UCI transmission without a PUCCH, based on some specific implementations, is provided.

[0100] Figure 5 A flowchart illustrating an example method for UCI reception without a PUCCH, based on some specific implementations, is shown.

[0101] Figure 6 Example UEs based on some specific implementations are shown.

[0102] Figure 7 Example access nodes are shown according to some specific implementations. Detailed Implementation

[0103] In 3GPP 5G New Radio (NR) systems, uplink control information (UCI) such as Channel State Information (CSI), Hybrid Automatic Repeat Request (HARQ) Acknowledgment (HARQ-ACK) feedback, and Scheduling Request (SR) are carried on the Physical Uplink Control Channel (PUCCH). Determining which PUCCH resource to use and whether / how to multiplex that PUCCH with the Physical Uplink Shared Channel (PUSCH) is a multi-stage process that depends on factors such as UCI type, PUCCH resource overlap, PUSCH resource overlap, and other rules. For example, a User Equipment (UE) might be configured to discard CSI PUCCH transmissions that overlap with CSI PUSCH transmissions, multiplex PUCCH HARQ-ACK transmissions with overlapping PUSCH transmissions, or discard SR PUCCHs that overlap with data PUSCHs, and so on.

[0104] In existing UCI transmission schemes, the process of selecting time-frequency resources (referred to as containers) for each UCI type can be somewhat complex. The UE typically considers multiple candidate PUCCH resources, applies type-specific multiplexing or dropping rules, compares them with PUSCH timing, and applies additional rules to select the final candidate. In some cases, the UE selects the UCI container based on the mapping between uplink component carriers (CCs) and downlink CCs. Because the network can dynamically associate downlink CCs with uplink CCs, the UE may unintentionally select an incorrect container if it misses dynamic indications from the network. This can lead to signaling overhead, retransmissions, wasted power, and lower reliability.

[0105] This disclosure describes a technique for simplifying the UCI resource selection process by carrying all UCIs at the same PUSCH timing, which can also carry uplink data. In some examples, in the case of... CSI-MeasConfig or uplinkConfig The configured PUSCH (CG-PUSCH) resources are authorized to carry periodic CSI (P-CSI) and event-triggered CSI reporting. The UE can signal via Radio Resource Control (RRC) capability information how many uplink CCs per time slot can support P-CSI and how many downlink CCs can be reported on each uplink CC. For HARQ-ACK, the network can explicitly instruct the UE to reuse the PUSCH resources with accumulated ACK bits. This instruction can be provided via Downlink Control Information (DCI) or RRC signaling. For SR, the UE can use dedicated (e.g., special) PUSCH resources configured per cell instead of PUCCH. This helps resolve ambiguity on the UE side.

[0106] As an example, a UE configured with three downlink CCs mapped to one uplink CC can receive ( CSI- MeasConfig The CG-PUSCH configuration specifies the timing of one or more uplink CCs and / or PUSCHs for periodic CSI reporting. When a periodic report is triggered, the UE only transmits on that specific PUSCH without evaluating overlapping PUCCH resources or other PUSCH candidates. Similarly, if the network schedules a Physical Downlink Shared Channel (PDSCH) on CC2 and transmits an uplink DCI with a "one-time" flag in the same time slot, the UE can multiplex all pending HARQ-ACK bits for CC2 onto the PUSCH indicated by that uplink DCI without additional selection logic. Since each UCI container is explicitly signaled, the UE no longer needs to perform complex overlap resolution. This reduces the chance of UE-network misalignment, lowers UE processing overhead, and simplifies the UCI transmission process.

[0107] Carrying UCI on PUSCH resources allows the network to reuse existing uplink shared channel mechanisms, eliminating the need for a separate 3GPP 6G (6G) PUCCH design. Providing explicit PUSCH indication also eliminates ambiguity and ensures that the UE and network agree on the same resources, which improves communication reliability. Reporting UCI on PUSCH resources allows the UE to take advantage of the high throughput and flexible PUSCH framework of 6G, and eliminates the need for a separate 6G PUCCH framework. Additionally, UE capability signaling with supported CC mappings helps the network avoid unsupported multi-carrier reporting configurations, which improves network robustness.

[0108] Figure 1 An example wireless network 100 according to some specific implementation is illustrated. The wireless network 100 includes a UE 102 and a base station 104 connected via one or more channels 106A, 106B across an air interface 108. The UE 102 and the base station 104 communicate using a system that supports control for managing the UE 102's access to the network via the base station 104.

[0109] In some implementations, wireless network 100 is, for example, a standalone (SA) network incorporating fifth-generation (5G) new radio (NR). In other implementations, wireless network 100 is a non-standalone (NSA) network incorporating Long Term Evolution (LTE) and 5G NR. In these implementations, wireless network 100 may be an Evolved Universal Terrestrial Radio Access (E-UTRA) NR Dual Connectivity (EN-DC) network or an NR-EUTRA Dual Connectivity (NE-DC) network. Furthermore, it is possible to implement wireless networks using one or more other types of communication standards, including future 3GPP systems (e.g., sixth generation (6G)), IEEE 802.11 technologies, etc. While this document may use terminology generally associated with 5G NR to describe aspects, the aspects of this disclosure are applicable to other systems, such as systems beyond 5G (e.g., 6G).

[0110] In wireless network 100, UE 102 and any other UE in the system may be, for example, a laptop computer, smartphone, tablet computer, machine-type device (such as a smart meter or dedicated device for healthcare), intelligent transportation system, or any other wireless device. In network 100, base station 104 provides UE 102 with network connectivity to a wider network (not shown). This UE 102 connectivity is provided via air interface 108 within the base station service area provided by base station 104. In some implementations, this wider network may be a wide area network operated by a cellular network provider, or it may be the Internet. Each base station service area associated with base station 104 is supported by one or more antennas integrated with base station 104. The service area may be divided into several sectors associated with one or more specific antennas. Such sectors may be physically associated with one or more fixed antennas, or may be assigned to a physical area having one or more tunable antennas or antenna configurations that can be adjusted during beamforming to direct signals to a specific sector.

[0111] UE 102 includes control circuitry 110 coupled to transmitting circuitry 112 and receiving circuitry 114. Transmitting circuitry 112 and receiving circuitry 114 may each be coupled to one or more antennas. Control circuitry 110 may include dedicated circuitry, baseband circuitry, or any combination thereof. Transmitting circuitry 112 and receiving circuitry 114 may be adapted to transmit and receive data respectively, and may include radio frequency (RF) circuitry and / or front-end module (FEM) circuitry.

[0112] In various specific implementations, aspects of the transmitting circuit 112, the receiving circuit 114, and / or the control circuit 110 can be integrated in various ways to implement the operations described herein. The control circuit 110 can be adapted to or configured to perform various operations, such as the various UE-related operations described elsewhere in this disclosure. For example, the control circuit 110 can determine which PUSCH resources should be used for UCI transmission based on a report configuration provided by the base station 104.

[0113] Transmitting circuit 112 can perform various operations described herein. For example, transmitting circuit 112 can transmit UCI via a PUSCH resource set according to a report configuration. Additionally, transmitting circuit 112 can use multiplexed uplink physical channels for transmission. The uplink physical channels can be multiplexed, for example, according to time division multiplexing (TDM) or frequency division multiplexing (FDM), and in some specific implementations, carrier aggregation. Transmitting circuit 112 can be configured to receive block data from control circuit 110 for transmission on air interface 108.

[0114] Receiver circuit 114 can perform various operations described herein. For example, receiver circuit 114 can receive control signaling configuring one or more UCI reporting parameters. Additionally, receiver circuit 114 can receive multiplexed downlink physical channels from air interface 108 and relay these physical channels to control circuit 110. The downlink physical channels can be multiplexed, for example, according to TDM or FDM, such as with carrier aggregation. Transmitter circuit 112 and receiver circuit 114 can respectively transmit and receive structured control data and content data (e.g., messages, images, video) within data blocks carried by the physical channels.

[0115] Figure 1 Base station 104 is also illustrated. In some implementations, base station 104 may be a 5G radio access network (RAN), a next-generation RAN, an E-UTRAN, a non-terrestrial cell, or a traditional RAN (such as UTRAN). As used herein, the term "5G RAN" and the like may refer to base station 104 operating in an NR wireless network 100, and the term "E-UTRAN" and the like may refer to base station 104 operating in an LTE wireless network 100. UE 102 utilizes connections (or channels) 106A and 106B, each connection including a physical communication interface or layer.

[0116] The base station 104 circuitry may include control circuitry 116 coupled (directly or indirectly) to transmitting circuitry 118 and / or receiving circuitry 120. Transmitting circuitry 118 and receiving circuitry 120 may each be coupled (directly or indirectly) to one or more antennas, which may be used for communication via air interface 108. Transmitting circuitry 118 and receiving circuitry 120 may be adapted to transmit and receive data, respectively, to any UE connected to base station 104. Receiving circuitry 120 may receive uplink physical channel transmissions from one or more UEs, including UE 102.

[0117] exist Figure 1 In this embodiment, one or more channels 106A, 106B are exemplified as air interfaces for implementing communication coupling and may conform to cellular communication protocols such as LTE, LTE-A (LTE-Advanced), LTE-based Unlicensed Spectrum Access (LTE-U), NR, NR-based Unlicensed Spectrum Access (NR-U), and / or any other communication protocol. In some specific implementations, UE 102 may directly exchange communication data via the ProSe interface. The ProSe interface may alternatively be referred to as a sidelink (SL) interface and may include one or more logical channels, including but not limited to the Physical Sidelink Control Channel (PSCCH), Physical Sidelink Discovery Channel (PSDCH), and Physical Sidelink Broadcast Channel (PSBCH).

[0118] In 5G, for CSI, there are two UCI reporting procedures on the PUCCH, such as persistent and semi-persistent CSI on the PUCCH. If PUCCH resources overlap in time, the multiplexing / dropping procedures used to resolve the overlap can be complex. Similarly, there are two reports (semi-persistent and aperiodic) on the PUSCH. If a PUCCH with CSI overlaps with a PUSCH with CSI, the PUCCH with CSI is discarded. If two PUSCHs with CSI overlap, the semi-persistent PUSCH is discarded. For HARQ-ACK, PUCCH resources are dynamically indicated (e.g., for DG-PDSCH and SPS release) or RRC indicated (e.g., for SPS-PDSCH). If a PUCCH overlaps with a PUSCH, it is generally assumed that the UE performs multiplexing on the PUSCH. Depending on the content of the PUCCH, the format of the PUCCH, and whether the SR is affirmative or negative, the SR can be multiplexed or discarded on the PUCCH. If a PUCCH with an SR overlaps with a PUSCH without data, the PUSCH is discarded. If a PUCCH with an SR overlaps with a PUSCH with data, then the SR is discarded.

[0119] For CSI reporting without a PUCCH, the techniques disclosed herein support at least one of aperiodic CSI (A-CSI) on the PUSCH and P-CSI or semi-persistent CSI (SP-CSI) on the PUSCH. P-CSI on the PUSCH does not exist in 5G, and there is no mechanism in 4G / 5G to support event-triggered CSI on the PUSCH. To support P-CSI on the PUSCH, a serving cell with an uplink uses P-CSI reporting on the PUSCH to indicate, for example, through... CSI-ReportConfig In CSI-MeasConfig ,in reportConfigType Set as periodicOnPUSCH .

[0120] As part of the UE capability information, UE 102 can indicate the number of uplink CCs that are valid per timeslot for P-CSI on the PUSCH. This number can be set to 1 by default. Additionally or alternatively, UE 102 can report the maximum number of valid uplink CCs with P-CSI on the PUSCH, regardless of whether the P-CSI PUSCHs overlap in time. As part of the UE capability information, the UE can also indicate the number of downlink CCs on which P-CSI can be measured and reported on a single uplink CC. If this value is greater than 1, the UE can be configured with multiple... CSI-ReportConfigIds The corresponding ID CSI-ReportConfig Associated with a downlink CC. The UE will not expect any CSI-ReportConfigId Associated with more than one valid P-CSI report on PUSCH.

[0121] For the uplink serving cell, when UE 102 is configured with P-CSI on the PUSCH, the UE can be configured with CG-PUSCH to report P-CSI reports on the PUSCH. In some specific implementations, the CG-PUSCH configuration or the ID of the CG-PUSCH configuration carrying P-CSI on the PUSCH is transmitted via... ServingCellConfig In CSI-MeasConfig Provided to UE 102. If there is a (>1) one-to-one mapping between the downlink CC to be measured and the uplink CC to be reported P-CSI CG-PUSCH (e.g., ... Figure 2 (As shown), this method is useful. If there is a one-to-one mapping between the downlink CC to be measured and the uplink CC to be reported in P-CSI CG-PUSCH, then it can be done via... CSI-MeasConfig In IE CSI-ReportConfig Provide configuration to UE 102. Alternatively, it can be done via... ServingCellConfig In uplinkConfig The configuration is then communicated via a signal.

[0122] A CG-PUSCH ID or a configured list for P-CSI reporting can be configured for each serving cell, one per uplink BWP. For each valid uplink BWP, UE 102 knows which CG-PUSCH is used for P-CSI reporting on the PUSCH. Alternatively, a CG-PUSCH for P-CSI reporting can be configured for each serving cell for use in one uplink BWP. P-CSI on the PUSCH can be activated when that particular uplink BWP is valid. The content of the P-CSI on the PUSCH can be similar to the content of the SP-CSI on the PUSCH in 5G. However, in 5G, the content of the CSI on the PUSCH can be different from the CSI on the PUCCH.

[0123] Different procedures exist for constructing the HARQ-ACK codebook, but all procedures follow the same rules, where the resource reporting the HARQ-ACK is initially a PUCCH resource. If the resulting PUCCH resource (after multiplexing with other PUCCH resources) overlaps with a PUSCH, the associated UCI can be multiplexed on the PUSCH. For HARQ-ACK reports without a PUCCH, UE102 can be configured to multiplex the accumulated HARQ-ACK bits on the indicated PUSCH resource. This indication can be provided via an uplink DCI or RRC indication. The indicated "PUSCH" container may or may not carry data.

[0124] For the association between a downlink CC and an uplink CC carrying HARQ-ACK feedback for the corresponding downlink CC, a 1 (or > 1) one-to-1 mapping may exist between the downlink CC and the uplink CC. UE 102 may not be able to report HARQ-ACK for PDSCHs scheduled on more than one uplink CC. Alternatively, one or more downlink CCs may be mapped to more than one uplink CC. In such a case, UE 102 can be configured to report HARQ-ACK for PDSCHs scheduled on the downlink CC on more than one uplink CC. Using this method, HARQ-ACK feedback from overlapping PUSCHs spanning different uplink CCs can be reused when HARQ procedures are reported simultaneously on more than one uplink CC.

[0125] In some implementations, the association between a downlink CC and an uplink CC can be configured by RRC or indicated by MAC-CE. This association can also be indicated by a DCI, in which case fields in the DCI can indicate that a downlink scheduling is associated with a specific uplink CC. If the association is configured via an uplink DCI, fields in the DCI can be used to indicate which downlink CC(s) the PUSCH is carrying HARQ-ACK for. An indication of PUSCH resources carrying HARQ-ACK feedback can be provided via an uplink DCI that schedules PUSCHs with or without data. Alternatively, this indication can be provided by a downlink DCI that schedules the PDSCH. In this case, the PUSCH will be transmitted on the uplink CC associated with the downlink CC on which the PDSCH is scheduled. In some cases, the indicated PUSCH may not carry data. For example, UE102 may be configured with one or more specific PUSCHs on the uplink CC via RRC, and the downlink DCI can indicate which PUSCH to select.

[0126] For the construction and reporting of the HARQ-ACK codebook on the indicated uplink CC, UE 102 can use a type 3 codebook variant. Using this codebook, the uplink DCI can have a one-time flag. When this flag is set to 1, the HARQ-ACK bits of all downlink HARQ procedure numbers on the corresponding downlink CC can be multiplexed on the scheduled PUSCH. This method can be applied to all downlink messages for which UE 102 should provide HARQ-ACK, including SPS-PDSCH, DG-PDSCH, SPS release, etc.

[0127] Alternatively, UE 102 may use a Type 2 codebook variant. Using this codebook, each downlink DCI may have a downlink assignment indicator (DAI) and a K1 offset value indicating the number of bits to be reported in a given uplink slot, but without an indication of the PUSCH carrying HARQ-ACK. The downlink DAI may increment across all downlink CCs corresponding to that uplink CC. The uplink DCI scheduling the PUSCH on that slot may have a total DAI value. In some implementations, each downlink DCI also indicates in which PUSCH to carry HARQ-ACK. The indicated PUSCH (which may not carry data) is a configured resource on that uplink CC. A Type 3 codebook variant may be used for downlink scheduling without a DCI (such as SPS-PDSCH) or for downlink scheduling not corresponding to a DCI with a DAI value.

[0128] For SR transmission, UE 102 may be configured with special PUSCH resources that do not carry data via RRC. These special PUSCH resources will not overlap with regular PUSCH resources (with or without data) across any uplink CC. SR resources with positive SR and HARQ-ACK resources can be multiplexed. In some implementations, UE 102 is configured with cell-specific resources for uplink CC to carry HARQ-ACK. For example, this cell-specific resource could be Msg4 HARQ-ACK transmission. When UE 102 is configured with UE-specific resources, the cell-specific resources can be released. UE 102 may not expect cell-specific resources to overlap with UE-specific resources.

[0129] Supporting UCI without PUCCH allows for the simultaneous transmission of different PUSCHs across different CCs without complex multiplexing / priority ordering rules. The following methods can be used for multiplexing and / or prioritizing different PUSCHs with or without UCI. First, UE 102 resolves overlap of different PUSCHs within a CC, where (with or without UCI) DG-PUSCH takes precedence over (with or without UCI) CG-PUSCH, and CG-PUSCH takes precedence over P-CSI on the PUSCH. Within a given uplink CC, UE 102 may not expect the indicated PUSCH resource to overlap with a PUSCH carrying data scheduled by an uplink DCI (with or without HARQ-ACK). Alternatively, a special PUSCH with HARQ-ACK can be multiplexed with a PUSCH carrying data. However, this approach will be similar to PUCCH and PUSCH overlap in 5G.

[0130] UE 102 can further resolve overlap of different PUSCHs across different CCs. At any given time, only one CSI is allowed on a PUSCH across all CCs. This applies to: A-CSIs with data, which take precedence over A-CSIs without data; A-CSIs (with or without data), which take precedence over P-CSIs on the PUSCH; and CSIs on smaller serving cell indices, which take precedence over CSIs on larger serving cell indices. In some specific implementations, UE 102 does not multiplex PUSCHs with HARQ-ACKs and / or CSIs across different CCs. Instead, UE 102 can prioritize the transmission of remaining overlapping PUSCHs across different CCs simultaneously based on UE capability and power priority. The aforementioned resolution process applies to both identical and different PHY priority levels.

[0131] For different PHY priority orders, the priority of a PUSCH can be determined by the priority of the data carried by the PUSCH or the priority of the HARQ-ACK feedback carried by the PUSCH. In some examples, UE 102 does not expect the priority of the HARQ-ACK to be different from the priority of the PUSCH data. When it is determined that the total transmit power across different serving cells results in a total power exceeding the UE's power level, a lower priority PUSCH can be discarded (as determined above).

[0132] For event-triggered CSI reporting, the measurement resource can be a periodic or semi-persistent CSI reference signal (CSI-RS) or a synchronization signal block (SSB). For the number of CSI reports, the UE102 can be configured with a timer for the Layer 1 (L1) reference signal received power (L1-RSRP), which is reset when a CSI report is triggered and transmitted. One or more thresholds can be defined to trigger a report. A report can be triggered if the timer does not run and the measured quantity exceeds (or falls below) the configured threshold. The triggered report can be transmitted in the MAC-CE. In such cases, the MAC-CE can indicate which quantities are included in the report. Alternatively, a separate MAC-CE can be configured for each reported quantity.

[0133] Figure 2 Example resource diagram 200 is illustrated according to some specific implementations. Resource diagram 200 shows how the PUSCH resource can be used to implement P-CSI reporting when performing UCI reporting without PUCCH, as described herein. Figure 2 The diagram illustrates two distinct downlink CC sets: a first downlink CC set 202 comprising carriers C0, C1, and C2, and a second downlink CC set 206 comprising carriers C3 and C4. Each set of downlink CCs is mapped to a corresponding uplink CC carrying P-CSI on the PUSCH. Resource diagram 200 illustrates the mapping between two or more downlink CCs and a single CC.

[0134] The first group of downlink CCs 202 represents a serving cell configuration in which, for example, three downlink CCs are measured and reported together. UE capability signaling can indicate that up to three downlink CCs can be valid for periodic CSI reporting on a single uplink CC. In some specific implementations, the CG-PUSCH resource associated with uplink CC 204 is designated to carry periodic CSI for downlink carriers C0, C1, and C2. This direct association eliminates the need for UE 102 to evaluate multiple PUCCH candidates or resolve overlaps with other PUSCH timings.

[0135] The second group of downlink CCs 206 can be configured for periodic CSI reporting on different uplink CCs. In some specific implementations, the CG-PUSCH resource on uplink CC 208 is configured to carry periodic CSI for downlink carriers C3 and C4. This association can be determined by... ServingCellConfig RRC Information Elements (IE) CSI-MeasConfig Parameters are used for configuration. Alternatively, if a one-to-one mapping is used, then... CSI-MeasConfig of CSI-ReportConfig Parameters can be used to indicate PUSCH configuration.

[0136] Designating uplink CC 204 and uplink CC 208 as containers for P-CSI reduces the complexity of UCI reporting without PUCCH. Instead of selecting and multiplexing among multiple PUCCH resources according to traditional rules, UE 102 can simply send UCI on a designated CG-PUSCH resource within the effective uplink bandwidth portion (BWP). This reduces ambiguity and processing overhead by leveraging UE capability information and explicitly configuring the CG-PUSCH identifier (ID) for each serving cell and / or each uplink BWP.

[0137] The network can avoid unsupported multi-carrier reporting configurations by adhering to the maximum number of valid downlink CCs per uplink CC reported by the UE. Since the mapping between downlink CCs and uplink CCs is fixed (e.g., three downlink CCs to uplink CC 204 and two downlink CCs to uplink CC 208), UE 102 does not need to perform complex overlap resolution. Instead, UE 102 can reliably transmit periodic CSI reports on designated PUSCH resources without evaluating alternative UCI containers, which improves reliability and reduces signaling overhead.

[0138] Figure 3 Example signaling diagram 300 is illustrated according to some specific implementations. Signaling diagram 300 depicts UE 302 (such as...) in the context of a UCI report without PUCCH. Figure 1 UE 102) and base station 304 (such as Figure 1 The UE 302 communicates with base station 304. In signaling diagram 300, UE 302 announces its UCI reporting capability, receives reporting configuration from base station 304, processes any downlink indications, identifies the PUSCH container for UCI reporting, and sends UCI at the specified PUSCH timing.

[0139] At 306, UE 302 sends capability information to base station 304. In some examples, the capability information indicates the number of uplink CCs that UE 302 can support per time slot for periodic CSI on the PUSCH, the maximum number of valid uplink CCs that can overlap, and / or the number of downlink CCs that can be measured and reported on a single uplink CC. Providing these RRC capability parameters ensures that base station 304 will only configure multicarrier reporting parameters that can be reliably processed by UE 302.

[0140] At point 308, base station 304 provides UCI report configuration to UE 302. In some specific implementations, in CSI- MeasConfig or uplinkConfig The IE carries the UCI report configuration. The UCI report configuration can indicate, for example, that periodic CSI reports will be transmitted via the CG-PUSCH resource. Additionally or alternatively, the UCI report configuration can list the CG-PUSCH configuration IDs associated with the valid uplink BWP for each serving cell.

[0141] At 310, base station 304 may optionally transmit downlink messages, such as PDSCH transmissions or DCI indicating additional resources / flags for UCI reporting. In some examples, this downlink message carries a "one-time" flag to indicate the HARQ-ACK codebook for scheduled PUSCHs. Additionally or alternatively, the downlink message may reconfirm which CG-PUSCH timing will carry the next UCI report. This eliminates the need for UE 302 to perform complex PUCCH overlap resolution.

[0142] At position 312, UE 302 identifies the uplink resources to be used for UCI transmission, such as PUSCH resources. In some specific implementations, this involves the received... CSI-ReportConfigIds The CG-PUSCH ID is matched against the configuration used for the valid uplink BWP, and each downlink CC is mapped to its designated uplink CC and / or PUSCH container. If the downlink message (at 310) includes a DCI-based indicator for HARQ-ACK, UE 302 can also determine which PUSCH resource should carry the accumulated ACK bit.

[0143] At 314, UE 302 transmits a UCI to base station 304 via the identified uplink resource. This UCI may include periodic CSI, event-triggered CSI, HARQ-ACK feedback, or SR. As described herein, the UCI may be multiplexed or transmitted on a separate CG-PUSCH occasion. Since UE 302 already knows which PUSCH container to use, UE 302 can simply transmit the UCI via the specified PUSCH container without further selection logic.

[0144] Figure 4 A flowchart illustrating an example method 400 for UCI transmission without a PUCCH, according to some specific implementation, is shown. For clarity, method 400 is described in the context of the preceding figures. For example, method 400 may be provided by a UE (such as...) Figure 1 Method 400 can also be performed by any suitable system, environment, software, hardware, or combination thereof. In some implementations, the operation of method 400 may be performed in parallel, in combination, cyclically, or in any order. Figure 4 The example method 400 shown can be modified or reconfigured to include additional, fewer, or different steps. Figure 4 (not shown in the image), these steps can be performed in the order shown or in a different order.

[0145] At 402, the UE receives control signaling that configures one or more parameters for UCI reporting on PUSCH resources.

[0146] At 404, the UE determines the mapping between at least one downlink CC and at least one uplink CC based on one or more parameters configured for UCI reporting on PUSCH resources.

[0147] At 406, the UE transmits UCI via one or more PUSCH resources associated with at least one uplink CC, based at least on the determined mapping.

[0148] Figure 5 A flowchart illustrating an example method 500 for UCI reception without a PUCCH, according to some specific implementation, is shown. For clarity, method 500 is described in the context of the preceding figures. For example, method 500 may be provided by an access node such as... Figure 1 The method is executed by base station 104. Method 500 can also be executed by any suitable system, environment, software, hardware, or combination thereof. In some specific implementations, the operation of method 500 can be run in parallel, in combination, cyclically, or in any order. Figure 5 The example method 500 shown can be modified or reconfigured to include additional, fewer, or different steps. Figure 5 (not shown in the image), these steps can be performed in the order shown or in a different order.

[0149] At position 502, the access node sends control signaling that configures one or more parameters for UCI reporting on PUSCH resources.

[0150] At 504, the access node determines the mapping between at least one downlink CC and at least one uplink CC based on one or more parameters configured for UCI reporting on PUSCH resources.

[0151] At 506, the access node receives UCI via one or more PUSCH resources associated with at least one uplink CC, based at least on the determined mapping.

[0152] Figure 6 Example UE 600 according to some specific implementation is illustrated. UE 600 may be similar to Figure 1 UE 102, and / or substantially interchangeable with that UE. UE 600 can be any mobile or non-mobile computing device, such as (e.g.) mobile phones, computers, tablets, industrial wireless sensors, video devices (e.g., cameras or camcorders), wearable devices (e.g., smartwatches), slack IoT devices, etc.

[0153] UE 600 may include a processor 602, RF interface circuitry 604, memory / storage device 606, user interface 608, sensor 610, drive circuitry 612, power management integrated circuit (PMIC) 614, one or more antennas 616, and / or battery 618. The components of UE 600 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 6 The block diagram shows a simplified view of some of the components of the UE 600. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may be used in other specific implementations.

[0154] The components of UE 600 can be coupled to various other components via one or more interconnects 620, which can represent any type of interface, input / output, bus (local, system, or extended), transmit line, trace, optical connection, etc., allowing various circuit components (on common or different chips or chipsets) to interact with each other.

[0155] Processor 602 may include one or more processors. For example, processor 602 may include processor circuitry such as, for example, baseband processor circuitry (BB) 622A, central processing unit circuitry (CPU) 622B, and graphics processing unit circuitry (GPU) 622C. Processor 602 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional processes from memory / storage device 606) to cause UE 600 to perform the operations described herein.

[0156] In some implementations, the baseband processor circuit 622A can access the communication protocol stack 624 in the memory / storage device 606 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuit 622A can access the communication protocol stack to perform user plane functions at the Physical (PHY) layer, Medium Access Control (MAC) layer, Radio Link Control (RLC) layer, Packet Data Convergence Protocol (PDCP) layer, Serving Data Adaptation Protocol (SDAP) layer, and Protocol Data Unit (PDU) layer; and to perform control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and Non-Access Stratum (NAS) layer. In some implementations, PHY layer operations may additionally / optionally be performed by components of the RF interface circuit 604. The baseband processor circuit 622A can generate or process baseband signals or waveforms carrying information in a 3GPP-compliant network. In some specific implementations, the waveform used for NR can be based on Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM) in the uplink or downlink and Discrete Fourier Transform Extended OFDM (DFT-S-OFDM) in the uplink.

[0157] Memory / storage device 606 may include one or more non-transitory computer-readable media, including instructions (e.g., communication protocol stack 624) that can be executed by processor 602 to cause UE 600 to perform the various operations described herein. Memory / storage device 606 may include any type of volatile or non-volatile memory that can be distributed throughout UE 600. In some specific implementations, memory / storage device 606 may be located on processor 602 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 606 may be located external to processor 602 but accessible via a memory interface. Memory / storage device 606 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0158] RF interface circuitry 604 may include transceiver circuitry and a radio frequency front-end module (RFEM) that allows UE 600 to communicate with other devices via a radio access network. RF interface circuitry 604 may include various components arranged in the transmit or receive path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

[0159] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna 616 and continue to filter and amplify the signal (using a low-noise amplifier). This signal can be provided to the transceiver's receiver, which down-converts the RF signal into a baseband signal for the baseband processor.

[0160] In the transmission path, the transceiver's transmitter up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM can amplify the RF signal via a power amplifier before it is radiated across the air interface via antenna 616. In various specific implementations, the RF interface circuitry 604 can be configured to transmit / receive signals in a manner compatible with NR access technologies.

[0161] Antenna 616 may include one or more antenna elements to convert electrical signals into radio waves for travel through the air and to convert received radio waves into electrical signals in the air. In some embodiments, these antenna elements may be arranged as one or more antenna panels. Antenna 616 may have omnidirectional, directional, or a combination thereof antenna panels to enable beamforming and multiple-input multiple-output communication. Antenna 616 may include any / all of the following: microstrip antenna, printed antenna fabricated on the surface of one or more printed circuit boards, patch antenna, phased array antenna, etc. Antenna 616 may have one or more panels designed for one or more specific frequency bands (such as bands in FR1 or FR2).

[0162] User interface 608 includes various input / output (I / O) devices designed to enable a user to interact with UE 600. User interface 608 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual components for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, or a head-mounted device. Output device circuitry includes any physical or virtual components for displaying information or otherwise conveying information, such as sensor readings, actuator positions, or other similar information. Output device circuitry may include any number or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary status indicators such as light-emitting diodes "LEDs," and multi-character visual outputs), or more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays "LCDs," LED displays, quantum dot displays, projectors), wherein the output of characters, graphics, multimedia objects, etc., is generated or produced through the operation of UE 600.

[0163] Sensor 610 may include devices, modules, or subsystems intended to detect events or changes in their environment and transmit information about the detected events (sensor data) to other devices, modules, subsystems, etc. Examples of such sensors include, in particular, inertial measurement units (IMUs) including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; temperature sensors (e.g., thermistors); pressure sensors; image capture devices (e.g., cameras or lensless aperture devices); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices; and so on.

[0164] The driving circuitry 612 may include software and hardware elements that operate to control a specific device embedded in, attached to, or otherwise communicatively coupled to the UE 600. The driving circuitry 612 may include various drivers that allow other components to interact with or control various input / output (I / O) devices that may exist within or be connected to the UE 600. For example, the driving circuitry 612 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for acquiring sensor readings of a sensor 610 and controlling and allowing access to the sensor 610; an actuator for acquiring actuator positioning of an electromechanical component or controlling and allowing access to an electromechanical component; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0165] The PMIC 614 manages the power supplied to various components of the UE 600. Specifically, relative to the processor 602, the PMIC 614 controls power selection, voltage scaling, battery charging, or DC-DC conversion.

[0166] In some implementations, the PMIC 614 may control various power-saving mechanisms of the UE 600 or otherwise become part of those mechanisms. The battery 618 may power the UE 600, but in some examples, the UE 600 may be installed in a fixed location and may have a power source coupled to the mains grid. The battery 618 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in vehicle-based applications, the battery 618 may be a typical lead-acid automotive battery.

[0167] Figure 7 An example access node 700 according to some specific implementations is illustrated. Access node 700 (also referred to as a base station or gNB) may be similar to base station 104 and / or substantially interchangeable with it. Access node 700 may include one or more of a processor 702, RF interface circuitry 704, core network (CN) interface circuitry 706, memory / storage device circuitry 708, and one or more antennas 710. Processor 702 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional procedures from memory / storage device circuitry 708) to cause access node 700 to perform the operations described herein.

[0168] Components of access node 700 can be coupled to various other components via one or more interconnects 712. Processor 702, RF interface circuitry 704, memory / storage device circuitry 708 (including communication protocol stack 714), antenna 710, and interconnects 712 may be similarly named elements relative to those shown and described in Figure Y1. For example, processor 702 may include processor circuitry such as, for example, baseband processor circuitry (BB) 716A, central processing unit circuitry (CPU) 716B, and graphics processing unit circuitry (GPU) 716C.

[0169] The CN interface circuit 706 can provide connectivity to a core network (e.g., a 5GC using a 5G core network (5GC) compatible network interface protocol, such as carrier Ethernet or some other suitable protocol). Network connectivity can be provided to / from access node 700 via fiber optic or wireless backhaul. The CN interface circuit 706 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 706 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0170] As used herein, the terms "access node," "access point," etc., refer to equipment that provides radio baseband functionality for data and / or voice connectivity between a network and one or more users. Access nodes may also be referred to as base stations (BS), gNBs, RAN nodes, eNBs, NodeBs, roadside units (RSUs), transmit and receive points (TRPs), TRxPs, etc. Access nodes may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NGRAN node," etc., refer to access node 700 operating in an NR or 5G system (e.g., a gNB), and the terms "E-UTRAN node," etc., refer to access node 700 operating in an LTE or 4G system (e.g., an eNB). Depending on various specific implementations, access node 700 may be implemented as one or more of dedicated physical devices, such as macrocell base stations and / or low-power base stations for providing (compared to macrocells) smaller coverage areas, smaller user capacity, or higher bandwidth in femtocells, picocells, or other similar cells.

[0171] In some specific implementations, the access node 700 may be implemented as one or more software entities running on a server computer as part of a virtual network, which may be referred to as a cloud RAN (CRAN) and / or a virtual baseband unit pool (vBBUP). In the vehicle-to-everything (V2X) scenario, the access node 700 may be or act as an RSU, where RSU refers to any transport infrastructure entity used for V2X communication. An RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, wherein an RSU implemented in or by a UE is referred to as a "UE-type RSU," an RSU implemented in or by an eNB is referred to as an "eNB-type RSU," an RSU implemented in or by a gNB is referred to as a "gNB-type RSU," and so on.

[0172] In the preceding description, various components are described as performing one or more tasks. Such descriptions should be interpreted as including the phrase “configured to”. Statements describing a component as configured to perform one or more tasks are explicitly intended not to invoke the interpretation of 35 USC § 112(f) for that component.

[0173] In some implementations, one or more of the components described in the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods set forth in the following embodiments. For example, the baseband circuitry described in conjunction with one or more of the foregoing figures may be configured to operate according to one or more embodiments described below. As another example, circuitry associated with a UE, access node, base station, or network element may be configured to operate according to one or more embodiments set forth below.

[0174] Example 1 is a method comprising: receiving control signaling configuring one or more parameters for UCI reporting on PUSCH resources; determining a mapping between at least one downlink CC and at least one uplink CC based on the one or more parameters configured for UCI reporting on PUSCH resources; and transmitting a UCI via one or more PUSCH resources associated with the at least one uplink CC based on the determined mapping.

[0175] Example 2 includes the method according to Example 1, wherein the UCI includes at least one of P-CSI report, A-CSI report, event-triggered CSI report, HARQ ACK feedback or SR.

[0176] Example 3 includes the method according to Example 2, wherein the control signaling configures event-triggered CSI reports on one or more PUSCH resources.

[0177] Example 4 includes the method according to any one of Examples 1 to 3, the method further including sending capability signaling indicating at least one of the following: (i) the number of valid uplink CCs that can be reported for P-CSI on PUSCH resources per time slot; (ii) the maximum number of valid uplink CCs reported for P-CSI on PUSCH resources; or (iii) the number of downlink CCs that can be measured and reported on a single uplink CC.

[0178] Example 5 includes the method according to Example 4, wherein the capability signaling indication can measure and report more than one downlink CC on a single uplink CC.

[0179] Example 6 includes the method according to any one of Examples 1 to 5, wherein the control signaling configuration CSI- ReportConfigId A set of values, each associated with a different downlink CC.

[0180] Example 7 includes the method according to Example 6, wherein each CSI-ReportConfigId The value is associated with at most one valid periodic CSI report.

[0181] Example 8 includes the method according to any one of Examples 1 to 7, wherein the control signaling indicates a CG PUSCH resource to be used for P-CSI reporting.

[0182] Example 9 includes the method according to Example 8, wherein the identifier or configuration of the CG PUSCH resource is determined by... ServingCellConfig IE CSI-MeasConfig Fields, the described CSI-MeasConfig Within the field CSI- ReportConfig Subfield or the described ServingCellConfig In IE uplinkConfig At least one of the fields must be provided.

[0183] Example 10 includes the method according to any one of Examples 1 to 9, wherein one or more parameters include a list of CG PUSCH identifiers or configurations configured for P-CSI reporting per serving cell.

[0184] Example 11 includes the method according to Example 10, wherein a corresponding list of CGPUSCH identifiers or configurations is provided for each uplink BWP.

[0185] Example 12 includes the method according to any one of Examples 1 to 11, wherein a single CG PUSCH resource is configured for each serving cell for a particular uplink BWP, and wherein the CGPUSCH resource is activated when the particular uplink BWP is active.

[0186] Example 13 includes the method according to any one of Examples 1 to 12, the method further comprising multiplexing accumulated HARQ-ACK bits on the one or more PUSCH resources according to the control signaling.

[0187] Example 14 includes the method according to Example 13, wherein the control signaling includes DCI or RRC signaling.

[0188] Example 15 includes the method according to any one of Examples 13 to 14, wherein the accumulated HARQ-ACK bit is multiplexed with uplink data.

[0189] Example 16 includes the method according to any one of Examples 1 to 15, wherein determining the mapping includes receiving a mapping between a downlink CC and an uplink CC via the control signaling, a mapping between more than one downlink CC and an uplink CC, a mapping between one downlink CC and more than one uplink CC, or a mapping between more than one downlink CC and more than one uplink CC.

[0190] Example 17 includes the method according to Example 16, wherein HARQ-ACK feedback is not reported for PDSCH on downlink CCs mapped to more than one uplink CC.

[0191] Example 18 includes the method according to any one of Examples 16 to 17, wherein HARQ-ACK feedback is reported for PDSCH scheduled on downlink CCs mapped to more than one uplink CC.

[0192] Example 19 includes the method according to any one of Examples 16 to 18, wherein the control signaling includes an RRC message, MAC-CE, or DCI indicating the association between the downlink CC and the uplink CC.

[0193] Example 20 includes the method according to Example 19, wherein the field in the DCI instructs the PUSCH to send a HARQ-ACK feedback carrying one or more uplink CCs in the uplink CCs.

[0194] Example 21 includes the method according to Example 20, wherein the DCI schedules the PUSCH transmission with or without uplink data.

[0195] Example 22 includes the method according to any one of Examples 20 to 21, wherein the DCI schedules PDSCH transmission on the downlink CC.

[0196] Example 23 includes the method according to Example 22, wherein the PUSCH transmission is scheduled on an uplink CC associated with the downlink CC on which the PDSCH transmission is received.

[0197] Example 24 includes the method according to any one of Examples 20 to 23, wherein the control signaling is configured for one or more PUSCH resources for UCI transmission without uplink data.

[0198] Example 25 includes the method according to any one of Examples 20 to 24, the method further comprising: in response to determining that a flag in the DCI is set to one, multiplexing the HARQ-ACK bit for all downlink HARQ procedures on the downlink CC mapped to the uplink CC on which the PUSCH transmission is scheduled.

[0199] Example 26 includes the method according to any one of Examples 20 to 25, wherein the DCI includes DAI and a K1 offset value indicating the number of bits to be reported in the uplink timeslot.

[0200] Example 27 includes the method according to Example 26, wherein the DAI increments across all downlink CCs corresponding to the uplink CCs on which the PUSCH is scheduled to be transmitted.

[0201] Example 28 includes the method according to any one of Examples 20 to 27, wherein the DCI indicates a PUSCH resource to be used for sending HARQ-ACK feedback for PDSCH transmission, and wherein the indicated PUSCH resource does not carry uplink data.

[0202] Example 29 includes the method according to any one of Examples 1 to 28, wherein the control signaling configures one or more PUSCH resources of each uplink CC to carry an SR that does not have uplink data.

[0203] Example 30 includes the method according to Example 29, wherein one or more PUSCH resources do not overlap with PUSCH resources carrying uplink data across any uplink CC.

[0204] Example 31 includes the method according to any one of Examples 29 to 30, the method further comprising multiplexing the HARQ-ACK feedback with the SR on a shared PUSCH resource when both the SR and the HARQ-ACK feedback are scheduled on the same uplink CC.

[0205] Example 32 includes the method according to any one of Examples 1 to 31, the method further comprising configuring cell-specific PUSCH resources of each uplink CC to carry HARQ-ACK feedback for Msg4, wherein the cell-specific PUSCH resources are released when one or more UE-specific PUSCH resources are configured.

[0206] Example 33 includes the method according to Example 32, wherein the cell-specific PUSCH resources do not overlap with the one or more UE-specific PUSCH resources.

[0207] Example 34 includes the method according to any one of Examples 1 to 33, the method further comprising: identifying overlap between multiple PUSCH transmissions scheduled on the uplink CC; and resolving the overlap by prioritizing DG PUSCH transmissions over CG PUSCH transmissions and prioritizing CG PUSCH transmissions over P-CSI reports.

[0208] Example 35 includes the method according to any one of Examples 1 to 34, wherein the PUSCH resources configured for UCI transmission on a specific uplink CC do not overlap with PUSCH resources carrying data scheduled by DCI.

[0209] Example 36 includes the method according to any one of Examples 1 to 35, wherein a PUSCH carrying CSI is allowed to be transmitted across all uplink CCs.

[0210] Example 37 includes the method according to any one of Examples 1 to 36, wherein A-CSI reports with data are preferred over A-CSI reports without data, and wherein A-CSI reports with or without data are preferred over P-CSI reports, and wherein CSI transmissions associated with a lower serving cell index are preferred over CSI reports with a higher serving cell index.

[0211] Example 38 includes the method according to any one of Examples 1 to 37, the method further comprising concurrently transmitting overlapping PUSCH transmissions across different uplink CCs without multiplexing the UCI across the uplink CCs.

[0212] Example 39 includes the method according to any one of Examples 1 to 38, the method further comprising determining the priority of a PUSCH resource based on at least one of: (i) the priority of uplink data carried by the PUSCH resource, or (ii) the priority of HARQ-ACK feedback carried by the PUSCH resource, wherein the priority of HARQ-ACK feedback corresponds to the priority of the uplink data.

[0213] Example 40 includes the method according to Example 39, the method further comprising discarding PUSCH transmissions with lower priority when the sum of transmission power across multiple serving cells exceeds a threshold.

[0214] Example 41 includes the method according to any one of Examples 1 to 40, the method further comprising performing measurements on one or more resources according to an event-driven CSI reporting configuration, wherein the one or more resources include periodic or semi-persistent CSI-RS resources or SSBs.

[0215] Example 42 includes the method according to any one of Examples 1 to 41, wherein the control signaling is configured to trigger a timer and one or more thresholds for an event-driven CSI report.

[0216] Example 43 includes the method according to Example 42, wherein the timer is reset after an event-driven CSI report is sent.

[0217] Example 44 includes the method according to any one of Examples 42 to 43, the method further comprising sending a triggered event-driven CSI report in the MAC-CE, the triggered event-driven CSI report indicating which CSI quantities are included in the CSI report.

[0218] Example 45 includes the method according to any one of Examples 42 to 44, wherein a separate MAC-CE format is configured for each CSI report volume.

[0219] Example 46 includes the method according to any one of Examples 1 to 45, wherein receiving the control signaling for configuring the one or more parameters for UCI reporting on PUSCH resources includes receiving network indications for the one or more parameters to be used for overlap resolution and resource selection.

[0220] Example 47 includes the method according to Example 46, wherein the control signaling further indicates a set of UCI types to be multiplexed on the one or more PUSCH resources selected for transmitting the UCI.

[0221] Example 48 is an apparatus comprising: one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform the method according to any one of Examples 1 to 47.

[0222] Example 49 is a baseband processor configured to perform the method according to any one of Examples 1 to 47.

[0223] Example 50 is a method comprising: sending control signaling configuring one or more parameters for UCI reporting on PUSCH resources; determining a mapping between at least one downlink CC and at least one uplink CC based on the one or more parameters configured for UCI reporting on PUSCH resources; and receiving UCIs via one or more PUSCH resources associated with the at least one uplink CC based on the determined mapping.

[0224] Example 51 includes the method according to Example 50, wherein the UCI includes at least one of P-CSI report, A-CSI report, event-triggered CSI report, HARQ-ACK feedback or SR.

[0225] Example 52 includes the method according to Example 51, wherein the control signaling configures an event-triggered CSI report on one or more PUSCH resources.

[0226] Example 53 includes the method according to any one of Examples 50 to 52, the method further comprising receiving capability signaling indicating at least one of the following: (i) the number of valid uplink CCs that can be reported for P-CSI on PUSCH resources per time slot; (ii) the maximum number of valid uplink CCs reported for P-CSI on PUSCH resources; or (iii) the number of downlink CCs that can be measured and reported on a single uplink CC.

[0227] Example 54 includes the method according to Example 53, wherein the capability signaling indication can measure and report more than one downlink CC on a single uplink CC.

[0228] Example 55 includes the method according to any one of Examples 50 to 54, wherein the control signaling configuration CSI-ReportConfigId A set of values, each associated with a different downlink CC.

[0229] Example 56 includes the method according to Example 55, wherein each CSI-ReportConfigId The value is associated with at most one valid periodic CSI report.

[0230] Example 57 includes the method according to any one of Examples 50 to 56, wherein the control signaling indicates a CG PUSCH resource to be used for P-CSI reporting.

[0231] Example 58 includes the method according to Example 57, wherein the identifier or configuration of the CG PUSCH resource is determined by... ServingCellConfig IE CSI-MeasConfig Fields, the described CSI-MeasConfig Within the field CSI- ReportConfig Subfield or the described ServingCellConfig In IE uplinkConfig At least one of the fields must be provided.

[0232] Example 59 includes the method according to any one of Examples 50 to 58, wherein one or more parameters include a list of CG PUSCH identifiers or configurations configured for P-CSI reporting per serving cell.

[0233] Example 60 includes the method according to Example 59, wherein a corresponding list of CGPUSCH identifiers or configurations is provided for each uplink BWP.

[0234] Example 61 includes the method according to any one of Examples 50 to 60, wherein a single CG PUSCH resource is configured for each serving cell for a particular uplink BWP, and wherein the CG PUSCH resource is activated when the particular uplink BWP is active.

[0235] Example 62 includes the method according to any one of Examples 50 to 61, the method further comprising receiving accumulated HARQ-ACK bits multiplexed on the one or more PUSCH resources according to the control signaling.

[0236] Example 63 includes the method according to Example 62, wherein the control signaling includes DCI or RRC signaling.

[0237] Example 64 includes the method according to any one of Examples 62 to 63, wherein the accumulated HARQ-ACK bit is multiplexed with uplink data.

[0238] Example 65 includes the method according to any one of Examples 50 to 64, wherein determining the mapping includes receiving a mapping between a downlink CC and an uplink CC via the control signaling, a mapping between more than one downlink CC and an uplink CC, a mapping between one downlink CC and more than one uplink CC, or a mapping between more than one downlink CC and more than one uplink CC.

[0239] Example 66 includes the method according to Example 65, wherein HARQ-ACK feedback is not reported for PDSCH on downlink CCs mapped to more than one uplink CC.

[0240] Example 67 includes the method according to any one of Examples 65 to 66, wherein HARQ-ACK feedback is reported for PDSCH scheduled on downlink CCs mapped to more than one uplink CC.

[0241] Example 68 includes the method according to any one of Examples 65 to 67, wherein the control signaling includes an RRC message, MAC-CE, or DCI indicating the association between the downlink CC and the uplink CC.

[0242] Example 69 includes the method according to Example 68, wherein the field in the DCI instructs the PUSCH to send a HARQ-ACK feedback carrying one or more uplink CCs in the uplink CCs.

[0243] Example 70 includes the method according to Example 69, wherein the DCI schedules the PUSCH transmission with or without uplink data.

[0244] Example 71 includes the method according to any one of Examples 69 to 70, wherein the DCI schedules PDSCH transmission on the downlink CC.

[0245] Example 72 includes the method according to Example 71, wherein the PUSCH transmission is scheduled on an uplink CC associated with the downlink CC on which the PDSCH transmission is received.

[0246] Example 73 includes the method according to any one of Examples 69 to 72, wherein the control signaling is configured for one or more PUSCH resources for UCI transmission without uplink data.

[0247] Example 74 includes the method according to any one of Examples 69 to 73, wherein the DCI includes DAI and a K1 offset value indicating the number of bits to be reported in the uplink timeslot.

[0248] Example 75 includes the method according to Example 74, wherein the DAI increments across all downlink CCs corresponding to the uplink CCs on which the PUSCH is scheduled to be transmitted.

[0249] Example 76 includes the method according to any one of Examples 69 to 75, wherein the DCI indicates a PUSCH resource to be used for sending HARQ-ACK feedback for PDSCH transmission, and wherein the indicated PUSCH resource does not carry uplink data.

[0250] Example 77 includes the method according to any one of Examples 50 to 76, wherein the control signaling configures one or more PUSCH resources of each uplink CC to carry an SR that does not have uplink data.

[0251] Example 78 includes the method according to Example 77, wherein one or more PUSCH resources do not overlap with PUSCH resources carrying uplink data across any uplink CC.

[0252] Example 79 includes the method according to any one of Examples 50 to 78, the method further comprising configuring cell-specific PUSCH resources of each uplink CC to carry HARQ-ACK feedback for Msg4, wherein the cell-specific PUSCH resources are released when one or more UE-specific PUSCH resources are configured.

[0253] Example 80 includes the method according to Example 79, wherein the cell-specific PUSCH resources do not overlap with the one or more UE-specific PUSCH resources.

[0254] Example 81 includes the method according to any one of Examples 50 to 80, wherein the PUSCH resources configured for UCI transmission on a particular uplink CC do not overlap with PUSCH resources carrying data scheduled by DCI.

[0255] Example 82 includes the method according to any one of Examples 50 to 81, wherein a PUSCH carrying CSI is allowed to be transmitted across all uplink CCs.

[0256] Example 83 includes the method according to any one of Examples 50 to 82, wherein A-CSI reports with data are preferred over A-CSI reports without data, and wherein A-CSI reports with or without data are preferred over P-CSI reports, and wherein CSI transmissions associated with a lower serving cell index are preferred over CSI reports with a higher serving cell index.

[0257] Example 84 includes the method according to any one of Examples 50 to 83, the method further comprising concurrently receiving overlapping PUSCH transmissions across different uplink CCs, wherein the UCI is not multiplexed across the uplink CCs.

[0258] Example 85 includes the method according to any one of Examples 50 to 84, the method further comprising determining the priority of a PUSCH resource based on at least one of: (i) the priority of uplink data carried by the PUSCH resource, or (ii) the priority of HARQ-ACK feedback carried by the PUSCH resource, wherein the priority of HARQ-ACK feedback corresponds to the priority of the uplink data.

[0259] Example 86 includes the method according to any one of Examples 50 to 85, wherein the control signaling configures a timer and one or more thresholds for triggering an event-driven CSI report.

[0260] Example 87 includes the method according to Example 86, wherein the timer is reset after an event-driven CSI report is sent.

[0261] Example 88 includes the method according to any one of Examples 86 to 87, the method further including receiving a triggered event-driven CSI report in the MAC-CE, the triggered event-driven CSI report indicating which CSI quantities are included in the CSI report.

[0262] Example 89 includes the method according to any one of Examples 86 to 88, wherein a separate MAC-CE format is configured for each CSI report volume.

[0263] Example 90 includes the method according to any one of Examples 50 to 89, wherein sending the control signaling configuring the one or more parameters for UCI reporting on PUSCH resources includes sending network indications for the one or more parameters to be used for overlap resolution and resource selection.

[0264] Example 91 includes the method according to Example 90, wherein the control signaling further indicates a set of UCI types to be multiplexed on the one or more PUSCH resources selected for transmitting the UCI.

[0265] Example 92 is an apparatus comprising: one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform the method according to any one of Examples 50 to 91.

[0266] Example 93 is a baseband processor configured to perform the method according to any one of Examples 50 to 91.

[0267] Unless otherwise expressly stated, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. In view of the teachings above, modifications and variations are possible, or modifications and variations may be obtained from practice of various embodiments.

[0268] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the above disclosure is fully understood. It is intended that the following claims be construed as encompassing all such variations and modifications.

[0269] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

Claims

1. A method, the method comprising: Receive control signaling, which configures one or more parameters for uplink control information (UCI) reporting on Physical Uplink Shared Channel (PUSCH) resources; The mapping between at least one downlink component carrier (CC) and at least one uplink CC is determined based on one or more parameters configured for UCI reporting on PUSCH resources; as well as UCI is sent via one or more PUSCH resources associated with at least one uplink CC, based at least on the determined mapping.

2. The method of claim 1, wherein the UCI includes at least one of periodic channel state information (P-CSI) report, aperiodic channel state information (A-CSI) report, event-triggered CSI report, hybrid automatic repeat request (HARQ) acknowledgment (ACK) feedback or scheduling request (SR), and wherein the control signaling configures event-triggered CSI report on the one or more PUSCH resources.

3. The method of claim 1, further comprising sending capability signaling, the capability signaling indicating at least one of the following: (i) the number of valid uplink CCs that can be reported for P-CSI on PUSCH resources per time slot, (ii) the maximum number of valid uplink CCs reported for P-CSI on PUSCH resources, or (iii) the number of downlink CCs that can be measured and reported on a single uplink CC, wherein the capability signaling indicates that more than one downlink CC can be measured and reported on a single uplink CC.

4. The method according to claim 1, wherein the control signaling configures multiple CSI-ReportConfigId Values, each associated with a different downlink CC, and each of them CSI-ReportConfigId The value is associated with at most one valid periodic CSI report, and The control signaling indicates the configuration permission (CG)PUSCH resource to be used for P-CSI reporting, and the identifier or configuration of the CGPUSCH resource is determined by... ServingCellConfig IE CSI-MeasConfig Fields, as described CSI- MeasConfig Fields CSI-ReportConfig Subfield or the described ServingCellConfig In IE uplinkConfig At least one of the fields must be provided.

5. The method of claim 1, wherein the one or more parameters include a list of CG PUSCH identifiers or configurations configured for P-CSI reporting per serving cell. This provides a list of CG PUSCH identifiers or configurations for each uplink bandwidth portion (BWP), and Each serving cell is configured with a single CG PUSCH resource for a specific uplink BWP, and the CG PUSCH resource is activated when the specific uplink BWP is active.

6. The method of claim 1, further comprising multiplexing accumulated HARQ-ACK bits on the one or more PUSCH resources according to the control signaling, wherein the accumulated HARQ-ACK bits are multiplexed with uplink data.

7. The method of claim 1, wherein determining the mapping includes receiving, via the control signaling, a mapping between a downlink CC and an uplink CC, a mapping between more than one downlink CC and an uplink CC, a mapping between one downlink CC and more than one uplink CC, or a mapping between more than one downlink CC and more than one uplink CC.

8. The method of claim 7, wherein the control signaling includes a DCI, the DCI (i) indicating the association between the downlink CC and the uplink CC, and (ii) scheduling the transmission of PDSCH on the downlink CC. The fields in the DCI indicate that the PUSCH transmission carries a HARQ-ACK feedback for one or more uplink CCs in the uplink CCs, and the PUSCH transmission is scheduled on the uplink CC associated with the downlink CC on which the PDSCH transmission is received.

9. The method of claim 8, wherein the DCI comprises a downlink allocation indicator (DAI) and a K1 offset value indicating the number of bits to be reported in the uplink slot, wherein the DAI increments across all downlink CCs corresponding to the uplink CCs on which the PUSCH is scheduled to be transmitted.

10. The method according to claim 1, further comprising: The priority of a PUSCH resource is determined based on at least one of the following: (i) the priority of the uplink data carried by the PUSCH resource or (ii) the priority of the HARQ-ACK feedback carried by the PUSCH resource, wherein the priority of the HARQ-ACK feedback corresponds to the priority of the uplink data. as well as When the sum of transmission power across multiple serving cells exceeds a threshold, PUSCH transmissions with lower priority are discarded.

11. The method of claim 1, wherein the control signaling configuration is used to trigger a timer and one or more thresholds for an event-driven CSI report, wherein the timer is reset after the event-driven CSI report is sent.

12. The method of claim 1, wherein receiving the control signaling configuring the one or more parameters for UCI reporting on PUSCH resources includes receiving network indications for the one or more parameters to be used for overlap resolution and resource selection, and The control signaling further indicates the set of UCI types to be multiplexed on the one or more PUSCH resources selected for transmitting the UCI.

13. A method, the method comprising: Send control signaling that configures one or more parameters for UCI reporting on PUSCH resources; The mapping between at least one downlink CC and at least one uplink CC is determined based on one or more parameters configured for UCI reporting on PUSCH resources; as well as UCI is received at least based on the determined mapping via one or more PUSCH resources associated with the at least one uplink CC.

14. The method of claim 13, wherein the UCI comprises at least one of a P-CSI report, an A-CSI report, an event-triggered CSI report, a HARQ-ACK feedback, or a scheduling request (SR), and The control signaling configured event-triggered CSI reporting on one or more PUSCH resources.

15. The method of claim 13, further comprising receiving capability signaling, the capability signaling indicating at least one of the following: (i) the number of valid uplink CCs that can be reported for P-CSI on PUSCH resources per time slot, (ii) the maximum number of valid uplink CCs with P-CSI reports on PUSCH resources, or (iii) the number of downlink CCs that can be measured and reported on a single uplink CC. The capability signaling indicates that more than one downlink CC can be measured and reported on a single uplink CC.

16. The method of claim 13, wherein the control signaling configures multiple CSI-ReportConfigId Values, each associated with a different downlink CC, Each of them CSI-ReportConfigId The value is associated with at most one valid periodic CSI report.

17. The method of claim 13, wherein the control signaling indicates a CG PUSCH resource to be used for P-CSI reporting. The identifier or configuration of the CG PUSCH resource is determined by... ServingCellConfig IE CSI-MeasConfig Fields, as described CSI-MeasConfig Fields CSI-ReportConfig Subfield or the described ServingCellConfig In IE uplinkConfig At least one of the fields must be provided.

18. The method of claim 13, wherein the one or more parameters include a list of CG PUSCH identifiers or configurations configured for P-CSI reporting per serving cell. This provides a list of CG PUSCH identifiers or configurations for each uplink BWP, and Each serving cell is configured with a single CG PUSCH resource for a specific uplink BWP, and the CG PUSCH resource is activated when the specific uplink BWP is active.

19. The method of claim 13, wherein the control signaling includes a DCI indicating an association between a downlink CC and an uplink CC, and a field in the DCI instructs the PUSCH to send a HARQ-ACK feedback carrying for one or more uplink CCs. The DCI includes a DAI and a K1 offset value indicating the number of bits to be reported in the uplink slot, wherein the DAI increments across all downlink CCs corresponding to the uplink CCs on which the PUSCH is scheduled to be transmitted.

20. An apparatus comprising: One or more processors; as well as A memory that stores instructions that, when executed by the one or more processors, cause the device to perform operations including: Receive control signaling, which configures one or more parameters for uplink control information (UCI) reporting on Physical Uplink Shared Channel (PUSCH) resources; The mapping between at least one downlink component carrier (CC) and at least one uplink CC is determined based on one or more parameters configured for UCI reporting on PUSCH resources; as well as UCI is sent via one or more PUSCH resources associated with at least one uplink CC, based at least on the determined mapping.

21. The apparatus of claim 20, wherein the UCI includes at least one of periodic channel state information (P-CSI) report, aperiodic channel state information (A-CSI) report, event-triggered CSI report, hybrid automatic repeat request (HARQ) acknowledgment (ACK) feedback or scheduling request (SR), and wherein the control signaling configures event-triggered CSI report on the one or more PUSCH resources.

22. The apparatus of claim 20, wherein the instruction causes the apparatus to further perform the operation of: sending capability signaling indicating at least one of the following: (i) the number of valid uplink CCs that can be reported for P-CSI on PUSCH resources per time slot, (ii) the maximum number of valid uplink CCs reported for P-CSI on PUSCH resources, or (iii) the number of downlink CCs that can be measured and reported on a single uplink CC, wherein the capability signaling indicates that more than one downlink CC can be measured and reported on a single uplink CC.

23. The apparatus of claim 20, wherein the control signaling is configured with a plurality of CSI-ReportConfigId Values, each associated with a different downlink CC, and each of them CSI-ReportConfigId The value is associated with at most one valid periodic CSI report, and The control signaling indicates the configuration permission (CG)PUSCH resource to be used for P-CSI reporting, and the identifier or configuration of the CGPUSCH resource is determined by... ServingCellConfig IE CSI-MeasConfig Fields, the described CSI- MeasConfig Within the field CSI-ReportConfig Subfield or the described ServingCellConfig In IE uplinkConfig At least one of the fields must be provided.

24. The apparatus of claim 20, wherein the one or more parameters include a list of CG PUSCH identifiers or configurations configured for P-CSI reporting per serving cell. This provides a list of CG PUSCH identifiers or configurations for each uplink bandwidth portion (BWP), and Each serving cell is configured with a single CG PUSCH resource for a specific uplink BWP, and the CG PUSCH resource is activated when the specific uplink BWP is active.

25. The apparatus of claim 20, wherein determining the mapping includes receiving, via the control signaling, a mapping between a downlink CC and an uplink CC, a mapping between more than one downlink CC and an uplink CC, a mapping between one downlink CC and more than one uplink CC, or a mapping between more than one downlink CC and more than one uplink CC.

26. The apparatus of claim 25, wherein the control signaling includes a DCI, the DCI (i) indicating the association between a downlink CC and an uplink CC, and (ii) scheduling the transmission of a PDSCH on the downlink CC. The fields in the DCI indicate that the PUSCH transmission carries a HARQ-ACK feedback for one or more uplink CCs in the uplink CCs, and the PUSCH transmission is scheduled on the uplink CC associated with the downlink CC on which the PDSCH transmission is received.

27. The apparatus of claim 26, wherein the DCI includes a downlink allocation indicator (DAI) and a K1 offset value indicating the number of bits to be reported in the uplink slot, wherein the DAI increments across all downlink CCs corresponding to the uplink CCs on which the PUSCH is scheduled to be transmitted.

28. An apparatus comprising: One or more processors; as well as A memory that stores instructions that, when executed by the one or more processors, cause the device to perform operations including: Send control signaling that configures one or more parameters for UCI reporting on PUSCH resources; The mapping between at least one downlink CC and at least one uplink CC is determined based on one or more parameters configured for UCI reporting on PUSCH resources; as well as UCI is received at least based on the determined mapping via one or more PUSCH resources associated with the at least one uplink CC.

29. The apparatus of claim 28, wherein the instruction causes the apparatus to further perform the operation of: receiving capability signaling, the capability signaling indicating at least one of the following: (i) the number of valid uplink CCs that can be reported for P-CSI on PUSCH resources per time slot, (ii) the maximum number of valid uplink CCs with P-CSI reports on PUSCH resources, or (iii) the number of downlink CCs that can be measured and reported on a single uplink CC. The capability signaling indicates that more than one downlink CC can be measured and reported on a single uplink CC.

30. The apparatus of claim 28, wherein the control signaling includes a DCI indicating an association between a downlink CC and an uplink CC, and a field in the DCI instructs the PUSCH to send a HARQ-ACK feedback carrying for one or more uplink CCs. The DCI includes a DAI and a K1 offset value indicating the number of bits to be reported in the uplink slot, wherein the DAI increments across all downlink CCs corresponding to the uplink CCs on which the PUSCH is scheduled to be transmitted.

Images