Patent Description:
"<NPL>, provides an overview of the NR system multi-beam operation in terms of initial access procedures and mechanisms associated with synchronization, system information, and random access. , relates to a summary of an email discussion which mentions SSB index and RACH occasion index. <NPL>, focusses on several aspects of RACH procedure, including SS block to RACH resource mapping, RACH procedure timeline, search space of Msg <NUM>/<NUM>/<NUM>, Msg <NUM> power control, etc. <NPL>et al, discusses remaining issues in the random access procedure in NR.

In some aspects, a method of wireless communication, performed by a wireless node, according to claim <NUM> is provided.

In some aspects, a wireless node for wireless communication according to independent claim <NUM> is provided.

In some aspects, a method of wireless communication, performed by a wireless node, according to independent claim <NUM> is provided.

Controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform one or more techniques associated with separation of synchronization signal blocks (SSBs) for access and backhaul random access channel (RACH) transmissions, as described in more detail elsewhere herein. For example, controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform or direct operations of, for example, process <NUM> of <FIG>, process <NUM> of <FIG>, and/or other processes as described herein. Memories <NUM> and <NUM> may store data and program codes for base station <NUM> and UE <NUM>, respectively.

In some aspects, a wireless node (e.g., base station <NUM>, UE <NUM>, and/or the like) may include means for identifying a first set of synchronization signal blocks (SSBs), within a synchronization signal (SS) burst set, that are used to indicate random access channel (RACH) occasions for a first wireless link type, the SS burst set including a second set of SSBs used to indicate RACH occasions for a second wireless link type; means for transmitting a RACH message in a RACH occasion corresponding to an SSB index of an SSB included in the first set of SSBs; and/or the like. Additionally, or alternatively, a wireless node (e.g., base station <NUM>, UE <NUM>, and/or the like) may include means for configuring a synchronization signal (SS) burst set to include a first set of synchronization signal blocks (SSBs) to be used to indicate random access channel (RACH) occasions for a first wireless link type and a second set of SSBs to be used to indicate RACH occasions for a second wireless link type; means for transmitting the SS burst set; and/or the like. In some aspects, such means may include one or more components of base station <NUM> and/or UE <NUM> described in connection with <FIG>.

<FIG> shows an example frame structure <NUM> for FDD in a telecommunications system (e.g., NR). In some aspects, a scheduling unit for the FDD may frame-based, subframe-based, slot-based, symbol-based, and/or the like.

New Radio (NR) may refer to radios configured to operate according to a new air interface (e.g., other than Orthogonal Frequency Divisional Multiple Access (OFDMA)-based air interfaces) or fixed transport layer (e.g., other than Internet Protocol (IP)).

Beamforming may be supported, and beam direction may be dynamically configured.

<FIG> is a diagram illustrating examples <NUM> of radio access networks, in accordance with various aspects of the disclosure.

As shown by reference number <NUM>, a traditional (e.g., <NUM>, <NUM>, LTE, and/or the like) radio access network may include multiple base stations <NUM> (e.g., access nodes (AN)), where each base station <NUM> communicates with a core network via a wired backhaul link <NUM>, such as a fiber connection. A base station <NUM> may communicate with a UE <NUM> via an access link <NUM>, which may be a wireless link. In some aspects, a base station <NUM> shown in <FIG> may correspond to a base station <NUM> shown in <FIG>. Similarly, a UE <NUM> shown in <FIG> may correspond to a UE <NUM> shown in <FIG>.

As shown by reference number <NUM>, a radio access network may include a wireless backhaul network, where at least one base station is an anchor base station <NUM> that communicates with a core network via a wired backhaul link <NUM>, such as a fiber connection. The wireless backhaul network may include one or more non-anchor base stations <NUM>, also referred to as relay base stations, that communicate directly with or indirectly with (e.g., via one or more non-anchor base stations <NUM>) the anchor base station <NUM> via one or more backhaul links <NUM> to form a backhaul path to the core network for carrying backhaul traffic. Backhaul link <NUM> may be a wireless link. Anchor base station(s) <NUM> and/or non-anchor base station(s) <NUM> may communicate with one or more UEs <NUM> via access links <NUM>, which may be wireless links for carrying access traffic. In some aspects, an anchor base station <NUM> and/or a non-anchor base station <NUM> shown in <FIG> may correspond to a base station <NUM> shown in <FIG>. Similarly, a UE <NUM> shown in <FIG> may correspond to a UE <NUM> shown in <FIG>.

