Identification of control channel resource

Abstract

Each state involves the transmission of Entity Uplink Control Channel (PUCCH) information. User Equipment (UE) can receive a first Entity Downlink Control Channel (PDCCH) candidate carried by a control resource set, which also carries a second PDCCH candidate, wherein these PDCCH candidates are associated with different aggregation levels. UE can identify PUCCH resources used to transmit information (e.g., ACK or NACK) associated with Entity Downlink Shared Channel (PDSCH) transmissions scheduled by the first PDCCH candidate. For example, UE can identify PUCCH resources based on the Control Channel Element (CCE) index corresponding to the starting CCE of the first and second PDCCH candidates.

Description

Identification of control channel resources This patent application claims priority and interest in pending U.S. non-provisional application No. 17 / 956,557, filed September 29, 2022, entitled "IDENTIFICATION OF CONTROL CHANNEL REOURCE," which has been assigned to the assignee of this application and is hereby expressly incorporated herein by reference as if its entire contents were fully set forth herein and for all applicable purposes. Application No. 17 / 956,557 claims priority and interest in pending U.S. provisional application No. 63 / 285,943, filed December 3, 2021, entitled "IDENTIFICATION OF CONTROL CHANNEL REOURCE," which has been assigned to the assignee of this application and is hereby expressly incorporated herein by reference as if its entire contents were fully set forth herein and for all applicable purposes. The technology discussed below is generally related to wireless communication, and more specifically, to identifying resources used for the transmission of information for the physical uplink control channel. Next-generation wireless communication systems (e.g., 5G) may include a 5G core network and a 5G radio access network (RAN), such as a new radio (NR)-RAN. NR-RAN supports communication via one or more cells. For example, a wireless communication device such as a user equipment (UE) may access a first cell of a first base station (BS) such as a gNB and / or access a second cell of a second base station. Base stations can schedule access to cells to support access by multiple UEs. For example, a base station can allocate different resources (e.g., time-domain and frequency-domain resources) to different UEs operating within a cell on the base station. The following is a simplified summary of one or more aspects of the content of this case to provide a basic understanding of these aspects. This summary is not a comprehensive overview of all anticipated aspects of the content of this case, nor is it intended to identify key or essential elements of all aspects of the content of this case, nor is it a description of any or all aspects of the content of this case. Its sole purpose is to present some concepts of one or more aspects of the content of this case as a prelude to a more detailed description to be presented later. In some instances, a user equipment may include a transceiver, memory, and a processor coupled to the transceiver and memory. The processor and memory may be configured to: receive via the transceiver a first entity downlink control channel (PDCCH) candidate for a first control resource set, the first PDCCH candidate being associated with a first aggregation level and configured to schedule entity uplink control channels (PUCCHs) with acknowledgment information, the first aggregation level being different from a second aggregation level associated with a second PDCCH candidate for the first control resource set. The processor and memory may also be configured to: transmit via the transceiver a PUCCH with acknowledgment information on PUCCH resources identified at least in part based on the index of a first control channel element (CCE) corresponding to the starting CCE of the first and second PDCCH candidates. In some instances, a method for wireless communication at a user equipment is disclosed. The method may include: receiving a first entity downlink control channel (PDCCH) candidate of a first control resource set, the first PDCCH candidate being associated with a first aggregation level and configured to schedule an entity uplink control channel (PUCCH) with acknowledgment information, the first aggregation level being different from a second aggregation level associated with a second PDCCH candidate of the first control resource set. The method may also include: transmitting a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on the index of a first control channel element (CCE) corresponding to the starting CCE of the first PDCCH candidate and the second PDCCH candidate. In some instances, a user equipment may include: a unit for receiving a first entity downlink control channel (PDCCH) candidate of a first control resource set, the first PDCCH candidate being associated with a first aggregation level and configured to schedule an entity uplink control channel (PUCCH) with acknowledgment information, the first aggregation level being different from a second aggregation level associated with a second PDCCH candidate of the first control resource set. The user equipment may also include: a unit for transmitting a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on the index of a first control channel element (CCE) corresponding to the starting CCE of the first and second PDCCH candidates. In some instances, a non-transitory computer-readable medium has instructions stored therein, executable by one or more processors of a user device, to perform the following operations: receiving a first entity downlink control channel (PDCCH) candidate of a first control resource set, the first PDCCH candidate being associated with a first aggregation level and configured to schedule an entity uplink control channel (PUCCH) with acknowledgment information, the first aggregation level being different from a second aggregation level associated with a second PDCCH candidate of the first control resource set. The non-transitory computer-readable medium may also have instructions stored therein, executable by one or more processors of a user device, to perform the following operations: transmitting a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on a first CCE index corresponding to the start control channel element (CCE) of the first and second PDCCH candidates. In some instances, a user equipment may include a transceiver, memory, and a processor coupled to the transceiver and memory. The processor and memory may be configured to: receive via the transceiver a first entity downlink control channel (PDCCH) candidate of a first control resource set, the first PDCCH candidate scheduling an entity uplink control channel (PUCCH) with acknowledgment information (e.g., HARQ-Ack information), and starting at the same control channel element (CCE) as a second PDCCH candidate within the first control resource set; the first PDCCH candidate repeats in a third PDCCH candidate of a second control resource set; the second PDCCH candidate repeats in a fourth PDCCH candidate of the second control resource set; the third PDCCH candidate is associated with a first aggregation level; and the fourth PDCCH candidate is associated with a second aggregation level higher than the first aggregation level. The processor and memory may also be configured to: transmit via the transceiver a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on a first CCE index corresponding to the starting CCE of the fourth PDCCH candidate associated with the second aggregation level higher than the first aggregation level. In some instances, a method for wireless communication at a user equipment is disclosed. The method may include: receiving a first entity downlink control channel (PDCCH) candidate in a first control resource set, the first PDCCH candidate scheduling an entity uplink control channel (PUCCH) with acknowledgment information (e.g., HARQ-Ack information), and starting at the same control channel element (CCE) as a second PDCCH candidate within the first control resource set; the first PDCCH candidate repeating in a third PDCCH candidate in a second control resource set; the second PDCCH candidate repeating in a fourth PDCCH candidate in the second control resource set; the third PDCCH candidate associated with a first aggregation level; and the fourth PDCCH candidate associated with a second aggregation level higher than the first aggregation level. The method may also include: transmitting a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on a first CCE index corresponding to the starting CCE of the fourth PDCCH candidate associated with the second aggregation level higher than the first aggregation level. In some instances, a user equipment may include: a unit for receiving a first entity downlink control channel (PDCCH) candidate of a first control resource set, the first PDCCH candidate scheduling an entity uplink control channel (PUCCH) with acknowledgment information (e.g., HARQ-Ack information) and starting at the same control channel element (CCE) as a second PDCCH candidate within the first control resource set, the first PDCCH candidate repeating in a third PDCCH candidate of a second control resource set, the second PDCCH candidate repeating in a fourth PDCCH candidate of the second control resource set, the third PDCCH candidate associated with a first aggregation level, and the fourth PDCCH candidate associated with a second aggregation level higher than the first aggregation level. The user equipment may also include: a unit for transmitting a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on a first CCE index corresponding to the starting CCE of the fourth PDCCH candidate associated with the second aggregation level higher than the first aggregation level. In some instances, a non-transitory computer-readable medium has instructions stored therein that can be executed by one or more processors of a user device to perform the following operations: receiving a first entity downlink control channel (PDCCH) candidate of a first control resource set, the first PDCCH candidate scheduling an entity uplink control channel (PUCCH) with acknowledgment information (e.g., HARQ-Ack information) and starting at the same control channel element (CCE) as a second PDCCH candidate in the first control resource set, the first PDCCH candidate repeating in a third PDCCH candidate of a second control resource set, the second PDCCH candidate repeating in a fourth PDCCH candidate of a second control resource set, the third PDCCH candidate being associated with a first aggregation level, and the fourth PDCCH candidate being associated with a second aggregation level higher than the first aggregation level. The non-transitory computer-readable medium may also have instructions stored therein, which can be executed by one or more processors of a user device to perform the following operation: sending a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on a first CCE index corresponding to the starting CCE of a fourth PDCCH candidate associated with a second aggregation level above the first aggregation level. In some instances, a user equipment may include a transceiver, memory, and a processor coupled to the transceiver and memory. The processor and memory may be configured to: receive via the transceiver a first entity downlink control channel (PDCCH) candidate of a first control resource set, the first PDCCH candidate scheduling an entity uplink control channel (PUCCH) with acknowledgment information (e.g., HARQ-Ack information), and starting at the same control channel element (CCE) as a second PDCCH candidate within the first control resource set; the first PDCCH candidate repeats in a third PDCCH candidate of a second control resource set; the second PDCCH candidate repeats in a fourth PDCCH candidate of the second control resource set; the third PDCCH candidate is associated with a first aggregation level; and the fourth PDCCH candidate is associated with a second aggregation level higher than the first aggregation level. The processor and memory may also be configured to: transmit via the transceiver a PUCCH with acknowledgment information on PUCCH resources identified at least in part based on a first CCE index corresponding to the starting CCE of the third PDCCH candidate associated with a first aggregation level lower than the second aggregation level. In some instances, a method for wireless communication at a user equipment is disclosed. The method may include: receiving a first entity downlink control channel (PDCCH) candidate in a first control resource set, the first PDCCH candidate scheduling an entity uplink control channel (PUCCH) with acknowledgment information (e.g., HARQ-Ack information), and starting at the same control channel element (CCE) as a second PDCCH candidate within the first control resource set; the first PDCCH candidate repeating in a third PDCCH candidate in a second control resource set; the second PDCCH candidate repeating in a fourth PDCCH candidate in the second control resource set; the third PDCCH candidate associated with a first aggregation level; and the fourth PDCCH candidate associated with a second aggregation level higher than the first aggregation level. The method may also include: transmitting a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on a first CCE index corresponding to the starting CCE of the third PDCCH candidate associated with the first aggregation level and lower than the second aggregation level. In some instances, a user equipment may include: a unit for receiving a first entity downlink control channel (PDCCH) candidate of a first control resource set, the first PDCCH candidate scheduling an entity uplink control channel (PUCCH) with acknowledgment information (e.g., HARQ-Ack information) and starting at the same control channel element (CCE) as a second PDCCH candidate within the first control resource set, the first PDCCH candidate repeating in a third PDCCH candidate of a second control resource set, the second PDCCH candidate repeating in a fourth PDCCH candidate of the second control resource set, the third PDCCH candidate associated with a first aggregation level, and the fourth PDCCH candidate associated with a second aggregation level higher than the first aggregation level. The user equipment may also include: a unit for transmitting a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on a first CCE index corresponding to the starting CCE of the third PDCCH candidate associated with the first aggregation level and lower than the second aggregation level. In some instances, a non-transitory computer-readable medium has instructions stored therein that can be executed by one or more processors of a user device to perform the following operations: receiving a first entity downlink control channel (PDCCH) candidate of a first control resource set, the first PDCCH candidate scheduling an entity uplink control channel (PUCCH) with acknowledgment information (e.g., HARQ-Ack information) and starting at the same control channel element (CCE) as a second PDCCH candidate in the first control resource set, the first PDCCH candidate repeating in a third PDCCH candidate of a second control resource set, the second PDCCH candidate repeating in a fourth PDCCH candidate of a second control resource set, the third PDCCH candidate being associated with a first aggregation level, and the fourth PDCCH candidate being associated with a second aggregation level higher than the first aggregation level. The non-transitory computer-readable medium may also have instructions stored therein, which can be executed by one or more processors of a user device to perform the following operation: sending a PUCCH with confirmation information on a PUCCH resource identified at least in part based on a first CCE index corresponding to the starting CCE of a third PDCCH candidate associated with a first aggregation level and below the second aggregation level. In some instances, a user equipment may include a transceiver, memory, and a processor coupled to the transceiver and memory. The processor and memory may be configured to: receive via the transceiver a first entity downlink control channel (PDCCH) candidate for a first control resource set, the first PDCCH candidate scheduling an entity uplink control channel (PUCCH) with acknowledgment information, and starting at the same control channel element (CCE) as a second PDCCH candidate within the first control resource set; the first PDCCH candidate repeats in a third PDCCH candidate of a second control resource set; the second PDCCH candidate repeats in a fourth PDCCH candidate of the second control resource set; within the second control resource set, the third PDCCH candidate is associated with a first starting CCE, and the fourth PDCCH candidate is associated with a second starting CCE higher than the first starting CCE. The processor and memory may also be configured to: transmit via the transceiver a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on a first CCE index corresponding to the second starting CCE. In some instances, a method for wireless communication at a user equipment is disclosed. The method may include: receiving a first entity downlink control channel (PDCCH) candidate in a first control resource set, the first PDCCH candidate scheduling an entity uplink control channel (PUCCH) with acknowledgment information, and starting at the same control channel element (CCE) as a second PDCCH candidate within the first control resource set; the first PDCCH candidate repeating in a third PDCCH candidate in a second control resource set; the second PDCCH candidate repeating in a fourth PDCCH candidate in the second control resource set; within the second control resource set, the third PDCCH candidate associated with a first starting CCE; and the fourth PDCCH candidate associated with a second starting CCE above the first starting CCE. The method may also include: transmitting a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on a first CCE index corresponding to the second starting CCE. In some instances, a user equipment may include: a unit for receiving a first entity downlink control channel (PDCCH) candidate in a first control resource set, the first PDCCH candidate scheduling an entity uplink control channel (PUCCH) with acknowledgment information and starting at the same control channel element (CCE) as a second PDCCH candidate in the first control resource set, the first PDCCH candidate repeating in a third PDCCH candidate in a second control resource set, the second PDCCH candidate repeating in a fourth PDCCH candidate in the second control resource set, the third PDCCH candidate being associated with a first starting CCE in the second control resource set, and the fourth PDCCH candidate being associated with a second starting CCE above the first starting CCE. The user equipment may also include: a unit for transmitting a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on a first CCE index corresponding to the second starting CCE. In some instances, a non-transitory computer-readable medium has instructions stored therein, executable by one or more processors of a user device, to perform the following operations: receiving a first entity downlink control channel (PDCCH) candidate in a first control resource set, the first PDCCH candidate scheduling an entity uplink control channel (PUCCH) with acknowledgment information, and starting at the same control channel element (CCE) as a second PDCCH candidate in the first control resource set; the first PDCCH candidate repeats in a third PDCCH candidate in a second control resource set; the second PDCCH candidate repeats in a fourth PDCCH candidate in the second control resource set; within the second control resource set, the third PDCCH candidate is associated with a first starting CCE; and the fourth PDCCH candidate is associated with a second starting CCE above the first starting CCE. The non-transitory computer-readable medium may also have instructions stored therein, executable by one or more processors of a user device, to perform the following operations: transmitting a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on a first CCE index corresponding to a second starting CCE. These and other variations of the present invention will be more fully understood after reading the following description of specific examples of the present invention. Other variations, features, and examples of the present invention will become apparent to those skilled in the art upon reading the following description of specific examples of the present invention in conjunction with the accompanying drawings. Although features of the present invention may be discussed below with respect to certain examples and drawings, all examples of the present invention may include one or more of the advantageous features discussed herein. That is, although one or more examples may be discussed as having certain advantageous features, one or more of such features may also be used in various examples of the present invention discussed herein. Similarly, although examples may be discussed below as examples of apparatus, systems, or methods, it should be understood that such examples may be implemented in various apparatuses, systems, and methods. The embodiments described below with reference to the accompanying drawings are intended as descriptions of various configurations and are not intended to represent the only configurations in which the concepts described herein can be practiced. Specific details are included in these embodiments to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art to which this invention pertains that these concepts can be practiced without these specific details. In some cases, various structures and components are illustrated in block diagram form to avoid obscuring these concepts. Although various forms and examples have been described herein through the illustration of some instances, those skilled in the art will understand that other implementations and use cases can be realized in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, forms and / or uses can be implemented via devices that integrate chip instances and other non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a particular use case or application, a wide variety of applicability to 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 original equipment manufacturer (OEM) devices or systems incorporating one or more forms of the described innovations. In some practical settings, devices incorporating the described forms and features may also necessary include additional components and features for implementing and practicing the declared and described examples. For example, the transmission and reception of wireless signals must include multiple 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 innovative intentions described herein can be implemented in a wide variety of devices, chip-level components, systems, distributed arrangements, de-aggregated arrangements (e.g., base stations and / or UEs), end-user equipment, etc., of different sizes, shapes, and configurations. The various forms of this case involve the transmission of Entity Uplink Control Channel (PUCCH) information. A User Equipment (UE) can receive Entity Downlink Control Channel (PDCCH) candidates carrying Downlink Control Information (DCI) from a network entity such as a base station via at least one set of control resources. In some cases, these PDCCH candidates can be repeated (e.g., in different sets of control resources) and can be associated with different aggregation levels. The UE can identify the PUCCH resource used to transmit information (e.g., a positive acknowledgment (ACK) or a negative acknowledgment (NACK)) in response to a DCI carried by at least one of the PDCCH candidates. In some instances, the identification of such PUCCH resources can be based at least in part on the control channel element (CCE) index corresponding to the starting CCE of the PDCCH candidate carrying the DCI. In some cases (e.g., when PDCCH candidates are repeated and have different aggregation levels), there may be ambiguity regarding which starting CCE will be used as the basis for the PUCCH resource decision. In some cases, this application relates to various rules for specifying a particular starting CCE used to determine PUCCH resources. In some instances, the UE can identify PUCCH resources based on the CCE index corresponding to the starting CCE of a first PDCCH candidate and a second PDCCH candidate (i.e., these PDCCH candidates have the same starting CCE). In some instances, the UE can identify PUCCH resources based on the CCE index corresponding to the starting CCE of a PDCCH candidate associated with a higher aggregation level than the other PDCCH candidate. In some instances, the UE can identify PUCCH resources based on the CCE index corresponding to the starting CCE of a PDCCH candidate associated with a lower aggregation level than the other PDCCH candidate. In some instances, the UE can identify PUCCH resources based on the CCE index corresponding to the starting CCE of a PDCCH candidate with a higher starting CCE than the other PDCCH candidate. The various concepts presented throughout this document can be implemented in various telecommunications systems, network architectures, and communication standards. Referring now to Figure 1, as a non-limiting illustrative example, various aspects of this document are illustrated with reference to a wireless communication system 100. 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. With the aid of the wireless communication system 100, the UE 106 can perform data communication with an external data network 110 (such as, but not limited to, the Internet). RAN 104 can implement any suitable (multiple) radio communication technologies to provide radio access to UE 106. As one example, RAN 104 can operate according to the 3GPP New Radio (NR) specification (commonly referred to as 5G). As another example, RAN 104 can operate under a hybrid of 5G NR and the Evolved Universal Terrestrial Radio Access Network (eUTRAN) standard, commonly known as Long Term Evolution (LTE). 3GPP refers to this hybrid RAN as Next Generation RAN or NG-RAN. In yet another instance, RAN 104 can operate according to both LTE and 5G NR standards. Of course, many other examples can be utilized within the scope of this case. As shown in the figure, RAN 104 includes a plurality of base stations 108. Broadly speaking, a base station is a network element (e.g., a network entity) in a radio access network responsible for transmitting radio signals 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), node B (NB), eNode B (eNB), gNode B (gNB), transmit and receive point (TRP), or some other suitable term. In some instances, a base station may include two or more TRPs that may be co-located or non-co-located. Each TRP may communicate on the same or different carrier frequencies within the same or different frequency bands. In an instance where RAN 104 operates according to both LTE and 5G NR standards, one of the base stations 108 may be an LTE base station, while the other may be a 5G NR base station. Further illustration shows a radio access network 104 supporting wireless communication for multiple mobile devices. Mobile devices may be referred to as User Equipment (UE) 106 in the 3GPP standard, but may also be referred to by those skilled in the art as mobile station (MS), user station, mobile unit, user unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile user station, access terminal (AT), mobile terminal, wireless terminal, remote terminal, handheld device, terminal, user agent, mobile service client, client, or any other suitable term. The UE may be a device that provides access to network services to users. In an example where RAN 104 operates according to both LTE and 5G NR standards, the UE 106 may be an Evolved Universal Terrestrial Radio Access Network - New Radio Dual Connectivity (EN-DC) UE capable of simultaneously connecting to both LTE and NR base stations to receive data packets from both. In this document, a mobile device is not necessarily capable of movement and can be stationary. The term mobile device or mobile equipment refers to a wide variety of devices and technologies. A UE may include multiple hardware components that are sized, shaped, and arranged to facilitate communication; these 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 a broad array of mobile devices, cellular phones, smartphones, conversation initiation protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smart computers, tablets, personal digital assistants (PDAs), and embedded systems, such as those corresponding to the "Internet of Things" (IoT). Mobile devices can also include automobiles or other transport vehicles, remote sensors or actuators, robots or robotic equipment, satellite radio equipment, 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 include digital home or smart home devices such as home audio, video and / or multimedia equipment, appliances, vending machines, smart lighting, home security systems, smart meters, etc. Mobile devices can also include smart energy devices, security devices, solar panels or solar arrays, municipal infrastructure equipment for controlling electricity (e.g., smart grids), lighting, water, etc.; industrial automation and enterprise equipment; logistics controllers; agricultural equipment, etc. Furthermore, mobile devices can provide connected medical or telemedicine support, i.e., remote healthcare. Remote healthcare devices may include remote healthcare monitoring devices and remote healthcare management devices, whose communications may be given priority processing or access over other types of information, for example, priority access for transmitting critical service data and / or related QoS patterns for transmitting critical service data. Radio communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions via 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. In some instances, the term downlink can refer to point-to-multipoint transmissions initiated at the base station (e.g., base station 108). Another way to describe such point-to-multipoint transmission schemes 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. In some instances, the term uplink can refer to point-to-point transmissions initiated at the UE (e.g., UE 106). In some instances, access to an empty interfacing can be scheduled, where a scheduling entity (e.g., base station 108) allocates resources for communication between some or all devices and apparatuses within its service area or cell. In this context, as further discussed below, the scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more scheduled entities (e.g., UEs). That is, for scheduled communication, multiple UEs 106 of the scheduled entities may utilize resources allocated by the scheduling entity (e.g., base station 108). Base station 108 is not the only entity that can be used as a scheduling entity. That is, in some instances, 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). For example, a UE can communicate with other UEs in a peer-to-peer or device-to-device manner and / or in a relay configuration. As shown in Figure 1, a scheduling entity (e.g., base station 108) can broadcast downlink traffic 112 to one or more scheduled entities (e.g., UE 106). Broadly speaking, a scheduling entity is a node or device responsible for scheduling traffic in a wireless communication network, including downlink traffic 112, and in some instances, uplink traffic 116 and / or uplink control information 118 from one or more scheduled entities to the scheduling entity. Alternatively, a scheduled entity is a node or device receiving downlink control information 114, which includes, but is not limited to, scheduling information (e.g., authorization), synchronization or timing information, or other control information from another entity in the wireless communication network (such as the scheduling entity). Additionally, uplink control information 118, downlink control information 114, downlink traffic 112, and / or uplink traffic 116 can be time-divided into frames, subframes, time slots, and / or symbols. As used herein, a symbol can refer to a time unit in an Orthogonal Frequency Division Multiplexing (OFDM) waveform where each subcarrier carries a resource element (RE). In some instances, a time slot can carry 7 or 14 OFDM symbols. A subframe can refer to a duration of 1 millisecond (ms). Multiple subframes or time slots can be encapsulated together to form a single frame or radio frame. Within the scope of this document, a frame can represent a predetermined duration (e.g., 10 ms) for wireless transmission, where each frame consists of, for example, 10 subframes, each 1 ms in length. Of course, these definitions are not mandatory, and any suitable scheme for organizing the waveform can be used, and various time divisions of the waveform can have any suitable duration. Typically, base station 108 may include a backhaul interface for communicating with backhaul 120 of a wireless communication system. Backhaul 120 provides a link between base station 108 and core network 102. Furthermore, in some instances, the backhaul network provides interconnection between the individual base stations 108. Various types of backhaul interfaces using any suitable transport network can be employed, such as direct physical connections, virtual networks, etc. The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some instances, the core network 102 may be configured according to a 5G standard (e.g., 5GC). In other instances, the core network 102 may be configured according to 4G Evolved Packet Core (EPC) or any other suitable standard or configuration. Referring now to Figure 2, a schematic diagram of a radio access network (RAN) 200 is provided as an example rather than a limitation. In some instances, RAN 200 may be the same as RAN 104 described above and shown in Figure 1. The geographical area covered by RAN 200 can be divided into cellular regions (cells), which can be uniquely identified by user equipment (UE) based on an identifier broadcast from an access point or base station. Figure 2 illustrates cells 202, 204, 206, and 208, each of which may include one or more sectors (not shown). A sector is a sub-region of a cell. All sectors within a cell are served by the same base station. Radio links within a sector can be identified by a single logical identifier belonging to that sector. In a cell divided into sectors, multiple sectors within the cell can be formed by antenna groups, where each antenna is responsible for communicating with UEs within a portion of the cell. Various base station arrangements can be utilized. For example, in Figure 2, two base stations 210 and 212 are illustrated in cells 202 and 204; and base station 214 is shown as the remote radio head (RRH) 216 in control cell 206. That is, the base station can have an integrated antenna, or it can be wired to an antenna or RRH via a feed cable. In the illustrated example, cells 202, 204, and 206 can be referred to as macrocells because base stations 210, 212, and 214 support cells with large sizes. Furthermore, base station 218 is illustrated in cell 208, which can overlap with one or more macrocells. In this example, cell 208 can be referred to as a small cell (e.g., microcell, picocell, femtocell, home base station, home B-node, home eNode B-node, etc.) because base station 218 supports cells with relatively small sizes. Cell size design can be accomplished according to system design and component constraints. It should 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 instances, base stations 210, 212, 214, and / or 218 may be identical to the base station / scheduling entities described above and shown in Figure 1. Figure 2 also includes a drone (UAV) 220, which can be a drone or a quadcopter. The UAV 220 can be configured to be used as a base station, or more specifically as a mobile base station. That is, in some instances, the cell may not necessarily be stationary, and the geographical area of ​​the cell may move depending on the location of a mobile base station such as the UAV 220. 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, and 218 may be configured to provide an access point to core network 102 (see Figure 1) to all UEs within the corresponding cell. 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; and UE 234 may communicate with base station 218. In some instances, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may be the same as the UE / scheduled entity described above and shown in Figure 1. In some instances, UAV 220 (e.g., a quadcopter) can be a mobile network node and can be configured to function as a UE. For example, UAV 220 can operate within cell 202 via communication with base station 210. In another configuration of RAN 200, sidelink signals can be used between UEs without relying on scheduling or control information from the base station. For example, sidelink communication can be utilized in device-to-device (D2D) networks, peer-to-peer (P2P) networks, vehicle-to-vehicle (V2V) networks, vehicle-to-everything (V2X) networks, and / or other suitable sidelink networks. For instance, two or more UEs (e.g., UEs 238, 240, and 242) can communicate with each other using sidelink signal 237 without relaying the communication via a base station. In some instances, UEs 238, 240, and 242 can each act as a scheduling entity or sending sidelink device and / or a scheduled entity or receiving sidelink device to schedule resources and communicate using sidelink signal 237 without relying on scheduling or control information from the base station. In other instances, two or more UEs (e.g., UEs 226 and 228) within the coverage area of ​​a base station (e.g., base station 212) may also communicate using the sidelink signal 227 on a direct link (sidelink) without transmitting the communication via base station 212. In this instance, base station 212 may allocate resources for sidelink communication to UEs 226 and 228. In RAN 200, the ability of a UE to communicate independently of its location while on the move is referred to as mobility. Typically, under the control of the Access and Mobility Management Function (AMF, not shown, part of core network 102 in Figure 1), various physical channels between the UE and the radio access network are established, maintained, and released. The AMF may include the Security Context Management Function (SCMF) for managing the security context for both control plane and user plane functions, and the Security Anchoring Function (SEAF) for performing authentication. RAN 200 can utilize DL-based mobility or UL-based mobility to achieve mobility and handover (i.e., transferring the UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, 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 (shown as a vehicle, but any suitable form of UE can be used) can move from the geographic area corresponding to its serving cell (e.g., cell 202) to the geographic area corresponding to a neighboring cell (e.g., cell 206). When the signal strength or quality from a neighboring cell exceeds that of its serving cell for a given amount of time, UE 224 may send a report message indicating this condition to its serving base station (e.g., base station 210). In response, UE 224 may receive a handover command, and the UE may experience a handover to cell 206. In a network configured for UL-based mobility, the UL reference signal from each UE can be used by the network to select a serving cell for each UE. In some instances, base stations 210, 212, and 214 / 216 can broadcast a unified synchronization signal (e.g., a unified primary synchronization signal (PSS), a unified secondary synchronization signal (SSS), and a unified physical broadcast channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 can receive the unified synchronization signal, derive the carrier frequency and time slot timing from the synchronization signal, and, in response to the derive timing, transmit an uplink pilot frequency or reference signal. The uplink pilot frequency signal transmitted by a UE (e.g., UE 224) can be simultaneously received by two or more cells within RAN 200 (e.g., base stations 210 and 214 / 216). Each cell can measure the strength of the pilot signal, and the radio access network (e.g., one or more of base stations 210 and 214 / 216 and / or a central node within the core network) can determine the serving cell for UE 224. When UE 224 moves via RAN 200, the network can continuously monitor the uplink pilot signal transmitted by UE 224. When the signal strength or quality of the pilot signal measured by a neighboring cell exceeds the signal strength or quality of the pilot signal measured by the serving cell, RAN 200 can switch UE 224 from the serving cell to a neighboring cell, with or without notifying UE 224. Although synchronization signals transmitted by base stations 210, 212, and 214 / 216 can be unified, the synchronization signals do not need to identify specific cells. Instead, they can identify areas of multiple cells operating at the same frequency and / or with the same timing. Using areas in 5G networks or other next-generation communication networks implements an uplink-based mobility framework and improves the efficiency of both the UE and the network by reducing the amount of mobility messages that need to be exchanged between the UE and the network. In various implementations, the air interface in RAN 200 can utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum provides exclusive use of a portion of the spectrum, typically due to mobile network service providers purchasing licenses from government regulatory agencies. Unlicensed spectrum provides shared use of a portion of the spectrum without requiring a government-granted license. While access to unlicensed spectrum generally still requires compliance with some technical rules, it is typically available to any service provider or device. Shared spectrum can fall between licensed and unlicensed spectrum, where technical rules or restrictions on access may be required, but the spectrum can still be shared by multiple service providers and / or multiple radio access technologies (RATs). For example, a licensee for a portion of licensed spectrum can provide licensed shared access (LSA) to share the spectrum with other parties, for example, by utilizing conditions determined by the appropriate licensee. The air interface in RAN 200 can utilize one or more multiplexing and multiplexing access algorithms to enable simultaneous communication between various devices. For example, the 5G NR specification uses Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) to provide multiplexing access for UL transmissions from UEs 222 and 224 to base station 210, as well as multiplexing 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 case, multiplexing and multiplexing access are not limited to the above-mentioned schemes, but can be provided using Time Division Multiplexing Access (TDMA), Code Division Multiplexing Access (CDMA), Frequency Division Multiplexing Access (FDMA), Sparse Code Multiplexing Access (SCMA), Resource Extended Access Multiplexing Access (RSMA), or other suitable multiplexing access schemes. Furthermore, multiplexing for 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. The air interface in RAN 200 can also utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link where two endpoints can communicate with each other in both directions. Full-duplex means that two 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 often implemented for wireless links utilizing Time Division Duplex (TDD). In TDD, time division multiplexing separates transmissions in different directions on a given channel from each other. That is, at certain times, the channel is dedicated to transmissions in one direction, and at other times, the channel is dedicated to transmissions in the other direction, where the direction can change very rapidly, for example, multiple times per time slot. In wireless links, full-duplex channels typically rely on physical isolation between the transmitter and receiver, as well as appropriate interference cancellation techniques. Full-duplex simulation for wireless links is often implemented using Frequency Division Duplex (FDD) or Space Division Duplex (SDD). In FDD, transmissions in different directions operate at different carrier frequencies. In SDD, transmissions in different directions on a given channel are separated from each other using Space Division Multiplexing (SDM). In other instances, full-duplex communication can be implemented in unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur in different subbands of the carrier bandwidth. This type of full-duplex communication can be referred to as Subband Full-Duplex (SBFD), Cross-Split-Duplex (xDD), or Flexible Duplex. The various forms of this invention will be described with reference to OFDM waveforms, an example of which is schematically shown in Figure 3. Those skilled in the art will understand that the various forms of this invention can be applied to SC-FDMA waveforms in essentially the same manner as described below. That is, although some examples of this invention may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to SC-FDMA waveforms. Referring now to FIG3, an expanded view of exemplary subframe 302 is illustrated, which depicts an OFDM resource grid. However, as will be readily understood by those skilled in the art to which this invention pertains, the entity (PHY) layer transport architecture for any particular application may differ from the examples described herein, depending on any number of factors. In this figure, time is in the horizontal direction, in OFDM symbols; frequency is in the vertical direction, in subcarriers of a carrier. 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 available antenna ports, a corresponding number of resource grids 304 can be used for communication. Resource grid 304 is divided into multiple resource elements (REs) 306. An RE 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 can represent one or more bits of information. In some instances, an RE block can be referred to as a physical resource block (PRB) or more simply as a resource block (RB) 308, which contains any suitable number of consecutive subcarriers in the frequency domain. In one instance, an RB can include 12 subcarriers, the number of which is independent of the digital scheme used. In some instances, depending on the digital scheme, an RB can include any suitable number of consecutive OFDM symbols in the time domain. In this context, it is assumed that a single RB such as RB 308 corresponds exactly to a single direction of communication (either transmission or reception for a given device). A collection of contiguous or discontinuous resource blocks may be referred to herein as a Resource Block Group (RBG), a subband, or a Bandwidth Part (BWP). A collection of subbands or BWPs may span the entire bandwidth. Scheduling by a scheduling entity (e.g., a UE) for downlink, uplink, or sidelink transmission typically involves scheduling one or more resource elements 306 within one or more subbands or bandwidth parts (BWPs). Therefore, a UE typically utilizes only a subset of the resource grid 304. In some instances, an RB may be the smallest unit of resource that can be allocated to a UE. Therefore, the more RBs scheduled for a UE, and the higher the modulation scheme selected for the air interface, the higher the data rate of the UE. RBs may be scheduled by a scheduling entity (such as a network entity (e.g., gNB, eNB, etc.)) or may be self-scheduled by the UE implementing D2D sidelink communication. In this figure, RB 308 is shown occupying less than the entire bandwidth of subframe 302, with some subcarriers illustrated above and below RB 308. In the given embodiment, subframe 302 may have a bandwidth corresponding to any number of one or more RBs 308. Furthermore, in this figure, RB 308 is shown occupying less than the entire duration of subframe 302, although this is merely one possible example. Each 1 ms subframe 302 can consist of one or more adjacent time slots. In the example shown in Figure 3, as an illustrative example, a subframe 302 includes four time slots 310. In some instances, time slots can 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. Other instances may include hour slots with shorter durations (e.g., one or three OFDM symbols), sometimes referred to as shortened transmission time intervals (TTIs). In some cases, these hour slots or shortened transmission time intervals (TTIs) can be transmitted, occupying resources scheduled for ongoing time slot transmissions for the same or different UEs. Any number of resource blocks can be utilized within a subframe or time slot. The unfolded diagram of one of the time slots 310 illustrates that the time slot 310 includes a control area 312 and a data area 314. Typically, the control area 312 may carry control channels, and the data area 314 may carry data channels. Of course, a time slot may contain all DLs, all ULs, or at least one DL portion and at least one UL portion. The structure shown in Figure 3 is merely an example, and different time slot structures can be used, and may include one or more of each of one (or more) control areas and one (or more) data areas. Although not illustrated in Figure 3, 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 frequencies or reference signals. These pilot frequencies or reference signals can be provided to the receiving equipment to perform channel estimation for the corresponding channels, which enables coherent demodulation / detection of the control and / or data channels within RB 308. In some instances, time slot 310 can be used for broadcast, multicast, or unicast communications. For example, broadcast, multicast, or unicast communications can refer to point-to-multipoint transmissions from one device (e.g., a network entity, UE, or other similar device) to other devices. Here, broadcast communications are delivered to all devices, while multicast or unicast communications are delivered to multiple intended receiving devices. Unicast communications can refer to point-to-point transmissions from one device to a single other device. In instances of cellular communication over a cellular carrier via a Uu interface, for DL ​​transmissions, a scheduling entity (e.g., a network entity) may allocate one or more REs 306 (e.g., within control area 312) to one or more scheduled entities (e.g., UEs) to carry DL control information including one or more DL control channels (such as Entity Downlink Control Channel (PDCCH)). The PDCCH carries downlink control information (DCI), including but not limited to power control commands (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, grants, and / or allocation of REs for DL ​​and UL transmissions. The PDCCH may also carry Hybrid Automatic Repeat Request (HARQ) feedback transmissions, such as ACK or NACK. HARQ is a technique well-known to those skilled in the art to which this invention pertains, where the integrity of packet transmissions can be checked for accuracy at the receiving end, for example, using any suitable integrity checking mechanism such as checksum or cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK can be sent; otherwise, a NACK can be sent. In response to a NACK, the sending device can send a HARQ retransmission, which can implement Chase combination, incremental redundancy, etc. Network entities can also 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 can be broadcast at regular intervals based on periodicity (e.g., 5ms, 10ms, 20ms, 30ms, 80ms, or 130ms). SSBs include the primary synchronization signal (PSS), secondary synchronization signal (SSS), and entity broadcast control channel (PBCH). UEs can utilize PSS and SSS to achieve synchronization of radio frames, subframes, time slots, and symbols in the time domain, identify the center of the channel (system) bandwidth in the frequency domain, and identify the entity cell identifier (PCI) of the cell. The PBCH in the SSB may also include a Master Information Block (MIB), which contains 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 (residual) 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., a default downlink digital scheme), system frame number, configuration of the PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), cell disable indicator, cell reselection indicator, grid offset, and search space (SS) 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. Network entities may also transmit other system information (OSI). In UL transmissions, the scheduled entity (e.g., the UE) may utilize one or more RE 306s to carry UL Control Information (UCI) to the scheduling entity, including one or more UL control channels (such as the Entity Uplink Control Channel (PUCCH)). UCIs may include various group types and categories, including pilot signals, reference signals, and information configured to enable or assist in decoding uplink data transmissions. Examples of uplink reference signals may include Sounding Reference Signals (SRS) and Uplink DMRS. In some instances, a UCI may include a scheduling request (SR), i.e., a request to the scheduling entity to schedule uplink transmissions. Here, in response to an SR sent on the UCI, the scheduling entity may send Downlink Control Information (DCI), which can schedule resources for uplink packet transmissions. UCIs may also include HARQ feedback, Channel Status Feedback (CSF) (such as CSI reports), or any other suitable UCI. In addition to control information, one or more REs 306 can be assigned to data traffic (e.g., within data area 314). Such data traffic can be carried on one or more traffic channels, for example, a Physical Downlink Shared Channel (PDSCH) for DL ​​traffic; or a Physical Uplink Shared Channel (PUSCH) for UL traffic. In some instances, one or more REs 306 within data area 314 can be configured to carry other signals, such as one or more SIBs and DMRSs. In an example of sidelink communication on a sidelink carrier via the ProSe 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 the initiating (transmitting) sidelink device (e.g., a transmitting (Tx) V2X device or other Tx UE) to one or more other receiving sidelink device sets (e.g., a receiving (Rx) V2X device or some other Rx UE). The data area 314 of time slot 310 may include a physical sidelink shared channel (PSSCH), which includes sidelink data transmissions transmitted by the initiating (transmitting) sidelink device within resources reserved on the sidelink carrier by the transmitting sidelink device via the SCI. Other information may also be transmitted on each RE 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. Additionally, one or more reference signals, such as sidelink SSB, sidelink CSI-RS, sidelink SRS, and / or sidelink positioning reference signal (PRS), can be transmitted within time slot 310. These physical channels are typically overridden and mapped to transport channels for processing at the Media Access Control (MAC) layer. Transport channels carry blocks called transport blocks (TBs). The transport block size (TBS) can correspond to the number of bits of information and can be a controlled parameter based on the modulation and coding scheme (MCS) and the number of redundancies (RBs) in a given transmission. The channels or carriers described above with reference to Figures 1 to 3 are not necessarily all channels or carriers that can be used between the scheduling entity and the scheduled entity, and those skilled in the art to which this invention pertains will recognize that other channels or carriers, such as other transmission, control, and feedback channels, may also be used in addition to the channels or carriers described. As mentioned above, network entities (e.g., base stations) can use the downlink control area of ​​a time slot to send PDCCH information to the UE. In some instances, the PDCCH information can be a scheduled DCI for a downlink transmission to the UE, an uplink transmission performed by the UE, or some other transmission. In some instances, the PDCCH information can be a non-scheduled DCI (e.g., a DCI carrying information but not scheduled for transmission). Figures 4 and 5 illustrate instance resource configurations that can be used to carry such PDCCH information. Figure 4 is a schematic diagram of an example of a downlink (DL) control region 402 according to some type of time slot. The DL control region 402 may correspond to, for example, the control region 312 of time slot 310 shown in Figure 3. As mentioned above, the DL control region 402 may carry a PDCCH including one or more DCIs. The DL control region 402 includes a plurality of CORESETs 404 indexed from CORESET #1 to CORESET #N. Each CORESET 404 includes several subcarriers in the frequency domain and one or more symbols in the time domain. In the example of Figure 4, each CORESET 404 includes at least one control channel element (CCE) 406, which has a size set to span at least three OFDM symbols in both frequency and time. CORESETs 404 having a size spanning two or more OFDM symbols may be advantageous for use on relatively small system bandwidths (e.g., 5 MHz). However, single-symbol CORESETs are also possible. In some instances, network entities can be configured with a CORESET 404 to carry group-shared control information or UE-specific control information, thereby enabling the CORESET 404 to transmit PDCCHs including group-shared control information or UE-specific control information to one or more UEs. Each UE can be configured to monitor one or more CORESET 404s to look for UE-specific control information or group-shared control information (e.g., on the PDCCH). In some instances, depending on the PDCCH format (e.g., aggregation level), a PDCCH can be constructed from a variable number of CCEs. Each PDCCH format (e.g., aggregation level) supports different DCI lengths. In some instances, PDCCH aggregation levels of 1, 2, 4, 8, and 16 can be supported, corresponding to 1, 2, 4, 8, or 16 adjacent CCEs, respectively. Figure 5 is a schematic diagram of an example of a CCE structure 500 in a DL control region 506 of a time slot of some type. The DL control region 506 may correspond to, for example, the control region 312 of a time slot 310 shown in Figure 3. The CCE structure 500 includes several REs 502 that can be grouped into at least one RE group (REG) 504. Each REG 504 may typically contain, for example, twelve consecutive REs 502 (or nine REs 502 and three DMRS REs) within the same OFDM symbol and the same RB. In the example of Figure 5, the CCE structure 500 includes at least six REGs 504 (not shown in whole) distributed across three OFDM symbols. However, as will be readily understood by those skilled in the art to which this invention pertains, the CCE structure 500 for any particular application may differ from the example described herein, depending on any number of factors. For example, the CCE structure 500 may contain any suitable number of REGs. In some instances, the UE may not be aware of the specific aggregation level of the PDCCH or whether multiple PDCCHs for that UE might exist in a time slot. Therefore, the UE can perform blind decoding of various PDCCH candidates within the first N control OFDM symbols of the time slot (as indicated by the time slot format) and / or the remaining OFDM symbols of the time slot. In some instances, this decoding is based on the Radio Network Temporary Identifier (RNTI) expected to be used by the network entity when encoding the PDCCH (e.g., a UE-specific RNTI or a group RNTI). Each PDCCH candidate comprises a set of one or more consecutive CCEs based on an assumed DCI length (e.g., the PDCCH aggregation level). The term PDCCH candidate is used here to emphasize that the UE may not be configured with information precisely indicating what type of PDCCH to carry in the time slot or where to carry a specific PDCCH within the time slot. Therefore, using blind decoding, the UE attempts to decode signals received on different resource sets (e.g., corresponding to different PDCCH candidates) to determine which resources actually carry a PDCCH. To limit the number of blind decodings performed by the UE, network entities can configure certain search spaces, such as UE-specific search spaces (USS) and common search spaces (CSS). Here, the network entity can send PDCCHs to the UE or set of UEs only on the resources specified for one (or more) configured search spaces. Therefore, the one or more UEs can restrict their blind decoding to the one (or more) configured search spaces. In some instances, the network entity can configure one or more search space sets, each including at least one search space. In some instances, different search space set identifiers (IDs) can be assigned to different search space sets. In some instances, the search space set ID can be referred to as the search space set index. A UE-specific search space set consists of CCEs used to send control information to a specific UE. The starting point (offset or index) of the UE-specific search space can be different for each UE. In addition, each UE can have multiple UE-specific search spaces (e.g., one search space per aggregation level). The common search space set consists of CCEs used to send control information common to a group of UEs or all UEs. Therefore, the common search space set is monitored by multiple UEs within the cell. The starting point (offset or index) of the search space set used for group-shared control information can be the same for all UEs in the group, and multiple search space sets can exist defined for group-shared control information (e.g., one search space set defined for each configured aggregation level of the group of UEs). The UE can perform blind decoding on all aggregation levels and the corresponding USS or CSS to determine whether the UE-specific search space (USS) or common search space (CSS) carries at least one valid DCI for that UE. By using the set of search spaces configured for the UE (e.g., USS and CSS) for blind decoding, the number of blind decoding operations performed by the UE for each PDCCH format combination can be reduced. The UE can monitor the search space to find downlink assignments and uplink grants related to a specific component carrier of the UE. For example, the UE can monitor the search space to find a PDCCH that includes a DCI, which schedules a PDSCH in the same or different time slots for use on that component carrier. In this case, the DCI includes frequency domain resource assignments and time domain resource assignments for the PDSCH, as well as other information (e.g., MCS, etc.) that enables the UE to decode the PDSCH. Figure 6 is a schematic diagram of an example of downlink time-frequency resource 600, where the search space is defined within the CORESET. In Figure 6, time is in the horizontal direction in units of OFDM symbols, and frequency is in the vertical direction in units of CCEs. For example, the vertical dimension of each main solid rectangle represents a CCE 602. Each CCE 602 includes 6 resource element groups (REGs). Each REG can correspond to a physical resource block (PRB), which includes 12 resource elements (REs) in the frequency domain and one OFDM symbol in the time domain. The 6 REGs of each CCE 602 are represented by small dashed rectangles. A time slot 604 in the time domain is shown. Other resource configurations can be used in other instances. Figure 6 illustrates a bandwidth portion (BWP) 606 within carrier bandwidth (CBW) 605. Depending on the pattern, BWP 606 is a set of consecutive entity resource blocks (PRBs) on a given carrier. In Figure 6, the set of consecutive PRBs is represented by a set of consecutive CCEs 602. In the example of Figure 6, BWP 606 corresponds to a set of 64 PRBs, representing 648 subcarriers (i.e., 12 RE / REGs x 6 REG / CCEs x 9 CCEs). Network entities can configure different sets of these CCEs as common CCEs or UE-specific CCEs. In Figure 6, for example, CORESET 608 includes 48 REGs in a set of eight CCEs (where each CCE can be similar to CCE 602). These eight CCEs can be grouped as the first DCI. A CORESET may include one or more search spaces. Search space 618 includes all or part of the CORESET. A CORESET may be associated with a common search space, a UE-specific search space, or a combination of both. In the example of Figure 6, a search space (SS) 618 (indicated by a slash) is indicated for CORESET 608. The search space can include several PDCCH candidates. As mentioned above, the UE can attempt to blindly decode the PDCCH candidates in each search space, even if the network entity has not scheduled a PDCCH in any given search space. Referring to some instances of NR, the following relationships between CORESET, BWP, and search space are established; however, these are exemplary and not limiting, and other relationships between CORESET, BWP, and search space (or their equivalents, such as in other radio technologies) are within the scope of this document. In some instances, for a given UE, a network entity may configure up to three CORESETs in the BWPs (e.g., component carriers (CCs)) of a serving cell, including both public CORESETs and UE-specific CORESETs. Additionally, a network entity may configure up to four BWPs per serving cell, wherein at a given time, one of these BWPs is active. Accordingly, in these instances, the maximum number of CORESETs per serving cell for the UE may be twelve (e.g., 3 CORESETs per BWP x 4 BWPs per serving cell). Resource elements of a CORESET may be mapped to one or more CCEs. One or more CCEs from a CORESET may be aggregated to form resources used by a PDCCH. In some instances, the maximum number of search spaces per BWP may be ten (10). In some instances, multiple search spaces can use the time-frequency resources of a single CORESET. Network entities can send PDCCH to the UE via downlink time-frequency resource 600 (e.g., within a configured search space). In some instances, the network entity can calculate the Cyclic Redundancy Check (CRC) of the DCI payload carried by the PDCCH. The CRC can be scrambled using the UE's identifier. An example of such an identifier could be a Radio Network Temporary Identifier (RNTI), such as a Random Access Radio Network Temporary Identifier (RA-RNTI). During blind decoding of the search space, the UE may attempt to descramble the CRC of the PDCCH candidate using RNTI. For example, the UE may use the same procedure as that used by the network entity to calculate the CRC of the payload for the corresponding DCI and then compare the CRCs. If the CRCs are equal, the DCI is destined for this UE. If the payload is corrupted or the CRC is scrambled using another UE's RNTI, the CRCs will not match, and the UE may ignore the DCI. As mentioned above, the network entity can configure up to three cores per BWP for the UE, where each core can be associated with an Active Transmission Configuration Indicator (TCI) state. As part of the configuration for each core, the network entity can use Radio Resource Control (RRC) configuration messages to configure the RBs of the core in the frequency domain and the number of symbols for the core (e.g., 1, 2, 3, or OFDM symbols). Additionally, a Set of Service (SS) can be associated with a core. Network entities can use RRC configuration messages to configure various parameters as part of the SS set configuration. Examples of these parameters include, but are not limited to: the associated CORESET, the periodicity and offset of the monitoring slot, the monitoring symbols within the slot (e.g., the PDCCH monitoring timing (MO) used to determine the SS set), the SS set type (e.g., public SS (CSS) or UE-specific SS (USS)), the DCI format to be monitored, and the number of PDCCH candidates for a given aggregation level (e.g., the number corresponding to CCEs). In some instances, PDCCH candidates are defined as part of the SS set configuration. For example, PDCCH candidates with a given aggregation level (AL) and a given candidate index can be defined in a given SS set. As mentioned above, the UE can receive DCI via PDCCH candidates. For example, the UE can monitor PDCCH candidates in a specified SS set by blind decoding of the SS set. When one or more PDCCH candidates pass CRC verification (successful decoding), at least one DCI has been successfully decoded. In some instances, network entities can use PDCCH repetition, where each repetition is a PDCCH candidate. For example, two PDCCH candidates can be concatenated to repeat the same DCI. These two PDCCH candidates can have the same aggregation level (e.g., the same number of CCEs), and the DCI payloads transmitted using these two PDCCH candidates can be identical. Therefore, a UE notified of the concatenated PDCCH candidates can perform soft combination to decode the DCI, or the UE can decode the two PDCCH candidates individually. Figure 7 illustrates a first instance 702 and a second instance 704 of linked PDCCH candidates. The first instance 702 includes a first SS set 706 and a second SS set 708. PDCCH candidates within the monitoring time (MO1) of the first SS set 706 are linked to PDCCH candidates within the monitoring time (MO1) of the second SS set 708. For example, a first PDCCH candidate of the first SS set 706 is linked to a first PDCCH candidate of the second SS set 708, a second PDCCH candidate of the first SS set 706 is linked to a second PDCCH candidate of the second SS set 708, and so on. In some cases, in this instance, the first SS set 706 and the second SS set 708 may be referred to as linked SS sets (e.g., linked for PDCCH repetition). The second instance 704 includes a first SS set 710 and a second SS set 712. PDCCH candidates in the first monitoring time (MO1) of the first SS set 710 are linked to PDCCH candidates in the first monitoring time (MO1) of the second SS set 712. Additionally, PDCCH candidates in the second monitoring time (MO2) of the first SS set 710 are linked to PDCCH candidates in the second monitoring time (MO2) of the second SS set 712. In some instances, the following join rules can be used. Two SS collections are joined via RRC configuration, where the MOs of the two joined SS collections are mapped one-to-one, and PDCCH candidates with the same aggregation level and the same candidate index for the two joined SS collections are joined. Here, for each aggregation level, the two joined SS collections can be configured with the same number of candidates. In some instances, a DCI carried by a PUCCH can be scheduled for one or more resources of PDSCH, PUSCH, PUCCH, or some other type of transmission. For example, a DCI can schedule both PDSCH and PUCCH transmissions for an associated HARQ-Ack (e.g., ACK or NACK). As another example, a DCI that is not scheduled for PDSCH or PUSCH can still be scheduled for a PUCCH transmission of a HARQ-Ack associated with that DCI (e.g., so the UE can send an ACK or NACK to acknowledge the DCI). The PUCCH Resource Indicator (PRI) in the DCI (e.g., the DCI for HARQ-ACK on the scheduled PUCCH) can signal the likelihood that a PUCCH resource within a PUCCH resource set will be used by the UE for PUCCH transmission. In some instances, the PRI has 3 bits. Therefore, this PCI can signal up to 8 possibilities for PUCCH resources within a PUCCH resource set. However, in some instances, the first PUCCH resource set (out of four sets) may contain up to 32 PUCCH resources. In this case, the PRI cannot independently determine the PUCCH resource used for HARQ-ACK transmission. To address this issue, the determination of PUCCH resources can be based on the PRI, the number of CCEs in the CORESET where the DCI is received, and the index of the first CCE received by the DCI in the CORESET. For example, Equation 1 can be used to determine the PUCCH resource set ( PUCCH resource index () ), where the decision is based on PRI ( The number of CCEs that receive DCI CORESET (in which) ) and the index of the first CCE received by DCI in CORESET ( ). Equation 1 Ambiguity may arise in the identification of PUCCH resources when a UE receives a DCI in multiple PDCCH candidates linked for repetition. This ambiguity can occur because a network entity may decode the DCI only in the first linked candidate, only in the second linked candidate, or in both linked candidates. In this case, the initial DCI used by the UE to identify the PUCCH resources for HARQ-Ack (e.g., in Equation 1) may differ depending on whether the UE decodes the DCI only in the first linked candidate, only in the second linked candidate, or in both linked candidates. In some instances, when a UE receives a DCI in a PDCCH candidate linked for repetition, the following rule can be used to avoid the aforementioned ambiguity. When a DL DCI is repeatedly transmitted via PDCCH, for a PUCCH resource decision for HARQ-Ack when the corresponding PUCCH resource set has a size greater than 8, the starting CCE index and the number of CCEs in the CORESET of one of the linked PDCCH candidates are applied (e.g., for Equation 1). In some instances, a PDCCH candidate with the lowest SS set ID (e.g., the lowest search space index) can be applied. In this case, the UE can use the number of starting CCEs and CORESETs of the PDCCH candidate associated with the lower SS set ID (SS set 1) in Equation 1 respectively. and . Figure 8 illustrates an instance 800 of linked PDCCH candidates in a scenario where a first CORESET (CORESET 1) 802 is associated with an SS set ID lower than that of a second CORESET (CORESET 2) 804. Here, the PDCCH candidate 806 of the first CORESET 802 is linked to the PDCCH candidate 808 of the second CORESET 804. In this case, the starting CCE of PDCCH candidate 806 and the number of CCEs in the first CORESET 802 can be used respectively for Equation 1. and . In some instances, ambiguity may arise in the identification of PUCCH resources when a UE receives a DCI among multiple PDCCH candidates that are linked for repetition and have different aggregation levels. For example, ambiguity may occur when a UE attempts to decode a search space that includes a first PDCCH candidate with a first aggregation level and a second PDCCH with a second aggregation level. For example, a UE can use polar coding to transmit DCI. In polar coding, the mother code length is defined by the number of coded bits, which depends on the aggregation level (e.g., AL8 with 8 CCEs, AL16 with 16 CCEs, etc.). For AL8 and AL16, the original mother code length is the same (e.g., 512 bits). However, the number of decoded bits for AL8 can be 864 bits (e.g., some decoded bits are repeated and added to the mother code to provide an 864-bit length). Similarly, the number of decoded bits for AL16 can be 1728 bits (e.g., the mother code is repeated 3 times, and some repeated decoded bits are added to provide a 1728-bit length). In the above encoding scheme, the first eight CCEs of the AL16 candidate can be represented as the AL8 candidate to the UE, thus causing ambiguity. It can be observed that this is only a problem when the starting CCE index is the same for two configured PDCCH candidates with AL8 and AL16 (in other cases, the UE will decode the PDCCH candidates separately). In some instances, this ambiguity is only a problem when two PDCCH candidates are associated with the same CORESET (e.g., AL8 and AL16 PDCCH candidates are in the same SS set; or AL8 and AL16 PDCCH candidates are in different SS sets, but these SS sets are associated with the same CORESET and have overlapping monitoring times and the same DCI size). If the PDCCH candidates are in different CORESETs, this ambiguity can be avoided because different scrambling can be used for different CORESETs. In some instances, this ambiguity is a problem only for single-symbol non-interleaved CORESETs. In other cases, the problem can be avoided due to the frequency domain, the first time domain, and the second mapping. In view of the above, when there are two AL8 candidates and two AL16 candidates in two linked SS sets (associated with the corresponding CORESET), and in the SS set with the higher ID (e.g., SS set 2), the AL8 PDCCH candidate and the AL16 PDCCH candidate have the same starting CCE, and one of these two PDCCH candidates is used to decode the DCI, if the CORESET associated with SS set 2 (e.g., CORESET 2) is single-symbol and non-interleaved, the UE may not be able to distinguish whether the DCI comes from the AL8 PDCCH candidate or the AL16 PDCCH candidate. In the rules discussed above in conjunction with Figure 8, the UE uses the starting CCE of the PDCCH candidate and the number of CCEs of the CORESET associated with the lower SS set ID (e.g., SS set 1). However, if the AL8 PDCCH candidate and the AL16 PDCCH candidate do not have the same starting CCE in the SS set (SS set 1) with the lower ID, there may be ambiguity regarding which starting CCE to use. Figure 9 illustrates an instance 900 of PDCCH candidates linked to a scenario where a first CORESET (CORESET 1) 902 is associated with a lower SS set ID than a second CORESET (CORESET 2) 904. Here, the first PDCCH candidate 906 of the first CORESET 902 is linked to the first PDCCH candidate 908 of the second CORESET 904. Additionally, the second PDCCH candidate 910 of the first CORESET 902 is linked to the second PDCCH candidate 912 of the second CORESET 904. Furthermore, the first PDCCH candidates 906 and 908 have lower aggregation levels than the second PDCCH candidates 910 and 912. Moreover, the first PDCCH candidate 908 and the second PDCCH candidate 912 have the same starting CCE, while the first PDCCH candidate 906 and the second PDCCH candidate 910 have different starting CCEs. Therefore, if the rules discussed above in conjunction with Figure 8 are applied here, there is ambiguity about which starting CCE (first PDCCH candidate 906 or second PDCCH candidate 910) will be used in Equation 1. In some cases, this case pertains to procedures for identifying the initial CCE to be used for identifying PUCCH resources. In other cases, these procedures can be used to resolve potential ambiguities in the above discussion when using PDCCH candidate repeats and different aggregation levels. In the first example procedure, the UE can use such an SS set as a reference for PUCCH resource determination purposes: in this SS set, PDCCH candidates with different aggregation levels (e.g., AL8 PDCCH candidate and AL16 PDCCH candidate) have the same starting CCE. In this case, the common starting CCE and the number of CCEs of the CORESET associated with this SS set can be used (e.g., for Equation 1). The use of this procedure is independent of whether the SS set (e.g., in this SS set, AL8 and AL16 PDCCH candidates have the same starting CCE) has a lower ID or a higher ID in the two linked SS sets. In the first example procedure, the following rule can be used to determine the starting CCE. If two PDCCH candidates with different aggregation levels (e.g., AL8 and AL16) have the same starting CCE in a non-interleaved CORESET with one OFDM symbol, and these two PDCCH candidates are in the first SS set linked to the second SS set, and if the linked PDCCH candidates in the second SS set (e.g., AL8 PDCCH candidate and AL16 PDCCH candidate) do not have the same starting CCE, then when the size of the corresponding PUCCH resource set is greater than 8, the first SS set is used as a reference for determining the PUCCH resource for HARQ-Ack. In this scenario, the ambiguity arising in one SS set / CORESET does not depend on a reference defined in another CORESET / SS set. Therefore, network entity (e.g., gNB) scheduling can be more efficient, and the UE's decision regarding PUCCH resources can be more efficient. Furthermore, it is not necessary to notify network entities whether a candidate from SS set 1 or SS set 2 is being decoded. Therefore, potential ambiguity that might arise when only candidates (AL8 or AL16) in SS set 1 are decoded can be avoided in this case. Figure 10 illustrates Example 1000, where a first example procedure can be used to identify the starting CCE to be used in Equation 1. Example 1000 illustrates the PDCCH candidates for the connection of a scenario where a first CORESET (CORESET 1) 1002 is associated with a lower SS set ID than the second CORESET (CORESET 2) 1004. The first PDCCH candidate 1006 of the first CORESET 1002 is linked to the first PDCCH candidate 1008 of the second CORESET 1004. The second PDCCH candidate 1010 of the first CORESET 1002 is linked to the second PDCCH candidate 1012 of the second CORESET 1004. The first PDCCH candidates 1006 and 1008 have a lower aggregation level than the second PDCCH candidates 1010 and 1012. The first PDCCH candidate 1008 and the second PDCCH candidate 1012 have the same starting CCE, while the first PDCCH candidate 1006 and the second PDCCH candidate 1010 have different starting CCEs. In this case, the common starting CCE of the first PDCCH candidate 1008 and the second PDCCH candidate 1012 can be used as the starting CCE of Equation 1 ( Additionally, the number of CCEs in the second CORESET 1004 can be used as the number of CCEs in Equation 1 (). ). In the second, third, and fourth instance procedures, the UE uses the number of CCEs in the CORESET (e.g., CORESET 1) associated with a lower SS set ID and one of the two starting CCEs of the PDCCH candidates with different aggregation levels (e.g., AL8 and AL16) in SS set 1 as a reference for PUCCH resource determination. Figure 11 illustrates Example 1100, where the second, third, and fourth example procedures can be used to identify the starting CCE to be used in Equation 1. Example 1100 illustrates the PDCCH candidates for the connection of a scenario where a first CORESET (CORESET 1) 1102 is associated with a lower SS set ID than the second CORESET (CORESET 2) 1104. The first PDCCH candidate 1106 of the first CORESET 1102 is linked to the first PDCCH candidate 1108 of the second CORESET 1104. The second PDCCH candidate 1110 of the first CORESET 1102 is linked to the second PDCCH candidate 1112 of the second CORESET 1104. The first PDCCH candidates 1106 and 1108 have a lower aggregation level than the second PDCCH candidates 1110 and 1112. The first PDCCH candidate 1108 and the second PDCCH candidate 1112 have the same starting CCE, while the first PDCCH candidate 1106 and the second PDCCH candidate 1110 have different starting CCEs. In the second example procedure, the UE uses the starting CCE associated with the higher aggregation level (e.g., AL16) PDCCH candidate in the first CORESET 1102 (associated with a lower SS set ID) to identify the PUCCH resource (e.g., for Equation 1). Thus, the starting CCE of the second PDCCH candidate 1110 can be used as the starting CCE of Equation 1 ( Additionally, the number of CCEs in the first CORESET 1102 can be used as the number of CCEs in Equation 1 (). In some cases, this procedure can be effectively used in implementations of SS sets that do not use PDCCH repetition or linking, where AL16 is used as a reference for PDSCH rate matching. In the third example procedure, the UE uses the starting CCE associated with the lower aggregation level (e.g., AL8) PDCCH candidate in the first CORESET 1102 (associated with the lower SS set ID) to identify the PUCCH resource (e.g., for Equation 1). Thus, the starting CCE of the first PDCCH candidate 1106 ( ) can be used as the starting CCE in Equation 1. Additionally, the number of CCEs in the first CORESET 1102 can be used as the number of CCEs in Equation 1 ( ). In the fourth example procedure, the UE uses the starting CCE associated with the PDCCH candidate with a higher starting CCE in the first CORESET 1102 (associated with the lower SS set ID) to identify the PUCCH resource (e.g., for Equation 1). In this case, the starting CCE of the second PDCCH candidate 1110 can be used as the starting CCE of Equation 1 ( Additionally, the number of CCEs in the first CORESET 1102 can be used as the number of CCEs in Equation 1 (). ). Figure 12 is a signaling diagram 1200 illustrating an example of signaling related to PUCCH resource identification in a wireless communication system including a network entity (e.g., a base station) 1202 and a user equipment (UE) 1204. In some instances, network entity 1202 may correspond to any of the network entities, base stations, or scheduling entities shown in any of Figures 1, 2, and 18. In some instances, UE 1204 may correspond to any of the UEs shown in any of Figures 1, 2, and 13 or any of the scheduled entities. At 1206 in Figure 12, network entity 1202 transmits (e.g., via RRC message transmission) the CORESET and SS configurations that UE 1204 will use to receive information from network entity 1202. For example, the CORESET configuration for the UE can specify the number of RBs and symbols for each CORESET configured for UE 1204. Additionally, the SS configuration can specify the associated CORESET, PDCCH MO information, PDCCH candidates, etc., for each configured SS set. At 1208, UE 1204 repeatedly monitors the configured SS set to determine whether network entity 1202 has sent any messages to UE 1204. As discussed herein, this may involve blind decoding of PDCCH candidates in the search space configured for UE 1204. At 1210, at some point in time, network entity 1202 schedules a DCI transmission for UE 1204. As discussed herein, in some instances, this DCI may schedule a PDSCH transmission and an associated PUCCH transmission, or the DCI may simply schedule a PUCCH transmission for HARQ-Ack. Therefore, at 1212, network entity 1202 sends a DCI to UE 1204 via one or more PDCCH candidates, wherein the DCI indicates the scheduled PDSCH transmission (if applicable), and / or includes a PRI for identifying the PUCCH resource for HARQ-Ack. As discussed herein, the DCI may be sent using PDCCH repetition. Furthermore, network entity 1202 may send different PDCCH candidates with different aggregation levels on a given CORESET, as discussed herein. Optionally, at 1214, network entity 1202 may send a PDSCH transmission to UE 1204. Subsequently, UE 1204 may attempt to decode the DCI (and optionally, PDSCH) and generate a HARQ-Ack to be sent to network entity 1202 to indicate whether UE 1204 has successfully received the DCI and / or PDSCH transmission. Therefore, UE 1204 will identify the PUCCH resource used to send the HARQ-Ack to network entity 1202. For example, UE 1204 may use a resource partially based on the initial CCE parameter ( Equation 1. In 1216, UE 1204 can identify potential starting CCE ambiguities associated with PDCCH candidates decoded by UE 1204. For example, as discussed herein, if two PDCCH candidates with different aggregation levels are received on the same CORESET and have the same starting CCE, and if these PDCCH candidates are replicated on another CORESET and in that other CORESET the two PDCCH candidates have different starting CCEs, ambiguity may arise regarding which starting CCE will be used to compute the PUCCH resource for HARQ-Ack (e.g., using Equation 1). At 1218, UE 1204 uses one of the example procedures described herein in conjunction with Figures 10 and 11 to identify the initial CCE to be used for calculating the PUCCH resource for HARQ-Ack. For example, UE 1204 can be configured to use the first example procedure, the second example procedure, the third example procedure, or the fourth example procedure. At 1220, UE 1204 identifies the PUCCH resources for HARQ-Ack based on the starting CCE identified at 1216. For example, the UE can use Equation 1 to identify the set of PUCCH resources ( PUCCH resource index () ). At 1222, UE 1204 transmits a PUCCH transmission on the PUCCH resource identified at 1220. For example, UE 1204 can use the resource indicated by the PUCCH resource index to transmit a HARQ-Ack. Figure 13 is a block diagram illustrating an example of a hardware implementation of a UE 1300 employing processing system 1314. For example, UE 1300 may be a device configured to wirelessly communicate with a network entity, as discussed in any one or more of Figures 1-12. In some implementations, UE 1300 may correspond to the UE shown in any of Figures 1, 2, and 12 or any of the scheduled entities. Depending on the various embodiments of this document, the processing system 1314 may be used to implement components, any part of components, or any combination of components. The processing system 1314 may include one or more processors 1304. Examples of processors 1304 include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, individual hardware circuitry, and other suitable hardware configured to perform the various functions described throughout this document. In various instances, the UE 1300 may be configured to perform any one or more of the functions described herein. That is, the processor 1304 used in the UE 1300 may be used to implement any one or more of the programs and routines described herein. In some instances, processor 1304 may be implemented via a baseband or modem chip, and in other embodiments, processor 1304 may include multiple devices that are different from and distinct from the baseband or modem chip (e.g., in cases where they can work together to implement the instances discussed herein). Furthermore, as mentioned above, various hardware arrangements and components other than the baseband modem processor may be used in embodiments, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc. In this example, the processing system 1314 can be implemented using a bus architecture generally represented by bus 1302. Bus 1302 may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system 1314. Bus 1302 communicatively couples various circuits including one or more processors (generally represented by processor 1304), memory 1305, and computer-readable media (generally represented by computer-readable media 1306). Bus 1302 may also connect various other circuits, such as timing sources, peripheral devices, voltage regulators, and power management circuits, which are well known in the art and will therefore not be described further. Bus interface 1308 provides an interface between bus 1302 and transceiver 1310 and between bus 1302 and interface 1330. Transceiver 1310 provides a communication interface or unit for communicating with various other devices via wireless transmission media. In some instances, the UE may include two or more transceivers 1310. Interface 1330 provides a communication interface or unit for communicating with various other devices and equipment (e.g., other devices housed within the same device as the UE or other external devices) via an internal bus or external transmission medium (such as an Ethernet cable). Depending on the nature of the device, interface 1330 may include a user interface (e.g., a keypad, display, speaker, microphone, joystick). Of course, such a user interface is optional and may be omitted in some instances (such as IoT devices). Processor 1304 is responsible for managing bus 1302 and general processing, including executing software stored on computer-readable media 1306. When executed by processor 1304, the software causes processing system 1314 to perform various functions described below for any particular device. Computer-readable media 1306 and memory 1305 can also be used to store data manipulated by processor 1304 while executing the software. For example, memory 1305 may store resource information 1315 (e.g., information related to PUCCH resources) coordinated by processor 1304 and transceiver 1310 for sending and / or receiving messages. One or more processors 1304 in the processing system can execute software. Software should be interpreted broadly as instructions, instruction sets, code, code fragments, program code, program, subprogram, software module, application, software application, software suite, convention, sub-convention, object, executable program, thread of execution, program, function, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or something else. Software may reside on computer-readable media 1306. Computer-readable media 1306 may be non-transitory computer-readable media. As examples, non-transitory computer-readable media includes magnetic storage devices (e.g., hard disks, floppy disks, magnetic stripes), optical discs (e.g., CDs or DVDs), smart cards, flash memory devices (e.g., cards, sticks, or key floppy disk drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electronically erasable PROM (EEPROM), registers, removable disks, and any other suitable media for storing software and / or instructions accessible and readable by a computer. Computer-readable media 1306 may reside in processing system 1314, be external to processing system 1314, or be distributed across multiple entities including processing system 1314. Computer-readable media 1306 may be embodied in a computer program product. As an example, a computer program product may include computer-readable media within packaging material. Those skilled in the art to which this invention pertains will recognize how the functions presented throughout this document are best achieved, depending on the specific application and the overall design constraints imposed on the system. UE 1300 can be configured to perform any one or more of the operations described herein (e.g., as described above in conjunction with Figures 1-12 and below in conjunction with Figures 14-17). In some forms of the content of this document, such as the processor 1304 utilized in UE 1300, circuitry configured for various functions may be included. Processor 1304 may include communication and processing circuitry 1341. Communication and processing circuitry 1341 may be configured to communicate with a network entity, such as a gNB. Communication and processing circuitry 1341 may include one or more hardware components that provide physical structures for performing various programs related to wireless communication (e.g., signal reception and / or signal transmission) as described herein. Communication and processing circuitry 1341 may also include one or more hardware components that provide physical structures for performing various processes related to signal processing (e.g., processing received signals and / or processing signals for transmission) as described herein. In some instances, communication and processing circuitry 1341 may include two or more transmit / receive chains, each configured to handle signals of a different RAT (or RAN) type. Communication and processing circuitry 1341 may also be configured to execute communication and processing software 1351 included on computer-readable media 1306 to implement one or more of the functions described herein. In some implementations where communication involves receiving information, communication and processing circuitry 1341 may obtain information from a component of UE 1300 (e.g., a transceiver 1310 that receives information via radio frequency signal transmission or some other type of signal transmission suitable for an applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, communication and processing circuitry 1341 may output information to another component of processor 1304, memory 1305, or bus interface 1308. In some instances, communication and processing circuitry 1341 may receive one or more of signals, messages, other information, or any combination thereof. In some instances, communication and processing circuitry 1341 may receive information via one or more channels. In some instances, communication and processing circuitry 1341 may include the functionality of a receiving unit. In some instances, communication and processing circuitry 1341 may include the functionality of a decoding unit. In some embodiments where communication involves transmitting (e.g., sending) information, communication and processing circuitry 1341 may acquire information (e.g., from another component of processor 1304, memory 1305, or bus interface 1308), process (e.g., encode) the information, and output the processed information. For example, communication and processing circuitry 1341 may output information to transceiver 1310 (e.g., transceiver 1310 transmits information via radio frequency signal transmission or some other type of signal transmission suitable for an applicable communication medium). In some instances, communication and processing circuitry 1341 may transmit one or more of signals, messages, other information, or any combination thereof. In some instances, communication and processing circuitry 1341 may transmit information via one or more channels. In some instances, communication and processing circuitry 1341 may include the functionality of units for transmission. In some instances, communication and processing circuitry 1341 may include the functionality of units for encoding. Processor 1304 may include PDCCH processing circuitry 1342 configured to perform PDCCH processing-related operations as discussed herein (e.g., one or more of the operations described in conjunction with Figures 4-12). PDCCH processing circuitry 1342 may be configured to execute PDCCH processing software 1352 included on computer-readable media 1306 to implement one or more of the functions described herein. PDCCH processing circuit 1342 may include the functionality of a unit for receiving PDCCH candidates (e.g., as discussed above in conjunction with 1212 of FIG12). For example, PDCCH processing circuit 1342, together with communication and processing circuit 1341 and transceiver 1310, may monitor the search space to look for PDCCH candidates and attempt to decode the DCI carried by the PDCCH candidates. Processor 1304 may include PUCCH processing circuitry 1343 configured to perform PUCCH processing-related operations as discussed herein (e.g., one or more of the operations described in conjunction with Figures 4-12). PUCCH processing circuitry 1343 may be configured to execute PUCCH processing software 1353 included on computer-readable media 1306 to implement one or more of the functions described herein. PUCCH processing circuit 1343 may include the functionality of a unit for identifying PUCCH resources (e.g., as discussed above in conjunction with any of Figures 8-12). For example, PUCCH processing circuit 1343 may identify PUCCH resources used for HARQ-Ack transmission (e.g., using Equation 1). PUCCH processing circuitry 1343 may include the functionality of units for transmitting PUCCH information (e.g., as discussed above in conjunction with 1216-1222 of FIG12). For example, PUCCH processing circuitry 1343 may coordinate with communication and processing circuitry 1341 and transceiver 1310 to transmit HARQ-Ack on identified PUCCH resources. Figure 14 is a flowchart illustrating an example method 1400 for wireless communication according to some forms of the present invention. As described herein, some or all of the shown features may be omitted in certain embodiments within the scope of the present invention, and all instances may be implemented without some of the shown features. In some instances, method 1400 may be performed by the UE 1300 shown in Figure 13. In some instances, method 1400 may be performed by any suitable means or unit for performing the functions or algorithms described below. At block 1402, the user equipment can receive a first entity downlink control channel (PDCCH) candidate of a first control resource set. This first PDCCH candidate is associated with a first aggregation level and configured to schedule an entity uplink control channel (PUCCH) with acknowledgment information. The first aggregation level is different from the second aggregation level associated with a second PDCCH candidate of the first control resource set. For example, the PDCCH processing circuitry 1342 shown and described above in conjunction with FIG13, together with the communication and processing circuitry 1341 and the transceiver 1310, can provide a unit for receiving the first entity downlink control channel (PDCCH) candidate of the first control resource set. At block 1404, the user equipment can transmit a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on a first CCE index corresponding to the start control channel element (CCE) of the first PDCCH candidate and the second PDCCH candidate. For example, the PUCCH processing circuit 1343 shown and described above in conjunction with FIG13, together with the communication and processing circuit 1341 and the transceiver 1310, can provide a unit for transmitting a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on the first CCE index corresponding to the start control channel element (CCE) of the first PDCCH candidate and the second PDCCH candidate. In some instances, the user equipment may identify the PUCCH resource at least in part based on the first CCE index in response to determining that the first PDCCH candidate and the second PDCCH candidate begin at the same location (i.e., the same location) within the first control resource set. In some instances, the user equipment may identify the PUCCH resource, at least in part, based on the first CCE index, in response to the determination that the first control resource set is a non-interleaved control resource set with a single orthogonal frequency division multiplexing (OFDM) symbol. In some instances, a user equipment may respond to a decision to identify a PUCCH resource at least in part based on a first CCE index: a first PDCCH candidate and a second PDCCH candidate are in a first search space set linked to a second search space set for PDCCH repetition, wherein the first search space set is assigned a first search space set index that is higher than a second search space set index assigned to the second search space set. In some instances, a user device may identify a PUCCH resource based at least in part on a first CCE index in response to a determination that the set of PUCCH resources including the PUCCH resource includes more than eight PUCCH resources. In some instances, the second control resource set carries a repeated third PDCCH candidate as a first PDCCH candidate. In some instances, the second control resource set carries a repeated fourth PDCCH candidate as a second PDCCH candidate. In some instances, the user equipment can identify the PUCCH resource at least in part based on the first CCE index in response to the difference between the first starting CCE for determining the third PDCCH candidate and the second starting CCE for determining the fourth PDCCH candidate. In some instances, a user equipment may respond to decisions to identify a PUCCH resource at least in part based on a first CCE index, including: the first PDCCH candidate and the second PDCCH candidate begin at the same location within a first control resource set, which is a non-interleaved control resource set with a single orthogonal frequency division multiplexing (OFDM) symbol; the first PDCCH candidate and the second PDCCH candidate are in a first search space set linked to a second search space set for PDCCH repetition (where the first search space set is assigned a first search space set index, which is higher than a second search space set index assigned to the second search space set); the PUCCH resource set including the PUCCH resource includes more than eight PUCCH resources; and the first starting CCE of a third PDCCH candidate, which is a copy of the first PDCCH candidate, is different from the second starting CCE of a fourth PDCCH candidate, which is a copy of the second PDCCH candidate. In some instances, the first aggregation level corresponds to eight CCEs. In some instances, the second aggregation level corresponds to sixteen CCEs. In some instances, the first PDCCH candidate includes a PUCCH resource indicator. In some instances, the first control resource set includes a defined number of control channel elements. In some instances, the user equipment can identify the PUCCH resource based at least in part on the first CCE index, the PUCCH resource indicator, and the defined number of control channel elements. In some instances, the first PDCCH candidate includes the first downlink control information (DCI) scheduled for transmission on the first entity downlink shared channel (PDSCH). In some instances, the second PDCCH candidate includes the second DCI scheduled for transmission on the second PDSCH. Figure 15 is a flowchart illustrating an example method 1500 for wireless communication according to some forms of the present invention. As described herein, some or all of the shown features may be omitted in certain embodiments within the scope of the present invention, and all instances may be implemented without some of the shown features. In some instances, method 1500 may be performed by the UE 1300 shown in Figure 13. In some instances, method 1500 may be performed by any suitable means or unit for performing the functions or algorithms described below. At block 1502, the user equipment can receive a first entity downlink control channel (PDCCH) candidate of a first control resource set. The first PDCCH candidate schedules an entity uplink control channel (PUCCH) with acknowledgment information (e.g., HARQ-Ack information) and begins at the same control channel element (CCE) as the second PDCCH candidate within the first control resource set. The first PDCCH candidate repeats in a third PDCCH candidate of a second control resource set, and the second PDCCH candidate repeats in a fourth PDCCH candidate of the second control resource set. The third PDCCH candidate is associated with a first aggregation level, and the fourth PDCCH candidate is associated with a second aggregation level higher than the first aggregation level. For example, the PDCCH processing circuitry 1342 shown and described above in conjunction with FIG13, together with the communication and processing circuitry 1341 and the transceiver 1310, can provide a unit for receiving the first entity downlink control channel (PDCCH) candidate of the first control resource set. At block 1504, the user equipment can transmit a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on a first CCE index corresponding to the starting CCE of a fourth PDCCH candidate associated with a second aggregation level higher than the first aggregation level. For example, the PUCCH processing circuit 1343 shown and described above in conjunction with FIG13, together with the communication and processing circuit 1341 and the transceiver 1310, can provide a unit for transmitting a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on a first CCE index corresponding to the starting CCE of a fourth PDCCH candidate associated with a second aggregation level higher than the first aggregation level. In some instances, the user equipment may identify the PUCCH resource at least in part based on the first CCE index in response to determining that the first PDCCH candidate and the second PDCCH candidate begin at the same location within the first control resource set. In some instances, the user equipment may identify the PUCCH resource, at least in part, based on the first CCE index, in response to the determination that the first control resource set is a non-interleaved control resource set with a single orthogonal frequency division multiplexing (OFDM) symbol. In some instances, a user equipment may respond to a decision to identify a PUCCH resource at least in part based on a first CCE index: a first PDCCH candidate and a second PDCCH candidate are in a first search space set linked to a second search space set for PDCCH repetition, wherein the first search space set is assigned a first search space set index that is higher than a second search space set index assigned to the second search space set. In some instances, a user device may identify a PUCCH resource based at least in part on a first CCE index in response to a determination that the set of PUCCH resources including the PUCCH resource includes more than eight PUCCH resources. In some instances, the second control resource set carries a repeated third PDCCH candidate as a first PDCCH candidate. In some instances, the second control resource set carries a repeated fourth PDCCH candidate as a second PDCCH candidate. In some instances, the user equipment can identify the PUCCH resource at least in part based on the first CCE index in response to the determination that the starting CCE of the third PDCCH candidate is different from the starting CCE of the fourth PDCCH candidate. In some instances, a user equipment may respond to decisions to identify a PUCCH resource at least in part based on a first CCE index, including: the first PDCCH candidate and the second PDCCH candidate begin at the same location within a first control resource set, which is a non-interleaved control resource set with a single orthogonal frequency division multiplexing (OFDM) symbol; the first PDCCH candidate and the second PDCCH candidate are in a first search space set linked to a second search space set for PDCCH repetition (where the first search space set is assigned a first search space set index, which is higher than a second search space set index assigned to the second search space set); the PUCCH resource set including the PUCCH resource includes more than eight PUCCH resources; and the starting CCE of the third PDCCH candidate is different from the starting CCE of the fourth PDCCH candidate. In some instances, the first aggregation level corresponds to eight CCEs. In some instances, the second aggregation level corresponds to sixteen CCEs. In some instances, the first PDCCH candidate includes a PUCCH resource indicator. In some instances, the first control resource set includes a defined number of control channel elements. In some instances, the user equipment can identify the PUCCH resource based at least in part on the first CCE index, the PUCCH resource indicator, and the defined number of control channel elements. In some instances, the first PDCCH candidate includes the first downlink control information (DCI) scheduled for transmission on the first entity downlink shared channel (PDSCH). In some instances, the second PDCCH candidate includes the second DCI scheduled for transmission on the second PDSCH. Figure 16 is a flowchart illustrating an example method 1600 for wireless communication according to some forms of the present invention. As described herein, some or all of the shown features may be omitted in certain embodiments within the scope of the present invention, and all instances may be implemented without some of the shown features. In some instances, method 1600 may be performed by the UE 1300 shown in Figure 13. In some instances, method 1600 may be performed by any suitable means or unit for performing the functions or algorithms described below. At block 1602, the user equipment can receive a first entity downlink control channel (PDCCH) candidate of a first control resource set. The first PDCCH candidate schedules an entity uplink control channel (PUCCH) with acknowledgment information (e.g., HARQ-Ack information) and begins at the same control channel element (CCE) as the second PDCCH candidate within the first control resource set. The first PDCCH candidate repeats in a third PDCCH candidate of a second control resource set, and the second PDCCH candidate repeats in a fourth PDCCH candidate of the second control resource set. The third PDCCH candidate is associated with a first aggregation level, and the fourth PDCCH candidate is associated with a second aggregation level higher than the first aggregation level. For example, the PDCCH processing circuitry 1342 shown and described above in conjunction with FIG13, together with the communication and processing circuitry 1341 and the transceiver 1310, can provide a unit for receiving the first entity downlink control channel (PDCCH) candidate of the first control resource set. At block 1604, the user equipment can transmit a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on a first CCE index corresponding to the starting CCE of a third PDCCH candidate associated with a first aggregation level and below the second aggregation level. For example, the PUCCH processing circuit 1343 shown and described above in conjunction with FIG13, together with the communication and processing circuit 1341 and the transceiver 1310, can provide a unit for transmitting a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on a first CCE index corresponding to the starting CCE of a third PDCCH candidate associated with a first aggregation level and below the second aggregation level. In some instances, the user equipment may identify the PUCCH resource at least in part based on the first CCE index in response to determining that the first PDCCH candidate and the second PDCCH candidate begin at the same location within the first control resource set. In some instances, the user equipment may identify the PUCCH resource, at least in part, based on the first CCE index, in response to the determination that the first control resource set is a non-interleaved control resource set with a single orthogonal frequency division multiplexing (OFDM) symbol. In some instances, a user equipment may respond to a decision to identify a PUCCH resource at least in part based on a first CCE index: a first PDCCH candidate and a second PDCCH candidate are in a first search space set linked to a second search space set for PDCCH repetition, wherein the first search space set is assigned a first search space set index that is higher than a second search space set index assigned to the second search space set. In some instances, a user device may identify a PUCCH resource based at least in part on a first CCE index in response to a determination that the set of PUCCH resources including the PUCCH resource includes more than eight PUCCH resources. In some instances, a user equipment may identify a PUCCH resource, at least in part, based on the first CCE index, in response to the fact that the starting CCE of the third PDCCH candidate is different from that of the fourth PDCCH candidate. In some instances, a user equipment may identify a PUCCH resource at least in part based on a first CCE index by responding to decisions such as: the first PDCCH candidate and the second PDCCH candidate begin at the same location within a first control resource set, which is a non-interleaved control resource set with a single orthogonal frequency division multiplexing (OFDM) symbol; the first PDCCH candidate and the second PDCCH candidate are in a first search space set linked to a second search space set for PDCCH repetition (where the first search space set is assigned a first search space set index, which is higher than a second search space set index assigned to the second search space set); the PUCCH resource set including the PUCCH resource includes more than eight PUCCH resources; and the starting CCE of the third PDCCH candidate is different from the starting CCE of the fourth PDCCH candidate. In some instances, the first aggregation level corresponds to eight CCEs. In some instances, the second aggregation level corresponds to sixteen CCEs. In some instances, the first PDCCH candidate includes a PUCCH resource indicator. In some instances, the first control resource set includes a defined number of control channel elements. In some instances, the user equipment can identify the PUCCH resource based at least in part on the first CCE index, the PUCCH resource indicator, and the defined number of control channel elements. In some instances, the first PDCCH candidate includes the first downlink control information (DCI) scheduled for transmission on the first entity downlink shared channel (PDSCH). In some instances, the second PDCCH candidate includes the second DCI scheduled for transmission on the second PDSCH. Figure 17 is a flowchart illustrating an example method 1700 for wireless communication according to some forms of the present invention. As described herein, some or all of the shown features may be omitted in certain embodiments within the scope of the present invention, and all instances may be implemented without some of the shown features. In some instances, method 1700 may be performed by the UE 1300 shown in Figure 13. In some instances, method 1700 may be performed by any suitable means or unit for performing the functions or algorithms described below. At block 1702, the user equipment can receive a first entity downlink control channel (PDCCH) candidate of a first control resource set. The first PDCCH candidate schedules an entity uplink control channel (PUCCH) with acknowledgment information and begins at the same control channel element (CCE) as the second PDCCH candidate within the first control resource set. The first PDCCH candidate repeats in a third PDCCH candidate of a second control resource set, and the second PDCCH candidate repeats in a fourth PDCCH candidate of the second control resource set. Within the second control resource set, the third PDCCH candidate is associated with a first starting CCE, and the fourth PDCCH candidate is associated with a second starting CCE higher than the first starting CCE. For example, the PDCCH processing circuitry 1342 shown and described above in conjunction with FIG13, together with the communication and processing circuitry 1341 and the transceiver 1310, can provide a unit for receiving the first entity downlink control channel (PDCCH) candidate of the first control resource set. At block 1704, the user equipment can transmit a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on the index of the first CCE corresponding to the second starting CCE. For example, the PUCCH processing circuit 1343 shown and described above in conjunction with FIG13, together with the communication and processing circuit 1341 and the transceiver 1310, can provide a unit for transmitting a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on the index of the first CCE corresponding to the second starting CCE. In some instances, the user equipment may respond by determining that the first PDCCH candidate and the second PDCCH candidate begin at the same location within the first control resource set, at least in part based on the first CCE index to identify the PUCCH resource. In some instances, the user equipment may identify the PUCCH resource, at least in part, based on the first CCE index, in response to the determination that the first control resource set is a non-interleaved control resource set with a single orthogonal frequency division multiplexing (OFDM) symbol. In some instances, a user equipment may respond to a decision to identify a PUCCH resource at least in part based on a first CCE index: a first PDCCH candidate and a second PDCCH candidate are in a first search space set linked to a second search space set for PDCCH repetition, wherein the first search space set is assigned a first search space set index that is higher than a second search space set index assigned to the second search space set. In some instances, a user device may identify a PUCCH resource based at least in part on a first CCE index in response to a determination that the set of PUCCH resources including the PUCCH resource includes more than eight PUCCH resources. In some instances, a user device may identify a PUCCH resource, at least in part, based on the first CCE index, in response to a determination that the first starting CCE is different from the second starting CCE. In some instances, a user equipment may respond to decisions to identify a PUCCH resource at least in part based on a first CCE index, including: the first PDCCH candidate and the second PDCCH candidate begin at the same location within a first control resource set, which is a non-interleaved control resource set with a single orthogonal frequency division multiplexing (OFDM) symbol; the first PDCCH candidate and the second PDCCH candidate are in a first search space set linked to a second search space set for PDCCH repetition (where the first search space set is assigned a first search space set index, which is higher than a second search space set index assigned to the second search space set); the PUCCH resource set including the PUCCH resource includes more than eight PUCCH resources; and the first starting CCE is different from the second starting CCE. In some instances, the third PDCCH candidate is associated with the first aggregation level. In some instances, the fourth PDCCH candidate is associated with a second aggregation level that is different from the first aggregation level. In some instances, the first PDCCH candidate includes a PUCCH resource indicator. In some instances, the first control resource set includes a defined number of control channel elements. In some instances, the user equipment can identify the PUCCH resource based at least in part on the first CCE index, the PUCCH resource indicator, and the defined number of control channel elements. In some instances, the first PDCCH candidate includes the first downlink control information (DCI) scheduled for transmission on the first entity downlink shared channel (PDSCH). In some instances, the second PDCCH candidate includes the second DCI scheduled for transmission on the second PDSCH. In one configuration, UE 1300 includes: a unit for receiving a first entity downlink control channel (PDCCH) candidate of a first control resource set, the first PDCCH candidate being associated with a first aggregation level and configured to schedule an entity uplink control channel (PUCCH) with acknowledgment information, the first aggregation level being different from a second aggregation level associated with a second PDCCH candidate of the first control resource set; and a unit for transmitting a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on a first CCE index corresponding to the start control channel element (CCE) of the first PDCCH candidate and the second PDCCH candidate. In one configuration, UE 1300 includes: receiving a first entity downlink control channel (PDCCH) candidate in a first control resource set, the first PDCCH candidate scheduling an entity uplink control channel (PUCCH) with acknowledgment information (e.g., HARQ-Ack information) and starting at the same control channel element (CCE) as a second PDCCH candidate in the first control resource set, the first PDCCH candidate repeating in a third PDCCH candidate in a second control resource set, the second PDCCH candidate repeating in a fourth PDCCH candidate in a second control resource set, the third PDCCH candidate being associated with a first aggregation level, and the fourth PDCCH candidate being associated with a second aggregation level higher than the first aggregation level; and transmitting a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on a first CCE index corresponding to the starting CCE of the fourth PDCCH candidate associated with the second aggregation level higher than the first aggregation level. In one configuration, UE 1300 includes: a unit for receiving a first entity downlink control channel (PDCCH) candidate of a first control resource set, the first PDCCH candidate scheduling an entity uplink control channel (PUCCH) with acknowledgment information (e.g., HARQ-Ack information) and starting at the same control channel element (CCE) as a second PDCCH candidate in the first control resource set, the first PDCCH candidate repeating in a third PDCCH candidate of a second control resource set, the second PDCCH candidate repeating in a fourth PDCCH candidate of a second control resource set, the third PDCCH candidate associated with a first aggregation level, and the fourth PDCCH candidate associated with a second aggregation level higher than the first aggregation level; and a unit for transmitting a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on a first CCE index corresponding to the starting CCE of the third PDCCH candidate associated with the first aggregation level and lower than the second aggregation level.In one configuration, UE 1300 includes: a unit for receiving a first entity downlink control channel (PDCCH) candidate in a first control resource set, the first PDCCH candidate scheduling an entity uplink control channel (PUCCH) with acknowledgment information and starting at the same control channel element (CCE) as the second PDCCH candidate in the first control resource set, the first PDCCH candidate repeating in a third PDCCH candidate in a second control resource set, the second PDCCH candidate repeating in a fourth PDCCH candidate in the second control resource set, the third PDCCH candidate associated with a first starting CCE in the second control resource set, and the fourth PDCCH candidate associated with a second starting CCE above the first starting CCE; and a unit for transmitting a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on a first CCE index corresponding to the second starting CCE. Alternatively, the aforementioned unit may be the processor 1304 shown in FIG. 13, configured to perform the functions described by the aforementioned unit (e.g., as discussed above). In another instance, the aforementioned unit may be a circuit or any device configured to perform the functions described by the aforementioned unit. Of course, in the above examples, the circuitry included in processor 1304 is provided merely as an example, and other units for performing the described functions may be included in various forms of the content of this document, including but not limited to instructions stored in computer-readable media 1306, or any other suitable means or units described in any one or more of Figures 1, 2, 12 and 13 and utilizing, for example, the methods and / or algorithms described herein with respect to Figures 14-17. The methods shown in Figures 14-17 may include additional patterns, such as any single pattern or any combination of patterns, as described below and / or any other procedures described in conjunction with other parts of this document. The deployment of communication systems such as 5G New Radio (NR) systems can be arranged with various components or parts in a variety of ways. In a 5G NR system or network, network nodes, network entities, network mobility components, radio access network (RAN) nodes, core network nodes, network elements, or network equipment (such as base stations (BS) or one or more units (or components) performing base station functions) can be implemented in aggregated or deaggregated architectures. For example, BSs (such as node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as aggregated base stations (also known as standalone BS or monolithic BS) or deaggregated base stations. Aggregation base stations can be configured to utilize radio protocol stacks physically or logically integrated within a single RAN node. Deaggregation base stations can be configured to utilize protocol stacks physically or logically distributed between two or more units (e.g., one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some cases, the CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. DUs can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU). Base station type operation or network design can consider the aggregation characteristics of base station functions. For example, de-aggregated base stations can be utilized in Integrated Access Backload (IAB) networks, Open Radio Access Networks (O-RAN (e.g., network configurations sponsored by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). De-aggregation can include distributing functions across two or more units at various physical locations, as well as virtually distributing functions to at least one unit, which enables flexibility in network design. Various units of a de-aggregated base station or de-aggregated RAN architecture can be configured to communicate with at least one other unit via wired or wireless means. Figure 18 illustrates a schematic diagram of the example deconverging base station 1800 architecture. The deconverging base station 1800 architecture may include one or more central units (CUs) 1810, which may communicate directly with the core network 1820 via a backhaul link, or indirectly with the core network 1820 via one or more deconverging base station units (e.g., a near-real-time (near-RT) RAN Intelligent Controller (RIC) 1825 via an E2 link, or a non-real-time (non-RT) RIC 1815 associated with a Service Management and Orchestration (SMO) framework 1805, or both). CUs 1810 may communicate with one or more distributed units (DUs) 1830 via corresponding midhaul links (e.g., F1 interfaces). DUs 1830 may communicate with one or more radio units (RUs) 1840 via corresponding fronthaul links. RUs 1840 may communicate with corresponding UEs 1850 via one or more radio frequency (RF) access links. In some implementations, UE 1850 can be served by multiple RU 1840s simultaneously. Each of the units (i.e., CU 1810, DU 1830, RU 1840, and near-RT RIC 1825, non-RT RIC 1815, and SMO frame 1805) may include, or be coupled to, one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit, or the associated processor or controller providing instructions to the unit's communication interface, may be configured to communicate with one or more other units via transmission media. For example, a unit may include a wired interface configured to receive or transmit signals via a wired transmission media to one or more other units. Additionally, a unit may include a wireless interface, which may include a receiver, transmitter, or transceiver (e.g., a radio frequency (RF) transceiver) configured to receive or transmit signals via a wireless transmission media to one or more other units, or both. In some configurations, the CU 1810 can accommodate one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), etc. Each control function can be implemented with an interface configured to signal communicate with other control functions accommodated by the CU 1810. The CU 1810 can be configured to handle user plane functions (i.e., Central Unit-User Plane (CU-UP)), control plane functions (i.e., Central Unit-Control Plane (CU-CP)), or combinations thereof. In some implementations, the CU 1810 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface (e.g., an E1 interface). The CU 1810 can be implemented to communicate with the Distributed Unit (DU) 1830 as needed for network control and signal transmission. DU 1830 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU 1840s. In some configurations, DU 1830 may, at least in part, depend on the functional partitioning (e.g., the functional partitioning defined by the 3rd Generation Partnership Project (3GPP)) to accommodate one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and one or more high-physical (PHY) layers (e.g., modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.). In some configurations, DU 1830 may also accommodate one or more low-PHY layers. Each layer (or module) may be implemented with an interface configured to signal communicate with other layers (and modules) accommodated by DU 1830 or with the control functions accommodated by CU 1810. Lower-level functions can be implemented by one or more RU 1840s. In some deployments, an RU 1840 controlled by a DU 1830 may correspond to a logical node that accommodates RF processing functions, or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both, at least partially based on functional partitioning (such as lower-level functional partitioning). In such architectures, one (or more) RU 1840s can be implemented to handle over-the-air (OTA) communications with one or more UE 1850s. In some implementations, the real-time and non-real-time patterns of communication between the control plane and user plane of one (or more) RU 1840s can be controlled by the corresponding DU 1830. In some scenarios, this configuration allows one (or more) DU 1830s and CU 1810s to be implemented in a cloud-based RAN architecture (e.g., vRAN architecture). The SMO framework 1805 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 1805 can be configured to support the deployment of dedicated entity resources for RAN coverage requirements, which can be managed via an operation and maintenance interface (e.g., the O1 interface). For virtualized network elements, the SMO framework 1805 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) 1890) to perform network element lifecycle management (such as generating entities for virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, CU 1810, DU 1830, RU 1840, and near-RT RIC 1825. In some implementations, the SMO framework 1805 can communicate with 4G RAN hardware models (such as the Open eNB (O-eNB) 1811) via the O1 interface. Additionally, in some implementations, the SMO framework 1805 can communicate directly with one or more RUs 1840 via the O1 interface. The SMO framework 1805 may also include a non-RT RIC 1815 configured to support the functionality of the SMO framework 1805. The non-RT RIC 1815 can be configured to include logical functions that enable non-real-time control and optimization of RAN components and resources, including AI / ML workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 1825. The non-RT RIC 1815 can be coupled to or communicate with the near-RT RIC 1825 (e.g., via the A1 interface). The near-RT RIC 1825 can be configured to include logical functions that enable near-real-time control and optimization of RAN components and resources via data collection and actions on interfaces (such as via the E2 interface) connecting one or more CU 1810s, one or more DU 1830s, or both, and O-eNBs to the near-RT RIC 1825. In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 1825, the non-RT RIC 1815 can receive parameters or external rich information from an external server. This information can be utilized by the near-RT RIC 1825 and can be received from non-network data sources or from network functions at the SMO framework 1805 or the non-RT RIC 1815. In some instances, the non-RT RIC 1815 or near-RT RIC 1825 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 1815 can monitor long-term trends and patterns in performance and employ AI / MI models to perform corrective actions via the SMO framework 1805 (such as reconfiguration via O1) or via the establishment of RAN management policies (such as A1 policies). The following provides an overview of several aspects of the case. Sample 1: A method for wireless communication at a user equipment, the method comprising: receiving a first entity downlink control channel (PDCCH) candidate of a first control resource set, the first PDCCH candidate being associated with a first aggregation level and configured to schedule an entity uplink control channel (PUCCH) with acknowledgment information, the first aggregation level being different from a second aggregation level associated with a second PDCCH candidate of the first control resource set; and transmitting a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on an index of a first control channel element (CCE) corresponding to the starting CCE of the first PDCCH candidate and the second PDCCH candidate. State 2: According to the method of State 1, it also includes: in response to determining the first PDCCH candidate and the second PDCCH candidate at the same location in the first control resource set, identifying the PUCCH resource at least in part based on the first CCE index. State 3: According to the method of State 1 or 2, it also includes: in response to determining that the first control resource set is a non-interleaved control resource set with a single orthogonal frequency division multiplexing (OFDM) symbol, identifying the PUCCH resource at least in part based on the first CCE index. State 4: The method according to any one of states 1 to 3 also includes: in response to determining the first PDCCH candidate and the second PDCCH candidate in the first search space set linked to the second search space set for PDCCH repetition, identifying the PUCCH resource at least in part based on the first CCE index. State 5: The method according to any one of States 1 to 4 also includes: in response to determining that the set of PUCCH resources including PUCCH resources includes more than eight PUCCH resources, identifying the PUCCH resources at least in part based on the first CCE index. State 6: The method according to any one of States 1 to 5, wherein: the second control resource set carries a repeated third PDCCH candidate as a first PDCCH candidate; the second control resource set carries a repeated fourth PDCCH candidate as a second PDCCH candidate; and the method also includes: in response to the difference between the first starting CCE for determining the third PDCCH candidate and the second starting CCE for determining the fourth PDCCH candidate, identifying the PUCCH resource at least in part based on the first CCE index. State 7: According to the method of State 1, it also includes: in response to determining that the first PDCCH candidate and the second PDCCH candidate start at the same position in the first control resource set, identifying the PUCCH resource at least in part based on the first CCE index, the first control resource set being a non-interleaved control resource set having a single orthogonal frequency division multiplexing (OFDM) symbol, the first PDCCH candidate and the second PDCCH candidate being in the first search space set linked to the second search space set for PDCCH repetition; the PUCCH resource set including the PUCCH resource includes more than eight PUCCH resources, and the first starting CCE of the repetition of the third PDCCH candidate as the first PDCCH candidate is different from the second starting CCE of the repetition of the fourth PDCCH candidate as the second PDCCH candidate. State 8: The method according to any one of states 1 to 7, wherein: the first polymerization level corresponds to eight CCEs; and the second polymerization level corresponds to sixteen CCEs. State 9: The method according to any one of States 1 to 8, wherein: the first PDCCH candidate includes a PUCCH resource indicator; the first control resource set includes a defined number of control channel elements; and the method also includes: identifying a PUCCH resource based at least in part on a first CCE index, the PUCCH resource indicator and the defined number of control channel elements. State 10: The method according to any one of states 1 to 9, wherein: the first PDCCH candidate includes first downlink control information (DCI) transmitted in the scheduled first entity downlink shared channel (PDSCH); and the second PDCCH candidate includes second DCI transmitted in the scheduled second PDSCH. State 11: A user equipment comprising: a transceiver configured to communicate with a radio access network, memory, and a processor coupled to the transceiver and memory, wherein the processor and memory are configured to execute any one of states 1 to 10. State 12: An apparatus configured for wireless communication, comprising at least one unit for performing any one of states 1 to 10. Sample 13: A non-transitory computer-readable medium storing computer-executable code, including code for causing a device to execute any one of Samples 1 to 10. Sample 21: A method for wireless communication at a user equipment, the method comprising: receiving a first entity downlink control channel (PDCCH) candidate of a first control resource set, the first PDCCH candidate scheduling an entity uplink control channel (PUCCH) with acknowledgment information (e.g., HARQ-Ack information) and starting at the same control channel element (CCE) as a second PDCCH candidate in the first control resource set, the first PDCCH candidate repeating in a third PDCCH candidate of a second control resource set, the second PDCCH candidate repeating in a fourth PDCCH candidate of the second control resource set, the third PDCCH candidate being associated with a first aggregation level, and the fourth PDCCH candidate being associated with a second aggregation level higher than the first aggregation level; and transmitting a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on a first CCE index corresponding to the starting CCE of the fourth PDCCH candidate associated with the second aggregation level higher than the first aggregation level. State 22: The method according to State 21 also includes: in response to determining that the first PDCCH candidate and the second PDCCH candidate start at the same position in the first control resource set, to identify the PUCCH resource at least in part based on the first CCE index. Sample 23: The method according to any one of Samples 21 to 22 also includes: in response to determining that the first control resource set is a non-interleaved control resource set with a single orthogonal frequency division multiplexing (OFDM) symbol, identifying the PUCCH resource at least in part based on the first CCE index. Version 24: The method according to any one of versions 21 to 23 also includes: in response to determining to identify PUCCH resources at least in part based on a first CCE index: a first PDCCH candidate and a second PDCCH candidate are in a first search space set linked to a second search space set for PDCCH repetition, wherein the first search space set is assigned a first search space set index, which is higher than a second search space set index assigned to the second search space set. Sample 25: The method according to any one of Samples 21 to 24 also includes: in response to determining that the set of PUCCH resources including PUCCH resources comprises more than eight PUCCH resources, identifying the PUCCH resources at least in part based on the first CCE index. Version 26: The method according to any one of versions 21 to 25 also includes: in response to the fact that the starting CCE of the third PDCCH candidate is different from the starting CCE of the fourth PDCCH candidate, identifying the PUCCH resource based at least in part on the first CCE index. Version 27: The method according to Version 22 also includes: in response to determining that the first PDCCH candidate and the second PDCCH candidate begin at the same position within a first control resource set, identifying the PUCCH resource at least in part based on a first CCE index, the first control resource set being a non-interleaved control resource set having a single orthogonal frequency division multiplexing (OFDM) symbol, the first PDCCH candidate and the second PDCCH candidate being in a first search space set linked to a second search space set for PDCCH repetition, wherein the first search space set is assigned a first search space set index, which is higher than a second search space set index assigned to the second search space set, the PUCCH resource set including the PUCCH resource includes more than eight PUCCH resources, and the starting CCE of the third PDCCH candidate is different from the starting CCE of the fourth PDCCH candidate. State 28: The method according to any one of states 21 to 27, wherein: the first polymerization level corresponds to eight CCEs; and the second polymerization level corresponds to sixteen CCEs. Sample 29: The method according to any one of Samples 21 to 28, wherein: the first PDCCH candidate includes a PUCCH resource indicator; the second control resource set includes a defined number of control channel elements; and the method also includes: identifying a PUCCH resource based at least in part on the first CCE index, the PUCCH resource indicator and the defined number of control channel elements. State 30: The method according to any one of states 21 to 29, wherein: the first PDCCH candidate includes first downlink control information (DCI) scheduled for transmission of the first entity downlink shared channel (PDSCH); and the second PDCCH candidate includes second DCI scheduled for transmission of the second PDSCH. State 31: A user equipment comprising: a transceiver configured to communicate with a radio access network, memory, and a processor coupled to the transceiver and memory, wherein the processor and memory are configured to execute any one of states 21 to 30. State 32: An apparatus configured for wireless communication, comprising at least one unit for performing any one of states 21 to 30. Format 33: A non-transitory computer-readable medium storing computer-executable code, including code for causing a device to execute any one of formats 21 to 30. Sample 41: A method for wireless communication at a user equipment, the method comprising: receiving a first entity downlink control channel (PDCCH) candidate of a first control resource set, the first PDCCH candidate scheduling an entity uplink control channel (PUCCH) with acknowledgment information (e.g., HARQ-Ack information) and starting at the same control channel element (CCE) as a second PDCCH candidate in the first control resource set, the first PDCCH candidate repeating in a third PDCCH candidate of a second control resource set, the second PDCCH candidate repeating in a fourth PDCCH candidate of the second control resource set, the third PDCCH candidate being associated with a first aggregation level, and the fourth PDCCH candidate being associated with a second aggregation level higher than the first aggregation level; and transmitting a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on a first CCE index corresponding to the starting CCE of the third PDCCH candidate associated with the first aggregation level lower than the second aggregation level. Version 42: The method according to version 41 also includes: in response to determining the first PDCCH candidate and the second PDCCH candidate at the same location within the first control resource set, identifying the PUCCH resource at least in part based on the first CCE index. State 43: The method according to any one of states 1 to 42 also includes: in response to determining that the first control resource set is a non-interleaved control resource set with a single orthogonal frequency division multiplexing (OFDM) symbol, identifying the PUCCH resource at least in part based on the first CCE index. Version 44: The method according to any one of versions 1 to 43 also includes: in response to determining to identify PUCCH resources at least in part based on a first CCE index: a first PDCCH candidate and a second PDCCH candidate are in a first search space set linked to a second search space set for PDCCH repetition, wherein the first search space set is assigned a first search space set index, which is higher than a second search space set index assigned to the second search space set. Sample 45: The method according to any one of Samples 1 to 44 also includes: in response to determining that the set of PUCCH resources including PUCCH resources comprises more than eight PUCCH resources, identifying the PUCCH resources at least in part based on the first CCE index. Version 46: The method according to any one of versions 1 to 45 also includes: in response to the difference between the starting CCE of the third PDCCH candidate and the starting CCE of the fourth PDCCH candidate, identifying the PUCCH resource at least in part based on the first CCE index. Version 47: The method according to Version 41 also includes: in response to determining that the first PDCCH candidate and the second PDCCH candidate begin at the same position within a first control resource set, identifying the PUCCH resource at least in part based on a first CCE index, the first control resource set being a non-interleaved control resource set having a single orthogonal frequency division multiplexing (OFDM) symbol, the first PDCCH candidate and the second PDCCH candidate being in a first search space set linked to a second search space set for PDCCH repetition, wherein the first search space set is assigned a first search space set index, which is higher than a second search space set index assigned to the second search space set; the PUCCH resource set including the PUCCH resource includes more than eight PUCCH resources, and the starting CCE of the third PDCCH candidate is different from the starting CCE of the fourth PDCCH candidate. State 48: The method according to any one of states 1 to 47, wherein: the first polymerization level corresponds to eight CCEs; and the second polymerization level corresponds to sixteen CCEs. State 49: The method according to any one of states 1 to 48, wherein: the first PDCCH candidate includes a PUCCH resource indicator; the second control resource set includes a defined number of control channel elements; and the method also includes: identifying a PUCCH resource based at least in part on the first CCE index, the PUCCH resource indicator and the defined number of control channel elements. State 50: The method according to any one of states 1 to 49, wherein: the first PDCCH candidate includes first downlink control information (DCI) scheduled for transmission of the first entity downlink shared channel (PDSCH); and the second PDCCH candidate includes second DCI scheduled for transmission of the second PDSCH. State 51: A user equipment comprising: a transceiver configured to communicate with a radio access network, memory, and a processor coupled to the transceiver and memory, wherein the processor and memory are configured to execute any one of states 41 to 50. State 52: An apparatus configured for wireless communication, comprising at least one unit for performing any one of states 41 to 50. Format 53: A non-transitory computer-readable medium storing computer-executable code, including code for causing a device to execute any one of formats 41 to 50. Sample 61: A method for wireless communication at a user equipment, the method comprising: receiving a first entity downlink control channel (PDCCH) candidate of a first control resource set, the first PDCCH candidate scheduling an entity uplink control channel (PUCCH) with acknowledgment information and starting at the same control channel element (CCE) as a second PDCCH candidate in the first control resource set, the first PDCCH candidate repeating in a third PDCCH candidate of a second control resource set, the second PDCCH candidate repeating in a fourth PDCCH candidate of the second control resource set, the third PDCCH candidate being associated with a first starting CCE in the second control resource set, and the fourth PDCCH candidate being associated with a second starting CCE above the first starting CCE; and transmitting a PUCCH with acknowledgment information on a PUCCH resource identified at least in part based on a first CCE index corresponding to the second starting CCE. Version 62: The method according to Version 61 also includes: in response to determining the first PDCCH candidate and the second PDCCH candidate at the same location within the first control resource set, identifying the PUCCH resource at least in part based on the first CCE index. State 63: The method according to any one of states 1 to 62 further includes: in response to determining that the first control resource set is a non-interleaved control resource set having a single orthogonal frequency division multiplexing (OFDM) symbol, identifying the PUCCH resource at least in part based on the first CCE index. Sample 64: The method according to any one of Samples 1 to 63 also includes: in response to determining that a PUCCH resource is identified at least in part based on a first CCE index: a first PDCCH candidate and a second PDCCH candidate are in a first search space set linked to a second search space set for PDCCH repetition, wherein the first search space set is assigned a first search space set index, which is higher than a second search space set index assigned to the second search space set. Version 65: The method according to any one of versions 1 to 64 also includes: in response to determining that the set of PUCCH resources including PUCCH resources comprises more than eight PUCCH resources, identifying the PUCCH resources at least in part based on the first CCE index. Format 66: The method according to any one of formats 1 to 65 also includes: in response to determining that the first starting CCE is different from the second starting CCE, identifying the PUCCH resource based at least in part on the first CCE index. Version 67: The method according to Version 61 also includes: in response to determining that the first PDCCH candidate and the second PDCCH candidate begin at the same position within a first control resource set, identifying the PUCCH resource at least in part based on a first CCE index, the first control resource set being a non-interleaved control resource set having a single orthogonal frequency division multiplexing (OFDM) symbol, the first PDCCH candidate and the second PDCCH candidate being in a first search space set linked to a second search space set for PDCCH repetition, wherein the first search space set is assigned a first search space set index that is higher than a second search space set index assigned to the second search space set, the PUCCH resource set including the PUCCH resource includes more than eight PUCCH resources, and the first starting CCE and the second starting CCE are different. State 68: The method according to any one of states 1 to 67, wherein: the third PDCCH candidate is associated with the first polymerization level; and The fourth PDCCH candidate is associated with a second aggregation level that is different from the first aggregation level. State 69: The method according to any one of states 1 to 68, wherein: the first PDCCH candidate includes a PUCCH resource indicator; the second control resource set includes a defined number of control channel elements; and the method also includes: identifying a PUCCH resource based at least in part on the first CCE index, the PUCCH resource indicator and the defined number of control channel elements. State 70: The method according to any one of states 1 to 69, wherein: the first PDCCH candidate includes first downlink control information (DCI) transmitted in the scheduled first entity downlink shared channel (PDSCH); and the second PDCCH candidate includes second DCI transmitted in the scheduled second PDSCH. State 71: A user equipment comprising: a transceiver configured to communicate with a radio access network, memory, and a processor coupled to the transceiver and memory, wherein the processor and memory are configured to execute any one of states 61 to 70. State 72: A device configured for wireless communication, comprising at least one unit for performing any one of states 61 to 70. Sample 73: A non-transitory computer-readable medium storing computer-executable code, including code for causing a device to execute any one of samples 61 to 70. Several forms of wireless communication networks have been presented with reference to exemplary embodiments. As will be readily understood by those skilled in the art, the various forms described herein can be extended to other telecommunications systems, network architectures, and communication standards. For example, various forms 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 forms can also be extended to systems defined by 3GPP2, such as CDMA2000 and / or Evolved Data Optimization (EV-DO). Other examples can be implemented within systems using IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The specific telecommunications standards, network architecture, and / or communication standards employed will depend on the specific application and the overall design constraints imposed on the system. In this context, the term "exemplary" is used to mean "used as an example, illustration, or description." Any implementation or manner described herein as "exemplary" is not necessarily to be construed as preferred or superior to other manner described herein. Similarly, the term "manner" does not require that all manner described herein include the features, advantages, or modes of operation discussed. The term "coupling" is used herein to represent direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C can still be considered coupled to each other—even if they are not physically in direct contact. For example, the first object can be coupled to the second object even if the first object never physically contacts the second object. The terms "circuit" and "circuit system" are used broadly and are intended to include hardware implementations of electrical devices and conductors that, when connected and configured, can achieve the functions described herein, without limitation on the type of electronic circuit, as well as software implementations of information and instructions that, when executed by a processor, can achieve the functions described herein. As used herein, the term "decision" can encompass a wide variety of actions. For example, "decision" can include calculation, operation, processing, deduction, investigation, examination (e.g., examining in a table, database, or other data structure), identification, analysis, selection, picking, creation, reception (e.g., receiving information), access (e.g., accessing data in memory), etc. One or more of the components, steps, features, and / or functions shown in Figures 1-18 can be rearranged and / or combined into a single component, step, feature, or function, or embodied as several components, steps, or functions. Additional components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Any of the apparatuses, devices, and / or components shown in Figures 1, 2, 12, 13, and 18 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 using software and / or embedded hardware. It should be understood that the specific order or hierarchy of the steps in the disclosed method is an illustration of an example procedure. Based on design preferences, it is understood that the specific order or hierarchy of the steps in the method may be rearranged. The appended method request presents the elements of each step in an exemplary order and is not intended to be limited to the specific order or hierarchy presented, unless specifically indicated herein. The preceding description is provided to enable anyone skilled in the art to practice the various forms described herein. Various modifications to these forms will be apparent to those skilled in the art, and the general principles defined herein can be applied to other forms. Therefore, the claims are not intended to be limited to the forms shown herein, but should be given the full scope consistent with the language of the claims, wherein reference to a component in the singular does not mean "one and only one," but rather "one or more," unless specifically stated otherwise. Unless otherwise specified, the term "some" means one or more. The phrase "at least one" in the list of references to items means any combination of these items, including a single member. For 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 elements of the various forms described throughout this document, known or subsequently learned by those skilled in the art, are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, regardless of whether such disclosures are explicitly stated in the request, nothing disclosed herein is intended to be made public. 100: Wireless Communication System 102: Core Network 104: Radio Access Network (RAN) 106: User Equipment (UE) 108: Base Station 110: External Data Network 112: Downlink Traffic 114: Downlink Control Information 116: Uplink Traffic 118: Uplink Control Information 120: Backhaul 200: Radio Access Network (RAN) 202: Cell 204: Cell 206: Cell 208: Cell 210: Base Station 212: Base Station 214: Base Station 216: Remote Radio Header (RRH) 218: Base Station 220: Unmanned Aerial Vehicle (UAV) 222: UE 224: UE 226: UE 227: Sidelink Signal 228: UE 230: UE 232: UE 234: UE 236: UE 237: Sidelink Signal 238: UE 240: UE 242: UE 302: Subframe 304: Resource Grid 306: Resource Element (RE) 308: Resource Block (RB) 310: Time Slot 312: Control Area 314: Data Area 402: DL Control Area 404: CORESET 406: Control Channel Element (CCE) 500: CCE Structure 502: RE 504: RE Group (REG) 506: DL Control Area 600: Downlink Time-Frequency Resources 602: CCE 604: Time Slot 605: Carrier Bandwidth (CBW) 606: Bandwidth Part (BWP) 608: CORESET 618: Search Space (SS) 702: First Instance 704: Second Instance 706: First SS Set 708: Second SS Set 710: First SS Set 712: Second SS Set 800: Instance 802: First CORESET (CORESET) 1) 804: Second CoreSet (CoreSet 2) 806: PDCCH Candidate 808: PDCCH Candidate 900: Instance 902: First CoreSet 904: Second CoreSet 906: First PDCCH Candidate 908: First PDCCH Candidate 910: Second PDCCH Candidate 912: Second PDCCH Candidate 1000: Instance 1002: First CoreSet (CoreSet 1) 1004: Second CoreSet (CoreSet 2) 1006: First PDCCH Candidate 1008: First PDCCH Candidate 1010: Second PDCCH Candidate 1012: Second PDCCH Candidate 1100: Instance 1102: First CoreSet (CoreSet 1) 1104: Second CoreSet (CoreSet 2) 1106: First PDCCH Candidate1108: First PDCCH Candidate 1110: Second PDCCH Candidate 1112: Second PDCCH Candidate 1200: Signal Transmission Diagram 1202: Network Entity 1204: UE 1206: Procedure 1208: Procedure 1210: Procedure 1212: Procedure 1214: Procedure 1216: Procedure 1218: Procedure 1220: Procedure 1222: Procedure 1300: UE 1302: Bus 1304: Processor 1305: Memory 1306: Computer-readable Media 1308: Bus Interface 1310: Transceiver 1314: Processing System 1315: Resource Information 1330: Interface 1341: Communication and Processing Circuitry 1342: PDCCH Processing Circuitry 1343: PUCCH Processing Circuitry 1351: Communication and Processing Software 1352: PDCCH Processing Software 1353: PUCCH Processing Software 1400: Method 1402: Block 1404: Block 1500: Method 1502: Block 1504: Block 1600: Method 1602: Block 1604: Block 1700: Method 1702: Block 1704: Block 1800: De-aggregation Base Station 1805: Service Management and Orchestration (SMO) Framework 1810: Central Unit (CU) 1811: Open eNB 1815: Non-RT RIC 1820: Core Network 1825: Near-Real-Time (Near-RT) RAN Intelligent Controller (RIC) 1830: DU 1840: Radio Unit (RU) 1850: UE 1890: Open Cloud A1: Interface AL16: Given Aggregation Level AL8: Given Aggregation Level E2: Link MO1: First Monitoring Time MO2: Second Monitoring Time O1: Interface O2: Interface Figure 1 is a schematic diagram of a wireless communication system based on some different states. Figure 2 is a conceptual illustration of some examples of radio access networks. Figure 3 is a schematic diagram of an example of utilizing radio resources in the spatial intermediate plane of Orthogonal Frequency Division Multiplexing (OFDM) according to some patterns. Figure 4 is a schematic diagram of an example of a downlink control region based on some state slots. Figure 5 is a schematic diagram of an example of a control channel element structure based on some states. Figure 6 is a schematic diagram of an example of downlink time-frequency resources based on some states. Figure 7 is a schematic diagram illustrating an example of repeated downlink control channel (PDCCH) based on some state of entity. Figure 8 is a schematic diagram showing an example of PDCCH candidates based on some state connections. Figure 9 is a schematic diagram showing an example of a start control channel element (CCE) for connecting PDCCH candidates according to some state. Figure 10 is a schematic diagram showing an example of a Start Control Channel Element (CCE) selected according to some pattern to identify an entity uplink control channel (PUCCH) resource. Figure 11 is a schematic diagram illustrating other instances of the initial CCE selected for identifying entity uplink control channel (PUCCH) resources according to some patterns. Figure 12 is a signal transmission diagram illustrating an example of signal transmission related to PUCCH resource identification based on some states. Figure 13 is a block diagram illustrating an example of a hardware implementation of a user device employing a processing system according to some different configurations. Figure 14 is a flowchart of a first instance method for sending entity uplink control channel (PUCCH) information according to some patterns. Figure 15 is a flowchart of a second instance method for sending entity uplink control channel (PUCCH) information according to some patterns. Figure 16 is a flowchart of a third instance method for sending entity uplink control channel (PUCCH) information according to some patterns. Figure 17 is a flowchart of a fourth instance method for sending entity uplink control channel (PUCCH) information according to some patterns. Figure 18 is a schematic diagram providing a high-level illustration of an example configuration of a depolymerization base station based on some state. Domestic storage information (please note in order of storage institution, date, and number): None. International storage information (please note in order of storage country, institution, date, and number): None. 1400: Method 1402: Square 1404: Square

