Search space set configuration for a pair of downlink and uplink cells

Abstract

Methods, systems, and apparatus for conducting wireless communication are described. A user equipment (UE) can receive indications of search space set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell comprising an uplink-only cell and the second cell comprising a downlink-only cell. The UE can receive permission to schedule uplink transmissions via the first cell using the uplink carrier, downlink transmissions via the second cell using the downlink carrier, or both, based on the search space set parameters and received via the downlink carrier of the second cell or a second downlink carrier associated with a third cell. The UE can perform uplink transmissions, receive downlink transmissions, or both, based on the permission.

Description

Cross-references

[0001] This patent application claims the benefit of U.S. Patent Application No. 18 / 501,385, filed November 3, 2023, entitled “SEARCH SPACESET CONFIGURATION FOR A PAIR OF DOWNLINK AND UPLINK CELLS”, which has been assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0002] This disclosure relates to wireless communications, including the configuration of a search space set for a pair of downlink cells and uplink cells. Background Technology

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

[0004] The described technology relates to improved methods, systems, devices, and apparatuses for configuring search space (SS) sets for a pair of downlink and uplink cells. For example, the described technology provides various mechanisms for saving resources when configuring a user equipment (UE) using a pair of uplink-only and downlink-only cells. The UE can receive indications of parameters for SS sets for a first cell (uplink-only cell, without downlink carrier) and a second cell (downlink-only cell, without uplink carrier) with downlink carriers. The SS set parameters can be a shared or common SS set, as the UE monitors the same SS set to obtain permission for the configured cell. The UE can receive permission to schedule uplink transmissions to the first cell (the uplink-only cell) or downlink transmissions from the second cell (the downlink-only cell) using the shared or common SS set. The UE can perform the uplink transmission or receive the downlink transmission based on the permission.

[0005] A method for wireless communication by a UE is described. The method may include: receiving indications of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell including an uplink-only cell and the second cell including a downlink-only cell; receiving permission to schedule uplink transmissions via the first cell using the uplink carrier, downlink transmissions via the second cell using the downlink carrier, or both, the permission being received based on the SS set parameters and via the downlink carrier of the second cell or a second downlink carrier associated with a third cell; and performing the uplink transmission, receiving the downlink transmission, or both, based on the permission.

[0006] A UE for wireless communication is described. The UE may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code so that the UE: receives indications of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell including an uplink-only cell and the second cell including a downlink-only cell; receives permission to schedule uplink transmissions via the first cell using the uplink carrier, downlink transmissions via the second cell using the downlink carrier, or both, the permission being received based on the SS set parameters and via the downlink carrier of the second cell or a second downlink carrier associated with a third cell; and performs the uplink transmission, receives the downlink transmission, or both, based on the permission.

[0007] Another UE for wireless communication is described. The UE may include: components for receiving indications of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell including an uplink-only cell and the second cell including a downlink-only cell; components for receiving permission to schedule uplink transmissions via the first cell using the uplink carrier, downlink transmissions via the second cell using the downlink carrier, or both, the permission being received based on the SS set parameters and via the downlink carrier of the second cell or a second downlink carrier associated with a third cell; and components for performing the uplink transmission, receiving the downlink transmission, or both, based on the permission.

[0008] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: receive indications of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell including an uplink-only cell and the second cell including a downlink-only cell; receive permission to schedule uplink transmissions using the uplink carrier via the first cell, downlink transmissions using the downlink carrier via the second cell, or both, the permission being received based on the SS set parameters and via the downlink carrier of the second cell or a second downlink carrier associated with a third cell; and perform the uplink transmission, receive the downlink transmission, or both, based on the permission.

[0009] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving information identifying the first cell and the second cell as a cell pairing set, wherein the SS set parameters may be based on the cell pairing set.

[0010] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, receiving the grant may include operations, features, components, or instructions for the following actions: receiving a shared carrier indicator field (CIF) of the grant that may be associated with the first cell and the second cell, wherein the shared CIF indicates that the grant is scheduled for the uplink transmission via the first cell, the downlink transmission via the second cell, or both.

[0011] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, receiving the grant may include operations, features, components, or instructions for: receiving a first grant scheduled for uplink transmission via the first cell; and receiving a second grant scheduled for downlink transmission via the second cell, wherein a first number of information bits in the first grant and a second number of information bits in the second grant comprise the same number of information bits.

[0012] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication of the allocation of information bit size for scheduling the uplink transmission via the first cell and for scheduling the downlink transmission via the second cell, wherein the same number of information bits may be allocated based on the information bit size.

[0013] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, receiving the grant may include operations, features, components, or instructions for the following actions: receiving an indication of whether the grant is to schedule the uplink transmission via the first cell or the downlink transmission via the second cell.

[0014] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, receiving the permission may include operations, features, components, or instructions for monitoring the downlink carrier of the second cell, the second downlink carrier of the third cell, or the SS set on both, based on the SS set parameters.

[0015] In some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein, the SS set parameter identifies the set of control channel resources to be monitored for reception on the downlink carrier of the second cell or the second downlink carrier of the third cell.

[0016] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, the grant includes downlink control information (DCI) format 0_2 uplink grant, DCI format 1_2 downlink grant, or both.

[0017] In some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein, the first cell includes a non-downlink carrier cell, and the second cell includes a non-uplink carrier cell.

[0018] A method for wireless communication by a network entity is described. The method may include: sending to a UE an indication of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell including an uplink-only cell and the second cell including a downlink-only cell; sending permission for the UE to schedule uplink transmissions via the first cell using the uplink carrier, downlink transmissions via the second cell using the downlink carrier, or both, the permission being sent based on the SS set parameters and via the downlink carrier of the second cell or a second downlink carrier associated with a third cell; and receiving the uplink transmission from the UE, performing the downlink transmission to the UE, or both, based on the permission.

[0019] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code to cause the network entity to: send to a UE an indication of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell including an uplink-only cell and the second cell including a downlink-only cell; send permission for the UE to schedule uplink transmissions using the uplink carrier via the first cell, downlink transmissions using the downlink carrier via the second cell, or both, the permission being sent based on the SS set parameters and via the downlink carrier of the second cell or a second downlink carrier associated with a third cell; and receive the uplink transmission from the UE, perform the downlink transmission to the UE, or both, based on the permission.

[0020] Another network entity for wireless communication is described. This network entity may include: components for transmitting to a UE an indication of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell including an uplink-only cell and the second cell including a downlink-only cell; components for transmitting permission for the UE to schedule uplink transmissions via the first cell using the uplink carrier, downlink transmissions via the second cell using the downlink carrier, or both, the permission being transmitted based on the SS set parameters and via the downlink carrier of the second cell or a second downlink carrier associated with a third cell; and components for receiving the uplink transmission from the UE, performing the downlink transmission to the UE, or both, based on the permission.

[0021] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: send to a UE an indication of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell including an uplink-only cell and the second cell including a downlink-only cell; send permission for the UE to schedule uplink transmissions using the uplink carrier via the first cell, downlink transmissions using the downlink carrier via the second cell, or both, the permission being sent based on the SS set parameters and via the downlink carrier of the second cell or a second downlink carrier associated with a third cell; and receive the uplink transmission from the UE, perform the downlink transmission to the UE, or both, based on the permission.

[0022] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: sending information identifying the first cell and the second cell as a cell pairing set, wherein the SS set parameters may be based on the cell pairing set.

[0023] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, sending the permission may include operations, features, components, or instructions for: configuring the permission to indicate a shared CIF that can be associated with the first cell and the second cell, wherein the shared CIF indicates that the permission schedules the uplink transmission via the first cell, the downlink transmission via the second cell, or both.

[0024] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, transmitting the grant may include operations, features, components, or instructions for: transmitting a first grant for scheduling the uplink transmission via the first cell; and transmitting a second grant for scheduling the downlink transmission via the second cell, wherein a first number of information bits in the first grant and a second number of information bits in the second grant comprise the same number of information bits.

[0025] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending an indication of the allocation of information bit size for scheduling the uplink transmission via the first cell and for scheduling the downlink transmission via the second cell, wherein the same number of information bits may be allocated based on the information bit size.

[0026] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, sending the grant may include operations, features, components, or instructions for configuring the grant as an indication of whether the uplink transmission is scheduled via the first cell or the downlink transmission is scheduled via the second cell.

[0027] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, transmitting the grant may include operations, features, components, or instructions for transmitting the grant on the SS set of the second cell, the third cell, or both, based on the SS set parameters.

[0028] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the SS set parameter identifies the set of control channel resources to be monitored for reception on the downlink carrier of the second cell or the second downlink carrier of the third cell.

[0029] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the grant includes DCI format 0_2 uplink grant, DCI format 1_2 downlink grant, or both.

[0030] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first cell includes a non-downlink carrier cell, and the second cell includes a non-uplink carrier cell. Attached Figure Description

[0031] Figure 1 An example of a wireless communication system supported by one or more aspects of this disclosure for configuring a search space (SS) set for a pair of downlink cells and uplink cells is shown.

[0032] Figure 2 An example of a wireless communication system configured with an SS set for a pair of downlink cells and uplink cells, according to one or more aspects of this disclosure, is shown.

[0033] Figure 3 An example of a wireless communication system configured with an SS set for a pair of downlink cells and uplink cells, according to one or more aspects of this disclosure, is shown.

[0034] Figure 4 An example of a bit-size scheme for configuring an SS set for a pair of downlink cells and uplink cells, according to one or more aspects of this disclosure, is shown.

[0035] Figure 5 and Figure 6A block diagram of an apparatus that supports SS set configuration for a pair of downlink cells and uplink cells, according to one or more aspects of this disclosure, is shown.

[0036] Figure 7 A block diagram is shown that supports the configuration of a communication manager for a pair of downlink and uplink cell SS sets according to one or more aspects of this disclosure.

[0037] Figure 8 A diagram is shown of a system including an apparatus that supports SS set configuration for a pair of downlink cells and uplink cells, according to one or more aspects of this disclosure.

[0038] Figure 9 and Figure 10 A block diagram of an apparatus that supports SS set configuration for a pair of downlink cells and uplink cells, according to one or more aspects of this disclosure, is shown.

[0039] Figure 11 A block diagram is shown that supports the configuration of a communication manager for a pair of downlink and uplink cell SS sets according to one or more aspects of this disclosure.

[0040] Figure 12 A diagram is shown of a system including an apparatus that supports SS set configuration for a pair of downlink cells and uplink cells, according to one or more aspects of this disclosure.

[0041] Figures 13 to 17 A flowchart illustrating a method for configuring an SS set for a pair of downlink cells and uplink cells according to one or more aspects of this disclosure is shown. Detailed Implementation