As shown by reference number <NUM>, in some aspects, a radio access network that includes a wireless backhaul network may utilize millimeter wave technology and/or directional communications (e.g., beamforming, precoding and/or the like) for communications between base stations and/or UEs (e.g., between two base stations, between two UEs, and/or between a base station and a UE). For example, wireless backhaul links <NUM> between base stations may use millimeter waves to carry information and/or may be directed toward a target base station using beamforming, precoding, and/or the like. Similarly, the wireless access links <NUM> between a UE and a base station may use millimeter waves and/or may be directed toward a target wireless node (e.g., a UE and/or a base station). In this way, inter-link interference may be reduced.

The configuration of base stations and UEs in <FIG> is shown as an example, and other examples are contemplated. For example, one or more base stations illustrated in <FIG> may be replaced by one or more UEs that communicate via a UE-to-UE access network (e.g., a peer-to-peer network, a device-to-device network, and/or the like). In this case, an anchor node may refer to a UE that is directly in communication with a base station (e.g., an anchor base station or a non-anchor base station).

<FIG> is a diagram illustrating an example <NUM> of an integrated access and backhaul (IAB) network architecture, in accordance with various aspects of the disclosure.

As shown in <FIG>, an IAB network may include anchor nodes <NUM>, or IAB donors (shown as IAB-donor), that connect to a core network via a wired connection (shown as wireline). For example, an Ng interface of an anchor node <NUM> may terminate at a core network. Additionally, or alternatively, an anchor node <NUM> may connect to one or more devices of the core network that provide a core access and mobility management function (e.g., AMF). In some aspects, an anchor node <NUM> may include a base station <NUM>, such as an anchor base station, as described above in connection with <FIG>.

As further shown in <FIG>, the IAB network may include non-anchor nodes <NUM>, or IAB nodes (shown as IAB-Node). A non-anchor node <NUM> may provide integrated access and backhaul functionality, and may include UE functions (UEF) <NUM> and access node functions (ANF) <NUM>. The UE functions <NUM> may be controlled and/or scheduled by another non-anchor node <NUM> and/or an anchor node <NUM>. The AN functions <NUM> may control and/or schedule other non-anchor nodes <NUM> and/or UEs <NUM> (e.g., which may correspond to UEs <NUM>). In some aspects, an anchor node <NUM> may include only AN functions <NUM>, and not UE functions <NUM>. That is, an anchor node <NUM> may control and schedule communications with non-anchor nodes <NUM> and/or UEs <NUM>. Additionally, or alternatively, a UE <NUM> may include only UE functions <NUM>, and not AN functions <NUM>. That is, communications of a UE <NUM> may be controlled and/or scheduled by an anchor node <NUM> and/or a non-anchor node <NUM>.

