Uplink control channel resource selection for scheduling request transmission

By selecting the scheduling request resources based on signal metrics and parameter sets among multiple cells, the problem of scheduling request resource selection ambiguity is solved, the reliability and throughput of wireless communication is improved, and power consumption and delay are reduced.

CN119032535APending Publication Date: 2024-11-26QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380034371.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-28
Filing Date
2023-04-13
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

In a wireless communication system, there is ambiguity when the user equipment (UE) selects scheduling request resources among multiple cells, resulting in increased communication delay, reduced reliability and increased power consumption.

Method used

Based on the parameters associated with the cell, such as power mode, signal metrics, and parameter sets, the UE selects the most suitable scheduling request resource to send scheduling requests, reducing ambiguity and improving communication reliability and throughput.

Benefits of technology

By selecting the optimal scheduling request resource, the UE reduces power consumption while improving communication reliability and throughput, reducing delay, and improving the performance of scheduling request transmission.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119032535A_ABST
    Figure CN119032535A_ABST
Patent Text Reader

Abstract

Methods, systems, and devices for wireless communication are described. Some wireless communication systems may support techniques for a user equipment (UE) to select a scheduling request resource from a plurality of scheduling request resources allocated across different cells based on one or more conditions. The UE may receive control signaling indicating a first scheduling request resource on a first cell and a second scheduling request resource on a second cell. The UE may generate a scheduling request applicable to the first scheduling request resource and the second scheduling request resource. The UE may select the first scheduling request resource for transmission of the scheduling request on the first cell based on one or more of a power mode of the UE, a signal metric associated with the first cell, or a set of parameters of the first cell. The UE may send the scheduling request via the first resource on the first cell based on the selection.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 731,406, filed by Mukkera et al. on April 28, 2022, entitled “UPLINK CONTROLCHANNEL RESOURCE SELECTION FOR SCHEDULING REQUEST TRANSMISSION,” which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including uplink control channel resource selection for scheduling request transmission. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication of communication devices, which may be referred to as user equipment (UE).

[0005] In some systems, a UE may send a scheduling request to request resources for uplink transmissions of the UE.The UE may send the scheduling request via one or more physical uplink control channel (PUCCH) resources indicated via a scheduling request configuration. Summary of the invention

[0006] The described technology relates to improved methods, systems, devices and apparatuses for supporting uplink control channel resource selection for scheduling request transmission. In some wireless communication systems, a user equipment (UE) may be configured to communicate with a network through multiple cells (e.g., a primary cell (PCell), a secondary cell (SCell), a secondary cell (SpCell) in a primary or secondary cell group, another type of cell, or any combination thereof). A network entity may send control signaling to the UE to allocate scheduling request resources (e.g., physical uplink control channel (PUCCH) resources) to the UE across cells. In some aspects, the UE may generate a scheduling request at a first time, and available scheduling request resources may be allocated on multiple cells simultaneously or within a time period of the first time. In general, the described technology may provide a mechanism for the UE to select between multiple available scheduling request resources on different cells for the transmission of the scheduling request.

[0007] The UE may select a scheduling request resource from the multiple scheduling request resources indicated via control signaling for sending the scheduling request based on one or more parameters or conditions associated with the UE, associated with the cell corresponding to the one or more scheduling request resources, or both. For example, the scheduling request resource selection may be based on the power mode of the UE (e.g., low power mode), the relative signal metric associated with the cells (e.g., reference signal received power (RSRP)), the relative parameter set of the cells, or a combination thereof. The UE may send the scheduling request via the selected scheduling request resource on the corresponding cell. The selection of the scheduling request resource based on the one or more conditions or parameters may provide reduced ambiguity, which may reduce latency and improve reliability and throughput of the scheduling request sending.

[0008] A method for wireless communication at a UE is described. The method may include: receiving control signaling indicating a first scheduling request resource on a first cell and a second scheduling request resource on a second cell; generating a scheduling request at the UE, wherein both the first scheduling request resource on the first cell and the second scheduling request resource on the second cell are applicable to the scheduling request; selecting the first scheduling request resource for sending the scheduling request on the first cell based on one or more of the following: a power mode of the UE, a signal metric associated with the first cell, or a parameter set of the first cell; and sending the scheduling request via the first scheduling request resource on the first cell based on the selection.

[0009] A device for wireless communication at a UE is described. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the device to: receive control signaling indicating a first scheduling request resource on a first cell and a second scheduling request resource on a second cell; generate a scheduling request at the UE, wherein both the first scheduling request resource on the first cell and the second scheduling request resource on the second cell are applicable to the scheduling request; select the first scheduling request resource for sending the scheduling request on the first cell based on one or more of the following: a power mode of the UE, a signal metric associated with the first cell, or a parameter set of the first cell; and send the scheduling request via the first scheduling request resource on the first cell based on the selection.

[0010] Another apparatus for wireless communication at a UE is described. The apparatus may include: a component for receiving control signaling indicating a first scheduling request resource on a first cell and a second scheduling request resource on a second cell; a component for generating a scheduling request at the UE, wherein both the first scheduling request resource on the first cell and the second scheduling request resource on the second cell are applicable to the scheduling request; a component for selecting the first scheduling request resource for sending the scheduling request on the first cell based on one or more of the following: a power mode of the UE, a signal metric associated with the first cell, or a parameter set of the first cell; and a component for sending the scheduling request via the first scheduling request resource on the first cell based on the selection.

[0011] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions that can be executed by a processor to: receive control signaling indicating a first scheduling request resource on a first cell and a second scheduling request resource on a second cell; generate a scheduling request at the UE, wherein both the first scheduling request resource on the first cell and the second scheduling request resource on the second cell are applicable to the scheduling request; select the first scheduling request resource for sending the scheduling request on the first cell based on one or more of the following: a power mode of the UE, a signal metric associated with the first cell, or a parameter set of the first cell; and send the scheduling request via the first scheduling request resource on the first cell based on the selection.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for operating in a reduced power mode, wherein selecting the first scheduling request resource may be based on operating in the reduced power mode.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, selecting the first scheduling request resource may include operations, features, components, or instructions for the following actions: selecting the first scheduling request resource based on a type of the first cell associated with the first scheduling request resource.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the type of the first cell may be a SpCell, and selecting the first scheduling request resource may be based on the type of the first cell being the SpCell.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, selecting the first scheduling request resource may include operations, features, components, or instructions for the following actions: selecting the first scheduling request resource based on the signal metric associated with the first cell being greater than a second signal metric associated with the second cell.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for: receiving one or more reference signals via the first cell and the second cell; and measuring the signal metric associated with the first cell and the second signal metric associated with the second cell based on the one or more reference signals, wherein selecting the first scheduling request resource may be based on the measurement.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the scheduling request may include operations, features, components, or instructions for the following actions: sending the scheduling request according to a first transmit power, the first transmit power being based on the value of the signal metric.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the signal metric and the second signal metric include an RSRP metric.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, selecting the first scheduling request resource may include operations, features, components, or instructions for the following actions: selecting the first scheduling request resource based on the parameter set of the first cell being greater than or equal to the parameter set of the second cell.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, selecting the first scheduling request resource may include operations, features, components, or instructions for the following actions: selecting the first scheduling request resource based on a type of the first cell.

[0021] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first scheduling request resource and the second scheduling request resource may at least partially overlap in time. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first scheduling request resource and the second scheduling request resource may not overlap in time.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control signaling may indicate the same scheduling request identifier (ID) for the first scheduling request resource and the second scheduling request resource; generating the scheduling request may be based on the same scheduling request ID; and the selection may be based on the first scheduling request resource and the second scheduling request resource both being associated with the same scheduling request ID as the scheduling request. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 An example of a wireless communication system supporting uplink control channel resource selection for scheduling request transmission in accordance with one or more aspects of the present disclosure is illustrated.

[0024] Figure 2 An example of a wireless communication system supporting uplink control channel resource selection for scheduling request transmission in accordance with one or more aspects of the present disclosure is illustrated.

[0025] Figure 3 An example of a communication timeline supporting uplink control channel resource selection for scheduling request transmissions in accordance with one or more aspects of the present disclosure is illustrated.

[0026] Figure 4 An example of a communication timeline supporting uplink control channel resource selection for scheduling request transmissions in accordance with one or more aspects of the present disclosure is illustrated.

[0027] Figure 5 An example of a process flow to support uplink control channel resource selection for scheduling request transmission in accordance with one or more aspects of the present disclosure is illustrated.

[0028] Figure 6 and Figure 7 A block diagram of an apparatus supporting uplink control channel resource selection for scheduling request transmission according to one or more aspects of the present disclosure is shown.

[0029] Figure 8 A block diagram of a communications manager supporting uplink control channel resource selection for scheduling request transmissions is shown in accordance with one or more aspects of the present disclosure.

[0030] Fig. 9A diagram of a system including a device supporting uplink control channel resource selection for scheduling request transmission is shown in accordance with one or more aspects of the present disclosure.