[0042] Wireless networks can support configuring a downlink-only cell for a user equipment (UE), such as for downlink carrier aggregation communication with the UE. The UE can also be configured using an uplink-only cell, such as for uplink carrier aggregation with the UE. For example, the UE can be configured by the network using a primary cell with both uplink and downlink carriers, the downlink-only cell, or the uplink-only cell. Such networks can support cross-carrier scheduling, where the primary cell or the downlink-only cell sends permission to schedule uplink transmissions via the primary cell or the uplink-only cell, or permission to schedule downlink transmissions via the primary cell or the downlink-only cell. However, such techniques are inefficient because such permission is scheduled for communication individually on a per-cell basis.

[0043] The described technique provides several mechanisms for saving resources when configuring a UE using a pair of uplink-only cells and downlink-only cells. The UE can receive indications of parameters for a search space (SS) set for a first cell (uplink-only cell, without downlink carrier) and a second cell (downlink-only cell, without uplink carrier) with a downlink carrier. The SS set parameters can be a shared or common SS set, as the UE monitors the same SS set to obtain permission for the configured cell. The UE can receive permission to schedule uplink transmissions to the first cell (the uplink-only cell) or downlink transmissions from the second cell (the downlink-only cell) using the shared or common SS set. The UE can then perform the uplink transmission or receive the downlink transmission based on the permission.

[0044] The aspects of this disclosure are first described in the context of a wireless communication system. The aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to the configuration of an SS set for a pair of downlink cells and uplink cells.

[0045] Figure 1 An example of a wireless communication system 100 configured to support an SS set for a pair of downlink and uplink cells, according to one or more aspects of this disclosure, is shown. 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 under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0046] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, among other designations. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0047] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

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

[0049] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with 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, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

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

[0051] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, 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, a non-real-time RIC), a service management and orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0052] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities 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, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can 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 each can be at least partially controlled by CU 160. Alternatively or additionally, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0053] In some wireless communication systems (e.g., wireless communication system 100), the 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 core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 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 DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., 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 node 104) via supported access and backhaul links (e.g., backhaul communication link 120). 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 a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, 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 IAB node 104) may be configured to operate according to the techniques described herein.

[0054] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), 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, an 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), wherein the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, the CU 160 may communicate with the core network via an interface (which may be part of a backhaul link) and may communicate with other CU 160s (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be part of a backhaul link).

[0055] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability, 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 communicating with one or more child nodes (e.g., an IAB donor may relay UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the AN's relay chain or configuration, IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Therefore, the IAB-MT entity of IAB node 104 can provide a Uu interface for child IAB node 104 to receive signaling from parent IAB node 104, and the DU interface (e.g., DU 165) can provide a Uu interface for parent IAB node 104 to send signaling notifications to child IAB node 104 or UE 115.

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

[0057] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support SS set configurations for a pair of downlink and uplink cells as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

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

[0059] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0060] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a physical layer structure defined for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating 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 coordinating carrier operation, user data, or other signaling. Wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured using multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0061] In some examples, such as in carrier aggregation configurations, a carrier may also have acquisition signaling or control signaling to coordinate 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 identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

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

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

[0064] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case 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 decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0065] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, multiple BWPs can be used to configure UE 115. In some examples, a single BWP of a carrier can be active at a given time, and the communication of UE 115 can be constrained to one or more active BWPs.

[0066] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0067] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a 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 number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

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

[0069] Depending on the technology, carriers can be used to multiplex physical channels for communication. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., a Control Resource Set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESETs) can be configured for a set in UE 115. For example, one or more in UE 115 can monitor or search for control regions based on one or more SS sets to obtain control information, and each SS set can include one or more control channel candidates arranged in a cascaded manner with one or more aggregation levels. The aggregation level of the control channel candidates can refer to the amount 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 SS set may include a common SS set configured to send control information to multiple UEs 115 and a UE-specific SS set configured to send control information to a specific UE 115.

[0070] 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 (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may be from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be a building, a subset of buildings, or external space between or overlapping coverage areas 110, or may include buildings, subsets of buildings, or external space between or overlapping coverage areas.

[0071] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0072] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0073] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile 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 use the same or different radio access technologies to provide coverage for various coverage areas 110.

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

[0075] Some UE 115s (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with 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 acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115s may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0076] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115s include entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0077] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private 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 business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

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

[0079] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these. Vehicles may signal information related to traffic conditions, signaling, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0080] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), and may include at least one control plane entity (e.g., a Mobility Management Entity (MME), 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), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0081] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer waves in the High Frequency (HF) or Very High Frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0082] The wireless communication system 100 can also operate in the ultra-high frequency (SHF) region (also known as the centimeter band) in the range of 3 GHz to 30 GHz or in the extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz) (also known as the millimeter band) using the spectrum. In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmission, EHF transmission may experience even greater attenuation and a shorter range. The techniques disclosed herein can be adopted for transmission across one or more different frequency regions, and the frequency band usage specified across these frequency regions may vary by country or regulatory authority.

[0083] Wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be combined with component carriers operating with licensed frequency bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0084] 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 techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation 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, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include 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 transmitted via the antenna ports.

[0085] Network entity 105 or UE 115 can use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique is known as spatial multiplexing. The multiple signals can be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals can be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

[0086] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0087] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, 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 UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 along different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) the beam direction for later transmission or reception by network entity 105.

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

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

[0090] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a transmitting device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of reception beamforming weights (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of the antenna array; or processing the received signal according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these operations may be referred to as “listening” according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when a data signal is received). A single receiver configuration can be aligned along a beam direction determined based on listening according to different receiver 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).

[0091] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also implement error detection, error correction, or both to support retransmission and improve link efficiency. In the control plane, the RRC layer can provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 supporting user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0092] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0093] UE 115 can receive indications of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, wherein the first cell includes an uplink-only cell and the second cell includes a downlink-only cell. UE 115 can receive permission to schedule uplink transmissions via the first cell using the uplink carrier, downlink transmissions via the second cell using the downlink carrier, or both, based on the SS set parameters and received via the downlink carrier of the second cell or a second downlink carrier associated with a third cell. UE 115 can perform uplink transmissions, receive downlink transmissions, or both based on the permission granted.

[0094] Network entity 105 may send to UE 115 an indication of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, wherein the first cell includes an uplink-only cell and the second cell includes a downlink-only cell. Network entity 105 may send permission for UE 115 to schedule uplink transmissions via the first cell using the uplink carrier, downlink transmissions via the second cell using the downlink carrier, or both, based on the SS set parameters and via the downlink carrier of the second cell or a second downlink carrier associated with a third cell. Network entity 105 may, based on the permission, receive uplink transmissions from UE 115, perform downlink transmissions to UE 115, or both.

[0095] Figure 2An example of a wireless communication system 200 configured to support an SS set for a pair of downlink and uplink cells, according to one or more aspects of this disclosure, is shown. The wireless communication system 200 may implement aspects of the wireless communication system 100. The wireless communication system 200 may include a UE 205, network entity 210, network entity 215, and network entity 220, which may be examples of the corresponding devices described herein.

[0096] For example, network entity 210 may be an example of a PCell, SPCell, or SCell associated with uplink carrier 230 and downlink carrier 225. Network entity 215 may be an example of a first cell (e.g., SCell) associated with uplink carrier 235 (e.g., the first cell may be an uplink-only cell without a downlink carrier). Network entity 220 may be an example of a second cell (e.g., SCell) associated with downlink carrier 240 (e.g., the second cell may be a downlink-only cell without an uplink carrier).

[0097] In other words, network entity 210 can be the primary serving cell of UE 205. This can include network entity 210 scheduling communication with UE 205, such as downlink communication using downlink carrier 225 or uplink communication using uplink carrier 230. Network entity 215 (first cell) and network entity 220 (second cell) can be a pair of cells associated with UE 205, wherein each cell has an uplink carrier but no downlink carrier, or has a downlink carrier but no uplink carrier. UE 205 can be scheduled to perform uplink transmissions to network entity 215 via uplink carrier 235, or receive downlink transmissions from network entity 220 via downlink carrier 240. Network entity 215 can be an example of a secondary uplink carrier (SUL) cell configured for uplink transmissions from UE 205 or an example of an enhanced SUL (eSUL) cell. Network entity 220 may be an example of an auxiliary downlink (SDL) cell or an example of enhanced SDL (eSDL).

[0098] For example, when operating in connected mode, the eSUL can be configured as an uplink-only cell for uplink CA with cells that do not have a corresponding downlink carrier. The uplink-only cell can be scheduled by the PDCCH in other cells that have downlink carriers. In some examples, this can include cross-carrier / multi-carrier scheduling occurring between different cells. For example, wireless communication system 200 illustrates a non-limiting example of network entity 210 scheduling uplink or downlink communication using its associated uplink carrier 230 or downlink carrier 225, respectively, wherein network entity 220 schedules uplink transmissions to network entity 215 via uplink carrier 235 or downlink transmissions from network entity 220 via downlink carrier 240. Wireless communication system 300 illustrates a non-limiting example of a PCell (e.g., network entity 210) scheduling uplink or downlink communication for the PCell, the uplink-only cell, or the downlink-only cell.

[0099] When operating in idle mode, eSUL can be used for initial channel access (e.g., random access), such as using a System Information Block (SIB) on the downlink cell that carries uplink / eSUL configuration information for the random access procedure.

[0100] UE 205 typically monitors a set of SS elements to detect permission to schedule communications (e.g., PDCCH) for UE 205. For example, SS set parameters define the time resources, frequency resources, spatial resources, or code resources that UE 205 should monitor to detect PDCCH transmissions from cells with downlink carriers. For example, an SS set defines the set of continuous control channel elements (CCE) / resource element groups (REGs) that UE 205 should monitor for scheduling assignments / permissions related to CC. As discussed above, the SS set can be a common SS set or a UE-specific SS set. The SS set defines the control channel resources that UE 205 should monitor to receive PDCCH permission.

[0101] Some wireless networks allocate or otherwise configure SS sets for UEs in a given cell (e.g., on a per-serving-cell basis for UE 205). A single SS set configuration enables PDCCH monitoring for both downlink and uplink downlink control information (DCI) formats for the serving cell. For PCells, primary / secondary cells (PSCells), or SCells with both uplink and downlink carriers (e.g., network entity 210), this allows the network to configure UE 205 to monitor PDCCH candidates for both downlink and uplink scheduling DCI formats (e.g., on resources of the SS set). For SCells with only downlink carriers (e.g., for downlink CA but not uplink CA), UE 205 may not monitor the uplink DCI format in a downlink-only cell SS set configuration. That is, some wireless networks may not support uplink scheduling in downlink-only SCells.

[0102] These networks enable the configuration of a downlink-only cell (e.g., network entity 220) as an SCell for UE 205, where only the downlink cell supports downlink CA technology. Similarly, an uplink-only cell can be configured as an SCell for UE 205, where only the uplink cell supports uplink CA technology.

