Random access on enhanced secondary uplink cells

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive a first indication of a first cell associated with a first uplink carrier and a first downlink carrier and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell. The UE may receive a second indication of subsequent communications to be performed via a first uplink carrier of the first cell, a second uplink carrier of the second cell, or both via a first downlink carrier of the first cell or via a second downlink carrier associated with the third cell. The UE may perform a subsequent communication according to the second indication, wherein the subsequent communication includes at least one of an access communication, an uplink communication, or both.

Description

[0001] Cross-referencing

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 476,124, entitled “RANDOM ACCESSON ENHANCED SECONDARY UPLINK CELL”, filed September 27, 2023, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following discussion pertains to wireless communications, including random access on enhanced secondary uplink cells. Background Technology

[0004] 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

[0005] The described technology relates to improved methods, systems, devices, and apparatuses for supporting random access on enhanced secondary uplink (eSUL) cells. For example, the described technology provides a unified framework for supporting eSUL within a radio network. Broadly speaking, an eSUL can be considered as an uplink carrier of a cell that does not have an associated downlink carrier (e.g., an uplink-only cell). A user equipment (UE) can receive a first indication for a first cell. The first cell can be a conventional cell, as it includes both uplink and downlink carriers. The first indication can also identify a second cell (e.g., an eSUL). The second cell can be an uplink-only cell that does not have an associated downlink carrier. The UE can receive a second indication for subsequent communication to be performed. The second indication can be received via a downlink carrier of the first cell or via a different downlink carrier from a third cell. The second indication can schedule subsequent communication. The UE can perform subsequent communication via the eSUL and / or via the uplink carrier of the first cell. Subsequent communication may include uplink / downlink communication and / or random access channel communication.

[0006] A method for wireless communication by a UE is described. The method may include: receiving a first indication for a first cell associated with a first uplink carrier and a first downlink carrier and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell; receiving, via the first downlink carrier of the first cell or via the second downlink carrier associated with a third cell, a second indication for subsequent communication to be performed via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both; and performing the subsequent communication according to the second indication, wherein the subsequent communication includes access communication, uplink communication, or at least one of both.

[0007] 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 to cause the UE to: receive a first indication of a first cell associated with a first uplink carrier and a first downlink carrier, and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell; receive a second indication of subsequent communication to be performed via the first downlink carrier of the first cell or via the second downlink carrier associated with a third cell, for the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both; and perform the subsequent communication according to the second indication, wherein the subsequent communication includes access communication, uplink communication, or at least one of both.

[0008] Another UE for wireless communication is described. The UE may include: means for receiving a first indication of a first cell associated with a first uplink carrier and a first downlink carrier, and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell; means for receiving, via the first downlink carrier of the first cell or via the second downlink carrier associated with a third cell, a second indication of subsequent communication to be performed via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both; and means for performing the subsequent communication according to the second indication, wherein the subsequent communication includes access communication, uplink communication, or at least one of both.

[0009] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: receive a first indication for a first cell associated with a first uplink carrier and a first downlink carrier, and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell; receive, via the first downlink carrier of the first cell or via the second downlink carrier associated with a third cell, a second indication for subsequent communication to be performed via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both; and perform the subsequent communication according to the second indication, wherein the subsequent communication includes access communication, uplink communication, or at least one of both.

[0010] In some examples of the method, user equipment (UE), and nontransitory computer-readable medium described herein, receiving the second indication may include an operation, feature, component, or instruction for the following action: receiving permission to schedule uplink communication via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both, wherein the subsequent communication includes the uplink communication.

[0011] In some examples of the method, user equipment (UE), and non-transitory computer-readable medium described herein, the grant includes cross-carrier scheduling grant, multi-cell scheduling grant, or both.

[0012] The method described herein, some examples of user equipment (UE) and non-transitory computer-readable media may further include operations, features, components or instructions for identifying a first feedback process associated with uplink communication via the first cell and a second feedback process associated with uplink communication via the second cell.

[0013] The method described herein, some examples of user equipment (UE) and non-transitory computer-readable media may further include operations, features, components or instructions for: receiving a reference signal transmitted via the first downlink carrier of the first cell, via the second downlink carrier associated with the third cell, or both; and performing timing and power control operations using the reference signal.

[0014] In some examples of the method, user equipment (UE), and non-transitory computer-readable medium described herein, performing the subsequent communication may include operations, features, components, or instructions for transmitting uplink communication via the second uplink carrier of the second cell, or receiving downlink communication via the first downlink carrier of the first cell, according to a half-duplex scheme.

[0015] In some examples of the method, user equipment (UE), and non-transitory computer-readable medium described herein, performing the subsequent communication may include operations, features, components, or instructions for: performing simultaneous transmission on the first uplink carrier of the first cell and transmission on the second uplink carrier of the second cell, according to a simultaneous transmission antenna switching scheme; or performing non-simultaneous transmission on the first uplink carrier of the first cell and transmission on the second uplink carrier of the second cell, according to an uplink transmission antenna switching scheme.

[0016] In some examples of the method, user equipment (UE), and nontransitory computer-readable medium described herein, receiving the second instruction may include operations, features, components, or instructions for: receiving a system information message that identifies a first access resource for accessing the first cell via the first uplink carrier and a second access resource for accessing the second cell via the second uplink carrier; and accessing the first cell or the second cell based on the first access resource or the second access resource.

[0017] The method described herein, some examples of user equipment (UE) and non-transitory computer-readable media may further include operations, features, components or instructions for: identifying a first access channel timing corresponding to the first access resource and a second access channel timing corresponding to the second access resource, based on the fact that the subsequent communication is scheduled in a time-domain duplex (TDD) scheme, according to the access scheme.

[0018] In some examples of the method, user equipment (UE), and non-transitory computer-readable medium described herein, information is used to identify, based on the first indication, uplink configuration, TDD uplink / downlink configuration, candidate synchronization signal block index set, or any combination thereof for the second uplink carrier used in the second cell.

[0019] In some examples of the method described herein, user equipment (UE), and non-transitory computer-readable media, this information may be carried in the eSUL carrier sequence indication.

[0020] In some examples of the method described herein, user equipment (UE), and non-transitory computer-readable media, this information may be carried in the serving cell configuration common system information block eSUL carrier indication.

[0021] A method for wireless communication by a network entity is described. The method may include: sending a first indication to a UE regarding a first cell associated with a first uplink carrier and a first downlink carrier, and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell; sending to the UE, via the first downlink carrier of the first cell or via the second downlink carrier associated with a third cell, a second indication to be performed for subsequent communication via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both; and performing the subsequent communication with the UE according to the second indication.

[0022] 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 a first indication to a UE regarding a first cell associated with a first uplink carrier and a first downlink carrier, and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell; send a second indication to the UE via the first downlink carrier of the first cell or via the second downlink carrier associated with a third cell regarding subsequent communication to be performed via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both; and perform the subsequent communication with the UE according to the second indication.

[0023] Another network entity for wireless communication is described. This network entity may include: components for transmitting to a UE a first indication of a first cell associated with a first uplink carrier and a first downlink carrier, and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell; components for transmitting to the UE, via the first downlink carrier of the first cell or via the second downlink carrier associated with a third cell, a second indication of subsequent communication to be performed via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both; and components for performing the subsequent communication with the UE according to the second indication.

[0024] 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 a first indication of a first cell associated with a first uplink carrier and a first downlink carrier, and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell; send to the UE, via the first downlink carrier of the first cell or via the second downlink carrier associated with a third cell, a second indication of subsequent communication to be performed via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both; and perform the subsequent communication with the UE according to the second indication.

[0025] In some examples of the method, network entity, and nontransitory computer-readable medium described herein, sending the second indication may include operations, features, components, or instructions for: sending permission to schedule uplink communication with the UE via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both, wherein the subsequent communication includes the uplink communication.

[0026] In some examples of the method, network entity, and nontransitory computer-readable medium described herein, the grant includes cross-carrier scheduling grant, multi-cell scheduling grant, or both.

[0027] The method described herein, network entities, and some examples of nontransitory computer-readable media may further include operations, features, components, or instructions for identifying a first feedback process associated with uplink communication via the first cell and a second feedback process associated with uplink communication via the second cell.

[0028] The methods, network entities, and some examples of non-transitory computer-readable media described herein may further include operations, features, components, or instructions for: transmitting a reference signal to the UE via the first downlink carrier; and using the reference signal to perform timing and power control operations with the UE.

[0029] In some examples of the method, network entity, and nontransitory computer-readable medium described herein, performing the subsequent communication may include operations, features, components, or instructions for receiving uplink communication from the UE via the second uplink carrier of the second cell, or sending downlink communication to the UE via the first downlink carrier of the first cell, according to a half-duplex scheme.

[0030] In some examples of the method, network entity, and nontransitory computer-readable medium described herein, sending the second instruction may include operations, features, components, or instructions for: sending a system information message to the UE that identifies a first access resource for accessing the first cell via the first uplink carrier and a second access resource for accessing the second cell via the second uplink carrier, wherein the UE accesses the first cell or the second cell based on the first access resource or the second access resource.

[0031] The method described herein, network entities, and some examples of nontransitory computer-readable media may further include operations, features, components, or instructions for: identifying a first access channel timing corresponding to the first access resource and a second access channel timing corresponding to the second access resource, based on the fact that the subsequent communication is scheduled in a TDD scheme.

[0032] In some examples of the method, network entity, and non-transitory computer-readable medium described herein, information is used to identify, based on the first indication, uplink configuration, TDD uplink / downlink configuration, candidate synchronization signal block index set, or any combination thereof for the second uplink carrier used in the second cell.

[0033] In some examples of the method, network entities, and non-transitory computer-readable media described herein, this information may be carried in the eSUL carrier sequence indication.

[0034] In some examples of the method, network entity, and non-transitory computer-readable medium described herein, this information may be carried in the serving cell configuration common system information block eSUL carrier indication. Attached Figure Description

[0035] Figure 1An example of a wireless communication system supporting random access on an enhanced secondary uplink (eSUL) cell, according to one or more aspects of this disclosure, is shown.

[0036] Figure 2 An example of a wireless communication system supporting random access on an eSUL cell is shown, according to one or more aspects of this disclosure.

[0037] Figure 3 An example of a message format supporting random access on an eSUL cell is shown, according to one or more aspects of this disclosure.

[0038] Figure 4 An example of a message format supporting random access on an eSUL cell is shown, according to one or more aspects of this disclosure.

[0039] Figure 5 An example of a message format supporting random access on an eSUL cell is shown, according to one or more aspects of this disclosure.