[0031] Figures 10 to 12 A flow chart illustrating a method of supporting uplink control channel resource selection for scheduling request transmission according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0032] In some wireless communication systems, a user equipment (UE) may send a scheduling request to request uplink resources for subsequent transmission by the UE. The scheduling request may be sent via a physical uplink control channel (PUCCH) according to a scheduling request configuration. For example, a network entity may send control signaling (e.g., a radio resource control (RRC) configuration) that may allocate one or more PUCCH resources for the transmission of a scheduling request, which control signaling may be referred to as a scheduling request configuration. In some aspects, PUCCH resources may be referred to as scheduling request resources. The scheduling request configuration and each of the scheduling request resources indicated by the scheduling request configuration may be associated with or identified by the same scheduling request identifier (ID). The scheduling request resources indicated by the scheduling request configuration may be allocated across one or more cells (such as a secondary cell (SCell), a primary cell (PCell), a primary cell in a primary or secondary cell group (SpCell), or any combination thereof).

[0033] If the UE is configured with scheduling request resources corresponding to the same scheduling request ID on different cells, the selection of which scheduling request resource to use to signal the scheduling request may depend on the UE specific implementation. In some cases, for example, the UE may select a scheduling request resource on the SCell, and the UE may refrain from sending scheduling requests on the SpCell for a certain duration, which may reduce reliability and increase power consumption. Additionally or alternatively, the scheduling request resource selection may be random or otherwise ambiguous.

[0034] As described herein, a UE configured with scheduling request resources on two or more different cells may select a scheduling request resource for the transmission of a scheduling request based on one or more conditions or parameters to reduce ambiguity. The technology for scheduling request resource selection described herein may provide improved communication reliability and throughput, as well as reduced latency and reduced power consumption of the UE. For example, the UE may select a scheduling request resource based on the UE's power mode, the signal metric level of the corresponding cell (e.g., reference signal received power (RSRP) level or other signal metric), the parameter set of the corresponding cell (e.g., time slot length in the time domain, symbol length in the time domain, or subcarrier spacing (SCS) value), or any combination thereof. The UE may select a scheduling request resource from two or more scheduling request resources configured for scheduling request transmission on different cells and associated with the same scheduling request ID. The two or more scheduling request resources may overlap or not overlap in time. The UE may send a scheduling request to a network entity via the selected scheduling request resource. In response to the scheduling request, the network entity may grant or schedule an uplink shared channel resource for the UE to send.

[0035] In some aspects, the UE may operate in a reduced power mode. The UE may be configured to select a scheduling request resource based on the type of cell when operating in a reduced power mode. If the UE operates in a reduced power mode, the UE may, for example, select a scheduling request resource on the SpCell to improve the reliability of transmission during the reduced power mode. In some other aspects, the UE may measure a signal metric (e.g., RSRP) associated with each cell. The UE may select a scheduling request resource on a cell associated with the maximum measured signal metric to improve reliability and reduce power consumption. In some other aspects, the UE may select a scheduling request resource on a cell associated with a maximum parameter set (e.g., the shortest time slot length, the shortest symbol length, or the maximum SCS). The UE may send a scheduling request faster via the selected scheduling request resource on the cell associated with the maximum parameter set than the UE sends a scheduling request on other cells associated with a lower parameter set. Therefore, the UE may select a scheduling request resource from a set of configured scheduling request resources associated with the same scheduling request ID based on one or more rules or parameters configured to improve the reliability and throughput of scheduling request transmission while reducing the latency and power consumption of the UE.

[0036] Various aspects of the disclosure are first described in the context of a wireless communication system. Additional aspects are described with reference to communication timelines and process flows. Various aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to uplink control channel resource selection for scheduling request transmission.

[0037] Figure 1An example of a wireless communication system 100 supporting uplink control channel resource selection for scheduling request transmission according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0038] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In different examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, etc. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). Each network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0039] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UE 115 are illustrated in FIG. The UE 115 described herein can be used with various types of devices such as Figure 1 Communicate with other UEs 115 or network entities 105 shown in FIG.

[0040] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as a network node. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0041] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), and other examples or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0042] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a Home Node B, a Home Evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture that may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0043] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration initiated by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0044] The functional split between CU 160, DU 165 and RU 175 is flexible, and different functionalities may be supported depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, and RU 175. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165, such that CU 160 may support one or more layers of a protocol stack, and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by the other of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating over those communication links.

[0045] In a wireless communication system (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to a core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0046] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between an IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of part of a backhaul link) and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB donors) via an Xn-C interface (which may be an example of part of a backhaul link).

[0047] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., an IAB donor may relay transmissions to a UE through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, an IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, the IAB-MT entity of IAB node 104 may provide a Uu interface for child IAB node 104 to receive signaling from parent IAB node 104 , and a DU interface (eg, DU 165 ) may provide a Uu interface for parent IAB node 104 to signal to child IAB node 104 or UE 115 .

[0048] For example, the IAB node 104 may be referred to as a parent node that supports communication of a child IAB node, and may be referred to as a child IAB node associated with an IAB donor. The IAB donor may include a CU 160 having a wired or wireless connection (e.g., a backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB donor may relay transmission to the UE 115 through the IAB node 104, and may directly signal the UE 115 of the transmission. The CU 160 of the IAB donor may signal the IAB node 104 of the communication link establishment via the F1 interface, and the IAB node 104 may schedule the transmission (e.g., the transmission relayed from the IAB donor to the UE 115) through the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling through the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0049] In the case where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support uplink control channel resource selection for scheduling request transmission as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0050] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as electrical appliances or vehicles, meters, etc.

[0051] The UE 115 described herein is capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, and network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, such as Figure 1 shown.

[0052] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) on one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a defined physical layer structure to support the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any part (e.g., entity, sub-entity) of the network entity 105. For example, when referring to the network entity 105, the terms "sending", "receiving" or "communicating" may refer to any part of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0053] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be located according to a channel raster for discovery by a UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be performed by a UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or different radio access technology).

[0054] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communications or uplink communications (e.g., in FDD mode), or may be configured to carry downlink communications and uplink communications (e.g., in TDD mode).

[0055] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as a "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communication on a particular carrier bandwidth or may be configurable to support communication on one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

[0056] The signal waveform sent on the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a subcarrier resource, where the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device can be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE115.

[0057] One or more parameter sets for a carrier may be supported, where the parameter set may include subcarrier spacing (Δf) and cyclic prefix. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of the UE 115 may be restricted to the one or more active BWPs.

[0058] The time interval of the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, T s =1 / (Δf max ·N f ) seconds sampling period, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., in the range of 0 to 1023).

[0059] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, a time slot may be further divided into a plurality of micro time slots including one or more symbols. In addition to the cyclic prefix, each symbol period may include one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0060] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0061] Physical channels may be multiplexed on a carrier according to various techniques. For example, physical control channels and physical data channels may be multiplexed on a downlink carrier using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0062] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., on a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other) used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0063] A macro cell typically covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have a service subscription with a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) (compared to a macro cell), and the small cell may operate in the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to UEs 115 that have a service subscription with a network provider, or may provide restricted access to UEs 115 associated with a small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications on one or more cells.

[0064] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0065] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and, therefore, provide communication coverage for mobile geographic coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0066] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) may have similar frame timing, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timing, and in some examples, transmissions from different network entities 105 may not be aligned in time. The techniques described herein may be used for synchronous or asynchronous operation.

[0067] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may allow automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, wildlife monitoring, weather and geographic event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0068] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for UE 115 include entering a power-saving deep sleep mode when not engaged in active communications, operating with limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a subcarrier or resource block (RB) set) within a carrier, within a guard band of a carrier, or outside a carrier.

[0069] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC). UE 115 can be designed to support ultra-reliable, low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency and ultra-reliable low-latency may be used interchangeably herein.

[0070] In some examples, a UE 115 can communicate directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P) or D2D or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured or scheduled by the network entity 105. One or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or otherwise unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .

[0071] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to an IP service 150 for one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0072] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region of 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is about one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0073] The wireless communication system 100 can utilize both licensed RF spectrum bands and unlicensed RF spectrum bands. For example, the wireless communication system 100 can adopt licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 can adopt carrier sensing for conflict detection and avoidance. In some examples, operations in unlicensed bands can be based on a carrier aggregation configuration (e.g., LAA) combined with component carriers operating in licensed bands. Operations in unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0074] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels that can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may have an antenna array having a set of rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0075] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such technology may be referred to as spatial multiplexing. For example, multiple signals may be sent by a transmitting device via different antennas or different combinations of antennas. Similarly, multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO), in which multiple spatial layers are sent to the same receiving device; and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to multiple devices.

[0076] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0077] The network entity 105 or the UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different beamforming weight sets associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device such as the network entity 105, or by a receiving device such as the UE 115) the beam direction for later transmission or reception by the network entity 105.

[0078] Some signals, such as data signals associated with a particular receiving device, may be sent by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device, such as receiving network entity 105 or receiving UE 115). In some examples, a beam direction associated with transmission along a single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0079] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more subbands. Network entity 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may or may not be precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-faceted codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0080] When receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105), the receiving device (e.g., UE 115) may perform receiving operations (e.g., directional listening) according to multiple receiving configurations. For example, the receiving device may perform reception according to multiple receiving directions by performing the following operations: receiving via different antenna subarrays, processing the received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0081] The wireless communication system 100 can be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication at the bearer layer or the PDCP layer can be IP-based. The RLC layer can perform packet segmentation and reassembly for transmission on a logical channel. The MAC layer can perform priority processing and multiplexing of logical channels to transport channels. The MAC layer can also use error detection technology, error correction technology, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer can provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between the UE 115 and the network entity 105 or the core network 130. At the PHY layer, the transport channel can be mapped to a physical channel.

