Power control for physical uplink control channel (PUCCH) transmissions on secondary component carriers

Abstract

Aspects relate to supporting power control for physical uplink control channel (PUCCH) transmissions on uplink secondary component carriers (SCCs) for wireless communications systems. In some aspects, a user equipment (UE) receives a power control configuration from a base station to be used by the UE for PUCCH transmissions on a selected uplink SCC. The UE then transmits a PUCCH to the base station on the selected uplink SCC based at least in part on the power control configuration. Closed loop and open loop power control examples are provided. In some aspects, a common or shared power control configuration is provided by the base station for use with each component carrier of a PUCCH group. In other aspects, a carrier-specific power control configuration is provided by the base station.

Description

[0001] Cross-reference to related applications

[0002] This patent application claims priority to pending non-provisional application S / N.17 / 410,987 filed with the U.S. Patent and Trademark Office on August 24, 2021, and provisional application S / N.63 / 083,075 filed with the U.S. Patent and Trademark Office on September 24, 2020, both of which have been assigned to the assignee of this application and are hereby expressly incorporated by reference as fully set forth below and for all applicable purposes.

[0003] open field

[0004] The techniques discussed in this article generally relate to wireless communication systems, and more specifically, to power control for physical uplink control channels.

[0005] Related technical descriptions

[0006] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems, which may be referred to as NR systems. These systems can employ various technologies, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each of which simultaneously supports communication from multiple communication devices, which may also be referred to as User Equipment (UE).

[0007] Some wireless communication systems employ carrier aggregation to allow the UE to communicate with the base station using a primary component carrier and multiple secondary component carriers. There is an ongoing need for improvements in power control during uplink transmissions, particularly in conjunction with carrier aggregation.

[0008] Overview

[0009] The following provides an overview of one or more aspects of this disclosure to provide a basic understanding of these aspects. This overview is not an exhaustive summary of all conceived features of this disclosure, nor is it intended to identify any or all key or defining elements of any or all aspects of this disclosure, nor to define the scope of any or all aspects of this disclosure. Its purpose is to present some concepts of one or more aspects of this disclosure in one form as a prelude to the more detailed description that follows.

[0010] In one aspect, a user equipment (UE) is provided, comprising: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory. The processor is configured to: receive from a base station an indicator of a power control configuration, the power control configuration being transmitted by the UE on a physical uplink control channel (PUCCH) on a secondary component carrier in a set of uplink component carriers including a primary component carrier and secondary component carriers; and transmit the PUCCH transmission to the base station on the secondary component carrier, at least in part based on the power control configuration.

[0011] In another aspect, a method for wireless communication used by a UE in a communication network is provided. The method includes: receiving from a base station an indicator of a power control configuration, the power control configuration being used by the UE for PUCCH transmission on a sub-component carrier in an uplink component carrier set including a primary component carrier and a secondary component carrier; and transmitting the PUCCH transmission to the base station on the sub-component carrier, at least in part based on the power control configuration.

[0012] In another aspect, a base station is provided, comprising: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory. The processor is configured to: transmit an indicator of a power control configuration to a UE, the power control configuration being used by the UE for PUCCH transmission on a sub-component carrier in an uplink component carrier set including a primary component carrier and a secondary component carrier; and receive the PUCCH transmission from the UE on the sub-component carrier based at least in part on the power control configuration.

[0013] In another aspect, a method for wireless communication used by a base station in a communication network is provided. The method includes: transmitting to a UE an indicator of a power control configuration, the power control configuration being used by the UE for PUCCH transmission on a sub-component carrier in an uplink component carrier set including a primary component carrier and a secondary component carrier; and receiving the PUCCH transmission from the UE on the sub-component carrier based at least in part on the power control configuration.

[0014] These and other aspects of this disclosure will become more fully understood upon reading the following detailed description. Other aspects, features, and embodiments of this disclosure will be apparent to those skilled in the art after reading the following description of specific exemplary embodiments in conjunction with the accompanying drawings. Although features of this disclosure may be discussed below with respect to certain embodiments and drawings, all embodiments of this disclosure may include one or more of the advantageous features discussed herein. In other words, although one or more embodiments may be discussed having certain advantageous features, one or more of such features may also be used according to the various embodiments of this disclosure discussed herein. Similarly, although exemplary embodiments may be discussed below as embodiments of an apparatus, system, or method, it should be understood that such exemplary embodiments may be implemented in various apparatuses, systems, and methods. Brief description of the attached diagram

[0016] Figure 1 It is a schematic explanation based on some aspects of wireless communication systems.

[0017] Figure 2 This is an explanation based on examples of radio access networks.

[0018] Figure 3 This is a diagram illustrating an example of a frame structure used in a radio access network, based on several aspects.

[0019] Figure 4 This is a block diagram illustrating a wireless communication system that supports multiple-input multiple-output (MIMO) and beamforming communication based on several aspects.

[0020] Figure 5 This is a diagram illustrating an example of a wireless communication system that uses uplink main component carriers and sub-component carriers to separate base stations, based on various aspects of support.

[0021] Figure 6 This is a diagram illustrating an example of a wireless communication system that supports uplink primary component carriers and secondary component carriers (PCC and SCC) to a single base station based on several aspects.

[0022] Figure 7 An example of carrier configuration supporting uplink control on a subcarrier is explained.

[0023] Figure 8 Another example of carrier configuration that supports uplink control on subcarriers is explained, based on several aspects.

[0024] Figure 9 It is a timing diagram explaining the specifications of some aspects, in which power control is provided for the PUCCH of the SCC.

[0025] Figure 10 It is a flowchart explaining the procedures according to some aspects, in which open-loop power control is provided for the PUCCH of SCC.

[0026] Figure 11 This is a flowchart explaining another procedure based on some aspects, in which open-loop power control is provided for the PUCCH of the SCC.

[0027] Figure 12 It is a flowchart explaining the procedures according to some aspects, in which closed-loop power control is provided for the SCC's PUCCH.

[0028] Figure 13 This is a block diagram illustrating carrier-dependent power control aggregation on PCC and SCC based on certain aspects.

[0029] Figure 14 This is a flowchart explaining another procedure based on some aspects, in which closed-loop power control is provided for the PUCCH of the SCC.

[0030] Figure 15 It is a block diagram illustrating an example of the hardware implementation of a base station (or other scheduling entity) based on some aspects.

[0031] Figure 16 It is a block diagram illustrating an example of the hardware implementation of a UE (or other scheduled entity) based on some aspects.

[0032] Figure 17 This is a flowchart illustrating an exemplary process for use by a UE (or other scheduled entity) based on certain aspects.

[0033] Figure 18 This is a flowchart illustrating further aspects of an exemplary process for open-loop power control provided to a UE (or other scheduled entity) based on certain aspects.

[0034] Figure 19 This is a flowchart illustrating further aspects of an exemplary process for a UE (or other scheduled entity) to use for closed-loop power control, based on several aspects.

[0035] Figure 20 This is a flowchart illustrating an exemplary process used by a base station (or other scheduling entity) based on certain aspects.

[0036] Figure 21 This is a flowchart illustrating further aspects of an exemplary process for open-loop power control by a base station (or other scheduling entity) based on certain aspects.

[0037] Figure 22 This is a flowchart illustrating further aspects of an exemplary process for closed-loop power control provided by a base station (or other scheduling entity) according to certain aspects.

[0038] Detailed description

[0039] The detailed description that follows, taken in conjunction with the accompanying drawings, is intended as a description of various configurations and is not intended to represent only the configurations in which the concepts described herein can be practiced. This detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can 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.

[0040] While aspects and embodiments are described herein by way of example, those skilled in the art will understand that additional implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, embodiments and / or devices may arise via integrated chip embodiments and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to particular use cases or applications, broad applicability of the described innovations is possible. Implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations. In some practical contexts, devices incorporating the described aspects and features may also necessarily include additional components and features for implementing and practicing the claimed and described embodiments. For example, the transmission and reception of wireless signals requires 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.). The innovations described herein are intended to be implemented in a wide variety of devices, chip-level components, systems, distributed deployments, end-user equipment, etc., of various sizes, shapes, and configurations.

[0041] User equipment (UE) can be configured for multi-carrier communication using one or more cells associated with one or more primary carriers (e.g., primary component carriers (PCCs)) and one or more secondary carriers (e.g., secondary component carriers (SCCs)). In some examples, these cells may include a group of physical uplink control channels (PUCCHs) associated with the UE for multi-carrier communication. One cell may be designated as a primary cell (PCell), while one or more other cells may be designated as secondary cells (SCells). A PCell may be associated with a PCC (e.g., a primary carrier), and each SCell may be associated with one or more SCCs (e.g., secondary carriers). However, note that the UE may use both primary and secondary component carriers to transmit data to a single base station. Therefore, these secondary SCCs are not necessarily associated with separate base stations. Instead, a single base station may act as both the PCell and SCell for uplink transmissions from the UE, wherein the base station includes separate radio frequency (RF) receive chains for separately receiving and processing transmissions from the UE on the PCCs and SCCs.

[0042] Furthermore, some carriers can be configured for Time Division Duplex (TDD), where each transmission opportunity (e.g., each symbol, mini-slot, slot, etc.) is designated as a downlink transmission opportunity, an uplink transmission opportunity, or a flexible transmission opportunity (e.g., a slot can be used for uplink or downlink communication and may include handover gaps for the UE to revert from downlink transmission to uplink transmission or vice versa). Some carriers can be configured for Frequency Division Duplex (FDD), where a transmission opportunity can be used for uplink or downlink communication. In some wireless communication systems, the UE may be limited to transmitting uplink control information within, for example, the Physical Uplink Control Channel (PUCCH) on the primary carrier. However, when the primary carrier is a TDD carrier (among other things), this can lead to large latency for PUCCH transmissions due to uplink / downlink / flexible slot configurations or modes (e.g., uplink transmission may not be allowed in a TDD slot configured with all downlink symbols).

[0043] Therefore, the aspects of the techniques described herein address the aforementioned and other problems by providing mechanisms in which the UE can transmit uplink control information, for example, within the PUCCH, on a subcarrier, or on both the primary and subcarriers. For example, techniques for power control supporting PUCCH transmission over the SCC are described.

[0044] In some aspects, the UE receives an indicator of a power control configuration from a base station, which is transmitted by the UE over a selected SCC for an uplink aggregated component carrier set, wherein the uplink component carrier set includes a PCC and one or more SCCs. This indicator may be, for example, parameters provided within downlink control information (DCI) for closed-loop power control and radio resource control (RRC) signaling for open-loop power control. The UE then transmits the PUCCH to the base station over that SCC, at least in part, based on the power control configuration. Note that in the above example, the aggregated component carrier is an uplink component carrier. It should also be noted that in many of the examples described herein, uplink transmissions from the UE are sent to a single base station that acts as both a PCell and an SCell for both PCC and SCC uplink transmissions. At least some aspects described herein also apply to PCC / SCC uplink transmissions to separate base stations, one of which acts as a PCell for uplink PCC transmissions from the UE, while the separate base stations act as SCells for uplink SCC transmissions from the UE.

[0045] In some respects, the indicator is configured to indicate or specify the open-loop power control configuration, such as by providing a common (or shared) open-loop target receive power value (PC) for the PCC and SCC used for PUCCH. O For example, the indicator can indicate the nominal PUCCH power value (P). O_nominal_PUCCH The shared or common value of the power setting value (p0-Set) indicates the shared open-loop target received power value (P). O In other words, the UE can use the same P. O_nominal_PUCCH The p0-Set value is used for PCC PUCCH transmission and SCC PUCCH transmission.

[0046] In other respects, the indicator can indicate the carrier-specific open-loop target received power value (PC) for PCC and SCC. O For example, the indicator can be obtained through P for each component carrier. O_nominal_PUCCH The p0-Set indicator is a separate value used to indicate the open-loop target received power value (P) that varies depending on the carrier. O In other words, the UE can connect different P... O_nominal_PUCCH The p0-Set value is used for PCC PUCCH transmission and different SCC PUCCH transmissions on different SCCs. In some examples, 16 uplink SCCs are provided together with the uplink PCC in a wireless communication system.

[0047] In other respects, the indicator is configured to indicate or specify closed-loop power control commands or configurations, such as by specifying carrier-specific cumulative closed-loop power control (where power control (PC) values ​​are accumulated separately for PCC and SCC). In other examples, the indicator is configured to indicate or specify carrier-specific absolute power control (where PC values ​​are accumulated for neither PCC nor SCC). In this way, problems related to handling PC values ​​obtained from PCC and SCC are resolved.

[0048] For wireless communication systems that support both enhanced mobile broadband (eMBB) and ultra-reliable low latency communication (URLLC) transmissions, separate power control configuration indicators can be provided for eMBB and URLLC to allow for individual power control; for example, one can be configured for open-loop power control and the other for closed-loop power control. This addresses the issues related to the handling of eMBB and URLLC.

[0049] Before discussing other technologies in detail, an overview of wireless communication systems is provided. However, it should be noted that the various concepts presented throughout this disclosure can be implemented across a wide variety of telecommunications systems, network architectures, and communication standards.

[0050] Now refer to Figure 1 The various aspects of this disclosure are explained with reference to a wireless communication system 100, by way of illustrative example and not limitation. The wireless communication system 100 includes three interaction domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. The wireless communication system 100 enables the UE 106 to perform data communication with an external data network 110 (such as, but not limited to, the Internet).

[0051] RAN 104 can implement any suitable one or more wireless communication technologies to provide radio access to UE 106. As an example, RAN 104 can operate according to the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification (commonly referred to as 5G). As another example, RAN 104 can operate in a hybrid of 5G NR and the Evolved Universal Terrestrial Radio Access Network (eUTRAN) standard (commonly referred to as LTE). 3GPP refers to this hybrid RAN as Next Generation RAN, or NG-RAN. Of course, many other examples can be utilized within the scope of this disclosure.

