Cross-carrier RACH transmission for inter-band carrier aggregation with SSB-free carriers
By adopting inter-band carrier aggregation technology without synchronous signal block carriers in wireless communication systems, using non-anchor carriers to transmit RACH messages, the problem of high power consumption in carrier aggregation is solved, and the system efficiency and user experience are improved.
Patent Information
- Application Number
- CN202280094364.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-04-13
- Publication Date
- 2024-11-15
AI Technical Summary
The existing carrier aggregation technology has the problem of high power consumption in wireless communication systems, especially when deploying carrier aggregation, resulting in poor system efficiency and user experience.
Using inter-band carrier aggregation technology without synchronous signal block (SSB) carriers, by configuring communication devices to send random access channel (RACH) messages on multiple carriers, reducing transmission on anchor carriers, and using non-anchor carriers Transmission of RACH messages reduces power consumption and improves resource utilization.
It effectively reduces the power consumption of wireless communication systems, improves resource utilization, improves user experience and system efficiency, and supports higher data rates.
Smart Images

Figure CN118975376A_ABST
Abstract
Description
Technical Field
[0001] The following relates to wireless communications including cross-carrier random access channel (RACH) transmissions for inter-band carrier aggregation with no synchronization signal block (SSB) carriers. Background Art
[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM).
[0003] A wireless multiple access communication system may include one or more network entities, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE). Some wireless communication systems may support carrier aggregation, where multiple carriers may be combined into a single data channel to increase the data capacity of the communication network. In some cases, existing carrier aggregation techniques may be deficient. Summary of the invention
[0004] The described technology relates to improved methods, systems, devices, and apparatuses for supporting cross-carrier random access channel (RACH) transmission for inter-band carrier aggregation with carriers without synchronization signal blocks (SSBs). For example, the described technology provides for configuring a communication device (e.g., a user equipment (UE)) with one or more rules for performing carrier aggregation with carriers without SSBs. In some examples, the UE may receive a first message including first information indicating an inter-band carrier aggregation configuration. The inter-band carrier aggregation configuration may identify a carrier set for carrier aggregation communication between the UE and a network entity. The UE may receive a second message including second information indicating a random access procedure configuration. The random access procedure configuration may include rules regarding whether a RACH message may be sent on multiple carriers, a mapping of multiple RACH opportunities to at least one SSB index, and a repetition number indicating the number of RACH message repetitions sent by the UE. The UE may send the number of RACH message repetitions based on the mapping. The number of RACH messages may be sent on one carrier or on the multiple carriers in the carrier set based on the rule. Therefore, the UE can reduce power consumption and increase resource utilization within a wireless communication system.
[0005] A method for wireless communication at a UE is described. The method may include: receiving a first message including first information indicating an inter-band carrier aggregation configuration, the inter-band carrier aggregation configuration identifying a carrier set for carrier aggregation communication between the UE and a network entity; receiving a second message including second information indicating a random access procedure configuration, the random access procedure configuration including a rule regarding whether to send a RACH message on multiple carriers, a mapping of a set of multiple RACH opportunities to at least one SSB index, and a repetition number indicating a number of RACH message repetitions for sending by the UE; and sending the number of RACH message repetitions based on the mapping, wherein the number of RACH messages is sent on one carrier or on the multiple carriers in the carrier set based on the rule.
[0006] An apparatus for wireless communication is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive a first message, the first message including first information indicating an inter-band carrier aggregation configuration, the inter-band carrier aggregation configuration identifying a carrier set for carrier aggregation communication between the UE and a network entity; receive a second message, the second message including second information indicating a random access procedure configuration, the random access procedure configuration including a rule regarding whether to send a RACH message on multiple carriers, a mapping of a set of multiple RACH opportunities to at least one SSB index, and a repetition number indicating a number of RACH message repetitions to be sent by the UE; and send the number of RACH message repetitions based on the mapping, wherein the number of RACH messages is sent on one carrier or on the multiple carriers in the carrier set based on the rule.
[0007] Another apparatus for wireless communication is described. The apparatus may include: a component for receiving a first message, the first message including first information indicating an inter-band carrier aggregation configuration, the inter-band carrier aggregation configuration identifying a carrier set for carrier aggregation communication between the UE and a network entity; a component for receiving a second message, the second message including second information indicating a random access procedure configuration, the random access procedure configuration including a rule regarding whether to send a RACH message on multiple carriers, a mapping of a set of multiple RACH opportunities to at least one SSB index, and a repetition number indicating a number of RACH message repetitions for sending by the UE; and a component for sending the number of RACH message repetitions based on the mapping, wherein the number of RACH messages is sent on one carrier or on the multiple carriers in the carrier set based on the rule.
[0008] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions that can be executed by a processor to: receive a first message, the first message including first information indicating an inter-band carrier aggregation configuration, the inter-band carrier aggregation configuration identifying a carrier set for carrier aggregation communication between the UE and a network entity; receive a second message, the second message including second information indicating a random access procedure configuration, the random access procedure configuration including a rule on whether to send a RACH message on multiple carriers, a mapping of a set of multiple RACH opportunities to at least one SSB index, and a repetition number indicating a number of RACH message repetitions for sending by the UE; and send the number of RACH message repetitions based on the mapping, wherein the number of RACH messages is sent on one carrier or on the multiple carriers in the carrier set based on the rule.
[0009] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the number of RACH message repetitions may include operations, features, components, or instructions for sending the number of RACH message repetitions on a carrier according to the rule.
[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one carrier comprises a non-anchor carrier.
[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the number of RACH message repetitions may include operations, features, components, or instructions for sending a first portion of the number of RACH message repetitions on the one carrier during a first association period, and sending a second portion of the number of RACH message repetitions on the one carrier during a second association period, the second association period occurring after the first association period.
[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the number of RACH message repetitions may include operations, features, components, or instructions for: sending the number of RACH message repetitions on at least two of the multiple carriers according to the rule.
[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the at least two carriers include at least one non-anchor carrier.
[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a first portion of the number of RACH message repetitions on a first carrier of the at least two carriers and sending a second portion of the number of RACH message repetitions on a second carrier of the at least two carriers, wherein the second portion of the number of RACH message repetitions may be sent simultaneously with or after the first portion of the number of RACH message repetitions.
[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the first portion of the number of RACH message repetitions on the first carrier and sending the second portion of the number of RACH message repetitions on the second carrier may include operations, features, components, or instructions for sending the first portion of the number of RACH message repetitions on the first carrier using a first spatial filter and sending the second portion of the number of RACH message repetitions on the second carrier using a second spatial filter, the second spatial filter being the same spatial filter as the first spatial filter or a different spatial filter from the first spatial filter.
[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the first portion of the number of RACH message repetitions on the first carrier and sending the second portion of the number of RACH message repetitions on the second carrier may include operations, features, components, or instructions for: sending the second portion of the number of RACH message repetitions after the first portion of the number of RACH message repetitions based on an ordering of the number of RACH message repetitions, wherein the ordering of the number of RACH message repetitions corresponds to the mapping of the set of the plurality of RACH opportunities to the at least one SSB index.
[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the number of RACH message repetitions may include operations, features, components, or instructions for: sending the number of RACH message repetitions on at least one carrier of the multiple carriers according to the rule and a sequence ordering of the number of RACH message repetitions, wherein the sequence ordering of the number of RACH message repetitions corresponds to the mapping of the set of the multiple RACH opportunities to the at least one SSB index.
[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the number of RACH message repetitions may include operations, features, components, or instructions for sending a first RACH message repetition of the number of RACH message repetitions during a first RACH opportunity and on a first carrier in the multiple carriers according to the rule, wherein the first RACH opportunity may be associated with a lowest RACH identifier in a set of RACH identifiers for a set of the multiple RACH opportunities, and wherein the first carrier may be associated with a lowest frequency radio band or a highest frequency radio band in a set of radio bands for sending the number of RACH message repetitions.
[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the number of RACH message repetitions may include operations, features, components, or instructions for: receiving a third message including third information indicating a radio frequency band for sending RACH message repetitions of the number of RACH message repetitions and sending a first RACH message repetition of the number of RACH message repetitions during a first RACH opportunity and on a first carrier among the multiple carriers according to the rule, wherein the first RACH opportunity may be associated with a lowest RACH identifier in a set of RACH identifiers for the set of the multiple RACH opportunities, and wherein the first carrier may be associated with the radio frequency band indicated by the third message. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] Figure 1 and Figure 2A Each illustrates an example of a wireless communication system supporting cross-carrier random access channel (RACH) transmission for inter-band carrier aggregation with no synchronization signal block (SSB) carrier according to one or more aspects of the present disclosure.
[0021] Figure 2B An example of a transmission scheme supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers according to one or more aspects of the present disclosure is illustrated.
[0022] Figures 3 to 7 Each illustrates an example of a timing diagram supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers according to one or more aspects of the present disclosure.
[0023] Figure 8 An example of a process flow supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers in accordance with one or more aspects of the present disclosure is illustrated.
[0024] Fig. 9 and Fig.10 A block diagram of an apparatus supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers in accordance with one or more aspects of the present disclosure is shown.
[0025] Fig.11 A block diagram of a communications manager supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers is shown in accordance with one or more aspects of the present disclosure.
[0026] Fig.12 A diagram of a system including a device supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers in accordance with one or more aspects of the present disclosure is shown.
[0027] Figures 13 to 15 A flow chart illustrating a method of supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION
[0028] A wireless communication system may include a communication device, such as a user equipment (UE) or one or more network entities. A network entity may be an example of a wired or wireless network node that may support one or more radio access technologies. Examples of radio access technologies may include fourth generation (4G) systems such as LTE systems and fifth generation (5G) systems (which may be referred to as 5G new radio (NR) systems), as well as other wireless communication systems (e.g., subsequent generations of wireless communication systems) or one or more other network entities. A communication device may support wireless communication on one or more radio frequency bands and one or more carriers. In some examples, a network (e.g., one or more network entities) may schedule a communication device with a single carrier or with multiple carriers to support wireless communication in the form of, for example, carrier aggregation or dual connectivity.
[0029] In some examples, in order to increase the data capacity of the wireless communication system, the network may configure the communication device to support carrier aggregation on a single radio band or multiple radio bands (e.g., inter-band carrier aggregation). For example, the network may configure the communication device to aggregate two or more carriers across the same radio band or between multiple (e.g., separate) radio bands. In some examples of inter-band carrier aggregation, one of the multiple carriers (e.g., a component carrier) may be a supplementary uplink (SUL) carrier. Additionally or alternatively, the component carrier may be, for example, a normal uplink carrier associated with a serving cell (e.g., a primary serving cell) of the SUL carrier. Additionally or alternatively, one or more component carriers may be used for carrier aggregation (e.g., may be conventional carrier aggregation carriers).
[0030] In some examples, while some carrier aggregation deployments may improve user experience and system efficiency, carrier aggregation may increase power consumption within a wireless communication system. In some examples, in order to reduce power consumption, the network may implement wireless communication on a carrier in which a synchronization signal block (SSB) is not sent. For example, in order to reduce power consumption within a wireless communication system and increase resource utilization, the network may configure the communication device to perform inter-band carrier aggregation of one or more carriers (e.g., SUL carriers or conventional carrier aggregation carriers) in which SSBs are not sent. Such carriers may be referred to as SSB-free carriers or non-anchor carriers. The communication device may use SSBs (e.g., synchronization signal / physical broadcast channel (SS / PBCH) blocks) to obtain information (e.g., cell information, random access information) during a cell search procedure (or cell selection procedure). For example, the communication device may use SSBs to obtain parameters for a random access procedure, which the communication device may perform to obtain access to a wireless channel (e.g., for communication with the network). In some examples, the SSB may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a PBCH (e.g., with one or more associated demodulation reference signals (DMRS)). Additionally or alternatively, the SSB may identify a control resource set (CORESET) for a physical downlink control channel (PDCCH) scheduling a physical downlink shared channel (PDSCH) transmission carrying a system information block (SIB).
[0031] In some examples of inter-band carrier aggregation with a non-anchor carrier, the communication device can reduce power consumption by reducing the number of transmissions communicated on the carrier of the primary serving cell. That is, the communication device can reduce the number of transmissions communicated on the carrier (e.g., the anchor carrier) in which the SSB is transmitted. For example, the network can reduce anchor carrier transmissions by sending communications such as random access channel (RACH) messages on the non-anchor carrier. That is, the communication device can offload RACH message (e.g., including a physical random access channel (PRACH) preamble for obtaining access to a wireless channel) transmission (e.g., RACH transmission) from the anchor carrier to other non-anchor carriers. In some examples, by offloading RACH transmissions to non-anchor carriers, the communication device can reduce the possibility of collisions between RACH messages sent by the communication device and other RACH messages sent by other communication devices. Therefore, the efficiency of the wireless communication system can be increased. In some examples, the network can configure the communication device to send multiple RACH messages. However, in such examples, the communication device may not be able to determine whether to use multiple non-anchor carriers for multiple RACHs.
[0032] Various aspects of the present disclosure relate to cross-carrier RACH transmission for inter-band carrier aggregation with SSB-free (e.g., non-anchor) carriers, and more particularly, to configuring a communication device with one or more rules for performing carrier aggregation with non-anchor carriers. For example, the present disclosure may provide techniques for configuring a communication device with one or more rules for determining whether to send multiple RACH messages on a single non-anchor carrier or on multiple carriers that may include at least one non-anchor carrier.
[0033] For example, a network (e.g., one or more network entities) may send an indication of an inter-band carrier aggregation configuration to a communication device. The inter-band carrier aggregation configuration may identify a set of multiple carriers (e.g., an anchor carrier and one or more non-anchor carriers) for carrier aggregation communications between the communication device and the network. Additionally or alternatively, the network may send an indication of a random access procedure configuration to the communication device. The random access procedure configuration may include rules regarding whether a RACH message may be sent on multiple carriers. In some examples, the random access procedure configuration may include a mapping of RACH opportunities to one or more SSB indices and a repetition number indicating the number of RACH message repetitions to be sent by the communication device. In some examples, the rule may instruct the communication device to suppress sending multiple transmissions on multiple carriers. For example, the rule may instruct the communication device to send multiple RACH messages on a single non-anchor carrier.
[0034] Additionally or alternatively, the rule may instruct the communication device to send multiple RACH messages on multiple carriers (e.g., including at least one non-anchor carrier). That is, the network may configure the communication device to send multiple RACH messages on a non-anchor carrier and an anchor carrier or one or more other non-anchor carriers. In some examples, the network may configure the communication device to use a common spatial filter across multiple carriers, or to use different spatial filters depending on the carrier. Additionally or alternatively, the network may configure the communication device to send multiple RACH messages across multiple carriers according to an order (e.g., corresponding to a mapping). In some examples, the order may be based on an identifier of a RACH opportunity on which the RACH message may be sent. For example, the communication device may send multiple RACH messages sequentially across multiple carriers (e.g., according to a RACH opportunity identifier) or in a portion that may be divided (e.g., equally) between each of the multiple carriers. Additionally or alternatively, the communication device may send multiple RACH messages according to an order based on radio frequency bands associated with the multiple carriers.
[0035] Certain aspects of the subject matter described herein may be implemented to achieve one or more of the following potential advantages. For example, the techniques employed by the described communication devices may provide benefits and enhancements to wireless communication devices operating within a network, including achieving reduced power consumption within a wireless communication system. In some examples, operations performed by the described communication devices may provide improvements to techniques for carrier aggregation and increase resource utilization within a wireless communication system. Operations performed by the described communication devices to improve techniques for carrier aggregation may include sending RACH messages on one or more non-anchor carriers. In some other specific implementations, operations performed by the described wireless communication devices may also support improvements to user experience and higher data rates, as well as other benefits.
[0036] Various aspects of the disclosure are first described in the context of wireless communication systems. Various aspects of the disclosure are also described in the context of transmission schemes, timing diagrams, and process flows. Various aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to cross-carrier RACH transmission for inter-band carrier aggregation with SSB-free (e.g., non-anchor) carriers.
[0037] Figure 1 An example of a wireless communication system 100 supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).
[0038] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100 and may include devices in different forms or with different capabilities. In different examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, etc. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).
[0039] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile or both stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be able to communicate with various types of devices (such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.
[0040] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from the second node.
[0041] In some examples, the network entities 105 may communicate with the core network 130, or communicate with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other on the backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication link 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication link 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, the midhaul communication link 162, or the fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), and other examples or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .
[0042] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a home Node B, a home evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).
[0043] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).
[0044] The functional split between CU 160, DU 165, and RU 170 is flexible and may 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 functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating over those communication links.
[0045] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.
[0046] In the case where the techniques described herein are applied to the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support cross-carrier RACH transmissions for inter-band carrier aggregation with no SSB carriers as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).
[0047] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as electrical appliances or vehicles, meters, etc.
[0048] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 as shown in .
[0049] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) on one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a defined physical layer structure to support the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any part (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send", "receive", or "communicate" when referring to the network entity 105 may refer to any part of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).
[0050] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be located according to a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be made by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.
[0051] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communications or uplink communications (e.g., in an FDD mode), or may be configured to carry both downlink communications and uplink communications (e.g., in a TDD mode).
[0052] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communication over a particular carrier bandwidth, or may be configured to support communication over one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, a BWP) or all of a carrier bandwidth.
[0053] The signal waveform sent on the carrier may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a subcarrier resource, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.
[0054] One or more parameter sets for a carrier may be supported, where the parameter set may include subcarrier spacing (Δf) and cyclic prefix. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.
[0055] The time interval of the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).
[0056] 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, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, the time slot may be further divided into multiple micro-time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.
[0057] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).
[0058] Physical channels may be multiplexed on a carrier according to various techniques. For example, physical control channels and physical data channels may be multiplexed on a downlink carrier using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., CORESET) for a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESET) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. A search space set may include: a common search space set configured for transmitting control information to multiple UEs 115, and a UE-specific search space set for transmitting control information to a specific UE 115.
[0059] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., via a carrier), and may be associated with an identifier used to distinguish adjacent cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other cell identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) within which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.
[0060] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. Small cells may be associated with lower power network entities 105 (e.g., lower power base stations 140) than macro cells, and small cells may operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with small cells (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications on one or more cells.
[0061] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.
[0062] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for 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 provide coverage for various coverage areas 110 using the same or different radio access technologies.
[0063] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.
[0064] In some examples, a UE 115 may be able to communicate directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each other UE 115 in the group. In some examples, the network entity 105 may facilitate scheduling resources for D2D communication. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .
[0065] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity for managing access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity for routing packets or interconnecting to an external network (e.g., a serving gateway (S-GW)), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to an IP service 150 for one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.
[0066] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is approximately one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide service to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.
[0067] The wireless communication system 100 can utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can use licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 can use carrier sensing for conflict detection and avoidance. In some examples, operations in unlicensed bands can be based on carrier aggregation configuration (e.g., LAA) in combination with component carriers operating in licensed bands. Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.
[0068] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas, which can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may have an antenna array having antenna ports of a set of rows and columns that the network entity 105 can use to support beamforming for communication with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.
[0069] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of the antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).
[0070] The wireless communication system 100 may support configuring a communication device (e.g., UE 115) with one or more rules for performing carrier aggregation with no SSB (e.g., non-anchor) carriers. For example, the UE 115 may receive a first message including first information indicating an inter-band carrier aggregation configuration. The inter-band carrier aggregation configuration may identify a carrier set for carrier aggregation communication between the UE 115 and the network entity 105. The UE 115 may receive a second message including second information indicating a random access procedure configuration. The random access procedure configuration may include rules regarding whether a RACH message may be sent on multiple carriers, a mapping of multiple RACH opportunities to at least one SSB index, and a repetition number indicating the number of RACH message repetitions sent by the UE 115. The UE 115 may send the number of RACH message repetitions based on the mapping. The number of RACH messages may be sent on one carrier or on multiple carriers in the carrier set based on the rules. Therefore, the UE 115 may reduce power consumption and increase resource utilization within the wireless communication system.
[0071] Figure 2A An example of a wireless communication system 200 supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 200 may implement or be implemented by one or more aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a UE 215, which may be a reference Figure 1 The wireless communication system 200 may further include a network entity 205, which may be a network entity such as the one described in reference Figure 1 The network entity 205 and the UE 215 may communicate within one or more coverage areas 210 (e.g., coverage area 210-a or coverage area 210-b), each of which may be as described in reference to Figure 1 An example of the coverage area 110 is shown. Additionally or alternatively, the network entity 205 and the UE 215 can communicate within the SUL coverage area 211. The wireless communication system 200 can include features for improving communication between the network entity 205 and the UE 215, as well as other benefits.
[0072] In some examples, in order to increase the data capacity of the network, the wireless communication system 200 may support carrier aggregation, in which multiple carriers (e.g., component carriers) may be combined into a single data channel. For example, the UE 215 may be configured with multiple uplink carriers 220 (e.g., carrier 220-a, carrier 220-b), each of which may be associated with a serving cell (e.g., serving a serving cell). In the example of FIG. 2, carrier 220-a may be a primary carrier that may serve a primary cell (e.g., providing coverage area 210-a), and carrier 220-b may be a secondary carrier that may serve a secondary cell (e.g., providing coverage area 210-b). In some examples, carrier 220-a may be associated with a downlink carrier 230 (e.g., a primary downlink carrier). Additionally or alternatively, in order to increase uplink performance and throughput, the network may configure the UE 215 with a SUL carrier 221 that may provide a SUL coverage area 211. In some examples, SUL carrier 221 may operate in a relatively lower frequency band (e.g., relative to carrier 220-a and carrier 220-b), thereby providing increased uplink coverage for high frequency deployments. In some examples, while carrier aggregation deployments may improve user experience and system efficiency by increasing the data capacity of the network, carrier aggregation may result in increased power consumption within the wireless communication system.
[0073] For example, operations performed by a network (e.g., a cellular network) such as MIMO operations performed by a RAN (e.g., network entity 205) may be energy intensive and costly (e.g., may result in relatively high costs to the network). Thus, techniques to reduce power consumption (e.g., provide network energy savings) may be desirable for some network deployments (e.g., adoption and expansion of cellular networks). For example, the wireless communication system 200 may support techniques for employing a network (e.g., RAN, base station) energy consumption model in which a framework for power consumption modeling and evaluation methods (e.g., including relative energy consumption for downlink and uplink) may consider factors such as power amplifier efficiency, the number of transmitting devices (e.g., RUs), base station load, sleep states and associated transition times, and one or more reference parameters (e.g., configurations).
[0074] Additionally or alternatively, the wireless communication system 200 may support techniques based on (e.g., using) an evaluation method and multiple (e.g., different) key performance indicators (KPIs). In some examples of techniques using an evaluation method, system-level network energy consumption and energy saving gains may be evaluated. That is, the impact of energy saving on network and user performance (e.g., spectrum efficiency, capacity, user perceived throughput, latency, handover performance, call drop rate, initial access performance, and KPIs related to service level agreement guarantees), energy efficiency, UE power consumption, and complexity may be estimated (or balanced). Additionally or alternatively, such techniques may provide evaluations of multiple (e.g., different KPIs).
[0075] Additionally or alternatively, a communication device operating within the wireless communication system 200 may support techniques for improving network energy conservation for both (e.g., by) transmission and reception (e.g., with respect to the transmission and reception). For example, a communication device (e.g., network entity 205) may support techniques for achieving increased operational efficiency for dynamic or semi-static signaling (e.g., transmission). Additionally or alternatively, such techniques may enable relatively finer-grained adaptation of transmission or reception (e.g., in the time domain, frequency domain, spatial domain, and power domain) with support (e.g., feedback information and auxiliary information) from another communication device (e.g., UE 215). In some examples, the exchange and coordination of information (e.g., feedback information and auxiliary information) may occur over one or more network interfaces (e.g., communication links).
[0076] In some examples, energy-saving techniques may consider idle (e.g., relatively empty) and relatively low (or relatively average) load scenarios. For example, energy-saving techniques may consider scenarios in which different loads among carriers (e.g., and adjacent cells) may be enabled. Such scenarios may include single-carrier and multi-carrier deployments, such as urban microcell (or small cell) deployments (e.g., in frequency range 1 (FR1) including TDD massive MIMO), beam-based scenarios (e.g., in frequency range 2 (FR2)), urban or rural macrocell deployments (e.g., in FR1 with or without dynamic spectrum sharing (DSS)), Evolved Universal Terrestrial Radio Access (E-UTRA) dual connectivity scenarios, or NR dual connectivity scenarios. For example, such energy-saving techniques may consider deployment on a macrocell with a primary cell capable of FDD operation, TDD operation, or massive MIMO operation (e.g., on relatively high FR1 or FR2 frequencies).
[0077] In some examples, UE 215 (or other UEs 215 (not shown)) may be able to access a network that implements such energy-saving techniques (e.g., energy-saving techniques that may or may not be associated with a greenfield deployment). In some examples, such techniques may provide energy saving for one or more network entities (e.g., network entity 205, IAB node (not shown)). Additionally or alternatively, such energy-saving techniques may provide improved coordination between multiple network entities (e.g., between multiple RANs). Some energy-saving techniques may employ carriers in which SSBs are not transmitted (e.g., SSB-free carriers). For example, the network may configure UE 215 to perform inter-band carrier aggregation with SSB-free carriers, which may be referred to as non-anchor carriers. In some examples, UE 215 may not be able to use such non-anchor carriers in greenfield deployment scenarios.
[0078] In some examples of inter-band carrier aggregation with a non-anchor carrier, the UE 215 may offload RACH message transmissions (e.g., RACH transmissions, PRACH transmissions) from a carrier of a primary cell including an SSB to one or more non-anchor carriers. In some examples, the carrier including the SSB (e.g., the carrier of the primary cell) may be referred to as an anchor carrier. As an illustrative example, the UE 215 may offload RACH transmissions from carrier 220-a (e.g., an anchor carrier) to carrier 220-b or SUL carrier 221 (e.g., a non-anchor carrier). In some examples, by offloading RACH transmissions from the anchor carrier to one or more non-anchor carriers, the UE 215 may reduce the likelihood of collisions between RACH messages (e.g., including a PRACH preamble for obtaining access to a wireless channel) sent by the UE 215 and other RACH messages (not shown) sent by other UEs 215. In some examples, by reducing the likelihood of collisions between RACH messages sent by multiple UEs 215, the network may also reduce the number of RACH message retransmissions and thereby increase system efficiency within the wireless communication system 200. Additionally or alternatively, the network may extend RACH coverage throughout the wireless communication system 200 by offloading RACH transmissions from the anchor carrier to one or more non-anchor carriers.
[0079] In some examples, an SSB sent in one carrier may provide time and frequency synchronization for a carrier that may not include an SSB. That is, an SSB of an anchor carrier may provide time and frequency synchronization for a non-anchor carrier. For example, an SSB sent by carrier 220-a may provide time and frequency synchronization information for carrier 220-b and SUL carrier 221. In some examples, a non-anchor carrier may be associated with an FR1 segment band, where the bands are adjacent (e.g., at approximately 700 MHz, 800 MHz, 900 MHz, 1.8 GHz, 2.1 GHz, 1.9 GHz, 2 GHz, or 2.3 GHz). For example, band combinations for carrier aggregation with a non-anchor carrier (e.g., supported by a wireless network operator) may include: 700 MHz, 800 MHz, and 900 MHz; 1.8 GHz and 2.1 GHz; 1.9 GHz, 2 GHz, and 2.3 GHz; or 600 MHz, 1.9 GHz, and 3.5 GHz, as well as other band combinations.
[0080] In some examples, inter-band carrier aggregation with a non-anchor carrier may support one or more features for improved coordination between multiple network entities (e.g., transmit and receive points (TRPs)) operating within a wireless communication system 200 (not shown) and coordination between one or more network entities (e.g., network entity 205 and one or more other network entities 20 (not shown)) and UE 215. For example, the network may define a maximum receive timing difference (MRTD) that may provide relative frame timing alignment at UE 215. In some examples, the MRDT may take into account network relative time alignment error and radio frequency propagation delay. Additionally or alternatively, inter-band carrier aggregation with a non-anchor carrier may provide a quasi-co-location relationship between SSBs (e.g., transmitted via an anchor carrier) and signals transmitted via a non-anchor carrier. Additionally or alternatively, inter-band carrier aggregation with a non-anchor carrier may support an increased number of uplink transmissions (e.g., by UE 215 or one or more other UEs 215 (not shown)). In some examples, by supporting inter-band carrier aggregation with non-anchor carriers, the network can improve secondary cell activation latency by enabling secondary cell activation (or deactivation) according to traffic conditions. Thus, the network can achieve power savings and improve resource utilization, for example, by reducing downlink overhead.
[0081] In some examples, inter-band carrier aggregation with a non-anchor carrier can reduce power consumption within the network (e.g., can provide energy savings) while providing one or more enhancements to user experience and system efficiency. In some examples, the network can configure UE 215 to send multiple RACH messages (e.g., for multiple RACH transmissions). However, in such examples, UE 215 may not be able to determine whether to use multiple non-anchor carriers for multiple RACH transmissions. Therefore, techniques for configuring a communication device such as UE 215 with one or more rules for performing carrier aggregation with a non-anchor carrier may be desirable.
[0082] In some examples, techniques for cross-carrier RACH transmission for inter-band carrier aggregation with non-anchor carriers as described herein can provide one or more enhancements to carrier aggregation by enabling UE 215 to send multiple RACH messages on one or more non-anchor carriers. For example, UE 215 can receive a first message including first information indicating an inter-band carrier aggregation configuration 235 from network entity 205 (e.g., via downlink carrier 230). Inter-band carrier aggregation configuration 235 can identify a set of carriers (e.g., carrier 220-a, carrier 220-b, and SUL carrier 221) for carrier aggregation communications between UE 215 and network entity 205. In some examples, the set of carriers can serve virtual cell 225.
[0083] Additionally or alternatively, the UE 215 may receive a second message including second information indicating a random access procedure configuration 240. The random access procedure configuration 240 may include rules regarding whether a RACH message (e.g., one or more RACH messages 245) may be sent on multiple carriers (e.g., two or more carriers of the carrier 220-a, the carrier 220-b, and the SUL carrier 221). In some examples, the random access procedure configuration 240 may include a mapping of multiple RACH opportunities to at least one SSB index (e.g., of an SSB sent via an anchor carrier) and a repetition number indicating the number of RACH message repetitions sent by the UE 215. In some examples, the UE 215 may send the number of RACH message repetitions based on the mapping. Additionally or alternatively, the UE 215 may send the number of RACH messages on one carrier or on multiple carriers in a carrier set based on a rule. Therefore, the UE 215 may reduce power consumption and increase resource utilization within the wireless communication system.
[0084] In some examples, UE 215 may send the number of RACH messages on one carrier or on multiple carriers according to one or more (e.g., different) configurations (e.g., virtual cell configurations). Figure 2BAn example of a transmission scheme 201 supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers according to one or more aspects of the present disclosure is illustrated. The transmission scheme 201 may include a virtual cell 225-a, a virtual cell 225-b, and a virtual cell 225-c, each of which may be as described in reference Figure 2A In some examples, the transmission scheme 201 may implement or be implemented by one or more aspects of the wireless communication system 100 and the wireless communication system 200. For example, the transmission scheme 201 may be implemented by reference to Figure 2A The UE 215 is implemented.
[0085] In some examples, inter-band carrier aggregation with a non-SSB carrier (e.g., a non-anchor carrier) can provide improved communication between the network and the UE 215. For example, inter-band carrier aggregation with a non-anchor carrier can provide one or more enhancements to random access procedures performed on one or more radio frequency bands (e.g., FR1 and FR2) and random access procedures performed according to one or more PRACH formats (e.g., a relatively short PRACH format or an otherwise suitable PRACH format). In some examples, inter-band carrier aggregation with a non-anchor carrier can provide one or more benefits (e.g., can be useful) for reducing conflicts between RACH message transmissions (e.g., RACH transmissions, PRACH transmissions). For example, one or more RACH messages sent during a random access procedure (e.g., a two-step random access procedure or a four-step random access procedure) can be sent on a non-anchor carrier. In some examples, the RACH messages can be sent with the same beam or with different beams (e.g., for a four-step RACH procedure). Additionally or alternatively, the uplink RACH message may be sent in the same uplink carrier and the downlink RACH message may be sent in the same downlink carrier. In some examples, the uplink carrier and the downlink carrier may be different from the carrier carrying the SSB. That is, each of the uplink carrier and the downlink carrier may be a non-anchor carrier or an anchor carrier.
[0086] For example, the network may send a random access procedure configuration to the UE 215, which may include rules regarding whether a RACH message (e.g., one or more RACH messages 245) may be sent on multiple carriers. The random access procedure configuration may be as described in reference to Figure 2A245-b). In some examples, the rule may instruct UE 215 to send multiple RACH messages 245 on a single non-anchor carrier. In such an example, UE 215 may send multiple RACH messages 245 (e.g., RACH message 245-a and RACH message 245-b) on virtual cell 225-a (e.g., served by anchor carrier 250-a, non-anchor carrier 251-a, and non-anchor carrier 251-b) according to configuration 226-a. That is, UE 215 may send RACH message 245-a and RACH message 245-b via non-anchor carrier 251-a. In some examples, non-anchor carrier 251-a may be in the same band (or a different band) as anchor carrier 250-a (or non-anchor carrier 251-b). That is, for a virtual cell (e.g., virtual cell 225-a, virtual cell 225-b, or virtual cell 225-c) that includes a carrier with SSB (e.g., anchor carrier 250-a, anchor carrier 250-b, or anchor carrier 250-c) and a carrier without SSB (e.g., one or more non-anchor carriers in non-anchor carrier 251), each carrier may be in the same radio frequency band or in different radio frequency bands.
[0087] In other examples, the rule may instruct the UE 215 to send multiple RACH messages 245 on multiple carriers. In such examples, the UE 215 may send multiple RACH messages 245 (e.g., RACH message 245-c and RACH message 245-d) on a virtual cell 225-c (e.g., served by the anchor carrier 250-b, the non-anchor carrier 251-c, and the non-anchor carrier 251-d) according to the configuration 226-b. For example, the UE 215 may send the RACH message 245-c via the anchor carrier 250-b and send the RACH message 245-d via the non-anchor carrier 251-c. Additionally or alternatively, if the rules instruct UE 215 to send multiple RACH messages 245 on multiple carriers, UE 215 may send RACH message 245-e and RACH message 245-f on virtual cell 225-d (e.g., served by anchor carrier 250-c, non-anchor carrier 251-e, and non-anchor carrier 251-f) according to configuration 226-c. For example, UE 215 may send RACH message 245-e via non-anchor carrier 251-e and send RACH message 245-f via non-anchor carrier 251-f. In some examples, by configuring UE 215 with rules regarding whether RACH messages may be sent on multiple carriers, the network may reduce power consumption while providing one or more enhancements to user experience and system efficiency within the wireless communication system.
[0088] Figure 3An example of a timing diagram 300 for supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers according to one or more aspects of the present disclosure is illustrated. In some examples, the timing diagram 300 may implement or be implemented by one or more aspects of the wireless communication system 100 and the wireless communication system 200. For example, the timing diagram 300 may be implemented by the UE 115 or the network entity 105 (which may be as described in reference to Figure 1 and Figure 2A The corresponding device example described above is implemented. Figure 3 In the example of Figure 1 The CU, DU, RU, base station, IAB node or one or more other network node examples. Additionally or alternatively, in Figure 3 In the example of , the non-SSB carrier may be referred to as a non-anchor carrier. Timing diagram 300 may include features for improving communications between network entity 105 and UE 115, as well as other benefits.
[0089] For example, the network may configure UE 115 to send a RACH message (e.g., may be configured for RACH transmission) on a normal uplink carrier (e.g., an anchor carrier) or on a SUL carrier (or another non-anchor carrier). In such an example, the network may configure UE 115 for multiple RACH transmissions (e.g., PRACH transmissions). Thus, the network may determine to specify (e.g., indicate) to UE 115 whether UE 115 may use one or more carriers for multiple RACH transmissions. In some examples, by indicating whether UE 115 may use one or more carriers for multiple RACH transmissions, the network may provide one or more enhancements for inter-band carrier aggregation with non-anchor carriers. For example, the network may provide one or more enhancements for inter-band carrier aggregation communications, wherein UE 115 may perform RACH transmissions on a non-anchor carrier (SUL carrier or other non-anchor carrier) during initial access (e.g., during an initial access procedure).
[0090] In some examples, the network may indicate via rules whether UE 115 may use one or more carriers (e.g., component carriers) for multiple RACH transmissions. For example, the network may send an indication of a random access procedure configuration to UE 115, which may include rules regarding whether multiple RACH messages may be sent on multiple carriers. The random access procedure configuration may be as described in reference to Figure 2A In some examples, the rule may instruct UE 115 to send a RACH message on a single non-anchor carrier. In such an example, if UE 115 is configured with multiple RACH transmissions (e.g., configured to send multiple RACH messages), UE 115 may send multiple RACH messages on a single carrier 320.
[0091] In some examples, the random access procedure configuration may include a mapping of one or more RACH opportunities 305 (e.g., for sending one or more RACH messages 315) to one or more SSB indexes (e.g., a first SSB index 310 or a second SSB index 311). In some examples, the mapping may be associated with (correspond to, include) one or more parameters. For example, the mapping may provide (e.g., establish, indicate) a relationship between the number of RACH opportunities 305 and the number of SSBs based on a parameter (N). In some examples, the number of SSBs may be sent by an anchor carrier and used by the UE 115 to obtain information (e.g., cell information, random access information). Figure 3 In the example of , the value of the parameter (N) may be equal to approximately one-half (e.g., 1 / 2, 0.5). That is, the same SSB index may be mapped to two (e.g., different) RACH opportunity indices, which may each correspond to one or more RACH opportunities 305 configured at the UE 115 for sending a RACH message 315. For example, a RACH opportunity 305 corresponding to index RO#0 (e.g., RACH opportunity 305-a and RACH opportunity 305-e) and a RACH opportunity corresponding to index RO#1 (e.g., RACH opportunity 305-b and RACH opportunity 305-f) may be mapped to a first SSB index 310 (e.g., SSB#0). Additionally or alternatively, the RACH timings 305 corresponding to index RO#2 (e.g., RACH timing 305-c and RACH timing 305-g) and the RACH timings 305 corresponding to index RO#3 (e.g., RACH timing 305-d and RACH timing 305-h) may be mapped to a second SSB index 311 (e.g., SSB#1).
[0092] Additionally or alternatively, the mapping may indicate via a parameter (M) the resources used to send the RACH message 315. That is, the network may indicate the PRACH frequency resources to the UE 115 via the parameter (M). In some examples, the parameter (M) may correspond to (e.g., be equal to) a higher layer parameter, such as indicated via a msg1-FDM information element (IE). Figure 3 In an example of , the value of parameter (M) may be equal to about two. That is, the configured RACH opportunity 305 may occur on two resources in the frequency domain (e.g., two PRACH frequency resources). Additionally or alternatively, the mapping may provide multiple directions in which SSBs (e.g., corresponding to the mapped SSB indices) may be sent, for example, by the network entity 105 on the anchor carrier. In some examples, the mapping may provide a configuration in which the SSBs are transmitted via parameter (M). The number of directions in which SSB is sent. Figure 3 In the example, the parameter The value of may be equal to approximately two, which may correspond to two directions (e.g., beamforming directions). That is, the SSBs used by UE 115 (e.g., the SSB corresponding to the first SSB index 310 and the SSB corresponding to the second SSB index 311) may be sent by the network entity 105 in two (e.g., different) beamforming directions.
[0093] Additionally or alternatively, the random access procedure configuration may include a repetition number, which may indicate a number of RACH message repetitions (e.g., repetitions of RACH message 315) to be sent by UE 115. Figure 3 In the example of , the value of the number of repetitions can be about four. That is, the random access procedure configuration can instruct UE 115 to send four RACH messages 315 (e.g., RACH message 315-a, RACH message 315-b, RACH message 315-c, and RACH message 315-d). In some examples, a single (e.g., one) association period 325 (e.g., a PRACH association period) may not support each (e.g., all) RACH message repetitions (e.g., the number of RACH message repetitions) indicated by the random access procedure configuration. Thus, UE 115 can send RACH message repetitions across multiple association periods (e.g., association period 325-a and association period 325-b). That is, in some examples, RACH message repetitions can span association periods. For example, UE 115 may send a first portion of the number of RACH message repetitions (e.g., RACH message 315-a and RACH message 315-b) during association period 325-a, and send a second portion of the number of RACH message repetitions (e.g., RACH message 315-c and RACH message 315-d) during association period 325-b. In some examples, association period 325-b may occur at a time after association period 325-a. In some examples, by sending multiple RACH messages 315 on a non-anchor carrier (e.g., carrier 320), UE 115 may reduce power consumption while providing one or more enhancements to inter-band carrier aggregation communications.
[0094] Figure 4 An example of a timing diagram 400 for supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers according to one or more aspects of the present disclosure is illustrated. In some examples, the timing diagram 400 may implement or be implemented by one or more aspects of the wireless communication system 100 and the wireless communication system 200. For example, the timing diagram 400 may be implemented by the UE 115 or the network entity 105 (which may be as described in reference to Figure 1 and Figure 2A The corresponding device example described above is implemented. Figure 4 In the example of Figure 1 The CU, DU, RU, base station, IAB node or one or more other network node examples. Additionally or alternatively, in Figure 4 In the example of , the non-SSB carrier may be referred to as a non-anchor carrier. Timing diagram 400 may include features for improving communications between network entity 105 and UE 115, as well as other benefits.
[0095] For example, Figure 4 As illustrated in the example of , the network may instruct UE 115 to send multiple RACH messages (e.g., RACH message 415-a, RACH message 415-b, RACH message 415-c, RACH message 415-d) on multiple carriers (e.g., component carriers). That is, the network may configure UE 115 for RACH transmission via rules included in the random access procedure configuration. The random access procedure configuration may be as shown in reference Figure 2A and Figure 3 An example of a random access procedure configuration as described. In some examples, the rule may indicate that the multiple carriers include at least one non-anchor carrier. In such an example, if the UE 115 is configured with multiple RACH transmissions (e.g., configured to send multiple RACH messages 415), the UE 115 may send multiple RACH messages 415 on multiple carriers 420 (e.g., carrier 420-a and carrier 420-b). In some examples, by instructing the UE 115 to send multiple RACH messages 415 on multiple carriers, the network may improve PRACH performance, for example, via frequency hopping (e.g., for adjacent bands, such as approximately 700 MHz and approximately 800 MHz or one or more other adjacent band combinations). Additionally or alternatively, by instructing the UE 115 to send multiple RACH messages 415 on multiple carriers, the network may reduce the latency associated with the transmission of multiple RACH messages (e.g., performing multiple PRACH transmissions). Figure 4 In the example of , at least one of carrier 420-a and carrier 420-b may be a non-anchor carrier. Additionally or alternatively, carrier 420-a or carrier 420-b may be an anchor carrier.
[0096] In some examples, the random access procedure configuration may include a mapping of one or more RACH opportunities 405 to one or more SSB indices. In some examples, the mapping may be associated with one or more parameters. For example, the mapping may provide a relationship between the number of RACH opportunities 405 and the number of SSBs according to a parameter (N). Figure 4In the example of , the parameter (N) may have a value equal to approximately one-half (e.g., 1 / 2, 0.5). That is, the same SSB index may be mapped to two RACH opportunity indices. For example, the RACH opportunity 405 corresponding to index RO#0 (e.g., RACH opportunity 405-a and RACH opportunity 405-e) and the RACH opportunity 405 corresponding to index RO#1 (e.g., RACH opportunity 405-b and RACH opportunity 405-f) may be mapped to the first SSB index 410 (e.g., SSB#0). Additionally or alternatively, the RACH opportunity 405 corresponding to index RO#2 (e.g., RACH opportunity 405-c and RACH opportunity 405-g) and the RACH opportunity 405 corresponding to index RO#3 (e.g., RACH opportunity 405-d and RACH opportunity 405-h) may be mapped to the second SSB index 411 (e.g., SSB#1).
[0097] Additionally or alternatively, the mapping may indicate the PRACH frequency resources to the UE 115 via a parameter (M) which may be equal to approximately two. That is, the configured RACH occasions 405 may occur on two PRACH frequency resources. Additionally or alternatively, the mapping may provide where the PRACH frequency resources are indicated via the parameter (M). The number of directions in which the SSBs are transmitted may be equal to about two. That is, the SSBs used by the UE 115 (eg, the SSB corresponding to the first SSB index 410 and the SSB corresponding to the second SSB index 411) may be transmitted by the network entity 105 in two beamforming directions.
[0098] Additionally or alternatively, the random access procedure configuration may include a number of repetitions, which may be equal to approximately four. That is, the random access procedure configuration may instruct UE 115 to send four RACH messages 415 (e.g., RACH message 415-a, RACH message 415-b, RACH message 415-c, and RACH message 415-d). In some examples, UE 115 may send a first portion of the number of RACH message repetitions (e.g., RACH message 415-a and RACH message 415-b) on a first carrier (e.g., carrier 420-a) and send a second portion of the number of RACH message repetitions (e.g., RACH message 415-c and RACH message 415-d) on a second carrier (e.g., carrier 420-b). Figure 4 In the example of , the second portion of the number of RACH message repetitions may be sent after the first portion of the number of RACH message repetitions. For example, RACH message 415-c and RACH message 415-d may be sent after RACH message 415-a and RACH message 415-b.
[0099] In some examples, if UE 115 is configured to send multiple RACH messages 415 on multiple non-anchor carriers (or multiple carriers that may include at least one non-anchor carrier) (e.g., if UE 115 is configured with multiple PRACH transmissions), the UE may utilize (e.g., use) a common (e.g., the same) spatial filter across the multiple carriers or a spatial filter that varies from carrier to carrier to perform each of the PRACH transmissions. That is, UE 115 may use a first spatial filter to send a first portion of the number of RACH message repetitions (e.g., RACH message 415-a and RACH message 415-b) and use a second spatial filter to send a second portion of the number of RACH message repetitions (e.g., RACH message 415-c and RACH message 415-d), and the second spatial filter may be the same spatial filter as the first spatial filter or a spatial filter different from the first spatial filter.
[0100] Additionally or alternatively, if the UE 115 is configured to send multiple RACH messages 415 across multiple non-anchor carriers (or multiple carriers that may include at least one non-anchor carrier), the UE 115 may send the multiple RACH messages 415 according to an order that may be based on identifiers (e.g., RACH opportunity indexes) of the RACH opportunities in which the multiple RACH messages 415 are mapped. For example, a first RACH message 415 may be sent in a RACH opportunity 405 associated with a relatively low RACH opportunity index (e.g., a lowest valid identifier or otherwise suitable valid identifier) in a radio frequency band having a relatively low or relatively high frequency (e.g., on a first carrier having a lowest frequency, a highest frequency, or an otherwise acceptable frequency compared to other carriers configured at the UE 115 for sending RACH messages 415). That is, the first RACH message 415 (e.g., the start of RACH message repetition, the start of a PRACH transmission count) may occur from a RACH opportunity 405 associated with a first carrier of a radio frequency band that includes a relatively low frequency, a relatively high frequency, or an otherwise suitable frequency compared to other radio frequency bands configured at the UE 115 for sending the RACH message 415. As an illustrative example, the UE 115 may send the first RACH message 415 (e.g., RACH message 415-a) on a RACH opportunity 405-a (e.g., corresponding to index RO#0) via a carrier 420-a (e.g., a carrier of a radio frequency band that includes a relatively low frequency compared to the frequencies of other configured radio frequency bands). Additionally or alternatively, the first RACH message 415 (e.g., the start of RACH message repetition, the start of a PRACH transmission count) may occur from a RACH opportunity 405 associated with a carrier of the radio frequency band configured by the network (e.g., with the lowest valid identifier or with an otherwise suitable valid identifier). That is, in some examples, carrier 420-a may be associated with a radio frequency band indicated by the network to UE 115.
[0101] In some examples, by sending multiple RACH messages 415 on multiple carriers (e.g., carrier 420-a and carrier 420-b), UE 115 can reduce power consumption while providing one or more enhancements to inter-band carrier aggregation communications.
[0102] Figure 5 An example of a timing diagram 500 for supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers according to one or more aspects of the present disclosure is illustrated. In some examples, the timing diagram 500 may implement or be implemented by one or more aspects of the wireless communication system 100 and the wireless communication system 200. For example, the timing diagram 500 may be implemented by the UE 115 or the network entity 105 (which may be as described in reference to Figure 1 and Figure 2A The corresponding device example described above is implemented. Figure 5 In the example of Figure 1 The CU, DU, RU, base station, IAB node or one or more other network node examples. Additionally or alternatively, in Figure 5 In the example of , the non-SSB carrier may be referred to as a non-anchor carrier. Timing diagram 500 may include features for improving communications between network entity 105 and UE 115, as well as other benefits.
[0103] As illustrated in timing diagram 500, the network may instruct UE 115 to send multiple RACH messages (e.g., RACH message 515-a, RACH message 515-b, RACH message 515-c, and RACH message 515-d) on multiple carriers (e.g., component carriers). For example, the network may configure UE 115 for RACH transmissions via rules included in a random access procedure configuration. The random access procedure configuration may be as described in reference to Figure 2A , Figure 3 and Figure 4 In some examples, the rule may indicate that the multiple carriers include at least one non-anchor carrier. In such an example, if UE 115 is configured with multiple RACH transmissions (e.g., configured to send multiple RACH messages 515), UE 115 may send multiple RACH messages 515 on multiple carriers 520 (e.g., carrier 520-a and carrier 520-b). Figure 5 In the example of , at least one of carrier 520-a and carrier 520-b may be a non-anchor carrier. Additionally or alternatively, carrier 520-a or carrier 520-b may be an anchor carrier.
[0104] In some examples, the random access procedure configuration may include a mapping of RACH opportunities 505 that may be associated with one or more parameters (e.g., to one or more SSB indices). For example, the mapping may provide a relationship between the number of RACH opportunities 505 and the number of SSBs according to a parameter (N), which may have a value equal to approximately one-half (e.g., 1 / 2, 0.5). That is, the same SSB index may be mapped to two RACH opportunity indices. For example, a RACH opportunity 505 corresponding to index RO#0 (e.g., RACH opportunity 505-a and RACH opportunity 505-e) and a RACH opportunity 505 corresponding to index RO#1 (e.g., RACH opportunity 505-b and RACH opportunity 505-f) may be mapped to a first SSB index 510 (e.g., SSB#0). Additionally or alternatively, the RACH timings 505 corresponding to index RO#2 (e.g., RACH timing 505-c and RACH timing 505-g) and the RACH timings 505 corresponding to index RO#3 (e.g., RACH timing 505-d and RACH timing 505-h) may be mapped to a second SSB index 511 (e.g., SSB#1).
[0105] Additionally or alternatively, the mapping may indicate the PRACH frequency resources to the UE 115 via a parameter (M) which may be equal to approximately two. That is, the configured RACH occasions 505 may occur on two PRACH frequency resources. Additionally or alternatively, the mapping may provide where the PRACH frequency resources are indicated via the parameter (M). The number of directions in which the SSBs are transmitted may be equal to about two. That is, the SSBs used by the UE 115 (eg, the SSB corresponding to the first SSB index 510 and the SSB corresponding to the second SSB index 511) may be transmitted by the network entity 105 in two beamforming directions.
[0106] Additionally or alternatively, the random access procedure configuration may include a number of repetitions, which may be equal to approximately four. That is, the random access procedure configuration may instruct UE 115 to send four RACH messages 515 (e.g., RACH message 515-a, RACH message 515-b, RACH message 515-c, and RACH message 515-d). In some examples, UE 115 may send a first portion of the number of RACH message repetitions (e.g., RACH message 515-a and RACH message 515-b) on a first carrier (e.g., carrier 520-a) and send a second portion of the number of RACH message repetitions (e.g., RACH message 515-c and RACH message 515-d) on a second carrier (e.g., carrier 520-b). Figure 5In the example of , the second portion of the number of RACH message repetitions may be sent simultaneously with the first portion of the number of RACH message repetitions. For example, RACH message 515-c and RACH message 515-d may be sent simultaneously with RACH message 515-a and RACH message 515-b.
[0107] Figure 6 An example of a timing diagram 600 for supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers according to one or more aspects of the present disclosure is illustrated. In some examples, the timing diagram 600 may implement or be implemented by one or more aspects of the wireless communication system 100 and the wireless communication system 200. For example, the timing diagram 600 may be implemented by the UE 115 or the network entity 105 (which may be as described in reference to Figure 1 and Figure 2A The corresponding device example described above is implemented. Figure 6 In the example of Figure 1 The CU, DU, RU, base station, IAB node or one or more other network node examples. Additionally or alternatively, in Figure 6 In the example of , the non-SSB carrier may be referred to as a non-anchor carrier. Timing diagram 600 may include features for improving communications between network entity 105 and UE 115, as well as other benefits.
[0108] As illustrated in timing diagram 600, the network may instruct UE 115 to send multiple RACH messages (e.g., RACH message 615-a, RACH message 615-b, RACH message 615-c, RACH message 615-d) on multiple carriers (e.g., component carriers). For example, the network may configure UE 115 for RACH transmissions via rules included in a random access procedure configuration. The random access procedure configuration may be as described in reference to Figure 2A , Figure 3 , Figure 4 and Figure 5 In some examples, the rule may indicate that the multiple carriers include at least one non-anchor carrier. In such an example, if UE 115 is configured with multiple RACH transmissions (e.g., configured to send multiple RACH messages 615), UE 115 may send multiple RACH messages 615 on multiple carriers 620 (e.g., carrier 620-a and carrier 620-b). Figure 6 In the example of , at least one of carrier 620-a and carrier 620-b may be a non-anchor carrier. Additionally or alternatively, carrier 620-a or carrier 620-b may be an anchor carrier.
[0109] In some examples, the random access procedure configuration may include a mapping of RACH opportunities 605 (e.g., to one or more SSB indices) that may be associated with one or more parameters. For example, the mapping may provide a relationship between the number of RACH opportunities 605 and the number of SSBs according to a parameter (N), which may have a value equal to approximately one-fourth (e.g., 1 / 4, 0.25). That is, the same SSB index may be mapped to four RACH opportunity indices. For example, a RACH opportunity 605 corresponding to index RO#0 (e.g., RACH opportunity 605-a and RACH opportunity 605-i), a RACH opportunity 605 corresponding to index RO#1 (e.g., RACH opportunity 605-b and RACH opportunity 605-j), a RACH opportunity 605 corresponding to index RO#2 (RACH opportunity 605-c and RACH opportunity 605-k), and a RACH opportunity 605 corresponding to index RO#3 (RACH opportunity 605-d and RACH opportunity 605-l) may be mapped to a first SSB index 610 (e.g., SSB#0). Additionally or alternatively, the RACH timing 605 corresponding to index RO#4 (e.g., RACH timing 605-e and RACH timing 605-m), the RACH timing 605 corresponding to index RO#5 (e.g., RACH timing 605-f and RACH timing 605-n), the RACH timing 605 corresponding to index RO#6 (RACH timing 605-g and RACH timing 605-o), and the RACH timing 605 corresponding to index RO#7 (RACH timing 605-h and RACH timing 605-p) may be mapped to a second SSB index 611 (e.g., SSB#1).
[0110] Additionally or alternatively, the mapping may indicate the PRACH frequency resources to the UE 115 via a parameter (M) which may be equal to approximately four. That is, the configured RACH occasions 605 may occur on four PRACH frequency resources. Additionally or alternatively, the mapping may provide where the PRACH frequency resources are indicated via the parameter (M). The number of directions in which the SSBs are transmitted may be equal to about two. That is, the SSBs used by the UE 115 (eg, the SSB corresponding to the first SSB index 610 and the SSB corresponding to the second SSB index 611) may be transmitted by the network entity 105 in two beamforming directions.
[0111] Additionally or alternatively, the random access procedure configuration may include a repetition number, which may be equal to approximately four. That is, the random access procedure configuration may instruct the UE 115 to send four RACH messages 615 (e.g., RACH message 615-a, RACH message 615-b, RACH message 615-c, and RACH message 615-d). In some examples, the UE 115 may send the RACH message 615 on multiple carriers (e.g., carrier 620-a and carrier 620-b) according to a transmission order. For example, the UE 115 may send the RACH message 615 in a sequence order (e.g., the RACH message may be sequentially mapped to valid RACH opportunities in carrier 620-a and carrier 620-b). That is, the UE 115 may send repetitions of the RACH message 615 on carrier 620-a and carrier 620-b according to the sequence order of the RACH message 615. In some examples, the sequence order may correspond to the order of the RACH opportunity indexes. For example, UE 115 may sequentially send RACH message 615-a, RACH message 615-b, RACH message 615-c, and RACH message 615-d during RACH opportunity 605 according to the order of corresponding RACH opportunity indexes (e.g., RACH opportunity index RO#0, RACH opportunity index RO#1, RACH opportunity index RO#2, RACH opportunity index RO#3). Thus, UE 115 may send RACH message 615-a, RACH message 615-b, RACH message 615-c, and RACH message 615-d on carrier 620-a (e.g., a first carrier). In some examples, by sending multiple RACH messages 615 on multiple carriers (e.g., carrier 620-a and carrier 620-b) according to the order, UE 115 may improve carrier aggregation communication between the network and UE 115.
[0112] Figure 7 An example of a timing diagram 700 for supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers according to one or more aspects of the present disclosure is illustrated. In some examples, the timing diagram 700 may implement or be implemented by one or more aspects of the wireless communication system 100 and the wireless communication system 200. For example, the timing diagram 700 may be implemented by the UE 115 or the network entity 105 (which may be as described in reference to Figure 1 and Figure 2A The corresponding device example described above is implemented. Figure 7 In the example of Figure 1 The CU, DU, RU, base station, IAB node or one or more other network node examples. Additionally or alternatively, in Figure 7In the example of , the non-SSB carrier may be referred to as a non-anchor carrier. Timing diagram 700 may include features for improving communications between network entity 105 and UE 115, as well as other benefits.
[0113] As illustrated in timing diagram 700, the network may instruct UE 115 to send multiple RACH messages (e.g., RACH message 715-a, RACH message 715-b, RACH message 715-c, RACH message 715-d) on multiple carriers (e.g., component carriers). For example, the network may configure UE 115 for RACH transmissions via rules included in a random access procedure configuration. The random access procedure configuration may be as described in reference to Figure 2A , Figure 3 , Figure 4 , Figure 5 and Figure 6 In some examples, the rule may indicate that the multiple carriers include at least one non-anchor carrier. In such an example, if UE 115 is configured with multiple RACH transmissions (e.g., configured to send multiple RACH messages 715), UE 115 may send multiple RACH messages 715 on multiple carriers 720 (e.g., carrier 720-a and carrier 720-b). Figure 7 In the example of , at least one of carrier 720-a and carrier 720-b may be a non-anchor carrier. Additionally or alternatively, carrier 720-a or carrier 720-b may be an anchor carrier.
[0114] In some examples, the random access procedure configuration may include a mapping of RACH opportunities (e.g., to one or more SSB indices) that may be associated with one or more parameters. For example, the mapping may provide a relationship between the number of RACH opportunities 705 and the number of SSBs according to a parameter (N), which may have a value equal to approximately one-fourth (e.g., 1 / 4, 0.25). That is, the same SSB index may be mapped to four RACH opportunity indices. For example, a RACH opportunity 705 corresponding to index RO#0 (e.g., RACH opportunity 705-a and RACH opportunity 705-i), a RACH opportunity 705 corresponding to index RO#1 (e.g., RACH opportunity 705-b and RACH opportunity 705-j), a RACH opportunity 705 corresponding to index RO#2 (RACH opportunity 705-c and RACH opportunity 705-k), and a RACH opportunity 705 corresponding to index RO#3 (RACH opportunity 705-d and RACH opportunity 705-l) may be mapped to a first SSB index 710 (e.g., SSB#0). Additionally or alternatively, the RACH timing 705 corresponding to index RO#4 (e.g., RACH timing 705-e and RACH timing 705-m), the RACH timing 705 corresponding to index RO#5 (e.g., RACH timing 705-f and RACH timing 705-n), the RACH timing 705 corresponding to index RO#6 (RACH timing 705-g and RACH timing 705-o), and the RACH timing 705 corresponding to index RO#7 (RACH timing 705-h and RACH timing 705-p) may be mapped to a second SSB index 711 (e.g., SSB#1).
[0115] Additionally or alternatively, the mapping may indicate the PRACH frequency resources to the UE 115 via a parameter (M) which may be equal to approximately four. That is, the configured RACH occasions 705 may occur on four PRACH frequency resources. Additionally or alternatively, the mapping may provide where the PRACH frequency resources are indicated via the parameter (M). The number of directions in which the SSBs are transmitted may be equal to about two. That is, the SSBs used by the UE 115 (eg, the SSB corresponding to the first SSB index 710 and the SSB corresponding to the second SSB index 711) may be transmitted by the network entity 105 in two beamforming directions.
[0116] Additionally or alternatively, the random access procedure configuration may include a repetition number, which may be equal to approximately four. That is, the random access procedure configuration may instruct the UE 115 to send four RACH messages 715 (e.g., RACH message 715-a, RACH message 715-b, RACH message 715-c, and RACH message 715-d). In some examples, the UE 115 may send the RACH message 715 on multiple carriers (e.g., carrier 720-a and carrier 720-b) according to a transmission order. For example, the UE 115 may send a subset of the RACH messages 715 (e.g., half of the configured repetitions) in a first carrier (e.g., carrier 720-a) and send another subset of the RACH messages 715 (e.g., the remaining RACH message repetitions configured for the UE) in a second carrier (e.g., carrier 720-a). That is, UE 115 may send a first portion of RACH message 715 (e.g., RACH message 715-a and RACH message 715-b) on carrier 720-a and send a second portion of RACH message 715 (e.g., RACH message 715-c and RACH message 715-d) on carrier 720-b. In some examples, UE 115 may send the second portion of RACH message 715 after the first portion of RACH message 715 based on the ordering.
[0117] Figure 8 An example of a process flow 800 for supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers according to one or more aspects of the present disclosure is illustrated. In some examples, the process flow 800 can implement one or more aspects of the wireless communication system 100 and the wireless communication system 200. For example, the process flow 800 can include example operations associated with the network entity 805 and the UE 815, which can be referenced Figure 1 and Figure 2A Examples of the corresponding devices described. Figure 8 In the example of FIG. 8 , the network entity 805 may be as shown in FIG. Figure 1 The CU, DU, RU, base station, IAB node or one or more other network node examples. Additionally or alternatively, in Figure 8 In the example of , the non-SSB carrier may be referred to as a non-anchor carrier. Operations performed by the network entity 805 and the UE 815 may support improvements to communications between the UE 815 and the network entity 805, as well as other benefits.
[0118] In some examples, the network entity 805 may configure the UE 815 with one or more rules for performing carrier aggregation with a non-anchor carrier. For example, at 820, the UE 815 may receive a first message including first information indicating an inter-band carrier aggregation configuration. In some examples, the inter-band carrier aggregation configuration may be as described in reference Figure 2A , Figure 3 , Figure 4 , Figure 5 , Figure 6 and Figure 7 For example, the inter-band carrier aggregation configuration may identify a set of carriers (eg, component carriers) used for carrier aggregation communications between the UE 815 and the network entity 805.
[0119] At 825, UE 815 may receive a second message including second information indicating a random access procedure configuration. In some examples, the random access procedure configuration may be as described in reference Figure 2A , Figure 3 , Figure 4 , Figure 5 , Figure 6 and Figure 7 An example of a random access procedure configuration. For example, the random access procedure configuration may include rules regarding whether a RACH message may be sent on multiple carriers. Additionally or alternatively, the random access procedure configuration may include a mapping of RACH opportunities to one or more SSB indices (e.g., each RACH opportunity corresponds to an SSB) and a repetition number indicating the number of RACH message repetitions to be sent by the UE 815.
[0120] At 830, UE 815 may send a RACH message based on the mapping (e.g., the number of RACH message repetitions). In some examples, the RACH message may be sent on one carrier or on multiple carriers (e.g., in a set of carriers) based on a rule. In some examples, by configuring UE 815 with a rule as to whether a RACH message may be sent on multiple carriers, network entity 805 may reduce power consumption while providing one or more enhancements to user experience and system efficiency.
[0121] Fig. 9 A block diagram 900 of a device 905 supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of a UE 115 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).
[0122] The receiver 910 may provide means 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 related to cross-carrier RACH transmissions for inter-band carrier aggregation with no SSB carriers). The information may be communicated to other components of the device 905. The receiver 910 may utilize a single antenna or a collection of multiple antennas.
[0123] The transmitter 915 may provide means for transmitting signals generated by other components of the device 905. For example, the transmitter 915 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to cross-carrier RACH transmissions for inter-band carrier aggregation with no SSB carriers), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 915 may be co-located with the receiver 910 in a transceiver module. The transmitter 915 may utilize a single antenna or a collection of multiple antennas.
[0124] The communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers (e.g., non-anchor carriers) as described herein. For example, the communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof or components may support methods for performing one or more of the functions described herein.
[0125] In some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which is configured to or otherwise supports components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory by the processor).
[0126] Additionally or alternatively, in some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured or otherwise supported to perform the functions described in the present disclosure).
[0127] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the receiver 910, the transmitter 915, or both. For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated in conjunction with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.
[0128] According to examples as disclosed herein, the communication manager 920 may support wireless communications at a UE (e.g., device 905). For example, the communication manager 920 may be configured to or otherwise support a component for receiving a first message, the first message including first information indicating an inter-band carrier aggregation configuration, the inter-band carrier aggregation configuration identifying a carrier set for carrier aggregation communications between the UE and a network entity. The communication manager 920 may be configured to or otherwise support a component for receiving a second message, the second message including second information indicating a random access procedure configuration, the random access procedure configuration including rules regarding whether to send a RACH message on multiple carriers, a mapping of a set of multiple RACH opportunities to at least one SSB index, and a repetition number indicating a number of RACH message repetitions to be sent by the UE. The communication manager 920 may be configured to or otherwise support a component for sending the number of RACH message repetitions based on the mapping, wherein the number of RACH message repetitions is sent on one carrier or on multiple carriers in the carrier set based on the rule.
[0129] By including or configuring the communication manager 920 according to the examples described herein, the device 905 (e.g., a processor controlling or otherwise coupling the receiver 910, the transmitter 915, the communication manager 920, or a combination thereof) can support techniques for reducing power consumption and more efficiently utilizing communication resources.
[0130] Fig.10A block diagram 1000 of a device 1005 supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the device 905 or UE 115 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).
[0131] The receiver 1010 may provide means 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 related to cross-carrier RACH transmissions for inter-band carrier aggregation with no SSB carriers). The information may be communicated to other components of the device 1005. The receiver 1010 may utilize a single antenna or a collection of multiple antennas.
[0132] The transmitter 1015 may provide means for transmitting signals generated by other components of the device 1005. For example, the transmitter 1015 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to cross-carrier RACH transmissions for inter-band carrier aggregation with no SSB carriers), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 1015 may be co-located with the receiver 1010 in a transceiver module. The transmitter 1015 may utilize a single antenna or a collection of multiple antennas.
[0133] The device 1005 or its various components may be examples of components for performing various aspects of cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carrier (e.g., non-anchor carrier) as described herein. For example, the communication manager 1020 may include a carrier aggregation configuration component 1025, a random access procedure configuration component 1030, a RACH message component 1035, or any combination thereof. The communication manager 1020 may be an example of various aspects of the communication manager 920 as described herein. In some examples, the communication manager 1020 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 1010, the transmitter 1015, or both. 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, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.
[0134] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a UE (e.g., device 1005). The carrier aggregation configuration component 1025 may be configured to or otherwise support means for receiving a first message, the first message including first information indicating an inter-band carrier aggregation configuration, the inter-band carrier aggregation configuration identifying a carrier set for carrier aggregation communications between the UE and a network entity. The random access procedure configuration component 1030 may be configured to or otherwise support means for receiving a second message, the second message including second information indicating a random access procedure configuration, the random access procedure configuration including rules regarding whether to send a RACH message on multiple carriers, a mapping of a set of multiple RACH opportunities to at least one SSB index, and a repetition number indicating a number of RACH message repetitions to be sent by the UE. The RACH message component 1035 may be configured to or otherwise support means for sending the number of RACH message repetitions based on the mapping, wherein the number of RACH message repetitions is sent on one carrier or on multiple carriers in the carrier set based on the rule.
[0135] Fig.11 A block diagram 1100 of a communication manager 1120 supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers is shown in accordance with one or more aspects of the present disclosure. The communication manager 1120 may be an example of aspects of the communication manager 920, the communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of components for performing various aspects of cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers (e.g., non-anchor carriers) as described herein. For example, the communication manager 1120 may include a carrier aggregation configuration component 1125, a random access procedure configuration component 1130, a RACH message component 1135, an association period component 1140, a sorting component 1145, a radio band indication component 1150, a RACH identifier component 1155, a spatial filter component 1160, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).
[0136] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a UE (e.g., UE 115). The carrier aggregation configuration component 1125 may be configured to or otherwise support means for receiving a first message, the first message including first information indicating an inter-band carrier aggregation configuration, the inter-band carrier aggregation configuration identifying a carrier set for carrier aggregation communications between the UE and a network entity. The random access procedure configuration component 1130 may be configured to or otherwise support means for receiving a second message, the second message including second information indicating a random access procedure configuration, the random access procedure configuration including rules regarding whether to send a RACH message on multiple carriers, a mapping of a set of multiple RACH opportunities to at least one SSB index, and a repetition number indicating a number of RACH message repetitions to be sent by the UE. The RACH message component 1135 may be configured to or otherwise support means for sending the number of RACH message repetitions based on the mapping, wherein the number of RACH message repetitions is sent on one carrier or on multiple carriers in the carrier set based on the rule.
[0137] In some examples, to support sending the number of RACH message repetitions, RACH message component 1135 can be configured or otherwise support means for sending the number of RACH message repetitions on one carrier according to a rule. In some examples, one carrier includes a non-anchor carrier.
[0138] In some examples, to support sending the number of RACH message repetitions, the association period component 1140 may be configured or otherwise support means for sending a first portion of the number of RACH message repetitions on one carrier during a first association period and sending a second portion of the number of RACH message repetitions on one carrier during a second association period, the second association period occurring after the first association period.
[0139] In some examples, to support sending the number of RACH message repetitions, the RACH message component 1135 can be configured or otherwise support components for sending the number of RACH message repetitions on at least two of the multiple carriers according to a rule. In some examples, the at least two carriers include at least one non-anchor carrier.
[0140] In some examples, the RACH message component 1135 may be configured to or otherwise support components for sending a first portion of the number of RACH message repetitions on a first carrier of the at least two carriers and sending a second portion of the number of RACH message repetitions on a second carrier of the at least two carriers, wherein the second portion of the number of RACH message repetitions is sent simultaneously with or after the first portion of the number of RACH message repetitions.
[0141] In some examples, to support sending a first portion of the number of RACH message repetitions on a first carrier and sending a second portion of the number of RACH message repetitions on a second carrier, the spatial filter component 1160 may be configured to or otherwise support components for sending the first portion of the number of RACH message repetitions on the first carrier using a first spatial filter and sending the second portion of the number of RACH message repetitions on the second carrier using a second spatial filter, the second spatial filter being the same spatial filter as the first spatial filter or a different spatial filter from the first spatial filter.
[0142] In some examples, to support sending a first portion of the number of RACH message repetitions on a first carrier and sending a second portion of the number of RACH message repetitions on a second carrier, the ordering component 1145 may be configured to or otherwise support means for sending the second portion of the number of RACH message repetitions after the first portion of the number of RACH message repetitions based on an ordering of the number of RACH message repetitions, wherein the ordering of the number of RACH message repetitions corresponds to a mapping of a set of multiple RACH opportunities to at least one SSB index.
[0143] In some examples, to support sending the number of RACH message repetitions, the ordering component 1145 may be configured to or otherwise support means for sending the number of RACH message repetitions on at least one of the multiple carriers according to a rule and a sequence ordering of the number of RACH message repetitions, wherein the sequence ordering of the number of RACH message repetitions corresponds to a mapping of a set of multiple RACH opportunities to at least one SSB index.
[0144] In some examples, to support sending the number of RACH message repetitions, the RACH message component 1135 may be configured to or otherwise support components for sending a first RACH message repetition among the number of RACH message repetitions during a first RACH opportunity and on a first carrier among multiple carriers in accordance with a rule, wherein the first RACH opportunity is associated with a lowest RACH identifier in a set of RACH identifiers for a set of multiple RACH opportunities, and wherein the first carrier is associated with a lowest frequency radio band or a highest frequency radio band in a set of radio bands for sending the number of RACH message repetitions.
[0145] In some examples, to support sending the number of RACH message repetitions, the radio band indication component 1150 may be configured to or otherwise support means for receiving a third message including third information indicating a radio band for sending RACH message repetitions in the number of RACH message repetitions. In some examples, to support sending the number of RACH message repetitions, the RACH identifier component 1155 may be configured to or otherwise support means for sending a first RACH message repetition in the number of RACH message repetitions according to a rule during a first RACH opportunity and on a first carrier in a plurality of carriers. In some examples, the first RACH opportunity is associated with a lowest RACH identifier in a set of RACH identifiers for a set of a plurality of RACH opportunities, and the first carrier is associated with a radio band indicated by the third message.
[0146] Fig.12 A diagram of a system 1200 including a device 1205 supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of a device 905, a device 1005, or a UE 115 as described herein or include components of these devices. The device 1205 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1205 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1220, an input / output (I / O) controller 1210, a transceiver 1215, an antenna 1225, a memory 1230, a code 1235, and a processor 1240. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1245).
[0147] I / O controller 1210 can manage input and output signals for device 1205. I / O controller 1210 can also manage peripheral devices that are not integrated into device 1205. In some cases, I / O controller 1210 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1210 can utilize an operating system such as or another known operating system. Additionally or alternatively, I / O controller 1210 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1210 may be implemented as part of a processor such as processor 1240. In some cases, a user may interact with device 1205 via I / O controller 1210 or via hardware components controlled by I / O controller 1210.
[0148] In some cases, the device 1205 may include a single antenna 1225. However, in some other cases, the device 1205 may have more than one antenna 1225, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1215 may communicate bidirectionally via one or more antennas 1225, a wired or wireless link as described herein. For example, the transceiver 1215 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1215 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1225 for transmission; and demodulating packets received from one or more antennas 1225. The transceiver 1215, or the transceiver 1215 and one or more antennas 1225 may be examples of the transmitter 915, the transmitter 1015, the receiver 910, the receiver 1010, or any combination thereof or components thereof as described herein.
[0149] The memory 1230 may include random access memory (RAM) and read-only memory (ROM). The memory 1230 may store computer-readable, computer-executable code 1235 including instructions that, when executed by the processor 1240, cause the device 1205 to perform various functions described herein. The code 1235 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 1235 may not be directly executable by the processor 1240, but may cause the computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, the memory 1230 may include a basic I / O system (BIOS), etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.
[0150] The processor 1240 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1240 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1240. The processor 1240 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1230) to cause the device 1205 to perform various functions (e.g., various functions or tasks supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers). For example, the device 1205 or a component of the device 1205 may include a processor 1240 and a memory 1230 coupled to the processor 1240, and the processor 1240 and the memory 1230 are configured to perform the various functions described herein.
[0151] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a UE (e.g., device 1205). For example, the communication manager 1220 may be configured to or otherwise support a component for receiving a first message, the first message including first information indicating an inter-band carrier aggregation configuration, the inter-band carrier aggregation configuration identifying a carrier set for carrier aggregation communications between the UE and a network entity. The communication manager 1220 may be configured to or otherwise support a component for receiving a second message, the second message including second information indicating a random access procedure configuration, the random access procedure configuration including rules regarding whether to send a RACH message on multiple carriers, a mapping of a set of multiple RACH opportunities to at least one SSB index, and a repetition number indicating a number of RACH message repetitions to be sent by the UE. The communication manager 1220 may be configured to or otherwise support a component for sending the number of RACH message repetitions based on the mapping, wherein the number of RACH message repetitions is sent on one carrier or on multiple carriers in the carrier set based on the rule.
[0152] By including or configuring a communication manager 1220 according to examples as described herein, the device 1205 can support techniques for reduced power consumption, more efficient use of communication resources, and longer battery life.
[0153] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1215, one or more antennas 1225, or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the processor 1240, the memory 1230, the code 1235, or any combination thereof. For example, the code 1235 may include instructions that may be executed by the processor 1240 to cause the device 1205 to perform various aspects of cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers (e.g., non-anchor carriers) as described herein, or the processor 1240 and the memory 1230 may be otherwise configured to perform or support such operations.
[0154] Fig.13 A flow chart illustrating a method 1300 for supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers according to one or more aspects of the present disclosure is shown. The operations of the method 1300 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE or components thereof as described herein. Figures 1 to 12 The UE 115 described herein performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.
[0155] At 1305, the method may include: receiving a first message including first information indicating an inter-band carrier aggregation configuration, the inter-band carrier aggregation configuration identifying a set of carriers for carrier aggregation communications between the UE and the network entity. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Fig.11 The carrier aggregation configuration component 1125 is used to perform.
[0156] At 1310, the method may include receiving a second message including second information indicating a random access procedure configuration, the random access procedure configuration including rules regarding whether to send a RACH message on multiple carriers, a mapping of a set of multiple RACH opportunities to at least one SSB index, and a repetition number indicating a number of RACH message repetitions for transmission by the UE. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed as described in reference to Fig.11 The random access procedure is configured by component 1130 for execution.
[0157] At 1315, the method may include: sending the number of RACH message repetitions based on the mapping, wherein the number of RACH message repetitions is sent based on a rule on one carrier or on multiple carriers in a carrier set. The operations of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed as described in reference to Fig.11 The RACH message component 1135 is used to perform.
[0158] Fig.14 A flow chart illustrating a method 1400 for supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or components thereof as described herein. Figures 1 to 12 The UE 115 described herein performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.
[0159] At 1405, the method may include: receiving a first message including first information indicating an inter-band carrier aggregation configuration, the inter-band carrier aggregation configuration identifying a set of carriers for carrier aggregation communications between the UE and the network entity. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Fig.11 The carrier aggregation configuration component 1125 is used to perform.
[0160] At 1410, the method may include receiving a second message including second information indicating a random access procedure configuration, the random access procedure configuration including rules regarding whether to send a RACH message on multiple carriers, a mapping of a set of multiple RACH opportunities to at least one SSB index, and a repetition number indicating a number of RACH message repetitions for transmission by the UE. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Fig.11 The random access procedure is configured by component 1130 for execution.
[0161] At 1415, the method may include: sending the number of RACH message repetitions based on the mapping, wherein the number of RACH message repetitions are sent on one carrier according to a rule. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Fig.11 The RACH message component 1135 is used to perform.
[0162] Fig.15 A flow chart illustrating a method 1500 for supporting cross-carrier RACH transmission for inter-band carrier aggregation with no SSB carriers according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or components thereof as described herein. Figures 1 to 12 The UE 115 described herein performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.
[0163] At 1505, the method may include: receiving a first message including first information indicating an inter-band carrier aggregation configuration, the inter-band carrier aggregation configuration identifying a set of carriers for carrier aggregation communications between the UE and the network entity. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig.11 The carrier aggregation configuration component 1125 is used to perform.
[0164] At 1510, the method may include receiving a second message including second information indicating a random access procedure configuration, the random access procedure configuration including rules regarding whether to send a RACH message on multiple carriers, a mapping of a set of multiple RACH opportunities to at least one SSB index, and a repetition number indicating a number of RACH message repetitions for transmission by the UE. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Fig.11 The random access procedure is configured by component 1130 for execution.
[0165] At 1515, the method may include: sending the number of RACH message repetitions based on the mapping, wherein the number of RACH message repetitions are sent on at least two of the multiple carriers according to a rule. The operations of 1515 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Fig.11 The RACH message component 1135 is used to perform.
[0166] Aspect 1: A method for wireless communication at a UE, comprising: receiving a first message, the first message including first information indicating an inter-band carrier aggregation configuration, the inter-band carrier aggregation configuration identifying a carrier set used for carrier aggregation communication between the UE and a network entity; receiving a second message, the second message including second information indicating a random access procedure configuration, the random access procedure configuration including rules on whether to send a RACH message on multiple carriers, a mapping of multiple RACH opportunities to at least one SSB index, and a repetition number indicating the number of RACH message repetitions to be sent by the UE; and sending the number of RACH message repetitions based at least in part on the mapping, wherein the number of RACH messages is sent on one carrier or on the multiple carriers in the carrier set based at least in part on the rules.
[0167] Aspect 2: The method according to aspect 1, wherein sending the number of RACH message repetitions comprises: sending the number of RACH message repetitions on the one carrier according to the rule.
[0168] Aspect 3: The method according to aspect 2, wherein the one carrier comprises a non-anchor carrier.
[0169] Aspect 4: A method according to Aspect 1, wherein sending the number of RACH message repetitions includes: sending a first part of the number of RACH message repetitions on the one carrier during a first association period, and sending a second part of the number of RACH message repetitions on the one carrier during a second association period, and the second association period occurs after the first association period.
[0170] Aspect 5: The method according to aspect 1, wherein sending the number of RACH message repetitions comprises: sending the number of RACH message repetitions on at least two carriers among the multiple carriers according to the rule.
[0171] Aspect 6: The method according to aspect 5, wherein the at least two carriers include at least one non-anchor carrier.
[0172] Aspect 7: The method according to any one of Aspects 5 to 6 also includes: sending a first part of the number of RACH message repetitions on a first carrier among the at least two carriers, and sending a second part of the number of RACH message repetitions on a second carrier among the at least two carriers, wherein the second part of the number of RACH message repetitions is sent simultaneously with or after the first part of the number of RACH message repetitions.
[0173] Aspect 8: A method according to Aspect 7, wherein sending the first part of the number of RACH message repetitions on the first carrier and sending the second part of the number of RACH message repetitions on the second carrier includes: sending the first part of the number of RACH message repetitions on the first carrier using a first spatial filter, and sending the second part of the number of RACH message repetitions on the second carrier using a second spatial filter, wherein the second spatial filter is the same spatial filter as the first spatial filter or a spatial filter different from the first spatial filter.
[0174] Aspect 9: A method according to Aspect 7, wherein sending the first part of the number of RACH message repetitions on the first carrier and sending the second part of the number of RACH message repetitions on the second carrier includes: sending the second part of the number of RACH message repetitions after the first part of the number of RACH message repetitions based at least in part on an ordering of the number of RACH message repetitions, wherein the ordering of the number of RACH message repetitions corresponds to the mapping of the multiple RACH opportunities to the at least one SSB index.
[0175] Aspect 10: A method according to Aspect 1, wherein sending the number of RACH message repetitions comprises: sending the number of RACH message repetitions on at least one carrier among the multiple carriers according to the rule and the sequence ordering of the number of RACH message repetitions, wherein the sequence ordering of the number of RACH message repetitions corresponds to the mapping of the multiple RACH opportunities to the at least one SSB index.
[0176] Aspect 11: A method according to Aspect 1, wherein sending the number of RACH message repetitions includes: sending a first RACH message repetition among the number of RACH message repetitions during a first RACH opportunity and on a first carrier among the multiple carriers according to the rule, wherein the first RACH opportunity is associated with a lowest RACH identifier in a set of RACH identifiers used for the multiple RACH opportunities, and wherein the first carrier is associated with a lowest frequency radio band or a highest frequency radio band in a set of radio bands used to send the number of RACH message repetitions.
[0177] Aspect 12: A method according to Aspect 1, wherein sending the number of RACH message repetitions includes: receiving a third message, the third message including third information indicating a radio frequency band used to send RACH message repetitions in the number of RACH message repetitions; and sending a first RACH message repetition in the number of RACH message repetitions during a first RACH opportunity and on a first carrier in the multiple carriers according to the rule, wherein the first RACH opportunity is associated with the lowest RACH identifier in a set of RACH identifiers used for the multiple RACH opportunities, and wherein the first carrier is associated with the radio frequency band indicated by the third message.
[0178] Aspect 13: An apparatus for performing wireless communication at a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 12.
[0179] Aspect 14: An apparatus for wireless communication, comprising at least one component for performing the method according to any one of aspects 1 to 12.
[0180] Aspect 15: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 12.
[0181] It should be noted that the methods described herein describe possible implementations, and that the various operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.
[0182] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.
[0183] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.
[0184] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).
[0185] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium, or sent via a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the functions are implemented at different physical locations.
[0186] Computer-readable media include both non-transient computer storage media and communication media, including any medium that facilitates a computer program to be transferred from one place to another.Non-transient storage media can be any available medium that can be accessed by a general or special-purpose computer.By way of example and not limitation, non-transient computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage devices, disk storage devices or other magnetic storage devices, or may be used to carry or store desired program code components and any other non-transient medium that can be accessed by a general or special-purpose computer or a general or special-purpose processor in the form of an instruction or data structure.In addition, any connection is appropriately referred to as computer-readable media.For example, if software is sent from a website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable media. Disk and disc, as used herein, includes CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.
[0187] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."
[0188] The terms "determine" or "determine" encompass a variety of actions, and thus, "determine" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and similar actions. Furthermore, "determine" may include receiving (such as receiving information), accessing (such as accessing data in a memory), and similar actions. Furthermore, "determine" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.
[0189] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label regardless of the second reference label, or other subsequent reference labels.
[0190] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." The specific implementation includes specific details to provide an understanding of the technology. However, the technologies may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples.
[0191] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A method for wireless communication at a user equipment (UE), comprising: receiving a first message, the first message comprising first information indicating an inter-band carrier aggregation configuration, the inter-band carrier aggregation configuration identifying a set of carriers used for carrier aggregation communication between the UE and a network entity; receiving a second message, the second message comprising second information indicating a random access procedure configuration, the random access procedure configuration comprising rules on whether a random access channel message is to be sent on multiple carriers, a mapping of multiple random access channel opportunities to at least one synchronization signal block index, and a repetition number indicating a number of random access channel message repetitions for sending by the UE; as well as The number of random access channel message repetitions is sent based at least in part on the mapping, wherein the number of random access channel message repetitions is sent on one carrier or on the plurality of carriers in the set of carriers based at least in part on the rule.
2. The method of claim 1 , wherein sending the number of random access channel message repetitions comprises: The number of random access channel message repetitions are sent on the one carrier according to the rule.
3. The method of claim 2, wherein the one carrier comprises a non-anchor carrier.
4. The method of claim 1 , wherein sending the number of random access channel message repetitions comprises: A first portion of the number of random access channel message repetitions is sent on the one carrier during a first association period, and a second portion of the number of random access channel message repetitions is sent on the one carrier during a second association period, the second association period occurring after the first association period.
5. The method of claim 1 , wherein sending the number of random access channel message repetitions comprises: The number of random access channel message repetitions are sent on at least two carriers of the plurality of carriers according to the rule.
6. The method of claim 5, wherein the at least two carriers include at least one non-anchor carrier.
7. The method according to claim 5, further comprising: A first portion of the number of random access channel message repetitions is sent on a first carrier among the at least two carriers, and a second portion of the number of random access channel message repetitions is sent on a second carrier among the at least two carriers, wherein the second portion of the number of random access channel message repetitions is sent simultaneously with or after the first portion of the number of random access channel message repetitions.
8. The method of claim 7, wherein sending the first portion of the number of random access channel message repetitions on the first carrier and sending the second portion of the number of random access channel message repetitions on the second carrier comprises: The first portion of the number of random access channel message repetitions is sent on the first carrier using a first spatial filter, and the second portion of the number of random access channel message repetitions is sent on the second carrier using a second spatial filter, wherein the second spatial filter is the same spatial filter as the first spatial filter or a spatial filter different from the first spatial filter.
9. The method of claim 7, wherein sending the first portion of the number of random access channel message repetitions on the first carrier and sending the second portion of the number of random access channel message repetitions on the second carrier comprises: The second portion of the number of random access channel message repetitions is sent after the first portion of the number of random access channel message repetitions based at least in part on an ordering of the number of random access channel message repetitions, wherein the ordering of the number of random access channel message repetitions corresponds to the mapping of the multiple random access channel opportunities to the at least one synchronization signal block index.
10. The method of claim 1, wherein sending the number of random access channel message repetitions comprises: The number of random access channel message repetitions is sent on at least one carrier among the multiple carriers according to the rule and the sequence ordering of the number of random access channel message repetitions, wherein the sequence ordering of the number of random access channel message repetitions corresponds to the mapping of the multiple random access channel opportunities to the at least one synchronization signal block index.
11. The method of claim 1 , wherein sending the number of random access channel message repetitions comprises: A first random access channel message repetition among the number of random access channel message repetitions is sent according to the rule during a first random access channel opportunity and on a first carrier among the multiple carriers, wherein the first random access channel opportunity is associated with a lowest random access channel identifier in a set of random access channel identifiers used for the multiple random access channel opportunities, and wherein the first carrier is associated with a lowest frequency radio band or a highest frequency radio band in a set of radio bands used to send the number of random access channel message repetitions.
12. The method of claim 1, wherein sending the number of random access channel message repetitions comprises: receiving a third message including third information indicating a radio frequency band used for transmitting a random access channel message repetition of the number of random access channel message repetitions; as well as A first random access channel message repetition among the number of random access channel message repetitions is sent according to the rule during a first random access channel opportunity and on a first carrier among the multiple carriers, wherein the first random access channel opportunity is associated with a lowest random access channel identifier in a set of random access channel identifiers for the multiple random access channel opportunities, and wherein the first carrier is associated with the radio frequency band indicated by the third message.
13. A user equipment (UE) for wireless communication, comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the UE to: receiving a first message, the first message comprising first information indicating an inter-band carrier aggregation configuration, the inter-band carrier aggregation configuration identifying a set of carriers used for carrier aggregation communication between the UE and a network entity; receiving a second message, the second message comprising second information indicating a random access procedure configuration, the random access procedure configuration comprising rules on whether a random access channel message is to be sent on multiple carriers, a mapping of multiple random access channel opportunities to at least one synchronization signal block index, and a repetition number indicating a number of random access channel message repetitions for sending by the UE; as well as The number of random access channel message repetitions is sent based at least in part on the mapping, wherein the number of random access channel message repetitions is sent on one carrier or on the plurality of carriers in the set of carriers based at least in part on the rule.
14. The UE of claim 13, wherein the instructions for sending the number of random access channel message repetitions are executable by the processor to cause the UE to: The number of random access channel message repetitions are sent on the one carrier according to the rule.
15. The UE of claim 14, wherein the one carrier comprises a non-anchor carrier.
16. The UE of claim 13, wherein the instructions for sending the number of random access channel message repetitions are executable by the processor to cause the UE to: A first portion of the number of random access channel message repetitions is sent on the one carrier during a first association period, and a second portion of the number of random access channel message repetitions is sent on the one carrier during a second association period, the second association period occurring after the first association period.
17. The UE of claim 13, wherein the instructions for sending the number of random access channel message repetitions are executable by the processor to cause the UE to: The number of random access channel message repetitions are sent on at least two carriers of the plurality of carriers according to the rule.
18. The UE according to claim 17, wherein: The at least two carriers include at least one non-anchor carrier.
19. The UE of claim 17, wherein the instructions are further executable by the processor to cause the UE to: A first portion of the number of random access channel message repetitions is sent on a first carrier among the at least two carriers, and a second portion of the number of random access channel message repetitions is sent on a second carrier among the at least two carriers, wherein the second portion of the number of random access channel message repetitions is sent simultaneously with or after the first portion of the number of random access channel message repetitions.
20. The UE of claim 19, wherein the instructions for sending the first portion of the number of random access channel message repetitions on the first carrier and sending the second portion of the number of random access channel message repetitions on the second carrier are executable by the processor to cause the UE to: The first portion of the number of random access channel message repetitions is sent on the first carrier using a first spatial filter, and the second portion of the number of random access channel message repetitions is sent on the second carrier using a second spatial filter, wherein the second spatial filter is the same spatial filter as the first spatial filter or a spatial filter different from the first spatial filter.
21. The UE of claim 19, wherein the instructions for sending the first portion of the number of random access channel message repetitions on the first carrier and sending the second portion of the number of random access channel message repetitions on the second carrier are executable by the processor to cause the UE to: The second portion of the number of random access channel message repetitions is sent after the first portion of the number of random access channel message repetitions based at least in part on an ordering of the number of random access channel message repetitions, wherein the ordering of the number of random access channel message repetitions corresponds to the mapping of the multiple random access channel opportunities to the at least one synchronization signal block index.
22. The UE of claim 13, wherein the instructions for sending the number of random access channel message repetitions are executable by the processor to cause the UE to: The number of random access channel message repetitions is sent on at least one carrier among the multiple carriers according to the rule and the sequence ordering of the number of random access channel message repetitions, wherein the sequence ordering of the number of random access channel message repetitions corresponds to the mapping of the multiple random access channel opportunities to the at least one synchronization signal block index.
23. The UE of claim 13, wherein the instructions for sending the number of random access channel message repetitions are executable by the processor to cause the UE to: A first random access channel message repetition among the number of random access channel message repetitions is sent according to the rule during a first random access channel opportunity and on a first carrier among the multiple carriers, wherein the first random access channel opportunity is associated with a lowest random access channel identifier in a set of random access channel identifiers used for the multiple random access channel opportunities, and wherein the first carrier is associated with a lowest frequency radio band or a highest frequency radio band in a set of radio bands used to send the number of random access channel message repetitions.
24. The UE of claim 13, wherein the instructions for sending the number of random access channel message repetitions are executable by the processor to cause the UE to: receiving a third message including third information indicating a radio frequency band used for transmitting a random access channel message repetition among the number of random access channel message repetitions; and A first random access channel message repetition among the number of random access channel message repetitions is sent according to the rule during a first random access channel opportunity and on a first carrier among the multiple carriers, wherein the first random access channel opportunity is associated with a lowest random access channel identifier in a set of random access channel identifiers for the multiple random access channel opportunities, and wherein the first carrier is associated with the radio frequency band indicated by the third message.
25. A user equipment (UE) for wireless communication, comprising: means for receiving a first message, the first message comprising first information indicating an inter-band carrier aggregation configuration, the inter-band carrier aggregation configuration identifying a set of carriers for carrier aggregation communications between the UE and a network entity; means for receiving a second message, the second message comprising second information indicating a random access procedure configuration, the random access procedure configuration comprising rules regarding whether a random access channel message is to be sent on multiple carriers, a mapping of multiple random access channel opportunities to at least one synchronization signal block index, and a repetition number indicating a number of random access channel message repetitions for transmission by the UE; and means for sending the number of random access channel message repetitions based at least in part on the mapping, wherein the number of random access channel message repetitions is sent on a carrier or on the plurality of carriers in the set of carriers based at least in part on the rule.
26. The UE of claim 25, wherein the means for sending the number of random access channel message repetitions comprises: means for sending said number of random access channel message repetitions on said one carrier according to said rule.
27. The UE of claim 25, wherein the means for sending the number of random access channel message repetitions comprises: means for transmitting the number of random access channel message repetitions on at least two of the plurality of carriers according to the rule.
28. A non-transitory computer readable medium storing code for wireless communication, the code comprising instructions executable by a processor to: receiving a first message including first information indicating an inter-band carrier aggregation configuration, the inter-band carrier aggregation configuration identifying a set of carriers for carrier aggregation communications between a user equipment (UE) and a network entity; receiving a second message, the second message comprising second information indicating a random access procedure configuration, the random access procedure configuration comprising rules on whether a random access channel message is to be sent on multiple carriers, a mapping of multiple random access channel opportunities to at least one synchronization signal block index, and a repetition number indicating a number of random access channel message repetitions for sending by the UE; as well as The number of random access channel message repetitions is sent based at least in part on the mapping, wherein the number of random access channel message repetitions is sent on one carrier or on the plurality of carriers in the set of carriers based at least in part on the rule.
29. The non-transitory computer readable medium of claim 28, wherein the instructions for sending the number of random access channel message repetitions are executable by the processor to: The number of random access channel message repetitions are sent on the one carrier according to the rule.
30. The non-transitory computer readable medium of claim 28, wherein the instructions for sending the number of random access channel message repetitions are executable by the processor to: The number of random access channel message repetitions are sent on at least two carriers of the plurality of carriers according to the rule.