Claims

1. A user equipment, comprising: One transceiver; One or more memory locations from which the processor can execute code; And one or more processors configured to execute processor executable code and enable the user equipment to: receive, via the transceiver, a first entity downlink control channel (PDCCH) candidate of a first control resource set, the first PDCCH candidate scheduling an entity uplink control channel (PUCCH) with acknowledgment information, and starting at a control channel element (CCE) in the first control resource set that is the same as a second PDCCH candidate, the first PDCCH candidate repeating in a third PDCCH candidate of a second control resource set, the second PDCCH candidate repeating in a fourth PDCCH candidate of the second control resource set, the third PDCCH candidate being associated with a first aggregation level, and the fourth PDCCH candidate being associated with a second aggregation level; and via the transceiver, transmit the PUCCH with the acknowledgment information in response to a PUCCH resource identified at least in part based on a first CCE index corresponding to a starting CCE of the fourth PDCCH candidate, in response to a determination that the second aggregation level is higher than the first aggregation level.

2. According to the user equipment of request item 1, wherein the one or more processors are also configured to execute the processor executable code and cause the user equipment to: identify the PUCCH resource at least in part based on the first CCE index in response to determining that the first PDCCH candidate and the second PDCCH candidate begin at the same location within the first control resource set.

3. The user equipment according to request item 1, wherein the one or more processors are also configured to execute processor executable code and enable the user equipment to: identify the PUCCH resource at least in part based on the first CCE index in response to determining that the first control resource set is a non-interleaved control resource set having a single orthogonal frequency division multiplexing (OFDM) symbol.