[0052] As explained, RAN 104 includes multiple base stations 108. Broadly speaking, a base station is a network element in a radio access network responsible for radio transmissions to and from a UE in one or more cells. In different technologies, standards, or contexts, a base station may be 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), extended service set (ESS), access point (AP), B-node (NB), evolved B-node (eNB), next-generation B-node (gNB), transmit / receive point (TRP), or some other suitable term. In some examples, a base station may include two or more co-located or non-co-located TRPs. Each TRP may communicate on the same or different carrier frequencies within the same or different frequency bands. In an example where RAN 104 operates according to both LTE and 5G NR standards, one of these base stations may be an LTE base station, while the other may be a 5G NR base station.

[0053] Radio access network 104 is further described as supporting wireless communication for multiple mobile devices. In 3GPP standards, a mobile device may be referred to as User Equipment (UE), but may also be referred to by those skilled in the art as a mobile station (MS), subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal (AT), mobile terminal, radio terminal, remote terminal, handheld device, terminal, user agent, mobile client, client, or any other suitable term. A UE may be a device (e.g., a mobile device) that provides users with access to network services.

[0054] In this document, a “mobile” device does not necessarily need to be mobile and may be stationary. The term mobile device or mobile equipment refers to a wide variety of devices and technologies. A UE may include several hardware structural components that are sized, shaped, and arranged 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 devices, cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), laptops, netbooks, smartbooks, tablets, personal digital assistants (PDAs), and a wide variety of embedded systems, such as those corresponding to the “Internet of Things” (IoT). Additionally, mobile devices can be automobiles or other transportation vehicles, remote sensors or actuators, robots or robotic equipment, satellite radios, Global Positioning System (GPS) devices, object tracking devices, drones, multi-rotor aircraft, quadcopters, remote control devices, consumer and / or wearable devices (such as glasses), wearable cameras, virtual reality devices, smartwatches, health or fitness trackers, digital audio players (e.g., MP3 players), cameras, game consoles, etc. Mobile devices can also be digital home or smart home devices, such as home audio, video and / or multimedia equipment, appliances, vending machines, smart lighting equipment, home security systems, smart meters, etc. Mobile devices can also be smart energy devices, security devices, solar panels or solar arrays, municipal infrastructure equipment controlling electricity, lighting, and water (e.g., smart grids), industrial automation and enterprise equipment; logistics controllers; agricultural equipment, etc. Furthermore, mobile devices can provide connected or telemedicine support, such as remote healthcare. Remote healthcare devices may include remote healthcare monitoring devices and remote healthcare supervision devices, whose communications may be given priority or preferential access over other types of information, for example, in the form of priority access for critical service data transmission and / or relevant QoS for critical service data transmission.

[0055] Wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) can be referred to as downlink (DL) transmissions. According to certain aspects of this disclosure, the term downlink can refer to point-to-multipoint transmissions originating at a base station (e.g., base station 108). Another way to describe this scheme is to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. According to a further aspect of this disclosure, the term uplink can refer to point-to-point transmissions originating at a UE (e.g., UE 106).

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

[0057] Base station 108 is not the only entity that can be used as a scheduling entity. That is, in some examples, a UE can be used as a scheduling entity to schedule resources for one or more scheduled entities (e.g., one or more other UEs). And as discussed below, a UE can communicate directly with other UEs in a peer-to-peer manner and / or in a relay configuration.

[0058] like Figure 1 As explained, scheduling entity 108 may broadcast downlink traffic 112 to one or more scheduled entities 106 (e.g., one or more UEs 106). Broadly speaking, scheduling entity 108 is a node or device responsible for scheduling traffic (including downlink traffic 112 and, in some examples, uplink traffic 116 from one or more scheduled entities 106 (e.g., one or more UEs 106) to scheduling entity 108) in a wireless communication network. On the other hand, scheduled entity 106 (e.g., UE 106) is a node or device that receives downlink control information 114 (including, but not limited to, scheduling information (e.g., permission), synchronization or timing information), or other control information) from another entity in the wireless communication network (such as scheduling entity 108).

[0059] Additionally, uplink and / or downlink control information and / or traffic information can be transmitted on a waveform that can be temporally divided into frames, subframes, time slots, and / or symbols. As used herein, a symbol may refer to a time unit in an Orthogonal Frequency Division Multiplexing (OFDM) waveform that carries one resource element (RE) per subcarrier. A time slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 ms. Multiple subframes or time 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, wherein each frame comprises, for example, 10 subframes, each 1 ms in length. Of course, these definitions are not mandatory, and any suitable scheme may be used to organize the waveform, and various time divisions of the waveform may have any suitable duration.

[0060] Generally, base station 108 may include a backhaul interface for communicating with the backhaul section 120 of a wireless communication system. Backhaul 120 provides a link between base station 108 and core network 102. Furthermore, in some examples, the backhaul network provides interconnection between the respective base stations 108. Various types of backhaul interfaces can be employed, such as a direct physical connection using any suitable transport network, a virtual network, etc.

[0061] Core network 102 may be part of wireless communication system 100 and may be independent of the radio access technology used in RAN 104. In some examples, core network 102 may be configured according to 5G standards (e.g., 5GC). In other examples, core network 102 may be configured according to 4G evolved packet core (EPC) or any other suitable standard or configuration.

[0062] Now refer to Figure 2 The illustrative explanation of RAN 200 is provided as an example, not a limitation. In some examples, RAN 200 may be used in conjunction with the above description and in Figure 1 The RAN 104 in the Chinese explanation is the same.

[0063] The geographical area covered by RAN 200 can be divided into cellular areas (cells), which can be uniquely identified by user equipment (UE) based on an identifier broadcast from an access point or base station. Figure 2 Cells 202, 204, 206, and 208 are described, each of which may include one or more sectors (not shown). A sector is a sub-area 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 identifier belonging to that sector. In a cell divided into sectors, multiple sectors within the cell may be formed by an antenna array, where each antenna is responsible for communication with UEs within a portion of the cell.

[0064] It can be deployed using various base stations. For example, in Figure 2In this example, two base stations (base station 210 and base station 212) are shown in cells 202 and 204. A third base station (base station 214) is shown as a remote radio head (RRH) 216 controlling cell 206. That is, the base station may have an integrated antenna, or it may be connected to the antenna or RRH 216 by a feed cable. In the illustrated example, cells 202, 204, and 206 may be referred to as macrocells because base stations 210, 212, and 214 support cells with large sizes. Furthermore, base station 218 is shown in cell 208, which may overlap with one or more macrocells. In this example, cell 208 may be referred to as a small cell (e.g., microcell, picocell, femtocell, home base station, home B-node, home evolved B-node, etc.) because base station 218 supports cells with relatively small sizes. Cell size settings can be determined based on system design and component constraints.

[0065] It will be understood that RAN 200 may include any number of radio base stations and cells. Furthermore, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, and 218 provide radio access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be connected to the network described above and in... Figure 1 The base station / scheduling entity 108 described in the Chinese explanation is the same.

[0066] Figure 2 This further includes an unmanned aerial vehicle (UAV) 220, which may be a drone or a quadcopter. The UAV 220 can be configured to function as a base station, or more specifically as a mobile base station. That is, in some examples, the cell may not be stationary, and the geographical area of ​​the cell may move depending on the location of the mobile base station (such as the UAV 220).

[0067] Within RAN 200, a cell may include UEs capable of communicating with one or more sectors of each cell. Furthermore, each base station 210, 212, 214, 218, and 220 may be configured to provide all UEs in the respective cell to the core network 102 (see [link to core network 102]). Figure 1Access points. For example, UEs 222 and 224 may communicate with base station 210; UEs 226 and 228 may communicate with base station 212; UEs 230 and 232 may communicate with base station 214 via RRH 216; UE 234 may communicate with base station 218; and UE 236 may communicate with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240 and / or 242 may communicate with the access points described above and in... Figure 1 The UE / scheduled entity 106 described in the text is the same as or similar to the UE. In some examples, the UAV 220 (e.g., a quadcopter) can be a mobile network node and can be configured to act as a UE. For example, the UAV 220 can operate within cell 202 by communicating with base station 210.

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

[0069] In RAN 200, the ability of a UE to communicate independently of its location while moving is referred to as mobility. The various physical channels between the UE and the RAN are generally defined within the Access and Mobility Management Function (AMF, not explained). Figure 1 The AMF is established, maintained, and released under the control of the core network 102 (part of the core network). In some scenarios, the AMF may include Security Context Management (SCMF) and Security Anchor Function (SEAF) for performing authentication. The SCMF can manage the security context of both the control plane and user plane functionalities, either overall or in part.

[0070] In some examples, RAN 200 enables mobility and handover (i.e., the UE's connection is transferred from one radio channel to another). For example, during a call with a scheduling entity, or at any other time, the UE can monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Depending on the quality of these parameters, the UE can maintain communication with one or more 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 can perform a handover or handover from the serving cell to a neighboring (target) cell. For example, UE 224 (explained as a means of transportation, but any suitable form of UE may be used) can move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to a neighboring cell 206. When the signal strength or quality from the neighboring cell 206 exceeds the signal strength or quality of its serving cell 202 for a given amount of time, UE 224 can transmit a report message indicating this condition to its serving base station 210. In response, UE 224 may receive a handover command and may undergo a handover to cell 206.

[0071] To achieve a low block error rate (BLER) while still maintaining a very high data rate over RAN 200, channel coding can be used. That is, wireless communication typically utilizes appropriate error-correcting block codes. In a typical block code, an information message or sequence is broken down into coded code blocks (CBs), and an encoder (e.g., CODEC) at the transmitting device then mathematically adds redundancy to the information message. This redundancy in the coded information message improves message reliability, thereby enabling the correction of any bit errors that may occur due to noise.

[0072] In earlier 5G NR specifications, quasi-cyclic low-density parity-check (LDPC) with two different basemaps was used to encode user data traffic: one basemap was used for large code blocks and / or high code rates, while the other basemap was used for other cases. Polarity decoding was used based on nested sequences to decode control information and the physical broadcast channel (PBCH). For at least some of these channels, puncturing, shortening, and repetition were used for rate matching.

[0073] However, those skilled in the art will understand that aspects of this disclosure can be implemented using any suitable channel code. Various implementations of the scheduling entity and the scheduled entity may include suitable hardware and capabilities (e.g., encoders, decoders, and / or CODECs) to utilize one or more of these channel codes for wireless communication.

[0074] In various implementations, the air interface in RAN 200 can utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically 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 shared use of a portion of the spectrum without a government-granted license. While some technical rules generally still apply to accessing unlicensed spectrum, access is available to any operator or device. Shared spectrum falls between licensed and unlicensed spectrum, where technical rules or restrictions may be required for spectrum access, but the spectrum may still be shared by multiple operators and / or multiple RATs. For example, a licensee of a portion of licensed spectrum can provide Licensed Shared Access (LSA) to share that spectrum with other parties, for example, by utilizing conditions determined by the appropriate licensee.

[0075] The air interface in RAN 200 can utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication between individual devices. For example, the 5G NR specification utilizes Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) to provide multiple access for UL transmissions from UEs 222 and 224 to base station 210, and to provide multiplexing for DL ​​transmissions from base station 210 to one or more UEs 222 and 224. Additionally, for UL transmissions, the 5G NR specification provides support for Discrete Fourier Transform Extended OFDM (DFT-s-OFDM) with CP (also known 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 can be provided using Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Sparse Code Multiple Access (SCMA), Resource Extended Multiple Access (RSMA), or other suitable multiple access schemes. In addition, multiplexing of DL transmissions from base station 210 to UEs 222 and 224 can be provided using 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.

[0076] The air interface in RAN 200 can further utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link where 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 can send information to the other endpoint at a time. Half-duplex simulation is typically implemented for wireless links using Time Division Duplex (TDD). In TDD, transmissions in different directions on a given channel are separated using time division multiplexing. That is, in some scenarios, the channel is dedicated to transmissions in one direction, while at other times, the channel is dedicated to transmissions in the other direction, where the direction can change very rapidly, for example, several times per time slot. In wireless links, full-duplex channels generally rely on physical isolation between the transmitter and receiver, and appropriate interference cancellation techniques. Full-duplex simulation is typically implemented for wireless links using Frequency Division Duplex (FDD) or Space Division Duplex (SDD). In FDD, transmissions in different directions can operate at different carrier frequencies (e.g., within paired spectrum). In SDD, transmissions in different directions on a given channel are separated from each other using spatial division multiplexing (SDM). In other examples, full-duplex communication can be implemented within unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different subbands of the carrier bandwidth. This type of full-duplex communication may be referred to herein as Subband Full-Duplex (SBFD), also known as flexible duplex.

[0077] Reference Figure 3 The OFDM waveforms illustrated herein are used to describe various aspects of this disclosure. Those skilled in the art will understand that various aspects of this disclosure can be applied to SC-FDMA waveforms in substantially the same manner as described below. That is, while some examples of this disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to SC-FDMA waveforms.

[0078] Now refer to Figure 3 An expanded view of exemplary subframe 302 is illustrated, showing the OFDM resource grid. However, as those skilled in the art will readily appreciate, the PHY transport architecture for any particular application can vary from the example described herein depending on any number of factors. Here, time is in the horizontal direction in units of OFDM symbols; while frequency is in the vertical direction in units of the carrier's subcarriers.

[0079] Resource grid 304 can be used to schematically represent time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple antenna ports available, there can be corresponding multiple resource grids 304 available for communication. Resource grid 304 is divided into multiple resource elements (REs) 306. An RE (which is 1 subcarrier × 1 symbol) is the smallest discrete part of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation used in a particular implementation, each RE may represent one or more information bits. In some examples, an RE block may be referred to as a physical resource block (PRB) or resource block (RB) 308, which contains any suitable number of coherent subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers, the number of which is independent of the parameter design used. In some examples, depending on the parameter design, an RB may include any suitable number of coherent OFDM symbols in the time domain. Within this disclosure, it is assumed that a single RB (such as RB 308) corresponds exactly to a single communication direction (transmission or reception for a given device).

[0080] A set of contiguous or discontinuous resource blocks may be referred to herein as a resource block group (RBG), subband, or bandwidth portion (BWP). A set of subbands or BWPs can span the entire bandwidth. Scheduling of a scheduled entity (e.g., a UE) for downlink, uplink, or sidelink transmissions typically involves scheduling one or more resource elements 306 within one or more subbands or bandwidth portions (BWPs). Thus, the 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 the UE. Therefore, the more RBs scheduled for the UE and the higher the modulation scheme selected for the air interface, the higher the UE's data rate. RBs can be scheduled by base stations (e.g., gNB, eNB, etc.) or can be self-scheduled by the UE implementing D2D sidelink communication.

[0081] In this explanation, RB 308 is shown to occupy less than the entire bandwidth of subframe 302, where some subcarriers above and below RB 308 are explained. In a given implementation, subframe 302 may have bandwidth corresponding to any number of one or more RB 308s. Furthermore, in this explanation, RB 308 is shown to occupy less than the entire duration of subframe 302, but this is merely one possible example.

[0082] Each 1ms subframe 302 may include one or more adjacent time slots. As an illustrative example, in... Figure 3In the example shown, a subframe 302 includes four time slots 310. In some examples, time slots may be defined based on a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include mini-time slots with shorter durations (e.g., one or two OFDM symbols). In some cases, these mini-time slots, or shortened transmission time intervals (TTIs), may occupy resources scheduled for ongoing time slot transmissions for the same or different UEs. Any number of resource blocks may be utilized within a subframe or time slot.

[0083] An expanded view of time slot 310 illustrates time slot 310 including control region 312 and data region 314. Generally, control region 312 may carry control channels, while data region 314 may carry data channels. Of course, a time slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 3 The structure described herein is merely exemplary in nature and may utilize different time-slot structures, and may include one or more for each of the control region and data region.

[0084] Although not in Figure 3 The explanation is as follows: Each RE 306 within RB 308 can be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within RB 308 can also carry pilot or reference signals. These pilot or reference signals can be used by the receiver equipment to perform channel estimation for the corresponding channels, which enables coherent demodulation / detection of the control and / or data channels within RB 308.

[0085] In some examples, time slot 310 can be used for broadcast or unicast communication. For example, broadcast, multicast, or ensemble communication can refer to point-to-multipoint transmission from one device (e.g., a base station, UE, or other similar device) to other devices. Here, broadcast communication is delivered to all devices, while multicast communication is delivered to multiple intended receiving devices. Unicast communication can refer to point-to-point transmission from one device to a single other device.

[0086] In an example of cellular communication over a cellular carrier via the Uu interface, for DL ​​transmission, a scheduling entity (e.g., a base station) may allocate one or more REs 306 (e.g., within control area 312) to carry DL control information, including one or more DL control channels (such as the Physical Downlink Control Channel (PDCCH)), destined for one or more scheduled entities (e.g., UEs). The PDCCH carries downlink control information (DCI), including but not limited to power control commands for DL ​​and UL transmissions (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 RE assignments. The PDCCH may further carry HARQ feedback transmissions, such as acknowledgment (ACK) or negative acknowledgment (NACK). HARQ is a technique well known to those skilled in the art, where, for accuracy, any suitable integrity verification mechanism (such as a checksum or cyclic redundancy check (CRC)) may be used to verify the integrity of packet transmissions at the receiving side. If the integrity of the transmission is acknowledged, an ACK may be transmitted, and if not, a NACK may be transmitted. In response to NACK, the transmitting device can send a HARQ retransmission, which enables catch-up retransmission, incremental redundancy, and so on.

[0087] The base station may further allocate one or more REs 306 (e.g., in control area 312 or data area 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). SSBs may be broadcast at regular intervals based on periodicity (e.g., 5, 10, 20, 40, 80, or 160 milliseconds). SSBs include the primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast control channel (PBCH). The UE may utilize the PSS and SSS to achieve radio frame, subframe, time 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.

[0088] The PBCH in the SSB may further include: a Master Information Block (MIB), which includes various system information and parameters for decoding the System Information Block (SIB). The SIB may be, for example, System Information Type 1 (SIB1), which may include various additional system information. Together, the MIB and SIB1 provide the 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 parameter design), system frame number, configuration of the PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), cell prohibition indicator, cell reselection indicator, raster offset, and search space for SIB1. Examples of residual 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).

