Uplink control information carrier switching

Abstract

Aspects relate to component carriers associated with an uplink control channel group. In some examples, data may be communicated on one of the component carriers and feedback about the data may be communicated on another of the component carriers.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This patent application claims priority to and the benefit of pending Greek patent application No. 20210100318, filed May 11, 2021, entitled “UPLINK CONTROL INFORMATION CARRIER SWITCH,” which is assigned to the assignee of the present application and is expressly incorporated herein by reference as if fully set forth below in its entirety and for all applicable purposes.

[0002] TECHNICAL FIELD The technology described below relates generally to wireless communications, and more particularly, to switching transmission of uplink control information between different carriers. [Background technology]

[0003] Next-generation wireless communication systems (e.g., 5GS) may include a 5G core network and a 5G radio access network (RAN), such as a new radio (NR)-RAN. The NR-RAN supports communication over one or more cells. For example, a wireless communication device, such as a user equipment (UE), may access a first cell of a first base station (BS), such as a gNB, and / or access a second cell of a second base station.

[0004] A base station may schedule access to a cell to support access by multiple UEs. For example, the base station may allocate different resources (e.g., time domain resources and frequency domain resources) to be used by different UEs operating in the cell. In some examples, the base station may send downlink control information (DCI) to the UE, which identifies resources to be used for downlink transmissions to the UE or uplink transmissions from the UE, as well as other information that the UE can use to receive downlink transmissions or send uplink transmissions. Summary of the Invention [Means for solving the problem]

[0005] The following presents a summary of one or more aspects of the present disclosure in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated features of the disclosure, nor is it intended to identify key or critical elements of all aspects of the disclosure, nor is it intended to delineate the scope of any or all aspects of the disclosure. Its sole purpose is to present some concepts of one or more aspects of the disclosure as a prelude to the more detailed description that is presented later.

[0006] In some examples, a user equipment may include a transceiver, a memory, and a processor coupled to the transceiver and the memory. The processor and memory may be configured to receive data on a first component carrier of a plurality of component carriers. In some examples, the plurality of component carriers are associated with an uplink control channel group. The processor and memory may also be configured to receive a first indication that the user equipment is permitted to transmit feedback about the data on a second component carrier of the plurality of component carriers.

[0007] In some examples, a method for wireless communication in a user equipment is disclosed. The method may include receiving data on a first component carrier of a plurality of component carriers. In some examples, the plurality of component carriers are associated with an uplink control channel group. The method may also include receiving a first indication that the user equipment is permitted to transmit feedback about the data on a second component carrier of the plurality of component carriers.

[0008] In some examples, the user equipment may include means for receiving data on a first component carrier of the plurality of component carriers. In some examples, the plurality of component carriers are associated with an uplink control channel group. The user equipment may also include means for receiving a first indication that the user equipment is authorized to transmit feedback about the data on a second component carrier of the plurality of component carriers.

[0009] In some examples, an article of manufacture for use by a user equipment includes a non-transitory computer-readable medium having stored thereon instructions executable by one or more processors of the user equipment to receive data on a first component carrier of a plurality of component carriers. In some examples, the plurality of component carriers are associated with an uplink control channel group. The computer-readable medium may also store thereon instructions executable by one or more processors of the user equipment to receive a first indication that the user equipment is authorized to transmit feedback about the data on a second component carrier of the plurality of component carriers.

[0010] In some examples, the network entity may include a transceiver, a memory, and a processor coupled to the transceiver and the memory. The processor and memory may be configured to transmit data to a user equipment on a first component carrier of the multiple component carriers. In some examples, the multiple component carriers are associated with an uplink control channel group. The processor and memory may also be configured to transmit a first indication that the user equipment is permitted to transmit feedback about the data on a second component carrier of the multiple component carriers.

[0011] In some examples, a method for wireless communication in a network entity is disclosed. The method may include transmitting data to a user equipment on a first component carrier of a plurality of component carriers. In some examples, the plurality of component carriers are associated with an uplink control channel group. The method may also include transmitting a first indication that the user equipment is permitted to transmit feedback about the data on a second component carrier of the plurality of component carriers.

[0012] In some examples, the network entity may include means for transmitting data to the user equipment on a first component carrier of the plurality of component carriers. In some examples, the plurality of component carriers are associated with an uplink control channel group. The network entity may also include means for transmitting a first indication that the user equipment is permitted to transmit feedback about the data on a second component carrier of the plurality of component carriers.

[0013] In some examples, an article of manufacture for use by a network entity includes a non-transitory computer-readable medium having stored thereon instructions executable by one or more processors of the network entity to transmit data to a user equipment on a first component carrier of a plurality of component carriers. In some examples, the plurality of component carriers are associated with an uplink control channel group. The computer-readable medium may also store thereon instructions executable by one or more processors of the network entity to transmit a first indication that the user equipment is permitted to transmit feedback about the data on a second component carrier of the plurality of component carriers.

[0014] In some examples, the user equipment may include a transceiver, a memory, and a processor coupled to the transceiver and the memory. The processor and memory may be configured to receive data on a first component carrier of the multiple component carriers. In some examples, the multiple component carriers are associated with an uplink control channel group. The processor and memory may also be configured to receive a first resource assignment. In some examples, the first resource assignment is for transmitting feedback about the data on the first component carrier. The processor and memory may further be configured to receive a second resource assignment. In some examples, the second resource assignment is for transmitting feedback about the data on a second component carrier of the multiple component carriers.

[0015] In some examples, a method for wireless communication in a user equipment is disclosed. The method may include receiving data on a first component carrier of a plurality of component carriers. In some examples, the plurality of component carriers are associated with an uplink control channel group. The method may also include receiving a first resource assignment. In some examples, the first resource assignment is for transmitting feedback about the data on the first component carrier. The method may further include receiving a second resource assignment. In some examples, the second resource assignment is for transmitting feedback about the data on a second component carrier of the plurality of component carriers.

[0016] In some examples, the user equipment may include means for receiving data on a first component carrier of the plurality of component carriers. In some examples, the plurality of component carriers are associated with an uplink control channel group. The user equipment may also include means for receiving a first resource assignment. In some examples, the first resource assignment is for transmitting feedback about the data on the first component carrier. The user equipment may further include means for receiving a second resource assignment. In some examples, the second resource assignment is for transmitting feedback about the data on a second component carrier of the plurality of component carriers.

[0017] In some examples, an article of manufacture for use by a user equipment includes a non-transitory computer-readable medium having stored thereon instructions executable by one or more processors of the user equipment to receive data on a first component carrier of a plurality of component carriers. In some examples, the plurality of component carriers are associated with an uplink control channel group. The computer-readable medium may also store instructions executable by one or more processors of the user equipment to receive a first resource allocation. In some examples, the first resource allocation is for transmitting feedback about the data on the first component carrier. The computer-readable medium may further store instructions executable by one or more processors of the user equipment to receive a second resource allocation. In some examples, the second resource allocation is for transmitting feedback about the data on a second component carrier of the plurality of component carriers.

[0018] In some examples, the network entity may include a transceiver, a memory, and a processor coupled to the transceiver and the memory. The processor and memory may be configured to transmit data on a first component carrier of the multiple component carriers. In some examples, the multiple component carriers are associated with an uplink control channel group. The processor and memory may also be configured to transmit a first resource assignment. In some examples, the first resource assignment is for transmitting feedback about the data on the first component carrier. The processor and memory may be further configured to transmit a second resource assignment. In some examples, the second resource assignment is for transmitting feedback about the data on a second component carrier of the multiple component carriers.

[0019] In some examples, a method for wireless communication in a network entity is disclosed. The method may include transmitting data on a first component carrier of a plurality of component carriers. In some examples, the plurality of component carriers are associated with an uplink control channel group. The method may also include transmitting a first resource assignment. In some examples, the first resource assignment is for transmitting feedback about the data on the first component carrier. The method may further include transmitting a second resource assignment. In some examples, the second resource assignment is for transmitting feedback about the data on a second component carrier of the plurality of component carriers.

[0020] In some examples, the network entity may include means for transmitting data on a first component carrier of the plurality of component carriers. In some examples, the plurality of component carriers are associated with an uplink control channel group. The network entity may also include means for transmitting a first resource assignment. In some examples, the first resource assignment is for transmitting feedback about the data on the first component carrier. The network entity may further include means for transmitting a second resource assignment. In some examples, the second resource assignment is for transmitting feedback about the data on a second component carrier of the plurality of component carriers.

[0021] In some examples, an article of manufacture for use by a network entity includes a non-transitory computer-readable medium having stored thereon instructions executable by one or more processors of the network entity to transmit data on a first component carrier of a plurality of component carriers. In some examples, the plurality of component carriers are associated with an uplink control channel group. The computer-readable medium may also store instructions executable by one or more processors of the network entity to transmit a first resource allocation. In some examples, the first resource allocation is for transmitting feedback about the data on the first component carrier. The computer-readable medium may further store instructions executable by one or more processors of the network entity to transmit a second resource allocation. In some examples, the second resource allocation is for transmitting feedback about the data on a second component carrier of the plurality of component carriers.

[0022] In some examples, a user equipment may include a transceiver, a memory, and a processor coupled to the transceiver and the memory. The processor and memory may be configured to receive data on a first component carrier of a plurality of component carriers. In some examples, the plurality of component carriers are associated with an uplink control channel group. The processor and memory may also be configured to select a physical uplink control channel (PUCCH) resource on a second component carrier of the plurality of component carriers for transmitting feedback about the data. The processor and memory may be further configured to selectively transmit the feedback in parallel with the uplink information based on whether parallel uplink transmission is enabled after selection of the PUCCH resource on the second component carrier.

[0023] In some examples, a method for wireless communication in a user equipment is disclosed. The method may include receiving data on a first component carrier of a plurality of component carriers. In some examples, the plurality of component carriers are associated with an uplink control channel group. The method may also include selecting a physical uplink control channel (PUCCH) resource on a second component carrier of the plurality of component carriers for transmitting feedback about the data. The method may further include, after selecting a PUCCH resource on the second component carrier, selectively transmitting the feedback in parallel with the uplink information based on whether parallel uplink transmission is enabled.

[0024] In some examples, the user equipment may include means for receiving data on a first component carrier of the multiple component carriers. In some examples, the multiple component carriers are associated with an uplink control channel group. The user equipment may also include means for selecting a physical uplink control channel (PUCCH) resource on a second component carrier of the multiple component carriers for transmitting feedback about the data. The user equipment may further include means for selectively transmitting the feedback in parallel with the uplink information based on whether parallel uplink transmission is enabled after selecting the PUCCH resource on the second component carrier.

[0025] In some examples, an article of manufacture for use by a user equipment includes a non-transitory computer-readable medium having stored thereon instructions executable by one or more processors of the user equipment to receive data on a first component carrier of a plurality of component carriers. In some examples, the plurality of component carriers are associated with an uplink control channel group. The computer-readable medium may also store instructions executable by one or more processors of the user equipment to select a physical uplink control channel (PUCCH) resource on a second component carrier of the plurality of component carriers for transmitting feedback about the data. The computer-readable medium may further store instructions executable by one or more processors of the user equipment to selectively transmit feedback in parallel with uplink information based on whether parallel uplink transmission is enabled after selection of a PUCCH resource on the second component carrier.

[0026] In some examples, the network entity may include a transceiver, a memory, and a processor coupled to the transceiver and the memory. The processor and memory may be configured to transmit data on a first component carrier of a plurality of component carriers. In some examples, the plurality of component carriers are associated with an uplink control channel group. The processor and memory may also be configured to identify a physical uplink control channel (PUCCH) resource on a second component carrier of the plurality of component carriers for transmitting feedback about the data by the user equipment. The processor and memory may be further configured to selectively receive feedback in parallel with the uplink information based on whether parallel uplink transmission is enabled after identifying the PUCCH resource on the second component carrier.

[0027] In some examples, a method for wireless communication in a network entity is disclosed. The method may include transmitting data on a first component carrier of a plurality of component carriers. In some examples, the plurality of component carriers are associated with an uplink control channel group. The method may also include identifying a physical uplink control channel (PUCCH) resource on a second component carrier of the plurality of component carriers for transmitting feedback about the data by the user equipment. The method may further include, after identifying the PUCCH resource on the second component carrier, selectively receiving feedback in parallel with the uplink information based on whether parallel uplink transmission is enabled.

[0028] In some examples, the network entity may include means for transmitting data on a first component carrier of a plurality of component carriers. In some examples, the plurality of component carriers are associated with an uplink control channel group. The network entity may include means for identifying a physical uplink control channel (PUCCH) resource on a second component carrier of the plurality of component carriers for transmitting feedback about the data by the user equipment, and means for selectively receiving the feedback in parallel with the uplink information based on whether parallel uplink transmission is enabled after identifying the PUCCH resource on the second component carrier.

[0029] In some examples, an article of manufacture for use by a network entity includes a non-transitory computer-readable medium having stored thereon instructions executable by one or more processors of the network entity to transmit data on a first component carrier of a plurality of component carriers. In some examples, the plurality of component carriers are associated with an uplink control channel group. The computer-readable medium may also store instructions executable by one or more processors of the network entity to identify a physical uplink control channel (PUCCH) resource on a second component carrier of the plurality of component carriers for transmitting feedback about the data by the user equipment. The computer-readable medium may also store instructions executable by one or more processors of the network entity to selectively receive feedback in parallel with the uplink information based on whether parallel uplink transmission is enabled after identification of the PUCCH resource on the second component carrier.

[0030] These and other aspects of the present disclosure will be more fully understood upon consideration of the detailed description below. Other aspects, features, and examples of the present disclosure will become apparent to those skilled in the art upon consideration of the following description of certain exemplary embodiments of the present disclosure together with the accompanying figures. Although the features of the present disclosure may be described with respect to some examples and figures below, all examples of the present disclosure may include one or more of the advantageous features described herein. In other words, although one or more examples may be described as having some advantageous features, one or more of such features may also be used in accordance with various examples of the present disclosure described herein. Similarly, although exemplary embodiments may be described below as examples of devices, systems, or methods, it should be understood that such exemplary embodiments may be implemented in various devices, systems, and methods. [Brief description of the drawings]

[0031] [Figure 1] FIG. 1 is a schematic diagram of a wireless communication system, according to some aspects. [Diagram 2] FIG. 1 is a conceptual diagram of an example radio access network, in accordance with some aspects. [Diagram 3] 1 is a schematic diagram of wireless resources in an air interface utilizing Orthogonal Frequency Division Multiplexing (OFDM), in accordance with some aspects. [Figure 4] 1 provides a high-level view of an example of a configuration of a non-aggregated base station, in accordance with some aspects. [Diagram 5] 1 is a signaling diagram illustrating an example of Physical Downlink Shared Channel (PDSCH) related signaling, in accordance with some aspects. [Figure 6] FIG. 1 is a conceptual diagram of an example of wireless communication over multiple radio frequency (RF) carriers, according to some aspects. [Figure 7] 1 is a conceptual diagram of an example of physical uplink control channel (PUCCH) scheduling, in accordance with some aspects. [Figure 8]1 is a conceptual diagram of an example of PUCCH carrier switching, in accordance with some aspects. [Figure 9] 1 is a conceptual diagram of another example of PUCCH carrier switching, in accordance with some aspects. [Figure 10] 1 is a conceptual diagram of another example of PUCCH carrier switching, in accordance with some aspects. [Figure 11] 1 is a conceptual diagram of an example of PUCCH carrier switching and parallel transmission, in accordance with some aspects. [Figure 12] 1 is a conceptual diagram of an example of restricted PUCCH carrier switching, in accordance with some aspects. [Figure 13] 1 is a signaling diagram illustrating an example of PDSCH-related signaling, in accordance with some aspects. [Figure 14] FIG. 2 is a block diagram conceptually illustrating an example of a hardware implementation for a user equipment employing a processing system, in accordance with some aspects. [Figure 15] 1 is a flowchart illustrating an example wireless communication method for feedback transmission, according to some aspects. [Figure 16] 1 is a flowchart illustrating an example wireless communication method regarding resource allocation for feedback transmission, according to some aspects. [Figure 17] 1 is a flowchart illustrating an example wireless communication method regarding PUCCH resources for feedback transmission, in accordance with certain aspects. [Figure 18] 1 is a flowchart illustrating an example wireless communication method for selective feedback transmission, according to some aspects. [Figure 19] 1 is a block diagram conceptually illustrating an example of a hardware implementation for a network entity employing a processing system, in accordance with some aspects. [Figure 20] 1 is a flowchart illustrating an example wireless communication method for feedback transmission, according to some aspects. [Figure 21]1 is a flowchart illustrating an example wireless communication method regarding resource allocation for feedback transmission, according to some aspects. [Figure 22] 1 is a flowchart illustrating an example wireless communication method regarding PUCCH resources for feedback transmission, in accordance with certain aspects. [Figure 23] 1 is a flowchart illustrating an example wireless communication method for selective feedback reception, according to some aspects. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0032] The detailed description set forth below with reference to the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0033] Although aspects and examples are described in this application by illustrating some examples, those skilled in the art will understand that additional implementations and use cases may arise in many different configurations and scenarios. The innovations described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging configurations. For example, aspects and / or applications may arise with integrated chip examples and other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence-enabled (AI-enabled) devices, etc.). Some examples may or may not be specifically targeted to a use case or application, but a wide variety of applicability of the described innovations may arise. Implementations may range from chip-level or modular components to non-modular, non-chip-level implementations, and even aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also necessarily include additional components and features for the implementation and practice of the claims and described examples. For example, the transmission and reception of wireless signals necessarily includes several components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). It is contemplated that the innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed configurations, non-aggregated configurations (e.g., base stations and / or UEs), end-user devices, etc. of various sizes, shapes, and configurations.