4. The user equipment according to request item 1, wherein the one or more processors are also configured to execute processor executable code and cause the user equipment to: identify the PUCCH resource at least in part based on the first CCE index in response to determining that the first PDCCH candidate and the second PDCCH candidate are in a first search space set linked to a second search space set for PDCCH repetition, wherein the first search space set is assigned a first search space set index, which is higher than a second search space set index assigned to the second search space set.

5. According to the user equipment of request item 1, wherein the one or more processors are also configured to execute processor executable code and cause the user equipment to: identify the PUCCH resource at least in part based on the first CCE index in response to determining that a set of PUCCH resources including the PUCCH resource includes more than eight PUCCH resources.

6. According to the user equipment of request item 1, wherein the one or more processors are also configured to execute processor executable code and cause the user equipment to: identify the PUCCH resource at least in part based on the first CCE index in response to determining that the starting CCE of the third PDCCH candidate is different from the starting CCE of the fourth PDCCH candidate.

7. The user equipment according to request item 1, wherein the one or more processors are also configured to execute processor executable code and cause the user equipment to respond to identifying the PUCCH resource at least in part based on the first CCE index by determining the following: the first PDCCH candidate and the second PDCCH candidate begin at the same location within the first control resource set; the first control resource set is a non-interleaved control resource set having a single orthogonal frequency division multiplexing (OFDM) symbol; the first PDCCH candidate and the second PDCCH candidate are in a first search space set linked to a second search space set for PDCCH repetition, wherein the first search space set is assigned a first search space set index, the first search space set index being higher than a second search space set index assigned to the second search space set; a PUCCH resource set including the PUCCH resource includes more than eight PUCCH resources; and the starting CCE of the third PDCCH candidate is different from the starting CCE of the fourth PDCCH candidate.