[0103] However, some wireless networks may be inefficient because unnecessary configuration and PDCCH monitoring may be performed. That is, typically, UE 205 is configured with SS set configuration (e.g., SS set parameters) and a carrier indicator field (CIF) for cross-carrier scheduling carried in the PDCCH grant on a per-cell basis. For example, in some networks, UE 205 may be configured using a first SS set for network entity 210 and a second SS set for network entity 220. UE 205 can monitor grants from each configured cell (e.g., monitor SS set resources) based on the SS set configured for the respective cell. In some examples, additional SS set configuration is configured for UE 205 to monitor grants scheduled to uplink transmissions to network entity 215 (e.g., from a third cell).

[0104] Therefore, in some networks, separate SS set configurations and CIF values ​​are used even for downlink-only cells and uplink-only cells. Thus, if UE 205 is configured using CA with cells #1, #2, and #3, where cell #1 has both downlink and uplink capabilities, cell #2 has only uplink capabilities, and cell #3 has only downlink capabilities, this could result in UE 205 being configured with three different SS set configurations and three different CIF values. UE 205 can monitor PDCCH candidates for three different serving cells on different SS sets. Furthermore, UE 205 can handle multiple DCI formats for each of the three serving cells (e.g., UE 205 may be able to handle three times the maximum number of DCI format sizes that UE 205 can handle per cell). Furthermore, if UE 205 reports limited PDCCH blind decoding (BD) / CCE capabilities (e.g., via the pdcch-BlindDetectionCA parameter), then a limited number of PDCCH BD / CCEs can be shared across SS sets used in three different serving cells.

[0105] Therefore, the aspects of the techniques described herein provide SS set configurations for a pair of downlink-only cells and uplink-only cells. These aspects provide a pair of downlink-only cells and uplink-only cells to share a single SS set configuration for both cells (e.g., shared SS set). In some examples, the pair of cells may be treated as a pair of spectrums, or as if it were an FDD cell.

[0106] For example, UE 205 may receive or otherwise obtain indications of SS set parameters for a PCell (e.g., network entity 210) associated with both uplink carrier 230 and downlink carrier 225. SS set parameters may identify the resources that UE 205 wants to monitor to receive permission from the PCell. For example, UE 205 may receive or otherwise obtain permission via downlink carrier 225 of network entity 210 (e.g., PDCCH 245). This permission may schedule downlink transmissions from network entity 210 to UE 205 via downlink carrier 225 (e.g., PDSCH 250), or may schedule uplink transmissions from UE 205 to network entity 210 via uplink carrier 230 (e.g., PUSCH 255). The SS set for a PCell / PSCell or for an SCell having both uplink and downlink carriers may be a common SS set or a UE-specific SS set.

[0107] UE 205 may also receive or otherwise obtain indications of SS set parameters for a first cell (e.g., network entity 215 with uplink carrier 235) having an uplink carrier or otherwise associated with an uplink carrier, and a second cell (e.g., network entity 220 with downlink carrier 240) having a downlink carrier or otherwise associated with a downlink carrier. The first cell may be an uplink-only cell, since network entity 215 does not have a downlink carrier. The second cell may be a downlink-only cell, since network entity 220 does not have an uplink carrier. SS set parameters may be shared SS resources that UE 205 needs to monitor to receive uplink transmissions scheduled to the first cell or downlink transmissions scheduled from the second cell.