[0082] UE 115 and network entity 105 may support retransmission of data to increase the likelihood of data being successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data through a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support simultaneous slot HARQ feedback, wherein the device may provide HARQ feedback in a specific time slot for data received in a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0083] In some examples of the wireless communication system 100, the UE 115 may receive control signaling that may indicate or configure one or more scheduling request resources. The scheduling request resources may be allocated across a first cell, a second cell, one or more other cells, or any combination thereof (e.g., a PCell, an SCell, a SpCell, or some other cell). The UE 115 may generate a scheduling request based on the control signaling to request resources for subsequent uplink transmissions of the UE 115. The generated scheduling request may be applicable to each of the scheduling request resources indicated by the control signaling. For example, the control signaling may correspond to a scheduling request resource configuration that may be associated with a single scheduling request ID, such that each of the indicated scheduling request resources may be associated with the same scheduling request ID as the generated scheduling request.

[0084] The UE 115 may select a scheduling request resource (e.g., a PUCCH resource) for sending a scheduling request on one of the cells based on one or more parameters or conditions associated with the UE 115, the cell, or both. For example, the scheduling request resource selection may be based on a power mode (e.g., a low power mode) of the UE 115, a relative signal metric (e.g., RSRP) associated with the cell, a relative parameter set of the cell, or a combination thereof. The UE 115 may send a scheduling request via the selected scheduling request resource on the corresponding cell. The selection of the scheduling request resource based on one or more conditions or parameters may provide reduced ambiguity, which may reduce latency of communications and improve reliability and throughput of scheduling request transmissions.

[0085] Figure 2 An example of a wireless communication system 200 that supports uplink control channel resource selection for scheduling request transmission according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may be implemented as shown in FIG. Figure 1Various aspects of the wireless communication system 100 described above may be implemented by various aspects of the wireless communication system. For example, the wireless communication system 200 may include a network entity 105-a and a UE 115-a, which may be represented as shown in FIG. Figure 1 1 and 10. The network entity 105-a may communicate with the UE 115-a within the geographic coverage area 110-a and via one or more cells 210 (e.g., cells 210-a and 210-b). In some aspects, the network entity 105-a may send downlink data or control information to the UE 115-a via a downlink communication link 205, which may be included in one or more of the cells 210 or separate therefrom.