8. According to the user equipment in request item 1, wherein: The first aggregation level corresponds to eight CCEs; and the second aggregation level corresponds to sixteen CCEs.

9. According to the user equipment in request item 1, wherein: The first PDCCH candidate includes a PUCCH resource indicator; the second control resource set includes a defined number of control channel elements; and the one or more processors are also configured to execute processor executable code and enable the user equipment to identify the PUCCH resource at least in part based on the first CCE index, the PUCCH resource indicator, and the defined number of control channel elements.

10. According to the user equipment of request item 1, wherein: The first PDCCH candidate includes the first downlink control information (DCI) transmitted via the Scheduled First Entity Downlink Shared Channel (PDSCH); and the second PDCCH candidate includes the second DCI transmitted via the Scheduled Second PDSCH.

11. A method for wireless communication at a user equipment, the method comprising the steps of: receiving a first entity downlink control channel (PDCCH) candidate in a first control resource set, the first PDCCH candidate scheduling an entity uplink control channel (PUCCH) with acknowledgment information and starting at a control channel element (CCE) in the first control resource set that is the same as a second PDCCH candidate, the first PDCCH candidate repeating in a third PDCCH candidate in a second control resource set, the second PDCCH candidate repeating in a fourth PDCCH candidate in the second control resource set, the third PDCCH candidate being associated with a first aggregation level, and the fourth PDCCH candidate being associated with a second aggregation level; and transmitting the PUCCH having the acknowledgment information in response to a PUCCH resource identified at least in part based on a first CCE index corresponding to a starting CCE of the fourth PDCCH candidate, which determines that the second aggregation level is higher than the first aggregation level.