[0089] In UL transmissions, the scheduled entity (e.g., the UE) may use one or more RE 306s to carry UL control information (UCI) to the scheduling entity. This UL control information includes one or more UL control channels, such as the Physical Uplink Control Channel (PUCCH). The UCI may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. Examples of uplink reference signals may include probe reference signals (SRS) and uplink DMRS. In some examples, the UCI may include a scheduling request (SR), i.e., a request for the scheduling entity to schedule uplink transmissions. Here, in response to an SR transmitted on the UCI, the scheduling entity may transmit downlink control information (DCI), which can schedule resources for uplink packet transmissions. The UCI may also include HARQ feedback, channel state feedback (CSF) (such as CSI reports), or any other suitable UCI.

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

[0091] In an example of sidelink communication on a sidelink carrier via the PC5 interface, the control area 312 of time slot 310 may include a Physical Sidelink Control Channel (PSCCH), which includes sidelink control information (SCI) transmitted by an initiating (transmitting) sidelink device (e.g., a V2X or other sidelink device) toward a set of one or more other receiving sidelink devices. The data area 314 of time slot 310 may include a Physical Sidelink Shared Channel (PSSCH), which includes sidelink data traffic transmitted by the initiating (transmitting) sidelink device within resources reserved on the sidelink carrier by the transmitting sidelink device via the SCI. Further information may be transmitted on the respective REs 306 within time slot 310. For example, HARQ feedback information may be transmitted from the receiving sidelink device to the transmitting sidelink device in the Physical Sidelink Feedback Channel (PSFCH) within time slot 310. In addition, one or more reference signals, such as sidelink SSB, sidelink CSI-RS, sidelink SRS and / or sidelink positioning reference signal (PRS), can be transmitted in time slot 310.

[0092] These physical channels are typically multiplexed and mapped to transport channels for processing by the Media Access Control (MAC) layer. The transport channel carries blocks of information, called transport blocks (TBs). The transport block size (TBS) (which may correspond to the number of information bits) can be a controlled parameter based on the modulation and coding scheme (MCS) and the number of redundancies (RBs) in a given transmission.

[0093] The above description and in Figures 1 to 3 The channels or carriers described are not necessarily all the channels or carriers that can be used between the scheduling entity 108 and the scheduled entity 106, and those skilled in the art will recognize that other channels or carriers, such as other traffic, control, and feedback channels, can be used in addition to those described.

[0094] These physical channels are typically multiplexed and mapped to transport channels for processing by the Media Access Control (MAC) layer. The transport channel carries blocks of information, called transport blocks (TBs). The transport block size (TBS) (which may correspond to the number of information bits) can be a controlled parameter based on the modulation and coding scheme (MCS) and the number of redundancies (RBs) in a given transmission.

[0095] In some respects, the scheduling entity and / or the scheduled entity can be configured for beamforming and / or multiple-input multiple-output (MIMO) techniques. Figure 4An example of a MIMO-enabled wireless communication system 400 has been described. In the MIMO system, transmitter 402 includes multiple transmit antennas 404 (e.g., N transmit antennas), and receiver 406 includes multiple receive antennas 408 (e.g., M receive antennas). Thus, there are N×M signal paths 410 from the transmit antennas 404 to the receive antennas 408. Each of transmitter 402 and receiver 406 may be implemented, for example, in scheduling entity 108, scheduled entity 106, or any other suitable wireless communication device.

[0096] The use of such multi-antenna techniques enables wireless communication systems to utilize the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing can be used to simultaneously transmit different data streams (also known as layers) on the same time-frequency resources. These data streams can be transmitted to a single UE to increase the data rate or to multiple UEs to increase the overall system capacity, the latter being known as multi-user MIMO (MU-MIMO). This is achieved by spatially precoding each data stream (i.e., multiplying these data streams by different weights and phase shifts) and then transmitting each spatially precoded stream over multiple transmit antennas on the downlink. The spatially precoded data streams arrive at the UE with different spatial signatures, which allow each UE to recover one or more data streams intended for that UE. On the uplink, each UE transmits spatially precoded data streams, which allows the base station to identify the source of each spatially precoded data stream.

[0097] The number of data streams or layers corresponds to the transmission rank. Generally, the rank of a MIMO system 400 is limited by the lower of the number of transmit or receive antennas 404 or 408. Additionally, channel conditions at the UE and other considerations (such as available resources at the base station) can also affect the transmission rank. For example, the rank assigned to a particular UE on the downlink (and therefore the number of data streams) can be determined based on a rank indicator (RI) transmitted from that UE to the base station. The RI can be determined based on the antenna configuration (e.g., the number of transmit and receive antennas) and the measured signal-to-interference-plus-noise ratio (SINR) on each receive antenna. The RI can indicate, for example, the number of layers that can be supported under the current channel conditions. The base station can use the RI along with resource information (e.g., available resources and the amount of data to be scheduled for the UE) to assign a transmission rank to the UE.

[0098] In a Time Division Duplex (TDD) system, UL and DL are reciprocal, with each using different time slots of the same frequency bandwidth. Therefore, in a TDD system, the base station can assign a rank for DL ​​MIMO transmission based on UL SINR measurements (e.g., based on a probe reference signal (SRS) or other pilot signal transmitted from the UE). Based on the assigned rank, the base station can then transmit CSI-RS using separate C-RS sequences for each layer to provide multi-layer channel estimation. According to the CSI-RS, the UE can measure channel quality across layers and resource blocks and feed back Channel State Information (CSI). CSI may include, for example, a Channel Quality Indicator (CQI) indicating to the base station the modulation and coding scheme (MCS) used for transmission to the UE, an RI indicating to the base station the number of layers used for transmission to the UE, a Precoding Matrix Indicator (PMI) indicating to the base station the precoding matrix used for transmission to the UE, and other suitable parameters.

[0099] In one example, such as Figure 4 As shown, rank-2 spatial multiplexing transmission on a 2x2 MIMO antenna configuration delivers one data stream from each transmit antenna 404. Each data stream arrives at each receive antenna 408 along a different signal path 410. Receiver 406 can then reconstruct these data streams using the signals received from each receive antenna 408.

[0100] Beamforming is a signal processing technique used in conjunction with antenna arrays for directional signal transmission and / or reception. Each antenna in the array transmits a signal in a manner that causes signals at a specific angle to experience constructive interference while other signals experience destructive interference, in combination with signals from other antennas in the same array. To create the desired constructive / destructive interference, transmitter 402 or receiver 406 may apply amplitude and / or phase shifts to the signals transmitted or received from each of the antennas 404 or 408 associated with transmitter 402 or receiver 406.

[0101] Figure 5 An example of a wireless communication system 500 supporting both primary and secondary component carriers has been explained. In some examples, the wireless communication system 500 can implement... Figure 1-4 The wireless communication system 500 may include base stations 505, 510, 515 and / or UE 520, which may be examples of the corresponding devices described herein. In some aspects, base stations 505, 510 and 515 may constitute or otherwise form a PUCCH group for UE 520 to support multicarrier communication using at least a primary carrier and one or more subcarriers.

[0102] UE 520 can be configured for multi-carrier communication using one or more cells associated with at least a primary carrier (e.g., PCC) and a secondary carrier (e.g., SCC). These cells can form a PUCCH group associated with UE 520 for multi-carrier communication. Figure 5 In the illustrated example, base stations 505, 510, and 515 can be considered as cells within the PUCCH group used for UE 520 and thus forming a PUCCH group. One cell (e.g., base station 505) can be designated as a PCell, while other cells (e.g., base stations 510 and 515) can be designated as secondary cells. A PCell can be associated with a PCC (e.g., a primary carrier), and each secondary cell can be associated with one or more SCCs (e.g., secondary carriers). For example, base station 510 can be associated with a first secondary carrier (e.g., SCC1), and base station 515 can be associated with a second or additional secondary carrier (e.g., SCC2).

[0103] Furthermore, some carriers can be configured for TDD, where each transmission opportunity (e.g., each symbol, mini-slot, slot, etc.) is designated as a downlink transmission opportunity, an uplink transmission opportunity, or a flexible transmission opportunity (e.g., a slot can be used for uplink or downlink communication and may include handover gaps for the UE to revert from downlink transmission to uplink transmission or vice versa). Some carriers can be configured for FDD, where transmission opportunities (e.g., slots) can be used for both uplink and downlink communication simultaneously. In some wireless communication systems, the UE is only permitted to transmit PUCCH information on the primary carrier. However, when the primary carrier is a TDD carrier, this can lead to large latency for PUCCH transmission due to uplink / downlink / flexible slot configurations or modes (e.g., uplink transmission may not be allowed in a TDD slot configured with all downlink symbols). Therefore, aspects of the described techniques provide a mechanism in which the UE 520 is able to transmit PUCCH on subcarriers (e.g., SCC1 and / or SCC2) while performing power control.

[0104] For example, UE 520 may receive downlink transmissions (e.g., PDCCH and / or PDSCH) from the cells of the PUCCH cluster on a primary carrier (e.g., on the PCC from base station 505) and / or on a secondary carrier (e.g., on SCC1 from base station 510 and / or on SCC2 from base station 515). UE 520 may identify or otherwise determine feedback information based on the downlink transmission (e.g., based on whether UE 520 can successfully decode ACK / NACK information of the downlink transmission, channel measurement reports associated with the downlink transmission (e.g., CSI-RS measurement reports), etc.). UE 520 may then select a primary carrier (e.g., PCC) and / or a secondary carrier (e.g., SCC1 and / or SCC2) to transmit the feedback information to the base station (e.g., base station 505 if UE 520 selects PCC; base station 510 if UE 520 selects SCC1, etc.). UE 520 can select a primary carrier and / or a secondary carrier for transmitting feedback messages (e.g., PUCCH transmission) that include feedback information to the base station (depending on which carrier UE 520 selects for PUCCH transmission).