[0034] Various aspects of the present disclosure relate to dynamically selecting a component carrier to be used to transmit uplink control information. This selection process may be referred to as uplink control information carrier switching. For example, to enable uplink control information such as Physical Uplink Control Channel (PUCCH) feedback to be transmitted as soon as possible (e.g., in the case of time-sensitive communications such as Extended Industrial Internet of Things (IIoT) traffic and / or Ultra-Reliable Low Latency Communications (URLLC) traffic), a UE may transmit uplink control information on a carrier different from the carrier used to receive the data for which feedback is being sent.

[0035] In an uplink carrier aggregation configuration, a UE may receive data from a network entity, such as a base station, on a physical downlink shared channel (PDSCH) of a primary component carrier during a particular slot. In addition, the UE may be instructed (e.g., via downlink control information) to transmit Hybrid Automatic Repeat Request (HARQ) ACK / NAK feedback in a subsequent slot. In a scenario where no uplink or special slots are available on the primary component carrier for some slots, it may be beneficial to transmit HARQ ACK / NAK feedback instead on a secondary component carrier configured with earlier uplink or special slots.

[0036] Such uplink control information (e.g., PUCCH) carrier switching may be configured in different ways in different examples. In some examples, each component carrier may be independently configured for uplink control information carrier switching (e.g., by Radio Resource Control (RRC) signaling). In some examples, uplink resources per component carrier may be independently configured for uplink control information carrier switching (e.g., by RRC signaling).

[0037] Parallel uplink transmission may be enabled (e.g., configured) or not enabled (e.g., not configured) in the UE. In some examples (e.g., the UE is configured to perform parallel uplink transmission), the UE may first select a carrier for transmitting uplink control information and then perform parallel transmission of the PUCCH and a physical uplink shared channel (PUSCH). Similarly, in some examples (e.g., the UE is not configured to perform parallel uplink transmission), the UE may first select a carrier for transmitting uplink control information and then perform multiplexing of the PUCCH and the PUSCH.

[0038] In some examples, the UE may prioritize a primary component carrier for transmitting uplink control information. For example, the UE may first determine whether a slot designated for transmission of feedback is available for uplink transmission on the primary component carrier (e.g., that slot on the primary component carrier is not scheduled for downlink transmission). If the slot is available, the UE uses the primary component carrier to transmit the feedback. If the slot is not available on the primary component carrier, the UE uses a designated secondary component carrier to transmit the feedback if that slot on that component carrier is available for uplink transmission. In some examples, the UE is permitted to use only one secondary component carrier to transmit this feedback (i.e., the UE does not verify whether the UE can transmit feedback on any other secondary component carrier).

[0039] Various concepts presented throughout this disclosure may be implemented across a wide variety of telecommunications systems, network architectures, and communication standards. Referring now to FIG. 1, various aspects of the present disclosure are illustrated with respect to a wireless communication system 100 as a non-limiting illustrative example. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. The wireless communication system 100 may enable the UE 106 to conduct data communications with an external data network 110, such as (but not limited to) the Internet.

[0040] The RAN 104 may implement any suitable wireless communication technology or technologies for providing radio access to the UEs 106. As an example, the RAN 104 may operate in accordance with the 3rd Generation Partnership Project (3GPP®) New Radio (NR) specification, often referred to as 5G. As another example, the RAN 104 may operate under a hybrid of 5G NR and evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, often referred to as Long Term Evolution (LTE). 3GPP refers to this hybrid RAN as Next Generation RAN or NG-RAN. In another example, the RAN 104 may operate in accordance with both LTE and 5G NR standards. Of course, many other examples may be utilized within the scope of this disclosure.

[0041] As shown, the RAN 104 includes multiple base stations 108. Generally, a base station is a network element in a radio access network responsible for radio transmission and radio reception in one or more cells to and from UEs. In different technologies, standards, or contexts, a base station may be variously referred to by those skilled in the art as a base transceiver station (BTS), radio base station, radio transceiver, transceiver function, basic service set (BSS), enhanced service set (ESS), access point (AP), Node B (NB), eNode B (eNB), gNode B (gNB), transmit receiving point (TRP), or some other suitable term. In some examples, a base station may include two or more TRPs, which may be collocated or non-collocated. Each TRP may communicate on the same or different carrier frequencies in the same or different frequency bands. In examples where the RAN 104 operates according to both LTE and 5G NR standards, one of the base stations 108 may be an LTE base station and another base station may be a 5G NR base station.

[0042] Further shown is a radio access network 104 supporting wireless communication for a plurality of mobile devices. The mobile devices may be referred to as user equipment (UE) 106 in 3GPP standards, but may also be referred to by those skilled in the art as mobile stations (MS), subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals (ATs), mobile terminals, wireless terminals, remote terminals, handsets, terminals, user agents, mobile clients, clients, or any other suitable terminology. The UE 106 may be a device that provides a user with access to network services. In an example where the RAN 104 operates according to both LTE and 5G NR standards, the UE 106 may be an Evolved-Universal Terrestrial Radio Access Network - New Radio dual connectivity (EN-DC) UE that is capable of simultaneously connecting to an LTE base station and an NR base station to receive data packets from both the LTE base station and the NR base station.

[0043] In this document, a mobile device does not necessarily have to have the ability to move and may be stationary. The term mobile device or mobile device broadly refers to a wide variety of devices and technologies. A UE may include several hardware structural components sized, shaped, and configured to facilitate communication, such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile, cellular (cell) phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablets, personal digital assistants (PDAs), and a wide range of embedded systems, for example, those that support the Internet of Things (IoT).

[0044] In addition, the mobile device may be an automobile or other transportation vehicle, a remote sensor or actuator, a robot or robotics device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multicopter, a quadcopter, a remote control device, a consumer and / or wearable device, such as eyewear, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., MP3 player), a camera, a game console, etc. In addition, the mobile device may be a home audio, video, and / or multimedia device, a digital home or smart home device, such as an appliance, a vending machine, an intelligent lighting, a home security system, a smart meter, etc. In addition, the mobile device may be a smart energy device, a security device, a solar panel or solar array, a city infrastructure device controlling power (e.g., smart grid), lighting, water, etc., an industrial automation and enterprise device, a logistics controller, an agricultural equipment, etc. Still further, the mobile device may provide support for connected medicine or telemedicine, i.e., remote healthcare. Telehealth devices may include telehealth monitoring devices and telehealth management devices, whose communications may be given preferential treatment or prioritized access over other types of information, e.g., with respect to prioritized access for the transport of critical service data and / or associated QoS for the transport of critical service data.

[0045] The wireless communication between the RAN 104 and the UE 106 may be described as utilizing an air interface. A transmission over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) may be referred to as a downlink (DL) transmission. In some examples, the term downlink may refer to a point-to-multipoint transmission originating at a base station (e.g., base station 108). Another way to describe this point-to-multipoint transmission scheme may be to use the term broadcast channel multiplexing. A transmission from a UE (e.g., UE 106) to a base station (e.g., base station 108) may be referred to as an uplink (UL) transmission. In some examples, the term uplink may refer to a point-to-point transmission originating at a UE (e.g., UE 106).

[0046] In some examples, access to the air interface may be scheduled, and a scheduling entity of some other type of network entity (e.g., base station 108) allocates resources for communication among some or all devices and equipment within its service area or cell. Within this disclosure, as described further below, the scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more scheduled entities (e.g., UEs). That is, for scheduled communication, multiple UEs 106, which may be scheduled entities, may utilize resources allocated by the scheduling entity (e.g., base station 108).

[0047] The base station 108 is not the only entity that may act as a scheduling entity. That is, in some examples, a UE may act as a scheduling entity that schedules resources for one or more scheduled entities (e.g., one or more other UEs). For example, a UE may communicate with other UEs in a peer-to-peer or device-to-device manner and / or in a relay configuration.

[0048] 1, a scheduling entity (e.g., a base station 108) may broadcast downlink traffic 112 to one or more scheduled entities (e.g., UEs 106). Generally, a scheduling entity is a node or device responsible for scheduling traffic in a wireless communication network, including the downlink traffic 112 and, in some examples, uplink traffic 116 and / or uplink control information 118 from one or more scheduled entities to the scheduling entity. A scheduled entity, on the other hand, is a node or device that receives downlink control information 114, including scheduling information (e.g., grants), synchronization or timing information, or other control information, from another entity in the wireless communication network, such as, but not limited to, the scheduling entity.

[0049] In addition, the uplink control information 118, the downlink control information 114, the downlink traffic 112, and / or the uplink traffic 116 may be time-divided into frames, subframes, slots, and / or symbols. As used herein, a symbol may refer to a unit of time that carries one resource element (RE) per subcarrier in an orthogonal frequency division multiplexing (OFDM) waveform. A slot may carry, in some examples, 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 millisecond (ms). Multiple subframes or slots may be grouped together to form a single frame or radio frame. Within this disclosure, a frame may refer to a predetermined duration (e.g., 10 ms) for wireless transmission, with each frame consisting of, for example, 10 subframes of 1 ms each. Of course, these definitions are not required and any suitable scheme for organizing the waveform may be utilized, and the various time divisions of the waveform may have any suitable duration.

[0050] In general, the base stations 108 may include a backhaul interface for communication with a backhaul network 120 of a wireless communication system. The backhaul network 120 may provide a link between the base stations 108 and the core network 102. Additionally, in some examples, the backhaul network may provide interconnection between each base station 108. Various types of backhaul interfaces may be employed, such as a direct physical connection, a virtual network, etc., using any suitable transport network.

[0051] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured in accordance with a 5G standard (e.g., 5GC). In other examples, the core network 102 may be configured in accordance with a 4G Evolved Packet Core (EPC), or any other suitable standard or configuration.

[0052] 2, by way of example and not limitation, a schematic diagram of a Radio Access Network (RAN) 200 is provided. In some examples, the RAN 200 may be the same as the RAN 104 described above and shown in FIG.

[0053] The geographic area covered by the RAN 200 may be divided into cellular regions (cells), which may be uniquely identified by user equipment (UE) based on an identification broadcasted from one access point or base station. FIG. 2 shows cells 202, 204, 206, and 208, each of which may include one or more sectors (not shown). A sector is a subarea of ​​a cell. All sectors within a cell are served by the same base station. Radio links within a sector may be identified by a single logical identification belonging to that sector. In sectorized cells, multiple sectors within a cell may be formed by a group of antennas, each antenna responsible for communication with UEs in a portion of the cell.

[0054] Various base station arrangements may be utilized. For example, in FIG. 2, two base stations 210 and 212 are shown in cells 202 and 204, and a base station 214 is shown controlling a remote radio head (RRH) 216 in cell 206. That is, the base stations may have integrated antennas or may be connected to the antennas or RRHs by feeder cables. In the illustrated example, the base stations 210, 212, and 214 support cells having a large size, so the cells 202, 204, and 206 may be referred to as macro cells. Furthermore, a base station 218 is shown in a cell 208 that may overlap with one or more macro cells. In this example, the base station 218 supports a cell having a relatively small size, so the cell 208 may be referred to as a small cell (e.g., a micro cell, a pico cell, a femto cell, a home base station, a home node B, a home eNodeB, etc.). Cell sizing may be performed according to system design as well as component constraints.

[0055] It should be appreciated that the RAN 200 may include any number of wireless base stations and cells. Additionally, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. The base stations 210, 212, 214, 218 provide wireless access points to the core network for any number of mobile devices. In some examples, the base stations 210, 212, 214, and / or 218 may be the same as the base stations / scheduling entities described above and shown in FIG. 1.

[0056] 2 further includes an unmanned aerial vehicle (UAV) 220, which may be a drone or a quadcopter. The UAV 220 may be configured to function as a base station, or more specifically, as a mobile base station. That is, in some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move according to the location of a mobile base station, such as the UAV 220.

[0057] Within the RAN 200, cells may include UEs that may be in communication with one or more sectors of each cell. Additionally, each base station 210, 212, 214, and 218 may be configured to provide an access point to the core network 102 (see FIG. 1) for all UEs in the respective cell. For example, UEs 222 and 224 may be in communication with base station 210, UEs 226 and 228 may be in communication with base station 212, UEs 230 and 232 may be in communication with base station 214 via RRH 216, and UE 234 may be in communication with base station 218. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may be the same as the UE / scheduled entities described above and illustrated in FIG. 1. In some examples, UAV 220 (e.g., a quadcopter) may be a mobile network node and may be configured to function as a UE. For example, the UAV 220 may operate within the cell 202 by communicating with the base station 210 .

[0058] In further aspects of the RAN 200, sidelink signals may be used between UEs without necessarily relying on scheduling or control information from a base station. Sidelink communications may be utilized, for example, in device-to-device (D2D) networks, peer-to-peer (P2P) networks, vehicle-to-vehicle (V2V) networks, vehicle-to-everything (V2X) networks, and / or other suitable sidelink networks. For example, two or more UEs (e.g., UEs 238, 240, and 242) may communicate with each other using sidelink signals 237 without relaying the communications through a base station. In some examples, UEs 238, 240, and 242 may each function as a scheduling entity or transmitting sidelink device and / or a scheduled entity or receiving sidelink device to schedule resources and communicate sidelink signals 237 therebetween without relying on scheduling or control information from a base station. In another example, two or more UEs (e.g., UEs 226 and 228) within the coverage area of ​​a base station (e.g., base station 212) may also communicate sidelink signals 227 over a direct link (sidelink) without conducting the communications through the base station 212. In this example, the base station 212 may allocate resources to the UEs 226 and 228 for sidelink communication.

[0059] In the RAN 200, the ability of a UE to communicate while moving independent of its location is referred to as mobility. The various physical channels between the UE and the radio access network are generally set up, maintained, and released under the control of an Access and Mobility Management Function (AMF, not shown, part of the Core Network 102 in FIG. 1), which may include a Security Context Management Function (SCMF), which manages security contexts for both control plane functions and user plane functions, and a Security Anchor Function (SEAF), which performs authentication.