12. The method according to request item 11 also includes the following steps: in response to determining that the first PDCCH candidate and the second PDCCH candidate begin at the same location within the first control resource set, to identify the PUCCH resource at least in part based on the first CCE index.

13. The method according to request item 11 also includes the following steps: in response to determining that the first control resource set is a non-interleaved control resource set having a single orthogonal frequency division multiplexing (OFDM) symbol, identifying the PUCCH resource at least in part based on the first CCE index.

14. The method according to request 11 also includes the following steps: In response to determining that the PUCCH resource is identified at least in part based on the first CCE index, the first PDCCH candidate and the second PDCCH candidate are in a first search space set linked to a second search space set for PDCCH repetition, wherein the first search space set is assigned a first search space set index, which is higher than a second search space set index assigned to the second search space set.

15. The method according to request item 11 also includes the following steps: in response to determining that a set of PUCCH resources including the PUCCH resource includes more than eight PUCCH resources, to identify the PUCCH resource at least in part based on the first CCE index.

16. The method according to request item 11 also includes the following steps: in response to the determination that the starting CCE of the third PDCCH candidate is different from the starting CCE of the fourth PDCCH candidate, to identify the PUCCH resource at least in part based on the first CCE index.

17. The method according to claim 11 also includes responding to the determination of at least in part based on the first CCE index to identify the PUCCH resource: the first PDCCH candidate and the second PDCCH candidate begin at the same position within the first control resource set; the first control resource set is a non-interleaved control resource set having a single orthogonal frequency division multiplexing (OFDM) symbol; the first PDCCH candidate and the second PDCCH candidate are in a first search space set linked to a second search space set for PDCCH repetition, wherein the first search space set is assigned a first search space set index, which is higher than a second search space set index assigned to the second search space set; a PUCCH resource set including the PUCCH resource includes more than eight PUCCH resources; and the starting CCE of the third PDCCH candidate is different from the starting CCE of the fourth PDCCH candidate.