[0086] UE 115-a and network entity 105-a may exchange signaling on one or both of cell 210-a and cell 210-b. Cell 210-a and cell 210-b may be examples of different serving cells or different component carriers supported for communication between UE 115-a and network entity 105-a. Cell 210 may refer to a logical communication entity used to communicate with network entity 105-a (e.g., via a carrier). Each cell 210 may be associated with a corresponding cell ID for distinguishing from other neighboring cells. Cell 210-a and cell 210-b may be associated with the same network entity 105-a or with different network entities 105. For example, network entity 105-a may provide communication coverage via cell 210-a, cell 210-b, one or more other cells 210, or any combination thereof. In some aspects, different components of network entity 105-a (e.g., different RUs, CUs, radio heads, or transmit / receive points (TRPs)) may be associated with each cell 210. In some other aspects, cell 210-a and cell 210-b may be associated with different network entities 105( Figure 2 (not shown in the example) is associated.

[0087] Cell 210-a and cell 210-b may be co-located (eg, may be located at the same physical location) or may be distributed (eg, may be located at different physical locations). Figure 2As shown, cell 210-a and cell 210-b may be associated with the same coverage area 110-a. In some other aspects, cell 210-a may be associated with coverage area 110-a and UE115-a may communicate via a second cell 210, which may be associated with a different coverage area 110 or a portion of coverage area 110 that at least partially overlaps with coverage area 110-a. Each of cells 210-a and 210-b may be an example of a PCell, SCell, P(S)Cell (e.g., one or both of a PCell and a PSCell), SpCell, or some other type of cell or may otherwise be used as such. SpCell may correspond to a primary cell in a cell group (such as a primary cell group or a secondary cell group). In some aspects, SpCell may be associated with higher reliability than a secondary cell in a cell group.

[0088] After establishing a connection with the UE 115-a via one or more cells 210, the network entity 105-a may send control signaling 215 to the UE 115-a. The control signaling 215 may represent an example of an RRC configuration, a medium access control-control element (MAC-CE), downlink control information (DCI), or some other control signaling 215. The control signaling 215 may be sent via a downlink communication link 205, which may be associated with a cell 210-a, a cell 210-b, another cell 210, or any combination thereof. The control signaling 215 may include a scheduling request configuration (e.g., an information element (IE) in the control signaling 215), which may allocate PUCCH resources, and the UE 115-a may send a scheduling request 230 via the PUCCH resources. The PUCCH resources allocated for the scheduling request 230 may be referred to herein as scheduling request resources 220.

[0089] The scheduling request configuration may additionally or alternatively configure one or more parameters for the cell 210-a and / or the cell 210-b, may indicate one or more timers (e.g., an inhibit timer) for scheduling request transmission, or both. The scheduling request configuration and each of the scheduling request resources 220 indicated by the scheduling request configuration may be associated with the same scheduling request ID.

[0090] UE 115-a may select a scheduling request resource 220 from a set of scheduling request resources 220 allocated by a scheduling request configuration for sending a scheduling request 230. When UE 115-a is triggered to generate an uplink transmission (e.g., UE 115-a has data to send), UE 115-a may select a scheduling request resource 220. The scheduling request 230 sent by UE 115-a via the selected scheduling request resource 220 may request uplink resources (e.g., physical uplink shared channel (PUSCH) resources) for subsequent uplink transmission by UE 115-a. Network entity 105-a may receive scheduling request 230 and select resources to be allocated to UE 115-a. Network entity 105-a may send second control signaling 215 to UE 115a to indicate the allocated PUSCH resources.

[0091] The scheduling request 230 generated by the UE 115-a may be associated with a scheduling request ID that is the same as the scheduling request ID of the scheduling request configuration. That is, the UE 115-a may select a scheduling request resource 220 from a set of scheduling request resources 220 that have the same scheduling request ID as the generated scheduling request 230. However, in some cases, the scheduling request configuration may allocate scheduling request resources 220 with the same scheduling request ID across multiple cells 210. Figure 2 In the example of , the scheduling request configuration may allocate scheduling request resources 220 on both cells 210-a and 210-b. In such cases, the technique for selecting which scheduling request resource 220 and which corresponding cell 210 to use for scheduling request transmission may be unambiguous.

[0092] In some cases, for example, the UE 115-a may randomly select a scheduling request resource 220, or the UE 115-a may select a scheduling request resource 220 that occurs earlier in time, which may cause the UE 115-a to repeatedly transmit on one of the cells 210. For example, the scheduling request resources 220 may be allocated earlier in time on the cell 210-b (e.g., SCell) than on the cell 210-a (e.g., SpCell), such that the UE 115-a may select the scheduling request resource 220 on the cell 210-b for each scheduling request 230, which may be associated with lower reliability, lower throughput, and increased latency compared to alternating which cells 210 are used for transmission or transmitting on the cell 210-a.

[0093] To reduce ambiguity and improve communication reliability, the UE 115-a as described herein may select a scheduling request resource 220 based on various conditions or parameters, such as a power mode of the UE 115-a, a signal metric associated with the cell 210, a parameter set for the cell 210, or any combination thereof. The UE 115-a may then transmit the generated scheduling request 230 via the selected scheduling request resource 220 on the corresponding cell 210. The conditions and parameters for scheduling request resource selection described herein may provide rules for selecting the scheduling request resource 220 on the cell 210 that may provide improved throughput and reliability for a given wireless communication, as well as reduced latency for uplink transmissions.

[0094] In some aspects, the UE 115-a may operate in a reduced power mode. The UE 115-a may be configured to select the scheduling request resources 220 based on the type of cell when operating in this reduced power mode. For example, if the scheduling request configuration allocates the scheduling request resources 220 on both the cell 210-a and the cell 210-b and the UE 115-a operates in the reduced power mode, the UE 115-a may select the scheduling request resources 220 allocated on the cell 210-a based on the type of cell and the rules related to cell selection for scheduling request transmission during the reduced power mode. The rules for selecting which type of cell 210 to select when operating in the reduced power mode may be configured (e.g., predefined in a standard or configured during manufacturing of the UE 115-a) or indicated to the UE 115-a via control signaling 215 (e.g., RRC configuration, DCI, or MAC-CE).

[0095] In some aspects, the rule may instruct the UE 115-a to select a cell 210 associated with the scheduled transmission that has a higher transmit power than other cells 210 to improve the throughput and reliability of the transmission when the UE 115-a is operating in the reduced power mode. For example, if the cell 210-a is a SpCell and the cell 210-b is a SCell and the UE 115-a is operating in the reduced power mode, the UE 115-a may select the scheduling request resource 220 on the SpCell based on the rule and that the SpCell transmission is scheduled at a higher power than the SCell (e.g., PUCCH SCell) transmission. Additionally or alternatively, the rule may indicate a certain type of cell 210 for the reduced power mode.

[0096] In some other aspects, the UE 115-a may measure a signal metric associated with each cell 210, and the UE 115-a may select a scheduling request resource 220 based on the measured signal metric. For example, the UE 115-a may select a scheduling request resource 220 associated with the maximum measured signal metric on the cell 210 to improve reliability and reduce power consumption. The signal metric may be a reference signal received power (RSRP), a signal-to-noise ratio (SNR), a signal-to-interference-plus-noise ratio (SINR), or some other signal metric. The UE 115-a may receive one or more reference signals 225 via each cell 210, and measure a signal metric associated with each of the cells 210-a and 210-b based on the reference signals 225. In some aspects, UE 115-a may measure an RSRP of reference signal 225 received via cell 210-b that is greater than the measured RSRP of reference signal 225 received via cell 210-a, and UE 115-a may accordingly select scheduling request resources 220 on cell 210-b for scheduling request 230.

[0097] The signal metric level may remain the same for each cell 210 over time, or may change dynamically. In some aspects, the UE 115-a may subsequently measure a greater RSRP level for cell 210-a than for cell 210-b, and the UE 115-a may accordingly select a scheduling request resource 220 on cell 210-a for a subsequent scheduling request 230. By selecting a scheduling request resource 220 on any cell 210 having the greatest signal metric, the UE 115-a may improve the reliability of the transmission of the scheduling request 230, and may reduce power consumption of the UE 115-a. For example, the UE 115-a may transmit the scheduling request 230 according to a transmit power based on the value of the signal metric. If cell 210-a has a lower signal metric measurement than cell 210-b, the UE 115-a may transmit the scheduling request 230 according to a lower transmit power on cell 210-b than on cell 210-a, which may reduce power consumption and complexity.

[0098] In some other aspects, the UE 115-a may select the scheduling request resource 220 based on a parameter set (e.g., symbol length, slot length, or SCS) for each cell 210. For example, the UE 115-a may select the scheduling request resource 220 on a cell 210 that is associated with a parameter set that is greater than a parameter set of other cells 210 on which the scheduling request resource 220 is allocated. Figure 2In the example of , if scheduling request resources 220 associated with the same scheduling request ID are allocated on cell 210-a and cell 210-b, and cell 210-a has a larger parameter set than cell 210-b, UE 115-a may select scheduling request resources 220 on cell 210-a for transmission of scheduling request 230. Cell 210 may be any type of cell 210 described herein or any additional type of cell 210. In some aspects, transmission via a cell 210 having a larger parameter set may be associated with reduced latency (e.g., faster) compared to transmission on other cells 210. As such, selecting scheduling request resources 220 based on the parameter set of a cell 210 as described herein may reduce latency.

[0099] If the parameter set of one cell 210 is the same as the parameter set of another cell 210, the UE 115-a may be configured to select the scheduling request resources 220 based on the type of cell 210 (e.g., based on a rule related to cell selection for scheduling requests). For example, the rule may instruct the UE 115-a to select the scheduling request resources 220 on the SpCell or some other type of cell 210. In some aspects, when the parameter sets of two or more cells 210 are unavailable, uncertain, or if their parameter sets are equal, a specific type of cell 210 (such as SpCell) may be used as a default. In some aspects, transmissions on the default cell 210 may be associated with a higher power than other cells 210, so that transmissions on the default cell 210 may have improved reliability and throughput.

[0100] Thus, the UE 115-a may select a scheduling request resource 220 from a set of multiple scheduling request resources 220 associated with the same scheduling request ID and allocated across multiple cells 210 based on one or more conditions, parameters, and rules as described herein. The described scheduling request resource selection techniques may reduce ambiguity and improve the performance of scheduling request transmissions by the UE 115-a. For example, the described techniques may enable the UE 115-a to select a scheduling request resource 220 that is associated with improved reliability, improved throughput, reduced power consumption, or reduced latency compared to other selection techniques. The described conditions, parameters, and rules may be applied by the UE 115-a when the set of allocated scheduling request resources 220 overlap at least partially in time or do not overlap in time, as described in further detail elsewhere herein, including with reference to Figure 3 and Figure 4 .

[0101] Figure 3 An example of a communication timeline 300 that supports uplink control channel resource selection for scheduling request transmission according to one or more aspects of the present disclosure is illustrated. In some examples, the communication timeline 300 may be implemented as described in reference to Figure 1 and Figure 2 Aspects of the wireless communication system 100 or 200 are described. For example, the communication timeline 300 illustrates the scheduling request resources 320 (eg, PUCCH resources) allocated on the SpCell 305 and the SCell 310, which may represent reference Figure 2 In this example, the scheduling request resources 320 on the SpCell 305 may not overlap with the scheduling request resources 320 on the SCell 310 in time.

[0102] The scheduling request resource 320 may be allocated by the network entity 105 for the UE 115, and the network entity and the UE may be represented as shown in FIG. Figure 1 and Figure 2 For example, the network entity 105 may send a control signaling including a scheduling request configuration for allocating the scheduling request resource 320 on the SpCell 305 and the SCell 310 to the UE 115, as shown in FIG. Figure 2 The scheduling request configuration may indicate a scheduling request ID 315 (eg, SR id_0 or some other ID) associated with each of the scheduling request resources 320 allocated by the configuration. The scheduling request resources 320 may include time and frequency resources allocated within the bandwidth of each cell.

[0103] In some aspects, the UE 115, the network entity 105, or both may be configured with various timers for scheduling request communications. An example of such a timer may include a scheduling request timer 325 (e.g., a scheduling request inhibit timer), which may be configured when delay tolerant data is available for transmission by the UE 115. The scheduling request timer 325 may be configured for a logical channel, various layers of the network, one or more cells, or any combination thereof. The scheduling request timer 325 may help prioritize high priority traffic. For example, the network entity 105 may refrain from scheduling uplink resources, and the UE 115 may refrain from sending a scheduling request to provide for transmission of high priority traffic (e.g., time sensitive information) before the scheduling request timer 325 expires.

[0104] exist Figure 3In the example of , if the UE 115 selects the scheduling request resource 320 randomly or based on the earliest available resource, the UE 115 may select the scheduling request resource 320 on the SCell 310. The UE 115 may send a scheduling request via the scheduling request resource 320 on the SCell 310, which may initiate a scheduling request timer 325. The UE 115 may not send a scheduling request before the scheduling request timer 325 expires. In this way, the UE 115 may not send a scheduling request via the scheduling request resource 320 on the SpCell 305. In some aspects, the scheduling request resource 320 may be periodically configured so that similar resource allocations may exist on the SpCell 305 and the SCell 310 within one or more time periods (e.g., every 100 ms, or some other time period). In such a case, the UE 115 may continue to send scheduling requests via the SCell 310, and the UE 115 may refrain from sending via the SpCell 305, which may reduce the reliability and throughput of the communication.

[0105] To reduce ambiguity and improve communication reliability, the UE 115 may select a scheduling request resource 320 from a set of scheduling request resources 320 associated with the same scheduling request ID 315 based on one or more conditions, rules, and parameters. Figure 3 In the example of , the scheduling request configuration may allocate scheduling request resources 320 on SpCell 305 and SCell 310, and the scheduling request resources 320 on SCell 310 may appear first in time. However, UE 115 may select any one of the scheduling request resources 320 based on the rules and parameters described herein.

[0106] For example, if the UE 115 is operating in a reduced power mode, the UE 115 may select the scheduling request resource 320 based on the type of cell on which the scheduling request resource 320 is allocated. In some aspects, the UE 115 may receive signaling or configuration indicating the type of cell (e.g., rules related to cell selection for scheduling request transmission). Figure 3 In the example of FIG. 1 , if the type of cell indicated by the rules related to cell selection for scheduling request is SpCell 305, UE 115 may select Figure 3 305. The UE 115 may send a scheduling request via the scheduling request resource 320 on the SpCell 305, and the UE 115 may refrain from sending via the scheduling request resource 320 on the SCell 310 (e.g., the UE 115 may skip the resource). In such a case, the scheduling request timer 325 may be initiated by the sending of the scheduling request via the scheduling request resource 320 on the SpCell 305.

[0107] In some other aspects, the UE 115 may measure a signal metric (e.g., RSRP, SNR, SINR, or some other signal metric) based on one or more reference signals received via each of the SpCell 305 and the SCell 310. The UE 115 may select a scheduling request resource 320 on whichever cell is associated with the greater signal metric level. For example, if the cell condition of the SpCell 305 is greater than the cell condition of the SCell 310 based on the measured signal metric levels, the UE 115 will send a scheduling request via the scheduling request resource 320 on the SpCell 305, and the UE 115 will refrain from sending a scheduling request on the SCell 310.

[0108] In some other aspects, the UE 115 may select the scheduling request resource 320 based on a parameter set for the corresponding cell. Figure 3 In the example of , the parameter set of SpCell 305 may be greater than the parameter set of SCell 310. UE 115 may send a scheduling request via a scheduling request resource 320 on SpCell 305 based on the greater parameter set, and UE 115 may refrain from sending a scheduling request via a scheduling request resource 320 on SCell 310. If the parameter sets of the cells are the same or uncertain, a cell type (e.g., a default cell) for selection may be configured to UE 115. For example, the default cell may be SpCell 305, and UE 115 may select a scheduling request resource 320 on SpCell 305 accordingly.

[0109] Although in Figure 3 305 and SCell 310 are illustrated in FIG. 306 , but it should be understood that the described techniques for selecting scheduling request resources 320 can be applied to scheduling request resources 320 allocated across any type of cell and any number of cells, including the cell types illustrated here and any other cell types. In some aspects, the UE 115 can use a combination of the described techniques for scheduling request resource selection. For example, the UE 115 can select the scheduling request resource 320 based on both the power mode of the UE 115 and the signal metric of the cell, or some other combination.

[0110] Additionally or alternatively, cell conditions, selection techniques, or both may change dynamically over time. For example, the UE 115 may select the scheduling request resource 320 based on the power mode of the UE 115 in a first time period, and the UE 115 may select the scheduling request resource 320 based on the parameter set of the cell in a second time period. In such cases, for the scheduling request resources 320 allocated in each time period (e.g., periodic allocation), the scheduling request configuration and the corresponding scheduling request ID 315 may be the same or different. The UE 115 may receive control signaling indicating which conditions to use to select the scheduling request resource 320 at a given time.

[0111] Thus, the UE 115 may select a scheduling request resource 320 from a set of non-overlapping scheduling request resources 320 associated with the same scheduling request ID 315 and allocated across different cells based on one or more conditions or parameters. The described techniques for selecting scheduling request resources 320 may improve communication reliability, improve throughput, reduce ambiguity, reduce latency, and reduce power consumption, among other advantages.

[0112] Figure 4 An example of a communication timeline 400 that supports uplink control channel resource selection for scheduling request transmission according to one or more aspects of the present disclosure is illustrated. In some examples, the communication timeline 400 may be implemented as described in reference to Figure 1 and Figure 2 Aspects of the wireless communication system 100 or 200 are described. For example, the communication timeline 400 illustrates the scheduling request resources 420 (eg, PUCCH resources) allocated on the SpCell 405 and the SCell 410, which may represent reference Figure 2 and Figure 3 An example of the corresponding elements described. In this example, the scheduling request resources 420 on the SpCell 405 may overlap at least partially in time with the scheduling request resources 420 on the SCell 410 .

[0113] The scheduling request resource 420 may be allocated by the network entity 105 for the UE 115, and the UE and the network entity may be represented as shown in FIG. Figure 1-Figure 3 For example, the network entity 105 may send a control signaling including a scheduling request configuration for allocating the scheduling request resource 420 on the SpCell 405 and the SCell 410 to the UE 115, as shown in FIG. Figure 2 The scheduling request configuration may indicate a scheduling request ID 415 (eg, SRid_0 or some other ID) associated with each of the scheduling request resources 420 allocated by the configuration. The scheduling request resources 420 may include time and frequency resources allocated within the bandwidth of each cell.

[0114] The UE 115 may not support sending scheduling requests via scheduling request resources 420 on different cells that overlap in time. That is, the UE 115 may not send two or more scheduling requests at the same time. In some aspects, the UE 115, the network entity 105, or both may be configured with a scheduling request timer that may prohibit the simultaneous sending of scheduling requests, such as Figure 3 The scheduling request timer 325 illustrated in FIG. Figure 4 In the example of , the UE 115 may therefore select a single scheduling request resource 420 from the set of scheduling request resources 420 associated with the scheduling request ID 415 for sending the scheduling request. However, in some cases, the selection of the scheduling request resource 420 may be ambiguous or random, which may reduce the reliability and throughput of the communication.

[0115] To reduce ambiguity and improve communication reliability as described herein, the UE 115 may select a scheduling request resource 420 from a set of scheduling request resources 420 associated with the same scheduling request ID 415 based on one or more conditions, rules, and parameters. Figure 4 In the example of FIG. 4 , the scheduling request configuration may allocate scheduling request resources 420 that may occur simultaneously on the SpCell 405 and the SCell 410. The UE 115 may select any one of the scheduling request resources 420 based on the rules and parameters described herein.

[0116] For example, if the UE 115 is operating in a reduced power mode, the UE 115 may select the scheduling request resource 420 based on the type of cell on which the scheduling request resource 420 is allocated. In some aspects, the UE 115 may receive signaling or configuration indicating the type of cell (e.g., rules related to cell selection for scheduling request transmission). Figure 4 In the example of FIG. 1 , if the type of cell indicated by the rules related to cell selection for scheduling request is SpCell 405, UE 115 may select Figure 4 The UE 115 may send a scheduling request via the scheduling request resource 420 on the SpCell 405, and the UE 115 may refrain from sending via the scheduling request resource 420 on the SCell 410 (eg, the UE 115 may skip the resource).

[0117] In some other aspects, the UE 115 may measure a signal metric (e.g., RSRP, SNR, SINR, or some other signal metric) based on one or more reference signals received via each of the SpCell 405 and the SCell 410. The UE 115 may select a scheduling request resource 420 on whichever cell is associated with the greater signal metric level. For example, if the cell condition of the SpCell 405 is greater than the cell condition of the SCell 410 based on the measured signal metric levels, the UE 115 may send a scheduling request via the scheduling request resource 420 on the SpCell 405, and the UE 115 may refrain from sending a scheduling request on the SCell 410.

[0118] In some other aspects, the UE 115 may select the scheduling request resource 420 based on a parameter set for the corresponding cell. Figure 4 In the example of , the parameter set of SpCell 405 may be greater than the parameter set of SCell 410. UE 115 may send a scheduling request via a scheduling request resource 420 on SpCell 405 based on the greater parameter set, and UE 115 may refrain from sending a scheduling request via a scheduling request resource 420 on SCell 410. If the parameter sets of the cells are the same or uncertain, a cell type (e.g., a default cell) for selection may be configured to UE 115. For example, the default cell may be SpCell 405, and UE 115 may select a scheduling request resource 420 on SpCell 405 accordingly.

[0119] Although in Figure 4 4, but it should be understood that the described techniques for selecting scheduling request resources 420 can be applied to scheduling request resources 420 allocated across any type of cell and any number of cells (including the cell types illustrated here and any other cell types). In some aspects, the UE 115 can use a combination of the described techniques for scheduling request resource selection. For example, the UE 115 can select the scheduling request resource 420 based on both the power mode of the UE 115 and the signal metric of the cell, or some other combination.

[0120] Additionally or alternatively, cell conditions, selection techniques, or both may change dynamically over time. For example, the UE 115 may select the scheduling request resource 420 based on the power mode of the UE 115 in a first time period, and the UE 115 may select the scheduling request resource 420 based on the parameter set of the cell in a second time period. In such cases, for the scheduling request resources 420 allocated in each time period (e.g., periodic allocation), the scheduling request configuration and the corresponding scheduling request ID 415 may be the same or different. The UE 115 may receive control signaling indicating which conditions to use to select the scheduling request resource 420 at a given time.

[0121] Thus, the UE 115 may select a scheduling request resource 420 from a set of scheduling request resources 420 that are at least partially overlapping in time, associated with the same scheduling request ID 415, and allocated across different cells based on one or more conditions or parameters. The described techniques for selecting a scheduling request resource 420 may improve communication reliability, improve throughput, reduce ambiguity, reduce latency, and reduce power consumption, among other advantages.

[0122] Figure 5 An example of a process flow 500 for supporting uplink control channel resource selection for scheduling request transmission according to one or more aspects of the present disclosure is illustrated. The process flow 500 may be implemented as shown in FIG. Figure 1-Figure 4 Aspects of the wireless communication systems 100 and 200 or the communication timelines 300 or 400 described above may be implemented by or in accordance with these aspects. For example, the process flow 500 illustrates a technique for selecting a scheduling request resource for sending a scheduling request between a UE 115-b and a network entity 105-b, which may be represented as shown in reference Figure 1-Figure 4 In some aspects, UE 115-b may select a scheduling request resource based on various conditions or parameters, such as reference Figure 2-Figure 4 described.

[0123] In the following description of process flow 500, operations between UE 115-b and network entity 105-b may be performed in a different order or at a different time. Some operations may also be excluded from process flow 500, or other operations may be added. Although UE 115-b and network entity 105-b are shown as performing operations of process flow 500, some aspects of some operations may also be performed by one or more other wireless devices.

[0124] At 505, the network entity 105-b may send control signaling to the UE 115-b. The control signaling may indicate a first scheduling request resource on a first cell (e.g., a SpCell or some other type of cell) and a second scheduling request resource on a second cell (e.g., a SCell or some other type of cell). The control signaling may additionally or alternatively indicate a scheduling request ID for the first scheduling request resource and the second scheduling request resource, as described in reference to FIG. Figure 3 and Figure 4 described.

[0125] At 510, UE 115-b may generate a scheduling request. Both a first scheduling request resource on the first cell and a second scheduling request resource on the second cell may be applicable to the scheduling request. For example, UE 115-b may generate a scheduling request based on a scheduling request ID indicated via control signaling, such that the same scheduling request ID may be applicable to the scheduling request and the first scheduling request resource and the second scheduling request resource.

[0126] At 515, UE 115-b may select one of the scheduling request resources for sending the scheduling request. UE 115-b may select the scheduling request resource based on one or more of a power mode of UE 115-b, a signal metric associated with the cell, or a parameter set for the cell. In some aspects, UE 115 may operate in a reduced power mode. In this case, the scheduling request resource selection may be based on UE 115-b operating in a reduced power mode and the type of cell associated with the selected scheduling request resource (e.g., SpCell).

[0127] In some other aspects, UE 115-b may receive one or more reference signals from network entity 105-b via the first cell and the second cell. UE 115-b may measure signal metrics associated with the first cell and the second cell based on the one or more reference signals, and UE 115-b may select a scheduling request resource based on the measured signal metric levels. In some other aspects, UE 115-b may select the first scheduling request resource based on a parameter set for the first cell being greater than a parameter set for the second cell.

[0128] The selection of the scheduling request resource may be based on the first cell and the second cell being associated with the same scheduling request ID as the scheduling request. The first scheduling request resource and the second scheduling request resource may not overlap in time or may at least partially overlap in time, as shown in reference Figure 3 and Figure 4 described.

[0129] At 520, UE 115-b may send a scheduling request to network entity 105-b via the selected scheduling request resource on the corresponding cell. The scheduling request may be sent according to a first transmit power that may be based on a value of a signal metric of the cell. For example, if the signal metric is relatively high, the scheduling request may be sent at a relatively low transmit power.

[0130] Figure 6 A block diagram 600 of a device 605 supporting uplink control channel resource selection for scheduling request transmission according to one or more aspects of the present disclosure is shown. The device 605 can be an example of aspects of a UE 115 as described herein. The device 605 can include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0131] The receiver 610 may provide means for receiving information such as packets associated with various information channels (e.g., control channels related to uplink control channel resource selection for scheduling request transmissions, data channels, information channels), user data, control information, or any combination thereof. The information may be communicated to other components of the device 605. The receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0132] The transmitter 615 may provide means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information such as packets associated with various information channels (e.g., control channels related to uplink control channel resource selection for scheduling request transmissions, data channels, information channels), user data, control information, or any combination thereof. In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0133] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of uplink control channel resource selection for scheduling request transmission as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may support methods for performing one or more of the functions described herein.