[0060] The RAN 200 may utilize DL-based mobility or UL-based mobility to enable mobility and handover (i.e., transition of a UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity or at any other time, a UE may monitor various parameters of a signal from its serving cell, as well as various parameters of neighboring cells. Depending on the quality of these parameters, the UE may maintain communication with one or more of the neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE may undertake a handoff or handover from the serving cell to a neighboring (target) cell. For example, a UE 224 (shown as a vehicle, although any suitable form of UE may be used) may move from a geographic area corresponding to its serving cell (e.g., cell 202) to a geographic area corresponding to a neighboring cell (e.g., cell 206). When the signal strength or quality from a neighbor cell exceeds that of the serving cell for a given amount of time, the UE 224 may send a report message indicating this condition to its serving base station (e.g., base station 210). In response, the UE 224 may receive a handover command and the UE may undergo a handover to the cell 206.

[0061] In a network configured for UL-based mobility, the UL reference signal from each UE may be utilized by the network to select a serving cell for each UE. In some examples, the base stations 210, 212, and 214 / 216 may broadcast a combined synchronization signal (e.g., a combined primary synchronization signal (PSS), a combined secondary synchronization signal (SSS), and a combined physical broadcast channel (PBCH)). The UEs 222, 224, 226, 228, 230, and 232 may receive the combined synchronization signal, derive carrier frequency and slot timing from the synchronization signal, and transmit uplink pilot or reference signals in response to the derivation of the timing. An uplink pilot signal transmitted by a UE (e.g., UE 224) may be received simultaneously by two or more cells (e.g., base stations 210 and 214 / 216) in the RAN 200. Each of the cells can measure the strength of the pilot signal, and the radio access network (e.g., one or more of the base stations 210 and 214 / 216 and / or a central node in the core network) can determine the serving cell for the UE 224. As the UE 224 moves through the RAN 200, the network can continue to monitor the uplink pilot signals transmitted by the UE 224. When the signal strength or quality of the pilot signal measured by a neighboring cell exceeds the signal strength or quality measured by the serving cell, the RAN 200 may handover the UE 224 from the serving cell to the neighboring cell, with or without notification to the UE 224.

[0062] Although the synchronization signals transmitted by base stations 210, 212, and 214 / 216 may be integrated, the synchronization signals may not identify a particular cell, but rather a zone of multiple cells operating on the same frequency and / or with the same timing. The use of zones in 5G networks or other next generation communication networks enables an uplink-based mobility framework, improving the efficiency of both the UE and the network as the number of mobility messages that need to be exchanged between the UE and the network may be reduced.

[0063] In various implementations, the air interface in the RAN 200 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum generally provides exclusive use of a portion of the spectrum by a mobile network operator purchasing a license from a government regulatory body. Unlicensed spectrum provides sharing of a portion of the spectrum without the need for a government-granted license. Compliance with some technical rules is generally still required to access unlicensed spectrum, but generally any operator or device can gain access. Shared spectrum may be in between licensed and unlicensed spectrum, and while technical rules or restrictions may be required to access the spectrum, the spectrum may still be shared by multiple operators and / or multiple radio access technologies (RATs). For example, a holder of a license to a portion of licensed spectrum may offer licensed shared access (LSA), for example, to share that spectrum with other parties under appropriate terms determined by the licensee to gain access.

[0064] The air interface in the RAN 200 may utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiple access for UL transmissions from the UEs 222 and 224 to the base station 210, as well as for multiplexing of DL transmissions from the base station 210 to one or more UEs 222 and 224, utilizing orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP). In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also referred to as single carrier FDMA (SC-FDMA)). However, within the scope of this disclosure, multiplexing and multiple access are not limited to the above schemes and may be provided utilizing time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource spread multiple access (RSMA), or other suitable multiple access schemes. Additionally, multiplexing of DL transmissions from base station 210 to UEs 222 and 224 may be done utilizing time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0065] The air interface in the RAN 200 may further utilize one or more duplexing algorithms. Duplexing refers to a point-to-point communication link in which both endpoints can communicate with each other in both directions. Full duplex means that both endpoints can communicate with each other simultaneously. Half duplex means that only one endpoint at a time can send information to the other. Half duplex emulation is frequently implemented for wireless links utilizing time division duplexing (TDD). In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, at some times the channel is dedicated to transmission in one direction, while at other times the channel is dedicated to transmission in the opposite direction, where the direction may change very rapidly, e.g., several times per slot. In wireless links, full duplex channels generally rely on physical separation of the transmitter and receiver, and appropriate interference cancellation techniques. Full duplex emulation is frequently implemented for wireless links by utilizing frequency division duplexing (FDD) or spatial division duplexing (SDD). In FDD, transmissions in different directions operate at different carrier frequencies. In SDD, transmissions in different directions on a given channel are separated from one another using spatial division multiplexing (SDM). In other examples, full-duplex communication may be implemented in an unpaired spectrum (e.g., within a single carrier bandwidth), with transmissions in different directions occurring in different sub-bands of the carrier bandwidth. This type of full-duplex communication is sometimes referred to as sub-band full duplex (SBFD), cross division duplex (xDD), or flexible duplex.

[0066] Various aspects of the present disclosure are described with reference to OFDM waveforms, an example of which is shown generally in Figure 3. It should be understood by those skilled in the art that the various aspects of the present disclosure may be applied to SC-FDMA waveforms in substantially the same manner as described herein below, i.e., while some examples of the present disclosure may focus on OFDM links for clarity, it should be understood that the same principles may also be applied to SC-FDMA waveforms.

[0067] 3, an expanded view of an example subframe 302 is shown illustrating an OFDM resource grid. However, as one skilled in the art will readily appreciate, the physical (PHY) layer transmission structure for any particular application may differ from the example described herein depending on any number of factors, where time is in units of OFDM symbols horizontally and frequency is in units of subcarriers of a carrier vertically.

[0068] The resource grid 304 may be used to generally represent time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple antenna ports available, a corresponding number of resource grids 304 may be available for communication. The resource grid 304 is divided into multiple resource elements (REs) 306. An RE, which is 1 subcarrier by 1 symbol, is the smallest individual portion of the time-frequency grid and contains a single complex value that represents data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE may represent one or more bits of information. In some examples, a block of REs may be referred to as a physical resource block (PRB) or more simply a resource block (RB) 308, which includes any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers, a number that is independent of the numerology used. In some examples, depending on the numerology, an RB may include any suitable number of consecutive OFDM symbols in the time domain. Within this disclosure, it is assumed that a single RB, such as RB 308, corresponds entirely to a single direction of communication (either transmit or receive for a given device).

[0069] A set of contiguous or non-contiguous resource blocks may be referred to herein as a resource block group (RBG), subband, or bandwidth part (BWP). A set of subbands or BWPs may span the entire bandwidth. Scheduling of a scheduled entity (e.g., a UE) for downlink, uplink, or sidelink transmission typically involves scheduling one or more resource elements 306 in one or more subbands or bandwidth parts (BWPs). Thus, a UE generally utilizes only a subset of the resource grid 304. In some examples, an RB may be the smallest unit of resource that can be allocated to a UE. Thus, the more RBs scheduled for a UE and the higher the modulation scheme chosen for the air interface, the higher the data rate for the UE. The RBs may be scheduled by a scheduling entity such as a base station (e.g., gNB, eNB, etc.) or may be self-scheduled by a UE implementing D2D sidelink communication.

[0070] In this figure, the RB 308 is shown as occupying less than the entire bandwidth of the subframe 302, with several subcarriers shown above and below the RB 308. In a given implementation, the subframe 302 may have a bandwidth corresponding to any number of one or more RBs 308. Additionally, in this figure, the RB 308 is shown as occupying less than the entire duration of the subframe 302, although this is just one possible example.

[0071] Each 1 ms subframe 302 may consist of one or more contiguous slots. In the example shown in FIG. 3, one subframe 302 includes four slots 310 as an illustrative example. In some examples, a slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include minislots, sometimes referred to as reduced transmission time intervals (TTIs), having a shorter duration (e.g., 1 to 3 OFDM symbols). These minislots or reduced transmission time intervals (TTIs) may be transmitted occupying resources scheduled for ongoing slot transmissions for the same or different UEs, as the case may be. Any number of resource blocks may be utilized within a subframe or slot.

[0072] An expanded view of one of the slots 310 shows the slot 310 including a control region 312 and a data region 314. In general, the control region 312 can carry a control channel and the data region 314 can carry a data channel. Of course, a slot may include all DL, all UL, or at least one DL portion and at least one UL portion. The structure shown in FIG. 3 is only an example, and different slot structures may be utilized and may include one or more of each of the control and data regions.

[0073] 3, various REs 306 in the RB 308 may be scheduled to carry one or more physical channels, including a control channel, a shared channel, a data channel, etc. Other REs 306 in the RB 308 may also carry pilot or reference signals. These pilot or reference signals may enable a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation / detection of the control channel and / or data channel in the RB 308.

[0074] In some examples, the slots 310 may be utilized for broadcast, multicast, groupcast, or unicast communications. For example, broadcast, multicast, or groupcast communications may refer to a point-to-multipoint transmission by one device (e.g., a base station, a UE, or other similar device) to other devices, where a broadcast communication is delivered to all devices, while a multicast or groupcast communication is delivered to multiple intended recipient devices. Unicast communications may refer to a point-to-point transmission by one device to a single other device.

[0075] In one example of cellular communication on a cellular carrier over a Uu interface, for DL ​​transmission, a scheduling entity (e.g., a base station) may allocate one or more REs 306 (e.g., in the control region 312) to carry DL control information including one or more DL control channels, such as a physical downlink control channel (PDCCH), to one or more scheduled entities (e.g., UEs). The PDCCH carries downlink control information (DCI), including, but not limited to, power control commands (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, grants, and / or allocation of REs for DL ​​and UL transmissions. The PDCCH may further carry hybrid automatic repeat request (HARQ) feedback transmissions, such as positive acknowledgements (ACKs) or negative acknowledgements (NACKs). HARQ is a technique well known to those skilled in the art, and the integrity of a packet transmission may be checked at the receiving end utilizing any suitable integrity checking mechanism, such as, for example, a checksum or a cyclic redundancy check (CRC), for accuracy. If the integrity of the transmission is confirmed, an ACK may be sent, but if not, a NACK may be sent. In response to a NACK, the transmitting device may send a HARQ retransmission, which may implement Chase combining, incremental redundancy, etc.

[0076] The base station may further allocate one or more REs 306 (e.g., in the control region 312 or data region 314) to carry other DL signals such as demodulation reference signals (DMRS), phase tracking reference signals (PT-RS), channel state information (CSI) reference signals (CSI-RS), and synchronization signal blocks (SSBs). The SSBs may be broadcast at regular intervals based on a period (e.g., 5, 10, 20, 30, 80, or 130 ms). The SSBs include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast control channel (PBCH). The UE may utilize the PSS and SSS to achieve radio frame, subframe, slot, and symbol synchronization in the time domain, identify the center of the channel (system) bandwidth in the frequency domain, and identify the physical cell identity (PCI) of the cell.

[0077] The PBCH in the SSB may further include a Master Information Block (MIB) that includes various system information along with parameters for decoding the System Information Block (SIB). The SIB may be, for example, System Information Type 1 (SIB1), which may include various additional (remaining) system information. The MIB and SIB1 together provide minimum system information (SI) for initial access. Examples of system information transmitted in the MIB may include, but are not limited to, subcarrier spacing (e.g., default downlink numerology), system frame number, configuration of the PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), cell barring indicator, cell reselection indicator, raster offset, and search space for SIB1. Examples of remaining minimum system information (RMSI) transmitted in SIB1 may include, but are not limited to, random access search space, paging search space, downlink configuration information, and uplink configuration information. The base station may also transmit other system information (OSI).

[0078] In an UL transmission, a scheduled entity (e.g., a UE) may utilize one or more REs 306 to convey UL control information (UCI) including one or more UL control channels, such as a physical uplink control channel (PUCCH), to a scheduling entity. The UCI may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding an uplink data transmission. Examples of uplink reference signals may include a sounding reference signal (SRS) and an uplink DMRS. In some examples, the UCI may include a scheduling request (SR), i.e., a request for the scheduling entity to schedule an uplink transmission. Here, in response to the SR transmitted on the UCI, the scheduling entity may transmit downlink control information (DCI) that may schedule resources for an uplink packet transmission. The UCI may also include channel condition feedback (CSF), such as HARQ feedback, CSI reporting, or any other suitable UCI.

[0079] In addition to control information, one or more REs 306 (e.g., in the data region 314) may be allocated for data traffic. Such data traffic may be carried on one or more traffic channels, such as a Physical Downlink Shared Channel (PDSCH) for DL ​​transmissions or a Physical Uplink Shared Channel (PUSCH) for UL transmissions. In some examples, one or more REs 306 in the data region 314 may be configured to carry other signals, such as one or more SIBs and a DMRS.

[0080] In one example of sidelink communication on a sidelink carrier via a Proximity Services (ProSe) PC5 interface, the control area 312 of the slot 310 may include a Physical Sidelink Control Channel (PSCCH) including sidelink control information (SCI) transmitted by an initiating (transmitting) sidelink device (e.g. a transmitting (Tx) V2X device or other Tx UE) towards a set of one or more other receiving sidelink devices (e.g. a receiving (Rx) V2X device or some other Rx UE). The data area 314 of the slot 310 may include a Physical Sidelink Shared Channel (PSSCH) including sidelink data traffic transmitted by the initiating (transmitting) sidelink device in resources reserved on the sidelink carrier by the transmitting sidelink device via the SCI. Other information may be further transmitted on various REs 306 in the slot 310. For example, HARQ feedback information may be transmitted from the receiving sidelink device to the transmitting sidelink device in a Physical Sidelink Feedback Channel (PSFCH) in the slot 310. Additionally, one or more reference signals, such as a sidelink SSB, a sidelink CSI-RS, a sidelink SRS, and / or a sidelink positioning reference signal (PRS), may be transmitted within the slot 310.

[0081] These physical channels described above are generally multiplexed and mapped to transport channels for processing at the Medium Access Control (MAC) layer. The transport channels carry blocks of information called Transport Blocks (TBs). The Transport Block Size (TBS), which may correspond to the number of bits of information, may be a controlled parameter based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission.

[0082] The channels or carriers described above with reference to Figures 1-3 are not necessarily all of the channels or carriers that may be utilized between a scheduling entity and a scheduled entity, and those skilled in the art will recognize that other channels or carriers, such as other traffic channels, control channels, and feedback channels, may be utilized in addition to those illustrated.

[0083] The deployment of a communication system such as a 5G New Radio (NR) system may be configured in multiple ways with various components or components. In a 5G NR system or network, network equipment such as a network node, a network entity, a mobility element of the network, a Radio Access Network (RAN) node, a core network node, a network element, or a base station (BS) or one or more units (or one or more components) performing a base station function may be implemented in an aggregated or non-aggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit reception point (TRP), or cell) may be implemented as an aggregated base station (also known as a standalone BS or monolithic BS) or a non-aggregated base station.

[0084] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A non-aggregated base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively may be geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0085] The operation of a base station type or network design may take into account the aggregation characteristics of the base station functions. For example, a non-aggregated base station may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as the network configuration sponsored by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Non-aggregation may include distributed functions across two or more units in various physical locations, as well as distributed functions for at least one unit, which may allow flexibility in network design, virtually. Various units of a non-aggregated base station or non-aggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0086] FIG. 4 illustrates a diagram illustrating an exemplary non-aggregated base station 400 architecture. The non-aggregated base station 400 architecture may include one or more central units (CUs) 410 that may communicate directly with the core network 420 via a backhaul link or indirectly with the core network 420 through one or more non-aggregated base station units (such as a near-real-time (Near-RT) RAN intelligent controller (RIC) 425 via an E2 link, or a non-real-time (Non-RT) RIC 415 associated with a service management and organization (SMO) framework 405, or both). The CUs 410 may communicate with one or more distributed units (DUs) 430 via respective midhaul links, such as an F1 interface. The DUs 430 may communicate with one or more radio units (RUs) 440 via respective fronthaul links. The RUs 440 may communicate with respective UEs 450 via one or more radio frequency (RF) access links. In some implementations, the UEs 450 may be served by multiple RUs 440 simultaneously.

[0087] Each of the units, i.e., CU410, DU430, RU440, and Near-RT RIC425, Non-RT RIC415, and SMO framework 405, may include one or more interfaces or may be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) over a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the unit's communication interface, may be configured to communicate with one or more of the other units over a transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals over a wired transmission medium to or from one or more of the other units. In addition, a unit may include a wireless interface, which may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive or transmit signals over a wireless transmission medium to or from one or more of the other units.

[0088] In some aspects, the CU 410 may host one or more upper layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by the CU 410. The CU 410 may be configured to handle user plane functions (i.e., central unit-user plane (CU-UP)), control plane functions (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, the CU 410 may be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP units may communicate bidirectionally with the CU-CP units via an interface, such as an E1 interface when implemented in an O-RAN configuration. The CU 410 may be implemented to communicate with a distributed unit (DU) 430, as needed, for network control and signaling.

[0089] The DU 430 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 440. In some aspects, the DU 430 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more upper physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.), at least in part according to a functional split such as that defined by the 3rd Generation Partnership Project (3GPP). In some aspects, the DU 430 may further host one or more lower PHY layers. Each layer (or module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 430 or with a control function hosted by the CU 410.

[0090] The lower layer functions may be implemented by one or more RUs 440. In some deployments, the RUs 440 controlled by the DU 430 may correspond to logical nodes hosting RF processing functions, or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split, such as a lower layer functional split. In such an architecture, the RUs 440 may be implemented to handle over-the-air (OTA) communications with one or more UEs 450. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RUs 440 may be controlled by a corresponding DU 430. In some scenarios, this configuration may enable the DUs 430 and CUs 410 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0091] The SMO framework 405 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 405 may be configured to support deployment of dedicated physical resources for RAN coverage requirements that may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 405 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 490) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, the CU 410, the DU 430, the RU 440, and the Near-RT RIC 425. In some implementations, the SMO framework 405 may communicate with hardware aspects of a 4G RAN, such as the open eNB (O-eNB) 411, via an O1 interface. Additionally, in some implementations, the SMO framework 405 can communicate directly with one or more RUs 440 via an O1 interface. The SMO framework 405 may also include a Non-RT RIC 415 configured to support the functionality of the SMO framework 405.

[0092] The Non-RT RIC 415 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / functions in the Near-RT RIC 425. The Non-RT RIC 415 may be coupled to or in communication with the Near-RT RIC 425 (such as via an A1 interface). The Near-RT RIC 425 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources through data collection and action via an interface connecting one or more CUs 410, one or more DUs 430, or both, and the O-eNB with the Near-RT RIC 425 (such as via an E2 interface).

[0093] In some implementations, the Non-RT RIC 415 may receive parameters or external enrichment information from an external server to generate an AI / ML model to be deployed in the Near-RT RIC 425. Such information may be utilized by the Near-RT RIC 425 or may be received in the SMO framework 405 or the Non-RT RIC 415 from a non-network data source or from a network function. In some examples, the Non-RT RIC 415 or the Near-RT RIC 425 may be configured to adjust RAN behavior or performance. For example, the Non-RT RIC 415 may employ the AI / ML model to monitor long-term trends and patterns in performance and take corrective action through the SMO framework 405 (e.g., reconfiguration via O1) or by creating a RAN management policy (e.g., A1 policy).