[0040] Figure 6 and Figure 7 A block diagram of an apparatus supporting random access on an eSUL cell is shown, according to one or more aspects of this disclosure.

[0041] Figure 8 A block diagram of a communication manager supporting random access on an eSUL cell, according to one or more aspects of this disclosure, is shown.

[0042] Figure 9 A diagram of a system including a device supporting random access on an eSUL cell, according to one or more aspects of this disclosure, is shown.

[0043] Figure 10 and Figure 11 A block diagram of an apparatus supporting random access on an eSUL cell is shown, according to one or more aspects of this disclosure.

[0044] Figure 12 A block diagram of a communication manager supporting random access on an eSUL cell, according to one or more aspects of this disclosure, is shown.

[0045] Figure 13 A diagram of a system including a device supporting random access on an eSUL cell, according to one or more aspects of this disclosure, is shown.

[0046] Figures 14 to 18 A flowchart illustrating a method for supporting random access on an eSUL cell according to one or more aspects of this disclosure is shown. Detailed Implementation

[0047] Wireless networks can use secondary uplink carrier (SUL) cells for communication between user equipment (UE) and the network. The network can use SUL in cells with both downlink and uplink carriers (e.g., DL+UL+SUL). That is, in a cell with both uplink and downlink carriers, the SUL can be configured as a secondary UL carrier. Such networks may not have a framework to support enhanced SUL (eSUL), in which the SUL is located in a cell without an associated downlink carrier.

[0048] Therefore, the described aspects of the technology provide a unified framework for supporting eSUL within a wireless network. Broadly speaking, eSUL can be considered as an uplink carrier of a cell where the cell does not have an associated downlink carrier (e.g., it is an uplink-only cell). This can include signaling or otherwise instructing the user equipment (UE) to a first indication to a first cell. The first cell can be a conventional cell, as it includes both uplink and downlink carriers. The first indication can also identify a second cell (e.g., eSUL). The second cell may not have an associated downlink carrier, making it an uplink-only cell. The UE can receive a second indication for subsequent communication to be performed. This indication can be received via a downlink carrier of the first cell or via a different downlink carrier from a third cell. The second indication can schedule subsequent communication. The UE can perform subsequent communication via eSUL and / or via an uplink carrier of the first cell. Subsequent communication can include uplink / downlink communication and / or random access channel communication.

[0049] The various aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to random access on an eSUL cell.

[0050] Figure 1 An example of a wireless communication system 100 supporting random access on an eSUL cell 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.

[0051] 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).

[0052] 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 Examples of UE 115 are illustrated herein. The UE 115 described herein can be able to support communication with various types of devices, such as other UE 115s or network entities 105, such as Figure 1 As shown.

[0053] 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.

[0054] 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.

[0055] 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).

[0056] 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)).

[0057] 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. Additionally or alternatively, 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.

[0058] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can 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.

[0059] 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), where 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).

[0060] 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 for UE transmissions via 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 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.

[0061] 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.

[0062] 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 random access on eSUL 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).

[0063] 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.

[0064] 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, relay base stations, etc. Figure 1 As shown.

[0065] 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 with 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).

[0066] 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.

[0067] 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).

[0068] 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 a hardware configuration that supports communication using a specific carrier bandwidth, or may be configured to support communication using one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or 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.

[0069] 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.

[0070] 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, UE 115 can be configured with multiple BWPs. 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.

[0071] 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).

[0072] 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.

[0073] 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. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0074] 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., 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., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of 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 search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0075] 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.

[0076] 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.

[0077] 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)).

[0078] 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.

[0079] 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.

[0080] 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.

[0081] Some UE 115s can be configured to operate in reduced power consumption modes, 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 reduced peak rates. 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.

[0082] 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, 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 prioritizing 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.

[0083] 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.

[0084] 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 a combination of these. Vehicles may signal information related to traffic conditions, signal control, 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.

[0085] 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 transferred through user plane entities, which provide IP address allocation and other functions. User plane entities 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.

[0086] 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 wavelengths 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).

[0087] The wireless communication system 100 can also operate in the ultra-high frequency (SHF) band (also known as the centimeter band) or the extremely high frequency (EHF) band (e.g., 30 GHz to 300 GHz) (also known as the millimeter band) range, which can utilize the spectrum from 3 GHz to 30 GHz. 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 across transmissions using one or more different frequency bands, and the frequency band usage specified across these frequency bands may vary by country or regulatory authority.

[0088] 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.

[0089] 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.

[0090] 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), for which multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), for which multiple spatial layers are transmitted to multiple devices.

[0091] 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).

[0092] 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.

[0093] 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.

[0094] 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).

[0095] 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).

[0096] 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.

[0097] 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 can 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.

[0098] UE 115 may receive a first indication for a first cell associated with a first uplink carrier and a first downlink carrier, and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell. UE 115 may receive a second indication, via the first downlink carrier of the first cell or via the second downlink carrier associated with a third cell, for subsequent communication to be performed via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both. UE 115 may perform the subsequent communication according to the second indication, wherein the subsequent communication includes access communication, uplink communication, or at least one of both.

[0099] Network entity 105 may send a first indication to UE 115 regarding a first cell associated with a first uplink carrier and a first downlink carrier, and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell. Network entity 105 may send a second indication to UE 115 via the first downlink carrier of the first cell or via the second downlink carrier associated with a third cell, regarding subsequent communication to be performed via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both. Network entity 105 may perform the subsequent communication with UE 115 according to the second indication.

[0100] Figure 2 An example of a wireless communication system 200 supporting random access on an eSUL cell according to one or more aspects of this disclosure is shown. Wireless communication system 200 may implement aspects of wireless communication system 100. Wireless communication system 200 may include UE 205, network entity 210, and network entity 215, which may be examples of the corresponding devices described herein. For example, network entity 210 may be an example of a first cell associated with a first uplink carrier 225 and a first downlink carrier 220. Network entity 215 may be an example of a second cell associated with a second uplink carrier 230 (e.g., the second cell may be an uplink-only cell without a downlink carrier).

[0101] The wireless network can support different configurations for providing a secondary uplink carrier for UE 205. One example may include support for a SUL (Supplemental Uplink Carrier), which is configured to allow the UE to support enhanced uplink services from UE 205. This SUL configuration typically includes a cell with a downlink carrier and two uplink carriers, where the second uplink carrier is designated as the SUL carrier to supplement uplink communication. Another example may include support for UL-CA (Ultra-Ultra-Cardinal Array), where multiple cells are configured to support uplink communication. In a UL-CA configuration, a regular cell is assigned to support the uplink carrier (e.g., via its uplink carrier), while the downlink carrier of the primary cell and / or the downlink carrier of the secondary cell are used to schedule the uplink carrier.

[0102] However, the network handles these SUL / UL-CA scenarios differently (e.g., scheduling / configuration in different ways). This is partly due to the fact that each scenario has or otherwise supports different capabilities / functions within the radio network. For example, SUL does not support simultaneous uplink transmission and / or multi-cell scheduling, while UL-CA does. SUL can support random access in idle mode, but UL-CA may not support random access via a secondary uplink carrier in this mode. The HARQ process is also different, where the SUL scenario is configured with one HARQ space for the UL / SUL carriers of the serving cell, while the UL-CA scenario uses a separate HARQ space for each CC. The scheduling mechanisms used for each scenario are also different (e.g., indicating UL / SUL for SUL in the DCI, and using the Carrier Indicator Field (CIF) in the DCI to distinguish uplink carrier scheduling). Finally, uplink transmission handover is supported in the SUL scenario, but in UL-CA, uplink transmission handover is only supported when the "switchedUL" or "dualUL" indicator is configured.

[0103] Both the SUL and UL-CA scenarios involve at least one cell configured to enable UE 205 to support enhanced uplink communication. An SUL configuration includes a cell with a downlink carrier, an uplink carrier and a downlink carrier, or a downlink carrier, an uplink carrier, and a SUL carrier. A UL-CA configuration includes only a downlink carrier, or a downlink carrier and an uplink carrier. Multiple cells (each with a downlink carrier, or a downlink carrier and an uplink carrier) are configured to enable UE 205 to support enhanced uplink communication.

[0104] Therefore, the various aspects of the technology described in this paper provide a unified framework approach for using eSUL. eSUL is typically configured as a second cell to support uplink communication with UE 205. eSUL is an uplink-only cell because it does not have a downlink carrier. This is in Figure 2 As shown, network entity 210 is a first cell with both downlink and uplink carriers, and network entity 215 is only an uplink carrier.

[0105] This may include UE 205 receiving or otherwise obtaining a first indication associated with a first cell (e.g., network entity 210) and a second cell (e.g., network entity 215), the first cell being associated with a first downlink carrier 220 and a first uplink carrier 225, and the second cell being associated with a second uplink carrier 230. As discussed, the second cell is an uplink-only cell because it does not have an integrated downlink carrier. The first indication may be received via RRC signaling and / or via higher-layer signaling. The first indication may typically identify, select, or otherwise configure the first and second cells to support communication with UE 205. Regarding Figures 3 to 5 More specific examples of the first instruction are discussed.

[0106] UE 205 may receive or otherwise obtain a second indication of subsequent communication to be performed via a first uplink carrier 225 and / or via a second uplink carrier 230. The second indication may be received via a first downlink carrier 220 of a first cell and / or via a second downlink carrier of a third cell (e.g., a different cell with a downlink carrier other than the first cell). UE 205 may perform the subsequent communication according to the second indication. In some aspects, the subsequent communication may be uplink communication and / or access communication.

[0107] An example of uplink communication may include UE 205 receiving permission to schedule uplink communication via a first uplink carrier 225 and / or via a second uplink carrier 230. This permission may be received when UE 205 is operating in a connected mode (e.g., a power-saving mode). In some respects, eSUL may be considered UL-CC of UL-CA, but without a downlink carrier in the cell.

[0108] For example, the grant may include a PDCCH 235 (e.g., DCI-based grant) received from a first cell via a first downlink carrier 220 (in this non-limiting example). The grant may schedule a PDSCH 240 (e.g., downlink communication) via the first downlink carrier 220, a PUSCH 245 (e.g., uplink communication) via a first uplink carrier 225, and / or a PUSCH 250 (e.g., uplink communication) via a second uplink carrier 230. The grant may carry or otherwise convey an indication of a CIF field used to distinguish subsequent communication scheduled on the first cell from subsequent communication scheduled on a second cell (e.g., eSUL). For example, a CIF field set to "0" may indicate that subsequent communication was scheduled via the first cell, and a CIF field set to "1" may indicate that subsequent communication was scheduled via the second cell, and vice versa.