[0105] In some aspects, this may include, when using TDD for uplink carrier aggregation (e.g., when all CCs in the PUCCH group are TDD carriers), base station 505 (PCell in this example) may (e.g., in the time domain) configure the TDD mode in an interleaved / complementary manner such that there exists a maximum number of time slots supporting uplink transmission across all CCs. Base station 505 may transmit or otherwise communicate to UE 520 a signal configuring the time slot format mode, for example, in Radio Resource Control (RRC) signaling, Media Access Control Element (MAC CE), DCI, etc. In a non-limiting example, this may include base station 505 configuring the time slot format mode such that at least one carrier is available for UE 520 to use for uplink transmission in each time slot. For example, UE 520 may receive a signal configuring the time slot format mode for the primary carrier and / or secondary carriers, wherein the time slot modes for different carriers are selected such that instances of uplink time slots are interleaved to occur more frequently.

[0106] exist Figure 5In the examples described, it should be understood that various carrier TDD / FDD configurations can be supported. That is, PCC, SCC1, and / or SCC2 can be any combination of TDD carriers, FDD carriers, or TDD / FDD carriers. In one example, PCC can be a TDD carrier, and SCC1 and / or SCC2 can be FDD carriers. In another example, PCC can be an FDD carrier, and SCC1 and / or SCC2 can be TDD carriers. In yet another example, SCC1 can be a TDD carrier and SCC2 can be an FDD carrier, or vice versa. Therefore, aspects of the described techniques can be applied to any configuration of TDD / FDD carriers in a PUCCH group.

[0107] In some aspects, this may include configuring PUCCH resources on each carrier in the PUCCH group to support PUCCH transmission on subcarriers. For example, UE 520 may receive signals from base station 505 configuring a first resource set for transmitting feedback messages on a primary carrier (e.g., on the PCC), a second resource set for transmitting feedback messages on a subcarrier (e.g., SCC1), a third resource set for transmitting feedback messages on an additional subcarrier (e.g., SCC2), and so on. These resources may include time resources, frequency resources, spatial resources, and / or code resources allocated for transmitting PUCCH on the respective carriers. In some aspects, UE 520 may select a primary carrier (e.g., the PCC) or a subcarrier (e.g., SCC1 and / or SCC2) for transmitting feedback messages based on the configured resources and the resources required for transmitting feedback messages. For example, UE 520 may determine the resource usage for transmitting feedback messages and select the primary carrier and / or subcarrier for transmitting feedback messages based on the available resources configured for the primary carrier and / or subcarrier.

[0108] In some respects, the indication / determination of which carrier the UE 520 will use to transmit the PUCCH (e.g., including feedback messages) can be: based on predefined priority rules, dynamically indicated (e.g., in DCI), or semi-statically indicated (e.g., using RRC signaling), etc. Therefore, the UE 520 can determine the priority rules associated with transmitting feedback messages on the primary and secondary carriers, and select the carrier for transmitting the feedback messages based on those priority rules.

[0109] Therefore, UE 520 can be configured with default rules or priority rules (e.g., by base station 505, which in this example is PCell). Without additional signaling, these default rules or priority rules can correspond to a first priority level associated with PCC, a second priority level associated with SCC1, a third priority level associated with SCC2, and so on. In some non-limiting examples, the first priority can be a higher priority than the second priority, the second priority can be a higher priority than the third priority, and so on. In other non-limiting examples, the second or third priority can be the highest priority. That is, without additional signaling in DCI, RRC, etc., if PUCCH transmission on a subcarrier is enabled for UE 520 (e.g., via RRC signaling), then in the slot where UE 520 is assumed to feedback HARQ-ACK, UE 520 can feedback HARQ-ACK on a carrier with sufficient uplink OFDM symbols to accommodate the PUCCH resources configured by RRC, where the carrier priority ranges from PCC to SCC1 to SCC2, and so on.

[0110] However, in some examples, when UE 520 needs to transmit PUCCH, base station 505 can use signaling to override the carrier selection priority rules. As an example, for dynamically scheduled PDSCH, base station 505 can add a field to the DCI of the scheduled PDSCH to indicate the carrier index that UE 520 will use for HARQ-ACK feedback. Therefore, UE 520 can receive scheduled downlink transmissions (e.g., PDSCH) and indicate permission (e.g., from base station 505) for a primary carrier (e.g., PCC) or a secondary carrier (e.g., SCC1 and / or SCC2) for transmitting feedback messages on the PUCCH. UE 520 can select the primary or secondary carrier at least in part based on the permission of the override priority rules (e.g., the DCI), for example, by selecting a carrier corresponding to the carrier index indicated in the DCI.

[0111] In another example, for semi-persistent CSI and / or aperiodic CSI (e.g., reference signal measurement reports, such as CSI-RS reports) on the PUCCH, base station 505 may add a field in the DCI that activates / schedules semi-persistent CSI and / or aperiodic CSI to indicate the carrier index that UE 520 will use to transmit CSI reports on the PUCCH. For example, UE 520 may receive permission from base station 505 that activates semi-persistent resources for downlink transmission and indicates the primary carrier (e.g., PCC) or secondary carrier (e.g., SCC1 and / or SCC2) for transmitting feedback messages. In this example, UE 520 may select the primary and / or secondary carriers to transmit feedback messages based on permission according to a override priority rule, for example, by selecting a carrier corresponding to the carrier index indicated in the DCI.

[0112] In another example, for periodic CSI on the PUCCH and / or ACK / NACK for PDSCH based on semi-persistent scheduling (SPS), base station 505 may add a field to the RRC configuring the PUCCH or SPS to indicate the carrier index used to transmit the periodic CSI on the PUCCH. Therefore, UE 520 can receive a configuration signal from base station 505 indicating the semi-persistent resources used for downlink transmission and indicating the primary carrier (e.g., PCC) or secondary carrier (e.g., SCC1 and / or SCC2) used to transmit the feedback message. In this example, UE 520 may select the primary and / or secondary carriers to transmit the feedback message based on the configuration signal of the override priority rule, for example, selecting a carrier corresponding to the carrier index indicated in the DCI.

[0113] In some respects, PUCCH transmission on subcarriers can be based on UE capabilities. For example, UE 520 can transmit or otherwise convey to base station 505 (e.g., PCell in this example) a message instructing the UE to transmit feedback messages using the primary carrier and / or subcarriers. Base station 505 can, for example, use RRC signaling, MAC CE, DCI, etc., to enable / disable PUCCH transmission on subcarriers for UE 520.

[0114] In some aspects, UE 520 can have uplink transmissions with different traffic types, and in some examples, these can be transmitted on subcarriers. For example, UE 520 can have traffic such as URLLC and eMBB for uplink transmissions. In this context, some examples may include allowing uplink transmissions (e.g., PUCCH and / or PUSCH) on subcarriers based on traffic type (e.g., URLLC for reducing latency). In this example, UE 520 can transmit eMBB transmissions on PCC. Therefore, UE 520 can determine that an uplink transmission (e.g., URLLC) is scheduled to be transmitted to base station 505, and that the uplink transmission has a corresponding traffic type that supports transmission on a subcarrier. UE 520 can select the subcarrier for the transmission of uplink transmissions (e.g., URLLC traffic) based on the traffic type. UE 520 can determine that a second uplink transmission (e.g., eMBB traffic) will be transmitted to base station 505, and that the second uplink transmission has a corresponding second traffic type that supports transmission on the primary carrier. In this example, UE 520 can select the primary carrier for the transmission used for the second uplink transmission based on its transmission type.

[0115] Figure 5 The example illustrates that primary component carriers and secondary component carriers can correspond to different signal paths between the UE and different base stations. Alternatively, and more commonly, primary component carriers and secondary component carriers correspond to a single signal path between the UE and a specific base station.

[0116] Figure 6 An example of a wireless communication system 600 supporting primary and secondary component carriers along a shared signal transmission path between a UE and a specific (single) base station is explained. In some examples, the wireless communication system 600 can implement... Figure 1-4 The wireless communication system 600 may include a base station 605 and a UE 620, which may be examples of the corresponding devices described herein. In some aspects, the base station 605 and its transceivers may constitute or otherwise form a PUCCH group for the UE 620 to support multicarrier communication using at least a primary carrier and one or more subcarriers along the signal paths therebetween. Generally, Figure 6 The system operation can be with Figure 5 The same as in, the difference is that the signal is not as good. Figure 5 It relays between multiple base stations, as in the case of China.

[0117] PUCCH transmission on PCC or SCC