[0094] 5 is a signaling diagram 500 illustrating an example of PDSCH-related signaling in a wireless communication system including a network entity 502 and a user equipment (UE) 504. In some examples, the network entity 502 may correspond to any of the base stations, CUs, DUs, RUs, or scheduling entities shown in any of Figures 1, 2, 4, 6, 13, and 19. In some examples, the UE 504 may correspond to any of the UEs or scheduled entities shown in any of Figures 1, 2, 4, 6, 13, and 14.

[0095] 5, the network entity 502 transmits (e.g., via RRC messaging) a CORESET configuration and an SS configuration that the UE 504 should use to receive information from the network entity 502. For example, the CORESET configuration for the UE may specify the number of RBs and symbols for each CORESET configured for the UE 504. In addition, the search space (SS) configuration may specify the associated CORESET, PDCCH monitoring occasion (MO) information, PDCCH candidates, etc. for each configured SS set.

[0096] At 508, the UE 504 repeatedly monitors the configured SS set to determine if the network entity 502 has sent any messages to the UE 504. In some aspects, this may involve blind decoding of PDCCH candidates in the search space configured for the UE 504.

[0097] At some point in time, the network entity 502 schedules a PDSCH transmission for the UE 504 at 510. In some examples, the network entity 502 may schedule a PDSCH transmission and an associated PUCCH transmission (e.g., for a HARQ-Ack). Thus, at 512, the network entity 502 transmits DCI to the UE 504, which may indicate PDSCH resources for the PDSCH transmission and PUCCH resources for the HARQ-Ack. At 514, the network entity 502 transmits the PDSCH transmission to the UE 504.

[0098] At 516, the UE 504 attempts to decode the PDSCH transmission and generates a HARQ-Ack to be sent to the network entity 502 to indicate whether the UE 504 successfully received the PDSCH transmission. Accordingly, at 518, the UE 504 identifies a PUCCH resource for sending the HARQ-Ack to the network entity 502 (e.g., based on information in the DCI received at 512). At 520, the UE 504 transmits the HARQ-Ack transmission on the PUCCH resource identified at 518.

[0099] 5G-NR networks may support carrier aggregation (CA) of component carriers transmitted from different cells and / or different transmit reception points (TRPs) in a multi-cell transmission environment. Different TRPs may be associated with a single serving cell or multiple serving cells. In some aspects, the term component carrier may refer to a carrier frequency (or band) utilized for communication within a cell.

[0100] FIG. 6 is a conceptual diagram of a wireless communication system illustrating a network entity (e.g., BS) and a user equipment (UE) communicating over multiple carriers according to some aspects of the disclosure. In particular, FIG. 6 illustrates an example of a wireless communication system 600 including a primary serving cell (PCell) 602 and one or more secondary serving cells (SCells) 606a, 606b, 606c, and 606d. The PCell 602 may be referred to as an anchor cell that provides a radio resource control (RRC) connection to the UE 610. In some examples, the PCell and the SCell may be co-located (e.g., different TRPs at the same location). In some examples, the UE 610 may correspond to any of the UEs or scheduled entities illustrated in any of FIG. 1, FIG. 2, FIG. 4, FIG. 5, FIG. 13, and FIG. 14.

[0101] One or more of the SCells 606a-606d may be activated or added to the PCell 602 to form a serving cell serving the UE 610. Each serving cell corresponds to a component carrier (CC). The CC of the PCell 602 may be referred to as a primary CC, and the CC of the SCells 606a-606d may be referred to as a secondary CC. One or more of the PCell 602 and the SCells 606 may be served by a respective base station 604 and 608a-608c, similar to any of the network entities, base stations, CUs, DUs, RUs, or scheduling entities shown in any of Figures 1, 2, 4, 5, 13, and 19. In the example shown in Figure 6, the SCells 606a-606c are each served by a respective base station 608a-608c. The SCell 606d is co-located with the PCell 602. For example, the base station 604 may include multiple TRPs, each supporting a different carrier. Because component carriers in different frequency bands may experience different path losses, the coverage of the PCell 602 and the SCell 606d may be different.

[0102] In some examples, the PCell 602 may add or remove one or more of the SCells 606a-606d to improve reliability and / or increase data rates of the connection to the UE 610. The PCell 602 may be changed upon handover to another PCell.

[0103] In some examples, the PCell 602 may utilize a first radio access technology (RAT), such as LTE, while one or more of the SCells 606 may utilize a second RAT, such as 5G-NR. In this example, the multi-cell transmission environment may be referred to as a Multi-RAT-Dual Connectivity (MR-DC) environment. One example of MR-DC is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN)-New Radio (NR) Dual Connectivity (EN-DC) mode that allows a UE to simultaneously connect to an LTE base station and an NR base station to receive data packets from and send data packets to both LTE and NR base stations.

[0104] In some examples, the PCell 602 may be a low-band cell, and the SCell 606 may be a high-band cell. A low-band (LB) cell uses a CC in a frequency band lower than that of a high-band cell. For example, a high-band cell may use a millimeter-wave (mmW) CC, and a low-band cell may use a CC in a band lower than mmW (e.g., sub-6 GHz band). In general, a cell using mmW CC can provide a larger bandwidth than a cell using a low-band CC. In addition, when using a frequency carrier above 6 GHz (e.g., mmW), in some examples, beamforming may be used to transmit and receive signals.

[0105] The present disclosure relates in some aspects to physical layer feedback techniques. In some examples, these techniques may provide improved feedback that can meet, for example, Extended Industrial Internet of Things (IIOT) and Ultra-Reliable Low Latency Communications (URLLC) requirements. In some examples, this feedback may relate to PUCCH carrier switching for HARQ feedback.

[0106] In some wireless communication networks, the PUCCH is transmitted only on a Primary Component Carrier (PCC) or a PUCCH Secondary Component Carrier (SCC) in a PUCCH group in an uplink (UL) carrier aggregation (CA). This restriction may impose unnecessary extra latency and reduced reliability, especially in the TDD spectrum.

[0107] Diagram 700 of Figure 7 illustrates an example of PDSCH scheduling in a PUCCH group 702 that includes a PCC 704 and an SCC 706. As shown in Figure 7, slots on the PCC 704 and SCC 706 may be designated (e.g., configured) as downlink (D) slots, uplink (U) slots, or special (S) slots (e.g., capable of carrying uplink and / or downlink signaling). A PDSCH transmission 708 occurs during slot 710 on the PCC 704, and an associated PUCCH transmission 712 (e.g., HARQ-Ack) occurs during slot 714 on the PCC 704. In addition, parameter K1 included in the DCI that scheduled the PDSCH transmission 708 specifies a delay of two slots 716.

[0108] As shown in Figure 7, in one example of TDD+FDD CA, for a PDSCH in the first DL slot (slot 710), the UE must wait until the "S" slot (slot 714) at the earliest to feed back the HARQ-ACK in the PUCCH, because the HARQ-ACK can only be transmitted on the PUCCH. Here, the slot for transmitting the HARQ-ACK is indicated by the K1 parameter in the DCI that scheduled the PDSCH. Since K1=2 in this example, the earliest the UE can transmit the HARQ-ACK is during the UL part of the indicated special (S) slot.

[0109] However, if the restriction of allowing PUCCH only on PCC is lifted, the HARQ-ACK can be fed back on any component carrier (CC) in the PUCCH group. Thus, in this case, the UE can feed back the HARQ-ACK earlier by utilizing PUCCH resources configured on other CCs, which can reduce the HARQ-ACK delay (e.g., for URLLC, etc.), as shown in Figure 8. Moreover, by allowing the UE to switch the CC used for HARQ-ACK, the UE can select the CC with more reliability.

[0110] Diagram 800 of Figure 8 illustrates an example of PDSCH scheduling in a PUCCH group 802 that includes a PCC 804 and an SCC 806. As shown in Figure 8, slots on the PCC 804 and SCC 806 may be designated as downlink (D) slots, uplink (U) slots, or special (S) slots. A PDSCH transmission 808 occurs during slot 810 on the PCC 804, and an associated PUCCH transmission 812 (e.g., HARQ-Ack) occurs during slot 814 on the SCC 806. In this case, parameter K1 included in the DCI that scheduled the PDSCH transmission 808 may specify a shorter delay of one slot 816.

[0111] Thus, the PUCCH carrier switching scheme for HARQ-ACK may reduce HARQ-ACK feedback latency (e.g., for inter-band CA with unaligned subframe numbers (SFNs)). Thus, in some aspects, HARQ-ACK carrier switching may achieve lower latency and higher reliability, which may be important in use cases such as URLLC and IIOT.

[0112] Various techniques may be used to indicate PUCCH carrier switching for HARQ-ACK. In some examples, PUCCH carrier switching may be indicated by dynamic and explicit indication in DCI. In some examples, PUCCH carrier switching may be indicated by implicit derivation based on some static rules. Dynamic / explicit indication in DCI may have more flexibility. However, there may be reliability issues associated with such indication. Since each DCI may update the carrier on which the HARQ-ACK codebook is transmitted, if the DCI is not successfully received by the UE, the base station (e.g., gNB) does not know on which CC the HARQ-ACK is transmitted and therefore performs multiple blind detection. With UCI multiplexing on PUSCH, the problem of failed reception of DCI may be more serious if dynamic / explicit indication is applied to this feature. In some aspects, this may be more of an issue than ambiguity in HARQ-ACK codebook size due to failed reception of DCI. Regarding the HARQ-ACK codebook size issue, there is a Downlink Allocation Index (DAI) mechanism that is introduced to solve this issue (at least for the majority of scenarios, except for the scenario where, for example, all DL DCIs on all DL CCs are lost in the monitoring occasion).

[0113] On the other hand, more robust performance may be achieved if the indication is based on some static rules (e.g., implemented in the 3GPP RAN 1 specification). For PUCCH carrier switching, in some examples, the following static rules may be applied in a given slot to determine the CC for transmitting the HARQ-ACK: The lowest indexed CC with enough UL OFDM symbols to accommodate the HARQ-ACK PUCCH resources is selected to transmit the HARQ-ACK.

[0114] For PUCCH carrier switching, the slot for transmitting the HARQ-ACK follows K1 indicated in the scheduling DCI, and the granularity of K1 follows the numerology of the PCC.

[0115] The following steps may be used in an example using the static rules above. Step 1: The UE follows K1 (referring to the PCC numerology) to determine a reference slot for feeding back the HARQ-ACK. Step 2: In the determined reference slot, the UE follows a predefined order of CCs (PCC first, then SCC-1, SCC-2, etc.). If the first CC has enough UL OFDM symbols to accommodate the indicated HARQ-ACK PUCCH resource, that CC is used to transmit the HARQ ACK. If the second CC does not have enough UL OFDM symbols to accommodate the indicated HARQ-ACK PUCCH resource, the UE checks the next CC to see if it has enough UL OFDM symbols to accommodate the indicated HARQ-ACK PUCCH resource. If the next CC has enough UL OFDM symbols, the UE uses that CC to transmit the HARQ-ACK. This process may be repeated until a CC with sufficient resources is identified. The determination of whether there are enough UL OFDM symbols may be similar to an SPS ACK / NAK (A / N) deferral procedure (e.g., defer to next slot) in some examples. In a scenario where different subcarrier spacings (SCS) on different CCs are supported, if a CC includes multiple slots, each having enough UL OFDM symbols to accommodate the HARQ-ACK PUCCH resource in the determined reference slot, the earliest slot in the set of multiple slots may be selected.

[0116] Figure 9 shows an example of the above rules in a scenario of UL CA with the same numerology (SCS) on each carrier. When the UE identifies the reference slot, the UE checks the allocations in the SCCs according to the defined order to identify the SCCs that can be used to transmit the A / N. In this case, the UE transmits the A / N on SCC-1.

[0117] Diagram 900 of Figure 9 illustrates an example of PDSCH scheduling in a PUCCH group 902 that includes a PCC 904, a first SCC (SCC-1) 906, and a second SCC (SCC-2) 908. As shown in Figure 9, slots on the PCC 904, the first SCC 906, and the second SCC 908 may be designated as downlink (D) slots, uplink (U) slots, or special (S) slots. A PDSCH transmission 910 occurs during slot 912 on the PCC 904, and an associated PUCCH transmission for an A / N 914 (e.g., HARQ-Ack) occurs during slot 916 on the first SCC 906.

[0118] PUCCH carrier switching may be supported for UL CA with different numerologies (SCS) across CCs. Figure 10 shows an example of the above rules in a scenario of UL CA with different numerologies on different carriers. Once the UE identifies a reference slot, the UE checks the allocations in the SCCs according to a defined order to identify an SCC that can be used to transmit the A / N. In this case, the UE transmits the A / N on SCC-1. In some examples, if multiple slots on the determined CC can be used to transmit the PUCCH within the reference slot (based on the PCC numerology) indicated by K1, the earliest slot may be selected.

[0119] Diagram 1000 of Figure 10 illustrates an example of PDSCH scheduling in a PUCCH group 1002 that includes a PCC 1004, a first SCC (SCC-1) 1006, and a second SCC (SCC-2) 1008. In this example, the SCS for the PCC 1004 is 30 kHz, the SCS for the first SCC 1006 is 60 kHz, and the SCS for the second SCC 1008 is 15 kHz. As shown in Figure 10, slots on the PCC 1004, the first SCC 1006, and the second SCC 1008 may be designated as downlink (D) slots, uplink (U) slots, or special (S) slots. A PDSCH transmission 1010 occurs during slot 1012 on the PCC 1004 , and an associated PUCCH transmission for the A / N 1014 (eg, HARQ-Ack) occurs during slot 1016 on the first SCC 1006 .

[0120] The present disclosure relates in some aspects to PUCCH carrier switching configured by RRC per CC (e.g., as opposed to per UE). In this case, a base station (e.g., gNB) may have the flexibility to control which SCCs can support PUCCH carrier switching based on whether some prerequisite conditions are met. For example, RRC configuration messages may be used to enable / disable the feature per CC. As an example, a gNB may restrict PUCCH carrier switching over SCCs that have the same PDSCH processing capability (CAP1 vs. CAP2) as a PCC.

[0121] The present disclosure relates in some aspects to PUCCH carrier switching in which PUCCH resource sharing between dynamic PUCCH resources (indicated by a PUCCH resource indicator (PRI) in a DCI) and configured (by RRC) PUCCH resources is not supported. For example, slots with configured PUCCH resources may not be applicable to PUCCH carrier switching (e.g., as in the case of SPS A / N deferral). To support a unified design between SPS A / N deferral and PUCCH carrier switching, PUCCH resource sharing between dynamic PUCCH resources (indicated by a PRI) and semi-statically configured (by RRC) PUCCH resources may be indicated as not supported.

[0122] The present disclosure relates in some aspects to configuring PUCCH resources per CC (as opposed to, for example, configuring the same PUCCH resources for all CCs). For example, in a scenario where different CCs have different bandwidths, PUCCH resources may be configured per CC. For example, a PCC may have a bandwidth of 100 RBs and an SCC may have a bandwidth of only 50 RBs. In this case, PUCCH resources may be configured on RBs within the [0,99] range of the PCC. For example, a PUCCH resource of 10 RBs spans from RB90 to RB99. However, the PUCCH resources configured for the PCC may not be used on the SCC in this example. Configuring PUCCH resources per CC can solve this problem.

[0123] The present disclosure relates in some aspects to specifying the interplay between PUCCH carrier switching, UCI multiplexing, and PUCCH / PUSCH parallel transmission. In UCI multiplexing, if a UCI (PUCCH) transmission overlaps with a PUSCH transmission in the time domain, the UCI may be multiplexed with the PUSCH. For example, the original PUCCH transmission may be dropped, but the content for that PUCCH transmission may be multiplexed with the PUSCH transmission. In PUCCH / PUSCH parallel transmission, if a PUCCH transmission overlaps with a PUSCH transmission in the time domain, the two transmissions are performed simultaneously.

[0124] Referring to FIG. 11, as a first operation 1102, the UE performs a PUCCH carrier switch to determine on which CC / slot the PUCCH should be transmitted. Then, as a second operation 1104, the UE may perform either a parallel PUCCH / PUSCH transmission or a UCI multiplexing procedure (e.g., on the CC selected for PUCCH carrier switch) depending on whether parallel transmission is enabled or not. The second operation 1104 of this procedure is the same whether the PUCCH carrier switch function is supported or not. Also, even when the PUCCH carrier switch function is enabled, the first operation 1102 (PUCCH carrier switch function) may be effectively bypassed by the gNB by dynamically adjusting the K1 value if the gNB intends to do so.