[0109] In some examples, scheduling the first cell and eSUL in this manner can support both cross-carrier scheduling and / or multi-cell scheduling. For example, the grant (e.g., PDCCH 235) can be a cross-carrier grant and / or a multi-cell scheduling grant. Scheduling in this manner can support configuring an independent HARQ space for each UL / eSUL. That is, a first feedback process (e.g., HARQ) can be associated with uplink communication via the first cell, and a second feedback process can be associated with uplink communication via the second cell.

[0110] For timing / power control functions, scheduling in this manner may include configuring the eSUL (e.g., the second cell) using reference signals in the first cell or different cells (e.g., the third cell). That is, since the eSUL does not have an associated downlink carrier, the downlink carriers of the first cell and / or the third cell can be used for channel performance measurements and reporting, which can be used for power control operations (and many other operations) for the eSUL. For example, UE 205 may receive a reference signal transmitted via the first downlink carrier 220 and / or via the second downlink carrier of the second cell, and use this reference signal to perform timing and power control operations for the second uplink carrier 230. That is, channel performance measurements can be used to select the uplink transmit power, MCS, repetition, etc., for uplink communication performed via the second uplink carrier 230 of the second cell.

[0111] In some respects, this type of connectivity mode scheduling can support half-duplex capability between the eSUL and the downlink cell (e.g., a cell with a downlink carrier, which could be a downlink carrier of a first cell or a third cell). For example, UE 205 can transmit uplink communication via a second uplink carrier 230 or receive downlink communication via a first downlink carrier 220 (or a downlink carrier of a third cell) according to a half-duplex scheme. The half-duplex scheme can be triggered and / or identified by permission and / or by other signaling means.

[0112] Connection mode scheduling (e.g., via PDCCH 235) can also support UE 205 to perform simultaneous uplink transmissions or uplink transmission handovers (e.g., options 1 / 2) via the first uplink carrier 225 and the second uplink carrier 230. For example, UE 205 can perform simultaneous transmissions on the first uplink carrier 225 and the second uplink carrier 230, or perform non-simultaneous transmissions on the first uplink carrier 225 and the second uplink carrier 230 of the first cell. Simultaneous transmissions can be performed according to a simultaneous transmission antenna handover scheme. Non-simultaneous transmissions can be performed according to an uplink transmission antenna handover scheme.

[0113] An example of access communication may include UE 205 receiving a system information message (e.g., SIB 255) that identifies a first access resource (e.g., PRACH 260) for accessing a first cell via a first uplink carrier 225 and a second access resource (e.g., PRACH 265) for accessing a second cell via a second uplink carrier 230. In some aspects, UE 205 may operate in idle mode while monitoring and receiving system information messages. SIB 255 may carry information regarding eSUL and the first uplink carrier 225 available for random access (e.g., identifying the resource). The UE may then identify or otherwise select the first uplink carrier 225 or the second uplink carrier 230 for random access (e.g., via the associated PRACH resource). In some examples, this may include the UE 205 identifying or otherwise determining the first access channel timing (e.g., the first PRACH timing) of the first access resource (e.g., PRACH 260) and the second access channel timing (e.g., the second PRACH timing) of the second access resource (e.g., PRACH 265).

[0114] although Figure 2 The unified framework illustrated here shows an eSUL configured in a second cell different from the first cell; however, it should be understood that in some examples, the second cell may be configured as a virtual cell within the first cell. That is, the first cell may have two uplink carriers, and the second uplink carrier may be scheduled as, or otherwise treated as, a separate cell (e.g., an eSUL) similarly scheduled or otherwise configured with the features discussed above. For example, when UE 205 operates in connected mode, the eSUL may also be treated as a UL-CC of a UL-CA without a downlink carrier. When UE 205 operates in idle mode, the access features discussed above may also be applied to the uplink carrier and eSUL carrier of the cell.

[0115] In some respects, PRACH selection can be based on the UE being configured for subsequent communication using eSUL in the TDD band. That is, the PRACH timing selection techniques described herein can be based on whether the serving cell (e.g., the first cell) and / or eSUL (e.g., the second cell) are configured with TDD UL-DL, such as using the references below. Figures 3 to 5 The message receiving and sending scheme under discussion.

[0116] Figure 3 An example of a message format 300 supporting random access on an eSUL cell according to one or more aspects of this disclosure is shown. Aspects of message format 300 may be implemented in or by aspects of wireless communication system 100 and / or wireless communication system 200. Aspects of message format 300 may be implemented at or by a UE and / or network entity, which may be examples of the corresponding devices described herein. For example, the network entity may be associated with a first cell or a second cell for wireless communication with the UE.

[0117] As discussed above, aspects of the technology described herein support (e.g., via a first indication) configuring the UE using a first cell having both uplink and downlink carriers and a second cell as an uplink-only cell (e.g., having an uplink carrier but no downlink carrier). The UE may receive a second indication for subsequent uplink communication. Subsequent communication may be uplink communication and / or access communication (e.g., via a first uplink carrier of the first cell and / or via a second uplink carrier of the second cell). Uplink communication may be scheduled via a DCI that is permitted to be carried on a first downlink carrier of the first cell and / or carried on a second downlink carrier of a third cell (e.g., because the second cell does not have a downlink carrier). Access communication may include an SIB that indicates PRACH resources (e.g., access resources) for the uplink carrier of the first cell and / or for the uplink carrier of the second cell (e.g., eSUL).

[0118] Typically, when access communication occurs via paired spectrum or supplemental uplink bands (e.g., for FDD-based networks), the UE can usually select from all PRACH timings. For TDD-based networks, the UE can select the PRACH timing based on whether the UE is configured with the tdd-UL-DL-ConfigurationCommon parameter and other factors. Therefore, for FDD and legacy SUL configurations, there are no instances of invalid PRACH timings. However, for TDD networks, the validity / invalidity of a PRACH timing depends on one or more of the time-domain resources for the candidate SSB of the cell, the TDD UL-DL configuration of the cell, and / or the next channel occupancy time (e.g., for cells with both uplink and downlink carriers).

[0119] Therefore, in legacy SUL operation, the carrier is always configured in the FDD band, where the SUL is configured with an uplink symbol in its band. However, the eSUL discussed herein can be configured for both FDD and / or TDD operation, and / or can be configured for operation in shared or unlicensed RF bands. From the UE's perspective, configuration in the TDD band may result in the eSUL becoming a cell with only an uplink carrier. However, from the network's perspective, when configured for TDD operation, the eSUL is a cell / carrier / frequency that can have both downlink and uplink. When the eSUL is configured in a TDD or unlicensed band, there are time-domain resources that are unavailable for uplink transmission due to SSB candidate, TDD UL-DL configuration, and / or next channel occupancy time.

[0120] Therefore, when operating in FDD bands, some techniques can utilize existing mechanisms used for eSUL because all PRACH timings are available. However, such techniques may not be applicable when eSUL is configured in TDD or unlicensed bands because all PRACH timings may be unavailable to the UE (e.g., due to uplink / downlink / special symbol-level configurations in TDD bands). In other words, TDD UL-DL configurations are typically different for the first cell and for eSUL.

[0121] Therefore, various aspects of message format 300 can be implemented when configuring the UE using the first cell and the second cell. That is, message format 300 illustrates a non-limiting example of a first indication that can be provided to the UE to configure or otherwise identify a first cell having both an uplink carrier and a downlink carrier, and a second cell as an uplink-only cell (e.g., without a downlink carrier). In some aspects, message format 300 illustrates an example of a ServingCellConfigCommonSIB parameter indicated via RRC signaling (e.g., configuration message 305). However, it should be understood that the features discussed with respect to message format 300 are equally applicable to ServingCellConfigCommon parameters indicated via RRC signaling. That is, the eSUL features discussed with reference to message format 300 can be applied to the ServingCellConfigCommon parameter.

[0122] Generally, the ServingCellConfigCommonSIB / ServingCellConfigCommon parameters typically indicate the candidate SSB index, TDD UL-DL configuration, and channel access mode for the serving cell (e.g., the first cell in this example). However, configuration message 305 illustrates a non-limiting example of how to configure both the serving cell (e.g., the first cell in this example) and eSUL (e.g., the second cell in this example) for a UE.

[0123] This may include configuration message 305, which in the first line indicates the "downlinkConfigCommon—DownlinkConfigCommonSIB" parameter, which identifies various downlink resources configured for the first cell. The second line may indicate the "uplinkConfigCommon—UplinkConfigCommonSIB" parameter, which identifies the RACH, PUCCH, and PUSCH configuration for the NUL carrier of the first cell. The third line may indicate the "supplementaryUplink—UplinkConfigCommonSIB" parameter, which identifies the RACH, PUCCH, and PUSCH configuration for the SUL carrier of the cell. That is, if the first cell has two uplink carriers, a primary uplink carrier (NUL) and a secondary uplink carrier (SUL), this third line may configure the SUL for the UE. However, it should be understood that since the UE is configured with the eSUL of the second cell, this third line may be deleted from the configuration message 305 (e.g., without signaling notification).

[0124] The fourth line can identify the "tdd-UL-DL-ConfigurationCommon—TDD-UL-DL-ConfigCommon" parameter, the fifth line can identify the "ssb-PistionInBurst—Bit strings" parameter, and the sixth line can identify the "channelAccessMode-r16—Choice (dynamic or semi-static)". These three lines typically identify the candidate SSB indexes, TDD UL-DL configuration, and channel access mode (e.g., in unlicensed bands) for the downlink and uplink carriers (e.g., NUL) used in the first cell (e.g., the serving cell in this example).

[0125] However, configuration message 305 also carries or otherwise conveys information for identifying, selecting, or otherwise configuring the UE using a second cell (e.g., eSUL) with only uplink carriers. That is, in addition to providing uplink configuration for eSUL, configuration message 305 also provides the UE with the eSUL's TDD UL-DL configuration and candidate SSB index (e.g., the first indication includes an eSUL indication for configuring a second cell for the UE).

[0126] For example, the seventh line may identify the "eSUL-UplinkConfigCommonSIB" parameter, which identifies the RACH, PUCCH, and PUSCH configurations used for eSUL. The seventh line may also identify the "ssb-PositionInBursteSUL-Bit strings" parameter, the eighth line may identify the "tdd-UL-DL-ConfigurationCommoneSUL-TDD-UL-DL-ConfigCommon" parameter, and the ninth line may identify the "channelAccessModeeSUL-CHOICE (dynamic or semi-static)" parameter. These three parameters typically carry or otherwise convey information identifying the candidate SSB index, TDD UL-DL configuration, and channel access mode for the cell / carrier / frequency configured as eSUL (e.g., the second cell in this example).