[0108] UE 205 may also receive or otherwise obtain permission (e.g., PDCCH 260) for uplink transmissions (e.g., PUSCH 265) scheduled via a first cell (e.g., uplink transmission to network entity 215) or downlink transmissions (e.g., PDSCH 270) scheduled via a second cell (e.g., downlink transmission from network entity 220). Permission may be received based on SS set parameters. For example, permission may be received based on UE 205 monitoring an SS set. For example, SS set parameters may identify or otherwise indicate a set of control channel resources (e.g., PDCCH resources) to be monitored to receive permission. Permission may be received from a second cell using downlink carrier 240, or from a second downlink carrier associated with a third cell (such as downlink carrier 225 of the UE's PCell, e.g., ...). Figure 3 (As shown) Reception. Grant can be a DCI format 0_2 uplink grant, or a DCI format 1_2 downlink grant. UE 205 can perform uplink transmission to the first cell (e.g., UE 205 can perform PUSCH 265 transmission on uplink carrier 235) or receive downlink transmission from the second cell (e.g., UE 205 can receive PDSCH 270 on downlink carrier 240) based on the grant.

[0109] Therefore, the wireless communication system 200 illustrates a non-limiting example of SS set configuration provided for a pair of cells consisting of uplink-only cells (cells without downlink carriers) and downlink-only cells (cells without uplink carriers). Shared SS set configuration (e.g., SS set parameters) may be based on the cells being paired (e.g., considered as paired spectrum or FDD cells). In some examples, UE 205 may utilize information identifying the pair of cells (e.g., paired uplink-only cells and downlink-only cells) to configure or otherwise receive this information. For example, UE 205 may receive information identifying a first cell and a second cell as a cell pairing set. SS set parameters may be configured or paired cells. For example, RRC parameters may be indicated to UE 205, identifying which pairs of downlink-only cells and uplink-only cells are associated with each other.

[0110] In some examples, a shared CIF value can be used to schedule permission for communication via a cell pair set. For example, aspects of the techniques described herein can use the same CIF value to schedule permission received via an SS set. That is, a cell pair set can be considered a pair of cells sharing the SS set configuration and CIF value if the same CIF value is configured for downlink-only and uplink-only cells scheduled by the same cell. If the scheduled cells are a pair of downlink-only and uplink-only cells, the same CIF value is configured for different scheduled cells from the same scheduling cell. Therefore, in some examples, UE 205 can receive a CIF in permission associated with both the first cell and the second cell. A shared CIF (e.g., the same CIF value) can indicate permission to schedule uplink transmissions to the first cell, downlink transmissions from the second cell, or both. Additionally or alternatively, aspects of the techniques described herein may not use the CIF field to schedule permission received via an SS set. In other words, if the UE is configured using downlink-only and uplink-only cells scheduled by the same cell, and if no other cells are scheduled by the same cell, the cell pair set can be considered a pair of cells configured with a shared SS set that does not have a CIF field. Therefore, in some examples, UE 205 can receive permission without a CIF field associated with both the first and second cells.

[0111] In some examples, the bits of the identifier for the DCI format can be used to indicate whether uplink or downlink transmission is permitted to be scheduled. For example, each DCI format may include a single bit of the DCI format identifier. According to the techniques described herein, this identifier can be used to indicate whether, for a given pair of uplink-only cells and downlink-only cells, the DCI format is used for downlink scheduling on a downlink-only cell or for uplink scheduling on an uplink-only cell. For example, the value of this bit can be set to "0" to indicate an uplink DCI format, or set to "1" to indicate a downlink DCI format, and vice versa. Accordingly, UE 205 can receive an indication of whether uplink or downlink transmission is permitted to be scheduled. This indication can be provided via the identifier of the DCI format.

[0112] Therefore, the wireless communication system 200 illustrates a non-limiting example of pairing downlink-only cells and uplink-only cells for an SS set configuration. This reduces the number of cells (e.g., SS sets) that UE 205 must monitor (e.g., from three cells to two cells in this non-limiting example). This reduces the UE complexity regarding PDCCH monitoring (e.g., based on UE 205 monitoring fewer SS sets). The techniques described herein can further increase the PDCCH scheduling flexibility of the network.

[0113] Figure 3 An example of a wireless communication system 300 configured to support an SS set for a pair of downlink and uplink cells, according to one or more aspects of this disclosure, is shown. The wireless communication system 300 may implement aspects of wireless communication system 100 or wireless communication system 200. The wireless communication system 300 may include a UE 305, network entity 310, network entity 315, and network entity 320, which may be examples of the corresponding devices described herein.

[0114] For example, network entity 310 may be an example of a PCell, PSCell, or SCell associated with uplink carrier 330 and downlink carrier 325. Network entity 315 may be an example of a first cell (e.g., SCell) associated with uplink carrier 335 (e.g., the first cell may be an uplink-only cell without a downlink carrier). Network entity 320 may be an example of a second cell (e.g., SCell) associated with downlink carrier 340 (e.g., the second cell may be a downlink-only cell without an uplink carrier).

[0115] As discussed above, the wireless communication system 300 illustrates a non-limiting example of PCell (e.g., network entity 310) scheduling uplink or downlink communication for the PCell, uplink-only cells, or downlink-only cells. For example, aspects of the techniques described herein provide SS set configurations for a pair of downlink-only and uplink-only cells. The techniques described herein provide a pair of downlink-only and uplink-only cells to share a single SS set configuration for these two cells (e.g., shared SS set). In some examples, the pair of cells may be considered as a pair of spectrums, or as if it were an FDD cell. Figure 3 In the non-limiting example shown, the SS set used for the paired cell set can use the same control channel resources as the SS set used for the PCell. Instead, the CIF value can be used to indicate whether uplink or downlink communication is permitted to be scheduled via the PCell, or uplink or downlink communication is permitted to be scheduled via a paired set of uplink-only and downlink-only cells.

[0116] For example, UE 305 may receive or otherwise obtain indications of SS set parameters for a PCell (e.g., network entity 310) associated with both uplink carrier 330 and downlink carrier 325. However, the SS set can also be used to schedule permission for communication via a first cell (e.g., an uplink-only cell, such as network entity 315) or a second cell (e.g., a downlink-only cell, such as network entity 320). SS set parameters may identify the resources that UE 305 wants to monitor to receive permission from the PCell to schedule PCell communication or to schedule paired cell communication. For example, UE 305 may receive or otherwise obtain permission (e.g., PDCCH 345) via downlink carrier 325 of network entity 310. In this example, this could include UE 305 receiving permission on a second downlink carrier associated with a third cell (in this example, the third cell refers to network entity 310). This permits the scheduling of downlink transmissions from network entity 310 to UE 305 via downlink carrier 325 (e.g., PDSCH 350), or the scheduling of uplink transmissions from UE 305 to network entity 310 via uplink carrier 330 (e.g., PUSCH 355).

[0117] In some examples, the permission may be scheduled for uplink transmissions via a first cell (e.g., PUSCH360) (e.g., uplink transmissions to network entity 315) or for downlink transmissions via a second cell (e.g., PDSCH 365) (e.g., downlink transmissions from network entity 320). The permission may be received based on SS set parameters.

[0118] In some examples, a shared CIF value can be used to grant permission for communication to be scheduled via a set of cell pairs. For example, aspects of the techniques described herein may use the CIF value indicated in the permission to identify or otherwise indicate whether permission is being granted for communication to be scheduled via a PCell or for communication to be scheduled via a first cell or a second cell (e.g., a set of paired uplink-only cells and downlink-only cells). For example, the CIF value indicated in PDCCH 345 may be set to “0” to indicate permission is being granted for communication to be scheduled between UE 305 and network entity 310 via downlink carrier 340 or uplink carrier 335, or may be set to “1” to indicate permission is being granted for uplink transmissions to network entity 315 via uplink carrier 330 or downlink transmissions from network entity 320 via downlink carrier 325, and vice versa. Accordingly, UE 305 may detect the CIF value indicated in the grant and use the CIF value to identify or otherwise determine whether the grant is scheduling communication with a PCell (e.g., a PCell, PSCell, or SCell with both uplink and downlink carriers) or scheduling communication with a paired set of uplink-only and downlink-only cells (e.g., network entity 315 or network entity 320).

[0119] Figure 4 An example of a bit size scheme 400 supporting SS set configuration for a pair of downlink cells and uplink cells, according to one or more aspects of this disclosure, is shown. The bit size scheme 400 may implement aspects of wireless communication systems 100, 200, or 300. The aspects of the bit size scheme 400 may be implemented at or by a UE or network entity, which may be an example of the corresponding device described herein.

[0120] As discussed above, the aspects of the techniques described herein provide a set of SS (Side Messages) to be configured, which is shared between paired sets of uplink-only cells and downlink-only cells. For example, a UE may receive indications of SS set parameters for a first cell (uplink-only) and a second cell (downlink-only). The first cell may have an uplink carrier but no downlink carrier. The second cell may have a downlink carrier but no uplink carrier. The first and second cells can be paired cells because these cells can be considered or regarded as paired spectrum or FDD cells for scheduling purposes. The UE may monitor control channel resources (e.g., PDCCH resources) based on the SS set parameters to receive permission. Permission can be scheduled for uplink transmissions via the first cell using an uplink carrier or for downlink transmissions via the second cell using a downlink carrier. Permission can be received via a downlink carrier of the second cell or via a second downlink carrier of a third cell. For example, the SS set parameters may identify control channel resources for downlink carriers of the second cell, or the SS set parameters may identify control channel resources for downlink carriers of the PCell / PSCell. The UE may, upon authorization, perform uplink transmissions to the first cell using the uplink carrier, or receive downlink transmissions from the second cell.

[0121] Therefore, in some examples, the SS set parameters can be used to schedule uplink grants (e.g., first grants) for uplink transmissions via uplink carriers to a first cell, or to schedule downlink grants (e.g., second grants) for downlink transmissions via downlink carriers from a second cell. In some examples, uplink and downlink grants can be size-aligned (e.g., based on the number of information bits). That is, in some examples, a DCI size alignment process may be in operation, assuming that downlink DCIs (e.g., second grants) and uplink DCIs (e.g., first grants) from a pair of downlink-only and uplink-only cells from the same scheduling cell are size-aligned (e.g., treated as if these grants were for downlink and uplink carriers of the same serving cell).

[0122] For example, the scheduling cell or UE may receive or otherwise determine an indication of the allocation of information bit size (e.g., DCI size budget) to be used for scheduling uplink and downlink transmissions. The DCI size budget may define the same number of information bits for the first and second grants. Aligning the number of information bits in the first and second grants may be based on the DCI size budget (e.g., where necessary).

[0123] Bit size scheme 400 illustrates a non-limiting example of information bit size scheme 405, which can be used to schedule a first grant for uplink communication and a second grant for scheduling downlink communication for a set of paired uplink-only and downlink-only cells. Information bit size scheme 405 illustrates an example in which DCI format 0_0 for scheduling uplink transmissions to a first cell and DCI format 1_0 for scheduling downlink transmissions from a second cell can be size-aligned as necessary to meet a DCI size budget. Information bit size scheme 405 illustrates an example in which DCI format 0_1 ​​for scheduling uplink transmissions to a first cell and DCI format 1_1 for scheduling downlink transmissions from a second cell can be size-aligned as necessary to meet a DCI size budget. Information bit size scheme 405 illustrates an example in which DCI format 0_2 for scheduling uplink transmissions to a first cell and DCI format 1_2 for scheduling downlink transmissions from a second cell can be size-aligned as necessary to meet a DCI size budget. In other words, based on the allocation of information bits, the number of information bits in the first grant can be the same as the number of information bits in the second grant.

[0124] Specifically, information bit size scheme 405 illustrates non-limiting steps for aligning the sizes of the first and second grants to include the same number of information bits. Padding and truncation can be applied to the DCI format according to the steps performed in the indicated order (e.g., steps 0–4).

[0125] For example, at step 0, the network entity or UE may determine the size of the DCI format 0_0 to be used for scheduling uplink transmissions from the UE to the first cell (e.g., the number of information bits to be used). The size of the DCI (e.g., the number of information bits) may be based on a fixed number of bits (e.g., a known number of bits corresponding to time-domain resource allocation, MCS, and other parameters) and a variable number of information bits used to indicate other parameters (such as frequency-domain resource allocation). For reference, the size of DCI format 0_0 may be set to A (e.g., A information bits are included in DCI format 0_0 for uplink transmissions on uplink carriers of uplink-only cells). The network entity or UE may identify or otherwise determine that the number of information bits included in DCI format 1_0 for downlink transmissions on downlink carriers of downlink-only cells may also be set to A to size-align the DCI formats. If DCI format 1_0 has more bits, the number of information bits included in DCI format 0_0 can be filled; or if the frequency domain resource allocation in DCI format 1_0 has more bits than in DCI format 0_0, the bits can be truncated. DCI formats 0_0 and 1_0 discussed here can be monitored in a shared search space.

[0126] At step 1, the network entity or UE may determine the size of DCI formats 0_0 and 1_0 to be size B according to the techniques discussed above. However, here, DCI formats 0_0 and 1_0 may be DCIs monitored in a UE-specific search space. The network entity or UE may identify or otherwise determine that the number of information bits included in DCI format 1_0 transmitted on a downlink carrier of a downlink-only cell can be set to B in order to size-align the DCI format with DCI format 0_0. Similarly, padding or truncation may be applied to the DCI format to achieve size alignment.

[0127] At step 2, the network entity or UE may determine the size of DCI format 0_1 ​​for uplink transmission on the uplink carrier of a cell scheduled for uplink-only transmission, and the size of DCI format 1_1 for downlink transmission on the downlink carrier of a cell scheduled for downlink-only transmission. The number of information bits included in DCI formats 0_1 and 1_1 may again be based on a mixture of fixed bit sizes used to indicate various parameters and variable bit sizes used to indicate other parameters (e.g., such as frequency domain resource allocation bit sizes). The network entity or UE may align the number of information bits included in DCI formats 0_1 and 1_1 to be the same (e.g., size C / D).

[0128] At step 2A, the network entity or UE may determine the size of DCI format 0_2 for uplink transmission on the uplink carrier of a cell scheduled for uplink-only transmission, and the size of DCI format 1_2 for downlink transmission on the downlink carrier of a cell scheduled for downlink-only transmission. The number of information bits included in DCI formats 0_2 and 1_2 may again be based on a mixture of fixed bit sizes used to indicate various parameters and variable bit sizes used to indicate other parameters (e.g., frequency domain resource allocation bit sizes). The network entity or UE may align the number of information bits included in DCI formats 0_2 and 1_2 to be the same (e.g., size E / F).

[0129] At step 3, the network entity or UE may check two conditions to determine whether the size alignment process is complete. For example, the network entity or UE may identify or otherwise determine whether the total number of different DCI sizes the UE is configured to monitor does not exceed four for a cell (or does not exceed three for a DCI size with C-RNTI). If yes, the process is complete. If not, the process can proceed to the next step.

[0130] If the UE is configured to monitor more than four DCI sizes, at step 4A, the network entity or the UE may adjust the number of information bits included in DCI formats 0_0 and 1_0 to reduce the total number of different DCI sizes the UE needs to monitor. For example, if the number of information bits included in the search space for UE-specific DCI monitoring is greater than four, bits may be added or truncated to align the sizes of DCI formats 0_0 and 1_0 monitored in the UE-specific search space so that these UE-specific SS set DCI sizes (size B) are aligned with the common SS set DCI size (size A).

[0131] At step 4B, the network entity or UE may adjust the number of information bits included in DCI formats 0_2 and 1_2 to make these DCI formats size-aligned. For example, if DCI sizes E and F are not equal, bits may be padded or truncated (e.g., to align the DCI format sizes to the same size in order to reduce the number of different-sized DCI formats that the UE must monitor).

[0132] At step 4C, the network entity or UE may adjust the number of information bits included in DCI formats 0_1 and 1_1 to make these DCI formats size-aligned. For example, if DCI sizes C and D are not equal, bits may be padded or truncated (e.g., to align the DCI formats to the same size).

[0133] Therefore, information bit size scheme 405 illustrates non-limiting steps for aligning the sizes of the first and second grants to include the same number of information bits. The size alignment process also minimizes the number of different DCI sizes that the network entity needs to transmit and that the UE needs to monitor.

[0134] Figure 5 A block diagram 500 illustrates a device 505 configured to support an SS set for a pair of downlink and uplink cells according to one or more aspects of this disclosure. Device 505 may be an example of various aspects of UE 115 as described herein. Device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Device 505, or one or more components of device 505 (e.g., receiver 510, transmitter 515, and communication manager 520), may include at least one processor coupled to at least one memory and storing instructions in that at least one memory to individually or collectively support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0135] Receiver 510 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with the configuration of an SS set for a pair of downlink and uplink cells). The information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

[0136] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with the configuration of an SS set for a pair of downlink and uplink cells). In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0137] The communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the SS set configuration for a pair of downlink and uplink cells as described herein. For example, the communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0138] In some examples, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., executing instructions stored in at least one memory individually or collectively by one or more processors).

[0139] Additionally or alternatively, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be performed by any combination of a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0140] In some examples, the communication manager 520 may be configured to use or otherwise cooperate with the receiver 510, the transmitter 515, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 520 may receive information from the receiver 510, transmit information to the transmitter 515, or be integrated with the receiver 510, the transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0141] Communication manager 520 may support wireless communication according to examples disclosed herein. For example, communication manager 520 may be capable of, configured to, or operable to support components for receiving indications of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell comprising an uplink-only cell and the second cell comprising a downlink-only cell. Communication manager 520 may be capable of, configured to, or operable to support components for receiving authorization to schedule uplink transmissions using an uplink carrier via the first cell, downlink transmissions using a downlink carrier via the second cell, or both, based on SS set parameters and received via a downlink carrier of the second cell or a second downlink carrier associated with a third cell. Communication manager 520 may be capable of, configured to, or operable to support components for performing uplink transmissions, receiving downlink transmissions, or both, based on authorization.