[0134] In some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports means for performing the functions described in the present disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0135] Additionally or alternatively, in some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0136] In some examples, communication manager 620 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 610, transmitter 615, or both. For example, communication manager 620 can receive information from receiver 610, transmit information to transmitter 615, or integrate in conjunction with receiver 610, transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0137] According to the examples disclosed herein, the communication manager 620 may support wireless communications at the UE. For example, the communication manager 620 may be configured to or otherwise support a component for receiving control signaling indicating a first scheduling request resource on a first cell and a second scheduling request resource on a second cell. The communication manager 620 may be configured to or otherwise support a component for generating a scheduling request at the UE, wherein both the first scheduling request resource on the first cell and the second scheduling request resource on the second cell are applicable to the scheduling request. The communication manager 620 may be configured to or otherwise support a component for selecting a first scheduling request resource for sending a scheduling request on the first cell based on one or more of the following: a power mode of the UE, a signal metric associated with the first cell, or a parameter set of the first cell. The communication manager 620 may be configured to or otherwise support a component for sending a scheduling request via a first scheduling request resource on the first cell based on the selection.

[0138] By including or configuring the communication manager 620 according to the examples described herein, the device 605 (e.g., a processor that controls or otherwise couples with the receiver 610, the transmitter 615, the communication manager 620, or a combination thereof) can support techniques for reduced processing, reduced power consumption, and more efficient use of communication resources, as well as other advantages. For example, by selecting a scheduling request resource based on one or more of a power mode of the device 605 (e.g., a UE), a signal metric level of a corresponding cell, and a parameter set of the corresponding cell, the device 605 can select a reliable resource. For example, the selected resource may be located on a cell associated with an increased transmit power, which may improve the reliability of the transmission, or the selected resource may be located on a cell associated with a larger parameter set and may reduce the latency of the transmission, or both. Therefore, the processor of the device 605 can reduce processing associated with retransmissions that may occur if the resource is randomly selected, reduce power consumption, improve communication reliability, and improve throughput by selecting a scheduling request resource according to the described techniques.