[0127] Therefore, in some examples, the first indication may carry or otherwise transmit information identifying the uplink configuration, TDD UL / DL configuration, and / or candidate SSB index set for both the serving cell (e.g., the first cell) and the eSUL (e.g., the second cell). This allows the network to configure the idle-mode UE using both the PRACH resources (e.g., the first access resource) for the first uplink carrier of the first cell and the PRACH resources (e.g., the second access resource) for the second uplink carrier of the second cell.

[0128] Figure 4 An example of a message format 400 supporting random access on an eSUL cell according to one or more aspects of this disclosure is shown. Aspects of message format 400 may implement aspects of wireless communication system 100 and / or wireless communication system 200 and / or aspects of message format 300. Aspects of message format 400 may be implemented at or by a UE and / or a network entity, which may be examples of the corresponding devices described herein. For example, a network entity may be associated with a first cell or a second cell for wireless communication with a UE.

[0129] As discussed above, aspects of the technology described herein support (e.g., via a first instruction) configuring the UE using a first cell having both uplink and downlink carriers and a second cell as an uplink-only cell (e.g., having an uplink carrier but no downlink carrier). The UE can receive a second instruction for subsequent uplink communication and perform subsequent communication according to the second instruction. Subsequent communication can be uplink communication and / or access communication (e.g., via a first uplink carrier of the first cell and / or via a second uplink carrier of the second cell). Uplink communication can be scheduled via a DCI that is permitted to be carried on a first downlink carrier of the first cell and / or carried on a second downlink carrier of a third cell (e.g., because the second cell does not have a downlink carrier). Access communication may include an SIB that indicates PRACH resources (e.g., access resources) for the uplink carrier of the first cell and / or for the uplink carrier of the second cell (e.g., eSUL).

[0130] As discussed above, the eSUL discussed herein can be configured for both FDD and / or TDD operation, and / or can be configured for operation in shared or unlicensed radio spectrum bands. Therefore, aspects of message format 400 can be implemented when configuring the UE using a first cell and a second cell. That is, message format 400 illustrates a non-limiting example of a first indication that can be provided to the UE to configure or otherwise identify a first cell having both uplink and downlink carriers and a second cell as an uplink-only cell (e.g., without a downlink carrier). In some aspects, message format 400 illustrates an example of a ServingCellConfigCommonSIB parameter indicated via RRC signaling (e.g., configuration message 405). However, it should be understood that the features discussed with respect to message format 400 are equally applicable to ServingCellConfigCommon parameters indicated via RRC signaling. That is, the eSUL features discussed with reference to message format 400 can be applied to the ServingCellConfigCommon parameter.

[0131] Generally, the ServingCellConfigCommonSIB / ServingCellConfigCommon parameters typically indicate the candidate SSB index, TDD UL-DL configuration, and channel access mode for the serving cell (e.g., the first cell in this example). However, configuration message 405 illustrates a non-limiting example of how to configure both the serving cell (e.g., the first cell in this example) and eSUL (e.g., the second cell in this example) for a UE.

[0132] Typically, the parameters indicated in lines 1 through 5 are similar to those discussed in lines 1 through 6 of configuration message 305 above (e.g., minus the channel access mode). These parameters typically identify the uplink and / or downlink resources, TDD UL-DL configuration, and candidate SSB index for the first cell.

[0133] However, configuration message 405 illustrates a non-limiting example of how the first indication carries or otherwise conveys information for identifying, selecting, or otherwise configuring the UE using a second cell (e.g., an eSUL) with only an uplink carrier. That is, in addition to providing uplink configuration for the eSUL, configuration message 405 also provides the UE with the eSUL's TDD UL-DL configuration and candidate SSB index (e.g., the first indication includes an eSUL indication for configuring the second cell for the UE). However, this information is provided in an "eSUL configuration" sequence indication for configuring the UE using one or more second cells (e.g., one or more eSULs). For example, if multiple eSULs are associated with a cell having a downlink carrier, the eSUL configuration can be a configuration list, in which case each entry in the list provides the necessary parameters for the eSUL in that entry, such as uplink configuration, TDD UL-DL configuration, and / or candidate SSB index. For example, a UE can be configured with “eSULToAddModList—SEQUENCE (Size (1,…,maxNrofeSULs) of eSUL-Config”, which indicates and / or otherwise identifies how many cells and / or which cells are configured as eSULs for the UE. Each identified eSUL can be associated with a unique identifier or sequence used to distinguish different eSULs. Each identifier or sequence can then be used to provide information identifying each eSUL configured for the UE.

[0134] For a given eSUL sequence, configuration message 405 may include the “eSUL-ULConfig—UplinkConfigCommonSIB” parameter, which identifies the RACH, PUCCH, and PUSCH configurations used for the eSUL. The “ssb-PositionInBurst—Bit strings” parameter, the “tdd-UL-DL-ConfigurationCommon—TDD-UL-DL-ConfigCommon” parameter, and the “channelAccessModeeSUL—CHOICE (dynamic or semi-static)” parameter identify the candidate SSB index, TDD UL-DL configuration, and channel access mode used to configure the cell / carrier / frequency for the eSUL associated with the eSUL sequence (e.g., the second cell in this example).

[0135] Therefore, in some examples, the first indication may carry or otherwise convey information identifying the uplink configuration, TDD UL / DL configuration, and / or candidate SSB index set for both the serving cell (e.g., the first cell) and one or more eSULs (e.g., the second cell). This allows the network to configure the idle-mode UE using both the PRACH resources (e.g., the first access resource) for the first uplink carrier of the first cell and the PRACH resources (e.g., the second access resource) for the second cell or the additional eSUL. Configuration message 405 illustrates a non-limiting example where configurations for eSULs can be provided in a list configuration when multiple eSULs are associated with a cell having a downlink carrier, in which case each entry in the list (e.g., each eSUL sequence) provides the necessary parameters (e.g., such as uplink configuration, TDD UL-DL configuration, etc.) for the eSUL in that particular entry.

[0136] It should be understood that referring to a second cell (e.g., eSUL) as associated with a downlink carrier does not mean that the eSUL has a downlink carrier. Rather, it should be understood that the eSUL can be configured as a separate cell relative to a serving cell that has both an uplink carrier and a downlink carrier. However, the eSUL can be linked to or otherwise associated with a different cell that has a downlink carrier. Subsequently, the downlink carrier of that cell can be used for scheduling, reference signaling, or other functions typically associated with the downlink carrier of the serving cell. For example, the downlink carrier of another cell can be used for channel performance and measurement operations, power control operations, etc., against a second uplink carrier of the second cell.

[0137] Figure 5 An example of a message format 500 supporting random access on an eSUL cell according to one or more aspects of this disclosure is shown. Aspects of message format 500 may implement aspects of wireless communication system 100 and / or wireless communication system 200 and / or aspects of message format 300 and / or message format 400. Aspects of message format 500 may be implemented at or by a UE and / or a network entity, which may be an example of the corresponding device described herein. For example, the network entity may be associated with a first cell or a second cell for wireless communication with the UE.

[0138] As discussed above, aspects of the technology described herein support (e.g., via a first instruction) configuring the UE using a first cell having both uplink and downlink carriers and a second cell as an uplink-only cell (e.g., having an uplink carrier but no downlink carrier). The UE can receive a second instruction for subsequent uplink communication and perform subsequent communication according to the second instruction. Subsequent communication can be uplink communication and / or access communication (e.g., via a first uplink carrier of the first cell and / or via a second uplink carrier of the second cell). Uplink communication can be scheduled via a DCI that is permitted to be carried on a first downlink carrier of the first cell and / or carried on a second downlink carrier of a third cell (e.g., because the second cell does not have a downlink carrier). Access communication may include an SIB that indicates PRACH resources (e.g., access resources) for the uplink carrier of the first cell and / or for the uplink carrier of the second cell (e.g., eSUL).

[0139] As discussed above, the eSUL discussed herein can be configured for both FDD and / or TDD operation, and / or can be configured for operation in shared or unlicensed radio spectrum bands. Therefore, aspects of message format 500 can be implemented when configuring the UE using a first cell and a second cell. That is, message format 500 exemplifies a non-limiting example of a first indication that can be provided to the UE to configure or otherwise identify a first cell having both uplink and downlink carriers and a second cell as an uplink-only cell (e.g., without a downlink carrier). In some aspects, message format 500 exemplifies an example of a ServingCellConfigCommonSIB parameter indicated via RRC signaling (e.g., configuration message 505). However, it should be understood that the features discussed with respect to message format 500 are equally applicable to ServingCellConfigCommon parameters indicated via RRC signaling. That is, the eSUL features discussed with reference to message format 500 can be applied to the ServingCellConfigCommon parameter.

[0140] Generally, the ServingCellConfigCommonSIB / ServingCellConfigCommon parameters typically indicate the candidate SSB index, TDD UL-DL configuration, and channel access mode for the serving cell (e.g., the first cell in this example). However, configuration message 505 illustrates a non-limiting example of how to configure both the serving cell (e.g., the first cell in this example) and eSUL (e.g., the second cell in this example) for the UE. Specifically, configuration message 505 illustrates a non-limiting example where the ServingCellConfigCommonSIB parameter carries all parameters for the RACH, candidate SSB, TDD UL-DL configuration, and channel access for eSUL.