[0118] Figure 7An example of a carrier configuration 700 supporting PCC and SCC transmissions has been explained. Aspects of the carrier configuration 700 can be implemented by a base station and / or a UE, and can be examples of the corresponding devices described herein. For example, one or more base stations (e.g., cells) can constitute or otherwise form a PUCCH group for supporting multi-carrier communication using at least a primary carrier and one or more secondary carriers. For example, the UE can receive downlink transmissions (e.g., PDCCH and / or PDSCH) from the cell in the PUCCH group during downlink slot 705 (e.g., a slot configured only with downlink symbols) on the primary carrier (e.g., on the PCC) and / or secondary carrier (e.g., on the SCC). The UE can identify or otherwise determine feedback information based on the downlink transmissions (e.g., based on whether the UE can successfully decode the downlink transmissions' ACK / NACK information, channel measurement reports associated with the downlink transmissions (such as CSI-RS measurement reports), etc.). The UE can then select a primary carrier (e.g., PCC) and / or a secondary carrier (e.g., SCC2) to transmit feedback information to the base station. Therefore, the UE can select a primary carrier and / or a secondary carrier (depending on which carrier the UE selects for PUCCH transmission) to transmit feedback messages (e.g., PUCCH transmission) including feedback information to the base station.

[0119] In some aspects, this may include, when using TDD for uplink carrier aggregation (e.g., when all CCs in a PUCCH group are TDD carriers), the base station (PCell in this example) may (e.g., in the time domain) configure the TDD mode in an interleaved / complementary manner, such that there exists a maximum number 715 of time slots 715 supporting uplink transmission across all carriers. The base station may transmit or otherwise convey to the UE a signal configuring the time slot format mode (e.g., in RRC signaling, MAC CE, DCI, etc.). In a non-limiting example, this may include the base station configuring the time slot format mode such that at least one carrier is available to the UE for uplink transmission in each time slot 705. For example, the UE may receive a signal configuring the time slot format mode for the primary carrier and / or secondary carriers, wherein the time slot modes for different carriers are selected such that instances of uplink transmission opportunities 715 are interleaved to occur more frequently.

[0120] Figure 7The carrier configuration 700 described herein provides an example of a time slot format mode that can be signaled to the UE according to various aspects of the described technology. The time slot format mode may include a first time slot format mode for the primary carrier and a second time slot format mode for the subcarrier. For example, the first time slot format mode for the primary carrier (e.g., PCC) may include a downlink transmission opportunity 710 configured for a first subset of initial symbols for time slots 705-a, 705-b, 705-c, 705-e, 705-f, and 705-g. The second time slot format mode for the subcarrier (e.g., SCC) may include a downlink transmission opportunity 710 configured for a first subset of initial symbols for time slots 705-a, 705-c, 705-d, 705-e, 705-g, and 705-h.

[0121] The first time slot format mode for the primary carrier (e.g., PCC) may include uplink transmission opportunity 715, which is configured for a second subset of the last symbols of time slot 705-c, time slot 705-d, a second subset of the last symbols of time slot 705-g, and time slot 705-h. The second time slot format mode for the subcarrier (e.g., SCC) may include uplink transmission opportunity 715, which is configured for a second subset of the last symbols of time slot 705-a, time slot 705-b, a second subset of the last symbols of time slot 705-e, and time slot 705-f.

[0122] The first time slot format mode for the primary carrier (e.g., PCC) may include a switching period 720 configured during time slots 705-c and 705-g (e.g., during a third subset of the intermediate symbols of time slots 705-c and 705-g). The second time slot format mode for the subcarrier (e.g., SCC) may include a switching period 720 configured during time slots 705-a and 705-e (e.g., during a third subset of the intermediate symbols of time slots 705-a and 705-e). Therefore, the first time slot format mode for the primary carrier and the second time slot format mode for the subcarrier together include an interleaved instance of uplink transmission opportunity 715 for transmitting feedback messages in the time domain. Figure 7 In the non-limiting examples described, the first time slot format pattern and the second time slot format pattern provide instances of uplink transmission opportunities 715 that occur every other time slot 705 for transmitting feedback messages in the time domain.

[0123] It should be understood that when additional subcarriers are provided or otherwise configured within the PUCCH group, additional slot format modes can be configured for the additional subcarriers, which reduces instances between each uplink slot 715 configured across carriers.

[0124] Figure 8 An example of a carrier configuration 800 supporting PCC and SCC transmissions has been explained. Various aspects of the carrier configuration 800 can be implemented by base stations and / or UEs, and can be examples of the corresponding devices described herein. For example, one or more base stations (e.g., cells) can constitute or otherwise form a PUCCH group for supporting multi-carrier communication of a UE using at least a primary carrier and one or more subcarriers. Furthermore, some carriers can be configured for TDD, where each transmission opportunity (e.g., each symbol, mini-slot, slot, etc.) is designated as a downlink transmission opportunity 815, an uplink transmission opportunity 820, or a handover period 825 (e.g., which can be used for uplink or downlink communication, and may include handover gaps for the UE to revert from downlink transmission to uplink transmission or vice versa). Additionally, some carriers in the PUCCH group can be configured with different subcarrier spacing (SCS) configurations, which may result in slots having different durations. Figure 8 In the non-limiting example described, the primary carrier (e.g., PCC) has an SCS that provides the duration of time slot 805 on the PCC, which is twice the duration of time slot 810 on a subcarrier having a different SCS. For example, the duration of time slots 810-a and 810-b of the SCC can be the same as the duration of time slot 805-a of the PCC in the time domain; the duration of time slots 810-c and 810-d of the SCC can be the same as the duration of time slot 805-b of the PCC in the time domain; the duration of time slots 810-e and 810-f of the SCC can be the same as the duration of time slot 805-c of the PCC in the time domain; and the duration of time slots 810-g and 810-h of the SCC can be the same as the duration of time slot 805-d of the PCC in the time domain.

[0125] For example, the UE may receive downlink transmissions during one or more downlink transmission opportunities 815 on the primary carrier (e.g., on the PCC) and / or on the secondary carrier (e.g., on the SCC) of the cell from the PUCCH group (e.g., PDCCH 830 during time slot 805-a schedules PDSCH 835 during time slot 805-b and / or PDCCH 850 during time slot 810-b schedules PDSCH 855 during time slot 810-e).

[0126] The UE can identify or otherwise determine the feedback information 840 / 860 for the corresponding downlink transmission (e.g., based on whether the UE can successfully decode the ACK / NACK information of the downlink transmission, channel measurement reports associated with the downlink transmission (such as CSI-RS measurement reports), etc.). The UE can then select a primary carrier (e.g., PCC) and / or a secondary carrier (e.g., SCC) to transmit the feedback information 840 / 860 to the base station. Therefore, the UE can select a primary carrier and / or a secondary carrier (depending on which carrier the UE selects for PUCCH transmission) to transmit a feedback message (e.g., PUCCH transmission) including the feedback information 840 / 860 to the base station. For example, the UE can transmit acknowledgment information (e.g., ACK / NACK) 840 for PDSCH 835 during time slot 805-d on the PCC, and acknowledgment information (e.g., ACK / NACK) 860 for PDSCH 855 during time slot 810-h on the SCC.

[0127] In some respects, this may lead to overlap of uplink transmission opportunities on the primary and secondary carriers. In this case, the UE can identify or otherwise select the primary carrier (e.g., PCC) and secondary carrier (e.g., SCC) for transmitting feedback messages. The UE can transmit feedback messages on both the primary and secondary carriers. In some respects, different options for transmitting feedback messages on the primary and secondary carriers can be supported.

[0128] In one example, the UE can transmit HARQ-ACK separately on the PCC / SCC in parallel (e.g., without combining multiple HARQ-ACK codebooks into one). For example, the UE can implement separate codebook construction and downlink assignment indicator (DAI) mechanisms on a per-carrier basis. This can include the UE receiving downlink transmissions on the PCC (e.g., scheduling PDSCH 835 and reception information 840 on PDCCH 830) and determining reception information 840 for the downlink transmissions (e.g., based on whether the UE can successfully receive and decode PDCCH 830 and PDSCH 835). The UE can construct a first codebook for the downlink transmission on the PCC and transmit an indication of that codebook in the reception information 840 provided in the feedback message transmitted during time slot 805-d. For SCC, this could include the UE receiving downlink transmissions on the SCC (e.g., PDCCH 850 scheduling PDSCH 855 and reception information 860), and determining reception information 860 for the downlink transmissions (e.g., based on whether the UE can successfully receive and decode PDCCH 850 and PDSCH 855). The UE can construct a second codebook for the downlink transmissions on the SCC and provide an indication of this codebook in the reception information 860 transmitted in the feedback message during time slot 810-h. Therefore, the UE can transmit a first feedback message using a first codebook generated at least partially based on downlink transmissions received on the primary carrier. The UE can transmit a second feedback message using a second codebook generated at least partially based on downlink transmissions received on the subcarrier.

[0129] In other examples, when multiple DCIs / RRCs point to HARQ-ACK transmissions in overlapping uplink transmission opportunities 820 or handover periods 825, the UE can transmit a combined HARQ-ACK codebook in the HARQ-ACK resource following the most recently received DCI. For example, the UE can implement a single codebook construction / DAI mechanism for downlink transmissions received on the PCC and SCC. This can include the UE receiving downlink transmissions on the PCC (e.g., PDCCH 830 scheduling PDSCH 835 and reception information 840) and receiving downlink transmissions on the SCC (e.g., PDCCH 850 scheduling PDSCH 855 and reception information 860). The UE can determine the reception information 840 / 460 for the downlink transmission (e.g., based on whether the UE can successfully receive and decode PDCCH 830, PDSCH 835, PDCCH 850, and / or PDSCH 855). The UE can construct a combined codebook for downlink transmissions on the PCC and SCC, and transmit an indication of this combined codebook in the feedback message provided with reception information 840 during time slot 805-d and in the feedback message provided with reception information 860 during time slot 810-h. In this example, reception information 840 and reception information 860 are the same, for example, the combined codebook. Therefore, the UE can use the combined codebook generated at least in part based on downlink transmissions received on the primary and secondary carriers to transmit feedback messages on both the primary and secondary carriers.

[0130] Power control for PUCCH on SCC

[0131] Figure 9 This diagram provides a high-level overview of power control for PUCCH transmissions over SCCs, based on several aspects. At 906, UE 902 may attempt to connect to base station 904 using an initial access procedure (e.g., RACH procedure). At 908, base station 904 may transmit (and UE may receive) downlink transmissions (such as PDCCH) on the primary and / or secondary carriers, which include system information (e.g., PDCCH DCI for closed-loop power control and RRC configuration for open-loop power control), including power control configuration parameters for PCC and for all SCCs. Exemplary power control configuration parameters are discussed below. After the UE receives and decodes the system information from the base station, the UE may select a specific carrier (e.g., a specific SCC) for transmitting the PUCCH and then transmit the PUCCH on the UE-selected SCC at 910.

[0132] although Figure 9Although not shown, each operation in the figure may include various intermediate steps or operations and various intermediate transmissions according to the 5G NR standard (or other applicable standards). For example, the UE may provide reception feedback to the base station to indicate that the UE has successfully received and decoded the PDCCH transmitted on the downlink at 908. The reception information may be a positive reception information (e.g., ACK) or a negative reception information (e.g., NACK) of the type described above. The UE may then select a specific subcarrier for transmitting the subsequent PUCCH at 910 (based on the reception and based on path loss measurements using various reference signals). The PUCCH transmitted at 910 on the selected uplink SCC is transmitted by the UE, while the transmission power is controlled according to the power control configuration parameters of the SCC provided by the base station. In addition, although not shown, various beamforming operations may be performed.

[0133] In the illustrative example, the wireless system is configured according to 5G NR, and the power control for PUCCH transmission can be performed according to an open-loop or closed-loop power control protocol.

[0134] For open-loop power control, the open-loop target receiver power (P) O The open-loop target receiver power (P) can be specified by the base station. O It is the sum of the following two components: the nominal PUCCH power value used by all UEs in communicating with the base station (P O_nominal_PUCCH ) and power values ​​that vary from UE to UE (P O_UE_nominal_PUCCH This value is selected from the p0-Set values. In some examples, according to the 5G NR standard and specifications, the cardinality of the set associated with the P0-Set is maxNrofPUCCH-P0-PerSet. For each entry in the P0-Set, the set includes {p0-PUCCH-Id, p0-PUCCH-Value(p0-PUCCH-value)}.

[0135] In radio systems where only PUCCH is permitted on the PCC, the aforementioned open-loop power control parameters are specified by the base station for use with the PCC. For radio systems as disclosed herein where PUCCH can be transmitted on the SCC, the aforementioned parameters (or other suitable parameters) may be indicated by the base station using one or more mechanisms or technologies specified in revised and updated standards such as 3GPP 5G NR Release 17 and later.

[0136] In some open-loop power control examples disclosed herein, the base station is configured (via, for example, RRC) to indicate that the same power control parameters will be used by the UE for both the PCC and each SCC's PUCCH for open-loop power control. That is, power control parameters shared (or common) by the PCC and SCC are used. This is particularly convenient when the base station simultaneously acts as both a PCell and an SCell, such that the PCC and each SCC follow the same signal path and therefore suffer the same path loss, as in... Figure 6 In this scenario, in other examples disclosed herein, the base station provides carrier-specific parameters for the UE to use for the PCC and for each different SCC. That is, the power control parameters used can differ between the PCC and each SCC. The carrier-specific power control configuration can be used when the base station acts as both a PCell and an SCell, but it is also useful if the PCell and SCell are in different locations, causing the PCC and SCC to travel along different signal paths and thus suffer different path losses, as in... Figure 5 In the scene.

[0137] Additionally, open-loop power control parameters can specify carrier-specific spatial relation information (PUCCH-SpatialRelationInfo) for the PCC and SCC. The carrier-specific spatial relation information can include parameters for the UE to determine a carrier-specific reference signal (PUCCH-PathlossReferenceRS-Id) used to measure path loss on a specific component carrier between the UE and the base station. In some examples, PUCCH-SpatialRelationInfo corresponds to the CC index used, based on the CC index on which the PUCCH is transmitted. PUCCH-SpatialRelationInfo can include three parameters: {PUCCH-PathlossReferenceRS-Id, p0-PUCCH-Id, closedLoopIndex}: PUCCH-PathlossReferenceRS-Id is used to determine the RS on the PUCCH CC for path loss measurement; p0-PUCCH-Id is used to determine which p0PUCCH value to use for the corresponding CC carrying the PUCCH; and closedLoopIndex indicates which power control closed-loop index to use for the current PUCCH transmitted on that CC. (In other words, in 5G NR, even when using open-loop power control, a closed-loop index can be specified.)

[0138] In some of the closed-loop power control examples disclosed herein, when scheduling DL PDSCHs, a single dynamic power control command is sufficient in the DL DCI for the A / N (ACK / NACK) feedback of the scheduled PDSCH. A single power control command can be applied to any CC carrying A / N feedback (e.g., PCC, SCC1, SCC2, etc.). If cumulative closed-loop power control is indicated by the base station, the power control command accumulates only within each CC. Power control commands do not accumulate across CCs. For example, the power control value for the PCC is an accumulation or summation independently for SCC1 and independently for SCC2, and so on. In some aspects, the power control command is signaled by the base station in the DCI. In other closed-loop power control examples, absolute dynamic power control commands are used instead of cumulative dynamic power control commands. With absolute dynamic power control, the power control value does not accumulate within a specific CC or across CCs.

[0139] Also note that the UE's final Tx power is equal to P. O +Path loss +Dynamic power control loop output. In some respects, power control commands are used in P O The PUCCH Tx power is dynamically adjusted. In some aspects, the UE is configured with two dynamic power control loops for PUCCH transmission (e.g., one loop for URLLC and another for eMBB).

[0140] Various exemplary open-loop or closed-loop procedures for PUCCH transmission on uplink SCC are available in Figure 10 As will be explained below.

[0141] Figure 10 This is a diagram illustrating an exemplary open-loop power control procedure for uplink PUCCH over an SCC, according to some aspects, where shared or common power control parameters are applied to the PCC and any SCC. At 1002, the base station generates and transmits (and the UE receives) a downlink transmission (e.g., RRC configuration) that includes RRC parameters or other indicators specifying the open-loop power control configuration for PUCCH transmission over the uplink PCC and one or more uplink SCCs. The base station configures the indicators to indicate the nominal PUCCH power value (P...). O_nominal_PUCCH The shared value of the power setting value (p0-Set) and the common value of the open-loop target received power value (P) are used to indicate the shared (or common) open-loop target received power value. O ), so that the same P O_nominal_PUCCHThe p0-Set value is used by the UE for PCC PUCCH transmission and any SCC PUCCH transmission. In some respects, the indicators used in conjunction with eMBB transmission and URLLC transmission can be different (e.g., one indicator for the power control loop of URLLC and another for the power control loop of eMBB). At 1004, the UE selects the uplink SCC for transmitting PUCCH, for example, based on path loss measurements obtained using a reference signal (according to the exemplary technique described above). At 1006, the UE transmits on the SCC selected by the UE and the base station receives the PUCCH on the SCC selected by the UE, while the UE uses a shared or shared PCC provided by the base station. O_nominal_PUCCH And open-loop power control with p0-Sett values. More details are provided above. This procedure is particularly useful in systems where the base station acts as both PCell and SCell, and therefore any path losses of PCC and SCC are very similar, allowing common open-loop power control parameters to be used. That is, in some respects, Figure 10 The characteristics of the PCC and SCC can be utilized by base stations acting as PCell and SCell, making any path loss of the PCC and SCC sufficiently similar, so that shared open-loop power control parameters can be used.

[0142] Figure 11 This is a diagram illustrating an exemplary open-loop power control procedure for uplink PUCCH over an SCC, according to some aspects, where carrier-specific power control parameters are applied separately to the PCC and any SCC. At 1102, the base station generates and transmits (and the UE receives) a downlink transmission (e.g., RRC configuration) that includes RRC parameters or other indicators specifying the open-loop power PC configuration for PUCCH transmission over the PCC and one or more SCCs, wherein these indicators are configured by the base station to indicate the nominal P... O_nominal_PUCCH The carrier-dependent values ​​of p0-Set and PUCCH-SpatialRelationInfo indicate the carrier-dependent open-loop target received power value (P). O And spatial relationship information that varies due to carrier waves, so that different P O_nominal_PUCCH The p0-Set and PUCCH-SpatialRelationInfo values ​​can be used by the UE for PCCPUCCH transmission and any SCC PUCCH transmission. At 1104, the UE selects the uplink SCC for transmitting the PUCCH, for example, based on path loss measurements obtained using a reference signal (according to the exemplary technique described above). At 1106, the UE transmits on the UE-selected SCC, and the base station receives the PUCCH on the UE-selected SCC, while the UE uses a carrier-specific PCC provided by the base station. O_nominal_PUCCHOpen-loop power control of the p0-Set and PUCCH-SpatialRelationInfo values ​​includes determining a carrier-specific reference signal (PUCCH-PathlossReferenceRS-Id) for measuring the path loss on the component carrier selected by the UE. More details are provided above. As explained above, this procedure can be used in systems where a single base station acts as both PCell and SCell, but it can also be used in systems where the PCell and SCell are in different locations so that any path loss for PCC and SCC may differ.

[0143] Figure 12 This is a diagram illustrating an exemplary closed-loop power control procedure for uplink PUCCH on an SCC, according to some aspects, where power control values ​​are accumulated for the PCC and each SCC separately. At 1202, the base station generates and transmits (and the UE receives) a downlink transmission (e.g., PDCCH) including a DCI or other indicator specifying a closed-loop power configuration for PUCCH transmission, wherein these indicators are configured by the base station to indicate carrier-specific accumulated closed-loop power control where power control (PC) values ​​are accumulated separately for the PCC and each SCC. In some aspects, the indicators used in conjunction with eMBB and URLLC transmissions may differ (as discussed above). At 1204, the UE selects the uplink SCC for transmitting the PUCCH, for example, based on path loss measurements obtained using a reference signal (according to the exemplary technique described above). At 1206, the UE transmits and the base station receives the PUCCH on the UE-selected SCC, while the UE accumulates PC values ​​on the selected CC separately from any PC values ​​accumulated on other CCs. In step 1208, the base station transmits on the SCC selected by the UE, and the UE receives PC adjustments for the transmission on the SCC selected by the UE, where these adjustments are based on the cumulative PC value of the selected SCC. For example, the base station may signal to the UE to increase its transmission power on the PCC, but decrease its transmission power on the SCC. Therefore, Figure 12 The features take into account PC values ​​from different CCs.

[0144] Figure 13The cumulative power control has been explained. PUCCH group 1300 includes PCC transmission 1302 and SCC transmission 1304. PCC transmission 1302 includes various PC values ​​(PC1, PC3, PC5, and PC6). SCC transmission 1304 includes various other PC values ​​(PC2, PC4, and PC7). As shown by the dashed lines, the PC values ​​of PCC (PC1+PC3+PC5+PC6) and SCC values ​​(PC2+PC4+PC7) are accumulated separately. The accumulated values ​​can be transmitted to the base station for the base station to use in controlling the UE's transmissions. For example, the base station can signal to the UE to increase its power level for PCC PUCCH transmissions while decreasing its power level for SCC PUCCH transmissions, or vice versa. Although Figure 13 Only a single SCC is shown, but the accumulation of PC values, which varies from carrier to carrier, can be performed on each SCC in the SCC set (such as on sixteen different SCCs).

[0145] Figure 14 This is a diagram illustrating an exemplary closed-loop power control procedure for an uplink PUCCH on an SCC, according to some aspects of which absolute closed-loop power control is performed. At 1402, the base station generates and transmits (and the UE receives) a downlink transmission (e.g., a PDCCH) that includes a DCI or other indicator specifying a closed-loop power configuration for PUCCH transmissions on the PCC and one or more SCCs, wherein these indicators are configured by the base station to indicate absolute closed-loop power control in which PC values ​​do not accumulate on the PCC or any SCC. That is, the base station will respond to each individual PC value. At 1404, the UE selects an uplink SCC for transmitting the PUCCH, for example, based on path loss measurements obtained using a reference signal (according to the exemplary technique described above). At 1406, the UE transmits and the base station receives the PUCCH on the UE-selected SCC, while the UE determines the absolute PC value on the selected CC separately from any other PC values ​​on the same SCC or other CCs. At 1408, the base station transmits on the SCC selected by the UE, and the UE receives PC adjustments for the transmission on the SCC selected by the UE, wherein these adjustments are based on the latest absolute PC value of the selected SCC. Therefore, in some aspects, Figure 14 Its features provide closed-loop power control for use with PCC and SCC.

[0146] Brief reference again Figure 13 For absolute closed-loop power control, the power level can be adjusted using each individual PC value (e.g., PC1, PC2, etc.) instead of accumulating or summing the PC values ​​together (commonly for all uplink CCs or separately for each individual CC).

[0147] Figure 15This is a block diagram illustrating an example of a hardware implementation of a base station 1500 (e.g., a scheduling entity) employing a processing system 1514. For example, base station 1500 could be as follows: Figures 1 to 6 and Figure 9 The scheduling entity or gNB described by any one or more of them.

[0148] Base station 1500 can be implemented using a processing system 1514 including one or more processors 1504. Examples of processors 1504 include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. In various examples, base station 1500 can be configured to perform any one or more functions described herein. That is, the processor 1504 utilized in base station 1500 can be used to implement the functions discussed below and in... Figure 7-14 The processes and procedures described and explained in 17-18, as discussed below.

[0149] In some instances, processor 1504 may be implemented via a baseband or modem chip, while in other implementations, processor 1604 may include several devices that are different from and distinct from the baseband or modem chip (e.g., those that can work together to achieve the examples discussed herein). Furthermore, as mentioned above, various hardware arrangements and components beyond the baseband modem processor can be used in the implementation, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.

[0150] exist Figure 15In the example, processing system 1514 can be implemented using a bus architecture generally represented by bus 1502. Depending on the specific application and overall design constraints of processing system 1514, bus 1502 may include any number of interconnect buses and bridges. Bus 1502 communicatively couples together various circuits including one or more processors (generally represented by processor 1504), memory 1505, and computer-readable media (generally represented by computer-readable media 1506). Bus 1502 may also link various other circuits, such as timing sources, peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. Bus interface 1508 provides an interface between bus 1502 and transceiver 1510. Transceiver 1510 provides a communication interface or means for communicating with various other devices over a transmission medium. Transceiver 1510 may be connected to antenna array 1515, which may be configured to use beamforming technology to transmit and / or receive multiple beams (e.g., transmit and receive beams). Transceiver 1510 includes one or more receivers 1511 and one or more transmitters 1513. Receivers 1511 are coupled to antenna array 1515. Transmitters 1513 are coupled to the same or different antenna arrays 1517. Antenna arrays may be used for beamforming. Different RF receiver chains for different CCs may be provided within receiver 1511, allowing base station 1500 to operate as both PCell and one or more SCells to receive uplink signals from the UE on multiple CCs, including receiving PUCCH transmissions from the UE on uplink SCCs.

[0151] Depending on the characteristics of the equipment, a user interface 1512 (e.g., keypad, display, speaker, microphone, joystick) may also be provided. Of course, such a user interface 1512 is optional and may be omitted in some examples (such as base stations).

[0152] In some aspects, processor 1504 may include circuitry configured for various functions, including, for example, power control functions associated with uplink PUCCH transmissions on the SCC. For example, the circuitry may be configured to implement the following combinations Figure 7-14 The base station functions described in 17-18 are discussed below.

[0153] The processor 1504 may include an uplink SCC open-loop power control configuration circuit 1540, which may be configured to control SCC open-loop power control functions, such as generating an open-loop power control configuration for PUCCH transmission on the SCC of the uplink component carrier set, and controlling the transceiver 1510 to transmit an indicator of the open-loop power control configuration to the UE for use by the UE for PUCCH transmission on the SCC of the uplink component carrier set including the PCC and SCC.

[0154] The processor 1504 may include an uplink SCC closed-loop power control configuration circuit 1542, which may be configured to control SCC closed-loop power control functions, such as generating a closed-loop power control configuration for PUCCH transmission on the SCC of the uplink component carrier set, and controlling the transceiver 1510 to transmit an indicator of the closed-loop power control configuration to the UE for use by the UE for PUCCH transmission on the SCC of the uplink component carrier set including the PCC and SCC.

[0155] The processor 1504 may include an uplink SCC PUCCH receiver circuit 1544, which may be configured to control the transceiver to receive PUCCH transmissions from the UE on a subcomponent carrier based at least in part on the power control configuration, and then process the received SCC PUCCH to decode the information therein.

[0156] The processor 1504 can access power control parameters 1507 stored in the memory 1505, such as the stored nominal power value.

[0157] As mentioned above, in some wireless communication systems, the UE may be limited to transmitting uplink control information on the primary carrier, for example, within the PUCCH. When the primary carrier is a TDD carrier (among other things), this can lead to large latency for PUCCH transmission due to uplink / downlink / flexible link slot configurations or modes (e.g., uplink transmission may not be allowed in a TDD slot configured with all downlink symbols). Furthermore, in some systems, particularly under UL CA, PUCCH transmission can only be performed on the PCC within the PUCCH group, which can be limiting. Therefore, the processor 1504 can be configured to provide power control so that the UE can transmit uplink control information within the PUCCH on a subcarrier (or on both the primary and subcarriers) to address the aforementioned problems. For example, PUCCH resources can be configured on each carrier in the PUCCH group to support PUCCH transmission on subcarriers. In some aspects, processor 1504 provides a circuit system to (a) generate and transmit to the UE an indicator of a power control configuration, the power control configuration being used by the UE for PUCCH transmission on a sub-component carrier in an uplink component carrier set including a primary component carrier and a secondary component carrier; and (2) receive the PUCCH transmission from the UE on the sub-component carrier based at least in part on the power control configuration. In some aspects, the circuit system includes an uplink SCC open-loop power control configuration circuit 1540 and an uplink SCC PUCCH receiving circuit 1544. In other aspects, the circuit system includes an uplink SCC closed-loop power control configuration circuit 1542 and an uplink SCC PUCCH receiving circuit 1544. Note that uplink PCC power control can be provided with Figure 15 Additional circuitry not shown.

[0158] Processor 1504 is responsible for managing bus 1502 and general processing, including the execution of software stored on computer-readable medium 1506. When executed by processor 1504, the software causes processing system 1514 to perform various functions described below for any particular device. Computer-readable medium 1506 and memory 1505 may also be used to store data manipulated by processor 1504 during software execution.

[0159] One or more processors 1504 in the processing system can execute software. Software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. The software may reside on a computer-readable medium 1506. The computer-readable medium 1506 may be a non-transitory computer-readable medium. As examples, non-transient computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic tapes), optical discs (e.g., compact discs (CDs) or digital multi-purpose discs (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions accessible and readable by a computer. As examples, computer-readable medium 1506 may also include carrier waves, transmission lines, and any other suitable medium for transmitting software and / or instructions accessible and readable by a computer. Computer-readable medium 1506 may reside in processing system 1514, be external to processing system 1514, or be distributed across multiple entities including processing system 1514. Computer-readable medium 1506 may be implemented in a computer program product. As examples, a computer program product may include a computer-readable medium in encapsulation material. Those skilled in the art will recognize how the functionality described throughout this disclosure can be best achieved, depending on the specific application and the overall design constraints imposed on the system as a whole.

[0160] In one or more examples, computer-readable medium 1506 may include software executable by processor 1504, configured to implement one or more functions described elsewhere herein, including, for example, power control of the SCC PUCCH. For example, software code or instructions may be configured to implement... Figure 7-14 And one or more of the functions described in 17-18.

[0161] Computer-readable medium 1506 may include code 1552, executable by uplink SCC open-loop power control configuration circuitry 1540, for controlling SCC open-loop power control functions, such as generating an open-loop power control configuration for PUCCH transmission on the SCC of the uplink component carrier set, and controlling transceiver 1510 to transmit an indicator of the open-loop power control configuration to the UE for use by the UE for PUCCH transmission on the SCC of the uplink component carrier set including the PCC and SCC.

[0162] Computer-readable medium 1506 may include code or instructions 1554 executable by uplink SCC closed-loop power control configuration circuitry 1542 for controlling closed-loop power control functions, such as generating a closed-loop power control configuration for PUCCH transmission on the SCC of the uplink component carrier set, and controlling transceiver 1510 to transmit an indicator of the closed-loop power control configuration to the UE for use by the UE for PUCCH transmission on the SCC of the uplink component carrier set including PCC and SCC.

[0163] Computer-readable medium 1506 may include code or instructions 1556 that can be executed by uplink SCC PUCCH receiving circuitry 1544 to control transceiver 1510 to receive PUCCH transmissions from UE on subcomponent carriers at least in part based on the power control configuration, and then process the received SCC PUCCH to decode the information therein.

[0164] It should be noted that the circuitry included in processor 1504 is provided merely as an example, and other means for performing the described functions may be included within various aspects of this disclosure, including but not limited to instructions stored in computer-readable medium 1506, or... Figure 1-6 The description and use of either of the above, and for example, this article regarding Figure 7-14 And any other suitable equipment or apparatus for the process and / or algorithm described in 17-18.

[0165] In some respects, the uplink SCC open-loop power control configuration circuit 1540 provides means for generating an open-loop power control configuration for PUCCH transmission on the SCC of the uplink component carrier set, and for controlling the transceiver 1510 to transmit an indicator of the open-loop power control configuration to the UE for use by the UE for PUCCH transmission on the SCC of the uplink component carrier set including the PCC and the SCC.

[0166] In some respects, the uplink SCC closed-loop power control configuration circuit 1542 provides means for generating a closed-loop power control configuration for PUCCH transmission on the SCC of the uplink component carrier set, and for controlling the transceiver 1510 to transmit an indicator of the closed-loop power control configuration to the UE for use by the UE for PUCCH transmission on the SCC of the uplink component carrier set including the PCC and the SCC.

[0167] In some respects, the uplink SCC PUCCH receiving circuit 1544 provides means for receiving PUCCH transmissions from the UE on a subcomponent carrier, at least in part based on a power control configuration, and means for processing the received SCC PUCCH to decode the information therein.

[0168] In some aspects, processor 1504 provides means for transmitting an indicator of a power control configuration to a UE, the power control configuration being transmitted by the UE via PUCCH on a sub-component carrier in an uplink component carrier set including a primary component carrier and a secondary component carrier; and transceiver 1510 provides means for receiving the PUCCH transmission from the UE on the sub-component carrier based at least in part on the power control configuration.

[0169] Figure 16 This is a block diagram illustrating an example hardware implementation of an exemplary UE 1600 (e.g., a scheduled entity) employing a processing system 1614. Depending on the aspects, elements, or any part of elements, or any combination of elements, can be implemented using a processing system 1614 including one or more processors 1604. For example, UE 1600 can be as shown in... Figure 1-6 The UE explained in any one or more of 9.

[0170] Processing system 1614 can be with Figure 16 The processing system 1614 described herein is generally similar, including a bus interface 1608, a bus 1602, a memory 1605, a processor 1604, and a computer-readable medium 1606. Furthermore, the UE 1600 may include components similar to those described above. Figure 16 User interface 1612 and transceiver 1610 are substantially similar to those user interfaces and transceivers described herein. Transceiver 1610 includes one or more receivers 1611 and one or more transmitters 1613. Receivers 1611 are coupled to antenna set 1615. Transmitters 1613 are coupled to the same or different antenna sets 1617. Antenna sets can be used for beamforming. Transceiver 1610 may include separate receive and transmit RF components or chains of RF components, such as receivers 1611 and transmitters 1613, as shown in the figure. Different RF transmit chains can be provided within transmitter 1613 for use with different CCs, enabling UE 1600 to transmit uplink signals to one or more base stations over multiple CCs, including transmitting PUCCH transmissions over uplink SCCs.

[0171] Depending on the nature of the device, user interface 1612 may include, for example, a keyboard, display, speaker, microphone, joystick, etc. User interface 1512 is optional and may be omitted in some examples.

[0172] In some aspects, processor 1604 may include circuitry configured for various functions, including, for example, power control functions in conjunction with uplink PUCCH transmissions on the SCC. For example, the circuitry may be configured to implement the following combinations Figure 7-14 And one or more UE functions described in 17-18, as discussed below.

[0173] The processor 1604 may include an uplink SCC open-loop power control circuit 1640, which can be configured to control SCC open-loop power control functions, such as receiving an indicator of an open-loop power control configuration from a base station, the open-loop power control configuration being used by the UE for PUCCH transmission on the SCC of an uplink component carrier set including the PCC and SCC.

[0174] The processor 1604 may include an uplink SCC closed-loop power control circuit 1642, which can be configured to control SCC closed-loop power control functions, such as controlling the transceiver 1610 to receive an indicator of a closed-loop power control configuration from a base station, the closed-loop power control configuration being used by the UE for PUCCH transmission on the SCC of an uplink component carrier set including the PCC and SCC.

[0175] The processor 1604 may include an uplink SCC PUCCH transmission circuit 1644, which may be configured to control the transceiver to transmit PUCCH transmissions to the base station on a subcomponent carrier, at least in part based on power control.

[0176] The processor 1604 can store power control parameters 1607 received from the base station, such as nominal power values, in the memory 1605.

[0177] As discussed above, in some wireless communication systems, the UE may be limited to transmitting uplink control information on the primary carrier, for example, within the PUCCH. When the primary carrier is a TDD carrier (among other things), this can lead to large latency for PUCCH transmission due to uplink / downlink / flexible time slot configurations or modes (e.g., uplink transmission is not allowed in downlink time slots). Furthermore, in some systems, particularly in UL CA systems, PUCCH transmission is restricted to the PCC within the PUCCH group. Therefore, Figure 16The processor 1604 can be configured to provide power control so that the UE can transmit uplink control information within the PUCCH on a subcarrier (or on both the primary and subcarriers) to address the aforementioned problems. In some aspects, the processor 1604 provides circuitry to (a) receive from a base station an indicator of a power control configuration used by the UE for PUCCH transmission on the subcarrier within a set of uplink component carriers including the primary and subcarriers; and (b) transmit the PUCCH transmission to the base station on the subcarrier at least in part based on the power control configuration. In some aspects, the circuitry includes an uplink SCC open-loop power control circuitry 1640 and an uplink SCC PUCCH transmission circuitry 1644. In other aspects, the circuitry includes an uplink SCC closed-loop power control circuitry 1642 and an uplink SCC PUCCH transmission circuitry 1644. Note that uplink PCC power control can be provided... Figure 15 Additional circuitry not shown.

[0178] Note that the processor 1604 and its circuitry may additionally or alternatively be one or more controllers. As mentioned above, the same considerations apply to all circuits and processors or processing systems described herein.

[0179] Processor 1604 is responsible for managing bus 1602 and general processing, including the execution of software stored on computer-readable medium 1606. When executed by processor 1604, the software causes processing system 1614 to perform various functions described below for any particular device. Computer-readable medium 1606 and memory 1605 may also be used to store data manipulated by processor 1604 during software execution. For example, software code or instructions may be configured to implement... Figure 7-14 The computer-readable medium 1606 may include code or instructions 1652 executable by processor 1604 for controlling UE-based operations to control SCC open-loop power control functions, such as an indicator controlling transceiver 1610 to receive an open-loop power control configuration from a base station, the open-loop power control configuration being used by the UE for PUCCH transmission on the SCC in an uplink component carrier set including the PCC and SCC.

[0180] The computer-readable medium 1606 may include code or instructions 1652 executable by the uplink SCC open-loop power control circuitry 1640 for controlling the transceiver 1610 to: receive an indicator of an open-loop power control configuration from a base station, the open-loop power control configuration being used by the UE for PUCCH transmission on a sub-component carrier in an uplink component carrier set including a primary component carrier and a secondary component carrier; and process the open-loop power control configuration for PUCCH transmission on the SCC of the uplink component carrier set.

[0181] The computer-readable medium 1606 may also include code or instructions 1654 executable by the uplink SCC closed-loop power control circuitry 1642 for controlling the transceiver 1610 to: receive an indicator of a closed-loop power control configuration from a base station, the closed-loop power control configuration being used by the UE for PUCCH transmission on a sub-component carrier in an uplink component carrier set including a primary component carrier and a secondary component carrier; and process the closed-loop power control configuration for PUCCH transmission on the SCC of the uplink component carrier set.

[0182] The computer-readable medium 1606 may include code or instructions 1656 executable by the uplink SCC PUCCH transmission circuit 1644 for controlling the transceiver 1610 to transmit the PUCCH transmission to the base station on the subcomponent carrier, at least in part based on the power control configuration.

[0183] Note that the circuitry included in processor 1604 is provided merely as an example, and other means for performing the described functions may be included within various aspects of this disclosure, including but not limited to instructions stored in computer-readable medium 1606, or... Figure 1-6 The description and use of either of the above, and for example, this article regarding Figure 7-14 And any other suitable equipment or apparatus for the process and / or algorithm described in 17-18.

[0184] In some respects, the uplink SCC open-loop power control circuit 1640 provides means for receiving an indicator of an open-loop power control configuration from a base station, the open-loop power control configuration being used by the UE for PUCCH transmission on the SCC of an uplink component carrier set including the PCC and the SCC.

[0185] In some respects, the uplink SCC closed-loop power control circuit 1642 provides means for receiving an indicator of a closed-loop power control configuration from a base station, the closed-loop power control configuration being used by the UE for PUCCH transmission on the SCC of an uplink component carrier set including the PCC and the SCC.

[0186] In some respects, the uplink SCC PUCCH transmission circuit 1644 provides means for receiving PUCCH transmissions from the UE on a subcomponent carrier, at least in part based on power control configuration.

[0187] In some aspects, processor 1604 provides means for receiving an indicator of a power control configuration from a base station, the power control configuration being used by the UE for PUCCH transmission on a sub-component carrier in an uplink component carrier set including a primary component carrier and a secondary component carrier; and transceiver 1610 provides means for transmitting the PUCCH transmission to the base station on the sub-component carrier, at least in part, based on the power control configuration.

[0188] Figure 17 This is a flowchart illustrating an exemplary process 1700 according to some aspects. As stated below, some or all of the described features may be omitted in a particular implementation within the scope of this disclosure, and some described features may not be required to implement all examples. In some examples, process 1700 may be provided by the UE (e.g., Figure 16 The process 1700 is executed by the UE (explained in section 1600). In some examples, the process 1700 may be executed by any suitable equipment or apparatus for performing the functions or algorithms described below.

[0189] In box 1702, the UE receives an indicator of a power control configuration from the base station, which is used by the UE to transmit PUCCH on the secondary component carrier in an uplink component carrier set that includes a primary component carrier and secondary component carriers. For example, in conjunction with the above... Figure 16 The uplink SCC open-loop power control circuit 1640 or uplink SCC closed-loop power control circuit 1642 (or both) shown and described can provide means for receiving an indicator of a power control configuration from a base station, which is used by the UE for PUCCH transmission on a sub-component carrier in an uplink component carrier set including a primary component carrier and a sub-component carrier.

[0190] In box 1704, the UE transmits PUCCH transmissions to the base station on the SCC, at least in part, based on a power control configuration. For example, in conjunction with the above... Figure 16 The uplink SCC PUCCH transmission circuit 1644 shown and described can provide means for transmitting PUCCH transmissions to a base station on the SCC, at least in part based on power control configuration.

[0191] Figure 18 This is a flowchart illustrating an exemplary process 1800 according to some aspects. In certain implementations within the scope of this disclosure, some or all of the illustrated features may be omitted, and some illustrated features may not be required for all example implementations. In some examples, process 1800 may be provided by a UE (e.g., Figure 16 The process 1800 is executed by the UE 1600 described. In some examples, the process 1800 may be executed by any suitable equipment or apparatus for performing the functions or algorithms described below.

[0192] In box 1802, the UE receives data from the base station (e.g., Figure 15 The base station 1500 (described in the text) receives one or more indicators for a power control configuration used by the UE for PUCCH transmission on sub-component carriers in an uplink component carrier set including primary and secondary component carriers. These indicators are configured to indicate: (a) an open-loop power control configuration, (b) a carrier-specific open-loop target received power value associated with each component carrier in the uplink component carrier set, and (c) separate power loop control parameters for eMBB transmission and URLLC transmission. In block 1804, the UE transmits PUCCH transmissions to the base station on the SCC, at least partially based on the power control configuration, while employing open-loop power control and separate power control loops associated with eMBB and URLLC.

[0193] Figure 19 This is a flowchart illustrating an exemplary process 1900 according to some aspects. In certain implementations within the scope of this disclosure, some or all of the illustrated features may be omitted, and some illustrated features may not be required for all example implementations. In some examples, process 1900 may be provided by a UE (e.g., Figure 16 The process 1900 is executed by the UE 1600 described. In some examples, the process 1900 may be executed by any suitable equipment or apparatus for performing the functions or algorithms described below.

[0194] In box 1902, the UE receives data from the base station (e.g., Figure 15 The base station 1500 (described in the text) receives one or more indicators for power control configuration, which is used by the UE for PUCCH transmission on sub-component carriers in an uplink component carrier set including primary component carriers and secondary component carriers. These indicators are configured to indicate: (a) a closed-loop power control configuration, (b) carrier-specific cumulative closed-loop power control, wherein the power control value is accumulated individually by the UE for each component carrier in the uplink component carrier set, and (c) separate power loop control parameters for eMBB transmission and URLLC transmission. These indicators may be a single dynamic power control command within the DCI for ACK / NACK feedback of scheduled PDSCH. In block 1904, the UE transmits PUCCH transmissions to the base station on the SCC, at least in part, based on the power control configuration, while employing closed-loop power control and separate power control loops associated with eMBB and URLLC.

[0195] Figure 20 This is a flowchart illustrating an exemplary process 2000 according to some aspects. In certain implementations within the scope of this disclosure, some or all of the illustrated features may be omitted, and some illustrated features may not be required for all example implementations. In some examples, process 2000 may be provided by a base station (e.g., Figure 15 The process 2000 is executed by the base station 1500 described. In some examples, the process 2000 may be executed by any suitable equipment or apparatus for performing the functions or algorithms described below.

[0196] In box 2002, the base station (e.g., a scheduling entity) transmits an indicator of a power control configuration to the UE (or other scheduled entity), which is used by the UE for PUCCH transmission on the sub-component carriers of an uplink component carrier set including primary and secondary component carriers. For example, in conjunction with the above... Figure 15 The uplink SCC open-loop power control configuration circuit 1540 or the uplink SCC closed-loop power control configuration circuit 1542 (or both) shown and described can provide means for transmitting an indicator of power control configuration to the UE, which is used by the UE to transmit PUCCH on the sub-component carriers of the uplink component carrier set including the primary component carrier and the sub-component carrier.

[0197] In box 2004, the base station receives PUCCH transmissions from the UE on SCC, at least in part, based on a power control configuration. For example, the above combined Figure 15 The uplink SCC PUCCH receiver circuit 1544 shown and described can provide means for receiving PUCCH transmissions from the UE on a subcomponent carrier, at least in part based on a power control configuration.

[0198] Figure 21 This is a flowchart illustrating an exemplary process 2100 according to some aspects. In certain implementations within the scope of this disclosure, some or all of the illustrated features may be omitted, and some illustrated features may not be required for all example implementations. In some examples, process 2100 may be provided by a base station (e.g., Figure 15 The process 2100 is executed by the base station 1500 described. In some examples, the process 2100 may be executed by any suitable equipment or apparatus for performing the functions or algorithms described below.

[0199] In box 2102, the base station (e.g., Figure 15 The base station 1500 (explained) sends a signal to the UE (e.g., Figure 16The UE (1600) described transmits one or more indicators for power control configuration, which is used by the UE for PUCCH transmission on sub-component carriers in an uplink component carrier set including primary and secondary component carriers. These indicators are configured to indicate: (a) a closed-loop power control configuration, (b) carrier-specific cumulative closed-loop power control, where the power control value is accumulated individually by the UE for each component carrier in the uplink component carrier set, and (c) separate power loop control parameters for eMBB transmission and URLLC transmission. These indicators may be a single dynamic power control command within the DCI for ACK / NACK feedback of scheduled PDSCH. In block 2104, the base station receives PUCCH transmissions from the UE on the SCC, at least partially based on the power control configuration, while employing closed-loop power control and separate power control loops associated with eMBB and URLLC.

[0200] Figure 22 This is a flowchart illustrating an exemplary process 2200 according to some aspects. In certain implementations within the scope of this disclosure, some or all of the illustrated features may be omitted, and some illustrated features may not be required for all example implementations. In some examples, process 2200 may be provided by a base station (e.g., Figure 15 The process 2200 is executed by the base station 1500 described. In some examples, the process 2200 may be executed by any suitable equipment or apparatus for performing the functions or algorithms described below.

[0201] In box 2202, the base station (e.g., Figure 15 The base station 1500 (explained) sends a signal to the UE (e.g., Figure 16 The UE (1600) described transmits one or more indicators for power control configuration, which is used by the UE for PUCCH transmission on sub-component carriers in an uplink component carrier set including primary and secondary component carriers. These indicators are configured to indicate: (a) a closed-loop power control configuration, (b) carrier-specific cumulative closed-loop power control, where the power control value is accumulated individually by the UE for each component carrier in the uplink component carrier set, and (c) separate power loop control parameters for eMBB transmission and URLLC transmission. These indicators may be a single dynamic power control command within the DCI for ACK / NACK feedback of scheduled PDSCH. In block 2204, the base station receives PUCCH transmissions from the UE on the SCC, at least partially based on the power control configuration, while employing closed-loop power control and separate power control loops associated with eMBB and URLLC.

[0202] The following provides an overview of the various examples of this disclosure.

[0203] Example 1: A UE includes: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory and configured to: receive from a base station an indicator of a power control configuration, the power control configuration being used by the UE for PUCCH transmission on the sub-component carriers in an uplink component carrier set including a primary component carrier and a secondary component carrier; and transmit the PUCCH transmission to the base station on the sub-component carriers based at least in part on the power control configuration.

[0204] Example 2: The UE as described in Example 1, wherein the indicator is configured to indicate an open-loop power control configuration.

[0205] Example 3: The UE as described in Example 2, wherein the indicator is further configured to indicate a carrier-specific open-loop target received power value associated with each component carrier in the uplink component carrier set.

[0206] Example 4: The UE as described in Example 1, wherein the indicator is further configured to indicate a closed-loop power control command.

[0207] Example 5: The UE as described in Example 4, wherein the indicator is further configured to indicate carrier-specific cumulative closed-loop power control, wherein the power control value is accumulated by the UE individually for each component carrier in the uplink component carrier set.

[0208] Example 6: The UE as described in Example 5, wherein the processor is further configured to receive from the base station individual power adjustment indicator signals for each component carrier in the uplink component carrier set according to the carrier-specific cumulative closed-loop power control.

[0209] Example 7: A UE as described in Examples 4, 5 or 6, wherein the indicator includes a single dynamic power control command within the DCI for ACK / NACK feedback of the scheduled PDSCH.

[0210] Example 8: A UE as described in Examples 1, 2, 3, 4, 5, 6 or 7, wherein the indicator includes: a first indicator associated with eMBB transmission and a second indicator associated with URLLC transmission.

[0211] Example 9: A method for wireless communication at a UE, the method comprising: receiving from a base station an indicator of a power control configuration, the power control configuration being used by the UE for PUCCH transmission on the sub-component carriers in an uplink component carrier set including a primary component carrier and a secondary component carrier; and transmitting the PUCCH transmission to the base station on the sub-component carriers based at least in part on the power control configuration.

[0212] Example 10: The method as described in Example 9, wherein the indicator is configured to indicate an open-loop power control configuration.

[0213] Example 11: The method as described in Example 10, wherein the indicator is further configured to indicate a carrier-specific open-loop target received power value associated with each component carrier in the uplink component carrier set.

[0214] Example 12: The method as described in Example 9, wherein the indicator is further configured to indicate a closed-loop power control command.

[0215] Example 13: The method as described in Example 12, wherein the indicator is further configured to indicate carrier-specific cumulative closed-loop power control, wherein the power control value is accumulated individually by the UE for each component carrier in the uplink component carrier set.

[0216] Example 14: The method as described in Example 12 or 13, wherein the indicator includes a single dynamic power control command within the DCI for ACK / NACK feedback of the scheduled PDSCH.

[0217] Example 15: The method as described in Examples 9, 10, 11, 12, 13 or 14, wherein the indicator includes: a first indicator associated with eMBB transport and a second indicator associated with URLLC transport.

[0218] Example 16: A base station comprising: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory and configured to: transmit an indicator of a power control configuration to a UE, the power control configuration being used by the UE for PUCCH transmission on the sub-component carriers in an uplink component carrier set including a primary component carrier and a secondary component carrier; and receive the PUCCH transmission from the UE on the sub-component carriers based at least in part on the power control configuration.

[0219] Example 17: A base station as described in Example 16, wherein the indicator is configured to indicate an open-loop power control configuration.

[0220] Example 18: A base station as described in Example 17, wherein the indicator is further configured to indicate a carrier-specific open-loop target received power value associated with each component carrier in the uplink component carrier set.

[0221] Example 19: A base station as described in Example 16, wherein the indicator is further configured to indicate a closed-loop power control command.

[0222] Example 20: A base station as described in Example 19, wherein the indicator is further configured to indicate carrier-specific cumulative closed-loop power control, wherein the power control value is accumulated individually by the UE for each component carrier in the uplink component carrier set.

[0223] Example 21: A base station as described in Example 20, wherein the processor is further configured to transmit to the UE a separate power adjustment indicator signal for each component carrier in the uplink component carrier set according to the carrier-specific cumulative closed-loop power control.

[0224] Example 22: A base station as described in Examples 19, 20, or 21, wherein the indicator includes a single dynamic power control command within the DCI for ACK / NACK feedback of the scheduled PDSCH.

[0225] Example 23: A base station as described in Examples 16, 17, 18, 19, 20, 21 or 22, wherein the indicator includes: a first indicator associated with eMBB transmission and a second indicator associated with URLLC transmission.

[0226] Example 24: A method for wireless communication at a base station, the method comprising: transmitting to a UE an indicator of a power control configuration, the power control configuration being used by the UE for PUCCH transmission on the sub-component carriers in an uplink component carrier set including a primary component carrier and a secondary component carrier; and receiving the PUCCH transmission from the UE on the sub-component carriers at least in part based on the power control configuration.

[0227] Example 25: The method as described in Example 24, wherein the indicator is configured to indicate an open-loop power control configuration.

[0228] Example 26: The method as described in Example 25, wherein the indicator is further configured to indicate a carrier-specific open-loop target received power value associated with each component carrier in the uplink component carrier set.

[0229] Example 27: The method as described in Example 24, wherein the indicator is further configured to indicate a closed-loop power control command.

[0230] Example 28: The method as described in Example 27, wherein the indicator is further configured to indicate carrier-specific cumulative closed-loop power control, wherein the power control value is accumulated individually by the UE for each component carrier in the uplink component carrier set.

[0231] Example 29: The method as described in Examples 24, 25, 26 or 27, wherein the indicator includes a single dynamic power control command within the DCI for ACK / NACK feedback of the scheduled PDSCH.

[0232] Example 30: The method as described in Examples 24, 25, 26, 27 or 28, wherein the indicator includes: a first indicator associated with eMBB transport and a second indicator associated with URLLC transport.

[0233] Several aspects of wireless communication networks have been described with reference to exemplary implementations. As will be readily apparent to those skilled in the art, the various aspects described herein can be extended to other telecommunications systems, network architectures, and communication standards.

[0234] As examples, various aspects can 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 Communications (GSM). These aspects can also be extended to systems defined by 3GPP2, such as CDMA2000 and / or Evolved Data Optimized (EV-DO). Other examples can be implemented within systems employing IEEE 1002.11 (Wi-Fi), IEEE 1002.16 (WiMAX), IEEE 1002.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunications standards, network architecture, and / or communication standards employed will depend on the specific application and the overall design constraints imposed on the system.

[0235] While aspects and embodiments are described herein by way of example, those skilled in the art will understand that additional implementations and use cases may arise in many different arrangements and scenarios. The features described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, embodiments and / or devices may arise via integrated chip embodiments and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to particular use cases or applications, broad applicability of the described innovations is possible. The scope of implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical contexts, devices incorporating the described aspects and features may also necessarily include additional components and features for implementing and practicing the claimed and described embodiments. For example, the transmission and reception of wireless signals requires several components for analog and digital purposes (e.g., hardware components, including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The features described herein are intended to be implemented in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user equipment, etc., of various sizes, shapes, and configurations.

[0236] Within this disclosure, the term "exemplary" is used to mean "serving as an example, instance, or illustration." Any implementation or aspect described herein as "exemplary" is not necessarily to be construed as superior to or better than other aspects. Similarly, the term "aspect" does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed. The term "coupling" is used herein to refer to direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, then objects A and C can still be considered coupled to each other—even if they are not in direct physical contact. For example, a first object can be coupled to a second object, even if the first object never directly contacts the second object. The terms "circuit" and "circuit system" are used broadly and are intended to include both hardware implementations of electronic devices and conductors, and software implementations of information and instructions, which, when connected and configured, enable the performance of the functions described in this disclosure, without limitation on the type of electronic circuit, and which, when executed by a processor, enable the performance of the functions described in this disclosure.

[0237] Figure 1-22One or more of the components, steps, features, and / or functions described herein may be rearranged and / or combined into a single component, step, feature, or function, or may be implemented in several components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figure 1 , 2 The apparatus, devices, and / or components described in 4, 5, 6, 9, 15, and 16 can be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein can also be efficiently implemented in software and / or embedded in hardware. Generally, Figure 1-22 The various components, steps, features, and / or functions described in the text are not mutually exclusive.

[0238] It will be understood that the specific order or hierarchy of the steps in the disclosed methods is an explanation of an exemplary process. Based on design preferences, it will be understood that the specific order or hierarchy of the steps in these methods may be rearranged. The appended method claims present the elements of the various steps in a sample order and are not intended to be limited to the specific order or hierarchy presented, unless specifically stated herein.

[0239] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will readily be understood by those skilled in the art, and the universal principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be granted the full scope consistent with the language of the claims, wherein references to the singular form of an element are not intended to mean “one and only one”—unless specifically stated otherwise—but are intended to mean “one or more.” Unless specifically stated otherwise, the term “some” refers to one or more. The phrase “at least one” referring to a list of items refers to any combination of these items, including a single member. As an example, “at least one of a, b, or c” is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the aspects described throughout this disclosure that are currently or hereafter known to a person skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be donated to the public, whether or not such disclosure is expressly stated in the claims.

Claims

1. A user equipment (UE), comprising: transceiver; Memory; as well as A processor, communicatively coupled to the transceiver and the memory, and configured to: The UE receives an indicator of power control configuration from the base station, the power control configuration being transmitted by the UE on the physical uplink control channel (PUCCH) on the secondary component carriers of an uplink component carrier set including primary component carriers and secondary component carriers, wherein the indicator indicates carrier-specific cumulative closed-loop power control, wherein the power control value is accumulated individually by the UE for each component carrier in the uplink component carrier set; and The PUCCH transmission is transmitted to the base station on the subcomponent carrier, at least in part based on the power control configuration.

2. The UE of claim 1, wherein the processor is further configured to receive individual power adjustment indicator signals for each component carrier in the uplink component carrier set according to the carrier-specific cumulative closed-loop power control.

3. The UE of claim 1, wherein the indicator includes a single dynamic power control command within downlink control information (DCI) for ACK / NACK feedback of the scheduled physical downlink shared channel (PDSCH).

4. The UE of claim 1, wherein the indicator comprises: A first indicator used in conjunction with enhanced mobile broadband (eMBB) transmission and a second indicator used in conjunction with ultra-reliable low latency communication (URLLC) transmission.

5. A method for conducting wireless communication at a user equipment (UE), the method comprising: The UE receives an indicator of power control configuration from the base station, the power control configuration being transmitted by the UE on the physical uplink control channel (PUCCH) on the secondary component carriers of an uplink component carrier set including primary component carriers and secondary component carriers, wherein the indicator indicates carrier-specific cumulative closed-loop power control, wherein the power control value is accumulated individually by the UE for each component carrier in the uplink component carrier set; and The PUCCH transmission is transmitted to the base station on the subcomponent carrier, at least in part based on the power control configuration.

6. The method of claim 5, wherein the indicator comprises a single dynamic power control command within downlink control information (DCI) for ACK / NACK feedback of the scheduled physical downlink shared channel (PDSCH).

7. The method of claim 5, wherein the indicator comprises: A first indicator used in conjunction with enhanced mobile broadband (eMBB) transmission and a second indicator used in conjunction with ultra-reliable low latency communication (URLLC) transmission.

8. A base station, comprising: transceiver; Memory; as well as A processor, communicatively coupled to the transceiver and the memory, and configured to: A power control configuration indicator is transmitted to the User Equipment (UE) by the UE via the Physical Uplink Control Channel (PUCCH) on the secondary component carriers in an uplink component carrier set comprising a primary component carrier and secondary component carriers. The indicator indicates carrier-specific cumulative closed-loop power control, wherein the power control value is accumulated individually by the UE for each component carrier in the uplink component carrier set. The UE receives the PUCCH transmission on the subcomponent carrier, at least in part based on the power control configuration.

9. The base station of claim 8, wherein the processor is further configured to transmit individual power adjustment indicator signals for each component carrier in the uplink component carrier set according to the carrier-specific cumulative closed-loop power control.

10. The base station of claim 8, wherein the indicator includes a single dynamic power control command within downlink control information (DCI) for ACK / NACK feedback of the scheduled physical downlink shared channel (PDSCH).

11. The base station of claim 8, wherein the indicator includes: A first indicator used in conjunction with enhanced mobile broadband (eMBB) transmission and a second indicator used in conjunction with ultra-reliable low latency communication (URLLC) transmission.

12. A method for conducting wireless communication at a base station, the method comprising: A power control configuration indicator is transmitted to the User Equipment (UE) by the UE via the Physical Uplink Control Channel (PUCCH) on the secondary component carriers in an uplink component carrier set comprising a primary component carrier and secondary component carriers. The indicator indicates carrier-specific cumulative closed-loop power control, wherein the power control value is accumulated individually by the UE for each component carrier in the uplink component carrier set. The UE receives the PUCCH transmission on the subcomponent carrier, at least in part based on the power control configuration.

13. The method of claim 12, wherein the indicator comprises a single dynamic power control command within downlink control information (DCI) for ACK / NACK feedback of the scheduled physical downlink shared channel (PDSCH).

14. The method of claim 12, wherein the indicator comprises: A first indicator used in conjunction with enhanced mobile broadband (eMBB) transmission and a second indicator used in conjunction with ultra-reliable low latency communication (URLLC) transmission.

Images