[0139] Figure 7 A block diagram 700 of a device 705 supporting uplink control channel resource selection for scheduling request transmission according to one or more aspects of the present disclosure is shown. The device 705 can be an example of aspects of the device 605 or UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0140] The receiver 710 may provide means for receiving information such as packets associated with various information channels (e.g., control channels related to uplink control channel resource selection for scheduling request transmissions, data channels, information channels), user data, control information, or any combination thereof. The information may be communicated to other components of the device 705. The receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0141] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information such as packets associated with various information channels (e.g., control channels related to uplink control channel resource selection for scheduling request transmissions, data channels, information channels), user data, control information, or any combination thereof. In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0142] The device 705 or its various components may be examples of components for performing various aspects of uplink control channel resource selection for scheduling request transmission as described herein. For example, the communication manager 720 may include a control signaling component 725, a scheduling request generation component 730, a resource selection component 735, or any combination thereof. The communication manager 720 may be an example of various aspects of the communication manager 620 as described herein. In some examples, the communication manager 720 or its various components may be configured to use or otherwise cooperate with the receiver 710, the transmitter 715, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 720 may receive information from the receiver 710, transmit information to the transmitter 715, or be integrated with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0143] According to the examples disclosed herein, the communication manager 720 may support wireless communication at the UE. The control signaling component 725 may be configured to or otherwise support a component for receiving control signaling indicating a first scheduling request resource on a first cell and a second scheduling request resource on a second cell. The scheduling request generation component 730 may be configured to or otherwise support a component for generating a scheduling request at the UE, wherein both the first scheduling request resource on the first cell and the second scheduling request resource on the second cell are applicable to the scheduling request. The resource selection component 735 may be configured to or otherwise support a component for selecting a first scheduling request resource for sending a scheduling request on the first cell based on one or more of the following: a power mode of the UE, a signal metric associated with the first cell, or a parameter set of the first cell. The scheduling request generation component 730 may be configured to or otherwise support a component for sending a scheduling request via a first scheduling request resource on the first cell based on the selection.

[0144] Figure 8 A block diagram 800 of a communication manager 820 supporting uplink control channel resource selection for scheduling request transmission according to one or more aspects of the present disclosure is shown. The communication manager 820 can be an example of aspects of the communication manager 620, the communication manager 720, or both as described herein. The communication manager 820 or its various components can be examples of means for performing various aspects of uplink control channel resource selection for scheduling request transmission as described herein. For example, the communication manager 820 can include a control signaling component 825, a scheduling request generation component 830, a resource selection component 835, a reduced power component 840, a reference signal processing component 845, a signal metric component 850, a transmit power component 855, or any combination thereof. Each of these components can communicate with each other directly or indirectly (e.g., via one or more buses).

[0145] According to the examples disclosed herein, the communication manager 820 may support wireless communication at the UE. The control signaling component 825 may be configured to or otherwise support a component for receiving control signaling indicating a first scheduling request resource on a first cell and a second scheduling request resource on a second cell. The scheduling request generation component 830 may be configured to or otherwise support a component for generating a scheduling request at the UE, wherein both the first scheduling request resource on the first cell and the second scheduling request resource on the second cell are applicable to the scheduling request. The resource selection component 835 may be configured to or otherwise support a component for selecting a first scheduling request resource for the transmission of the scheduling request on the first cell based on one or more of the following: a power mode of the UE, a signal metric associated with the first cell, or a parameter set of the first cell. In some examples, the scheduling request generation component 830 may be configured to or otherwise support a component for sending a scheduling request via a first scheduling request resource on the first cell based on the selection.

[0146] In some examples, the reduced power component 840 may be configured as or otherwise support means for operating in a reduced power mode, wherein selecting the first scheduling request resource may be based on operating in the reduced power mode. In some examples, to support selecting the first scheduling request resource, the resource selection component 835 may be configured as or otherwise support means for selecting the first scheduling request resource based on a type of a first cell associated with the first scheduling request resource. In some examples, the type of the first cell is SpCell. In some examples, selecting the first scheduling request resource is based on the type of the first cell being SpCell.

[0147] In some examples, to support selection of the first scheduling request resource, resource selection component 835 may be configured to or otherwise support means for selecting the first scheduling request resource based on a signal metric associated with the first cell being greater than a second signal metric associated with the second cell.

[0148] In some examples, reference signal processing component 845 may be configured or otherwise support means for receiving one or more reference signals via the first cell and the second cell. In some examples, signal metric component 850 may be configured or otherwise support means for measuring a signal metric associated with the first cell and a second signal metric associated with the second cell based on the one or more reference signals, wherein selecting the first scheduling request resource may be based on the measurement.

[0149] In some examples, to support sending a scheduling request, the transmit power component 855 may be configured to or otherwise support a component for sending a scheduling request according to a first transmit power that is based on a value of a signal metric. In some examples, the signal metric and the second signal metric include an RSRP metric.

[0150] In some examples, to support selecting the first scheduling request resource, resource selection component 835 may be configured or otherwise support means for selecting the first scheduling request resource based on the parameter set of the first cell being greater than or equal to the parameter set of the second cell (e.g., the respective SCS of each cell). In some examples, the parameter set of the first cell and the parameter set of the second cell may be equal, and to support selecting the first scheduling request resource, resource selection component 835 may be configured or otherwise support means for selecting the first scheduling request resource based on the type of the first cell.

[0151] In some examples, the first scheduling request resource and the second scheduling request resource may at least partially overlap in time. In some examples, the first scheduling request resource and the second scheduling request resource may not overlap in time.

[0152] In some examples, the control signaling indicates the same scheduling request ID for the first scheduling request resource and the second scheduling request resource. In some examples, generating the scheduling request is based on the same scheduling request ID. In some examples, the selection is based on the first scheduling request resource and the second scheduling request resource being associated with the same scheduling request ID as the scheduling request.

[0153] Fig. 9 A diagram of a system 900 including a device 905 supporting uplink control channel resource selection for scheduling request transmission according to one or more aspects of the present disclosure is shown. The device 905 may be an example of a device 605, a device 705, or a UE 115 as described herein or include a component of these devices. The device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 905 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, a memory 930, a code 935, and a processor 940. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 945).