[0141] Typically, the parameters indicated in lines 1 through 5 are similar to those discussed in lines 1 through 6 of configuration message 305 above (e.g., minus the channel access mode). These parameters typically identify the uplink and / or downlink resources, TDD UL-DL configuration, and candidate SSB index for the first cell (e.g., the UE's serving cell).

[0142] However, configuration message 505 illustrates a non-limiting example of how the first indication carries or otherwise conveys information for identifying, selecting, or otherwise configuring the UE using a second cell (e.g., an eSUL) with only an uplink carrier. That is, in addition to providing uplink configuration for the eSUL, configuration message 505 also provides the UE with the eSUL's TDD UL-DL configuration and candidate SSB index (e.g., the first indication includes an eSUL indication for configuring the second cell for the UE). However, this information is provided in a “ServingCellConfigCommonSIBeSUL” indication, which is used to configure the UE using one or more second cells (e.g., one or more eSULs). For example, if multiple eSULs are associated with a cell having a downlink carrier, the eSUL configuration can be a configuration list, in which case each entry in the list provides the necessary parameters for the eSUL in that entry, such as uplink configuration, TDD UL-DL configuration, and / or candidate SSB index. For example, a UE can be configured with "ServingCellConfigCommonSIBeSUL_SEQUENCE", a parameter that indicates and / or otherwise identifies how many cells and / or which cells are configured as eSULs for the UE. Each identified eSUL can be associated with a unique identifier or sequence used to distinguish different eSULs. Each identifier or sequence can then be used to provide information identifying each eSUL configured for the UE.

[0143] For a given eSUL sequence, configuration message 505 may include the “ULConfigCommon—UplinkConfigCommonSIB” parameter, which identifies the RACH, PUCCH, and PUSCH configurations used for the eSUL. The “ssb-PositionInBurst—Bit strings” parameter, the “tdd-UL-DL-ConfigurationCommon—TDD-UL-DL-ConfigCommon” parameter, and the “channelAccessModeeSUL—CHOICE (dynamic or semi-static)” parameter respectively identify the candidate SSB index, TDD UL-DL configuration, and channel access mode for the cell / carrier / frequency configured for the eSUL associated with the eSUL sequence (e.g., the second cell in this example).

[0144] Therefore, in some examples, the first indication may carry or otherwise convey information identifying the uplink configuration, TDD UL / DL configuration, and / or candidate SSB index set for both the serving cell (e.g., the first cell) and one or more eSULs (e.g., the second cell). This allows the network to configure the idle-mode UE using both the PRACH resources (e.g., the first access resource) for the first uplink carrier of the first cell and the PRACH resources (e.g., the second access resource) for the second cell or the additional eSUL. Configuration message 505 illustrates a non-limiting example where configurations for eSULs can be provided in a list configuration when multiple eSULs are associated with a cell having a downlink carrier, in which case each entry in the list (e.g., each eSUL sequence) provides the necessary parameters (e.g., such as uplink configuration, TDD UL-DL configuration, etc.) for the eSUL in that particular entry.

[0145] Figure 6 A block diagram 600 illustrates a device 605 supporting random access on an eSUL cell according to one or more aspects of this disclosure. Device 605 may be an example of various aspects of 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 that may be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0146] 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 random access on an eSUL cell). The information may be passed to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

[0147] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information associated with various information channels (e.g., control channels, data channels, information channels associated with random access on an eSUL cell), such as packets, user data, control information, or any combination thereof. 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.

[0148] The communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of random access on an eSUL cell as described herein. For example, the communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0149] In some examples, the communication manager 620, receiver 610, transmitter 615, 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 component, 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). For example, the communication manager 620 may be configured to receive or transmit messages or other signaling as described herein via a transceiver (e.g., receiver 610 and / or transmitter 615).

[0150] Additionally or alternatively, the communication manager 620, receiver 610, transmitter 615, 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 620, receiver 610, transmitter 615, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of 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).

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

[0152] Communication manager 620 may support wireless communication according to examples disclosed herein. For example, communication manager 620 may be capable of, configured to, or operable to support components for: receiving a first indication for a first cell associated with a first uplink carrier and a first downlink carrier, and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell. Communication manager 620 may be capable of, configured to, or operable to support components for: receiving a second indication for subsequent communication to be performed via the first downlink carrier of the first cell or via the second downlink carrier associated with a third cell, or both. Communication manager 620 may be capable of, configured to, or operable to support components for: performing the subsequent communication according to the second indication, wherein the subsequent communication includes access communication, uplink communication, or at least one of both.

[0153] By including or configuring a communication manager 620 according to an example as described herein, device 605 (e.g., control receiver 610, transmitter 615, communication manager 620, or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for configuring the UE using a serving cell having both uplink and downlink carriers, as well as an eSUL having only an uplink carrier. The eSUL can be configured individually for the UE (e.g., relative to the serving cell) via RRC signaling carrying or delivering eSUL parameters for a single eSUL and / or for multiple eSULs.

[0154] Figure 7 A block diagram 700 illustrates a device 705 supporting random access on an eSUL cell according to one or more aspects of this disclosure. Device 705 may be an example of aspects of device 605 or UE 115 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705, or one or more components of device 705 (e.g., receiver 710, transmitter 715, and communication manager 720), may include at least one processor that may 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).

[0155] Receiver 710 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 random access on an eSUL cell). The information may be passed to other components of device 705. Receiver 710 may utilize a single antenna or a collection of antennas.

[0156] Transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information associated with various information channels (e.g., control channels, data channels, information channels associated with random access on an eSUL cell), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0157] Device 705 or its various components may be examples of parts used to perform various aspects of random access on an eSUL cell as described herein. For example, communication manager 720 may include cell manager 725, scheduling manager 730, uplink communication manager 735, or any combination thereof. Communication manager 720 may be examples of aspects of communication manager 620 as described herein. In some examples, communication manager 720 or its various components may be configured to use or otherwise cooperate with receiver 710, transmitter 715, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 720 may receive information from receiver 710, transmit information to transmitter 715, or be integrated in combination with receiver 710, transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0158] Communication manager 720 may support wireless communication according to examples disclosed herein. Cell manager 725 is capable of, configured to, or operable to support components for: receiving a first indication for a first cell associated with a first uplink carrier and a first downlink carrier, and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell. Scheduling manager 730 is capable of, configured to, or operable to support components for: receiving a second indication for subsequent communication to be performed via the first downlink carrier of the first cell or via the second downlink carrier associated with a third cell, or both. Uplink communication manager 735 is capable of, configured to, or operable to support components for: performing the subsequent communication according to the second indication, wherein the subsequent communication includes access communication, uplink communication, or at least one of both.

[0159] Figure 8 A block diagram 800 of a communication manager 820 supporting random access on an eSUL cell according to one or more aspects of this disclosure is shown. The communication manager 820 may be an example of a communication manager 620, a communication manager 720, or aspects thereof as described herein. The communication manager 820 or its various components may be examples of components for performing various aspects of random access on an eSUL cell as described herein. For example, the communication manager 820 may include a cell manager 825, a scheduling manager 830, an uplink communication manager 835, an authorization manager 840, an access manager 845, a carrier identification manager 850, 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).

[0160] Communication manager 820 may support wireless communication according to examples disclosed herein. Cell manager 825 is capable of, configured to, or operable to support components for: receiving a first indication for a first cell associated with a first uplink carrier and a first downlink carrier, and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell. Scheduling manager 830 is capable of, configured to, or operable to support components for: receiving a second indication for subsequent communication to be performed via the first downlink carrier of the first cell or via the second downlink carrier associated with a third cell, or both. Uplink communication manager 835 is capable of, configured to, or operable to support components for: performing the subsequent communication according to the second indication, wherein the subsequent communication includes access communication, uplink communication, or at least one of both.

[0161] In some examples, to support receiving the second instruction, the grant manager 840 is capable, configured, or operable to support components for receiving grants for scheduling uplink communication via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both, wherein the subsequent communication includes the uplink communication. In some examples, the grant includes cross-carrier scheduling grants, multi-cell scheduling grants, or both.

[0162] In some examples, the grant manager 840 is capable of, configured to, or operable to support components for: identifying a first feedback procedure associated with uplink communication via the first cell and a second feedback procedure associated with uplink communication via the second cell. In some examples, the grant manager 840 is capable of, configured to, or operable to support components for: receiving a reference signal transmitted via the first downlink carrier of the first cell, via the second downlink carrier associated with the third cell, or both. In some examples, the grant manager 840 is capable of, configured to, or operable to support components for: performing timing and power control operations using the reference signal.

[0163] In some examples, to support the execution of this subsequent communication, the grant manager 840 is capable, configured, or operable to support components for: transmitting uplink communication via the second uplink carrier of the second cell, or receiving downlink communication via the first downlink carrier of the first cell, according to a half-duplex scheme. In some examples, to support the execution of this subsequent communication, the grant manager 840 is capable, configured, or operable to support components for: performing simultaneous transmission on the first uplink carrier of the first cell and transmission on the second uplink carrier of the second cell, according to a simultaneous transmission antenna switching scheme; or performing non-simultaneous transmission on the first uplink carrier of the first cell and transmission on the second uplink carrier of the second cell, according to an uplink transmission antenna switching scheme.

[0164] In some examples, to support receiving the second instruction, the access manager 845 is capable of, configured to, or able to operate to support components for: receiving system information messages that identify a first access resource for accessing the first cell via the first uplink carrier and a second access resource for accessing the second cell via the second uplink carrier. In some examples, to support receiving the second instruction, the access manager 845 is capable of, configured to, or able to operate to support components for: accessing the first cell or the second cell based on the first access resource or the second access resource.

[0165] In some examples, the access manager 845 is capable of, configured to, or able to operate to support components for: identifying a first access channel timing corresponding to the first access resource and a second access channel timing corresponding to the second access resource, based on the access scheme, since the subsequent communication is scheduled in a TDD scheme.

[0166] In some examples, the carrier identification manager 850 is capable of, configured to, or able to operate to support components that identify, based on the first indication, information regarding the uplink configuration, TDD uplink / downlink configuration, candidate synchronization signal block index set, or any combination thereof, for the second uplink carrier used in the second cell. In some examples, this information is carried in the eSUL carrier sequence indication. In some examples, this information is carried in the serving cell configuration common system information block eSUL carrier indication.

[0167] Figure 9A diagram of a system 900 including device 905 supporting random access on an eSUL cell, according to one or more aspects of this disclosure, is shown. Device 905 may be an example of device 605, device 705, or UE 115 as described herein, or may include components thereof. Device 905 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 905 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, at least one memory 930, a code 935, and at least one processor 940. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 945).

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

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

[0170] At least one memory 930 may include random access memory (RAM) and read-only memory (ROM). At least one memory 930 may store computer-readable, computer-executable code 935, including instructions that, when executed by at least one processor 940, cause device 905 to perform the various functions described herein. Code 935 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 935 may not be directly executable by at least one processor 940, 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 930 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0171] At least one processor 940 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 940 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 940. At least one processor 940 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 930) to cause device 905 to perform various functions (e.g., supporting various functions or tasks of random access on an eSUL cell). For example, device 905 or components of device 905 may include at least one processor 940 and at least one memory 930 coupled to or coupled to at least one processor 940, wherein at least one processor 940 and at least one memory 930 are configured to perform the various functions described herein. In some examples, at least one processor 940 may include multiple processors, and at least one memory 930 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 940 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 940) and memory circuitry (which may include at least one memory 930)) 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 940 or a processing system including at least one processor 940 may be configured, capable of being configured, or operable to cause device 905 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 930 or otherwise.