18. According to the method of request item 11, wherein: The first aggregation level corresponds to eight CCEs; and the second aggregation level corresponds to sixteen CCEs.

19. According to the method of request item 11, wherein: The first PDCCH candidate includes a PUCCH resource indicator; The second control resource set includes a defined number of control channel elements; The method also includes identifying the PUCCH resource based at least in part on the first CCE index, the PUCCH resource indicator, and the defined number of control channel elements.

20. According to the method of request item 11, wherein: The first PDCCH candidate includes the first downlink control information (DCI) transmitted via the Scheduled First Entity Downlink Shared Channel (PDSCH); and the second PDCCH candidate includes the second DCI transmitted via the Scheduled Second PDSCH.

21. A user equipment, comprising: A unit for receiving a first entity downlink control channel (PDCCH) candidate in a first control resource set, the first PDCCH candidate scheduling an entity uplink control channel (PUCCH) with acknowledgment information and starting at a control channel element (CCE) in the first control resource set that is the same as a second PDCCH candidate, the first PDCCH candidate repeating in a third PDCCH candidate in a second control resource set, the second PDCCH candidate repeating in a fourth PDCCH candidate in the second control resource set, the third PDCCH candidate being associated with a first aggregation level, and the fourth PDCCH candidate being associated with a second aggregation level; and a unit for transmitting the PUCCH with the acknowledgment information in response to a PUCCH resource identified at least in part based on a first CCE index corresponding to a starting CCE of the fourth PDCCH candidate, in response to a determination that the second aggregation level is higher than the first aggregation level.

22. A non-transitory computer-readable medium having instructions stored therein, the instructions being executable by one or more processors of a user device to: receive a first entity downlink control channel (PDCCH) candidate in a first control resource set, the first PDCCH candidate scheduling an entity uplink control channel (PUCCH) with acknowledgment information and starting at a control channel element (CCE) in the first control resource set that is the same as a second PDCCH candidate, the first PDCCH candidate repeating in a third PDCCH candidate in a second control resource set, the second PDCCH candidate repeating in a fourth PDCCH candidate in the second control resource set, the third PDCCH candidate being associated with a first aggregation level, and the fourth PDCCH candidate being associated with a second aggregation level; and, in response to a PUCCH resource identified at least in part based on a first CCE index corresponding to a starting CCE of the fourth PDCCH candidate, in response to a determination that the second aggregation level is higher than the first aggregation level.

Images