[0154] I / O controller 910 can manage input and output signals of device 905. I / O controller 910 can also manage peripheral devices that are not integrated into device 905. In some cases, I / O controller 910 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 can utilize an operating system such as or another known operating system. Additionally or alternatively, I / O controller 910 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 910 may be implemented as part of a processor such as processor 940. In some cases, a user may interact with device 905 via I / O controller 910 or via hardware components controlled by I / O controller 910.

[0155] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have more than one antenna 925, which can send or receive multiple wireless transmissions concurrently. The transceiver 915 can communicate bidirectionally via one or more antennas 925, wired or wireless links as described herein. For example, the transceiver 915 may represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 915 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 925 for transmission, and demodulating packets received from one or more antennas 925. The transceiver 915 or the transceiver 915 and one or more antennas 925 can be examples of transmitters 615, transmitters 715, receivers 610, receivers 710, or any combination or components thereof as described herein.

[0156] The memory 930 may include random access memory (RAM) and read-only memory (ROM). The memory 930 may store computer-readable, computer-executable code 935 including instructions that, when executed by the processor 940, cause the device 905 to perform various functions described herein. The code 935 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 935 may not be directly executable by the processor 940, but may cause the computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, the memory 930 may contain a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0157] The processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 930) to enable the device 905 to perform various functions (e.g., functions or tasks that support uplink control channel resource selection for scheduling request transmission). For example, the device 905 or a component of the device 905 may include a processor 940 and a memory 930 coupled to or coupled to the processor 940, and the processor 940 and the memory 930 are configured to perform the various functions described herein.

[0158] According to the examples disclosed herein, the communication manager 920 may support wireless communication at the UE. For example, the communication manager 920 may be configured to or otherwise support a component for receiving control signaling indicating a first scheduling request resource on a first cell and a second scheduling request resource on a second cell. The communication manager 920 may be configured to or otherwise support a component for generating a scheduling request at the UE, wherein both the first scheduling request resource on the first cell and the second scheduling request resource on the second cell are applicable to the scheduling request. The communication manager 920 may be configured to or otherwise support a component for selecting a first scheduling request resource for sending a scheduling request on the first cell based on one or more of the following: a power mode of the UE, a signal metric associated with the first cell, or a parameter set of the first cell. The communication manager 920 may be configured to or otherwise support a component for sending a scheduling request via a first scheduling request resource on the first cell based on the selection.

[0159] By including or configuring the communication manager 920 according to examples as described herein, the device 905 can support techniques for improved communication reliability, reduced latency, reduced power consumption, more efficient use of communication resources, improved inter-device coordination, and longer battery life, among other advantages.

[0160] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 915, one or more antennas 925, or any combination thereof. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 may include instructions that are executable by the processor 940 to cause the device 905 to perform various aspects of uplink control channel resource selection for scheduling request transmission as described herein, or the processor 940 and the memory 930 may be otherwise configured to perform or support such operations.

[0161] Fig.10 A flow chart illustrating a method 1000 for supporting uplink control channel resource selection for scheduling request transmission according to one or more aspects of the present disclosure is shown. The operations of the method 1000 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1000 may be implemented by a UE or a component thereof as described herein. Figures 1 to 9 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0162] At 1005, the method may include receiving control signaling indicating a first scheduling request resource on the first cell and a second scheduling request resource on the second cell. The operations of 1005 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1005 may be performed as described in reference to Figure 8 The control signaling component 825 is used to execute.

[0163] At 1010, the method may include generating a scheduling request at the UE, wherein both a first scheduling request resource on the first cell and a second scheduling request resource on the second cell are applicable to the scheduling request. The operations of 1010 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1010 may be performed as described in reference to Figure 8 The scheduling request generation component 830 is executed.

[0164] At 1015, the method may include: selecting a first scheduling request resource for transmission of the scheduling request on the first cell based on one or more of: a power mode of the UE, a signal metric associated with the first cell, or a parameter set of the first cell. The operations of 1015 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1015 may be performed as described in reference to Figure 8The described resource selection component 835 is executed.

[0165] At 1020, the method may include: sending a scheduling request via a first scheduling request resource on the first cell based on the selection. The operations of 1020 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1020 may be performed as described in reference to Figure 8 The scheduling request generation component 830 is executed.

[0166] Fig.11 A flow chart illustrating a method 1100 for supporting uplink control channel resource selection for scheduling request transmission according to one or more aspects of the present disclosure is shown. The operations of the method 1100 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1100 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0167] At 1105, the method may include receiving control signaling indicating a first scheduling request resource on the first cell and a second scheduling request resource on the second cell. The operations of 1105 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1105 may be performed as described in reference to Figure 8 The control signaling component 825 is used to execute.

[0168] At 1110, the method may include generating a scheduling request at the UE, wherein both a first scheduling request resource on the first cell and a second scheduling request resource on the second cell are applicable to the scheduling request. The operations of 1110 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1110 may be performed as described in reference to Figure 8 The scheduling request generation component 830 is executed.

[0169] At 1115, the method may include operating in a reduced power mode. In some aspects, the UE may switch to operate in a reduced power mode, or the UE may continue to operate in a reduced power mode. The operations of 1115 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1115 may be performed as described in reference to Figure 8 The reduced power component 840 is implemented.

[0170] At 1120, the method may include: selecting a first scheduling request resource for sending a scheduling request on the first cell based on the UE operating in a reduced power mode. The operations of 1120 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1120 may be performed as described in reference to Figure 8 The resource selection component 835 is executed.

[0171] At 1125, the method may include: sending a scheduling request via a first scheduling request resource on the first cell based on the selection. The operations of 1125 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1125 may be performed as described in reference to Figure 8 The scheduling request generation component 830 is executed.

[0172] Fig.12 A flow chart illustrating a method 1200 for supporting uplink control channel resource selection for scheduling request transmission according to one or more aspects of the present disclosure is shown. The operations of the method 1200 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1200 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0173] At 1205, the method may include receiving control signaling indicating a first scheduling request resource on the first cell and a second scheduling request resource on the second cell. The operations of 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1205 may be performed as described in reference to Figure 8 The control signaling component 825 is used to execute.

[0174] At 1210, the method may include generating a scheduling request at the UE, wherein both a first scheduling request resource on the first cell and a second scheduling request resource on the second cell are applicable to the scheduling request. The operations of 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1210 may be performed as described in reference to Figure 8 The scheduling request generation component 830 is executed.

[0175] At 1215, the method may include: receiving one or more reference signals via the first cell and the second cell. The operations of 1215 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1215 may be performed by Figure 8 The reference signal processing component 845 is used to perform.

[0176] At 1220, the method may include measuring a signal metric associated with the first cell and a second signal metric associated with the second cell based on the one or more reference signals. The operations of 1220 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1220 may be performed by Figure 8 The signal measurement component 850 is used to perform.

[0177] At 1225, the method may include: selecting a first scheduling request resource for the transmission of the scheduling request on the first cell based on the signal metric associated with the first cell being greater than the second signal metric associated with the second cell. The operations of 1225 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1225 may be performed as described in reference to Figure 8 The resource selection component 835 is executed.

[0178] At 1230, the method may include: sending a scheduling request via a first scheduling request resource on the first cell based on the selection. The operations of 1230 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1230 may be performed as described in reference to Figure 8 The scheduling request generation component 830 is executed.

[0179] The following provides an overview of various aspects of the disclosure:

[0180] Aspect 1: A method for performing wireless communications at a UE, comprising: receiving control signaling indicating a first scheduling request resource on a first cell and a second scheduling request resource on a second cell; generating a scheduling request at the UE, wherein both the first scheduling request resource on the first cell and the second scheduling request resource on the second cell are applicable to the scheduling request; selecting the first scheduling request resource for sending the scheduling request on the first cell based at least in part on one or more of the following: a power mode of the UE, a signal metric associated with the first cell, or a parameter set of the first cell; and sending the scheduling request via the first scheduling request resource on the first cell based at least in part on the selection.

[0181] Aspect 2: The method according to aspect 1 also includes: operating in a reduced power mode, wherein selecting the first scheduling request resource is at least partially based on operating in the reduced power mode.

[0182] Aspect 3: The method according to aspect 2, wherein selecting the first scheduling request resource includes: selecting the first scheduling request resource based at least in part on a type of the first cell associated with the first scheduling request resource.

[0183] Aspect 4: The method according to aspect 3, wherein the type of the first cell is SpCell; and the first scheduling request resource is selected at least in part based on the type of the first cell being the SpCell.

[0184] Aspect 5: The method according to aspect 1, wherein selecting the first scheduling request resource includes: selecting the first scheduling request resource based at least in part on the signal metric associated with the first cell being greater than a second signal metric associated with the second cell.

[0185] Aspect 6: The method according to Aspect 5 further includes: receiving one or more reference signals via the first cell and the second cell; and measuring the signal metric associated with the first cell and the second signal metric associated with the second cell based at least in part on the one or more reference signals, wherein selecting the first scheduling request resource is based at least in part on the measurement.

[0186] Aspect 7: The method according to any one of aspects 5 to 6, wherein sending the scheduling request comprises: sending the scheduling request according to a first transmit power, the first transmit power being based at least in part on the value of the signal metric.

[0187] Aspect 8: The method according to any one of aspects 5 to 7, wherein the signal metric and the second signal metric include RSRP metrics.