[0172] 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: receiving a first indication for a first cell associated with a first uplink carrier and a first downlink carrier, and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell. The communication manager 920 may be capable of, configured to, or operable to support components for: receiving a second indication for subsequent communication to be performed via the first downlink carrier of the first cell or via the second downlink carrier associated with a third cell, for the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both. The communication manager 920 may be capable of, configured to, or operable to support components for: performing the subsequent communication according to the second indication, wherein the subsequent communication includes access communication, uplink communication, or at least one of both.

[0173] By including or configuring a communication manager 920 according to an example as described herein, device 905 can support techniques for configuring a UE using a serving cell with both uplink and downlink carriers, as well as an eSUL with only an uplink carrier. The eSUL can be configured individually for the UE (e.g., relative to the serving cell) via RRC signaling carrying or delivering eSUL parameters for a single eSUL and / or for multiple eSULs.

[0174] In some examples, the communication manager 920 may be configured to use or otherwise coordinate with the transceiver 915, one or more antennas 925, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported by or performed by at least one processor 940, at least one memory 930, code 935, or any combination thereof. For example, code 935 may include instructions that can be executed by at least one processor 940 to cause device 905 to perform various aspects of random access on an eSUL cell as described herein, or at least one processor 940 and at least one memory 930 may be otherwise configured to perform or support such operations individually or jointly.

[0175] Figure 10A block diagram 1000 of a device 1005 supporting random access on an eSUL cell according to one or more aspects of this disclosure is shown. Device 1005 may be an example of aspects of 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 may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0176] 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.

[0177] 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.

[0178] The communication manager 1020, receiver 1010, transmitter 1015, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of random access on an eSUL cell as described herein. For example, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0179] In some examples, the communication manager 1020, receiver 1010, transmitter 1015, 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 unit, 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).

[0180] Additionally or alternatively, the communication manager 1020, receiver 1010, transmitter 1015, 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 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of 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).

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

[0182] The communication manager 1020 may support wireless communication according to examples disclosed herein. For example, the communication manager 1020 may be, configured to, or operable to support components for: sending to the UE a first indication of a first cell associated with a first uplink carrier and a first downlink carrier, and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell. The communication manager 1020 may be, configured to, or operable to support components for: sending to the UE a second indication of subsequent communication to be performed via the first downlink carrier of the first cell or via the second downlink carrier associated with a third cell, or both. The communication manager 1020 may be, configured to, or operable to support components for: performing the subsequent communication with the UE according to the second indication.

[0183] By including or configuring a communication manager 1020 according to the example described herein, device 1005 (e.g., controlling receiver 1010, transmitter 1015, communication manager 1020, or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for configuring the UE using a serving cell having both uplink and downlink carriers, as well as an eSUL having only an uplink carrier. The eSUL can be configured individually for the UE (e.g., relative to the serving cell) via RRC signaling carrying or delivering eSUL parameters for a single eSUL and / or for multiple eSULs.

[0184] Figure 11 A block diagram 1100 of a device 1105 supporting random access on an eSUL cell according to one or more aspects of this disclosure is shown. Device 1105 may be an example of aspects of device 1005 or network entity 105 as described herein. Device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. Device 1105, or one or more components of device 1105 (e.g., receiver 1110, transmitter 1115, and communication manager 1120), may include at least one processor that may 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).

[0185] Receiver 1110 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 1105. In some examples, receiver 1110 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0186] Transmitter 1115 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1105. For example, transmitter 1115 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 1115 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1115 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 1115 and receiver 1110 may be co-located in a transceiver, which may include or be coupled to a modem.

[0187] Device 1105 or its various components may be examples of parts used to perform various aspects of random access on an eSUL cell as described herein. For example, communication manager 1120 may include cell manager 1125, scheduling manager 1130, uplink communication manager 1135, or any combination thereof. Communication manager 1120 may be examples of aspects of communication manager 1020 as described herein. In some examples, communication manager 1120 or its various components may be configured to use or otherwise coordinate with receiver 1110, transmitter 1115, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated in combination with receiver 1110, transmitter 1115, or both to acquire information, output information, or perform various other operations as described herein.

[0188] Communication manager 1120 may support wireless communication according to examples disclosed herein. Cell manager 1125 is capable of, configured to, or operable to support components for: sending to the UE a first indication of a first cell associated with a first uplink carrier and a first downlink carrier, and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell. Scheduling manager 1130 is capable of, configured to, or operable to support components for: sending to the UE a second indication of subsequent communication to be performed via the first downlink carrier of the first cell or via the second downlink carrier associated with a third cell, or both. Uplink communication manager 1135 is capable of, configured to, or operable to support components for: performing the subsequent communication with the UE according to the second indication.

[0189] Figure 12 A block diagram 1200 is shown of a communication manager 1220 supporting random access on an eSUL cell according to one or more aspects of this disclosure. The communication manager 1220 may be an example of a communication manager 1020, a communication manager 1120, or aspects thereof as described herein. The communication manager 1220 or its various components may be examples of components for performing various aspects of random access on an eSUL cell as described herein. For example, the communication manager 1220 may include a cell manager 1225, a scheduling manager 1230, an uplink communication manager 1235, an authorization manager 1240, an access manager 1245, a carrier identifier manager 1250, 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.

[0190] Communication manager 1220 may support wireless communication according to examples disclosed herein. Cell manager 1225 is capable of, configured to, or operable to support components for: sending to the UE a first indication of a first cell associated with a first uplink carrier and a first downlink carrier, and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell. Scheduling manager 1230 is capable of, configured to, or operable to support components for: sending to the UE a second indication of subsequent communication to be performed via the first downlink carrier of the first cell or via the second downlink carrier associated with a third cell, or both. Uplink communication manager 1235 is capable of, configured to, or operable to support components for: performing the subsequent communication with the UE according to the second indication.

[0191] In some examples, to support the transmission of the second instruction, the grant manager 1240 is capable, configured, or operable to support components that transmit grants for scheduling uplink communication with the UE via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both, wherein the subsequent communication includes the uplink communication. In some examples, the grant includes cross-carrier scheduling grants, multi-cell scheduling grants, or both.

[0192] In some examples, the grant manager 1240 is capable of, configured to, or able to operate to support components for: identifying a first feedback procedure associated with uplink communication via the first cell and a second feedback procedure associated with uplink communication via the second cell. In some examples, the grant manager 1240 is capable of, configured to, or able to operate to support components for: transmitting a reference signal to the UE via the first downlink carrier. In some examples, the grant manager 1240 is capable of, configured to, or able to operate to support components for: performing timing and power control operations with the UE using the reference signal.

[0193] In some examples, in order to support the execution of this subsequent communication, the grant manager 1240 is able, can be configured, or is operable to support components for receiving uplink communication from the UE via the second uplink carrier of the second cell, or sending downlink communication to the UE via the first downlink carrier of the first cell, according to a half-duplex scheme.

[0194] In some examples, in order to support the transmission of the second instruction, the access manager 1245 is capable, configured, or able to operate to support components for: sending a system information message to the UE, the system information message identifying a first access resource for accessing the first cell via the first uplink carrier and a second access resource for accessing the second cell via the second uplink carrier, wherein the UE accesses the first cell or the second cell based on the first access resource or the second access resource.

[0195] In some examples, the access manager 1245 is capable of, configured to, or able to operate to support components for: identifying a first access channel timing corresponding to the first access resource and a second access channel timing corresponding to the second access resource, based on the access scheme, since the subsequent communication is scheduled in a TDD scheme.

[0196] In some examples, the carrier identification manager 1250 is capable of, configured to, or operable to support components that identify, based on the first indication, information regarding the uplink configuration, TDD uplink / downlink configuration, candidate synchronization signal block index set, or any combination thereof, for the second uplink carrier used in the second cell. In some examples, this information is carried in the eSUL carrier sequence indication. In some examples, this information is carried in the serving cell configuration common system information block eSUL carrier indication.

[0197] Figure 13 A diagram of a system 1300 including device 1305 supporting random access on an eSUL cell, according to one or more aspects of this disclosure, is shown. Device 1305 may be an example of device 1005, device 1105, or network entity 105 as described herein, or may include components thereof. Device 1305 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 1305 may include components that support output and enable communication, such as a communication manager 1320, a transceiver 1310, an antenna 1315, at least one memory 1325, code 1330, and at least one processor 1335. 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 1340).

[0198] As described herein, transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both. In some examples, transceiver 1310 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1310 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1305 may include one or more antennas 1315 that are capable of transmitting or receiving wireless transmissions (e.g., concurrently). Transceiver 1310 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1315, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1315, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1315 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1315 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1310 may include one or more processors or one or more memory components or be configured to couple to said one or more processors or one or more memory components, said one or more processors or one or more 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 1310, or transceiver 1310 and one or more antennas 1315, or transceiver 1310 and one or more antennas 1315 and one or more processors or one or more memory components (e.g., at least one processor 1335, at least one memory 1325, or both) may be included in a chip or chip assembly mounted in device 1305. In some examples, transceiver 1310 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).

[0199] At least one memory 1325 may include RAM, ROM, or any combination thereof. At least one memory 1325 may store computer-readable, computer-executable code 1330 including instructions that, when executed by one or more of the at least one processor 1335, cause the device 1305 to perform the various functions described herein. The code 1330 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1330 may not be directly executable by one of the at least one processor 1335, but may enable the computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, at least one memory 1325 may also contain a BIOS that controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1335 may include multiple processors, and at least one memory 1325 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).

[0200] At least one processor 1335 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, at least one processor 1335 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 processors in at least one processor 1335. At least one processor 1335 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1325) to cause device 1305 to perform various functions (e.g., supporting various functions or tasks of random access on an eSUL cell). For example, device 1305 or components of device 1305 may include at least one processor 1335 and at least one memory 1325 coupled to one or more processors in at least one processor 1335, wherein at least one processor 1335 and at least one memory 1325 are configured to perform the various functions described herein. At least one processor 1335 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 1330) host functions for performing the functions of device 1305. At least one processor 1335 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1305 (such as within one or more memories of at least one memory 1325). In some examples, at least one processor 1335 may include multiple processors, and at least one memory 1325 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 1335 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 1335) and memory circuitry (which may include at least one memory 1325)) 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 1335 or a processing system including at least one processor 1335 may be configured, can be configured, or can be operated to cause the device 1305 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 1325 or otherwise.

[0201] In some examples, bus 1340 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1340 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 1305, or communication performed between different components of device 1305 that are co-addressable or may be located in different locations (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, at least one memory 1325, code 1330 and at least one processor 1335 may be located in one component of different components or partitioned between different components).