[0125] The present disclosure relates in some aspects to allowing only one SCC to be configured to transmit PUCCH in addition to the PCC. In some examples, allowing one more carrier to transmit PUCCH is sufficient to obtain a desired level of latency reduction and diversity gain. By limiting PUCCH carrier switching to only one SCC, the PUCCH carrier switching procedure may be more efficient. In some examples, an RRC message may be used to indicate this one SCC (e.g., by configuring the SCC index to be used). In some examples, the RRC message may carry a bitmap indicating for each SCC whether that SCC is enabled for PUCCH carrier switching.

[0126] The present disclosure relates in some aspects to prioritizing a PCC for PUCCH carrier switching. On the UE side, the UE first prioritizes the PCC by interpreting K1 and PRI based on the PCC (e.g., using conventional techniques). If the interpreted slots and PUCCH resources on the PCC do not conflict with non-UL OFDM symbols (such as DL symbols, SSB symbols, CORESET0 symbols, etc.), the UE transmits PUCCH on the PCC (e.g., without checking whether a single additionally configured SCC has an available earlier PUCCH resource). If not, the UE moves to a single additionally configured SCC (SCC-1 in the example shown in FIG. 12) and interprets K1 and PRI based on the numerology and PUCCH resource configuration on that SCC. If the PCC did not have available resources for PUCCH transmission, it may be expected that the UE would find sufficient UL resources to transmit PUCCH on that SCC. For example, if the UE cannot transmit PUCCH on either the PCC or the additional allowed PUCCH SCC, this may be considered a gNB scheduling error.

[0127] It can be seen that this scheme can avoid the use of additional overhead in DCI while achieving a suitable level of flexibility to dynamically indicate PUCCH carriers between PCC and SCC. Also, the UE can avoid scanning multiple CCs and checking UL OFDM symbols for every CC until the UE finds a legitimate CC for transmitting PUCCH. In the example of Figure 12, the UE interprets K1 and PRI twice, once on the PCC and once on the authorized PUCCH SCC. Between the two interpretations, the interpretation on the PCC takes precedence.

[0128] Diagram 1200 of Figure 12 illustrates an example of PDSCH scheduling in a PUCCH group 1202 that includes a PCC 1204, a first SCC (SCC-1) 1206, and a second SCC (SCC-2) 1208. In this example, PUCCH is allowed on the PCC 1204, PUCCH is allowed on the first SCC 1206, and PUCCH is not allowed on the second SCC 1208. As shown in Figure 12, slots on the PCC 1204, the first SCC 1206, and the second SCC 1208 may be designated as downlink (D) slots, uplink (U) slots, or special (S) slots. A PDSCH transmission 1210 occurs during slot 1212 on the PCC 1204, and an associated PUCCH transmission for the A / N 1214 (e.g., HARQ-Ack) occurs during slot 1216 on the first SCC 1206 (e.g., due to a contention on the PCC 1204 where the preferred slot for transmitting the A / N is a downlink slot).

[0129] Thus, the present disclosure relates in some aspects to efficient PUCCH carrier switching involving limiting the CCs allowed to transmit PUCCH to only one additional SCC. The UE interprets the K1 and PRI parameters (or the RRC configured PUCCH resource indicator for SPS A / N) twice, once for the PCC and once for the configured allowed PUCCH SCC, with the PCC taking precedence.

[0130] 13 is a signaling diagram 1300 illustrating an example of PDSCH-related signaling in a wireless communication system including a network entity 1302 and a user equipment (UE) 1304. In some examples, the network entity 1302 may correspond to any of the base station, CU, DU, RU, or scheduling entity shown in any of Figures 1, 2, 4, 5, 6, and 19. In some examples, the UE 1304 may correspond to any of the UE or scheduled entity shown in any of Figures 1, 2, 4, 5, 6, and 14.

[0131] At 1306 of FIG. 13, the network entity 1302 transmits (e.g., via RRC messaging) resource information that the UE 1304 may use to transmit a PUCCH. For example, the resource information may specify that a first set of RBs (e.g., 100 RBs) may be used for PUCCH transmission on a first CC (e.g., CC1) and a second set of RBs (e.g., 10 RBs) may be used for PUCCH transmission on a second CC (e.g., CC2).

[0132] At 1308, the network entity 1302 sends (e.g., via RRC messaging) an indication of whether, for a data transmission on one CC, the UE 1304 is permitted to send feedback on another CC. For example, the indication may specify that a data transmission on a first CC (e.g., PCC) may be acknowledged on a second CC (e.g., SCC) and / or vice versa.

[0133] At some point in time, at 1310, the network entity 1302 schedules a PDSCH transmission for the UE 1304. In some examples, the network entity 1302 may schedule a PDSCH transmission and an associated PUCCH transmission (e.g., for HARQ-Ack). Thus, at 1312, the network entity 1302 transmits a DCI to the UE 1304, where the DCI may indicate PDSCH resources for the PDSCH transmission on a first CC (CC1) and PUCCH resources for the HARQ-Ack on a second CC (CC2). At 1314, the network entity 1302 transmits a PDSCH transmission on CC1 to the UE 1304.

[0134] The UE 1304 attempts to decode the PDSCH transmission, at 1316. The UE 1304 then generates a HARQ-Ack to be sent to the network entity 1302 to indicate whether the UE 1304 successfully received the PDSCH transmission.

[0135] At 1318, the UE 1304 identifies a CC for sending a HARQ-Ack to the network entity 1302. For example, the UE 1304 may select to send a HARQ-Ack on CC2 to achieve a shorter feedback turnaround time than is possible on CC1. At 1320, the UE 1304 transmits a HARQ-Ack transmission on CC2.

[0136] 14 is a block diagram illustrating an example of a hardware implementation for a UE 1400 employing a processing system 1414. For example, the UE 1400 may be a device configured to wirelessly communicate with a base station as described in any one or more of Figures 1-13. In some implementations, the UE 1410 may correspond to any of the UEs or scheduled entities shown in any of Figures 1, 2, 4, 5, 6, and 13.

[0137] According to various aspects of the disclosure, the elements, or any portion of the elements, or any combination of the elements, may be implemented using a processing system 1414. The processing system 1414 may include one or more processors 1404. Examples of the processor 1404 include a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, gate logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout the disclosure. In various examples, the UE 1400 may be configured to perform any one or more of the functions described herein. That is, the processor 1404 utilized in the UE 1400 may be used to implement any one or more of the processes and procedures described herein.

[0138] The processor 1404 may be implemented via a baseband or modem chip in some cases, while in other implementations the processor 1404 may include several different devices separate from the baseband or modem chip (e.g., in scenarios that may work together to achieve the examples described herein). As mentioned above, various hardware configurations and components external to the baseband modem processor may be used in implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.

[0139] In this example, the processing system 1414 may be implemented with a bus architecture, represented generally by bus 1402. The bus 1402 may include any number of interconnected buses and bridges, depending on the particular application and overall design constraints of the processing system 1414. The bus 1402 communicatively couples various circuits, including one or more processors (represented generally by processor 1404), memory 1405, and computer-readable media (represented generally by computer-readable media 1406). The bus 1402 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. The bus interface 1408 provides an interface between the bus 1402 and the transceiver 1410 and between the bus 1402 and the interface 1430. The transceiver 1410 provides a communication interface or means for communicating with various other devices over a wireless transmission medium. The interface 1430 provides a communication interface or means for communicating with various other apparatus and devices (e.g., other devices housed within the same apparatus as the UE or other external apparatus) via an internal bus or an external transmission medium such as an Ethernet cable. Depending on the nature of the apparatus, the interface 1430 may include a user interface (e.g., a keypad, a display, a speaker, a microphone, a joystick). Of course, such a user interface is optional and may be omitted in some instances, such as an IoT device.

[0140] The processor 1404 is responsible for general processing, including managing the bus 1402 and executing software stored on the computer-readable medium 1406. The software, when executed by the processor 1404, causes the processing system 1414 to perform various functions described below for any particular apparatus. The computer-readable medium 1406 and the memory 1405 may also be used to store data that is manipulated by the processor 1404 when executing the software. For example, the memory 1405 may store carrier configuration information 1415 (e.g., PCC information and SCC information) used by the processor 1404 for communication operations as described herein.

[0141] One or more processors 1404 in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software may reside on computer-readable medium 1406.

[0142] The computer readable medium 1406 may be a non-transitory computer readable medium. Non-transitory computer readable media include, by way of example, a magnetic storage device (e.g., a hard disk, a floppy disk, a magnetic strip), an optical disk (e.g., a compact disk (CD) or a digital versatile disk (DVD)), a smart card, a flash memory device (e.g., a card, stick, or key drive), a random access memory (RAM), a read only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), a register, a removable disk, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. The computer readable medium 1406 may be present within the processing system 1414, may be present outside the processing system 1414, or may be distributed across multiple entities including the processing system 1414. The computer readable medium 1406 may be embodied in a computer program product. By way of example, the computer program product may include the computer readable medium in packaging materials. Those skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system.

[0143] The UE 1400 may be configured to perform any one or more of the operations described herein (e.g., as described above in connection with FIGS. 1-13 and below in connection with FIGS. 15-18). In some aspects of the disclosure, the processor 1404 utilized in the UE 1400 may include circuits configured for various functions.

[0144] The processor 1404 may include a communication and processing circuit 1441. The communication and processing circuit 1441 may be configured to communicate with a base station, such as a gNB. The communication and processing circuit 1441 may include one or more hardware components that provide a physical structure to perform various processes related to wireless communication (e.g., signal reception and / or signal transmission) as described herein. The communication and processing circuit 1441 may further include one or more hardware components that provide a physical structure to perform various processes related to signal processing (e.g., processing received signals and / or processing signals for transmission) as described herein. In some examples, the communication and processing circuit 1441 may include two or more transmit / receive chains. The communication and processing circuit 1441 may be further configured to execute communication and processing software 1451 included on the computer-readable medium 1406 to implement one or more functions described herein.