[0188] Aspect 9: The method according to aspect 1, wherein selecting the first scheduling request resource includes: selecting the first scheduling request resource at least in part based on the parameter set of the first cell being greater than or equal to the parameter set of the second cell.

[0189] Aspect 10: A method according to aspect 9, wherein the parameter set of the first cell and the parameter set of the second cell are equal, and wherein selecting the first scheduling request resource includes: selecting the first scheduling request resource at least in part based on the type of the first cell.

[0190] Aspect 11: The method according to any one of aspects 1 to 10, wherein the first scheduling request resource and the second scheduling request resource at least partially overlap in time.

[0191] Aspect 12: The method according to any one of aspects 1 to 10, wherein the first scheduling request resource and the second scheduling request resource do not overlap in time.

[0192] Aspect 13: A method according to any one of Aspects 1 to 12, wherein: the control signaling indicates the same scheduling request ID used for the first scheduling request resource and the second scheduling request resource; generating the scheduling request is at least partially based on the same scheduling request ID; and the selection is at least partially based on the first scheduling request resource and the second scheduling request resource being associated with the same scheduling request ID as the scheduling request.

[0193] Aspect 14: An apparatus for performing wireless communications at a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 13.

[0194] Aspect 15: An apparatus for performing wireless communication at a UE, comprising: at least one component for performing the method according to any one of aspects 1 to 13.

[0195] Aspect 16: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 13.

[0196] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0197] Although aspects of LTE, LTE-A, LTE-APro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-APro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-APro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0198] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0199] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0200] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium, or sent on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0201] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that promotes computer program to be transmitted from one place to another.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code member and can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure Any other non-transient medium.In addition, any connection is appropriately referred to as computer-readable medium.For example, when using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave to send software from website, server or other remote sources, coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, includes CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0202] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on".

[0203] The term "determining" encompasses a wide variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database, or another data structure), ascertaining, and similar actions. Furthermore, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), and similar actions. Furthermore, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0204] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. When only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label regardless of the second reference label or other subsequent reference labels.

[0205] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration" and does not mean "preferred" or "having advantages over other examples". The specific implementation includes specific details to provide an understanding of the technology. However, the technologies may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples.

[0206] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a user equipment (UE), include: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving control signaling indicating a first scheduling request resource on a first cell and a second scheduling request resource on a second cell; generating a scheduling request at the UE, wherein both the first scheduling request resource on the first cell and the second scheduling request resource on the second cell are applicable to the scheduling request; selecting the first scheduling request resource for transmission of the scheduling request on the first cell based at least in part on one or more of: a power mode of the UE, a signal metric associated with the first cell, or a parameter set for the first cell; as well as The scheduling request is sent via the first scheduling request resource on the first cell based at least in part on the selection.

2. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: Operating in a reduced power mode, wherein selecting the first scheduling request resource is based at least in part on operating in the reduced power mode.

3. The apparatus of claim 2, wherein the instructions to select the first scheduling request resource are executable by the processor to cause the apparatus to: The first scheduling request resource is selected based at least in part on a type of the first cell associated with the first scheduling request resource.

4. The device according to claim 3, in: The type of the first cell is a primary cell in a primary or secondary cell group; and Selecting the first scheduling request resource is based at least in part on the type of the first cell being the primary cell in the primary or secondary cell group.

5. The apparatus of claim 1 , wherein the instructions to select the first scheduling request resource are executable by the processor to cause the apparatus to: The first scheduling request resource is selected based at least in part on the signal metric associated with the first cell being greater than a second signal metric associated with the second cell.

6. The apparatus of claim 5, wherein the instructions are further executable by the processor to cause the apparatus to: receiving one or more reference signals via the first cell and the second cell; and The signal metric associated with the first cell and the second signal metric associated with the second cell are measured based at least in part on the one or more reference signals, wherein selecting the first scheduling request resource is based at least in part on the measurements.

7. The apparatus of claim 5, wherein the instructions to send the scheduling request are executable by the processor to cause the apparatus to: The scheduling request is transmitted according to a first transmit power based at least in part on a value of the signal metric.

8. The apparatus of claim 5, wherein the signal metric and the second signal metric comprise a reference signal received power metric.

9. The apparatus of claim 1, wherein the instructions to select the first scheduling request resource are executable by the processor to cause the apparatus to: The first scheduling request resource is selected based at least in part on the set of parameters for the first cell being greater than or equal to a set of parameters for the second cell.

10. The apparatus of claim 9, wherein the parameter set of the first cell and the parameter set of the second cell are equal, and wherein the instructions to select the first scheduling request resource are executable by the processor to cause the apparatus to: The first scheduling request resource is selected based at least in part on a type of the first cell.

11. The apparatus of claim 1, wherein the first scheduling request resource and the second scheduling request resource at least partially overlap in time.

12. The apparatus of claim 1, wherein the first scheduling request resource and the second scheduling request resource do not overlap in time.

13. The device according to claim 1, in: The control signaling indicates a same scheduling request identifier for the first scheduling request resource and the second scheduling request resource; generating the scheduling request based at least in part on the same scheduling request identifier; and The selecting is based at least in part on the first scheduling request resource and the second scheduling request resource both being associated with the same scheduling request identifier as the scheduling request.

14. A method for wireless communication at a user equipment (UE), include: receiving control signaling indicating a first scheduling request resource on a first cell and a second scheduling request resource on a second cell; generating a scheduling request at the UE, wherein both the first scheduling request resource on the first cell and the second scheduling request resource on the second cell are applicable to the scheduling request; selecting the first scheduling request resource for transmission of the scheduling request on the first cell based at least in part on one or more of: a power mode of the UE, a signal metric associated with the first cell, or a parameter set for the first cell; as well as The scheduling request is sent via the first scheduling request resource on the first cell based at least in part on the selection.

15. The method according to claim 14, further comprising: include: Operating in a reduced power mode, wherein selecting the first scheduling request resource is based at least in part on operating in the reduced power mode.

16. The method of claim 15, wherein the first scheduling request resource is selected include: The first scheduling request resource is selected based at least in part on a type of the first cell associated with the first scheduling request resource.

17. The method according to claim 16, in: The type of the first cell is a primary cell in a primary or secondary cell group; and Selecting the first scheduling request resource is based at least in part on the type of the first cell being the primary cell in the primary or secondary cell group.

18. The method of claim 14, wherein the first scheduling request resource is selected include: The first scheduling request resource is selected based at least in part on the signal metric associated with the first cell being greater than a second signal metric associated with the second cell.

19. The method according to claim 18, further comprising: include: receiving one or more reference signals via the first cell and the second cell; as well as The signal metric associated with the first cell and the second signal metric associated with the second cell are measured based at least in part on the one or more reference signals, wherein selecting the first scheduling request resource is based at least in part on the measurements.

20. The method of claim 18, wherein sending the scheduling request include: The scheduling request is transmitted according to a first transmit power based at least in part on a value of the signal metric.

21. The method of claim 18, wherein the signal metric and the second signal metric comprise a reference signal received power metric.

22. The method of claim 14, wherein the first scheduling request resource is selected include: The first scheduling request resource is selected based at least in part on the set of parameters for the first cell being greater than or equal to a set of parameters for the second cell.

23. The method of claim 22, wherein the parameter set of the first cell and the parameter set of the second cell are equal, and wherein the first scheduling request resource is selected include: The first scheduling request resource is selected based at least in part on a type of the first cell.

24. The method of claim 14, wherein the first scheduling request resource and the second scheduling request resource at least partially overlap in time.

25. The method of claim 14, wherein the first scheduling request resource and the second scheduling request resource do not overlap in time.

26. The method according to claim 14, in: The control signaling indicates a same scheduling request identifier for the first scheduling request resource and the second scheduling request resource; generating the scheduling request based at least in part on the same scheduling request identifier; and The selecting is based at least in part on the first scheduling request resource and the second scheduling request resource both being associated with the same scheduling request identifier as the scheduling request.

27. An apparatus for wireless communication at a user equipment (UE), include: means for receiving control signaling indicating a first scheduling request resource on a first cell and a second scheduling request resource on a second cell; means for generating a scheduling request at the UE, wherein both the first scheduling request resources on the first cell and the second scheduling request resources on the second cell are applicable to the scheduling request; means for selecting the first scheduling request resource for transmission of the scheduling request on the first cell based at least in part on one or more of: a power mode of the UE, a signal metric associated with the first cell, or a parameter set for the first cell; and Means for sending the scheduling request via the first scheduling request resource on the first cell based at least in part on the selection.

28. The device according to claim 27, further comprising: include: Means for operating in a reduced power mode, wherein selecting the first scheduling request resource is based at least in part on operating in the reduced power mode.

29. The apparatus of claim 28, wherein the means for selecting the first scheduling request resource include: Means for selecting the first scheduling request resource based at least in part on a type of the first cell associated with the first scheduling request resource.

30. A non-transitory computer-readable medium storing code for wireless communication at a user equipment (UE), the code comprising instructions executable by a processor to: receiving control signaling indicating a first scheduling request resource on a first cell and a second scheduling request resource on a second cell; generating a scheduling request at the UE, wherein both the first scheduling request resource on the first cell and the second scheduling request resource on the second cell are applicable to the scheduling request; selecting the first scheduling request resource for transmission of the scheduling request on the first cell based at least in part on one or more of: a power mode of the UE, a signal metric associated with the first cell, or a parameter set for the first cell; and The scheduling request is sent via the first scheduling request resource on the first cell based at least in part on the selection.