[0142] By including or configuring a communication manager 520 according to an example as described herein, device 505 (e.g., controlling receiver 510, transmitter 515, communication manager 520 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for pairing sets of uplink-only cells and downlink-only cells to configure a set of SS that can be used to schedule the two cells.

[0143] Figure 6A block diagram 600 illustrates a device 605 configured to support an SS set for a pair of downlink and uplink cells, according to one or more aspects of this disclosure. Device 605 may be an example of aspects of device 505 or UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605, or one or more components of device 605 (e.g., receiver 610, transmitter 615, and communication manager 620), may include at least one processor coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0144] Receiver 610 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with the configuration of an SS set for a pair of downlink and uplink cells). The information may be passed to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

[0145] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with the configuration of an SS set for a pair of downlink and uplink cells). In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0146] Device 605 or its various components may be examples of parts for performing various aspects of SS set configuration for a pair of downlink and uplink cells as described herein. For example, communication manager 620 may include SS set manager 625, grant manager 630, transmit manager 635, or any combination thereof. Communication manager 620 may be examples of aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to use or otherwise cooperate with receiver 610, transmitter 615, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated with receiver 610, transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0147] Communication manager 620 may support wireless communication according to examples disclosed herein. SS set manager 625 is capable of, configured to, or operable to support components for receiving indications of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell comprising an uplink-only cell and the second cell comprising a downlink-only cell. Grant manager 630 is capable of, configured to, or operable to support components for receiving grants for scheduling uplink transmissions using an uplink carrier via the first cell, downlink transmissions using a downlink carrier via the second cell, or both, based on SS set parameters and received via a downlink carrier of the second cell or a second downlink carrier associated with a third cell. Transmission manager 635 is capable of, configured to, or operable to support components for performing uplink transmissions, receiving downlink transmissions, or both, based on grants.

[0148] In some cases, the SS set manager 625, grant manager 630, and transmit manager 635 may each be a processor (e.g., a transceiver processor, a radio processor, a transmitter processor, or a receiver processor) or at least part of a processor. The processor may be coupled to memory and execute instructions stored in that memory that enable the processor to perform or facilitate the features of the SS set manager 625, grant manager 630, or transmit manager 635 discussed herein. The transceiver processor may co-locate with or communicate with (e.g., instruct its operation) the transceiver of the device. The radio processor may co-locate with or communicate with (e.g., instruct its operation) the radio of the device (e.g., NR radio, LTE radio, Wi-Fi radio). The transmitter processor may co-locate with or communicate with (e.g., instruct its operation) the transmitter of the device. The receiver processor may co-locate with or communicate with (e.g., instruct its operation) the receiver of the device.

[0149] Figure 7A block diagram 700 illustrates a communication manager 720 supporting SS set configuration for a pair of downlink and uplink cells according to one or more aspects of this disclosure. The communication manager 720 may be an example of a communication manager 520, a communication manager 620, or aspects thereof as described herein. The communication manager 720 or its various components may be examples of components for performing various aspects of SS set configuration for a pair of downlink and uplink cells as described herein. For example, the communication manager 720 may include an SS set manager 725, an authorization manager 730, a transmission manager 735, a cell pair manager 740, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0150] Communication manager 720 may support wireless communication according to examples disclosed herein. SS set manager 725 is capable of, configured to, or operable to support components for receiving indications of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell comprising an uplink-only cell and the second cell comprising a downlink-only cell. Grant manager 730 is capable of, configured to, or operable to support components for receiving grants for scheduling uplink transmissions via the first cell using an uplink carrier, downlink transmissions via the second cell using a downlink carrier, or both, based on SS set parameters and received via a downlink carrier of the second cell or a second downlink carrier associated with a third cell. Transmission manager 735 is capable of, configured to, or operable to support components for performing uplink transmissions, receiving downlink transmissions, or both, based on grants.

[0151] In some examples, the cell pair manager 740 is capable of, configured to, or operable to support components for receiving information identifying the first cell and the second cell as a cell pair set, wherein the SS set parameter is based on the cell pair set. In some examples, to support reception grants, the cell pair manager 740 is capable of, configured to, or operable to support components for receiving a shared CIF for grants associated with the first cell and the second cell, wherein the shared CIF indicates grant scheduling for uplink transmissions via the first cell, downlink transmissions via the second cell, or both.

[0152] In some examples, to support receive grants, the cell pair manager 740 is capable, configured, or operable to support components for receiving a first grant scheduled for uplink transmissions via a first cell. In some examples, to support receive grants, the cell pair manager 740 is capable, configured, or operable to support components for receiving a second grant scheduled for downlink transmissions via a second cell, wherein a first number of information bits in the first grant and a second number of information bits in the second grant comprise the same number of information bits.

[0153] In some examples, the cell pair manager 740 is capable of, configured to, or operable to support components for receiving indications of the allocation of information bit sizes for scheduling uplink transmissions via a first cell and for scheduling downlink transmissions via a second cell, wherein the same number of information bits are allocated based on the information bit size. In some examples, to support reception grant, the cell pair manager 740 is capable of, configured to, or operable to support components for receiving indications of whether the grant is for scheduling uplink transmissions via the first cell or downlink transmissions via the second cell.

[0154] In some examples, to support reception grants, the cell pair manager 740 is capable of, configured to, or operable to support components for monitoring SS sets on the downlink carrier of a second cell, the second downlink carrier of a third cell, or both, based on SS set parameters. In some examples, the SS set parameters identify the set of control channel resources to be monitored for reception grants on the downlink carrier of the second cell or the second downlink carrier of the third cell. In some examples, grants include DCI format 0_2 uplink grants, DCI format 1_2 downlink grants, or both. In some examples, the first cell includes a non-downlink carrier cell, and the second cell includes a non-uplink carrier cell.

[0155] In some cases, the SS set manager 725, grant manager 730, transmit manager 735, or cell pair manager 740 may each be a processor (e.g., a transceiver processor, a radio processor, a transmitter processor, or a receiver processor) or at least part of a processor. The processor may be coupled to memory and execute instructions stored in memory that enable the processor to perform or facilitate the features of the SS set manager 725, grant manager 730, transmit manager 735, or cell pair manager 740 discussed herein.

[0156] Figure 8A diagram is shown of a system 800 including device 805 supporting SS set configuration for a pair of downlink cells and uplink cells, according to one or more aspects of this disclosure. Device 805 may be an example of device 505, device 605, or UE 115 as described herein, or may include components thereof. Device 805 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. Device 805 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, at least one memory 830, code 835, and at least one processor 840. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 845).

[0157] I / O controller 810 manages the input and output signals of device 805. I / O controller 810 can also manage peripheral devices not integrated into device 805. In some cases, I / O controller 810 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 810 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, the I / O controller 810 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 810 may be implemented as part of one or more processors, such as at least one processor 840. In some cases, a user may interact with the device 805 via the I / O controller 810 or via hardware components controlled by the I / O controller 810.

[0158] In some cases, device 805 may include a single antenna 825. However, in other cases, device 805 may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 815 may communicate bidirectionally via one or more antennas 825, a wired link, or a wireless link as described herein. For example, transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 815 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 825 for transmission; and demodulating packets received from one or more antennas 825. Transceiver 815, or transceiver 815 and one or more antennas 825, may be an example of transmitter 515, transmitter 615, receiver 510, receiver 610, or any combination thereof or components thereof as described herein.

[0159] At least one memory 830 may include random access memory (RAM) and read-only memory (ROM). At least one memory 830 may store computer-readable, computer-executable code 835, including instructions that, when executed by at least one processor 840, cause device 805 to perform the various functions described herein. Code 835 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 835 may not be directly executable by at least one processor 840, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, at least one memory 830 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0160] At least one processor 840 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 840. At least one processor 840 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 830) to cause device 805 to perform various functions (e.g., functions or tasks supporting SS set configurations for a pair of downlink cells and uplink cells). For example, device 805 or components of device 805 may include at least one processor 840 and at least one memory 830 coupled to or coupled to at least one processor 840, at least one processor 840 and at least one memory 830 configured to perform the various functions described herein. In some examples, at least one processor 840 may include multiple processors, and at least one memory 830 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 840 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 840) and memory circuitry (which may include at least one memory 830)) or components that receive or receive input and process the input to produce, generate or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Thus, at least one processor 840 or a processing system including at least one processor 840 may be configured, capable of being configured, or operable to cause device 805 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 830 or otherwise.

[0161] The communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for receiving indications of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell comprising an uplink-only cell and the second cell comprising a downlink-only cell. The communication manager 820 may be capable of, configured to, or operable to support components for receiving authorization to schedule uplink transmissions using an uplink carrier via the first cell, downlink transmissions using a downlink carrier via the second cell, or both, based on the SS set parameters and received via the downlink carrier of the second cell or a second downlink carrier associated with a third cell. The communication manager 820 may be capable of, configured to, or operable to support components for performing uplink transmissions, receiving downlink transmissions, or both, based on the authorization.

[0162] By including or configuring a communication manager 820 according to an example as described herein, device 805 can support a technique for pairing sets of uplink-only cells and downlink-only cells to configure a set of SS that can be used to schedule the two cells.

[0163] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or in cooperation with transceiver 815, one or more antennas 825, or any combination thereof. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported by or executed by at least one processor 840, at least one memory 830, code 835, or any combination thereof. For example, code 835 may include instructions that can be executed by at least one processor 840 to cause device 805 to perform various aspects of the SS set configuration for a pair of downlink cells and uplink cells as described herein, or at least one processor 840 and at least one memory 830 may be otherwise configured to perform or support such operations individually or jointly.

[0164] Figure 9A block diagram 900 illustrates a device 905 configured to support an SS set for a pair of downlink and uplink cells, according to one or more aspects of this disclosure. Device 905 may be an example of aspects of network entity 105 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905, or one or more components of device 905 (e.g., receiver 910, transmitter 915, and communication manager 920), may include at least one processor coupled to at least one memory and storing instructions in that memory to individually or collectively support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0165] Receiver 910 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 905. In some examples, receiver 910 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 910 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0166] Transmitter 915 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 905. For example, transmitter 915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 915 and receiver 910 may be co-located in a transceiver, which may include or be coupled to a modem.

[0167] The communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the SS set configuration for a pair of downlink and uplink cells as described herein. For example, the communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0168] In some examples, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., executing instructions stored in at least one memory individually or collectively by one or more processors).

[0169] Additionally or alternatively, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be performed by any combination of a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0170] In some examples, the communication manager 920 may be configured to use or otherwise cooperate with the receiver 910, transmitter 915, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated with the receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0171] The communication manager 920 may support wireless communication according to examples disclosed herein. For example, the communication manager 920 may be capable of, configured to, or operable to support components for transmitting to the UE an indication of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell including an uplink-only cell and the second cell including a downlink-only cell. The communication manager 920 may be capable of, configured to, or operable to support components for transmitting permission for the UE to schedule uplink transmissions via the first cell using an uplink carrier, downlink transmissions via the second cell using a downlink carrier, or both, transmitted according to the SS set parameters and via a downlink carrier of the second cell or a second downlink carrier associated with a third cell. The communication manager 920 may be capable of, configured to, or operable to support components for receiving uplink transmissions from the UE, performing downlink transmissions to the UE, or both, based on the permission.