[0145] In some implementations where communication involves receiving information, the communication and processing circuit 1441 may obtain information from a component of the UE 1400 (e.g., from the transceiver 1410, which receives information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuit 1441 may output the information to another component of the processor 1404, to the memory 1405, or to the bus interface 1408. In some examples, the communication and processing circuit 1441 may receive one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuit 1441 may receive information over one or more channels. In some examples, the communication and processing circuit 1441 may include functionality for a means for receiving. In some examples, the communication and processing circuit 1441 may include functionality for a means for decoding. In some examples, the communication and processing circuit 1441 may include functionality for a means for receiving data on one or more component carriers.

[0146] In some implementations where communication involves sending (e.g., transmitting) information, the communication and processing circuit 1441 may obtain information (e.g., from another component of the processor 1404, the memory 1405, or the bus interface 1408), process (e.g., encode) the information, and output the processed information. For example, the communication and processing circuit 1441 may output the information to the transceiver 1410 (e.g., transmit the information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, the communication and processing circuit 1441 may send one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuit 1441 may send information via one or more channels. In some examples, the communication and processing circuit 1441 may include functionality for a means for sending (e.g., a means for transmitting). In some examples, the communication and processing circuit 1441 may include functionality for a means for encoding. In some examples, the communications and processing circuit 1441 may include functionality for means for transmitting feedback on one or more component carriers.

[0147] The processor 1404 may include a feedback processing circuit 1442 configured to perform feedback processing related operations as described herein (e.g., one or more of the operations described above in connection with FIGS. 8-17). The feedback processing circuit 1442 may be configured to execute feedback processing software 1452 included on the computer-readable medium 1406 to implement one or more functions described herein.

[0148] The feedback processing circuit 1442 may include functionality for means for receiving an indication that the UE is permitted to send feedback on another CC (e.g., as described above in connection with FIGS. 8-17). For example, the feedback processing circuit 1442, along with the communication and processing circuit 1441 and the transceiver 1410, may receive an RRC message on the PDSCH that includes the indication.

[0149] The processor 1404 may include resource control circuitry 1443 configured to perform resource control related operations as described herein (e.g., one or more of the operations described above in connection with FIGS. 8-17). The resource control circuitry 1443 may be configured to execute resource control software 1453 included on the computer-readable medium 1406 to implement one or more functions described herein.

[0150] The resource control circuit 1443 may include functionality for selecting a resource. For example, the resource control circuit 1443 may select one CC of a set of CCs to receive the PUCCH.

[0151] The resource control circuitry 1443 may include functionality for means for receiving a resource allocation. For example, the resource control circuitry 1443 may receive an RRC message on a PDSCH that includes an indication of a resource allocation for transmitting feedback.

[0152] 15 is a flow chart illustrating an example method 1500 for a wireless communication system according to some aspects of the disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the disclosure, and some illustrated features may not be required for implementation of all examples. In some examples, the method 1500 may be performed by the user equipment 1400 shown in FIG. 14. In some examples, the method 1500 may be performed by any suitable device or means for performing the functions or algorithms described below.

[0153] At block 1502, the user equipment may receive data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group. In some examples, the communication and processing circuitry 1441 and the transceiver 1410 illustrated and described in FIG. 14 may provide means for receiving data on a first component carrier of the plurality of component carriers.

[0154] At block 1504, the user equipment may receive a first indication that the user equipment is permitted to transmit feedback for the data on a second component carrier of the plurality of component carriers. In some examples, the feedback processing circuit 1442 illustrated and described in FIG. 14 together with the communication and processing circuit 1441 and the transceiver 1410 may provide means for receiving a first indication that the user equipment is permitted to transmit feedback for the data on a second component carrier of the plurality of component carriers.

[0155] In some examples, to receive the first indication, the user equipment may receive a radio resource control (RRC) message including the first indication for each component carrier.

[0156] In some examples, the user equipment may transmit feedback on a physical uplink control channel (PUCCH) of the second component carrier after receiving the first indication.

[0157] In some examples, the user equipment may receive data on a physical downlink shared channel (PDSCH) of the first component carrier.

[0158] In some examples, the user equipment may receive a second indication that the user equipment is authorized to transmit feedback for the data on a third component carrier of the plurality of component carriers, and select one of the second component carrier and the third component carrier for transmitting the feedback. In some examples, the first component carrier is a primary component carrier, the second component carrier is a first secondary component carrier, and the third component carrier is a second secondary component carrier.

[0159] In some examples, the uplink control channel group may be a physical uplink control channel (PUCCH) group for uplink carrier aggregation.

[0160] In some examples, the user equipment may receive a first resource allocation, the first resource allocation being for transmitting feedback about the data on a first component carrier, hi some examples, the user equipment may receive a second resource allocation, the second resource allocation being for transmitting feedback about the data on a second component carrier of the plurality of component carriers.

[0161] In some examples, the first component carrier is a primary component carrier and the second component carrier is a secondary component carrier. In some examples, the first component carrier is a secondary component carrier and the second component carrier is a primary component carrier.

[0162] 16 is a flow chart illustrating an example method 1600 for a wireless communication system according to some aspects of the disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the disclosure, and some illustrated features may not be required for implementation of all examples. In some examples, the method 1600 may be performed by the user equipment 1400 shown in FIG. 14. In some examples, the method 1600 may be performed by any suitable device or means for performing the functions or algorithms described below.

[0163] At block 1602, the user equipment may receive data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group. In some examples, the communications and processing circuitry 1441 and the transceiver 1410 illustrated and described in FIG. 14 may provide means for receiving data on a first component carrier of the plurality of component carriers.

[0164] At block 1604, the user equipment may receive a first resource allocation, the first resource allocation being for transmitting feedback about the data on the first component carrier. In some examples, the resource control circuitry 1443 shown and described in FIG. 14 together with the communication and processing circuitry 1441 and the transceiver 1410 may provide means for receiving the first resource allocation.

[0165] At block 1606, the user equipment may receive a second resource allocation, the second resource allocation being for transmitting feedback about the data on a second component carrier of the plurality of component carriers. In some examples, the resource control circuitry 1443 shown and described in FIG. 14 together with the communication and processing circuitry 1441 and the transceiver 1410 may provide means for receiving the second resource allocation.

[0166] In some examples, the first resource allocation specifies a first set of physical uplink control channel (PUCCH) resources for a first component carrier, and the second resource allocation specifies a second set of PUCCH resources for a second component carrier.

[0167] In some examples, to receive the first resource allocation and to receive the second resource allocation, the user equipment may receive at least one radio resource control (RRC) configuration message indicating the first resource allocation and the second resource allocation.

[0168] In some examples, the user equipment may receive a third resource allocation, the third resource allocation being for transmitting feedback about the data on a third component carrier of the plurality of component carriers. In some examples, the first component carrier is a primary component carrier, the second component carrier is a first secondary component carrier, and the third component carrier is a second secondary component carrier. In some examples, the user equipment may transmit feedback on the second component carrier or the third component carrier.

[0169] In some examples, a first component carrier is assigned a first bandwidth and a second component carrier is assigned a second bandwidth that is different from the first bandwidth.

[0170] In some examples, the user equipment may receive a first indication that the user equipment is permitted to transmit feedback about the data on a second component carrier of the multiple component carriers.

[0171] In some examples, the first component carrier is a primary component carrier and the second component carrier is a secondary component carrier. In some examples, the first component carrier is a secondary component carrier and the second component carrier is a primary component carrier.

[0172] 17 is a flow chart illustrating an example method 1700 for a wireless communication system according to some aspects of the disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the disclosure, and some illustrated features may not be required for implementation of all examples. In some examples, the method 1700 may be performed by the user equipment 1400 shown in FIG. 14. In some examples, the method 1700 may be performed by any suitable device or means for performing the functions or algorithms described below.

[0173] At block 1702, the user equipment may receive data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group. In some examples, the communications and processing circuitry 1441 and the transceiver 1410 illustrated and described in FIG. 14 may provide means for receiving data on a first component carrier of the plurality of component carriers.

[0174] In block 1704, the user equipment may select a physical uplink control channel (PUCCH) resource on a second component carrier of the plurality of component carriers for transmitting feedback about the data. In some examples, the resource control circuitry 1443 shown and described in FIG. 14 may provide means for selecting a physical uplink control channel (PUCCH) resource on a second component carrier of the plurality of component carriers for transmitting feedback about the data.

[0175] In block 1706, the user equipment, after selecting the PUCCH resource on the second component carrier, may selectively transmit feedback in parallel with the uplink information based on whether parallel uplink transmission is enabled. In some examples, the feedback processing circuit 1442 shown and described in FIG. 14 together with the communication and processing circuit 1441 and the transceiver 1410 may provide a means for selectively transmitting feedback in parallel with the uplink information based on whether parallel uplink transmission is enabled.

[0176] In some examples, to selectively transmit feedback in parallel with uplink information based on whether parallel uplink transmission is enabled, a user equipment may transmit feedback in parallel with physical uplink shared channel (PUSCH) information when parallel uplink transmission is enabled.

[0177] In some examples, to selectively transmit feedback in parallel with uplink information based on whether parallel uplink transmission is enabled, the user equipment may multiplex the feedback with a physical uplink shared channel (PUSCH) when parallel uplink transmission is not enabled.

[0178] In some examples, to selectively transmit feedback in parallel with uplink information based on whether parallel uplink transmission is enabled, the user equipment may refrain from transmitting feedback in parallel with uplink information when parallel uplink transmission is not enabled.

[0179] In some examples, to selectively transmit feedback in parallel with the uplink information based on whether parallel uplink transmission is enabled, the user equipment may refrain from transmitting feedback in parallel with the uplink information after determining that the PUCCH resources do not overlap with scheduled physical uplink shared channel (PUSCH) resources on the second component carrier or scheduled uplink control information (UCI) resources on the second component carrier.

[0180] In some examples, the user equipment may transmit feedback in parallel with physical uplink shared channel (PUSCH) information when parallel uplink transmission is enabled, and in some examples, the user equipment may multiplex the feedback with the physical uplink shared channel (PUSCH) when parallel uplink transmission is not enabled.

[0181] In some examples, the first component carrier is a primary component carrier and the second component carrier is a secondary component carrier. In some examples, the first component carrier is a secondary component carrier and the second component carrier is a primary component carrier.

[0182] 18 is a flow chart illustrating an example method 1800 for a wireless communication system according to some aspects of the disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the disclosure, and some illustrated features may not be required for implementation of all examples. In some examples, the method 1800 may be performed by the user equipment 1400 shown in FIG. 14. In some examples, the method 1800 may be performed by any suitable device or means for performing the functions or algorithms described below.

[0183] In block 1802, the user equipment may receive data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group. In some examples, the communication and processing circuitry 1441 and the transceiver 1410 illustrated and described in FIG. 14 may provide means for receiving data on the first component carrier of the plurality of component carriers.

[0184] In block 1804, the user equipment may determine that the first component carrier does not have available resources for transmitting feedback about the data. In some examples, the resource control circuitry 1443 illustrated and described in FIG. 14, together with the communication and processing circuitry 1441 and the transceiver 1410, may provide means for determining that the first component carrier does not have available resources for transmitting feedback about the data.

[0185] In block 1806, the user equipment may selectively transmit feedback on a second component carrier of the plurality of component carriers after determining that the first component carrier does not have available resources for transmitting feedback. In some examples, the feedback processing circuit 1442 shown and described in FIG. 14 together with the communication and processing circuit 1441 and the transceiver 1410 may provide means for selectively transmitting feedback on a second component carrier of the plurality of component carriers.

[0186] In some examples, the user equipment may receive an indication that only one secondary component carrier of the multiple component carriers may be used to transmit feedback.

[0187] In some examples, to determine that the first component carrier does not have available resources for transmitting feedback, the user equipment may identify a slot on the first component carrier for transmitting feedback and identify that transmission of the feedback would conflict with at least one downlink orthogonal frequency division multiplexing (ODFM) symbol.

[0188] In some examples, to selectively transmit feedback on a second component carrier of the multiple component carriers, the user equipment may transmit feedback on a physical uplink control channel (PUCCH) resource on the second component carrier when the second component carrier has available resources for transmitting the feedback.

[0189] In some examples, to selectively transmit feedback on a second component carrier of the multiple component carriers, the user equipment may refrain from transmitting feedback on physical uplink control channel (PUCCH) resources on the second component carrier when the second component carrier does not have available resources for transmitting feedback.

[0190] In some examples, the first component carrier is a primary component carrier and the second component carrier is a secondary component carrier. In some examples, the first component carrier is a secondary component carrier and the second component carrier is a primary component carrier.

[0191] In one configuration, the user equipment 1400 includes means for receiving data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group, and means for receiving a first indication that the user equipment is authorized to transmit feedback about the data on a second component carrier of the plurality of component carriers. In one configuration, the user equipment 1400 includes means for receiving data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group, means for receiving a first resource assignment, the first resource assignment for transmitting feedback about the data on the first component carrier, and means for receiving a second resource assignment, the second resource assignment for transmitting feedback about the data on the second component carrier of the plurality of component carriers. In one configuration, the user equipment 1400 includes means for receiving data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group; means for selecting a physical uplink control channel (PUCCH) resource on a second component carrier of the plurality of component carriers for transmitting feedback about the data; and means for selectively transmitting the feedback in parallel with the uplink information after selecting the PUCCH resource on the second component carrier based on whether parallel uplink transmission is enabled.In one configuration, the user equipment 1400 includes means for receiving data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group, means for determining that the first component carrier does not have available resources for transmitting feedback about the data, and means for selectively transmitting feedback on a second component carrier of the plurality of component carriers after determining that the first component carrier does not have available resources for transmitting feedback. In one aspect, the aforementioned means may be the processor 1404 shown in FIG. 14 configured to perform the functions recited by the aforementioned means (e.g., as described above). In another aspect, the aforementioned means may be a circuit or any device configured to perform the functions recited by the aforementioned means.

[0192] Of course, in the above examples, the circuitry included in the processor 1404 is provided by way of example only, and other means for performing the described functions may be included within various aspects of the disclosure, including, but not limited to, instructions stored on the computer-readable medium 1406, or any other suitable apparatus or means employing the methods and / or algorithms described in any one or more of Figures 1, 2, 4, 5, 6, 13, and 14, and described herein, for example, with respect to Figures 15-18.

[0193] 19 is a conceptual diagram illustrating an example of a hardware implementation for a network entity 1900 employing a processing system 1914. In some implementations, the network entity 1900 may correspond to any of the network entities, BSs (e.g., gNBs), CUs, DUs, RUs, or scheduling entities shown in any of FIGS.

[0194] According to various aspects of the disclosure, the elements, or any portion of the elements, or any combination of the elements, may be implemented using a processing system 1914. The processing system may include one or more processors 1904. The processing system 1914 may be substantially similar to the processing system 1414 shown in FIG. 14 and includes a bus interface 1908, a bus 1902, a memory 1905, a processor 1904, and a computer-readable medium 1906. The memory 1905 may store carrier configuration information 1915 (e.g., PCC information and SCC information) used by the processor 1904 for communication operations as described herein. Additionally, the network entity 1900 may include an interface 1930 (e.g., a network interface) that provides a means for communicating with at least one other device in the core network and with at least one radio access network.

[0195] The network entity 1900 may be configured to perform any one or more of the operations described herein (e.g., as described above in connection with FIGS. 1-13 and below in connection with FIGS. 20-23). ​​In some aspects of the disclosure, a processor 1904 utilized in the network entity 1900 may include circuitry configured for various functions.

[0196] The processor 1904 may be configured to generate, schedule, and modify resource assignments or grants of time-frequency resources (e.g., a set of one or more resource elements). For example, the processor 1904 may schedule time-frequency resources within multiple time division duplexing (TDD) and / or frequency time division duplexing (FDD) subframes, slots, and / or minislots to carry user data traffic and / or control information to and / or from multiple UEs. The processor 1904 may be configured to schedule resources for transmission of downlink signals and / or resources for transmission of uplink signals.

[0197] In some aspects of the disclosure, the processor 1904 may include a communication and processing circuit 1941. The communication and processing circuit 1941 may be configured to communicate with a UE. The communication and processing circuit 1941 may include one or more hardware components that provide a physical structure to perform various processes related to communication (e.g., signal reception and / or signal transmission) as described herein. The communication and processing circuit 1941 may further include one or more hardware components that provide a physical structure to perform various processes related to signal processing (e.g., processing received signals and / or processing signals for transmission) as described herein. The communication and processing circuit 1941 may be further configured to execute communication and processing software 1951 included on the computer-readable medium 1906 to implement one or more functions described herein.

[0198] The communication and processing circuit 1941 may be further configured to transmit messages to the UE and / or receive messages from the UE. For example, the downlink message may be included in a MAC-CE carried in a PDSCH, a DCI carried in a PDCCH or a PDSCH, or an RRC message. In addition, the uplink message may be included in a MAC-CE carried in a PUSCH, a UCI carried in a PUCCH, a random access message, or an RRC message.

[0199] In some implementations where communication involves receiving information, the communication and processing circuit 1941 may obtain information from a component of the network entity 1900 (e.g., from a transceiver 1910 that receives information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuit 1941 may output the information to another component of the processor 1904, to the memory 1905, or to the bus interface 1908. In some examples, the communication and processing circuit 1941 may receive one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuit 1941 may receive information over one or more channels. In some examples, the communication and processing circuit 1941 may include functionality for a means for receiving. In some examples, the communication and processing circuit 1941 may include functionality for a means for decoding. In some examples, the communications and processing circuit 1941 may include functionality for means for receiving feedback data on one or more component carriers.

[0200] In some implementations where communication involves sending (e.g., transmitting) information, the communication and processing circuit 1941 may obtain information (e.g., from another component of the processor 1904, the memory 1905, or the bus interface 1908), process (e.g., encode) the information, and output the processed information. For example, the communication and processing circuit 1941 may output the information to a transceiver 1910 (e.g., which transmits the information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, the communication and processing circuit 1941 may send one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuit 1941 may send information via one or more channels. In some examples, the communication and processing circuit 1941 may include functionality for a means for sending (e.g., a means for transmitting). In some examples, the communication and processing circuit 1941 may include functionality for a means for encoding. In some examples, the communications and processing circuit 1941 may include functionality for means for transmitting data on one or more component carriers.

[0201] The processor 1904 may include a feedback control circuit 1942 configured to perform feedback control related operations as described herein (e.g., one or more of the operations described above in connection with FIGS. 8-13). The feedback control circuit 1942 may be configured to execute feedback control software 1952 included on the computer-readable medium 1906 to implement one or more functions described herein.

[0202] The feedback control circuit 1942 may include functionality for means for transmitting an indication that the UE is permitted to transmit feedback on another CC (e.g., as described above in connection with FIGS. 8-13). For example, the feedback control circuit 1942, in conjunction with the communication and processing circuit 1941 and the transceiver 1910, may transmit an RRC message including the indication on the PDSCH.

[0203] The processor 1904 may include resource control circuitry 1943 configured to perform resource control related operations as described herein (e.g., one or more of the operations described above in connection with FIGS. 8-13). The resource control circuitry 1943 may be configured to execute resource control software 1953 included on the computer-readable medium 1906 to implement one or more functions described herein.

[0204] The resource control circuit 1943 may include functionality for identifying a resource. For example, the resource control circuit 1943 may select one CC of a set of CCs for a PUCCH transmission.

[0205] The resource control circuit 1943 may include functionality for means for transmitting a resource allocation, For example, the resource control circuit 1943 may transmit an RRC message on the PDSCH including an indication of a resource allocation for transmitting feedback.

[0206] In some examples, the network entity 1900 illustrated and described above with respect to FIG. 19 may be a non-aggregated base station. For example, the network entity 1900 illustrated in FIG. 19 may include a CU and optionally one or more DU / RUs of a non-aggregated base station. Other DU / RUs associated with the network entity 1900 may be distributed throughout the network. In some examples, the DU / RU may correspond to a TRP associated with the network entity. In some examples, the CU and / or DU / RU of the non-aggregated base station (e.g., in the network entity 1900) may generate data and provide the data to a user equipment via a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group.

[0207] 20 is a flow chart illustrating another example method 2000 for a wireless communication system according to some aspects of the disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the disclosure, and some illustrated features may not be required for implementation of all examples. In some examples, the method 2000 may be performed by the network entity 1900 shown in FIG. 19. In some examples, the method 2000 may be performed by any suitable device or means for performing the functions or algorithms described below.

[0208] In block 2002, the network entity may transmit data to a user equipment on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group. In some examples, the communication and processing circuitry 1941 and the transceiver 1910 illustrated and described in FIG. 19 may provide means for transmitting data to a user equipment on a first component carrier of the plurality of component carriers.

[0209] In block 2004, the network entity may transmit a first indication that the user equipment is permitted to transmit feedback for the data on a second component carrier of the plurality of component carriers. In some examples, the feedback control circuit 1942 illustrated and described in FIG. 19 together with the communication and processing circuit 1941 and the transceiver 1910 may provide means for transmitting the first indication that the user equipment is permitted to transmit feedback for the data on a second component carrier of the plurality of component carriers.

[0210] In some examples, the network entity may transmit a radio resource control (RRC) message including the first indication.

[0211] In some examples, the network entity may receive feedback on a physical uplink control channel (PUCCH) of the second component carrier after sending the first indication.

[0212] In some examples, the network entity may transmit data on a physical downlink shared channel (PDSCH) of the first component carrier.

[0213] In some examples, the network entity may send a second indication that the user equipment is permitted to send feedback for the data on a third component carrier of the plurality of component carriers and receive the feedback on the second component carrier or the third component carrier. In some examples, the first component carrier is a primary component carrier, the second component carrier is a first secondary component carrier, and the third component carrier is a second secondary component carrier.

[0214] In some examples, the uplink control channel group may be a physical uplink control channel (PUCCH) group for uplink carrier aggregation.

[0215] In some examples, the network entity may transmit a first resource allocation, the first resource allocation being for transmitting feedback about the data on a first component carrier, hi some examples, the network entity may transmit a second resource allocation, the second resource allocation being for transmitting feedback about the data on a second component carrier of the plurality of component carriers.

[0216] In some examples, the first component carrier is a primary component carrier and the second component carrier is a secondary component carrier. In some examples, the first component carrier is a secondary component carrier and the second component carrier is a primary component carrier.

[0217] 21 is a flow chart illustrating another example method 2100 for a wireless communication system according to some aspects of the disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the disclosure, and some illustrated features may not be required for implementation of all examples. In some examples, the method 2100 may be performed by the network entity 1900 shown in FIG. 19. In some examples, the method 2100 may be performed by any suitable device or means for performing the functions or algorithms described below.

[0218] In block 2102, the network entity may transmit data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group. In some examples, the communication and processing circuitry 1941 and the transceiver 1910 illustrated and described in FIG. 19 may provide means for transmitting data on the first component carrier of the plurality of component carriers.

[0219] At block 2104, the network entity may transmit a first resource allocation, the first resource allocation being for transmitting feedback about the data on the first component carrier. In some examples, the resource control circuit 1943 illustrated and described in FIG. 19 together with the communication and processing circuit 1941 and the transceiver 1910 may provide means for transmitting the first resource allocation.

[0220] At block 2106, the network entity may transmit a second resource allocation, the second resource allocation being for transmitting feedback about the data on a second component carrier of the plurality of component carriers. In some examples, the resource control circuitry 1943 shown and described in FIG. 19 together with the communication and processing circuitry 1941 and the transceiver 1910 may provide means for transmitting the second resource allocation.

[0221] In some examples, the first resource allocation specifies a first set of physical uplink control channel (PUCCH) resources for a first component carrier, and the second resource allocation specifies a second set of PUCCH resources for a second component carrier.

[0222] In some examples, the network entity may transmit at least one radio resource control (RRC) configuration message indicating the first resource allocation and the second resource allocation.

[0223] In some examples, the network entity may transmit a third resource allocation, the third resource allocation being for transmitting feedback about the data on a third component carrier of the plurality of component carriers, in some examples, the first component carrier is a primary component carrier, the second component carrier is a first secondary component carrier, and the third component carrier is a second secondary component carrier.

[0224] In some examples, the network entity may receive the feedback on the second component carrier or the third component carrier.

[0225] In some examples, a first component carrier is assigned a first bandwidth and a second component carrier is assigned a second bandwidth that is different from the first bandwidth.

[0226] In some examples, the network entity may transmit a first indication that the user equipment is permitted to transmit feedback about the data on a second component carrier of the plurality of component carriers.

[0227] In some examples, the first component carrier is a primary component carrier and the second component carrier is a secondary component carrier. In some examples, the first component carrier is a secondary component carrier and the second component carrier is a primary component carrier.

[0228] 22 is a flow chart illustrating another example method 2200 for a wireless communication system according to some aspects of the disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the disclosure, and some illustrated features may not be required for implementation of all examples. In some examples, the method 2200 may be performed by the network entity 1900 shown in FIG. 19. In some examples, the method 2200 may be performed by any suitable device or means for performing the functions or algorithms described below.

[0229] In block 2202, the network entity may transmit data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group. In some examples, the communication and processing circuitry 1941 and the transceiver 1910 illustrated and described in FIG. 19 may provide means for transmitting data on the first component carrier of the plurality of component carriers.

[0230] At block 2204, the network entity may identify a physical uplink control channel (PUCCH) resource on a second component carrier of the plurality of component carriers for transmitting feedback about the data by the user equipment. In some examples, the resource control circuitry 1943 shown and described in FIG. 19 may provide means for identifying a physical uplink control channel (PUCCH) resource on a second component carrier of the plurality of component carriers for transmitting feedback about the data by the user equipment.

[0231] In block 2206, the network entity, after identifying the PUCCH resource on the second component carrier, may selectively receive feedback in parallel with the uplink information based on whether parallel uplink transmission is enabled. In some examples, the feedback control circuit 1942 shown and described in FIG. 19 together with the communication and processing circuit 1941 and the transceiver 1910 may provide means for selectively receiving feedback in parallel with the uplink information based on whether parallel uplink transmission is enabled.

[0232] In some examples, to selectively receive feedback in parallel with uplink information based on whether parallel uplink transmission is enabled, a network entity may receive feedback in parallel with physical uplink shared channel (PUSCH) information when parallel uplink transmission is enabled.

[0233] In some examples, to selectively receive feedback in parallel with uplink information based on whether parallel uplink transmission is enabled, a network entity may receive multiplexed feedback and uplink control information (UCI) when parallel uplink transmission is enabled.

[0234] In some examples, to selectively receive feedback in parallel with the uplink information based on whether parallel uplink transmission is enabled, the network entity may refrain from receiving feedback in parallel with the uplink information when parallel uplink transmission is not enabled.

[0235] In some examples, the first component carrier is a primary component carrier and the second component carrier is a secondary component carrier. In some examples, the first component carrier is a secondary component carrier and the second component carrier is a primary component carrier.

[0236] 23 is a flow chart illustrating another example method 2300 for a wireless communication system according to some aspects of the disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the disclosure, and some illustrated features may not be required for implementation of all examples. In some examples, the method 2300 may be performed by the network entity 1900 shown in FIG. 19. In some examples, the method 2300 may be performed by any suitable device or means for performing the functions or algorithms described below.

[0237] In block 2302, the network entity may transmit data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group. In some examples, the communication and processing circuitry 1941 and the transceiver 1910 illustrated and described in FIG. 19 may provide means for transmitting data on the first component carrier of the plurality of component carriers.

[0238] In block 2304, the network entity may determine that the first component carrier does not have available resources for transmitting feedback about the data. In some examples, the resource control circuit 1943 illustrated and described in FIG. 19, together with the communication and processing circuit 1941 and the transceiver 1910, may provide means for determining that the first component carrier does not have available resources for transmitting feedback about the data.

[0239] In block 2306, the network entity may selectively receive feedback on a second component carrier of the plurality of component carriers after determining that the first component carrier does not have available resources for transmitting feedback. In some examples, the feedback control circuit 1942 illustrated and described in FIG. 19 together with the communication and processing circuit 1941 and the transceiver 1910 may provide means for selectively receiving feedback on a second component carrier of the plurality of component carriers.

[0240] In some examples, the network entity may transmit an indication that only one secondary component carrier of the multiple component carriers may be used to transmit feedback.

[0241] In some examples, to determine that the first component carrier does not have available resources for transmitting feedback, the network entity may identify a slot on the first component carrier for transmitting feedback and identify a scheduled downlink transmission during the slot that conflicts with the transmission of the feedback.

[0242] In some examples, to selectively receive feedback on a second component carrier of the multiple component carriers, the network entity may receive feedback on a physical uplink control channel (PUCCH) resource on the second component carrier when the second component carrier has available resources for transmitting the feedback.

[0243] In some examples, to selectively receive feedback on a second component carrier of the multiple component carriers, the network entity may refrain from receiving feedback on physical uplink control channel (PUCCH) resources on the second component carrier when the second component carrier does not have available resources for transmitting feedback.

[0244] In some examples, the first component carrier is a primary component carrier and the second component carrier is a secondary component carrier. In some examples, the first component carrier is a secondary component carrier and the second component carrier is a primary component carrier.

[0245] In one configuration, the network entity 1900 includes means for transmitting data to a user equipment on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group, and means for transmitting a first indication that the user equipment is authorized to transmit feedback about the data on a second component carrier of the plurality of component carriers. In one configuration, the network entity 1900 includes means for transmitting data on the first component carrier of the plurality of component carriers, means for transmitting a first resource allocation, the first resource allocation for transmitting feedback about the data on the first component carrier, and means for transmitting a second resource allocation, the second resource allocation for transmitting feedback about the data on the second component carrier of the plurality of component carriers. In one configuration, the network entity 1900 includes means for transmitting data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group; means for identifying a physical uplink control channel (PUCCH) resource on a second component carrier of the plurality of component carriers for transmitting feedback about the data by a user equipment; and means for selectively receiving the feedback in parallel with the uplink information after identifying the PUCCH resource on the second component carrier based on whether parallel uplink transmission is enabled.In one configuration, the network entity 1900 includes means for transmitting data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group, means for determining that the first component carrier does not have available resources for transmitting feedback about the data, and means for selectively receiving feedback on a second component carrier of the plurality of component carriers after determining that the first component carrier does not have available resources for transmitting feedback. In one aspect, the aforementioned means may be the processor 1904 shown in FIG. 19 configured to perform the functions recited by the aforementioned means (e.g., as described above). In another aspect, the aforementioned means may be a circuit or any device configured to perform the functions recited by the aforementioned means.

[0246] Of course, in the above examples, the circuitry included in the processor 1904 is provided by way of example only, and other means for performing the described functions may be included within various aspects of the disclosure, including, but not limited to, instructions stored on a computer-readable medium 1906, or any other suitable apparatus or means employing the methods and / or algorithms described in any one or more of Figures 1, 2, 4, 5, 6, 13, and 19, and described herein, for example, with respect to Figures 20-23.

[0247] The methods illustrated in Figures 15-18 and 20-23 may include additional aspects, such as any single aspect or any combination of aspects described below and / or with respect to one or more other processes described elsewhere herein.

[0248] In some examples, a user equipment may include a transceiver, a memory, and a processor coupled to the transceiver and the memory. The processor and memory may be configured to receive data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group, determine that the first component carrier does not have available resources for transmitting feedback about the data, and selectively transmit the feedback on a second component carrier of the plurality of component carriers after determining that the first component carrier does not have available resources for transmitting the feedback.

[0249] In some examples, a method for wireless communication in a user equipment is disclosed, which may include receiving data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group, determining that the first component carrier does not have available resources for transmitting feedback about the data, and selectively transmitting the feedback on a second component carrier of the plurality of component carriers after determining that the first component carrier does not have available resources for transmitting the feedback.

[0250] In some examples, a user equipment may include means for receiving data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group; means for determining that the first component carrier does not have available resources for transmitting feedback about the data; and means for selectively transmitting feedback on a second component carrier of the plurality of component carriers after determining that the first component carrier does not have available resources for transmitting feedback.

[0251] In some examples, an article of manufacture for use by a user equipment includes a non-transitory computer-readable medium having stored thereon instructions executable by one or more processors of the user equipment to receive data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group; determining that the first component carrier does not have available resources for transmitting feedback about the data; and selectively transmitting the feedback on a second component carrier of the plurality of component carriers after determining that the first component carrier does not have available resources for transmitting the feedback.

[0252] In some examples, the network entity may include a transceiver, a memory, and a processor coupled to the transceiver and the memory. The processor and memory may be configured to transmit data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group, determine that the first component carrier does not have available resources for transmitting feedback about the data, and selectively receive feedback on a second component carrier of the plurality of component carriers after determining that the first component carrier does not have available resources for transmitting the feedback.

[0253] In some examples, a method for wireless communication in a network entity is disclosed, which may include transmitting data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group, determining that the first component carrier does not have available resources for transmitting feedback about the data, and selectively receiving feedback on a second component carrier of the plurality of component carriers after determining that the first component carrier does not have available resources for transmitting the feedback.

[0254] In some examples, the network entity may include means for transmitting data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group; means for determining that the first component carrier does not have available resources for transmitting feedback about the data; and means for selectively receiving feedback on a second component carrier of the plurality of component carriers after determining that the first component carrier does not have available resources for transmitting feedback.

[0255] In some examples, an article of manufacture for use by a network entity includes a non-transitory computer-readable medium having stored thereon instructions executable by one or more processors of the network entity to transmit data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group; determining that the first component carrier does not have available resources for transmitting feedback about the data; and selectively receiving feedback on a second component carrier of the plurality of component carriers after determining that the first component carrier does not have available resources for transmitting the feedback.

[0256] The following provides a summary of several aspects of the disclosure.

[0257] Aspect 1: A method for wireless communications in a user equipment, the method including: receiving data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group; and receiving a first indication that the user equipment is authorized to transmit feedback about the data on a second component carrier of the plurality of component carriers.

[0258] Aspect 2: The method of aspect 1, wherein receiving the first indication includes receiving a radio resource control (RRC) message including the first indication for each component carrier.

[0259] Aspect 3: The method of aspect 1 or 2, further comprising transmitting feedback on a physical uplink control channel (PUCCH) of the second component carrier after receiving the first indication.

[0260] Aspect 4: The method of aspect 3, wherein receiving the data includes receiving the data on a physical downlink shared channel (PDSCH) of the first component carrier.

[0261] Aspect 5: The method of any of aspects 1-4, further comprising: receiving a second indication that the user equipment is authorized to transmit feedback for the data on a third component carrier of the plurality of component carriers; and selecting one of the second component carrier and the third component carrier for transmitting the feedback.

[0262] Aspect 6: The method of aspect 5, wherein the first component carrier is a primary component carrier, the second component carrier is a first secondary component carrier, and the third component carrier is a second secondary component carrier.

[0263] Example 7: The method of any of Examples 1-6, wherein the uplink control channel group includes a physical uplink control channel (PUCCH) group for uplink carrier aggregation.

[0264] Example 8: The method of any of Examples 1 to 5 and 7, wherein the second component carrier is a primary component carrier and the first component carrier is a secondary component carrier.

[0265] Aspect 9: The method of any of Aspects 1-8, further comprising: receiving a first resource allocation, the first resource allocation being for transmitting feedback about the data on a first component carrier; and receiving a second resource allocation, the second resource allocation being for transmitting feedback about the data on a second component carrier of the plurality of component carriers.

[0266] Aspect 11: A method for wireless communication in a network entity, the method including: transmitting data to a user equipment on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group; and transmitting a first indication that the user equipment is authorized to transmit feedback about the data on a second component carrier of the plurality of component carriers.

[0267] Aspect 12: The method of aspect 11, wherein the step of transmitting the first indication includes the step of transmitting a radio resource control (RRC) message including the first indication.

[0268] Aspect 13: The method of any of aspects 11-12, further comprising receiving feedback on a physical uplink control channel (PUCCH) of the second component carrier after the step of transmitting the first indication.

[0269] Aspect 14: The method of aspect 13, wherein transmitting the data includes transmitting the data on a physical downlink shared channel (PDSCH) of the first component carrier.

[0270] Aspect 15: The method of any of aspects 11-14, further comprising: transmitting a second indication that the user equipment is permitted to transmit feedback for the data on a third component carrier of the plurality of component carriers; and receiving the feedback on the second component carrier or the third component carrier.

[0271] Aspect 16: The method of aspect 15, wherein the first component carrier is a primary component carrier, the second component carrier is a first secondary component carrier, and the third component carrier is a second secondary component carrier.

[0272] Example 17: The method of any of Examples 11-16, wherein the uplink control channel group includes a physical uplink control channel (PUCCH) group for uplink carrier aggregation.

[0273] Example 18: The method of any of Examples 11-14 and 17, wherein the second component carrier is a primary component carrier and the first component carrier is a secondary component carrier.

[0274] Aspect 19: The method of any of Aspects 11-18, further comprising: transmitting a first resource allocation, the first resource allocation for transmitting feedback about the data on a first component carrier; and transmitting a second resource allocation, the second resource allocation for transmitting feedback about the data on a second component carrier of the plurality of component carriers.

[0275] Aspect 21: A method for wireless communication in a user equipment, comprising: receiving data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group; receiving a first resource allocation, the first resource allocation for transmitting feedback about the data on the first component carrier; and receiving a second resource allocation, the second resource allocation for transmitting feedback about the data on a second component carrier of the plurality of component carriers.

[0276] Aspect 22: The method of aspect 21, wherein the first resource assignment specifies a first set of physical uplink control channel (PUCCH) resources for a first component carrier and the second resource assignment specifies a second set of PUCCH resources for a second component carrier.

[0277] Aspect 23: The method of any of aspects 21-22, wherein the step of receiving the first resource allocation and the step of receiving the second resource allocation include the step of receiving at least one radio resource control (RRC) configuration message indicating the first resource allocation and the second resource allocation.

[0278] Aspect 24: The method of any of Aspects 21-23, further comprising the step of receiving a third resource allocation, the third resource allocation being for transmitting feedback about the data on a third component carrier of the plurality of component carriers.

[0279] Aspect 25: The method of aspect 24, wherein the first component carrier is a primary component carrier, the second component carrier is a first secondary component carrier, and the third component carrier is a second secondary component carrier.

[0280] Aspect 26: The method of any of aspects 24-25, further comprising transmitting feedback on the second component carrier or the third component carrier.

[0281] Example 27: The method of any of Examples 21 to 26, wherein a first component carrier is assigned a first bandwidth, and a second component carrier is assigned a second bandwidth, the second bandwidth being different from the first bandwidth.

[0282] Example 28: The method of any of Examples 21 to 24 and 27, wherein the second component carrier is a primary component carrier and the first component carrier is a secondary component carrier.

[0283] Aspect 29: The method of any of aspects 21-28, further comprising receiving a first indication that the user equipment is permitted to transmit feedback about the data on a second component carrier of the plurality of component carriers.

[0284] Aspect 31: A method for wireless communication in a network entity, comprising: transmitting data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group; transmitting a first resource allocation, the first resource allocation for transmitting feedback about the data on the first component carrier; and transmitting a second resource allocation, the second resource allocation for transmitting feedback about the data on a second component carrier of the plurality of component carriers.

[0285] Aspect 32: The method of aspect 31, wherein the first resource assignment specifies a first set of physical uplink control channel (PUCCH) resources for a first component carrier and the second resource assignment specifies a second set of PUCCH resources for a second component carrier.

[0286] Aspect 33: The method of any of aspects 31-32, wherein the step of transmitting the first resource allocation and the step of transmitting the second resource allocation include the step of transmitting at least one radio resource control (RRC) configuration message indicating the first resource allocation and the second resource allocation.

[0287] Aspect 34: The method of any of aspects 31 to 33, further comprising the step of transmitting a third resource allocation, the third resource allocation being for transmitting feedback about the data on a third component carrier of the plurality of component carriers.

[0288] Aspect 35: The method of aspect 34, wherein the first component carrier is a primary component carrier, the second component carrier is a first secondary component carrier, and the third component carrier is a second secondary component carrier.

[0289] Example 36: The method of any of Examples 34-35, further comprising receiving feedback on the second component carrier or the third component carrier.

[0290] Example 37: The method of any of Examples 31 to 36, wherein a first component carrier is assigned a first bandwidth, and a second component carrier is assigned a second bandwidth, different from the first bandwidth.

[0291] Example 38: The method of any of Examples 31 to 34 and 37, wherein the second component carrier is a primary component carrier and the first component carrier is a secondary component carrier.

[0292] Aspect 39: The method of any of aspects 31-38, further comprising receiving a first indication that the user equipment is permitted to transmit feedback about the data on a second component carrier of the plurality of component carriers.

[0293] Aspect 41: A method for wireless communication in a user equipment, comprising: receiving data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group; selecting a physical uplink control channel (PUCCH) resource on a second component carrier of the plurality of component carriers for transmitting feedback about the data; and after selecting the PUCCH resource on the second component carrier, selectively transmitting the feedback in parallel with uplink information based on whether parallel uplink transmission is enabled.

[0294] Aspect 42: The method of aspect 41, wherein the step of selectively transmitting feedback in parallel with the uplink information based on whether parallel uplink transmission is enabled includes the step of transmitting feedback in parallel with physical uplink shared channel (PUSCH) information when parallel uplink transmission is enabled.

[0295] Aspect 43: The method of aspect 41, wherein the step of selectively transmitting feedback in parallel with the uplink information based on whether parallel uplink transmission is enabled includes the step of multiplexing the feedback with a physical uplink shared channel (PUSCH) when parallel uplink transmission is not enabled.

[0296] Aspect 44: The method of aspect 41, wherein the step of selectively transmitting feedback in parallel with the uplink information based on whether parallel uplink transmission is enabled includes the step of refraining from transmitting feedback in parallel with the uplink information when parallel uplink transmission is not enabled.

[0297] Aspect 45: The method of aspect 41, wherein the step of selectively transmitting feedback in parallel with the uplink information based on whether parallel uplink transmission is enabled includes the step of refraining from transmitting the feedback in parallel with the uplink information after determining that the PUCCH resources do not overlap with scheduled physical uplink shared channel (PUSCH) resources on the second component carrier or scheduled uplink control information (UCI) resources on the second component carrier.

[0298] Aspect 46: The method of any of aspects 41 to 45, wherein the first component carrier is a primary component carrier and the second component carrier is a secondary component carrier.

[0299] Example 47: The method of any of Examples 41 to 45, wherein the second component carrier is a primary component carrier and the first component carrier is a secondary component carrier.

[0300] Aspect 48: The method of any of aspects 41 and 46-47, further comprising: transmitting feedback in parallel with physical uplink shared channel (PUSCH) information when parallel uplink transmission is enabled; and multiplexing the feedback with the physical uplink shared channel (PUSCH) when parallel uplink transmission is not enabled.

[0301] Aspect 51: A method for wireless communication in a network entity, comprising: transmitting data on a first component carrier of a plurality of component carriers, the plurality of component carriers being associated with an uplink control channel group; identifying a physical uplink control channel (PUCCH) resource on a second component carrier of the plurality of component carriers for transmitting feedback about the data by a user equipment; and after identifying the PUCCH resource on the second component carrier, selectively receiving the feedback in parallel with the uplink information based on whether parallel uplink transmission is enabled.

[0302] Aspect 52: The method of aspect 51, wherein the step of selectively receiving feedback in parallel with the uplink information based on whether parallel uplink transmission is enabled includes the step of receiving feedback in parallel with physical uplink shared channel (PUSCH) information when parallel uplink transmission is enabled.

[0303] Aspect 53: The method of aspect 51, wherein the step of selectively receiving feedback in parallel with the uplink information based on whether parallel uplink transmission is enabled includes the step of receiving multiplexed feedback and physical uplink shared channel (PUSCH) information when parallel uplink transmission is not enabled.

[0304] Aspect 54: The method of aspect 51, wherein the step of selectively receiving feedback in parallel with the uplink information based on whether parallel uplink transmission is enabled includes the step of refraining from receiving feedback in parallel with the uplink information when parallel uplink transmission is not enabled.

[0305] Example 55: The method of any of Examples 51 to 54, wherein the first component carrier is a primary component carrier and the second component carrier is a secondary component carrier.

[0306] Example 56: The method of any of Examples 51 to 54, wherein the second component carrier is a primary component carrier and the first component carrier is a secondary component carrier.

[0307] Aspect 57: A user equipment comprising a transceiver configured to communicate with a radio access network, a memory, and a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform any one of aspects 1-9.

[0308] Aspect 58: An apparatus configured for wireless communication, comprising at least one means for performing any one of aspects 1-9.

[0309] Aspect 59: A non-transitory computer readable medium storing computer executable code, the non-transitory computer readable medium comprising code for causing an apparatus to perform any one of aspects 1-9.

[0310] Aspect 60: A network entity comprising a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory, the processor and the memory configured to perform any one of aspects 11-19.

[0311] Aspect 61: An apparatus configured for wireless communication, comprising at least one means for performing any one of aspects 11-19.

[0312] Aspect 62: A non-transitory computer-readable medium storing computer-executable code, the non-transitory computer-readable medium comprising code for causing an apparatus to execute any one of aspects 11-19.

[0313] Aspect 63: A user equipment comprising a transceiver configured to communicate with a radio access network, a memory, and a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform any one of aspects 21-29.

[0314] Example 64: An apparatus configured for wireless communication, comprising at least one means for performing any one of examples 21-29.

[0315] Aspect 65: A non-transitory computer-readable medium storing computer-executable code, the non-transitory computer-readable medium comprising code for causing an apparatus to perform any one of aspects 21-29.

[0316] Aspect 66: A network entity comprising a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory, the processor and the memory configured to perform any one of aspects 31 to 39.

[0317] Aspect 67: An apparatus configured for wireless communication, comprising at least one means for performing any one of aspects 31-39.

[0318] Aspect 68: A non-transitory computer-readable medium storing computer-executable code, the non-transitory computer-readable medium comprising code for causing an apparatus to execute any one of aspects 31-39.

[0319] Aspect 69: A user equipment comprising a transceiver configured to communicate with a radio access network, a memory, and a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform any one of aspects 41 to 48.

[0320] Aspect 70: An apparatus configured for wireless communication, comprising at least one means for performing any one of aspects 41-48.

[0321] Aspect 71: A non-transitory computer-readable medium storing computer-executable code, the non-transitory computer-readable medium comprising code for causing an apparatus to perform any one of aspects 41-48.

[0322] Aspect 72: A network entity comprising a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform any one of aspects 51 to 56.

[0323] Aspect 73: An apparatus configured for wireless communication, comprising at least one means for performing any one of aspects 51-56.

[0324] Aspect 74: A non-transitory computer-readable medium storing computer-executable code, the non-transitory computer-readable medium comprising code for causing an apparatus to perform any one of aspects 51-56.

[0325] Several aspects of wireless communication networks have been presented with reference to example implementations. As one skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunications systems, network architectures, and communication standards.

[0326] As examples, various aspects may be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile (GSM). Various aspects may also be extended to systems defined by 3rd Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution Data Optimized (EV-DO). Other examples may be implemented within systems employing the Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunications standard, network architecture, and / or communications standard employed will depend on the particular application and the overall design constraints imposed on the system.

[0327] Within this disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration." Any implementation or aspect described herein as "exemplary" should not necessarily be construed as preferred or advantageous over other aspects of the disclosure. Likewise, the term "aspect" does not require that all aspects of the disclosure include the described feature, advantage, or mode of operation. The term "coupled" is used herein to refer to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, then object A and object C may still be considered to be coupled to each other even if they are not in direct physical contact with each other. For example, a first object may be coupled to a second object even if the first object is not in direct physical contact with the second object at all. The terms "circuit" and "circuitry" are used broadly and are not limited with respect to types of electronic circuitry, but are intended to include both hardware implementations of electrical devices and conductors that, when connected and configured, enable the performance of the functions described in this disclosure, and software implementations of information and instructions that, when executed by a processor, enable the performance of the functions described in this disclosure. As used herein, the term "determining" may include, for example, ascertaining, resolving, selecting, choosing, establishing, calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, database, or another data structure), and the like. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like.

[0328] One or more of the components, steps, features, and / or functions shown in Figures 1-23 may be rearranged and / or combined into a single component, step, feature, or function, or embodied in several components, steps, or functions. Additional elements, components, steps, and / or functions may be added without departing from the novel features disclosed herein. The apparatus, devices, and / or components shown in Figures 1, 2, 4, 5, 6, 13, 14, and 19 may be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein may also be efficiently implemented in software and / or incorporated into hardware.

[0329] It is understood that the specific order or hierarchy of steps in the disclosed methods is an example of an example process. Based on design preferences, it is understood that the specific order or hierarchy of steps in the methods may be rearranged. The accompanying method claims present elements of the various steps in a sample order, and are not limited to the specific order or hierarchy presented, unless specifically recited in the method claims.

[0330] The foregoing description is provided to enable any person skilled in the art to practice the various embodiments described herein. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments. Thus, the claims are not limited to the embodiments set forth herein, but are to be accorded the widest scope consistent with the language of the claims, and references to elements in the singular shall mean "one or more" and not "one and only" unless expressly stated otherwise. Unless otherwise stated, the term "several" refers to one or more. A phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. As an example, "at least one of a, b, or c" shall include a, b, c, a and b, a and c, b and c, and a, b, and c. All structural and functional equivalents of the elements of the various embodiments described throughout this disclosure that are known or later become known to those skilled in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be made available to the public, regardless of whether such disclosure is expressly recited in the claims. [Explanation of symbols]

[0331] 100 Wireless communication system 102 Core Network 104 Radio Access Network (RAN), RAN 106 User Equipment (UE) 108 Base Station 110 External Data Network 112 Downlink Traffic 114 Downlink control information 116 Uplink Traffic 118 Uplink Control Information 120 Backhaul 200 Radio Access Network (RAN), RAN 202 Cells 204 Cells 206 Cells 208 Cells 210 base station 212 Base Station 214 Base Station 216 Remote Radio Head (RRH), RRH 220 Unmanned Aerial Vehicle (UAV), UAV 222UE 224UE 226 UE 227 Sidelink Signal 228 UE 230 UE 232 UE 234 UE 236 UE 237 Sidelink Signal 238 UE 240 UE 242 U.S. 302 Subframe 304 Resource Grid 306 Resource Element (RE), Resource Element 308 Resource Block (RB), RB 310 Slots 312 Control Area 314 Data Area 400 Non-aggregated base stations 405 Service Management and Organization (SMO) Framework, SMO Framework 410 Central Unit (CU), CU 411 Open eNB (O-eNB) 415 Non-Real-Time (Non-RT) RIC, Non-RT RIC 420 Core Network 425 Near Real-Time (Near-RT) RAN Intelligent Controller (RIC), Near-RT RIC 430 Distributed Unit (DU), DU 440 Radio Unit (RU), RU 450UE 490 Open Cloud (O-Cloud) 500 Signaling Diagram 502 Network Entity 504UE 600 Wireless Communication System 602 Primary Serving Cell (PCell), PCell 604 Base Station 606 SCell 606a, 606b, 606c, 606d Secondary serving cell (SCell), SCell 608a, 608b, 608c base station 610UE 700 Figures 702 PUCCH Group 704 PCC 706 SCC 708 PDSCH transmission 710 Slots 712 PUCCH transmission 714 Slots 716 Slots 800 Figures 802 PUCCH Group 804 PCC 806 SCC 808 PDSCH transmission 810 Slots 812 PUCCH transmission 814 Slots 816 Slots 900 Figures 902 PUCCH Group 904 PCC 906 First SCC (SCC-1), First SCC 908 Second SCC (SCC-2), Second SCC 910 PDSCH transmission 912 Slots 914 A / N 916 Slots 1000 Figures 1002 PUCCH Group 1004 PCC 1006 First SCC (SCC-1), First SCC 1008 Second SCC (SCC-2), Second SCC 1010 PDSCH transmission 1012 Slots 1014 A / N 1016 Slots 1102 First Action 1104 Second Action 1200 Figures 1202 PUCCH Group 1204 PCC 1206 First SCC (SCC-1), First SCC 1208 Second SCC (SCC-2), Second SCC 1210 PDSCH transmission 1212 Slots 1214 A / N 1216 Slots 1300 Signaling Diagram 1302 Network Entities 1304 UE 1400 UE 1402 Bus 1404 processor 1405 Memory 1406 Computer-readable medium 1408 Bus Interface 1410 Transceiver 1414 Processing System 1415 Carrier Configuration Information 1430 Interface 1441 Communication and Processing Circuits 1442 Feedback Processing Circuit 1443 Resource Control Circuit 1451 Communication and Processing Software 1452 Feedback Processing Software 1453 Resource Control Software 1500 ways 1600 methods 1700 methods 1800 methods 1900 Network Entities 1902 Bus 1904 Processor 1905 Memory 1906 Computer-readable medium 1908 Bus Interface 1910 Transceiver 1914 Processing System 1915 Carrier Configuration Information 1930 Interface 1941 Communication and Processing Circuits 1942 Feedback Control Circuit 1943 Resource Control Circuit 1951 Communications and processing software 1952 Feedback Control Software 1953 Resource Control Software 2000 methods 2100 method 2200 method 2300 methods

Claims

1. A user equipment, A transceiver; Memory, a processor coupled to the transceiver and the memory, the processor and the memory comprising: receiving data from a network entity on a first component carrier of a plurality of component carriers associated with an uplink control channel group; receiving a radio resource control (RRC) message from the network entity, the RRC message including a first indication per component carrier that the user equipment is permitted to transmit feedback for the data on a second component carrier of the plurality of component carriers, the second component carrier being different from the first component carrier; receiving, from the network entity, downlink control information (DCI) configured at least to indicate uplink resources for transmitting the feedback about the data on the second component carrier; decoding the received data and generating the feedback to indicate whether reception of the data by the user equipment was successful; and transmitting the generated feedback to the network entity via the uplink resources of the second component carrier; A user equipment configured to:

2. The processor and the memory and further configured to transmit the feedback on a physical uplink control channel (PUCCH) of the second component carrier after receiving the first indication.

13. The user equipment of claim 1.

3. The processor and the memory and further configured to receive the data on a physical downlink shared channel (PDSCH) of the first component carrier.

3. The user equipment of claim 2.

4. The processor and the memory receiving a second indication that the user equipment is authorized to transmit the feedback for the data on a third component carrier of the plurality of component carriers; selecting one of the second component carrier and the third component carrier for transmitting the feedback; The user equipment of claim 1, further configured to:

5. the first component carrier is a primary component carrier; the second component carrier is a first secondary component carrier; the third component carrier is a second secondary component carrier; 5. A user equipment as claimed in claim 4.

6. 2. The user equipment of claim 1, wherein the uplink control channel group includes a physical uplink control channel (PUCCH) group for uplink carrier aggregation.

7. the second component carrier is a primary component carrier; the first component carrier is a secondary component carrier; 13. The user equipment of claim 1.

8. The processor and the memory receiving a first resource allocation, the first resource allocation being for transmitting the feedback about the data on the first component carrier; receiving a second resource allocation, the second resource allocation being for transmitting the feedback about the data on the second component carrier of the plurality of component carriers; The user equipment of claim 1, further configured to:

9. A method for wireless communication in a user equipment, comprising: receiving data from a network entity on a first component carrier of a plurality of component carriers associated with an uplink control channel group; receiving a Radio Resource Control (RRC) message from the network entity, the RRC message including a first indication per component carrier that the user equipment is permitted to transmit feedback for the data on a second component carrier of the plurality of component carriers, the second component carrier being different from the first component carrier; receiving from the network entity downlink control information (DCI) configured at least to indicate uplink resources for transmitting the feedback about the data on the second component carrier; decoding the received data and generating the feedback to indicate whether reception of the data by the user equipment was successful; transmitting the generated feedback to the network entity via the uplink resources of the second component carrier; A method comprising:

10. A network entity comprising: A transceiver; Memory, a processor coupled to the transceiver and the memory, the processor and the memory comprising: transmitting data to a user equipment on a first component carrier of a plurality of component carriers associated with an uplink control channel group; transmitting a radio resource control (RRC) message to the user equipment, the RRC message including a first indication per component carrier that the user equipment is authorized to transmit feedback for the data on a second component carrier of the plurality of component carriers, the second component carrier being different from the first component carrier; transmitting, to the user equipment, downlink control information (DCI) configured at least to indicate uplink resources for transmitting the feedback about the data on the second component carrier; receiving the feedback from the user equipment via the uplink resources of the second component carrier, the feedback being generated by the user equipment based on decoding the received data to indicate whether reception of the data by the user equipment was successful; and A network entity configured to:

11. A method for wireless communication in a network entity, comprising: transmitting data to a user equipment on a first component carrier of a plurality of component carriers associated with an uplink control channel group; transmitting a Radio Resource Control (RRC) message to the user equipment, the RRC message including a first indication per component carrier that the user equipment is authorized to transmit feedback for the data on a second component carrier of the plurality of component carriers, the second component carrier being different from the first component carrier; transmitting to the user equipment Downlink Control Information (DCI) configured at least to indicate uplink resources for transmitting the feedback about the data on the second component carrier; receiving the feedback from the user equipment via the uplink resources of the second component carrier, the feedback being generated by the user equipment based on decoding the received data to indicate whether reception of the data by the user equipment was successful; A method comprising:

12. A computer program comprising instructions which, when executed by a processor in the user equipment, cause the user equipment to perform the method of claim 9.

13. A computer program comprising instructions which, when executed by a processor in the network entity, cause the network entity to perform the method of claim 11.

Images