[0202] In some examples, the communication manager 1320 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 1320 may manage the transfer of data communication with client devices, such as one or more UEs 115. In some examples, the communication manager 1320 may manage communication with other network entities 105 and may include a controller or scheduler for coordinating with other network entities 105 to control communication with UE 115. In some examples, the communication manager 1320 may support an X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0203] Communication manager 1320 may support wireless communication according to examples disclosed herein. For example, communication manager 1320 may be capable of, configured to, or operated to support components for: sending to the UE a first indication of a first cell associated with a first uplink carrier and a first downlink carrier, and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell. Communication manager 1320 may be capable of, configured to, or operated to support components for: sending to the UE a second indication of subsequent communication to be performed via the first downlink carrier of the first cell or via the second downlink carrier associated with a third cell, or both. Communication manager 1320 may be capable of, configured to, or operated to support components for: performing the subsequent communication with the UE according to the second indication.

[0204] By including or configuring a communication manager 1320 according to an example as described herein, device 1305 can support techniques for configuring a UE using a serving cell with both uplink and downlink carriers, as well as an eSUL with only an uplink carrier. The eSUL can be configured individually for the UE (e.g., relative to the serving cell) via RRC signaling carrying or delivering eSUL parameters for a single eSUL and / or for multiple eSULs.

[0205] In some examples, the communication manager 1320 may be configured to use or otherwise coordinate with the transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the transceiver 1310, one or more processors in at least one processor 1335, one or more memories in at least one memory 1325, code 1330, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1335, at least one memory 1325, code 1330, or any combination thereof). For example, code 1330 may include instructions that can be executed by one or more processors in at least one processor 1335 to cause the device 1305 to perform various aspects of random access on an eSUL cell as described herein, or at least one processor 1335 and at least one memory 1325 may be otherwise configured to perform or support such operations individually or jointly.

[0206] Figure 14 A flowchart illustrating a method 1400 for supporting random access on an eSUL cell according to various aspects of this disclosure is shown. Operation of method 1400 may be implemented by a UE or its components as described herein. For example, operation of method 1400 may be performed by, as referenced... Figures 1 to 9 The UE 115 described herein performs the following: In some examples, the UE can 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.

[0207] At 1405, the method may include receiving a first indication of a first cell associated with a first uplink carrier and a first downlink carrier, and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell. Operation of block 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1405 may be provided by reference to [reference needed]. Figure 8 The described cell manager 825 is used to execute this.

[0208] At 1410, the method may include receiving a second indication, via the first downlink carrier of the first cell or via a second downlink carrier associated with a third cell, of subsequent communication to be performed via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both. 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 8 The described scheduler 830 is used for execution.

[0209] At 1415, the method may include performing the subsequent communication according to the second instruction, wherein the subsequent communication includes access communication, uplink communication, or at least one of both. 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 8 The described uplink communication manager 835 is used to execute this.

[0210] Figure 15 A flowchart illustrating a method 1500 for supporting random access on an eSUL cell according to various aspects of this disclosure is shown. Operation of method 1500 may be implemented by a UE or its components as described herein. For example, operation of method 1500 may be performed by, as referenced... Figures 1 to 9 The UE 115 described herein performs the following: In some examples, the UE can 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.

[0211] At 1505, the method may include receiving a first indication of a first cell associated with a first uplink carrier and a first downlink carrier, and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell. Operation of block 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1505 may be provided by reference to [reference needed]. Figure 8 The described cell manager 825 is used to execute this.

[0212] At 1510, the method may include receiving a second indication for subsequent communication to be performed via the first downlink carrier of the first cell or via a second downlink carrier associated with a third cell, or both. 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 8 The described scheduler 830 is used for execution.

[0213] At 1515, the method may include receiving permission to schedule uplink communication via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both, wherein the subsequent communication includes the uplink communication. Operation of block 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1515 may be provided by reference to [reference needed]. Figure 8 The described permission manager 840 is used to execute this.

[0214] At 1520, the method may include performing the subsequent communication according to the second instruction, wherein the subsequent communication includes access communication, uplink communication, or at least one of both. Operation of block 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1520 may be provided by reference to [reference needed]. Figure 8 The described uplink communication manager 835 is used to execute this.

[0215] Figure 16 A flowchart illustrating a method 1600 for supporting random access on an eSUL cell according to various aspects of this disclosure is shown. Operation of method 1600 may be implemented by a UE or its components as described herein. For example, operation of method 1600 may be performed by, as referenced... Figures 1 to 9 The UE 115 described herein performs the following: In some examples, the UE can 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.

[0216] At 1605, the method may include receiving a first indication of a first cell associated with a first uplink carrier and a first downlink carrier, and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell. 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 8 The described cell manager 825 is used to execute this.

[0217] At 1610, the method may include receiving a second indication for subsequent communication to be performed via the first downlink carrier of the first cell or via a second downlink carrier associated with a third cell, or both. Operation of block 1610 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1610 may be provided by reference to [reference needed]. Figure 8 The described scheduler 830 is used for execution.

[0218] At 1615, the method may include receiving a system information message that identifies a first access resource for accessing the first cell via the first uplink carrier and a second access resource for accessing the second cell via the second uplink carrier. Operation of block 1615 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1615 may be derived from references... Figure 8 The described access manager 845 is used to execute this.

[0219] At 1620, the method may include accessing the first cell or the second cell based on the first access resource or the second access resource. Operation of block 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1620 may be derived from references... Figure 8 The described access manager 845 is used to execute this.

[0220] At 1625, the method may include performing the subsequent communication according to the second instruction, wherein the subsequent communication includes access communication, uplink communication, or at least one of both. The operation of block 1625 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1625 may be provided by reference to [reference needed]. Figure 8 The described uplink communication manager 835 is used to execute this.

[0221] Figure 17 A flowchart illustrating a method 1700 for supporting random access on an eSUL cell 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 5 as well as Figures 10 to 13 The network entity described herein performs the function. 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 function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0222] At 1705, the method may include sending to the UE a first indication of a first cell associated with a first uplink carrier and a first downlink carrier, and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-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 12 The described cell manager 1225 is used to execute this.

[0223] At 1710, the method may include sending to the UE a second indication, via the first downlink carrier of the first cell or via a second downlink carrier associated with a third cell, of subsequent communication to be performed via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both. Operation of block 1710 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1710 may be provided by reference to [reference needed]. Figure 12 The described scheduler 1230 is used to execute this.

[0224] At 1715, the method may include performing the subsequent communication with the UE according to the second instruction. 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... Figure 12 The described uplink communication manager 1235 is used to execute this.

[0225] Figure 18 A flowchart illustrating a method 1800 for supporting random access on an eSUL cell according to various aspects of this disclosure is shown. The operation of method 1800 may be implemented by a network entity or its components as described herein. For example, the operation of method 1800 may be implemented by, as referenced... Figures 1 to 5 as well as Figures 10 to 13 The network entity described herein performs the function. 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 function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0226] At 1805, the method may include sending to the UE a first indication of a first cell associated with a first uplink carrier and a first downlink carrier, and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell. Operation of block 1805 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1805 may be provided by reference to [reference needed]. Figure 12 The described cell manager 1225 is used to execute this.

[0227] At 1810, the method may include information based on the first indication to identify an uplink configuration, TDD uplink / downlink configuration, candidate synchronization signal block index set, or any combination thereof for the second uplink carrier used for the second cell. Operation of block 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1810 may be derived from references... Figure 12 The carrier identifier manager 1250 described herein is used to perform this action.

[0228] At 1815, the method may include sending to the UE a second indication, via the first downlink carrier of the first cell or via a second downlink carrier associated with a third cell, of subsequent communication to be performed via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both. Operation of block 1815 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1815 may be provided by reference to [reference needed]. Figure 12 The described scheduler 1230 is used to execute this.

[0229] At 1820, the method may include performing the subsequent communication with the UE according to the second instruction. The operation of block 1820 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1820 may be provided by reference to... Figure 12 The described uplink communication manager 1235 is used to execute this.

[0230] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for performing wireless communication at a UE, the method comprising: receiving a first indication for a first cell associated with a first uplink carrier and a first downlink carrier and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell; receiving a second indication for subsequent communication to be performed via the first downlink carrier of the first cell or via the second downlink carrier associated with a third cell, or both; and performing the subsequent communication according to the second indication, wherein the subsequent communication includes at least one of access communication, uplink communication, or both.

[0231] Aspect 2: According to the method of aspect 1, receiving the second instruction includes: receiving permission to schedule uplink communication via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both, wherein the subsequent communication includes the uplink communication.

[0232] Aspect 3: According to the method of aspect 2, the permission includes cross-carrier scheduling permission, multi-cell scheduling permission, or both.

[0233] Aspect 4: The method according to any one of Aspects 2 to 3, the method further comprising: identifying a first feedback process associated with uplink communication via the first cell and a second feedback process associated with uplink communication via the second cell.

[0234] Aspect 5: The method according to any one of Aspects 2 to 4, the method further comprising: receiving a reference signal transmitted via a first downlink carrier of the first cell, via a second downlink carrier associated with a third cell, or both; and performing timing and power control operations using the reference signal.

[0235] Aspect 6: The method according to any one of Aspects 2 to 5, wherein performing the subsequent communication comprises: transmitting uplink communication via the second uplink carrier of the second cell, or receiving downlink communication via the first downlink carrier of the first cell, according to a half-duplex scheme.

[0236] Aspect 7: The method according to any one of Aspects 2 to 6, wherein performing the subsequent communication comprises: performing simultaneous transmission on the first uplink carrier of the first cell and transmission on the second uplink carrier of the second cell according to a simultaneous transmission antenna switching scheme, or performing non-simultaneous transmission on the first uplink carrier of the first cell and transmission on the second uplink carrier of the second cell according to an uplink transmission antenna switching scheme.

[0237] Aspect 8: The method according to any one of Aspects 1 to 7, wherein receiving the second instruction comprises: receiving a system information message, the system information message identifying a first access resource for accessing the first cell via the first uplink carrier and a second access resource for accessing the second cell via the second uplink carrier; and accessing the first cell or the second cell according to the first access resource or the second access resource.

[0238] Aspect 9: According to the method of aspect 8, the method further includes: based on the fact that the subsequent communication is scheduled in a TDD scheme, identifying the first access channel timing corresponding to the first access resource and the second access channel timing corresponding to the second access resource according to the access scheme.

[0239] Aspect 10: The method according to any one of Aspects 1 to 9, the method further comprising: identifying, at least in part, information on an uplink configuration, a TDD uplink / downlink configuration, a candidate synchronization signal block index set, or any combination thereof for a second uplink carrier for the second cell, based on the first indication.

[0240] Aspect 11: According to the method of aspect 10, the information is carried in the eSUL carrier sequence indication.