[0172] By including or configuring a communication manager 920 according to an example as described herein, device 905 (e.g., control receiver 910, transmitter 915, communication manager 920 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for pairing sets of uplink-only cells and downlink-only cells to configure a set of SS that can be used to schedule the two cells.

[0173] Figure 10 A block diagram 1000 of device 1005 supporting SS set configuration for a pair of downlink and uplink cells according to one or more aspects of this disclosure is shown. Device 1005 may be an example of aspects of device 905 or network entity 105 as described herein. Device 1005 may include receiver 1010, transmitter 1015, and communication manager 1020. Device 1005 or one or more components of device 1005 (e.g., receiver 1010, transmitter 1015, and communication manager 1020) may include at least one processor that can be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0174] Receiver 1010 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1005. In some examples, receiver 1010 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0175] Transmitter 1015 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1005. For example, transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1015 and receiver 1010 may be co-located in a transceiver, which may include or be coupled to a modem.

[0176] Device 1005 or its various components may be examples of parts for performing various aspects of SS set configuration for a pair of downlink and uplink cells as described herein. For example, communication manager 1020 may include SS set manager 1025, grant manager 1030, transmit manager 1035, or any combination thereof. Communication manager 1020 may be examples of aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to use or otherwise cooperate with receiver 1010, transmitter 1015, or both to perform various operations (e.g., receive, acquire, monitor, output, transmit). For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in combination with receiver 1010, transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0177] Communication manager 1020 may support wireless communication according to examples disclosed herein. SS set manager 1025 is capable of, configured to, or operable to support components for transmitting to the UE indications of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell comprising an uplink-only cell and the second cell comprising a downlink-only cell. Grant manager 1030 is capable of, configured to, or operable to support components for transmitting grants for the UE to schedule uplink transmissions via the first cell using an uplink carrier, downlink transmissions via the second cell using a downlink carrier, or both, based on SS set parameters and transmitted via a downlink carrier of the second cell or a second downlink carrier associated with a third cell. Transmission manager 1035 is capable of, configured to, or operable to support components for receiving uplink transmissions from the UE, performing downlink transmissions to the UE, or both, based on grants.

[0178] In some cases, the SS set manager 1025, grant manager 1030, and transmit manager 1035 may each be a processor (e.g., a transceiver processor, a radio processor, a transmitter processor, or a receiver processor) or at least part of a processor. The processor may be coupled to memory and execute instructions stored in that memory that enable the processor to perform or facilitate the features of the SS set manager 1025, grant manager 1030, or transmit manager 1035 discussed herein. The transceiver processor may co-locate with or communicate with (e.g., instruct its operation) the transceiver of the device. The radio processor may co-locate with or communicate with (e.g., instruct its operation) the radio of the device (e.g., NR radio, LTE radio, Wi-Fi radio). The transmitter processor may co-locate with or communicate with (e.g., instruct its operation) the transmitter of the device. The receiver processor may co-locate with or communicate with (e.g., instruct its operation) the receiver of the device.

[0179] Figure 11A block diagram 1100 is shown of a communication manager 1120 supporting SS set configuration for a pair of downlink and uplink cells according to one or more aspects of this disclosure. Communication manager 1120 may be an example of aspects of communication manager 920, communication manager 1020, or both as described herein. Communication manager 1120 or its various components may be examples of components for performing various aspects of SS set configuration for a pair of downlink and uplink cells as described herein. For example, communication manager 1120 may include SS set manager 1125, grant manager 1130, transmit manager 1135, cell pair manager 1140, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and such communication may include communication within protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0180] Communication manager 1120 may support wireless communication according to examples disclosed herein. SS set manager 1125 is capable of, configured to, or operable to support components for transmitting to the UE indications of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell comprising an uplink-only cell and the second cell comprising a downlink-only cell. Grant manager 1130 is capable of, configured to, or operable to support components for transmitting grants for the UE to schedule uplink transmissions via the first cell using an uplink carrier, downlink transmissions via the second cell using a downlink carrier, or both, based on SS set parameters and transmitted via a downlink carrier of the second cell or a second downlink carrier associated with a third cell. Transmission manager 1135 is capable of, configured to, or operable to support components for receiving uplink transmissions from the UE, performing downlink transmissions to the UE, or both, based on grants.

[0181] In some examples, the cell pair manager 1140 is capable of, configured to, or operable to support components for transmitting information identifying the first cell and the second cell as a cell pair set, wherein the SS set parameter is based on the cell pair set. In some examples, to support transmission permission, the cell pair manager 1140 is capable of, configured to, or operable to support components for configuring permission to indicate a shared CIF associated with the first cell and the second cell, wherein the shared CIF indicates permission to schedule uplink transmissions via the first cell, downlink transmissions via the second cell, or both.

[0182] In some examples, to support transmission grants, cell pair manager 1140 is capable, configured, or operable to support components for a first grant for scheduling uplink transmissions via a first cell. In some examples, to support transmission grants, cell pair manager 1140 is capable, configured, or operable to support components for a second grant for scheduling downlink transmissions via a second cell, wherein a first number of information bits in the first grant and a second number of information bits in the second grant comprise the same number of information bits.

[0183] In some examples, the cell pair manager 1140 is capable of, configured to, or operable to support components for transmitting indications of the allocation of information bit size for scheduling uplink transmissions via a first cell and for scheduling downlink transmissions via a second cell, wherein the same number of information bits are allocated based on the information bit size. In some examples, to support transmission grant, the cell pair manager 1140 is capable of, configured to, or operable to support components for transmitting indications of whether the grant is for scheduling uplink transmissions via the first cell or downlink transmissions via the second cell.

[0184] In some examples, to support transmission grants, the cell pair manager 1140 can, is configured, or is operable to support components for transmitting grants on the SS set of a second cell's downlink carrier, a third cell's second downlink carrier, or both, based on SS set parameters. In some examples, the SS set parameters identify the set of control channel resources to be monitored for receiving grants on the downlink carrier of the second cell or the second downlink carrier of the third cell. In some examples, the grant includes DCI format 0_2 uplink grants, DCI format 1_2 downlink grants, or both. In some examples, the first cell includes a non-downlink carrier cell, and the second cell includes a non-uplink carrier cell.

[0185] In some cases, the SS set manager 1125, grant manager 1130, transmit manager 1135, or cell pair manager 1140 may each be a processor (e.g., a transceiver processor, a radio processor, a transmitter processor, or a receiver processor) or at least part of a processor. The processor may be coupled to memory and execute instructions stored in memory that enable the processor to perform or facilitate the features of the SS set manager 1125, grant manager 1130, transmit manager 1135, or cell pair manager 1140 discussed herein.

[0186] Figure 12 A diagram of a system 1200 including device 1205 supporting SS set configuration for a pair of downlink and uplink cells, according to one or more aspects of this disclosure, is shown. Device 1205 may be an example of device 905, device 1005, or network entity 105 as described herein, or may include components thereof. Device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and such communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1205 may include components that support output and obtain communication, such as a communication manager 1220, a transceiver 1210, an antenna 1215, at least one memory 1225, code 1230, and at least one processor 1235. These components may communicate electronically or otherwise (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1240).

[0187] Transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1210 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1210 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1205 may include one or more antennas 1215 that are capable of transmitting or receiving wireless transmissions (e.g., concurrently). Transceiver 1210 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1215, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1215, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1215 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1215 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1210 may include one or more processors or one or more memory components or configured to be coupled to said one or more processors or one or more memory components, said one or more processors or memory components being operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1210, or transceiver 1210 and one or more antennas 1215, or transceiver 1210 and one or more antennas 1215 and one or more processors or one or more memory components (e.g., at least one processor 1235, at least one memory 1225, or both) may be included in a chip or chip assembly mounted in device 1205. In some examples, transceiver 1210 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0188] At least one memory 1225 may include RAM, ROM, or any combination thereof. At least one memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by one or more of at least one processor 1235, cause device 1205 to perform the various functions described herein. Code 1230 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1230 may not be directly executable by one of the at least one processor 1235, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, at least one memory 1225 may also include a BIOS that controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1235 may include multiple processors, and at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0189] At least one processor 1235 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any combination thereof). In some cases, at least one processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more of the at least one processor 1235. At least one processor 1235 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1225) to cause device 1205 to perform various functions (e.g., functions or tasks supporting SS set configurations for a pair of downlink cells and uplink cells). For example, device 1205 or components of device 1205 may include at least one processor 1235 and at least one memory 1225 coupled to one or more of the at least one processor 1235, the at least one processor 1235 and the at least one memory 1225 being configured to perform the various functions described herein. At least one processor 1235 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can (e.g., by executing code 1230) host functions for performing the functions of device 1205. At least one processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1205 (such as within one or more memories of at least one memory 1225). In some examples, at least one processor 1235 may include multiple processors, and at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1235 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1235) and memory circuitry (which may include at least one memory 1225)) or components that receive or acquire input and process the input to produce, generate, or acquire a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Therefore, at least one processor 1235 or a processing system including at least one processor 1235 may be configured, can be configured, or can be operated to cause the device 1205 to perform one or more of the functions described herein.Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1225 or otherwise.

[0190] In some examples, bus 1240 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1240 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1205, or communication performed between different components of device 1205 that are co-addressable or may be located in different locations (e.g., where device 1205 may refer to a system in which one or more of communication manager 1220, transceiver 1210, at least one memory 1225, code 1230 and at least one processor 1235 may be located in one component of different components or partitioned between different components).

[0191] In some examples, the communication manager 1220 may manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1220 may manage the delivery of data communications by client devices, such as one or more UEs 115. In some examples, the communication manager 1220 may manage communication with other network entities 105 and may include a controller or scheduler for cooperating with other network entities 105 to control communication with UE 115. In some examples, the communication manager 1220 may support an X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0192] The communication manager 1220 may support wireless communication according to examples disclosed herein. For example, the communication manager 1220 may be capable of, configured to, or operable to support components for transmitting to the UE an indication of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell including an uplink-only cell and the second cell including a downlink-only cell. The communication manager 1220 may be capable of, configured to, or operable to support components for transmitting permission for the UE to schedule uplink transmissions via the first cell using an uplink carrier, downlink transmissions via the second cell using a downlink carrier, or both, transmitted according to the SS set parameters and via a downlink carrier of the second cell or a second downlink carrier associated with a third cell. The communication manager 1220 may be capable of, configured to, or operable to support components for receiving uplink transmissions from the UE, performing downlink transmissions to the UE, or both, based on the permission granted.