When a first node controls and/or schedules communications for a second node (e.g., when the first node provides AN functions for the second node's UE functions), the first node may be referred to as a parent node of the second node, and the second node may be referred to as a child node of the first node. Thus, an AN function <NUM> of a parent node may control and/or schedule communications for child nodes of the parent node. A parent node may be an anchor node <NUM> or a non-anchor node <NUM>, and the child node may be a non-anchor node <NUM> or a UE <NUM>. Communications of a UE function <NUM> of a child node may be controlled and/or scheduled by a parent node of the child node.

As further shown in <FIG>, a link between a UE <NUM> (e.g., which only has UE functions <NUM>, and not AN functions <NUM>) and an anchor node <NUM>, or between a UE <NUM> and a non-anchor node <NUM>, may be referred to as an access link <NUM>. Access link <NUM> may be a wireless access link that provides a UE <NUM> with radio access to a core network via an anchor node <NUM>, and optionally via one or more non-anchor nodes <NUM>.

As further shown in <FIG>, a link between an anchor node <NUM> and a non-anchor node <NUM> or between two non-anchor nodes <NUM> may be referred to as a backhaul link <NUM>. Backhaul link <NUM> may be a wireless backhaul link that provides a non-anchor node <NUM> with radio access to a core network via an anchor node <NUM>, and optionally via one or more other non-anchor nodes <NUM>. In some aspects, a backhaul link <NUM> may be a primary backhaul link (shown as backhaul link <NUM>) or a secondary backhaul link <NUM> (e.g., a backup backhaul link). In some aspects, a secondary backhaul link <NUM> may be used if a primary backhaul link fails, becomes congested, becomes overloaded, and/or the like.

In an IAB network, radio resources (e.g., time resources, frequency resources, spatial/beam resources, and/or the like) may be shared between access links and backhaul links, including for random access channel (RACH) procedures. However, access links and backhaul links may have different characteristics, use cases, deployment scenarios, requirements, and/or the like, which may complicate such resource sharing. For example, backhaul links may need to support a longer link distance than access links due to, for example, a longer distance between two access nodes (e.g., an anchor node <NUM> and a non-anchor node <NUM>, or two non-anchor nodes <NUM>) as compared to a distance between an access node and a UE <NUM>, congestion at an intermediate non-anchor node (e.g., as shown by reference number <NUM>), remote non-anchor nodes <NUM>, and/or the like.

As a result, if the same resources are used for a random access channel (RACH) procedure for both access links and backhaul links, there may be increased interference due to a smaller number of supportable cyclic shifts for the RACH procedure. Furthermore, a first RACH preamble format may be better suited for a RACH procedure on an access link, and a second RACH preamble format may be better suited for a RACH procedure on a backhaul link (e.g., due to a cyclic prefix duration that supports a larger cell radius).

Some techniques and apparatuses described herein permit separation of synchronization signal blocks (SSBs), of an SS burst set, into a first set of SSBs used for an access link RACH procedure and a second set of SSBs used for a backhaul link RACH procedure. For example, SSBs in the first set may map to RACH occasions for transmission of a RACH message (e.g., message <NUM>) for establishing an access link, and SSBs in the second set may map to RACH occasions for transmission of a RACH message (e.g., message <NUM>) for establishing a backhaul link. In this way, RACH interference may be reduced, RACH procedures for access links and backhaul links may be configured differently to support different requirements (e.g., using different RACH preambles), and/or the like. Additional details are described below.

<FIG> is a diagram illustrating an example <NUM> of separation of SSBs for access and backhaul RACH transmissions, in accordance with various aspects of the present disclosure.

As shown in <FIG>, a first wireless node <NUM> (shown as a base station) and a second wireless node <NUM> (shown as a UE) may communicate with one another. In some aspects, the first wireless node <NUM> may be a base station <NUM>, such as an anchor base station, a non-anchor base station, a parent node, a device with an AN function <NUM>, and/or the like. In some aspects, the second wireless node <NUM> may be a UE <NUM>, a base station <NUM> (e.g., a non-anchor base station), a child node, a device with a UE function <NUM>, and/or the like. The first wireless node <NUM> may control and/or schedule communications of the second wireless node <NUM>. In some aspects, the first wireless node <NUM> and the second wireless node <NUM> may communicate in an IAB network.

As shown by reference number <NUM>, the first wireless node <NUM> may configure synchronization signal blocks (SSBs), in an SS burst set, for a first wireless link type or a second wireless link type. For example, the first wireless node <NUM> may configure the SS burst set to include a first set of SSBs associated with a first wireless link type, and may configure the SS burst set to include a second set of SSBs associated with a second wireless link type. A wireless link type may include a wireless access link, a wireless backhaul link, and/or the like, as described above in connection with <FIG>.

As shown by reference number <NUM>, the first wireless node <NUM> may configure a first set of SSBs, in the SS burst set, for a first wireless link type. Such a configuration may map the first set of SSBs to random access channel (RACH) occasions (e.g., time and/or frequency resources, resource elements, and/or the like) to be used for a RACH procedure for the first wireless link type. One or more of the RACH occasions may be used by a device that receives SSBs (e.g., one or more second wireless nodes <NUM>) to transmit a RACH message (e.g., RACH message <NUM>, or MSG1) for establishing and/or communicating via a first wireless link of the first wireless link type. In example <NUM>, the first wireless node <NUM> configures SSB <NUM> and SSB <NUM>, within SS burst <NUM> of an SS burst set, for a wireless access link.

As shown by reference number <NUM>, the first wireless node <NUM> may configure a second set of SSBs, in the SS burst set, for a second wireless link type. Such a configuration may map the second set of SSBs to RACH occasions to be used for a RACH procedure for the second wireless link type. One or more of the RACH occasions may be used by a device that receives SSBs (e.g., one or more second wireless nodes <NUM>) to transmit a RACH message (e.g., RACH message <NUM>, or MSG1) for establishing and/or communicating via a second wireless link of the second wireless link type. In example <NUM>, the first wireless node <NUM> configures SSB <NUM> and SSB <NUM>, within SS burst <NUM> of an SS burst set, for a wireless backhaul link.

The first wireless link type is one of a wireless access link or a wireless backhaul link, and the second wireless link type is the other one of the wireless access link or the wireless backhaul link. For example, as shown, the first wireless link type may be a wireless access link, and the second wireless link type may be a wireless backhaul link. Alternatively, the first wireless link type may be a wireless backhaul link, and the second wireless link type may be a wireless access link. Although some techniques are described herein as separating SSBs within an SS burst set for different wireless link types, in some aspects, SSBs within an SS burst set may be separated for other types of differing configurations. In general, the first wireless node <NUM> may configure the first set of SSBs for use with a first configuration, and may configure the second set of SSBs for use with a second configuration. In some aspects, the first wireless node <NUM> may configure more than two sets of SSBs in the SS burst set, corresponding to more than two configuration types.

In some aspects, the first set of SSBs and the second set of SSBs may be mutually exclusive. That is, any SSB included in the first set may not be included in the second set, and any SSB included in the second set may not be included in the first set. Alternatively, some SSBs may be included in both the first set and the second set (e.g., some SSBs may be used for a RACH procedure for both the first wireless link type and the second wireless link type), and some SSBs may be exclusive to a single set. For example, one of the first set of SSBs or the second set of SSBs may include all SSBs in the SS burst set (e.g., SSBs that are actually transmitted), and the other of the first set or the second set may include a subset of those SSBs in the SS burst set.

As shown by reference number <NUM>, the first wireless node <NUM> may transmit the SS burst set. For example, the first wireless node <NUM> may transmit one or more SSBs on one or more resource elements configured and/or reserved for SSB transmission. In some aspects, different SSBs within an SS burst and/or an SS burst set may have different beamforming and/or precoding configurations.

As shown by reference number <NUM>, the second wireless node <NUM> may identify SSBs, in the SS burst set, relevant to the second wireless node <NUM>, depending on a type of wireless link that the second wireless node <NUM> is attempting to establish and/or use to communicate. In example <NUM>, the second wireless node <NUM> is a UE <NUM> attempting to establish a wireless access link with the first wireless node <NUM>. Thus, in this case, the second wireless node <NUM> identifies SSBs included in the first set of SSBs used for wireless access links. However, if the second wireless node <NUM> were a base station <NUM> attempting to establish a wireless backhaul link with the first wireless node <NUM>, then the second wireless node <NUM> would identify SSBs included in the second set of SSBs used for wireless backhaul links.

In some aspects, the first wireless node <NUM> may indicate the first set of SSBs and/or the second set of SSBs to the second wireless node <NUM> (e.g., using explicit signaling or implicit signaling), and the second wireless node <NUM> may identify the first set of SSBs and/or the second set of SSBs based at least in part on the indication. For example, the first wireless node <NUM> may indicate the first set of SSBs and/or the second set of SSBs in a physical broadcast channel (PBCH) communication, a system information block (SIB), remaining minimum system information (RMSI), other system information (OSI), a handover command, a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a channel state information reference signal (CSI-RS), downlink control information (DCI), a media access control (MAC) control element (MAC-CE), and/or the like. The first set of SSBs and/or the second set of SSBs may be indicated, for example, by signaling a first set of SSB indices that identify the first set of SSBs, by signaling a second set of SSB indices that identify the second set of SSBs, by signaling an index value that maps to a corresponding table entry (e.g., of a table stored by the first wireless node <NUM> and/or the second wireless node <NUM>) that indicates SSB indices of the first set of SSBs and/or the second set of SSBs, and/or the like.

Additionally, or alternatively, the first wireless node <NUM> may indicate the first set of SSBs and/or the second set of SSBs to the second wireless node <NUM> based at least in part on a RACH configuration index (sometimes referred to as a physical RACH (PRACH) configuration index), which may be indicated in system information (e.g., RMSI, OSI, a system information block, and/or the like). A RACH configuration index may indicate, for example, RACH preamble formats corresponding to RACH occasions, time resources in which those RACH occasions are located, and/or the like. For example, the RACH configuration index may indicate that a first RACH occasion is associated with a first RACH preamble format, that a second RACH occasion is associated with a second preamble format, and/or the like.

In some aspects, the first set of SSBs may be associated with the first RACH preamble format, and the second set of SSBs may be associated with the second RACH preamble format. In this case, the second wireless node <NUM> may identify the first set of SSBs by using the RACH configuration index to identify RACH occasions associated with the first preamble format, and identifying the first set of SSBs as SSBs that map to the RACH occasions associated with the first preamble format (e.g., using one or more prespecified mapping rules to map SSB indices to RACH occasions). As an example, a RACH message (e.g., MSG1) for a wireless access link may be transmitted using RACH preamble format B (e.g., wireless access links may be associated with RACH preamble format B). Additionally, or alternatively, a RACH message for a wireless backhaul link may be transmitted using RACH preamble format A (e.g., wireless backhaul links may be associated with RACH preamble format A).

In some aspects, a mapping between wireless link types and RACH preamble formats may be prespecified (e.g., in a wireless communication standard) and/or may be hard coded in memory of the first wireless node <NUM> and/or the second wireless node <NUM>. Additionally, or alternatively, the mapping may be indicated by the first wireless node <NUM> to the second wireless node <NUM>. For example, the mapping may be indicated in a PBCH communication, a SIB, RMSI, OSI, a handover command, a PSS, an SSS, a CSI-RS, DCI, a MAC-CE, and/or the like.

After identifying the set of SSBs to be used by the second wireless node <NUM> for a specific wireless link type of a wireless link to be established and/or used for communication, the second wireless node <NUM> may measure that set of SSBs. Based at least in part on such measurements, the second wireless node <NUM> may identify a specific SSB (e.g., the best SSB in the set, the SSB with characteristics and/or signal parameters that satisfy a threshold with respect to the other SSBs in the set, and/or the like), may identify a set of RACH occasions corresponding to the specific SSB, and may select (e.g., randomly, pseudo-randomly, and/or the like) a RACH occasion in the set of RACH occasions for transmission of a RACH message (e.g., MSG1).

As shown by reference number <NUM>, the second wireless node <NUM> may transmit a RACH message in a RACH occasion corresponding to an SSB index of an SSB included in the set of SSBs relevant to the second wireless node <NUM> (e.g., the first set of SSBs in example <NUM>). As described above, the second wireless node <NUM> may identify a specific SSB in the set of SSBs. The second wireless node <NUM> may then determine an SSB index of that SSB, and may determine one or more RACH occasions that map to the SSB index (e.g., using a prespecified rule that indicates a mapping of SSB indices to RACH occasions). The second wireless node <NUM> may select (e.g., randomly, pseudo-randomly, and/or the like) a RACH occasion from the one or more RACH occasions, and may transmit the RACH message in the RACH occasion. In some aspects, the second wireless node <NUM> may transmit the RACH message using a RACH preamble format corresponding to the set of SSBs and/or indicated by a RACH configuration index. By separating SSBs of an SS burst set into a first set of SSBs used for an access link RACH procedure and a second set of SSBs used for a backhaul link RACH procedure, RACH interference may be reduced, RACH procedures for access links and backhaul links may be configured differently to support different requirements (e.g., using different RACH preambles), and/or the like.

In some aspects, when the second wireless node <NUM> is in an idle mode (e.g., RRC-idle), the second wireless node <NUM> may receive an indication of only the set of SSBs for a wireless link type associated with the second wireless node <NUM> (referred to below as a first set of SSBs for example <NUM>), and may not receive an indication of the set of SSBs for a wireless link type not associated with the second wireless node <NUM> (referred to below as a second set of SSBs for example <NUM>). In example <NUM>, when in an idle mode, the second wireless node <NUM> may receive an indication of only the first set of SSBs, and may not receive an indication of the second set of SSBs. In some aspects, the indication of the first set of SSBs may be received in system information, such as a SIB, RMSI, and/or the like. In some aspects, such an indication may be <NUM> bits, and may indicate an SSB pattern for a set of <NUM> possible SSBs. The SSB pattern may indicate the SSBs included in the first set of SSBs. Thus, the second wireless node <NUM> may use this information to perform a RACH procedure and enter a connected mode (e.g., RRC-connected) with the first wireless node <NUM>.

When in the connected mode, the second wireless node <NUM> may receive a more granular indication of the first set of SSBs as compared to the indication received with the second wireless node <NUM> is in the idle mode. For example, the indication in connected mode may be <NUM> bits, with one bit corresponding to each SSB of a set of <NUM> possible SSBs. In some aspects, this indication may be indicated in a radio resource control (RRC) message (e.g., an RRC configuration message, an RRC reconfiguration message, and/or the like). Additionally, or alternatively, when in the connected mode, the second wireless node <NUM> may receive an indication of the second set of SSBs (e.g., which may not be received when the second wireless node <NUM> is in the idle mode), such as in an RRC message. In some aspects, the second wireless node <NUM> may use the indication of the second set of SSBs to perform rate matching (e.g., to rate match one or more communications, such as PDSCH communications, around the second set of SSBs). Additionally, or alternatively, the second wireless node <NUM> may perform rate matching around the first set of SSBs. In this way, spectral efficiency may be improved.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a wireless node, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where a wireless node (e.g., base station <NUM>, UE <NUM>, non-anchor base station <NUM>, UE <NUM>, non-anchor node <NUM>, UE <NUM>, wireless node <NUM>, and/or the like) performs operations associated with separation of SSBs for access and backhaul RACH transmissions.

As shown in <FIG>, process <NUM> includes identifying a first set of synchronization signal blocks (SSBs), within a synchronization signal (SS) burst set, that are used to indicate random access channel (RACH) occasions for a first wireless link type, the SS burst set including a second set of SSBs used to indicate RACH occasions for a second wireless link type (block <NUM>). The wireless node (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, and/or the like) identifies a first set of SSBs, within an SS burst set, that are used to indicate RACH occasions for a first wireless link type, as described above in connection with <FIG>. The SS burst set includes a second set of SSBs used to indicate RACH occasions for a second wireless link type.

As further shown in <FIG>, process <NUM> includes transmitting a RACH message in a RACH occasion corresponding to an SSB index of an SSB included in the first set of SSBs (block <NUM>). For example, the wireless node (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may transmit a RACH message in a RACH occasion corresponding to an SSB index of an SSB included in the first set of SSBs, as described above in connection with <FIG>.

The first wireless link type is one of a wireless access link or a wireless backhaul link, and the second wireless link type is the other one of the wireless access link or the wireless backhaul link.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a wireless node, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where a wireless node (e.g., base station <NUM>, UE <NUM>, anchor base station <NUM>, non-anchor base station <NUM>, anchor node <NUM>, non-anchor node <NUM>, wireless node <NUM>, and/or the like) performs operations associated with separation of SSBs for access and backhaul RACH transmissions.

As shown in <FIG>, process <NUM> includes configuring a synchronization signal (SS) burst set to include a first set of synchronization signal blocks (SSBs) to be used to indicate random access channel (RACH) occasions for a first wireless link type and a second set of SSBs to be used to indicate RACH occasions for a second wireless link type (block <NUM>). The base station (e.g., using controller/processor <NUM> and/or the like) configures an SS burst set to include a first set of SSBs to be used to indicate RACH occasions for a first wireless link type and a second set of SSBs to be used to indicate RACH occasions for a second wireless link type, as described above in connection with <FIG>.

As further shown in <FIG>, process <NUM> includes transmitting the SS burst set (block <NUM>). For example, the base station (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may transmit the SS burst set, as described above in connection with <FIG>.

Claim 1:
A method (<NUM>) of wireless communication performed by a wireless node, comprising:
identifying (<NUM>) a first set of synchronization signal blocks, SSBs, within a received synchronization signal, SS, burst set, wherein the first set of SSBs are used to indicate random access channel, RACH, occasions for a first wireless link type, the SS burst set including a second set of SSBs used to indicate RACH occasions for a second wireless link type, wherein the first wireless link type is one of a wireless access link or a wireless backhaul link, and wherein the second wireless link type is the other one of the wireless access link or the wireless backhaul link; and
transmitting (<NUM>) a RACH message in a RACH occasion corresponding to an SSB index of an SSB included in the first set of SSBs.