[0241] Aspect 12: The method according to any one of Aspects 10 to 11, wherein the information is carried in the serving cell configuration common system information block eSUL carrier indication.

[0242] Aspect 13: A method for wireless communication at a network entity, the method comprising: sending to a UE a first indication of a first cell associated with a first uplink carrier and a first downlink carrier and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell; sending to the UE a second indication of subsequent communication to be performed via the first downlink carrier of the first cell or via the second downlink carrier associated with a third cell for subsequent communication to be performed via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both; and performing the subsequent communication with the UE according to the second indication.

[0243] Aspect 14: According to the method of aspect 13, sending the second instruction includes: sending permission to schedule uplink communication with the UE via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both, wherein the subsequent communication includes the uplink communication.

[0244] Aspect 15: The method according to aspect 14, wherein the grant includes cross-carrier scheduling grant, multi-cell scheduling grant, or both.

[0245] Aspect 16: The method according to any one of Aspects 14 to 15, the method further comprising: identifying a first feedback process associated with uplink communication via the first cell and a second feedback process associated with uplink communication via the second cell.

[0246] Aspect 17: The method according to any one of Aspects 14 to 16, the method further comprising: transmitting a reference signal transmitted to the UE via the first downlink carrier; and performing timing and power control operations with the UE using the reference signal.

[0247] Aspect 18: The method according to any one of Aspects 14 to 17, wherein performing the subsequent communication comprises: receiving uplink communication from the UE via the second uplink carrier of the second cell according to a half-duplex scheme, or sending downlink communication to the UE via the first downlink carrier of the first cell.

[0248] Aspect 19: The method according to any one of Aspects 13 to 18, wherein sending the second instruction comprises: sending a system information message to the UE, the system information message identifying a first access resource for accessing the first cell via the first uplink carrier and a second access resource for accessing the second cell via the second uplink carrier, wherein the UE accesses the first cell or the second cell according to the first access resource or the second access resource.

[0249] Aspect 20: According to the method of aspect 19, the method further includes: based on the fact that the subsequent communication is scheduled in a TDD scheme, identifying a first access channel timing corresponding to the first access resource and a second access channel timing corresponding to the second access resource according to the access scheme.

[0250] Aspect 21: The method according to any one of Aspects 13 to 20, the method further comprising: identifying, at least in part, information on uplink configuration, TDD uplink / downlink configuration, candidate synchronization signal block index set, or any combination thereof for the second uplink carrier for the second cell based on the first indication.

[0251] Aspect 22: According to the method of aspect 21, the information is carried in the eSUL carrier sequence indication.

[0252] Aspect 23: The method according to any one of Aspects 21 to 22, wherein the information is carried in the serving cell configuration common system information block eSUL carrier indication.

[0253] Aspect 24: 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 to cause the UE to perform a method according to any one of aspects 1 to 12.

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

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

[0256] Aspect 27: 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 13 to 23.

[0257] Aspect 28: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 13 to 23.

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

[0259] 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.

[0260] 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.

[0261] The information and signals described herein can be represented using any of a variety of different techniques and skills. 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.

[0262] 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 cooperating 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.

[0263] 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.

[0264] 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 devices, magnetic disk storage devices 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.

[0265] 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".

[0266] 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” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as 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” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0267] 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, creating, and other similar actions.

[0268] 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.

[0269] 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.

[0270] 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: At least one memory; At least one transceiver; and At least one processor, coupled to the memory and the transceiver, and configured to: The transceiver receives a first indication of a first cell associated with a first uplink carrier and a first downlink carrier, and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell. Receive, via the transceiver and via the first downlink carrier of the first cell or via the second downlink carrier associated with the third cell, a second indication for subsequent communication to be performed via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both; and The subsequent communication is performed in accordance with the second instruction, wherein the subsequent communication includes access communication, uplink communication, or at least one of both.

2. The UE according to claim 1, wherein, In order to receive the second instruction, the at least one processor is further configured to: The system receives permission to schedule uplink communication via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both, wherein the subsequent communication includes the uplink communication.

3. The UE according to claim 2, wherein the grant includes cross-carrier scheduling grant, multi-cell scheduling grant, or both.

4. The UE according to claim 2, wherein the at least one processor is further configured to: Identify a first feedback procedure associated with uplink communication via the first cell and a second feedback procedure associated with uplink communication via the second cell.

5. The UE according to claim 2, wherein the at least one processor is further configured to: Receive a reference signal transmitted via the first downlink carrier of the first cell, via the second downlink carrier associated with the third cell, or both; and The reference signal is used to perform timing and power control operations.

6. The UE according to claim 2, wherein, In order to perform the subsequent communication, the at least one processor is further configured to: According to the half-duplex scheme, uplink communication is transmitted via the second uplink carrier of the second cell, or downlink communication is received via the first downlink carrier of the first cell.

7. The UE according to claim 2, wherein, In order to perform the subsequent communication, the at least one processor is further configured to: According to the simultaneous transmission antenna switching scheme, simultaneous transmission on the first uplink carrier of the first cell and transmission on the second uplink carrier of the second cell are performed; or according to the uplink transmission antenna switching scheme, non-simultaneous transmission on the first uplink carrier of the first cell and transmission on the second uplink carrier of the second cell are performed.

8. The UE according to claim 1, wherein, In order to receive the second instruction, the at least one processor is further configured to: Receive system information messages, wherein the system information messages identify a first access resource for accessing the first cell via the first uplink carrier and a second access resource for accessing the second cell via the second uplink carrier; as well as Access to the first cell or the second cell is based on the first access resource or the second access resource.

9. The UE of claim 8, wherein the at least one processor is further configured to: Since the subsequent communication is scheduled in a time-domain duplex scheme, the first access channel timing corresponding to the first access resource and the second access channel timing corresponding to the second access resource are identified according to the access scheme.

10. The UE of claim 1, wherein the at least one processor is further configured to: Information identifying, at least in part, the uplink configuration, time-domain duplex uplink / downlink configuration, candidate synchronization signal block index set, or any combination thereof for the second uplink carrier used in the second cell, based on the first indication.

11. The UE of claim 10, wherein the information is carried in an enhanced secondary uplink carrier sequence indication.

12. The UE of claim 10, wherein the information is carried in the Serving Cell Configuration Common System Information Block Enhanced Secondary Uplink Carrier Indication.

13. A network entity, the network entity comprising: At least one memory; and At least one processor, the at least one processor being coupled to the memory and configured to: Send a first indication to the user equipment (UE) for a first cell associated with a first uplink carrier and a first downlink carrier and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell; Sending a second indication to the UE, via the first downlink carrier of the first cell or via the second downlink carrier associated with the third cell, a second indication for subsequent communication to be performed via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both; and The subsequent communication with the UE is performed according to the second instruction.

14. The network entity according to claim 13, wherein, In order to send the second instruction, the at least one processor is further configured to: The system grants permission for uplink communication with the UE via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both, wherein the subsequent communication includes the uplink communication.

15. The network entity of claim 14, wherein the grant includes cross-carrier scheduling grant, multi-cell scheduling grant, or both.

16. The network entity of claim 14, wherein the at least one processor is further configured to: Identify a first feedback procedure associated with uplink communication via the first cell and a second feedback procedure associated with uplink communication via the second cell.

17. The network entity of claim 14, wherein the at least one processor is further configured to: Transmit a reference signal to the UE via the first downlink carrier; and The reference signal is used to perform timing and power control operations with the UE.

18. The network entity according to claim 14, wherein, In order to perform the subsequent communication, the at least one processor is further configured to: According to the half-duplex scheme, uplink communication is received from the UE via the second uplink carrier of the second cell, or downlink communication is sent to the UE via the first downlink carrier of the first cell.

19. The network entity according to claim 13, wherein, In order to send the second instruction, the at least one processor is further configured to: A system information message is sent to the UE, wherein the system information message identifies a first access resource for accessing the first cell via the first uplink carrier and a second access resource for accessing the second cell via the second uplink carrier, wherein the UE accesses the first cell or the second cell based on the first access resource or the second access resource.

20. The network entity of claim 19, wherein the at least one processor is further configured to: Since the subsequent communication is scheduled in a time-domain duplex scheme, the first access channel timing corresponding to the first access resource and the second access channel timing corresponding to the second access resource are identified according to the access scheme.

21. The network entity of claim 13, wherein the at least one processor is further configured to: Information identifying, at least in part, the uplink configuration, time-domain duplex uplink / downlink configuration, candidate synchronization signal block index set, or any combination thereof for the second uplink carrier used in the second cell, based on the first indication.

22. The network entity of claim 21, wherein the information is carried in an enhanced secondary uplink carrier sequence indication.

23. The network entity of claim 21, wherein the information is carried in the serving cell configuration common system information block enhanced secondary uplink carrier indication.

24. A method for conducting wireless communication at a user equipment (UE), the method comprising: Receive a first indication of a first cell associated with a first uplink carrier and a first downlink carrier and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell; Receive a second indication, via the first downlink carrier of the first cell or via a second downlink carrier associated with the third cell, of subsequent communication to be performed via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both; and The subsequent communication is performed in accordance with the second instruction, wherein the subsequent communication includes access communication, uplink communication, or at least one of both.

25. The method of claim 24, wherein receiving the second instruction comprises: The system receives permission to schedule uplink communication via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both, wherein the subsequent communication includes the uplink communication.

26. The method of claim 25, wherein the grant includes cross-carrier scheduling grant, multi-cell scheduling grant, or both.

27. The method of claim 25, further comprising: Identify a first feedback procedure associated with uplink communication via the first cell and a second feedback procedure associated with uplink communication via the second cell.

28. The method of claim 25, further comprising: Receive a reference signal transmitted via the first downlink carrier of the first cell, via the second downlink carrier associated with the third cell, or both. as well as The reference signal is used to perform timing and power control operations.

29. The method of claim 25, wherein performing the subsequent communication comprises: According to the half-duplex scheme, uplink communication is transmitted via the second uplink carrier of the second cell, or downlink communication is received via the first downlink carrier of the first cell.

30. A method for conducting wireless communication at a network entity, the method comprising: Send a first indication to the user equipment (UE) for a first cell associated with a first uplink carrier and a first downlink carrier and a second cell associated with a second uplink carrier, wherein the second cell includes an uplink-only cell; Sending a second indication to the UE, via the first downlink carrier of the first cell or via the second downlink carrier associated with the third cell, a second indication for subsequent communication to be performed via the first uplink carrier of the first cell, the second uplink carrier of the second cell, or both; and The subsequent communication with the UE is performed according to the second instruction.

Images