[0193] By including or configuring a communication manager 1220 according to an example as described herein, device 1205 can support a technique for pairing sets of uplink-only cells and downlink-only cells to configure a set of SS that can be used to schedule the two cells.

[0194] In some examples, the communication manager 1220 may be configured to use or otherwise coordinate with the transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the transceiver 1210, one or more processors in at least one processor 1235, one or more memories in at least one memory 1225, code 1230, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1235, at least one memory 1225, code 1230, or any combination thereof). For example, code 1230 may include instructions that can be executed by one or more of at least one processor 1235 to cause device 1205 to perform various aspects of the SS set configuration for a pair of downlink cells and uplink cells as described herein, or at least one processor 1235 and at least one memory 1225 may be otherwise configured to perform or support such operations individually or jointly.

[0195] Figure 13 A flowchart illustrating a method 1300 for configuring an SS set for a pair of downlink and uplink cells according to various aspects of this disclosure is shown. Operation of method 1300 can be implemented by a UE or its components as described herein. For example, operation of method 1300 can be implemented by, as referenced... Figures 1 to 8 The UE 115 described herein performs the following: In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0196] At 1305, the method may include: receiving indications of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell comprising an uplink-only cell and the second cell comprising a downlink-only cell. Operation of block 1305 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1305 may be provided by reference to [reference needed]. Figure 7 The SS set manager 725 described is executed.

[0197] At 1310, the method may include: receiving permission to schedule uplink transmissions via a first cell using an uplink carrier, downlink transmissions via a second cell using a downlink carrier, or both, wherein the permission is received based on SS set parameters and via a downlink carrier of the second cell or a second downlink carrier associated with a third cell. The operation of block 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1310 may be provided by reference to [reference needed]. Figure 7 The described grant manager 730 is executed.

[0198] At 1315, the method may include: performing an uplink transmission, receiving a downlink transmission, or both, based on permission. The operation of block 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1315 may be derived from references... Figure 7 The described send manager 735 is executed.

[0199] Figure 14 A flowchart illustrating a method 1400 for configuring an SS set for a pair of downlink and uplink cells according to various aspects of this disclosure is shown. Operation of method 1400 can be implemented by a UE or its components as described herein. For example, operation of method 1400 can be implemented by, as referenced... Figures 1 to 8 The UE 115 described herein performs the following: In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0200] At 1405, the method may include: receiving information identifying a first cell and a second cell as a cell pairing set, wherein the SS set parameter is based on the cell pairing set. The operation of block 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1405 may be derived from references... Figure 7 The described cell is executed on manager 740.

[0201] At 1410, the method may include: receiving indications of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell comprising an uplink-only cell and the second cell comprising a downlink-only cell. Operation of block 1410 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1410 may be provided by reference to [reference needed]. Figure 7 The SS set manager 725 described is executed.

[0202] At 1415, the method may include: receiving permission to schedule uplink transmissions via a first cell using an uplink carrier, downlink transmissions via a second cell using a downlink carrier, or both, wherein the permission is received based on SS set parameters and via a downlink carrier of the second cell or a second downlink carrier associated with a third cell. The operation of block 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1415 may be provided by reference to [reference needed]. Figure 7 The described grant manager 730 is executed.

[0203] At 1420, the method may include: performing an uplink transmission, receiving a downlink transmission, or both, based on permission. The operation of block 1420 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1420 may be derived from references... Figure 7 The described send manager 735 is executed.

[0204] Figure 15 A flowchart illustrating a method 1500 for configuring an SS set for a pair of downlink and uplink cells according to various aspects of this disclosure is shown. Operation of method 1500 can be implemented by a UE or its components as described herein. For example, operation of method 1500 can be achieved by referring to... Figures 1 to 8 The UE 115 described herein performs the following: In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0205] At 1505, the method may include: receiving indications of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell comprising an uplink-only cell and the second cell comprising a downlink-only cell. Operation of block 1505 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1505 may be provided by reference to [reference needed]. Figure 7 The SS set manager 725 described is executed.

[0206] At 1510, the method may include: receiving permission to schedule uplink transmissions via a first cell using an uplink carrier, downlink transmissions via a second cell using a downlink carrier, or both, wherein the permission is received based on SS set parameters and via a downlink carrier of the second cell or a second downlink carrier associated with a third cell. Operation of block 1510 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1510 may be provided by reference to [reference needed]. Figure 7 The described grant manager 730 is executed.

[0207] At 1515, the method may include: receiving an authorized shared carrier indicator field (CIF) associated with a first cell and a second cell, wherein the shared CIF indicates authorization to schedule uplink transmissions via the first cell, downlink transmissions via the second cell, or both. Operation of block 1515 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1515 may be provided by reference to [reference needed]. Figure 7 The described cell is executed on manager 740.

[0208] At 1520, the method may include: performing an uplink transmission, receiving a downlink transmission, or both, based on permission. The operation of block 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1520 may be derived from references... Figure 7 The described send manager 735 is executed.

[0209] Figure 16 A flowchart illustrating a method 1600 for configuring an SS set for a pair of downlink and uplink cells according to various aspects of this disclosure is shown. The operation of method 1600 can be implemented by a network entity or its components as described herein. For example, the operation of method 1600 can be implemented by, as referenced... Figures 1 to 4 as well as Figures 9 to 12 The described network entity performs the functions. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0210] At 1605, the method may include: sending to the UE an indication of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell comprising an uplink-only cell and the second cell comprising a downlink-only cell. The operation of block 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1605 may be provided by reference to [reference needed]. Figure 11 The described SS set manager 1125 is executed.

[0211] At 1610, the method may include: sending permission for the UE to schedule uplink transmission via a first cell using an uplink carrier, downlink transmission via a second cell using a downlink carrier, or both, the permission being sent according to SS set parameters and via a downlink carrier of the second cell or a second downlink carrier associated with a third cell. The operation of block 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1610 may be provided by reference to [reference needed]. Figure 11 The described permission manager 1130 is executed.

[0212] At 1615, the method may include: receiving uplink transmissions from the UE, performing downlink transmissions to the UE, or both, based on permission. The operation of block 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1615 may be derived from references... Figure 11 The described send manager 1135 is executed.

[0213] Figure 17 A flowchart illustrating method 1700 for configuring an SS set for a pair of downlink and uplink cells according to various aspects of this disclosure is shown. Operation of method 1700 may be implemented by a network entity or its components as described herein. For example, operation of method 1700 may be implemented by, as referenced... Figures 1 to 4 as well as Figures 9 to 12 The described network entity performs the functions. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0214] At 1705, the method may include: sending to the UE an indication of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell comprising an uplink-only cell and the second cell comprising a downlink-only cell. Operation of block 1705 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1705 may be provided by reference to [reference needed]. Figure 11 The described SS set manager 1125 is executed.

[0215] At 1710, the method may include: configuring an indication of whether to schedule uplink transmission via a first cell or downlink transmission via a second cell. The operation of block 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1710 may be provided by reference to [reference needed]. Figure 11 The described cell is executed on manager 1140.

[0216] At 1715, the method may include: transmitting permission for the UE to schedule uplink transmission via a first cell using an uplink carrier, downlink transmission via a second cell using a downlink carrier, or both, the permission being transmitted based on SS set parameters and via a downlink carrier of the second cell or a second downlink carrier associated with a third cell. The operation of block 1715 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1715 may be provided by reference to [reference missing]. Figure 11 The described permission manager 1130 is executed.

[0217] At 1720, the method may include: receiving uplink transmissions from the UE, performing downlink transmissions to the UE, or both, based on permission. The operation of block 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1720 may be derived from references... Figure 11 The described send manager 1135 is executed.

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

[0219] Aspect 1: A method for performing wireless communication at a UE, the method comprising: receiving indications of SS set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell comprising an uplink-only cell and the second cell comprising a downlink-only cell; receiving permission to schedule uplink transmissions via the first cell using the uplink carrier, downlink transmissions via the second cell using the downlink carrier, or both, the permission being received based on the SS set parameters and via the downlink carrier of the second cell or a second downlink carrier associated with a third cell; and performing the uplink transmissions, receiving the downlink transmissions, or both, based on the permission.

[0220] Aspect 2: According to the method of aspect 1, the method further includes: receiving information identifying the first cell and the second cell as a cell pairing set, wherein the SS set parameter is at least partially based on the cell pairing set.

[0221] Aspect 3: The method according to any one of Aspects 1 to 2, wherein receiving the grant comprises: receiving a shared CIF of the grant associated with the first cell and the second cell, wherein the shared CIF indicates that the grant is scheduled for the uplink transmission via the first cell, the downlink transmission via the second cell, or both.

[0222] Aspect 4: The method according to any one of Aspects 1 to 3, wherein receiving the grant comprises: receiving a first grant scheduled to be transmitted via the uplink through the first cell; and receiving a second grant scheduled to be transmitted via the downlink through the second cell, wherein a first number of information bits in the first grant and a second number of information bits in the second grant comprise the same number of information bits.

[0223] Aspect 5: According to the method of aspect 4, the method further includes: receiving an indication of information bit size allocation for scheduling the uplink transmission via the first cell and for scheduling the downlink transmission via the second cell, wherein the same number of information bits are allocated based on the information bit size.

[0224] Aspect 6: The method according to any one of Aspects 1 to 5, wherein receiving the grant comprises: receiving an indication of whether the grant is to schedule the uplink transmission via the first cell or the downlink transmission via the second cell.

[0225] Aspect 7: The method according to any one of Aspects 1 to 6, wherein receiving the grant comprises: monitoring the downlink carrier of the second cell, the second downlink carrier of the third cell, or the SS set on both, according to the SS set parameters.

[0226] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the SS set parameter identifies the set of control channel resources to be monitored for reception on the downlink carrier of the second cell or the second downlink carrier of the third cell.

[0227] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the grant includes DCI format 0_2 uplink grant, DCI format 1_2 downlink grant, or both.

[0228] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the first cell comprises a non-downlink carrier cell and the second cell comprises a non-uplink carrier cell.

[0229] Aspect 11: A method for wireless communication at a network entity, the method comprising: sending to a UE an indication of SS set parameters of a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell comprising an uplink-only cell and the second cell comprising a downlink-only cell; sending an authorization for the UE to schedule uplink transmissions via the first cell using the uplink carrier, downlink transmissions via the second cell using the downlink carrier, or both, the authorization being sent based on the SS set parameters and via the downlink carrier of the second cell or a second downlink carrier associated with a third cell; and receiving the uplink transmissions from the UE, performing the downlink transmissions to the UE, or both, based on the authorization.

[0230] Aspect 12: According to the method of aspect 11, the method further includes: sending information identifying the first cell and the second cell as a cell pairing set, wherein the SS set parameters are at least partially based on the cell pairing set.

[0231] Aspect 13: The method according to any one of Aspects 11 to 12, wherein sending the grant includes: configuring the grant to indicate a shared CIF associated with the first cell and the second cell, wherein the shared CIF indicates that the grant is scheduled for the uplink transmission via the first cell, the downlink transmission via the second cell, or both.

[0232] Aspect 14: The method according to any one of Aspects 11 to 13, wherein transmitting the grant comprises: transmitting a first grant scheduled for uplink transmission via the first cell; and transmitting a second grant scheduled for downlink transmission via the second cell, wherein a first number of information bits in the first grant and a second number of information bits in the second grant comprise the same number of information bits.

[0233] Aspect 15: The method according to aspect 14, the method further comprising: sending an indication of an information bit size allocation for scheduling the uplink transmission via the first cell and for scheduling the downlink transmission via the second cell, wherein the same number of information bits are allocated based on the information bit size.

[0234] Aspect 16: The method according to any one of Aspects 11 to 15, wherein sending the grant includes: configuring an indication of whether the grant is scheduled for uplink transmission via the first cell or downlink transmission via the second cell.

[0235] Aspect 17: The method according to any one of Aspects 11 to 16, wherein sending the grant comprises: sending the grant on the SS set on the downlink carrier of the second cell, the second downlink carrier of the third cell, or both, according to the SS set parameters.

[0236] Aspect 18: The method according to any one of Aspects 11 to 17, wherein the SS set parameter identifies the set of control channel resources to be monitored for reception on the downlink carrier of the second cell or the second downlink carrier of the third cell.

[0237] Aspect 19: The method according to any one of Aspects 11 to 18, wherein the grant includes DCI format 0_2 uplink grant, DCI format 1_2 downlink grant, or both.

[0238] Aspect 20: The method according to any one of Aspects 11 to 19, wherein the first cell comprises a non-downlink carrier cell and the second cell comprises a non-uplink carrier cell.

[0239] Aspect 21: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, so that the UE performs a method according to any one of aspects 1 to 10.

[0240] Aspect 22: A UE for wireless communication, the UE comprising at least one component for performing the method according to any one of aspects 1 to 10.

[0241] Aspect 23: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to any one of aspects 1 to 10.

[0242] Aspect 24: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the network entity to perform a method according to any one of Aspects 11 to 20.

[0243] Aspect 25: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 11 to 20.

[0244] Aspect 26: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to any one of aspects 11 to 20.

[0245] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0246] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0247] The information and signals described herein can 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 description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0248] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A 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 working in conjunction with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0249] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code 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 can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including portions distributed such that the functions are implemented in different physical locations.

[0250] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0251] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, 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). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0252] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components,” and subsequent reference to “component” in a claim may be understood to be equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” may refer to any or all of the one or more components. For example, reference to "one or more components" in subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0253] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, acquiring, selecting, choosing, building, and other similar actions.

[0254] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate them. If only the first reference numeral is used in the description, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0255] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0256] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: Receive an indication of search space set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell including uplink-only cells and the second cell including downlink-only cells; The recipient schedules an uplink transmission via the first cell using the uplink carrier, a downlink transmission via the second cell using the downlink carrier, or an authorization for both, the authorization being received based on the search space set parameters and via the downlink carrier of the second cell or a second downlink carrier associated with a third cell; as well as The uplink transmission, the downlink transmission, or both are performed based on the permission granted.

2. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Receive information identifying the first cell and the second cell as a cell pairing set, wherein the search space set parameters are at least partially based on the cell pairing set.

3. The UE according to claim 1, wherein, In order to receive the permission, the one or more processors can operate individually or jointly to execute the code to enable the UE to: Receive the granted shared carrier indicator field (CIF) associated with the first cell and the second cell, wherein the shared carrier indicator field (CIF) indicates that the granted scheduling is for the uplink transmission via the first cell, the downlink transmission via the second cell, or both.

4. The UE according to claim 1, wherein, In order to receive the permission, the one or more processors can operate individually or jointly to execute the code to enable the UE to: Receive scheduling via the first cell to send the first permission via the uplink; as well as The receiver schedules a second grant sent via the downlink through the second cell, wherein the first number of information bits in the first grant and the second number of information bits in the second grant comprise the same number of information bits.

5. The UE of claim 4, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Receive an instruction for the allocation of information bit size for scheduling the uplink transmission via the first cell and for scheduling the downlink transmission via the second cell, wherein the same number of information bits are allocated based on the information bit size.

6. The UE according to claim 1, wherein, In order to receive the permission, the one or more processors can operate individually or jointly to execute the code to enable the UE to: Receive an indication of whether the permission is to schedule the uplink transmission via the first cell or the downlink transmission via the second cell.

7. The UE according to claim 1, wherein, In order to receive the permission, the one or more processors can operate individually or jointly to execute the code to enable the UE to: The search space set is monitored based on the search space set parameters on the downlink carrier of the second cell, the second downlink carrier of the third cell, or the search space set on both.

8. The UE of claim 1, wherein the search space set parameter identifies the set of control channel resources to be monitored for reception on the downlink carrier of the second cell or the second downlink carrier of the third cell.

9. The UE of claim 1, wherein the grant includes uplink grant in downlink control information (DCI) format 0_2, downlink grant in DCI format 1_2, or both.

10. The UE of claim 1, wherein the first cell comprises a non-downlink carrier cell and the second cell comprises a non-uplink carrier cell.

11. A network entity, the network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the network entity: Instructions are sent to the User Equipment (UE) for search space set parameters of a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell including uplink-only cells and the second cell including downlink-only cells; Sending an authorization for the UE to schedule uplink transmission via the first cell using the uplink carrier, downlink transmission via the second cell using the downlink carrier, or both, the authorization being sent based on the search space set parameters and via the downlink carrier of the second cell or a second downlink carrier associated with a third cell; as well as Based on the permission, receive the uplink transmission from the UE, perform the downlink transmission to the UE, or both.

12. The network entity of claim 11, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: Send information identifying the first cell and the second cell as a cell pairing set, wherein the search space set parameters are at least partially based on the cell pairing set.

13. The network entity according to claim 11, wherein, In order to send the authorization, the one or more processors can operate individually or jointly to execute the code to enable the network entity to: Configure the grant to indicate a shared carrier indicator (CIF) field associated with the first cell and the second cell, wherein the shared carrier indicator (CIF) field indicates that the grant is scheduled for the uplink transmission via the first cell, the downlink transmission via the second cell, or both.

14. The network entity according to claim 11, wherein, In order to send the authorization, the one or more processors can operate individually or jointly to execute the code to enable the network entity to: First permission is granted for the uplink transmission scheduled via the first cell; as well as The transmission schedules a second grant for downlink transmission via the second cell, wherein the first number of information bits in the first grant and the second number of information bits in the second grant comprise the same number of information bits.

15. The network entity of claim 14, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: Send an indication of the allocation of information bit size for scheduling the uplink transmission via the first cell and for scheduling the downlink transmission via the second cell, wherein the same number of information bits are allocated based on the information bit size.

16. The network entity according to claim 11, wherein, In order to send the authorization, the one or more processors can operate individually or jointly to execute the code to enable the network entity to: Configure an indication of whether the permission is to schedule the uplink transmission via the first cell or the downlink transmission via the second cell.

17. The network entity according to claim 11, wherein, In order to send the authorization, the one or more processors can operate individually or jointly to execute the code to enable the network entity to: The grant is transmitted on the search space set of the second cell's downlink carrier, the third cell's second downlink carrier, or both, based on the search space set parameters.

18. The network entity of claim 11, wherein the search space set parameter identifies the set of permitted control channel resources to be monitored for reception on the downlink carrier of the second cell or the second downlink carrier of the third cell.

19. The network entity of claim 11, wherein the grant includes uplink grant of downlink control information (DCI) format 0_2, downlink grant of DCI format 1_2, or both.

20. The network entity of claim 11, wherein the first cell comprises a non-downlink carrier cell and the second cell comprises a non-uplink carrier cell.

21. A method for conducting wireless communication at a user equipment (UE), the method comprising: Receive an indication of search space set parameters for a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell including uplink-only cells and the second cell including downlink-only cells; The recipient schedules an uplink transmission via the first cell using the uplink carrier, a downlink transmission via the second cell using the downlink carrier, or an authorization for both, the authorization being received based on the search space set parameters and via the downlink carrier of the second cell or a second downlink carrier associated with a third cell; as well as The uplink transmission, the downlink transmission, or both are performed based on the permission granted.

22. The method according to claim 21, further comprising: Receive information identifying the first cell and the second cell as a cell pairing set, wherein the search space set parameters are at least partially based on the cell pairing set.

23. The method of claim 21, wherein receiving the permission comprises: Receive the granted shared carrier indicator field (CIF) associated with the first cell and the second cell, wherein the shared carrier indicator field (CIF) indicates that the granted scheduling is for the uplink transmission via the first cell, the downlink transmission via the second cell, or both.

24. The method of claim 21, wherein receiving the permission comprises: Receive scheduling via the first cell to send the first permission via the uplink; as well as The receiver schedules a second grant sent via the downlink through the second cell, wherein the first number of information bits in the first grant and the second number of information bits in the second grant comprise the same number of information bits.

25. The method according to claim 24, further comprising: Receive an instruction for the allocation of information bit size for scheduling the uplink transmission via the first cell and for scheduling the downlink transmission via the second cell, wherein the same number of information bits are allocated based on the information bit size.

26. The method of claim 21, wherein receiving the permission comprises: Receive an indication of whether the permission is to schedule the uplink transmission via the first cell or the downlink transmission via the second cell.

27. The method of claim 21, wherein receiving the permission comprises: The search space set is monitored based on the search space set parameters on the downlink carrier of the second cell, the second downlink carrier of the third cell, or the search space set on both.

28. The method of claim 21, wherein the search space set parameter identifies the set of permitted control channel resources to be monitored for reception on the downlink carrier of the second cell or the second downlink carrier of the third cell.

29. The method of claim 21, wherein the grant includes uplink grant of downlink control information (DCI) format 0_2, downlink grant of DCI format 1_2, or both.

30. A method for conducting wireless communication at a network entity, the method comprising: Instructions are sent to the User Equipment (UE) for search space set parameters of a first cell associated with an uplink carrier and a second cell associated with a downlink carrier, the first cell including uplink-only cells and the second cell including downlink-only cells; Sending an authorization for the UE to schedule uplink transmission via the first cell using the uplink carrier, downlink transmission via the second cell using the downlink carrier, or both, the authorization being sent based on the search space set parameters and via the downlink carrier of the second cell or a second downlink carrier associated with a third cell; as well as Based on the permission, receive the uplink transmission from the UE, perform the downlink transmission to the UE, or both.

Images